Communication system and related product

Abstract

The invention provides a communication system and related products, the system comprises a first network element, at least one second network element and at least one third network element, the first network element is in communication connection with the at least one second network element and the at least one third network element, and the first network element is in communication connection with the at least one third network element. The control module is used for controlling the operation of the at least one second network element and the at least one third network element; a second network element in the at least one second network element is in communication connection with a fourth network element and is used for interacting with the fourth network element on a control and management surface; and a third network element in the at least one third network element is in communication connection with a fifth network element and is used for interacting with the fifth network element on a data plane.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Application No. 63 / 579,815, 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 communication system 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 with the 5G CP, 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 routing and other functions. 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 communication system. The system includes: a first network element, at least one second network element, and at least one third network element, wherein...

[0006] The first network element is communicatively connected to the at least one second network element and the at least one third network element, and is used to control the operation of the at least one second network element and the at least one third network element;

[0007] The second network element in the at least one second network element is communicatively connected to the fourth network element and is used to interact with the fourth network element on the control and management plane;

[0008] The third network element in the at least one third network element is communicatively connected to the fifth network element and is used to interact with the fifth network element on the data plane.

[0009] By managing at least one C / M-TW-GW (second network element) and at least one Data-TW-GW (third network element) through the C / M function (first network element) in the communication system, the following capabilities / services can be achieved: control and management of BAS domain / infrastructure domain / management domain; enabling interaction between 6G XaaS services provided by the same or different partners, and simultaneously enabling interaction between 6G XaaS services, vertical industries, and XaaS services deployed in third-party infrastructure / cloud; and providing anonymous interaction capabilities for XaaS services through the implementation of C / M-TW-GW and Data-TW-GW to achieve more reliable and trusted management.

[0010] In one possible implementation of the first aspect, the first network element is used for:

[0011] Obtain the first configuration file of the fourth network element;

[0012] The second network element is configured based on the first configuration file, wherein...

[0013] The first configuration file includes at least one of the reachable address of the fourth network element or the authorization configuration file of the fourth network element. The reachable address is used to establish a connection between the fourth network element and the second network element, and the authorization configuration file of the fourth network element is used to determine the consumer that the fourth network element can provide the first basic service.

[0014] With the reachable address of the fourth network element, a secure logical connection can be established between the fourth network element and the third first network element under the control of the first network element. With the help of the authorization configuration file, the first network element can determine the consumer of the first basic service (such as XaaS) that the fourth network element can provide, and can use the information from the first configuration file of the fourth network element to configure the third first network element, thus realizing the configuration of the second network element.

[0015] In one possible implementation of the first aspect, the first network element is used to receive the first configuration file from the fourth network element.

[0016] In one possible implementation of the first aspect, the second network element is configured to receive the first configuration file from a sixth network element connected to the second network element, and forward the first configuration file to the first network element.

[0017] The first network element is used to receive the first configuration file from the second network element.

[0018] In one possible implementation of the first aspect, the first network element is used to receive the first configuration file from the first basic service to which the fourth network element belongs.

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

[0020] In one possible implementation of the first aspect, the first network element is used to send the information in the first configuration file to the second network element;

[0021] The second network element is used to receive the information in the first configuration file from the first network element.

[0022] In one possible implementation of the first aspect, the second network element is used to establish the connection between the fourth network element and the second network element based on the information in the first configuration file.

[0023] In one possible implementation of the first aspect, the first network element is used for:

[0024] Obtain the second configuration file;

[0025] The third network element is configured based on the second configuration file, wherein,

[0026] The second configuration file includes at least one of the task configuration file of the third network element or the reachable address of the fifth network element. The task configuration file is used to instruct the third network element to execute actions in the task, and the reachable address of the fifth network element is used to establish a connection between the third network element and the fifth network element.

[0027] By using the reachable address of the fifth network element, a secure logical connection between the third 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 third network element can be configured using information from the second configuration file of the fifth network element, thus realizing the configuration of the third network element.

[0028] In one possible implementation of the first aspect, the second configuration file includes the reachable address of the fifth network element, and the first network element is used to receive the second configuration file from the fifth network element.

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

[0030] The third network element is used to receive the second configuration file from the sixth network element connected to the third network element, and forward the second configuration file to the first network element;

[0031] The first network element is used to receive the second configuration file from the third network element.

[0032] In one possible implementation of the first aspect, the second configuration file includes the reachable address of the fifth network element, and the first network element is used to receive the second configuration file from the first basic service to which the fifth network element belongs.

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

[0034] In one possible implementation of the first aspect, the first network element is used to send information from the second configuration file to the third network element;

[0035] The third network element is used to receive the information in the second configuration file from the first network element.

[0036] In one possible implementation of the first aspect, the third network element is used to establish the connection between the fifth network element and the third network element based on the information in the second configuration file.

[0037] In one possible implementation of the first aspect, the first network element is used to obtain gateway deployment configuration files of one or more network elements within the BAS domain in which the first network element resides. Here, the network element may be a C / M-TW-GW or a Data-TW-GW, and the gateway deployment configuration file may include deployment information (such as reachable addresses) of the C / M-TW-GW or Data-TW-GW. In this way, the first network element can configure the connection between C / M-TW-GWs or the connection between Data-TW-GWs based on the gateway deployment configuration file.

[0038] In one possible implementation of the first aspect, the first network element is used to obtain gateway deployment configuration files of one or more network elements in another BAS domain different from the BAS domain in which the first network element resides. Here, the gateway deployment configuration file may include deployment information (such as reachable addresses) about gateways in other BAS domains (e.g., one or more C / M-TW-GWs and one or more Data-TW-GWs), without limitation. After obtaining such a gateway deployment configuration file, the first network element can configure the logical connections between the C / M-TW-GW controlled by the first network element and other C / M-TW-GWs in other BAS domains, and / or the logical connections between the Data-TW-GW controlled by the first network element and other Data-TW-GWs in other BAS domains.

[0039] In one possible implementation of the first aspect, the first network element is used to obtain gateway deployment configuration files from one or more third-party network elements. Here, the gateway deployment configuration file may include deployment information (such as reachable addresses) about the gateways of one or more third parties, and is not limited thereto. After obtaining such a gateway deployment configuration file, the first network element can configure the logical connections between the C / M-TW-GW controlled by the first network element and the third-party gateways, and / or the logical connections between the Data-TW-GW controlled by the first network element and the third-party gateways.

[0040] In one possible implementation of the first aspect, the second network element is used to send a first load report to the first network element, wherein the first load report indicates the load traffic processed by the second network element;

[0041] The first network element is used to receive the first load report from the second network element.

[0042] In one possible implementation of the first aspect, the first network element is used to set the timing for the second network element to report the first load report.

[0043] In one possible implementation of the first aspect, the at least one second network element includes two or more second network elements;

[0044] The first network element is used to select another second network element from the two or more second network elements based on a first load report from the two or more second network elements.

[0045] In this way, the first network element (such as the C / M function used as a controller) can obtain the load report of each second 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.

[0046] In one possible implementation of the first aspect, the third network element is used to send a second load report to the first network element, wherein the second load report indicates the load traffic processed by the third network element;

[0047] The first network element is used to receive the second load report from the third network element.

[0048] In one possible implementation of the first aspect, the first network element is used to set the timing for the third network element to report the second load report.

[0049] In one possible implementation of the first aspect, the at least one third network element includes two or more third network elements;

[0050] The first network element is used to select another third network element from the two or more third network elements based on the second load report from the two or more third network elements.

[0051] 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 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.

[0052] In one possible implementation of the first aspect, the first network element is used for:

[0053] The second network element is instructed to record the interaction between the second network element and the fourth network element;

[0054] The second network element is used to record the interaction between the second network element and the fourth network element, and to report the log results to the first network element.

[0055] The interaction between the second network element and the fourth network element is recorded by the second network element, and the first network element can manage the logical topology of the BAS domain where the first network element is located.

[0056] In one possible implementation of the first aspect, the first network element is used for:

[0057] The third network element is instructed to record the interaction between the third network element and the fifth network element;

[0058] The third network element is used to record the interaction between the third network element and the fifth network element, and to report the log results to the first network element.

[0059] The interaction between the third network element and the fifth network element is recorded by the third network element, and the first network element can manage the logical topology of the BAS domain where the first network element is located.

[0060] In one possible implementation of the first aspect, the second network element is used for:

[0061] Receive a first request message from the fourth network element, wherein the first request message indicates the work requested by the fourth network element;

[0062] Based on the first request message, a process for implementing the work requested by the fourth network element is determined.

[0063] In this way, with the help of the first request message, the second network element can determine the process for implementing the work based on the first request message or based on the first request message and information stored locally on the second network element. It can also determine one or more actions corresponding to the process, as well as one or more producer network elements providing services (such as X-as-a-Service, or XaaS) to the fourth network element (the C / M functional entity acting as a consumer-side XaaS). This allows for interaction between the fourth network element and the producer network elements with the assistance of the second network element. In one possible implementation where the second network element is a gateway (also known as a trusted gateway or C / M-TW-GW), the introduction of anonymous services provided by a trusted gateway on the control / management (C / M) plane enhances the trustworthiness of communication from the perspective of the communication system's (such as a 6G system) operation.

[0064] In one possible implementation of the first aspect, the second network element is used to monitor the signaling exchange on the established connection between the second network element and the fourth network element, and also records the signaling exchange (such as the time of the signaling exchange, the object of the signaling exchange, and the duration of the signaling exchange (by recording the start time and end time)).

[0065] In one possible implementation of the first aspect, the third network element is used to process the data format of the data packet when transmitting the data packet.

[0066] In one possible implementation of the first aspect, the third network element is used to perform at least one of decryption or encryption operations when transmitting the data packet.

[0067] By performing decryption or encryption operations on data packets, the security of data packets during transmission can be ensured.

[0068] In one possible implementation of the first aspect, the third network element is used to monitor data exchange on the established connection between the third network element and the fifth network element, and also records the data exchange (such as the time of data exchange, the object of data exchange, and the duration of data exchange (by recording the start time and end time)).

[0069] In one possible implementation of the first aspect, the first network element is communicatively connected to the seventh network element and is used to coordinate the process and data packet exchange on the data plane with the seventh network element.

[0070] Based on the above, different C / M functions within different BAS domains can communicate directly and exchange data packets through their interfaces.

[0071] In one possible implementation of the first aspect, the first network element is used for:

[0072] Obtain a third configuration file, wherein the third configuration file includes reachable addresses of the eighth and ninth network elements under the control of the seventh network element, the reachable address of the eighth network element is used to establish a connection between the second network element and the eighth network element, and the reachable address of the ninth network element is used to establish a connection between the third network element and the ninth network element;

[0073] Configure the second network element and the eighth network element to establish the connection between the second network element and the eighth network element;

[0074] Configure the third network element and the ninth network element to establish the connection between the third network element and the ninth network element.

[0075] Based on the above, different C / M-TW-GWs within different BAS domains can communicate with each other, thus facilitating data packet exchange on the control and management plane.

[0076] In one possible implementation of the first aspect, the first network element is used for:

[0077] Receive a first session establishment request, wherein the first session establishment request indicates a first device to establish a first session;

[0078] The second network element is configured based on the first session establishment request to establish the first session between the first device and the second network element.

[0079] By using the first session establishment request, the first network element can determine the first device, the first session of the first device, and the second network element (i.e., service C / M-TW-GW); based on the determined information, the second network element is configured; thus, the first session of the first device can be established, thereby ensuring the information transmission of the first device on the control and management plane. In addition, information related to the establishment of the first session can be updated to the second service (i.e., SPM service) to protect the first session, and updated to the first service (i.e., CM service) to record information related to the establishment of the first session.

[0080] In one possible implementation of the first aspect, the first network element is used for:

[0081] Receive a second session establishment request, wherein the second session establishment request indicates a first device to establish a second session;

[0082] The third network element is configured based on the second session establishment request to establish the second session between the first device and the third network element.

[0083] By using the second session establishment request, the first network element can determine the first device, the second session of the first device, and the third network element (i.e., the Data-TW-GW service); based on the determined information, the third network element is configured; therefore, the second session of the first device can be established, thereby ensuring the information transmission of the first device on the data plane. In addition, information related to the establishment of the second session can be updated to the second service (i.e., the SPM service) to protect the second session, and updated to the first service (i.e., the CM service) to record information related to the establishment of the second session.

[0084] In one possible implementation of the first aspect, the at least one second network element includes two or more second network elements, and at least two of the two or more second network elements are communicatively connected.

[0085] In one possible implementation of the first aspect, the at least one third network element includes two or more third network elements, and at least two of the two or more third network elements are communicatively connected.

[0086] In the communication system according to this disclosure, the system includes: a first network element, at least one second network element, and at least one third network element, wherein the first network element is communicatively connected to the at least one second network element and the at least one third network element, and is used to control the operation of the at least one second network element and the at least one third network element; the second network element of the at least one second network element is communicatively connected to a fourth network element, and is used to interact with the fourth network element on the control and management plane; the third network element of the at least one third network element is communicatively connected to a fifth network element, and is used to interact with the fifth network element on the data plane. By managing at least one C / M-TW-GW (second network element) and at least one Data-TW-GW (third network element) through the C / M function (first network element) in the communication system, the following capabilities / services can be achieved: control and management of BAS domain / infrastructure domain / management domain; enabling interaction between 6G XaaS services provided by the same or different partners, and simultaneously enabling interaction between 6G XaaS services, vertical industries, and XaaS services deployed in third-party infrastructure / cloud; and providing anonymous interaction capabilities for XaaS services through the implementation of C / M-TW-GW and Data-TW-GW to achieve more reliable and trusted management. Attached Figure Description

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

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

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

[0090] 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.

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

[0092] 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.

[0093] Figure 6A A schematic diagram of the structure of a communication system according to one or more embodiments of the present disclosure is shown.

[0094] Figure 6B A schematic diagram of the structure of an exemplary communication system according to one or more embodiments of the present disclosure is shown.

[0095] Figure 6C An exemplary interface structure diagram of an exemplary communication system according to one or more embodiments of the present disclosure is shown.

[0096] Figure 6D An exemplary interface structure diagram of an exemplary communication system according to one or more embodiments of the present disclosure is shown.

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

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

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

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

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

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

[0103] Figure 9A An exemplary first operating mode of a second network element according to one or more embodiments of the present disclosure is shown.

[0104] Figure 9B An exemplary second operating mode of a second network element according to one or more embodiments of the present disclosure is shown.

[0105] Figure 9C An exemplary third operating mode of a second network element according to one or more embodiments of this disclosure is shown.

[0106] Figure 10A A schematic flowchart illustrating the establishment of a first session for a first device according to one or more embodiments of the present disclosure is shown.

[0107] Figure 10B Another schematic flowchart illustrating the establishment of a first session for a first device according to one or more embodiments of the present disclosure is shown.

[0108] Figure 11A A schematic flowchart illustrating the establishment of a second session for a first device according to one or more embodiments of the present disclosure is shown.

[0109] Figure 11B Another schematic flowchart illustrating the establishment of a second session for a first device according to one or more embodiments of the present disclosure is shown. Detailed Implementation

[0110] To more clearly describe the technical solutions in the embodiments or prior art disclosed herein, the accompanying drawings required for describing the embodiments or prior art are briefly introduced below.

[0111] 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.

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

[0113] Example communication systems and devices

[0114] refer to Figure 1 , Figure 1This 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.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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.

[0121] Basic component structure

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] 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.

[0129] 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.

[0130] 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).

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] 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.

[0136] 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.

[0137] 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.

[0138] 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.

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

[0140] Basic module structure

[0141] 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.

[0142] 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.

[0143] 6G Smart Air Interface

[0144] 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.

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

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] The solutions 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).

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

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

[0155] 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.

[0156] 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.

[0157] 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:

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

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

[0160] - 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.

[0161] 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.

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

[0163] - 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.

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

[0165] 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.

[0166] 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.

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

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

[0169] 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.

[0170] - 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.

[0171] 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.

[0172] - 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.

[0173] - 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.

[0174] 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.

[0175] 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.

[0176] 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.

[0177] 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.

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

[0179] - 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.

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

[0181] - Define 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 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.

[0182] - 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.

[0183] - 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 implementation options. 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.

[0184] - 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.

[0185] - 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.

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

[0187] -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.

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

[0189] - 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.

[0190] - 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.

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

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

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

[0194] - 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.

[0195] 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.

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

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

[0198] 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.

[0199] - 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.

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

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

[0202] Privacy and trustworthiness, etc.

[0203] -Simplify and standardize.

[0204] - Rapid deployment.

[0205] -etc.

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

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

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

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

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

[0211] The proposed 6G network architecture needs to achieve better trust management.

[0212] The proposed 6G network architecture enables controlled anonymous interaction among multiple participants.

[0213] This disclosure proposes a service framework that is expected to meet the aforementioned new requirements for 6G networks.

[0214] The proposed service framework owns and manages the C / M-TW-GW and Data-TW-GW. This service framework provides the following capabilities / services:

[0215] Control and manage the BAS domain / infrastructure domain / management domain.

[0216] Enables interaction between 6G XaaS services provided by the same or different partners, and also enables interaction between 6G XaaS services, vertical industries, and XaaS services deployed in third-party infrastructure / cloud.

[0217] By implementing C / M-TW-GW and Data-TW-GW, anonymous interaction capabilities for XaaS services are provided to achieve more reliable and trusted management.

[0218] This service framework can be provided by the infrastructure owner (such as RAN providers and CN providers).

[0219] The scheme described in this disclosure is applicable to future 6G networks.

[0220] The proposed C / M-TW-GW and Data-TW-GW are expected to become core potential points for 6G products.

[0221] Figure 6A A schematic diagram of the structure of the above-described service framework (hereinafter also referred to as a communication system) according to one or more embodiments of the present disclosure is shown. The communication system includes: a first network element, at least one second network element, and at least one third network element, wherein the first network element is communicatively connected to the at least one second network element and the at least one third network element, and is used to control the operation of the at least one second network element and the at least one third network element; the second network element of the at least one second network element is communicatively connected to a fourth network element, and is used to interact with the fourth network element on the control and management plane; the third network element of the at least one third network element is communicatively connected to a fifth network element, and is used to interact with the fifth network element on the data plane.

[0222] The first, second, and third network elements are three types of logical network elements. The first network element can be a C / M function within the BAS domain; the second network element can be a control / management planet-rustworthy GW (C / M-TW-GW) within the BAS domain; and the third network element can be a data planet-rustworthy GW (Data-TW-GW) within the BAS domain. Within a BAS domain or a management domain (or simply a domain), there can be one C / M function, at least one C / M-TW-GW, and at least one Data-TW-GW. It should be noted that although... Figure 6A One domain is shown, but the number of domains is not limited in this disclosure embodiment.

[0223] The first network element controlling the operation of at least one second network element and at least one third network element can be a C / M function within the BAS domain; the C / M function controls and manages the topology of the BAS domain, such as the logical connection between XaaS services / vertical industries within such a domain and GW (including C / M-TW-GW and Data-TW-GW); XaaS services within the same BAS domain as the C / M function have their own C / M function entity (implementing the C / M function of the XaaS service module) and data function entity (implementing the data processing function of the XaaS service module); vertical industries within the same BAS domain as the C / M function also have their own C / M function entity and data function entity; the C / M-TW-GW under the control of the C / M function within the BAS domain provides the ability to connect the C / M function entities of XaaS services and vertical industries within the BAS domain, so as to realize anonymous and secure C / M plane interaction between XaaS services according to the authorization profile of the XaaS service, and at the same time realize anonymous and secure C / M plane interaction between vertical industries. The Data-TW-GW under the C / M function control within the BAS domain provides the ability to connect XaaS services within the BAS domain and data function entities in vertical industries. This enables anonymous and secure data plane interaction between XaaS services and between vertical industries, ensuring service performance. Additionally, for example, a second network element can be used as a service C / M-TW-GW for 6G devices / D-Users / any type of customer, and a third network element can be used as a service Data-TW-GW for 6G devices / D-Users / any type of customer. The C / M function also manages C / M sessions and / or data sessions to control access to the communication system for 6G devices / D-Users / any type of customer. Here, the C / M session can be a secure logical connection established between the 6G device / D-User / any type of customer and its service C / M-TW-GW (second network element), and is used to realize signaling exchange between the two parties on the C / M plane; the data session can be a secure logical connection established between the 6G device / D-User / any type of customer and its service Data-TW-GW (third network element), and is used to realize data exchange between the two parties on the data plane.

[0224] In one possible implementation, the fourth network element can be an XaaS service within the BAS domain or a C / M function entity within a vertical industry. In another possible implementation, the fifth network element can be an XaaS service within the BAS domain or a data function entity within a vertical industry.

[0225] For the concept of XaaS services, please refer to [link / reference]. Figure 5The 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 who need other XaaS services to support their operation, while XaaS services provide their capabilities to 6G customers.

[0226] 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 can be connected through C / M-TW-GW to support anonymous and secure C / M plane interaction between XaaS services.

[0227] 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 can be connected through Data-TW-GW to support anonymous and secure data plane interaction between XaaS services.

[0228] Vertical industries refer to enterprise or industry clients, which differs from personal wireless devices. Vertical industries may have their own dedicated network resources, integrate their custom functions with network functions, and have their own clients. For example, a vertical industry here can refer to a type of service that operates on a network provided by a carrier, etc. The vertical industry itself typically does not own this network, but may still be able to provide services to users based on the network; therefore, from the carrier's perspective, this type of service can be considered 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 considered vertical industries. Vertical industries may also have one or more servers, as well as one or more client / management (C / M) functional entities and one or more data functional entities. Therefore, in order for a vertical industry to provide services to users, the C / M-TW-GW needs to be connected to the vertical industry's C / M functional entities, and the Data-TW-GW needs to be connected to the vertical industry's data functional entities. It should be noted that although the examples in the following description are illustrated in conjunction with the C / M and data entities of an XaaS service, these examples also apply to the C / M and data entities of vertical industries.

[0229] In one possible implementation, at least one second network element includes only one second network element, where the second network element in the above-mentioned at least one second network element refers to the unique second network element, which is communicatively connected to the fourth network element.

[0230] In one possible implementation, at least one second network element includes two or more second network elements, and at least two of these two or more second network elements are communicatively connected. For example, different C / M-TW-GWs (some or all of the C / M-TW-GWs within the same BAS domain) can be connected. In this case, the second network element in the aforementioned at least one second network element can refer to one or more of two or more second network elements, and each of these one or more second network elements can be communicatively connected to the fourth network element directly or indirectly (through other second network elements). For example, not all C / M-TW-GWs need to be individually connected to the C / M function entity of the XaaS service within the BAS domain; it should be noted that, although Figure 6A The illustration shows a scenario where each of one or more second network elements is directly or indirectly connected to a fourth network element. However, the scheme of this disclosure is also applicable to the scenario where each of one or more second network elements is directly connected to a fourth network element.

[0231] In one possible implementation, at least one third network element includes only one third network element, where the third network element in the above-mentioned at least one third network element refers to the unique third network element, which is communicatively connected to the fifth network element.

[0232] In one possible implementation, at least one third network element includes two or more third network elements, and at least two of these third network elements are communicatively connected. For example, different Data-TW-GWs (some or all of the Data-TW-GWs within the same BAS domain) can be connected. In this case, the third network element in the aforementioned at least one third network element can refer to one or more of the two or more third network elements, each of which is directly or indirectly (through other third network elements) communicatively connected to the fifth network element. For example, not all Data-TW-GWs need to be individually connected to the data function entity of the XaaS service within the BAS domain; it should be noted that, although Figure 6A The illustration shows a scenario where each of one or more third network elements is directly or indirectly connected to a fifth network element. However, the scheme of this disclosure is also applicable to the scenario where each of one or more third network elements is directly connected to a fifth network element.

[0233] The following will combine Figures 6B to 6DThis describes a specific example of a communication system, which can be a service framework having a C / M-TW-GW and a Data-TW-GW. It should be noted that this example uses one C / M-TW-GW and one Data-TW-GW, but in practice, any number of C / M-TW-GWs and Data-TW-GWs can be configured as needed. One or more NET4CON C / M functions can be one or more of the aforementioned first network elements, the C / M-TW-GW can be one of the aforementioned second network elements, and the Data-TW-GW can be one of the aforementioned third network elements.

[0234] The service framework provides the following capabilities / services:

[0235] Control and manage the BAS domain / infrastructure domain / management domain.

[0236] Enables interaction between 6G XaaS services provided by the same or different partners, and also enables interaction between 6G XaaS services, vertical industries, and XaaS services deployed in third-party infrastructure / cloud.

[0237] By implementing C / M-TW-GW and Data-TW-GW, anonymous interaction capabilities for XaaS services are provided to achieve more reliable and trusted management.

[0238] This service framework can be provided by the infrastructure owner (such as RAN providers and CN providers).

[0239] This service framework (within a BAS domain or a management domain) consists of the following components:

[0240] >Logical units, including:

[0241] •NET4CON C / M functionality;

[0242] • One or more C / M-TW-GW;

[0243] • One or more Data-TW-GWs.

[0244] Internal interfaces include:

[0245] •NET4CON_C / M_Function-C / M-TW-GW;

[0246] •NET4CON_C / M_Function-Data-TW-GW.

[0247] External interfaces include:

[0248] • Interfaces related to C / M-TW-GW, such as 6G-C / M-1, 6G-C / M-2 and 6G-C / M-3, will be described in detail below;

[0249] • Interfaces related to Data-TW-GW, such as 6G-Data-1, 6G-Data-2, and 6G-Data-3;

[0250] • Interfaces related to C / M functionality, such as NET4CON-NET4CON and External-NET4CON.

[0251] The Service C / M-TW-GW, which is one of the aforementioned C / M-TW-GWs, is the network-side endpoint of the C / M session of a device (such as a 6G device) that communicates with the communication system through the C / M session.

[0252] The Data-TW-GW service, one of the aforementioned Data-TW-GWs, is the network-side endpoint of a data session for a device (such as a 6G device), which is used to enable the exchange of data plane packets between the device and the communication system.

[0253] The C / M function is responsible for the following (but not limited to):

[0254] • Information acquisition (which will be discussed below) Figures 7A to 7C as well as Figures 9A to 9C (Example provided)

[0255] o Obtain the XaaS service deployment configuration file from external sources (such as CONET, XaaS service, etc.);

[0256] o Obtain the XaaS service authorization configuration file;

[0257] o Obtain the GW deployment.

[0258] •Manage BAS / manage domain logical topology (which will be discussed below) Figures 7A to 7C as well as Figures 8A to 8C (Example provided)

[0259] o Configure GWs to establish secure connections between these GWs (including third-party GWs), which can be achieved through GW deployments obtained from GWs in other BAS domains;

[0260] Configure the C / M-TW-GW within the BAS domain and the C / M plane functional entity (also known as the C / M functional entity) of the XaaS service to establish a secure connection;

[0261] Configure C / M-TW-GW based on the XaaS service's authorization configuration file and XaaS service's deployment configuration file;

[0262] Configure C / M-TW-GW and vertical industries to establish secure connections between C / M-TW-GW and vertical industries when needed;

[0263] Configure the Data-TW-GW and XaaS service's data plane functional entity (also known as the data functional entity) within the BAS domain to establish a secure connection;

[0264] Configure Data-TW-GW and vertical industries to establish secure connections between Data-TW-GW and vertical industries when needed.

[0265] • Manage C / M sessions and data sessions for mobile devices and D-Users (anchors) in NET4DW (described below in conjunction with...) Figure 10A and Figure 10B as well as Figure 11A and Figure 11B (Example provided)

[0266] o Establishment of a C / M session (the logical connection between the device and its serving C / M-TW-GW) for the control device;

[0267] o Establishment of a data session (logical connection between the device and its serving Data-TW-GW) for the control device;

[0268] o Maintains information about the device's service C / M sessions and data sessions, as well as the mapping between RBs and sessions.

[0269] • Manage logs and loads for C / M-TW-GW and Data-TW-GW

[0270] Based on the interaction logs of XaaS services on the C / M plane and data plane, configure C / M-TW-GW and Data-TW-GW;

[0271] o Track the load status of C / M-TW-GW and Data-TW-GW;

[0272] o Manage GW load balancing by disconnecting XaaS service functions from the current secure connection of some GWs and re-establishing secure connections with other GWs.

[0273] •etc.

[0274] C / M-TW-GW is responsible for providing the ability to connect XaaS services within the BAS / infrastructure domain with one or more C / M functional entities in vertical industries, enabling anonymous and secure C / M face interactions between XaaS services based on the authorization profiles of the XaaS services.

[0275] The C / M-TW-GW function is responsible for the following (but not limited to):

[0276] • Receive configurations from C / M functions or other entities, maintain the authorization profiles for XaaS services, and manage local active authorization tables to control the authorization of XaaS service consumers and providers;

[0277] • Receive configuration from C / M functions or other entities and maintain the deployment configuration files for XaaS services;

[0278] • Establish and maintain a secure tunnel with each XaaS service and vertical industry within the BAS / infrastructure domain;

[0279] • Perform operations related to safe tunnels;

[0280] • Perform valid C / M face message detection and message logging;

[0281] • Record the load on these tunnels to enable load management;

[0282] • Implement multiple operating modes in the C / M plane message exchange process between XaaS services. The following will combine... Figures 9A to 9C Provide a detailed description.

[0283] Data-TW-GW is responsible for providing the ability to connect one or more XaaS services within the basic architecture structure (BAS) domain to one or more data function entities in one or more vertical industries, in order to enable anonymous and secure data plane interaction between one or more XaaS services and ensure service performance.

[0284] Data-TW-GW is responsible for the following (but not limited to):

[0285] • Establish and maintain a secure tunnel with XaaS services and one or more data plane functions of each vertical industry within the BAS / infrastructure domain;

[0286] • Configuration for receiving packet exchange between XaaS services;

[0287] • Record the load of each of these tunnels and update it to the NET4CON C / M function to achieve load management;

[0288] • When transmitting data packets, perform decryption and encryption operations as needed;

[0289] • Data format conversion to enable the data function entities of the XaaS service to understand the format of the received data;

[0290] • Based on configuration managed through task management or carried out via the protocol stack, QoS-oriented and routing-oriented protocol processing is performed. In the latter case, Data-TW-GW processes the protocol header and performs the corresponding QoS processing and routing operations;

[0291] • Traffic is recorded based on configuration to support network operation optimization, service performance assurance, and billing;

[0292] • Perform a validity check based on the configuration;

[0293] •etc.

[0294] The three types of logical network elements mentioned above are interconnected through interfaces. For example, within the same BAS domain, the C / M function can be connected to both the C / M-TW-GW and the Data-TW-GW; different C / M-TW-GWs within the same BAS domain can be connected, as can different Data-TW-GWs within the same BAS domain; the C / M-TW-GW within the same BAS domain can be connected to the C / M function entity of the XaaS service, and the Data-TW-GW within the same BAS domain can be connected to the data function entity of the XaaS service.

[0295] For example, for different domains, the C / M-TW-GW in one BAS domain can be connected to the C / M-TW-GW in other BAS domains, the Data-TW-GW in one BAS domain can be connected to the Data-TW-GW in other BAS domains, and different C / M functions in different domains can also be connected.

[0296] The aforementioned service framework is used as a service (NET4CON service). This service framework includes a first network element (C / M function), one or more second network elements (C / M-TW-GW), and one or more third network elements (Data-TW-GW) to implement the NET4CON service within a BAS domain. The NET4CON services belonging to the first, second, and third network elements, and the services belonging to the fourth and fifth network elements (XaaS services), are different services. The NET4CON service is used to provide connectivity between entities providing XaaS services. The NET4CON service is used for illustrative purposes only and may be used under other names; this disclosure does not limit its use. Unless otherwise stated, the C / M function in this document refers to the C / M function of the NET4CON service.

[0297] The interfaces related to the connections of the aforementioned logical network elements will be described in detail. For the NET4CON service, internal interfaces are defined as the interfaces under C / M function control between C / M functions within the same domain and between C / M-TW-GW, and the interfaces under C / M function control between C / M functions within the same domain and Data-TW-GW. All interfaces other than internal interfaces are referred to as external interfaces. That is to say, the external interfaces of the NET4CON service include the interfaces between the NET4CON service and other XaaS services and functions implemented in third-party infrastructure, the interfaces between different C / M-TW-GWs, and the interfaces between different Data-TW-GWs.

[0298] Still referencing Figure 6B The C / M function can connect to the C / M-TW-GW or Data-TW-GW within the same BAS domain via internal interfaces. Specifically, the C / M function connects to the C / M-TW-GW via the interface NET4CON_C / M_Function-C / M_GW, and the C / M function connects to the Data-TW-GW via the interface NET4CON_C / M_Function-Data_GW. Specifically:

[0299] • The interface NET4CON_C / M_Function-C / M_GW is used for (but is not limited to):

[0300] >Configure the C / M function to configure C / M-TW-GW, including XaaS service deployment configuration files, XaaS service authorization configuration files, etc.;

[0301] >Enable the C / M function to configure C / M-TW-GW as a service C / M-TW-GW for a device / D-User;

[0302] > Enables the C / M-TW-GW to forward some C / M messages to the C / M function to make decisions (such as selecting a service C / M-TW-GW for the device).

[0303] > Enables the C / M function to send its decision-making messages to the C / M-TW-GW;

[0304] >Enable the C / M-TW-GW to report its recorded load information so that the C / M function can perform load management;

[0305] >etc.

[0306] • The interface NET4CON_C / M_Function-Data_GW is used for (but is not limited to):

[0307] >Configure the C / M function to configure Data-TW-GW, including XaaS service deployment configuration files, (optional) XaaS service authorization configuration files, etc.;

[0308] > Enables the C / M function to configure Data-TW-GW as a service Data-TW-GW for a device / D-User;

[0309] > Enables the Data-TW-GW to report its recorded load information so that the C / M function can perform load management;

[0310] >etc.

[0311] Connections between different C / M-TW-GWs within the same BAS domain, between different Data-TW-GWs within the same BAS domain, between a C / M-TW-GW within the same BAS domain and a C / M functional entity of an XaaS service, between a Data-TW-GW within the same BAS domain and a data functional entity of an XaaS service, between different C / M-TW-GWs within different BAS domains, between different Data-TW-GWs within different BAS domains, between a C / M-TW-GW and a C / M functional entity implemented in a third-party infrastructure, and between a Data-TW-GW and a data functional entity implemented in a third-party infrastructure can be implemented through external interfaces. These interfaces include... Figure 6C As shown.

[0312] like Figure 6C As shown, the C / M-TW-GW within the same BAS domain (such as BAS domain A or BAS domain B) and the C / M functional entity of the XaaS service (i.e., Figure 6C The C / M plane function of the XaaS service shown is connected via external interface 6G-C / M-1; different C / M-TW-GWs within BAS domain A are connected via external interface 6G-C / M-2; different C / M-TW-GWs within BAS domain B are connected via external interface 6G-C / M-2; and C / M-TW-GWs within BAS domain A and BAS domain B are connected via external interface 6G-C / M-3. Similarly, Data-TW-GWs within the same BAS domain (such as BAS domain A or BAS domain B) are connected to the data function entity of the XaaS service (i.e.,... Figure 6CThe data plane function of the XaaS service shown is connected through external interface 6G-Data-1; different Data-TW-GWs within BAS domain A are connected through external interface 6G-Data-2; different Data-TW-GWs within BAS domain B are connected through external interface 6G-Data-2; and Data-TW-GWs within BAS domain A and Data-TW-GWs within BAS domain B are connected through external interface 6G-Data-3.

[0313] Interface 6G-C / M-1 is used for:

[0314] > Receive and send C / M plane messages between C / M-TW-GW and the C / M function entity (also known as C / M function) of XaaS service;

[0315] Enables interaction between C / M functional entities of different XaaS services.

[0316] Interface 6G-C / M-2 is used for:

[0317] Interaction between C / M-TW-GW within the BAS / Infrastructure Domain.

[0318] The 6G-C / M-3 interface is used for:

[0319] Interactions between C / M-TW-GW belonging to different BAS / infrastructure domains;

[0320] Interaction with third-party control / management functions, suitable for C / M-TW-GW connected to third-party clouds, such as for information sharing.

[0321] Interface 6G-Data-1 is used for:

[0322] Receiving and sending data plane packets between the Data-TW-GW and the data function entities (also known as data functions) of the XaaS service;

[0323] Enables data packet exchange between different XaaS service data processing entities.

[0324] Interface 6G-Data-2 is used for:

[0325] Interaction between Data-TW-GW within the BAS / Infrastructure Domain.

[0326] Interface 6G-Data-3 is used for:

[0327] Interaction between Data-TW-GW belonging to different BAS / infrastructure domains.

[0328] Interaction with third-party data plane functions is applicable to Data-TW-GW connected to third-party cloud / infrastructure, such as sending data packets to or receiving data plane data packets from third-party infrastructure.

[0329] Different client / master functions within different domains are connected through external interfaces, such as... Figure 6D As shown, the C / M function in BAS domain A and the C / M function in BAS domain B are connected through the external interface 6G-C / M_Function-1.

[0330] Interface 6G-C / M_Function-1 is used for:

[0331] Enables direct communication between NET4CON C / M functions within different BAS / infrastructure domains;

[0332] Enables direct communication between the BAS domain, which connects to third-party infrastructure, and the third party's control / management functions;

[0333] Coordinate data plane processes and packet exchange.

[0334] It should be noted that the names of the interfaces mentioned above are merely illustrative and should not be construed as limiting the embodiments of this disclosure.

[0335] The following describes how the first network element (C / M function) in the BAS domain controls and manages the second network element (C / M-TW-GW) connected to the fourth network element (C / M function entity of XaaS service) and the third network element (Data-TW-GW) connected to the fifth network element (data function entity of XaaS service).

[0336] As mentioned above, the C / M function can acquire information, such as XaaS service deployment configuration files and / or XaaS service authorization configuration files. These one or more acquired configuration files can be used to establish logical connections between C / M-TW-GW and the C / M function entities of the XaaS service, as well as logical connections between Data-TW-GW and the data function entities of the XaaS service. They can also be used to configure C / M-TW-GW so that C / M-TW-GW can support anonymous and secure connections between the C / M function entities of the XaaS service.

[0337] In one possible implementation, the first network element is used to obtain the gateway deployment configuration files of one or more network elements within the BAS domain where the first network element resides. These network elements can be multiple second network elements or multiple third network elements, such as... Figure 6AAs shown, the gateway deployment configuration file can include deployment information (such as reachable addresses) of the second network element (C / M-TW-GW) or the third network element (Data-TW-GW), enabling the first network element to configure the connection between the second network elements or the connection between the third network elements based on the gateway deployment configuration file.

[0338] In one possible implementation, the first network element obtains gateway deployment configuration files from one or more network elements in a different BAS domain than the BAS domain in which the first network element resides. These network elements can be one or more eighth network elements (C / M-TW-GW) or one or more ninth network elements (Data-TW-GW) in a different BAS domain than the BAS domain in which the first network element resides. Here, the gateway deployment configuration file can include deployment information (such as reachable addresses) about gateways in other BAS domains (such as one or more C / M-TW-GWs and one or more Data-TW-GWs), without limitation. After obtaining such a gateway deployment configuration file, the first network element can configure the logical connections between the second network element controlled by the first network element and the eighth network element controlled by the seventh network element (such as the C / M function) in other BAS domains, and / or the logical connections between the third network element controlled by the first network element and the ninth network element controlled by the seventh network element in other BAS domains.

[0339] In one possible implementation, the first network element obtains gateway deployment configuration files from one or more third-party network elements. Here, the gateway deployment configuration file may include deployment information (such as reachable addresses) about the gateways of one or more third parties, without limitation. After obtaining such a gateway deployment configuration file, the first network element can configure the logical connections between the C / M-TW-GW controlled by the first network element and the third-party gateways, and / or the logical connections between the Data-TW-GW controlled by the first network element and the third-party gateways.

[0340] In one possible implementation, the first network element is used to: obtain a first configuration file of the fourth network element; configure the second network element based on the first configuration file, wherein the first configuration file includes at least one of the reachable address of the fourth network element or the authorization configuration file of the fourth network element. The reachable address is used to establish a connection between the fourth network element and the second network element, and the authorization configuration file of the fourth network element (also referred to as the aforementioned XaaS service authorization configuration file) is used to determine the consumer of the first basic service that the fourth network element can provide. The consumer can refer to one or more producer XaaS service request services (also referred to herein as the first basic service or XaaS service), where the producer XaaS service refers to the XaaS service that provides the consumer XaaS service request service through its C / M functional entity (also referred to herein as the fourth network element), and the first basic service can be... Figure 5 This can be any XaaS service or any other possible XaaS service. Here, the reachable address of the fourth network element can be the reachable physical address of the fourth network element, such as the ID of the fourth network element, or other forms, as long as other network elements can access the fourth network element.

[0341] As mentioned earlier, various types of XaaS services exist. When providing services, one XaaS service may need the assistance of another XaaS service, or may request services from another XaaS service. Therefore, these two XaaS services may play different roles: one XaaS service acts as a consumer XaaS service, and the other acts as a producer XaaS service. A consumer XaaS service typically refers to a service that requires services from another XaaS service, while a producer XaaS service typically refers to a service that provides services from a consumer XaaS service. For example, the NET4AI service, which provides AI capabilities to support various AI applications, may need the NET4DAM service to collect data. Therefore, in this example, the NET4AI service is a consumer XaaS service, and the NET4DAM service is a producer XaaS service. The producer XaaS service can be... Figure 5 Any XaaS service or any other possible XaaS service in the list, the consumer XaaS service can also be Figure 5 Any one of the XaaS services or any other possible XaaS service.

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

[0343] 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 fourth 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.

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

[0345] In one implementation of this disclosure, a first network element receives a first configuration file from a fourth network element. In another implementation, the first network element receives a registration message from the fourth network element, wherein the registration message indicates the first configuration file. Specifically, the registration message is sent to the first network element via the fourth network element, and the first network element directly receives the registration message sent by the fourth network element or forwarded from the fourth network element by another network element, wherein the other network element is connected to the fourth network element.

[0346] In one implementation of this disclosure, a second network element receives a first configuration file from a sixth network element connected to it and forwards the first configuration file to the first network element; the first network element receives the first configuration file from the second network element. In another implementation, the second network element receives the first configuration file forwarded by another network element from the sixth network element, wherein the other network element is connected to the sixth network element. For example, the sixth network element is a consortium network (CONET), or the sixth network element is deployed within the CONET, which stores the reachable address and authorized configuration file of the fourth network element. The CONET provides the capability for 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 other network element can be another C / M-TW-GW located in the same BAS domain as the second network element. The other network element first receives the first configuration file from the sixth network element and then sends the received first configuration file to the first network element. It should be noted that the operation of the other network element can be the same as the operation of the second network element described in the embodiments of this disclosure.

[0347] In one implementation of this disclosure, the first network element receives a first configuration file from a first basic service to which the fourth network element belongs. In another implementation, the first network element receives a registration message from the 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 fourth network element belongs.

[0348] In the case where the first configuration file comes from the sixth 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.

[0349] 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 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 fourth 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 fourth 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 of the XaaS service, 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 fifth network element of the first basic service, 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 fourth network element. Upon receiving the XaaS service deployment configuration file, the first network element can obtain the reachable address of the fourth network element to configure it.

[0350] 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 fourth network element), one or more IDs of one or more C / M functional entities of one or more consumer XaaS services authorized by the fourth 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 fourth network element to provide XaaS services can be used as the authorization profile of the fourth network element. After receiving the XaaS service authorization profile, the first network element can obtain the authorization profile of the fourth network element to configure the fourth network element.

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

[0352] After obtaining the first configuration file of the fourth network element, the configuration of the second network element can be based on the first configuration file. In one implementation of this disclosure, when at least one second network element includes two or more second network elements, in order to configure the second network element based on the first configuration file, the first network element can first determine the second network element (the second network element to be configured) from the two or more second network elements, and then configure the determined second network element based on the information in the first configuration file. That is, the first network element controls and manages two or more second network elements, and after receiving the first configuration file of the fourth network element, the first network element can determine the second network element for the fourth network element. For example, the first network element can consider the specific information included in the first configuration file and then select / choose a suitable second network element for the fourth network element.

[0353] In one implementation of this disclosure, when the first configuration file includes the reachable address of the fourth network element, the first network element can randomly select a second network element (such as a C / M-TW-GW) within the BAS domain, or select a C / M-TW-GW as the second 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 second 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. In this case, the information used to configure the second network element is included in the first configuration file, and the information used to configure the second network element is the reachable address of the fourth network element.

[0354] In one implementation of this disclosure, when the first configuration file includes the authorization configuration file of the fourth network element, the first network element can determine the consumers that the fourth 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 fourth network element is located) and one or more C / M-TW-GWs, a C / M-TW-GW is selected as the second network element. For example, in addition to the first network element (i.e., the C / M function) and the fourth 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 fourth 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 C / M functional entity A of consumer 1 and C / M-TW-GW1, C / M-TW-GW1 is selected as the second network element to be configured to support anonymous and secure interaction between C / M functional entity A of consumer 1 and the fourth network element; based on the authorization configuration file and the connection between C / M functional entity B of consumer 2 and C / M-TW-GW2, C / M-TW-GW2 is selected as the second network element to be configured to support anonymous and secure interaction between C / M functional entity B of consumer 2 and the fourth network element. In this case, the information used to configure C / M-TW-GW1 is included in the first configuration file and is the authorization information related to C / M functional entity A of consumer 1 in the authorization configuration file of the fourth network element; the information used to configure C / M-TW-GW2 is included in the first configuration file and is the authorization information related to C / M functional entity B of consumer 2 in the authorization configuration file of the second network element.

[0355] In one implementation of this disclosure, configuring the second network element based on the first configuration file by the first network element further includes: the first network element sending information from the first configuration file to the second network element; and the second network element receiving information from the first network element. The information in the first configuration file can be used for the operation of the second network element. The operation of the second network element can include operations involving the second network element when establishing a connection between the second network element and the fourth network element, as well as the configuration of the second network element, etc. The information in the first configuration file can be some or all of the information in the first configuration file.

[0356] For example, as described in the example above, if a C / M-TW-GW (second 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 configuration file of the C / M-TW-GW will be the authorization information related to one or more C / M functional entities of one or more consumers connected to the C / M-TW-GW in the authorization configuration file.

[0357] In this way, the first network element does not need to send all information to the second network element, but only sends information related to the operation of the second network element (specific information), thus reducing system overhead.

[0358] When the first configuration file only includes the reachable address of the fourth network element, the step of configuring the second network element based on the first configuration file is a process of establishing a connection between the second and fourth network elements. In this case, the fourth network element can be a C / M function entity of a consumer-side XaaS service or a producer-side XaaS service. When the first configuration file only includes the authorization configuration file of the fourth network element, the step of configuring the second network element based on the first configuration file is a configuration process performed by the second network element to support the fourth 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, the step of configuring the second network element based on the first configuration file is a connection and configuration process for the second network element. In the first case, the second network element is used to establish a connection between the fourth and second network elements based on the first configuration file. The configuration of the connection between the fourth and second network elements is as follows: Figure 7A As shown, the specific steps include:

[0359] In S701A, the first network element notifies the second network element of the reachable address of the fourth network element; or the first network element notifies the fourth network element of the reachable address of the second network element based on the reachable address of the fourth network element. The first network element has multiple options when configuring a connection, including notifying both parties establishing the connection of each other's reachable addresses.

[0360] S702A, the second network element establishes a connection between itself and the fourth network element based on the reachable address of the fourth network element. If the reachable address of the second network element is notified to the fourth network element, this connection can be initiated by the fourth network element; if the reachable address of the fourth network element is notified to the second network element, this connection can be initiated by the second network element.

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

[0362] After the connection between the second network element and the fourth network element is established, the second 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 fourth network elements.

[0363] In S704A, after receiving the first notification, the first network element sends a first acknowledgment to the second network element; the second network element receives the first acknowledgment from the first network element. The first acknowledgment indicates that the first notification has been received.

[0364] In one implementation of this disclosure, both the first notification and the first confirmation include an identifier of the first basic service. This allows for secure and reliable information exchange between the first network element and the second network element.

[0365] In one implementation of this disclosure, the first notification includes the identifier of the second network element, the identifier of the first basic service, the identifier of the fourth network element, and connection description information of the connection between the second network element and the fourth 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.

[0366] Figure 7BA schematic flowchart illustrating an exemplary connection process between a second network element and a fourth network element according to one or more embodiments of this disclosure is shown. The first network element is a C / M function of the NET4CON service, the second network element is a C / M-TW-GW in the NET4CON service, and the fourth network element is a C / M function entity of the XaaS service. The prerequisites for establishing a connection between the C / M-TW-GW and the C / M function entity are: one or more C / M-TW-GWs within each BAS domain have been deployed; the C / M function 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 function entity of the XaaS service have obtained the required certificates (applicable to certificate-based schemes).

[0367] 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 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 second network element (C / M-TW-GW) and the fourth 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.

[0368] This connection can be established by either the C / M-TW-GW or the C / M functional entity of the XaaS service. In the first case, the C / M function of the NET4CON service can notify the C / M-TW-GW of the reachability address of the newly deployed C / M functional entity of the XaaS service. That is, the C / M function of the NET4CON service notifies the C / M functional entity of the XaaS service of its reachability address based on the reachability address of the XaaS service's C / M functional entity. In the latter case, the newly deployed C / M functional entity of the XaaS service can be configured based on the reachability address of the C / M-TW-GW. For example, the C / M function notifies the C / M-TW-GW of its reachability address to the C / M functional entity of the XaaS service.

[0369] like Figure 7B As 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.

[0370] 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 facet topology table (which may be included in the BAS / management domain logical topology mentioned above). This C / M facet topology table 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.

[0371] 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.

[0372] It should be understood that, except for the case illustrated above where the C / M-TW-GW connected to the C / M functional entity and the C / M-TW-GW reporting the established connection to the C / M functional entity are the same gateway, the scheme disclosed herein also applies to the case where the C / M-TW-GW connected to the C / M functional entity and the C / M-TW-GW reporting the established connection to the C / M functional entity are different gateways.

[0373] Figure 7C A schematic flowchart illustrating an exemplary configuration process for a second network element (i.e., C / M-TW-GW) according to one or more embodiments of this disclosure is shown. The first network element is the C / M function of the NET4CON service, the second network element is the C / M-TW-GW in NET4CON, and the third network element is the Data-TW-GW in NET4CON. The prerequisites for configuring the C / M-TW-GW to be configured 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 this establishment can be achieved as follows: Figure 7BThe 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.

[0374] 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 XaaS service deployment configuration file (or the aforementioned XaaS service deployment configuration file) 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 XaaS service authorization configuration file includes the following information: XaaS service ID, provider ID, its authorized consumer IDs, and the IDs of the XaaS services provided by these consumers.

[0375] 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).

[0376] 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.

[0377] 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.

[0378] like Figure 7C As 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.

[0379] CONET (a specific example of the sixth network element mentioned above) first sends message 1 (a specific example of the first configuration file mentioned above) 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 first configuration file mentioned above). 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.

[0380] It should be understood that, apart from the case illustrated above where the C / M-TW-GW connected to CONET and the C / M-TW-GW to be configured are the same gateway, the solution disclosed herein also applies to cases where the C / M-TW-GW connected to CONET and the C / M-TW-GW to be configured are different gateways.

[0381] In one implementation of this disclosure, a second network element is used to send a first load report to a first network element, wherein the first load report indicates the load traffic processed by the second network element; the first network element is used to receive the first load report from the second network element. The first load report reflects the load status of one or more C / M-TW-GWs, therefore, by having the C / M-TW-GW report the first load report, the load status of the C / M-TW-GW can be tracked.

[0382] In one implementation of this disclosure, the first network element is used to set the timing for the second network element to report the first load report.

[0383] For example, the C / M function can receive load reports from each C / M-TW-GW it controls and manages. Each C / M-TW-GW automatically or in response to instructions from the C / M function, or based on a specific timing, continuously or periodically reports its load traffic. Such timing includes, but is not limited to: reporting load traffic at regular intervals, and continuously or periodically reporting load traffic when it is greater than or less than a preset value. This timing can be configured by the first network element or predefined. Because the timing of load report reporting can be set by the first network element or predefined, load reports can be flexibly reported according to actual applications.

[0384] In one implementation of this disclosure, when there is more than one second network element, i.e., when at least one second network element includes two or more second network elements, the first network element may reselect a second network element based on a first load report from these second network elements. The first network element is used to select another second network element from the two or more second network elements based on the first load report from the two or more second network elements. In this way, the first network element (such as a C / M function used as a controller) can obtain the load report of each second network element (such as a 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 a preset threshold, thereby efficiently managing and controlling the C / M-TW-GW and saving system overhead.

[0385] For example, after receiving the load traffic of the configured C / M-TW-GW (i.e., the second 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 second network element and sending information specific to the other second network element) 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 fourth network element, and the connection between the fourth network element and another second network element. In another implementation, after the C / M function sends the configuration information corresponding to another C / M-TW-GW (the information in the first configuration file mentioned above) 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. In this way, load balancing maintenance can be implemented by the first network element.

[0386] In one possible implementation, the first network element is used to: obtain a second configuration file; and configure a third network element based on the second configuration file. The second configuration file includes at least one of the third network element's task configuration file or the reachable address of the fifth network element. The task configuration file instructs the third network element to execute actions within a task, and the reachable address of the fifth network element establishes a connection between the third and fifth network elements. In another possible implementation, the first network element can be a C / M function as described above, the third network element can be a Data-TW-GW to be configured, and the fifth network element can be a data function entity of an XaaS service within the BAS domain. It can also be a network element that executes actions immediately following the third network element upon completion of a task (e.g., triggered by the MM service). The C / M function controls and manages the logical connection between the data function entity and the Data-TW-GW to be configured, and also configures the Data-TW-GW to be configured. Here, the reachable address of the fifth network element can be its reachable physical address, such as its ID, or other forms, as long as other network elements can access it. The task configuration file can come from the MM service. A third network element is a network element that completes the task issued by the MM service. This completion may require multiple third network elements. In this case, the second configuration file (explained later; a concrete example is the task session configuration configuration file) can include the task configuration files of all the third network elements required to complete the task. Each third network element can be configured in the same way. In this case, the task configuration file of each third network element is used to instruct that third network element to execute actions in the task. The task is to achieve a specified goal, called the task objective. This goal includes providing packet data unit (PDU) connectivity and providing data processing. A task can include one or more actions, such as AI training, AI inference, data preprocessing, data de-identification, data cleaning, data collection, data analysis, and perception.

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

[0388] In one implementation of this disclosure, the second configuration file includes the reachable address of the fifth network element; the third network element receives the second configuration file from the sixth network element connected to the third network element and forwards the second configuration file to the first network element; the first network element receives the second configuration file from the third network element. For example, the sixth network element is a confederation network (CONET), which stores the reachable address of the fifth network element and the authorization configuration file of the fifth network element.

[0389] In one implementation of this disclosure, the second configuration file includes the reachable address of the fifth network element, and the first network element receives the second configuration file from the first basic service to which the fifth network element belongs. In another implementation, the first network element receives a registration message from the first basic service, wherein the registration message indicates the second configuration file. Specifically, the registration message is sent to the first network element through the first basic service to which the fifth network element belongs.

[0390] In addition, the reachable address of the fifth 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] Based on the above, the first network element can obtain the second configuration file of the fifth network element in multiple ways, and therefore the receiving method of the second configuration file can be flexibly set according to actual needs.

[0392] After obtaining the second configuration file of the fifth network element, the configuration of the third network element can be based on the second configuration file. In one implementation of this disclosure, when at least one third network element includes two or more third network elements, in order to configure the third network element based on the second configuration file, the first network element can first determine the third network element from the two or more third network elements, and then configure the determined third network element based on the information in the second configuration file. That is, the first network element controls and manages two or more third network elements, and after receiving the second configuration file of the fifth network element, the first network element can determine the third network element. For example, the first network element can consider the specific information included in the second configuration file and then select / choose a suitable third network element.

[0393] In one implementation of this disclosure, when the second configuration file includes the reachable address of the fifth network element, the first network element can randomly select a third network element (such as a Data-TW-GW) within the BAS domain, or select a Data-TW-GW as the third 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 third 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 third network element, the first network element can select a Data-TW-GW as the third network element based on the task configuration file and the connection between the data function entity (fifth network element) of the XaaS service located in the same BAS domain as the third network element and the Data-TW-GW. For example, in addition to the first network element and the fifth network element (i.e., the C / M function and the data function entity of the XaaS service in the BAS domain), there are multiple third 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, the actions to be executed by the gateway, the identifier of the next network element (fifth network element) that executes other actions after the third network element, and the identifier used to indicate the second action; since the fifth 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 third 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 third network element and the fifth network element based on the reachable address of the fifth network element; the third network element is configured based on this connection and the task configuration file of the third network element.

[0396] In one implementation of this disclosure, the configuration of the third network element by the first network element based on the second configuration file further includes: the first network element sending information from the second configuration file to the third network element; and the third network element receiving information from the second configuration file from the first network element. The information in the second configuration file can be used for the operation of the third network element. The operation of the third network element can include operations involving the third network element when establishing a connection between the third network element and the fifth network element, as well as the configuration of the third network element, etc. The information in the second configuration file can be some or all of the information in the second configuration file.

[0397] 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 third network element, the quality of service (QoS) parameters of the third network element, an identifier indicating the next network element to perform the second action after the third network element, and an identifier indicating the connection between the third network element and the next network element (such as the fifth network element). For example, the first action could be a decryption or encryption operation when transmitting data packets from a data function entity of an XaaS service to a data function entity (the fifth network element) of another XaaS service, and the second action could be an action by which the fifth network element provides the corresponding service, such as data collection in a NET4DAM service scenario. Alternatively, the first action could be an operation to convert the data format of data packets when transmitting them from a data function entity of an XaaS service to a data function entity (the fifth network element) of another XaaS service, so that data packets from the data function entity of the XaaS service can be parsed or understood by the data function entities of other XaaS services.

[0398] In one implementation of this disclosure, the information in the second configuration file includes an identifier for indicating the quality of service (QoS) parameters of the third network element.

[0399] For example, the third network element is used to perform QoS-oriented and routing-oriented protocol processing based on configurations managed by task management or carried out via a protocol stack. For example, in the latter case, the Data-TW-GW processes the protocol header and performs the corresponding QoS processing and routing operations.

[0400] When the second configuration file only includes the reachable address of the fifth network element, the step of the first network element configuring the third network element based on the second configuration file is the process of establishing a connection between the third and fifth network elements. In this case, the fourth network element can be a data function entity of the consumer XaaS service or a data function entity of the producer XaaS service. When the second configuration file only includes the task configuration file of the third network element, the step of the first network element configuring the third network element based on the second configuration file is the configuration process of the third network element. When the second configuration file includes both the reachable address of the fifth network element and the task configuration file of the third network element, the step of the first network element configuring the third network element based on the second configuration file is the connection and configuration process of the third network element. In the first case, the third network element is used to establish a connection between the third and fifth network elements based on the second configuration file. The configuration of the connection between the third and fifth network elements is as follows: Figure 8A As shown, the specific steps include:

[0401] S801A, the first network element notifies the third network element of the reachable address of the fifth network element; or the first network element notifies the fifth network element of the reachable address of the third network element based on the reachable address of the fifth network element.

[0402] S802A: The third network element establishes a connection between the third network element and the fifth network element based on the reachable address of the fifth network element.

[0403] In S803A, the third network element sends a second notification to the first network element; the first network element receives the second notification from the third network element. The second notification indicates the connection between the third network element and the fifth network element.

[0404] Steps S801A to 803A are similar to steps S701A to 703A above, and the detailed description of steps S801A to 803A will not be repeated here.

[0405] After the connection between the third network element and the fifth network element is established, the third 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 third network element and the fifth network element.

[0406] In S804A, after receiving the second notification, the first network element sends a second acknowledgment to the third network element; the third network element receives the second acknowledgment from the first network element. The second acknowledgment indicates that the second notification has been received.

[0407] In one implementation of this disclosure, both the second notification and the second confirmation include the identifier of the first basic service to which the fifth network element belongs. This allows for secure and reliable information exchange between the first and third network elements.

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

[0409] Figure 8B A schematic flowchart illustrating an exemplary connection process between a third network element and a fifth network element according to one or more embodiments of this disclosure is shown. The third network element is the Data-TW-GW of the XaaS service, and the fifth network element is the data function entity of the XaaS service. The prerequisites for establishing a connection are: one or more Data-TW-GWs within each BAS domain have been deployed; 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 schemes).

[0410] 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 a connection is established between the Data-TW-GW and the data function entities of the XaaS service, this established connection can be notified to the first network element, which can store this information locally, for example, in the aforementioned local BAS domain / infrastructure topology table.

[0411] 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.

[0412] like Figure 8B 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.

[0413] 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 may be included in the BAS / management domain logical topology mentioned above). This data plane topology table 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 second confirmation mentioned above) to the Data-TW-GW to indicate receipt of message 2.1.

[0414] 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.

[0415] It should be understood that although the specification describes the case where the Data-TW-GW connected to the Data Function Entity and the Data-TW-GW reporting the established connection to the C / M function are the same gateway, the scheme disclosed herein also applies to the case where the Data-TW-GW connected to the Data Function Entity and the Data-TW-GW reporting the established connection to the C / M function are different gateways.

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

[0417] 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.

[0418] like Figure 8C 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).

[0419] 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.

[0420] 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 operation, 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 task configuration file for the third network element) to each Data-TW-GW using Message 2.3. The Data-TW-GW receives and stores its own task session table, then sends Message 2.5 to the C / M function in response to Message 2.3. 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.

[0421] It should be understood that although the specification describes the case where the C / M-TW-GW connected to the triggering entity and the C / M-TW-GW connected to the C / M function are the same gateway, the solution disclosed herein also applies to the case where the C / M-TW-GW connected to the triggering entity and the C / M-TW-GW connected to the C / M function are different gateways.

[0422] In one implementation of this disclosure, a third network element sends a second load report to a first network element, wherein the second load report indicates the load traffic processed by the third network element; the first network element receives the second load report from the third network element. The second load report reflects the load status of one or more Data-TW-GWs, therefore, by having the Data-TW-GW report the first load report, the load status of the Data-TW-GW can be tracked.

[0423] In one implementation of this disclosure, the first network element is used to set the timing for the third network element to report the second load report.

[0424] For example, the C / M function can receive load reports from each Data-TW-GW it controls and manages. Each Data-TW-GW automatically or in response to instructions from the C / M function, or based on certain timing, continuously or periodically reports its load traffic. Such timing includes, but is not limited to: reporting load traffic at regular intervals, and continuously or periodically reporting load traffic when it is greater than or less than a preset value. This timing can be configured by the first network element or predefined. Because the timing of load report reporting can be set by the first network element or predefined, load reports can be flexibly reported according to actual applications.

[0425] In one implementation of this disclosure, when multiple third network elements exist, i.e., when at least one third network element includes two or more third network elements, the first network element may reselect a third network element based on second load reports from these third network elements. The first network element is used to select another third network element from the two or more third network elements based on the second load reports from the two or more third network elements. In this way, the first network element (such as a C / M function used as a controller) can obtain the load report of each third network element (such as a 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 a preset threshold, thereby efficiently managing and controlling the Data-TW-GW and saving system overhead. For a detailed description, please refer to the relevant section on reselecting the second network element above.

[0426] In one implementation of this disclosure, the first network element is used to: instruct the second network element to record the interaction between the second network element and the fourth network element; the second network element is used to record the interaction between the second network element and the fourth network element, and report the log results to the first network element. For example, when establishing a connection between C / M-TW-GW (i.e., the second network element) and the C / M functional entity (i.e., the fourth network element) of the XaaS service, the C / M-TW-GW records the following information related to the connection as the log results, such as at least one of the following: the ID of the C / M-TW-GW, the ID of the C / M functional entity connected to the C / M-TW-GW, the ID of the XaaS service to which the C / M functional entity belongs, and the type and parameters of the connection (such as a TLS connection); then, the C / M-TW-GW reports the above information to the C / M function (i.e., the first network element). When C / M-TW-GW is configured, C / M-TW-GW logs the following configuration-related information as a result, such as at least one of the following: the deployment configuration file and authorization configuration file of the XaaS service, and the ID of C / M-TW-GW, wherein the ID indicates the selection of C / M-TW-GW as the service C / M-TW-GW (selected for the C / M function entity (i.e., the fourth network element) of the XaaS service); then, C / M-TW-GW reports the above information to the C / M function (i.e., the first network element).

[0427] For example, the second network element is used to monitor signaling exchanges on the established connection between the second network element and the fourth network element, and also records the signaling exchanges (such as the time of the signaling exchange, the objects involved, and the duration of the signaling exchange (by recording the start and end times)). This monitoring is conducted in compliance with general laws and regulations.

[0428] In one implementation of this disclosure, the second network element records the load it processes and generates a first load report to report to the first network element. Detailed information regarding the first load report can be found in the description above.

[0429] In one implementation of this disclosure, the first network element is used to: instruct the third network element to record the interaction between the third network element and the fifth network element; the third network element is used to record the interaction between the third network element and the fifth network element, and report the log results to the first network element. For example, when establishing a connection between the Data-TW-GW (i.e., the third network element) and the data function entity (i.e., the fifth network element) of the XaaS service, the Data-TW-GW records the following information related to the connection as the log results, such as at least one of the following: 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 type and parameters of the connection (such as a TLS connection); then, the Data-TW-GW reports the above information to the C / M function (i.e., the first network element). When the Data-TW-GW is configured, the Data-TW-GW logs the following configuration-related information as a result, such as at least one of the following: the task configuration file of the data function entity and the ID of the Data-TW-GW, wherein the ID indicates the selection of the Data-TW-GW as the serving Data-TW-GW (selected for the data function entity); then, the Data-TW-GW reports the above information to the C / M function (i.e., the first network element).

[0430] For example, the third network element is used to monitor data exchange on the established connection between the third network element and the fifth network element, and also records the data exchange (such as the time of data exchange, the objects involved, and the duration of the data exchange (by recording the start and end times)). This monitoring is conducted in compliance with general laws and regulations.

[0431] In one implementation of this disclosure, the third network element records the load it processes and generates a second load report to report to the first network element. For details regarding the second load report, please refer to the description above.

[0432] The following describes the operation of the C / M-TW-GW (the aforementioned second network element), which enables interaction between the C / M functional entities of the consumer-side XaaS service and the C / M functional entities of the producer-side XaaS service within the BAS domain where the C / M-TW-GW resides. The prerequisites for the operation of the C / M-TW-GW are as follows: logical connections have been established between the C / M-TW-GW within the BAS domain and the C / M functional entities of the consumer-side XaaS service, as well as between the C / M-TW-GW within the BAS domain and the C / M functional entities of the producer-side XaaS service. For example, these logical connections can be combined with... Figure 7A and Figure 7B as well as Figure 8A and Figure 8B The relevant descriptions are established.

[0433] It should be noted that there may be one or more C / M functional entities (hereinafter referred to as producer network elements) providing producer XaaS services (first basic services) within the BAS domain. In other words, producer XaaS services may have multiple C / M functional entities within the BAS domain, and one or more C / M functional entities belong to producer XaaS services.

[0434] In one implementation of this disclosure, the second network element is used to: receive a first request message from the fourth network element, wherein the first request message indicates the work requested by the fourth network element; and determine a process for implementing the work requested by the fourth network element based on the first request message.

[0435] Here, "work" can be interpreted as performing an action or a series of actions. One or more actions can be performed by one or more network elements (hereinafter referred to as one or more producer network elements) under the control of the accessibility second network element. Each of the one or more network elements can provide basic services, and performing actions is one way for a network element to provide basic services. In this way, by requesting work from the second network element, one or more actions can be performed, and thus the service provision of the fourth network element can be realized based on the result of performing one or more actions. For example, when providing services, the fourth network element may need one or more services from one or more other network elements under the control of the accessibility second network element. The provision of one or more services by one or more other network elements can be realized by performing an action or a series of actions for one or more other network elements. Therefore, the fourth network element can communicate with the second network element to request the performance of one or more actions. Then, the second network element can respond to this request by determining the process for implementing the work (performing one or more actions), thereby facilitating the service provision of the fourth network element.

[0436] In one possible implementation, the second network element can be the C / M-TW-GW as described above, and the fourth network element can be the C / M functional entity of the consumer XaaS service and connected to the second network element. The consumer XaaS service refers to an XaaS service that requests services from one or more producer XaaS services, and the producer XaaS service refers to an XaaS service that provides the services requested by the consumer XaaS service through its C / M functional entity (also referred to herein as the producer network element). In this implementation, the C / M functional entity of the consumer XaaS service sends a first request message to the C / M-TW-GW to request work. The C / M-TW-GW is used to ensure a trusted connection between the C / M functional entities of the consumer XaaS service and the C / M functional entities of the producer XaaS service. For example, when the NET4AI service needs the NET4DAM service to collect data, the NET4AI service is a consumer-side XaaS service, the NET4DAM service is a producer-side XaaS service, and data collection is an action performed by the C / M functional entity of the NET4DAM service to provide the NET4DAM service.

[0437] In one possible implementation, the second network element can be the C / M-TW-GW as described above, and the fourth network element can be a vertical industry located in the same BAS domain as the second network element and connected to the second network element. The vertical industry can request services from one or more other vertical industries (also referred to herein as one or more producer network elements). In this implementation, the vertical industry sends a first request message to the C / M-TW-GW to request work, and the C / M-TW-GW is used to ensure a trusted connection between the vertical industry (the requester) and another vertical industry (the responder).

[0438] In one possible implementation, the first request message can be a request of various types capable of instructing a process for implementing work. To implement the work, the second network element can determine one or more actions to be performed to implement the work. These one or more actions can be performed (implemented) by one or more producer network elements authorized to provide services to the fourth network element. Therefore, the second network element can determine a producer network element to perform each action, and, if multiple producer network elements need to perform actions according to dependencies, determine the order of the producer network elements. This producer network element can be a C / M functional entity of a producer XaaS service connected to the second network element. Therefore, determining the process for implementing the work requested by the fourth network element can include determining one or more actions to be performed to implement the work, one or more producer network elements to perform the one or more actions, and, if necessary, the order of the one or more actions.

[0439] In one possible implementation, the first request message is a first type of message and only includes some information needed to determine the process for implementing the work. The second network element can determine the process for implementing the work based on the first request message and other information stored locally on the second network element.

[0440] For example, the first request message may simply include a work identifier (ID) indicating the process mode. The second network element locally stores information about the correspondence between the process mode, one or more corresponding actions to be executed (and, if necessary, the order of one or more actions), and one or more corresponding producer network elements executing one or more actions. Therefore, the second network element can determine, based on the mode indicated in the first request message and the locally stored information, one or more actions to be executed (and, if necessary, the order of one or more actions) and one or more producer network elements executing one or more actions. Here, the process mode can indicate how to execute the process and also corresponds to the operating mode of the second network element when executing the process. Additionally, the work ID can also be implemented as a message ID; therefore, the first request message may include a message ID used to identify the process mode.

[0441] For example, the first request message may indicate a process pattern and one or more actions to be performed to complete the work (and, if necessary, the order of one or more actions). In this case, the second network element locally stores information about the correspondence between the one or more actions to be performed (and, if necessary, the order of one or more actions) and one or more producer network elements performing one or more actions. As one possible implementation, the second network element can determine one or more producer network elements based on the one or more actions indicated in the first request message and the locally stored information. As another possible implementation, for each of the one or more actions, there may be multiple producer network elements as candidate producer network elements. The second network element can determine the candidate producer network elements based on the one or more actions indicated in the first request message and the locally stored information. Furthermore, the second network element locally stores information about one or more connections between the fourth network element and one or more producer network elements. Therefore, the second network element can determine one or more producer network elements performing one or more actions based on one or more candidate producer network elements and one or more connections between the fourth network element and one or more producer network elements, such as selecting one or more producer network elements connected to the fourth network element.

[0442] For example, the first request message may indicate a process mode and at least one basic service (one or more basic services) requested by the fourth network element. In this case, the second network element stores information locally about the correspondence between the process mode and one or more corresponding actions to be executed (and the order of one or more actions if necessary). Therefore, the second network element can determine one or more actions to be executed (and the order of one or more actions if necessary) to perform the work based on the mode indicated in the first request message and the information stored locally. Furthermore, as mentioned above, the basic service is the producer XaaS service. When the fourth network element requests work from the second network element, it is actually requesting one or more actions to be performed by one or more producer network elements (one or more C / M functional entities of one or more producer XaaS services authorized to provide one or more basic services to the fourth network element). Executing one or more actions enables one or more producer XaaS services to provide one or more basic services. Therefore, when at least one basic service is indicated in the first request message, the fourth network element indicates the one or more services it requires. Since the second network element also stores information locally about the correspondence between the fourth network element (the consumer XaaS service's C / M functional entity) and one or more producer network elements (one or more C / M functional entities of one or more producer XaaS services), the second network element can determine one or more producer network elements providing one or more basic services by executing one or more actions based on at least one basic service requested by the fourth network element and the information stored locally. For example, in the first mode, the actions to be performed to realize the work requested by the fourth network element include data collection, data de-identification, or data analysis provided by the DAM service, which is the first basic service requested by the fourth network element. In the second or third mode, the actions to be performed to realize the fourth network element request include data collection, data de-identification and data analysis provided by the DAM service. These actions also include computation provided by NET4AI. Both the DAM service and NET4AI are the first basic services of the fourth network element request.

[0443] For example, in addition to the work identifier indicating the process mode and at least one basic service requested by the fourth network element, the first request message also includes information about one or more actions to be performed (and, if necessary, the order of one or more actions) to complete the work; the second network element also locally stores information about the correspondence between the fourth network element (the C / M functional entity of the consumer XaaS service) and one or more producer network elements (the C / M functional entities of the producer XaaS service). Therefore, the second network element can determine one or more producer network elements to perform one or more actions based on the first request message and the locally stored information. In possible implementations, one or more producer network elements can be determined based on the correspondence between one or more actions to be performed (and, if necessary, the order of one or more actions) and one or more producer network elements, or based on the correspondence between at least one first basic service requested by the fourth network element and one or more producer network elements.

[0444] In another possible implementation, the first request message is a second type of message and includes all the information needed to determine the process for performing the work. In this case, the second network element can determine the process for performing the work solely based on the first request message. For example, in addition to a work identifier indicating the pattern of the second network element, the first request message also includes one or more actions to be performed to perform the work, and information about one or more producer network elements (such as the ID of the producer network element or other information used to identify the producer network element) that will perform the one or more actions (and, if necessary, the order of the one or more actions) to be performed. In this way, the second network element can determine the one or more actions to be performed to perform the work, and the one or more producer network elements that will perform the one or more actions (and, if necessary, the order of the one or more actions) based on the first request message. The main difference between the first type of message and the second type of message is that the first type of message is not intelligent, so the second network element should use local information to determine the process for performing the work, while the second type of message is intelligent, so the second network element can determine the process for performing the work solely based on the first request message.

[0445] Therefore, there is a balance between the content of the first request message and the function of the second network element. The more information included in the first request message, the less local information the second network element needs to determine the process to implement the work.

[0446] In one possible implementation, the process for performing the work has three modes: mode one, mode two, or mode three. In mode one, the work is performed by executing one action; in mode two, the work is performed by executing multiple independent actions; and in mode three, the work is performed by executing multiple conditional actions.

[0447] Since the process has three modes, the second network element can perform different operations in different modes, thereby effectively managing the interaction between the second network element and the fourth network element.

[0448] In the first mode, only one producer network element participates in responding to the first request message from the fourth network element. The first request message from the fourth network element only requests one producer network element to perform an action (a single action) to complete the work requested by the fourth network element.

[0449] In both the second and third modes, in one implementation, one or more producer network elements participate in responding to a first request message from a fourth network element. In the second mode, the first request message from the fourth network element requests one or more producer network elements to perform multiple actions to fulfill the work requested by the fourth network element. These multiple actions are independent, and therefore each action can be performed independently by its corresponding producer network element. In the third mode, the first request message from the fourth network element requests one or more producer network elements to perform multiple actions to fulfill the work requested by the fourth network element. These multiple actions are dependent, so one action to be performed by a producer network element depends on the execution result of another action. In this implementation, each producer network element can perform one or more of the multiple actions.

[0450] Figures 9A to 9C Three operating modes of the second network element are illustrated, namely the three modes of C / M-TW-GW. In this mode, the C / M functional entity of the consumer XaaS service and the C / M functional entity of the producer XaaS service are both connected to the C / M-TW-GW, such as through an external interface (e.g., 6G-C / M-1 shown in the figure).

[0451] Mode 1 - Single Action

[0452] In this mode, the C / M-TW-GW receives a message (a specific example of the first request message mentioned above) from a C / M functional entity of a consumer XaaS service. This message requests a single action. After some processing by the C / M-TW-GW, the message is forwarded to the selected producer XaaS service. After the producer XaaS service's C / M functional entity performs the action, it sends a response message with the result back to the C / M-TW-GW. After some processing, the C / M-TW-GW sends a response message to the consumer XaaS service's C / M functional entity.

[0453] Mode 2 - Multiple independent actions (in parallel)

[0454] In this mode, C / M-TW-GW receives a message (a specific example of the first request message mentioned above) from a C / M functional entity of a consumer XaaS service. This message requests multiple concurrent actions from other producer XaaS services. After some processing by C / M-TW-GW, the message is forwarded to several selected producer XaaS services. After the C / M functional entities of the producer XaaS services execute multiple concurrent individual actions, multiple response messages with results from the various C / M functional entities of these producer XaaS services are sent back to C / M-TW-GW. After all actions are completed, C / M-TW-GW sends a single response message to the C / M functional entity of the consumer XaaS service after some processing.

[0455] Pattern 3 - Multiple dependent actions (condition order)

[0456] In this mode, the C / M-TW-GW receives a message (a specific example of the first request message mentioned above) from a C / M functional entity of a consumer XaaS service. This message requests multiple sequential (dependent) actions from other producer XaaS services. After some processing by the C / M-TW-GW, it executes a single-action flow (Mode 1) based on the message type and content. After completing all actions, the C / M-TW-GW sends a single response message to the consumer XaaS service.

[0457] In one possible implementation of this disclosure, the third network element is used to process the data format of the data packets during transmission. For example, the third network element receives data packets from network elements (such as data function entities), checks whether the data format of the data packets is consistent with the data format of other network elements (such as data function entities) to which the data packets arrive. If they are inconsistent, the third network element converts the data format of the data packets to the data format of the other data function entities and then passes the data packets to those other data function entities. For example, the data processing result from a data function entity of an XaaS service is included in a data packet, which is then sent from the XaaS service's data function entity to the third network element. Before forwarding the data packet to the next XaaS service's data function entity to complete the task, the third network element can perform data format conversion (in cases where the data formats of the two data function entities are different) and send the converted data packet to the next XaaS service's data function entity to ensure that the next XaaS service's data function entity can understand or parse the data packet.

[0458] In one possible implementation of this disclosure, the third network element is used to perform at least one of decryption or encryption operations when transmitting data packets. For example, upon receiving a data packet, the third network element can first decrypt the data packet and then encrypt it before transmitting it, thereby ensuring the security of data packet transmission.

[0459] In one possible implementation of this disclosure, the first network element is communicatively connected to the seventh network element and is used to coordinate process and data packet exchange on the data plane with the seventh network element. For example, the seventh network element can be a C / M function within another BAS domain, and C / M functions in different BAS domains can communicate directly through their interfaces. The process here may include exchanging topology information within the network element's own BAS domain, thereby achieving load balancing for the entire system.

[0460] In one possible implementation of this disclosure, the first network element is used to: obtain a third configuration file, wherein the third configuration file includes the reachable addresses of the eighth and ninth network elements controlled by the seventh network element, the reachable address of the eighth network element is used to establish a connection between the second network element and the eighth network element, and the reachable address of the ninth network element is used to establish a connection between the third network element and the ninth network element; configure the second and eighth network elements to establish a connection between the second and eighth network elements; and configure the third and ninth network elements to establish a connection between the third network element and the ninth network element. The eighth and ninth network elements can be C / M-TW-GW and Data-TW-GW in a BAS domain different from the BAS domain of the second and third network elements (i.e., the BAS domain where the seventh network element is located), respectively. Different C / M-TW-GWs in different domains can be connected according to their reachable addresses, and different Data-TW-GWs in different domains can also be connected according to their reachable addresses.

[0461] The following details the management of C / M sessions and data sessions for devices and D-Users (digital users, which can be in NET4DW, etc.). A C / M session can be a secure logical connection established between a 6G device / D-User and its serving C / M-TW-GW, used for signaling exchange on the C / M plane. The serving C / M-TW-GW is the network-side endpoint of the device's C / M session. A data session can be a secure logical connection established between a 6G device / D-User and its serving Data-TW-GW, used for data exchange on the data plane. The serving Data-TW-GW is the network-side endpoint of the device's data session. The device can be a wireless device capable of connecting to a 6G system and using authorized 6G and 5G services. The prerequisites for establishing a C / M session are: the BAS domain logical topology has been established; and the C / M radio bearer (RB) of the device establishing the C / M session has been established. The prerequisites for establishing a data session are: the BAS domain logical topology has been established; and the device's data RB and C / M RB have been established. C / M RB refers to the air connection that carries control signaling and C / M plane messages used for air interface management. The device may have multiple C / M RBs. The device's data RB refers to the air connection that carries data plane traffic. The device may have multiple data RBs.

[0462] The D-User represents the physical user using the primary device. Therefore, the digital user can subsequently handle events on behalf of the physical user, reducing the physical user's processing load. For example, when a call comes in, the D-User's anchor can communicate with the operator to determine if the call is valid. If it is not (e.g., a spam call), the anchor can directly reject the call. This entire process is completely transparent to the physical user, who no longer needs to operate the primary device, thus improving the user experience. Furthermore, digital functions can be pre-trained to handle most of the physical user's tasks. Therefore, the physical user can determine the scope of the digital user's authority to handle events on their behalf and train the anchor accordingly, providing greater flexibility in configuring anchors for the user. Establishing a C / M session for a D-User (anchor) can be similar to establishing a session for the first device, and establishing a data session for a D-User (anchor) can also be similar to establishing a session for the first device. The difference is that neither the C / M session nor the data session for a D-User involves any process related to establishing a C / M RB, and all notifications / requests / responses / acknowledgments (if any) involved in the establishment of the first session can be used in the same way to establish the third session, but excluding the indications of the first bearer.

[0463] To ensure the proper functioning of the digital functions, sessions similar to the first and second sessions described above are required. In one possible implementation of this disclosure, one or more third sessions are established between the digital functions associated with the first device and the corresponding service C / M-TW-GW. Each of the one or more third sessions is used to implement signaling exchange between the digital functions and the corresponding service C / M-TW-GW on the control and management plane. One or more fourth sessions are established between the digital functions associated with the first device and the corresponding service Data-TW-GW. Each of the one or more fourth sessions is used to implement data exchange between the digital functions and the corresponding service Data-TW-GW on the data plane.

[0464] In one possible implementation of this disclosure, the first network element is used to: receive a first session establishment request, wherein the first session establishment request indicates a first device to establish a first session; and configure a second network element based on the first session establishment request to establish a first session between the first device and the second network element. The first device may be the aforementioned wireless device, the first session may be the C / M session of the aforementioned first device, and the second network element may be the serving C / M-TW-GW of the first device. The first session establishment request can be considered a triggering condition for the establishment of the first session. After receiving the first session establishment request, the first network element can begin configuring the second network element. The configuration process will vary depending on the content of the first session establishment request.

[0465] In one possible implementation of this disclosure, the first session establishment request includes the identifier of the first device, such as the ID of the first device, which is not limited in this embodiment.

[0466] In one possible implementation of this disclosure, a first network element is used to receive a first session establishment request from a first service. The first service may be a connectivity management (CM) service that utilizes 5G connectivity management functions, but is extended to include the digital world. The first network element is also used to send a first session establishment response to the first service in response to the first session establishment request. The first session establishment response indicates a first device. For example, the first session establishment response may also include the ID of the first device. This disclosure does not limit this aspect.

[0467] In one possible implementation of this disclosure, the first session establishment request indicates the tenth network element and the first bearer corresponding to the first session. The first mapping relationship between the first bearer and the first session of the first device is maintained by the tenth network element, and the first bearer is established between the first device and the tenth network element. When the first network element receives the first session establishment request from the first service, that is, when the first session establishment of the first device is triggered by the first service (such as the CM service), the first service needs to establish a connection between the first device and the tenth network element through the first bearer before triggering the first session establishment. The first bearer can be the C / M RB of the first device, and the tenth network element can be the RB processor, that is, the air interface protocol stack processor. The RB processor is defined as a logical function that performs RB protocol stack operations after obtaining the configuration. The protocol stack processor is either a PDCP-only processor or a complete protocol stack processor. The RB processor receives RB configuration from the connectivity management (CM) service. The RB processor also receives security configuration, such as key materials, from the service provisioning management (SPM) service. Before triggering the first session establishment, the first service knows the first bearer and the tenth network element, and therefore can inform the first network element of the first bearer and the tenth network element through the first session establishment request. In one possible implementation, the first session establishment request may include the ID of the first bearer and the ID of the tenth network element.

[0468] In one possible implementation of this disclosure, the first network element is configured to receive a first session establishment request from a first device or another network element; the first network element is further configured to send a second session establishment response to the first device or another network element in response to the first session establishment request, wherein the second session establishment response indicates the first device, for example, the second session establishment response includes the ID of the first device, and this disclosure does not limit this.

[0469] The other network element can be a device other than the first device that establishes the first session. In other words, the establishment of the first session can also be triggered by different devices. Such devices are unaware of the first bearer and the tenth network element. Therefore, when the establishment of the first session is triggered by such a device, it is similar to the case where the establishment of the first session is triggered by the first device. It is also necessary to interact with the first service (CM service) to obtain the confirmation of the first bearer and the tenth network element.

[0470] In one possible implementation of this disclosure, the first network element is further configured to: send a first bearer request to a first service, wherein the first bearer request requests a tenth network element and a first bearer corresponding to a first session, and the first bearer request indicates a first device; receive a first bearer response from the first service, wherein the first bearer response indicates a tenth network element and a first bearer corresponding to the first session, a first mapping relationship between the first bearer and the first session of the first device is maintained by the tenth network element, and the first bearer is established between the first device and the tenth network element. In one possible implementation, the indication from the first device is sufficient to inform the first service that the first network element wants to know about the first bearer and the tenth network element. In another possible implementation, the first bearer request may also carry other information indicating that the first network element wants to know about the first bearer and the tenth network element. When a first network element receives a first session establishment request from a first device or another network element—that is, when the first session establishment of the first device is triggered by the first device or another network element—after receiving the first session establishment request, the first network element can communicate with the first service regarding the established first bearer and the corresponding tenth network element. Alternatively, after receiving the first session establishment request, the first network element can request the first service to establish a first bearer and notify the first network element of the established first bearer and tenth network element. Then, the first network element obtains information about the first bearer and tenth network element based on the first bearer response. For example, the C / M function obtains the ID of the first bearer and the ID of the tenth network element from the CM service. It should be noted that, throughout the entire text, although the embodiments of this disclosure do not limit the number of first bearers established for the first device, one or more bearers can exist to implement signaling exchange between the tenth network element and the first device on the control and management plane.

[0471] The first network element and the second network element are located in the same BAS domain. In practical applications, the first network element and the second network element can be located in different BAS domains. The following will describe in detail the case where the first network element and the second network element are located in the same BAS domain. However, it should be noted that the solution disclosed herein is also applicable to the case where the first network element and the second network element are located in different BAS domains.

[0472] As mentioned above, the second network element is the service C / M-TW-GW, which can be determined in the following way.

[0473] In one possible implementation of this disclosure, in order to determine the second network element based on the first session establishment request, the first network element is used to: obtain the current location of the first device and the motion prediction result of the first device based on the first session establishment request; and determine the second network element based on the current location of the first device and the motion prediction result of the first device.

[0474] In one possible implementation of this disclosure, the first network element is used to: obtain the current location of the first device and the motion prediction result of the first device from the first service based on the first session establishment request. The first device may be a mobile device, and the first service (such as a CM service) may obtain the current location and motion prediction result (such as movement speed and movement direction) of the first device, and may predict the location of the first device in the next few seconds, minutes or hours, without limitation.

[0475] In one possible implementation of this disclosure, when the establishment of the first session of the first device is triggered by the first service, the first session establishment request may also indicate the current location and mobility prediction result of the first device; the first network element may be used to directly obtain the current location and mobility prediction result of the first device from the first session establishment request, and determine the second network element based on the current location and mobility prediction result of the first device; for example, the first network element selects the C / M-TW-GW closest to the first device in real time within the BAS domain where the first network element is located as the second network element (i.e., the service C / M-TW-GW).

[0476] In one possible implementation of this disclosure, when the establishment of a first session for a first device is triggered by a first service and the first session establishment request does not carry information about the current location and mobility prediction results of the first device, after receiving the first session establishment request, the first network element performs the following actions: sends a request to the first service; obtains the current location and mobility prediction results of the first device based on the response, wherein the response carries information about the current location and mobility prediction results of the first device and corresponds to the request; and then determines a second network element based on the obtained current location and mobility prediction results of the first device. For example, the first network element selects the C / M-TW-GW closest to the first device in its BAS domain in real time as the second network element (i.e., the service C / M-TW-GW). It should be noted that when the first session establishment request includes multiple different contents for indicating multiple different information, these multiple contents can be indicated separately in multiple request / response messages, or they can be indicated together in one request / response message.

[0477] In one possible implementation of this disclosure, when the establishment of a first session for a first device is triggered by the first device or another network element, after receiving a first session establishment request from the first device or another network element, the first network element is used to: send a request to a first service; obtain the current location and mobility prediction result of the first device based on the response of the first service, wherein the response carries information about the current location and mobility prediction result of the first device and corresponds to the request; and then determine a second network element based on the obtained current location and mobility prediction result of the first device; for example, the first network element selects the C / M-TW-GW closest to the first device in the BAS domain where the first network element is located as the second network element (i.e., the service C / M-TW-GW) in real time. In one possible implementation, the first network element can be used to send the request for obtaining the current location and mobility prediction result together with the aforementioned first bearer request to the first service, or send them separately to the first service, and this disclosure does not limit this.

[0478] In one possible implementation of this disclosure, to determine a second network element based on a first session establishment request, the first network element is configured to: determine the second network element based on the first session establishment request and the capabilities of the network elements managed by the first network element. In this case, the first session establishment request is considered a trigger condition for determining the second network element. Therefore, upon receiving the first session establishment request, the first network element can consider the capabilities of the managed network elements to determine a suitable second network element. Information related to the capabilities of the network elements managed by the first network element can be stored locally on the first network element or in other network elements connected to the first network element, enabling the first network element to acquire the capabilities of the network elements managed by the first network element. The network element managed by the first network element can be a C / M-TW-GW managed by the C / M function. For example, the capability of the network element managed by the first network element can be the traffic load of the C / M-TW-GW. The first network element can select the C / M-TW-GW with the smallest traffic load as the serving C / M-TW-GW. Alternatively, the capability of the network element managed by the first network element can be the distance between the C / M-TW-GW and the first network element. The first network element can select the nearest C / M-TW-GW as the serving C / M-TW-GW. It should be understood that the above selection criteria are only for illustrative purposes and should not be construed as limiting the embodiments of this disclosure.

[0479] In one possible implementation of this disclosure, in order to determine the second network element based on the first session establishment request, the first network element is configured to: determine the second network element based on the current location and mobility prediction results of the first device and the capabilities of the network elements managed by the first network element. In one possible implementation, the first network element first determines multiple candidate C / M-TW-GWs based on the obtained current location and mobility prediction results of the first device, and then selects one C / M-TW-GW from the multiple candidate C / M-TW-GWs as the serving C / M-TW-GW based on the capabilities of the multiple candidate C / M-TW-GWs. In another possible implementation, the first network element first determines multiple candidate C / M-TW-GWs based on the capabilities of the C / M-TW-GWs managed by the first network element, and then selects one C / M-TW-GW from the multiple candidate C / M-TW-GWs as the serving C / M-TW-GW based on the obtained current location and mobility prediction results of the first device.

[0480] The following section describes in detail the configuration of the second network element to establish a first session between the first device and the second network element.

[0481] In one possible implementation of this disclosure, in order to configure the second network element, the first network element is configured to: determine the tenth network element and the first bearer corresponding to the first session based on the first session establishment request; allocate the first session between the first device and the second network element; and send a third notification to the second network element, wherein the third notification indicates the first device, the first bearer, the first session, and the tenth network element. Here, allocating the first session can, for example, be done by giving an ID to uniquely identify the first session.

[0482] In one possible implementation, when the establishment of the first session of the first device is triggered by the first service, as described above, the first session establishment request may indicate the first bearer and the tenth network element. Therefore, the first network element can be used to directly determine the third network element and the first bearer corresponding to the first session based on the first session establishment request. In another possible implementation, when the establishment of the first session of the first device is triggered by the first device or another network element, as described above, the first network element can be used to obtain the first bearer response based on the first bearer request triggered by the first session establishment request, and then determine the tenth network element and the first bearer corresponding to the first session based on the first bearer response. In another possible implementation, the third notification is used to notify the second network element of the selection of the second network element as the service C / M-TW-GW, and may include the ID of the first device, the ID of the first bearer, the ID of the first session, and the ID of the tenth network element.

[0483] In one possible implementation of this disclosure, after the first network element sends a third notification (which could be a possible implementation of a first session establishment notification) to the second network element, the second network element is configured to: receive the third notification from the first network element and send a fourth notification to the tenth network element based on the first session establishment notification, wherein the fourth notification indicates a first mapping relationship between the first device, the second network element, and the first bearer and the first session of the first device. Then, the tenth network element creates a mapping relationship between the first device, the first bearer, the first session, and the second network element based on the fourth notification received from the second network element.

[0484] In one possible implementation of this disclosure, the second network element is configured to receive a third acknowledgment from the tenth network element, wherein the third acknowledgment indicates that a fourth notification has been received. The third acknowledgment may include any information responding to the fourth notification (such as the ID of the first device), provided that the third acknowledgment corresponds to the fourth notification message and the second network element receives confirmation of receiving the fourth notification.

[0485] In one possible implementation of this disclosure, the second network element sends a fifth notification to the second service, wherein the fifth notification indicates the first device, the second network element, the service identifier of the second network element, and the first session. The second service may be a service provisioning management (SPM) service, which provides the ability to control and manage customer access to 6G services and provide requested services. The second network element sends the fifth notification to the SPM service to securely activate the first session of the first device. The SPM service can obtain the service identifier and the second network element based on the interface through which it receives the fifth notification from the second network element, wherein the service identifier may be the ID of the BAS domain in which the second network element resides.

[0486] In one possible implementation of this disclosure, the second network element is configured to receive a fourth acknowledgment from the second service, wherein the fourth acknowledgment indicates that a fifth notification has been received. The fourth acknowledgment may include any information responding to the fifth notification (such as the ID of the first device and the ID of the first session), as long as the fourth acknowledgment corresponds to the fifth notification and the second network element receives confirmation of receipt of the fifth notification.

[0487] In one possible implementation of this disclosure, both the fifth notification and the fourth confirmation include the identifier of the first device and the identifier of the first session.

[0488] In one possible implementation of this disclosure, a first network element receives a first update request from an eleventh network element, wherein the first update request indicates a first device, a second network element, the service identifier of the second network element, and a first session; and updates a first local record based on the first update request, wherein the first local record includes a mapping relationship between the service identifiers of the first device, the second network element, and the first session. The eleventh network element is a C / M-TW-GW within the BAS domain where the first network element is located, and is used to forward the first session establishment request from the first service, the first device, or another network element to the first network element. In one possible implementation, when the first network element determines that the service C / M-TW-GW is located within its BAS domain and the eleventh network element connected to the first service is exactly the service C / M-TW-GW, the eleventh network element can be the service C / M-TW-GW (the second network element), i.e., later as... Figure 10A and Figure 10B As shown in the diagram. In addition, as mentioned above, the first network element is also aware of the tenth network element and the first bearer. Therefore, the first local record can be a mapping relationship between the first device, the second network element, the service identifier of the second network element, the first session, the tenth network element, and the first bearer corresponding to the first session.

[0489] In this way, by using the first session establishment request, the first network element can determine the first device, the first session of the first device, the second network element (i.e., service C / M-TW-GW), and the BAS domain to which the second network element belongs; based on the information determined above, the second network element is configured; therefore, the first session of the first device can be established, thereby ensuring the information transmission of the first device on the control and management plane. In addition, the information related to the establishment of the first session can be updated to the second service (i.e., SPM service) to protect the first session, and updated to the first service (i.e., CM service) to record the information related to the establishment of the first session.

[0490] Figure 10A An exemplary flowchart is shown for establishing a first session for a first device in the following circumstances: the first network element and the second network element are located in the same BAS domain, and the first session of the first device is triggered by a first service; the method includes the following steps.

[0491] S1001A, the first network element receives the first session establishment request from the first service. Refer to the implementation described above.

[0492] S1002A, the first network element determines the second network element based on the first session establishment request. The method for determining the second network element can be found in the implementation described above.

[0493] S1003A, the first network element determines the tenth network element and the first bearer corresponding to the first session based on the first session establishment request; and allocates the first session between the first device and the second network element.

[0494] S1004A, the first network element sends a third notification to the second network element, and the second network element receives the third notification.

[0495] S1005A, the second network element sends a fourth notification to the tenth network element based on the third notification.

[0496] S1006A, the tenth network element creates a mapping relationship between the first device, the first bearer, the first session, and the second network element based on the fourth notification.

[0497] S1007A, the second network element receives the third confirmation from the tenth network element.

[0498] S1008A, the second network element sends the fifth notification to the second service.

[0499] S1009A, the second service securely activates the first session based on the received seventeenth notification.

[0500] S1010A, the second network element receives a fourth confirmation from the second service, wherein the fourth confirmation indicates that a fifth notification has been received.

[0501] S1011A, the first network element receives the first update request; when the eleventh network element used to forward the first session establishment request from the first service is the service C / M-TW-GW (i.e., the second network element), the first network element receives the first update request from the second network element; when the eleventh network element is not the service C / M-TW-GW, the first network element receives the first update request from the second network element, and the latter case is as follows: Figure 10A As shown.

[0502] S1012A, the first network element updates the first local record based on the first update request, wherein the first local record includes the mapping relationship between the first device, the second network element, the service identifier of the second network element, and the first session.

[0503] S1013A, the first network element sends a first session establishment response to the first service through the eleventh network element.

[0504] S1014A, the first service creation includes an entry for the first device, the service identifier of the second network element, the first session, and the second network element, such as an entry in a configuration file. This disclosure embodiment does not limit this.

[0505] For possible implementations of the third notification, fourth notification, third confirmation, fifth notification, and first session establishment response, please refer to the above description.

[0506] In one possible implementation of this disclosure, the C / M session established for the D-User (anchor) can be with Figure 10AThe establishment of the first device session is similar, except that: establishing a C / M session does not involve any process related to establishing a C / M RB (i.e., the first bearer mentioned above), and all notifications / requests / responses / acknowledgments (if any) involved in the establishment of the first session can be used in the same way to establish a C / M session for the D-User, but does not include the indication of the first bearer.

[0507] Figure 10B An exemplary flowchart is shown for establishing a first session for a first device in the following situation: the first network element and the second network element are located in the same BAS domain, and the session is triggered by the first device or another network element; the method includes the following steps.

[0508] S1001B, the first device or another network element sends a first session establishment request to the first network element, and the first network element receives the first session establishment request from the first device or another network element.

[0509] S1002B, the first network element sends a first bearer request to the first service, wherein the first bearer request is used to request the tenth network element and the first bearer corresponding to the first session, and the first bearer request indicates the first device.

[0510] S1003B, the first network element receives the first bearer response from the first service. The above implementation method can be referenced.

[0511] Steps S1004B to S1014B are the same as steps S1002A to S1012A, and will not be repeated here.

[0512] S1015B, the first network element sends a second session establishment response to the first device or another network element.

[0513] S1016B, the first network element sends a notification to the first service, wherein the notification indicates the service identifiers of the first device and the second network element, the first session, and the second network element. In this case, although the establishment of the first session is triggered by the first device or another network element, the first network element still notifies the first service that the first session has been established.

[0514] S1017B, the first service creation includes the service identifier of the first device and the second network element, the first session, and the second network element's entry, such as an entry in a configuration file. This disclosure embodiment does not limit this.

[0515] In one possible implementation of this disclosure, establishing a C / M session for the D-User (the aforementioned third session) can be done with... Figure 10BThe establishment of the first device session is similar to that shown, except that: establishing a C / M session does not involve any process related to establishing a C / M RB (i.e., the first bearer mentioned above), and all notifications / requests / responses / acknowledgments (if any) involved in the establishment of the first session can be used in the same way to establish a C / M session for the D-User, but does not include the indication of the first bearer.

[0516] To better manage device / D-User (anchor) access to the 6G system, the following describes device data sessions. The prerequisites for establishing a data session are: the BAS domain logical topology has been established; and the device's data RB and C / M RB have been established.

[0517] In one possible implementation of this disclosure, the first network element is used to: receive a second session establishment request, wherein the second session establishment request indicates a first device to establish a second session; and configure a third network element based on the second session establishment request to establish a second session between the first device and the third network element. The first device may be the aforementioned wireless device, the second session may be a data session of the aforementioned first device, and the third network element may be the service Data-TW-GW of the first device. The second session establishment request can be considered a triggering condition for the establishment of the first session. After receiving the second session establishment request, the first network element can begin configuring the third network element. The configuration process will vary depending on the content of the second session establishment request.

[0518] In one possible implementation of this disclosure, the second session establishment request includes the identifier of the first device, such as the ID of the first device, which is not limited in this embodiment of the disclosure.

[0519] In one possible implementation of this disclosure, the first network element is used to receive a second session establishment request from a third service. The third service may be a mission management (MM) service, which provides the ability to program the provision of XaaS services in the service layer to provide mission services. The first network element is also used to send a third session establishment response to the third service in response to the second session establishment request. The third session establishment response indicates the first device. For example, the third session establishment response may also include the ID of the first device. This disclosure does not limit this aspect.

[0520] In one possible implementation of this disclosure, the second session of the first device may be assigned by a third service (such as the MM service) or by a C / M function (the aforementioned first network element or seventh network element) located in the same BAS domain as the service Data-TW-GW, where the service Data-TW-GW is the network-side endpoint of the second session of the first device. Here, assigning the second session may, for example, involve providing an ID to uniquely identify the second session.

[0521] When the first network element receives a second session establishment request from the third service, i.e., when the second session establishment of the first device is triggered by the third service, the second session establishment request can also indicate the tenth network element and the second bearer corresponding to the second session. The second mapping relationship between the second bearer and the second session of the first device is maintained by the tenth network element, and the second bearer is established between the first device and the tenth network element. Alternatively, in one possible implementation, the third service can request the first service (such as a CM service) to establish a connection between the first device and the tenth network element through the second bearer before triggering the second session establishment. The second bearer can be the data radio bearer (data RB) of the first device, i.e., the over-the-air connection carrying data plane traffic; the first service is the CM service; and the tenth network element can be the RB processor. Since the third service knows the second bearer and the tenth network element before triggering the second session establishment, the second session establishment request can include the ID of the second bearer and the ID of the tenth network element. In another implementation, after receiving the second session establishment request, the first device may request the first service (such as the CM service) to establish a connection between the first device and the tenth network element through the second bearer. In this case, the second session establishment request no longer indicates the tenth network element and the second bearer corresponding to the second session. Instead, the first service may inform the first network element of the tenth network element and the second bearer corresponding to the second session.

[0522] Regarding the indication of the second session, when the first network element receives a second session establishment request from the third service, that is, when the second session establishment of the first device is triggered by the third service, the second session of the first device may have already been allocated by the third service (such as the MM service). Therefore, the second session establishment request can indicate the second session (such as including the ID of the second session).

[0523] The second session establishment request may not necessarily indicate a second session. In one possible implementation, the first network element can confirm with a third service to obtain confirmation of the second session. For example, after receiving the second session establishment request, the first network element can request information about the second session (such as the second session ID) from the third service. For instance, the C / M function requests the ID of the first device's data session from the MM service to establish the first device's data session. In another possible implementation, the second session can be allocated by a C / M function located in the same BAS domain as the service Data-TW-GW. For example, if it is determined that the service Data-TW-GW is located in the same BAS domain as the first network element, the first network element can allocate the second session itself, or it can wait for other network elements (C / M functions) in other BAS domains where the service Data-TW-GW is located to allocate the second session. This implementation will be described in detail later.

[0524] In one possible implementation of this disclosure, the first network element is configured to receive a second session establishment request from the first device or another network element; the first network element is configured to send a fourth session establishment response to the first device or another network element in response to the second session establishment request, wherein the fourth session establishment response indicates the first device, for example, the fourth session establishment response includes the ID of the first device, and this disclosure does not limit this.

[0525] In one possible implementation of this disclosure, when a first network element receives a second session establishment request from a first device or another network element—that is, when the establishment of a second session for the first device is triggered by the first device or another network element—the first network element is configured to: send a session request to a third service, wherein the session request indicates the first device; and receive a session response from the third service, wherein the session response indicates the second session. After receiving the second session establishment request, the first network element may request information about the second session from the third service. For example, the C / M function may request the ID of the first device's data session from the MM service to establish the first device's data session. In one possible implementation, the second session may be allocated by a C / M function located in the same BAS domain as the service Data-TW-GW. For example, if it is determined that the service Data-TW-GW is located in the same BAS domain as the first network element, the first network element may allocate the second session itself, or it may wait for other network elements (C / M functions) in other BAS domains where the service Data-TW-GW is located to allocate the second session. This implementation will be described in detail later.

[0526] In one possible implementation of this disclosure, the first network element is configured to: send a second bearer request to a first service, wherein the second bearer request requests a tenth network element and a second bearer corresponding to a second session, and the second bearer request indicates the first device; and receive a second bearer response from the first service, wherein the second bearer response indicates the tenth network element and the second bearer corresponding to the second session, a second mapping relationship between the second bearer and the second session of the first device is maintained by the tenth network element, and the second bearer is established between the first device and the tenth network element. In one possible implementation, the indication from the first device is sufficient to inform the first service that the first network element wants to know about the second bearer and the tenth network element. In another possible implementation, the first bearer request may also carry other information indicating that the first network element wants to know about the second bearer and the tenth network element. When a first network element receives a second session establishment request from a first device or another network element—that is, when the second session establishment of the first device is triggered by the first device or another network element—after receiving the second session establishment request, the first network element sends a second bearer request to the first service. One possible implementation is to use the second bearer request to request the establishment of a connection between the first device and the tenth network element through the second bearer, and use the second bearer response as a notification of the second bearer and the tenth network element, so that the first network element can obtain confirmation of the second bearer and the tenth network element. For example, the C / M function obtains the ID of the second bearer and the ID of the tenth network element from the CM service. Another possible implementation is to simply use the second bearer request to request the established second bearer and the corresponding tenth network element. It should be noted that, throughout the entire text, although the embodiments of this disclosure do not limit the number of second bearers established for the first device, one or more bearers can exist to implement signaling exchange between the tenth network element and the first device on the data plane.

[0527] The first network element and the third network element are located in the same BAS domain. In practical applications, the first network element and the third network element can be located in different BAS domains. The following will describe in detail the case where the first network element and the third network element are located in the same BAS domain. However, it should be noted that the solution disclosed in this paper is also applicable to the case where the first network element and the third network element are located in different BAS domains.

[0528] As mentioned above, the third network element is the service Data-TW-GW, which can be determined in the following way.

[0529] In one possible implementation of this disclosure, in order to determine the third network element based on the second session establishment request, the first network element is used to: obtain the current location of the first device and the motion prediction result of the first device based on the second session establishment request; and determine the third network element based on the current location of the first device and the motion prediction result of the first device.

[0530] In one possible implementation of this disclosure, the first network element is used to: obtain the current location of the first device and the motion prediction result of the first device from the first service based on the second session establishment request. The first device may be a mobile device, and the first service (such as a CM service) may obtain the current location and motion prediction result (such as movement speed and movement direction) of the first device, and may predict the location of the first device in the next few seconds, minutes or hours, without limitation.

[0531] In one possible implementation of this disclosure, when the establishment of a second session for the first device is triggered by a third service, the third service can be used to send a request to obtain information about the current location and mobility prediction results of the first device from the first service before triggering the second session establishment (before sending the second session establishment request). This request can be sent to the first service together with or separately from the aforementioned second bearer request. The second session establishment request may include information about the current location and mobility prediction results of the first device. The first network element can be used to directly obtain the current location and mobility prediction results of the first device from the second session establishment request and determine the third network element based on the current location and mobility prediction results of the first device. In another possible implementation, when the establishment of a second session for the first device is triggered by a third service, the first network element can be used to send a request to obtain information about the current location and mobility prediction results of the first device from the third service after receiving the second session establishment request and determine the third network element based on the current location and mobility prediction results of the first device. For example, based on the current location and mobility prediction results of the first device, the first network element can select the Data-TW-GW closest to the first device in the BAS domain where the first network element is located in real time as the third network element (i.e., the service Data-TW-GW).

[0532] In one possible implementation of this disclosure, when the establishment of a second session for the first device is triggered by the first device or another network element, after receiving the second session establishment request from the first device or another network element, the first network element is further configured to: send a request to a first service; obtain the current location and mobility prediction result of the first device based on the response of the first service, wherein the response carries information about the current location and mobility prediction result of the first device and corresponds to the request; determine a third network element based on the obtained current location and mobility prediction result of the first device; for example, the first network element selects the Data-TW-GW closest to the first device in the BAS domain where the first network element is located as the third network element (i.e., the service Data-TW-GW) in real time. In one possible implementation, the first network element may be configured to send the request for obtaining the current location and mobility prediction result together with the aforementioned second bearer request to the first service, or send them separately to the first service; this disclosure does not limit this.

[0533] In one possible implementation of this disclosure, to determine a third network element based on a second session establishment request, the first network element is configured to: determine the third network element based on the second session establishment request and the capabilities of the network elements managed by the first network element. In this case, the second session establishment request is considered a trigger condition for determining the third network element; therefore, upon receiving the second session establishment request, the first network element can consider the capabilities of the managed network elements to determine a suitable third network element. Information related to the capabilities of the network elements managed by the first network element can be stored locally on the first network element or in other network elements connected to the first network element, enabling the first network element to acquire the capabilities of the network elements it manages. The network element managed by the first network element can be a Data-TW-GW managed by the C / M function. For example, the capability of the network element managed by the first network element can be the traffic load of the Data-TW-GW. The first network element can select the Data-TW-GW with the smallest traffic load as the serving Data-TW-GW. Alternatively, the capability of the network element managed by the first network element can be the distance between the Data-TW-GW and the first network element. The first network element can select the nearest Data-TW-GW as the serving Data-TW-GW. It should be understood that the above selection criteria are for illustrative purposes only and should not be construed as limiting the embodiments of this disclosure.

[0534] In one possible implementation of this disclosure, to determine a third network element based on a first session establishment request, the first network element is configured to: determine the third network element based on the current location and mobility prediction results of the first device and the capabilities of the network elements managed by the first network element. In one possible implementation, the first network element first determines multiple candidate Data-TW-GWs based on the obtained current location and mobility prediction results of the first device, and then selects one Data-TW-GW from the multiple candidate Data-TW-GWs as the serving Data-TW-GW based on the capabilities of the multiple candidate Data-TW-GWs. In another possible implementation, the first network element first determines multiple candidate Data-TW-GWs based on the capabilities of the Data-TW-GWs managed by the first network element, and then selects one Data-TW-GW from the multiple candidate Data-TW-GWs as the serving Data-TW-GW based on the obtained current location and mobility prediction results of the first device.

[0535] It should be noted that, given that the service C / M-TW-GW corresponding to the service Data-TW-GW has been determined, the service Data-TW-GW is determined by considering information such as the current location and mobility prediction results of the first device, as well as the capabilities of the Data-TW-GW managed by the first network element.

[0536] The following section describes in detail the configuration of the third network element to establish a second session between the first device and the third network element.

[0537] In one possible implementation of this disclosure, in order to configure the third network element, the first network element is used to: determine the second session, the tenth network element, and the second bearer corresponding to the second session based on the second session establishment request; send a sixth notification to the third network element, wherein the sixth notification indicates the first device, the second bearer, the second session, and the tenth network element; and send a seventh notification to the twelfth network element, wherein the seventh notification indicates the first device, the second bearer, the second session, the tenth network element, and the third network element, and the twelfth network element interacts with the first device on the control and management plane. In one possible implementation, both the third network element and the twelfth network element are controlled by the first network element and are located in the same BAS domain, as will be discussed later. Figure 11A and Figure 11B As shown.

[0538] Regarding the determination of the second session, the tenth network element, and the second bearer corresponding to the second session, the above information can be notified to the first network element, or the first network element can be notified only of the tenth network element and the second bearer corresponding to the second session, while the first network element allocates the second session itself.

[0539] In one possible implementation, when the establishment of a second session by the first device is triggered by a third service, the second session establishment request may or may not indicate a second session. In the former case, the second session establishment request may indicate a second session. As described above, as a possible implementation, the third service may request the first service to obtain the tenth network element and the second bearer corresponding to the second session before triggering the second session establishment. Therefore, the second session establishment request may also indicate the tenth network element and the second bearer corresponding to the second session. Thus, the first network element is used to directly determine the second session, the tenth network element, and the second bearer corresponding to the second session based on the second session establishment request. In another possible implementation, after the first network element receives the second session establishment request from the third service, the first network element is used to: send a request to the third service to obtain confirmation of the second session; send a request to the first service to obtain confirmation of the tenth network element and the second bearer corresponding to the second session; and then determine the second session, the tenth network element, and the second bearer corresponding to the second session based on the responses corresponding to the above two requests.

[0540] In one possible implementation, when the establishment of the second session of the first device is triggered by the third service, but the second session establishment request does not indicate the second session, or when the establishment of the second session of the first device is triggered by the first device or another network element, after receiving the second session establishment request, the first network element sends a request to the third service to obtain confirmation of the second session; sends a second bearer request to the first service to obtain confirmation of the tenth network element and the second bearer corresponding to the second session; and determines the second session, the tenth network element, and the second bearer corresponding to the second session based on the responses corresponding to the above two requests.

[0541] In one possible implementation, when the establishment of a second session for the first device is triggered by a third service, but the second session establishment request does not indicate a second session, or when the establishment of a second session for the first device is triggered by the first device or another network element, the second session can be allocated by a C / M function located in the same BAS domain as the Data-TW-GW service, instead of being notified by the third service. For the second bearer and the tenth network element, the first network element can be used to send a second bearer request to the first service to obtain confirmation of the tenth network element and the second bearer corresponding to the second session, and the tenth network element and the second bearer corresponding to the second session are determined based on the second bearer response corresponding to the second bearer request.

[0542] The sixth notification is used to notify the third network element of the selection of the third network element as the service C / M-TW-GW, and may include the ID of the first device, the ID of the second bearer, the ID of the second session, and the ID of the tenth network element.

[0543] In one possible implementation of this disclosure, after the first network element sends a sixth notification (which could be a possible implementation of a second session establishment notification) to the third network element, the third network element receives the sixth notification. The first network element also sends a seventh notification to the twelfth network element, which receives the seventh notification accordingly. Within the BAS domain where the third network element resides, the twelfth network element interacts with the first device on the control and management plane. The twelfth network element can be the service C / M-TW-TW of the first device. The twelfth network element can be determined in the same way as the method for determining the second network element described in the above implementation, or it can be determined in other ways. Then, the twelfth network element sends an eighth notification to the tenth network element based on the sixth notification. The eighth notification indicates a second mapping relationship between the first device, the sixth network element, and the second bearer and the second session of the first device. The tenth network element creates a mapping relationship between the first device, the second bearer, the second session, and the third network element based on the eighth notification received from the twelfth network element. In one possible implementation, the tenth network element can also store the twelfth network element.

[0544] In one possible implementation of this disclosure, the twelfth network element is configured to receive a fifth acknowledgment from the tenth network element, wherein the fifth acknowledgment indicates that an eighth notification has been received. The fifth acknowledgment may include any information responding to the eighth notification (such as the ID of the first device), provided that the fifth acknowledgment corresponds to the eighth notification message and the twelfth network element obtains confirmation of receiving the eighth notification.

[0545] In one possible implementation of this disclosure, the twelfth network element is used to send a ninth notification to the second service, wherein the ninth notification indicates the service identifiers of the first device, the second session, the third network element, and the third network element. The second service may be a service provisioning management (SPM) service, which provides the ability to control and manage a customer's 6G service access and provide requested services. The twelfth network element is used to send the ninth notification to the SPM service to securely activate the second session of the first device. The SPM service can obtain the service identifier and the twelfth network element based on the interface from which it receives the ninth notification, wherein the service identifier may be the ID of the BAS domain in which the third network element and the twelfth network element reside.

[0546] In one possible implementation of this disclosure, the twelfth network element is configured to receive a sixth acknowledgment from the second service, wherein the sixth acknowledgment indicates receipt of a ninth notification. The sixth acknowledgment may include any information responding to the ninth notification (such as the ID of the first device and the ID of the second session), provided that the sixth acknowledgment corresponds to the ninth notification message and the twelfth network element receives confirmation of receipt of the ninth notification.

[0547] In one possible implementation of this disclosure, both the ninth notification and the sixth confirmation include the identifier of the first device and the identifier of the second session.

[0548] In one possible implementation of this disclosure, the first network element is used to receive a second update request from the eleventh network element, wherein the second update request indicates the service identifier of the first device, the third network element, and the second session; and updates a second local record based on the second update request, wherein the second local record includes the mapping relationship between the service identifiers of the first device, the third network element, and the second session. In one possible implementation, the first network element is used to receive the second update request forwarded by the eleventh network element from the twelfth network element, wherein the eleventh network element is the C / M-TW-GW within the BAS domain where the first network element is located, and is used to forward the second session establishment request from the third service, the first device, or another network element to the first network element. In one possible implementation, when the first network element determines that the service C / M-TW-GW is located within its BAS domain and the eleventh network element connected to the first service is exactly the service C / M-TW-GW, the eleventh network element can be the service C / M-TW-GW (the twelfth network element), i.e., later as... Figure 11A and Figure 11B As shown in the diagram. In addition, as mentioned above, the first network element is also aware of the tenth network element and the second bearer. Therefore, the second local record can be a mapping relationship between the first device, the third network element, the service identifier of the third network element, the second session, the tenth network element, and the second bearer corresponding to the second session.

[0549] In this way, by using the second session establishment request, the first network element can determine the first device, the second session of the first device, and the third network element (i.e., the Data-TW-GW service); based on the determined information, the third network element is configured; therefore, the second session of the first device can be established, thereby ensuring the information transmission of the first device on the data plane. In addition, information related to the establishment of the second session can be updated to the second service (i.e., the SPM service) to protect the second session, and updated to the first service (i.e., the CM service) to record information related to the establishment of the second session.

[0550] Figure 11A An exemplary flowchart is shown for establishing a second session for a first device under the following circumstances: the first network element and the third network element are located in the same BAS domain; the second session of the first device is triggered by a third service; the second session is allocated by a C / M function located in the same BAS domain as the service Data-TW-GW, rather than being notified by the third service; and the third service has already obtained the tenth network element and the second bearer corresponding to the second session from the third service before triggering the establishment of the second session; the method includes the following steps.

[0551] S1101A, the first network element receives the second session establishment request from the third service. The above implementation method can be referenced.

[0552] S1102A, the first network element determines the third network element based on the second session establishment request. The method for determining the third network element can be found in the implementation described above.

[0553] S1103A, the first network element determines the tenth network element and the second bearer corresponding to the second session based on the second session establishment request; and allocates the second session between the first device and the third network element.

[0554] S1104A, the first network element sends the sixth notification to the third network element.

[0555] S1105A, the first network element sends the seventh notification to the twelfth network element, and the twelfth network element receives the seventh notification.

[0556] S1106A, the twelfth network element sends the eighth notification to the tenth network element based on the seventh notification.

[0557] S1107A, the tenth network element creates a mapping relationship between the first device, the second bearer, the second session, and the third network element based on the eighth notification. In one possible implementation, the tenth network element may also record the twelfth network element in the mapping relationship.

[0558] S1108A, the twelfth network element receives the fifth confirmation from the tenth network element.

[0559] S1109A, the twelfth network element sends the ninth notification to the second service.

[0560] S1110A, the second service securely activates the second session based on the received ninth notification.

[0561] S1111A, the twelfth network element receives the sixth confirmation from the second service.

[0562] S1112A, the first network element receives the second update request from the twelfth network element.

[0563] S1113A, the first network element updates the second local record based on the second update request, wherein the second local record includes the mapping relationship between the first device, the third network element, the service identifier of the third network element, and the second session. In one possible implementation, the second local record may also record the twelfth network element.

[0564] S1114A, the first network element sends a third session establishment response to the third service through the twelfth network element in response to the second session establishment request.

[0565] S1115A, the first network element sends a message to the first service through the twelfth network element, wherein the message indicates the first device, the third network element, the service identifier of the third network element, the twelfth network element, and the second session.

[0566] S1116A, the first service creation includes entries for the first device, the service identifier of the third network element, the second session, the third network element, and the twelfth network element, such as entries in a configuration file. This disclosure embodiment does not limit this.

[0567] For possible implementations of the seventh notification, eighth notification, fifth confirmation, ninth notification, sixth confirmation, and third session establishment response, please refer to the above description.

[0568] In one possible implementation of this disclosure, establishing a data session for the D-User (the aforementioned fourth session) can be done with... Figure 11A The establishment of the first device session is similar, except that: establishing a data session does not involve any process related to establishing the data RB (i.e., the second bearer mentioned above), and all notifications / requests / responses / acknowledgments (if any) involved in the establishment of the second session can be used in the same way to establish the D-User data session, but does not include the indication of the second bearer.

[0569] Figure 11B An exemplary flowchart is shown for establishing a second session for a first device in the following circumstances: the first network element and the third network element are located in the same BAS domain, the session is triggered by the first device or another network element, and the second session is assigned by a C / M function located in the same BAS domain as the service Data-TW-GW, rather than being notified by the third service; the method includes the following steps.

[0570] S1101B, the first device or another network element sends a second session establishment request to the first network element; the first network element receives the second session establishment request from the first device or another network element.

[0571] S1102B, the first network element sends a second bearer request to the first service, wherein the second bearer request is used to request the tenth network element and the second bearer corresponding to the first session. Refer to the above implementation method.

[0572] S1103B, the first network element receives the second bearer response from the first service. The above implementation method can be referenced.

[0573] Steps S1104B to S1115B are the same as steps S1102A to S1113A, and will not be repeated here.

[0574] S1116B, the first network element sends a fourth session establishment response to the first device or another network through the twelfth network element in response to the second session establishment request, wherein the fourth session establishment response instructs the first device, and the first device or another network receives the fourth session establishment response from the first network element.

[0575] S1117B, the first network element sends a message to the first service through the twelfth network element, wherein the message indicates the first device, the third network element, the service identifier of the third network element, the second session, and the twelfth network element.

[0576] S1118B, the first service creation includes entries for the first device, the service identifier of the third network element, the second session, the third network element, and the twelfth network element, such as entries in a configuration file, which are not limited in this embodiment of the present disclosure.

[0577] It should be noted that in this example, the twelfth network element is shown as an intermediate network element, used to realize communication between the first network element and the first service or the third service. In addition, other network elements (C / M-TW-GW) different from the twelfth network element may also be used as such intermediate network elements, and this disclosure embodiment does not limit this.

[0578] In one possible implementation of this disclosure, establishing a data session (the aforementioned fourth session) for the digital functions associated with the first device can be done with... Figure 11B The establishment of the first device session is similar, except that: establishing a data session does not involve any process related to establishing the data RB (i.e., the second bearer mentioned above), and all notifications / requests / responses / acknowledgments (if any) involved in the establishment of the second session can be used in the same way to establish the fourth session, but excluding the indication of the second bearer.

[0579] 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.

[0580] 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.

[0581] 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.

[0582] 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.

[0583] 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.

[0584] 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.

[0585] 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 communication system comprising: a first network element, at least one second network element, and at least one third network element, wherein the first network element is communicatively connected with the at least one second network element and the at least one third network element, and is configured to control operations of the at least one second network element and the at least one third network element; a second network element of the at least one second network element is communicatively connected with a fourth network element, and is configured to interact with the fourth network element on a control and management plane; a third network element of the at least one third network element is communicatively connected with a fifth network element, and is configured to interact with the fifth network element on a data plane.

2. The system of claim 1, wherein, the first network element is configured to: obtain a first configuration file of the fourth network element; configure the second network element based on the first configuration file, wherein the first configuration file comprises at least one of a reachable address of the fourth network element or an authorized configuration file of the fourth network element, the reachable address being used to establish a connection between the fourth network element and the second network element, and the authorized configuration file of the fourth network element being used to determine that the fourth network element is able to provide a first base service for a consumer.

3. The system of claim 2, wherein, the first network element is configured to receive the first configuration file from the fourth network element.

4. The system of claim 2, wherein, the second network element is configured to receive the first configuration file from a sixth network element connected with the second network element, and forward the first configuration file to the first network element; the first network element is configured to receive the first configuration file from the second network element.

5. The system of claim 2, wherein, the first network element is configured to receive the first configuration file from a first base service to which the fourth network element belongs.

6. The system of any one of claims 2 to 5, wherein, the first network element is configured to send information in the first configuration file to the second network element; the second network element is configured to receive the information in the first configuration file from the first network element.

7. The system of claim 6, wherein, the second network element is configured to establish the connection between the fourth network element and the second network element based on the information in the first configuration file.

8. The system of any one of claims 1 to 7, wherein, the first network element is configured to: obtain a second configuration file; configure the third network element based on the second configuration file, wherein the second configuration file comprises at least one of a task configuration file of the third network element or a reachable address of the fifth network element, the task configuration file being used to instruct the third network element to perform an action in a task, and the reachable address of the fifth network element being used to establish a connection between the third network element and the fifth network element.

9. The system of claim 8, wherein, the second configuration file comprises the reachable address of the fifth network element, and the first network element is configured to receive the second configuration file from the fifth network element.

10. The system of claim 8, wherein, the second configuration file comprises the reachable address of the fifth network element; the third network element is configured to receive the second configuration file from a sixth network element connected with the third network element, and forward the second configuration file to the first network element; the first network element is configured to receive the second configuration file from the third network element.

11. The system of claim 8, wherein, the second configuration file comprises the reachable address of the fifth network element, and the first network element is configured to receive the second configuration file from a first base service to which the fifth network element belongs.

12. The system of any one of claims 9 to 11, wherein, the first network element is configured to send information in the second configuration file to the third network element; The third network element is configured to receive the information in the second configuration file from the first network element.

13. The system of claim 12, wherein, The third network element is configured to establish the connection between the fifth network element and the third network element based on the information in the second configuration file.

14. The system of any one of claims 1 to 13, wherein, The second network element is configured to send a first load report to the first network element, where the first load report indicates load traffic processed by the second network element. The first network element is configured to receive the first load report from the second network element.

15. The system of claim 14, wherein, The first network element is configured to set a timing at which the second network element reports the first load report.

16. The system of claim 13 or 14, wherein, The at least one second network element includes two or more second network elements. The first network element is configured to select another second network element from the two or more second network elements based on first load reports from the two or more second network elements.

17. The system of any one of claims 1 to 16, wherein, The third network element is configured to send a second load report to the first network element, where the second load report indicates load traffic processed by the third network element. The first network element is configured to receive the second load report from the third network element.

18. The system of claim 17, wherein, The first network element is configured to set a timing at which the third network element reports the second load report.

19. The system of claim 17 or 18, wherein, The at least one third network element includes two or more third network elements. The first network element is configured to select another third network element from the two or more third network elements based on second load reports from the two or more third network elements.

20. The system of any one of claims 1 to 19, wherein, The first network element is configured to: indicate the second network element to record interactions between the second network element and the fourth network element; The second network element is configured to record the interactions between the second network element and the fourth network element and report log results to the first network element.

21. The system of any one of claims 1 to 20, wherein, The first network element is configured to: indicate the third network element to record interactions between the third network element and the fifth network element; The third network element is configured to record the interactions between the third network element and the fifth network element and report log results to the first network element.

22. The system of any one of claims 1 to 21, wherein, The second network element is configured to: receive a first request message from the fourth network element, where the first request message indicates a job requested by the fourth network element; determine a flow for implementing the job requested by the fourth network element based on the first request message.

23. The system of any one of claims 1 to 22, wherein, The third network element is configured to process a data format of a data packet when transmitting the data packet.

24. The system of any one of claims 1 to 23, wherein, The third network element is configured to perform at least one of decryption or encryption operations when transmitting the data packet.

25. The system of any one of claims 1 to 24, wherein, The first network element is communicatively connected with a seventh network element and is configured to coordinate processes and data packet exchanges on the data plane with the seventh network element.

26. The system of claim 25, wherein, The first network element is configured to: obtain a third configuration file, where the third configuration file includes reachable addresses of an eighth network element and a ninth network element under control of the seventh network element, the reachable address of the eighth network element being used to establish a connection between the second network element and the eighth network element, and the reachable address of the ninth network element being used to establish a connection between the third network element and the ninth network element; configure the second network element and the eighth network element to establish the connection between the second network element and the eighth network element; configuring the third network element and the ninth network element to establish the connection between the third network element and the ninth network element.

27. The system of any one of claims 1 to 26, wherein, The first network element is configured to: receive a first session establishment request, wherein the first session establishment request indicates a first device for which a first session is to be established; configure the second network element to establish the first session between the first device and the second network element based on the first session establishment request.

28. The system of any one of claims 1 to 27, wherein, The first network element is configured to: receive a second session establishment request, wherein the second session establishment request indicates a first device for which a second session is to be established; configure the third network element to establish the second session between the first device and the third network element based on the second session establishment request.

29. The system of any one of claims 1 to 28, wherein, The at least one second network element comprises two or more second network elements, at least two of the two or more second network elements being communicatively connected.

30. The system of any one of claims 1 to 29, wherein, The at least one third network element comprises two or more third network elements, at least two of the two or more third network elements being communicatively connected.

Images