[go: up one dir, main page]

WO2025166575A1 - Procédés et dispositifs de gestion de session de service de données dans un système sans fil - Google Patents

Procédés et dispositifs de gestion de session de service de données dans un système sans fil

Info

Publication number
WO2025166575A1
WO2025166575A1 PCT/CN2024/076450 CN2024076450W WO2025166575A1 WO 2025166575 A1 WO2025166575 A1 WO 2025166575A1 CN 2024076450 W CN2024076450 W CN 2024076450W WO 2025166575 A1 WO2025166575 A1 WO 2025166575A1
Authority
WO
WIPO (PCT)
Prior art keywords
data service
data
network node
service session
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/076450
Other languages
English (en)
Inventor
Li Yang
Fei Wang
Wenwen SUN
Feng Xie
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2024/076450 priority Critical patent/WO2025166575A1/fr
Publication of WO2025166575A1 publication Critical patent/WO2025166575A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the various data services may include sensing service, computing service, artificial intelligence (AI) service, storage service, and/or security service.
  • AI artificial intelligence
  • storage service may include sensing service, computing service, artificial intelligence (AI) service, storage service, and/or security service.
  • PDU protocol data unit
  • 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 managing data service sessions in a wireless system, addressing at least one of the issues/problems discussed in the present disclosure, thus increasing efficiency of various data services, enabling future wireless system to support or handle the forward/transfer of data service data, and/or adapting to various demands of new generation wireless services.
  • an apparatus for wireless data service may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a device for wireless data service may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods.
  • the computer-readable medium may be a non-transitory computer-readable medium.
  • FIG. 1A shows an example of a wireless system.
  • 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. 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.
  • FIG. 7B shows a flow diagram of another method for wireless data service.
  • 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.
  • terms, such as “a” , “an” , or “the” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • the present disclosure describes methods and devices for managing data service sessions in a wireless system.
  • Wireless technologies are moving the world toward an increasingly connected and networked society.
  • High-speed and low-latency wireless system rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations and/or core networks) .
  • New generation networks are expected to provide various data services, in addition to conventional communication service, with high speed, low latency, and highly reliable capabilities, so as to fulfill requirements under various circumstances.
  • a 5G-advanced (5G-A) and 6G wireless systems may expect to integrate and/or harmonize various sensing, computing, artificial intelligence (AI) , storage, and/or security new functions/services along with their own classical communication functions/services.
  • the core network (CN) and/or radio access network (RAN) node may expect to be able to provide both wireless communication service and wireless sensing, computing, AI, storage, and/or security new services.
  • a conventional method of protocol data unit (PDU) session management in legacy 5G wireless system may be mainly targeted for forwarding/transferring user plane (UP) data, which is normally associated with external mobile users’ services, such as mobile application (APP) and web services.
  • UP data is normally generated outside 5G wireless 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.
  • 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 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.
  • NW intermediate/relay network
  • the present disclosure describes various designs, models, and/or methods for data service session management for data service data, enabling future wireless system to support or handle the forward/transfer of data service data, and/or adapting to various demands of various new services.
  • 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.
  • the system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry.
  • SoC systems on a chip
  • ASIC application specific integrated circuits
  • the system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300.
  • I/O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input /output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.
  • USB Universal Serial Bus
  • the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314.
  • the communication interface 302 may include one or more transceivers.
  • the transceivers may be wireless transceivers that include modulation /demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium.
  • the transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings.
  • the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G /Long Term Evolution (LTE) , 5G standards, and/or 6G or any future standards.
  • UMTS Universal Mobile Telecommunications System
  • HSPA High Speed Packet Access
  • LTE Long Term Evolution
  • 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.
  • a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.
  • 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.
  • 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.
  • 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.
  • 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.
  • the “DA Control” entities in each NW node shall firstly establish the E2E control plane of data service session, then the “DA Execution” entities in each NW node shall establish the E2E execution plane of data service session.
  • the control plane data (for configuring DA-E resources) of data service session shall be coupled 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.
  • 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 refers to an execution part of NW node for executing the Communication PDU Session, 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 “DA Control” in the source node determines the “Data Service Session Path” on demand, i.e. who 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.
  • control plane data of Data Service Session is de-coupled from the CP signaling procedure with communication service, i.e. dedicated new signaling procedure is used for Data Service, and the execution plane data of Data Service Session is carried via dedicated new 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 control plane data of Data Service Session is transferred by dedicated new signaling procedure with Data Service.
  • the execution plane data of Data Service Session is transferred by dedicated new Data Service Session tunnel (s) and RB (s) with Data Service.
  • the present disclosure describes various embodiments for managing data service sessions in a wireless 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-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.
  • a new controlling mechanism is applicable to any type of network node or entity (e.g.
  • DA Control DA Control
  • D-E DA Execution
  • 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.
  • the operation of a DA-E relies on triggering and configurations from a DA-C.
  • the present disclosure describes various embodiments of a method 700 for wireless data service.
  • 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 a data agent (DA) for configuring a data service session tunnel between the second network node and the data agent, wherein the DA is located in the second network node and the data service session tunnel is via an internal interface, or the DA is located in a third network node and the data service session tunnel is via an external interface; step 720, receiving, by the first network node from the second network node, a first data service session configuration response comprising the DA configuration information for establishing a data 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 DA, data service data via at least one data service session channel.
  • the first network node is a
  • the present disclosure describes various embodiments of a method 750 for wireless data service.
  • 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 a data agent (DA) for configuring a data service session tunnel between the second network node and the data agent, wherein the DA is located in the second network node and the data service session tunnel is via an internal interface, or the DA is located in a third network node and the data service session tunnel is via an external interface; step 780, sending, by the second network node to the first network node, a first data service session configuration response comprising the DA configuration information for establishing a data 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 data agent, data service data via at least one data service session channel.
  • step 760 receiving
  • the first network node comprises a user equipment (UE) ; the second network node comprises a radio access network (RAN) node; and/or the third network node comprises the DA.
  • UE user equipment
  • RAN radio access network
  • the first network node comprises a RAN node; the second network node comprises a core network entity comprising a data access and mobility management function (Data-AMF) ; and/or the third network node comprises the DA.
  • Data-AMF data access and mobility management function
  • the first network node sends the first data service session configuration request to the second network node comprises: the first network node determines to offer or obtain the desired data service data; 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 the data service configuration signaling for the receiving node’s reference; and/or the first network node sends the first data service session configuration request to the second network node.
  • the second network node communicates with the data agent for establishing the data service session tunnel between the second network node and the data agent comprises: the second network node selects the target data agent; the second network node sends a second data service session configuration request to a control part of the data agent (DA-C) , the second data service session configuration request may comprise data service configuration signaling for the receiving node’s reference; the DA-C configures an execution part of the data agent (DA-E) for processing and transferring the desired data service data; and/or the DA-C sends a second data service session configuration response to the second network node for establishing the data service session tunnel between the second network node and the DA-E, the second data service session configuration response comprises the data service configuration signaling.
  • D-C control part of the data agent
  • the second data service session configuration request may comprise data service configuration signaling for the receiving node’s reference
  • the DA-C configures an execution part of the data agent (DA-E) for processing and transferring the desired data service data
  • the first network node comprises the UE and the second network node comprises the RAN node; and/or the data service session channel between the UE and the RAN node comprises a data service session radio bearer.
  • the processing and transferring, between the first network node and the data agent, 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 the data service session radio bearer and data service session tunnel, 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.
  • 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.
  • the transferring, between the first network node and the data agent, 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, or sending, by the first network node, the desired data service data to the DA-E via at least one data service session tunnel.
  • the data service data comprises artificial intelligence (AI) model data; and the DA-E contains an AI model to provide the AI model data.
  • AI artificial intelligence
  • the data service data comprises AI model updating data; and/or that the DA-C configures the DA-E for processing and transferring the data service data comprises: the DA-C configures the DA-E for AI model retraining to provide the AI model updating data; and/or the DA-C configures the DA-E to transfer the AI model updating data.
  • the first network node sends the first data service session configuration request to the second network node comprises: the first network node determines to send the desired data service data; 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 the data service configuration signaling for the receiving node’s reference; and/or the first network node sends the first data service session configuration request to the second network node.
  • the second network node communicates with the data agent for establishing the data service session tunnel between the second network node and the data agent comprises: the second network node selects the target data agent; the second network node sends a second data service session configuration request to a control part of the data agent (DA-C) , the second data service session configuration request may comprise the data service configuration signaling for the receiving node’s reference; the DA-C configures an execution part of the data agent (DA-E) for processing and receiving the data service data; and/or the DA-C sends a second data service session configuration response to the second network node for establishing the data service session tunnel between the second network node and the DA-E.
  • D-C control part of the data agent
  • the first network node comprises the UE and the second network node comprises the RAN node; and/or the data service session channel between the UE and the RAN node comprises a data service session radio bearer.
  • the present disclosure describes various exemplary embodiments for managing data service sessions in a wireless system, and the exemplary embodiments merely serve as examples and do not pose limitations. Any steps and/or operations in one same embodiment/implementation or more than one different embodiments/implementation in the present disclosure may be combined or arranged in any amount or order, as desired. Two or more of the steps and/or operations may be performed in parallel. Embodiments and implementations in the disclosure may be used separately or combined in any order. Further, each of the methods (or embodiments) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits) .
  • processing circuitry e.g., one or more processors or one or more integrated circuits
  • the UE 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.
  • the Data Service Anchor Node e.g. xNB
  • the Data Service Anchor Node makes the Data Agent control (DA-C) selection, and forwards the Data Service Session configuration Request to the target DA-C entity, which contains the AI model that the requesting UE needs.
  • D-C Data Agent control
  • the target DA-C prepares (configuring the DA-E transferring resources) 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 Anchor Node prepares (configuring the UE resources) the Data Service Session Radio Bearer for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response to the UE.
  • AI model Data Service data
  • step 850 the DA-E entity starts transferring the AI model data to the UE.
  • 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 Emdodiment 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.
  • 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 DA-E 993, and a DA-C 994.
  • the exemplary process may include a portion or all of the following steps.
  • the xNB 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.
  • the Data Service Anchor Node makes the Data Agent control (DA-C) selection, and forwards the Data Service Session configuration Request to the target DA-C entity, which contains the AI model that the requesting xNB needs.
  • D-C Data Agent control
  • the target DA-C prepares (configuring the DA-E transferring resources) the Data Service Session tunnels for Data Service data (AI model) transfer. and generates the Data Service Session configuration Response message to the Data-AMF for establishing the Data Service Session tunnel.
  • 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.
  • step 950 the DA-E entity starts transferring the AI model data to the xNB.
  • the present disclosure describes various embodiments for a UE triggered AI model updating from a DA.
  • Various embodiments may be applied in the below exemplary scenario.
  • Local data may 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.
  • 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.
  • 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) 1092, a DA-E 1093, and a DA-C 1094.
  • the exemplary process may include a portion or all of the following steps.
  • the Data Service Anchor Node makes the Data Agent control (DA-C) selection, and forwards the Data Service Session configuration Request to the target DA-C entity. which is suitable for AI model retraining.
  • D-C Data Agent control
  • the target DA-C prepares (configuring the DA-E transferring resources) the Data Service Session tunnels for Data Service data (AI model) transfer, and prepares (configuring the DA-E processing resources) the Data Service Session storage and computing resource for Data Service data (AI model) processing, and then performs the AI model retraining using local DA-E processing resources, and then generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel.
  • the Data Service Anchor Node prepares (configuring the UE resources) the Data Service Session Radio Bearer for Data Service data (AI model) transfer, and generates the Data Service Session configuration Response to the UE.
  • AI model Data Service data
  • the DA-E entity starts transferring the updated AI model data to the UE.
  • 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 III, now the Data Service requesting Node is xNB, and the Data Service Anchor Node is a new CN entity, i.e. Data-AMF.
  • 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 DA-E 1193, and a DA-C 1194.
  • the exemplary process may include a portion or all of the following steps.
  • the xNB performs the AI model training based on its local data, then xNB generates the Data Service Session Configuration Request message according to its own AI requirement, and sends it to the Data-AMF for transferring the model update request.
  • the Data Service Anchor Node makes the Data Agent control (DA-C) selection, and forwards the Data Service Session configuration Request to the target DA-C entity, which is suitable for AI model retraining.
  • D-C Data Agent control
  • target DA-C prepares (configuring the DA-E transferring resources) the Data Service Session tunnels for Data Service data (AI model) transfer, and prepares (configuring the DA-E processing resources) the Data Service Session storage and computing resource for Data Service data (AI model) processing, and then performs the AI local model retraining using local DA-E processing resources, and then generates the Data Service Session configuration Response message to the Data-AMF for establishing the Data Service Session tunnel.
  • 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.
  • step 1150 the DA-E entity starts transferring the updated AI model data to the xNB.
  • a Data Service requesting Node is a user equipment (UE) which obtained a large amount of sensed data
  • 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.
  • 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) 1292, a DA-E 1293, and a DA-C 1294.
  • the exemplary process may include a portion or all of the following steps.
  • the UE For step 1210, the 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.
  • the Data Service Anchor Node e.g., xNB
  • step 1250 the UE starts transferring the sensed data to the target DA-E entity.
  • the present disclosure describes various embodiments for a xNB triggered sensed data transferring to a DA.
  • Various embodiments may be applied in the below exemplary scenario. Similar to Embodiment Set V, now the Data Service requesting Node is xNB, and the Data Service Anchor Node is a new CN entity, i.e. Data-AMF.
  • 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 DA-E 1393, and a DA-C 1394.
  • the exemplary process may include a portion or all of the following steps.
  • the xNB 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.
  • the Data Service Anchor Node makes the Data Agent control (DA-C) selection, and forwards the Data Service Session Configuration Request to the target DA-C entity, which is suitable for processing and storing the sensed data.
  • D-C Data Agent control
  • the target DA-C prepares (configuring the DA-E transferring resources) the Data Service Session tunnels for Data Service data (sensed data) transfer, and prepares (configuring the DA-E processing resources) the Data Service Session storage resource for Data Service data (sensed data) process, and then generates the Data Service Session configuration Response message to the Data Service Anchor Node for establishing the Data Service Session tunnel.
  • 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.
  • the xNB starts transferring the sensed data to the target DA-E entity.
  • the present disclosure describes methods, apparatus, and computer-readable medium for wireless data service.
  • the present disclosure addressed the issues with managing data service sessions in a wireless 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.

Landscapes

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

Abstract

La présente divulgation concerne des procédés, un système et des dispositifs de gestion de sessions de service de données dans un système sans fil. Un procédé consiste à envoyer, par un premier nœud de réseau à un deuxième nœud de réseau, une première demande de configuration de session de service de données, de sorte que le deuxième nœud de réseau communique avec un agent de données (DA) pour configurer un tunnel de session de service de données entre le deuxième nœud de réseau et l'agent de données, le DA étant situé dans le deuxième nœud de réseau ou le DA étant situé dans un troisième nœud de réseau ; recevoir, par le premier nœud de réseau en provenance du deuxième nœud de réseau, une première réponse de configuration de session de service de données comprenant les informations de configuration DA pour établir un canal de session de service de données entre le premier nœud de réseau et le deuxième nœud de réseau ; et traiter et transférer, entre le premier nœud de réseau et le DA, des données de service de données par l'intermédiaire d'au moins un canal de session de service de données.
PCT/CN2024/076450 2024-02-06 2024-02-06 Procédés et dispositifs de gestion de session de service de données dans un système sans fil Pending WO2025166575A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/076450 WO2025166575A1 (fr) 2024-02-06 2024-02-06 Procédés et dispositifs de gestion de session de service de données dans un système sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/076450 WO2025166575A1 (fr) 2024-02-06 2024-02-06 Procédés et dispositifs de gestion de session de service de données dans un système sans fil

Publications (1)

Publication Number Publication Date
WO2025166575A1 true WO2025166575A1 (fr) 2025-08-14

Family

ID=96698711

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/076450 Pending WO2025166575A1 (fr) 2024-02-06 2024-02-06 Procédés et dispositifs de gestion de session de service de données dans un système sans fil

Country Status (1)

Country Link
WO (1) WO2025166575A1 (fr)

Similar Documents

Publication Publication Date Title
US20220369177A1 (en) Methods and devices for updating iab-node configuration information during inter-donor migration
US12089070B2 (en) Methods and devices for updating configuration information of downstream devices during inter-donor migration
US12425936B2 (en) Methods and devices for enhancing mobility robustness to integrated access and backhaul for new radio
US20230044660A1 (en) Methods and devices for selecting radio bearer mode for multicast broadcast services
US20230007544A1 (en) Methods and devices for updating data transmission during inter-donor migration
US20240276292A1 (en) Method, device, and system for congestion control in wireless networks
US20240064703A1 (en) Methods, devices, and systems for small data transmission
WO2025166575A1 (fr) Procédés et dispositifs de gestion de session de service de données dans un système sans fil
WO2025166596A1 (fr) Procédés et dispositifs de gestion de service de données dans un système de communication sans fil
WO2025179559A1 (fr) Procédés et dispositifs de transfert de données de commande de service de données dans un système de communication sans fil
WO2023141877A1 (fr) Procédés, dispositifs et systèmes pour effectuer un remplacement de tranche de réseau pendant une mobilité
EP4470267A1 (fr) Procédés, dispositifs et systèmes pour effectuer un remplacement de tranche de réseau
US12396001B2 (en) Methods and devices for data transmission based on switching quality of service flow
WO2025147826A1 (fr) Procédés, dispositifs et systèmes de prise en charge d'une gestion basée sur un ensemble de pdu
WO2024229958A1 (fr) Coordination de multiples nœuds de service
US20250098025A1 (en) Method, device, and system for data transmission in wireless networks
US20240298209A1 (en) Deterministic communication with time sensitive networking in a transport network
WO2021035600A1 (fr) Transmission de données précoce pour données de liaison descendante

Legal Events

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

Ref document number: 24922818

Country of ref document: EP

Kind code of ref document: A1