Configuration method and related product

Abstract

The present disclosure provides a configuration method and related products, the method comprising: a first network element receiving a first configuration file of a second network element, the first configuration file comprising at least one of a reachable address of the second network element or an authorized configuration file of the second network element, the authorization configuration file is used for determining a consumer that the second network element can provide a first basic service; and the first network element determines a third network element based on the first configuration file of the second network element, and sends information in the first configuration file to the third network element based on the first configuration file.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Application No. 63 / 535,637, filed August 31, 2023. The entire disclosure of the above-mentioned patent application is incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a configuration method and related products. Background Technology

[0003] The 5G system's control plane (CP) service-based interface (SBI) employs service communication proxy (SCP) and network repository function (NRF) to support indirect communication between 5G CPs, but it does not support strong trust. The control plane is typically used to manage network device status information, routing tables, and access control lists, and to communicate with other devices to perform functions such as routing. The data plane is typically used to process and transmit network traffic, i.e., forwarding received data packets according to preset rules and ensuring that data packets correctly reach their destination devices.

[0004] The purpose of the background information is to disclose information that the applicant believes may be relevant to this disclosure. It is neither necessary nor appropriate to acknowledge that any of the aforementioned information constitutes prior art relative to this disclosure. Summary of the Invention

[0005] In a first aspect, one embodiment of this disclosure provides a configuration method. The method includes:

[0006] The first network element receives a first configuration file from the second network element, wherein the first configuration file includes at least one of the reachable address of the second network element or the authorization configuration file of the second network element, and the authorization configuration file is used to determine the consumer that the second network element can provide the first basic service;

[0007] The first network element determines the third network element based on the first configuration file of the second network element; and

[0008] The first network element sends the information in the first configuration file to the third network element based on the first configuration file.

[0009] In this way, by using the reachable address of the second network element, the first network element can determine a suitable third network element; a secure logical connection can be established between this second network element and the third first network element under the control of the first network element; using the authorization configuration file, the first network element can determine the consumer of the first basic service (such as XaaS) that the second network element can provide, and therefore can select a suitable third network element for the second network element; then, the third first network element can be configured using the information from the first configuration file of the second network element, thus realizing the configuration of the third network element. In a possible implementation where both the second and third network elements are gateways (also known as trusted gateways or C / M-TW-GW), by introducing the anonymous service provided by the trusted gateway on the control / management (C / M) plane of the communication system (such as a 6G system), the trustworthiness of communication is improved from the perspective of the operation of the communication system.

[0010] In one possible implementation of the first aspect, the first network element receiving the first configuration file of the second network element includes: the first network element receiving a registration message from the second network element, wherein the registration message indicates the first configuration file.

[0011] In one possible implementation of the first aspect, the first network element receiving the first configuration file of the second network element includes: the first network element receiving a registration message from the first basic service, wherein the registration message indicates the first configuration file.

[0012] In one possible implementation of the first aspect, the first network element receiving the first configuration file of the second network element includes:

[0013] The first network element receives the first configuration file forwarded by the third network element from the fifth network element, wherein the third network element is connected to the fifth network element; or

[0014] The first network element receives the first configuration file forwarded by the fourth network element from the fifth network element, wherein the fourth network element is connected to the fifth network element.

[0015] Based on the above, the first network element can receive the first configuration file of the second network element in multiple ways, so the receiving method of the first configuration file can be flexibly set according to actual needs.

[0016] In one possible implementation of the first aspect, the first configuration file includes the reachable address of the second network element and the authorization configuration file of the second network element;

[0017] The first network element sends the information in the first configuration file to the third network element based on the first configuration file, including:

[0018] The first network element configures the connection between the second network element and the third network element based on the reachable address of the second network element;

[0019] The first network element determines the information in the first configuration file based on the authorization configuration file and the connection between the second network element and the third network element;

[0020] The first network element sends the information in the first configuration file to the third network element.

[0021] In this way, the first network element does not need to send all the information to the third network element, but only sends the information related to the operation of the third network element in the first configuration file, thus reducing system overhead.

[0022] In one possible implementation of the first aspect, configuring the connection between the second network element and the third network element by the first network element includes:

[0023] The first network element notifies the third network element of the reachable address of the second network element.

[0024] In one possible implementation of the first aspect, configuring the connection between the second network element and the third network element by the first network element includes:

[0025] The first network element notifies the second network element of the reachable address of the third network element based on the reachable address of the second network element.

[0026] In one possible implementation of the first aspect, the method further includes:

[0027] The first network element receives a first notification from the third network element, wherein the first notification indicates the connection between the second network element and the third network element.

[0028] After the connection between the second network element and the third network element is established, the third network element sends a notification to the first network element indicating this connection, so that the first network element can better manage and control the second and third network elements.

[0029] In one possible implementation of the first aspect, the method further includes:

[0030] The first network element sends a first confirmation to the third network element, wherein the first confirmation indicates that the first notification has been received.

[0031] In one possible implementation of the first aspect, both the first notification and the first confirmation include the identifier of the first basic service.

[0032] In another possible implementation of the first aspect, both the first notification and the first confirmation include a transaction number predefined for the first basic service.

[0033] In this way, information exchange between the first network element and the third network element can be carried out safely and reliably.

[0034] In one possible implementation of the first aspect, the first notification includes the identifier of the third network element, the identifier of the first basic service, the identifier of the second network element, and connection description information of the connection between the second network element and the third network element.

[0035] Similarly, information exchange between the first network element and the third network element can be performed safely and reliably.

[0036] In one possible implementation of the first aspect, the method further includes:

[0037] The first network element receives a load report from the third network element, wherein the load report indicates the load traffic processed by the third network element.

[0038] In one possible implementation of the first aspect, the method further includes:

[0039] The first network element determines another third network element based on the first configuration file of the second network element and the load report;

[0040] The first network element configures the connection between the second network element and the other third network element based on the reachable address of the second network element;

[0041] The first network element sends the information in the first configuration file to the other third network element based on the first configuration file.

[0042] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each third network element (such as C / M-TW-GW) it controls and manages, and promptly reconfigure the new C / M-TW-GW 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.

[0043] In one possible implementation of the first aspect, the method further includes:

[0044] The first network element releases the connection between the second network element and the third network element.

[0045] In one possible implementation of the first aspect, the timing of the third network element reporting the load report is configured or predefined by the first network element.

[0046] Since the timing of load reporting can be configured by the first network element or predefined, load reporting can be flexibly performed according to actual applications.

[0047] In one possible implementation of the first aspect, the method further includes:

[0048] The first network element receives a second confirmation from the third network element, wherein the second confirmation indicates that the information in the first configuration file has been received.

[0049] In one possible implementation of the first aspect, the authorization configuration file of the second network element includes the identifier of the first basic service and the identifier of the second network element;

[0050] The authorization configuration file of the second network element further includes at least one of the following:

[0051] The identifier of the second basic service provided by the consumer and the identifier of the network element of the second basic service; or

[0052] Determine the permissions of the consumer.

[0053] Based on the information included in the authorization configuration file, the first network element can quickly determine the consumer of the first basic service that the second network element can provide, and further determine the third network element (such as C / M-TW-GW) that needs to be configured, thus reducing system overhead.

[0054] In a second aspect, one embodiment of this disclosure provides a configuration method. The method includes:

[0055] The third network element receives information from the first network element, wherein the information is included in a first configuration file of the second network element received by the first network element. The first configuration file includes at least one of the reachable address of the second network element or the authorization configuration file of the second network element. The authorization configuration file is used to determine the consumer that the second network element can provide the first basic service.

[0056] In this way, by using the reachable address of the second network element, the first network element can determine a suitable third network element; a secure logical connection between this second network element and the third first network element can be established under the control of the first network element; by using the authorization configuration file, the first network element can determine the consumer of the first basic service (such as XaaS) that the second network element can provide, and therefore can select a suitable third network element for the second network element; then, the third first network element can be configured using the information from the first configuration file of the second network element, thus realizing the configuration of the third network element. In a possible implementation where both the second and third network elements are gateways (also known as trusted gateways or C / M-TW-GW), by introducing the anonymous service provided by the trusted gateway on the control / management (C / M) plane of the communication system (such as a 6G system), the trustworthiness of communication is improved from the perspective of the operation of the communication system.

[0057] In one possible implementation of the second aspect, the first configuration file is indicated by a registration message received by the first network element from the second network element or the first basic service.

[0058] In one possible implementation of the second aspect, the method further includes:

[0059] The third network element receives the first configuration file from the fifth network element, wherein the third network element is connected to the fifth network element;

[0060] The third network element forwards the first configuration file to the first network element.

[0061] Based on the above, the first network element can receive the first configuration file of the second network element in multiple ways, so the receiving method of the first configuration file can be flexibly set according to actual needs.

[0062] In one possible implementation of the second aspect, the first configuration file includes the reachable address of the second network element and the authorization configuration file of the second network element;

[0063] The method further includes:

[0064] 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;

[0065] The third network element sends a first notification to the first network element, wherein the first notification indicates the connection between the second network element and the third network element.

[0066] After the connection between the second network element and the third network element is established, the third network element sends a notification to the first network element indicating this connection, so that the first network element can better manage and control the second and third network elements.

[0067] In one possible implementation of the second aspect, the method further includes:

[0068] The third network element receives a first confirmation from the first network element, wherein the first confirmation indicates that the first notification has been received.

[0069] In one possible implementation of the second aspect, both the first notification and the first confirmation include the identifier of the first basic service.

[0070] In another possible implementation of the second aspect, both the first notification and the first confirmation include a transaction number predefined for the first basic service.

[0071] In this way, information exchange between the first network element and the third network element can be carried out safely and reliably.

[0072] In one possible implementation of the second aspect, the first notification includes the identifier of the third network element, the identifier of the first basic service, the identifier of the second network element, and connection description information of the connection between the second network element and the third network element.

[0073] Similarly, information exchange between the first network element and the third network element can be performed safely and reliably.

[0074] In one possible implementation of the second aspect, the method further includes:

[0075] The third network element reports a load report to the first network element, wherein the load report indicates the load traffic processed by the third network element.

[0076] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each third network element (such as C / M-TW-GW) it controls and manages, and promptly reconfigure the new C / M-TW-GW 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.

[0077] In one possible implementation of the second aspect, the method further includes:

[0078] The third network element sends a second confirmation to the first network element, wherein the second confirmation indicates that the information in the first configuration file has been received.

[0079] By receiving confirmation of the information received in the first configuration file, the first network element can better manage and control the gateway.

[0080] In a third aspect, one embodiment of this disclosure provides a configuration method. The method includes:

[0081] The first network element receives a second configuration file, wherein the second configuration file includes at least one of a task configuration file of the sixth network element or a reachable address of the seventh network element. The task configuration file is used to instruct the sixth network element to execute an action in a task, and the reachable address of the seventh network element is used to establish a connection between the sixth network element and the seventh network element.

[0082] The first network element determines the sixth network element based on the second configuration file; and

[0083] The first network element sends the information in the second configuration file to the sixth network element based on the second configuration file.

[0084] In this way, by using the reachable address of the seventh network element, the first network element can determine the appropriate sixth network element; a secure logical connection between the sixth network element and this first network element can be established under the control of the first network element; by using the task configuration file, an appropriate sixth network element can be selected to execute the actions indicated in the task configuration file; and then the sixth network element can be configured using the information from the second configuration file of the seventh network element, thus realizing the configuration of the sixth network element.

[0085] In one possible implementation of the third aspect, the second configuration file includes the reachable address of the seventh network element;

[0086] The reachable address of the seventh network element received by the first network element includes:

[0087] The first network element receives a registration message from the seventh network element, wherein the registration message indicates the reachable address of the seventh network element.

[0088] In one possible implementation of the third aspect, the second configuration file includes the reachable address of the seventh network element;

[0089] The reachable address of the seventh network element received by the first network element includes:

[0090] The first network element receives a registration message from the first basic service to which the seventh network element belongs, wherein the registration message indicates the reachable address of the seventh network element.

[0091] In one possible implementation of the third aspect, the second configuration file includes the reachable address of the seventh network element;

[0092] The reachable address received by the first network element from the seventh network element includes:

[0093] The first network element receives the reachable address of the seventh network element forwarded from the fifth network element by the seventh network element, wherein the seventh network element is connected to the fifth network element.

[0094] Based on the above, the first network element can receive the reachable address of the seventh network element in multiple ways, so the receiving method of the reachable address can be flexibly set according to actual needs.

[0095] In one possible implementation of the third aspect, the second configuration file includes the reachable address of the seventh network element and the task configuration file of the sixth network element;

[0096] The first network element sends the information in the second configuration file to the sixth network element based on the second configuration file, including:

[0097] The first network element configures the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element;

[0098] The first network element determines the information in the second configuration file based on the second configuration file and the connection between the sixth and seventh network elements; and

[0099] The first network element sends the information in the second configuration file to the sixth network element.

[0100] In this way, the first network element does not need to send all the information to the sixth network element, but only sends the information related to the operation of the sixth network element in the second configuration file, thus reducing system overhead.

[0101] In one possible implementation of the third aspect, configuring the connection between the sixth and seventh network elements based on the reachable address of the seventh network element includes:

[0102] The first network element notifies the sixth network element of the reachable address of the seventh network element.

[0103] In one possible implementation of the third aspect, configuring the connection between the sixth and seventh network elements based on the reachable address of the seventh network element includes:

[0104] The first network element notifies the seventh network element of the reachable address of the sixth network element based on the reachable address of the seventh network element.

[0105] In one possible implementation of the third aspect, the method further includes:

[0106] The first network element receives a second notification from the sixth network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element.

[0107] After the connection between the sixth network element and the seventh network element is established, the sixth network element sends a notification to the first network element indicating this connection, so that the first network element can better manage and control the sixth network element and the seventh network element.

[0108] In one possible implementation of the third aspect, the method further includes:

[0109] The first network element sends a third confirmation to the sixth network element, wherein the third confirmation indicates that the second notification has been received.

[0110] In one possible implementation of the third aspect, both the second notification and the third confirmation include the identifier of the first basic service to which the seventh network element belongs.

[0111] In another possible implementation of the third aspect, both the second notification and the third confirmation include a transaction number predefined for the first basic service.

[0112] In this way, information exchange between the first network element and the sixth network element can be carried out safely and reliably.

[0113] In one possible implementation of the third aspect, the second notification includes the identifier of the sixth network element, the identifier of the first basic service to which the seventh network element belongs, the identifier of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

[0114] Similarly, information exchange between the first network element and the sixth network element can be performed safely and reliably.

[0115] In one possible implementation of the third aspect, the method further includes:

[0116] The first network element receives a fourth confirmation from the sixth network element, wherein the fourth confirmation indicates that the information in the second configuration file has been received.

[0117] By receiving confirmation of the information received in the second configuration file, the first network element can better manage and control the gateway.

[0118] In one possible implementation of the third aspect, both the information in the second configuration file and the fourth confirmation include an identifier for indicating the task.

[0119] In one possible implementation of the third aspect, the information in the second configuration file includes an identifier for indicating the first action to be performed by the sixth network element, an identifier for indicating the next network element to perform the second action after the sixth network element, and an identifier for indicating the second action.

[0120] In one possible implementation of the third aspect, the information in the second configuration file includes an identifier for indicating the first action to be performed by the sixth network element, a quality of service (QoS) parameter of the sixth network element, an identifier for indicating the next network element to perform the second action after the sixth network element, and an identifier for indicating the connection between the sixth network element and the next network element.

[0121] In one possible implementation of the third aspect, the information in the second configuration file includes an identifier for indicating the QoS parameters of the sixth network element.

[0122] In one possible implementation of the third aspect, the method further includes:

[0123] The first network element receives a load report from the sixth network element, wherein the load report indicates the load traffic processed by the sixth network element.

[0124] In one possible implementation of the third aspect, the method further includes:

[0125] The first network element determines another sixth network element based on the second configuration file and the load report;

[0126] The first network element configures the connection between the seventh network element and the other sixth network element based on the reachable address of the seventh network element; and

[0127] The first network element sends the information in the second configuration file to the other sixth network element based on the second configuration file.

[0128] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each sixth network element (such as Data-TW-GW) it controls and manages, and promptly reconfigure the new Data-TW-GW 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.

[0129] In one possible implementation of the third aspect, the method further includes:

[0130] The first network element releases the connection between the sixth network element and the seventh network element.

[0131] In one possible implementation of the third aspect, the timing at which the third network element reports the load report is configured by the first network element or predefined.

[0132] Since the timing of load reporting can be configured by the first network element or predefined, load reporting can be flexibly performed according to actual applications.

[0133] In a fourth aspect, one embodiment of this disclosure provides a configuration method, the method comprising:

[0134] The sixth network element receives information from the first network element, wherein the information is included in a second configuration file received by the first network element. The second configuration file includes at least one of the sixth network element's task configuration file or the reachable address of the seventh network element. The task configuration file is used to instruct the sixth network element to perform actions in a task, and the reachable address of the seventh network element is used to establish a connection between the sixth network element and the seventh network element.

[0135] In this way, by using the reachable address of the seventh network element, the first network element can determine the appropriate sixth network element; a secure logical connection between the sixth network element and this first network element can be established under the control of the first network element; by using the task configuration file, an appropriate sixth network element can be selected to execute the actions indicated in the task configuration file; and then the sixth network element can be configured using the information from the second configuration file of the seventh network element, thus realizing the configuration of the sixth network element.

[0136] In one possible implementation of the fourth aspect, the second configuration file includes the reachable address of the seventh network element;

[0137] The second configuration file is indicated by the registration message received by the first network element from the seventh network element or the first basic service.

[0138] Based on the above, the first network element can receive the reachable address of the seventh network element in multiple ways, so the receiving method of the reachable address can be flexibly set according to actual needs.

[0139] In one possible implementation of the fourth aspect, the second configuration file includes the reachable address of the seventh network element;

[0140] The method further includes:

[0141] The sixth network element establishes the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element;

[0142] The sixth network element sends a second notification to the first network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element.

[0143] After the connection between the sixth network element and the seventh network element is established, the sixth network element sends a notification to the first network element indicating this connection, so that the first network element can better manage and control the sixth network element and the seventh network element.

[0144] In one possible implementation of the fourth aspect, the method further includes:

[0145] The sixth network element receives a third confirmation from the first network element, wherein the third confirmation indicates that the second notification has been received.

[0146] In one possible implementation of the fourth aspect, both the second notification and the third confirmation include the identifier of the first basic service to which the seventh network element belongs.

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

[0148] In this way, information exchange between the first network element and the sixth network element can be carried out safely and reliably.

[0149] In one possible implementation of the fourth aspect, the second notification includes the identifier of the sixth network element, the identifier of the first basic service to which the seventh network element belongs, the identifier of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

[0150] Similarly, information exchange between the first network element and the sixth network element can be performed safely and reliably.

[0151] In one possible implementation of the fourth aspect, the method further includes:

[0152] The sixth network element sends a fourth confirmation to the first network element, wherein the fourth confirmation indicates that the information in the second configuration file has been received.

[0153] By receiving confirmation of the information received in the second configuration file, the first network element can better manage and control the gateway.

[0154] In one possible implementation of the fourth aspect, both the information in the second configuration file and the fourth confirmation include an identifier for indicating the task.

[0155] In one possible implementation of the fourth aspect, the method further includes:

[0156] The sixth network element reports a load report to the first network element, wherein the load report indicates the load traffic processed by the sixth network element.

[0157] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each sixth network element (such as Data-TW-GW) it controls and manages, and promptly reconfigure the new Data-TW-GW 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.

[0158] In a fifth aspect, one embodiment of this disclosure provides a configuration apparatus applied to a first network element and comprising modules for executing the configuration method according to the first aspect or any possible implementation thereof.

[0159] In a sixth aspect, one embodiment of this disclosure provides a configuration apparatus applied to a third network element and comprising modules for performing the configuration method according to the second aspect or any possible implementation thereof.

[0160] In a seventh aspect, one embodiment of this disclosure provides a configuration apparatus applied to a first network element and comprising modules for executing the configuration method according to the third aspect or any possible implementation thereof.

[0161] In an eighth aspect, one embodiment of this disclosure provides a configuration apparatus applied to a sixth network element and comprising modules for performing the configuration method according to the fourth aspect or any possible implementation thereof.

[0162] In a ninth aspect, one embodiment of this disclosure provides a first network element including processing circuitry for performing the configuration method according to the first aspect or any possible implementation thereof.

[0163] In a tenth aspect, one embodiment of this disclosure provides a third network element including processing circuitry for performing the configuration method according to the second aspect or any possible implementation thereof.

[0164] In an eleventh aspect, one embodiment of this disclosure provides a first network element including processing circuitry for performing the configuration method according to the third aspect or any possible implementation thereof.

[0165] In a twelfth aspect, one embodiment of this disclosure provides a sixth network element including processing circuitry for performing the configuration method according to the fourth aspect or any possible implementation thereof.

[0166] In a thirteenth aspect, one embodiment of this disclosure provides a computer-readable medium storing computer-executable instructions, wherein, when executed by a processor, the computer-executable instructions cause the processor to perform the configuration method according to the first aspect or any possible implementation thereof, or the configuration method according to the second aspect or any possible implementation thereof.

[0167] In a fourteenth aspect, one embodiment of this disclosure provides a computer-readable medium storing computer-executable instructions, wherein, when executed by a processor, the computer-executable instructions cause the processor to perform the configuration method according to the third aspect or any possible implementation thereof, or the configuration method according to the fourth aspect or any possible implementation thereof.

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

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

[0170] In a seventeenth aspect, one embodiment of this disclosure provides a computer program product including computer-executable instructions, wherein, when executed by a processor, the computer-executable instructions cause the processor to perform 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.

[0171] In an eighteenth aspect, one embodiment of this disclosure provides an apparatus including one or more processors. The one or more processors are configured to execute instructions stored in a memory, wherein, when executed by the one or more processors, the configuration method is performed according to the first aspect or any possible implementation thereof, or according to the second aspect or any possible implementation thereof, or according to the third aspect or any possible implementation thereof, or according to the fourth aspect or any possible implementation thereof.

[0172] In the configuration method according to this disclosure, a first network element receives a first configuration file from a second network element, wherein the first configuration file includes at least one of the reachable address of the second network element or the authorization configuration file of the second network element, the authorization configuration file being used to determine the consumer of the first basic service that the second network element can provide; a third network element is determined based on the first configuration file of the second network element; and information in the first configuration file is sent to the third network element based on the first configuration file. In this way, by using the reachable address of the second network element, the first network element can determine a suitable third network element; a secure logical connection between the second network element and the third network element can be established under the control of the first network element; by using the authorization configuration file, the first network element can determine the consumer of the first basic service (such as XaaS) that the second network element can provide, and therefore can select a suitable third network element for the second network element; then, the third network element can be configured using the information from the first configuration file of the second network element, thus realizing the configuration of the third network element. In one possible implementation where both the second and third network elements are gateways (also known as trusted gateways or C / M-TW-GW), the credibility of communication is enhanced from the perspective of the operation of the communication system by introducing anonymous services provided by trusted gateways on the control / management (C / M) plane and data plane of the communication system (such as 6G system). Attached Figure Description

[0173] The following figures illustrate exemplary embodiments of the present disclosure by way of example, in which:

[0174] Figure 1 This is a simplified schematic diagram of a communication system according to one or more embodiments of the present disclosure.

[0175] Figure 2 This is a schematic diagram of an example communication system according to one or more embodiments of the present disclosure.

[0176] Figure 3 This is a schematic diagram of the basic component structure of a communication system according to one or more embodiments of the present disclosure.

[0177] Figure 4A block diagram of a device in a communication system according to one or more embodiments of the present disclosure is shown.

[0178] Figure 5 A block diagram illustrating the conceptual structure of a 6G system according to one or more embodiments of the present disclosure is shown.

[0179] Figure 6 A schematic diagram of the framework according to one or more embodiments of the present disclosure is shown.

[0180] Figure 7 A schematic flowchart of a configuration method for C / M-TW-GW according to one or more embodiments of the present disclosure is shown.

[0181] Figure 8 A schematic flowchart of a configuration method based on reachable addresses and authorization profiles according to one or more embodiments of the present disclosure is shown.

[0182] Figure 9A A schematic flowchart illustrating the connection process between a second network element and a third network element according to one or more embodiments of the present disclosure is shown.

[0183] Figure 9B A schematic flowchart illustrating an exemplary connection process between a second network element and a third network element according to one or more embodiments of the present disclosure is shown.

[0184] Figure 9C A schematic flowchart illustrating another exemplary connection process between a second network element and a third network element according to one or more embodiments of the present disclosure is shown.

[0185] Figure 10A A schematic flowchart illustrating an exemplary configuration process for a third network element (i.e., C / M-TW-GW) according to one or more embodiments of this disclosure is shown.

[0186] Figure 10B A schematic flowchart of another exemplary configuration process for a third network element (i.e., C / M-TW-GW) according to one or more embodiments of the present disclosure is shown.

[0187] Figure 11 A schematic flowchart of a configuration method for a Data-TW-GW according to one or more embodiments of the present disclosure is shown.

[0188] Figure 12 A schematic flowchart of a configuration method based on reachable addresses and task profiles according to one or more embodiments of the present disclosure is shown.

[0189] Figure 13A A schematic flowchart illustrating the connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure is shown.

[0190] Figure 13B A schematic flowchart illustrating an exemplary connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure is shown.

[0191] Figure 13C A schematic flowchart illustrating another exemplary connection process between a sixth network element and a seventh network element according to one or more embodiments of the present disclosure is shown.

[0192] Figure 14A A schematic flowchart illustrating an exemplary configuration process for a sixth network element (i.e., Data-TW-GW) according to one or more embodiments of this disclosure is shown.

[0193] Figure 14B A schematic flowchart of another exemplary configuration process for a sixth network element (i.e., Data-TW-GW) according to one or more embodiments of this disclosure is shown.

[0194] Figure 15 This is a schematic diagram of the configuration device according to one or more embodiments of the present disclosure.

[0195] Figure 16 This is a schematic diagram of another configuration device according to one or more embodiments of the present disclosure.

[0196] Figure 17 This is a schematic diagram of another configuration device according to one or more embodiments of the present disclosure.

[0197] Figure 18 This is a schematic diagram of another configuration device according to one or more embodiments of the present disclosure. Detailed Implementation

[0198] To more clearly describe the embodiments of this disclosure or the technical solutions in the prior art, the accompanying drawings required for describing the embodiments or the prior art are briefly introduced below.

[0199] In the following description, reference is made to the accompanying drawings, which form a part of this disclosure, which illustrate by way of description specific aspects of embodiments of this disclosure or aspects that may be used with embodiments of this disclosure. It should be understood that embodiments of this disclosure can be used in other aspects and include structural or logical variations not depicted in the drawings. Therefore, the following detailed description should not be construed in a limiting sense, and the scope of this disclosure is defined by the appended claims.

[0200] To aid in understanding this disclosure, examples of wireless communication systems and devices are described below.

[0201] Example communication systems and devices

[0202] refer to Figure 1 , Figure 1 This is a non-limiting illustrative example providing a simplified schematic diagram of a communication system. Communication system 100 includes a radio access network 120. Radio access network 120 can be a next-generation (such as sixth-generation, 6G, or higher) radio access network or a traditional (such as 5G, 4G, 3G, or 2G) radio access network. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generally referred to as 110) can be interconnected with each other or connected to one or more network nodes (170a, 170b, generally referred to as 170) in radio access network 120. Core network 130 can be part of the communication system and can depend on or be independent of the radio access technology used in communication system 100. In addition, the communication system 100 includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0203] Figure 2 An example communication system 100 is illustrated. Generally, communication system 100 enables multiple wireless or wired components to communicate data and other content. The purpose of communication system 100 may be to provide content such as voice, data, video, and / or text via broadcast, multicast, unicast, etc. Communication system 100 can operate by sharing resources (such as carrier spectrum bandwidth) among its constituent components. Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide a wide variety of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, automated delivery, and mobility). Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can form a multi-layered heterogeneous network. Compared to traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link joint operation between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching.

[0204] Terrestrial communication systems and non-terrestrial communication systems can be considered subsystems of a communication system. Figure 2In the example shown, communication system 100 includes electronic devices (EDs) 110a, 110b, 110c, and 110d (generally referred to as ED 110), radio access networks (RANs) 120a and 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. RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which are generally referred to as terrestrial transmit and receive points (T-TRPs) 170a and 170b. The non-terrestrial communication network 120c includes access nodes 172, which are generally referred to as non-terrestrial transmit and receive points (NT-TRPs) 172.

[0205] Alternatively or additionally, any ED 110 can be used to interface, access, or communicate with any T-TRP 170a, 170b, and NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can communicate uplink and / or downlink with T-TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d can also communicate directly with each other via one or more side air interfaces 190b. In some examples, ED 110d can communicate uplink and / or downlink with NT-TRP 172 via non-terrestrial air interface 190c.

[0206] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, 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)). Air interfaces 190a and 190b can utilize other high-dimensional signal spaces, which may include combinations of orthogonal and / or non-orthogonal dimensions.

[0207] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link or simply via a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.

[0208] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b, and / or core network 130, can communicate directly or indirectly 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 use the same radio access technology as RANs 120a and / or RAN 120b. Core network 130 can also serve as a gateway access between (i) RANs 120a and 120b, and / or EDs 110a, 110b, and 110c, and (ii) other networks (such as PSTN 140, Internet 150, and other networks 160). Additionally, some or all of EDs 110a, 110b, and 110c may include functionality for communicating with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c can communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include computer networks and / or subnets (internal networks) and integrate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies and may include multiple transceivers required to support such technologies.

[0209] Basic component structure

[0210] Figure 3Another example of an ED 110 and base stations 170a, 170b, and / or 170c is shown. The ED 110 is used to connect people, things, machines, etc. The ED 110 can be widely used in various scenarios, including cellular communication, 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, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, and more.

[0211] Each ED 110 represents any suitable end-user equipment for wireless operation and may include (or be referred to as): user equipment / device (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smartbook, vehicle, automobile, truck, bus, train, or IoT device, wearable device (such as watch, glasses, head-mounted device, etc.), industrial equipment, or devices that include or incorporate the above-mentioned equipment (such as communication modules, modems, or chips), etc. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, referred to below as T-TRP 170. Furthermore, as Figure 3As shown, NT-TRP is referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically started (i.e., established, activated, or enabled), shut down (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0212] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure to avoid clutter. One, some, or all of the antennas 204 may alternatively be panels. The transmitter 201 and receiver 203 may be integrated, for example, integrated as a transceiver. The transceiver is used to modulate data or other content for transmission through at least one antenna 204 or a network interface controller (NIC). The transceiver may also be used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals.

[0213] ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by one or more processing units (such as processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) card, and processor cache, etc.

[0214] ED 110 may also include one or more input / output devices (not shown) or interfaces (such as those connected to...). Figure 1(Wired interface of Internet 150). Input / output devices or interfaces support interaction with users or other devices in the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user and / or for network interface communication. Suitable structures include, for example, speakers, microphones, keypads, keyboards, displays, touchscreens, etc.

[0215] ED 110 includes a processor 210 for performing the following operations: operations related to preparing to transmit uplink transmissions to NT-TRP 172 and / or T-TRP 170; operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and operations related to processing lateral link transmissions transmitted to and from other ED 110s. Processing operations related to preparing to transmit uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to an embodiment, the downlink transmission may be received by receiver 203, possibly using receive beamforming, and processor 210 may extract signaling from the downlink transmission (e.g., by detecting and / or decoding signaling). An example of signaling may be a reference signal transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 performs transmit beamforming and / or receive beamforming based on beam direction indications (such as beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (such as initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0216] Although not shown in the figures, processor 210 may be part of transmitter 201 and / or receiver 203. Although not shown in the figures, memory 208 may be part of processor 210.

[0217] The processing components in processor 210, transmitter 201, and receiver 203 may be implemented by the same or different processors for executing instructions stored in memory (such as memory 208). Alternatively, some or all of the processing components in processor 210, transmitter 201, and receiver 203 may be implemented using dedicated circuitry, such as a programmable 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.

[0218] In some implementations, the T-TRP 170 can have other names, such as base station (BS), base transceiver station (BTS), wireless base station, network node, network equipment, network-side equipment, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, next generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network equipment, ground base station, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), location node, etc. T-TRP 170 can be a macro BS, a pico BS, a relay node, or a donor node, or a combination thereof. T-TRP 170 can refer to the aforementioned equipment or to a component within such equipment (such as a communication module, modem, or chip).

[0219] In some embodiments, the components of T-TRP 170 may be distributed. For example, some modules in T-TRP 170 may be located remotely from the device housing the antenna 256 of T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) sometimes referred to as a fronthaul (such as a common public radio interface (CPRI)). Therefore, in some embodiments, the term "T-TRP 170" may also refer to network-side modules that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding, which are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that operate together to serve ED 110, such as through the use of cooperative multicast.

[0220] 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 shown in the figure to avoid clutter. One, some, or all of the antennas 256 may alternatively be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing operations related to: preparing downlink transmissions to be transmitted to ED 110; processing uplink transmissions received from ED 110; preparing backhaul transmissions to be transmitted to NT-TRP 172; and processing transmissions received from NT-TRP 172 via backhaul. Processing operations related to preparing downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to receiving transmissions in the uplink or backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. Processor 260 may also perform operations related to network access (such as initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB) and generating system information. In some embodiments, processor 260 may also generate beam direction indications, such as BAIs, that scheduler 253 can schedule for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110 and determining where to deploy NT-TRP 172. In some embodiments, processor 260 may generate signaling, for example, to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that the term "signaling" as used herein may also be alternatively referred to as control signaling. Signaling can be transmitted in physical layer control channels such as the physical downlink control channel (PDCCH). In this case, the signaling can be referred to as dynamic signaling. Signaling transmitted in the downlink physical layer control channel can be called downlink control information (DCI). Signaling transmitted in the uplink physical layer control channel can be called uplink control information (UCI). Signaling transmitted in the sidelink physical layer control channel can be called sidelink control information (SCI).Signaling can be included in higher-layer (e.g., above the physical layer) data packets transmitted over physical layer data channels such as the Physical Downlink Shared Channel (PDSCH). In this case, the signaling can be referred to as higher-layer signaling, static signaling, or semi-static signaling. Higher-layer signaling can also refer to radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling.

[0221] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included within T-TRP 170 or may operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, sidelink, and / or backlink transmissions, including issuing scheduling grants and / or configuring schedule-free (e.g., “configuration grants”) resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by processor 260.

[0222] Although not shown in the figures, processor 260 may be part of transmitter 252 and / or receiver 254. Furthermore, although not shown in the figures, processor 260 may implement scheduler 253. Although not shown in the figures, memory 258 may be part of processor 260.

[0223] The processing components in processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented by the same or different processors for executing instructions stored in memory (such as memory 258). Alternatively, some or all of the processing components in processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using special-purpose circuitry such as a programmable FPGA, hardware accelerator (such as a GPU or AI accelerator), or ASIC.

[0224] Although the NT-TRP 172 is exemplified only as a drone, it can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms, including international mobile communication base stations and unmanned aerial vehicles. Furthermore, in some implementations, the NT-TRP 172 may have other names, 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 shown in the figure to avoid clutter. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing operations related to: preparing downlink transmissions to ED 110; processing uplink transmissions received from ED 110; preparing return transmissions to T-TRP 170; and processing transmissions received from T-TRP 170 via return. Processing operations related to preparing downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing receive transmissions in the uplink or backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-layer functions, such as those in the medium access control (MAC) layer or radio link control (RLC) layer. Since this is only an example, NT-TRP 172 typically implements higher-layer functions in addition to physical layer processing.

[0225] The NT-TRP 172 also includes memory 278 for storing information and data. Although not shown in the figures, processor 276 may be part of transmitter 272 and / or receiver 274. Although not shown in the figures, memory 278 may be part of processor 276.

[0226] The processing components in processor 276, transmitter 272, and receiver 274 may be implemented by the same or different processors, which execute instructions stored in memory (such as memory 278). Alternatively, some or all of the processing components in processor 276, transmitter 272, and receiver 274 may be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerators (such as GPUs or AI accelerators), or ASIC. In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs operating together to serve ED 110, such as through cooperative multicast.

[0227] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but for clarity these components are omitted.

[0228] Basic module structure

[0229] according to Figure 4 One or more steps of the methods in the embodiments provided herein may be performed by the corresponding unit or module. Figure 4 The diagram illustrates units or modules within a device (such as ED 110, T-TRP 170, or NT-TRP 172). For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be circuits, such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more of these units or modules may be logic, such as logical functions executed by circuits, a portion of an integrated circuit, or software instructions executed by a processor. It should be understood that when modules are implemented using, for example, software executed by a processor, these modules may be retrieved by the processor, in whole or in part, individually or collectively, for processing of one or more instances as needed, and these modules themselves may include instructions for further deployment and instantiation.

[0230] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0231] 6G Smart Air Interface

[0232] An air interface typically includes numerous components and associated parameters that collectively specify how transmissions are sent and / or received between two or more communication devices via a wireless communication link. For example, an air interface may include one or more waveforms, one or more frame structures, one or more multiple access schemes, one or more protocols, one or more coding schemes, and / or one or more modulation schemes that define the transmission of information (such as data) via the wireless communication link. The wireless communication link may support links between a radio access network and user equipment (such as a "Uu" link), and / or it may support links between devices, such as links between two user equipment (such as a "sidelink"), and / or it may support links between a non-terrestrial (NT) communication network and user equipment (UE). The air interface may also utilize UWB technology to perform ambient awareness using UWB signals.

[0233] Here are some examples of the components mentioned above:

[0234] Waveform components can specify the shape and form of the signal being transmitted. Waveform options can include orthogonal multiple access (OFDM) and non-orthogonal multiple access (NOA) waveforms. Non-limiting examples of such waveform options include orthogonal frequency division multiplexing (OFDM), filtered OFDM (f-OFDM), time-domain windowed OFDM, filter bank multicarrier (FBMC), universal filtered multicarrier (UFMC), generalized frequency division multiplexing (GFDM), wavelet packet modulation (WPM), faster than nyquist (FTN) waveforms, high-rate pulse repetition frequency (HRP) UWB waveforms, low-rate pulse repetition frequency (LRP) UWB waveforms, and low peak-to-average power ratio (LPPRWF) waveforms.

[0235] The frame structure component can specify the configuration of a single frame or a group of frames. The frame structure component can indicate one or more of the following parameters: time, frequency, pilot signature, encoding, or other parameters for a single frame or a group of frames. The frame structure will be discussed in detail below.

[0236] Multiple access scheme components can specify multiple access technology options, including technologies that limit how communication devices share the 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). In addition, multiple access technology options may include: scheduled access and unscheduled access, also known as unlicensed access; non-orthogonal multiple access and orthogonal multiple access, such as through dedicated channel resources (e.g., not shared between multiple communication devices); contention-based shared channel resources and non-contention-based shared channel resources; and radio-based cognitive access.

[0237] The Hybrid Automatic Repeat Request (HARQ) protocol component can specify how transmission and / or retransmission are performed. Non-limiting examples of transmission and / or retransmission mechanism options include specifying the scheduling data pipeline size, the signaling mechanism used for transmission and / or retransmission, and examples of the retransmission mechanism.

[0238] The coding and modulation components specify how information being transmitted is encoded / decoded and modulated / demodulated for transmission / reception purposes. Encoding can refer to methods of error detection and forward error correction. Non-limiting examples of coding options include turbo lattice codes, turbo product codes, fountain codes, low-density parity-check codes, and polar codes. Modulation can simply refer to a constellation (e.g., including modulation techniques and orders), or more specifically to various types of advanced modulation methods such as layered modulation and low PAPR modulation.

[0239] In some embodiments, the air interface may be a "one-size-fits-all" concept. For example, once the air interface is defined, the components within it cannot be changed or adjusted. In some implementations, only a limited number of parameters or modes of the air interface can be configured, such as cyclic prefix (CP) length or multiple input multiple output (MIMO) mode. In some embodiments, the air interface design can provide a unified or flexible framework to support licensed and unlicensed access in frequency bands below and above 6 GHz (such as mmWave). For example, the flexibility of a configurable air interface provided by scalable parameter sets (numerology) and symbol durations can enable optimization of transmission parameters for different spectrum bands and different services / devices. Furthermore, a unified air interface can be self-contained in the frequency domain; a self-contained frequency domain design can support more flexible radio access network (RAN) slicing through channel resource sharing between different services in terms of frequency and time.

[0240] The schemes described in this disclosure can be applied to next-generation networks (such as sixth-generation (6G) or higher) as well as traditional networks (such as 5G or 4G).

[0241] The proposed 6G system architecture is defined as supporting 6G X as a Service (XaaS) services by employing technologies such as network function virtualization and network slicing. The 6G system architecture adopts a service-based interaction mechanism between 6G services.

[0242] This 6G system adopts a service-based architecture (SBA) and the XaaS concept. The XaaS services in the 6G system are divided into three layers. The conceptual structure of the 6G system is as follows: Figure 5 As shown.

[0243] The infrastructure layer includes the infrastructure that supports 6G services. This includes wireless network (RAN, CN) infrastructure, cloud / data center infrastructure, satellite networks, storage / database infrastructure, and sensing networks. This infrastructure can be provided by a single provider or multiple providers.

[0244] Each type of infrastructure can have its own control and management functions, represented as C / M functions, for infrastructure management. Each of these infrastructure types is a type of Infrastructure as a Service.

[0245] The control and management (C / M) layer includes control and management services for the 6G system. These services are developed and deployed using slicing technology and leveraging resources provided by the infrastructure layer. The 6G services in the control and management (C / M) layer include:

[0246] Resource management (RM) as a service: provides lifecycle management of various slices and the ability to allocate over-the-air resources to wireless devices.

[0247] - Mission management (MM) as a service: provides the ability to programmatically provide XaaS services in the service layer to provide mission services.

[0248] - Confederation Network (CONET) as a Service: Provides the ability for multiple partners to jointly deliver 6G services. This capability is provided through consortium formation, mutual authentication and authorization among partners, and protocol negotiation regarding the recording and traceability of selected actions performed by partners, ensuring a trusted environment for the operation of 6G systems.

[0249] Service provisioning management (SPM) as a service provides the ability to control and manage a customer's access to 6G services and to provide requested services. This capability can be provided through unified mutual authentication, authorization and policies, key management, QoS guarantees, and billing between any pair of XaaS service providers and customers. These customers include not only end customers in the physical world but also digital representatives in the digital world.

[0250] - Connectivity Management (CM) as a Service: Utilizes 5G connectivity management capabilities, but extends to include the digital world.

[0251] - Protocol as a Service: Provides the ability to design customized protocol stacks for identified interfaces. These protocol stacks can be predefined for selection on demand, or designed on demand.

[0252] - Cybersecurity as a Service: Provides infrastructure owners with the ability to detect potential security risks to their infrastructure.

[0253] 6G tasks are defined as services provided by a 6G system to customers. A task can be a type of service provided by a single 6G XaaS service, or it can be a type of service that requires contributions from multiple XaaS services.

[0254] XaaS services in the C / M layer support both the control and management of the 6G system itself and provide support to vertical industries upon request. For example, RM services can provide air resource management for the RAN and also provide services to vertical industries to enable them to allocate air resources to their end customers. XaaS in the C / M layer can be deployed using slicing technology.

[0255] The service layer includes 6G services provided to customers. In the conceptual architecture of a 6G system:

[0256] AI services can be represented as NET4AI as a Service. Artificial intelligence services provide AI capabilities to support a wide range of AI applications.

[0257] The service of data collection, data cleaning, data analysis, and data delivery is referred to as DAM as a service. This service provides the ability to manage the lifecycle of statistical data, including data acquisition, de-identification, analysis, and delivery of information statistics from any type of sensor, device, and network function.

[0258] - Data storage and sharing services can be represented as NET4Data as a Service, which provides the ability to reliably store and share data under the control of the data owner and in accordance with the regulations of recognized authorities regarding the control of identified data.

[0259] Providing services for the digital world can be represented as NET4DW as a Service. Digital world services provide the ability to build, control, and manage the digital world. The digital world is defined as the digital realization of the physical world.

[0260] - 6G blockchain services can be represented as NET4BC as a service. 6G connectivity services are represented as NET4Con as a service. These services provide the capability to support 6G blockchain services.

[0261] - Enhanced connectivity services (such as network for connectivity (NET4CON)) are services. These services provide the ability to exchange messages and data between supporting new 6G services.

[0262] All XaaS services in this layer utilize resources provided within the infrastructure and are developed and deployed using network function virtualization and slicing technologies. The capabilities of each 6G service are provided by its control and management functions, as well as service-specific data processing capabilities.

[0263] In addition to supporting 6G XaaS services at the service layer, the 6G system also leverages the 5G system to provide vertical services. The difference between 6G XaaS services and other vertical industries is that vertical industries are purely customers who need other XaaS services to support their operation, while each XaaS service provides its capabilities to the 6G customer.

[0264] Any pair of XaaS services in a 6G system can also be customer and provider to each other. Some examples include infrastructure owners providing their resources to XaaS services in the service layer and C / M layer; RM services potentially requiring capabilities provided by NET4AI, DAM, and NET4DW for resource management in vertical slicing; and CONET and NET4Data services potentially requiring capabilities provided by NET4BC for their operation.

[0265] Within an XaaS service module, there are one or more network functions. These network functions can be divided into two categories: C / M functions for control and management, and data processing functions (also known as data functions) for processing data. Data processing functions exist only in the XaaS service layer.

[0266] The core concepts of 6G systems include:

[0267] - Define the basic XaaS service by decoupling various integrated services from the basic XaaS service. The basic XaaS service provides unique capabilities to support specific types of services, such as NET4AI service, NET4DW service, DAM service, NET4Data service, blockchain service, task management service, etc.

[0268] - Allows multiple partners to jointly operate the 6G system.

[0269] - Defines the data plane of the 6G system, including the data plane processing functions of XaaS services. Programming the interconnection of these functions through task management services enables support for various customized customer services. The data plane defined in the 6G system is a collection of data processing functions of XaaS services in the service layer, used to process and transmit 6G system data plane traffic. Traffic data types in the 6G system include: training models in the NET4AI service, collected raw data, cleaned data in the DAM service, data in NET4Data, digital world data in NET4DW, and data blocks in NET4BC.

[0270] - By classifying basic control and management services and combining these services into basic XaaS services in the control and management (C / M) layer, the 6G system architecture is simplified.

[0271] - Define the C / M plane of the 6G system, which includes C / M functions in XaaS services and may include 5G CPs (such as AMF) depending on the implementation scheme. The C / M plane of the 6G system is defined as the set of C / M functions of XaaS services in the conceptual architecture of the 6G system, and is used for C / M plane message exchange between XaaS services.

[0272] - By introducing trusted gateways (GWs) on the data plane and C / M plane of the 6G system, the SBI interface is simplified. The control / management plane trusted gateway (C / M-TW-GW) provides control plane connectivity, anonymous communication, and secure communication capabilities. To achieve these capabilities, the C / M-TW-GW provides the following functions: establishing and maintaining secure tunnels with each XaaS service; performing decryption and encryption operations when transmitting C / M plane messages; maintaining authorization configuration files for each XaaS service; and transmitting C / M plane messages. The data plane trusted gateway (Data-TW-GW) provides the ability to connect XaaS services via the data plane to enable anonymous and secure data plane interaction between XaaS services. The Data-TW-GW provides the following functions: establishing and maintaining secure tunnels with each XaaS service; performing decryption and encryption operations when transmitting data packets; data format conversion; and transmitting data packets.

[0273] - Define a basic architecture structure (BAS), which is a unified infrastructure with a minimal number of interfaces and is independent of infrastructure type. A BAS is a collection of XaaS services (including C / M plane and data plane functions), the TW-GW on the C / M plane and data plane, and the interfaces between these functions. The infrastructure network implementing a single 6G system BAS is defined as a BAS domain. Each of the RAN, CN, cloud infrastructure, or wireless devices can be a BAS domain.

[0274] - Use the BAS concept to simplify the standardization, development and deployment of 6G systems, while supporting various infrastructure deployment scenarios.

[0275] -By leveraging the capabilities, capacity, and demands of the infrastructure network, BAS or subsets can be applied to the infrastructure to adapt to various deployment scenarios.

[0276] -Utilize the SBI interface concept and apply SBI interaction to both the 6G C / M plane and the 6G data plane.

[0277] - By introducing CONET capabilities, NET4BC capabilities, and the anonymity services provided by trusted GWs on the C / M plane and data plane of the 6G system, trustworthiness is improved from the perspective of 6G system operation.

[0278] - Enhance trustworthiness from the perspective of end-customer privacy protection by providing unified mutual authentication, IDM and data cleansing through SPM service, DAM service and 6G blockchain service.

[0279] - Simplify roaming management of wireless devices in the physical and digital worlds through unified authentication that includes all participating partners and customers.

[0280] - By introducing the BAS concept, multiple architectural solutions can be defined without investing a lot of effort, supporting multiple development paths from 5G systems to 6G systems.

[0281] - By leveraging the advantages of SBA and its additional features, backward compatibility is supported. 5G users can access 5G services using 6G systems.

[0282] - Thanks to the concept of anonymous service provision implemented in the trusted GW of the 6G C / M plane and 6G data plane, future expansion can be supported by adding new XaaS services while minimizing the impact on standardization and deployment.

[0283] In existing technologies, neither 5G systems nor O-RAN possess the proposed 6G network architecture. 5G systems employ SCP and NRF in their CP SBI, supporting indirect communication on the 5G CP plane, but not strong trustworthiness. 5G systems lack a data plane definition and the concept of Data-TW-GW. O-RAN has short-term and long-term RICs, but these do not address the potential challenges of 6G.

[0284] Many emerging trends will drive the considerations and design of 6G / future wireless networks:

[0285] - New network infrastructure capabilities, such as widely deployed cloud-native / friendly infrastructure.

[0286] Emerging (relatively) mature technologies, such as large-scale AI models, data privacy protection, and blockchain, have made significant progress and have had a major impact on society and human life.

[0287] - New applications and services, such as AI services, data (sensing) services, digital world services, etc., are widely used in the industrial / commercial sector and by individual customers.

[0288] - The trends of globalization, openness, and collaboration are becoming increasingly prominent, meaning that more open and collaborative operating models are becoming common practices in many fields.

[0289] New expectations and more stringent requirements for future networks are driving a rethinking and development of next-generation wireless networks. These requirements include:

[0290] Privacy and trustworthiness, etc.

[0291] -Simplify and standardize.

[0292] - Rapid deployment.

[0293] -etc.

[0294] All of the above have driven research into 6G network architecture.

[0295] The proposed (X-centric) 6G network architecture is based on SBA (XaaS service) and is cloud-native.

[0296] Requirements for 6G system network architecture design:

[0297] The proposed 6G network architecture needs to support new 6G services that can be developed / deployed by third parties.

[0298] The proposed 6G network architecture needs to build a more open ecosystem, opening the door to third parties with technical capabilities.

[0299] The proposed 6G network architecture requires improved trust management. It enables controlled, anonymous interaction among multiple participants.

[0300] A framework (also known as a service framework) can meet the above requirements.

[0301] A service framework has been proposed that is expected to meet the aforementioned new requirements for 6G networks.

[0302] This disclosure proposes and describes topology management, including the establishment of logical connections between gateways (GWs), XaaS services and vertical industries, and the configuration of these GWs, etc.

[0303] The schemes described in this disclosure are applicable to future 6G networks and all legacy networks.

[0304] Figure 6A schematic diagram of a framework is shown, which includes three types of logical network elements in a BAS domain (or simply a domain) or management domain: C / M function, at least one control / management plane trustworthy GW (C / M-TW-GW), and at least one data plane trustworthy GW (Data-TW-GW). It should be noted that, although... Figure 6 One domain is shown, but the number of domains is not limited in this disclosure. The C / M function within the BAS domain is used to control and manage the topology of the BAS domain, such as the logical connection between XaaS services / vertical industries within such a domain and GW (including one or more C / M-TW-GWs and one or more Data-TW-GWs), and to control 6G devices / D-Users / customer access to the 6G system by managing C / M sessions and data sessions. Within the BAS domain, where XaaS services share the same C / M functionality, they possess their own C / M functional entity (used to implement the C / M functions of XaaS service modules) and data functional entity (used to implement the data processing functions of XaaS service modules). Vertical industries, also within the same BAS domain, similarly possess their own C / M functional entity and data functional entity. The C / M-TW-GW within the BAS domain, controlled by the C / M function, connects the XaaS services within the BAS domain and the C / M functional entities of vertical industries. This enables anonymous and secure C / M plane interactions between XaaS services, as well as between vertical industries, based on the XaaS service's authorization profile. Similarly, the Data-TW-GW within the BAS domain, also controlled by the C / M function, connects the XaaS services within the BAS domain and the data functional entities of vertical industries. This enables anonymous and secure data plane interactions between XaaS services, as well as between vertical industries, to manage guaranteed service performance.

[0305] The C / M functional entities of the aforementioned XaaS services perform control and management plane functions for network control and management, and also support signaling exchange of XaaS services on the C / M plane. Different C / M functional entities are connected through C / M-TW-GW to support anonymous and secure C / M plane interaction between XaaS services.

[0306] The data function entities of the aforementioned XaaS services can be processors that handle data plane traffic (such as the NET4AI entity used for model training), and also support data exchange between XaaS services on the data plane. Different data function entities are connected through Data-TW-GW to support anonymous and secure data plane interaction between XaaS services.

[0307] like Figure 6 As shown in the exemplary framework, the C / M function is communicatively connected to at least one C / M-TW-GW and / or at least one Data-TW-GW. The C / M function controls the operation of at least one C / M-TW-GW and / or at least one Data-TW-GW. The C / M-TW-GW can communicatively connect to and interact with an XaaS service within the BAS domain or a vertical industry's C / M function entity to provide C / M plane functionality when needed. Similarly, the Data-TW-GW can communicatively connect to and interact with an XaaS service within the BAS domain or a vertical industry's data function entity to provide data plane functionality when needed.

[0308] For the concept of XaaS services, please refer to [link / reference]. Figure 5 The relevant descriptions in the text will not be repeated here. The difference between XaaS services and vertical industries is that vertical industries are purely customers, requiring other XaaS services to support their operation, while XaaS services provide their capabilities to 6G customers. Vertical industries refer to enterprise or industry customers, which is different from personal wireless devices. Vertical industries can have their own dedicated network resources, or integrate their custom functions with network functions, and can have their own customers, etc. For example, vertical industries here can refer to a type of service that operates based on a network provided by operators, etc. Vertical industries themselves usually do not own this network, but can still provide services to users based on the network. Therefore, from the operator's perspective, this type of service can be regarded as a vertical industry. For example, some chat applications do not have their own network, but can still provide services to users. These chat applications can be regarded as vertical industries. Vertical industries can also have one or more of their own servers, as well as one or more C / M function entities and one or more data function entities. Therefore, in order for vertical industries to provide services to users, the C / M-TW-GW needs to be connected to the vertical industry's C / M function entity, and the Data-TW-GW needs to be connected to the vertical industry's data function entity. It should be noted that although the examples in the following description are illustrated in conjunction with C / M entities and data entities of XaaS services, these examples are equally applicable to C / M entities and data entities in vertical industries.

[0309] C / M functions, C / M-TW-GW, and Data-TW-GW within the same domain can be connected, for example, through internal interfaces. Different C / M-TW-GWs within the same domain can be connected, as can different Data-TW-GWs within the same domain. C / M-TW-GWs within the same domain can be connected to the C / M function entities of the XaaS service, and Data-TW-GWs within the same domain can be connected to the data function entities of the XaaS service.

[0310] In one possible implementation of this disclosure, the framework can span multiple BAS domains and may include multiple C / M functions, multiple C / M-TW-GWs, and multiple Data-TW-GWs within the multiple BAS domains. C / M functions in different BAS domains can be interconnected. Each C / M function is used to control and manage one or more C / M-TW-GWs and one or more Data-TW-GWs within the domain to which it belongs. Furthermore, a C / M-TW-GW within one BAS domain can be communicatively connected to C / M-TW-GWs in other BAS domains, and correspondingly, a Data-TW-GW within one BAS domain can be communicatively connected to Data-TW-GWs in other BAS domains.

[0311] The following will describe in detail the establishment of logical connections between XaaS services and vertical industry gateways and functional entities, as well as the configuration of these gateways, etc.

[0312] This disclosure provides one implementation of a configuration method for C / M-TW-GW. See reference for details. Figure 7 The configuration method may include the following steps.

[0313] S701, the first network element receives the first configuration file of the second network element.

[0314] Specifically, the first configuration file includes at least one of the reachable address of the second network element or the authorization configuration file of the second network element. The authorization configuration file is used to determine the consumer that the second network element can provide the first basic service. In one possible implementation, the first network element can be a C / M function as described above, and the second network element can be a C / M function entity of the first basic service (also known as XaaS service) within the BAS domain. The first basic service can be... Figure 5 The C / M function is used to control and manage the logical connection between the C / M function entity and the C / M-TW-GW (third network element) to be configured, and is also used to configure the C / M-TW-GW to be configured. For example, the reachable address of the second network element can be the reachable physical address of the second network element, such as the ID of the second network element, or other forms, as long as other network elements can access the second network element.

[0315] In one implementation of this disclosure, the authorization configuration file of the second network element includes the identifier of the first basic service and the identifier of the second network element; the authorization configuration file of the second network element also includes at least one of the following: the identifier of the second basic service provided by the consumer and the identifier of the network element of the second basic service (or the identifier of the provider of the second service, the provider ID of the second service); or determining the permission conditions of the consumer. The second basic service can also be... Figure 5This refers to any one of the XaaS services or any other possible XaaS services. By using the above information, it is easier to determine the consumer that the second network element can provide the first basic service to.

[0316] In one implementation of this disclosure, the authorization configuration file may include a consumer list. This consumer list includes one or more consumers that the second network element can provide the first basic service and is directly sent to the first network element. The first network element determines the consumer based on this consumer list. In another possible implementation, the authorization configuration file may include authorization conditions. Authorization conditions for determining which consumer can provide the first basic service are sent to the first network element. These authorization conditions may be related to the traffic load of the candidate consumer. When a candidate consumer meets the authorization conditions, the first network element determines that candidate consumer as the consumer. It should be noted that this example is for illustrative purposes only, and the embodiments of this disclosure do not limit the authorization conditions.

[0317] In one implementation of this disclosure, the first network element can establish a connection between the second network element and the third network element based on the reachable address of the second network element; the third network element is configured based on this connection and the authorization configuration file of the second network element.

[0318] In one implementation of this disclosure, the first network element receiving the first configuration file of the second network element includes: the first network element receiving a registration message from the second network element, wherein the registration message indicates the first configuration file. Specifically, the registration message is sent to the first network element through the second network element, and the first network element directly receives the registration message sent by the second network element or forwarded by another network element from the second network element, wherein the other network element is connected to the second network element.

[0319] In one implementation of this disclosure, the first network element receiving the first configuration file of the second network element includes: the first network element receiving a registration message from a first basic service, wherein the registration message indicates the first configuration file. Specifically, the registration message is sent to the first network element through the first basic service to which the second network element belongs.

[0320] In one implementation of this disclosure, the first network element receiving the first configuration file from the second network element includes: the first network element receiving the first configuration file forwarded by the third network element from the fifth network element, wherein the third network element is connected to the fifth network element; or the first network element receiving the first configuration file forwarded by the fourth network element from the fifth network element, wherein the fourth network element is connected to the fifth network element. For example, the fifth network element is a consortium network (CONET), or the fifth network element is deployed within the CONET, which stores the reachable address of the second network element and the authorized configuration file of the second network element. The CONET provides the capability that enables multiple partners to jointly provide 6G services. This capability is provided through consortium formation, mutual authentication and authorization between partners, and protocol negotiation regarding recording and tracing selected actions performed by partners, to ensure a trusted environment for the operation of the 6G system. In the latter implementation, the fourth network element can be another C / M-TW-GW located in the same BAS domain as the third network element. The fourth network element first receives the first configuration file from the fifth network element and then sends the received first configuration file to the first network element. It should be noted that if a fourth network element needs to be configured, its configuration process is the same as that of the third network element described in the embodiments of this disclosure.

[0321] When the first configuration file comes from the fifth network element or the first basic service, the first configuration file can be the XaaS service deployment configuration file (also known as the deployment configuration file of the first basic service) and / or the XaaS service authorization configuration file.

[0322] The XaaS service deployment configuration file may include the following information: the XaaS service ID (referring to the ID of the first basic service, also known as the XaaS service ID), the provider ID of the XaaS service provider (referring to the ID of a provider that provides the first basic service within the BAS domain and has one or more entities, also known as the provider ID, where the provider has a C / M functional entity within the BAS domain, i.e., the aforementioned second network element), the ID of the C / M functional entity of the XaaS service located in the same BAS domain as the first network element (referring to the ID of the second network element of the first basic service, also known as the C / M functional entity ID), the reachable (physical) address of the C / M functional entity, and the ID of the data functional entity of the XaaS service located in the same BAS domain as the first network element (referring to the ID of the seventh network element of the first basic service described below, also known as the data functional entity ID), and the reachable physical address of the data functional entity. Therefore, the XaaS service deployment configuration file includes the reachable address of the second network element. Upon receiving the XaaS service deployment configuration file, the first network element can obtain the reachable address of the second network element to configure it.

[0323] The XaaS service authorization profile may include the following information: the XaaS service ID (referring to the ID of the first basic service, also known as the XaaS service ID), the provider ID of the XaaS service provider (referring to the ID of the provider that provides the first basic service within the BAS domain and has one or more entities, also known as the provider ID, where the provider has a C / M functional entity within the BAS domain, i.e., the aforementioned second network element), one or more IDs of one or more C / M functional entities of one or more consumer XaaS services authorized by the second network element to provide XaaS services within the same BAS domain as the first network element (also known as one or more authorized consumer IDs), and one or more IDs of authorized consumer XaaS services. The one or more IDs of one or more C / M functional entities of one or more consumer XaaS services authorized by the second network element to provide XaaS services can be used as the authorization profile of the second network element. After receiving the XaaS service authorization profile, the first network element can obtain the authorization profile of the second network element to configure the second network element.

[0324] Based on the above, the first network element can receive the first configuration file of the second network element in multiple ways, so the receiving method of the first configuration file can be flexibly set according to actual needs.

[0325] S702, the first network element determines the third network element based on the first configuration file of the second network element.

[0326] The first network element can control and manage multiple third network elements. After receiving the first configuration file of the second network element, the first network element can determine the third network element for the second network element. For example, the first network element can consider the specific information contained in the first configuration file and then select / choose a suitable third network element for the second network element.

[0327] In one implementation of this disclosure, when the first configuration file includes the reachable address of the second network element, the first network element can randomly select a third network element (such as a C / M-TW-GW) within the BAS domain, or select a C / M-TW-GW as the third network element based on its attributes (such as traffic load). For example, the C / M function selects the C / M-TW-GW with the lowest traffic load as the third network element. It should be understood that this selection condition is only for illustrative purposes, and this disclosure does not limit its scope. In this case, the information in the first configuration file sent to the determined third network element, also referred to as first information, is the reachable address of the second network element.

[0328] In one implementation of this disclosure, when the first configuration file includes the authorization configuration file of the second network element, the first network element can determine the consumers that the second network element can provide the first basic service to. Then, based on the authorization configuration file and the connection between the C / M function entity of the consumer in the BAS domain (i.e., the BAS domain where the second network element is located) and one or more C / M-TW-GWs, a C / M-TW-GW is selected as the third network element. For example, in addition to the first network element (i.e., the C / M function) and the second network element (i.e., the C / M function entity of the first basic service in the BAS domain), a BAS domain also contains 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, and C / M function entity B of consumer 2; the authorization configuration file indicates that the second network element can provide the first basic service to the C / M function entity A of consumer 1 and the consumer's C / M function entity B. Consumer 2's C / M functional entity B provides the first basic service. Consumer 1's C / M functional entity A is connected to C / M-TW-GW1 but not to C / M-TW-GW2. Consumer 2's C / M functional entity B is connected to C / M-TW-GW2 but not to C / M-TW-GW1. C / M-TW-GW3 and C / M-TW-GW4 are not connected to Consumer 1's C / M functional entity A or Consumer 2's C / M functional entity B. Then, based on the authorization configuration file and the connection between Consumer 1's C / M functional entity A and C / M-TW-GW1, C / M-TW-GW1 is selected as the third network element to be configured to support anonymous and secure interaction between Consumer 1's C / M functional entity A and the fourth network element; based on the authorization configuration file and the connection between Consumer 2's C / M functional entity B and C / M-TW-GW2, C / M-TW-GW2 is selected as the third network element to be configured to support anonymous and secure interaction between Consumer 2's C / M functional entity B and the fourth network element. In this case, the information in the first configuration file sent to C / M-TW-GW1 (also referred to as the first information for C / M-TW-GW1) is the authorization information related to Consumer 1's C / M functional entity A in the authorization configuration file of the second network element, and the information in the first configuration file sent to C / M-TW-GW2 (also referred to as the first information for C / M-TW-GW2) is the authorization information related to Consumer 2's C / M functional entity B in the authorization configuration file of the second network element.

[0329] In one implementation of this disclosure, the first network element can establish a connection between the second network element and the third network element based on the reachable address of the second network element; the third network element is configured based on this connection and the authorization configuration file of the second network element.

[0330] S703, the first network element sends the information in the first configuration file to the third network element based on the first configuration file; the third network element receives the information in the first configuration file from the first network element.

[0331] The information in the first configuration file can be used for the operation of the third network element. The operation of the third network element can include, for example, operations involving the third network element when establishing a connection between the third network element and the second network element, as well as the configuration of the third network element. The information in the first configuration file can be some or all of the information in the first configuration file.

[0332] This step can be viewed as a configuration step for the third network element, specifically including transmitting information from the first configuration file.

[0333] In one implementation of this disclosure, the first configuration file includes the reachable address of the second network element. The first network element receives the reachable address of the second network element, determines the third network element based on the reachable address of the second network element as described above, and sends the reachable address of the second network element to the third network element. 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 configuration file (which may also be referred to as the first information) is the reachable address of the second network element.

[0334] In one implementation of this disclosure, the first configuration file includes an authorization configuration file of a second network element. The first network element receives the authorization configuration file of the second network element, determines a third network element based on the authorization configuration file of the second network element as described above, and sends the authorization configuration file of the second network element to the third network element. The third network element receives the authorization configuration file of the second network element from the first network element. For example, as described in the example above, if a C / M-TW-GW (third network element) is selected based on the connection between the C / M-TW-GW and one or more C / M functional entities of one or more consumers, the information in the first configuration file sent to the C / M-TW-GW (also referred to as first information) will be the authorization information in the authorization configuration file related to one or more C / M functional entities of one or more consumers connected to the C / M-TW-GW.

[0335] When the first configuration file only includes the reachable address of the second network element, steps S701 to S703 are the process of establishing a connection between the second network element and the third network element. In this case, the fourth network element can be either the C / M function entity of the consumer-side XaaS service or the C / M function entity of the producer-side XaaS service. When the first configuration file only includes the authorization configuration file of the second network element, steps S701 to S703 are the configuration process performed by the third network element to support the second network element in providing services. When the first configuration file includes both the reachable address and the authorization configuration file of the second network element, steps S701 to S703 are the connection and configuration process for the third network element.

[0336] In one implementation of this disclosure, the first configuration file includes the reachable address of the second network element and the authorization configuration file of the second network element. The specific configuration of the third network element is as follows. Figure 8 A schematic flowchart is shown to configure a third network element based on a reachable address and an authorized configuration file. The configuration includes the following steps.

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

[0338] S802, the first network element determines the information in the first configuration file based on the authorized configuration file and the connection between the second and third network elements.

[0339] S803, the first network element sends the information in the first configuration file to the third network element.

[0340] For example, as described in the example above, if a C / M-TW-GW (third network element) is selected based on the connection between the C / M-TW-GW and one or more C / M functional entities of one or more consumers, the information sent to the first profile (also referred to as the first information) of the C / M-TW-GW will be the authorization information in the authorization profile related to one or more C / M functional entities of one or more consumers connected to the C / M-TW-GW.

[0341] In this way, the first network element does not need to send all information to the third network element, but only sends the information related to the operation of the third network element from the first configuration file, thus reducing system overhead. The operation of the third network element can be, for example, the operation involving the third network element when establishing a connection between the third network element and the second network element, as well as the configuration of the third network element.

[0342] In one implementation of this disclosure, the connection configuration in step S801 is as follows: Figure 9A As shown, the specific steps include:

[0343] (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 the reachable address of the third network element based on the reachable address of the second network element. The first network element has multiple options when configuring the connection, and can notify both parties establishing the connection of each other's reachable addresses.

[0344] (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 reachable address of the third network element is notified to the second network element, this connection can be initiated by the second network element; if the reachable address of the second network element is notified to the third network element, this connection can be initiated by the third network element.

[0345] (C) The third network element sends 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 indicates the connection between the second network element and the third network element. In one possible implementation, the first notification may include the type of connection and the identifier of the connection. The type of connection may be determined based on the protocol corresponding to the connection. For example, the type of connection may be a transport layer security (TLS) connection, which is not limited in this embodiment. The first notification may also include the identifier of the third network element so that the first network element can identify the third network element. Alternatively, the first notification may not include the identifier of the third network element. In this case, the first network element may identify the third network element from the first notification itself, for example, from the interface through which the first notification is received. After receiving the first notification, the first network element may record the connection between the second network element and the third network element.

[0346] After the connection between the second network element and the third network element is established, the third network element sends a first notification to the first network element indicating this connection, so that the first network element can better manage and control the second and third network elements.

[0347] In this way, by using the reachable address of the second network element, the first network element can determine a suitable third network element; a secure logical connection between this second network element and the third first network element can be established under the control of the first network element; by using the authorization configuration file, the first network element can determine the consumer of the first basic service (such as XaaS) that the second network element can provide, and therefore can select a suitable third network element for the second network element; then, the third first network element can be configured using the information from the first configuration file of the second network element, thus realizing the configuration of the third network element. In a possible implementation where both the second and third network elements are gateways (also known as trusted gateways or C / M-TW-GW), by introducing the anonymous service provided by the trusted gateway on the control / management (C / M) plane of the communication system (such as a 6G system), the trustworthiness of communication is improved from the perspective of the operation of the communication system.

[0348] In one implementation of this disclosure, after receiving the first notification, the first network element sends a first acknowledgment to the third network element, and the third network element receives the first acknowledgment from the first network element. The first acknowledgment indicates that the first notification has been received.

[0349] In one implementation of this disclosure, both the first notification and the first confirmation include an identifier for the first basic service. In another possible implementation of this disclosure, both the first notification and the first confirmation include a transaction number predefined for the first basic service. This allows for secure and reliable information exchange between the first network element and the third network element.

[0350] In one implementation of this disclosure, the first notification includes the identifier of the third network element, the identifier of the first basic service, the identifier 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 connection, the identifier of the connection, etc., and this disclosure does not limit this aspect.

[0351] The exemplary connection process between the second network element and the third network element is also as follows: Figure 9B As shown, the second network element is the C / M function entity of the XaaS service, and the third network element is the C / M-TW-GW in the NET4CON service. Combined with... Figure 9B This describes the establishment of a secure connection between the C / M-TW-GW within a BAS domain and the C / M functional entity of the XaaS service. The prerequisites for establishing this connection are: one or more C / M-TW-GWs within each BAS domain have been deployed; the C / M functional entity of the XaaS service that should connect to the C / M-TW-GW has been deployed and configured; and both the C / M-TW-GW and the C / M functional entity of the XaaS service have obtained the required certificates (applicable to certificate-based solutions).

[0352] The C / M function is implemented within the BAS domain / infrastructure domain. The C / M function requires the maintenance of a local BAS domain / infrastructure topology table. This table, for each C / M-TW-GW, stores information about the established secure logical connections between that C / M-TW-GW and the C / M function entity of the XaaS service. As described above, after the connection between the third network element (C / M-TW-GW) and the second network element (the C / M function entity of the XaaS service) is established, the first network element can be notified of this established connection. The first network element can store this information locally, for example, in the aforementioned local BAS domain / infrastructure topology table.

[0353] This connection can be established by either the C / M-TW-GW or the C / M function entity of the XaaS service. In the first case, the C / M function can notify the C / M-TW-GW of the reachable address of the newly deployed C / M function entity; that is, the C / M function notifies the C / M function entity of its reachable address based on the C / M function entity's reachable address. In the latter case, the newly deployed C / M function entity can be configured based on the C / M-TW-GW's reachable address; for example, the C / M function notifies the C / M function entity of the C / M-TW-GW's reachable address.

[0354] like Figure 9BAs shown, the connection between C / M-TW-GW and the C / M functional entity is established through an external interface (shown as 6G-C / M-1). This established connection is a transport layer security (TLS) connection. It should be noted that the TLS connection shown in the figure is merely exemplary; other types of connections may exist in actual applications.

[0355] After establishing the connection, the C / M-TW-GW sends message 2.1 (a specific example of the first notification mentioned above) to the C / M function, reporting that the TLS connection has been established. Message 2.1 includes the ID of the XaaS service to which the C / M function entity belongs and the ID of the C / M function entity. Then, in response to the received message 2.1, the C / M function updates the C / M plane topology table, which includes the ID of the C / M-TW-GW, the ID of the C / M function entity connected to the C / M-TW-GW, the ID of the XaaS service to which the C / M function entity belongs, and the connection type and parameters, such as a TLS connection and parameters related to the TLS connection. In response to the message 2.1 received from the C / M-TW-GW, the C / M function sends message 2.3 (a specific example of the first confirmation mentioned above) to the C / M-TW-GW to indicate receipt of message 2.1.

[0356] Figure 9B The steps of the connection process shown are listed in Table 1 below.

[0357] The symbol in the table " "" indicates interfaces and messages within the service.

[0358] Table 1

[0359]

[0360] It should be noted that message 2.3 may include other information indicating that message 2.1 has been received, but not the XaaS service ID. Furthermore, the specific content of the messages shown in the tables throughout this document is for illustrative purposes only and not as a limitation.

[0361] Figure 9C A schematic flowchart illustrating another exemplary connection process between a second network element and a third network element according to one or more embodiments of this disclosure is shown, which is consistent with... Figure 9B The difference lies in the fact that the C / M-TW-GW connected to the C / M function entity and the C / M-TW-GW that reports the established connection to the C / M function are not the same gateway. For example... Figure 9CAs shown, C / M-TW-GW2 connects to the C / M function entity of the XaaS service and forwards information related to the connection establishment to C / M-TW-GW1. Then, C / M-TW-GW1 reports the connection establishment to the C / M function via a first notification. The reporting process performed by C / M-TW-GW1 and its integration... Figure 9B The reporting process described is the same as that performed by the C / M-TW-GW.

[0362] In one implementation of this disclosure, the configuration method further includes: a first network element receiving a load report from a third network element, and the third network element reporting the load report to the first network element, wherein the load report indicates the load traffic processed by the third network element.

[0363] In one implementation of this disclosure, the timing of the third network element reporting the load report is configured or predefined by the first network element.

[0364] For example, the C / M function can receive load reports from each of the C / M-TW-GWs it controls and manages. Each C / M-TW-GW automatically or in response to instructions from the C / M function, or based on a certain timing, continuously or periodically reports its load traffic. Such timing includes, but is not limited to: reporting load traffic at regular time intervals, and continuously or periodically reporting load traffic when the load traffic is greater than or less than a preset value. As mentioned above, this timing can be configured by the first network element or predefined.

[0365] In one implementation of this disclosure, the configuration method further includes: a first network element determining another third network element based on a first configuration file of the second network element and a load report; the first network element configuring the connection between the second network element and the other third network element based on the reachable address of the second network element; and the first network element sending information from the first configuration file to the other third network element based on the first configuration file. Here, the information in the first configuration file is information about the operation of the other third network element, and the relevant descriptions of the information in the first configuration file for the third network element also apply to this information. The operation of the other third network element may include, for example, operations involving the other third network element when establishing a connection between the other third network element and the second network element, as well as the configuration of the other third network element. The information in the first configuration file of the other third network element can also be called second information, which may be, for example, the readable address of the second network element, or authorization information in the authorization configuration file related to one or more C / M functional entities of one or more consumers connected to the other third network element. The specific content of the second information may be similar to the specific content of the first information described above, but they may be for different third network elements.

[0366] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each third network element (such as C / M-TW-GW) it controls and manages, and promptly reconfigure the new C / M-TW-GW 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.

[0367] In one implementation of this disclosure, the configuration method further includes: the first network element releasing the connection between the second network element and the third network element.

[0368] 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 it does, the C / M function needs to determine another C / M-TW-GW to be configured based on the authorization configuration file of the C / M function entity. The configuration process of the other C / M-TW-GW (including determining the other third network element and sending the information for the other third network element in the first configuration file) is the same as the configuration process of the configured C / M-TW-GW, and can be referred to the relevant description above, which will not be repeated here. In one implementation, the first network element can maintain two connections simultaneously, namely the connection between the second network element and the third network element, and the connection between the second network element and another third network element. In another implementation, after the C / M function sends the configuration information corresponding to the other C / M-TW-GW (the information mentioned above in the first configuration file) to another C / M-TW-GW, the C / M function controls the previously configured C / M-TW-GW to disconnect from the C / M function entity.

[0369] In this way, the C / M function can obtain the load traffic of each C / M-TW-GW it controls and manages, and promptly reconfigure the new C / M-TW-GW 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.

[0370] In one implementation of this disclosure, after the first network element sends the information in the first configuration file to the third network element, the configuration method further includes: the third network element sending a second confirmation to the first network element, and the first network element receiving the second confirmation from the third network element, wherein the second confirmation indicates that the information in the first configuration file has been received.

[0371] The exemplary configuration process for the C / M-TW-GW (i.e., the aforementioned third network element) to be configured is also as follows: Figure 10A As shown.

[0372] The prerequisites for configuring the C / M-TW-GW are as follows: One or more C / M-TW-GWs within each BAS domain controlled and managed by the C / M function have been deployed; secure connections have been established between the deployed C / M-TW-GWs and between the C / M function and the C / M-TW-GW, and these connections can be established as follows: Figure 9A and Figure 9B The implementation shown describes a scenario where CONET has topology configuration files (also known as XaaS service deployment configuration files) for deploying XaaS services within each BAS domain; CONET also has mutual authorization configuration files for the XaaS services within each BAS domain. In this example, CONET and the C / M-TW-GW to be configured are located in the same BAS domain. It should be understood that the scheme disclosed herein is also applicable to situations where CONET and the C / M-TW-GW to be configured are located in different BAS domains.

[0373] The purpose of the configuration process is to configure the C / M-TW-GW to be configured based on the deployment configuration file and authorization configuration file within the BAS domain (entity level). The deployment configuration file for the XaaS service includes the following information: XaaS service ID, provider ID, the C / M plane entity ID and its reachable physical address, and the data plane entity ID and its reachable physical address. The authorization configuration file for the XaaS service includes the following information: XaaS service ID, provider ID, its authorized consumer IDs, and the IDs of the XaaS services provided by these consumers.

[0374] The C / M function creates an authorization table based on these configuration files. This authorization table consolidates the authorization configuration files of the XaaS service providers (who deploy their entities within the BAS domain).

[0375] It's important to note that the entity that triggers the configuration process can be any XaaS service, such as CONET and Task Manager. The process shown uses CONET as an example.

[0376] In this process example, the C / M function obtains the deployment configuration file and authorization configuration file of the XaaS service from CONET. In other cases, the deployment configuration file and authorization configuration file can be sent directly to the C / M function by the XaaS service (i.e., through registration with the C / M function by the XaaS service). Alternatively, after the logical connection is established, the deployment configuration file and authorization configuration file can be obtained by each deployed C / M function entity registering with the C / M function.

[0377] like Figure 10AAs shown, the C / M function controls and manages the C / M-TW-GW and Data-TW-GW within its respective BAS domain. There may be one or more C / M-TW-GWs, and CONET also belongs to this BAS domain. The connection between one of the C / M-TW-GWs and the C / M function is established through an internal interface, while the connection between the C / M-TW-GW and CONET is established through an external interface (shown as 6G-C / M-1 in the diagram). The C / M-TW-GW connected to CONET may or may not be the C / M-TW-GW to be configured.

[0378] CONET (a specific example of the aforementioned fifth network element) first sends message 1 (a specific example of the aforementioned first configuration file) to the C / M-TW-GW connected to CONET to trigger the configuration process. Message 1 includes the deployment configuration file and authorization configuration file for the XaaS service. The C / M-TW-GW connected to CONET is only used for pass-through and has no right to access the received configuration file. The C / M-TW-GW forwards the deployment configuration file and authorization configuration file for the XaaS service included in message 1 to the C / M function via message 2.1 (also a specific example of the aforementioned first configuration file). Then, the C / M function stores the deployment configuration file and authorization configuration file and combines the authorization configuration file to create an authorization table. This combination can be performed in any known manner, and this disclosure embodiment does not limit this. Next, the C / M function sends the deployment configuration file and authorization configuration file. Preferably, it sends the deployment configuration file and authorization configuration file specific to the C / M-TW-GW to be configured based on the stored configuration file. The C / M-TW-GW to be configured stores the deployment configuration file and authorization configuration file from the C / M function, and in response to message 2.3 (a specific example of the information in the first configuration file mentioned above), sends message 2.5 (a specific example of the first acknowledgment mentioned above) to the C / M function. Message 2.5 may include any information used in response to message 2.3, as long as the two messages correspond to each other and the C / M function receives acknowledgment of receipt 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 the C / M-TW-GW ID, the XaaS service entity deployment configuration file, and the XaaS service authorization table.

[0379] Figure 10A The steps of the configuration process shown are listed in Table 2 below.

[0380] The symbol in the table " "" indicates interfaces and messages within the service.

[0381] Table 2

[0382]

[0383] Figure 10B A schematic flowchart illustrating another exemplary configuration process for a third network element (i.e., C / M-TW-GW) according to one or more embodiments of this disclosure is shown, which is consistent with... Figure 10A The difference lies in the fact that the C / M-TW-GW connected to CONET and the C / M-TW-GW to be configured are different gateways. For example... Figure 10B As shown, C / M-TW-GW1 connects to CONET, receives configuration files from CONET, and then forwards the received configuration files to the C / M function. In other words, C / M-TW-GW1 is only used to forward configuration files but cannot access them. The C / M function receives configuration files from C / M-TW-GW1 and sends a configuration file specific to the C / M-TW-GW2 to be configured. The configuration process and integration of C / M-TW-GW2 are described below. Figure 10A The configuration process for C / M-TW-GW is the same as described.

[0384] This disclosure provides one implementation of a configuration method for Data-TW-GW. See reference... Figure 11 The configuration method may include the following steps.

[0385] S1101, the first network element receives the second configuration file.

[0386] Specifically, the second configuration file includes at least one of the task configuration file of the sixth network element or the reachable address of the seventh network element. The task configuration file is used to instruct the sixth network element to execute actions in the task, and the reachable address of the seventh network element is used to establish a connection between the sixth and seventh network elements. In one possible implementation, the first network element can be the C / M function as described above, the sixth network element can be the Data-TW-GW to be configured, and the seventh network element can be the data function entity of the XaaS service within the BAS domain, and can be the network element that executes actions immediately following the sixth network element when completing a task (e.g., triggered by the MM service). The C / M function is used to control and manage the logical connection between the data function entity and the Data-TW-GW to be configured, and is also used to configure the Data-TW-GW to be configured. Here, the reachable address of the seventh network element can be, for example, the reachable physical address of the seventh network element, such as the ID of the seventh network element, or other forms, as long as other network elements can access the seventh network element. The task configuration file can come from the MM service. The sixth network element is the network element that completes the task issued by the MM service. This completion may require multiple sixth network elements. In this case, the second configuration file (explained later; a specific example is the task session configuration configuration file) can include the task configuration files of all the sixth network elements required to complete the task. Each sixth network element can be configured in the same way. In this case, the task configuration file of each sixth network element is used to instruct that each sixth network element to perform actions in the task. The task is to achieve a specified goal, called the task objective, which includes providing packet data unit (PDU) connectivity and providing data processing. The task can include one or more actions, which can be, for example, AI training, AI inference, data preprocessing, data de-identification, data cleaning, data collection, data analysis, perception, etc.

[0387] In one implementation of this disclosure, when the second configuration file includes the reachable address of the seventh network element, the first network element receiving the reachable address of the seventh network element includes: the first network element receiving a registration message from the seventh network element, wherein the registration message indicates the reachable address of the seventh network element. Specifically, the registration message is sent to the first network element through the seventh network element, and the first network element directly receives the registration message sent by the seventh network element or forwarded by another network element from the seventh network element, wherein the other network element is connected to the seventh network element.

[0388] In one implementation of this disclosure, the second configuration file includes the reachable address of the seventh network element. The first network element receiving the reachable address of the seventh network element includes: the first network element receiving a registration message from the first basic service to which the seventh network element belongs, wherein the registration message indicates the reachable address of the seventh network element. Specifically, the registration message is sent to the first network element through the first basic service to which the seventh network element belongs.

[0389] In one implementation of this disclosure, the second configuration file includes the reachable address of the seventh network element. 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 the fifth network element, wherein the seventh network element is connected to the fifth network element. For example, the fifth network element is a CONET, which stores the reachable address of the sixth network element and the authorization configuration file of the sixth network element.

[0390] In addition, the reachable address of the seventh network element can also be obtained from the XaaS service deployment configuration file. Please refer to the relevant description in the above section describing the acquisition of the first configuration file, which will not be repeated here.

[0391] S1102, the first network element determines the sixth network element based on the second configuration file.

[0392] The first network element can control and manage multiple sixth network elements. After receiving the second configuration file, the first network element can determine the sixth network element based on the second configuration file. For example, the first network element can consider the specific information included in the second configuration file and then select / choose the appropriate sixth network element.

[0393] In one implementation of this disclosure, when the second configuration file includes the reachable address of the seventh network element, the first network element can randomly select a sixth network element (such as a Data-TW-GW) within the BAS domain, or select a Data-TW-GW as the sixth network element based on its attributes (such as traffic load). For example, the C / M function selects the Data-TW-GW with the lowest traffic load as the sixth network element. It should be understood that this selection condition is only for illustrative purposes, and the embodiments of this disclosure do not impose any limitations on it.

[0394] In one implementation of this disclosure, when the second configuration file includes the task configuration file of the sixth network element, the first network element can select a Data-TW-GW as the sixth network element based on the task configuration file and the connection between the data function entity (seventh network element) of the XaaS service located in the same BAS domain as the sixth network element and the Data-TW-GW. For example, in addition to the first network element and the seventh network element (i.e., the C / M function and the data function entity of the XaaS service in the BAS domain), there are multiple sixth network elements (gateways, i.e., Data-TW-GW1, Data-TW-GW2); the task configuration file indicates the gateway's execution of actions in the task, for example, through the actions to be executed by the gateway, the identifier of the next network element (seventh network element) that executes other actions after the sixth network element, and the identifier used to indicate the second action. Since the seventh network element is connected to Data-TW-GW1 but not to Data-TW-GW2, the first network element can select Data-TW-GW1 as the sixth network element based on the task configuration file and the connection between the data function entity of the XaaS service and Data-TW-GW1.

[0395] In one implementation of this disclosure, the first network element can establish a connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; the sixth network element is configured based on this connection and the task configuration file of the sixth network element.

[0396] S1103, the first network element sends the information in the second configuration file to the sixth network element based on the second configuration file; the sixth network element receives the information in the second configuration file from the first network element.

[0397] The information in the second configuration file can be used for the operation of the sixth network element. The operation of the sixth network element can include, for example, operations involving the sixth network element when establishing a connection between the sixth and seventh network elements, as well as the configuration of the sixth network element. The information in the second configuration file can be some or all of the information in the second configuration file.

[0398] This step can be viewed as a configuration step for the sixth network element, specifically including transmitting information from the second configuration file.

[0399] In one implementation of this disclosure, the second configuration file includes the reachable address of the seventh network element. The first network element receives the reachable address of the seventh network element, determines the sixth network element based on the reachable address of the seventh network element as described above, and sends the reachable address of the seventh network element to the sixth network element. 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 configuration file sent to the determined sixth network element can also be referred to as third information, which is the reachable address of the seventh network element.

[0400] In one implementation of this disclosure, the second configuration file includes the task configuration file of the sixth network element. The first network element receives the task configuration file of the sixth network element, determines the sixth network element based on the task configuration file of the sixth network element as described above, and sends the task configuration file of the sixth network element to the sixth network element. The sixth network element receives the task configuration file of the sixth network element from the first network element. In this case, the information in the second configuration file (also referred to as the third information) is the task configuration file of the sixth network element. As described above, when the second configuration file includes the task configuration files of all the sixth network elements required to complete the task, the information in the second configuration file sent to each sixth network element (also referred to as the third information) will be the task configuration file of that sixth network element.

[0401] When the second configuration file only includes the reachable address of the seventh network element, steps S1101 to S1103 are the process of establishing a connection between the sixth and seventh network elements. In this case, the seventh network element can be a data function entity of the consumer-side XaaS service or a data function entity of the producer-side XaaS service. When the second configuration file only includes the task configuration file of the sixth network element, steps S1101 to S1103 are the configuration process of the sixth network element. When the second configuration file includes both the reachable address of the seventh network element and the task configuration file of the sixth network element, steps S1101 to S1103 are the connection and configuration process of the sixth network element to support the completion of tasks related to both the sixth and seventh network elements.

[0402] In this way, by using the reachable address of the seventh network element, the first network element can determine the appropriate sixth network element; a secure logical connection between the sixth network element and this first network element can be established under the control of the first network element; by using the task configuration file, the appropriate sixth network element can be selected to execute the actions indicated in the task configuration file; and then the sixth network element can be configured using the information from the second configuration file of the seventh network element, thus realizing the configuration of the sixth network element.

[0403] In one implementation of this disclosure, the information in the second configuration file includes an identifier indicating the first action to be performed by the sixth network element, an identifier indicating the next network element to perform the second action after the sixth network element, and an identifier indicating the second action. The next network element can be the seventh network element, i.e., a data function entity belonging to the next XaaS service. As described above, in an implementation where the second configuration file simultaneously includes the reachable address of the seventh network element and the task configuration file of the sixth network element, the seventh network element can be the next network element.

[0404] In one implementation of this disclosure, the information in the second configuration file includes an identifier indicating the first action to be performed by the sixth network element, the quality of service (QoS) parameters of the sixth network element, an identifier indicating the next network element to perform the second action after the sixth network element, and an identifier indicating the connection between the sixth network element and the next network element. As described above, in an implementation where the second configuration file simultaneously includes the reachable address of the seventh network element and the task configuration file of the sixth network element, the seventh network element can be the next network element. For example, the first action can be a decryption or encryption operation when transmitting data packets from a data function entity of an XaaS service to a data function entity of another XaaS service (the seventh network element), and the second action can be an action by which the seventh network element provides a corresponding service, such as data collection in a NET4DAM service scenario. Alternatively, the first action can be an operation to convert the data format of data packets when transmitting data packets from a data function entity of an XaaS service to a data function entity of another XaaS service (the seventh network element).

[0405] In one implementation of this disclosure, the information in the second configuration file includes an identifier for indicating the QoS parameters of the sixth network element.

[0406] In one implementation of this disclosure, the second configuration file includes the reachable address of the seventh network element and the task configuration file of the sixth network element. In this case, the seventh network element can be the next network element, or it can be the next network element that performs an action after the sixth network element to complete the task. The specific configuration of the sixth network element is as follows.

[0407] Figure 12 A schematic flowchart is shown to configure the sixth network element based on the reachable address and task configuration file. The configuration includes the following steps.

[0408] S1201, the first network element configures the connection between the sixth and seventh network elements based on the reachable address of the seventh network element.

[0409] S1202, the first network element determines the information in the second configuration file based on the second configuration file and the connection between the sixth and seventh network elements.

[0410] S1203, the first network element sends the information in the second configuration file to the sixth network element.

[0411] The information in the second configuration file is the task configuration file of the determined sixth network element. As mentioned above, if the second configuration file includes the task configuration files of all the sixth network elements required to complete the task, the information in the second configuration file sent to each sixth network element (also referred to as the third information) will be the task configuration file of that sixth network element.

[0412] In this way, the first network element does not need to send all the information to the sixth network element, but only sends the information related to the operation of the sixth network element in the second configuration file, thus reducing system overhead.

[0413] In one implementation of this disclosure, the connection is configured in step S1201 as follows: Figure 13A As shown, the specific steps include:

[0414] (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 the reachable address of the sixth network element based on the reachable address of the seventh network element. The first network element has multiple options when configuring the connection, including notifying both parties establishing the connection of each other's reachable addresses.

[0415] (B) The sixth network element establishes a connection between itself and the seventh network element based on the reachable address of the seventh network element. If the reachable address of the seventh network element is notified to the sixth network element, this connection can be initiated by the sixth network element; if the reachable address of the sixth network element is notified to the seventh network element, this connection can be initiated by the seventh network element.

[0416] (C) The sixth network element sends 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 indicates the connection between the sixth network element and the seventh network element. In one possible implementation, the second notification may include the type of connection and the identifier of the connection. The second notification may also include the identifier of the sixth network element so that the first network element can identify the sixth network element. Alternatively, the second notification may not include the identifier of the sixth network element. In this case, the first network element can identify the sixth network element from the second notification itself, for example, from the interface through which the second notification is received. After receiving the second notification, the first network element may record the connection between the sixth network element and the seventh network element.

[0417] After the connection between the sixth network element and the seventh network element is established, the sixth network element sends a second notification to the first network element indicating this connection, so that the first network element can better manage and control the sixth network element and the seventh network element.

[0418] In this way, by using the reachable address of the seventh network element, the first network element can determine the appropriate sixth network element; a secure logical connection between the sixth network element and this first network element can be established under the control of the first network element; by using the task configuration file, an appropriate sixth network element can be selected to execute the actions indicated in the task configuration file; and then the sixth network element can be configured using the information from the second configuration file of the seventh network element, thus realizing the configuration of the sixth network element.

[0419] In one implementation of this disclosure, after receiving the second notification, the first network element sends a third confirmation to the sixth network element, and the sixth network element receives the third confirmation from the first network element, wherein the third confirmation indicates that the second notification has been received.

[0420] In one implementation of this disclosure, both the second notification and the third confirmation include the identifier of the first basic service to which the seventh network element belongs. In another possible implementation of this disclosure, both the second notification and the third confirmation include a transaction number predefined for the first basic service. This allows for secure and reliable information exchange between the first network element and the sixth network element.

[0421] In one implementation of this disclosure, the second notification includes the identifier of the sixth network element, the identifier of the first basic service to which the seventh network element belongs, the identifier of the seventh network element, and the identifier of the connection between the sixth and seventh network elements. Here, the connection description information may include the connection type, the connection identifier, etc., and this disclosure does not limit this aspect.

[0422] The exemplary connection process between the sixth network element and the seventh network element is also as follows: Figure 13B As shown, the sixth network element is the Data-TW-GW of the XaaS service, and the seventh network element is the data function entity of the XaaS service. Combined with... Figure 13B This describes the establishment of a secure connection between the Data-TW-GW within a BAS domain and the data function entity of the XaaS service. The prerequisites for establishing this connection are: one or more Data-TW-GWs have been deployed within each BAS domain; the XaaS service data function entity that should connect to the Data-TW-GW has been deployed; and both the Data-TW-GW and the XaaS service data function entity have obtained the required certificates (applicable to certificate-based solutions).

[0423] The C / M function is implemented within the BAS domain / infrastructure domain. The C / M function requires maintaining a local BAS domain / infrastructure topology table. This table, for each Data-TW-GW, stores information about the established secure logical connections between that Data-TW-GW and the data function entities of the XaaS service. As described above, after the connection between the sixth network element (Data-TW-GW) and the seventh network element (the data function entity of the XaaS service) is established, the first network element can be notified of this established connection. The first network element can store this information locally, for example, in the aforementioned local BAS domain / infrastructure topology table.

[0424] This connection can be established by either the Data-TW-GW or the data function entity of the XaaS service. In the first case, the C / M function can notify the Data-TW-GW of the reachable address of the newly deployed data function entity; that is, the C / M function notifies the Data-TW-GW of the reachable address of the data function entity. In the latter case, the newly deployed data function entity can be configured based on the reachable address of the Data-TW-GW; for example, the C / M function notifies the data function entity of the reachable address of the Data-TW-GW.

[0425] like Figure 13B As shown, the connection between the Data-TW-GW and the data function entity is established through an external interface (6G-C / M-1 in the diagram). This established connection is a transport layer security (TLS) connection. It should be noted that the TLS connection shown in the diagram is merely exemplary; other types of connections may exist in actual applications.

[0426] After establishing the connection, the Data-TW-GW sends message 2.1 (a specific example of the second notification mentioned above) to the C / M function, reporting that the TLS connection has been established. Message 2.1 includes the ID of the XaaS service to which the data function entity belongs and the ID of the data function entity. Then, in response to the received message 2.1, the C / M function updates the data plane topology table, which includes the ID of the Data-TW-GW, the ID of the data function entity connected to the Data-TW-GW, the ID of the XaaS service to which the data function entity belongs, and the connection type and parameters, such as a TLS connection and parameters related to the TLS connection. In response to the message 2.1 received from the Data-TW-GW, the C / M function sends message 2.3 (a specific example of the third confirmation mentioned above) to the Data-TW-GW to indicate receipt of message 2.1.

[0427] Figure 13B The steps of the connection process shown are listed in Table 3 below.

[0428] The symbol in the table " "" indicates interfaces and messages within the service.

[0429] Table 3

[0430]

[0431] It should be noted that message 2.3 may include other information indicating that message 2.1 has been received, but does not include the XaaS service ID.

[0432] Figure 13C A schematic flowchart illustrating another exemplary connection process between a sixth network element and a seventh network element according to one or more embodiments of this disclosure is shown, which is consistent with... Figure 13B The difference lies in the fact that the Data-TW-GW connected to the data function entity and the Data-TW-GW that reports the established connection to the C / M function are not the same gateway. For example... Figure 13C As shown, Data-TW-GW2 connects to the data function entity of the XaaS service and forwards information related to the connection establishment to Data-TW-GW1. Then, Data-TW-GW1 reports the connection establishment to the C / M function via a second notification. The reporting process performed by Data-TW-GW1 and its integration... Figure 13B The reporting process described is the same as that performed by Data-TW-GW.

[0433] In one implementation of this 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 the load report to the first network element, wherein the load report indicates the load traffic processed by the sixth network element.

[0434] In one implementation of this disclosure, the timing of the sixth network element reporting the load report is configured by the first network element or predefined.

[0435] For example, the C / M function can receive load reports from each of the Data-TW-GWs it controls and manages. Each Data-TW-GW automatically or in response to instructions from the C / M function, or based on certain timings, continuously or periodically reports its load traffic. Such timings include, but are not limited to: reporting load traffic at regular time intervals, and continuously or periodically reporting load traffic when the load traffic is greater than or less than a preset value. As mentioned above, this timing can be configured by the first network element or predefined.

[0436] Since the timing of load reporting can be configured by the first network element or predefined, load reporting can be flexibly performed according to actual applications.

[0437] In one implementation of this disclosure, the configuration method further includes: a first network element determining another sixth network element based on a second configuration file and a load report; the first network element configuring the connection between the seventh network element and the other sixth network element based on the reachable address of the seventh network element; and the first network element sending information from the second configuration file to the other sixth network element based on the second configuration file. Here, the information in the second configuration file for the other sixth network element can also be referred to as fourth information. This information can be, for example, the readable address of the seventh network element, or a task configuration file related to one or more data function entities of one or more consumers connected to the other sixth network element. The information in the second configuration file is information about the operation of the other sixth network element. The relevant descriptions of the information in the second configuration file for the sixth network element also apply to this information. That is, the specific content of the fourth information can be similar to the specific content of the third information described above, except that they can be for different sixth network elements.

[0438] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each sixth network element (such as Data-TW-GW) it controls and manages, and promptly reconfigure the new Data-TW-GW 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.

[0439] In one implementation of this disclosure, the configuration method further includes: the first network element releasing the connection between the sixth network element and the seventh network element.

[0440] 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 it does, the C / M function needs to determine another Data-TW-GW to be configured based on the task configuration file of the data function entity. The configuration process of the other Data-TW-GW (including determining the other sixth network element and sending the information for the other sixth network element in the second configuration file) is the same as the configuration process of the configured Data-TW-GW, which can be referred to in the relevant description above and will not be repeated here. In one implementation, the first network element can maintain two connections simultaneously, namely the connection between the sixth network element and the seventh network element, and the connection between the other sixth network element and the seventh network element. In another implementation, after the C / M function sends the configuration information corresponding to the other Data-TW-GW (the above information in the second configuration file) to the other Data-TW-GW, the C / M function controls the previously configured Data-TW-GW to disconnect from the data function entity.

[0441] In this way, the C / M function can obtain the load traffic of each Data-TW-GW it controls and manages, and promptly reconfigure the new Data-TW-GW 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.

[0442] In one implementation of this disclosure, after the first network element sends the information in the second configuration file to the sixth network element, the configuration method further includes: the sixth network element sending a fourth confirmation to the first network element, and the first network element receiving the fourth confirmation from the sixth network element, wherein the fourth confirmation indicates that the information in the second configuration file has been received.

[0443] In one implementation of this disclosure, both the information in the second configuration file and the fourth confirmation include an identifier used to indicate the task.

[0444] The exemplary configuration process for the Data-TW-GW (i.e., the sixth network element mentioned above) to be configured is also as follows: Figure 14A As shown. The purpose of this configuration process is to configure the Data-TW-GW to support task sessions, including 5G PDU sessions.

[0445] The prerequisite for configuring the Data-TW-GW is that one or more Data-TW-GWs within the BAS domain have been deployed. This process is executed each time a task service is provided.

[0446] like Figure 14A As shown, the C / M function controls and manages the C / M-TW-GW and Data-TW-GW within its BAS domain; there may be one or more Data-TW-GWs, wherein the connection between the Data-TW-GW or C / M-TW-GW and the C / M function is established through an internal interface; the entity that triggers the configuration process can be any type of triggering entity, such as a mission management (MM) entity; the connection between the C / M-TW-GW and the triggering entity is established through an external interface (shown as 6G-C / M-1 in the diagram).

[0447] The triggering entity creates a task session configuration file (a specific example of the second configuration file mentioned above) related to the network element within the BAS domain where the C / M function resides. The triggering entity first sends message 1 to the C / M-TW-GW connected to it to trigger the configuration process. Message 1 includes the task session configuration file related to the network element within the BAS domain. The C / M-TW-GW connected to the triggering entity is only used for pass-through and has no access to the received configuration file.

[0448] The C / M-TW-GW forwards the task session configuration file included in Message 1 to the C / M function via Message 2.1. The C / M function then stores the task session configuration file, identifies the Data-TW-GWs involved in the task operations, and creates a task session table for each identified Data-TW-GW. Next, the C / M function sends the corresponding task session table (a specific example of the information in the second configuration file mentioned above) to each Data-TW-GW using Message 2.3. The Data-TW-GW receives and stores its own task session table, and then sends Message 2.5 to the C / M function in response to Message 2.3 (a specific example of the fourth acknowledgment mentioned above). Message 2.5 can include any information used to respond to Message 2.3, as long as the two messages correspond and the C / M function receives confirmation of receipt of Message 2.3, such as the task session ID. After receiving message 2.5 from the Data-TW-GW, the C / M function creates a Data-TW-GW configuration record for each supporting Data-TW-GW, including the task session ID and a task session table, and sends message 2.7, including the task session ID, 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 responds to message 1 by sending message 3, including the task session ID, to the triggering entity.

[0449] Figure 14A The steps of the configuration process shown are listed in Table 4 below.

[0450] The symbol in the table " "" indicates interfaces and messages within the service.

[0451] Table 4

[0452]

[0453] The task session configuration profile can include information (for each Data-TW-GW involved):

[0454] Option 1:

[0455] • Route destination

[0456] For each pair of [task session ID, action ID]: the entity ID and action ID of the next XaaS service (the ID of the action that the next XaaS service will perform).

[0457] •QoS Guarantee

[0458] For each pair of [task ID, action ID]: QoS parameters (or QoS ID)

[0459] Option 2:

[0460] • For each connection ID: QoS parameters (or QoS ID), the entity ID of the next XaaS service, and the connection ID of the next XaaS service.

[0461] Figure 14B A schematic flowchart illustrating another exemplary configuration process for a sixth network element (i.e., Data-TW-GW) according to one or more embodiments of this disclosure is shown, which is consistent with... Figure 14A The difference lies in the fact that the C / M-TW-GW connected to the triggering entity and the C / M-TW-GW connected to the C / M function are not the same gateway. For example... Figure 14B As shown, C / M-TW-GW2 connects to the triggering entity and receives the configuration file from it. Then, it sends the received configuration file to the C / M function via C / M-TW-GW1. The C / M function receives the configuration file from C / M-TW-GW1 and sends messages to C / M-TW-GW2 via C / M-TW-GW1. The configuration process and integration of Data-TW-GW are described below. Figure 14A The configuration process for Data-TW-GW is the same as described.

[0462] The following will describe an example of a product related to the configuration method.

[0463] Figure 15 This is a schematic diagram of the configuration device according to an embodiment of the present disclosure. Figure 15 As shown, the configuration device 1500 may include:

[0464] The receiving module 1501 is used to receive a first configuration file of the second network element, wherein the first configuration file includes at least one of the reachable address of the second network element or the authorization configuration file of the second network element, and the authorization configuration file is used to determine the consumer that the second network element can provide the first basic service.

[0465] Module 1502 is used to determine a third network element based on a first configuration file of the second network element; and

[0466] The sending module 1503 is used to send information in the first configuration file to the third network element based on the first configuration file.

[0467] In one possible implementation of the fifth aspect, the receiving module 1501 is used for:

[0468] The registration message is received from the second network element, where the registration message indicates the first configuration file.

[0469] In one possible implementation, the receiving module 1501 is used for:

[0470] Receive a registration message from the first basic service, where the registration message indicates the first configuration file.

[0471] In one possible implementation, the receiving module 1501 is used for:

[0472] Receive the first configuration file forwarded by the third network element from the fifth network element, wherein the third network element is connected to the fifth network element; or

[0473] The fourth network element receives the first configuration file forwarded from the fifth network element, wherein the fourth network element is connected to the fifth network element.

[0474] In one possible implementation, the first configuration file includes the reachable address of the second network element and the authorization configuration file of the second network element;

[0475] The sending module 1503 is used for:

[0476] Configure the connection between the second network element and the third network element based on the reachable address of the second network element;

[0477] Based on the authorized configuration file and the connection between the second network element and the third network element, the information in the first configuration file is determined;

[0478] Send the information from the first configuration file to the third network element.

[0479] In one possible implementation, the sending module 1503 is used for:

[0480] The third network element is notified of the reachable address of the second network element.

[0481] In one possible implementation, the sending module 1503 is used for:

[0482] The reachable address of the third network element is notified to the second network element based on the reachable address of the second network element.

[0483] In one possible implementation, the receiving module 1501 is further configured to:

[0484] The first notification is received from the third network element, wherein the first notification indicates the connection between the second network element and the third network element.

[0485] In one possible implementation, the sending module 1503 is further configured to:

[0486] Send a first confirmation to the third network element, wherein the first confirmation indicates that the first notification has been received.

[0487] In one possible implementation, both the first notification and the first confirmation include the identifier of the first basic service.

[0488] In one possible implementation, the first notification includes the identifier of the third network element, the identifier of the first basic service, the identifier of the second network element, and connection description information of the connection between the second network element and the third network element.

[0489] In one possible implementation, the receiving module 1501 is further configured to:

[0490] Receive load reports from the third network element, where the load reports indicate the load traffic processed by the third network element.

[0491] In one possible implementation,

[0492] The determination module 1502 is also used to determine another third network element based on the first configuration file and load report of the second network element;

[0493] The sending module 1503 is also used for:

[0494] Configure the connection between the second network element and another third network element based on the reachable address of the second network element;

[0495] The information in the first configuration file is sent to another third network element based on the first configuration file.

[0496] In one possible implementation, the above-mentioned device further includes:

[0497] The release module is used to release the connection between the second network element and the third network element.

[0498] In one possible implementation, the timing for the third network element to report load is configured by the first network element or predefined.

[0499] In one possible implementation, the receiving module 1501 is further configured to receive a second confirmation from a third network element, wherein the second confirmation indicates that information in the first configuration file has been received.

[0500] In one possible implementation, the authorization configuration file of the second network element includes the identifier of the first basic service and the identifier of the second network element;

[0501] The authorization configuration file for the second network element also includes at least one of the following:

[0502] The identifier of the second basic service provided by the consumer and the identifier of the network element of the second basic service; or

[0503] Determine the consumer's permissions.

[0504] Figure 16 This is a schematic diagram of the configuration device according to an embodiment of the present disclosure. Figure 16 As shown, the configuration device 1600 may include:

[0505] The receiving module 1601 is used to receive information from the first network element, wherein the information includes a first configuration file of the second network element received by the first network element. The first configuration file includes at least one of the reachable address of the second network element or the authorization configuration file of the second network element. The authorization configuration file is used to determine the consumer that the second network element can provide the first basic service.

[0506] In one possible implementation, the first configuration file is indicated by a registration message received by the first network element from the second network element or the first basic service.

[0507] In one possible implementation,

[0508] The receiving module 1601 is also used to receive the first configuration file from the fifth network element, wherein the third network element is connected to the fifth network element;

[0509] The aforementioned device further includes: a first transmitting module, used to forward the first configuration file to the first network element.

[0510] In one possible implementation, the first configuration file includes the reachable address of the second network element and the authorization configuration file of the second network element;

[0511] The above-mentioned device also includes: a building module, used for:

[0512] A connection between the second network element and the third network element is established based on the reachable address of the second network element;

[0513] The aforementioned device further includes: a second transmitting module, configured to send a first notification to the first network element, wherein the first notification indicates the connection between the second network element and the third network element.

[0514] In one possible implementation, the receiving module 1601 is further configured to:

[0515] The first acknowledgment is received from the first network element, wherein the first acknowledgment indicates that the first notification has been received.

[0516] In one possible implementation, both the first notification and the first confirmation include the identifier of the first basic service.

[0517] In one possible implementation, the first notification includes the identifier of the third network element, the identifier of the first basic service, the identifier of the second network element, and connection description information of the connection between the second network element and the third network element.

[0518] In one possible implementation, the above-mentioned device further includes: a reporting module, used for:

[0519] A load report is reported to the first network element, wherein the load report indicates the load traffic processed by the third network element.

[0520] In one possible implementation, the above-mentioned apparatus further includes: a third transmitting module, used for:

[0521] A second confirmation is sent to the first network element, wherein the second confirmation indicates that information in the first configuration file has been received.

[0522] Figure 17 This is a schematic diagram of the configuration device according to an embodiment of the present disclosure. Figure 17 As shown, the configuration device 1700 may include:

[0523] The receiving module 1701 is used to receive a second configuration file, wherein the second configuration file includes at least one of the task configuration file of the sixth network element or the reachable address of the seventh network element. The task configuration file is used to instruct the sixth network element to execute the action in the task, and the reachable address of the seventh network element is used to establish a connection between the sixth network element and the seventh network element.

[0524] Module 1702 is used to determine the sixth network element based on the second configuration file; and

[0525] The sending module 1703 is used to send information in the second configuration file to the sixth network element based on the second configuration file.

[0526] In one possible implementation, the second configuration file includes the reachable address of the seventh network element;

[0527] Receiver module 1701 is used for:

[0528] The registration message is received from the seventh network element, where the registration message indicates the reachable address of the seventh network element.

[0529] In one possible implementation, the second configuration file includes the reachable address of the seventh network element;

[0530] Receiver module 1701 is used for:

[0531] The seventh network element receives a registration message from the first basic service to which it belongs. The registration message indicates the reachable address of the seventh network element.

[0532] In one possible implementation, the second configuration file includes the reachable address of the seventh network element;

[0533] Receiver module 1701 is used for:

[0534] The seventh network element receives the reachable address of the seventh network element forwarded from the fifth network element, where the seventh network element is connected to the fifth network element.

[0535] In one possible implementation, the second configuration file includes the reachable address of the seventh network element and the task configuration file of the sixth network element;

[0536] The sending module 1703 is used for:

[0537] Configure the connection between the sixth and seventh network elements based on the reachable address of the seventh network element;

[0538] Based on the second configuration file and the connection between the sixth and seventh network elements, the information in the second configuration file is determined; and

[0539] Send the information from the second configuration file to the sixth network element.

[0540] In one possible implementation, the sending module 1703 is used for:

[0541] The sixth network element is notified of the reachable address of the seventh network element.

[0542] In one possible implementation, the sending module 1703 is used for:

[0543] The reachable address of the sixth network element is notified to the seventh network element based on the reachable address of the seventh network element.

[0544] In one possible implementation, the receiving module 1701 is further configured to:

[0545] The sixth network element receives a second notification, which indicates the connection between the sixth network element and the seventh network element.

[0546] In one possible implementation, the sending module 1703 is further configured to:

[0547] A third confirmation is sent to the sixth network element, wherein the third confirmation indicates that the second notification has been received.

[0548] In one possible implementation, both the second notification and the third confirmation include the identifier of the first basic service to which the seventh network element belongs.

[0549] In one possible implementation of the seventh aspect, the second notification includes the identifier of the sixth network element, the identifier of the first basic service to which the seventh network element belongs, the identifier of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

[0550] In one possible implementation, the receiving module 1701 is further configured to:

[0551] The fourth confirmation is received from the sixth network element, wherein the fourth confirmation indicates that information in the second configuration file has been received.

[0552] In one possible implementation, both the information in the second configuration file and the fourth confirmation include an identifier used to indicate the task.

[0553] In one possible implementation, the information in the second configuration file includes an identifier for indicating the first action to be performed by the sixth network element, an identifier for indicating the next network element to perform the second action after the sixth network element, and an identifier for indicating the second action.

[0554] In one possible implementation, the information in the second configuration file includes an identifier for indicating the first action to be performed by the sixth network element, the quality of service (QoS) parameters of the sixth network element, an identifier for indicating the next network element to perform the second action after the sixth network element, and an identifier for indicating the connection between the sixth network element and the next network element.

[0555] In one possible implementation, the information in the second configuration file includes an identifier for indicating the QoS parameters of the sixth network element.

[0556] In one possible implementation, the receiving module 1701 is further configured to:

[0557] Receive load reports from the sixth network element, where the load reports indicate the load traffic processed by the sixth network element.

[0558] In one possible implementation, the determining module 1702 is also used to determine another sixth network element based on the second configuration file and the load report;

[0559] The sending module 1703 is also used for:

[0560] Configure the connection between the seventh network element and another sixth network element based on the reachable address of the seventh network element;

[0561] The information in the second configuration file is sent to another sixth network element based on the second configuration file.

[0562] In one possible implementation, the above-mentioned device further includes:

[0563] The release module is used to release the connection between the sixth network element and the seventh network element.

[0564] In one possible implementation, the timing for the third network element to report load is configured by the first network element or predefined.

[0565] Figure 18 This is a schematic diagram of the configuration device according to an embodiment of the present disclosure. Figure 18 As shown, the configuration device 1800 may include:

[0566] The receiving module 1801 is used to receive information from the first network element, wherein the information is included in a second configuration file received by the first network element. The second configuration file includes at least one of a task configuration file of the sixth network element or a reachable address of the seventh network element. The task configuration file is used to instruct the sixth network element to perform actions in a task, and the reachable address of the seventh network element is used to establish a connection between the sixth network element and the seventh network element.

[0567] In one possible implementation, the second configuration file includes the reachable address of the seventh network element;

[0568] The second configuration file is indicated by the registration message received by the first network element from the seventh network element or the first basic service.

[0569] In one possible implementation, the second configuration file includes the reachable address of the seventh network element;

[0570] The aforementioned device also includes an establishment module and a first transmission module:

[0571] Establish a module to establish a connection between the sixth and seventh network elements based on the reachable address of the seventh network element;

[0572] The first sending module is used to send a second notification to the first network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element.

[0573] In one possible implementation, the receiving module 1801 is further configured to:

[0574] The third confirmation is received from the first network element, wherein the third confirmation indicates that the second notification has been received.

[0575] In one possible implementation, both the second notification and the third confirmation include the identifier of the first basic service to which the seventh network element belongs.

[0576] In one possible implementation, the second notification includes the identifier of the sixth network element, the identifier of the first basic service to which the seventh network element belongs, the identifier of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

[0577] In one possible implementation, the above-mentioned apparatus further includes: a second transmitting module, configured to:

[0578] A fourth acknowledgment is sent to the first network element, wherein the fourth acknowledgment indicates that information in the second configuration file has been received.

[0579] In one possible implementation, both the information in the second configuration file and the fourth confirmation include an identifier used to indicate the task.

[0580] In one possible implementation, the above-mentioned device further includes: a reporting module, used for:

[0581] A load report is reported to the first network element, wherein the load report indicates the load traffic processed by the sixth network element.

[0582] One embodiment of this disclosure provides a first network element, including processing circuitry for performing any of the above-described configuration methods.

[0583] One embodiment of this disclosure provides a third network element, including processing circuitry for performing any of the above-described configuration methods.

[0584] One embodiment of this disclosure provides a first network element, including processing circuitry for performing any of the above-described configuration methods.

[0585] One embodiment of this disclosure provides a sixth network element, including processing circuitry for performing any of the above-described configuration methods.

[0586] One embodiment of this disclosure provides a computer-readable medium storing computer-executable instructions, wherein, when executed by a processor, these computer-executable instructions cause the processor to perform any of the above-described configuration methods.

[0587] One embodiment of this disclosure provides a computer program product including computer-executable instructions, wherein, when executed by a processor, these computer-executable instructions cause the processor to perform any of the above-described configuration methods.

[0588] One embodiment of this disclosure provides a wireless system including the first network element and the third network element described above.

[0589] One embodiment of this disclosure provides a wireless system, including the first network element and the sixth network element described above.

[0590] One embodiment of this disclosure provides an apparatus including one or more processors, wherein the one or more processors are configured to execute instructions stored in memory, and when these instructions are executed by the one or more processors, perform any of the above-described configuration methods.

[0591] It should be noted that when the above request or response includes multiple different contents for indicating multiple different information, the multiple contents can be indicated separately in multiple request / response messages, or they can be indicated together in a single request / response message.

[0592] It should be noted that the network elements mentioned in this disclosure are all logical network elements. They can be implemented as independent devices or as chips or modules that can be integrated into a certain device.

[0593] Although this disclosure describes methods and processes by way of steps performed in a certain order, one or more steps in the methods and processes may be omitted or modified as appropriate. Where appropriate, one or more steps may be performed in an order other than that described.

[0594] It is important to note that the expression "at least one of A or B" used in this document is interchangeable with the expression "A and / or B". This expression refers to a list in which A or B or A and B can be selected. Similarly, the expression "at least one of A, B, or C" used in this document is interchangeable with "A and / or B and / or C" or "A, B, and / or C". This expression refers to a list in which the following can be selected: A or B or C, or A and B, or A and C, or B and C, or all of A, B, and C. The same principle applies to longer lists with the same format.

[0595] While this disclosure describes at least part of the methodological aspects, those skilled in the art will understand that this disclosure also relates to various components, whether hardware components, software, or any combination thereof, for performing at least some aspects and features of the methods. Accordingly, the technical solutions of this disclosure can be embodied in the form of a software product. Suitable software products can be stored in pre-recorded storage devices or other similar non-volatile or non-transitory computer-readable media, including DVDs, CD-ROMs, USB flash drives, removable hard drives, or other storage media. The software product includes instructions tangibly stored thereon that cause a processing device (e.g., a personal computer, server, or network device) to perform examples of the methods disclosed herein. Machine-executable instructions can be in the form of sequences of code, configuration information, or other data that, when executed, cause a machine (e.g., a processor or other processing device) to perform the steps in the methods according to the examples of this disclosure.

[0596] This disclosure may be implemented in other specific forms without departing from the subject matter of the claims. The exemplary embodiments described are illustrative in all respects and not restrictive. Features selected from one or more of the foregoing embodiments may be combined to create alternative embodiments not explicitly described, and features suitable for such combinations will be understood within the scope of this disclosure.

[0597] All values ​​and subranges within the scope of the disclosure are also disclosed. Furthermore, while the systems, devices, and processes disclosed and shown herein may include a specific number of elements / components, the systems, devices, and components may be modified to include more or fewer such elements / components. For example, while any element / component disclosed may be referenced as a single quantity, embodiments disclosed herein may be modified to include multiple such elements / components. The subject matter described herein is intended to cover and encompass all appropriate technical changes.

[0598] Although embodiments have been described above with reference to the accompanying drawings, those skilled in the art will understand that variations and modifications can be made without departing from the scope defined by the appended claims.

Claims

1. A configuration method, comprising: receiving, by a first network element, a first configuration file of a second network element, wherein the first configuration file comprises at least one of a reachable address of the second network element or an authorized configuration file of the second network element, the authorized configuration file being used to determine a consumer of the second network element capable of providing a first base service; determining, by the first network element, a third network element based on the first configuration file of the second network element; and sending, by the first network element, information in the first configuration file to the third network element based on the first configuration file.

2. The method of claim 1, wherein, receiving, by the first network element, the first configuration file of the second network element comprises: receiving, by the first network element, a registration message from the second network element, wherein the registration message indicates the first configuration file.

3. The method of claim 1, wherein, receiving, by the first network element, the first configuration file of the second network element comprises: receiving, by the first network element, a registration message from the first base service, wherein the registration message indicates the first configuration file.

4. The method of claim 1, wherein, receiving, by the first network element, the first configuration file of the second network element comprises: receiving, by the first network element, the first configuration file 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 configuration file forwarded by a fourth network element from a fifth network element, wherein the fourth network element is connected with the fifth network element.

5. The method of any one of claims 1 to 4, wherein, the first configuration file comprises the reachable address of the second network element and the authorized configuration file of the second network element; sending, by the first network element, the information in the first configuration file to the third network element based on the first configuration file 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 configuration file based on the authorized configuration file and the connection between the second network element and the third network element; sending, by the first network element, the information in the first configuration file to the third network element.

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

7. The method of claim 5, wherein, configuring, by the first network element, the connection between the second network element and the third network element comprises: informing, 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. 8.The method of any of claims 5 to 7, further comprising: receiving, by the first network element, a first notification from the third network element, wherein the first notification indicates the connection between the second network element and the third network element. 9.The method of claim 8, further comprising: sending, by the first network element, a first acknowledgement to the third network element, wherein the first acknowledgement indicates that the first notification is received.

10. The method of claim 9, wherein, the first notification and the first acknowledgement both comprise an identity of the first base service.

11. The method of any one of claims 8-10, wherein, The first notification comprises an identity of the third network element, an identity of the first base service, an identity of the second network element, and connection description information of the connection between the second network element and the third network element.

12. The method of any of claims 1-11, further comprising: receiving, by the first network element, a load report from the third network element, wherein the load report indicates a load traffic handled by the third network element.

13. The method of claim 12, further comprising: determining, by the first network element, another 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 another third network element based on the reachable address of the second network element; sending, by the first network element, information in the first profile to the another third network element based on the first profile.

14. The method of claim 12 or 13, further comprising: releasing, by the first network element, the connection between the second network element and the third network element.

15. The method of any one of claims 12 to 14, wherein, The timing of reporting the load report by the third network element is configured by the first network element or predefined.

16. The method of any of claims 1-15, further comprising: receiving, by the first network element, a second acknowledgement from the third network element, wherein the second acknowledgement indicates that the information in the first profile is received.

17. The method of any one of claims 1 to 16, wherein, The authorized profile of the second network element comprises an identity of the first base service and an identity of the second network element; The authorized profile of the second network element further comprises at least one of: an identity of a second base service provided by the consumer and an identity of a network element of the second base service; or determining a permission condition of the consumer.

18. 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, the first profile comprises at least one of a reachable address of the second network element or an authorized profile of the second network element, the authorized profile is used to determine a consumer of a first base service that the second network element is able to provide.

19. The method of 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 base service.

20. The method of 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; forwarding, by the third network element, the first profile to the first network element.

21. The method of any one of claims 18-20, wherein, The first profile comprises the reachable address of the second network element and the authorized profile of the second network element; 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; sending, by the third network element, a first notification to the first network element, wherein the first notification indicates the connection between the second network element and the third network element.

22. The method of claim 21, further comprising: The third network element receives a first acknowledgement from the first network element, wherein the first acknowledgement indicates that the first notification is received.

23. The method of claim 22, wherein, The first notification and the first acknowledgement both comprise an identity of the first basic service.

24. The method of any one of claims 21-23, wherein, The first notification comprises an identity of the third network element, an identity of the first basic service, an identity of the second network element, and connection description information of the connection between the second network element and the third network element.

25. The method of any of claims 18-24, further comprising: The third network element reports a load report to the first network element, wherein the load report indicates a load traffic processed by the third network element.

26. The method of any of claims 18-25, further comprising: The third network element sends a second acknowledgement to the first network element, wherein the second acknowledgement indicates that the information in the first configuration file is received.

27. A configuration method, comprising: A first network element receives a second configuration file, wherein the second configuration file comprises at least one of a task configuration file of a sixth network element or a reachable address of a seventh network element, the task configuration file being used to indicate execution of an action in a task by the sixth network element, the reachable address of the seventh network element being used to establish a connection between the sixth network element and the seventh network element; The first network element determines the sixth network element based on the second configuration file; and The first network element sends information in the second configuration file to the sixth network element based on the second configuration file.

28. The method of claim 27, wherein, The second configuration file comprises the reachable address of the seventh network element; The first network element receives the reachable address of the seventh network element of the seventh network element comprises: The first network element receives a registration message from the seventh network element, wherein the registration message indicates the reachable address of the seventh network element.

29. The method of claim 27, wherein, The second configuration file comprises the reachable address of the seventh network element; The first network element receives the reachable address of the seventh network element of the seventh network element comprises: The first network element receives a registration message from a first basic service to which the seventh network element belongs, wherein the registration message indicates the reachable address of the seventh network element.

30. The method of claim 27, wherein, The second configuration file comprises the reachable address of the seventh network element; The first network element receives the reachable address of the seventh network element comprises: The first network element receives the reachable address of the seventh network element forwarded by a fifth network element from the seventh network element, wherein the seventh network element is connected with the fifth network element.

31. The method of any one of claims 27-30, wherein, The second configuration file comprises the reachable address of the seventh network element and the task configuration file of the sixth network element; The first network element sends the information in the second configuration file to the sixth network element based on the second configuration file comprises: 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; The first network element determines the information in the second configuration file based on the second configuration file and the connection between the sixth network element and the seventh network element; and The first network element sends the information in the second configuration file to the sixth network element.

32. The method of claim 31, wherein, The first network element configures the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element includes: The first network element informs the sixth network element of the reachable address of the seventh network element.

33. The method of claim 31, wherein, The first network element configures the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element includes: The first network element informs the seventh network element of the reachable address of the sixth network element based on the reachable address of the seventh network element.

34. The method of any of claims 31 to 33, further comprising: The first network element receives a second notification from the sixth network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element.

35. The method of claim 34, further comprising: The first network element sends a third acknowledgement to the sixth network element, wherein the third acknowledgement indicates that the second notification is received.

36. The method of claim 35, wherein, Both the second notification and the third acknowledgement include an identification of a first underlying service to which the seventh network element belongs.

37. The method of any one of claims 34-36, wherein, The second notification includes an identification of the sixth network element, an identification of a first underlying 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.

38. The method of any of claims 27 to 37, further comprising: The first network element receives a fourth acknowledgement from the sixth network element, wherein the fourth acknowledgement indicates that the information in the second configuration file is received.

39. The method of claim 38, wherein, Both the information in the second configuration file and the fourth acknowledgement include an identification for indicating the task.

40. The method of any one of claims 27-39, wherein, The information in the second configuration file includes an identification for indicating a first action to be performed by the sixth network element, an identification of a next network element after the sixth network element to perform a second action, and an identification of the second action.

41. The method of any one of claims 27-39, wherein, The information in the second configuration file includes an identification for indicating a first action to be performed by the sixth network element, a quality of service (QoS) parameter of the sixth network element, an identification of a next network element after the sixth network element to perform a second action, and an identification of a connection between the sixth network element and the next network element.

42. The method of any one of claims 27-39, wherein, The information in the second configuration file includes an identification for indicating a quality of service (QoS) parameter of the sixth network element.

43. The method of any of claims 27 to 42, further comprising: The first network element receives a load report from the sixth network element, wherein the load report indicates a load traffic processed by the sixth network element.

44. The method of claim 43, further comprising: The first network element determines another sixth network element based on the second configuration file and the load report; The first network element configures a connection between the seventh network element and the another sixth network element based on the reachable address of the seventh network element; and The first network element sends information in the second configuration file to the another sixth network element based on the second configuration file.

45. The method of claim 43 or 44, further comprising: The first network element releases the connection between the sixth network element and the seventh network element.

46. The method of any one of claims 43-45, wherein, The timing of reporting the load report by the third network element is configured by the first network element or predefined.

47. A configuration method, comprising: A sixth network element receives information from a first network element, wherein the information is included in a second configuration file received by the first network element, and the second configuration file includes at least one of a task configuration file of the sixth network element or a reachable address of a seventh network element, the task configuration file being used to instruct the sixth network element to perform an action in a task, and the reachable address of the seventh network element being used to establish a connection between the sixth network element and the seventh network element.

48. The method of claim 47, wherein, The second configuration file includes the reachable address of the seventh network element. The second configuration file is indicated by a registration message received by the first network element from the seventh network element or a first base service.

49. The method of claim 47, wherein, The second configuration file includes the reachable address of the seventh network element. The method further comprises: The sixth network element establishes the connection between the sixth network element and the seventh network element based on the reachable address of the seventh network element; The sixth network element sends a second notification to the first network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element.

50. The method of claim 49, further comprising: The sixth network element receives a third confirmation from the first network element, wherein the third confirmation indicates that the second notification is received.

51. The method of claim 50, wherein, Both the second notification and the third confirmation include an identity of a first base service to which the seventh network element belongs.

52. The method of any one of claims 49-51, wherein, The second notification includes an identity of the sixth network element, an identity of a first base service to which the seventh network element belongs, an identity of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

53. The method of any one of claims 47 to 52, further comprising: The sixth network element sends a fourth confirmation to the first network element, wherein the fourth confirmation indicates that the information in the second configuration file is received.

54. The method of claim 53, wherein, Both the information in the second configuration file and the fourth confirmation include an identity used to indicate the task.

55. The method of any one of claims 47 to 54, further comprising: The sixth network element reports a load report to the first network element, wherein the load report indicates a load traffic processed by the sixth network element.

56. A configuration apparatus applied to a first network element and comprising: A receiving module configured to receive a first configuration file of a second network element, wherein the first configuration file includes at least one of a reachable address of the second network element or an authorization configuration file of the second network element, and the authorization configuration file is used to determine that the second network element is capable of providing a consumer of a first base service; A determining module configured to determine a third network element based on the first configuration file of the second network element; and The sending module is configured to send information in the first configuration file to the third network element based on the first configuration file.

57. The device of claim 56, wherein, The receiving module is configured to: receive a registration message from the second network element, wherein the registration message indicates the first configuration file.

58. The device of claim 56, wherein, The receiving module is configured to: receive a registration message from the first basic service, wherein the registration message indicates the first configuration file.

59. The device of claim 56, wherein, The receiving module is configured to: receive the first configuration file 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 configuration file forwarded by a fourth network element from a fifth network element, wherein the fourth network element is connected with the fifth network element.

60. The device of any one of claims 56-59, wherein, The first configuration file comprises the reachable address of the second network element and the authorized configuration file of the second network element; The sending 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 configuration file based on the authorized configuration file and the connection between the second network element and the third network element; and send the information in the first configuration file to the third network element.

61. The device of claim 60, wherein, The sending module is configured to: inform the third network element of the reachable address of the second network element.

62. The device of claim 60, wherein, The sending module is configured to: inform the second network element of a reachable address of the third network element based on the reachable address of the second network element.

63. The device of any one of claims 60-62, wherein, The receiving module is further configured to: receive a first notification from the third network element, wherein the first notification indicates the connection between the second network element and the third network element.

64. The device of claim 63, wherein, The sending module is further configured to: send a first acknowledgement to the third network element, wherein the first acknowledgement indicates that the first notification is received.

65. The device of claim 64, wherein, The first notification and the first acknowledgement both comprise an identity of the first basic service.

66. The device of any one of claims 63-65, wherein, The first notification comprises an identity of the third network element, an identity of the first basic service, an identity of the second network element, and connection description information of the connection between the second network element and the third network element.

67. The device of any one of claims 56-66, wherein, The receiving module is further configured to: receive a load report from the third network element, wherein the load report indicates a load traffic processed by the third network element.

68. The apparatus of claim 67, wherein, The determining module is further configured to determine another third network element based on the first configuration file of the second network element and the load report. The sending module is further configured to: configure a connection between the second network element and the another third network element based on the reachable address of the second network element; and send information in the first configuration file to the another third network element based on the first configuration file.

69. The apparatus of claim 67 or 68, further comprising: a releasing module configured to release the connection between the second network element and the third network element.

70. The device of any one of claims 67-69, wherein, The timing at which the third network element reports the load report is configured by the first network element or predefined.

71. The apparatus of any of claims 56 to 70, wherein, The receiving module is further configured to receive a second acknowledgement from the third network element, where the second acknowledgement indicates that the information in the first configuration file is received.

72. The device of any one of claims 56-71, wherein, The authorization configuration file of the second network element includes an identity of the first basic service and an identity of the second network element. The authorization configuration file of the second network element further includes at least one of: an identity of a second basic service provided by the consumer and an identity of a network element of the second basic service; or a permission condition of the consumer.

73. A configuration apparatus applied to a third network element and comprising: a receiving module configured to receive information from a first network element, where the information is included in a first configuration file of a second network element received by the first network element, the first configuration file includes at least one of a reachable address of the second network element or an authorization configuration file of the second network element, and the authorization configuration file is used to determine a consumer of a first basic service that the second network element is able to provide.

74. The device of claim 73, wherein, The first configuration file is indicated by a registration message received by the first network element from the second network element or the first basic service.

75. The apparatus of claim 73, wherein, The receiving module is further configured to receive the first configuration file from a fifth network element, where the third network element is connected with the fifth network element. The apparatus further comprises a first sending module configured to forward the first configuration file to the first network element.

76. The device of any one of claims 73-75, wherein, The first configuration file includes the reachable address of the second network element and the authorization configuration file of the second network element. 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. The apparatus further comprises a second sending module configured to send a first notification to the first network element, where the first notification indicates the connection between the second network element and the third network element.

77. The device of claim 76, wherein, The receiving module is further configured to: receive a first acknowledgement from the first network element, where the first acknowledgement indicates that the first notification is received.

78. The device of claim 77, wherein, The first notification and the first acknowledgement both include an identity of the first basic service.

79. The device of any one of claims 76-78, wherein, The first notification includes an identity of the third network element, an identity of the first basic service, an identity of the second network element, and connection description information of the connection between the second network element and the third network element.

80. The device of any one of claims 73-79, wherein, The apparatus further comprises a reporting module configured to: report a load report to the first network element, where the load report indicates a load traffic processed by the third network element.

81. The device of any one of claims 73-80, wherein, The apparatus further comprises a third sending module configured to: send a second acknowledgement to the first network element, where the second acknowledgement indicates that the information in the first configuration file is received.

82. A configuration apparatus applied to a first network element and comprising: The receiving module is configured to receive a second configuration file, wherein the second configuration file comprises at least one of a task configuration file of a sixth network element or a reachable address of a seventh network element, the task configuration file being used to indicate execution of an action in a task by the sixth network element, and the reachable address of the seventh network element being used to establish a connection between the sixth network element and the seventh network element; The determining module is configured to determine the sixth network element based on the second configuration file; and The sending module is configured to send information in the second configuration file to the sixth network element based on the second configuration file.

83. The device of claim 82, wherein, The second configuration file comprises the reachable address of the seventh network element. The receiving module is configured to: receive a registration message from the seventh network element, wherein the registration message indicates the reachable address of the seventh network element.

84. The device of claim 82, wherein, The second configuration file comprises the reachable address of the seventh network element. 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 indicates the reachable address of the seventh network element.

85. The device of claim 82, wherein, The second configuration file comprises the reachable address of the seventh network element. 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.

86. The device of any one of claims 82-85, wherein, The second configuration file comprises the reachable address of the seventh network element and the task configuration file of the sixth network element. The sending module is configured to: configure the 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 configuration file based on the second configuration file and the connection between the sixth network element and the seventh network element; and send the information in the second configuration file to the sixth network element. The sending module is configured to:

87. The device of claim 86, wherein, notify the sixth network element of the reachable address of the seventh network element. The sending module is configured to:

88. The device of claim 86, wherein, 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 receiving module is further configured to:

89. The device of any one of claims 86-88, wherein, receive a second notification from the sixth network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element. The sending module is further configured to:

90. The device of claim 89, wherein, send a third confirmation to the sixth network element, wherein the third confirmation indicates that the second notification is received. The second notification and the third confirmation both comprise an identity of a first basic service to which the seventh network element belongs.

91. The device of claim 90, wherein, The second notification comprises an identity of the sixth network element, an identity of the first basic service to which the seventh network element belongs, an identity of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

92. The device of any one of claims 89-91, wherein, The receiving module is further configured to:

93. The device of any one of claims 82-92, wherein, receive a fourth confirmation from the sixth network element, wherein the fourth confirmation indicates that the information in the second configuration file is received. The information in the second configuration file and the fourth confirmation both comprise an identity used to indicate the task.

94. The device of claim 93, wherein, ​ 95. The device of any one of claims 82-94, wherein, The information in the second configuration file comprises an identifier of a first action to be performed by the sixth network element, an identifier of a next network element after the sixth network element to perform a second action, and an identifier of the second action.

96. The device of any one of claims 82-94, wherein, The information in the second configuration file comprises an identifier of a first action to be performed by the sixth network element, a quality of service (QoS) parameter of the sixth network element, an identifier of a next network element after the sixth network element to perform a second action, and an identifier of a connection between the sixth network element and the next network element.

97. The device of any one of claims 82-94, wherein, The information in the second configuration file comprises an identifier of a quality of service (QoS) parameter of the sixth network element.

98. The device of any one of claims 82-97, wherein, The receiving module is further configured to: receive a load report from the sixth network element, wherein the load report indicates a load traffic processed by the sixth network element.

99. The apparatus of claim 98, wherein, The determining module is further configured to determine another sixth network element based on the second configuration file and the load report. The sending module is further configured to: configure a connection between the seventh network element and the another sixth network element based on the reachable address of the seventh network element; and send information in the second configuration file to the another sixth network element based on the second configuration file.

100. The apparatus of claim 98 or 99, further comprising: a releasing module configured to release the connection between the sixth network element and the seventh network element.

101. The device of any one of claims 98-100, wherein, The timing at which the third network element reports the load report is configured by the first network element or predefined.

102. 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 configuration file received by the first network element, and the second configuration file comprises at least one of a task configuration file of the sixth network element or a reachable address of a seventh network element, the task configuration file being used to indicate execution of an action in a task by the sixth network element, and the reachable address of the seventh network element being used to establish a connection between the sixth network element and the seventh network element.

103. The device of claim 102, wherein, The second configuration file comprises the reachable address of the seventh network element. The second configuration file is indicated by a registration message received by the first network element from the seventh network element or a first base service.

104. The device of claim 102, wherein, The second configuration file comprises the reachable address of the seventh network element. The apparatus further comprises an establishing module and a first sending 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 sending module is configured to send a second notification to the first network element, wherein the second notification indicates the connection between the sixth network element and the seventh network element.

105. The device of claim 104, wherein, The receiving module is further configured to: receive a third confirmation from the first network element, wherein the third confirmation indicates that the second notification is received.

106. The device of claim 105, wherein, Both the second notification and the third confirmation comprise an identifier of a first base service to which the seventh network element belongs.

107. The device of any one of claims 104-106, wherein, The second notification comprises an identity of the sixth network element, an identity of a first basic service to which the seventh network element belongs, an identity of the seventh network element, and connection description information of the connection between the sixth network element and the seventh network element.

108. The device of any one of claims 102-107, wherein, The apparatus further comprises a second sending module configured to: send a fourth acknowledgement to the first network element, wherein the fourth acknowledgement indicates that the information in the second configuration file is received.

109. The device of claim 108, wherein, The information in the second configuration file and the fourth acknowledgement both comprise an identity used to indicate the task.

110. The device of any one of claims 102-109, wherein, The apparatus further comprises a reporting module configured to: report a load report to the first network element, wherein the load report indicates a load traffic processed by the sixth network element. 111.An apparatus comprising one or more processors configured to execute instructions stored in a memory, the instructions, when executed by the one or more processors, perform the method of any of claims 1-55. 112.A computer-readable medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform the method of any of claims 1-55.

Images