WO2025044065A1

WO2025044065A1 - Configuration method and related products

Info

Publication number: WO2025044065A1
Application number: PCT/CN2024/075633
Authority: WO
Inventors: Hang Zhang
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2023-08-31
Filing date: 2024-02-02
Publication date: 2025-03-06
Anticipated expiration: 2026-02-28

Abstract

The present disclosure provides a configuration method and related products, the method includes: a first network element receiving a first profile of a second network element, where the first profile includes at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service, the first network element determining a third network element based on the first profile of the second network element and transmitting information in the first profile to the third network element based on the first profile.

Description

CONFIGURATION METHOD AND RELATED PRODUCTS

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No. 63/535,637, filed on August 31, 2023. The disclosure of the above patent application is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the field of communication technologies, and in particular, to a configuration method and related products.

BACKGROUND

5G (5th generation) system CP (control plane) SBI (service-based interface) uses SCP (Service Communication Proxy) and NRF (network Repository Function) , etc. to support 5G CP plane indirect communication but not support strong trustworthiness. The control plane is generally used for managing state information, routing table and access control list, etc. of a network device, and communicates with other devices to realize functions such as routing. The data plane is generally used for processing and transmitting network traffic, i.e., forwarding a received data packet according to a preset rule, and ensuring that the data packet reaches a target device correctly.

This background information is provided to reveal information believed by the applicant to be of possible relevance to the present disclosure. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present disclosure.

SUMMARY

In a first aspect, an embodiment of the present disclosure provides a configuration method, where the method includes:

receiving, by a first network element, a first profile of a second network element, where the first profile includes at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service;

determining, by the first network element, a third network element based on the first profile of the second network element; and

transmitting, by the first network element, information in the first profile to the third network element based on the first profile.

In this way, by virtue of the reachable address of the second network element, a suitable third network element can be determined by the first network element and a logical and secured connection between such second network element and the third first network element can be established under the control of the first network element, and by virtue of the authorization profile, a consumer to which the second network element is capable of providing a first basic service (e.g., X as a service, XaaS for short) can be determined by the first network element and thus an appropriate third network element can be selected for the second network element, then the third first network element can be configured with the information in the first profile from the second network element, thus realizing the configuration of the third network element. In a possible implementation where both of the second network element and the third network element are gateways (also referred to as trustworthy gateways or C/M-TW-GW) , trustworthiness of the communication from perspectives of operation of the communication system (such as a 6G System) is improved by introducing anonymous service provisioning provided by the trustworthy gateways in the control/management (C/M) plane of the communication system.

In a possible implementation of the first aspect, where receiving, by the first network element, the first profile of the second network element includes: receiving, by the first network element, a registration message from the second network element, where the registration message is indicative of the first profile.

In a possible implementation of the first aspect, where receiving, by the first network element, the first profile of the second network element includes: receiving, by the first network element, a registration message from the first basic service, where the registration message is indicative of the first profile.

In a possible implementation of the first aspect, where receiving, by the first network element, the first profile of the second network element includes:

receiving, by the first network element, the first profile forwarded by the third network element from a fifth network element, where the third network element is connected with the fifth network element; or,

receiving, by the first network element, the first profile forwarded by a fourth network element from a fifth network element, where the fourth network element is connected with the fifth network element.

Based on the above, the first network element can receive the first profile of the second network element in various ways, so the reception of the first profile can be set flexibly according to actual requirements.

In a possible implementation of the first aspect, where the first profile includes the reachable address of the second network element and the authorization profile of the second network element;

where transmitting, by the first network element, the information in the first profile to the third network element based on the first profile includes:

configuring, by the first network element, a connection between the second network element and the third network element based on the reachable address of the second network element;

determining, by the first network element, the information in the first profile based on the authorization profile and the connection between the second network element and the third network element; and

transmitting, by the first network element, the information in the first profile to the third network element.

In this way, instead of transmitting all information to the third network element, the first network element simply transmits the information related to operations of the third network element in the first profile to the third network element, thus reducing the system overhead.

In a possible implementation of the first aspect, where configuring, by the first network element, the connection between the second network element and the third network element includes:

notifying, by the first network element, the third network element of the reachable address of the second network element.

notifying, by the first network element, the second network element of a reachable address of the third network element based on the reachable address of the second network element.

In a possible implementation of the first aspect, the method further includes:

receiving, by the first network element, a first notification from the third network element, where the first notification is indicative of the connection between the second network element and the third network element.

After the connection between the second network element and the third network element is established, the third network element transmits the notification indicating such connection to the first network element, so that the first network element can better manage and control the second and third network elements.

In a possible implementation of the first aspect, where the method further includes:

transmitting, by the first network element, a first acknowledgement to the third network element, where the first acknowledgement is indicative of a reception of the first notification.

In a possible implementation of the first aspect, where both of the first notification and the first acknowledgement include an identification of the first basic service.

In another possible implementation of the first aspect, where both of the first notification and the first acknowledgement include a transaction number predefined for the first basic service.

In this way, the interaction of the information between the first network element and the third network element can be performed safely and reliably.

In a possible implementation of the first aspect, where the first notification includes an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.

Similarly, the interaction of the information between the first network element and the third network element can be performed safely and reliably.

receiving, by the first network element, a load report from the third network element, where the load report is indicative of load traffic handled by the third network element.

determining, by the first network element, a further third network element based on the first profile of the second network element and the load report;

configuring, by the first network element, a connection between the second network element and the further third network element based on the reachable address of the second network element; and

transmitting, by the first network element, information in the first profile to the further third network element based on the first profile.

In this way, the first network element (e.g., a C/M function which serves as a controller) can acquire the load report of each third network element (e.g., C/M-TW-GW) that it controls and manages, and reconfigure a new C/M-TW-GW in time when the load traffic of the previously configured C/M-TW-GW does not meet the preset threshold, thereby efficiently managing and controlling the C/M-TW-GW and saving system overhead.

releasing, by the first network element, a connection between the second network element and the third network element.

In a possible implementation of the first aspect, where an occasion for reporting the load report by the third network element is configured by the first network element or predefined.

Since the occasion for reporting the load report can be configured by the first network element or predefined, the load report can be reported flexibly according to actual applications.

receiving, by the first network element, a second acknowledgement from the third network element, where the second acknowledgement is indicative of a reception of the information in the first profile.

In a possible implementation of the first aspect, where the authorization profile of the second network element includes an identification of the first basic service and an identification of the second network element;

the authorization profile of the second network element further includes at least one of following items:

an identification of a second basic service provided by the consumer and an identification of a network element of the second basic service; or,

a permissions condition for determining the consumer.

Based the information included in the authorization profile, the first network element can quickly determine the consumer to which the second network element is capable of providing the first basic service, and further determine the third network element (e.g., C/M-TW-GW) that needs to be configured, thus reducing the system overhead.

In a second aspect, an embodiment of the present disclosure provides a configuration method, where the method includes:

receiving, by a third network element, information from a first network element, where the information is included in a first profile of a second network element received by the first network element, and the first profile includes at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service.

In a possible implementation of the second aspect, where the first profile is indicated by a registration message received by the first network element from the second network element or the first basic service.

In a possible implementation of the second aspect, the method further includes:

receiving, by the third network element, the first profile from a fifth network element, where the third network element is connected with the fifth network element; and

forwarding, by the third network element, the first profile to the first network element.

In a possible implementation of the second aspect, where the first profile includes the reachable address of the second network element and the authorization profile of the second network element;

where the method further includes:

establishing, by the third network element, a connection between the second network element and the third network element based on the reachable address of the second network element; and

transmitting, by the third network element, a first notification to the first network element, where the first notification is indicative of the connection between the second network element and the third network element.

In a possible implementation of the second aspect, the method further includes:

receiving, by the third network element, a first acknowledgement from the first network element, where the first acknowledgement is indicative of a reception of the first notification.

In a possible implementation of the second aspect, where both of the first notification and the first acknowledgement include an identification of the first basic service.

In another possible implementation of the second aspect, where both of the first notification and the first acknowledgement include a transaction number predefined for the first basic service.

In a possible implementation of the second aspect, where the first notification includes an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.

In a possible implementation of the second aspect, the method further includes:

reporting, by the third network element, a load report to the first network element, where the load report is indicative of load traffic handled by the third network element.

In a possible implementation of the second aspect, the method further includes:

transmitting, by the third network element, a second acknowledgement to the first network element, where the second acknowledgement is indicative of a reception of the information in the first profile.

By receiving the acknowledgement for indicating the reception of the information in the first profile, the first network element can better manage and control the gateways.

In a third aspect, an embodiment of the present disclosure provides a configuration method, where the method includes:

receiving, by a first network element, a second profile, where the second profile includes at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, where the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element;

determining, by the first network element, the sixth network element based on the second profile; and

transmitting, by the first network element, information in the second profile to the sixth network element based on the second profile.

In this way, by virtue of the reachable address of the seventh network element, a suitable sixth network element can be determined by the first network element and a logical and secured connection between the sixth network element and such first network element can be established under the control of the first network element, and by virtue of the mission profile, an appropriate sixth network element can be selected for executing the action indicated in the mission profile, and then the sixth network element can be configured with the information in the second profile from the seventh network element, thus realizing the configuration of the sixth network element.

In a possible implementation of the third aspect, where the second profile includes the reachable address of the seventh network element;

where receiving, by the first network element, the reachable address of the seventh network element of the seventh network element includes:

receiving, by the first network element, a registration message from the seventh network element, where the registration message is indicative of the reachable address of the seventh network element.

receiving, by the first network element, a registration message from a first basic service to which the seventh network element belongs, where the registration message is indicative of the reachable address of the seventh network element.

where receiving, by the first network element, the reachable address of the seventh network element includes:

receiving, by the first network element, the reachable address of the seventh network element forwarded by the seventh network element from a fifth network element, where the seventh network element is connected with the fifth network element.

Based on the above, the first network element can receive the reachable address of the seventh network element in various ways, so the reception of the reachable address can be set flexibly according to actual requirements.

In a possible implementation of the third aspect, where the second profile includes the reachable address of the seventh network element and the mission profile of the sixth network element;

where transmitting, by the first network element, the information in the second profile to the sixth network element based on the second profile includes:

configuring, by the first network element, a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element;

determining, by the first network element, the information in the second profile based on the second profile and the connection between the sixth network element and the seventh network element; and

transmitting, by the first network element, the information in the second profile to the sixth network element.

In this way, instead of transmitting all information to the sixth network element, the first network element simply transmits the information related to operations of the sixth network element in the second profile to the sixth network element, thus reducing the system overhead.

In a possible implementation of the third aspect, where configuring, by the first network element, the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element includes:

notifying, by the first network element, the sixth network element of the reachable address of the seventh network element.

notifying, by the first network element, the seventh network element of a reachable address of the sixth network element based on the reachable address of the seventh network element.

In a possible implementation of the third aspect, where the method further includes:

receiving, by the first network element, a second notification from the sixth network element, where the second notification is indicative of the connection between the sixth network element and the seventh network element.

After the connection between the sixth network element and the seventh network element is established, the sixth network element transmits the notification indicating such connection to the first network element, so that the first network element can better manage and control the sixth and seventh network elements.

transmitting, by the first network element, a third acknowledgement to the sixth network element, where the third acknowledgement is indicative of a reception of the second notification.

In a possible implementation of the third aspect, where both of the second notification and the third acknowledgement include an identification of a first basic service to which the seventh network element belongs.

In another possible implementation of the third aspect, where both of the second notification and the third acknowledgement include a transaction number predefined for the first basic service.

In this way, the interaction of the information between the first network element and the sixth network element can be performed safely and reliably.

In a possible implementation of the third aspect, where the second notification includes an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.

Similarly, the interaction of the information between the first network element and the sixth network element can be performed safely and reliably.

receiving, by the first network element, a fourth acknowledgement from the sixth network element, where the fourth acknowledgement is indicative of a reception of the information in the second profile.

By receiving the acknowledgement for indicating the reception of the information in the second profile, the first network element can better manage and control the gateways.

In a possible implementation of the third aspect, where both of the information in the second profile and the fourth acknowledgement include an identification for indicating the mission.

In a possible implementation of the third aspect, where the information in the second profile includes an identification for indicating a first action to be performed by the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating the second action.

In a possible implementation of the third aspect, where the information in the second profile includes an identification for indicating a first action to be performed by the sixth network element, a QoS (Quality of Service) parameter of the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating a connection between the sixth network element and the next network element.

In a possible implementation of the third aspect, where the information in the second profile includes an identification for indicating a QoS parameter of the sixth network element.

receiving, by the first network element, a load report from the sixth network element, where the load report is indicative of load traffic handled by the sixth network element.

determining, by the first network element, a further sixth network element based on the second profile and the load report;

configuring, by the first network element, a connection between the seventh network element and the further sixth network element based on the reachable address of the seventh network element; and

transmitting, by the first network element, information in the second profile to the further sixth network element based on the second profile.

In this way, the first network element (e.g., a C/M function which serves as a controller) can acquire the load report of each sixth network element (e.g., Data-TW-GW) that it controls and manages, and reconfigure a new Data-TW-GW in time when the load traffic of the previously configured Data-TW-GW does not meet the preset threshold, thereby efficiently managing and controlling the Data-TW-GW and saving system overhead.

releasing, by the first network element, the connection between the sixth network element and the seventh network element.

In a possible implementation of the third aspect, where an occasion for reporting the load report by the third network element is configured by the first network element or predefined.

In a fourth aspect, an embodiment of the present disclosure provides a configuration method, the method further includes:

receiving, by a sixth network element, information from a first network element, where the information is included in a second profile received by the first network element, where the second profile includes at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, where the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element.

In a possible implementation of the fourth aspect, where the second profile includes the reachable address of the seventh network element;

where the second profile is indicated by a registration message received by the first network element from the seventh network element or a first basic service.

the method further includes:

establishing, by the sixth network element, the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; and

transmitting, by the sixth network element, a second notification to the first network element, where the second notification is indicative of the connection between the sixth network element and the seventh network element.

In a possible implementation of the fourth aspect, where the method further includes:

receiving, by the sixth network element, a third acknowledgement from the first network element, where the third acknowledgement is indicative of a reception of the second notification.

In a possible implementation of the fourth aspect, where both of the second notification and the third acknowledgement include an identification of a first basic service to which the seventh network element belongs.

In another possible implementation of the fourth aspect, where both of the second notification and the third acknowledgement include a transaction number predefined for the first basic service.

In a possible implementation of the fourth aspect, where the second notification includes an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.

transmitting, by the sixth network element, a fourth acknowledgement to the first network element, where the fourth acknowledgement is indicative of a reception of the information in the second profile.

In a possible implementation of the fourth aspect, where both of the information in the second profile and the fourth acknowledgement include an identification for indicating the mission.

reporting, by the sixth network element, a load report to the first network element, where the load report is indicative of load traffic handled by the sixth network element.

In a fifth aspect, an embodiment of the present disclosure provides a configuration apparatus, the apparatus is applied to a first network element and includes various modules configured to execute the configuration method according to the first aspect or any possible implementation of the first aspect.

In a sixth aspect, an embodiment of the present disclosure provides a configuration apparatus, the apparatus is applied to a third network element and includes various modules configured to execute the configuration method according to the second aspect or any possible implementation of the second aspect.

In a seventh aspect, an embodiment of the present disclosure provides a configuration apparatus, the apparatus is applied to a first network element and includes various modules configured to execute the configuration method according to the third aspect or any possible implementation of the third aspect.

In an eighth aspect, an embodiment of the present disclosure provides a configuration apparatus, the apparatus is applied to a sixth network element and includes various modules configured to execute the configuration method according to the fourth aspect or any possible implementation of the fourth aspect.

In a ninth aspect, an embodiment of the present disclosure provides a first network element including processing circuitry for executing the configuration method according to the first aspect or any possible implementation of the first aspect.

In a tenth aspect, an embodiment of the present disclosure provides a third network element including processing circuitry for executing the configuration method according to the second aspect or any possible implementation of the second aspect.

In an eleventh aspect, an embodiment of the present disclosure provides a first network element including processing circuitry for executing the configuration method according to the third aspect or any possible implementation of the third aspect.

In a twelfth aspect, an embodiment of the present disclosure provides a sixth network element including processing circuitry for executing the configuration method according to the fourth aspect or any possible implementation of the fourth aspect.

In a thirteenth aspect, an embodiment of the present disclosure provides a computer-readable medium storing computer execution instructions which, when executed by a processor, causes the processor to execute the configuration method according to the first aspect or any possible implementation of the first aspect, or the configuration method according to the second aspect or any possible implementation of the second aspect.

In a fourteenth aspect, an embodiment of the present disclosure provides a computer-readable medium storing computer execution instructions which, when executed by a processor, causes the processor to execute the configuration method according to the third aspect or any possible implementation of the third aspect, or the configuration method according to the fourth aspect or any possible implementation of the fourth aspect.

In a fifteenth aspect, an embodiment of the present disclosure provides a wireless system, including the first network element according to the ninth aspect and the third network element according to the tenth aspect.

In a sixteenth aspect, an embodiment of the present disclosure provides a wireless system, including the first network element according to eleventh aspect and the sixth network element according to the twelfth aspect.

In a seventeenth aspect, an embodiment of the present disclosure provides a computer program product including computer execution instructions which, when executed by a processor, causes the processor to execute the configuration method according to the first aspect or any possible implementation of the first aspect, or according to the second aspect or any possible implementation of the second aspect, or according to the third aspect or any possible implementation of the third aspect, or according to the fourth aspect or any possible implementation of the fourth aspect.

In an eighteenth aspect, an embodiment of the present disclosure an apparatus, including one or more processors, the one or more processors are configured to execute instructions stored in memory, when the instructions is executed by the one or more processors, the configuration method according to the first aspect or any possible implementation of the first aspect, or according to the second aspect or any possible implementation of the second aspect, or according to the third aspect or any possible implementation of the third aspect, or according to the fourth aspect or any possible implementation of the fourth aspect is performed.

In the configuration method according to the present disclosure, the first network element receives a first profile of a second network element, where the first profile comprises at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service; determines a third network element based on the first profile of the second network element; and transmits information in the first profile to the third network element based on the first profile. In this way, by virtue of the reachable address of the second network element, a suitable third network element can be determined by the first network element and a logical and secured connection between such second network element and the third first network element can be established under the control of the first network element, and by virtue of the authorization profile, a consumer to which the second network element is capable of providing a first basic service (e.g., X as a service, XaaS for short) can be determined by the first network element and thus an appropriate third network element can be selected for the second network element, then the third first network element can be configured with the information in the first profile from the second network element, thus realizing the configuration of the third network element. In a possible implementation where both of the second network element and the third network element are gateways (also referred to as trustworthy gateways or C/M-TW-GW) , trustworthiness of the communication from perspectives of operation of the communication system (such as a 6G System) is improved by introducing anonymous service provisioning provided by the trustworthy gateways in the C/control/management (C/M) plane and data plane of the communication system.

BRIEF DESCRIPTION OF DRAWINGS

Reference will now be made, by way of example, to the accompanying drawings which show example embodiments of the present disclosure, and in which:

FIG. 1 is a simplified schematic illustration of a communication system according to one or more embodiments of the present disclosure.

FIG. 2 is a schematic illustration of an example communication system according to one or more embodiments of the present disclosure.

FIG. 3 is a schematic illustration of a basic component structure of a communication system according to one or more embodiments of the present disclosure.

FIG. 4 illustrates a block diagram of a device in a communication system according to one or more embodiments of the present disclosure.

FIG. 5 illustrates a block diagram of a 6G System conceptual structure according to one or more embodiments of the present disclosure.

FIG. 6 illustrates a structural schematic of a framework according to one or more embodiments of the present disclosure.

FIG. 7 illustrates a schematic flowchart of a configuration method for a C/M-TW-GW according to one or more embodiments of the present disclosure.

FIG. 8 illustrates a schematic flowchart of a configuration method based on a reachable address and an authorization profile according to one or more embodiments of the present disclosure.

FIG. 9A illustrates a schematic flowchart of a connection process between a second network element and a third network element according to one or more embodiments of the present disclosure.

FIG. 9B illustrates a schematic flowchart of an exemplary connection process between a second network element and a third network element according to one or more embodiments of the present disclosure.

FIG. 9C illustrates a schematic flowchart of another exemplary connection process between a second network element and a third network element according to one or more embodiments of the present disclosure.

FIG. 10A illustrates a schematic flowchart of an exemplary configuration procedure of a third network element (i.e., C/M-TW-GW) according to one or more embodiments of the present disclosure.

FIG. 10B illustrates a schematic flowchart of another exemplary configuration procedure of a third network element (i.e., C/M-TW-GW) according to one or more embodiments of the present disclosure.

FIG. 11 illustrates a schematic flowchart of a configuration method for a Data-TW-GW according to one or more embodiments of the present disclosure.

FIG. 12 illustrates a schematic flowchart of a configuration method based on a reachable address and a mission profile according to one or more embodiments of the present disclosure.

FIG. 13A illustrates a schematic flowchart of a connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure.

FIG. 13B illustrates a schematic flowchart of an exemplary connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure.

FIG. 13C illustrates a schematic flowchart of another exemplary connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure.

FIG. 14A illustrates a schematic flowchart of an exemplary configuration procedure of a sixth network element (i.e., Data-TW-GW) according to one or more embodiments of the present disclosure.

FIG. 14B illustrates a schematic flowchart of another exemplary configuration procedure of a sixth network element (i.e., Data-TW-GW) according to one or more embodiments of the present disclosure.

FIG. 15 is a schematic structural diagram of a configuration apparatus according to one or more embodiments of the present disclosure.

FIG. 16 is a schematic structural diagram of another configuration apparatus according to one or more embodiments of the present disclosure.

FIG. 17 is a schematic structural diagram of another configuration apparatus according to one or more embodiments of the present disclosure.

FIG. 18 is a schematic structural diagram of another configuration apparatus according to one or more embodiments of the present disclosure.

DESCRIPTION OF EMBODIMENTS

To describe the technical solutions in embodiments of the present disclosure or in the prior art more clearly, the following briefly introduces the accompanying drawings needed for describing the embodiments or the prior art.

In the following description, reference is made to the accompanying figures, which form part of the present disclosure, and which show, by way of illustration, specific aspects of embodiments of the present disclosure or specific aspects in which embodiments of the present disclosure may be used. It is understood that embodiments of the present disclosure may be used in other aspects and include structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

To assist in understanding the present disclosure, examples of wireless communication systems and devices are described below.

Example communication systems and devices

Referring to FIG. 1, as an illustrative example without limitation, a simplified schematic illustration of a communication system is provided. The communication system 100 comprises a radio access network 120. The radio access network 120 may be a next generation (e.g. sixth generation (6G) or later) radio access network, or a legacy (e.g. 5G, 4G, 3G or 2G) radio access network. One or more communication electronic devices (ED) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generically referred to as 110) may be interconnected to one another or connected to one or more network nodes (170a, 170b, generically referred to as 170) in the radio access network 120. A core network 130 may be a part of the communication system and may be dependent or independent of the radio access technology used in the communication system 100. Also the communication system 100 comprises a public switched telephone network (PSTN) 140, the internet 150, and other networks 160.

FIG. 2 illustrates an example communication system 100. In general, the communication system 100 enables multiple wireless or wired elements to communicate data and other content. The purpose of the communication system 100 may be to provide content, such as voice, data, video, and/or text, via broadcast, multicast, groupcast, unicast, etc. The communication system 100 may operate by sharing resources, such as carrier spectrum bandwidth, between its constituent elements. The communication system 100 may include a terrestrial communication system and/or a non-terrestrial communication system. The communication system 100 may provide a wide range of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc. ) . The communication system 100 may provide a high degree of availability and robustness through a joint operation of a terrestrial communication system and a non-terrestrial communication system. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can result in what may be considered a heterogeneous network comprising multiple layers. Compared to conventional communication networks, the heterogeneous network may achieve better overall performance through efficient multi-link joint operation, more flexible functionality sharing, and faster physical layer link switching between terrestrial networks and non-terrestrial networks.

The terrestrial communication system and the non-terrestrial communication system could be considered sub-systems of the communication system. In the example shown in FIG. 2, the communication system 100 includes electronic devices (ED) 110a, 110b, 110c, 110d (generically referred to as ED 110) , radio access networks (RANs) 120a, 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. The RANs 120a, 120b include respective base stations (BSs) 170a, 170b, which may be generically referred to as terrestrial transmit and receive points (T-TRPs) 170a, 170b. The non-terrestrial communication network 120c includes an access node 172, which may be generically referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.

Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any T-TRP 170a, 170b and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the preceding. In some examples, ED 110a may communicate an uplink and/or downlink transmission over a terrestrial air interface 190a with T-TRP 170a. In some examples, the EDs 110a, 110b, 110c, and 110d may also communicate directly with one another via one or more sidelink air interfaces 190b. In some examples, ED 110d may communicate an uplink and/or downlink transmission over a non-terrestrial air interface 190c with NT-TRP 172.

The air interfaces 190a and 190b may use similar communication technology, such as any suitable radio access technology. For example, the communication system 100 may implement one or more channel access methods, such as code division multiple access (CDMA) , space division multiple access (SDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or single-carrier FDMA (SC-FDMA, also known as discrete Fourier transform spread OFDMA, DFT-s-OFDMA) in the air interfaces 190a and 190b. The air interfaces 190a and 190b may utilize other higher dimension signal spaces, which may involve a combination of orthogonal and/or non-orthogonal dimensions.

The non-terrestrial air interface 190c can enable communication between the ED 110d and one or multiple NT-TRPs 172 via a wireless link or simply a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or multiple NT-TRPs 172 for multicast transmission.

The RANs 120a and 120b are in communication with the core network 130 to provide the EDs 110a 110b, and 110c with various services such as voice, data, and other services. The RANs 120a and 120b and/or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown) , which may or may not be directly served by core network 130, and may or may not employ the same radio access technology as RAN 120a, RAN 120b or both. The core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b or EDs 110a 110b, and 110c or both, and (ii) other networks (such as the PSTN 140, the Internet 150, and the other networks 160) . In addition, some or all of the EDs 110a 110b, and 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of wireless communication (or in addition thereto) , the EDs 110a 110b, and 110c may communicate via wired communication channels to a service provider or switch (not shown) , and to the Internet 150. PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS) . Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols, such as Internet Protocol (IP) , Transmission Control Protocol (TCP) , User Datagram Protocol (UDP) . EDs 110a 110b, and 110c may be multimode devices capable of operation according to multiple radio access technologies, and incorporate multiple transceivers necessary to support such.

Basic component structure

FIG. 3 illustrates another example of an ED 110 and a base station 170a, 170b and/or 170c. The ED 110 is used to connect persons, objects, machines, etc. The ED 110 may be widely used in various scenarios including, for example, cellular communications, device-to-device (D2D) , vehicle to everything (V2X) , peer-to-peer (P2P) , machine-to-machine (M2M) , machine-type communications (MTC) , internet of things (IoT) , virtual reality (VR) , augmented reality (AR) , mixed reality (MR) , metaverse, digital twin, industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to) as a user equipment/device (UE) , a wireless transmit/receive unit (WTRU) , a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA) , a machine type communication (MTC) device, a personal digital assistant (PDA) , a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, wearable devices (such as a watch, a pair of glasses, head mounted equipment, etc. ) , an industrial device, or an apparatus in (e.g. communication module, modem, or chip) or comprising the forgoing devices, among other possibilities. Future generation EDs 110 may be referred to using other terms. The base station 170a and 170b is a T-TRP and will hereafter be referred to as T-TRP 170. Also shown in FIG. 3, a NT-TRP will hereafter be referred to as NT-TRP 172. Each ED 110 connected to T-TRP 170 and/or NT-TRP 172 can be dynamically or semi-statically turned-on (i.e., established, activated, or enabled) , turned-off (i.e., released, deactivated, or disabled) and/or configured in response to one of more of: connection availability and connection necessity.

The ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 204 may alternatively be panels. The transmitter 201 and the receiver 203 may be integrated, e.g. as a transceiver. The transceiver is configured to modulate data or other content for transmission by at least one antenna 204 or network interface controller (NIC) . The transceiver is also configured to demodulate data or other content received by the at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and/or processing signals received wirelessly or by wire. Each antenna 204 includes any suitable structure for transmitting and/or receiving wireless or wired signals.

The ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by the ED 110. For example, the memory 208 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by one or more processing unit (s) (e.g., a processor 210) . Each memory 208 includes any suitable volatile and/or non-volatile storage and retrieval device (s) . Any suitable type of memory may be used, such as random access memory (RAM) , read only memory (ROM) , hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, and the like.

The ED 110 may further include one or more input/output devices (not shown) or interfaces (such as a wired interface to the Internet 150 in FIG. 1) . The input/output devices or interfaces permit interaction with a user or other devices in the network. Each input/output device or interface includes any suitable structure for providing information to or receiving information from a user, and/or for network interface communications. Suitable structures include, for example, a speaker, microphone, keypad, keyboard, display, touch screen, etc.

The ED 110 includes the processor 210 for performing operations including those operations related to preparing a transmission for uplink transmission to the NT-TRP 172 and/or the T-TRP 170; those operations related to processing downlink transmissions received from the NT-TRP 172 and/or the T-TRP 170; and those operations related to processing sidelink transmission to and from another ED 110. Processing operations related to preparing a transmission for uplink transmission may include operations such as encoding, modulating, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating and decoding received symbols. Depending upon the embodiment, a downlink transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission (e.g. by detecting and/or decoding the signaling) . An example of signaling may be a reference signal transmitted by the NT-TRP 172 and/or by the T-TRP 170. In some embodiments, the processor 210 implements the transmit beamforming and/or the receive beamforming based on the indication of beam direction, e.g. beam angle information (BAI) , received from the T-TRP 170. In some embodiments, the processor 210 may perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as operations relating to detecting a synchronization sequence, decoding and obtaining the system information, etc. In some embodiments, the processor 210 may perform channel estimation, e.g. using a reference signal received from the NT-TRP 172 and/or from the T-TRP 170.

Although not illustrated, the processor 210 may form part of the transmitter 201 and/or part of the receiver 203. Although not illustrated, the memory 208 may form part of the processor 210.

The processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory (e.g. in the memory 208) . Alternatively, some or all of the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmed field-programmable gate array (FPGA) , an application-specific integrated circuit (ASIC) , or a hardware accelerator such as a graphics processing unit (GPU) or an artificial intelligence (AI) accelerator.

The T-TRP 170 may be known by other names in some implementations, such as a base station, a base transceiver station (BTS) , a radio base station, a network node, a network device, a device on the network side, a transmit/receive node, a Node B, an evolved NodeB (eNodeB or eNB) , a Home eNodeB, a next Generation NodeB (gNB) , a transmission point (TP) , a site controller, an access point (AP) , a wireless router, a relay station, a terrestrial node, a terrestrial network device, a terrestrial base station, a base band unit (BBU) , a remote radio unit (RRU) , an active antenna unit (AAU) , a remote radio head (RRH) , a central unit (CU) , a distributed unit (DU) , a positioning node, among other possibilities. The T-TRP 170 may be a macro BS, a pico BS, a relay node, a donor node, or the like, or combinations thereof. The T-TRP 170 may refer to the forgoing devices or refer to apparatus (e.g. a communication module, a modem, or a chip) in the forgoing devices.

In some embodiments, the parts of the T-TRP 170 may be distributed. For example, some of the modules of the T-TRP 170 may be located remote from the equipment that houses the antennas 256 for the T-TRP 170, and may be coupled to the equipment that houses the antennas 256 over a communication link (not shown) sometimes known as front haul, such as common public radio interface (CPRI) . Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations, such as determining the location of the ED 110, resource allocation (scheduling) , message generation, and encoding/decoding, and that are not necessarily part of the equipment that houses the antennas 256 of the T-TRP 170. The modules may also be coupled to other T-TRPs. In some embodiments, the T-TRP 170 may actually be a plurality of T-TRPs that are operating together to serve the ED 110, e.g. through the use of coordinated multipoint transmissions.

The T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels. The transmitter 252 and the receiver 254 may be integrated as a transceiver. The T-TRP 170 further includes a processor 260 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to the NT-TRP 172, and processing a transmission received over backhaul from the NT-TRP 172. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. multiple input multiple output (MIMO) precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. The processor 260 may also perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as generating the content of synchronization signal blocks (SSBs) , generating the system information, etc. In some embodiments, the processor 260 also generates an indication of beam direction, e.g. BAI, which may be scheduled for transmission by a scheduler 253. The processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining where to deploy the NT-TRP 172, etc. In some embodiments, the processor 260 may generate signaling, e.g. to configure one or more parameters of the ED 110 and/or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is transmitted by the transmitter 252. Note that “signaling” , as used herein, may alternatively be called control signaling. Signaling may be transmitted in a physical layer control channel, e.g. a physical downlink control channel (PDCCH) , in which case the signaling may be known as dynamic signaling. Signaling transmitted in a downlink physical layer control channel may be known as Downlink Control Information (DCI) . Signaling transmitted in an uplink physical layer control channel may be known as Uplink Control Information (UCI) . Signaling transmitted in a sidelink physical layer control channel may be known as Sidelink Control Information (SCI) . Signaling may be included in a higher-layer (e.g., higher than physical layer) packet transmitted in a physical layer data channel, e.g. in a physical downlink shared channel (PDSCH) , in which case the signaling may be known as higher-layer signaling, static signaling, or semi-static signaling. Higher-layer signaling may also refer to Radio Resource Control (RRC) protocol signaling or Media Access Control –Control Element (MAC-CE) signaling.

The scheduler 253 may be coupled to the processor 260. The scheduler 253 may be included within or operated separately from the T-TRP 170. The scheduler 253 may schedule uplink, downlink, sidelink, and/or backhaul transmissions, including issuing scheduling grants and/or configuring scheduling-free (e.g., “configured grant” ) resources. The T-TRP 170 further includes a memory 258 for storing information and data. The memory 258 stores instructions and data used, generated, or collected by the T-TRP 170. For example, the memory 258 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 260.

Although not illustrated, the processor 260 may form part of the transmitter 252 and/or part of the receiver 254. Also, although not illustrated, the processor 260 may implement the scheduler 253. Although not illustrated, the memory 258 may form part of the processor 260.

The processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 258. Alternatively, some or all of the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.

Although the NT-TRP 172 is illustrated as a drone only as an example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form, such as satellites and high altitude platforms, including international mobile telecommunication base stations and unmanned aerial vehicles, for example. Also, the NT-TRP 172 may be known by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and the receiver 274 may be integrated as a transceiver. The NT-TRP 172 further includes a processor 276 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to T-TRP 170, and processing a transmission received over backhaul from the T-TRP 170. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. MIMO precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, the processor 276 implements the transmit beamforming and/or receive beamforming based on beam direction information (e.g. BAI) received from the T-TRP 170. In some embodiments, the processor 276 may generate signaling, e.g. to configure one or more parameters of the ED 110. In some embodiments, the NT-TRP 172 implements physical layer processing, but does not implement higher layer functions such as functions at the medium access control (MAC) or radio link control (RLC) layer. As this is only an example, more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.

The NT-TRP 172 further includes a memory 278 for storing information and data. Although not illustrated, the processor 276 may form part of the transmitter 272 and/or part of the receiver 274. Although not illustrated, the memory 278 may form part of the processor 276.

The processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 278. Alternatively, some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC. In some embodiments, the NT-TRP 172 may actually be a plurality of NT-TRPs that are operating together to serve the ED 110, e.g. through coordinated multipoint transmissions.

The T-TRP 170, the NT-TRP 172, and/or the ED 110 may include other components, but these have been omitted for the sake of clarity.

Basic module structure

One or more steps of the embodiment methods provided herein may be performed by corresponding units or modules, according to FIG. 4. FIG. 4 illustrates units or modules in a device, such as in the ED 110, in the T-TRP 170, or in the NT-TRP 172. For example, a signal may be transmitted by a transmitting unit or by a transmitting module. A signal may be received by a receiving unit or by a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module. The respective units or modules may be implemented using hardware, one or more components or devices that execute software, or a combination thereof. For instance, one or more of the units or modules may be a circuit such as an integrated circuit. Examples of an integrated circuit includes a programmed FPGA, a GPU, or an ASIC. For instance, one or more of the units or modules may be logical such as a logical function performed by a circuit, by a portion of an integrated circuit, or by software instructions executed by a processor. It will be appreciated that where the modules are implemented using software for execution by a processor for example, the modules may be retrieved by a processor, in whole or part as needed, individually or together for processing, in single or multiple instances, and that the modules themselves may include instructions for further deployment and instantiation.

Additional details regarding the EDs 110, the T-TRP 170, and the NT-TRP 172 are known to those of skill in the art. As such, these details are omitted here.

6G intelligent air interface

An air interface generally includes a number of components and associated parameters that collectively specify how a transmission is to be sent and/or received over a wireless communications link between two or more communicating devices. For example, an air interface may include one or more components defining the waveform (s) , frame structure (s) , multiple access scheme (s) , protocol (s) , coding scheme (s) and/or modulation scheme (s) for conveying information (e.g. data) over a wireless communications link. The wireless communications link may support a link between a radio access network and user equipment (e.g. a “Uu” link) , and/or the wireless communications link may support a link between device and device, such as between two user equipments (e.g. a “sidelink” ) , and/or the wireless communications link may support a link between a non-terrestrial (NT) -communication network and user equipment (UE) . The air interfaces may also use UWB technology to perform sensing of the surrounding environment using UWB signals.

The followings are some examples for the above components:

A waveform component may specify a shape and form of a signal being transmitted. Waveform options may include orthogonal multiple access waveforms and non-orthogonal multiple access waveforms. Non-limiting examples of such waveform options include Orthogonal Frequency Division Multiplexing (OFDM) , Filtered OFDM (f-OFDM) , Time windowing OFDM, Filter Bank Multicarrier (FBMC) , Universal Filtered Multicarrier (UFMC) , Generalized Frequency Division Multiplexing (GFDM) , Wavelet Packet Modulation (WPM) , Faster Than Nyquist (FTN) Waveform, high rate pulse repetition frequency (HRP) UWB waveform, low rate pulse repetition frequency (LRP) UWB waveform and low Peak to Average Power Ratio Waveform (low PAPR WF) .

A frame structure component may specify a configuration of a frame or group of frames. The frame structure component may indicate one or more of a time, frequency, pilot signature, code, or other parameter of the frame or group of frames. More details of frame structure will be discussed below.

A multiple access scheme component may specify multiple access technique options, including technologies defining how communicating devices share a common physical channel, such as: Time Division Multiple Access (TDMA) , Frequency Division Multiple Access (FDMA) , Code Division Multiple Access (CDMA) , Single Carrier Frequency Division Multiple Access (SC-FDMA) , Low Density Signature Multicarrier Code Division Multiple Access (LDS-MC-CDMA) , Non-Orthogonal Multiple Access (NOMA) , Pattern Division Multiple Access (PDMA) , Lattice Partition Multiple Access (LPMA) , Resource Spread Multiple Access (RSMA) , and Sparse Code Multiple Access (SCMA) . Furthermore, multiple access technique options may include: scheduled access vs. non-scheduled access, also known as grant-free access; non-orthogonal multiple access vs. orthogonal multiple access, e.g., via a dedicated channel resource (e.g., no sharing between multiple communicating devices) ; contention-based shared channel resources vs. non-contention-based shared channel resources, and cognitive radio-based access.

A hybrid automatic repeat request (HARQ) protocol component may specify how a transmission and/or a re-transmission is to be made. Non-limiting examples of transmission and/or re-transmission mechanism options include those that specify a scheduled data pipe size, a signaling mechanism for transmission and/or re-transmission, and a re-transmission mechanism.

A coding and modulation component may specify how information being transmitted may be encoded/decoded and modulated/demodulated for transmission/reception purposes. Coding may refer to methods of error detection and forward error correction. Non-limiting examples of coding options include turbo trellis codes, turbo product codes, fountain codes, low-density parity check codes, and polar codes. Modulation may refer, simply, to the constellation (including, for example, the modulation technique and order) , or more specifically to various types of advanced modulation methods such as hierarchical modulation and low PAPR modulation.

In some embodiments, the air interface may be a “one-size-fits-all concept” . For example, the components within the air interface cannot be changed or adapted once the air interface is defined. In some implementations, only limited parameters or modes of an air interface, such as a cyclic prefix (CP) length or a multiple input multiple output (MIMO) mode, can be configured. In some embodiments, an air interface design may provide a unified or flexible framework to support below 6GHz and beyond 6GHz frequency (e.g., mmWave) bands for both licensed and unlicensed access. As an example, flexibility of a configurable air interface provided by a scalable numerology and symbol duration may allow for transmission parameter optimization for different spectrum bands and for different services/devices. As another example, a unified air interface may be self-contained in a frequency domain, and a frequency domain self-contained design may support more flexible radio access network (RAN) slicing through channel resource sharing between different services in both frequency and time.

The solution described in the present disclosure may be applicable to a next generation (e.g. sixth generation (6G) or later) network, or a legacy (e.g. 5G or 4G) network.

The proposed 6G System architecture is defined to support 6G X as a services (XaaS services) by using techniques such as Network Function Virtualization and Network Slicing. The 6G System architecture utilizes service-based interactions between 6G services.

The 6G System leverages service-based architecture and XaaS concept. XaaS services in the 6G System are categorized into three layers. The 6G System conceptual structure is shown in FIG. 5.

Infrastructure Layer includes infrastructures supporting 6G services. Among them are wireless networks (RAN, CN) infrastructures, Cloud/data center infrastructures, satellite networks, storage/database infrastructures, and sensing networks, and etc. These infrastructures can be provided by a single provider or by multiple providers.

Each of the infrastructures could have its control and management functions, denoted as C/M functions, for infrastructure management. Each of these infrastructures is one type of Infrastructure as a Service.

Control and Management (C/M) layer includes control and management services of the 6G System. They are developed and deployed by using slicing techniques and utilizing resource provided by infrastructure layer. 6G services in Control and Management (C/M) layer are:

-Resource Management (RM) as a Service provides a capability of life-cycle management of a variety of slices and over-the-air resource assignment to wireless devices.

-Mission Management (MM) as a Service provides a capability to program provisioning of XaaS services at Service Layer to provide mission services.

-Confederation Network (CONET) as a Service provides a capability to enable multiple partners jointly provide 6G services. This capability is provided by confederation formation, mutual authentication, mutual authorization among partners and negotiation of agreement on recording and retracing of selected actions performed by partners, in order to assure a trustworthy environment of 6G System operations.

-Service Provisioning Management (SPM) as a Service provides a capability of control and management of 6G service access by customers and provisioning of requested services. The capability is provided by unified mutual authentication, authorization and policy, key management, QoS assurance and charging between any pair of XaaS service provider and customer. The customers include end-customers not only in physical world, but also digital representatives in digital world.

-Connectivity Management (CM) as a Service leverages 5G connectivity management functions, but with extension to include digital world.

-Protocol as a Service provides a capability to design service customized protocol stacks for identified interfaces. The protocol stacks could be pre-defined for on-demand selection, or could be on-demand designed.

-Network Security as a Service provides a capability for owners of infrastructures to detect potential security risks of their infrastructures.

A 6G mission is defined as a service provided to customers by the 6G System. A mission can be a type of services which is provided by a single 6G XaaS service or a type of services that needs contributions from multiple XaaS services.

XaaS services in C/M Layer support control and management of the 6G System itself and also provide support to verticals if requested. One example is that RM service can serve RAN for over-the-air resource management and can also provide service to a vertical for the vertical’s over-the-air resource allocation to its end-customers. The XaaS in C/M layer can be deployed by using slicing technique.

Service Layer includes 6G services which provide services to customers. In the 6G System conceptual structure:

-AI service may be denoted as NET4AI as a Service. Artificial Intelligence service provides AI capability to support a variety of AI applications.

-Service of data collection, data sanitization, data analysis and data delivery are denoted as DAM as a Service, this service provides a capability of lifecycle management of statistic data, including acquisition, de-privatization, analysis and delivery of data which are information statistic data from any types of sensors, devices, network functions, and etc.

-Service of storage and sharing of data may be denoted as NET4Data as a Service, this service provides a capability to trustworthily storage and share data under the control of owners of data and following recognized authorities’ regulations on control of identified data.

-Service to provide digital world may be denoted as NET4DW as a Service, Digital World service provides a capability to construct, control and manage digital world. Digital world is defined as digital realization of physical world.

-6G block chain service may be denoted as NET4BC as a Service. 6G connectivity service is denoted as NET4Con as a Service. This service provides a capability to support 6G block chain services.

-Enhanced connectivity service, e.g., network for connectivity (NET4CON) as a service. This service provides a capability to support exchange of messages and data among new 6G services.

All XaaS services at this Layer are developed and deployed by using resource provided in infrastructure and utilizing Network Function Virtualization and Slicing techniques. The capability of each of 6G services is provided by its control and management functions and service specific data process functions.

In addition to support 6G XaaS services at Service Layer, 6G System leverages 5G System for provisioning of vertical services. The difference between 6G XaaS services and other verticals are that a vertical is a pure customer which needs other XaaS services to enable its operation, while each of XaaS services provide their capabilities to 6G customers.

Any pair of XaaS services of the 6G System could also be mutual customer and provider of each other. Some of examples are that an infrastructure owner provides its resource to XaaS services in Service Layer and C/M Layer; RM services may need the capabilities provided by NET4AI, DAM and NET4DW for its resource management for vertical slicing; CONET service and NET4Data service may need the capability provided by NET4BC for their operation.

In a XaaS service module, there are one or multiple network functions, these network functions can be classified into two categories: C/M function is used for control and management, data processing function (also can be referred to as data function) is used for processing data, the data processing function is only existed in the XaaS services at the service layer.

The key concepts of 6G System includes:

-Define Basic XaaS Services by decoupling comprehensive types of services into basic XaaS services. A basic XaaS service provides unique capability to enable a specific type of service, such as NET4AI service, NET4DW service, DAM service, NET4Data service, Block chain service, mission management service, etc.

-Allow joint operation of the 6G System by multiple partners.

-Define Data Plane of the 6G System which includes processing functions of data plane of XaaS services. Programing the interconnection of these functions, by mission management service, enables to support a variety of customized customer services. Data plane defined in 6G system is a collection of data processing functions of XaaS service in service layer, used for processing and transmitting 6G system data plane traffic. Types of traffic data in 6G system include: training model in NET4AI services, raw data collected, post-sanitized data in DAM service, data in NET4Data, data within digital world in NET4DW, data blocks in NET4BC.

-Simplify 6G System architecture by categorizing basic control services and management services and combining them as basic XaaS services in Control and Management (C/M) Layer.

-Define C/M Plane of the 6G System which includes C/M functions in XaaS services and may include 5G CP (e.g., AMF) depending on implementation options. C/M Plane of the 6G System is defined as a collection of C/M functions of XaaS services in the 6G System Conceptual Structure and used for C/M plane messages exchange among XaaS services.

-Simplify SBI interfaces by introducing trustworthy GWs in Data Plane and C/M Plane of the 6G System. The C/M-TW-GW (Control/Management plane TrustWorthy GateWay) provides the abilities of control plane connectivity, anonymous communication, and secure communication, to enable these abilities, the C/M-TW-GW provides following functionalities: establishes and maintains secured tunnel with each of XaaS services, performs decryption and encryption operation when transferring C/M plane message; maintains an authorization profile for each of XaaS services; transfers the C/M plane message. The Data-TW-GW (Date plane TrustWorthy GateWay) provides the abilities to connect data plane functions of XaaS services to enable to anonymous and secured data plane interaction among XaaS services, the Data-TW-GW provides following functionalities: establishes and maintains secured tunnel with each of XaaS services, performs decryption and encryption operation when transferring data packets; data format translation; transfer the data packets.

-Define Basic Architecture Structure (BAS) which is a unified basic structure with minimized number of interfaces and is independent of types of infrastructures. A BAS is a collection of XaaS services (including C/M plane functions and data plane functions) , TW-GWs in both C/M plane and data plane, and the interfaces between these functions. An infrastructure network that implements a single 6G System BAS is defined as a BAS domain. Each of RAN, CN, a cloud infrastructure, or a wireless device could be a BAS domain.

-Simplify standardization, development and deployment of the 6G System using the BAS concept, while supporting a variety of infrastructure deployment scenarios.

-Adapt to a variety of deployment scenarios by applying the BAS or a subset of it to infrastructures based on capability, capacity and requirement of the infrastructure networks.

-Leverage SBI interface concept and apply SBI interaction in both 6G C/M plane and 6G data plane. -Improve trustworthiness from perspectives of operation of the 6G System by introducing CONET capability, NET4BC capability and anonymous service provisioning provided by the trustworthy GWs in the C/M plane and data plane of the 6G System.

-Improve trustworthiness from perspective of end customer privacy protection by unified mutual authentication, IDM, data sanitization and etc. provided by SPM service, DAM service and 6G Block Chain service.

-Simplify roaming management of wireless devices, in physical world and digital world, by unified authentication including all participated partners and customers.

-Support multiple development paths from 5G System to 6G System by defining multiple architecture options without incurring much efforts due to the introduction of the BAS concept.

-Support backward compatibility by utilizing benefits of SBA and its add-on feature. 5G users can use the 6G System to access 5G services.

-Support future extension by adding new XaaS services with minimized impact on standardization and deployment, due to the introduced anonymous service provisioning concept implemented in trustworthy GWs in 6G C/M plane and in 6G data plane.

In the existing art, 5G system and O-RAN don’t have the proposed 6G network architecture. 5G system CP SBI uses SCP and NRF, etc., to support 5G CP plane indirect communication but not support strong trustworthiness. 5G system has no Data plane definition and has no Data-TW-GW concept. O-RAN has near-term RIC and long term RIC which are not solving issues that 6G may be facing.

Many new trends will trigger the consideration and design of 6G/future wireless networks:

-New network infrastructure capability, e.g., cloud natured/friendly infrastructures that are broadly deployed.

-New (relative) matured techniques, e.g., AI large scale models, Data de-privacy, Block chain, etc. that have made significant progresses and significantly impact on the entire society and human life.

-New apps and services, e.g., AI services, Data (sensing) service, Digital world service, etc. that are broadly applied in industry/business and used by individual customers.

-More global/open/collaborative operation trend, i.e., a more open and more collaborative operation mode are becoming common practice in many fields.

New expectation and stricter requirements on future networks also drive rethinking and development of new generation of wireless networks. These requirements include

-Privacy and trustworthiness, etc.

-Simplified standardization.

-Rapid deployment.

-Etc.

All of the above drives 6G network architecture research work.

The proposed 6G network architecture (X-centric) are SBA (XaaS service) based and Cloud-native.

Requirements to 6G System network architecture design:

> The proposed 6G network architecture needs to support new 6G services which could be developed/deployed by 3rd parties.

> The proposed 6G network architecture needs to embrace more open ecosystem to open door to technical capable 3rd parties.

> The proposed 6G network architecture needs to enable better trustworthiness management. The proposed 6G network architecture may enable controlled anonymous interactions among multiple players.

A framework (which is also referred to as a service framework) enables above requirements to be met.

The service framework is proposed, which is expected to meet the above new requirements to 6G networks.

In the present disclosure, the topology management, including logical connection establishment among GWs (gateways) and XaaS services and vertical, configuration of these GWs, and etc., are proposed and described.

The solution described in the present disclosure is applicable to future 6G networks and all legacy networks.

FIG. 6 illustrates a structural schematic of a framework, the framework includes three kinds of logical network elements, i.e., a C/M function, at least one C/M-TW-GW (control/management plane trustworthy GW) and at least one Data-TW-GW (Data plane trustworthy GW) in one BAS domain (or referred to as domain for short) or administration domains. It should be noted that although one domain is shown in FIG. 6, the number of domains is not limited in the embodiments of the present disclosure. The C/M function in the BAS domain is configured to control and manage topology of the BAS domain, e.g., logical connections between XaaS services/verticals and GWs (including C/M-TW-GW (s) and Data-TW-GW (s) ) in such a domain, and control 6G devices/D-Users/any types of customers to access 6G system by managing C/M session and data session. XaaS services have their own C/M function entities (for realizing their C/M functions of XaaS service modules) and data function entities (for realizing their data processing functions of XaaS service modules) in the same BAS domain as the C/M function, verticals also have their own C/M function entities and data function entities in the same BAS domain as the C/M function, the C/M-TW-GW under control of the C/M function in the BAS domain is configured to connect the C/M function entities of XaaS services and verticals in a BAS domain, in order to enable anonymous and secured C/M plane interaction among XaaS services following authorization profiles of XaaS services, as well as anonymous and secured C/M plane interaction among verticals. The Data-TW-GW under control of the C/M function in the BAS domain is configured to connect the data function entities of XaaS services and verticals in a BAS domain, to enable anonymous and secured data plane interaction among XaaS services, as well as anonymous and secured data plane interaction among verticals to manage assured service performance.

The aforementioned C/M function entity of the XaaS service performs control and management plane functions that are for purpose of network control and management, and also supports signaling exchanging of the XaaS service on the C/M plane. Different C/M function entities are connected via the C/M-TW-GW for supporting anonymous and secured C/M plane interaction among XaaS services.

The aforementioned data function entity of the XaaS service can be a processer which processes data plane traffic, such as NET4AI entity is for model training, etc., and also supports data exchanging of the XaaS service on the data plane. Different data function entities are connected via the Data-TW-GW for supporting anonymous and secured data plane interaction among XaaS services.

As shown in the exemplary framework of FIG. 6, the C/M function is communicatively connected to the at least one C/M-TW-GW and/or the at least one Data-TW-GW. The C/M function is configured to control operations of the at least one C/M-TW-GW and/or the at least one Data-TW-GW. The C/M-TW-GW can be communicatively connected to a C/M function entity of a XaaS service or a vertical in the BAS domain, and configured to interact with the C/M function entity so as to provide C/M plane functions when needed. Similarly, the Data-TW-GW can be communicatively connected to a data function entity of the XaaS service or a vertical in the BAS domain, and configured to interact with the data function entity so as to provide data plane function when needed.

For the concept of the XaaS service, reference can be made to the related description in FIG. 5, and will not be repeated here. The difference between the XaaS service and the vertical is that the vertical is a pure customer which needs other XaaS services to enable its operation, while the XaaS service provides its capabilities to 6G customers. The vertical is a business or industry customer, which is different from an individual wireless device. It could have its dedicated network resource, or integrate its self-defined functions with network functions, could have its own customers, etc. For example, the vertical here may be a kind of service running on the basis of a network provided by e.g., an operator, the vertical per se normally does not own such a network, but may also be able to provide a service to users based on the network, so from the perspective of the operator, such service can be regarded as a vertical. For example, some chatting applications do not have their networks, but can also provide services to users, these chatting applications can be regarded as verticals. The vertical may also have its own server (s) , and its own C/M function entity/entities and data function entity/entities, so in order to make it possible for the vertical to provide a service to users, the C/M-TW-GW and the C/M function entity of the vertical needs to be connected and the Data-TW-GW and the data function entity of the vertical needs to be connected. It should be noted that although examples in the following description are shown with respect to C/M and data entities of XaaS service, but they would also be applicable for C/M and data entities of the vertical.

The C/M function, the C/M-TW-GW and Data-TW-GW in the same domain are connected, e.g., via internal interfaces. Different C/M-TW-GWs in the same domain may be connected, different Data-TW-GWs in the same domain may be also be connected, the C/M-TW-GW and the C/M function entity of a XaaS service in the same domain may be connected, and the Data-TW-GW and the Data function entity of a XaaS service in the same domain are connected.

In an impossible implementation of the present disclosure, the framework may be across multiple BAS domains, and may include multiple C/M functions, multiple C/M-TW-GWs and multiple Data-TW-GWs in the multiple BAS domains, and the C/M functions in different BAS domains may be connected, and each of the C/M functions is configured to control and manage the C/M-TW-GW (s) and the Data-TW-GW (s) in the domain to which the C/M function belongs. Besides, a C/M-TW-GW in one BAS domain may be communicatively connected to a C/M-TW-GW in another BAS domain, and a Data-TW-GW in one BAS domain may be communicatively connected to a Data-TW-GW in another BAS domain accordingly.

In the following, the logical connection establishment among GWs and function entities of XaaS services and vertical, configuration of these GWs, and etc., in the framework will be described in detail.

An implementation of the present disclosure provides a configuration method for a C/M-TW-GW. Reference may be made to FIG. 7, the configuration method may include the following steps.

S701, a first network element receives a first profile of a second network element.

Specifically, the first profile includes at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service. In a possible implementation, the first network element can be a C/M function as mentioned above, the second network element can be a C/M function entity of the first basic service (which is also referred to as XaaS service) in a BAS domain, the first basic service can be any one XaaS service in FIG. 5 or any other possible XaaS service, and the C/M function is configured to control and manage a logical connection between the C/M function entity and the to-be-configured C/M-TW-GW (the third network element) , and further adapted to configure the to-be-configured C/M-TW-GW. For example, the reachable address of the second network element can be a reachable physical address of the second network element, such as an ID of the second network element, it could also be in other forms, as long as the second network element can be reached by other network elements.

In an implementation of the present disclosure, the authorization profile of the second network element includes an identification of the first basic service and an identification of the second network element; the authorization profile of the second network element further includes at least one of following items: an identification of a second basic service provided by the consumer and an identification of a network element of the second basic service (or referred to as an identification of a provider of the second service, provider ID of the second service) ; or, a permissions condition for determining the consumer. Among them, the second basic service can also be any one XaaS service in FIG. 5 or any other possible XaaS service. By using the above information, the consumer to which the second network element is capable of providing the first basic service can be determined in a much easier way.

In an implementation of the present disclosure, the authorization profile can include a consumer list, the consumer list including one or more consumers to which the second network element is capable of providing the first basic service is directly transmitted to the first network element, and the first network element determines the consumer based on the consumer list. In another possible implementation, the authorization profile can include an authorization condition, the authorization condition for determining which consumer can be provided with the first basic service is transmitted to the first network element, the authorization condition may be related to traffic load of a candidate consumer, when a candidate consumer meets the authorization condition, then the first network element determines it as the consumer, it should be noted that the example is simply for illustration purpose, and the authorization condition is not limited in the embodiments of the present disclosure.

In an implementation of the present disclosure, the first network element can establish the connection between the second network element and the third network element based on the reachable address of the second network element; and configure the third network element based on such connection and the authorization profile of the second network element.

In an implementation of the present disclosure, the first network element receiving the first profile of the second network element includes: the first network element receiving a registration message from the second network element, where the registration message is indicative of the first profile. Specifically, the registration message is transmitted to the first network element by registration of the second network element to the first network element, and the first network element directly receives the registration message transmitted by the second network element, or forwarded by a further network element from the second network element, the further network element is connected to the second network element.

In an implementation of the present disclosure, the first network element receiving the first profile of the second network element includes: the first network element receiving a registration message from the first basic service, where the registration message is indicative of the first profile. Specifically, the registration message is transmitted to the first network element by registration of the first basic service to which the second network element belongs to the first network element.

In an implementation of the present disclosure, the first network element receiving the first profile of the second network element includes: the first network element receiving the first profile forwarded by the third network element from a fifth network element, where the third network element is connected with the fifth network element; or, the first network element receiving the first profile forwarded by a fourth network element from a fifth network element, where the fourth network element is connected with the fifth network element. For example, the fifth network element is a confederation network (CONET) or the fifth network element is deployed in the CONET, which stores the reachable address of the second network element and the authorization profile of the second network element, the CONET provides a capability to enable multiple partners jointly provide 6G services. This capability is provided by confederation formation, mutual authentication, mutual authorization among partners and negotiation of agreement on recording and retracing of selected actions performed by partners, in order to assure a trustworthy environment of 6G System operations. In the above latter implementation, the fourth network element may be another C/M-TW-GW in the same BAS domain as the third network element, the fourth network element first receives the first profile from the fifth network element, and then transmits the received first profile to the first network element. It should be noted that if the fourth network element needs to be configured, its configuration procedure is the same as that of the third network element described in the embodiments of the present disclosure.

In the case where the first profile is from the fifth network element or the first basic service, the first profile may be a XaaS service deployment profile (which is also referred to as a deployment profile of the first basic service) and/or a XaaS service authorization profile.

The XaaS service deployment profile may include information, such as, an ID of the XaaS service (which refers to an ID of the first basic service and is also referred to as XaaS service ID) , an ID of a provider providing the XaaS service (which refers to an ID of a provider which provides the first basic service and has its entity (entities) in the BAS domain, and this ID is also referred to as provider ID, said provider has a C/M function entity in the BAS domain which is the above-mentioned second network element) , an ID of a C/M function entity of the XaaS service (which refers to an ID of the second network element of the first basic service, and is also referred to as C/M function entity ID) in the same BAS domain as the first network element, a reachable (physical) address of the C/M function entity, an ID of a data function entity of the XaaS service (which refers to an ID of a seventh network element of the first basic service mentioned below, and is also referred to as data function entity ID) in the same BAS domain as the first network element, a reachable physical address of the data function entity. Therefore, the XaaS service deployment profile includes the reachable address of the second network element, and upon receiving the XaaS service deployment profile, the first network element can get the reachable address of the second network element for configuring the second network element.

The XaaS service authorization profile may include information, such as, an ID of the XaaS service (which refers to an ID of the first basic service and is also referred to as XaaS service ID) , an ID of a provider providing the XaaS service (which refers to an ID of a provider which provides the first basic service and has its entity (entities) in the BAS domain, and this ID is also referred to as provider ID, said provider has a C/M function entity in the BAS domain which is the above-mentioned second network element) , ID (s) of C/M function entity/entities of consumer XaaS service (s) (also referred to as authorized consumer ID (s) ) to which the second network element is authorized to provide XaaS service in the same BAS domain as the first network element, and ID (s) of the authorized consumer XaaS services. The ID (s) of C/M function entity/entities of consumer XaaS service (s) to which the second network element is authorized to provide XaaS service can be taken as the authorization profile of the second network element, and upon receiving the XaaS service authorization profile, the first network element can get the authorization profile of the second network element for configuring the second network element.

S702, the first network element determines a third network element based on the first profile of the second network element.

The first network element may control and manage multiple third network elements, upon receiving the first profile of the second network element, the first network element may determine a third network element for the second network element. For example, the first network element may consider specific information contained in the first profile and then select/choose a suitable third network element for the second network element.

In an implementation of the present disclosure, when the first profile includes the reachable address of the second network element, the first network element can randomly select one third network element (e.g., one C/M-TW-GW) in the BAS domain, or select a C/M-TW-GW based on attributes of the C/M-TW-GWs, such as the traffic load, as the third network element. For example, the C/M function selects a C/M-TW-GW with the smallest traffic load as the third network element, it should be understood that the selection condition is simply for illustration purpose, and not limited in the embodiment of the present disclosure. In this case, the information in the first profile to be sent to the determined third network element, which can also be referred to as first information, is the reachable address of the second network element.

In an implementation of the present disclosure, when the first profile includes the authorization profile of the second network element, the first network element can determine a consumer to which the second network element is capable of providing the first basic service, then based on the authorization profile and a connection between a C/M function entity of the consumer in the BAS domain (which is the BAS domain in which the second network element is located) and the C/M-TW-GW (s) , select a C/M-TW-GW as the third network element. For example, in addition to the first network element (i.e., the C/M function) and second network elements (i.e., the C/M function entity of the first basic service in a BAS domain) , there are C/M-TW-GW1, C/M-TW-GW2, C/M-TW-GW3 and C/M-TW-GW4, C/M function entity A of consumer 1, C/M function entity B of consumer 2 in one BAS domain, the authorization profile indicates that the second network element can provide the first basic service to C/M function entity A of consumer 1 and C/M function entity B of consumer 2, C/M function entity A of consumer 1 is connected to C/M-TW-GW1 but not to C/M-TW-GW2, and C/M function entity B of consumer 2 is connected to C/M-TW-GW2 but not to C/M-TW-GW1, while neither of C/M-TW-GW3 and C/M-TW-GW4 is connected to the C/M function entity A of consumer 1 and the C/M function entity B of consumer 2. Then the C/M-TW-GW1 is selected as a third network element to be configured for supporting anonymous and secured interaction between the C/M function entity A of consumer 1 and the fourth network element based on the authorization profile and the connection between C/M function entity A of consumer 1 and the C/M-TW-GW1, and the C/M-TW-GW2 is selected as a third network element to be configured for supporting anonymous and secured interaction between the C/M function entity B of consumer 2 and the fourth network element based on the authorization profile and the connection between C/M function entity B of consumer 2 and the C/M-TW-GW2. In this case, the information in the first profile (which can also be referred to as first information for C/M-TW-GW1) sent to the C/M-TW-GW1 is authorization information related to the C/M function entity A of consumer 1 in the authorization profile of the second network element, and the information in the first profile (which can also be referred to as first information for C/M-TW-GW2) sent to the C/M-TW-GW2 is authorization information related to the C/M function entity B of consumer 2 in the authorization profile of the second network element.

S703, the first network element transmits information in the first profile to the third network element based on the first profile, and the third network element receives the information in the first profile from the first network element.

The information in the first profile aforementioned can be used for operations of the third network element, the operations of the third network element can be for example, operations involved with the third network element during the establishment of the connection between the third network element and the second network element, and the configuration of the third network element. The information in the first profile can be part or all of the information in the first profile.

This step may be regarded as the configuration step for the third network element, and specifically includes the transmission of the information in the first profile.

In an implementation of the present disclosure, the first profile includes the reachable address of the second network element, the first network element receives the reachable address of the second network element, the first network element determines the third network element based on the reachable address of the second network element as described above and transmits the reachable address of the second network element to the third network element, and the third network element receives the reachable address of the second network element from the first network element. In this case, the information in the first profile (which can also be referred to as first information) is the reachable address of the second network element.

In an implementation of the present disclosure, the first profile includes the authorization profile of the second network element, the first network element receives the authorization profile of the second network element, the first network element determines the third network element based on the authorization profile of the second network element as described above and transmits the authorization profile of the second network element to the third network element, and the third network element receives the authorization profile of the second network element from the first network element. For example, as mentioned in the above example, if the C/M-TW-GW (third network element) is selected based on the connection between the C/M-TW-GW and the C/M function entity/entities of consumer (s) , the information in the first profile (which can also be referred to as first information) sent to the C/M-TW-GW would be authorization information in the authorization profile related to the C/M function entity/entities of consumer (s) connected to the C/M-TW-GW.

When the first profile merely includes the reachable address of the second network element, the steps S701 to S703 are procedures of establishing the connection between the second network element and the third network element, and in this case, the fourth network element can be a C/M function entity of a consumer XaaS service or a C/M function entity of a producer XaaS service. When the first profile merely includes the authorization profile of the second network element, the steps S701 to S703 are configuration procedures of the third network element for supporting service provision of the second network element. When the first profile includes both the reachable address and the authorization profile of the second network element, the steps S701 to S703 are connection and configuration procedures of the third network element.

In an implementation of the present disclosure, the first profile includes the reachable address of the second network element and the authorization profile of the second network element. The specific configuration of the third network element is as follows. FIG. 8 illustrates a schematic flowchart of a configuration of the third network element based on the reachable address and the authorization profile, the configuration includes the following steps.

S801, the first network element configures a connection between the second network element and the third network element based on the reachable address of the second network element.

S802, the first network element determines the information in the first profile based on the authorization profile and the connection between the second network element and the third network element.

S803, the first network element transmits the information in the first profile to the third network element.

For example, as mentioned in the above example, if the C/M-TW-GW (third network element) is selected based on the connection between the C/M-TW-GW and the C/M function entity/entities of consumer (s) , the information in the first profile (which can also be referred to as first information) sent to the C/M-TW-GW would be authorization information in the authorization profile related to the C/M function entity/entities of consumer (s) connected to the C/M-TW-GW.

In this way, instead of transmitting all information to the third network element, the first network element simply transmits the information related to operations of the third network element in the first profile to the third network element, thus reducing the system overhead. The operations of the third network element can be for example, the operations involved with the third network element during the establishment of the connection between the third network element and the second network element and the configuration of the third network element.

In an implementation of the present disclosure, configuration of the connection in Step S801 is shown in FIG. 9A, and specifically includes the following step.

A) , the first network element notifies the third network element of the reachable address of the second network element, or, the first network element notifies the second network element of a reachable address of the third network element based on the reachable address of the second network element. The first network element may have multiple choices when configuring the connection, each of the two parties for setting up a connection may be notified of its opposite parties’ reachable address.

B) , the third network element establishes a connection between the second network element and the third network element based on the reachable address of the second network element. If the second network element is notified of the reachable address of the third network element, such establishment may be initiated by the second network element, if the third network element is notified of the reachable address of the second network element, such establishment may be initiated by the third network element.

C) , the third network element transmits a first notification to the first network element, and the first network element receives the first notification from the third network element. The first notification is indicative of the connection between the second network element and the third network element. In a possible implementation, the first notification may include the type of the connection, the identification of the connection, the type of the connection can be determined based on a protocol corresponding to the connection, for example, the type of the connection can be a TLS (Transport Layer security) connection, which is not limited in the embodiment of the present disclosure. The first notification may further include the identification of the third network element so as to enable the first network element to recognize the third network element, alternatively, the first notification may also skip including the identification of the third network element, in this case, the first network element may recognize the third network element from the first notification per se, e.g., from an interface through which the first notification is received. Upon receiving the first notification, the first network element can record the connection between the second network element and the third network element.

After the connection between the second network element and the third network element is established, the third network element transmits the first notification indicating such connection to the first network element, so that the first network element can better manage and control the second and third network elements.

In an implementation of the present disclosure, after receiving the first notification, the first network element transmits a first acknowledgement to the third network element, and the third network element receives the first acknowledgement from the first network element. The first acknowledgement is indicative of a reception of the first notification.

In an implementation of the present disclosure, both of the first notification and the first acknowledgement include an identification of the first basic service. In another possible implementation of the present disclosure, both of the first notification and the first acknowledgement include a transaction number predefined for the first basic service. In this way, the interaction of the information between the first network element and the third network element can be performed safely and reliably.

In an implementation of the present disclosure, the first notification includes an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element. Here the connection description information may include the type of the connection, the identification of the connection, etc., which is not limited in the embodiments of the present disclosure.

An exemplary connection process between the second network element and the third network element is also shown in FIG. 9B, the second network element is a C/M Function entity of a XaaS Service, and the third network element is a C/M-TW-GW in the service of NET4CON. Establishment of a secured connection between a C/M-TW-GW and a C/M Function entity of a XaaS Service in a BAS domain is described with reference to FIG. 9B. The pre-condition for establishing the connection is: C/M-TW-GW (s) in each BAS domain has been deployed; XaaS service C/M function entity which should connect with a C/M-TW-GW has been deployed and configured; both C/M-TW-GW and C/M function entity of a XaaS service have obtained required certificates (for certificate based solution) .

The C/M function is implemented in BAS domain/infrastructure domain. The C/M function needs to maintain a local BAS domain/infrastructure topology table. This table, for each C/M-TW-GW, keeps information on each of established logical secured connection between this C/M-TW-GW and a C/M function entity of a XaaS service. As described above, after the connection between the third network element (C/M-TW-GW) and the second network element (aC/M function entity of a XaaS service) is established, the first network element may be notified of such established connection, and the first network element may store the information locally, for example, in the local BAS domain/infrastructure topology table described above.

The establishment of such connection can be triggered by either the C/M-TW-GW or the C/M function entity of the XaaS service. In the first case, the C/M-TW-GW can be notified by C/M function on the reachable address of the newly deployed C/M function entity, that is, the C/M function notifies the reachable address of the C/M function entity to the C/M-TW-GW based on the reachable address of the C/M function entity. In the latter case, the newly deployed C/M function entity can be configured on reachable address of the C/M-TW-GW, for example, the C/M function notifies the reachable address of the C/M-TW-GW to the C/M function entity.

As shown in FIG. 9B, the connection between the C/M-TW-GW and the C/M Function entity is established via an external interface (shown as 6G-C/M-1) , and the established connection is a TLS (Transport Layer Security, TLS) connection. Here it should be noted that the TLS connection shown in the figure is simply exemplary, and there could be other types of connection in actual applications.

After establishing the connection, the C/M-TW-GW transmits message 2.1 (which is a specific example of the above first notification) to the C/M function to report the establishment of the TLS connection, where message 2.1 includes an ID of the XaaS service to which the C/M function entity belongs and an ID of the C/M function entity, then the C/M function updates a C/M plane topology table in response to the received message 2.1, the C/M plane topology table includes an ID of a C/M-TW-GW, an ID of a C/M function entity connected to the C/M-TW-GW, an ID of an XaaS service to which the C/M function entity belongs, and a type and a parameter of the connection, such as, TLS connection, and the parameter related to the TLS connection. In response to the message 2.1 received from the C/M-TW-GW, the C/M function transmits message 2.3 (which is a specific example of the above first acknowledgement) for indicating a reception of message 2.1 to the C/M-TW-GW.

The steps of the connection procedure shown in FIG. 9B are listed in Table 1 below.

The symbol “*” in the table refers to interfaces and messages within service.

Table 1

It should be noted that message 2.3 may include other information instead of the XaaS service ID for indicating the reception of message 2.1. Besides, the specific content of messages shown in tables throughout the document is only for illustration purpose, rather than limitation.

FIG. 9C illustrates a schematic flowchart of another exemplary connection process between a second network element and a third network element according to one or more embodiments of the present disclosure, which differs from FIG. 9B in that the C/M-TW-GW connected to the C/M function entity and the C/M-TW-GW reporting the establishment of the connection to the C/M function are not the same gateway. As shown in FIG. 9C, C/M-TW-GW2 is connected to the C/M function entity of the XaaS service, and forwards information related to the establishment of the connection to C/M-TW-GW1, then C/M-TW-GW1 reports the establishment of connection to the C/M function, through the first notification. The reporting processing performed by C/M-TW-GW1 is as same as the C/M-TW-GW described with reference to FIG. 9B.

In an implementation of the present disclosure, the configuration method further includes: the first network element receiving a load report from the third network element, and the third network element reporting a load report to the first network element, where the load report is indicative of load traffic handled by the third network element.

In an implementation of the present disclosure, an occasion for reporting the load report by the third network element is configured by the first network element or predefined.

For example, the C/M function can receive a load report from each of C/M-TW-GWs that it controls and manages, and each C/M-TW-GW continuously or periodically reports its load traffic automatically, or in response to an instruction from the C/M function, or based on at a certain occasion, such occasion includes but is not limited to: reporting the load traffic at certain time intervals, reporting the load traffic continuously or periodically when the load traffic is larger or smaller than a preset value. As described above, this occasion can be configured by the first network element or predefined.

In an implementation of the present disclosure, the configuration method further includes: the first network element determining a further third network element based on the first profile of the second network element and the load report; the first network element configuring a connection between the second network element and the further third network element based on the reachable address of the second network element; and the first network element transmitting information in the first profile to the further third network element based on the first profile. Here the information in the first profile is information about operations of the further third network element, and relevant description for the information in the first profile for the third network element is also applicable for said information. The operations of the further third network element can be for example, operations involved with the further third network element during the establishment of the connection between the further third network element and the second network element and the configuration of the further third network element. The information in the first profile for the further third network element can also be referred to as second information, it can also be, e.g., the readable address of the second network element, authorization information in the authorization profile related to the C/M function entity/entities of consumer (s) connected to the further third network element, the specific content of the second information may be similar to that of the abovementioned first information, except that they may be for different third network elements.

In an implementation of the present disclosure, the configuration method further includes: the first network element releasing a connection between the second network element and the third network element.

For example, after receiving the load traffic of the configured C/M-TW-GW (i.e., the third network element) , the C/M function determines whether the load traffic of the configured C/M-TW-GW exceeds a preset threshold, if yes, the C/M function needs to determine a further to-be-configured C/M-TW-GW based on the authorization profile of the C/M function entity. The configuration procedure of the further C/M-TW-GW (including the determination of the further third network element and the transmission of the information in the first profile for the further third network element) is as same as that of the configured C/M-TW-GW, reference may be made to relevant description in the previous part and will not be repeated here. In an implementation, the first network element can maintain both connections, that is, the connection between the second network element and the third network element, and the connection between the second network element and the further third network element. In another implementation, after the C/M function transmits configuration information (the above information in the first profile) corresponding to the further C/M-TW-GW to the further C/M-TW-GW, the C/M function controls previously configured C/M-TW-GW to disconnect from the C/M function entity.

In this way, the C/M function can acquire the load traffic of each C/M-TW-GW that it controls and manages, and reconfigure a new C/M-TW-GW in time when the load traffic of the previously configured C/M-TW-GW does not meet the preset threshold, thereby efficiently managing and controlling the C/M-TW-GW and saving system overhead.

In an implementation of the present disclosure, after the first network element transmits the information in the first profile to the third network element, the configuration method further includes: the third network element transmitting a second acknowledgement to the first network element and the first network element receiving the second acknowledgement from the third network element, where the second acknowledgement is indicative of a reception of the information in the first profile.

An exemplary configuration procedure of a to-be-configured C/M-TW-GW (i.e., the third network element mentioned above) is also shown in FIG. 10A.

The pre-conditions for configuring a to-be-configured-C/M-TW-GW are as follows: C/M-TW-GW (s) in each BAS domain controlled and managed by a C/M function has been deployed; secured connection between the deployed C/M-TW-GWs and between the C/M function and the C/M-TW-GWs have been established, the establishment can be implemented as shown in FIG. 9A and FIG. 9B; CONET has topology profiles of XaaS services deployment (which is also referred to as deployment profiles of XaaS services) in each of BAS domains; CONET has mutual authorization profiles of XaaS services in each of BAS domains. CONET and the to-be-configured C/M-TW-GW are in the same BAS domain in this example. It should be understood that the solution of the present disclosure is also applicable for the case where CONET and the to-be-configured C/M-TW-GW are in different BAS domains.

The purpose of the configuration procedure is to configure the to-be-configured C/M-TW-GW on the deployment profile in a BAS domain (entity level) and the authorization profile. A deployment profile of a XaaS service includes information, such as, XaaS service ID, provider ID, its deployed C/M plane entities IDs and their reachable physical addresses, its deployed data plane entities IDs and their reachable physical addresses and etc. A authorization profile of a XaaS service includes information, such as, XaaS service ID, provider ID, its authorized consumer IDs and IDs of XaaS services provided by these consumers.

C/M function creates an authorization table based on these profiles. The authorization table combines authorization profiles of XaaS service providers that deploy their entities in the BAS domain.

Note that an entity that triggers the configuration procedure could be any XaaS services, e.g., CONET, Mission Management and etc. In the shown procedure, CONET is used as an example.

In this procedure example, the C/M function obtains the deployment profiles and authorization profiles of XaaS services from CONET. In other cases, the deployment profiles and the authorization profiles can be transmitted to C/M function by XaaS services directly, i.e., by registration of XaaS services to C/M function. Or the deployment profiles and the authorization profiles can be obtained by registration of each deployed C/M function entity to C/M function, after the logical connection establishment.

As shown in FIG. 10A, the C/M function controls and manages a C/M-TW-GW and a Data-TW-GW in a BAS domain to which it belongs, there may be one or more C/M-TW-GWs, and CONET also belongs to this BAS domain; where the connection between one of the C/M-TW-GWs and the C/M function is established via an internal interface, and the connection between the C/M-TW-GW and CONET is established via an external interface (shown as 6G-C/M-1) . The C/M-TW-GW connected to CONET can be the to-be-configured C/M-TW-GW or not.

CONET (which is a specific example of the above fifth network element) first transmits message 1 (which is a specific example of the above first profile) to the C/M-TW-GW connected to CONET for triggering this configuration procedure, where message 1 includes the deployment profiles and the authorization profiles of XaaS services. The C/M-TW-GW connected to CONET is only for transparent transmission, and does not have the right to access the received profiles. The C/M-TW-GW forwards the deployment profiles and the authorization profiles of XaaS services included in message 1 through message 2.1 (which is also a specific example of the above first profile) to the C/M function; then the C/M function stores the deployment profiles and the authorization profiles, and combines the authorization profiles to create an authorization table, the combination can be performed in any well-known manner, which is not limited in the embodiments of the present disclosure. Next, the C/M function transmits the deployment profile and the authorization profile, preferably transmits the deployment profile and the authorization profile specific to the to-be-configured C/M-TW-GW based on the stored profiles. The to-be-configured C/M-TW-GW stores the deployment profile and the authorization profile from the C/M function, and transmits message 2.5 (which is a specific example of the above first acknowledgement) to the C/M function in response to message 2.3 (which is a specific example of the above information in the first profile) , message 2.5 can include any information for responding to message 2.3, as long as these two messages are corresponding and the C/M function gets acknowledge of the reception of message 2.3. After receiving message 2.5 from the C/M-TW-GW, the C/M function creates a C/M-TW-GW configuration record including C/M-TW-GW ID, XaaS service entities deployment profiles, XaaS service Authorization table.

The steps of the configuration procedure shown in FIG. 10A are listed in Table 2 below.

Table 2

FIG. 10B illustrates a schematic flowchart of another exemplary configuration procedure of a third network element (i.e., C/M-TW-GW) according to one or more embodiments of the present disclosure, which differs from FIG. 10A in that the C/M-TW-GW connected to CONET and the to-be-configured C/M-TW-GW are not the same gateway. As shown in FIG. 10B, C/M-TW-GW1 is connected to CONET and receives the profiles from CONET, then transparently transmits the received profiles to the C/M function, that is, C/M-TW-GW1 is only used to forward the profiles, but cannot access the profiles. The C/M function receives the profiles from the C/M-TW-GW1, and transmits to a profile specific to the to-be-configured C/M-TW-GW2. The configuration procedure of C/M-TW-GW2 is as same as the C/M-TW-GW described with reference to FIG. 10A.

An implementation of the present disclosure provides a configuration method for a Data-TW-GW. Reference may be made to FIG. 11, the configuration method may include the following steps.

S1101, a first network element receives a second profile.

Specifically, the second profile includes at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, where the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element. In a possible implementation, the first network element can be a C/M function as mentioned above, the sixth network element can be a to-be-configured Data-TW-GW, the seventh network element can be a data function entity of a XaaS service in a BAS domain and may be a network element for performing an action next to the sixth network element when completing a mission (e.g., triggered by a MM service) , and the C/M function is configured to control and manage a logical connection between the Data function entity and the to-be-configured Data-TW-GW, and further adapted to configure the to-be-configured Data-TW-GW. Here, the reachable address of the seventh network element can be, e.g., a reachable physical address of the seventh network element, such as an ID of the seventh network element, it could also be in other forms, as long as the seventh network element can be reached by other network elements. The mission profile may be from an MM service, and the sixth network element is a network element for completing the mission issued by the MM service, such completion may require multiple sixth network elements, in that case, the second profile (as will be explained later, one specific example is a mission session configuration profile) may include mission profiles of all required sixth network elements for completing a mission, each of the sixth network elements may be configured in the same way, in this case, the mission profile of each sixth network element is used for indicating an execution of an action in a mission by the each sixth network element. The mission is to achieve a designated goal, known as a mission goal, which includes providing PDU (packet data unit) connectivity and providing data processing. The mission can includes one or more actions, the actions can be, for example, AI training, AI inference, data pre-processing, data de-privatization, data cleaning, data collection, data analytics, sensing, etc.

In an implementation of the present disclosure, when the second profile includes the reachable address of the seventh network element, where the first network element receiving the reachable address of the seventh network element of the seventh network element includes: the first network element receiving a registration message from the seventh network element, where the registration message is indicative of the reachable address of the seventh network element. Specifically, the registration message is transmitted to the first network element by registration of the seventh network element to the first network element, and the first network element directly receives the registration message transmitted by the seventh network element, or forwarded by a further network element from the seventh network element, the other network element is connected to the seventh network element.

In an implementation of the present disclosure, the second profile includes the reachable address of the seventh network element, where the first network element receiving the reachable address of the seventh network element of the seventh network element includes: the first network element receiving a registration message from a first basic service to which the seventh network element belongs, where the registration message is indicative of the reachable address of the seventh network element. Specifically, the registration message is transmitted to the first network element by registration of the first basic service to which the seventh network element belongs to the first network element.

In an implementation of the present disclosure, the second profile includes the reachable address of the seventh network element, where the first network element receiving the reachable address of the seventh network element includes: the first network element receiving the reachable address of the seventh network element forwarded by the seventh network element from a fifth network element, where the seventh network element is connected with the fifth network element. For example, the fifth network element is CONET, which stores the reachable address of the sixth network element and the authorization profile of the sixth network element.

Besides, the reachable address of the seventh network element can also be obtained from the XaaS service deployment profile, reference may be made to relevant description in the above part for describing the obtaining of the first profile, which will not be repeated here.

S1102, the first network element determines the sixth network element based on the second profile.

The first network element may control and manage multiple sixth network elements, upon receiving the second profile, the first network element may determine a sixth network element based on the second profile. For example, the first network element may consider specific information contained in the second profile and then select/choose a suitable sixth network element.

In an implementation of the present disclosure, when the second profile includes the reachable address of the seventh network element, the first network element can randomly select one sixth network element (e.g., one Data-TW-GW) in the BAS domain, or select a Data-TW-GW based on attributes of the Data-TW-GWs, such as the traffic load, as the sixth network element. For example, the C/M function selects a Data-TW-GW with the smallest traffic load as the sixth network element, it should be understood that the selection condition is simply for illustration purpose, and not limited in the embodiment of the present disclosure.

In an implementation of the present disclosure, when the second profile includes the mission profile of the sixth network element, the first network element can select a Data-TW-GW based on the mission profile and a connection between a data function entity of a XaaS service (the seventh network element) in the same BAS domain as the sixth network element and the Data-TW-GWs, as the sixth network element. For example, in addition to the first and seventh network elements (i.e., the C/M function and the data function entity of a XaaS service in a BAS domain) , there are multiple sixth network elements (gateways, i.e., Data-TW-GW1, Data-TW-GW2) , the mission profile indicates an execution of action in a mission by a gateway, for example, through an action to be executed by a gateway, an identification of a next network element (the seventh network element) for performing another action after the sixth network element, and an identification for indicating the second action, then since the seventh network element is connected to Data-TW-GW1 but not to Data-TW-GW2, so the first network element may choose the Data-TW-GW1 as the sixth network element based on the mission profile and the connection between a data function entity of a XaaS service and the Data-TW-GW1.

In an implementation of the present disclosure, the first network element can establish the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; and configure the sixth network element based on such connection and the mission profile of the sixth network element.

S1103, the first network element transmits information in the second profile to the sixth network element based on the second profile, and the sixth network element receives information in the second profile from the first network element.

The information in the second profile aforementioned can be used for operations of the sixth network element, the operations of the sixth network element can be for example, operations involved with the sixth network element during the establishment of the connection between the sixth network element and the seventh network element, and the configuration of the sixth network element. The information in the second profile can be part or all of the information in the second profile.

This step may be regarded as the configuration step for the sixth network element, and specifically includes the transmission of the information in the second profile.

In an implementation of the present disclosure, the second profile includes the reachable address of the seventh network element, the first network element receives the reachable address of the seventh network element, the first network element determines the sixth network element based on the reachable address of the seventh network element as described above and transmits the reachable address of the seventh network element to the sixth network element, and the sixth network element receives the reachable address of the seventh network element from the first network element. In this case, the information in the second profile to be transmitted to the determined sixth network element, which can also referred to as third information, is the reachable address of the seventh network element.

In an implementation of the present disclosure, the second profile includes the mission profile of the sixth network element, the first network element receives the mission profile of the sixth network element, the first network element determines the sixth network element based on the mission profile of the sixth network element as described above and transmits the mission profile of the sixth network element to the sixth network element, and the sixth network element receives the mission profile of the sixth network element from the first network element. In this case, the information in the second profile (which can also be referred to as third information) is the mission profile of the sixth network element. As mentioned above, in the case where the second profile includes mission profiles of all required sixth network elements for completing a mission, the information in the second profile (which can also be referred to as third information) transmitted to each sixth network element would be the mission profile of this sixth network element.

When the second profile merely includes the reachable address of the seventh network element, the steps S1101 to S1103 are procedures of establishing the connection between the sixth network element and the seventh network element, and in this case, the seventh network element can be a data function entity of a consumer XaaS service or a data function entity of a producer XaaS service. When the second profile merely includes the mission profile of the sixth network element, the steps S1101 to S1103 are configuration procedures of the sixth network element. When the second profile includes both the reachable address of the seventh network element and the mission profile of the sixth network element, the steps S1101 to S1103 are connection and configuration procedures of the sixth network element for supporting completion of a mission related to both of the sixth network element and the seventh network element.

In an implementation of the present disclosure, the information in the second profile includes an identification for indicating a first action to be performed by the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating the second action. The next network element can be a seventh network element, that is, a data function entity belonging to the next XaaS service. As described above, in an implementation where the second profile includes both the reachable address of the seventh network element and the mission profile of the sixth network element, the seventh network element may be said next network element.

In an implementation of the present disclosure, the information in the second profile includes an identification for indicating a first action to be performed by the sixth network element, a QoS (Quality of Service) parameter of the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating a connection between the sixth network element and the next network element. As described above, in an implementation where the second profile includes both the reachable address of the seventh network element and the mission profile of the sixth network element, the seventh network element may be said next network element. For example, the first action may be decryption or encryption operation when transferring a data packet from a data function entity of a XaaS service to a data function entity of another XaaS service (the seventh network element) , and the second action may be an action for providing a corresponding service by the seventh network element, e.g., data collection in the case of NET4DAM service. For another example, the first action may be an operation of transforming a data format of a data packet when transferring the data packet from a data function entity of a XaaS service to a data function entity of another XaaS service (the seventh network element) .

In an implementation of the present disclosure, the information in the second profile includes an identification for indicating a QoS parameter of the sixth network element.

In an implementation of the present disclosure, the second profile includes the reachable address of the seventh network element and the mission profile of the sixth network element. In this case, the seventh network element may be said next network element may be the next network element for performing an action after the sixth network element, so as to complete a mission. The specific configuration of the sixth network element is as follows.

FIG. 12 illustrates a schematic flowchart of a configuration of the sixth network element based on the reachable address and the mission profile, the configuration includes the following steps.

S1201, the first network element configures a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element.

S1202, the first network element determines the information in the second profile based on the second profile and the connection between the sixth network element and the seventh network element.

S1203, the first network element transmits the information in the second profile to the sixth network element.

The information in the second profile is the mission profile of the determined sixth network element. As mentioned above, in the case where the second profile includes mission profiles of all required sixth network elements for completing a mission, the information in the second profile (which can also be referred to as third information) transmitted to each sixth network element would be the mission profile of this sixth network element.

In an implementation of the present disclosure, configuration of the connection in Step S1201 is shown in FIG. 13A, and specifically includes the following step.

A) , the first network element notifies the sixth network element of the reachable address of the seventh network element, or the first network element notifies the seventh network element of a reachable address of the sixth network element based on the reachable address of the seventh network element. The first network element may have multiple choices when configuring the connection, each of the two parties for setting up a connection may be notified of its opposite parties’ reachable address.

B) , the sixth network element establishes a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element. If the sixth network element is notified of the reachable address of the seventh network element, such establishment may be initiated by the sixth network element, if the seventh network element is notified of the reachable address of the sixth network element, such establishment may be initiated by the seventh network element.

C) , the sixth network element transmits a second notification to the first network element, and the first network element receives the second notification from the sixth network element. The second notification is indicative of the connection between the sixth network element and the seventh network element. In a possible implementation, the second notification may include the type of the connection, the identification of the connection. The second notification may further include the identification of the sixth network element so as to enable the first network element to recognize the sixth network element, alternatively, the second notification may also skip including the identification of the sixth network element, in this case, the first network element may recognize the sixth network element from the second notification per se, e.g., from an interface through which the second notification is received. Upon receiving the second notification, the first network element can record the connection between the sixth network element and the seventh network element.

After the connection between the sixth network element and the seventh network element is established, the sixth network element transmits the second notification indicating such connection to the first network element, so that the first network element can better manage and control the sixth and seventh network elements.

In an implementation of the present disclosure, after receiving the second notification, the first network element transmits a third acknowledgement to the sixth network element, and the sixth network element receives the third acknowledgement from the first network element, where the third acknowledgement is indicative of a reception of the second notification.

In an implementation of the present disclosure, both of the second notification and the third acknowledgement includes an identification of a first basic service to which the seventh network element belongs. In another possible implementation of the present disclosure, both of the second notification and the third acknowledgement include a transaction number predefined for the first basic service. In this way, the interaction of the information between the first network element and the sixth network element can be performed safely and reliably.

In an implementation of the present disclosure, the second notification includes an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and of the connection between the sixth network element and the seventh network element. Here the connection description information may include the type of the connection, the identification of the connection, etc., which is not limited in the embodiments of the present disclosure.

An exemplary connection process between the sixth network element and the seventh network element is also shown in FIG. 13B, the sixth network element is a Data-TW-GW of a XaaS Service, and the seventh network element is a data function entity of a XaaS Service. Establishment of a secured connection between a Data-TW-GW and a data function entity of a XaaS Service in a BAS domain is described with reference to FIG. 13B. The pre-condition for establishing the connection is: Data-TW-GW (s) in each BAS domain has been deployed; XaaS service Data function entity which should connect with the Data-TW-GW has been deployed; both Data-TW-GW and data function entity of a XaaS service have obtained required certificates (for certificate based solution) .

The C/M function is implemented in a BAS domain/infrastructure domain. The C/M function needs to maintain a local BAS domain/infrastructure topology table. This table, for each Data-TW-GW, keeps information on each of established logical secured connection between this Data-TW-GW and a data function entity of a XaaS service. As described above, after the connection between the sixth network element (Data-TW-GW) and the seventh network element (adata function entity of a XaaS service) is established, the first network element may be notified of such established connection, and the first network element may store the information locally, for example, in the local BAS domain/infrastructure topology table described above.

The establishment of such connection can be triggered by either the Data-TW-GW or the data function entity of the XaaS service. In the first case, the Data-TW-GW can be notified by C/M function on the reachable address of the newly deployed data function entity, that is, the C/M function notifies the reachable address of the data function entity to the Data-TW-GW based on the reachable address of the data function entity. In the latter case, the newly deployed data function entity can be configured on reachable address of the Data-TW-GW, for example, the C/M function notifies the reachable address of the Data-TW-GW to the data function entity.

As shown in FIG. 13B, the connection between the Data-TW-GW and the data function entity is established via an external interface (shown as 6G-C/M-1) , and the established connection is a TLS (Transport Layer Security, TLS) connection. Here it should be noted that the TLS connection shown in the figure is simply exemplary, and there could be other types of connection in actual applications.

After establishing the connection, the Data-TW-GW transmits message 2.1 (which is a specific example of the above second notification) to the C/M function to report the establishment of the TLS connection, where message 2.1 includes an ID of the XaaS service to which the data function entity belongs and an ID of the data function entity, then the C/M function updates a data plane topology table in response to the received message 2.1, the data plane topology table includes an ID of a Data-TW-GW, an ID of a data function entity connected to the Data-TW-GW, an ID of a XaaS service to which the data function entity belongs, and a type and a parameter of the connection, such as, TLS connection, and the parameter related to the TLS connection. In response to the message 2.1 received from the Data-TW-GW, the C/M function transmits message 2.3 (which is a specific example of the above third acknowledgement) for indicating a reception of message 2.1 to the Data-TW-GW.

The steps of the connection procedure shown in FIG. 13B are listed in Table 3 below.

Table 3

It should be noted that message 2.3 may include other information instead of the XaaS service ID for indicating the reception of message 2.1.

FIG. 13C illustrates a schematic flowchart of another exemplary connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure, which differs from FIG. 13B in that the Data-TW-GW connected to the data function entity and the Data-TW-GW reporting the establishment of the connection to the C/M function are not the same gateway. As shown in FIG. 13C, Data-TW-GW2 is connected to the data function entity of the XaaS service, and forwards information related to the establishment of the connection to Data-TW-GW1, then Data-TW-GW1 reports the establishment of connection to the C/M function, through the second notification. The reporting processing performed by Data-TW-GW1 is as same as the Data-TW-GW described with reference to FIG. 13B.

In an implementation of the present disclosure, the configuration method further includes: the first network element receiving a load report from the sixth network element, and the sixth network element reporting a load report to the first network element, where the load report is indicative of load traffic handled by the sixth network element.

In an implementation of the present disclosure, an occasion for reporting the load report by the sixth network element is configured by the first network element or predefined.

For example, the C/M function can receive a load report from each of Data-TW-GWs that it controls and manages, and each Data-TW-GW continuously or periodically reports its load traffic automatically, or in response to an instruction from the C/M function, or based on at a certain occasion, such occasion includes but is not limited to: reporting the load traffic at certain time intervals, reporting the load traffic continuously or periodically when the load traffic is larger or smaller than a preset value. As described above, this occasion can be configured by the first network element or predefined.

In an implementation of the present disclosure, the configuration method further includes: the first network element determining a further sixth network element based on the second profile and the load report; the first network element configuring a connection between the seventh network element and the further sixth network element based on the reachable address of the seventh network element; and the first network element transmitting information in the second profile to the further sixth network element based on the second profile. Here, the information in the second profile for the further sixth network element can also be referred to as fourth information, it can also be, e.g., the readable address of the seventh network element, a mission profile related to the data function entity/entities of consumer (s) connected to the further sixth network element, the information in the second profile is information about operations of the further sixth network element, and relevant description for the information in the second profile for the sixth network element is also applicable for the said information, that is, the specific content of the fourth information may be similar to that of the abovementioned third information, except that they may be for different sixth network elements.

In an implementation of the present disclosure, the configuration method further includes: the first network element releasing a connection between the sixth network element and the seventh network element.

For example, after receiving the load traffic of the configured Data-TW-GW (i.e., the sixth network element) , the C/M function determines whether the load traffic of the configured Data-TW-GW exceeds a preset threshold, if yes, the C/M function needs to determine a further to-be-configured Data-TW-GW based on the mission profile of the data function entity. The configuration procedure of the further Data-TW-GW (including the determination of the further sixth network element and the transmission of the information in the second profile for the further sixth network element) is as same as that of the configured Data-TW-GW, reference may be made to relevant description in the previous part and will not be repeated here. In an implementation, the first network element can maintain both connections, that is, the connection between the sixth network element and the seventh network element, and the connection between the further sixth network element and the seventh network element. In another implementation, after the C/M function transmits configuration information (the above information in the second profile) corresponding to the further Data-TW-GW to the further Data-TW-GW, then the C/M function controls previously configured Data-TW-GW to disconnect from the data function entity.

In this way, the C/M function may acquire the load traffic of each Data-TW-GW that it controls and manages, and reconfigure a new Data-TW-GW in time when the load traffic of the previously configured Data-TW-GW does not meet the preset threshold, thereby efficiently managing and controlling the Data-TW-GW and saving system overhead.

In an implementation of the present disclosure, after the first network element transmits the information in the second profile to the sixth network element, the configuration method further includes: the sixth network element transmitting a fourth acknowledgement to the first network element and the first network element receiving the fourth acknowledgement from the sixth network element, where the fourth acknowledgement is indicative of a reception of the information in the second profile.

In an implementation of the present disclosure, both of the information in the second profile and the fourth acknowledgement includes an identification for indicating the mission.

An exemplary configuration procedure of a to-be-configured Data-TW-GW (i.e., the sixth network element mentioned above) is also shown in FIG. 14A. The purpose of this configuration procedure is to configure Data-TW-GW, so as to support a mission session, including 5G PDU session.

The pre-condition for configuring a to-be-configured-Data-TW-GW is: Data-TW-GW (s) in a BAS domain has been deployed. This procedure is conducted whenever a mission service is provided.

As shown in FIG. 14A, the C/M function controls and manages a C/M-TW-GW and a Data-TW-GW in a BAS domain to which it belongs, there may be one or more Data-TW-GWs, where the connection between one of the Data-TW-GWs or C/M-TW-GWs and the C/M function is established via an internal interface, the entity that triggers the configuration procedure can be any type of trigger, such as, an entity of Mission Management (MM) , and the connection between the C/M-TW-GW and the trigger entity is established via an external interface (shown as 6G-C/M-1) .

The trigger entity creates a mission session configuration profile (aspecific example of the second profile mentioned above) related to network elements in the BAS domain that the C/M function is located in. The trigger entity first transmits message 1 to the C/M-TW-GW connected to the trigger entity for triggering this configuration procedure, where message 1 includes the mission session configuration profile related to network elements in the BAS domain. The C/M-TW-GW connected to the trigger entity is only for transparent transmission, and does not have the right to access the received profile.

The C/M-TW-GW forwards the mission session configuration profile included in message 1 through message 2.1 to the C/M function; then the C/M function stores the mission session configuration profile, determines Data-TW-GWs that involve the mission operation, and creates mission session table for each of the determined Data-TW-GWs. Next, the C/M function transmits each mission session table (which is a specific example of the above information in the second profile) to a corresponding Data-TW-GW using message 2.3, the Data-TW-GW receives its own mission session table and stores it, then transmits message 2.5 to the C/M function to respond message 2.3 (which is a specific example of the above fourth acknowledgement) , message 2.5 can include any information for responding to message 2.3, as long as these two messages are corresponding and the C/M function gets acknowledge of the reception of message 2.3, such as an ID of the mission session. After receiving message 2.5 from the Data-TW-GW, the C/M function creates a Data-TW-GW configuration record including the ID of the mission session and mission session table for each supporting Data-TW-GW, and transmits message 2.7 including the ID of the mission session to the C/M-TW-GW in response to message 2.1. After receiving message 2.7 from the C/M function, the C/M-TW-GW transmits message 3 including the ID of the mission session to the trigger entity in response to message 1.

The steps of the configuration procedure shown in FIG. 14A are listed in Table 4 below.

Table 4

The mission session configuration profile could include information (for each involved Data-TW-GW) :

Option 1:

● For routing purpose

○ For each pair [Mission session ID, Action ID] : entity ID of next XaaS service, Action ID (ID of action that will be conducted by next XaaDS service) .

●For QoS assurance

○ For each pair [Mission ID, Action ID] : QoS parameters (or QoS ID) .

Option 2:

●For each Connection ID: QoS parameters (or QoS ID) , entity ID of next XaaS service, Connection ID to next XaaS service.

FIG. 14B illustrates a schematic flowchart of another exemplary configuration procedure of a sixth network element (i.e., Data-TW-GW) according to one or more embodiments of the present disclosure, which differs from FIG. 14A in that the C/M-TW-GW connected to the trigger entity and the C/M-TW-GW connected to the C/M function are not the same gateway. As shown in FIG. 14B, C/M-TW-GW2 is connected to the trigger entity and receives the profiles from the trigger entity, then transmits the received profiles via C/M-TW-GW1 to the C/M function The C/M function receives the profiles from the C/M-TW-GW1, and transmits to the message to C/M-TW-GW2 via C/M-TW-GW1. The configuration procedure of Data-TW-GW is as same as the Data-TW-GW described with reference to FIG. 14A.

Next, embodiments of products related to the configuration methods will be described.

FIG. 15 shows a schematic structural diagram of a configuration apparatus according to an embodiment of the present disclosure. As shown in FIG. 15, the configuration apparatus 1500 may include:

a receiving module 1501, configured to receive a first profile of a second network element, where the first profile includes at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service;

a determining module 1502, configured to determine a third network element based on the first profile of the second network element; and

a transmitting module 1503, configured to transmit information in the first profile to the third network element based on the first profile.

In a possible implementation of the fifth aspect, where the receiving module 1501 is configured to:

receive a registration message from the second network element, where the registration message is indicative of the first profile.

In a possible implementation, where the receiving module 1501 is configured to:

receive a registration message from the first basic service, where the registration message is indicative of the first profile.

In a possible implementation, where the receiving module 1501 is configured to:

receive the first profile forwarded by the third network element from a fifth network element, where the third network element is connected with the fifth network element; or,

receive the first profile forwarded by a fourth network element from a fifth network element, where the fourth network element is connected with the fifth network element.

In a possible implementation, where the first profile includes the reachable address of the second network element and the authorization profile of the second network element;

the transmitting module 1503 is configured to:

configure a connection between the second network element and the third network element based on the reachable address of the second network element;

determine the information in the first profile based on the authorization profile and the connection between the second network element and the third network element; and

transmit the information in the first profile to the third network element.

In a possible implementation, where the transmitting module 1503 is configured to:

notify the third network element of the reachable address of the second network element.

notify the second network element of a reachable address of the third network element based on the reachable address of the second network element.

In a possible implementation, where the receiving module 1501 is further configured to:

receive a first notification from the third network element, where the first notification is indicative of the connection between the second network element and the third network element.

In a possible implementation, where the transmitting module 1503 is further configured to:

transmit a first acknowledgement to the third network element, where the first acknowledgement is indicative of a reception of the first notification.

In a possible implementation, where both of the first notification and the first acknowledgement include an identification of the first basic service.

In a possible implementation, where the first notification includes an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.

receive a load report from the third network element, where the load report is indicative of load traffic handled by the third network element.

In a possible implementation, where

the determining module 1502 is further configured to determine a further third network element based on the first profile of the second network element and the load report;

the transmitting module 1503 is further configured to:

configure a connection between the second network element and the further third network element based on the reachable address of the second network element; and

transmit information in the first profile to the further third network element based on the first profile.

In a possible implementation, where the apparatus further includes:

a releasing module, configured to release a connection between the second network element and the third network element.

In a possible implementation, where an occasion for reporting the load report by the third network element is configured by the first network element or predefined.

In a possible implementation, where the receiving module 1501 is further configured to receive a second acknowledgement from the third network element, where the second acknowledgement is indicative of a reception of the information in the first profile.

In a possible implementation, where the authorization profile of the second network element includes an identification of the first basic service and an identification of the second network element;

a permissions condition for determining the consumer.

FIG. 16 shows a schematic structural diagram of a configuration apparatus according to an embodiment of the present disclosure. As shown in FIG. 16, the configuration apparatus 1600 may include:

a receiving module 1601, configured to receive information from a first network element, where the information is included in a first profile of a second network element received by the first network element, and the first profile includes at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service.

In a possible implementation, where the first profile is indicated by a registration message received by the first network element from the second network element or the first basic service.

In a possible implementation, where

the receiving module 1601 is further configured to receive the first profile from a fifth network element, where the third network element is connected with the fifth network element; and

the apparatus further includes a first transmitting module, configured to forward the first profile to the first network element.

where the apparatus further includes an establishing module, configured to:

establish a connection between the second network element and the third network element based on the reachable address of the second network element; and

the apparatus further includes a second transmitting module, configured to transmit a first notification to the first network element, where the first notification is indicative of the connection between the second network element and the third network element.

In a possible implementation, where the receiving module 1601 is further configured to:

receive a first acknowledgement from the first network element, where the first acknowledgement is indicative of a reception of the first notification.

In a possible implementation, the apparatus further includes a reporting module configured to:

report a load report to the first network element, where the load report is indicative of load traffic handled by the third network element.

In a possible implementation, the apparatus further includes a third transmitting module configured to:

transmit a second acknowledgement to the first network element, where the second acknowledgement is indicative of a reception of the information in the first profile.

FIG. 17 shows a schematic structural diagram of a configuration apparatus according to an embodiment of the present disclosure. As shown in FIG. 17, the configuration apparatus 1700 may include:

a receiving module 1701, configured to receive a second profile, where the second profile includes at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, where the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element;

a determining module 1702, configured to determine the sixth network element based on the second profile; and

a transmitting module 1703, configured to transmit information in the second profile to the sixth network element based on the second profile.

In a possible implementation, where the second profile includes the reachable address of the seventh network element;

where the receiving module 1701is configured to:

receive a registration message from the seventh network element, where the registration message is indicative of the reachable address of the seventh network element.

where the receiving module 1701 is configured to:

receive a registration message from a first basic service to which the seventh network element belongs, where the registration message is indicative of the reachable address of the seventh network element.

where the receiving module 1701 is configured to:

receive the reachable address of the seventh network element forwarded by the seventh network element from a fifth network element, where the seventh network element is connected with the fifth network element.

In a possible implementation, where the second profile includes the reachable address of the seventh network element and the mission profile of the sixth network element;

the transmitting module 1703 is configured to:

configure a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element;

determine the information in the second profile based on the second profile and the connection between the sixth network element and the seventh network element; and

transmit the information in the second profile to the sixth network element.

In a possible implementation, where the transmitting module 1703 is configured to:

notify the sixth network element of the reachable address of the seventh network element.

notify the seventh network element of a reachable address of the sixth network element based on the reachable address of the seventh network element.

In a possible implementation, where the receiving module 1701 is further configured to:

receive a second notification from the sixth network element, where the second notification is indicative of the connection between the sixth network element and the seventh network element.

In a possible implementation, where the transmitting module 1703 is further configured to:

transmit a third acknowledgement to the sixth network element, where the third acknowledgement is indicative of a reception of the second notification.

In a possible implementation, where both of the second notification and the third acknowledgement include an identification of a first basic service to which the seventh network element belongs.

In a possible implementation of the seventh aspect, where the second notification includes an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.

receive a fourth acknowledgement from the sixth network element, where the fourth acknowledgement is indicative of a reception of the information in the second profile.

In a possible implementation, where both of the information in the second profile and the fourth acknowledgement include an identification for indicating the mission.

In a possible implementation, where the information in the second profile includes an identification for indicating a first action to be performed by the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating the second action.

In a possible implementation, where the information in the second profile includes an identification for indicating a first action to be performed by the sixth network element, a QoS (Quality of Service) parameter of the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating a connection between the sixth network element and the next network element.

In a possible implementation, where the information in the second profile includes an identification for indicating a QoS parameter of the sixth network element.

receive a load report from the sixth network element, where the load report is indicative of load traffic handled by the sixth network element.

In a possible implementation, where the determining module 1702 is further configured to determine a further sixth network element based on the second profile and the load report;

the transmitting module 1703 is further configured to:

configure a connection between the seventh network element and the further sixth network element based on the reachable address of the seventh network element; and

transmit information in the second profile to the further sixth network element based on the second profile.

In a possible implementation, where the apparatus further includes:

a releasing module, configured to release the connection between the sixth network element and the seventh network element.

FIG. 18 shows a schematic structural diagram of a configuration apparatus according to an embodiment of the present disclosure. As shown in FIG. 18, the configuration apparatus 1800 may include:

a receiving module 1801, configured to receive information from a first network element, where the information is included in a second profile received by the first network element, where the second profile includes at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, where the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element.

the apparatus further includes an establishing module and a first transmitting module:

the establishing module is configured to establish the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; and

the first transmitting module is configured to transmit a second notification to the first network element, where the second notification is indicative of the connection between the sixth network element and the seventh network element.

In a possible implementation, where the receiving module 1801 is further configured to:

receive a third acknowledgement from the first network element, where the third acknowledgement is indicative of a reception of the second notification.

In a possible implementation, where the second notification includes an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.

In a possible implementation, the apparatus further includes a second transmitting module configured to:

transmit a fourth acknowledgement to the first network element, where the fourth acknowledgement is indicative of a reception of the information in the second profile.

report a load report to the first network element, where the load report is indicative of load traffic handled by the sixth network element.

An embodiment of the present disclosure provides a first network element including processing circuitry for executing any of the above configuration methods.

An embodiment of the present disclosure provides a third network element including processing circuitry for executing any of the above configuration methods.

An embodiment of the present disclosure provides a sixth network element including processing circuitry for executing any of the above configuration methods.

An embodiment of the present disclosure provides a computer-readable medium storing computer execution instructions which, when executed by a processor, causes the processor to execute any of the above configuration methods.

An embodiment of the present disclosure provides a computer program product including computer execution instructions which, when executed by a processor, causes the processor to execute any of the above configuration methods.

An embodiment of the present disclosure provides a wireless system, including the above first network element and the above third network element.

An embodiment of the present disclosure provides a wireless system, including the above first network element and the above sixth network element.

An embodiment of the present disclosure provides an apparatus, including one or more processors, the one or more processors are configured to execute instructions stored in memory, when the instructions is executed by the one or more processors, any of the above configuration methods is performed.

Note that when the request or the response mentioned above includes multiple different contents for indicating multiple different pieces of information, the multiple contents can be indicated separately in multiple request/response messages or together in a request/response message.

Note that the network elements mentioned in the present disclosure are all logical network elements, which can be implemented as individual devices, or can be implemented as chips or modules that could be integrated into a certain device.

Although the present disclosure describes methods and processes with steps in a certain order, one or more steps of the methods and processes may be omitted or altered as appropriate. One or more steps may take place in an order other than that in which they are described, as appropriate.

Note that the expression “at least one of A or B” , as used herein, is interchangeable with the expression “A and/or B” . It refers to a list in which you may select A or B or both A and B. Similarly, “at least one of A, B, or C” , as used herein, is interchangeable with “A and/or B and/or C” or “A, B, and/or C” . It refers to a list in which you may select: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B and C. The same principle applies for longer lists having a same format.

Although the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware components, software or any combination of the two. Accordingly, the technical solution of the present disclosure may be embodied in the form of a software product. A suitable software product may be stored in a pre-recorded storage device or other similar non-volatile or non-transitory computer readable medium, including DVDs, CD-ROMs, USB flash disk, a removable hard disk, or other storage media, for example. The software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, a server, or a network device) to execute examples of the methods disclosed herein. The machine-executable instructions may be in the form of code sequences, configuration information, or other data, which, when executed, cause a machine (e.g., a processor or other processing device) to perform steps in a method according to examples of the present disclosure.

The present disclosure may be embodied in other specific forms without departing from the subject matter of the claims. The described example embodiments are to be considered in all respects as being only illustrative and not restrictive. Selected features from one or more of the above-described embodiments may be combined to create alternative embodiments not explicitly described, features suitable for such combinations being understood within the scope of this disclosure.

All values and sub-ranges within disclosed ranges are also disclosed. Also, although the systems, devices and processes disclosed and shown herein may include a specific number of elements/components, the systems, devices and assemblies could be modified to include additional or fewer of such elements/components. For example, although any of the elements/components disclosed may be referenced as being singular, the embodiments disclosed herein could be modified to include a plurality of such elements/components. The subject matter described herein intends to cover and embrace all suitable changes in technology.

Although embodiments have been described above with reference to the accompanying drawings, those of skill in the art will appreciate that variations and modifications may be made without departing from the scope thereof as defined by the appended claims.

Claims

A configuration method, comprising:

receiving, by a first network element, a first profile of a second network element, wherein the first profile comprises at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service;

determining, by the first network element, a third network element based on the first profile of the second network element; and

transmitting, by the first network element, information in the first profile to the third network element based on the first profile.
The method according to claim 1, wherein receiving, by the first network element, the first profile of the second network element comprises:

receiving, by the first network element, a registration message from the second network element, wherein the registration message is indicative of the first profile.
The method according to claim 1, wherein receiving, by the first network element, the first profile of the second network element comprises:

receiving, by the first network element, a registration message from the first basic service, wherein the registration message is indicative of the first profile.
The method according to claim 1, wherein receiving, by the first network element, the first profile of the second network element comprises:

receiving, by the first network element, the first profile forwarded by the third network element from a fifth network element, wherein the third network element is connected with the fifth network element; or,

receiving, by the first network element, the first profile forwarded by a fourth network element from a fifth network element, wherein the fourth network element is connected with the fifth network element.
The method according to any one of claims 1 to 4, wherein the first profile comprises the reachable address of the second network element and the authorization profile of the second network element;

wherein transmitting, by the first network element, the information in the first profile to the third network element based on the first profile comprises:

configuring, by the first network element, a connection between the second network element and the third network element based on the reachable address of the second network element;

determining, by the first network element, the information in the first profile based on the authorization profile and the connection between the second network element and the third network element; and

transmitting, by the first network element, the information in the first profile to the third network element.
The method according to claim 5, wherein configuring, by the first network element, the connection between the second network element and the third network element comprises:

notifying, by the first network element, the third network element of the reachable address of the second network element.
The method according to claim 5, wherein configuring, by the first network element, the connection between the second network element and the third network element comprises:

notifying, by the first network element, the second network element of a reachable address of the third network element based on the reachable address of the second network element.
The method according to any one of claim 5 to 7, further comprising:

receiving, by the first network element, a first notification from the third network element, wherein the first notification is indicative of the connection between the second network element and the third network element.
The method according to claim 8, further comprising:

transmitting, by the first network element, a first acknowledgement to the third network element, wherein the first acknowledgement is indicative of a reception of the first notification.
The method according to claim 9, wherein both of the first notification and the first acknowledgement comprise an identification of the first basic service.
The method according to any one of claims 8 to 10, wherein the first notification comprises an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.
The method according to any one of claims 1 to 11, further comprising:

receiving, by the first network element, a load report from the third network element, wherein the load report is indicative of load traffic handled by the third network element.
The method according to claim 12, further comprising:

determining, by the first network element, a further third network element based on the first profile of the second network element and the load report;

configuring, by the first network element, a connection between the second network element and the further third network element based on the reachable address of the second network element; and

transmitting, by the first network element, information in the first profile to the further third network element based on the first profile.
The method according to claim 12 or 13, further comprising:

releasing, by the first network element, a connection between the second network element and the third network element.
The method according to any one of claims 12 to 14, wherein an occasion for reporting the load report by the third network element is configured by the first network element or predefined.
The method according to any one of claims 1 to 15, further comprising:

receiving, by the first network element, a second acknowledgement from the third network element, wherein the second acknowledgement is indicative of a reception of the information in the first profile.
The method according to any one of claims 1 to 16, wherein the authorization profile of the second network element comprises an identification of the first basic service and an identification of the second network element;

the authorization profile of the second network element further comprises at least one of following items:

an identification of a second basic service provided by the consumer and an identification of a network element of the second basic service; or,

a permissions condition for determining the consumer.
A configuration method, comprising:

receiving, by a third network element, information from a first network element, wherein the information is comprised in a first profile of a second network element received by the first network element, and the first profile comprises at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service.
The method according to claim 18, wherein the first profile is indicated by a registration message received by the first network element from the second network element or the first basic service.
The method according to claim 18, further comprising:

receiving, by the third network element, the first profile from a fifth network element, wherein the third network element is connected with the fifth network element; and

forwarding, by the third network element, the first profile to the first network element.
The method according to any one of claims 18 to 20, wherein the first profile comprises the reachable address of the second network element and the authorization profile of the second network element;

wherein the method further comprises:

establishing, by the third network element, a connection between the second network element and the third network element based on the reachable address of the second network element; and

transmitting, by the third network element, a first notification to the first network element, wherein the first notification is indicative of the connection between the second network element and the third network element.
The method according to claim 21, further comprising:

receiving, by the third network element, a first acknowledgement from the first network element, wherein the first acknowledgement is indicative of a reception of the first notification.
The method according to claim 22, wherein both of the first notification and the first acknowledgement comprise an identification of the first basic service.
The method according to any one of claims 21 to 23, wherein the first notification comprises an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.
The method according to any one of claims 18 to 24, further comprising:

reporting, by the third network element, a load report to the first network element, wherein the load report is indicative of load traffic handled by the third network element.
The method according to any one of claims 18 to 25, further comprising:

transmitting, by the third network element, a second acknowledgement to the first network element, wherein the second acknowledgement is indicative of a reception of the information in the first profile.
A configuration method, comprising:

receiving, by a first network element, a second profile, wherein the second profile comprises at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, wherein the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element;

determining, by the first network element, the sixth network element based on the second profile; and

transmitting, by the first network element, information in the second profile to the sixth network element based on the second profile.
The method according to claim 27, wherein the second profile comprises the reachable address of the seventh network element;

wherein receiving, by the first network element, the reachable address of the seventh network element of the seventh network element comprises:

receiving, by the first network element, a registration message from the seventh network element, wherein the registration message is indicative of the reachable address of the seventh network element.
The method according to claim 27, wherein the second profile comprises the reachable address of the seventh network element;

wherein receiving, by the first network element, the reachable address of the seventh network element of the seventh network element comprises:

receiving, by the first network element, a registration message from a first basic service to which the seventh network element belongs, wherein the registration message is indicative of the reachable address of the seventh network element.
The method according to claim 27, wherein the second profile comprises the reachable address of the seventh network element;

wherein receiving, by the first network element, the reachable address of the seventh network element comprises:

receiving, by the first network element, the reachable address of the seventh network element forwarded by the seventh network element from a fifth network element, wherein the seventh network element is connected with the fifth network element.
The method according to any one of claims 27 to 30, wherein the second profile comprises the reachable address of the seventh network element and the mission profile of the sixth network element;

wherein transmitting, by the first network element, the information in the second profile to the sixth network element based on the second profile comprises:

configuring, by the first network element, a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element;

determining, by the first network element, the information in the second profile based on the second profile and the connection between the sixth network element and the seventh network element; and

transmitting, by the first network element, the information in the second profile to the sixth network element.
The method according to claim 31, wherein configuring, by the first network element, the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element comprises:

notifying, by the first network element, the sixth network element of the reachable address of the seventh network element.
The method according to claim 31, wherein configuring, by the first network element, the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element comprises:

notifying, by the first network element, the seventh network element of a reachable address of the sixth network element based on the reachable address of the seventh network element.
The method according to any one of claims 31 to 33, further comprising:

receiving, by the first network element, a second notification from the sixth network element, wherein the second notification is indicative of the connection between the sixth network element and the seventh network element.
The method according to claim 34, further comprising:

transmitting, by the first network element, a third acknowledgement to the sixth network element, wherein the third acknowledgement is indicative of a reception of the second notification.
The method according to claim 35, wherein both of the second notification and the third acknowledgement comprise an identification of a first basic service to which the seventh network element belongs.
The method according to any one of claims 34 to 36, wherein the second notification comprises an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.
The method according to any one of claims 27 to 37, further comprising:

receiving, by the first network element, a fourth acknowledgement from the sixth network element, wherein the fourth acknowledgement is indicative of a reception of the information in the second profile.
The method according to claim 38, wherein both of the information in the second profile and the fourth acknowledgement comprise an identification for indicating the mission.
The method according to any one of claims 27 to 39, wherein the information in the second profile comprises an identification for indicating a first action to be performed by the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating the second action.
The method according to any one of claims 27 to 39, wherein the information in the second profile comprises an identification for indicating a first action to be performed by the sixth network element, a QoS (Quality of Service) parameter of the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating a connection between the sixth network element and the next network element.
The method according to any one of claims 27 to 39, wherein the information in the second profile comprises an identification for indicating a QoS (Quality of Service) parameter of the sixth network element.
The method according to any one of claims 27 to 42, further comprising:

receiving, by the first network element, a load report from the sixth network element, wherein the load report is indicative of load traffic handled by the sixth network element.
The method according to claim 43, further comprising:

determining, by the first network element, a further sixth network element based on the second profile and the load report;

configuring, by the first network element, a connection between the seventh network element and the further sixth network element based on the reachable address of the seventh network element; and

transmitting, by the first network element, information in the second profile to the further sixth network element based on the second profile.
The method according to claim 43 or 44, further comprising:

releasing, by the first network element, the connection between the sixth network element and the seventh network element.
The method according to any one of claims 43 to 45, wherein an occasion for reporting the load report by the third network element is configured by the first network element or predefined.
A configuration method, comprising:

receiving, by a sixth network element, information from a first network element, wherein the information is comprised in a second profile received by the first network element, wherein the second profile comprises at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, wherein the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element.
The method according to claim 47, wherein the second profile comprises the reachable address of the seventh network element;

wherein the second profile is indicated by a registration message received by the first network element from the seventh network element or a first basic service.
The method according to claim 47, wherein the second profile comprises the reachable address of the seventh network element;

the method further comprises:

establishing, by the sixth network element, the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; and

transmitting, by the sixth network element, a second notification to the first network element, wherein the second notification is indicative of the connection between the sixth network element and the seventh network element.
The method according to claim 49, further comprising:

receiving, by the sixth network element, a third acknowledgement from the first network element, wherein the third acknowledgement is indicative of a reception of the second notification.
The method according to claim 50, wherein both of the second notification and the third acknowledgement comprise an identification of a first basic service to which the seventh network element belongs.
The method according to any one of claims 49 to 51, wherein the second notification comprises an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.
The method according to any one of claims 47 to 52, further comprising:

transmitting, by the sixth network element, a fourth acknowledgement to the first network element, wherein the fourth acknowledgement is indicative of a reception of the information in the second profile.
The method according to claim 53, wherein both of the information in the second profile and the fourth acknowledgement comprise an identification for indicating the mission.
The method according to any one of claims 47 to 54, further comprising:

reporting, by the sixth network element, a load report to the first network element, wherein the load report is indicative of load traffic handled by the sixth network element.
A configuration apparatus, applied to a first network element and comprising:

a receiving module, configured to receive a first profile of a second network element, wherein the first profile comprises at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service;

a determining module, configured to determine a third network element based on the first profile of the second network element; and

a transmitting module, configured to transmit information in the first profile to the third network element based on the first profile.
The apparatus according to claim 56, wherein the receiving module is configured to:

receive a registration message from the second network element, wherein the registration message is indicative of the first profile.
The apparatus according to claim 56, wherein the receiving module is configured to:

receive a registration message from the first basic service, wherein the registration message is indicative of the first profile.
The apparatus according to claim 56, wherein the receiving module is configured to:

receive the first profile forwarded by the third network element from a fifth network element, wherein the third network element is connected with the fifth network element; or,

receive the first profile forwarded by a fourth network element from a fifth network element, wherein the fourth network element is connected with the fifth network element.
The apparatus according to any one of claims 56 to 59, wherein the first profile comprises the reachable address of the second network element and the authorization profile of the second network element;

the transmitting module is configured to:

configure a connection between the second network element and the third network element based on the reachable address of the second network element;

determine the information in the first profile based on the authorization profile and the connection between the second network element and the third network element; and

transmit the information in the first profile to the third network element.
The apparatus according to claim 60, wherein the transmitting module is configured to:

notify the third network element of the reachable address of the second network element.
The apparatus according to claim 60, wherein the transmitting module is configured to:

notify the second network element of a reachable address of the third network element based on the reachable address of the second network element.
The apparatus according to any one of claim 60 to 62, wherein the receiving module is further configured to:

receive a first notification from the third network element, wherein the first notification is indicative of the connection between the second network element and the third network element.
The apparatus according to claim 63, wherein the transmitting module is further configured to:

transmit a first acknowledgement to the third network element, wherein the first acknowledgement is indicative of a reception of the first notification.
The apparatus according to claim 64, wherein both of the first notification and the first acknowledgement comprise an identification of the first basic service.
The apparatus according to any one of claims 63 to 65, wherein the first notification comprises an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.
The apparatus according to any one of claims 56 to 66, wherein the receiving module is further configured to:

receive a load report from the third network element, wherein the load report is indicative of load traffic handled by the third network element.
The apparatus according to claim 67, wherein

the determining module is further configured to determine a further third network element based on the first profile of the second network element and the load report;

the transmitting module is further configured to:

configure a connection between the second network element and the further third network element based on the reachable address of the second network element; and

transmit information in the first profile to the further third network element based on the first profile.
The apparatus according to claim 67 or 68, further comprising:

a releasing module, configured to release a connection between the second network element and the third network element.
The apparatus according to any one of claims 67 to 69, wherein an occasion for reporting the load report by the third network element is configured by the first network element or predefined.
The apparatus according to any one of claims 56 to 70, wherein

the receiving module is further configured to receive a second acknowledgement from the third network element, wherein the second acknowledgement is indicative of a reception of the information in the first profile.
The apparatus according to any one of claims 56 to 71, wherein the authorization profile of the second network element comprises an identification of the first basic service and an identification of the second network element;

the authorization profile of the second network element further comprises at least one of following items:

an identification of a second basic service provided by the consumer and an identification of a network element of the second basic service; or,

a permissions condition for determining the consumer.
A configuration apparatus, applied to a third network element and comprising:

a receiving module, configured to receive information from a first network element, wherein the information is comprised in a first profile of a second network element received by the first network element, and the first profile comprises at least one of a reachable address of the second network element or an authorization profile of the second network element, and the authorization profile is used for determining a consumer to which the second network element is capable of providing a first basic service.
The apparatus according to claim 73, wherein the first profile is indicated by a registration message received by the first network element from the second network element or the first basic service.
The apparatus according to claim 73, wherein

the receiving module is further configured to receive the first profile from a fifth network element, wherein the third network element is connected with the fifth network element; and

the apparatus further comprises a first transmitting module, configured to forward the first profile to the first network element.
The apparatus according to any one of claims 73 to 75, wherein the first profile comprises the reachable address of the second network element and the authorization profile of the second network element;

wherein the apparatus further comprises an establishing module, configured to:

establish a connection between the second network element and the third network element based on the reachable address of the second network element; and

the apparatus further comprises a second transmitting module, configured to transmit a first notification to the first network element, wherein the first notification is indicative of the connection between the second network element and the third network element.
The apparatus according to claim 76, wherein the receiving module is further configured to:

receive a first acknowledgement from the first network element, wherein the first acknowledgement is indicative of a reception of the first notification.
The apparatus according to claim 77, wherein both of the first notification and the first acknowledgement comprise an identification of the first basic service.
The apparatus according to any one of claims 76 to 78, wherein the first notification comprises an identification of the third network element, an identification of the first basic service, an identification of the second network element and connection description information of the connection between the second network element and the third network element.
The apparatus according to any one of claims 73 to 79, wherein the apparatus further comprises a reporting module configured to:

report a load report to the first network element, wherein the load report is indicative of load traffic handled by the third network element.
The apparatus according to any one of claims 73 to 80, wherein the apparatus further comprises a third transmitting module configured to:

transmit a second acknowledgement to the first network element, wherein the second acknowledgement is indicative of a reception of the information in the first profile.
A configuration apparatus, applied to a first network element and comprising:

a receiving module, configured to receive a second profile, wherein the second profile comprises at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, wherein the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element;

a determining module, configured to determine the sixth network element based on the second profile; and

a transmitting module, configured to transmit information in the second profile to the sixth network element based on the second profile.
The apparatus according to claim 82, wherein the second profile comprises the reachable address of the seventh network element;

wherein the receiving module is configured to:

receive a registration message from the seventh network element, wherein the registration message is indicative of the reachable address of the seventh network element.
The apparatus according to claim 82, wherein the second profile comprises the reachable address of the seventh network element;

wherein the receiving module is configured to:

receive a registration message from a first basic service to which the seventh network element belongs, wherein the registration message is indicative of the reachable address of the seventh network element.
The apparatus according to claim 82, wherein the second profile comprises the reachable address of the seventh network element;

wherein the receiving module is configured to:

receive the reachable address of the seventh network element forwarded by the seventh network element from a fifth network element, wherein the seventh network element is connected with the fifth network element.
The apparatus according to any one of claims 82 to 85, wherein the second profile comprises the reachable address of the seventh network element and the mission profile of the sixth network element;

the transmitting module is configured to:

configure a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element;

determine the information in the second profile based on the second profile and the connection between the sixth network element and the seventh network element; and

transmit the information in the second profile to the sixth network element.
The apparatus according to claim 86, wherein the transmitting module is configured to:

notify the sixth network element of the reachable address of the seventh network element.
The apparatus according to claim 86, wherein the transmitting module is configured to:

notify the seventh network element of a reachable address of the sixth network element based on the reachable address of the seventh network element.
The apparatus according to any one of claims 86 to 88, wherein the receiving module is further configured to:

receive a second notification from the sixth network element, wherein the second notification is indicative of the connection between the sixth network element and the seventh network element.
The apparatus according to claim 89, wherein the transmitting module is further configured to:

transmit a third acknowledgement to the sixth network element, wherein the third acknowledgement is indicative of a reception of the second notification.
The apparatus according to claim 90, wherein both of the second notification and the third acknowledgement comprise an identification of a first basic service to which the seventh network element belongs.
The apparatus according to any one of claims 89 to 91, wherein the second notification comprises an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.
The apparatus according to any one of claims 82 to 92, wherein the receiving module is further configured to:

receive a fourth acknowledgement from the sixth network element, wherein the fourth acknowledgement is indicative of a reception of the information in the second profile.
The apparatus according to claim 93, wherein both of the information in the second profile and the fourth acknowledgement comprise an identification for indicating the mission.
The apparatus according to any one of claims 82 to 94, wherein the information in the second profile comprises an identification for indicating a first action to be performed by the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating the second action.
The apparatus according to any one of claims 82 to 94, wherein the information in the second profile comprises an identification for indicating a first action to be performed by the sixth network element, a QoS (Quality of Service) parameter of the sixth network element, an identification for indicating a next network element for performing a second action after the sixth network element, and an identification for indicating a connection between the sixth network element and the next network element.
The apparatus according to any one of claims 82 to 94, wherein the information in the second profile comprises an identification for indicating a QoS (Quality of Service) parameter of the sixth network element.
The apparatus according to any one of claims 82 to 97, wherein the receiving module is further configured to:

receive a load report from the sixth network element, wherein the load report is indicative of load traffic handled by the sixth network element.
The apparatus according to claim 98, wherein

the determining module is further configured to determine a further sixth network element based on the second profile and the load report;

the transmitting module is further configured to:

configure a connection between the seventh network element and the further sixth network element based on the reachable address of the seventh network element; and

transmit information in the second profile to the further sixth network element based on the second profile.
The apparatus according to claim 98 or 99, further comprising:

a releasing module, configured to release the connection between the sixth network element and the seventh network element.
The apparatus according to any one of claims 98 to 100, wherein an occasion for reporting the load report by the third network element is configured by the first network element or predefined.
A configuration apparatus, applied to a sixth network element and comprising:

a receiving module, configured to receive information from a first network element, wherein the information is comprised in a second profile received by the first network element, wherein the second profile comprises at least one of a mission profile of a sixth network element or a reachable address of a seventh network element, wherein the mission profile is used for indicating an execution of an action in a mission by the sixth network element, and the reachable address of the seventh network element is used for establishing a connection between the sixth network element and the seventh network element.
The apparatus according to claim 102, wherein the second profile comprises the reachable address of the seventh network element;

wherein the second profile is indicated by a registration message received by the first network element from the seventh network element or a first basic service.
The apparatus according to claim 102, wherein the second profile comprises the reachable address of the seventh network element;

the apparatus further comprises an establishing module and a first transmitting module:

the establishing module is configured to establish the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; and

the first transmitting module is configured to transmit a second notification to the first network element, wherein the second notification is indicative of the connection between the sixth network element and the seventh network element.
The apparatus according to claim 104, wherein the receiving module is further configured to:

receive a third acknowledgement from the first network element, wherein the third acknowledgement is indicative of a reception of the second notification.
The apparatus according to claim 105, wherein both of the second notification and the third acknowledgement comprise an identification of a first basic service to which the seventh network element belongs.
The apparatus according to any one of claims 104 to 106, wherein the second notification comprises an identification of the sixth network element, an identification of a first basic service to which the seventh network element belongs, an identification of the seventh network element and connection description information of the connection between the sixth network element and the seventh network element.
The apparatus according to any one of claims 102 to 107, wherein the apparatus further comprises a second transmitting module configured to:

transmit a fourth acknowledgement to the first network element, wherein the fourth acknowledgement is indicative of a reception of the information in the second profile.
The apparatus according to claim 108, wherein both of the information in the second profile and the fourth acknowledgement comprise an identification for indicating the mission.
The apparatus according to any one of claims 102 to 109, wherein the apparatus further comprises a reporting module configured to:

report a load report to the first network element, wherein the load report is indicative of load traffic handled by the sixth network element.
An apparatus, comprising one or more processors, the one or more processors are configured to execute instructions stored in memory, when the instructions is executed by the one or more processors, the method according to any one of claims 1 to 55 is performed.
A computer-readable medium storing computer execution instructions which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 55.