WO2025166596A1

WO2025166596A1 - Methods and devices for data service management in wireless communication system

Info

Publication number: WO2025166596A1
Application number: PCT/CN2024/076479
Authority: WO
Inventors: Li Yang; Fei Wang; Wenwen SUN; Feng Xie
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2024-02-06
Filing date: 2024-02-06
Publication date: 2025-08-14
Anticipated expiration: 2026-08-06

Abstract

The present disclosure describes methods, system, and devices for new data service management in a wireless communication system. One method includes sending, by a first network node to a second network node, a first data service session configuration request, so that the second network node communicates with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity; receiving a first data service session configuration response comprising an information element container comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node; and processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel.

Description

METHODS AND DEVICES FOR DATA SERVICE MANAGEMENT IN WIRELESS COMMUNICATION SYSTEM

TECHNICAL FIELD

The present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods and devices for new data service management in a wireless communication system.

BACKGROUND

Wireless technologies are moving the world toward an increasingly connected and networked society. High-speed and low-latency wireless communication system rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations and/or core networks) . A new generation network is expected to provide various data services, in addition to conventional communication service, with high speed, low latency, and highly reliable capabilities, so as to fulfill requirements under various circumstances.

In some wireless communication system s, the various data services may include sensing service, computing service, artificial intelligence (AI) service, storage service, and/or security service. There are some issues/problems associates with these various data services. For one non-limiting example, a conventional method of protocol data unit (PDU) session management may be unable to support or handle the forward/transfer of data for various data services (i.e., data service data) efficiently.

The present disclosure describes various embodiments for new data service management in a wireless communication system, addressing at least one of the issues/problems discussed in the present disclosure, thus increasing efficiency of various data services, enabling future wireless communication system to support or handle the forward/transfer of data service data, and/or adapting to various demands of new generation wireless services in wireless communication systems.

SUMMARY

This document relates to methods, systems, and devices for wireless data service via wireless communication, and more specifically, for new data service management in a wireless communication system, which is beneficial to enhance efficient utilization of wireless resources, increase the telecommunication resource utilization efficiency, and/or boost performance of the wireless data service via wireless communication.

In one embodiment, the present disclosure describes a method for wireless data service via wireless communication. The method includes sending, by a first network node to a second network node, a first data service session configuration request, so that the second network node communicates with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity, wherein the data service session tunnel is via a communication service session tunnel between the second network node and the target communication and the DA entity; receiving, by the first network node from the second network node, a first data service session configuration response comprising an information element container (IE container) comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node, wherein the data service session channel is via a communication service session channel between the first network node and the second network node; and processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel, wherein: the first network node is a data service requesting node, the second network node is a data service anchor node or data service response node, and the third network node is a data service response node.

In another embodiment, the present disclosure describes another method for wireless data service via wireless communication. The method includes receiving, from a first network node by a second network node, a first data service session configuration request; communicating, by the second network node, with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity, wherein the data service session tunnel is via a communication service session tunnel between the second network node and the target communication and the DA entity; sending, by the second network node to the first network node, a first data service session configuration response comprising an information element container (IE container) comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node, wherein the data service session channel is via a communication service session channel between the first network node and the second network node; and processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel, wherein: the first network node is a data service requesting node, the second network node is a data service anchor node or data service response node, and the third network node is a data service response node.

In some other embodiments, an apparatus for wireless data service via wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.

In some other embodiments, a device for wireless data service via wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.

In some other embodiments, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods. The computer-readable medium may be a non-transitory computer-readable medium.

The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A shows an example of a wireless communication system.

FIG. 1B shows a schematic diagram of various embodiments in the present disclosure.

FIG. 1C shows another schematic diagram of various embodiments in the present disclosure.

FIG. 1D shows another schematic diagram of various embodiments in the present disclosure.

FIG. 2 shows an example of a network node.

FIG. 3 shows an example of a user equipment.

FIG. 4 shows a schematic diagram of various embodiments in the present disclosure.

FIG. 5 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 6 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 7A shows a flow diagram of a method for wireless data service via wireless communication.

FIG. 7B shows a flow diagram of another method for wireless data service via wireless communication.

FIG. 8 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 9 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 10 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 11 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 12 shows another schematic diagram of various embodiments in the present disclosure.

FIG. 13 shows another schematic diagram of various embodiments in the present disclosure.

DETAILED DESCRIPTION

The present disclosure will now be described in detail hereinafter with reference to the accompanied drawings, which form a part of the present disclosure, and which show, by way of illustration, specific examples of embodiments. Please note that the present disclosure may, however, be embodied in a variety of different forms and, therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the embodiments to be set forth below.

Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” or “in some embodiments” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” or “in other embodiments” as used herein does not necessarily refer to a different embodiment. The phrase “in one implementation” or “in some implementations” as used herein does not necessarily refer to the same implementation and the phrase “in another implementation” or “in other implementations” as used herein does not necessarily refer to a different implementation. It is intended, for example, that claimed subject matter includes combinations of exemplary embodiments or implementations in whole or in part.

In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and” , “or” , or “and/or, ” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” or “at least one” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a” , “an” , or “the” , again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

The present disclosure describes methods and devices for new data service management in a wireless communication system.

Wireless technologies are moving the world toward an increasingly connected and networked society. High-speed and low-latency wireless communication system rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations and/or core networks) . New generation networks are expected to provide various data services, in addition to conventional communication service, with high speed, low latency, and highly reliable capabilities, so as to fulfill requirements under various circumstances.

With the latest development of wireless communication systems and various distributed sensing, computing, intelligence, storage, and/or security systems, technically they are supposed to integrate and/or harmonize with each other in terms of system architecture/capability and network and/or air interface resource usages etc. In some implementations, a 5G-advanced (5G-A) and 6G wireless communication system s may expect to integrate and/or harmonize various sensing, computing, artificial intelligence (AI) , storage, and/or security new functions/services along with their own classical communication functions/services. The core network (CN) and/or radio access network (RAN) node may expect to be able to provide both wireless communication service and wireless sensing, computing, AI, storage, and/or security new services.

In some implementations, a conventional method of protocol data unit (PDU) session management in legacy 5G wireless communication system may be mainly targeted for forwarding/transferring user plane (UP) data, which is normally associated with external mobile users’ services, such as mobile application (APP) and web services. Those UP data is normally generated outside 5G wireless communication system (transparent/invisible to 3GPP protocols) , and it is either originated/terminated at a user equipment (UE) or a data network server. The 5G CN and/or RAN nodes may need not to concern about the UP data type/content or characteristics of user data, and simply process and forward them from the input port to output port based on internal UP processing unit and protocols.

In some implementations, there may be some issues/problems associated with handling various data of new service types. For example, in 5G-A and 6G wireless communication systems, various data of new service types (such as sensing, computing, AI, storage, and/or security new services) with different characteristics may be generated, processed and transferred inside wireless communication system (visible/usable to 3GPP protocols) , and any CN and/or RAN node or UE may also be allowed to originate so call “data service session” on local demand and/or terminate the “data service session” at any other CN and/or RAN node or UE, and the intermediate/relay network (NW) node along the “data service session path” may also need to concern about the type/content/characteristics of the data service data. Thus, the conventional method of PDU session management in wireless communication system may not be able to support or handle the forward/transfer of data for various data services (i.e., data service data) efficiently.

The present disclosure describes various designs, models, and/or methods for new data service management in wireless communication systems for data service data, enabling future wireless communication system to support or handle the forward/transfer of data service data, and/or adapting to various demands of various new services.

FIG. 1A shows a wireless communication system 100 including a core network (CN) 110, a radio access network (RAN) 130, and one or more user equipments (UEs) (152, 154, and 156) . The RAN 130 may include one or more base stations. The base stations may include at least one evolved NodeB (eNB) for 4G Long Term Evolution (LTE) , or a Next generation NodeB (gNB) for 5G New Radio (NR) , or a NodeB for 6G, or any other type of signal transmitting/receiving device such as a UMTS NodeB. In one implementation, the core network 110 may include a 5G core network (5GC) , and the interface 125 may include a new generation (NG) interface. The core network 110 further includes at least one policy control function (PCF) , and/or at least one session management function (SMF) , and/or at least one user plane function (UPF) and/or at least one access and mobility management Function (AMF) .

Referring to FIG. 1A, a first UE 152 may receive one or more downlink communication 142 from the RAN 130 and send one or more uplink communication 141 to the RAN 130. Likewise, a second UE 154 may receive downlink communication 144 from the RAN 130 and send uplink communication 143 to the RAN 130; and a third UE 156 may receive downlink communication 146 from the RAN 130 and send uplink communication 145 to the RAN 130. For example but not limited to, a downlink communication may include a physical downlink (DL) shared channel (PDSCH) or a physical downlink control channel (PDCCH) , and a uplink (UL) communication may include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) .

In some implementations, the core network (CN) may include one or more core network functions related to the QoS information, as shown in FIG. 1B, which are described below. The core network may communicate with a UE 171 (or via a RAN 172) . The UPF 173 may perform the functionalities including but not limited to serving as an anchor point for intra-/inter-radio access technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, quality of service (QoS) handling for the user plane, downlink packet buffering and downlink data notification triggering. The AMF 16 may perform the functionalities including but not limited to registration management, connection management of, reachability management and mobility management of UE 171. AMF also performs access authentication and access authorization. The AMF 176 may have function as non-access stratum (NAS) security termination and relay the session management NAS messages between the UE 171 and SMF 177. The AMF 176 also performs SMF selection function during communication session establishment procedure and UE mobility procedure. The AMF may forward the QoS profile from the SMF to the RAN (or AN) , and forwards the QoS rule from the SMF to the UE. The SMF 177 may perform the functionalities including but not limited to establishment, modification, and release of communication sessions, UE IP address allocation and management (including optional authorization functions) , selection and control of UPF 173, and downlink data notification. Each SMF may control one or more UPFs and is associated with a service area being a collection of UPF service areas of all UPFs under its control. The SMF derives the QoS profile according to the PCC rule, generates a QoS flow, sends the QoS profile to the RAN, and sends the packet detection rule (PDR) to the UPF. The PCC rule is bound to the QoS flow. In some implementations, the SMF also selects the UPF based on the granularity of the UE or session, and can assign IP addresses, collect charging data, connect to the charging center, and so on. The PCF 179 is responsible for a unified policy framework, provides policy rules for control plane functions, determines policy control and charging (PCC) rules, and authorizes a session management function (SMF) on service data flow (SDF) basis. The PCF performs the functionalities including but not limited providing policy rules and controlling other network nodes to enforce the policy rules. Specifically, the PCF provides access and mobility related policies to the AMF 176 so that the AMF enforces them during mobility procedure.

In some implementations, in a typical international mobile telecommunication (IMT) wireless communication systems (e.g., 5G-NR specified by 3GPP) , a core network (CN) may include various types of control plane (CP) nodes or entities, e.g. 5G AMF/SMF, and user plane (UP) node or entity, e.g. 5G UPF. Referring to FIG. 1C in the RAN non-split case, the RAN node, e.g. 5G aggregated gNB consists of CP part and UP part together, and then terminates on UE via radio link (RL) in the air including signaling radio bearer (SRB) and/or data radio bearer (DRB) . Referring to FIG. 1D in the RAN split case, the RAN node, e.g. 5G dis-aggregated gNB including centralized unit control plan (CU-CP) node, CU-UP node and distributed unit (DU) node or entities, and then terminates on UE via RL in the air. The CP part or node is responsible for generating, processing and transferring control signaling, e.g. for (re) configuring and monitoring nodes; The UP part or node is responsible for processing and transferring user UP data, e.g. normally associated with mobile APP and Web services etc outside. For both CP and UP plane, they have their own interface and/or protocol stack and normally span from CN domain to RAN network and then to UE.

FIG. 2 shows an example of electronic device 200 to implement one or more core network functions, one or more network nodes, or one or more base stations. The example electronic device 200 may include radio transmitting/receiving (Tx/Rx) circuitry 208 to transmit/receive communication with UEs and/or other base stations. The electronic device 200 may also include network interface circuitry 209 to communicate the base station with other base stations and/or a core network, e.g., optical or wireline interconnects, Ethernet, and/or other data transmission mediums/protocols. The electronic device 200 may optionally include an input/output (I/O) interface 206 to communicate with an operator or the like.

The electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor (s) 221 and/or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for the one or more of the processors 124 to perform the functions of the network node. The parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.

FIG. 3 shows an example of an electronic device to implement a terminal device 300 (for example, user equipment (UE) ) . The UE 300 may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle. The UE 300 may include communication interfaces 302, a system circuitry 304, an input/output interfaces (I/O) 306, a display circuitry 308, and a storage 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic/circuitry. The system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry. The system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300. In that regard, the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the inputs/output (I/O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements. Additional examples of the I/O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input /output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.

Referring to FIG. 3, the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers that include modulation /demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings. As one specific example, the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G /Long Term Evolution (LTE) , 5G standards, and/or 6G or any future standards. The techniques described below, however, are applicable to other wireless communications technologies whether arising from the 3rd Generation Partnership Project (3GPP) , GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

Referring to FIG. 3, the system circuitry 304 may include one or more processors 321 and memories 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to carry out desired functionality for the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that the UE 300 may send, or has received, through the communication interfaces 302. In various implementations, a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.

FIG. 4 shows a conventional mechanism for PDU session management in a wireless communication system (e.g., 5G) . The AMF entity 430 in 5GC is the anchor controlling point of PDU session for particular served UE 410. The AMF triggers the control signaling procedures for establishing or modifying the PDU session across different NW nodes (including the SMF 440) . Upon configuration of the UP resources for UP data transfer in the UPF 450, the gNB 420, and the UE respectively, the outside UP data associated to served the UE may be transferred via the “tunnels or DRBs” across different NW nodes. During the UP data transfer, the UP resources, e.g. “tunnels or DRBs” may be reconfigured on demand.

There may be some issues/problems associated with a PDU session management. For example, with above PDU session management in current 5G wireless communication systems, the PDU Session mechanism may only serve the wireless communication service efficiently, i.e. transfer the outside UP data associated to a served UE, but it may not serve efficiently or flexibly the data forward/transfer of other new service types, such as sensing, computing, artificial intelligence (AI) , storage, and/or security services. For another example, the AMF in 5GC is the unique entity that is allowed to trigger the control signaling procedures for establishing or modifying the PDU session; and other network function (NF) in 5GC or gNB or UE may not trigger the management of PDU session. For another example, the served UE must be involved with particular PDU session, as the PDU Session is normally used to transfer the outside UP data associated to served UE. For another example, the PDU session path may not support flexible data transfer topology, i.e. it is always from the UPF to gNB then to UE or vice versa. It may not be established between any two NW nodes.

In various embodiments may include new mechanism for data service session management. FIG. 5 shows a new mechanism for data service session management in future wireless communication system. For any type of network node (NF in CN, RAN, or UE) , it may play the role of source node, intermediate/relay node or target node for particular data service session, and the network node includes two basic new logic functions: data agent-control part (DA Control or DA-C) and data agent-execution part (DA Execution or DA-E) . A “DA Control” entity is responsible for configuring/coordinating/monitoring data service session across different NW nodes. A “DA Execution” entity is responsible for processing the data of data service session, i.e. data service data. Hence, for a particular data service session across multiple network nodes, the “DA Control” entities in each NW node shall firstly establish the E2E virtual control plane of data service session, then the “DA Execution” entities in each NW node shall establish the E2E virtual execution plane of data service session. The control plane data (for configuring DA-E resources) of data service session shall be coupled, shared, and/or associated and carried via the CP signaling procedure with communication service, and the execution plane data of data service session shall be carried via data service session tunnel (s) and data service session RB (s) , which are (re) -configured by control plane data of data service session.

In various embodiments in the present disclosure, a communication service refers to a UE and/or a mobile user APP layer data transfer service provided by wireless communication system, i.e. the communication service data is normally generated outside the wireless system; a data service refers to new type of services beyond legacy communication service provided by wireless system, e.g. sensing, computing, Intelligence, storage, and/or security new services and their corresponding data service data is generated inside the wireless system, e.g. by UE AS layer, RAN node and NF in CN; a data service session refers to a data session for data service between the source node and target node, and it may also span multiple intermediate/relay nodes; a data service data refers to the data associated to particular data service session, i.e. different from communication service data; a data service session Radio Bearer” : the radio bearer carrying/transferring Data Service Data over the air interface; a data service session tunnel refers to the data tunnel carrying/transferring Data Service Data over the wirelined interface; a data service anchor node refers to the central controlling/coordinating node or entity for controlling the data service session, such as AMF, NWDAF, gNB, xNB etc depending on usage scenario; a data agent (DA) : new logical node or functional entity supporting data services and Data Service Session inside wireless system; a DA Control (DA-C) refers to a control part of DA for controlling/coordinating the Data Service Session; a DA Execution (DA-E) refers to an execution part of DA for executing/processing the Data Service Session; a DA-E processing resources refers to executing resources (such as CPU, GPU, DPU, NPU, TPU, DSP, Storage etc) for various processing Data Service Data inside DA Execution entity; a DA-E transferring resources refers to executing resources (such as data transfer tunnels, radio bearers etc. ) for transferring Data Service Data between DA Execution entities; a COMM-C refers to a control part of NW node for controlling the Communication PDU Session, such as gNB-CU-CP, SMF etc.; a COMM-E (or COMM-U) refers to an execution part of NW node for executing the Communication PDU Session (i.e., transferring UP data) , such as gNB-CU-UP, UPF etc.

FIG. 6 shows an exemplary architecture for data service session management in various embodiments. Each network node (e.g., a source node 620, an intermediate/relay node 630, and/or a target node 610) or entity includes two new logic functional entities: “DA Control” and “DA Execution” entities. The “DA Control” entity is responsible for controlling, configuring, coordinating, and/or monitoring the Data Service Session across different NW nodes or entities. The “DA Execution” entity is responsible for various data processing and/or transferring of Data Service Session, i.e. handling the Data Service data. The interface protocol stack between “DA Control” entities is coupled/shared/associated with the interface protocol stack between “COMM-C” entities; the interface protocol stack between “DA Execution” entities is coupled/shared/associated with the interface protocol stack between “COMM-E” entities; and/or the interface protocol stack between “DA Control” entity and “DA Execution” entity is coupled/shared/associated with the interface protocol stack between “COMM-C” and “COMM-E” entities.

In various embodiments, for particular Data Service Session across multiple network nodes or entities, “DA Control” entities in each involved NW node or entities shall firstly establish the virtual “E2E control plane of Data Service Session” (in dotted line in FIG. 6) , then “DA Execution” entities in each involved NW node or entities shall establish the virtual “E2E execution plane of Data Service Session” (in dotted line in FIG. 6) . The “control plane of Data Service Session” generates and transfers the control data for Data Service Session via CP signaling procedures with communication service across multiple NW nodes or entities. The “execution plane of Data Service Session” processes and transfers the Data Service data across multiple NW nodes or entities.

In various embodiments, for particular Data Service Session across multiple network nodes or entities, the “DA Control” in the source node determines the “Data Service Session Path” on demand, i.e. which are the intermediate/relay nodes and target nodes or entities. The “DA Control” in each involved NW node or entities determines the DA-E processing resources (such as CPU, GPU, DPU, NPU, TPU, DSP, Storage, Buffer etc. ) inside their associated “DA Execution” entities. The “DA Control” in each involved NW node or entities determines the DA-E transferring resources (such as data transfer tunnels, radio bearers etc. ) between their associated “DA Execution” entities.

In various embodiments, the Data Service Session’s control plane data transfer is coupled /shared /associated with the CP signaling procedure with communication service, e.g. in the form of “IE container” , and the Data Service Session’s execution plane data transfer is carried via Data Service Session tunnel (s) and Data Service Session RB (s) , which are (re) -configured by control plane data of Data Service Session from DA-C entity. The execution plane data of Data Service Session may be transferred by dedicated new Data Service Session tunnel (s) and RB (s) with data service, i.e. different from those tunnels or DRBs with communication service. The execution plane data of Data Service Session may also be transferred by legacy UP tunnel (s) and DRB(s) with communication service.

The present disclosure describes various embodiments for new data service management in a wireless communication system, which may be implemented, partly or totally, by the core network function, network base station, and/or the user equipment described above in FIGS. 2 to 3. The various embodiments in the present disclosure may increase efficiency of various data services, enable future wireless system to support or handle the forward/transfer of data service data, and/or adapt to various demands of new generation wireless services. In various embodiments, in order to support new service types in wireless systems (e.g., future and/or 6G systems) , such as sensing, computing, intelligence, storage, and/or security services, a new controlling mechanism is applicable to any type of network node or entity (e.g. NF in CN, RAN node or UE) for particular Data Service Session management (e.g. establishment, modification and release etc. ) , and the involved network node or entity includes two basic new logic functions: “DA Control” (DA-C) and “DA Execution” (DA-E) . The DA-C entity is responsible for control plane handling (such as control, establishment, modification, and/or release of DA-E processing and/or transferring resources and Data Service Session tunnels and/or RBs) of particular Data Service Session between any type of network node or entity. The DA-E entity is responsible for execution plane handling (such as processing, forwarding, transferring of Data Service data) of particular Data Service Session between any type of network node or entity. In some implementations, the operation of a DA-E relies on triggering and configurations from a DA-C.

Referring to FIG. 7A, the present disclosure describes various embodiments of a method 700 for wireless data service via wireless communication. The method 700 may include a portion or all of the following: step 710, sending, by a first network node to a second network node, a first data service session configuration request, so that the second network node communicates with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity, wherein the data service session tunnel is via a communication service session tunnel between the second network node and the target communication and the DA entity; step 720, receiving, by the first network node from the second network node, a first data service session configuration response comprising an information element container (IE container) comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node, wherein the data service session channel is via a communication service session channel between the first network node and the second network node; and/or step 730, processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel. The first network node is a data service requesting node, the second network node is a data service anchor node or data service response node, and/or the third network node is a data service response node.

Referring to FIG. 7B, the present disclosure describes various embodiments of a method 750 for wireless data service via wireless communication. The method 750 may include a portion or all of the following steps: step 760, receiving, from a first network node by a second network node, a first data service session configuration request; step 770, communicating, by the second network node, with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity, wherein the data service session tunnel is via a communication service session tunnel between the second network node and the target communication and the DA entity; step 780, sending, by the second network node to the first network node, a first data service session configuration response comprising an information element container (IE container) comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node, wherein the data service session channel is via a communication service session channel between the first network node and the second network node; and/or step 790, processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel. The first network node is a data service requesting node, the second network node is a data service anchor node or data service response node, and/or the third network node is a data service response node.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the first network node is a user equipment (UE) comprising a UE communication entity and a UE DA entity; the second network node is a radio access network (RAN) node comprising a RAN communication entity and a RAN DA entity; and/or the third network node comprises the target communication entity and the target DA entity.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the first network node comprises a RAN node comprising a RAN communication entity and a RAN DA entity; the second network node comprises a core network entity comprising a data access and mobility management function (Data-AMF) comprising a AMF communication entity and a AMF DA entity; and/or the third network node comprises the target communication entity and the target DA entity.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, that the first network node sends the first data service session configuration request to the second network node comprises: a DA of the first network node determines to offer or obtain the desired data service data; the DA of the first network node constructs the first data service session configuration request for offering or obtaining the desired data service data, the first data service session configuration request may comprise an IE container comprising data service configuration signaling for the receiving node’s reference; the DA of the first network node transmits the first data service session configuration request to the communication entity of the first network node via an internal interface; the communication entity of the first network node sends the first data service session configuration request to a communication entity of the second network node via a communication service session channel; and/or the communication entity of the second network node transmits the received first data service session configuration request to a DA of the second network node via an internal interface.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, that the second network node communicates with the third network node for configuring the data service session tunnel between the second network node and the target DA entity comprises: the second network node selects the third network node comprising the target communication entity and the target DA entity; the DA of the second network node sends a second data service session configuration request to the communication entity of the second network node via an internal interface, the second data service session configuration request may comprise an IE container comprising data service configuration signaling for the receiving node’s reference; the communication entity of the second network node sends the second data service session configuration request to a control part of the target communication entity (target COMM-C) via a communication service session channel; the target COMM-C transmits the second data service session configuration request to a control part of the target DA (target DA-C) via an internal interface; the target DA-C configures an execution part of the target DA (target DA-E) for processing and transferring the desired data service data; the target DA-C constructs a second data service session configuration response for establishing the data service session tunnel between the DA entity of the second network node and the target DA-E, the second data service session configuration response comprising an IE container comprising data service configuration signaling; and/or the third network node transmits the second data service session configuration response to the second network node via a communication service session channel.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the first network node comprises the UE and the second network node comprises the RAN node; the data service session channel between the UE and the RAN node comprises a data service session radio bearer; and/or the communication service session channel between the UE and the RAN node comprises a communication service radio bearer.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the processing and transferring, between the first network node and the target DA entity, the data service data via the communication service session channel comprises: receiving, by the first network node, the desired data service data from the DA-E via the data service session radio bearer and data service session tunnel associated to communication service, or sending, by the first network node, the desired data service data to the DA-E via the data service session radio bearer and data service session tunnel associated to communication service.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the first network node comprises the RAN node and the second network node comprises the Data-AMF; and/or the data service session channel between the RAN node and the Data-AMF comprises a data service session tunnel associated to communication service.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the processing and transferring, between the first network node and the target DA entity, the data service data via the data service session channel comprises: receiving, by the first network node, the desired data service data from the DA-E via at least one data service session tunnel associated to communication service, or sending, by the first network node, the desired data service data to the DA-E via at least one data service session tunnel associated to communication service.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the data service data comprises artificial intelligence (AI) model data; and/or the target DA-E contains an AI model to provide the AI model data.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the data service data comprises AI model updating data; and/or that the target DA-C configures the target DA-E for processing and transferring the data service data comprises: the target DA-C configures the target DA-E for AI model retraining to provide the AI model updating data; and/or the target DA-C configures the target DA-E to transfer the AI model updating data.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, that the first network node sends the first data service session configuration request to the second network node comprises: a DA of the first network node determines to send the desired data service data; the DA of the first network node constructs the first data service session configuration request for sending the desired data service data, the first data service session configuration request may comprise an IE container comprising data service configuration signaling for the receiving node’s reference; the DA of the first network node transmits the first data service session configuration request to the communication entity of the first network node via an internal interface; the communication entity of the first network node sends the first data service session configuration request to a communication entity of the second network node via a communication service session channel; and/or the communication entity of the second network node transmits the received first data service session configuration request to a DA entity of the second network node via an internal interface.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, that the second network node communicates with the third network node for configuring the data service session tunnel between the second network node and the target DA entity comprises: the second network node selects the third network node comprising the target communication entity and the target DA entity; the DA of the second network node sends a second data service session configuration request to the communication entity of the second network node via an internal interface, the second data service session configuration request may comprise an IE container comprising data service configuration signaling for the receiving node’s reference; the communication entity of the second network node sends the second data service session configuration request to a control part of the target communication entity (target COMM-C) via a communication service session channel; the target COMM-C transmits the second data service session configuration request to a control part of the target DA (target DA-C) via an internal interface; the target DA-C configures an execution part of the target DA (target DA-E) for processing and receiving the desired data service data; the target DA-C constructs a second data service session configuration response for establishing the data service session tunnel between the DA entity of the second network node and the target DA-E, the second data service session configuration response comprising an IE container comprising data service configuration signaling; and/or the third network node transmits the second data service session configuration response to the second network node via a communication service session channel.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the processing and transferring, between the first network node and the target DA entity, the data service data via the communication service session channel comprises: sending, by the first network node, the desired data service data to the DA-E via the data service session radio bearer and data service session tunnel associated to communication service; or receiving, by the first network node, the desired data service data from the DA-E via the data service session radio bearer and data service session tunnel associated to communication service.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the first network node comprises the RAN node and the second network node comprises the Data-AMF; and/or the data service session channel between the RAN node and the Data-AMF comprises a second data service session tunnel associated to communication service.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the processing and transferring, between the first network node and the target DA entity, the data service data via the data service session channel comprises: sending, by the first network node, the desired data service data to the DA-E via at least one data service session tunnel associated to communication service; or receiving, by the first network node, the desired data service data from the DA-E via at least one data service session tunnel associated to communication service.

In some implementations, in addition to a portion, an entire, or any combination of other implementation (s) /embodiment (s) described in the present disclosure, the data service data comprises sensed data; and/or the DA-E is capable of processing and storing the sensed data.

The present disclosure describes various exemplary embodiments for new data service management in a wireless communication system, and the exemplary embodiments merely serve as examples and do not pose limitations. Any steps and/or operations in one same embodiment/implementation or more than one different embodiments/implementation in the present disclosure may be combined or arranged in any amount or order, as desired. Two or more of the steps and/or operations may be performed in parallel. Embodiments and implementations in the disclosure may be used separately or combined in any order. Further, each of the methods (or embodiments) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits) .

Embodiment Set I

The present disclosure describes various embodiments for a UE triggered AI model data fetching from a DA.

In some implementations, a DA-C is a new logic network entity, and it is responsible for configuring, controlling, coordinating, and/or monitoring the Data Service Session across different NW nodes or entities. A COMM-C is the control part of NW node for controlling and/or coordinating the Communication PDU Session, and furthermore, it may send the Data Service’s configuration signaling generated by the DA-C in the form of an “IE container. ” The “IE container” is a container including the IE inside the container, wherein the IE inside the “IE container” may be transparent to an intermediate network node, function, or entity. In various embodiments, the DA-C and the COMM-C may be deployed together, e.g. in a same NW node.

In some implementations, a DA-E is a new logic network entity providing the Data Service Data handling (e.g. data collection, sensed data processing, AI model training, and/or AI model transferring) . The COMM-U is the execution part of NW node for transferring the Communication PDU Session data. In various embodiments, the DA-E and the COMM-U may be deployed together, e.g. in the same NW node.

Various embodiments may be applied in the below exemplary scenario. A data service requesting node is a user equipment (UE) which lacks of computing and storage resources. The UE reported the AI training data to DA-E ahead, and the DA-E collects the data for AI model training so then obtained the well-trained AI model later on. When the source UE requests the AI model data from the target DA-E, it will send the Data Service request to the associated COMM-C/DA-C entity via Data Service Anchor Node, e.g. xNB.

FIG. 8 shows an exemplary process of various embodiments, which include a portion or all of the following: a UE 891, a Data service anchor node (e.g., xNB (DA-C/DA-E) ) 892, a COMM-U/DA-E 893, and a COMM-C/DA-C 894. The exemplary process may include a portion or all of the following steps.

For step 810, the UE generates the Data Service Session Configuration Request message according to its own AI requirement, and sends it to the Data Service Anchor Node (e.g. xNB) for acquiring the desired AI model data in the target DA.

For step 820, the xNB makes the target COMM-C/DA-C selection, and forwards the Data Service Session configuration Request to the target COMM-C/DA-C entity, which contains the AI model that the requesting UE needs.

For step 830, the COMM-C notifies the associated DA-C to generate the configuration signaling of DA-E transferring resource, and then prepares the Data Service Session tunnels for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 840, the xNB notifies the associated DA-C to generate the configuration signaling of the xNB resources, and then prepares the Data Service Session Radio Bearer for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response to the UE. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 850, the COMM-U/DA-E entity starts transferring the AI model data to the UE, e.g. via legacy UP GTP-U tunnels and/or DRBs.

Embodiment Set II

The present disclosure describes various embodiments for a xNB triggered AI model data fetching from a DA. Various embodiments may be applied in the below exemplary scenario. similar to Embodiment Set I, now the Data Service requesting Node is xNB, and the Data Service Anchor Node is a new CN entity, i.e. Data-AMF. When the source xNB requests the AI model data from the target DA-E, it will send the Data Service request to the associated DA-C entity via Data Service Anchor Node, e.g. Data-AMF.

FIG. 9 shows an exemplary process of various embodiments, which include a portion or all of the following: a xNB 991, a Data-AMF 992, a COMM-U/DA-E 993, and a COMM-C/DA-C 994. The exemplary process may include a portion or all of the following steps.

For step 910, the xNB generates the Data Service Session Configuration Request message according to its own AI requirement, and sends it to the Data-AMF for acquiring the desired AI model data in the target DA.

For step 920, the Data Service Anchor Node makes the target COMM-C/DA-C selection, and forwards the Data Service Session configuration Request to the target COMM-C/DA-C entity, which contains the AI model that the requesting UE needs.

For step 930, the COMM-C notifies the associated DA-C to generate the configuration signaling of DA-E transferring resource, and then prepares the Data Service Session tunnels for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 940, the Data-AMF prepares (configuring the xNB resources) the Data Service Session tunnel for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response to the xNB.

For step 950, the COMM-U/DA-E entity starts transferring the AI model data to the xNB, e.g. via legacy UP GTP-U tunnels.

Embodiment Set III

The present disclosure describes various embodiments for a UE triggered AI updating from a DA. Various embodiments may be applied in the below exemplary scenario. Local data can be stored in UEs and local AI training can be conducted by UEs. The holistic AI model update can be aggregated and updated by a centralized network entity such as DA-E. The UE may send its own trained AI model to DA-E ahead, and the DA-E collects the AI models for further retraining, so then obtained the updated AI model later on. When the source UE wants to send its own trained AI model and requests the updated AI model data from the target DA-E, it will send the Data Service request to the associated DA-C entity via Data Service Anchor Node, e.g., xNB.

FIG. 10 shows an exemplary process of various embodiments, which include a portion or all of the following: a UE 1091, a Data service anchor node (e.g., xNB (DA-C/DA-E) ) 1092, a COMM-U/DA-E 1093, and a COMM-C/DA-C 1094. The exemplary process may include a portion or all of the following steps.

For step 1010, the UE performs the AI model training based on its local data, then UE generates the Data Service Session Configuration Request message according to its own AI requirement, and sends it to the Data Service Anchor Node (e.g. xNB) for transferring the model update request to the target DA.

For step 1020, the xNB makes the target COMM-C/DA-C selection, and forwards the Data Service Session configuration Request to the target COMM-C/DA-C entity, which is suitable for AI model retraining.

For step 1030, the COMM-C notifies the associated DA-C to generate the configuration signaling of DA-E transferring resource, and then prepares the Data Service Session tunnels for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 1040, the xNB notifies the associated DA-C to generate the configuration signaling of the xNB resources, and then prepares the Data Service Session Radio Bearer for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response to the UE. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 1050, the COMM-U/DA-E entity starts transferring the AI model data to the UE, e.g. via legacy UP GTP-U tunnels and DRBs.

Embodiment Set IV

The present disclosure describes various embodiments for a xNB triggered AI model updating from a DA. Various embodiments may be applied in the below exemplary scenario. Similar to Embodiment Set III, now the Data Service requesting Node is xNB, and the Data Service Anchor Node is a new CN entity, i.e. Data-AMF. When the source xNB wants to send its own trained AI model and requests the updated AI model data from the target DA-E, it will send the Data Service request to the associated DA-C entity via Data Service Anchor Node, e.g. Data-AMF.

FIG. 11 shows an exemplary process of various embodiments, which include a portion or all of the following: a xNB 1191, a Data-AMF 1192, a COMM-U/DA-E 1193, and a COMM-C/DA-C 1194. The exemplary process may include a portion or all of the following steps.

For step 1110, the xNB generates the Data Service Session Configuration Request message according to its own AI requirement, and sends it to the Data-AMF for acquiring the desired AI model data in the target DA.

For step 1120, the Data Service Anchor Node makes the target COMM-C/DA-C selection, and forwards the Data Service Session configuration Request to the target COMM-C/DA-C entity, which is suitable for AI model retraining.

For step 1130, the COMM-C notifies the associated DA-C to generate the configuration signaling of DA-E transferring resource, and then prepares the Data Service Session tunnels for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 1140, the Data-AMF prepares (configuring the xNB resources) the Data Service Session tunnel for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response to the xNB.

For step 1150, the COMM-U/DA-E entity starts transferring the AI model data to the xNB, e.g. via legacy UP GTP-U tunnels.

Embodiment Set V

The present disclosure describes various embodiments for a UE triggered sensed data transferring to a DA. Various embodiments may be applied in the below exemplary scenario. The Data Service requesting Node is a user equipment (UE) which obtained a large amount of sensed data, and the DA-E is a network entity providing the data services (e.g. data collection, sensed data processing, AI model training, and/or AI model transfer) . The UE may report the sensed data to DA-E, and the DA-E collects and processes the sensed data. When the source UE wants to send the sensed data to the target DA-E, it will send the Data Service request to the associated DA-C entity via Data Service Anchor Node, e.g. xNB.

FIG. 12 shows an exemplary process of various embodiments, which include a portion or all of the following: a UE 1291, a Data service anchor node (e.g., xNB (DA-C/DA-E) ) 1292, a COMM-U/DA-E 1293, and a COMM-C/DA-C 1294. The exemplary process may include a portion or all of the following steps.

For step 1210, the UE performs the AI model training based on its local data, then UE generates the Data Service Session Configuration Request message according to its own sensing service requirement, and sends it to the Data Service Anchor Node (e.g. xNB) for transferring its sensed data.

For step 1220, the xNB makes the target COMM-C/DA-C selection, and forwards the Data Service Session configuration Request to the target COMM-C/DA-C entity, which is suitable for processing and storing the sensed data.

For step 1230, the COMM-C notifies the associated DA-C to generate the configuration signaling of DA-E transferring resource, and then prepares the Data Service Session tunnels for Data Service data (sensed data) transfer, and generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 1240, the xNB notifies the associated DA-C to generate the configuration signaling of the xNB resources, and then prepares the Data Service Session Radio Bearer for Data Service data (sensed data) transfer, and generates the Data Service Session configuration Response to the UE. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 1250, the COMM-U/DA-E entity starts transferring the AI model data to the UE, e.g. via legacy UP GTP-U tunnels and DRBs.

Embodiment Set VI

The present disclosure describes various embodiments for a xNB triggered AI model updating from a DA. Various embodiments may be applied in the below exemplary scenario. Similar to Embodiment Set III, now the Data Service requesting Node is xNB, and the Data Service Anchor Node is a new CN entity, i.e. Data-AMF. When the source xNB wants to send the sensed data to the target DA-E, it will send the Data Service request to the associated DA-C entity via Data Service Anchor Node, e.g. Data-AMF.

FIG. 13 shows an exemplary process of various embodiments, which include a portion or all of the following: a xNB 1391, a Data-AMF 1392, a COMM-U/DA-E 1393, and a COMM-C/DA-C 1394. The exemplary process may include a portion or all of the following steps.

For step 1310, the xNB generates the Data Service Session Configuration Request message according to its own sensing service requirement, and sends it to the Data-AMF for transferring the its sensed data in the target DA.

For step 1320, the Data Service Anchor Node makes the target COMM-C/DA-C selection, and forwards the Data Service Session configuration Request to the target COMM-C/DA-C entity, which is suitable for processing and storing the sensed data.

For step 1330, the COMM-C notifies the associated DA-C to generate the configuration signaling of DA-E transferring resource, and then prepares the Data Service Session tunnels for Data Service data (sensed data) transfer, and generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel. The Data Service’s configuration signaling, as in the form of “IE container” is carried in the Data Service Session configuration Response message.

For step 1340, the Data-AMF prepares (configuring the xNB resources) the Data Service Session tunnel for Data Service data (sensed data) transfer, and generates the Data Service Session configuration Response to the xNB.

For step 1350, the COMM-U/DA-E entity starts transferring the AI model data to the xNB, e.g. via legacy UP GTP-U tunnels.

The present disclosure describes methods, apparatus, and computer-readable medium for wireless data service. The present disclosure addressed the issues with new data service management in a wireless communication system. The methods, devices, and computer-readable medium described in the present disclosure may facilitate the performance of wireless data service, thus improving efficiency and overall performance. The methods, devices, and computer-readable medium described in the present disclosure may improves the overall efficiency of the wireless communication systems.

In some other embodiments, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods. The computer-readable medium may be referred as non-transitory computer-readable media (CRM) that stores data for extended periods such as a flash drive or compact disk (CD) , or for short periods in the presence of power such as a memory device or random access memory (RAM) . In some embodiments, computer-readable instructions may be included in a software, which is embodied in one or more tangible, non-transitory, computer-readable media. Such non-transitory computer-readable media can be media associated with user-accessible mass storage as well as certain short-duration storage that are of non-transitory nature, such as internal mass storage or ROM. The software implementing various embodiments of the present disclosure can be stored in such devices and executed by a processor (or processing circuitry) . A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the processor (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM and modifying such data structures according to the processes defined by the software.

Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.

Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments, for non-limiting examples, a portion from one or more embodiment may be combined with another portion of other embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution can be practiced without one or more of the 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 the present solution.

Claims

A method for wireless data service via wireless communication, comprising:

sending, by a first network node to a second network node, a first data service session configuration request, so that the second network node communicates with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity, wherein the data service session tunnel is via a communication service session tunnel between the second network node and the target communication and the DA entity;

receiving, by the first network node from the second network node, a first data service session configuration response comprising an information element container (IE container) comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node, wherein the data service session channel is via a communication service session channel between the first network node and the second network node; and

processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel,

wherein:

the first network node is a data service requesting node,

the second network node is a data service anchor node or data service response node, and

the third network node is a data service response node.
A method for wireless data service via wireless communication, comprising:

receiving, from a first network node by a second network node, a first data service session configuration request;

communicating, by the second network node, with its internal data agent (DA) or a third network node comprising a target communication entity and a target DA entity for configuring a data service session tunnel between the second network node and the target DA entity, wherein the data service session tunnel is via a communication service session tunnel between the second network node and the target communication and the DA entity;

sending, by the second network node to the first network node, a first data service session configuration response comprising an information element container (IE container) comprising data service configuration signaling for establishing a data service session channel between the first network node and the second network node, wherein the data service session channel is via a communication service session channel between the first network node and the second network node; and

processing and transferring, between the first network node and the target communication and the DA entity, data service data via at least one communication service session channel,

wherein:

the first network node is a data service requesting node,

the second network node is a data service anchor node or data service response node, and

the third network node is a data service response node.
The method according to any of claims 1 to 2, wherein:

the first network node is a user equipment (UE) comprising a UE communication entity and a UE DA entity;

the second network node is a radio access network (RAN) node comprising a RAN communication entity and a RAN DA entity; and

the third network node comprises the target communication entity and the target DA entity.
The method according to any of claims 1 to 2, wherein:

the first network node comprises a RAN node comprising a RAN communication entity and a RAN DA entity;

the second network node comprises a core network entity comprising a data access and mobility management function (Data-AMF) comprising a AMF communication entity and a AMF DA entity; and

the third network node comprises the target communication entity and the target DA entity.
The method according to any of claims 3 to 4, wherein, that the first network node sends the first data service session configuration request to the second network node comprises:

a DA of the first network node determines to offer or obtain the desired data service data;

the DA of the first network node constructs the first data service session configuration request for offering or obtaining the desired data service data, the first data service session configuration request comprises an IE container comprising data service configuration signaling for the receiving node’s reference;

the DA of the first network node transmits the first data service session configuration request to the communication entity of the first network node via an internal interface;

the communication entity of the first network node sends the first data service session configuration request to a communication entity of the second network node via a communication service session channel; and

the communication entity of the second network node transmits the received first data service session configuration request to a DA of the second network node via an internal interface.
The method according to claim 5, wherein, that the second network node communicates with the third network node for configuring the data service session tunnel between the second network node and the target DA entity comprises:

the second network node selects the third network node comprising the target communication entity and the target DA entity;

the DA of the second network node sends a second data service session configuration request to the communication entity of the second network node via an internal interface, the second data service session configuration request comprises an IE container comprising data service configuration signaling for the receiving node’s reference;

the communication entity of the second network node sends the second data service session configuration request to a control part of the target communication entity (target COMM-C) via a communication service session channel;

the target COMM-C transmits the second data service session configuration request to a control part of the target DA (target DA-C) via an internal interface;

the target DA-C configures an execution part of the target DA (target DA-E) for processing and transferring the desired data service data;

the target DA-C constructs a second data service session configuration response for establishing the data service session tunnel between the DA entity of the second network node and the target DA-E, the second data service session configuration response comprising an IE container comprising data service configuration signaling; and

the third network node transmits the second data service session configuration response to the second network node via a communication service session channel.
The method according to any of claims 5 to 6, wherein:

the first network node comprises the UE and the second network node comprises the RAN node;

the data service session channel between the UE and the RAN node comprises a data service session radio bearer; and

the communication service session channel between the UE and the RAN node comprises a communication service radio bearer.
The method according to claim 7, wherein, the processing and transferring, between the first network node and the target DA entity, the data service data via the communication service session channel comprises:

receiving, by the first network node, the desired data service data from the DA-E via the data service session radio bearer and data service session tunnel associated to communication service, or

sending, by the first network node, the desired data service data to the DA-E via the data service session radio bearer and data service session tunnel associated to communication service.
The method according to any of claims 5 to 6, wherein:

the first network node comprises the RAN node and the second network node comprises the Data-AMF; and

the data service session channel between the RAN node and the Data-AMF comprises a data service session tunnel associated to communication service.
The method according to claim 9, wherein, the processing and transferring, between the first network node and the target DA entity, the data service data via the data service session channel comprises:

receiving, by the first network node, the desired data service data from the DA-E via at least one data service session tunnel associated to communication service, or

sending, by the first network node, the desired data service data to the DA-E via at least one data service session tunnel associated to communication service.
The method according to any of claims 6 to 10, wherein:

the data service data comprises artificial intelligence (AI) model data; and

the target DA-E contains an AI model to provide the AI model data.
The method according to any of claims 6 to 10, wherein:

the data service data comprises AI model updating data; and

that the target DA-C configures the target DA-E for processing and transferring the data service data comprises:

the target DA-C configures the target DA-E for AI model retraining to provide the AI model updating data; and

the target DA-C configures the target DA-E to transfer the AI model updating data.
The method according to any of claims 3 to 4, wherein, that the first network node sends the first data service session configuration request to the second network node comprises:

a DA of the first network node determines to send the desired data service data;

the DA of the first network node constructs the first data service session configuration request for sending the desired data service data, the first data service session configuration request comprises an IE container comprising data service configuration signaling for the receiving node’s reference;

the DA of the first network node transmits the first data service session configuration request to the communication entity of the first network node via an internal interface;

the communication entity of the first network node sends the first data service session configuration request to a communication entity of the second network node via a communication service session channel; and

the communication entity of the second network node transmits the received first data service session configuration request to a DA entity of the second network node via an internal interface.
The method according to claim 13, wherein, that the second network node communicates with the third network node for configuring the data service session tunnel between the second network node and the target DA entity comprises:

the second network node selects the third network node comprising the target communication entity and the target DA entity;

the DA of the second network node sends a second data service session configuration request to the communication entity of the second network node via an internal interface, the second data service session configuration request comprises an IE container comprising data service configuration signaling for the receiving node’s reference;

the communication entity of the second network node sends the second data service session configuration request to a control part of the target communication entity (target COMM-C) via a communication service session channel;

the target COMM-C transmits the second data service session configuration request to a control part of the target DA (target DA-C) via an internal interface;

the target DA-C configures an execution part of the target DA (target DA-E) for processing and receiving the desired data service data;

the target DA-C constructs a second data service session configuration response for establishing the data service session tunnel between the DA entity of the second network node and the target DA-E, the second data service session configuration response comprising an IE container comprising data service configuration signaling; and

the third network node transmits the second data service session configuration response to the second network node via a communication service session channel.
The method according to any of claims 13 to 14, wherein:

the first network node comprises the UE and the second network node comprises the RAN node;

the data service session channel between the UE and the RAN node comprises a data service session radio bearer; and

the communication service session channel between the UE and the RAN node comprises a communication service radio bearer.
The method according to claim 15, wherein, the processing and transferring, between the first network node and the target DA entity, the data service data via the communication service session channel comprises:

sending, by the first network node, the desired data service data to the DA-E via the data service session radio bearer and data service session tunnel associated to communication service; or

receiving, by the first network node, the desired data service data from the DA-E via the data service session radio bearer and data service session tunnel associated to communication service.
The method according to any of claims 13 to 14, wherein:

the first network node comprises the RAN node and the second network node comprises the Data-AMF; and

the data service session channel between the RAN node and the Data-AMF comprises a second data service session tunnel associated to communication service.
The method according to claim 17, wherein, the processing and transferring, between the first network node and the target DA entity, the data service data via the data service session channel comprises:

sending, by the first network node, the desired data service data to the DA-E via at least one data service session tunnel associated to communication service; or

receiving, by the first network node, the desired data service data from the DA-E via at least one data service session tunnel associated to communication service.
The method according to any of claims 15 to 18, wherein:

the data service data comprises sensed data; and

the DA-E is capable of processing and storing the sensed data.
A wireless data service apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 1 to 19.
A non-transitory computer program product comprising a computer-readable program medium code stored thereupon, the computer-readable program medium code, when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 19.