[go: up one dir, main page]

WO2025044063A1 - Procédé de traitement de données et produits associés - Google Patents

Procédé de traitement de données et produits associés Download PDF

Info

Publication number
WO2025044063A1
WO2025044063A1 PCT/CN2024/075631 CN2024075631W WO2025044063A1 WO 2025044063 A1 WO2025044063 A1 WO 2025044063A1 CN 2024075631 W CN2024075631 W CN 2024075631W WO 2025044063 A1 WO2025044063 A1 WO 2025044063A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
request message
mode
determining
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/075631
Other languages
English (en)
Inventor
Hang Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025044063A1 publication Critical patent/WO2025044063A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/009—Security arrangements; Authentication; Protecting privacy or anonymity specially adapted for networks, e.g. wireless sensor networks, ad-hoc networks, RFID networks or cloud networks

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a data processing method and related products.
  • 5G (5th generation) system CP control plane
  • SBI service-based interface
  • NRF network Repository Function
  • the control plane is generally used for managing state information, routing table and access control list, etc. of a network device, and communicates with other devices to realize functions such as routing.
  • the data plane is generally used for processing and transmitting network traffic, i.e., forwarding a received data packet according to a preset rule, and ensuring that the data packet reaches a target device correctly.
  • an embodiment of the present disclosure provides a data processing method, where the method includes:
  • the first network element is gateway (also referred to as trustworthy gateway or C/M-TW-GW)
  • trustworthiness of the communication from perspectives of operation of the communication system is improved by introducing anonymous service provisioning provided by the trustworthy gateways in the C/control/management (C/M) plane.
  • the procedure is one of a first mode, a second mode or a third mode
  • the first request message is indicative of a working identification
  • the working identification is used for determining a mode among the first mode, the second mode and the third mode
  • determining, by the first network element based on the first request message, the procedure for implementing the work requested by the second network element includes:
  • the procedure for implementing the work requested by the second network element further includes:
  • the mode is the first mode
  • the procedure for implementing the work requested by the second network element further includes:
  • the mode upon determining that the mode is the second mode, determining, by the first network element, the multiple independent actions based on the first request message, where the first request message is further indicative of the multiple independent actions.
  • the procedure for implementing the work requested by the second network element further includes:
  • the mode upon determining that the mode is the third mode, determining, by the first network element, the multiple conditional actions and a sequence of the multiple conditional actions based on the first request message, where the first request message is further indicative of the multiple conditional actions and the sequence of the multiple conditional actions.
  • the first network element can perform different operations for different modes, thereby effectively managing the interaction between the second network element and the third network element.
  • the first request message is further indicative of at least one first basic service requested by the second network element
  • determining, by the first network element based on the first request message, the procedure for implementing the work requested by the second network element further includes:
  • the first network element determines, by the first network element, at least one third network element based on a preset authorization profile, the second network element and the first basic service, where the at least one third network element is authorized to provide the at least one first basic service to the second network element;
  • the preset authorization profile is indicative of a correspondence between each of the at least one third network element and the second network element.
  • the first network element can quickly determine the third network element capable of providing the first basic service requested by the second network element, so that the operation efficiency of the first network element can be improved.
  • the preset authorization profile is further indicative of a validity of the correspondence
  • determination of the third network element includes:
  • the validity of the connection between the third network element and the second network element can be ensured, and the valid third network element can be determined quickly, so that the operation efficiency of the first network element can be improved, and the system overhead can be reduced.
  • determining, by the first network element, the third network element based on the result of the verification includes:
  • the to-be-verified network element upon determining that the validity of the to-be-verified network element is valid, determining, by the first network element, the to-be-verified network element as the third network element.
  • the validity of the connection between the third network element and the second network element can be ensured, and the valid third network element can be determined quickly, so that the operation efficiency of the first network element can be improved, and the system overhead can be reduced.
  • determining, by the first network element, the third network element based on the result of the verification includes:
  • the validity of the connection between the third network element and the second network element can be ensured, and the valid third network element can be determined quickly, so that the operation efficiency of the first network element can be improved, and the system overhead can be reduced.
  • the correspondence between the third network element and the second network element is represented by a correspondence between an identification of a second basic service to which the second network element belongs, an identification of the second network element, an identification of the first basic service to which a third network element belongs and an identification of the third network element.
  • the procedure for implementing the work requested by the second network element further includes:
  • the mode is the first mode, determining, by the first network element based on the first request message, the one action and a third network element for performing the one action, where the first request message is further indicative of the one action and the third network element.
  • the first network element does not need to store authorization profile information locally, and simply needs the first request message to determine all the information for the work requested by the second network element, thereby saving the memory of the first network element, and the first network element (i.e., C/M-TW-GW) is intelligent and capable of controlling and managing the interaction between the second network element and the one third network element (i.e., entities of the XaaS services) efficiently.
  • the first network element i.e., C/M-TW-GW
  • the one third network element i.e., entities of the XaaS services
  • the procedure for implementing the work requested by the second network element further includes:
  • the mode upon determining that the mode is the second mode, determining, by the first network element based on the first request message, the multiple independent actions and one or more third network elements for performing the multiple independent actions, where the first request message is further indicative of the multiple independent actions and the one or more third network elements.
  • the first network element does not need to store authorization profile information locally, and simply needs the first request message to determine all the information for the work requested by the second network element, thereby saving the memory of the first network element, and the first network element (i.e., C/M-TW-GW) is intelligent and capable of controlling and managing the interaction between the second network element and each of the one or more third network elements (i.e., entities of the XaaS services) efficiently.
  • the first network element i.e., C/M-TW-GW
  • the procedure for implementing the work requested by the second network element further includes:
  • the mode upon determining that the mode is the third mode, determining, by the first network element based on the first request message, the multiple conditional actions, a sequence of the multiple conditional actions and one or more third network elements for performing the multiple conditional actions, where the first request message is further indicative of the multiple conditional actions, the sequence of the multiple conditional actions and the one or more third network elements.
  • the first network element does not need to store authorization profile information locally, and simply needs the first request message to determine all the information for the work requested by the second network element, thereby saving the memory of the first network element, and the first network element (i.e., C/M-TW-GW) is intelligent and capable of controlling and managing the interaction between the second network element and each of the one or more third network elements (i.e., entities of the XaaS services) efficiently.
  • the first network element i.e., C/M-TW-GW
  • the method further includes:
  • the method further includes: recording, by the first network element, a status of the transmission of the second request message; and upon receiving the second response message, updating, by the first network element, the status.
  • the first network element can effectively manage and control the interaction between the second network element and the one third network element.
  • the method further includes:
  • the first network element receives the response messages from all the third network elements, thus ensuring that the service is correctly provided by the third network element to the second network elements.
  • the method further includes:
  • the first network element can effectively manage and control the interaction between the second network element and each of the one or more third network elements.
  • the method further includes: transmitting, by the first network element, the first response message to the second network element.
  • an embodiment of the present disclosure provides a data processing method, where the method includes:
  • the method further includes:
  • an embodiment of the present disclosure provides a data processing method, where the method includes:
  • a third network element receiving, by a third network element, a second request message from a first network element, where the second request message is determined based on a first request message, and the first request message is indicative of a work requested by a second network element;
  • an embodiment of the present disclosure provides a data processing apparatus, where the apparatus includes:
  • a receiving module configured to receive a first request message from a second network element, where the first request message is indicative of a work requested by the second network element;
  • a determining module configured to determine, based on the first request message, a procedure for implementing the work requested by the second network element.
  • the procedure is one of a first mode, a second mode or a third mode; here in the first mode, one action is taken for implementing the work; here in the second mode, multiple independent actions are taken for implementing the work; here in the third mode, multiple conditional actions are taken for implementing the work.
  • the first request message is indicative of a working identification
  • the working identification is used for determining a mode among the first mode, the second mode and the third mode
  • the determining module is configured to: determine based on the working identification, the mode among the first mode, the second mode and the third mode for implementing the work.
  • the determining module is further configured to: upon determining that the mode is the first mode, determine the one action based on the first request message, where the first request message is further indicative of the one action.
  • the determining module is further configured to: upon determining that the mode is the second mode, determine the multiple independent actions based on the first request message, where the first request message is further indicative of the multiple independent actions.
  • the determining module is further configured to: upon determining that the mode is the third mode, determine the multiple conditional actions and a sequence of the multiple conditional actions based on the first request message, where the first request message is further indicative of the multiple conditional actions and the sequence of the multiple conditional actions.
  • the first request message is further indicative of at least one first basic service requested by the second network element
  • determining module is further configured to: determine at least one third network element based on a preset authorization profile, the second network element and the first basic service, where the at least one third network element is authorized to provide the at least one first basic service to the second network element;
  • the preset authorization profile is indicative of a correspondence between each of the at least one third network element and the second network element.
  • the preset authorization profile is further indicative of a validity of the correspondence
  • determining module is configured to:
  • the determining module is configured to: upon determining that the validity of the to-be-verified network element is valid, determine the to-be-verified network element as the third network element.
  • the determining module is configured to perform one of the following operations:
  • the correspondence between the third network element and the second network element is represented by a correspondence between an identification of a second basic service to which the second network element belongs, an identification of the second network element, an identification of the first basic service to which a third network element belongs and an identification of the third network element.
  • the determining module is further configured to: upon determining that the mode is the first mode, determine based on the first request message, the one action and a third network element for performing the one action, where the first request message is further indicative of the one action and the third network element.
  • the determining module is further configured to: upon determining that the mode is the second mode, determine based on the first request message, the multiple independent actions and one or more third network elements for performing the multiple independent actions, where the first request message is further indicative of the multiple independent actions and the one or more third network elements.
  • the determining module is further configured to: upon determining that the mode is the third mode, determine based on the first request message, the multiple conditional actions, a sequence of the multiple conditional actions and one or more third network elements for performing the multiple conditional actions, where the first request message is further indicative of the multiple conditional actions, the sequence of the multiple conditional actions and the one or more third network elements.
  • the apparatus further includes:
  • a first transmitting module configured to transmit a second request message to the third network element based on the first request message
  • the receiving module is further configured to receive from the third network element, a second response message corresponding to the second request message to obtain a first response message for the second network element based on the second response message.
  • the apparatus further includes: a first recording module, configured to record a status of the transmission of the second request message; and a first updating module, configured to, upon receiving the second response message, update the status.
  • the apparatus further includes:
  • a second transmitting module configured to transmit multiple second request messages to the one or more third network elements respectively based on the first request message
  • the receiving module is further configured to receive, for each of the multiple second request messages a second response message corresponding to the second request message from a third network element receiving the second request message;
  • the determining module is further configured to determine whether second response messages corresponding to the second request messages one-by-one from the one or more third network elements have been received;
  • the apparatus further includes: a first obtaining module, configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • a first obtaining module configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • the apparatus further includes: a third transmitting module, configured to, upon determining that a triggering condition for transmitting a second request message is met, transmit the second request message to a third network element of the one or more third network elements;
  • the receiving module is further configured to receive a second response message corresponding to the second request message from the third network element;
  • the determining module is further configured to determine whether second response messages corresponding to second request messages one-by-one from the one or more third network elements have been received;
  • the apparatus further includes: a second obtaining module, configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • a second obtaining module configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • the apparatus further includes: a second recording module, configured to record a status of the transmission of the second request messages; and a second updating module, configured to, upon receiving the second response messages, update the status.
  • each of the first transmitting module, the second transmitting module and the third module is further configured to transmit the first response message to the second network element.
  • an embodiment of the present disclosure provides a data processing apparatus, where the apparatus includes:
  • a transmitting module configured to transmit a first request message to a first network element, where the first request message is indicative of a work requested by the second network element.
  • the apparatus further includes: a receiving module, configured to receive a first response message from the first network element in response to the first request message.
  • an embodiment of the present disclosure provides a data processing apparatus, where the apparatus includes:
  • a receiving module configured to receive a second request message from a first network element, where the second request message is determined based on a first request message, and the first request message is indicative of a work requested by a second network element;
  • a transmitting module configured to transmit a second response message corresponding to the second request message to the first network element, where the second response message is used to obtain a first response message corresponding to the first request message for the second network element.
  • an embodiment of the present disclosure provides a first network element including processing circuitry for executing the data processing method according to the first aspect or any possible implementation of the first aspect.
  • an embodiment of the present disclosure provides a second network element including processing circuitry for executing the data processing method according to the second aspect or any possible implementation of the second aspect.
  • an embodiment of the present disclosure provides a third network element including processing circuitry for executing the data processing method according to the third aspect or any possible implementation of the third aspect.
  • an embodiment of the present disclosure provides a computer-readable medium storing computer execution instructions which, when executed by a processor, causes the processor to execute the data processing method according to the first aspect or any possible implementation of the first aspect, the data processing method according to the second aspect or any possible implementation of the second aspect, or the data processing method according to the third aspect or any possible implementation of the third aspect.
  • an embodiment of the present disclosure provides a wireless system, including the first network element according to the seventh aspect, the second network element according to the eighth aspect and the third network element according to the ninth aspect.
  • an embodiment of the present disclosure provides a computer program product including computer execution instructions which, when executed by a processor, causes the processor to execute the data processing method according to the first aspect or any possible implementation of the first aspect, the data processing method according to the second aspect or any possible implementation of the second aspect, or the data processing method according to the third aspect or any possible implementation of the third aspect.
  • an embodiment of the present disclosure an apparatus, including one or more processors, the one or more processors are configured to execute instructions stored in memory, when the instructions is executed by the one or more processors, the data processing method according to the first aspect or any possible implementation of the first aspect, the data processing method according to the second aspect or any possible implementation of the second aspect, or the data processing method according to the third aspect or any possible implementation of the third aspect is performed.
  • the first network element receives a first request message from a second network element, where the first request message is indicative of a work requested by the second network element; and the first network element determines based on the first request message, a procedure for implementing the work requested by the second network element.
  • the procedure for implementing the work can be determined by the first network element, based on the first request message or based on the first request message and information stored locally in the first network element, action (s) corresponding to the procedure and third network element (s) which provides/provide a service (e.g., X as a service, XaaS for short) to the first network element can be determined, thereby realizing interaction between the second network element and the third network element with the help of the first network element.
  • a service e.g., X as a service, XaaS for short
  • the first network element is gateway (also referred to as trustworthy gateway or C/M-TW-GW)
  • trustworthiness of the communication from perspectives of operation of the communication system is improved by introducing anonymous service provisioning provided by the trustworthy gateways in the C/control/management (C/M) plane.
  • FIG. 1 is a simplified schematic illustration of a communication system according to one or more embodiments of the present disclosure.
  • FIG. 2 is a schematic illustration of an example communication system according to one or more embodiments of the present disclosure.
  • FIG. 3 is a schematic illustration of a basic component structure of a communication system according to one or more embodiments of the present disclosure.
  • FIG. 4 illustrates a block diagram of a device in a communication system according to one or more embodiments of the present disclosure.
  • FIG. 5 illustrates a block diagram of 6G System conceptual structure according to one or more embodiments of the present disclosure.
  • FIG. 6 illustrates a structural schematic of a NET4CON framework according to one or more embodiments of the present disclosure.
  • FIG. 7 illustrates a schematic flowchart of a data processing method according to one or more embodiments of the present disclosure.
  • FIG. 8A illustrates an exemplary first operation mode of a first network element according to one or more embodiments of the present disclosure.
  • FIG. 8B illustrates an exemplary second operation mode of a first network element according to one or more embodiments of the present disclosure.
  • FIG. 8C illustrates an exemplary third operation mode of a first network element according to one or more embodiments of the present disclosure.
  • FIG. 9A illustrates an exemplary schematic flowchart of a data processing method in a first mode according to one or more embodiments of the present disclosure.
  • FIG. 9B illustrates an exemplary schematic flowchart of an exemplary data processing method in a first mode according to one or more embodiments of the present disclosure.
  • FIG. 10A illustrates an exemplary schematic flowchart of a data processing method in a second mode according to one or more embodiments of the present disclosure.
  • FIG. 10B illustrates an exemplary schematic flowchart of an exemplary data processing method in a second mode according to one or more embodiments of the present disclosure.
  • FIG. 11A illustrates an exemplary schematic flowchart of a data processing method in a third mode according to one or more embodiments of the present disclosure.
  • FIG. 11B illustrates an exemplary schematic flowchart of an exemplary data processing method in a third mode according to one or more embodiments of the present disclosure.
  • the communication system 100 comprises a radio access network 120.
  • the radio access network 120 may be a next generation (e.g. sixth generation (6G) or later) radio access network, or a legacy (e.g. 5G, 4G, 3G or 2G) radio access network.
  • One or more communication electronic devices (ED) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generically referred to as 110) may be interconnected to one another or connected to one or more network nodes (170a, 170b, generically referred to as 170) in the radio access network 120.
  • a core network 130 may be a part of the communication system and may be dependent or independent of the radio access technology used in the communication system 100.
  • the communication system 100 comprises a public switched telephone network (PSTN) 140, the internet 150, and other networks 160.
  • PSTN public switched telephone network
  • FIG. 2 illustrates an example communication system 100.
  • the communication system 100 enables multiple wireless or wired elements to communicate data and other content.
  • the purpose of the communication system 100 may be to provide content, such as voice, data, video, and/or text, via broadcast, multicast, groupcast, unicast, etc.
  • the communication system 100 may operate by sharing resources, such as carrier spectrum bandwidth, between its constituent elements.
  • the communication system 100 may include a terrestrial communication system and/or a non-terrestrial communication system.
  • the communication system 100 may provide a wide range of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc. ) .
  • the communication system 100 may provide a high degree of availability and robustness through a joint operation of a terrestrial communication system and a non-terrestrial communication system.
  • integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can result in what may be considered a heterogeneous network comprising multiple layers.
  • the heterogeneous network may achieve better overall performance through efficient multi-link joint operation, more flexible functionality sharing, and faster physical layer link switching between terrestrial networks and non-terrestrial networks.
  • the communication system 100 includes electronic devices (ED) 110a, 110b, 110c, 110d (generically referred to as ED 110) , radio access networks (RANs) 120a, 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.
  • the RANs 120a, 120b include respective base stations (BSs) 170a, 170b, which may be generically referred to as terrestrial transmit and receive points (T-TRPs) 170a, 170b.
  • the non-terrestrial communication network 120c includes an access node 172, which may be generically referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.
  • N-TRP non-terrestrial transmit and receive point
  • Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any T-TRP 170a, 170b and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the preceding.
  • ED 110a may communicate an uplink and/or downlink transmission over a terrestrial air interface 190a with T-TRP 170a.
  • the EDs 110a, 110b, 110c, and 110d may also communicate directly with one another via one or more sidelink air interfaces 190b.
  • ED 110d may communicate an uplink and/or downlink transmission over a non-terrestrial air interface 190c with NT-TRP 172.
  • the air interfaces 190a and 190b may use similar communication technology, such as any suitable radio access technology.
  • the communication system 100 may implement one or more channel access methods, such as code division multiple access (CDMA) , space division multiple access (SDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or single-carrier FDMA (SC-FDMA, also known as discrete Fourier transform spread OFDMA, DFT-s-OFDMA) in the air interfaces 190a and 190b.
  • CDMA code division multiple access
  • SDMA space division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • the air interfaces 190a and 190b may utilize other higher dimension signal spaces, which may involve a combination of orthogonal and/or non-orthogonal dimensions.
  • the non-terrestrial air interface 190c can enable communication between the ED 110d and one or multiple NT-TRPs 172 via a wireless link or simply a link.
  • the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or multiple NT-TRPs 172 for multicast transmission.
  • the RANs 120a and 120b are in communication with the core network 130 to provide the EDs 110a 110b, and 110c with various services such as voice, data, and other services.
  • the RANs 120a and 120b and/or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown) , which may or may not be directly served by core network 130, and may or may not employ the same radio access technology as RAN 120a, RAN 120b or both.
  • the core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b or EDs 110a 110b, and 110c or both, and (ii) other networks (such as the PSTN 140, the Internet 150, and the other networks 160) .
  • the EDs 110a 110b, and 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of wireless communication (or in addition thereto) , the EDs 110a 110b, and 110c may communicate via wired communication channels to a service provider or switch (not shown) , and to the Internet 150.
  • PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS) .
  • Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols, such as Internet Protocol (IP) , Transmission Control Protocol (TCP) , User Datagram Protocol (UDP) .
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • EDs 110a 110b, and 110c may be multimode devices capable of operation according to multiple radio access technologies, and incorporate multiple transceivers necessary to support such.
  • FIG. 3 illustrates another example of an ED 110 and a base station 170a, 170b and/or 170c.
  • the ED 110 is used to connect persons, objects, machines, etc.
  • the ED 110 may be widely used in various scenarios including, for example, cellular communications, device-to-device (D2D) , vehicle to everything (V2X) , peer-to-peer (P2P) , machine-to-machine (M2M) , machine-type communications (MTC) , internet of things (IoT) , virtual reality (VR) , augmented reality (AR) , mixed reality (MR) , metaverse, digital twin, industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.
  • D2D device-to-device
  • V2X vehicle to everything
  • P2P peer-to-
  • Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to) as a user equipment/device (UE) , a wireless transmit/receive unit (WTRU) , a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA) , a machine type communication (MTC) device, a personal digital assistant (PDA) , a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, wearable devices (such as a watch, a pair of glasses, head mounted equipment, etc.
  • UE user equipment/device
  • WTRU wireless transmit/receive unit
  • MTC machine type communication
  • PDA personal digital assistant
  • the base station 170a and 170b is a T-TRP and will hereafter be referred to as T-TRP 170. Also shown in FIG. 3, a NT-TRP will hereafter be referred to as NT-TRP 172.
  • Each ED 110 connected to T-TRP 170 and/or NT-TRP 172 can be dynamically or semi-statically turned-on (i.e., established, activated, or enabled) , turned-off (i.e., released, deactivated, or disabled) and/or configured in response to one of more of: connection availability and connection necessity.
  • the ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 204 may alternatively be panels.
  • the transmitter 201 and the receiver 203 may be integrated, e.g. as a transceiver.
  • the transceiver is configured to modulate data or other content for transmission by at least one antenna 204 or network interface controller (NIC) .
  • NIC network interface controller
  • the transceiver is also configured to demodulate data or other content received by the at least one antenna 204.
  • Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and/or processing signals received wirelessly or by wire.
  • Each antenna 204 includes any suitable structure for transmitting and/or receiving wireless or wired signals.
  • the ED 110 includes at least one memory 208.
  • the memory 208 stores instructions and data used, generated, or collected by the ED 110.
  • the memory 208 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by one or more processing unit (s) (e.g., a processor 210) .
  • Each memory 208 includes any suitable volatile and/or non-volatile storage and retrieval device (s) . Any suitable type of memory may be used, such as random access memory (RAM) , read only memory (ROM) , hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, and the like.
  • RAM random access memory
  • ROM read only memory
  • SIM subscriber identity module
  • SD secure digital
  • the ED 110 may further include one or more input/output devices (not shown) or interfaces (such as a wired interface to the Internet 150 in FIG. 1) .
  • the input/output devices or interfaces permit interaction with a user or other devices in the network.
  • Each input/output device or interface includes any suitable structure for providing information to or receiving information from a user, and/or for network interface communications. Suitable structures include, for example, a speaker, microphone, keypad, keyboard, display, touch screen, etc.
  • the ED 110 includes the processor 210 for performing operations including those operations related to preparing a transmission for uplink transmission to the NT-TRP 172 and/or the T-TRP 170; those operations related to processing downlink transmissions received from the NT-TRP 172 and/or the T-TRP 170; and those operations related to processing sidelink transmission to and from another ED 110.
  • Processing operations related to preparing a transmission for uplink transmission may include operations such as encoding, modulating, transmit beamforming, and generating symbols for transmission.
  • Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating and decoding received symbols.
  • a downlink transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission (e.g. by detecting and/or decoding the signaling) .
  • An example of signaling may be a reference signal transmitted by the NT-TRP 172 and/or by the T-TRP 170.
  • the processor 210 implements the transmit beamforming and/or the receive beamforming based on the indication of beam direction, e.g. beam angle information (BAI) , received from the T-TRP 170.
  • the processor 210 may perform operations relating to network access (e.g.
  • the processor 210 may perform channel estimation, e.g. using a reference signal received from the NT-TRP 172 and/or from the T-TRP 170.
  • the processor 210 may form part of the transmitter 201 and/or part of the receiver 203.
  • the memory 208 may form part of the processor 210.
  • the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory (e.g. in the memory 208) .
  • some or all of the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmed field-programmable gate array (FPGA) , an application-specific integrated circuit (ASIC) , or a hardware accelerator such as a graphics processing unit (GPU) or an artificial intelligence (AI) accelerator.
  • FPGA programmed field-programmable gate array
  • ASIC application-specific integrated circuit
  • AI artificial intelligence
  • the T-TRP 170 may be known by other names in some implementations, such as a base station, a base transceiver station (BTS) , a radio base station, a network node, a network device, a device on the network side, a transmit/receive node, a Node B, an evolved NodeB (eNodeB or eNB) , a Home eNodeB, a next Generation NodeB (gNB) , a transmission point (TP) , a site controller, an access point (AP) , a wireless router, a relay station, a terrestrial node, a terrestrial network device, a terrestrial base station, a base band unit (BBU) , a remote radio unit (RRU) , an active antenna unit (AAU) , a remote radio head (RRH) , a central unit (CU) , a distributed unit (DU) , a positioning node, among other possibilities.
  • BBU base band unit
  • RRU remote radio unit
  • the T-TRP 170 may be a macro BS, a pico BS, a relay node, a donor node, or the like, or combinations thereof.
  • the T-TRP 170 may refer to the forgoing devices or refer to apparatus (e.g. a communication module, a modem, or a chip) in the forgoing devices.
  • the parts of the T-TRP 170 may be distributed.
  • some of the modules of the T-TRP 170 may be located remote from the equipment that houses the antennas 256 for the T-TRP 170, and may be coupled to the equipment that houses the antennas 256 over a communication link (not shown) sometimes known as front haul, such as common public radio interface (CPRI) .
  • the term T-TRP 170 may also refer to modules on the network side that perform processing operations, such as determining the location of the ED 110, resource allocation (scheduling) , message generation, and encoding/decoding, and that are not necessarily part of the equipment that houses the antennas 256 of the T-TRP 170.
  • the modules may also be coupled to other T-TRPs.
  • the T-TRP 170 may actually be a plurality of T-TRPs that are operating together to serve the ED 110, e.g. through the use of coordinated multipoint transmissions.
  • the T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels.
  • the transmitter 252 and the receiver 254 may be integrated as a transceiver.
  • the T-TRP 170 further includes a processor 260 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to the NT-TRP 172, and processing a transmission received over backhaul from the NT-TRP 172.
  • Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. multiple input multiple output (MIMO) precoding) , transmit beamforming, and generating symbols for transmission.
  • Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols.
  • the processor 260 may also perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as generating the content of synchronization signal blocks (SSBs) , generating the system information, etc.
  • the processor 260 also generates an indication of beam direction, e.g.
  • the processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining where to deploy the NT-TRP 172, etc.
  • the processor 260 may generate signaling, e.g. to configure one or more parameters of the ED 110 and/or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is transmitted by the transmitter 252.
  • signaling may be transmitted in a physical layer control channel, e.g. a physical downlink control channel (PDCCH) , in which case the signaling may be known as dynamic signaling.
  • PDCCH physical downlink control channel
  • Signaling transmitted in a downlink physical layer control channel may be known as Downlink Control Information (DCI) .
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • SCI Sidelink Control Information
  • Signaling may be included in a higher-layer (e.g., higher than physical layer) packet transmitted in a physical layer data channel, e.g. in a physical downlink shared channel (PDSCH) , in which case the signaling may be known as higher-layer signaling, static signaling, or semi-static signaling.
  • Higher-layer signaling may also refer to Radio Resource Control (RRC) protocol signaling or Media Access Control –Control Element (MAC-CE) signaling.
  • RRC Radio Resource Control
  • MAC-CE Media Access Control –Control Element
  • the scheduler 253 may be coupled to the processor 260.
  • the scheduler 253 may be included within or operated separately from the T-TRP 170.
  • the scheduler 253 may schedule uplink, downlink, sidelink, and/or backhaul transmissions, including issuing scheduling grants and/or configuring scheduling-free (e.g., “configured grant” ) resources.
  • the T-TRP 170 further includes a memory 258 for storing information and data.
  • the memory 258 stores instructions and data used, generated, or collected by the T-TRP 170.
  • the memory 258 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 260.
  • the processor 260 may form part of the transmitter 252 and/or part of the receiver 254. Also, although not illustrated, the processor 260 may implement the scheduler 253. Although not illustrated, the memory 258 may form part of the processor 260.
  • the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 258.
  • some or all of the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.
  • the NT-TRP 172 is illustrated as a drone only as an example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form, such as satellites and high altitude platforms, including international mobile telecommunication base stations and unmanned aerial vehicles, for example. Also, the NT-TRP 172 may be known by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station.
  • the NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas may alternatively be panels.
  • the transmitter 272 and the receiver 274 may be integrated as a transceiver.
  • the NT-TRP 172 further includes a processor 276 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to T-TRP 170, and processing a transmission received over backhaul from the T-TRP 170.
  • Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. MIMO precoding) , transmit beamforming, and generating symbols for transmission.
  • precoding e.g. MIMO precoding
  • Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols.
  • the processor 276 implements the transmit beamforming and/or receive beamforming based on beam direction information (e.g. BAI) received from the T-TRP 170.
  • the processor 276 may generate signaling, e.g. to configure one or more parameters of the ED 110.
  • the NT-TRP 172 implements physical layer processing, but does not implement higher layer functions such as functions at the medium access control (MAC) or radio link control (RLC) layer. As this is only an example, more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.
  • MAC medium access control
  • RLC radio link control
  • the NT-TRP 172 further includes a memory 278 for storing information and data.
  • the processor 276 may form part of the transmitter 272 and/or part of the receiver 274.
  • the memory 278 may form part of the processor 276.
  • the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 278.
  • some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.
  • the NT-TRP 172 may actually be a plurality of NT-TRPs that are operating together to serve the ED 110, e.g. through coordinated multipoint transmissions.
  • the T-TRP 170, the NT-TRP 172, and/or the ED 110 may include other components, but these have been omitted for the sake of clarity.
  • FIG. 4 illustrates units or modules in a device, such as in the ED 110, in the T-TRP 170, or in the NT-TRP 172.
  • a signal may be transmitted by a transmitting unit or by a transmitting module.
  • a signal may be received by a receiving unit or by a receiving module.
  • a signal may be processed by a processing unit or a processing module.
  • Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module.
  • the respective units or modules may be implemented using hardware, one or more components or devices that execute software, or a combination thereof.
  • one or more of the units or modules may be a circuit such as an integrated circuit.
  • Examples of an integrated circuit includes a programmed FPGA, a GPU, or an ASIC.
  • one or more of the units or modules may be logical such as a logical function performed by a circuit, by a portion of an integrated circuit, or by software instructions executed by a processor.
  • the modules may be retrieved by a processor, in whole or part as needed, individually or together for processing, in single or multiple instances, and that the modules themselves may include instructions for further deployment and instantiation.
  • An air interface generally includes a number of components and associated parameters that collectively specify how a transmission is to be sent and/or received over a wireless communications link between two or more communicating devices.
  • an air interface may include one or more components defining the waveform (s) , frame structure (s) , multiple access scheme (s) , protocol (s) , coding scheme (s) and/or modulation scheme (s) for conveying information (e.g. data) over a wireless communications link.
  • the wireless communications link may support a link between a radio access network and user equipment (e.g. a “Uu” link) , and/or the wireless communications link may support a link between device and device, such as between two user equipments (e.g.
  • a “sidelink” may support a link between a non-terrestrial (NT) -communication network and user equipment (UE) .
  • the air interfaces may also use UWB technology to perform sensing of the surrounding environment using UWB signals.
  • a waveform component may specify a shape and form of a signal being transmitted.
  • Waveform options may include orthogonal multiple access waveforms and non-orthogonal multiple access waveforms.
  • Non-limiting examples of such waveform options include Orthogonal Frequency Division Multiplexing (OFDM) , Filtered OFDM (f-OFDM) , Time windowing OFDM, Filter Bank Multicarrier (FBMC) , Universal Filtered Multicarrier (UFMC) , Generalized Frequency Division Multiplexing (GFDM) , Wavelet Packet Modulation (WPM) , Faster Than Nyquist (FTN) Waveform, high rate pulse repetition frequency (HRP) UWB waveform, low rate pulse repetition frequency (LRP) UWB waveform and low Peak to Average Power Ratio Waveform (low PAPR WF) .
  • OFDM Orthogonal Frequency Division Multiplexing
  • f-OFDM Filtered OFDM
  • FBMC Filter Bank Multicarrier
  • UMC Universal Filtered Multi
  • a frame structure component may specify a configuration of a frame or group of frames.
  • the frame structure component may indicate one or more of a time, frequency, pilot signature, code, or other parameter of the frame or group of frames. More details of frame structure will be discussed below.
  • a multiple access scheme component may specify multiple access technique options, including technologies defining how communicating devices share a common physical channel, such as: Time Division Multiple Access (TDMA) , Frequency Division Multiple Access (FDMA) , Code Division Multiple Access (CDMA) , Single Carrier Frequency Division Multiple Access (SC-FDMA) , Low Density Signature Multicarrier Code Division Multiple Access (LDS-MC-CDMA) , Non-Orthogonal Multiple Access (NOMA) , Pattern Division Multiple Access (PDMA) , Lattice Partition Multiple Access (LPMA) , Resource Spread Multiple Access (RSMA) , and Sparse Code Multiple Access (SCMA) .
  • multiple access technique options may include: scheduled access vs.
  • non-scheduled access also known as grant-free access
  • non-orthogonal multiple access vs. orthogonal multiple access, e.g., via a dedicated channel resource (e.g., no sharing between multiple communicating devices)
  • contention-based shared channel resources vs. non-contention-based shared channel resources, and cognitive radio-based access.
  • a hybrid automatic repeat request (HARQ) protocol component may specify how a transmission and/or a re-transmission is to be made.
  • Non-limiting examples of transmission and/or re-transmission mechanism options include those that specify a scheduled data pipe size, a signaling mechanism for transmission and/or re-transmission, and a re-transmission mechanism.
  • a coding and modulation component may specify how information being transmitted may be encoded/decoded and modulated/demodulated for transmission/reception purposes.
  • Coding may refer to methods of error detection and forward error correction.
  • Non-limiting examples of coding options include turbo trellis codes, turbo product codes, fountain codes, low-density parity check codes, and polar codes.
  • Modulation may refer, simply, to the constellation (including, for example, the modulation technique and order) , or more specifically to various types of advanced modulation methods such as hierarchical modulation and low PAPR modulation.
  • the air interface may be a “one-size-fits-all concept” .
  • the components within the air interface cannot be changed or adapted once the air interface is defined.
  • only limited parameters or modes of an air interface such as a cyclic prefix (CP) length or a multiple input multiple output (MIMO) mode, can be configured.
  • an air interface design may provide a unified or flexible framework to support below 6GHz and beyond 6GHz frequency (e.g., mmWave) bands for both licensed and unlicensed access.
  • flexibility of a configurable air interface provided by a scalable numerology and symbol duration may allow for transmission parameter optimization for different spectrum bands and for different services/devices.
  • a unified air interface may be self-contained in a frequency domain, and a frequency domain self-contained design may support more flexible radio access network (RAN) slicing through channel resource sharing between different services in both frequency and time.
  • RAN radio access network
  • the solution described in the present disclosure may be applicable to a next generation (e.g. sixth generation (6G) or later) network, or a legacy (e.g. 5G or 4G) network.
  • a next generation e.g. sixth generation (6G) or later
  • a legacy e.g. 5G or 4G
  • the proposed 6G System architecture is defined to support 6G X as a service (XaaS) by using techniques such as Network Function Virtualization and Network Slicing.
  • the 6G System architecture utilizes service-based interactions between 6G services.
  • the 6G System leverages service-based architecture and XaaS concept. XaaS services in the 6G System are categorized into three layers. The 6G System conceptual structure is shown in FIG. 5.
  • Infrastructure Layer includes infrastructures supporting 6G services. Among them are wireless networks (RAN, CN) infrastructures, Cloud/data center infrastructures, satellite networks, storage/database infrastructures, and sensing networks, and etc. These infrastructures can be provided by a single provider or by multiple providers.
  • RAN wireless networks
  • CN Cloud/data center infrastructures
  • satellite networks satellite networks
  • storage/database infrastructures and sensing networks, and etc.
  • sensing networks and etc.
  • Each of the infrastructures could have its control and management functions, denoted as C/M functions, for infrastructure management.
  • C/M functions for infrastructure management.
  • Each of these infrastructures is one type of Infrastructure as a Service.
  • Control and Management (C/M) layer includes control and management services of the 6G System. They are developed and deployed by using slicing techniques and utilizing resource provided by infrastructure layer. 6G services in Control and Management (C/M) layer are:
  • RM Resource Management
  • MM -Mission Management
  • CONET Confederation Network
  • SPM Service Provisioning Management
  • CM Connectivity Management
  • Protocol as a Service provides a capability to design service customized protocol stacks for identified interfaces.
  • the protocol stacks could be pre-defined for on-demand selection, or could be on-demand designed.
  • -Network Security as a Service provides a capability for owners of infrastructures to detect potential security risks of their infrastructures.
  • a 6G mission is defined as a service provided to customers by the 6G System.
  • a mission can be a type of services which is provided by a single 6G XaaS service or a type of services that needs contributions from multiple XaaS services.
  • XaaS services in C/M Layer support control and management of the 6G System itself and also provide support to verticals if requested.
  • RM service can serve RAN for over-the-air resource management and can also provide service to a vertical for the vertical’s over-the-air resource allocation to its end-customers.
  • the XaaS in C/M layer can be deployed by using slicing technique.
  • Service Layer includes 6G services which provide services to customers.
  • 6G System conceptual structure:
  • -AI service may be denoted as NET4AI as a Service.
  • Artificial Intelligence service provides AI capability to support a variety of AI applications.
  • DAM Data -Service of data collection, data sanitization, data analysis and data delivery
  • DAM Data -Service of data collection, data sanitization, data analysis and data delivery
  • this service provides a capability of lifecycle management of statistic data, including acquisition, de-privatization, analysis and delivery of data which are information statistic data from any types of sensors, devices, network functions, and etc.
  • NET4Data a Service
  • this service provides a capability to trustworthily storage and share data under the control of owners of data and following recognized authorities’ regulations on control of identified data.
  • NET4DW Digital World service
  • Digital world is defined as digital realization of physical world.
  • -6G block chain service may be denoted as NET4BC as a Service.
  • 6G connectivity service is denoted as NET4Con as a Service. This service provides a capability to support 6G block chain services.
  • -Enhanced connectivity service e.g., network for connectivity (NET4CON) as a service.
  • This service provides a capability to support exchange of messages and data among new 6G services.
  • All XaaS services at this Layer are developed and deployed by using resource provided in infrastructure and utilizing Network Function Virtualization and Slicing techniques.
  • the capability of each of 6G services is provided by its control and management functions and service specific data process functions.
  • 6G System leverages 5G System for provisioning of vertical services.
  • the difference between 6G XaaS services and other verticals are that a vertical is a pure customer which needs other XaaS services to enable its operation, while each of XaaS services provide their capabilities to 6G customers.
  • Any pair of XaaS services of the 6G System could also be mutual customer and provider of each other.
  • an infrastructure owner provides its resource to XaaS services in Service Layer and C/M Layer;
  • RM services may need the capabilities provided by NET4AI, DAM and NET4DW for its resource management for vertical slicing;
  • CONET service and NET4Data service may need the capability provided by NET4BC for their operation.
  • a XaaS service module there are one or multiple network functions, these network functions can be classified into two categories: C/M function is used for control and management, data processing function (also can be referred to as data function) is used for processing data, the data processing function is only existed in the XaaS services at the service layer.
  • C/M function is used for control and management
  • data processing function also can be referred to as data function
  • the data processing function is only existed in the XaaS services at the service layer.
  • the key concepts of 6G System includes:
  • a basic XaaS service provides unique capability to enable a specific type of service, such as NET4AI service, NET4DW service, DAM service, NET4Data service, Block chain service, mission management service, etc.
  • Data plane defined in 6G system is a collection of data processing functions of XaaS service in service layer, used for processing and transmitting 6G system data plane traffic.
  • Types of traffic data in 6G system include: training model in NET4AI services, raw data collected, post-sanitized data in DAM service, data in NET4Data, data within digital world in NET4DW, data blocks in NET4BC.
  • the C/M-TW-GW Control/Management plane TrustWorthy GateWay
  • the C/M-TW-GW provides the abilities of control plane connectivity, anonymous communication, and secure communication, to enable these abilities, the C/M-TW-GW provides following functionalities: establishes and maintains secured tunnel with each of XaaS services, performs decryption and encryption operation when transferring C/M plane message; maintains an authorization profile for each of XaaS services; transfers the C/M plane message.
  • the Data-TW-GW (Date plane TrustWorthy GateWay) provides the abilities to connect data plane functions of XaaS services to enable to anonymous and secured data plane interaction among XaaS services, the Data-TW-GW provides following functionalities: establishes and maintains secured tunnel with each of XaaS services, performs decryption and encryption operation when transferring data packets; data format translation; transfers the data packets.
  • a BAS is a collection of XaaS services (including C/M plane functions and data plane functions) , TW-GWs in both C/M plane and data plane, and the interfaces between these functions.
  • An infrastructure network that implements a single 6G System BAS is defined as a BAS domain.
  • Each of RAN, CN, a cloud infrastructure, or a wireless device could be a BAS domain.
  • 5G users can use the 6G System to access 5G services.
  • 5G system and O-RAN don’t have the proposed 6G network architecture.
  • 5G system CP SBI uses SCP and NRF, etc., to support 5G CP plane indirect communication but not support strong trustworthiness.
  • 5G system has no Data plane definition and has no Data-TW-GW concept.
  • O-RAN has near-term RIC and long term RIC which are not solving issues that 6G may be facing.
  • -New (relative) matured techniques e.g., AI large scale models, Data de-privacy, Block chain, etc. that have made significant progresses and significantly impact on the entire society and human life.
  • -New apps and services e.g., AI services, Data (sensing) service, Digital world service, etc. that are broadly applied in industry/business and used by individual customers.
  • the proposed 6G network architecture (X-centric) are SBA (XaaS service) based and Cloud-native.
  • the proposed 6G network architecture needs to enable better trustworthiness management.
  • the proposed 6G network architecture may enable controlled anonymous interactions among multiple players.
  • a framework (which is also referred as a service framework) enables above requirements to be met.
  • the service framework is proposed, which is expected to meet the above new requirements to 6G networks.
  • the proposed C/M-TW-GW could be key potential for 6G products.
  • FIG. 6 illustrates a structural schematic of a framework
  • the framework includes three kinds of logical network elements, i.e., a C/M function, at least one C/M-TW-GW (control/management plane trustworthy GW) and at least one Data-TW-GW (Data plane trustworthy GW) in one BAS domain (or referred to as domain for short) or administration domains.
  • a C/M function i.e., control/management plane trustworthy GW
  • Data-TW-GW Data plane trustworthy GW
  • FIG. 6 illustrates a structural schematic of a framework
  • the framework includes three kinds of logical network elements, i.e., a C/M function, at least one C/M-TW-GW (control/management plane trustworthy GW) and at least one Data-TW-GW (Data plane trustworthy GW) in one BAS domain (or referred to as domain for short) or administration domains.
  • C/M function control/management plane trustworthy GW
  • Data-TW-GW Data plane trustworthy GW
  • the C/M function in the BAS domain is configured to control and manage topology of the BAS domain, e.g., logical connections between XaaS services/verticals and GWs (including C/M-TW-GW (s) and Data-TW-GW (s) ) in such a domain, and control 6G devices/D-Users/any types of customers to access 6G system by managing C/M session and data session.
  • topology of the BAS domain e.g., logical connections between XaaS services/verticals and GWs (including C/M-TW-GW (s) and Data-TW-GW (s) ) in such a domain, and control 6G devices/D-Users/any types of customers to access 6G system by managing C/M session and data session.
  • XaaS services have their own C/M function entities (for realizing their C/M functions of XaaS service modules) and data function entities (for realizing their data processing functions of XaaS service modules) in the same BAS domain as the C/M function, verticals also have their own C/M function entities and data function entities in the same BAS domain as the C/M function, the C/M-TW-GW under control of the C/M function in the BAS domain is configured to connect the C/M function entities of XaaS services and verticals in a BAS domain, in order to enable anonymous and secured C/M plane interaction among XaaS services following authorization profiles of XaaS services, as well as anonymous and secured C/M plane interaction among verticals.
  • the Data-TW-GW under control of the C/M function in the BAS domain is configured to connect the data function entities of XaaS services and verticals in a BAS domain, to enable anonymous and secured data plane interaction among XaaS services, as well as anonymous and secured data plane interaction among verticals to manage assured service performance.
  • the aforementioned C/M function entity of the XaaS service performs control and management plane functions that are for purpose of network control and management, and also supports signaling exchanging of the XaaS service on the C/M plane.
  • Different C/M function entities are connected via the C/M-TW-GW for supporting anonymous and secured C/M plane interaction among XaaS services.
  • the aforementioned data function entity of the XaaS service can be a processer which processes data plane traffic, such as NET4AI entity is for model training, etc., and also supports data exchanging of the XaaS service on the data plane.
  • Different data function entities are connected via the Data-TW-GW for supporting anonymous and secured data plane interaction among XaaS services.
  • the difference between the XaaS service and the vertical is that the vertical is a pure customer which needs other XaaS services to enable its operation, while the XaaS service provides its capabilities to 6G customers.
  • the vertical is a business or industry customer, which is different from an individual wireless device. It could have its dedicated network resource, or integrate its self-defined functions with network functions, could have its own customers, etc.
  • the vertical here may be a kind of service running on the basis of a network provided by e.g., an operator, the vertical per se normally does not own such a network, but may also be able to provide a service to users based on the network, so from the perspective of the operator, such service can be regarded as a vertical.
  • some chatting applications do not have their networks, but can also provide services to users, these chatting applications can be regarded as verticals.
  • the vertical may also have its own server (s) , and its own C/M function entity/entities and data function entity/entities, so in order to make it possible for the vertical to provide a service to users, the C/M-TW-GW and the C/M function entity of the vertical needs to be connected and the Data-TW-GW and the data function entity of the vertical needs to be connected.
  • the C/M-TW-GW and the C/M function entity of the vertical needs to be connected and the Data-TW-GW and the data function entity of the vertical needs to be connected.
  • the C/M function, the C/M-TW-GW and Data-TW-GW in the same domain are connected, e.g., via internal interfaces.
  • Different C/M-TW-GWs in the same domain may be connected, different Data-TW-GWs in the same domain may be also be connected, the C/M-TW-GW and the C/M function entity of a XaaS service in the same domain may be connected, and the Data-TW-GW and the Data function entity of a XaaS service in the same domain are connected.
  • the framework may be across multiple BAS domains, and may include multiple C/M functions, multiple C/M-TW-GWs and multiple Data-TW-GWs in the multiple BAS domains, and the C/M functions in different BAS domains may be connected, and each of the C/M functions is configured to control and manage the C/M-TW-GW (s) and the Data-TW-GW (s) in the domain to which the C/M function belongs.
  • a C/M-TW-GW in one BAS domain may be communicatively connected to a C/M-TW-GW in another BAS domain
  • a Data-TW-GW in one BAS domain may be communicatively connected to a Data-TW-GW in another BAS domain accordingly.
  • the C/M-TW-GW can provide capabilities to connect C/M function entities of XaaS services and verticals in a BAS domain, in order to enable anonymous and secured C/M plane interaction among XaaS services following authorization profiles of XaaS services, as well as anonymous and secured C/M plane interaction verticals.
  • the C/M-TW-GW functions as an agent for connecting C/M function entities of different XaaS services or different verticals, in order to make sure that such connections are secured connections, for example, when responding to a request message from a C/M entity of a XaaS service (consumer) which requests a service from another XaaS service (producer) , the C/M-TW-GW will have to check the authorization information related to the requester, so as to ensure a trustworthy connection between the C/M entity of the consumer and the C/M entity of the producer which are both in the same BAS domain as the C/M-TW-GW and connected to the C/M-TW-GW.
  • the pre-conditions for operation of the C/M-TW-GW are as follows: a logical connection between the C/M-TW-GW and a C/M function entity of a consumer XaaS Service in a BAS domain (in which the C/M-TW-GW is located) and a logical connection between the C/M-TW-GW and a C/M function entity of a producer XaaS Service in a BAS domain (in which the C/M-TW-GW is located) have been established.
  • one XaaS service may need the help from the other XaaS service, or may seek provisioning of service from another XaaS service, so the two XaaS services may play different roles, namely, one XaaS service acts as a consumer XaaS service, and the other XaaS service acts as a producer XaaS service.
  • the consumer XaaS Service generally refers to a service which needs an action from another XaaS service
  • the producer XaaS Service generally refers to a service which provides an action to the consumer XaaS service.
  • the NET4AI service is a consumer XaaS service and the NET4DAM service is a producer XaaS service.
  • the producer XaaS service can be any one XaaS service in FIG. 5 or any other possible XaaS service
  • the consumer XaaS service can also be any one XaaS service in FIG. 5 or any other possible XaaS service.
  • the producer XaaS service may have multiple C/M function entities in the BAS domain, the one or multiple C/M function entities belong to the producer XaaS service.
  • An implementation of the present disclosure provides a data processing method applied to a first network element, e.g., a C/M-TW-GW. Reference may be made to FIG. 7, the data processing method may include the following steps.
  • a first network element receives a first request message from a second network element, where the first request message is indicative of a work requested by the second network element.
  • the “work” here may be construed as an execution of an action or a series of actions, the action (s) can be executed by network element (s) (third network element (s) below) whose accessibility is (are) under control of the first network element, each of the network element (s) is capable of providing a basic service (referred to as first basic service below) , the execution of the action is an implementation of the provisioning of the basic service by the network element.
  • first basic service referred to as first basic service below
  • the second network element may need service (s) from other network element (s) whose accessibility is (are) under control of the first network element, the provisioning of the service (s) from other network element (s) may be implemented as an action or a series of actions executed by other network element (s) , so the second network element may communicate with the first network element to request the execution of the action (s) , then the first network element may respond to such request by determining a procedure for implementing the work (executing the action (s) ) , thereby facilitating the service provisioning of the second network element.
  • the C/M function entity of the consumer XaaS service transmits the first request message to the C/M-TW-GW to request the work
  • the C/M-TW-GW is configured to ensure a trustworthy connection between the C/M function entity of the consumer XaaS service and the C/M function entity of the producer XaaS service.
  • the producer XaaS service may be referred to as a first basic service
  • the consumer XaaS service may be referred to as a second basic service
  • the NET4AI service is a consumer XaaS service (second basic service)
  • the NET4DAM service is a producer XaaS service (first basic service)
  • the data collection is the action executed by the C/M function entity of the NET4DAM service for providing the NET4DAM service.
  • the first network element can be a C/M-TW-GW as mentioned above
  • the second network element can be a vertical in the same domain as the first network element and connected to the first network element, where the vertical may request a service from one or more other verticals (which will be also referred as third network element (s) herein)
  • a vertical transmits the first request message to the C/M-TW-GW to request the work
  • the C/M-TW-GW is configured to ensure a trustworthy connection between the vertical (the requester) and another vertical (the responder) .
  • the method further includes the following steps.
  • a first network element determines based on the first request message, a procedure for implementing the work requested by the second network element.
  • the first request message may be various kinds of requests that can indicate the procedure for implementing the work.
  • the first network element may determine the action (s) to be taken for implementing the work, the action (s) may be executed (performed) by one or more third network elements authorized to provide service to the second network element, so the first network element may determine, for each action, the third network element to perform such action, as well as the sequence of the third network elements in a case where multiple third network elements are required to execute the actions dependently, the third network element may be a C/M function entity of a producer XaaS service and connected to the first network element.
  • the determination of the procedure for implementing the work requested by the second network element may include the determination of the action (s) to be taken for implementing the work and the third network element (s) to perform the action (s) , as well as the sequence of the action (s) if necessary.
  • the first request message is a first type of message and simply includes partial information needed for determining the procedure for implementing the work
  • the first network element may determine the procedure for implementing the work based on the first request message as well as other information locally stored in the first network element.
  • the first request message may simply include a working identification (ID for short) which indicates the mode of the procedure, and the first network element locally saves information about a correspondence between a mode of the procedure and the corresponding action (s) to be taken (as well as the sequence of the action (s) if necessary) and corresponding third network element (s) for executing the action (s) , so the first network element may determine the action (s) to be taken for implementing the work (as well as the sequence of the action (s) if necessary) and the third network element (s) for executing the action (s) based on the mode indicated in the first request message and the locally saved information.
  • ID working identification
  • the mode of the procedure may indicate how the procedure is to be executed, it also corresponds to the operation mode of the first network element when executing the procedure.
  • the work ID may also be implemented as a message ID, so the first request message could include a message ID which is for identifying the mode of the procedure.
  • the first request message may indicate the mode of the procedure and the action (s) to be taken for implementing the work (as well as the sequence of the action (s) if necessary)
  • the first network element locally saves information about a correspondence between the action (s) (as well as the sequence of the action (s) if necessary) to be taken and the third network element (s) for executing the action (s)
  • the first network element may determine the third network element (s) based on the action (s) indicated in the first request message and the locally saved information.
  • the first network element may determine the candidate third network elements based on the action (s) indicated in the first request message and the locally saved information, Further, the first network element locally saves information about connection (s) between the second network element and the third network element (s) , so the first network element may determine the third network element (s) for executing the action (s) from the candidate third network element (s) and the connection (s) between the second network element and the third network element (s) , e.g., choose third network element (s) connected to the second network element.
  • the first request message may indicate the mode of the procedure and at least one first basic service (first basic service (s) ) requested by the second network element, in this case, the first network element locally saves information about a correspondence between a mode of the procedure and the corresponding action (s) to be taken (as well as the sequence of the action (s) if necessary) , so the first network element may determine the action (s) to be taken for implementing the work (as well as the sequence of the action (s) if necessary) based on the mode indicated in the first request message and the locally saved information.
  • first basic service first basic service
  • the first basic service is the producer XaaS service
  • the second network element when the second network element requests a work from the first network element, it actually requests action (s) to be taken by third network element (s) (C/M function entity (entities) of the producer XaaS service (s) authorized to provide first basic service (s) to the second network element) , and execution of the action (s) realizes provisioning of first basic service (s) by producer XaaS service (s) , so when the at least one first basic service is indicated in the first request message, the second network element indicates its required service (s) , since the first network element also locally saves information about a correspondence between the second network element (C/M function entity of a consumer XaaS service) and the third network element (s) (C/M function entity/entities of producer XaaS service (s) ) , the first network element may determine the third network element (s) for providing the first basic service (s) by executing the action (s) based on the
  • the action to be taken for implementing the work requested by the second network element includes data collection, data de-privacy or data analysis which is provided by the DAM service
  • the DAM service is the first basic service requested by the second network element.
  • the actions to be taken for implementing the work requested by the second network element include data collection, data de-privacy and data analysis which are provided by the DAM service, and the actions also include the computing which is provided by the NET4AI, etc.
  • the DAM service and the NET4AI are both the first basic services requested by the second network element.
  • the first request message also includes information about the action (s) to be taken (as well as the sequence of the action (s) if necessary) so as to implement the work
  • the first network element also locally saves information about a correspondence between the second network element (C/M function entity of consumer XaaS service) and the third network element (s) (C/M function entities of producer XaaS services) , so the first network element may determine the third network element (s) to execute the action (s) based on the first request message and the locally saved information.
  • the third network element (s) can be determined based on a correspondence between the action (s) to be taken (as well as the sequence of the action (s) if necessary) and the third network element (s) , or based on a correspondence between the at least one first basic service requested by the second network element and the third network element (s) .
  • the first request message is a second type of message and includes all information needed for determining the procedure for implementing the work
  • the first network element may then determine the procedure for implementing the work simply based on the first request message.
  • the first request message also includes the action (s) to be taken for implementing the work and information of the third network element (s) (e.g., ID of the third network element or other information for identifying the third network element) to execute the action (s) (as well as the sequence of the action (s) if necessary) , in this way, the first network element may determine the action (s) to be taken for implementing the work and the third network element (s) to execute the action (s) (as well as the sequence of the action (s) if necessary) based on the first request message.
  • the third network element e.g., ID of the third network element or other information for identifying the third network element
  • the main difference between the first type of message and the second type of message lies in that the first type of message is not intelligent, so the first network element should use local information to determine the procedure for implementing the work, but the second type of message is intelligent, so the first network element can rely only on the first request message to determine the procedure for implementing the work.
  • the procedure for implementing the work can be determined by the first network element, based on the first request message or based on the first request message and information stored locally in the first network element, action (s) corresponding to the procedure and third network element (s) which provides/provide a service (e.g., X as a service, XaaS for short) to the first network element can be determined, thereby realizing interaction between the second network element and the third network element with the help of the first network element.
  • a service e.g., X as a service, XaaS for short
  • the first network element is gateway (also referred to as trustworthy gateway or C/M-TW-GW)
  • trustworthiness of the communication from perspectives of operation of the communication system is improved by introducing anonymous service provisioning provided by the trustworthy gateways in the C/control/management (C/M) plane.
  • the procedure for implementing the work has three modes, a first mode, a second mode or a third mode; where when the procedure is the first mode, one action is taken for implementing the work; where when the procedure is the second mode, multiple independent actions are taken for implementing the work; where when the procedure is the third mode, multiple conditional actions are taken for implementing the work.
  • the first network element can perform different operations in different modes, thereby effectively managing the interaction between the second network element and the third network element.
  • the first mode there is simply one third network element which is involved in responding to the first request message from the second network element, and the first request message from the second network element simply requests one action (asingle action) by the one third network element to implement the work requested by the second network element.
  • the second mode and the third mode there are one or multiple third network elements which are involved in responding to the first request message from the second network element.
  • the first request message from the second network element requests multiple actions by the one or multiple third network elements to implement the work requested by the second network element, and the multiple actions are independent actions, so each action can be performed by a corresponding third network element independently.
  • the first request message from the second network element requests multiple actions by the one or multiple third network elements to implement the work requested by the second network element, and the multiple actions are dependent actions, so an action to be performed by a third network element is dependent on a result of execution of another action.
  • each third network element can perform one or more actions of the multiple actions.
  • a relation between a message ID (which may be a C/M plane message ID and may be carried in a first request message from the second network element) and an associated mode type (which may be the aforementioned modes) is illustrated.
  • the table can be locally stored in the C/M-TW-GW (apossible implementation of the first network element) .
  • the C/M-TW-GW can be pre-configured with Table 1 to keep information on relation between a C/M plane message ID and associated mode type ID (mode 1, mode 2, or mode 3) , the mode type ID is for identifying the mode type.
  • the C/M-TW-GW can correctly operate based on the message ID (which may be carried in a first request message from the second network element) and its local information stored, this option corresponds to the case where the first request message is the first type of message mentioned above.
  • each C/M plane message can mark required mode type ID and other required information in order for a C/M-TW-GW to operate correctly, this option corresponds to the case where the request message is the second type of message mentioned above.
  • FIGS. 8A-8C exemplary illustrate three operation modes of the first network element respectively, i.e., three modes of the C/M-TW-GW, where the C/M function entity of the consumer XaaS service and the C/M function entity of the producer XaaS service are both connected to the C/M-TW-GW, e.g., via the external interface (for example, 6G-C/M-1 shown in the figures) .
  • the external interface for example, 6G-C/M-1 shown in the figures
  • the C/M-TW-GW receives a message (aspecific example for the aforementioned mentioned first request message) from one C/M function entity of one consumer XaaS service.
  • the message requests a single action.
  • This message is forwarded to a selected producer XaaS service after a certain process at the C/M-TW-GW.
  • a response type of message with result is sent back to the C/M-TW-GW.
  • the C/M-TW-GW sends a response message to the C/M function entity of the consumer XaaS service.
  • the C/M-TW-GW receives a message (aspecific example for the aforementioned mentioned first request message) from one C/M function entity of one consumer XaaS service.
  • the message requests multiple parallel actions from other producer XaaS services.
  • This message is forwarded to multiple selected producer XaaS services after a certain process at the C/M-TW-GW.
  • multiple response type of messages respectively from the multiple C/M function entities of the producer XaaS services with results are sent back to the C/M-TW-GW.
  • the C/M-TW-GW sends a single response message to the C/M function entity of the consumer XaaS service, after certain process.
  • the C/M-TW-GW receives a message (aspecific example for the aforementioned mentioned first request message) from one C/M function entity of one consumer XaaS service.
  • the message requests a multiple sequential (dependent) actions from other producer XaaS services.
  • the C/M-TW-GW performs single action procedure (mode 1) one by one based on message types and message content. After all actions are completed, the C/M-TW-GW sends a single response message to the consumer XaaS service.
  • the first request message is indicative of a working identification
  • the working identification is used for determining a mode among the first mode, the second mode and the third mode
  • the first network element determines, based on the working identification, the mode among the first mode, the second mode and the third mode for implementing the work.
  • ID the mode of the procedure
  • work ID 1, indicating that the mode is the first mode
  • work ID 2, indicating that the mode is the second mode
  • work ID 3, indicating that the mode is the third mode.
  • the first network element can directly determine the mode of the procedure based on a format of the first request message, where different formats are used for indicating different modes.
  • the specific formats of the first request message are not limited in the embodiments of the present disclosure.
  • the process of determining the procedure for implementing the work requested by the second network element by the first network element based on the first request message will be described, in the case where the first request message is the first type of message.
  • the procedure for implementing the work requested by the second network element further includes: the first network element determining the one action based on the first request message, where the first request message is further indicative of the one action.
  • the first request message can include a field indicating the one action to be performed by one third network element for implementing the work requested by the second network element, which is not limited in the embodiments of the present disclosure.
  • the first request message is further indicative of one first basic service (e.g., the above producer XaaS service) requested by the second network element; where determining, by the first network element based on the first request message, the procedure for implementing the work requested by the second network element further includes: the first network element determining one third network element based on a preset authorization profile, the second network element and the first basic service, where the one third network element is authorized to provide the one first basic service to the second network element; where the preset authorization profile is indicative of a correspondence between the one third network element and the second network element.
  • one first basic service e.g., the above producer XaaS service
  • the correspondence may be a matching relationship between the one third network element and the second network element, which means that this third network element is authorized to provide the first basic service to the second network element.
  • the correspondence may be a pair of IDs, one ID is the ID of the one third network element, and the other ID is the ID of the second network element.
  • a BAS domain there may be one or multiple third network elements providing the first basic service (XaaS service) . So, in the case of multiple third network elements, the determination of the one third network element may be to select one third network element among the multiple third network elements for providing the first basic service.
  • XaaS service first basic service
  • the preset authorization profile can be locally stored in the first network element.
  • the first network element may inform the first network element of its authorization profile indicating C/M function entity/entities (the third network element (s) ) in the same BAS domain as the first network element and its authorized consumer (s) in said BAS domain
  • the authorization profile may include ID (s) of the C/M function entity/entities of the producer XaaS service, an ID of the producer XaaS service, ID (s) of the authorized consumer XaaS service (s) and ID (s) of the C/M function entity/entities of the authorized consumer XaaS service (s) , then the first network element would know which C/M function entity/entities can act as producer (s) to provide the first basic service to which C/M function entity/entities acting as consumer (s) , so the first network element can thus obtain the
  • the registration is done by the C/M function entity of the producer XaaS service.
  • a C/M function entity (third network element) of a producer XaaS service registers to the first network element, it may inform the first network element of its authorization profile indicating its authorized consumer (s) in the same BAS domain as the first network element, the authorization profile may include an ID of the C/M function entity of the producer XaaS service, an ID of the producer XaaS service, ID (s) of the authorized consumer XaaS service (s) and ID (s) of the C/M function entity/entities of the authorized consumer XaaS service (s) , for one producer XaaS service, it may have multiple C/M function entities in said BAS domain, so each C/M function entity will register in the same way, then the first network element can take all the authorization profiles from the C/M function entities of the producer XaaS service as an authorization profile of the producer XaaS service, and
  • the first network element can quickly determine the third network element capable of providing the first basic service requested by the second network element, so that the operation efficiency of the first network element can be improved.
  • the correspondence between the third network element and the second network element is represented by a correspondence between an identification of a second basic service (e.g., the above consumer XaaS service) to which the second network element belongs, an identification of the second network element, an identification of the first basic service to which a third network element belongs and an identification of the third network element.
  • a second basic service e.g., the above consumer XaaS service
  • the preset authorization profile includes: a correspondence among an ID of the consumer XaaS service, an ID of the C/M function entity of the consumer XaaS service, an ID of the producer XaaS service and an ID of the C/M function entity of the producer XaaS service.
  • the determination process of the C/M function entity of the producer XaaS service is as follows: the C/M-TW-GW (the first network element) receives the first request message from the C/M function entity of the consumer XaaS service (the second network element) , determines the ID of the XaaS service requested by the C/M function entity of the consumer XaaS service based on the first request message, and determines the ID of the consumer XaaS service and the ID of the C/M function entity of the consumer XaaS service based on the C/M function entity of the consumer XaaS service (for example, C/M function entities of different consumer XaaS services may correspond to different interfaces on the first network element, so the first network element can know the C/M function entity of the consumer XaaS service based on the interface from which the first request message is received) , then the first network element looks up the preset authorization profile to determine a corresponding C/M function entity of the
  • the C/M-TW-GW can select any one of the candidate C/M function entities to provide the first basic service to the C/M function entity of the consumer XaaS service (the second network element) , the selection way may be as follows.
  • the authorization table is exemplarily shown in Table 2, as an implementation of the preset authorization profile.
  • a C/M-TW-GW may to keep a local authorization table for its authorization operation.
  • This table includes an entry for each pair of provider ID of a producer XaaS service and authorized provider ID of a consumer XaaS service.
  • Consumer XaaS service ID ID of a XaaS service which needs a service (action) from other XaaS service.
  • Producer XaaS service ID ID of a XaaS service which provides a service (action) to other XaaS service.
  • Provider ID of a XaaS service ID of provider (partner) which provides a XaaS service and has its entity in the BAS domain.
  • Token a value that is initialized at the time when a C/M-TW-GW selects a provider of requested XaaS service. This authorization remains valid during the time window when the token is valid. Note that a XaaS service can be provided by more than one providers/partners.
  • the determination process of the C/M function entity of the producer XaaS service (that is, the third network element mentioned above) is exemplarily described with reference to Table 2.
  • the Consumer XaaS service is a NET4AI service, and it requests a DAM service, the C/M function entity of the NET4AI service transmits a request message to the C/M-TW-GW which pre-stores the authorization table to request the DAM service, where the request message is used to indicate the DAM service requested by the C/M function entity of the NET4AI service; then the C/M-TW-GW looks up the authorization table based on the ID of the NET4AI service, the ID of the C/M function entity of the NET4AI service, the ID of the DAM service, to determine the C/M function entity of the DAM service as the C/M function entity of the Producer XaaS service.
  • the preset authorization profile is further indicative of a validity of the correspondence between the one third network element and the second network element, that means the connection between the one third network element and the second network element (the C/M function entities of the consumer and the producer) is not permanent, instead, such connection has a period of validity and may be expired if certain conditions are met.
  • the one third network element as a producer may be authorized to provide service to the second network element within a period of time, or for a preset number of times.
  • the determination of the third network element includes: the first network element determining a to-be-verified network element based on the first request message, the second network element and the preset authorization profile; the first network element verifying a validity of the to-be-verified network element based on the preset authorization profile; and the first network element determining the third network element based on a result of the verification. Based on the preset authorization profile indicating a validity of the correspondence, the validity of the connection between the third network element and the second network element can be ensured, and the valid third network element can be determined quickly, so that the operation efficiency of the first network element can be improved, and the system overhead can be reduced.
  • each candidate entity may be a to-be-verified network element mentioned above, since the preset authorization profile further includes the validity of the correspondence (which is indicated by the "token" in Table 2, for example) , the C/M-TW-GW may then select one entity from the candidate multiple entities of the producer XaaS service based on the validity of the correspondence.
  • the first network element determining, the third network element based on the result of the verification includes: upon determining that the validity of the to-be-verified network element is valid, the first network element determining the to-be-verified network element as the third network element.
  • the C/M-TW-GW determines one entity whose validity is valid among the candidate multiple entities as the entity providing the service to the C/M function entity of the consumer XaaS service, here the valid entity may be an entity that has interacted with the C/M function entity of the consumer XaaS service, or that is authorized to interact with the C/M function entity of the consumer XaaS service, e.g., within a valid period.
  • the first network element determining the third network element based on the result of the verification includes: upon determining that the validity of the to-be-verified network element is invalid, the first network element performing one of the following operations:
  • the invalid to-be-verified network element refers to a network element that has never interacted with the second network element
  • the determination of the third network element can be, for example, when one candidate entity of the producer XaaS service has never interacted with the C/M function entity of the consumer XaaS service
  • the C/M-TW-GW may determine the C/M function entity providing the service to the C/M function entity of the consumer XaaS service in two ways:
  • the invalid to-be-verified network element refers to a network element that has interacted with the second network element and whose validity is invalid (that is, the validity has expired)
  • the determination of the third network element can be, for example, when one candidate entity has interacted with the C/M function entity of the consumer XaaS service, but the validity period of the candidate entity has expired
  • the C/M-TW-GW may determine the C/M function entity providing the service to the C/M function entity of the consumer XaaS service in two ways:
  • the validity of the further candidate entity may be invalid, that is, the further candidate entity may have never communicated with the C/M function entity of the consumer XaaS service, so the first network element may also set the validity of the further candidate entity to be valid after selecting the further candidate entity.
  • the procedure for implementing the work requested by the second network element further includes: the first network element determining the multiple independent actions based on the first request message, where the first request message is further indicative of the multiple independent actions.
  • the first request message can include a field indicating the multiple independent actions to be performed by one or more third network elements for implementing the work requested by the second network element.
  • the procedure for implementing the work requested by the second network element further includes: the first network element determining the multiple conditional actions and a sequence of the multiple conditional actions based on the first request message, where the first request message is further indicative of the multiple conditional actions and the sequence of the multiple conditional actions.
  • the first request message can include fields indicating the multiple independent actions to be performed by one or more third network elements for implementing the work requested by the second network element and the sequence of the multiple conditional actions.
  • the first request message is further indicative of multiple first basic services (e.g., the above producer XaaS service) requested by the second network element; where determining, by the first network element based on the first request message, the procedure for implementing the work requested by the second network element further includes: the first network element determining one or more third network elements based on a preset authorization profile, the second network element and the first basic services, where the one or more third network elements are authorized to provide the multiple first basic services to the second network element respectively; where the preset authorization profile is indicative of a correspondence between each of the one or more third network elements and the second network element.
  • the preset authorization profile is indicative of a correspondence between each of the one or more third network elements and the second network element.
  • the determination process of the one or more third network elements is as same as that of the one third network element in the first mode, except that the first network element may determine multiple third network elements, e.g., the C/M-TW-GW selects multiple C/M function entities as the C/M function entities providing the multiple services to the C/M function entity of the consumer XaaS among the candidate entities of the producer XaaS service.
  • the first network element may determine multiple third network elements, e.g., the C/M-TW-GW selects multiple C/M function entities as the C/M function entities providing the multiple services to the C/M function entity of the consumer XaaS among the candidate entities of the producer XaaS service.
  • the first network element can determine the procedure for implementing the work simply based on the first request message.
  • the first network element determining, based on the first request message, the procedure for implementing the work requested by the second network element further includes: upon determining that the mode is the first mode, the first network element determining based on the first request message, the one action and a third network element for performing the one action, where the first request message is further indicative of the one action and the third network element.
  • the first network element determining, based on the first request message, the procedure for implementing the work requested by the second network element further includes: upon determining that the mode is the second mode, the first network element determining based on the first request message, the multiple independent actions and one or more third network elements for performing the multiple independent actions, where the first request message is further indicative of the multiple independent actions and the one or more third network elements.
  • the first network element determining based on the first request message, the procedure for implementing the work requested by the second network element further includes: upon determining that the mode is the third mode, the first network element determining based on the first request message, the multiple conditional actions, a sequence of the multiple conditional actions and one or more third network elements for performing the multiple conditional actions, where the first request message is further indicative of the multiple conditional actions, the sequence of the multiple conditional actions and the one or more third network elements.
  • the first request message In the case where the first request message is the second type of message, the first request message carries all information for determining the procedure for implementing the work requested by the second network element. For example, in the first mode, the first request message carries an ID of the one action as requested and ID of a third network element for performing the one action. In the second mode, the first request message carries IDs of the multiple independent actions as requested and ID (s) of the one or more third network elements for performing the multiple independent actions. In the third mode, the first request message carries IDs of the multiple conditional actions as requested, information indicative of the sequence of the multiple conditional actions and ID (s) of the one or more third network elements for performing the multiple conditional actions.
  • the first network element may interact with one or more third network elements, in the following, the specific interactions between the first network element and the one or more third network elements will be described.
  • the data processing method when the procedure is the first mode, further includes: the first network element transmitting a second request message to the third network element based on the first request message; and the first network element receiving from the third network element, a second response message corresponding to the second request message to obtain a first response message for the second network element based on the second response message.
  • the first network element may directly forward the first request message as the second request message to the third network element, or, the first network element may also add information (for protection purpose) into the first request message to obtain the second request message.
  • the first network element may directly take the second response message from the third network element as the first response message, or the first network element may also add information (e.g., for protection purpose) into the second response message to obtain the first response message.
  • the first response message and the second response message both include a processing result of the work requested by the second network element, such as information related to the first basic service requested by the second network element.
  • a response message (first response message) sent by the C/M function entity of the producer XaaS service (third network element) to the C/M-TW-GW (first network element) includes information related to the data collection (e.g., collected data)
  • the C/M-TW-GW sends a further response message (second response message) to the C/M function entity (second network element) of the consumer XaaS service
  • the further response message can be same as the response message, or can further include information for protecting the information included in the response message.
  • the first network element can effectively manage and control the interaction between the second network element and the one third network element.
  • the data processing method when the procedure is the first mode, further includes: the first network element transmitting the first response message to the second network element.
  • FIG. 9A illustrates an exemplary flowchart of the data processing method in the first mode described above, and the method includes the following steps.
  • the first network element may maintain a single action operation table during the operation of the one action in the first mode.
  • the table can include the following items: an ID of a message, an ID of a requested action, an ID of a consumer XaaS service, an ID of an entity/provider of the consumer XaaS service, an ID of a producer XaaS service, an ID of an entity/provider of the producer XaaS service and a status.
  • Table 3 exemplarily illustrates a single action operation table.
  • a C/M-TW-GW (the first network element) may maintain a single action operation table
  • Requested action ID an ID of an action or a basic procedure that can be requested by a consumer XaaS service and served by a producer of the requested XaaS service (that is the producer XaaS service mentioned above) .
  • Entity ID an ID of an entity that implements a C/M function of a XaaS service and is associated with a reachable address.
  • Status status of the action. It is set as Outstanding at a time when the C/M-TW-GW transmits a request message to the C/M function entity of the producer XaaS service; the status is set as Done after the response message corresponding to the action has be forwarded to the entity of the action requester (i.e., the C/M function entity of the consumer XaaS service) .
  • the C/M-TW-GW may maintain a local single action operation table. For each such operation, according to the received message from the C/M function entity of the consumer XaaS service, the C/M-TW-GW should obtain information such as the ID of the requested action, the ID of the consumer XaaS service, the ID of the entity/provider of the consumer XaaS service, and the ID of the requested producer XaaS service, as listed in columns 2, 3, 4 and 5 in Table 3. Based on the obtained information, the C/M-TW-GW should check its local active authorization table and determine an ID of an entity/Provider of the producer XaaS service, as listed in column 6. The entries of the table are filled by the C/M-TW-GW during the execution of the data processing method in the first mode.
  • the first network element receives a first request message from a second network element.
  • the first request message is indicative of a work requested by the second network element.
  • the first network element determines, based on the first request message, a mode of a procedure for implementing the work to be the first mode, and determines one action in the first mode and one third network element, the one third network element is authorized to provide one first basic service to the second network element.
  • the first network element transmits a second request message to the third network element based on the first request message, and records a status of the transmission of the second request message. For example, after transmitting the second request message to the third network element, the first network element records a status of the transmission of the second request message as “Outstanding” in the single action operation table as mentioned above. The status of “Outstanding” indicates that the third network element is instructed to perform the one action in the first mode and the one action has not been finished yet.
  • the first network element may directly forward the first request message as the second request message to the third network element, or, the first network element may also add information (for protection purpose) into the first request message to obtain the second request message.
  • the first network element receives a second response message corresponding to the second request message to obtain a first response message for the second network element based on the second response message.
  • the correspondence between the second response message and the second request message may be implemented in various ways, for example, both messages will carry a unique transaction number therein, or both messages will be through a unique interface between the first network element and the third network element.
  • the first network element may directly take the second response message from the third network element as the first response message, or the first network element may also add information (e.g., for protection purpose) into the second response message to obtain the first response message.
  • information e.g., for protection purpose
  • the first network element transmits the first response message to the second network element.
  • the first network element updates the status of the transmission. For example, after the second network element receives the first response message or after the first network element transmits the first response message, the first network element updates the status of the transmission from “Outstanding” to “Done” .
  • the status of “Done” indicates that the third network element has completed the execution of the one action and the result of the execution of the one action has been forwarded to the second network element.
  • FIG. 9B illustrates schematic flowchart of an exemplary data processing method in a first mode according to one or more embodiments of the present disclosure, that is, an exemplary operation of a first network element (i.e., C/M-TW-GW) in the first mode is shown in FIG. 9B.
  • a first network element i.e., C/M-TW-GW
  • the C/M-TW-GW first receives from a C/M function entity of a consumer XaaS service, a (request) message (aspecific example of the first request message mentioned above) that is corresponding to a request type of a single action in the first mode; determines that the operation mode is the first mode and an ID of the single action (i.e., the action ID shown in FIG. 9B) corresponding to the first mode based on the received message; and further determines, based on the received message, an ID of a XaaS service (i.e., the requested XaaS service ID or a producer XaaS service ID shown in FIG.
  • a (request) message (aspecific example of the first request message mentioned above) that is corresponding to a request type of a single action in the first mode
  • determines that the operation mode is the first mode and an ID of the single action i.e., the action ID shown in FIG. 9B
  • an ID of a XaaS service
  • the C/M-TW-GW checks an active authorization table (i.e., Table 2 as mentioned above) , and determines whether the authorization has been performed, that is, determines whether the "token" in Table 3 is valid, where the token being valid indicates that there is an entity of the producer XaaS service that has interacted with the C/M function entity of the consumer XaaS service and the validity of the C/M function entity of the producer XaaS service has not expired, if yes, the C/M-TW-GW updates the token (e.g., the C/M-TW-GW updates the period of validity during which the C/M function entity of the producer XaaS service can provide service to the C/M function entity of the consumer XaaS service or updates the times for which the C/M function entity of the producer XaaS service can provide service to the C/M function entity of the consumer XaaS service) ; if not, the C/M-TW-GW initializes the value of the token
  • the C/M-TW-GW forwards the message (aspecific example of the second request message mentioned above) to the determined C/M function entity of the producer XaaS service, and sets column “status (aspecific example of the status of the transmission of the second request message mentioned above) ” in Table 3 as “Outstanding” .
  • the C/M-TW-GW may also process the message from the C/M function entity of the consumer XaaS service to obtain the message to be delivered to the determined C/M function entity of the producer XaaS service.
  • the C/M-TW-GW receives a response message (a specific example of the second response message mentioned above) which may include an ID indicating that the message is a response message; checks the single action operation table mentioned above to determine whether there is a corresponding entry with status of “Outstanding” , if yes, it indicates that the received response message corresponds to the request message from the C/M function entity of the consumer XaaS service, and the C/M-TW-GW transmits the response message (aspecific example of the first response message mentioned above) to the C/M function entity of the consumer XaaS service and modifies the “status” in Table 3 from “Outstanding” to “Done” ; if not, it indicates that the received response message does not correspond to the request message from the C/M function entity of the consumer XaaS service, the C/M-TW-GW removes the received response message or performs error processing on the
  • the data processing method when the procedure is the second mode, further includes: the first network element transmitting multiple second request messages to the one or more third network elements respectively based on the first request message; for each of the multiple second request messages, the first network element receiving a second response message corresponding to the second request message from a third network element receiving the second request message; the first network element determining whether second response messages corresponding to the second request messages one-by-one from the one or more third network elements have been received; and upon determining that the second response messages from the one or more third network elements have been received, the first network element obtaining a first response message for the second network element based on the second response messages.
  • a second request message may be transmitted from the first network element to the third network element for triggering each action, and a corresponding second response message will be obtained after the action is performed. Then the first response message can be obtained upon determining that all the second response messages corresponding to the second request messages for triggering the multiple independent actions have been received.
  • the first network element receives the response messages from all the third network elements, thus ensuring that the service is correctly provided by the third network element to the second network elements.
  • the data processing method when the procedure is the third mode, further includes: upon determining that a triggering condition for transmitting a second request message is met, the first network element transmitting the second request message to a third network element of the one or more third network elements; the first network element receiving a second response message corresponding to the second request message from the third network element; the first network element determining whether second response messages corresponding to second request messages one-by-one from the one or more third network elements have been received; and upon determining that the second response messages from the one or more third network elements have been received, the first network element obtaining a first response message for the second network element based on the second response messages.
  • a second request message may be transmitted from the first network element to the third network element for triggering each action, and a corresponding second response message will be obtained after the action is performed. Then the first response message can be obtained upon determining that all the second response messages corresponding to the second request messages for triggering the multiple conditional actions have been received.
  • the first network element receives the response messages from the one or more third network elements, thus ensuring that the service is correctly provided by the third network element to the second network elements.
  • the determination of the triggering condition can be omitted, or it can be determined that the triggering condition for transmitting the second request message is met; and when the second request message is not the first second request message transmitted from the first network element to the third network element, the data processing method needs to follows the above steps, that is, first determining the triggering condition, then transmitting the second request message, and receiving the second response message, etc.
  • the triggering condition can be that the first network element receives the second response message corresponding to the previous action, and there is an action that needs to be executed after this previous action among the multiple conditional actions, it should be noted that the example is simply for illustration purpose, and the triggering condition is not limited in the embodiments of the present disclosure.
  • the data processing method when the procedure is the second mode or the third mode, the data processing method further includes: the first network element recording a status of the transmission of the second request messages; and upon receiving the second response messages, the first network element updating the status.
  • the first network element can effectively manage and control the interaction between the second network element and each of the one or more third network elements.
  • the data processing method when the procedure is the second mode or the third mode, the data processing method further includes: the first network element transmitting the first response message to the second network element.
  • the first network element may maintain a multiple actions operation table during the operation of the multiple actions in the second mode or third mode.
  • the table can include the following items: an ID of a message from a consumer XaaS service, an ID of a requested action, an ID of a consumer XaaS service, an ID of an entity/provider of the consumer XaaS service, an ID of a producer XaaS service, an ID of an entity/provider of the producer XaaS service, a status corresponding to each of the multiple actions, a condition triggering for next action (in the third mode case) , a status of multiple actions operation.
  • Table 4 exemplarily illustrates a multiple actions operation table.
  • a C/M-TW-GW may maintain a local multiple actions operation table.
  • the multiple actions operation include multiple single action operations.
  • the C/M-TW-GW For each action operation of such multiple action operation, according to the received message from the entity of the consumer XaaS service, the C/M-TW-GW should obtain information such as the IDs of the requested multiple actions and associated information as listed in columns 3, 4 and 5 of Table 4, check its local active authorization table and determine IDs of an entities of the producer XaaS services, as listed in column 6. The entries of the table are filled by the C/M-TW-GW during the execution of the data processing method in the second or third mode.
  • condition triggering next action indicates condition (s) for triggering next action. If a request message triggers multiple independent actions, that is, the request message indicates that the operation mode of the C/M-TW-GW is the second mode, the column “condition triggering next action” may be omitted or set as N/A.
  • the Status of multiple actions operation indicates the final status of the operation. It is set as “Done” when either all of actions complete or condition for triggering next action is not satisfied for dependent action case. Otherwise it is set as “Outstanding” .
  • FIG. 10A illustrates an exemplary flowchart of the data processing method in the second mode described above, and the method includes the following steps.
  • the first network element receives a first request message from a second network element.
  • the first request message is indicative of a work requested by the second network element.
  • the first network element determines, based on the first request message, a mode for implementing the work to be the second mode, and determines multiple independent actions in the second mode and multiple third network elements (i.e., third network element 1 and third network element 2 shown in FIG. 10A, the third network element 1 and the third network element 2 are configured for performing different independent actions, and their interactions with the first network element are similar) , the multiple third network elements are authorized to provide multiple first basic services to the second network element.
  • the two third network elements shown in the figure are simply exemplary, and there could be other number of third network elements in actual applications.
  • the first network element transmits the multiple second request messages to the multiple third network elements based on the first request message respectively, and records status of the transmissions of the second request messages to multiple third network elements respectively. For example, after transmitting the multiple second request messages to the multiple third network elements, the first network element records status of the transmissions of the second request messages transmitted to the multiple third network elements as “Outstanding” one-by-one in the multiple action operation table.
  • the second request message for each of the multiple third network elements may carry information indicating the action to be performed by this third network element and the basic service required to be provide by this third network element. That is, the first network element may parse the first request message to obtain the second request message specific to each third network element.
  • the first network element receives a second response message corresponding to the second request message from a third network element receiving the second request message, and updates the status of the transmission. For example, after the first network element receives the second response message corresponding to the second request message from a third network element receiving the second request message, the first network element updates the status of the transmission corresponding to this second request message from “Outstanding” to “Done” .
  • the correspondence between the second response message and the second request message may be implemented in various ways, for example, both messages will carry a unique transaction number therein, or both messages will be through a unique interface between the first network element and the third network element.
  • the first network element determines that the second response messages from all the multiple third network elements have been received, and obtains a first response message for the second network element based on the second response messages.
  • first network element may simply combine the second response messages from all the multiple third network elements or may further add other information therein, which is not limited in the embodiments of the present disclosure.
  • the first network element transmits the first response message to the second network element, and updates the status of the transmission of the first response message (for example, the status of the multiple actions operation as listed in the last column of Table 4) , where the status of the transmission of the first response message can be set to “Outstanding” in the initial state. For example, after the second network element receives the first response message or after the first network element transmits the first response message, the first network element updates the status of the transmission from “Outstanding” to “Done” .
  • FIG. 10B illustrates schematic flowchart of an exemplary data processing method in a second mode according to one or more embodiments of the present disclosure, that is, an exemplary operation of a first network element (i.e., C/M-TW-GW) in the second mode is shown in FIG. 10B.
  • a first network element i.e., C/M-TW-GW
  • the C/M-TW-GW first receives from a C/M function entity of a consumer XaaS service, a (request) message (aspecific example of the first request message mentioned above) that is corresponding to a request type of multiple independent actions in the second mode; determines that the operation mode is the second mode and IDs of the multiple independent actions based on the received message; and creates a multiple actions operation table (i.e., the Table 4 mentioned above) based on the determined the multiple independent actions, e.g., fills the IDs of the multiple independent actions in the second column of Table 4.
  • a (request) message (aspecific example of the first request message mentioned above) that is corresponding to a request type of multiple independent actions in the second mode
  • creates a multiple actions operation table i.e., the Table 4 mentioned above
  • the C/M-TW-GW may maintain a corresponding Table 4 each request message from a C/M function entity of a consumer XaaS service, or may also maintain a whole table for all request messages from C/M function entities of consumer XaaS services, which is not limited in the embodiments of the present disclosure.
  • the C/M-TW-GW performs the actions 1 to 6 in the first mode shown in FIG. 9B, the actions 1 to 6 are as follows: the C/M-TW-GW determines, based on the received message, an ID of a XaaS service (i.e., the requested XaaS service ID or a producer XaaS service ID shown in FIG.
  • the C/M-TW-GW determines whether there is an action that has not undergone the above operations, if yes, the C/M-TW-GW continues to perform the above operations 1-6, if not, the flow returns back to the receiving of the request message. That is, the C/M-TW-GW continues to wait another request message from another C/M function entity of a consumer XaaS service.
  • the C/M-TW-GW receives a response message (aspecific example of the second response message mentioned above) which may include an ID indicating that the message is a response message from the corresponding C/M function entity of the producer XaaS service; checks the multiple actions operation table (i.e., Table 4 mentioned above) to determine whether there is a corresponding entry with status for this action of “Outstanding” , if yes, it indicates that the received response message corresponds to the request message from the C/M function entity of the consumer XaaS service, and the C/M-TW-GW modifies the “status” for this action in Table 4 from “Outstanding” to “Done” ; if not, it indicates that the received response message does not correspond to the request message, the C/M-TW-GW removes the received response message (aspecific example of the second response message mentioned above) which may include an ID indicating that the message is a response message from the corresponding C/M function entity of the producer XaaS service; checks the multiple actions operation
  • the C/M-TW-GW determines whether there is an action with the status of “Outstanding” , if yes, it means that a C/M function entity of a producer XaaS service which receives the (request) message from the first network element and performs this action has not yet fed back a response message, the C/M-TW-GW returns to perform the operations such as receiving the response message and checking it using Table 4 and the like as described above; if not, it means that all the responses have been received from the C/M function entities of the multiple producer XaaS services have been received, the C/M-TW-GW then creates a response message (aspecific example of the first response message mentioned above) , and transmits it to the C/M function entity of the consumer XaaS service; finally, the C/M-TW-GW modifies the “status for the multiple actions operation” in Table 4 from “Outstanding” to “Done” .
  • FIG. 11A illustrates an exemplary flowchart of the data processing method in the third mode described above, and the method includes the following steps.
  • the first network element receives a first request message from a second network element.
  • the first request message is indicative of a work requested by the second network element.
  • the first network element determines, based on the first request message, a mode for implementing the work to be the third mode, and determines multiple conditional actions and a sequence of the multiple conditional actions in the third mode and multiple third network elements (i.e., third network element 1 and third network element 2 shown in FIG. 11A, the third network element 1 and the third network element 2 are configured for performing different conditional actions, and their interactions with the first network element are similar) , the multiple third network elements are authorized to provide multiple first basic services to the second network element.
  • the two third network elements shown in the figure are simply exemplary, and there could be other number of third network elements in actual applications.
  • the first network element transmits a second request message to a third network element of the multiple third network elements based on the first request message; and records status of the transmission of the second request message. For example, after transmitting the second request message to the third network element, the first network element records a status of the transmission of the second request message corresponding to Action 1 in Table 4 as “Outstanding” .
  • the second request message for the third network element may carry information indicating the action to be performed by this third network element and the basic service required to be provide by this third network element. That is, the first network element may parse the first request message to obtain the second request message specific to each third network element.
  • the first network element receives a second response message corresponding to the second request message from the third network element, and updates the status of the transmission. For example, after the first network element receives the second response message corresponding to the second request message, the first network element updates the status of the transmission from “Outstanding” to “Done” .
  • the first network element determines whether a triggering condition for transmitting a next second request message is met, if yes, returns to perform steps S1103-S1104; if not, continues to perform step S1106.
  • the first network element determines that the second response messages from all the multiple third network elements have been received, and obtains a first response message for the second network element based on the second response messages.
  • first network element may simply combine the second response messages from all the multiple third network elements or may further add other information therein, which is not limited in the embodiments of the present disclosure.
  • the first network element transmits the first response message to the second network element, and updates the status of the transmission of the first response message (for example, the status of the multiple actions operation as listed in the last column of Table 4) , where the status of the transmission of the first response message can be set to “Outstanding” in the initial state. For example, after the second network element receives the first response message or after the first network element transmits the first response message, the first network element updates the status of the transmission from “Outstanding” to “Done” .
  • FIG. 11A only two third network elements are illustrated and each of them performs one action, but the number of the third network elements and the number of actions performed by the third network elements are not limited in the embodiments of the present disclosure.
  • FIG. 11B illustrates schematic flowchart of an exemplary data processing method in a third mode according to one or more embodiments of the present disclosure, that is, an exemplary operation of a first network element (i.e., C/M-TW-GW) in the third mode is shown in FIG. 11B.
  • a first network element i.e., C/M-TW-GW
  • FIG. 11B For the first action of the multiple actions, the processes of the method shown in FIG. 11B before determining whether there is a next action (i.e., determining whether there is an action with the status of “Outstanding” in FIG. 10B) and the process of the above determination are similar to those shown in FIG. 10B.
  • the C/M-TW-GW determines whether a condition for triggering the next action is met, if yes, returns to perform the Action 1 as shown in FIG. 9B; if not, creates a response message (aspecific example of the first response message mentioned above) , transmits it to the C/M function entity of the consumer XaaS service, and modifies the “status for the multiple actions operation” in Table 4 from “Outstanding” to “Done” .
  • the C/M-TW-GW After determining that there is no next action, the C/M-TW-GW creates a response message (i.e., the first response message mentioned above) , transmits it to the C/M function entity of the consumer XaaS service, and modifies the “status for the multiple actions operation” in Table 4 from “Outstanding” to “Done” .
  • An implementation of the present disclosure provides a data processing method for a second network element (i.e., a C/M function entity of a consumer XaaS service) .
  • the data processing method may include:
  • the second network element transmitting a first request message to a first network element, where the first request message is indicative of a work requested by the second network element.
  • An implementation of the present disclosure provides a data processing method for a third network element (i.e., a C/M function entity of a producer XaaS service) .
  • the data processing method may include:
  • the third network element receiving a second request message from a first network element, where the second request message is determined based on a first request message, and the first request message is indicative of a work requested by a second network element;
  • the third network element transmitting a second response message corresponding to the second request message to the first network element, where the second response message is used to obtain a first response message corresponding to the first request message for the second network element.
  • FIG. 12 shows a schematic structural diagram of a data processing apparatus according to an embodiment of the present disclosure.
  • the data processing apparatus 1200 may include:
  • a receiving module 1201 configured to receive a first request message from a second network element, where the first request message is indicative of a work requested by the second network element;
  • a determining module 1202 configured to determine, based on the first request message, a procedure for implementing the work requested by the second network element.
  • the procedure is one of a first mode, a second mode or a third mode; here in the first mode, one action is taken for implementing the work; here in the second mode, multiple independent actions are taken for implementing the work; here in the third mode, multiple conditional actions are taken for implementing the work.
  • the determining module 1202 is configured to: determine based on the working identification, the mode among the first mode, the second mode and the third mode for implementing the work.
  • determining module 1202 is further configured to: upon determining that the mode is the first mode, determine the one action based on the first request message, where the first request message is further indicative of the one action.
  • determining module 1202 is further configured to: upon determining that the mode is the second mode, determine the multiple independent actions based on the first request message, where the first request message is further indicative of the multiple independent actions.
  • the determining module 1202 is further configured to: upon determining that the mode is the third mode, determine the multiple conditional actions and a sequence of the multiple conditional actions based on the first request message, where the first request message is further indicative of the multiple conditional actions and the sequence of the multiple conditional actions.
  • the first request message is further indicative of at least one first basic service requested by the second network element
  • determining module 1202 is further configured to: determine at least one third network element based on a preset authorization profile, the second network element and the first basic service, where the at least one third network element is authorized to provide the at least one first basic service to the second network element;
  • the preset authorization profile is indicative of a correspondence between each of the at least one third network element and the second network element.
  • the preset authorization profile is further indicative of a validity of the correspondence
  • determining module 1202 is configured to:
  • determining module 1202 is configured to: upon determining that the validity of the to-be-verified network element is valid, determine the to-be-verified network element as the third network element.
  • the determining module 1202 is configured to perform one of the following operations:
  • the correspondence between the third network element and the second network element is represented by a correspondence between an identification of a second basic service to which the second network element belongs, an identification of the second network element, an identification of the first basic service to which a third network element belongs and an identification of the third network element.
  • the determining module 1202 is further configured to: upon determining that the mode is the first mode, determine based on the first request message, the one action and a third network element for performing the one action, where the first request message is further indicative of the one action and the third network element.
  • determining module 1202 is further configured to: upon determining that the mode is the second mode, determine based on the first request message, the multiple independent actions and one or more third network elements for performing the multiple independent actions, where the first request message is further indicative of the multiple independent actions and the one or more third network elements.
  • the determining module 1202 is further configured to: upon determining that the mode is the third mode, determine based on the first request message, the multiple conditional actions, a sequence of the multiple conditional actions and one or more third network elements for performing the multiple conditional actions, where the first request message is further indicative of the multiple conditional actions, the sequence of the multiple conditional actions and the one or more third network elements.
  • apparatus further includes:
  • a first transmitting module configured to transmit a second request message to the third network element based on the first request message
  • the receiving module 1201 is further configured to receive from the third network element, a second response message corresponding to the second request message to obtain a first response message for the second network element based on the second response message.
  • the apparatus further includes: a first recording module, configured to record a status of the transmission of the second request message; and a first updating module, configured to, upon receiving the second response message, update the status.
  • the apparatus further includes:
  • a second transmitting module configured to transmit multiple second request messages to the one or more third network elements respectively based on the first request message
  • the receiving module 1201 is further configured to receive, for each of the multiple second request messages a second response message corresponding to the second request message from a third network element receiving the second request message;
  • the determining module is further configured to determine whether second response messages corresponding to the second request messages one-by-one from the one or more third network elements have been received;
  • the apparatus further includes: a first obtaining module, configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • a first obtaining module configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • the apparatus further includes: a third transmitting module, configured to, upon determining that a triggering condition for transmitting a second request message is met, transmit the second request message to a third network element of the one or more third network elements;
  • the receiving module 1201 is further configured to receive a second response message corresponding to the second request message from the third network element;
  • the determining module 1202 is further configured to determine whether second response messages corresponding to second request messages one-by-one from the one or more third network elements have been received;
  • the apparatus further includes: a second obtaining module, configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • a second obtaining module configured to, upon determining that the second response messages from the one or more third network elements have been received, obtain a first response message for the second network element based on the second response messages.
  • the apparatus further includes: a second recording module, configured to record a status of the transmission of the second request messages; and a second updating module, configured to, upon receiving the second response messages, update the status.
  • each of the first transmitting module, the second transmitting module and the third module is further configured to transmit the first response message to the second network element.
  • An implementation of the present disclosure provides a data processing apparatus, the data processing apparatus may include: a transmitting module, configured to transmit a first request message to a first network element, where the first request message is indicative of a work requested by the second network element.
  • the data processing apparatus may further include: a receiving module, configured to receive a first response message from the first network element in response to the first request message.
  • An implementation of the present disclosure provides a data processing apparatus, the data processing apparatus may include:
  • a receiving module configured to receive a second request message from a first network element, where the second request message is determined based on a first request message, and the first request message is indicative of a work requested by a second network element;
  • a transmitting module configured to transmit a second response message corresponding to the second request message to the first network element, where the second response message is used to obtain a first response message corresponding to the first request message for the second network element.
  • An embodiment of the present disclosure provides a first network element including processing circuitry for executing any of the above data processing methods.
  • An embodiment of the present disclosure provides a second network element including processing circuitry for executing any of the above data processing methods.
  • An embodiment of the present disclosure provides a third network element including processing circuitry for executing any of the above data processing methods.
  • An embodiment of the present disclosure provides a computer-readable medium storing computer execution instructions which, when executed by a processor, causes the processor to execute any of the above data processing methods.
  • An embodiment of the present disclosure provides a computer program product including computer execution instructions which, when executed by a processor, causes the processor to execute any of the above data processing methods.
  • An embodiment of the present disclosure provides a wireless system, including the above first network element, the second network element and the third network element.
  • An embodiment of the present disclosure provides an apparatus, including one or more processors, the one or more processors are configured to execute instructions stored in memory, when the instructions is executed by the one or more processors, any of the above data processing methods is performed.
  • network elements mentioned in the present disclosure are all logical network elements, which can be implemented as individual devices, or can be implemented as chips or modules that could be integrated into a certain device.
  • the expression “at least one of A or B” is interchangeable with the expression “A and/or B” . It refers to a list in which you may select A or B or both A and B.
  • “at least one of A, B, or C” is interchangeable with “A and/or B and/or C” or “A, B, and/or C” . It refers to a list in which you may select: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B and C. The same principle applies for longer lists having a same format.
  • the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware components, software or any combination of the two. Accordingly, the technical solution of the present disclosure may be embodied in the form of a software product.
  • a suitable software product may be stored in a pre-recorded storage device or other similar non-volatile or non-transitory computer readable medium, including DVDs, CD-ROMs, USB flash disk, a removable hard disk, or other storage media, for example.
  • the software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, a server, or a network device) to execute examples of the methods disclosed herein.
  • a processing device e.g., a personal computer, a server, or a network device
  • the machine-executable instructions may be in the form of code sequences, configuration information, or other data, which, when executed, cause a machine (e.g., a processor or other processing device) to perform steps in a method according to examples of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un procédé de traitement de données et des produits associés, le procédé comprenant les étapes suivantes : un premier élément de réseau reçoit un premier message de demande provenant d'un second élément de réseau, le premier message de demande indiquant un travail demandé par le second élément de réseau ; et le premier élément de réseau détermine, sur la base du premier message de demande, une procédure pour mettre en œuvre le travail demandé par le second élément de réseau.
PCT/CN2024/075631 2023-08-31 2024-02-02 Procédé de traitement de données et produits associés Pending WO2025044063A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363535643P 2023-08-31 2023-08-31
US63/535643 2023-08-31

Publications (1)

Publication Number Publication Date
WO2025044063A1 true WO2025044063A1 (fr) 2025-03-06

Family

ID=94818043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/075631 Pending WO2025044063A1 (fr) 2023-08-31 2024-02-02 Procédé de traitement de données et produits associés

Country Status (1)

Country Link
WO (1) WO2025044063A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7602762B1 (en) * 2000-07-26 2009-10-13 Nokia Corporation System and method for determining when a CSCF should act like I-CSCF or like S-CSCF
WO2019184293A1 (fr) * 2018-03-29 2019-10-03 Oppo广东移动通信有限公司 Procédé de commutation entre des éléments de réseau et de sélection d'élément de réseau, équipement d'utilisateur, élément de réseau
WO2021083026A1 (fr) * 2019-10-31 2021-05-06 大唐移动通信设备有限公司 Procédé et dispositif de traitement d'informations, équipement et support de stockage lisible par ordinateur
WO2022174794A1 (fr) * 2021-02-21 2022-08-25 华为技术有限公司 Procédé de communication et appareil de communication
CN116232594A (zh) * 2021-12-03 2023-06-06 维萨国际服务协会 令牌处理系统和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7602762B1 (en) * 2000-07-26 2009-10-13 Nokia Corporation System and method for determining when a CSCF should act like I-CSCF or like S-CSCF
WO2019184293A1 (fr) * 2018-03-29 2019-10-03 Oppo广东移动通信有限公司 Procédé de commutation entre des éléments de réseau et de sélection d'élément de réseau, équipement d'utilisateur, élément de réseau
WO2021083026A1 (fr) * 2019-10-31 2021-05-06 大唐移动通信设备有限公司 Procédé et dispositif de traitement d'informations, équipement et support de stockage lisible par ordinateur
WO2022174794A1 (fr) * 2021-02-21 2022-08-25 华为技术有限公司 Procédé de communication et appareil de communication
CN116232594A (zh) * 2021-12-03 2023-06-06 维萨国际服务协会 令牌处理系统和方法

Similar Documents

Publication Publication Date Title
LEI. et al. 5G system design
CN116648933A (zh) 无线通信网络中的感测系统、方法和装置
CN116848916A (zh) 用于无线通信系统的基于波束的测量和资源管理技术
CN109462462A (zh) 一种被用于无线通信的用户、基站中的方法和装置
CN110739988B (zh) 一种被用于无线通信的用户设备、基站中的方法和装置
CN112804038A (zh) 一种被用于无线通信的节点中的方法和装置
CN119790637A (zh) 用于无线ai/ml的rrc过程设计
CN110401516B (zh) 一种被用于无线通信的第一节点、基站中的方法和装置
CN112751656A (zh) 一种被用于无线通信的节点中的方法和装置
CN115834011B (zh) 一种被用于无线通信的节点中的方法和装置
WO2025044063A1 (fr) Procédé de traitement de données et produits associés
WO2025044062A1 (fr) Procédé de communication et produits associés
WO2025044065A1 (fr) Procédé de configuration et produits associés
CN115119309B (zh) 一种被用于无线通信的节点中的方法和装置
WO2025044064A1 (fr) Système de communication et produits associés
WO2025065970A1 (fr) Procédé et appareil de communication
WO2025065976A1 (fr) Procédé et appareil de communication
WO2025065973A1 (fr) Procédé et appareil de communication
WO2025066064A1 (fr) Procédé, appareil et système de communication pour session de mission
WO2025091739A1 (fr) Procédé, appareil et support de stockage lisible pour une communication
WO2025065975A1 (fr) Procédé et appareil de communication
WO2025066063A1 (fr) Procédé, appareil et système de communication pour session de mission
WO2025091741A1 (fr) Dispositif, procédé, appareil et support de stockage lisible pour gestion de ressources
CN118661436A (zh) 用于uav联网订阅管理的技术
WO2025081774A1 (fr) Procédé et appareil de commande de trafic d'utilisateur avec un utilisateur numérique

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24857620

Country of ref document: EP

Kind code of ref document: A1