Method and apparatus for transmitting data service control data in a wireless communication system

Abstract

The present disclosure describes methods, systems, and devices for transmitting data service control data in a wireless communication system. One method includes sending, by a first data agent control (DA-C) entity within a first network node, first data service control data to a second network node such that the second network node communicates with a second DA-C entity within a third network node to perform a data service, wherein the second DA-C entity generates second data service control data that indicates a target data agent execution (DA-E) entity associated with the second DA-C entity; and receiving, by the first DA-C entity, the second data service control data from the second network node for establishing a data service session channel between the first network node and the third network node.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications. In particular, this disclosure relates to methods and apparatus for transmitting data service control data in a wireless communication system. Background Technology

[0002] Wireless technology is driving the world toward an increasingly interconnected and networked society. High-speed and low-latency wireless communication systems 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). Next-generation networks promise to provide a variety of data services with high speed, low latency, and high reliability, in addition to traditional communication services, to meet the needs of various scenarios.

[0003] In some wireless communication systems, various data services may include sensing services, computing services, artificial intelligence (AI) services, storage services, and / or security services. Several problems / challenges exist associated with these diverse data services. As a non-limiting example, how can control data for various data services be transmitted across different network nodes to execute these services?

[0004] This disclosure describes various embodiments for transmitting data service control data in a wireless communication system, solving at least one problem / challenge discussed in this disclosure, thereby improving the efficiency of various data services, enabling future wireless communication systems to support or process the forwarding / transmission of data service data (e.g., the content of the data service), and / or adapting to the various needs of next-generation wireless services in wireless communication systems. Summary of the Invention

[0005] This document relates to methods, systems, and apparatus for wireless data services via wireless communication, and more specifically, to methods, systems, and apparatus for transmitting data service control data in wireless communication systems. These methods, systems, and apparatus for transmitting data service control data in wireless communication systems facilitate the efficient use of wireless resources, improve the efficiency of telecommunications resource utilization, and / or enhance the performance of wireless data services via wireless communication.

[0006] In one embodiment, this disclosure describes a method for transmitting data service control data for a data service via wireless communication. The method includes: sending first data service control data from a first data proxy control portion (DA-C) entity within a first network node to a second network node, causing the second network node to communicate with a second DA-C entity within a third network node to perform a 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, the second data service control data instructing a target data proxy execution portion (DA-E) entity associated with the second DA-C entity; and receiving the second data service control data from the second network node by the first DA-C entity for establishing a data service session channel between the first and third network nodes, wherein the data service session channel is transmitted between the first network node and the target DA-E via a communication service session channel between the first and third network nodes; wherein: the first network node is a data service requesting node, the second network node is a data service anchor node or a data service responding node, and the third network node is a data service responding node.

[0007] In another embodiment, this disclosure describes another method for transmitting data service control data for a data service via wireless communication. The method includes: receiving first data service control data from a first data proxy control portion (DA-C) entity within a first network node by a second network node; communicating between the second network node and a second DA-C entity within a third network node to perform a 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, the second data service control data indicating a target data proxy execution portion (DA-E) entity associated with the second DA-C entity; and sending the second data service control data from the second network node to the first DA-C entity to establish a data service session channel between the first network node and the third network node, wherein the data service session channel is transmitted between the first network node and the target DA-E entity via a communication service session channel between the first network node and the third network node; wherein: the first network node is a data service request node, the second network node is a data service anchor node or a data service response node, and the third network node is a data service response node.

[0008] In some other embodiments, an apparatus for transmitting data service control data via a wireless communication data service may include: a memory storing instructions, and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the method described above.

[0009] In some other embodiments, an apparatus for transmitting data service control data via a wireless communication data service may include: a memory storing instructions, and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the method described above.

[0010] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above. The computer-readable medium may be a non-transitory computer-readable medium.

[0011] The foregoing and other aspects, as well as embodiments thereof, are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0012] Figure 1A An example of a wireless communication system is shown.

[0013] Figure 1B Schematic diagrams of various embodiments of the present disclosure are shown.

[0014] Figure 1C Another schematic diagram of various embodiments of the present disclosure is shown.

[0015] Figure 1D Another schematic diagram of various embodiments of the present disclosure is shown.

[0016] Figure 2 An example of a network node is shown.

[0017] Figure 3 An example of a user device is shown.

[0018] Figure 4 Schematic diagrams of various embodiments of the present disclosure are shown.

[0019] Figure 5 Another schematic diagram of various embodiments of the present disclosure is shown.

[0020] Figure 6 Another schematic diagram of various embodiments of the present disclosure is shown.

[0021] Figure 7 Another schematic diagram of various embodiments of the present disclosure is shown.

[0022] Figure 8AA flowchart is shown for a method of transmitting data service control data via wireless communication.

[0023] Figure 8B A flowchart is shown for another method for transmitting data service control data via wireless communication.

[0024] Figure 9 Another schematic diagram of various embodiments of the present disclosure is shown.

[0025] Figure 10 Another schematic diagram of various embodiments of the present disclosure is shown.

[0026] Figure 11 Another schematic diagram of various embodiments of the present disclosure is shown.

[0027] Figure 12 Another schematic diagram of various embodiments of the present disclosure is shown.

[0028] Figure 13 Another schematic diagram of various embodiments of the present disclosure is shown. Detailed Implementation

[0029] This disclosure will now be described in detail with reference to the accompanying drawings, which form a part of this disclosure and illustrate specific examples of embodiments by way of illustration. It should be noted that this disclosure may be embodied in many different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0030] Throughout the specification and claims, terminology may have subtle differences, as suggested or implied by the context, in addition to its expressly stated meaning. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, it is intended to indicate that the claimed subject matter includes a combination of all or part of the various exemplary embodiments or embodiments.

[0031] In general, terms can be understood at least in part based on their usage in the context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings, which depend at least in part on the context in which they are used. Typically, “or,” when used to relate a list, such as A, B, or C, is intended to indicate A, B, and C (in an inclusive sense) and A, B, or C (in an exclusive sense). Furthermore, the terms “one or more” or “at least one,” as used herein, depend at least in part on the context and can be used to describe any feature, structure, or characteristic in a singular sense, or a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “described” can also be understood to convey either a singular or a plural usage, depending at least in part on the context. Moreover, the terms “based on” or “determined by” can be understood not necessarily to convey a set of exclusive factors, but rather to allow for the presence of additional factors that are not necessarily explicitly described, again depending at least in part on the context.

[0032] This disclosure describes methods and apparatus for transmitting data service control data in a wireless communication system.

[0033] Wireless technology is driving the world toward an increasingly interconnected and networked society. High-speed and low-latency wireless communication systems 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). Next-generation networks promise to provide a variety of data services with high speed, low latency, and high reliability, in addition to traditional communication services, to meet the needs of various scenarios.

[0034] With the latest developments in wireless communication systems and various distributed sensing, computing, intelligence, storage, and / or security systems, these systems should technically be integrated and / or coordinated in terms of system architecture / capabilities and network and / or air interface resource utilization. In some implementations, it is expected that advanced fifth-generation (5G-A) and sixth-generation (6G) wireless communication systems will integrate and / or coordinate various new functions / services such as sensing, computing, artificial intelligence (AI), storage, and / or security with their own traditional communication functions / services. It is expected that the core network (CN) and / or radio access network (RAN) nodes of 5G-A and 6G will be able to simultaneously provide wireless communication services as well as new services such as wireless sensing, computing, AI, storage, and / or security.

[0035] In some implementations, conventional methods for managing Protocol Data Unit (PDU) sessions in traditional 5G wireless communication systems may primarily target the forwarding / transmission of user plane (UP) data. UP data is typically associated with services provided by external mobile users, such as mobile applications (APPs) and web services. This UP data is usually generated outside the 5G wireless communication system (transparent / invisible to 3GPP protocols) and is initiated / terminated either at the user equipment (UE) or at the data network server. 5G CN nodes and / or 5G RAN nodes can process this data and forward it from the input port to the output port without needing to concern themselves with the UP data type / content or the characteristics of the user data.

[0036] In some implementations, there may be issues / challenges associated with handling data for various new service types. For example, in 5G-A and 6G wireless communication systems, data for various new service types (e.g., sensing, computing, AI, storage, and / or security services) with different characteristics can be generated, processed, and transmitted within the wireless communication system (visible / available to 3GPP protocols). Furthermore, any 5G-A and / or 6G CN node and / or RAN node or UE may be allowed to initiate so-called "data service sessions" based on local needs and terminate these sessions at any other CN node and / or RAN node or UE. Intermediate / relay network (NW) nodes along the "data service session path" may also need to be concerned with the type / content / characteristics of the data service data. Therefore, conventional methods of PDU session management in wireless communication systems may not effectively support or handle the forwarding / transmission of data for various data services (i.e., data service data).

[0037] In some implementations of a data service session management framework for future generation communication standards (e.g., 6G), a new data agent (DA) logical entity or node can be defined and responsible for managing various new 6G data services. The DA's control part (DA-C) can be the logical control portion of the DA, responsible for configuring, coordinating, and / or monitoring data service sessions across different network (NW) nodes. The DA-C can typically generate control data (e.g., referred to as data service control data) for one or more associated DAs' execution parts (DA-Es) located in the same or other NW nodes. Upon receiving data service control data (e.g., data service policy instructions, action commands, and detailed configuration parameters) from its associated DA-C, the DA-E entity can take corresponding data processing actions. Such a framework may present some challenges, such as how to transmit data service control data across different NW nodes to enable future 5G-A and 6G wireless communication systems to transmit data service control data and adapt to various (e.g., 6G) new data services.

[0038] This disclosure describes various designs, models, and / or methods for transmitting data service control data in a wireless communication system to perform data services, enabling future wireless communication systems to support or process the forwarding / transmission of data service data, and / or adapt to the various needs of various new services.

[0039] Figure 1AA wireless communication system 100 is illustrated, comprising a core network (CN) 110, a radio access network (RAN) 130, and one or more user equipments (UEs) (152, 154, and 156). RAN 130 may include one or more base stations. These 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 signaling / receiving equipment, such as a Universal Mobile Telecommunications System (UMTS) NodeB. In one embodiment, core network 110 may include a 5G core network (5GC), and interface 125 may include a new generation (NG) interface. The core network 110 also 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).

[0040] refer to Figure 1AThe first UE 152 may receive one or more downlink communications 142 from RAN 130 and send one or more uplink communications 141 to RAN 130. Similarly, the second UE 154 may receive downlink communications 144 from RAN 130 and send uplink communications 143 to RAN 130; the third UE 156 may receive downlink communications 146 from RAN 130 and send uplink communications 145 to RAN 130. As an example and not a limitation, downlink communications may include a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH), and uplink communications may include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0041] In some implementations, such as Figure 1BAs shown, the core network (CN) may include one or more core network functions, which are described below. The core network can communicate with UE 171 (or via RAN 172). Functions that UPF 173 can perform include, but are not limited to: acting as an anchor point for intra / inter-intra-radio access technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, user plane quality of service (QoS) processing, downlink packet buffering, and downlink data notification triggering. Functions that AMF 176 can perform include, but are not limited to: registration management, UE 171 connection management, UE 171 reachability management, and mobility management. AMF also performs access authentication and access authorization. AMF 176 may have non-access stratum (NAS) secure termination functionality and relay session management NAS messages between UE 171 and SMF 177. AMF 176 also performs SMF selection functionality during communication session establishment and UE mobility procedures. The AMF can forward QoS profiles from the SMF to the RAN (or Access Network (AN)) and QoS rules from the SMF to the UE. The functions that the SMF 177 can perform include, but are not limited to: establishing, modifying, and releasing communication sessions; UE IP address allocation and management (including optional authorization functions); selection and control of the UPF 173; and downlink data notification. Each SMF can control one or more UPFs, and each SMF is associated with a service area that is the set of UPF service areas of all UPFs under its control. The SMF derives QoS profiles based on Policy Control and Charging (PCC) rules, generates QoS flows, sends QoS profiles to the RAN, and sends packet detection rules (PDRs) to the UPFs. PCC rules are bound to QoS flows. In some implementations, the SMF also selects UPFs based on UE or session granularity and can assign IP addresses, collect charging data, connect to a charging center, etc. PCF 179 is responsible for a unified policy framework, providing policy rules for control plane functions, defining policy control and charging (PCC) rules, and authorizing Session Management Functions (SMF) based on service data flow (SDF). The functions performed by PCF include, but are not limited to, providing policy rules and controlling other network nodes to enforce those rules. Specifically, PCF provides access and mobility-related policies to AMF 176 so that AMF can enforce these policies during mobility processes.

[0042] In some implementations, in a typical international mobile telecommunications (IMT) wireless communication system (e.g., 5G-NR as defined by 3GPP), the core network (CN) may include various types of control plane (CP) nodes or CP entities (e.g., 5G AMF / SMF) and user plane (UP) nodes or UP entities (e.g., 5G UPF). Reference Figure 1C In the case of non-splitting RAN, the RAN node (e.g., a 5G aggregated gNB including CP and UP parts) then terminates at the UE via a radio link (RL) in the air interface, which includes a signaling radio bearer (SRB) and / or a data radio bearer (DRB). (See reference) Figure 1D In the case of RAN splitting, the RAN nodes (e.g., 5G de-aggregated gNBs, which include centralized unit (CU) control plane (CU-CP) nodes, CU-UP nodes, and distributed unit (DU) nodes or DU entities) then terminate at the UE via the RL in the air interface. The CP portion or CP nodes are responsible for generating, processing, and transmitting control signaling, such as for (re)configuration and monitoring of nodes; the UP portion or UP nodes are responsible for processing and transmitting user UP data, such as data typically associated with external mobile apps and web services. Both the CP plane and UP plane have their own interfaces and / or protocol stacks, and typically cross from the CN domain to the RAN network, and then to the UE.

[0043] This disclosure describes various embodiments for transmitting data service control data in a wireless communication system, solving at least one problem / challenge discussed in this disclosure, thereby improving the efficiency of various data services, enabling future wireless communication systems to support or process the forwarding / transmission of data service data (e.g., the content of the data service), and / or adapting to the various needs of next-generation wireless services in wireless communication systems.

[0044] Figure 2An example of an electronic device 200 is shown, which is used 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 a wireless transmit (Tx) / receive (Rx) circuitry 208 for transmitting / receiving communications with a UE and / or other base stations. The electronic device 200 may also include a network interface circuitry 209 for the base station to communicate with other base stations and / or the core network, for example, via fiber optic or wired interconnects, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

[0045] The electronic device 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more processors of the processors 221 to perform functions of the network node. Parameters 228 may include parameters supporting the execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0046] Figure 3An example of an electronic device for implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. The UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. The UE 300 may include a communication interface 302, system circuitry 304, input / output interfaces (I / O) 306, display circuitry 308, and storage device 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 / circuit. The system circuitry 304 may be implemented, for example, using one or more systems-on-a-chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system circuitry 304 may be part of an implementation of any desired functionality in the UE 300. In this regard, system circuitry 304 may include logic that facilitates, for example, the following: decoding and playing music and video (e.g., MP3, MP4, Moving Picture Experts Group (MPEG), Audio Video Interleaving (AVI), Freeform Lossless Audio Codec (FLAC), Audio Coding Technology 3 (AC3), or Waveform Audio File Format (WAV) decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, for example, for internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., infrared (IR) sensors), and other types of inputs.

[0047] refer to Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316, which processes signal transmission and reception via one or more antennas 314. The communication interface 302 may include one or more transceivers. These transceivers may be wireless transceivers that include modulation / demodulation circuitry, digital-to-analog converters (DACs), shapers, analog-to-digital converters (ADCs), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may conform to any of various formats, protocols, modulations (e.g., Quadrature Phase Shift Keying (QPSK), 16-QAM (Quadrature Amplitude Modulation), 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interface 302 may include a transceiver that supports transmission and reception under 2G, 3G, Bluetooth (BT), WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / LTE, 5G standards and / or 6G or any future standards. However, the techniques described below are applicable to other wireless communication technologies, regardless of whether these technologies are developed by the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, the Institute of Electrical and Electronics Engineers (IEEE), or other collaborative organizations or standards bodies.

[0048] refer to Figure 3System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute the instructions 326 to perform the desired functions of UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT data, WiFi data, 3G data, 4G data, 5G data, 6G data, or other data that UE 300 may send or receive via communication interface 302. In various embodiments, the system power of UE 300 may be provided by power storage devices such as batteries or transformers.

[0049] Figure 4 A conventional mechanism for PDU session management in a wireless communication system (e.g., 5G) is illustrated. The AMF entity 430 in the 5GC is the anchor control point for a specific served UE 410's PDU session. The AMF triggers control signaling procedures to establish or modify PDU sessions across different NW nodes (including the SMF 440). After configuring UP resources for UP data transmission in the UPF 450, gNB 420, and UE respectively, external UP data associated with the served UE can be transmitted via a "tunnel or DRB" across different NW nodes. During UP data transmission, UP resources (e.g., "tunnel or DRB") can be reconfigured as needed. In some implementations, a conventional communication control plane (CP) connection can primarily handle the transmission of communication service control data across different NW nodes.

[0050] In various embodiments, new mechanisms may be included for transmitting data service control data in a wireless communication system to perform data services. Figure 5This illustrates a new mechanism for data service session management in future wireless communication systems. For any type of network node (NF, RAN, or UE in a CN), the network node can act as a source / requesting node, intermediate / relay node, or target / response node for a specific data service session, and the network node can include two basic new logical functions: "DA-C" and "DA-E". The "DA-C" entity is responsible for configuring, coordinating, and / or monitoring data service sessions across different NW nodes; while the "DA-E" entity is responsible for processing and / or forwarding the data service session data, i.e., the data service data. In some implementations, a network node can include both a DA-C entity and a DA-E entity, and in this case, the node's DA-C entity is responsible for the node's DA-E. Alternatively, in some implementations, different network nodes can include both DA-C and DA-E (i.e., a network node can include only a DA-C entity or a DA-E entity), and in this case, there is cross-node control and cooperation between the DA-C and DA-E in different NW nodes.

[0051] In some implementations for specific data service sessions across multiple NW nodes, refer to Figure 6 Each involved NW node (e.g., target node 610, intermediate or relay node 630, and / or source node 620) can first establish an end-to-end (E2E) virtual control plane 652 for the data service session, and then each involved NW node can establish an E2E virtual execution plane 656 for the data service session. Data service control data (e.g., data used to guide and configure associated DA-E processing and / or forwarding resources) is processed and transmitted in the virtual control plane of the data service session. The transmission of data service control data can be independent of the control plane (CP) signaling process of the communication service (e.g., the E2E communication control plane 672 managed by the Comm-C entity in each NW node), or coupled / associated with the CP signaling process of the communication service. In some implementations, the transmission of data service data may be independent of the user plane (UP) signaling process of the communication service (e.g., the E2E communication user plane 676 managed by the Comm-U entity in each NW node), or coupled / associated with the UP signaling process of the communication service.

[0052] In various embodiments, each network node (e.g., source node 620, intermediate / relay node 630, and / or target node 610) or entity may include some or all of the following logical functional entities: a "DA control" entity and a "DA execution" entity. The "DA control" entity is responsible for controlling, configuring, coordinating, and / or monitoring data service sessions across different NW nodes or entities. The "DA execution" entity is responsible for various data processing and / or transmissions of the data service session, i.e., processing data service data. The interface protocol stacks between multiple "DA control" entities are coupled / shared / associated with the interface protocol stacks between multiple "COMM-C" entities; the interface protocol stacks between multiple "DA execution" entities are coupled / shared / associated with the interface protocol stacks between multiple "COMM-E" entities; and / or the interface protocol stacks between the "DA control" entity and the "DA execution" entity are coupled / shared / associated with the interface protocol stacks between the "COMM-C" entity and the "COMM-E" entity.

[0053] In various embodiments, for a specific data service session spanning multiple network nodes or entities, the “DA control” entity in each involved NW node or entity should first establish a virtual “E2E control plane for the data service session”. Figure 6 (The middle line is dashed), and then the "DA Execution" entity in each involved NW node or entity should establish a virtual "E2E Execution Surface of Data Service Session" ( Figure 6 (The middle line is dashed). The "control plane of the data service session" generates and transmits control data for the data service session via the CP signaling process of communication services across multiple NW nodes or entities. The "execution plane of the data service session" processes and transmits data service data across multiple NW nodes or entities.

[0054] In various embodiments, for a specific data service session spanning multiple network nodes or entities, the "DA control" in the source node determines the "data service session path" as needed, i.e., which are intermediate / relay nodes and the target node or entity. The "DA control" in each involved NW node or entity determines the DA-E processing resources (e.g., central processing unit (CPU), graphics processing unit (GPU), data processing unit (DPU), neural network processor (NPU), tensor processor (TPU), digital signal processor (DSP), storage devices, caches, etc.) within its associated "DA execution" entity. The "DA control" in each involved NW node or entity determines the DA-E transport resources (e.g., data transmission tunnels, wireless bearers, etc.) between its associated "DA execution" entities.

[0055] In various embodiments, control plane data transmission of a data service session is coupled / shared / associated with the CP signaling process of a communication service, for example, in the form of "information element (IE) containers," and execution plane data of the data service session is carried via one or more data service session tunnels and one or more data service session radio bearers (RBs), which are (re)configured from the control plane data of the data service session from the DA-C entity. Execution plane data of a data service session can also be transmitted by one or more dedicated new data service session tunnels and one or more new data service session RBs, which are used for data services, i.e., different from those tunnels or DRBs used for communication services. Execution plane data of a data service session can also be transmitted by one or more conventional UP tunnels and one or more DRBs used for communication services.

[0056] In various embodiments of this disclosure, communication service refers to data transmission service of the UE and / or mobile user APP layer provided by the wireless communication system; that is, communication service data is typically generated outside the wireless system. COMM-C refers to the control part of the NW node used to control the communication PDU session, such as gNB-CU-CP, SMF, etc.; COMM-E (or COMM-U) refers to the execution part of the NW node used to execute the communication PDU session (i.e., transmit UP data), such as gNB-CU-UP, UPF, etc.; data service refers to new services provided by the wireless system that go beyond traditional communication services, such as new sensing, computing, intelligence, storage and / or security services. The data service data corresponding to these new services is generated inside the wireless system, for example, generated by the NF in the UE AS layer, RAN node and CN; data proxy (data Agent (DA): A new logical node or functional entity that supports data services and data service sessions within a wireless system; DA Control (DA-C) refers to the control part of the DA, used to control / coordinate data service sessions; DA Execution (DA-E) refers to the execution part of the DA, used to execute / process data service sessions; DA-E Processing Resources refer to the execution resources within the DA execution entity used for various data service data processing (e.g., CPU, GPU, DPU, NPU, TPU, DSP, storage devices, etc.); DA-E Transmission Resources refer to the execution resources used to transmit data service data between multiple DA execution entities (e.g., data transmission tunnels, radio bearers, etc.); Data Service Session refers to the data session used for data services between a source node and a target node, which can also span multiple intermediate / relay nodes; Data Service Data refers to data associated with a specific data service session, i.e., different from communication service data, and comparable to the UP data of the communication service; Data Service Control Data refers to the control data of a specific data service session, i.e., generated and transmitted by the DA-C entity, and comparable to the CP data of the communication service; Data Service Session Radio Bearer (radio... A bearer (RB) refers to a wireless bearer that carries and / or transmits data service (control) data over an air interface; a data service session tunnel refers to a data tunnel that carries and / or transmits data service data over a wired interface; and a data service anchor node refers to a central control / coordination node or entity used to control data service sessions, such as an AMF, a Network Data Analysis Function (NWDAF), a gNB, or an xNB, depending on the data service use case.

[0057] Figure 7Various exemplary methods and architectures for processing and transmitting data service control data are illustrated in various embodiments, and the architecture may include some 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. Data service control data may be processed and / or transmitted along at least one of the following paths: a first path 751, where signaling terminates at the CN, involving the AMF and SMF; a second path 752, where signaling terminates at the CN, involving the AMF; a third path 753, where signaling terminates at the CN; a fourth path 754, where signaling terminates at the RAN, involving the RRC; and / or a fifth path 755, where signaling terminates at the RAN.

[0058] In various embodiments, for a specific data service session, each involved NW node (e.g., source node, intermediate / relay node, or target node) or entity may include at least one logical functional entity: DA-C and / or DA-E. In some embodiments, an NW node may include only DA-C, while the associated DA-E of that DA-C may be in another NW node. DA-C can generate the data service configuration.

[0059] In some implementations, the DA-C entity is responsible for generating and / or forwarding data service control data (e.g., data service policy guidelines, action commands, and / or detailed configuration parameters) across different NW nodes or entities. In some implementations, the CN can be a 6G CN, which may include some or all of the following: 6G AMF 712, 6G SMF 714, and / or 6G DA-C entity 716. The DA-C entity may be responsible for initiating or terminating data service control data at the CN. In some implementations, the RAN can be a 6G RAN (e.g., 6G xNB), which may include some or all of the following: 6G RRC entity 722, 6G DA-C entity 724, and / or 6G L2 / L1 entity 726; wherein, the DA-C entity may be responsible for initiating or terminating data service control data at the RAN. The UE can be a 6G UE, which may include some or all of the following: 6G Non-Access Stratum (NAS) entity / layer 732, 6G DA-C entity 734, 6G RRS entity 735, 6G DA-C entity 736, and / or 6G L2 / L1 entity 739; wherein, 6G DA-C entities 734 and / or 736 (which may be access stratum (AS) layer DA-C entities) may be responsible for initiating or terminating data service control data at the UE. In some implementations, 6G DA-C entity 734 is the same as 6G DA-C entity 736, therefore, UE 730 may effectively include a single DA-C entity.

[0060] This disclosure includes various exemplary schemes and / or architectures for processing and transmitting data service control data.

[0061] For one scheme (Scheme 1), from the perspective of the 6G CN: the DA-C entity in the CN can be part of the 6G SMF, 6G AMF, or 6G RAN, or directly connected to the 6G SMF, 6G AMF, or 6G RAN. Scheme 1-1: When the DA-C entity is connected to the 6G SMF, data service control data in the 6G CN can be processed and forwarded via the 6G SMF (from the 6G AMF / then further forwarded to the 6G AMF), i.e., coupled / associated with the SMF-related processes of the communication service. Scheme 1-2: When the DA-C entity is connected to the 6G AMF, data service control data in the 6G CN can be processed and forwarded via the 6G AMF, i.e., coupled / associated with the AMF-related processes of the communication service. Scheme 1-3: When the DA-C entity is directly connected to the 6G RAN, data service control data in the 6G CN can be directly processed and forwarded via the 6G RAN, i.e., independent of any 6G CN process. In this case, the interface between the 6G DA-C entity and the RAN can be redefined, employing an independent protocol stack and a new signaling connection.

[0062] For another scheme (Scheme 2), from the perspective of 6G RAN: the DA-C entity in the RAN can be part of a 6G RRC entity or a 6G L2 / L1 entity, or directly connected to a 6G RRC entity or a 6G L2 / L1 entity. Scheme 2-1: When the DA-C entity is connected to a 6G RRC entity, data service control data in the 6G RAN can be processed and forwarded via the 6G RRC, i.e., coupled / associated with the RRC-related processes of the communication service. Scheme 2-2: When the DA-C entity is directly connected to a 6G L2 / L1 entity, data service control data in the 6G RAN can be directly processed and forwarded via the 6G L2 / L1, i.e., independent of any RRC-related processes. In this case, the interface between the 6G DA-C entity and the L2 / L1 entity can be redefined, using an independent protocol stack and a new signaling connection.

[0063] In some implementations, 6G CN or 6G RAN data service control data can be transmitted over the air interface between the 6G RAN and the UE via one or more conventional communication service SRBs or one or more new data service session radio bearers.

[0064] For another option (Option 3): From the perspective of the 6G UE NAS layer: The DA-C entity can be part of a 6G NAS entity or a 6G RRC entity, or directly connected to a 6G NAS entity or a 6G RRC entity. Option 3-1: When the DA-C entity is connected to a 6G NAS entity, data service control data in the NAS layer can be processed and forwarded via the 6G NAS, i.e., coupled / associated with NAS-related processes of the communication service. Option 3-2: When the DA-C entity is directly connected to a 6G RRC entity, data service control data in the NAS layer can be processed and forwarded via the 6G RRC, i.e., independent of any NAS-related processes. In this case, the Service Access Point (SAP) between the 6G DA-C entity and the RRC entity can be redefined, employing an independent protocol stack and a new signaling connection.

[0065] For another option (Option 4): From the perspective of the 6G UE AS layer: the DA-C entity can be part of a 6G RRC entity or a 6G L2 / L1 entity, or directly connected to a 6G RRC entity or a 6G L2 / L1 entity. Option 4-1: When the DA-C entity is connected to a 6G RRC entity, data service control data in the AS layer can be processed and forwarded via the 6G RRC, i.e., coupled / associated with the RRC-related processes of the communication service. Option 4-2: When the DA-C entity is directly connected to a 6G L2 / L1 entity, data service control data in the AS layer can be processed and forwarded via the 6G L2 / L1 entity, i.e., independent of any RRC-related processes. In this case, the SAP between the 6G DA-C entity and the L2 / L1 entity can be redefined, employing an independent protocol stack and a new signaling connection.

[0066] This disclosure describes various embodiments for transmitting data service control data in a wireless communication system, which may be partly or wholly derived from the above. Figures 2 to 3 The core network functions, network base stations, and / or user equipment described herein are used to implement this. Various embodiments of this disclosure can improve the efficiency of various data services, enabling future wireless communication systems to support or process the forwarding / transmission of data service data, and / or adapt to the diverse needs of next-generation wireless services.

[0067] In various embodiments, in order to support new service types (e.g., sensing, computing, intelligence, storage, and / or security services) in wireless systems (e.g., future systems and / or 6G systems), a new mechanism and / or architecture for transmitting data service control data can be applied to any type of network node or entity (e.g., NF, RAN node, or UE in a 6G CN) for specific data service session management (e.g., establishing, modifying, and releasing, etc.), and each involved network node or entity includes two basic new logical functions: "DA control" (DA-C) and "DA execution" (DA-E).

[0068] In some implementations, the DA-C can be a new logical network entity responsible for configuring, controlling, coordinating, and / or monitoring data service sessions across different NW nodes or entities. The DA-C entity typically generates data service control data for one or more associated DA-Es, which are the execution parts of the DA and can reside on the same NW node or other NW nodes. Upon receiving data service control data from its associated DA-C, the DA-E entity can take appropriate data processing actions. The data service control data may include some or all of the following: data service policy guidelines, action commands, and / or detailed configuration parameters, etc.

[0069] In some implementations, the COMM-C (e.g., AMF / SMF / RRC) is the control portion of a PDU session used to control / coordinate communication services. Furthermore, the COMM-C can send data service control data generated by the DA-C, for example, in the form of an "IE container." The following various embodiments may be based on the assumption that the DA-C and COMM-C (e.g., AMF / SMF / RRC) are not deployed together. In some implementations, the DA-C entity may reside on the same NW node or a different NW node as the COMM-C (e.g., AMF / SMF / RRC).

[0070] refer to Figure 8AThis disclosure describes various embodiments of a method 800 for transmitting data service control data via wireless communication. Method 800 may include some or all of the following: step 810, where a first data proxy control portion (DA-C) entity within a first network node sends first data service control data to a second network node, causing the second network node to communicate with a second DA-C entity within a third network node to perform a 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, the second data service control data instructing a target data proxy execution portion (DA-E) entity associated with the second DA-C entity; and / or step 820, where the first DA-C entity receives the second data service control data from the second network node for establishing a data service session channel between the first and third network nodes, wherein the data service session channel is transmitted between the first network node and the target DA-E via a communication service session channel between the first and third network nodes. The first network node is a data service request node, the second network node is a data service anchor node or a data service response node, and / or the third network node is a data service response node.

[0071] refer to Figure 8B This disclosure describes various embodiments of a method 850 for transmitting data service control data via wireless communication. Method 850 may include some or all of the following steps: step 860, where a second network node receives first data service control data from a first data proxy control portion (DA-C) entity within a first network node; step 870, where the second network node communicates with a second DA-C entity within a third network node to perform a 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, the second data service control data indicating a target data proxy execution portion (DA-E) entity associated with the second DA-C entity; and / or step 880, where the second network node sends the second data service control data to the first DA-C entity to establish a data service session channel between the first and third network nodes, wherein the data service session channel is transmitted between the first network node and the target DA-E entity via a communication service session channel between the first and third network nodes. The first network node is a data service request node, the second network node is a data service anchor node or a data service response node, and / or the third network node is a data service response node.

[0072] In some implementations, in addition to any part, all or any combination of one or more other implementations / one or more other embodiments described in this disclosure, 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 a CN functional entity; the second network node is any one of a UE, a RAN node, a CN node or a CN functional entity; and / or the third network node is any one of a UE, a RAN node, a CN node or a CN functional entity.

[0073] In some implementations, in addition to some, all, or any combination of one or more other implementations / one or more other embodiments described in this disclosure, 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 a CN functional entity.

[0074] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of a first DA-C entity within a first network node sending first data service control data to a second network node includes: the first DA-C entity within a UE sending the first data service control data to a non-access stratum (NAS) entity within the UE; the NAS entity within the UE sending the first data service control data to a radio resource control (RRC) entity within the UE; and / or the RRC entity within the UE sending the first data service control data to the RAN via a signaling radio bearer (SRB) over the air interface.

[0075] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node communicating with a second DA-C entity within a third network node to perform a data service includes: the RAN node sending first data service control data to the Access Mobility Function (AMF) in the CN via an N2 reference interface for communication services; the AMF in the CN sending the first data service control data to the Session Management Function (SMF) in the CN; the SMF in the CN identifying the second DA-C entity to perform the data service; the SMF in the CN sending the first data service control data to the second DA-C entity within the CN; the second DA-C entity generating second data service control data; the second DA-C entity sending the second data service control data to the SMF; the SMF sending the second data service control data to the AMF; and / or the AMF sending the second data service control data to the RAN node via the N2 reference interface for communication services.

[0076] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node communicating with a second DA-C entity within a third network node to perform a data service includes: the RAN node sending first data service control data to the AMF in the CN via an N2 reference interface for communication services; the AMF in the CN identifying the second DA-C entity to perform the data service; the AMF in the CN sending the first data service control data to the second DA-C entity within the CN; the second DA-C entity generating second data service control data; the second DA-C entity sending the second data service control data to the AMF; and / or the AMF sending the second data service control data to the RAN node via the N2 reference interface for communication services.

[0077] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node sending the second data service control data to the first DA-C entity includes: the RAN node sending the second data service control data to the RRC entity in the UE via the SRB on the air interface; the RRC entity sending the second data service control data to the NAS entity in the UE; and / or the NAS entity sending the second data service control data to the first DA-C entity in the UE.

[0078] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of a first DA-C entity within a first network node sending first data service control data to a second network node includes: the first DA-C entity within a UE sending the first data service control data to an RRC entity within the UE; and / or the RRC entity within the UE sending the first data service control data to a RAN node via an SRB on the air interface.

[0079] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node communicating with a second DA-C entity within a third network node to perform a data service includes: the RAN node identifying a second DA-C entity within the CN to perform the data service; the RAN node sending first data service control data to the second DA-C entity through a new network interface for the data service; the second DA-C entity generating second data service control data; and / or the second DA-C entity sending the second data service control data to the RAN node through the new network interface for the data service.

[0080] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node sending the second data service control data to the first DA-C entity includes: the RAN node sending the second data service control data to the RRC entity in the UE via the SRB on the air interface; and / or the RRC entity sending the second data service control data to the first DA-C entity in the UE.

[0081] In some implementations, in addition to some, all, or any combination of one or more other implementations / one or more other embodiments described in this disclosure, the first network node is a UE; the second network node is a RAN node; and / or the third network node is the same as the second network node.

[0082] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of a first DA-C entity within a first network node sending first data service control data to a second network node includes: the first DA-C entity within a UE sending the first data service control data to an RRC entity within the UE; and / or the RRC entity within the UE sending the first data service control data to a RAN node via an SRB on the air interface.

[0083] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node communicating with a second DA-C entity within a third network node to perform a data service includes: the RAN node determining the second DA-C entity to which the data service is to be performed; the RRC in the RAN node sending first data service control data to the second DA-C entity within the RAN node; the second DA-C entity generating second data service control data; and / or the second DA-C entity sending the second data service control data to the RRC entity in the RAN node.

[0084] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the step of the second network node sending the second data service control data to the first DA-C entity includes: the RAN node sending the second data service control data to the RRC entity in the UE via the SRB on the air interface; and / or the RRC entity in the UE sending the second data service control data to the first DA-C entity within the UE.

[0085] In some implementations, in addition to one or more other implementations / one or more other embodiments described in this disclosure, the steps are as follows: a first DA-C entity within the UE determines a second DA-C entity to perform a data service; the first DA-C entity within the UE sends first data service control data to the second DA-C entity within the RAN node; the second DA-C entity generates 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 over the air interface.

[0086] This disclosure describes various exemplary embodiments for transmitting data service control data in a wireless communication system. These exemplary embodiments are merely examples and do not constitute limitations. Any steps and / or operations in the same embodiment / implementation or multiple different embodiments / implementations in this disclosure may be combined or arranged in any number or order as needed. Two or more steps and / or operations may be performed in parallel. The embodiments and implementations in this disclosure may be used individually or in combination in any order. Furthermore, each method (or embodiment) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits).

[0087] The following embodiments use AI-related data services requested / triggered by the UE (i.e., the DA-C in the UE) as non-limiting examples. Other embodiments of data services or data services requested by other network nodes (RAN, or CN, or CN functional entity) can also be applied similarly.

[0088] Example Set I This disclosure describes various embodiments of AI model data for UE triggering using schemes 1-1 and 3-1, wherein the 6G CN DA-C entity may be part of or directly connected to the 6G SMF, and the 6G UE local DA-C entity may be part of or directly connected to the 6G UE NAS.

[0089] Various embodiments can be applied to the following exemplary use cases. The data service request node is a user equipment (UE) lacking computing and storage resources. The UE reports AI training data to the 6G CN DA-E entity in advance. The 6G CN DA-E collects data for AI model training, thereby subsequently obtaining a trained AI model. When the source UE requests AI model data from the target 6G CN DA-E entity, the source UE can send a data service request to the associated COMM-C entity via a data service anchor node (e.g., SMF). The anchor SMF then sends a request to the DA-C to establish a control plane connection for data services between the CN and the UE.

[0090] Figure 9 Exemplary processes of various embodiments are illustrated, which include some or all of the following: 6G UE Local DA-C 991, UE NAS 992, 6G UE RRC 993, 6G RAN 994, 6G AMF 995, 6G SMF 996, and / or 6G CN DA-C 997. This exemplary process may include some or all of the following steps.

[0091] For step 910, the UE local DA-C entity generates a data service session configuration request message based on its own AI requirements and sends the request message to the UE local NAS entity, and then further sends the request message to the UE local RRC entity. The UE RRC entity then sends the request message to the RAN serving node (e.g., xNB) to obtain the desired AI model data in the target DA. The data service session configuration request includes data service control data generated by the UE local DA-C.

[0092] For step 920, the RAN service node forwards the data service session configuration request to the target AMF.

[0093] In step 930, the target AMF selects the target SMF and then forwards the data service session configuration request to the target SMF.

[0094] For step 940, the anchor SMF selects the target DA-C entity and then forwards the data service session configuration request to the target DA-C entity.

[0095] In step 950, the target DA-C entity receives and parses the data service session configuration request message (to understand the source UE's data service intent) and generates a data service session configuration response message containing data service control data, such as configuration signaling for DA-E transport resources. The data service control data in the data service session configuration response message (the data service control data in step 950) may differ from the data service control data in the data service session configuration request message (the data service control data in steps 910, 920, 930, and / or 940).

[0096] For step 960, DA-C sends a data service session configuration response to the anchor SMF, then the SMF sends the response to the AMF, and then the AMF sends the response to the RAN service node via N2AP reference signaling.

[0097] For step 970, the RAN serving node receives the data service session configuration response message and then generates a corresponding data service session configuration response message containing data service control data. For example, it sends the configuration signaling of UE DA-E transmission resources to the UE RRC entity via the SRB on the air interface. Then, the UE RRC entity forwards the data service session configuration response to the UE local NAS entity and then further forwards the response to the UE local DA-C entity.

[0098] In some implementations, the process may further include: after the control plane connection for data services between the CN and the UE is established, the 6G CN DA-E and the 6G UE are ready to transmit the AI ​​model data required by the UE.

[0099] Example Set II This disclosure describes various embodiments of AI model data for UE triggering using schemes 1-2 and 3-1, wherein a 6G CN DA-C entity can be connected to a 6G AMF, and a 6G UE local DA-C entity can be part of a 6G UE NAS or directly connected to a 6G UE NAS.

[0100] Various embodiments can be applied to the following exemplary use cases. The data service request node is a UE lacking computing and storage resources. The UE reports AI training data to the 6G CN DA-E entity in advance. The 6G CN DA-E collects data for AI model training, thereby subsequently obtaining a trained AI model. When the source UE requests AI model data from the target 6G CN DA-E entity, the source UE can send a data service request to the associated COMM-C entity via a data service anchor node (e.g., AMF). The anchor AMF then sends a request to the DA-C to establish a control plane connection for data services between the CN and the UE.

[0101] Figure 10 Exemplary processes of various embodiments are illustrated, which include some or all of the following: 6G UE Local DA-C 1091, UE NAS 1092, 6G UE RRC 1093, 6G RAN 1094, 6G AMF 1095 and / or 6G CNDA-C 1097. These exemplary processes may include some or all of the following steps.

[0102] For step 1010, the UE local DA-C entity generates a data service session configuration request message based on its own AI requirements and sends the request message to the UE local NAS entity, and then further sends the request message to the UE local RRC entity. The UE RRC entity then sends the request message to the RAN serving node (e.g., xNB) to obtain the desired AI model data in the target DA. The data service session configuration request includes data service control data generated by the UE local DA-C.

[0103] For step 1020, the RAN service node forwards the data service session configuration request to the anchor AMF.

[0104] For step 1030, the anchor AMF selects the target DA-C entity and then forwards the data service session configuration request to the target DA-C entity.

[0105] In step 1040, the target DA-C entity receives and parses the data service session configuration request message (to understand the source UE's data service intent) and generates a data service session configuration response message containing data service control data, such as configuration signaling for DA-E transport resources. The data service control data in the data service session configuration response message (generated by the target DA-C entity in step 1040) may differ from the data service control data in the data service session configuration request message (the data service control data in steps 1010, 1020, and / or 1030).

[0106] For step 1050, DA-C sends a data service session configuration response to the anchor AMF, and then the AMF sends the response to the anchor RAN via N2AP reference signaling.

[0107] For step 1060, the RAN serving node receives the data service session configuration response message and then generates a corresponding data service session configuration response message containing data service control data. For example, it sends the configuration signaling of UE DA-E transmission resources to the UE RRC entity via the SRB on the air interface. Then, the UE RRC entity forwards the data service session configuration response to the UE local NAS entity and then further forwards the response to the UE local DA-C entity.

[0108] In some implementations, the process may further include: after the control plane connection for data services between the CN and the UE is established, the 6G CN DA-E and the 6G UE are ready to transmit the AI ​​model data required by the UE.

[0109] Example Set III This disclosure describes various embodiments of AI model data for UE triggering using schemes 1-3 and 3-2, wherein the 6G CN DA-C entity can be directly connected to the 6G RAN via a new signaling connection, and the 6G UE local DA-C entity can be directly connected to the 6G UE RRC entity.

[0110] Various embodiments can be applied to the following exemplary use cases. The data service requesting node is a UE lacking computing and storage resources. The UE reports AI training data to the 6G CN DA-E entity in advance. The 6G CN DA-E collects data for AI model training, thereby subsequently obtaining a trained AI model. When the source UE requests AI model data from the target 6G CN DA-E entity, the source UE can send a data service request to the associated COMM-C entity via a data service anchor node (e.g., RAN). The anchor RAN then sends a request to the 6G CN DA-C to establish a control plane connection for data services between the CN and the UE.

[0111] Figure 11 Exemplary processes of various embodiments are illustrated, which include some or all of the following: 6GUE local DA-C 1191, 6G UE RRC 1193, 6G RAN 1194, and / or 6G CN DA-C 1197. These exemplary processes may include some or all of the following steps.

[0112] For step 1110, the UE local DA-C entity generates a data service session configuration request message based on its own AI requirements and sends the request message to the UE local RRC entity. Then, the UE RRC entity sends the request message to the anchor RAN to obtain the desired AI model data in the target DA. The data service session configuration request includes data service control data generated by the UE local DA-C.

[0113] For step 1120, the anchor RAN selects the target DA-C entity and then forwards the data service session configuration request to the target DA-C entity via a new signaling connection.

[0114] For step 1130, the target DA-C entity receives and parses the data service session configuration request message (to understand the source UE's data service intent), and accordingly generates a data service session configuration response message containing data service control data, such as configuration signaling for DA-E transport resources. The data service control data in the data service session configuration response message (the data service control data generated by the target DA-C entity in step 1130) may differ from the data service control data in the data service session configuration request message (the data service control data in steps 1110 and / or 1120).

[0115] For step 1140, DA-C sends a data service session configuration response to the anchor RAN via a new signaling connection.

[0116] For step 1150, the anchor RAN receives the data service session configuration response message and then generates a corresponding data service session configuration response message containing data service control data. For example, it sends UEDA-E transmission resource configuration signaling to the UE RRC entity via the SRB on the air interface, and then the UE RRC entity forwards the data service session configuration response to the local DA-C entity.

[0117] In some implementations, the process may further include: after the control plane connection for data services between the CN and the UE is established, the 6G CN DA-E and the 6G UE are ready to transmit the AI ​​model data required by the UE.

[0118] Example Set IV This disclosure describes various embodiments of AI model data for UE triggering using schemes 2-1 and 4-1, wherein the 6G RAN DA-C entity may be part of the 6G RAN RRC entity or directly connected to the 6G RAN RRC entity via a new signaling connection, and the 6G UE local DA-C entity may be part of the 6G UE RRC entity or directly connected to the 6G UE RRC entity.

[0119] Various embodiments can be applied to the following exemplary use cases. The data service request node is a UE lacking computing and storage resources. The UE reports AI training data to the 6G RAN DA-E entity in advance. The 6G RAN DA-E collects data for AI model training, thereby subsequently obtaining a trained AI model. When the source UE requests AI model data from the target 6G RAN DA-E entity, the source UE sends a data service request to the associated COMM-C entity via a data service anchor node (e.g., a 6G RAN RRC entity).

[0120] Figure 12 Exemplary processes of various embodiments are illustrated, which include some or all of the following: 6GUE local DA-C 1291, 6G UE RRC 1293, 6G RAN RRC 1294, and / or 6G RAN DA-C 1297. These exemplary processes may include some or all of the following steps.

[0121] For step 1210, the UE local DA-C entity generates a data service session configuration request message based on its own AI requirements and sends the request message to the UE local RRC entity. Then, the UE RRC entity sends the request message to the data service anchor node (e.g., a 6GRAN RRC entity) to obtain the desired AI model data in the target DA. The data service session configuration request includes data service control data generated by the UE local DA-C.

[0122] For step 1220, the anchor RRC entity selects the target 6G RAN DA-C entity and then forwards the data service session configuration request to the target DA-C entity via a new signaling connection.

[0123] For step 1230, the DA-C entity receives and parses the data service session configuration request message (to understand the source UE's data service intent), and accordingly generates a data service session configuration response message containing data service control data, such as configuration signaling for DA-E transport resources. The data service control data in the data service session configuration response message (the data service control data generated by the target DA-C entity in step 1230) may differ from the data service control data in the data service session configuration request message (the data service control data in steps 1210 and / or 1220).

[0124] For step 1240, DA-C sends a data service session configuration response to the anchor RRC entity via a new signaling connection.

[0125] For step 1250, the anchor RRC entity receives the data service session configuration response message, and then generates a corresponding data service session configuration response message containing data service control data. For example, it sends UE DA-E transmission resource configuration signaling to the UE RRC entity via the SRB on the air interface, and then the UE RRC entity forwards the data service session configuration response to the local DA-C entity.

[0126] In some implementations, the process may further include: after the control plane connection for data services between the RAN and the UE is established, the 6G RAN DA-E and the 6G UE are ready to transmit the AI ​​model data required by the UE.

[0127] Example Set IV This disclosure describes various embodiments of AI model data for UE triggering using schemes 2-2 and 4-2, wherein the 6G RAN DA-C entity may be part of the RAN L2 / L1 entity or directly connected to the RAN L2 / L1 entity via a new signaling connection, and the 6G UE local DA-C entity may be part of the 6G UE L2 / L1 entity or directly connected to the 6G UEL2 / L1 entity.

[0128] Various embodiments can be applied to the following exemplary use cases. The data service requesting node is a UE lacking computing and storage resources. The UE reports AI training data to the 6G RAN DA-E entity in advance. The 6G RAN DA-E collects data for AI model training, thereby subsequently obtaining a trained AI model. When the source UE requests AI model data from the target 6G RAN DA-E entity, the source UE will directly send a data service request to the 6G RAN DA-C entity.

[0129] Figure 13 Exemplary processes of various embodiments are illustrated, which include some or all of the following: 6GUE local DA-C 1391 and / or 6G RAN DA-C 1397. These exemplary processes may include some or all of the following steps.

[0130] For step 1310, the UE local DA-C entity generates a data service session configuration request message based on its own AI requirements and sends the request message directly to the 6G RAN DA-C entity via a new signaling connection to obtain the desired AI model data in the target DA. This new signaling can be, for example, a new SRB, one or more traditional SRBs, or a DRB (control PDU or media access control element (MAC CE)). The data service session configuration request includes data service control data generated by the UE local DA-C.

[0131] For step 1320, the DA-C entity receives and parses the data service session configuration request message (to understand the source UE's data service intent) and generates a data service session configuration response message containing data service control data, such as DA-E transport resource configuration signaling. The data service control data in the data service session configuration response message (generated by the 6G RANDA-C entity in step 1320) may differ from the data service control data in the data service session configuration request message (the data service control data in step 1210).

[0132] For step 1330, the DA-C sends a data service session configuration response message containing data service control data, such as configuration signaling for UE DA-E transport resources, to the UE local DA-C entity via a new signaling connection on the air interface (e.g., a new SRB, one or more legacy SRBs, or a DRB (control PDU or MAC CE)).

[0133] In some implementations, the process may further include: after the control plane connection for data services between the RAN and the UE is established, the 6G RAN DA-E and the 6G UE are ready to transmit the AI ​​model data required by the UE.

[0134] In some embodiments, instead of the UE triggering the data service session as the requesting node, the CN node can trigger the data service session as the requesting node (e.g., towards downstream nodes of the CN node, such as RAN nodes and / or UEs). For example, refer to Figures 9 to 11 The 6G CN DA-C can trigger a data service session in the following ways: It generates a data service session configuration request message based on its own AI needs and sends it to the anchor RAN node (e.g., ...). Figure 9 Transmitted via SMF and AMF, or as Figure 10 Send via AMF, or as Figure 11 The request message is sent directly from the UE. The data service session configuration request includes data service control data generated by the CN DA-C. The anchor RAN node selects the 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 (thus understanding the data service intent of the CN DA-C), and generates a data service session configuration response message containing data service control data, such as configuration signaling for DA-E transport resources. The data service control data in the data service session configuration response message (generated by the UE's local DA-C entity) may differ from the data service control data in the data service session configuration request message (generated by the 6G CN DA-C). The UE's local DA-C sends the data service session configuration response to the anchor RAN node via SRB or a new signaling connection. The anchor RAN node receives the data service session configuration response message, then generates a corresponding data service session configuration response message containing data service control data, such as configuration signaling for transmitting data service data, and then forwards the data service session configuration response to the CN DA-C entity. In some implementations, the process may further include: after the control plane connection for the data service between the CN and the UE is established, the 6G CN DA-E and the 6G UE are ready to transmit AI model data.

[0135] In some embodiments, a RAN node can trigger a data service session as a requesting node (e.g., toward a downstream node of that RAN node, such as a target UE). For example, refer to Figures 12 to 13 The 6G RAN DA-C can trigger a data service session by generating a data service session configuration request message based on its own AI needs. The RAN DA-C sends this message to the UEDA-C entity in the target UE (e.g., ...). Figure 12 Transmitted via RAN RRC, or as Figure 13 The UE DA-C entity receives and parses the Data Service Session Configuration Request message (to understand the RAN DA-C's data service intent) and generates a Data Service Session Configuration Response message containing data service control data, such as DA-E transport resource configuration signaling. The data service control data in the Data Service Session Configuration Response message (generated by the UE's local DA-C entity) may differ from the data service control data in the Data Service Session Configuration Request message (generated by the RAN DA-C). The UE's local DA-C sends (e.g., data service session configuration request message directly to the RAN DA-C via SRB or a new signaling connection) to the RAN DA-C. Figure 12 Transmitted via RAN RRC, or as Figure 13 The data service session configuration response is sent directly from the RAN. In some implementations, this process may further include: after the control plane connection for the data service between the RAN and the UE is established, the 6G RAN DA-E and the 6G UE are ready to transmit AI model data.

[0136] This disclosure describes methods, apparatus, and computer-readable media for wireless data services. This disclosure solves the problem of transmitting data service control data in a wireless communication system. The methods, apparatus, and computer-readable media described in this disclosure can improve the performance of data services, thereby increasing efficiency and overall performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0137] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above. The computer-readable medium may be referred to as: a non-transitory computer-readable medium (CRM) for long-term data storage, such as a flash drive or compact disk (CD); or a non-transitory computer-readable medium for short-term data storage under power, such as a storage device or random access memory (RAM). In some embodiments, the computer-readable instructions may be contained in software embodied in one or more tangible, non-transitory computer-readable media. Such non-transitory computer-readable media may be media associated with user-accessible mass storage or some kind of short-term non-transitory storage, such as internal mass storage or read-only memory (ROM). Software implementing various embodiments of this disclosure may be stored in such devices and executed by a processor (or processing circuitry). Depending on specific needs, the computer-readable medium may include one or more storage devices or chips. This software enables processors (including CPUs, GPUs, field-programmable gate arrays (FPGAs), etc.) to execute a specific process or a specific part of a specific process as described herein, including defining data structures stored in RAM and modifying these data structures according to the software-defined process.

[0138] References to features, advantages, or similar terms throughout this specification do not imply that all features and advantages achievable with this solution should be included or are indeed included in any single implementation thereof. Rather, references to features and advantages are to be understood as indicating that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, discussions of features and advantages, as well as similar terms, throughout this specification may, but do not necessarily, refer to the same embodiment.

[0139] Furthermore, the features, advantages, and characteristics described herein can be combined in any suitable manner in one or more embodiments. As a non-limiting example, a portion of one or more embodiments can be combined with another portion of other embodiments. Those skilled in the art will recognize from the description herein that this solution can be implemented without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of this solution.

Claims

1. A method for transmitting data service control data via a wireless communication data service, comprising: A first data proxy control portion (DA-C) entity within a first network node sends first data service control data to a second network node, enabling the second network node to communicate with a second DA-C entity within a third network node to perform data services based on the first data service control data generated by the first DA-C. The second DA-C entity generates second data service control data, which instructs a target data proxy execution portion (DA-E) entity associated with the second DA-C entity. The first DA-C entity receives the second data service control data from the second network node to establish a data service session channel between the first network node and the third network node. This data service session channel is transmitted via a communication service session channel between the first network node and the third network node, allowing data service data to be transmitted between the first network node and the target DA-E via the communication service session channel. in: The first network node is a data service request node. The second network node is either a data service anchor node or a data service response node, and The third network node is a data service response node.

2. A method for transmitting data service control data via wireless communication, comprising: The second network node receives first data service control data from the first data proxy control section (DA-C) entity within the first network node; The second network node communicates with a second DA-C entity within a third network node to execute a 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, which instructs a target data agent execution part (DA-E) entity associated with the second DA-C entity; and The second network node sends the second data service control data to the first DA-C entity to establish a data service session channel between the first network node and the third network node. This data service session channel is transmitted via a communication service session channel between the first network node and the third network node, enabling data service data to be transmitted between the first network node and the target DA-E entity via the communication service session channel. in: The first network node is a data service request node. The second network node is either a data service anchor node or a data service response node, and The third network node is a data service response node.

3. The method according to any one of claims 1 to 2, wherein: The first network node is any one of a user equipment (UE), a radio access network (RAN) node, a core network (CN) node, or a CN functional entity; The second network node is any one of the UE, RAN node, CN node, or CN functional entity; and The third network node is any one of the UE, RAN node, CN node, or CN functional entity.

4. The method according to any one of claims 1 to 2, wherein: The first network node is a UE; The second network node is a RAN node; and The third network node is a CN node or a CN functional entity.

5. The method according to claim 4, wherein, The first DA-C entity within the first network node sends the first data service control data to the second network node, including: The first DA-C entity within the UE sends the first data service control data to the non-access stratum (NAS) entity within the UE; The NAS entity within the UE sends the first data service control data to the Radio Resource Control (RRC) entity within the UE; and The RRC entity within the UE sends the first data service control data to the RAN via the signaling radio bearer (SRB) over the air interface.

6. The method according to any one of claims 4 to 5, wherein, The second network node communicates with the second DA-C entity within the third network node to perform the data service, including: The RAN node sends the first data service control data to the Access Mobility Function (AMF) in the CN through the N2 reference interface for communication services; The AMF in the CN sends the first data service control data to the 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 The AMF sends the second data service control data to the RAN node through the N2 reference interface for communication services.

7. The method according to any one of claims 4 to 5, wherein, The second network node communicates with the second DA-C entity within the third network node to perform data services, including: The RAN node sends the first data service control data to the AMF in the CN through the N2 reference interface for communication services; 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 The AMF sends the second data service control data to the RAN node through the N2 reference interface for communication services.

8. The method according to any one of claims 4 to 7, wherein, The second network node sends the second data service control data to the first DA-C entity, including: The RAN node sends the second data service control data to the RRC entity in the UE via the SRB on the air interface; The RRC entity sends the second data service control data to the NAS entity in the UE; and The NAS entity sends the second data service control data to the first DA-C entity within the UE.

9. The method according to claim 4, wherein, The first DA-C entity within the first network node sends the first data service control data to the second network node, including: The first DA-C entity within the UE sends the first data service control data to the RRC entity within the UE; and The RRC entity within the UE sends the first data service control data to the RAN node via the SRB on the air interface.

10. The method according to claim 9, wherein, The second network node communicates with the second DA-C entity within the third network node to perform the data service, including: 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 through a new network interface for data services; The second DA-C entity generates the second data service control data; and The second DA-C entity sends the second data service control data to the RAN node through a new network interface for data services.

11. The method according to any one of claims 9 to 10, wherein, The second network node sends the second data service control data to the first DA-C entity, including: The RAN node sends the second data service control data to the RRC entity in the UE through the SRB on the air interface; and The RRC entity sends the second data service control data to the first DA-C entity within the UE.

12. The method according to any one of claims 1 to 2, wherein: The first network node is a UE; The second network node is a RAN node; and The third network node is the same as the second network node.

13. The method according to claim 12, wherein, The first DA-C entity within the first network node sends the first data service control data to the second network node, including: The first DA-C entity within the UE sends the first data service control data to the RRC entity within the UE; and The RRC entity within the UE sends the first data service control data to the RAN node via the SRB on the air interface.

14. The method according to any one of claims 12 to 13, wherein, The second network node communicates with the second DA-C entity within the third network node to perform the data service, including: The RAN node determines the second DA-C entity to perform the data service; The 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 The second DA-C entity sends the second data service control data to the RRC entity in the RAN node.

15. The method according to any one of claims 12 to 14, wherein, The second network node sends the second data service control data to the first DA-C entity, including: The RAN node sends the second data service control data to the RRC entity in the UE via the SRB on the air interface; and The RRC entity in the UE sends the second data service control data to the first DA-C entity within the UE.

16. The method of claim 12, wherein: The 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 The second DA-C entity sends the second data service control data to the first DA-C entity within the UE over the air interface.

17. A wireless data service apparatus, the wireless data service apparatus comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 16.

18. A non-transitory computer program product comprising computer-readable program medium code stored thereon, the computer-readable program medium code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 16.

Images