[go: up one dir, main page]

WO2025179559A1 - Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil - Google Patents

Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil

Info

Publication number
WO2025179559A1
WO2025179559A1 PCT/CN2024/079434 CN2024079434W WO2025179559A1 WO 2025179559 A1 WO2025179559 A1 WO 2025179559A1 CN 2024079434 W CN2024079434 W CN 2024079434W WO 2025179559 A1 WO2025179559 A1 WO 2025179559A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
data service
data
network node
node
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/079434
Other languages
English (en)
Inventor
Li Yang
Fei Wang
Wenwen SUN
Feng Xie
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2024/079434 priority Critical patent/WO2025179559A1/fr
Publication of WO2025179559A1 publication Critical patent/WO2025179559A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Definitions

  • the present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods and devices for transferring data service control data in a wireless communication system.
  • Wireless technologies are moving the world toward an increasingly connected and networked society.
  • High-speed and low-latency wireless communication system rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations and/or core networks) .
  • a new generation network is expected to provide various data services, in addition to conventional communication service, with high speed, low latency, and highly reliable capabilities, so as to fulfill requirements under various circumstances.
  • the various data services may include sensing service, computing service, artificial intelligence (AI) service, storage service, and/or security service.
  • AI artificial intelligence
  • storage service storage service
  • security service There are some issues/problems associates with these various data services. For one non-limiting example, how to transfer data service control data across various network nodes for performing various data service.
  • the present disclosure describes various embodiments for transferring data service control data in a wireless communication system, addressing at least one of the issues/problems discussed in the present disclosure, thus increasing efficiency of various data services, enabling future wireless communication system to support or handle the forward/transfer of data service data (e.g. content of data service) , and/or adapting to various demands of new generation wireless services in wireless communication systems.
  • data service data e.g. content of data service
  • This document relates to methods, systems, and devices for wireless data service via wireless communication, and more specifically, for transferring data service control data in a wireless communication system, which is beneficial to enhance efficient utilization of wireless resources, increase the telecommunication resource utilization efficiency, and/or boost performance of the wireless data service via wireless communication.
  • the present disclosure describes a method for transferring data service control data for data service via wireless communication.
  • the method includes sending, by a first data agent’s control part (DA-C) entity within a first network node, first data service control data to a second network node, so that the second network node communicates with a second DA-C entity within a third network node for performing data service based on the first data service control data generated by the first DA-C, wherein the second DA-C entity generates second data service control data indicating a target data agent’s execution part (DA-E) entity associated with the second DA-C entity; and receiving, by the first DA-C entity from the second network node, the second data service control data for establishing a data service session channel between the first network node and the third network node, wherein the data service session channel is via a communication service session channel between the first network node and the third network node, so that data service data (e.g.
  • D-C control part
  • the first network node is a data service requesting node
  • the second network node is a data service anchor node or data service response node
  • the third network node is a data service response node.
  • the present disclosure describes another method for transferring data service control data for data service via wireless communication.
  • the method includes receiving, from a first data agent’s control part (DA-C) entity within a first network node by a second network node, first data service control data; communicating, by the second network node, with a second DA-C entity within a third network node for performing data service based on the first data service control data generated by the first DA-C, wherein the second DA-C entity generates second data service control data indicating a target data agent’s execution part (DA-E) entity associated with the second DA-C entity; and sending, by the second network node to the first DA-C entity, the second data service control data for establishing a data service session channel between the first network node and the third network node, wherein the data service session channel is via a communication service session channel between the first network node and the third network node, so that data service data is transferred between the first network node and the target DA-E entity via the communication service
  • an apparatus for transferring data service control data for data service via wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a device for transferring data service control data for data service via wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods.
  • the computer-readable medium may be a non-transitory computer-readable medium.
  • FIG. 1A shows an example of a wireless communication system.
  • FIG. 1B shows a schematic diagram of various embodiments in the present disclosure.
  • FIG. 1C shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 1D shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 2 shows an example of a network node.
  • FIG. 3 shows an example of a user equipment.
  • FIG. 4 shows a schematic diagram of various embodiments in the present disclosure.
  • FIG. 5 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 6 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 7 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 8A shows a flow diagram of a method for transferring data service control data for data service via wireless communication.
  • FIG. 8B shows a flow diagram of another method for transferring data service control data for data service via wireless communication.
  • FIG. 9 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 10 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 11 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 12 shows another schematic diagram of various embodiments in the present disclosure.
  • FIG. 13 shows another schematic diagram of various embodiments in the present disclosure.
  • terms, such as “a” , “an” , or “the” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • the present disclosure describes methods and devices for transferring data service control data in a wireless communication system.
  • Wireless technologies are moving the world toward an increasingly connected and networked society.
  • High-speed and low-latency wireless communication system rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations and/or core networks) .
  • New generation networks are expected to provide various data services, in addition to conventional communication service, with high speed, low latency, and highly reliable capabilities, so as to fulfill requirements under various circumstances.
  • a 5G-advanced (5G-A) and 6G wireless communication systems may expect to integrate and/or harmonize various sensing, computing, artificial intelligence (AI) , storage, and/or security new functions/services along with their own classical communication functions/services.
  • the 5G-A and 6G core network (CN) and/or radio access network (RAN) node may expect to be able to provide both wireless communication service and wireless sensing, computing, AI, storage, and/or security new services.
  • a conventional method of protocol data unit (PDU) session management in legacy 5G wireless communication system may be mainly targeted for forwarding/transferring user plane (UP) data, which is normally associated with external mobile users’ services, such as mobile application (APP) and web services.
  • UP data is normally generated outside 5G wireless communication system (transparent/invisible to 3GPP protocols) , and it is either originated/terminated at a user equipment (UE) or a data network server.
  • the 5G CN and/or RAN nodes may need not to concern about the UP data type/content or characteristics of user data, and simply process and forward them from the input port to output port based on internal UP processing unit and protocols.
  • any 5G-A and/or 6G CN and/or RAN node or UE may also be allowed to originate so call “data service session” on local demand and/or terminate the “data service session” at any other CN and/or RAN node or UE, and the intermediate/relay network (NW) node along the “data service session path” may also need to concern about the type/content/characteristics of the data service data.
  • NW intermediate/relay network
  • a new data agent (DA) logic entity or node may be defined and responsible for managing various 6G new data services.
  • a control part of the DA may be the logic controlling part of the DA, and responsible for configuring, coordinating, and/or monitoring data service session across different network (NW) nodes.
  • the DA-C may normally generate control data (e.g., called data service control data for its one or multiple associated logic executing part of the DA (DA-E) , located either in the same NW node or other NW nodes.
  • the DA-E entities may then take the corresponding data handling actions upon receiving the data service control data from its associated DA-C, such as data service policy guidance, action orders, and detailed configuration parameters etc.
  • data service policy guidance such as data service policy guidance, action orders, and detailed configuration parameters etc.
  • the present disclosure describes various designs, models, and/or methods for transferring data service control data in a wireless communication system for performing data service, enabling future wireless communication system to support or handle the forward/transfer of data service data, and/or adapting to various demands of various new services.
  • FIG. 1A shows a wireless communication system 100 including a core network (CN) 110, a radio access network (RAN) 130, and one or more user equipments (UEs) (152, 154, and 156) .
  • the RAN 130 may include one or more base stations.
  • the base stations may include at least one evolved NodeB (eNB) for 4G Long Term Evolution (LTE) , or a Next generation NodeB (gNB) for 5G New Radio (NR) , or a NodeB for 6G, or any other type of signal transmitting/receiving device such as a UMTS NodeB.
  • the core network 110 may include a 5G core network (5GC)
  • the interface 125 may include a new generation (NG) interface.
  • the core network 110 further includes at least one policy control function (PCF) , and/or at least one session management function (SMF) , and/or at least one user plane function (UPF) and/or at least one access and mobility management Function (AMF) .
  • a first UE 152 may receive one or more downlink communication 142 from the RAN 130 and send one or more uplink communication 141 to the RAN 130.
  • a second UE 154 may receive downlink communication 144 from the RAN 130 and send uplink communication 143 to the RAN 130; and
  • a third UE 156 may receive downlink communication 146 from the RAN 130 and send uplink communication 145 to the RAN 130.
  • a downlink communication may include a physical downlink (DL) shared channel (PDSCH) or a physical downlink control channel (PDCCH)
  • a uplink (UL) communication may include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) .
  • the core network may include one or more core network functions, as shown in FIG. 1B, which are described below.
  • the core network may communicate with a UE 171 (or via a RAN 172) .
  • the UPF 173 may perform the functionalities including but not limited to serving as an anchor point for intra-/inter-radio access technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, quality of service (QoS) handling for the user plane, downlink packet buffering and downlink data notification triggering.
  • the AMF 176 may perform the functionalities including but not limited to registration management, connection management of, reachability management and mobility management of UE 171. AMF also performs access authentication and access authorization.
  • the AMF 176 may have function as non-access stratum (NAS) security termination and relay the session management NAS messages between the UE 171 and SMF 177.
  • the AMF 176 also performs SMF selection function during communication session establishment procedure and UE mobility procedure.
  • the AMF may forward the QoS profile from the SMF to the RAN (or AN) , and forwards the QoS rule from the SMF to the UE.
  • the SMF 177 may perform the functionalities including but not limited to establishment, modification, and release of communication sessions, UE IP address allocation and management (including optional authorization functions) , selection and control of UPF 173, and downlink data notification.
  • Each SMF may control one or more UPFs and is associated with a service area being a collection of UPF service areas of all UPFs under its control.
  • the SMF derives the QoS profile according to the PCC rule, generates a QoS flow, sends the QoS profile to the RAN, and sends the packet detection rule (PDR) to the UPF.
  • the PCC rule is bound to the QoS flow.
  • the SMF also selects the UPF based on the granularity of the UE or session, and can assign IP addresses, collect charging data, connect to the charging center, and so on.
  • the PCF 179 is responsible for a unified policy framework, provides policy rules for control plane functions, determines policy control and charging (PCC) rules, and authorizes a session management function (SMF) on service data flow (SDF) basis.
  • the PCF performs the functionalities including but not limited providing policy rules and controlling other network nodes to enforce the policy rules.
  • the PCF provides access and mobility related policies to the AMF 176 so that the AMF enforces them during mobility procedure.
  • a core network may include various types of control plane (CP) nodes or entities, e.g. 5G AMF/SMF, and user plane (UP) node or entity, e.g. 5G UPF.
  • CP control plane
  • UP user plane
  • the RAN node e.g. 5G aggregated gNB consists of CP part and UP part together, and then terminates on UE via radio link (RL) in the air including signaling radio bearer (SRB) and/or data radio bearer (DRB) .
  • SRB signaling radio bearer
  • DRB data radio bearer
  • the RAN node e.g. 5G dis-aggregated gNB including centralized unit control plan (CU-CP) node, CU-UP node and distributed unit (DU) node or entities, and then terminates on UE via RL in the air.
  • the CP part or node is responsible for generating, processing and transferring control signaling, e.g. for (re) configuring and monitoring nodes;
  • the UP part or node is responsible for processing and transferring user UP data, e.g. normally associated with mobile APP and Web services etc. outside. For both CP and UP plane, they have their own interface and/or protocol stack and normally span from CN domain to RAN network and then to UE.
  • the present disclosure describes various embodiments for transferring data service control data in a wireless communication system, addressing at least one of the issues/problems discussed in the present disclosure, thus increasing efficiency of various data services, enabling future wireless communication system to support or handle the forward/transfer of data service data (e.g. content of data service) , and/or adapting to various demands of new generation wireless services in wireless communication systems.
  • data service data e.g. content of data service
  • FIG. 2 shows an example of electronic device 200 to implement one or more core network functions, one or more network nodes, or one or more base stations.
  • the example electronic device 200 may include radio transmitting/receiving (Tx/Rx) circuitry 208 to transmit/receive communication with UEs and/or other base stations.
  • the electronic device 200 may also include network interface circuitry 209 to communicate the base station with other base stations and/or a core network, e.g., optical or wireline interconnects, Ethernet, and/or other data transmission mediums/protocols.
  • the electronic device 200 may optionally include an input/output (I/O) interface 206 to communicate with an operator or the like.
  • I/O input/output
  • the electronic device 200 may also include system circuitry 204.
  • System circuitry 204 may include processor (s) 221 and/or memory 222.
  • Memory 222 may include an operating system 224, instructions 226, and parameters 228.
  • Instructions 226 may be configured for the one or more of the processors 124 to perform the functions of the network node.
  • the parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.
  • FIG. 3 shows an example of an electronic device to implement a terminal device 300 (for example, user equipment (UE) ) .
  • the UE 300 may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle.
  • the UE 300 may include communication interfaces 302, a system circuitry 304, an input/output interfaces (I/O) 306, a display circuitry 308, and a storage 309.
  • the display circuitry may include a user interface 310.
  • the system circuitry 304 may include any combination of hardware, software, firmware, or other logic/circuitry.
  • the system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry.
  • SoC systems on a chip
  • ASIC application specific integrated circuits
  • the system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300.
  • the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310.
  • the user interface 310 and the inputs/output (I/O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements.
  • I/O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input /output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.
  • USB Universal Serial Bus
  • the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314.
  • the communication interface 302 may include one or more transceivers.
  • the transceivers may be wireless transceivers that include modulation /demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium.
  • the transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings.
  • the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G /Long Term Evolution (LTE) , 5G standards, and/or 6G or any future standards.
  • UMTS Universal Mobile Telecommunications System
  • HSPA High Speed Packet Access
  • LTE Long Term Evolution
  • FIG. 4 shows a conventional mechanism for PDU session management in a wireless communication system (e.g., 5G) .
  • the AMF entity 430 in 5GC is the anchor controlling point of PDU session for particular served UE 410.
  • the AMF triggers the control signaling procedures for establishing or modifying the PDU session across different NW nodes (including the SMF 440) .
  • NW nodes including the SMF 440
  • the outside UP data associated to served the UE may be transferred via the “tunnels or DRBs” across different NW nodes.
  • the UP resources e.g. “tunnels or DRBs” may be reconfigured on demand.
  • a legacy communication control plan (CP) connection may be mainly responsible for transferring the communication service control data across different NW nodes.
  • CP communication control plan
  • FIG. 5 shows a new mechanism for data service session management in future wireless communication system.
  • network node NF in CN, RAN, or UE
  • it may play the role of source node/requesting node, intermediate/relay node or target node/response node for particular data service session, and the network node may include two basic new logic functions: “DA-C”and “DA-E” .
  • the “DA-C” entity is responsible for configuring, coordinating, and/or monitoring the data service session across different NW nodes; and the “DA-E” entity is responsible for processing and/or forwarding the data of data service session, i.e.
  • a network node may include both DA-C and DA-E entities together, and, in this case, the DA-C entity of the node is responsible for the DA-E of the same node.
  • different network nodes may include the DA-C and DA-E (i.e., one network node may include only DA-C or DA-E entity alone) , and, in this case, there is cross-node control and collaboration between DA-C and DA-E in different NW nodes.
  • “DA-C” entities in each involved NW node may firstly establish the E2E virtual control plane of data service session 652, then “DA-E” entities in each involved NW node may establish the E2E virtual execution plane of data service session 656.
  • the data service control data (e.g., for guiding and configuring the associated DA-E processing and/or forwarding resources) is handled and transferred in the virtual control plane of data service session.
  • the transferring of data service control data may be independent or coupled/associated with the control plane (CP) signaling procedure (s) of communication service (e.g., E2E communication control plan 672 managed by Comm-C entities in each NW node) .
  • the transferring of data service data may be independent or coupled/associated with the user plane (UP) signaling procedure (s) of communication service (e.g., E2E communication user plan 676 managed by Comm-U entities in each NW node) .
  • CP control plane
  • UP user plane
  • each network node e.g., a source node 620, an intermediate/relay node 630, and/or a target node 610 or entity may include a portion or all of the following logic functional entities: “DA Control” and “DA Execution” entities.
  • the “DA Control” entity is responsible for controlling, configuring, coordinating, and/or monitoring the data service session across different NW nodes or entities.
  • the “DA Execution” entity is responsible for various data processing and/or transferring of data service session, i.e. handling the data service data.
  • the interface protocol stack between “DA Control” entities is coupled/shared/associated with the interface protocol stack between “COMM-C” entities; the interface protocol stack between “DA Execution” entities is coupled/shared/associated with the interface protocol stack between “COMM-E” entities; and/or the interface protocol stack between “DA Control” entity and “DA Execution” entity is coupled/shared/associated with the interface protocol stack between “COMM-C” and “COMM-E” entities.
  • DA Control entities in each involved NW node or entities shall firstly establish the virtual “E2E control plane of data service session” (in dotted line in FIG. 6) , then “DA Execution” entities in each involved NW node or entities shall establish the virtual “E2E execution plane of data service session” (in dotted line in FIG. 6) .
  • the “control plane of data service session” generates and transfers the control data for data service session via CP signaling procedures with communication service across multiple NW nodes or entities.
  • execution plane of data service session processes and transfers the data service data across multiple NW nodes or entities.
  • the “DA control” in the source node determines the “data service session path” on demand, i.e. which are the intermediate/relay nodes and target nodes or entities.
  • the “DA control” in each involved NW node or entities determines the DA-E processing resources (such as CPU, GPU, DPU, NPU, TPU, DSP, Storage, Buffer etc. ) inside their associated “DA Execution” entities.
  • the “DA Control” in each involved NW node or entities determines the DA-E transferring resources (such as data transfer tunnels, radio bearers etc. ) between their associated “DA Execution” entities.
  • the data service session’s control plane data transfer is coupled/shared/associated with the CP signaling procedure with communication service, e.g. in the form of “IE container”
  • the data service session’s execution plane data transfer is carried via data service session tunnel (s) and data service session RB (s) , which are (re) -configured by control plane data of data service session from DA-C entity.
  • the execution plane data of data service session may be transferred by dedicated new data service session tunnel (s) and RB (s) with data service, i.e. different from those tunnels or DRBs with communication service.
  • the execution plane data of data service session may also be transferred by legacy UP tunnel (s) and DRB(s) with communication service.
  • a communication service refers to a UE and/or a mobile user APP layer data transfer service provided by wireless communication system, i.e. the communication service data is normally generated outside the wireless system;
  • a COMM-C refers to a control part of a NW node for controlling the Communication PDU Session, such as gNB-CU-CP, SMF etc.
  • a COMM-E or COMM-U refers to an execution part of a NW node for executing the Communication PDU Session (i.e., transferring UP data) , such as gNB-CU-UP, UPF etc.;
  • a data service refers to new type of services beyond legacy communication service provided by wireless system, e.g.
  • sensing, computing, Intelligence, storage, and/or security new services and their corresponding data service data is generated inside the wireless system, e.g. by UE AS layer, RAN node and NF in CN; a data agent (DA) : new logical node or functional entity supporting data services and data service session inside wireless system; a DA Control (DA-C) refers to a control part of DA for controlling/coordinating the data service session; a DA Execution (DA-E) refers to an execution part of DA for executing/processing the data service session; a DA-E processing resources refers to executing resources (such as CPU, GPU, DPU, NPU, TPU, DSP, Storage etc.
  • a DA-E transferring resources refers to executing resources (such as data transfer tunnels, radio bearers etc. ) for transferring data service data between DA Execution entities
  • a data service session refers to a data session for data service between the source node and target node, and it may also span multiple intermediate/relay nodes
  • a data service data refers to the data associated to particular data service session, i.e. different from communication service data and comparable to UP data of communication service
  • data service control data refers to the controlling data for particular data service session, i.e.
  • data service session radio bearer refers to the radio bearer carrying and/or transferring data service (control) data over an air interface
  • data service session tunnel refers to the data tunnel carrying and/or transferring data service data over a wirelined interface
  • a data service anchor node refers to the central controlling/coordinating node or entity for controlling the data service session, such as AMF, NWDAF, gNB, xNB, or etc. depending on data service usage scenario.
  • FIG. 7 shows various exemplary methods and architectures for handling and transferring data service control data in various embodiments, which may include a portion or all of the following: a core network (CN) 710, a radio access network (RAN, e.g., xNB) 720, and/or a user equipment (UE) 730.
  • CN core network
  • RAN radio access network
  • UE user equipment
  • the data service control data may be handled and/or transferred along at least one of the following paths, a first path 751 with signaling terminated at the CN with AMF and SMF involved, a second path 752 with signaling terminated at the CN with the AMF involved, a third path 753 with signaling terminated at the CN, a fourth path 754 with signaling terminated at the RAN with a RRC involved, and/or a fifth path 755 with signaling terminated at the RAN.
  • each involved NW node e.g. source node, intermediate/relay node or target node
  • entity may include at least one logic functional entities: DA-C and/or DA-E.
  • one NW node may include only the DA-C alone, and the DA-C’s associated DA-E may be in another NW node.
  • the DA-C may generate the data service configurations.
  • the DA-C entity is responsible for generating and/or forwarding the data service control data (such as data service policy guidance, action orders, detailed configuration parameters, and/or etc. ) across different NW nodes or entities.
  • the CN be a 6G CN, which may include a portion or all of the following, a 6G AMF 712, a 6G SMF 714, and/or a 6G DA-C entity 716.
  • the DA-C entity may be responsible for the data service control data originated or terminated at the CN.
  • the RAN may be a 6G RAN (e.g., 6G xNB) , which may include a portion or all of the following: a 6G RRC entity 722, a 6G DA-C entity 724, and/or a 6G L2/L1 entity 726, wherein the DA-C entity may be responsible for the data service control data originated or terminated at the RAN.
  • 6G xNB 6G RAN
  • the UE may be a 6G UE, which may include a portion or all of the following: a 6G non-access stratum (NAS) entity/layer 732, a 6G DA-C entity 734, a 6G RRS entity 735, a 6G DA-C entity 736, and/or a 6G L2/L1 entity 739, wherein the 6G DA-C entity 734 and/or 736, which may be access stratum (AS) layer DA-C entities, may be responsible for the data service control data originated or terminated at the UE.
  • the 6G DA-C entity 734 is the same as the 6G DA-C entity 736, and thus, the UE 730 may effectively include a single DA-C entity.
  • the present disclosure includes various exemplary schemes and/or architectures for handling and transferring data service control data as below.
  • the DA-C entity in the CN may be part of or connect to 6G SMF or 6G AMF or 6G RAN directly.
  • Scheme 1-1 when the DA-C entity connects to the 6G SMF, the data service control data in 6G CN may be processed and forwarded via 6G SMF (then further from/to 6G AMF) , i.e. coupling/associating with SMF relevant procedures of communication service.
  • Scheme 1-2 when the DA-C entity connects to the 6G AMF, the data service control data in 6G CN may be processed and forwarded via the 6G AMF, i.e. coupling/associating with AMF relevant procedures of communication service.
  • Scheme 1-3 when the DA-C entity connects to 6G RAN directly, the data service control data in 6G CN may be processed and forwarded via the 6G RAN directly, i.e. independent from any 6G CN procedures.
  • the interface between the 6G DA-C entity and the RAN may be newly defined, and adopting independent protocol stack and new signaling connection.
  • the DA-C entity in the RAN may be part of or connect to the 6G RRC entity or 6G L2/L1 entity directly.
  • Scheme 2-1 when the DA-C entity connects to the 6G RRC entity, the data service control data in the 6G RAN may be processed and forwarded via 6G RRC, i.e. coupling/associating with RRC relevant procedures of communication service.
  • Scheme 2-2 when the DA-C entity connects to the 6G L2/L1 entity directly, the data service control data in the 6G RAN may be processed and forwarded via 6G L2/L1 directly, i.e. independent from any RRC relevant procedures.
  • the interface between 6G DA-C entity and L2/L1 entity can be newly defined, and adopting independent protocol stack and new signaling connection.
  • the data service control data of the 6G CN or the 6G RAN may be transferred via either legacy communication service SRB (s) or new data service session Radio Bearer (s) over the air interface between the 6G RAN and the UE.
  • legacy communication service SRB s
  • new data service session Radio Bearer s
  • Scheme 3 from the 6G UE NAS layer perspective: the DA-C entity may be part of or connect to 6G NAS entity or 6G RRC entity directly.
  • Scheme 3-1 when the DA-C entity connects to 6G NAS entity, the data service control data in NAS layer may be processed and forwarded via the 6G NAS, i.e. coupling/associating with NAS relevant procedures of communication service.
  • Scheme 3-2 when the DA-C entity connects to the 6G RRC entity directly, the data service control data in NAS layer may be processed and forwarded via 6G RRC, i.e. independent from any NAS relevant procedures.
  • the SAP between 6G DA-C entity and RRC entity can be newly defined, and adopting independent protocol stack and new signaling connection.
  • Scheme 4 from the 6G UE AS layer perspective: the DA-C entity may be part of or connect to 6G RRC entity or 6G L2/L1 entity directly.
  • Scheme 4-1 when the DA-C entity connects to the 6G RRC entity, the data service control data in AS layer may be processed and forwarded via 6G RRC , i.e. coupling/associating with RRC relevant procedures of communication service.
  • Scheme 4-2 when the DA-C entity connects to the 6G L2/L1 entity directly, the data service control data in AS layer may be processed and forwarded via 6G L2/L1 entity, i.e. independent from any RRC relevant procedures.
  • the SAP between 6G DA-C entity and L2/L1 entity can be newly defined, and adopting independent protocol stack and new signaling connection.
  • the present disclosure describes various embodiments for transferring data service control data in a wireless communication system, which may be implemented, partly or totally, by the core network function, network base station, and/or the user equipment described above in FIGS. 2 to 3.
  • the various embodiments in the present disclosure may increase efficiency of various data services, enable future wireless communication system to support or handle the forward/transfer of data service data, and/or adapt to various demands of new generation wireless services.
  • a new mechanism and/or architecture for transferring data service control data which may be applicable to any type of network node or entity (e.g. NF in 6G CN, RAN node or UE) for particular data service session management (e.g. establishment, modification and release etc. ) , and each involved network node or entity includes two basic new logic functions: “DA Control” (DA-C) and “DA Execution” (DA-E) .
  • D-C DA Control
  • D-E DA Execution
  • the DA-C may be a new logic network entity, and is responsible for configuring, controlling, coordinating, and/or monitoring the data service session across different NW nodes or entities.
  • DA-C entity normally generates the data service control data for its associated one or multiple DA-E, which is an executing part of DA and located either in the same NW node or other NW node.
  • the DA-E entities may then take the corresponding data handling actions upon receiving the data service control data from its associated DA-C.
  • the data service control data may include a portion or all of the following: data service policy guidance, action orders, detailed configuration parameters, and/or etc.
  • the COMM-C (e.g. AMF/SMF/RRC) is the control part for controlling/coordinating the PDU Session of communication service, and furthermore, it may send the data service control data generated by DA-C, e.g. in the form of “IE container” .
  • Various following embodiments may be based on the assumption that the DA-C and the COMM-C (e.g. AMF/SMF/RRC) are not deployed together.
  • a DA-C entity may be located either in the same NW node or different NW node from the COMM-C (e.g. AMF/SMF/RRC) .
  • the present disclosure describes various embodiments of a method 800 for transferring data service control data for data service via wireless communication.
  • the method 800 may include a portion or all of the following: step 810, sending, by a first data agent’s control part (DA-C) entity within a first network node, first data service control data to a second network node, so that the second network node communicates with a second DA-C entity within a third network node for performing data service based on the first data service control data generated by the first DA-C, wherein the second DA-C entity generates second data service control data indicating a target data agent’s execution part (DA-E) entity associated with the second DA-C entity; and/or step 820, receiving, by the first DA-C entity from the second network node, the second data service control data for establishing a data service session channel between the first network node and the third network node, wherein the data service session channel is via a communication service session channel between the first network node and
  • D-C
  • the present disclosure describes various embodiments of a method 850 for transferring data service control data for data service via wireless communication.
  • the method 850 may include a portion or all of the following steps: step 860, receiving, from a first data agent’s control part (DA-C) entity within a first network node by a second network node, first data service control data; step 870, communicating, by the second network node, with a second DA-C entity within a third network node for performing data service based on the first data service control data generated by the first DA-C, wherein the second DA-C entity generates second data service control data indicating a target data agent’s execution part (DA-E) entity associated with the second DA-C entity; and/or step 880, sending, by the second network node to the first DA-C entity, the second data service control data for establishing a data service session channel between the first network node and the third network node, wherein the data service session channel is via a communication service session channel
  • D-C
  • the first network node is any one of a user equipment (UE) , a radio access network (RAN) node, or a core network (CN) node or function entity;
  • the second network node is any one of a UE, a RAN node, a CN node or function entity;
  • the third network node is any one of a UE, a RAN node, a CN node or function entity.
  • the first network node is a UE; the second network node is a RAN node; and/or the third network node is a CN node or function entity.
  • the step that the first DA-C entity within the first network node sends the first data service control data to the second network node comprises: the first DA-C entity within the UE sends the first data service control data to a non-access stratum (NAS) entity within the UE; the NAS entity within the UE sends the first data service control data to a radio resource control (RRC) entity within the UE; and/or the RRC entity within the UE sends the first data service control data to the RAN over signaling radio bearer (SRB) in an air interface.
  • NAS non-access stratum
  • RRC radio resource control
  • the step that the second network node communicates with the second DA-C entity within the third network node for performing the data service comprises: the RAN node sends the first data service control data to an access mobility function (AMF) in the CN over a N2 reference interface for communication service; the AMF in the CN sends the first data service control data to a session management function (SMF) in the CN; the SMF in the CN determines the second DA-C entity to perform the data service; the SMF in the CN sends the first data service control data to the second DA-C entity within the CN; the second DA-C entity generates the second data service control data; the second DA-C entity sends the second data service control data to the SMF; the SMF sends the second data service control data to the AMF; and/or the AMF sends the second data service control data to
  • the step that the second network node communicates with the second DA-C entity within the third network node for performing data service comprises: the RAN node sends the first data service control data to an AMF in the CN over a N2 reference interface for communication service; the AMF in the CN determines the second DA-C entity to perform the data service; the AMF in the CN sends the first data service control data to the second DA-C entity within the CN; the second DA-C entity generates the second data service control data; the second DA-C entity sends the second data service control data to the AMF; and/or the AMF sends the second data service control data to the RAN node over a N2 reference interface for communication service.
  • the step that the second network node sends the second data service control data to the first DA-C entity comprises: the RAN node sends the second data service control data to a RRC entity in the UE over the SRB in the air interface; the RRC entity sends the second data service control data to a NAS entity in the UE; and/or the NAS entity sends the second data service control data to the first DA-C entity within the UE.
  • the step that the first DA-C entity within the first network node sends the first data service control data to the second network node comprises: the first DA-C entity within the UE sends the first data service control data to a RRC entity within the UE; and/or the RRC entity within the UE sends the first data service control data to the RAN node over SRB in an air interface.
  • the step that the second network node communicates with the second DA-C entity within the third network node for performing the data service comprises: the RAN node determines the second DA-C entity within the CN to perform the data service; the RAN node sends the first data service control data to the second DA-C entity over a new network interface for data service; the second DA-C entity generates the second data service control data; and/or the second DA-C entity sends the second data service control data to the RAN node over a new network interface for data service.
  • the step that the second network node sends the second data service control data to the first DA-C entity comprises: the RAN node sends the second data service control data to a RRC entity in the UE over the SRB in the air interface; and/or the RRC entity sends the second data service control data to the first DA-C entity within the UE.
  • the first network node is a UE; the second network node is a RAN node; and/or the third network node is same as the second network node.
  • the step that the first DA-C entity within the first network node sends the first data service control data to the second network node comprises: the first DA-C entity within the UE sends the first data service control data to a RRC entity within the UE; and/or the RRC entity within the UE sends the first data service control data to the RAN node over SRB in the air interface.
  • the step that the second network node communicates with the second DA-C entity within the third network node performing the data service comprises: the RAN node determines the second DA-C entity to perform the data service; a RRC in the RAN node sends the first data service control data to the second DA-C entity within the RAN node; the second DA-C entity generates the second data service control data; and/or the second DA-C entity sends the second data service control data to a RRC entity in the RAN node.
  • the step that the second network node sends the second data service control data to the first DA-C entity comprises: the RAN node sends the second data service control data to a RRC entity in the UE over the SRB in the air interface; and/or the RRC entity in the UE sends the second data service control data to the first DA-C entity within the UE.
  • the step first DA-C entity within the UE determines the second DA-C entity to perform the data service; the first DA-C entity within the UE sends the first data service control data to the second DA-C entity within the RAN node; the second DA-C entity generates the second data service control data; and/or the second DA-C entity sends the second data service control data to the first DA-C entity within the UE in an air interface.
  • the present disclosure describes various exemplary embodiments for transferring data service control data in a wireless communication system, and the exemplary embodiments merely serve as examples and do not pose limitations. Any steps and/or operations in one same embodiment/implementation or more than one different embodiments/implementation in the present disclosure may be combined or arranged in any amount or order, as desired. Two or more of the steps and/or operations may be performed in parallel. Embodiments and implementations in the disclosure may be used separately or combined in any order. Further, each of the methods (or embodiments) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits) .
  • processing circuitry e.g., one or more processors or one or more integrated circuits
  • AI-related data service requested/triggered by a UE (i.e., a DA-C in the UE) as non-limiting example.
  • a UE i.e., a DA-C in the UE
  • Other embodiments with other data service or other network nodes (RAN or CN or CN functional entity) requesting data service may be similarly applicable as well.
  • the present disclosure describes various embodiments for a UE triggered AI model data with Scheme 1-1 and Scheme 3-1, wherein the 6G CN DA-C entity may be part of or connect to 6G SMF directly and the 6G UE local DA-C entity may be part of or connect to 6G UE NAS directly.
  • the various embodiments may be applicable in the below exemplary usage scenario.
  • the data service requesting node is a user equipment (UE) which lacks of computing and storage resources.
  • the UE reported the AI training data to 6G CN DA-E entity ahead, and the 6G CN DA-E collected the data for AI model training so then obtained the well-trained AI model later on.
  • the source UE requests the AI model data from the target 6G CN DA-E entity, it may send the data service request to the associated COMM-C entity via the data service anchor node, e.g. SMF.
  • anchor SMF sends the request to DA-C to establish the control plane connection of data service between CN and UE.
  • FIG. 9 shows an exemplary process of various embodiments, which includes a portion or all of the following: a 6G UE local DA-C 991, a UE NAS 992, a 6G UE RRC 993, a 6G RAN 994, a 6G AMF 995, a 6G SMF 996, and/or a 6G CN DA-C 997.
  • the exemplary process may include a portion or all of the following steps.
  • the UE local DA-C entity For step 910, the UE local DA-C entity generates the data service session configuration request message according to its own AI requirement, and sends it to UE local NAS entity and then further sends it to UE local RRC entity. Then, the UE RRC entity sends it to the RAN serving node, e.g., xNB, for acquiring the desired AI model data in the target DA.
  • the data service session configuration request includes the data service control data, which is generated by the UE local DA-C.
  • the RAN serving node forwards the data service session configuration request to the target AMF.
  • the target AMF makes the selection of target SMF, and then forwards the data service session configuration request to the target SMF.
  • the anchor SMF makes the target DA-C entity selection, and then forwards the data service session configuration request to the target DA-C entity.
  • the target DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the source UE) , and consequently generates the data service session configuration response message containing data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (in step 950) in the data service session configuration response message may be different from the data service control data (in steps 910, 920, 930, and/or 940) in the data service session configuration request message.
  • the DA-C sends the data service session configuration response to the anchor SMF, and then the SMF further sends it to the AMF, then the AMF sends it to the RAN serving node via N2AP reference signaling.
  • the RAN serving node receives the data service session configuration response message, then generates corresponding data service session configuration response message containing the data service control data, e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface, and then UE RRC entity forwards the data service session configuration response to UE local NAS entity and then further forwards it to UE local DA-C entity.
  • the data service control data e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface
  • UE RRC entity forwards the data service session configuration response to UE local NAS entity and then further forwards it to UE local DA-C entity.
  • the process may further include that, as the control plane connection of data service between CN and UE are established, the 6G CN DA-E and 6G UE are ready to transfer the AI model data that the UE needs.
  • the present disclosure describes various embodiments for a UE triggered AI model data with Scheme 1-2 and Scheme 3-1, wherein the 6G CN DA-C entity may connect to 6G AMF and the 6G UE local DA-C entity may be part of or connect to 6G UE NAS directly.
  • the various embodiments may be applicable in the below exemplary usage scenario.
  • the data service requesting Node is a UE which lacks of computing and storage resources.
  • the UE reported the AI training data to 6G CN DA-E entity ahead, and the 6G CN DA-E collected the data for AI model training so then obtained the well-trained AI model later on.
  • the source UE requests the AI model data from the target 6G CN DA-E entity, it may send the data service request to the associated COMM-C entity via the data service anchor node, e.g. AMF. then anchor AMF sends the request to DA-C to establish the control plane connection of data service between CN and UE.
  • the data service anchor node e.g. AMF
  • FIG. 10 shows an exemplary process of various embodiments, which includes a portion or all of the following: a 6G UE local DA-C 1091, a UE NAS 1092, a 6G UE RRC 1093, a 6G RAN 1094, a 6G AMF 1095, and/or a 6G CN DA-C 1097.
  • the exemplary process may include a portion or all of the following steps.
  • the UE local DA-C entity For step 1010, the UE local DA-C entity generates the data service session configuration request message according to its own AI requirement, and sends it to UE local NAS entity and then further sends it to UE local RRC entity. Then, UE RRC entity sends it to the RAN serving node, e.g., xNB for acquiring the desired AI model data in the target DA.
  • the data service session configuration request includes the data service control data, which is generated by the UE local DA-C.
  • the RAN serving node forwards the data service session configuration request to anchor AMF.
  • the anchor AMF makes the selection of target DA-C entity, and then forwards the data service session configuration request to the target DA-C entity.
  • the target DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the source UE) , and consequently generates the data service session configuration response message containing the data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (generated by the target DA-C entity in step 1040) in the data service session configuration response message may be different from the data service control data (in steps 1010, 1020, and/or 1030) in the data service session configuration request message.
  • the DA-C sends the data service session configuration response to the anchor AMF, then the AMF sends it to the anchor RAN via N2AP reference signaling.
  • the RAN serving node receives the data service session configuration response message, then generates corresponding data service session configuration response message containing the data service control data, e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface, and then UE RRC entity forwards the data service session configuration response to UE local NAS entity and then further forwards it to UE local DA-C entity.
  • the data service control data e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface
  • UE RRC entity forwards the data service session configuration response to UE local NAS entity and then further forwards it to UE local DA-C entity.
  • the process may further include that, as the control plane connection of data service between CN and UE are established, the 6G CN DA-E and 6G UE are ready to transfer the AI model data that the UE needs.
  • the present disclosure describes various embodiments for a UE triggered AI model data with Scheme 1-3 and Scheme 3-2, wherein the 6G CN DA-C entity may connect to the 6G RAN directly via new signaling connection and the 6G UE local DA-C entity may connect to the 6G UE RRC entity directly.
  • the various embodiments may be applicable in the below exemplary usage scenario.
  • the data service requesting Node is a UE which lacks of computing and storage resources.
  • the UE reported the AI training data to 6G CN DA-E entity ahead, and the 6G CN DA-E collected the data for AI model training so then obtained the well-trained AI model later on.
  • the source UE requests the AI model data from the target 6G CN DA-E entity, then it may send the data service request to the associated COMM-C entity via the data service anchor node, e.g. RAN.
  • the anchor RAN sends the request to 6G CN DA-C to establish the control plane connection of data service between CN and UE.
  • FIG. 11 shows an exemplary process of various embodiments, which includes a portion or all of the following: a 6G UE local DA-C 1191, a 6G UE RRC 1193, a 6G RAN 1194, and/or a 6G CN DA-C 1197.
  • the exemplary process may include a portion or all of the following steps.
  • the UE local DA-C entity For step 1110, the UE local DA-C entity generates the data service session configuration request message according to its own AI requirement, and sends it to UE local RRC entity and then UE RRC entity sends it to the anchor RAN for acquiring the desired AI model data in the target DA.
  • the data service session configuration request includes the data service control data, which is generated by the UE local DA-C.
  • the anchor RAN makes the selection of target DA-C entity, and then forwards the data service session configuration request to the target DA-C entity via new signaling connection.
  • the target DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the source UE) , and consequently generates the data service session configuration response message containing the data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (generated by the target DA-C entity in step 1130) in the data service session configuration response message may be different from the data service control data (in steps 1110 and/or 1120) in the data service session configuration request message.
  • the DA-C sends the data service session configuration response to the anchor RAN via new signaling connection.
  • the anchor RAN receives the data service session configuration response message, then generates corresponding data service session configuration response message containing the data service control data, e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface, and then UE RRC entity forwards the data service session configuration response to UE local DA-C entity.
  • the data service control data e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface
  • UE RRC entity forwards the data service session configuration response to UE local DA-C entity.
  • the process may further include that, as the control plane connection of data service between CN and UE are established, the 6G CN DA-E and 6G UE are ready to transfer the AI model data that the UE needs.
  • the present disclosure describes various embodiments for a UE triggered AI model data with Scheme 2-1 and Scheme 4-1, wherein the 6G RAN DA-C entity may be part of or connect to 6G RAN RRC entity directly via new signaling connection and the 6G UE local DA-C entity may be part of or connect to 6G UE RRC entity directly.
  • the various embodiments may be applicable in the below exemplary usage scenario.
  • the data service requesting node is a UE which lacks of computing and storage resources.
  • the UE reported the AI training data to 6G RAN DA-E entity ahead, and the 6G RAN DA-E collected the data for AI model training so then obtained the well-trained AI model later on.
  • the source UE requests the AI model data from the target 6G RAN DA-E entity, then it will send the data service request to the associated COMM-C entity via the data service anchor node, e.g. 6G RAN RRC entity.
  • FIG. 12 shows an exemplary process of various embodiments, which includes a portion or all of the following: a 6G UE local DA-C 1291, a 6G UE RRC 1293, a 6G RAN RRC 1294, and/or a 6G RAN DA-C 1297.
  • the exemplary process may include a portion or all of the following steps.
  • the UE local DA-C entity For step 1210, the UE local DA-C entity generates the data service session configuration request message according to its own AI requirement, and sends it to UE local RRC entity and then UE RRC entity sends it to the data service anchor node (e.g. 6G RAN RRC entity) for acquiring the desired AI model data in the target DA.
  • the data service session configuration request includes the data service control data, which is generated by the UE local DA-C.
  • the anchor RRC entity makes the selection of target 6G RAN DA-C entity, and then forwards the data service session configuration request to the target DA-C entity via new signaling connection.
  • the DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the source UE) , and consequently generates the data service session configuration response message containing the data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (generated by the target DA-C entity in step 1230) in the data service session configuration response message may be different from the data service control data (in steps 1210 and/or 1220) in the data service session configuration request message.
  • the DA-C sends the data service session configuration response to the anchor RRC entity via new signaling connection.
  • the anchor RRC entity receives the data service session configuration response message, then generates corresponding data service session configuration response message containing the data service control data, e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface, and then UE RRC entity forwards the data service session configuration response to UE local DA-C entity.
  • the data service control data e.g. configuration signaling of UE DA-E transferring resource to UE RRC entity via SRB in the air interface
  • UE RRC entity forwards the data service session configuration response to UE local DA-C entity.
  • the process may further include that, as the control plane connection of data service between RAN and UE are established, the 6G RAN DA-E and 6G UE are ready to transfer the AI model data that the UE needs.
  • the present disclosure describes various embodiments for a UE triggered AI model data with Scheme 2-2 and Scheme 4-2, wherein the 6G RAN DA-C entity may be part of or connect to RAN L2/L1 entity directly via new signaling connection and the 6G UE local DA-C entity may be part of or connect to 6G UE L2/L1 entity directly.
  • the various embodiments may be applicable in the below exemplary usage scenario.
  • the data service requesting node is a UE which lacks of computing and storage resources.
  • the UE reported the AI training data to 6G RAN DA-E entity ahead, and the 6G RAN DA-E collected the data for AI model training so then obtained the well-trained AI model later on.
  • the source UE requests the AI model data from the target 6G RAN DA-E entity, then it will send the data service request to the 6G RAN DA-C entity directly.
  • FIG. 13 shows an exemplary process of various embodiments, which includes a portion or all of the following: a 6G UE local DA-C 1391 and/or a 6G RAN DA-C 1397.
  • the exemplary process may include a portion or all of the following steps.
  • the UE local DA-C entity For step 1310, the UE local DA-C entity generates the data service session configuration request message according to its own AI requirement, and sends it to 6G RAN DA-C entity directly via new signaling connection (e.g. new type of SRB, legacy SRB (s) , or DRB (control PDU or MAC CE) ) for acquiring the desired AI model data in the target DA.
  • the data service session configuration request includes the data service control data, which is generated by the UE local DA-C.
  • the DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the source UE) , and consequently generates the data service session configuration response message containing the data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (generated by the 6G RAN DA-C entity in step 1320) in the data service session configuration response message may be different from the data service control data (in steps 1210) in the data service session configuration request message.
  • the DA-C sends the data service session configuration response message containing the data service control data, e.g. configuration signaling of UE DA-E transferring resource to UE local DA-C entity via new signaling connection (e.g. new type of SRB, legacy SRB (s) , or DRB (control PDU or MAC CE) ) in the air interface.
  • new signaling connection e.g. new type of SRB, legacy SRB (s) , or DRB (control PDU or MAC CE)
  • the process may further include that, as the control plane connection of data service between RAN and UE are established, the 6G RAN DA-E and 6G UE are ready to transfer the AI model data that the UE needs.
  • a CN node may be a requesting node to trigger a data service session (e.g., towards its downstream node, e.g., a RAN node and/or UE) .
  • a 6G CN DA-C may trigger a data service session by generating a data service session configuration request message according to its own AI requirement, and sending it to an anchor RAN node (via a SMF and an AMF as in FIG. 9, or via an AMF as in FIG. 10, or directly as in FIG. 11) .
  • the data service session configuration request includes the data service control data, which is generated by the CN DA-C.
  • the anchor RAN node makes the selection of target UE, and then forwards the data service session configuration request to the UE DA-C entity.
  • the UE DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the CN DA-C) , and consequently generates the data service session configuration response message containing the data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (generated by the UE local DA-C entity) in the data service session configuration response message may be different from the data service control data (generated by the 6G CN DA-C) in the data service session configuration request message.
  • the UE local DA-C sends the data service session configuration response to the anchor RAN node via SRB or new signaling connection.
  • the anchor RAN node receives the data service session configuration response message, then generates corresponding data service session configuration response message containing the data service control data, e.g. configuration signaling for transferring data service data, and then forwards the data service session configuration response to the CN DA-C entity.
  • the process may further include that, as the control plane connection of data service between CN and UE are established, the 6G CN DA-E and 6G UE are ready to transfer the AI model data.
  • a RAN node may be a requesting node to trigger a data service session (e.g., towards its downstream node, e.g., a target UE) .
  • a 6G RAN DA-C may trigger a data service session by generating a data service session configuration request message according to its own AI requirement.
  • the RAN DA-C sends the data service session configuration request message to a UE DA- C entity in the target UE (via a RAN RRC as in FIG. 12 or directly as in FIG. 13) .
  • the UE DA-C entity receives and parses the data service session configuration request message (so knowing the data service intention of the RAN DA-C) , and consequently generates the data service session configuration response message containing the data service control data, e.g. configuration signaling of DA-E transferring resource.
  • the data service control data (generated by the UE local DA-C entity) in the data service session configuration response message may be different from the data service control data (generated by the RAN DA-C) in the data service session configuration request message.
  • the UE local DA-C sends the data service session configuration response to the RAN DA-C via SRB or new signaling connection (via the RAN RRC as in FIG. 12 or directly as in FIG. 13) .
  • the process may further include that, as the control plane connection of data service between the RAN and the UE are established, the 6G RAN DA-E and 6G UE are ready to transfer the AI model data.
  • the present disclosure describes methods, apparatus, and computer-readable medium for wireless data service.
  • the present disclosure addressed the issues with transferring data service control data in a wireless communication system.
  • the methods, devices, and computer-readable medium described in the present disclosure may facilitate the performance of data service, thus improving efficiency and overall performance.
  • the methods, devices, and computer-readable medium described in the present disclosure may improves the overall efficiency of the wireless communication systems.
  • a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods.
  • the computer-readable medium may be referred as non-transitory computer-readable media (CRM) that stores data for extended periods such as a flash drive or compact disk (CD) , or for short periods in the presence of power such as a memory device or random access memory (RAM) .
  • CRM computer-readable media
  • computer-readable instructions may be included in a software, which is embodied in one or more tangible, non-transitory, computer-readable media.
  • Such non-transitory computer-readable media can be media associated with user-accessible mass storage as well as certain short-duration storage that are of non-transitory nature, such as internal mass storage or ROM.
  • the software implementing various embodiments of the present disclosure can be stored in such devices and executed by a processor (or processing circuitry) .
  • a computer-readable medium can include one or more memory devices or chips, according to particular needs.
  • the software can cause the processor (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM and modifying such data structures according to the processes defined by the software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne des procédés, un système et des dispositifs pour transférer des données de commande de service de données dans un système de communication sans fil. Un procédé consiste à envoyer, par une première entité de partie de commande (DA-C) d'agent de données dans un premier nœud de réseau, des premières données de commande de service de données à un deuxième nœud de réseau, de sorte que le deuxième nœud de réseau communique avec une seconde entité DA-C dans un troisième nœud de réseau pour effectuer un service de données, la seconde entité DA-C générant des secondes données de commande de service de données indiquant une entité de partie d'exécution (DA-E) d'agent de données cible associée à la seconde entité DA-C ; et recevoir, par la première entité DA-C en provenance du deuxième nœud de réseau, des secondes données de commande de service de données pour établir un canal de session de service de données entre le premier nœud de réseau et le troisième nœud de réseau.
PCT/CN2024/079434 2024-02-29 2024-02-29 Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil Pending WO2025179559A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/079434 WO2025179559A1 (fr) 2024-02-29 2024-02-29 Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/079434 WO2025179559A1 (fr) 2024-02-29 2024-02-29 Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil

Publications (1)

Publication Number Publication Date
WO2025179559A1 true WO2025179559A1 (fr) 2025-09-04

Family

ID=96919777

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/079434 Pending WO2025179559A1 (fr) 2024-02-29 2024-02-29 Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2025179559A1 (fr)

Similar Documents

Publication Publication Date Title
US12425936B2 (en) Methods and devices for enhancing mobility robustness to integrated access and backhaul for new radio
US12185194B2 (en) Methods and devices for selecting radio bearer mode for multicast broadcast services
US20230007544A1 (en) Methods and devices for updating data transmission during inter-donor migration
KR20240168348A (ko) 사용자 평면을 통해 서비스 품질 정보를 전송하는 방법 및 디바이스
WO2023141874A1 (fr) Procédés, dispositifs et systèmes pour effectuer un remplacement de tranche de réseau
WO2020200103A1 (fr) Procédé pour déterminer un type de support, et dispositif de communication
US20240276292A1 (en) Method, device, and system for congestion control in wireless networks
US20240349131A1 (en) Methods, devices, and systems for supporting l1/l2 based inter-cell mobility
US20240064703A1 (en) Methods, devices, and systems for small data transmission
WO2025179559A1 (fr) Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil
WO2025166575A1 (fr) Procédés et dispositifs de gestion de session de service de données dans un système sans fil
WO2025166596A1 (fr) Procédés et dispositifs de gestion de service de données dans un système de communication sans fil
WO2023141877A1 (fr) Procédés, dispositifs et systèmes pour effectuer un remplacement de tranche de réseau pendant une mobilité
US12396001B2 (en) Methods and devices for data transmission based on switching quality of service flow
WO2025147826A1 (fr) Procédés, dispositifs et systèmes de prise en charge d'une gestion basée sur un ensemble de pdu
WO2024217023A1 (fr) Procédé, dispositif, et système de gestion de consommation d'énergie dans des réseaux sans fil
WO2024113699A1 (fr) Procédés, dispositifs et systèmes de distribution d'informations de flux de qos
US20250098025A1 (en) Method, device, and system for data transmission in wireless networks
WO2025147828A1 (fr) Procédés, dispositifs et systèmes de prise en charge d'une gestion basée sur un ensemble de pdu dans une connectivité double
WO2021035600A1 (fr) Transmission de données précoce pour données de liaison descendante

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: 24926439

Country of ref document: EP

Kind code of ref document: A1