Data transmission method, data session management method, and device, apparatus and medium

Abstract

Provided in the present disclosure are a data transmission method, a data session management method, and a device, an apparatus and a medium. The data transmission method comprises: on the basis of service requirements of a data service, a terminal sending a first request message to a first network functional entity, wherein the first request message is used for triggering a network to create a new data session for the data service or modify an existing data session; and on the basis of the data session that is created or modified by the network for the data service, performing data transmission of the data service.

Description

Data transmission methods, data session management methods, equipment, devices and media

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411821102.X, filed on December 11, 2024, entitled “Data Transmission Method, Data Session Management Method, Apparatus, Device and Medium”, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to the field of wireless communication technology, and in particular to a data transmission method, a data session management method, a device, apparatus, and medium. Background Technology

[0004] Fifth-generation (5G) mobile communication networks serve as "pipelines" for session-based data transmission, acting as pathways for information exchange between terminals and the network. Unlike point-to-point transmission of session-based data, sixth-generation (6G) mobile communication networks require a distributed approach to data collection, preprocessing, storage, and analysis, encompassing intelligent, sensing, and network-operational data. This necessitates enhancements to data transmission and session management mechanisms to achieve more efficient data services. Summary of the Invention

[0005] This disclosure provides a data transmission method, a data session management method, a device, an apparatus, and a medium for achieving more efficient data services.

[0006] In a first aspect, this disclosure provides a data transmission method applied to a terminal, comprising:

[0007] Based on the service requirements of data services, a first request message is sent to the first network function entity. The first request message is used to trigger the network to create a new data session for data services or modify an existing data session.

[0008] Data services are transmitted through data sessions created or modified over the network for data services.

[0009] In some embodiments, the first request message is a first data session establishment or modification request message, which includes one or more of the following information:

[0010] Data session type;

[0011] Data session identifier;

[0012] Business continuity model;

[0013] Data parameters.

[0014] In some embodiments, the first request message is a service request message or a data service request message, and the service request message or data service request message contains one or more of the following information:

[0015] Data service types;

[0016] Business continuity model;

[0017] Data parameters.

[0018] In some embodiments, the data parameters include one or more of the following:

[0019] Data volume;

[0020] Data message type;

[0021] List of data service agreements;

[0022] Data transmission method;

[0023] Data type;

[0024] Data function types;

[0025] Data transmission direction.

[0026] In some embodiments, the first request message may further include one or more of the following: Protocol Data Unit (PDU) session identifier, data service identifier, and data service network identifier.

[0027] In some embodiments, the method further includes:

[0028] Receive a second data session establishment or modification request message from the data session management function entity. The second data session establishment or modification request message contains configuration instructions related to data services.

[0029] Data operations related to data services are performed based on configuration commands.

[0030] In some embodiments, data operations include one or more of the following: data acquisition operations, data transmission operations, data reception operations, data processing operations, and data storage operations.

[0031] Secondly, this disclosure also provides a data session management method, applied to a data session management functional entity, including:

[0032] Receive a second request message, which may be a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message;

[0033] Based on the second request message, perform one or more of the following operations:

[0034] Create a new data session for data services or modify an existing data session;

[0035] Identify the PDU sessions associated with data services;

[0036] Select data execution nodes for data services.

[0037] In some embodiments, receiving a second request message includes:

[0038] The receiving terminal sends a first data session establishment or modification request message or a data service request message; or,

[0039] Receive a data session context establishment or modification request message or a data service request message sent by the first network function entity; or

[0040] Receive data service request messages sent by the data service requester.

[0041] In some embodiments, the second request message includes one or more of the following: PDU session identifier, data service identifier, and data service network identifier.

[0042] In some embodiments, selecting a data execution node for a data service includes:

[0043] Based on the service requirements of data services, as well as the network identifier of data services and / or the context information of PDU sessions associated with data services, a data execution node is selected.

[0044] In some embodiments, the method further includes:

[0045] Based on the business processing logic of data services, the selected data execution nodes are organized in an orderly manner to construct the data service transmission path.

[0046] In some embodiments, constructing a data service transmission path includes:

[0047] Send a second data session establishment or modification request message to the data execution node. The second data session establishment or modification request message contains configuration instructions related to data services. The configuration instructions are used to indicate data operations related to data services.

[0048] In some embodiments, the data execution node includes one or more of a terminal, an access network entity, and a core network functional entity, and the number of each type of data execution node is one or more.

[0049] In some embodiments, the data service transmission path includes one or more of the following:

[0050] The data service transmission path between the terminal and the access network entity;

[0051] Data service transmission path between the terminal and core network functional entities;

[0052] Data service transmission path between access network entities and core network functional entities;

[0053] Data service transmission path between terminals, access network entities, and core network functional entities;

[0054] Data service transmission path between terminals;

[0055] Data service transmission paths between access network entities;

[0056] Data service transmission paths between core network functional entities.

[0057] In some embodiments, the method further includes:

[0058] A first data session establishment request message is sent to the first data execution node. The first data session establishment request message contains data transmission protocol information. The first data execution node is a network-side node that provides data.

[0059] In some embodiments, the method further includes:

[0060] Receive the address information of the channel sent by the first data execution node;

[0061] A second data session establishment request message is sent to the second data execution node. The second data session establishment request message contains the address information of the data provision channel; the second data execution node is the node that receives the data.

[0062] In some embodiments, the first data session establishment request message further includes information about a second data execution node, which is a node that receives data.

[0063] In some embodiments, the method further includes:

[0064] A third data session establishment request message is sent to the second data execution node. The third data session establishment request message contains the address information of the data provision channel; the second data execution node is the node receiving the data.

[0065] Thirdly, this disclosure also provides a terminal, including a memory, a transceiver, and a processor;

[0066] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0067] Based on the service requirements of data services, a first request message is sent to the first network function entity. The first request message is used to trigger the network to create a new data session for data services or modify an existing data session.

[0068] Data services are transmitted through data sessions created or modified over the network for data services.

[0069] In some embodiments, the first request message is a first data session establishment or modification request message, which includes one or more of the following information:

[0070] Data session type;

[0071] Data session identifier;

[0072] Business continuity model;

[0073] Data parameters.

[0074] In some embodiments, the first request message is a service request message or a data service request message, and the service request message or data service request message contains one or more of the following information:

[0075] Data service types;

[0076] Business continuity model;

[0077] Data parameters.

[0078] In some embodiments, the data parameters include one or more of the following:

[0079] Data volume;

[0080] Data message type;

[0081] List of data service agreements;

[0082] Data transmission method;

[0083] Data type;

[0084] Data function types;

[0085] Data transmission direction.

[0086] In some embodiments, the first request message may further include one or more of the following: Protocol Data Unit (PDU) session identifier, data service identifier, and data service network identifier.

[0087] In some embodiments, the operation further includes:

[0088] Receive a second data session establishment or modification request message from the data session management function entity. The second data session establishment or modification request message contains configuration instructions related to data services.

[0089] Data operations related to data services are performed based on configuration commands.

[0090] In some embodiments, data operations include one or more of the following: data acquisition operations, data transmission operations, data reception operations, data processing operations, and data storage operations.

[0091] Fourthly, this disclosure also provides a data session management function entity, including a memory, a transceiver, and a processor;

[0092] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0093] Receive a second request message, which may be a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message;

[0094] Based on the second request message, perform one or more of the following operations:

[0095] Create a new data session for data services or modify an existing data session;

[0096] Identify the PDU sessions associated with data services;

[0097] Select data execution nodes for data services.

[0098] In some embodiments, receiving a second request message includes:

[0099] The receiving terminal sends a first data session establishment or modification request message or a data service request message; or,

[0100] Receive a data session context establishment or modification request message or a data service request message sent by the first network function entity; or

[0101] Receive data service request messages sent by the data service requester.

[0102] In some embodiments, the second request message includes one or more of the following: PDU session identifier, data service identifier, and data service network identifier.

[0103] In some embodiments, selecting a data execution node for a data service includes:

[0104] Based on the service requirements of data services, as well as the network identifier of data services and / or the context information of PDU sessions associated with data services, a data execution node is selected.

[0105] In some embodiments, the operation further includes:

[0106] Based on the business processing logic of data services, the selected data execution nodes are organized in an orderly manner to construct the data service transmission path.

[0107] In some embodiments, constructing a data service transmission path includes:

[0108] Send a second data session establishment or modification request message to the data execution node. The second data session establishment or modification request message contains configuration instructions related to data services. The configuration instructions are used to indicate data operations related to data services.

[0109] In some embodiments, the data execution node includes one or more of a terminal, an access network entity, and a core network functional entity, and the number of each type of data execution node is one or more.

[0110] In some embodiments, the data service transmission path includes one or more of the following:

[0111] The data service transmission path between the terminal and the access network entity;

[0112] Data service transmission path between the terminal and core network functional entities;

[0113] Data service transmission path between access network entities and core network functional entities;

[0114] Data service transmission path between terminals, access network entities, and core network functional entities;

[0115] Data service transmission path between terminals;

[0116] Data service transmission paths between access network entities;

[0117] Data service transmission paths between core network functional entities.

[0118] In some embodiments, the operation further includes:

[0119] A first data session establishment request message is sent to the first data execution node. The first data session establishment request message contains data transmission protocol information. The first data execution node is a network-side node that provides data.

[0120] In some embodiments, the operation further includes:

[0121] Receive the address information of the channel sent by the first data execution node;

[0122] A second data session establishment request message is sent to the second data execution node. The second data session establishment request message contains the address information of the data provision channel; the second data execution node is the node receiving the data.

[0123] In some embodiments, the first data session establishment request message further includes information about a second data execution node, which is a node that receives data.

[0124] In some embodiments, the operation further includes:

[0125] A third data session establishment request message is sent to the second data execution node. The third data session establishment request message contains the address information of the data provision channel; the second data execution node is the node receiving the data.

[0126] Fifthly, this disclosure also provides a data transmission apparatus, comprising:

[0127] The first sending unit is used to send a first request message to the first network function entity based on the service requirements of the data service. The first request message is used to trigger the network to create a new data session for the data service or modify an existing data session.

[0128] The data transmission unit is used to establish or modify data sessions for data services based on the network, and to transmit data for these services.

[0129] Sixthly, this disclosure also provides a data session management apparatus, comprising:

[0130] The second receiving unit is used to receive a second request message, which is a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message.

[0131] An execution unit is configured to perform one or more of the following operations based on a second request message:

[0132] Create a new data session for data services or modify an existing data session;

[0133] Identify the PDU sessions associated with data services;

[0134] Select data execution nodes for data services.

[0135] In a seventh aspect, this disclosure also provides a non-transient readable storage medium storing a program for causing a processor to execute the data transmission method described in the first aspect above, or to execute the data session management method described in the second aspect above.

[0136] Eighthly, this disclosure also provides a communication device that stores a program for causing the communication device to perform the data transmission method described in the first aspect above, or the data session management method described in the second aspect above.

[0137] In a ninth aspect, this disclosure also provides a processor-readable storage medium storing a program for causing a processor to perform the data transmission method described in the first aspect above, or the data session management method described in the second aspect above.

[0138] In a tenth aspect, this disclosure also provides a chip product storing a program for causing the chip product to execute the data transmission method described in the first aspect above, or to execute the data session management method described in the second aspect above.

[0139] The data transmission method, data session management method, device, apparatus, and medium provided in this disclosure enable a terminal to send a first request message to a first network function entity based on the service requirements of a data service, thereby triggering the network to create a new data session or modify an existing data session for that data service. As a result, the terminal can perform data transmission based on the data session. By enhancing the data transmission mechanism, it helps to achieve more efficient data services and better improve network performance. Attached Figure Description

[0140] To more clearly illustrate the technical solutions in the embodiments or related technologies of this disclosure, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0141] Figure 1 is a flowchart illustrating the data transmission method provided in an embodiment of this disclosure.

[0142] Figure 2 is a flowchart illustrating the data session management method provided in an embodiment of this disclosure.

[0143] Figure 3 is a flowchart of Example 1 provided in the embodiments of this disclosure.

[0144] Figure 4 is a flowchart of Example 2 provided in the embodiments of this disclosure.

[0145] Figure 5 is a flowchart of Example 4 provided in the embodiments of this disclosure.

[0146] Figure 6 is a flowchart of Example 5 provided in the embodiments of this disclosure.

[0147] Figure 7 is a flowchart of Example 6 provided in the embodiments of this disclosure.

[0148] Figure 8 is a flowchart of Example 7 provided in the embodiments of this disclosure.

[0149] Figure 9 is a schematic diagram of the structure of the terminal provided in the embodiment of this disclosure.

[0150] Figure 10 is a schematic diagram of the structure of the data session management function entity provided in the embodiments of this disclosure.

[0151] Figure 11 is a schematic diagram of the structure of the data transmission device provided in an embodiment of this disclosure.

[0152] Figure 12 is a schematic diagram of the structure of the data session management device provided in the embodiments of this disclosure. Detailed Implementation

[0153] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0154] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0155] In the embodiments of this disclosure, the terms "first," "second," etc., are used to distinguish similar objects and are not used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this disclosure can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, and the number of objects is not limited; for example, the first object can be one or more.

[0156] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0157] Figure 1 is a flowchart illustrating the data transmission method provided in an embodiment of this disclosure. The method is applied to a terminal. As shown in Figure 1, the method includes the following steps 101 and 102.

[0158] Step 101: Based on the service requirements of the data service, send a first request message to the first network function entity. The first request message is used to trigger the network to create a new data session for the data service or modify an existing data session.

[0159] Step 102: Create or modify a data session for the data service based on the network, and transmit the data for the data service.

[0160] Specifically, data services refer to services related to data services, such as extended reality (XR), connected vehicles, and other specific services, or services related to data types, such as perception services and artificial intelligence (AI) services.

[0161] 6G communication networks propose a data plane architecture (or data framework, or other similar functions or framework) independent of the traditional user plane. The sessions corresponding to traditional user plane / user traffic transmission are Protocol Data Unit (PDU) sessions, while the sessions corresponding to data plane (or data framework) / intra-system service data transmission are called data sessions. It should be noted that the PDU sessions described in the embodiments of this disclosure may include traditional PDU sessions or other sessions that will implement similar functions in the future.

[0162] The main characteristics of data sessions include:

[0163] (1) A single data service may not necessarily trigger a data session; the network can associate multiple data services into a single data session. Furthermore, the initiator of a data session can be a traditional PDU session initiator such as a terminal or application function (AF), or it can be initiated by access network entities, core network functional entities, or operation administration and maintenance (OAM) equipment. Additionally, the initiator of a data session may be neither the data receiver, nor the data provider, nor the data sender.

[0164] (2) A data session may not establish uplink and downlink transmission paths at the same time. It supports bidirectional transmission and allows data sessions that only establish unidirectional transmission paths. In addition, the data transmission path can also be a ring path such as A→B→C→A.

[0165] (3) A data session may involve multiple types of data endpoints / entities (e.g., terminals, base stations, core network elements, third-party applications) and the number of data endpoints / entities may also be multiple. That is, data execution endpoints / entities (nodes or endpoints or entities that perform data service operations such as data collection, (pre)processing, storage, forwarding / transmission / distribution, etc., which may be terminals, base stations, core network elements, or third-party applications, and may also be called data execution nodes) support multiple endpoint / entity types. Data receiving endpoints / entities may be one or more of terminals, base stations, core network elements, and third-party applications at the same time. Data sending endpoints / entities may be one or more of terminals, base stations, core network elements, and third-party applications at the same time.

[0166] (4) The data execution nodes involved in a data session can support sensitive transmission, that is, the data receiving endpoint / entity, the data sending endpoint / entity, and the nodes responsible for data forwarding in the middle can all process the payload of the received data packets and re-encapsulate them. Finally, the data received by the data receiving endpoint / entity can be different from the data sent by the data sending endpoint / entity.

[0167] (5) A data session can be associated with a PDU session. For example, a special PDU session defined by a specific parameter (such as a combination mapping with a DNN and S-NSSAI, a mapping with a DNN, a mapping with a network node identifier, a mapping with a service identifier, a mapping with a network entity identifier, etc.) can be defined as a data session. DNN refers to Data Network Name, and S-NSSAI refers to Single Network Slice Selection Assistance Information. That is, a data session can be a special or specific PDU session, meaning that a data session is implemented based on a PDU session; a data session can also be implemented through a new mechanism that is not a PDU session.

[0168] Regarding the timing of data session establishment, explanations will be provided separately based on whether data transmission is related to the terminal.

[0169] (1) Data transmission is related to the terminal.

[0170] The timing of data session establishment can be as follows: when the terminal accesses the network, based on one or more of the following: terminal device type (e.g., ordinary terminal device, intelligent agent terminal device, IoT device, sensor device, VR device, vehicle-to-everything (V2X) device, drone device, camera device, etc.); terminal service capabilities (e.g., support for connectivity, data capabilities, sensing capabilities, AI capabilities, intelligent agent capabilities, immersive communication capabilities, etc.); user role (e.g., ordinary user, VIP user, advanced VIP user, private network user, etc.); application type; power consumption; resource status, etc. A data session can be established by default (e.g., for a terminal with sensing capabilities, a default data session can be established for transmitting terminal sensing information; or, for an intelligent agent terminal device, a default data session can be established for the terminal to receive AI models or transmit tokens issued by the network or application functions). Alternatively, the terminal can be established after it has registered and established a connection with the network; or it can be established after the terminal has established a PDU session with the network and constructed a user plane path. VR refers to Virtual Reality (VR), and VIP refers to Very Important Person (VIP).

[0171] The aforementioned data session, based on the distinction between terminal sending data and terminal receiving data, can be an uplink data plane path where only the terminal sends data, a downlink data plane path where only the terminal receives data, or it can include both uplink and downlink data plane paths.

[0172] (2) Data transmission is independent of the terminal.

[0173] The timing of data session establishment can be either a data session established by default when the network is created (for example, a data session can be established by default between the core network user plane function network element and the core network data analysis network element when the network element starts up, to carry the transmission of data analysis-related collected data), or a data session established later by the data service requester (e.g., event triggering).

[0174] This disclosure extends support for terminal data transmission based on data sessions. The terminal can send a first request message to a first network function entity based on the service requirements of a data service, triggering the network to create a new data session or modify an existing data session for that data service. Thus, the terminal can transmit data based on the data session, such as requesting data from the network, requesting data from a base station or other terminal, or providing data to the network. The requested or provided data can be generated or collected.

[0175] The first network function entity can be a network control plane anchor point, such as a network function entity responsible for access management, or a data session management function entity or a unified session management function entity, or an intelligent agent entity, etc., without limitation here.

[0176] The data session management function entity can be a separate new network element, or an enhancement of the function entity responsible for PDU session management (such as 5G SMF), or an enhancement of the function entity responsible for data collection control (such as 5G DCCF). Its main functions include: receiving request messages related to data sessions or data services (such as data session establishment, modification, or release request messages, data session context establishment, modification, or release request messages, or data service request messages); selecting data execution nodes or data function entities (such as terminals, base stations, core network elements, including data source / data collection function entities / data provider entities, data transmission function entities / data distribution function entities, data processing function entities, data storage function entities, data consumption function entities / data receiving function entities, etc., which are some or all of the entities or nodes related to the entire data lifecycle corresponding to the data service); and completing the establishment / modification / release of the data plane / data service path through data plane / data service signaling control. The data plane path refers to the data forwarding / transmission channel (or data service transmission path, data service channel, etc.) between data execution nodes, which uses the data plane interface protocol or the data service interface protocol.

[0177] The unified session management function entity is responsible for the unified management of data sessions and PDU sessions. It can be an independent network element or an enhanced implementation of the function entity responsible for PDU session management.

[0178] It should be noted that the aforementioned functional entities can also be implemented in the form of intelligent agents.

[0179] Modifying an existing data session for a data service can also be understood as associating the data service with an existing data session, rather than creating a new data session for that service.

[0180] The data transmission method provided in this disclosure allows a terminal to send a first request message to a first network function entity based on the service requirements of a data service, thereby triggering the network to create a new data session or modify an existing data session for the data service. This enables the terminal to transmit data based on the data session. By enhancing the data transmission mechanism, more efficient data services can be achieved, and user experience and / or network performance can be improved.

[0181] In some embodiments, the first request message is a first data session establishment or modification request message, which includes one or more of the following information:

[0182] Data session type;

[0183] Data session identifier;

[0184] Business continuity model;

[0185] Data parameters.

[0186] In the various embodiments of this disclosure, the data session establishment, modification, or release request message includes a data session establishment request message, a data session modification request message, or a data session release request message. This concept remains consistent throughout the text and will not be repeated hereafter.

[0187] The establishment of a data session can be achieved either by the data session management entity determining whether a data session needs to be established based on the implicit data service request from the data service requester, or by the data service requester explicitly initiating a data session establishment request. That is, the data session management entity may receive a message that explicitly requests the establishment of a certain type of data session, or the message may not explicitly include a request to establish a data session but only indicate a data service request. The data session management entity then determines whether to create a new data session based on data service requirements and policy information, or to directly or indirectly meet the data service requirements using an existing data session. The data session management entity's determination to create, modify, or release a data session may be related to information such as the data analysis and prediction results of the intelligent network element. The aforementioned data service requester can be a terminal, network (access network entity or core network functional entity), OAM, third-party applications, etc.

[0188] After a data session is established, it can be modified or released based on the update requests of the data service requester (which may be the same as or different from the data service request at the time the data session was established), network status, or data execution node status. Modification or release of a data session can be initiated by the data session management entity based on an explicit request from the data service requester, or it can be triggered or determined by the network based on the expected duration of the data session, data services, policy information, and data session type.

[0189] In some embodiments, based on the service requirements of the data service, the terminal may determine whether the data service requires the creation of a new data session or whether the data service does not require the creation of a new data session and only needs to modify the existing data session. The terminal may send a first data session establishment or modification request message to the first network function entity, which carries one or more pieces of information such as data session type, data session identifier (ID), service continuity mode, and data parameters.

[0190] Data session types can be defined in various ways, without specific limitations here. For example, they can be defined based on session duration, including: long-term sessions like Always On, one-time sessions used only for a single service or data transmission, and sessions lasting for a period of time for one or more services. They can also be defined based on the type of service they are applicable to, such as sessions for AI model transmission, sessions for sensing data transmission, sessions for location data transmission, and sessions for data transmission related to network energy-saving goals.

[0191] A data session is identified by a data session ID, which can be assigned by the network and unique within a certain range (e.g., globally, within the same public land mobile network (PLMN), within the same network node, or within the same radio access network; different ranges have different session ID pools). Alternatively, a data session can be uniquely distinguished by the data service requester's identifier (or the data node identifier assigned by the network) and the identifier of the data service requested by the requester (i.e., the data session ID consists of the data service requester's identifier (or data node identifier) ​​and the data service identifier). The network maintains the data session context information corresponding to each data session ID, the mapping relationship of data session IDs associated with each data service (one data session can map to multiple data services), and the context information of each data service (e.g., the requester of the service, the service requirement parameters of the service, the priority of the service, the service status of the service, etc.). The service continuity mode can indicate whether discontinuous data service occurrences are allowed. For example, it can adopt a Session and Service Continuity (SSC) mode similar to a PDU session or other modes; no specific limitation is made here.

[0192] In some embodiments, data parameters may include one or more of the following:

[0193] (1) Data volume.

[0194] This parameter can indicate the size of the data volume, such as whether the data volume is large or small, or the magnitude of the data volume, etc.

[0195] (2) Data message type.

[0196] Data message types include one or more such as Internet Protocol (IP) messages, Ethernet messages, and Internet of Things (IoT) unstructured messages.

[0197] (3) List of data service agreements.

[0198] The list of data service protocols can also be described as a list of data plane protocol stacks. This list may include, for example, one or more of the following: IP protocol stack, General Packet Radio Service Tunneling Protocol (GTP) protocol stack, Hypertext Transfer Protocol (HTTP) protocol stack, Quick UDP Internet Connections (QUIC) protocol stack, and MoQ protocol stack. UDP refers to User Datagram Protocol (UDP). MoQ refers to Media over QUIC (MoQ) protocol.

[0199] (4) Data transmission method.

[0200] Data transmission methods include, for example, synchronous or asynchronous, real-time or non-real-time, and so on.

[0201] (5) Data type.

[0202] Data types include, for example, one or more types of sensor data, AI data, network data, computing power data, location data, energy-saving related data, and network data.

[0203] The data types can be classified in other ways, and this disclosure does not limit them. For example, data types may include one or more of the following: IoT data, vehicle networking data, and XR data.

[0204] Data types, or different types of data, can be one or more messages, one or more files (such as audio, video, images, etc.), some measurement messages, or streaming media, etc.

[0205] (6) Data function type.

[0206] Data function types include one or more, such as collection, forwarding, storage, and processing.

[0207] (7) Data transmission direction.

[0208] Data transmission directions include, for example, uplink / downlink / uplink / downlink, send / receive / transmit / receive, etc.

[0209] In some embodiments, the first request message is a service request message or a data service request message, and the service request message or data service request message contains one or more of the following information:

[0210] Data service types;

[0211] Business continuity model;

[0212] Data parameters.

[0213] For example, if a terminal cannot determine whether a data session needs to be established, it can send a service request message or a data service request message to the first network function entity, carrying one or more pieces of information such as data service type, service continuity mode, and data parameters in the service request message or data service request message.

[0214] The data service type indicates the type of data service requested. The meanings of business continuity mode and data parameters can be found above and will not be repeated here.

[0215] In some embodiments, the first request message may further include one or more of the following: PDU session identifier, data service identifier, and data service network identifier.

[0216] The PDU session identifier is used to indicate the data session or PDU session associated with the data service corresponding to the first request message. For example, when a special PDU session defined by a specific parameter (such as a combination mapping with a DNN and S-NSSAI, a mapping with a DNN, a mapping with a network node identifier, a mapping with a service identifier, a mapping with a network entity identifier, etc.) is defined as a data session, or when the data session is based on a PDU session, the PDU session identifier corresponding to the data session can be carried.

[0217] The data service identifier is used to indicate the data service requested by the first request message, or to indicate the data service related to the data session corresponding to the first request message. For example, if the data session ID is jointly identified by the data node identifier and the data service identifier, the terminal can generate a locally unique data service identifier and carry it in the first request message.

[0218] The data service network identifier is used to indicate the data service network, distributed network node, distributed subnet, local network, or data processing function (DPF) entity or data service management entity related to the data session or data service corresponding to the first request message. This data service network identifier can be, for example, a DNN or S-NSSAI parameter similar to those used in 5G networks, or identification information similar to that assigned to the UE by the 5G AMF for routing to the AMF (e.g., AMF UE NGAP ID, GUAMI, GUTI, 5G-TMSI, etc.).

[0219] In some embodiments, the method further includes:

[0220] Receive a second data session establishment or modification request message from the data session management function entity. The second data session establishment or modification request message contains configuration instructions related to data services.

[0221] Data operations related to data services are performed based on configuration commands.

[0222] Specifically, the terminal triggers the network to create a new data session or modify an existing data session for the data service through a first request message. On the network side, the data session management function entity completes the establishment or modification of the data plane / data service path through data plane / data service signaling control. After selecting a data execution node / entity (including a data sending node, a data receiving node, and an intermediate execution node) for the data service, the data session management function entity can send a second data session establishment or modification request message to each data execution node / entity. The second data session establishment or modification request message carries configuration instructions related to the data service. These configuration instructions are used to instruct data operations related to the data service.

[0223] In some embodiments, data operations include one or more of the following: data acquisition / collection / generation operations, data transmission operations, data reception operations, data transmission operations, data distribution operations, data processing operations, data storage operations, and data sharing operations.

[0224] For example, after receiving the configuration command, the terminal can perform one or more operations related to the data service, such as data acquisition / collection / generation, data sending / transmission / distribution, data reception, data processing, data storage, and data sharing. Data acquisition / collection can involve collecting data locally on the terminal or data not locally on the terminal; this is not limited to these specific operations.

[0225] Figure 2 is a flowchart illustrating the data session management method provided in this embodiment of the present disclosure. The method is applied to the data session management function entity. As shown in Figure 2, the method includes the following steps 201 and 202.

[0226] Step 201: Receive a second request message, which may be a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message.

[0227] Step 202: Based on the second request message, perform one or more of the following operations:

[0228] Create a new data session for data services or modify an existing data session;

[0229] Identify the PDU sessions associated with data services;

[0230] Select data execution nodes for data services.

[0231] Specifically, the data session management function entity can be an independent network element, or it can be co-located with the function entity responsible for PDU session management, or it can be co-located with a similar entity for data collection functions (such as 5G DCCF). Its main functions include: receiving request messages related to data sessions or data services (such as data session establishment, modification, or release request messages, data session context establishment, modification, or release request messages, or data service request messages); selecting data execution nodes or data function entities (such as terminals, base stations, core network elements, including data source / data collection function entities / data provider entities, data transmission function entities / data distribution function entities, data processing function entities, data storage function entities, data consumption function entities / data receiving function entities, etc., which are some or all of the entities or nodes related to the entire data lifecycle corresponding to the data service); and completing the establishment / modification / release of the data plane / data service path through data plane / data service signaling control. The data plane / data service path refers to the data forwarding / transmission channel (or data service transmission path, data service channel, etc.) between data execution nodes, which uses a data plane interface protocol or a data service interface protocol.

[0232] Data session establishment or modification request messages include data session establishment request messages or data session modification request messages.

[0233] In some embodiments, the second request message may include a data session release request message.

[0234] The data session context establishment or modification request message includes a data session context establishment request message or a data session context modification request message. In some embodiments, the second request message may include a data session context release request message.

[0235] Modifying an existing data session can include releasing the existing data session.

[0236] Selecting a data execution node for a data service can be described as: selecting / reselecting / determining a data execution node for a data service.

[0237] The data session management method provided in this disclosure allows the data session management function entity to perform data session or data service-related operations based on received data session or data service-related request messages. These operations include creating a new data session for a data service or modifying an existing data session, determining a PDU session associated with a data service, and selecting a data execution node for a data service. By enhancing the session management mechanism, this method helps to achieve more efficient data services and better improve user experience and / or network performance.

[0238] In some embodiments, receiving a second request message includes:

[0239] The receiving terminal sends a first data session establishment or modification request message or a data service request message; or,

[0240] Receive a data session context establishment or modification request message or a data service request message sent by the first network function entity; or

[0241] Receive data service request messages sent by the data service requester.

[0242] For example, based on the service requirements of a data service, if the terminal determines that the data service needs to establish a new data session, or if it determines that the data service does not need to establish a new data session and only needs to modify an existing data session, the terminal can send a first data session establishment or modification request message to the session management function entity. Alternatively, if the terminal cannot determine whether a data session needs to be established, it can send a data service request message to the session management function entity.

[0243] For example, if the first network function entity is not a session management function entity, after the terminal sends a first request message to the first network function entity (such as an access management function entity or a unified session management function entity), the first network function entity sends a data session context establishment or modification request message to the session management function entity based on the first request message, or the first network function entity directly forwards the data service request message sent by the terminal.

[0244] For example, the data session management function entity can receive data service request messages sent by the data service requester, which can be a third-party application, OAM, access network entity, core network function entity, terminal, etc., without limitation.

[0245] In some embodiments, the second request message includes one or more of the following: PDU session identifier, data service identifier, and data service network identifier.

[0246] The PDU session identifier is used to indicate the data session corresponding to the second request message or the PDU session associated with the data service.

[0247] The data service identifier is used to indicate the data service requested by the second request message, or to indicate the data service related to the data session corresponding to the second request message.

[0248] The data service network identifier is used to indicate the data service network, distributed network node, distributed subnet, local network, or DPF entity or data service management entity that provides data services related to the data session or data service corresponding to the second request message.

[0249] In some embodiments, selecting a data execution node for a data service includes:

[0250] Based on the service requirements of data services, as well as the network identifier of data services and / or the context information of PDU sessions associated with data services, a data execution node is selected.

[0251] For example, the data session management function parses the business requirements of data services and selects data execution nodes based on the matching of data service capability information, status information, and permission restrictions. During the selection process, if the data service is associated with a PDU session, the selection of the data execution node can be based on the context information of that PDU session. If the second request message also carries a data service network identifier, the selection of the data execution node can also be based on that data service network identifier.

[0252] In some embodiments, the method further includes:

[0253] Based on the business processing logic of data services, the selected data execution nodes are organized in an orderly manner to construct the data service transmission path.

[0254] After selecting data execution nodes, the data session management function entity can organize the selected data execution nodes in an orderly manner according to the business processing logic of the data service (e.g., which data execution nodes or which data execution nodes will collect data, which data execution nodes or which data execution nodes will forward data, the order in which data is routed to each data execution node, etc.), thereby constructing the data service transmission path for the data service.

[0255] In some embodiments, constructing a data service transmission path includes:

[0256] Send a second data session establishment or modification request message to the data execution node. The second data session establishment or modification request message contains configuration instructions related to data services. The configuration instructions are used to indicate data operations related to data services.

[0257] Specifically, the data session management function entity can establish or modify the data plane path through data plane signaling control. After selecting data execution nodes (including data sending nodes, data receiving nodes, and intermediate execution nodes) for the data service, the data session management function entity can send a second data session establishment or modification request message to each data execution node. The second data session establishment or modification request message carries configuration instructions related to the data service. These configuration instructions are used to instruct data operations related to the data service.

[0258] In some embodiments, data operations include one or more of the following: data acquisition / collection / generation operations, data transmission operations, data reception operations, data transmission operations, data distribution operations, data processing operations, data storage operations, and data sharing operations.

[0259] In some embodiments, the data execution node includes one or more of a terminal, an access network entity, and a core network functional entity, and the number of each type of data execution node is one or more.

[0260] In some embodiments, the data service transmission path includes one or more of the following:

[0261] The data service transmission path between the terminal and the access network entity;

[0262] Data service transmission path between the terminal and core network functional entities;

[0263] Data service transmission path between access network entities and core network functional entities;

[0264] Data service transmission path between terminals, access network entities and core network functional entities (e.g., terminal collects data, access network entities collect data, and transmit it to core network functional entities);

[0265] Data service transmission path between terminals;

[0266] Data service transmission paths between access network entities;

[0267] Data service transmission paths between core network functional entities.

[0268] In some embodiments, the method further includes:

[0269] A first data session establishment request message is sent to the first data execution node. The first data session establishment request message contains data transmission protocol information. The first data execution node is a network-side node that provides data.

[0270] Specifically, in the case of establishing a new data session channel, after selecting the data execution node, the data session management function entity can first send a first data session establishment request message to the first data execution node (i.e., the network-side node that provides the data). The first data session establishment request message carries data transmission protocol information, indicating the protocol used for data transmission.

[0271] The first data execution node can build a data provision channel based on this data transmission protocol information, such as starting a QUIC server to provide data.

[0272] In some embodiments, the method further includes:

[0273] Receive the address information of the channel sent by the first data execution node;

[0274] A second data session establishment request message is sent to the second data execution node. The second data session establishment request message contains the address information of the data provision channel; the second data execution node is the node that receives the data.

[0275] For example, the construction of the data session channel is centrally controlled by the data session management function entity. After the first data execution node constructs the data provision channel based on the data transmission protocol information, it can send a first data session establishment response message to the data session management function entity. The first data session establishment response message carries the address information of the data provision channel.

[0276] Then, the data session management function entity sends a second data session establishment request message to the second data execution node (i.e., the node receiving the data), which carries the address information of the data provision channel.

[0277] The second data execution node can build a data receiving channel based on the address information of the data providing channel provided by the data session management function entity, for example, by starting a QUIC client.

[0278] When data transmission uses the QUIC protocol, the data provides channel address information, such as the IP address and port information of the QUIC server.

[0279] In some embodiments, network elements can provide data services based on a service-oriented mechanism. That is, the network element providing the data service (core network element or access network element) can define a service-oriented operation, and data service consumers can use this service operation to obtain the data service provided by the network element. In the case of a service-oriented approach, the address information of the data provision channel can be a Uniform Resource Locator (URL) address that provides the service operation.

[0280] In some embodiments, the first data session establishment request message further includes information about a second data execution node, which is a node that receives data.

[0281] For example, in the case of establishing a new data session channel, after selecting a data execution node, the data session management function entity can send a first data session establishment request message to the first data execution node. This first data session establishment request message carries not only data transmission protocol information but also information about the second data execution node. The first data execution node can construct a data provision channel based on this data transmission protocol information. Furthermore, the first data execution node can directly send the address information of the data provision channel to the second data execution node based on the information of the second data execution node provided by the data session management function entity, so that the second data execution node can construct a data receiving channel based on the address information of the data provision channel, such as starting a QUIC client.

[0282] The information of the second data execution node may include, for example, its identifier or address, and is not specifically limited here.

[0283] In some embodiments, the method further includes:

[0284] A third data session establishment request message is sent to the second data execution node. The third data session establishment request message contains the address information of the data provision channel; the second data execution node is the node receiving the data.

[0285] Specifically, if the first data execution node has established a data provision channel that meets business requirements and has provided the address information of the data provision channel to the data session management function entity, after selecting the data execution node, the data session management function entity can directly send a third data session establishment request message to the second data execution node (i.e., the node receiving data). The third data session establishment request message carries the address information of the data provision channel, so that the second data execution node can build a data receiving channel based on the address information of the data provision channel, such as starting the QUIC client.

[0286] The methods provided in the various embodiments of this disclosure are based on the same technical concept, so the implementation of each method can be referred to each other, and repeated parts will not be described again.

[0287] The methods provided in the above embodiments of this disclosure are illustrated by specific examples below.

[0288] Example 1: The process of establishing a data session initiated by the terminal, taking the terminal requesting data from the network as an example.

[0289] Figure 3 is a flowchart of Example 1 provided in the embodiments of this disclosure. As shown in Figure 3, its main processes include:

[0290] Step 1-0: The network has obtained the data service capability information corresponding to the terminal, base station, and data execution function entity.

[0291] Step 1-1: The terminal sends a data service-related request message to the network (e.g., to the network control plane anchor point, i.e., the access management function entity). This can be done in two ways:

[0292] (1) When the terminal explicitly needs to establish a new data session, it sends a request message that explicitly expresses the need to establish a data session, such as Data Session Establishment Request. The request message includes: the requested data session type, [local data session identifier], the requested business continuity mode, the requested data parameters, etc.

[0293] Data parameters may include: data volume (e.g., large data volume, small data volume), data packet type (e.g., IP packet, Ethernet packet, IoT unstructured packet, etc.), data service protocol list (e.g., IP protocol stack, GTP tunnel protocol stack, HTTP protocol stack, QUIC protocol stack, MoQ protocol stack, etc.), data transmission method (synchronous / asynchronous, real-time / non-real-time), data type (e.g., sensing data, AI data, network data, computing power data, etc.), data function type (e.g., collection, forwarding, storage, processing, etc.), and data transmission direction (uplink, downlink, uplink and downlink; or, send, receive, send and receive).

[0294] Data session types can be defined in different ways based on data parameters and other dimensions.

[0295] (2) When the terminal cannot determine whether a new data session needs to be established, it sends a data service request message, such as Data Service Establishment Request. The request message includes: the requested data service type, the requested service continuity mode (such as SSC mode similar to PDU session, which can indicate whether non-continuous data service is allowed), and the requested data parameters.

[0296] Then, the network determines whether to create a new data session or modify an existing data session based on the data service request message to meet the needs of the data service.

[0297] Figure 3 uses case (2) as an example.

[0298] In the above situations (1) or (2), the request message may also carry the PDU session ID of the user plane service. If carried, it indicates that the data session or data service is associated with the PDU session. In addition, if the data session ID is jointly identified by the data node identifier and the data service ID, the terminal can generate a locally unique data service ID and carry it in the request message.

[0299] Step 1-2: The access management function entity determines whether the data service is associated with a specific PDU session. If Step 1-1 includes a PDU session ID, then an association is established; otherwise, the access management function entity can determine whether the data service is associated with a specific PDU session based on the terminal type, the request message in Step 1-1, and locally maintained terminal-related PDU session IDs. The access management function entity selects the data session management function entity based on the association between the data service and the PDU session, and the request message in Step 1-1.

[0300] Steps 1-3: The access management function entity requests the data session management function entity to establish a data session context. The request message may carry the PDU session ID, data service ID, etc.

[0301] For steps 1-2 to 1-3, if the access management function entity cannot obtain more information, it can simply forward the terminal's data service request message.

[0302] Steps 1-4: The data session management entity determines whether the data service requester can obtain the requested data service at their current location. This can be achieved by interacting with the data management entity to obtain the requester's subscription data, with the policy control entity to obtain the policy information for the data service request, and with the authentication management entity to verify the requester's security-related parameters. Pre-authorization may be granted to certain high-level special users, and some security verification processes may be waived for data service requests triggered by certain special services (e.g., emergency services).

[0303] If the data session management function entity receives a data session context establishment request message, it establishes a data session; if it receives a data session context modification request message, it modifies a data session; if it receives a data service request message (which can be a data service that directly indicates a data service, or a service that implicitly indicates a data service requirement, such as a perception service or an AI service), it parses the data service requirement based on the message information and determines whether to create a new data session or modify an existing data session by combining the existing data session context information and policy information maintained locally.

[0304] Example of a scenario where an existing data session can be modified without creating a new one: A terminal requests data x from the network in service 1, and requests data y from the network in service 2. If the two services have the same quality of service (QoS) requirements for data transmission, when service 2 occurs, the existing data session transmission channel from the network to the terminal is available. It is only necessary to modify the existing data session to add the transmission channel from data 2 to the data execution function entity in the core network.

[0305] If a new data session is being created, a data session ID is generated based on the data session identification rules, or a data session ID is mapped based on the data service ID from step 1-1. If an existing data session is being modified, the data session ID of the data session to be modified is determined.

[0306] In addition, the data session management function entity can determine whether the data session ID is associated with a certain PDU session ID (if the access management function entity has already determined this in steps 1-2, you can choose whether to determine it again here).

[0307] Steps 1-5: If associated with a PDU session, the corresponding PDU session management function entity or storage function entity storing the PDU session context can be obtained through Network Repository Function (NRF) entity discovery, and interaction can be made with it to request relevant PDU session context information, including the user plane function identifier, packet forwarding rules, QoS policies, etc. of the PDU session.

[0308] Steps 1-6: The data session management function entity parses the data service requirements and selects the data execution node based on the matching of data service capability information, status information, permission restrictions, etc., including the selection of the core network data execution function entity, base station, terminal, etc. involved in the data session. During the selection process, if it is associated with the PDU session, it is necessary to combine the PDU session context information, such as the relationship with the PDU session user plane path.

[0309] Steps 1-7 to 1-10 involve the data session management function entity interacting with relevant data execution nodes (data execution function entity in the core network, base stations, and terminals) to issue configuration commands related to data services. These configuration commands may include data packet identification rules, data packet forwarding rules, and data packet processing rules, supporting "sensory transmission" characteristics.

[0310] Steps 1-11 to 1-12: The data session management function entity replies to the terminal with a data service response message.

[0311] Steps 1-13: The data session management function entity maintains or updates the data session context information for the data session ID.

[0312] Once a data session related to data services is established or modified, the data execution nodes perform on-demand routing and forwarding of data packets based on configuration commands (including support for unidirectional transmission).

[0313] Steps 1-14 to 1-16: Based on the data type requested by the terminal in step 1-1, the corresponding data (such as network data for terminal policy optimization, AI model data for terminal inference, etc.) arrives at the terminal through data execution function entities, base stations, etc. During the data packet transmission process, each data execution node that forwards data operates on the data packet based on configuration instructions. For example, it supports processing the payload of the data packet, re-encapsulating the packet, and sending it (therefore, the data 1 sent by the network and the data 2 received by the terminal may not be exactly the same).

[0314] Data 1 may be data already stored locally by the data execution function entity, or data obtained by the data execution function entity from the data storage function entity, third-party applications, etc. If it is the latter, a data plane transmission channel similar to the above or other transmission channels different from the above can be established between the data execution function entity and the data storage function entity, or application functions. One way is to establish a data plane transmission channel between two core network function entities as shown in Examples 5 to 7 below.

[0315] Example 2: Terminal-initiated data session establishment process. Taking the terminal requesting data from the network as an example, this example adds a unified session management function entity. This unified session management function entity can be an independent network element or it can be enhanced by the function entity responsible for PDU session management.

[0316] Figure 4 is a flowchart of Example 2 provided in the embodiments of this disclosure. As shown in Figure 4, its main processes include:

[0317] Step 2-0: The network has obtained the data service capability information corresponding to the terminal, base station, and data execution function entity.

[0318] Step 2-1: The terminal sends a service request message to the network (e.g., to the network control plane anchor point, i.e., the access management function entity). The request message includes: the requested data service type, the requested service continuity mode (e.g., SSC mode similar to a PDU session, which can indicate whether discontinuous data services are allowed), and the requested data parameters.

[0319] The request message can also carry the PDU session ID of the user plane service. If carried, it indicates that the data session or data service is associated with the PDU session. In addition, if the data session ID is jointly identified by the data node identifier and the data service ID, the terminal can generate a locally unique data service ID and carry it in the request message.

[0320] Step 2-2: The access management function entity selects the unified session management function entity based on the business request message in Step 2-1.

[0321] Steps 2-3: The access management function entity forwards the service request message to the unified session management function entity.

[0322] Steps 2-4: The unified session management function entity determines whether the request is a data service based on the service request message, and determines whether the data session or data service is associated with the PDU session.

[0323] Steps 2-5: After determining that it is a data service, the unified session management function entity interacts with the data session management function entity to request the establishment of a data session context. This request message may carry the PDU session ID, information of the storage function entity storing the PDU session context, data service ID, etc.

[0324] Steps 2-6: The data session management entity determines whether the data service requester can obtain the requested data service at their current location. This can be achieved by interacting with the data management entity to obtain the requester's subscription data, with the policy control entity to obtain the policy information for the data service request, and with the authentication management entity to verify the requester's security-related parameters. Pre-authorization may be granted to some high-level special users, and some data service requests triggered by special business needs (such as emergency business) may be exempt from certain security verification processes.

[0325] If the data session management function entity receives a data session context establishment request message, it establishes a data session; if it receives a data session context modification request message, it modifies a data session; if it receives a data service request message (which can be a data service that directly indicates a data service, or a service that implicitly indicates a data service requirement, such as a perception service or an AI service), it parses the data service requirement based on the message information and determines whether to create a new data session or modify an existing data session by combining the existing data session context information and policy information maintained locally.

[0326] If a new data session is being created, a data session ID is generated based on the data session identification rules, or a data session ID is mapped based on the data service ID from step 2-1. If an existing data session is being modified, the data session ID of the data session to be modified is determined.

[0327] Steps 2-7: If associated with a PDU session, you can interact with the corresponding PDU session management function entity or the storage function entity that stores the PDU session context to request relevant PDU session context information, including the user plane function identifier, packet forwarding rules, QoS policies, etc. of the PDU session.

[0328] Steps 2-8: The data session management function entity parses the data service requirements and selects the data execution node based on the matching of data service capability information, status information, permission restrictions, etc., including the selection of the core network data execution function entity, base station, terminal, etc. involved in the data session. During the selection process, if it is associated with the PDU session, it is necessary to combine the PDU session context information, such as the relationship with the PDU session user plane path.

[0329] Steps 2-9 to 2-12 involve the data session management function entity interacting with relevant data execution nodes (data execution function entity in the core network, base stations, and terminals) to issue configuration commands related to data services. These configuration commands may include data packet identification rules, data packet forwarding rules, and data packet processing rules, supporting "sensory transmission" characteristics.

[0330] Step 2-13: The data session management function entity replies to the unified session management function entity with a data session context establishment response message.

[0331] Step 2-14: The unified session management function entity replies to the terminal with a service response message.

[0332] Step 2-15: The data session management function entity maintains or updates the data session context information for the data session ID.

[0333] Once a data session related to data services is established or modified, the data execution nodes perform on-demand routing and forwarding of data packets based on configuration commands (including support for unidirectional transmission).

[0334] Steps 2-16 to 2-18: Based on the data type requested by the terminal in step 2-1, the corresponding data (such as network data for terminal policy optimization, AI model data for terminal inference, etc.) arrives at the terminal through the data execution function entity, base station, etc. During the data packet transmission process, each data execution node that forwards data operates on the data packet based on the configuration instructions. For example, it supports processing the payload of the data packet, re-encapsulating the packet, and sending it (therefore, the data 1 sent by the network and the data 2 received by the terminal may not be exactly the same).

[0335] Data 1 may be data already stored locally by the data execution function entity, or data obtained by the data execution function entity from the data storage function entity, third-party applications, etc. If it is the latter, a data plane transmission channel similar to the above or other transmission channels different from the above can be established between the data execution function entity and the data storage function entity, or application functions. One way is to establish a data plane transmission channel between two core network function entities as shown in Examples 5 to 7 below.

[0336] Example 3: The terminal requests data from the base station or other terminals.

[0337] For the first request message sent by the terminal to the network, when the session management function entity determines, based on the request message and the maintained data service capability information, that the data required for the data service is provided by the base station or the terminal, the relevant process is similar to that in Examples 1 and 2, with the main difference being the construction of the data plane path.

[0338] The data service transmission path provided by the base station can be: Base Station → Terminal. If the data-providing base station and the terminal-connected base station are different, and the data-providing base station and the terminal-connected base station can interact directly, then it can be: Data-providing base station → Terminal-connected base station → Terminal. If the data-providing base station and the terminal-connected base station cannot interact directly, then it can be: Data-providing base station → Core network data execution function entity → Terminal-connected base station → Terminal.

[0339] The data service transmission path for data provided by other terminals can be: Data Provider Terminal → Terminal. If two terminals cannot interact directly and are connected to the same base station, the path can be: Data Provider Terminal → Base Station → Terminal. If two terminals are connected to different base stations (denoted as Base Station 1 and Base Station 2, which can interact directly), the path can be: Data Provider Terminal → Base Station 1 → Base Station 2 → Terminal. If two terminals are connected to different base stations (which cannot interact directly), the path can be: Data Provider Terminal → Base Station 1 → Core Network Data Execution Function Entity → Base Station 2 → Terminal.

[0340] During data transmission, the data execution node can process the data based on the configuration instructions issued by the data session management function entity under secure and reliable conditions, and supports sending data and receiving data that are not exactly the same.

[0341] Example 4: Data session establishment process initiated by a non-terminal, taking the provision of data from the terminal to the network as an example.

[0342] In this example, the network establishes a data session that supports uplink data transmission by providing data from the terminal. This session can be triggered by third-party applications, application functions (AF), OAM, network function entities, terminals, etc., to request the terminal's sensor data, location data, energy consumption data, resource status data, AI model data, etc.

[0343] Figure 5 is a flowchart of Example 4 provided in the embodiments of this disclosure. As shown in Figure 5, its main processes include:

[0344] Step 4-0: The network has obtained the data service capability information corresponding to the terminal, base station, and data execution function entity.

[0345] Step 4-1: The data session management function entity (possibly through different signaling procedures) receives a data service-related request message. Figure 5 uses a request initiated by an application function, intelligent function, sensing function, or computing function as an example. This request may be authenticated by the network open function entity, and after the service management function entity parses the application function's service requirements and determines it to be a data service request, the request message is sent to the data session management function entity. For example, the application function requests the network to trigger a terminal (in this example, a terminal is used, but it could also be a base station, core network, etc.) to collect data, and then provides the data collected by the terminal (which may have been processed by the network) to the application function.

[0346] Step 4-2: The data session management function entity parses the data service request, including the data content type, data providing node, data providing frequency, data receiving endpoint / entity, etc., to determine whether the existing data or established data session in the network can (directly or after modification) satisfy the data service request.

[0347] If existing data can meet the requirements, respond directly to the data without creating a data session (e.g., if the requested data volume is small and the network has already stored the data, the existing signaling interaction mechanism can be used to respond without establishing a data session; note: if a data plane transmission path needs to be established between the data storage function entity and the data receiving endpoint / entity, then a data session needs to be created or updated); if an established data session has the potential to meet the requirements, associate the data service with an established data session and modify it (e.g., add a data receiving endpoint / entity to the original data collection process, or the raw data from the original data collection process can meet the above data service requirements after being processed by the terminal or network); otherwise, establish a new data session for the data service.

[0348] Meanwhile, the data session management function entity can interact with a network function entity (e.g., access management function entity, PDU session context storage function entity, PDU session management function entity, unified session management function entity) to obtain relevant PDU session information such as the data provider, data receiver, and data execution node related to the data service, and determine whether the data session needs to be associated with the PDU session.

[0349] Step 4-3: If associated with a PDU session, obtain the PDU session context.

[0350] The establishment or modification of a data session may include one or more of the following steps:

[0351] Step 4-4: The data session management function entity selects the data execution node based on the matching of data service capability information, status information, permission restrictions, etc., including the selection of the core network data execution function entity, base station, terminal, etc. involved in the data session. During the selection process, if it is associated with the PDU session, it is necessary to combine the PDU session context information, such as the relationship with the PDU session user plane path.

[0352] Steps 4-5: Send a data session establishment or modification request message to the core network's data execution function entity. The request message adds a configuration instruction to the data packet stream of the data session associated with the data service, instructing it to forward the data stream to the data receiving endpoint / entity corresponding to the aforementioned data service; or, send a data session modification request message to the core network's data execution function entity. The request message adds a data processing operation (e.g., data cleaning, data desmearing, data format conversion, data privacy removal, data fusion, etc.) to the data packet stream of the data session associated with the data service before forwarding it to the data receiving endpoint / entity corresponding to the aforementioned data service.

[0353] Steps 4-6: Send a data session establishment or modification request message to the base station. The request message will add data processing operations according to the data service requirements (such as data cleaning, data desmearing, data format conversion, data privacy removal, data fusion, etc.) to the data packet stream of the data session associated with the data service before forwarding.

[0354] Steps 4-7: (Through the base station) Send a data session establishment or modification request message to the terminal, requesting that the data packet stream of the data session associated with the data service be added and processed according to the data service requirements (such as data cleaning, data desmearing, data format conversion, data privacy removal, data fusion, etc.) before forwarding.

[0355] Steps 4-8: Response messages to data session establishment or modification request messages.

[0356] Steps 4-9: Response messages to data service request messages.

[0357] For terminal data that meets the above business requirements:

[0358] Steps 4-10: The terminal performs data operations based on the configuration instructions of the data session, including data forwarding operations and data processing operations.

[0359] Step 4-11: The base station performs data operations based on the configuration instructions of the data session, including data forwarding operations and data processing operations.

[0360] Step 4-12: The data execution function performs data execution operations based on the configuration instructions of the data session, including data forwarding operations and data processing operations.

[0361] In the above process, the initial data 1 and the final data 2 that arrive at the data receiving endpoint / entity may have been processed due to the terminal or network sensing transmission, which may cause data 2 to be different from data 1.

[0362] It should be noted that the uplink data transmission between the aforementioned data execution function entity and network function entities such as application functions may also require the establishment of a data plane transmission channel similar to the one described above or other transmission channels different from the one described above between the data execution function entity and the application function. One approach is to establish a data plane transmission channel between two core network function entities, as shown in Examples 5 to 7 below.

[0363] Example 5: Data session on the network side, creating a new data session channel.

[0364] The network-side data session differs from the traditional network-side data collection process that uses control plane signaling requests / responses, subscriptions / notifications, etc. Instead, it establishes a data plane transmission channel between the data providing endpoint / entity and the data receiving endpoint / entity, and supports continuous, high-volume, and efficient transmission of data through standardized interfaces and protocols.

[0365] In this example, the construction of the data session channel is centrally controlled by the data session management function entity. The data receiving function entity (i.e., the node that receives data, the data receiving endpoint / entity) can be the same as or different from the data service requester, and there can be one or more of them.

[0366] Figure 6 is a flowchart of Example 5 provided in the embodiments of this disclosure. As shown in Figure 6, its main processes include:

[0367] Step 5-1: The data session management function entity (which may receive a data service-related request message through different signaling processes) receives a request message related to a data service. For example, in Figure 6, a request initiated by an application function, intelligent function, sensing function, or computing function may be sent to the data session management function entity after being authenticated by the network open function entity and the service management function entity parses the application function's business requirements and determines that it is a data service request.

[0368] Step 5-2: The data session management function entity parses the data service request, including the data content type, data providing node, data providing frequency, data receiving endpoint / entity, etc., to determine whether the existing data or established data session in the network can (directly or after modification) satisfy the data service request.

[0369] When the data session management entity receives data service requests from network functions that are not from the same PLMN, the same operator, the same distributed subnet, or the same distributed network node, it may need to perform security processes such as identity authentication, authorization, and service authorization on the data service requester. For some special application functions, pre-authorization can be used to reduce response latency.

[0370] Step 5-3: The data session management entity selects a data execution node based on data service requirements. For the selected data execution node, the data session management entity determines whether a data session transmission channel exists between the network function entity providing the data and the data receiving function entity, and whether the established channel meets the transmission requirements of the data service. If not, proceed with the following steps:

[0371] Step 5-4: The data session management function entity requests the network function entity that provides the data to establish a data session transmission channel (or data service transmission path) for the data session transmission requirement. The request message carries the data transmission protocol, data content, etc.

[0372] Step 5-5: The network function entity providing the data constructs a data provision channel, for example, by starting the QUIC Server that provides the data. In some scenarios, the network function entity providing the data may need to first establish a data transmission channel with one or more other network function entities providing data. After obtaining the data, it performs certain processing operations on the data (such as data cleaning, data privacy removal, etc.) to finally prepare the data that meets the requirements.

[0373] Data acquisition scenarios include: collecting data from local cameras, sensors, etc., retrieving data stored in local storage, or acquiring data stored in non-local extended storage.

[0374] Steps 5-6: The data session establishment response message includes the address information of the data provision channel, such as the IP address and port of the QUIC Server.

[0375] Alternatively, network elements can provide data services based on a service-oriented mechanism. That is, the network element providing the data service (core network element or access network element) can define a service operation. Data service consumers use this service operation to obtain the data service provided by the network element (providing the data itself, providing data processing services, or providing data storage and retrieval services, etc.). For example, the network element providing data can define a Data Provide Service (such as Nnf_Data Provide Service). Data receiving endpoints / entities or data execution function entities use this service operation to request (fetch) the data provided by the network element.

[0376] In the case of a service-oriented approach, the address information of the data provision channel can be a URL address that provides the service operation.

[0377] Steps 5-7: The data session management function entity requests the data receiving function entity to build a data receiving channel and uses the address information of the data providing channel to obtain data.

[0378] Steps 5-8: The data receiving function entity constructs a data receiving channel, for example, by starting the QUIC Client.

[0379] Steps 5-9: Reply with a response indicating that the data receiving channel has been successfully established. Otherwise, reply with a statement indicating that the establishment failed and the reason for the failure, such as that the protocol is not supported.

[0380] Steps 5-10: The data session management function entity replies to the data service requester with a response, indicating success or failure.

[0381] Step 5-11: The data receiving function entity requests data based on the data session transmission channel.

[0382] Continuous data transmission.

[0383] Steps 5-12: The network function entity that provides the data is based on the request and response data.

[0384] Example 6: Data session on the network side, creating a new data session channel.

[0385] In this example, the data session management entity provides information about the data receiving endpoint / entity to the network function entity providing the data. The data receiving entity (i.e., the node receiving the data) can be the same as or different from the data service requester, and there can be one or more of them.

[0386] Figure 7 is a flowchart of Example 6 provided in the embodiments of this disclosure. As shown in Figure 7, its main processes include:

[0387] Step 6-1: The data session management function entity (which may receive a data service-related request message through different signaling processes) receives a request message related to a data service. For example, in Figure 7, a request initiated by an application function, intelligent function, sensing function, or computing function may be sent to the data session management function entity after being authenticated by the network open function entity and the service management function entity parses the application function's business requirements and determines that it is a data service request.

[0388] Step 6-2: The data session management function entity parses the data service request, including the data content type, data providing node, data providing frequency, data receiving endpoint / entity, etc., to determine whether the existing data or established data session in the network can (directly or after modification) satisfy the data service request.

[0389] When the data session management entity receives data service requests from network functions that are not from the same PLMN, the same operator, the same distributed subnet, or the same distributed network node, it may need to perform security processes such as identity authentication, authorization, and service authorization on the data service requester. For some special application functions, pre-authorization can be used to reduce response latency.

[0390] Step 6-3: The data session management entity selects a data execution node based on data service requirements. For the selected data execution node, the data session management entity determines whether a data session transmission channel exists between the network function entity providing the data and the data receiving function entity, and whether the established channel meets the transmission requirements of the data service. If not, proceed with the following steps:

[0391] Step 6-4: The data session management entity requests the network function entity providing the data to establish a data session transmission channel (or data service transmission path) for this data session transmission requirement. The request message carries the data transmission protocol, data content, and information about the data receiving endpoint / entity. This information may include, for example, the identifier or address of the data receiving endpoint / entity.

[0392] Step 6-5: The network function entity providing the data establishes a data provision channel, for example, by starting the QUIC Server that provides the data. In some scenarios, the network function entity providing the data may need to first establish a data transmission channel with one or more other network function entities providing data. After obtaining the data, it performs certain processing operations on the data (such as data cleaning, data privacy removal, etc.) to finally prepare the data that meets the requirements.

[0393] Data acquisition scenarios include: collecting data from local cameras, sensors, etc., retrieving data stored in local storage, or acquiring data stored in non-local extended storage.

[0394] Step 6-6: The network function entity providing the data sends a data reception notification to the data receiving function entity. This data reception notification includes the address information of the data providing channel, such as the IP address and port of the QUIC Server.

[0395] Alternatively, network elements can provide data services based on a service-oriented mechanism. That is, the network element providing the data service (core network element or access network element) can define a service-oriented operation. Data service consumers use this service operation to obtain the data service provided by the network element (providing the data itself, providing data processing services, or providing data storage and retrieval services, etc.). For example, the network element providing data defines a Data Provide Service (such as an NNF Data Provide Service), and the data receiving endpoint / entity or data execution function entity uses this service operation to request and fetch the data provided by the network element.

[0396] In the case of a service-oriented approach, the address information of the data provision channel can be a URL address that provides the service operation.

[0397] Steps 6-7: The data receiving function entity constructs a data receiving channel, for example, by starting the QUIC Client.

[0398] Steps 6-8: The data receiving function entity replies with a data receiving response, indicating that the data receiving channel has been successfully established. Otherwise, it replies with a failure message and the reason for the failure, such as the protocol not being supported.

[0399] Steps 6-9: The network function entity providing the data replies to the data session management function entity with a data session establishment response message.

[0400] Steps 6-10: The data session management function entity replies to the data service requester with a response, indicating success or failure.

[0401] Steps 6-11: The data receiving function entity requests data based on the data session transmission channel.

[0402] Continuous data transmission.

[0403] Steps 6-12: The network function entity that provides the data is based on the request and response data.

[0404] Example 7: Data session on the network side, with an existing data session channel.

[0405] In this example, when the data session management entity receives a data service request, if the network function entity providing the data has already reported (or provided in an existing data session) the address information of the data provision channel that meets the service requirements, the data session management entity can directly provide this address information to the data receiving endpoint / entity (i.e., the data receiving entity). The data receiving entity and the data service requester can be the same or different, and there can be one or more of them.

[0406] Figure 8 is a flowchart of Example 7 provided in the embodiments of this disclosure. As shown in Figure 8, its main processes include:

[0407] Step 7-1: The network function entity that provides the data constructs the data provision channel, for example, by starting the QUIC Server that provides the data.

[0408] Step 7-2: The network function entity providing data sends a data service provision request message to the data session management function entity. The data service provision request message includes the address information of the data provision channel, such as the IP address and port of the QUIC Server.

[0409] Step 7-3: The data session management function entity replies to the network function entity that provided the data with a response, indicating success or failure.

[0410] Step 7-4: The data session management function entity (which may receive a data service-related request message through different signaling processes) receives a request message related to a data service. For example, in Figure 8, a request initiated by an application function, intelligent function, sensing function, or computing function may be sent to the data session management function entity after being authenticated by the network open function entity and the service management function entity parses the application function's business requirements and determines that it is a data service request.

[0411] Step 7-5: The data session management function entity parses the data service request, including the data content type, data provider node, data provider frequency, data receiving endpoint / entity, etc., determines that an existing data session in the network can (directly or after modification) satisfy the data service request, and associates the data service with the existing data session.

[0412] Step 7-6: The data session management function entity selects the data execution node based on data service requirements and determines the existing data session transmission channel.

[0413] Step 7-7: The data session management function entity sends a data session establishment request message to the data receiving function entity. The request message carries the address information of the data providing channel.

[0414] Steps 7-8: The data receiving function entity constructs a data receiving channel, for example, by starting the QUIC Client.

[0415] Steps 7-9: The data receiving function entity replies to the data session management function entity with a data session establishment response message.

[0416] Steps 7-10: The data session management function entity replies to the data service requester with a response, indicating success or failure.

[0417] Steps 7-11: The data receiving function entity requests data based on the data session transmission channel.

[0418] Continuous data transmission.

[0419] Steps 7-12: The network function entity that provides the data is based on the request and response data.

[0420] It should be noted that in the various embodiments of this disclosure, the same data session may include the simultaneous uplink and downlink support of Examples 1, 2 and 4.

[0421] It should be noted that in the various embodiments of this disclosure, the number of terminals, base stations, and data execution function entities involved in the same data session can be 0, 1, or more.

[0422] It should be noted that in the various embodiments of this disclosure, the data execution nodes involved in multiple data services of the same data session may not be completely consistent. For example, data service 1 may request to obtain data from terminal 1 and terminal 2, while data service 2 may only request to obtain data from terminal 2.

[0423] It should be noted that in the various embodiments of this disclosure, the data session can involve multiple terminals (i.e., the data receiving endpoint / entity or the data sending endpoint / entity can be two or more of the following: terminal, base station, core network element, orchestration management function, and application function).

[0424] It should be noted that in Examples 1, 2, and 4, the data sending endpoint / entity can be both a terminal and a base station. For example, by collaboratively analyzing the environmental sensing data collected simultaneously by the terminal and the base station, a complete sensing result can be obtained. Alternatively, the data sending endpoint / entity can be multiple core network elements, for example, multiple network elements can collaborate to obtain more comprehensive network status information.

[0425] It should be noted that the technical solutions disclosed herein are not limited to the use of a session mechanism, but also include other similar processes and forms besides the session mechanism. The technical solutions disclosed herein are particularly suitable for large-scale data transmission scenarios, such as AI training data, AI model data, and synesthetic data, and of course, they can also be applied to a wider range of other scenarios, which are not limited in this respect.

[0426] Figure 9 is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure. As shown in Figure 9, the terminal includes a memory 920, a transceiver 910, and a processor 900; wherein the processor 900 and the memory 920 may also be physically arranged separately.

[0427] The memory 920 is used to store computer programs; the transceiver 910 is used to send and receive data under the control of the processor 900.

[0428] In Figure 9, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 900 and memory represented by memory 920. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described in detail herein. The bus interface provides an interface. The transceiver 910 may be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 930 may also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0429] The processor 900 is responsible for managing the bus architecture and general processing, while the memory 920 can store the data used by the processor 900 during operation.

[0430] The processor 900 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0431] The processor 900 executes any of the data transmission methods provided in the embodiments of this disclosure by calling a computer program stored in the memory 920 in accordance with the obtained executable instructions.

[0432] Figure 10 is a schematic diagram of the structure of the data session management function entity provided in the embodiment of this disclosure. As shown in Figure 10, the data session management function entity includes a memory 1020, a transceiver 1010 and a processor 1000; wherein, the processor 1000 and the memory 1020 can also be physically arranged separately.

[0433] The memory 1020 is used to store computer programs; the transceiver 1010 is used to send and receive data under the control of the processor 1000.

[0434] In Figure 10, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1000 and memory represented by memory 1020. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described in detail herein. A bus interface provides an interface. Transceiver 1010 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0435] The processor 1000 is responsible for managing the bus architecture and general processing, while the memory 1020 can store the data used by the processor 1000 when performing operations.

[0436] The processor 1000 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.

[0437] The processor 1000 executes any of the data session management methods provided in the embodiments of this disclosure by calling a computer program stored in the memory 1020 in accordance with the obtained executable instructions.

[0438] It should be noted that the terminal and data session management function entity provided in this embodiment can implement all the method steps implemented in the corresponding method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0439] The apparatus provided in the embodiments of this disclosure is described below, and the apparatus described below can be referred to in correspondence with the method described above.

[0440] Figure 11 is a schematic diagram of the data transmission device provided in an embodiment of this disclosure. As shown in Figure 11, the device includes:

[0441] The first sending unit 1110 is used to send a first request message to the first network function entity based on the service requirements of the data service. The first request message is used to trigger the network to create a new data session for the data service or modify an existing data session.

[0442] The data transmission unit 1120 is used to transmit data for data services by creating or modifying data sessions based on the network.

[0443] In some embodiments, the first request message is a first data session establishment or modification request message, which includes one or more of the following information:

[0444] Data session type;

[0445] Data session identifier;

[0446] Business continuity model;

[0447] Data parameters.

[0448] In some embodiments, the first request message is a service request message or a data service request message, and the service request message or data service request message contains one or more of the following information:

[0449] Data service types;

[0450] Business continuity model;

[0451] Data parameters.

[0452] In some embodiments, the data parameters include one or more of the following:

[0453] Data volume;

[0454] Data message type;

[0455] List of data service agreements;

[0456] Data transmission method;

[0457] Data type;

[0458] Data function types;

[0459] Data transmission direction.

[0460] In some embodiments, the first request message may further include one or more of the following: Protocol Data Unit (PDU) session identifier, data service identifier, and data service network identifier.

[0461] In some embodiments, the device further includes:

[0462] The first receiving unit is used to receive a second data session establishment or modification request message from the data session management function entity. The second data session establishment or modification request message contains configuration instructions related to data services.

[0463] The data operation unit is used to perform data operations related to data services based on configuration instructions.

[0464] In some embodiments, data operations include one or more of the following: data acquisition operations, data transmission operations, data reception operations, data processing operations, and data storage operations.

[0465] Figure 12 is a schematic diagram of the data session management device provided in an embodiment of this disclosure. As shown in Figure 12, the device includes:

[0466] The second receiving unit 1210 is used to receive a second request message, which is a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message.

[0467] Execution unit 1220 is configured to perform one or more of the following operations based on the second request message:

[0468] Create a new data session for data services or modify an existing data session;

[0469] Identify the PDU sessions associated with data services;

[0470] Select data execution nodes for data services.

[0471] In some embodiments, receiving a second request message includes:

[0472] The receiving terminal sends a first data session establishment or modification request message or a data service request message; or,

[0473] Receive a data session context establishment or modification request message or a data service request message sent by the first network function entity; or

[0474] Receive data service request messages sent by the data service requester.

[0475] In some embodiments, the second request message includes one or more of the following: PDU session identifier, data service identifier, and data service network identifier.

[0476] In some embodiments, selecting a data execution node for a data service includes:

[0477] Based on the service requirements of data services, as well as the network identifier of data services and / or the context information of PDU sessions associated with data services, a data execution node is selected.

[0478] In some embodiments, the device further includes:

[0479] The path construction unit is used to organize the selected data execution nodes in an orderly manner and construct the data service transmission path based on the business processing logic of data services.

[0480] In some embodiments, constructing a data service transmission path includes:

[0481] Send a second data session establishment or modification request message to the data execution node. The second data session establishment or modification request message contains configuration instructions related to data services. The configuration instructions are used to indicate data operations related to data services.

[0482] In some embodiments, the data execution node includes one or more of a terminal, an access network entity, and a core network functional entity, and the number of each type of data execution node is one or more.

[0483] In some embodiments, the data service transmission path includes one or more of the following:

[0484] The data service transmission path between the terminal and the access network entity;

[0485] Data service transmission path between the terminal and core network functional entities;

[0486] Data service transmission path between access network entities and core network functional entities;

[0487] Data service transmission path between terminals, access network entities, and core network functional entities;

[0488] Data service transmission path between terminals;

[0489] Data service transmission paths between access network entities;

[0490] Data service transmission paths between core network functional entities.

[0491] In some embodiments, the device further includes:

[0492] The second sending unit is used to send a first data session establishment request message to the first data execution node. The first data session establishment request message contains data transmission protocol information. The first data execution node is a network-side node that provides data.

[0493] In some embodiments, the device further includes:

[0494] The third receiving unit is used to receive the address information of the data providing channel sent by the first data execution node;

[0495] The third sending unit is used to send a second data session establishment request message to the second data execution node. The second data session establishment request message contains the address information of the data provision channel. The second data execution node is the node that receives the data.

[0496] In some embodiments, the first data session establishment request message further includes information about a second data execution node, which is a node that receives data.

[0497] In some embodiments, the device further includes:

[0498] The fourth sending unit is used to send a third data session establishment request message to the second data execution node. The third data session establishment request message contains the address information of the data provision channel; the second data execution node is the node receiving the data.

[0499] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the corresponding method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0500] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0501] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0502] On the other hand, embodiments of this disclosure also provide a processor-readable storage medium storing a program for causing a processor to execute the data transmission method or data session management method provided in the above embodiments.

[0503] It should be noted that the processor-readable storage medium provided in this embodiment can implement all the method steps implemented in the corresponding method embodiments described above, and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0504] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0505] The technical solutions provided in this disclosure can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as an Evolved Packet Core (EPC), a 5G core network (5GC), or a 6G core network.

[0506] The terminals disclosed in this embodiment can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminals may differ in different systems; for example, in a 5G system, a terminal may be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments disclosed herein.

[0507] The access network entity involved in this disclosure can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The access network entity can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The access network entity can also coordinate the attribute management of the air interface. For example, the access network entity involved in this disclosure can be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB) in Wide-band Code Division Multiple Access (WCDMA), an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in this disclosure. In some network structures, the access network entity may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0508] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0509] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0510] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0511] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0512] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A data transmission method, applied to a terminal, comprising: Based on the service requirements of the data service, a first request message is sent to the first network function entity. The first request message is used to trigger the network to create a new data session for the data service or modify an existing data session. Based on the network, a new or modified data session is created for the data service, and the data service is transmitted.

2. The data transmission method according to claim 1, wherein, The first request message is a first data session establishment or modification request message, which includes one or more of the following information: Data session type; Data session identifier; Business continuity model; Data parameters.

3. The data transmission method according to claim 1, wherein, The first request message is a service request message or a data service request message, and the service request message or the data service request message contains one or more of the following information: Data service types; Business continuity model; Data parameters.

4. The data transmission method according to claim 2 or 3, wherein, The data parameters include one or more of the following: Data volume; Data message type; List of data service agreements; Data transmission method; Data type; Data function types; Data transmission direction.

5. The data transmission method according to claim 2 or 3, wherein, The first request message also includes one or more of the following: Protocol Data Unit (PDU) session identifier, data service identifier, and data service network identifier.

6. The data transmission method according to any one of claims 1 to 3, wherein, The method further includes: Receive a second data session establishment or modification request message from the data session management function entity, the second data session establishment or modification request message containing configuration instructions related to the data service; Based on the configuration instructions, perform data operations related to the data service.

7. The data transmission method according to claim 6, wherein, The data operations include one or more of the following: data acquisition operations, data transmission operations, data reception operations, data processing operations, and data storage operations.

8. A data session management method, applied to a data session management function entity, comprising: Receive a second request message, which is a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message; Based on the second request message, perform one or more of the following operations: Create a new data session for data services or modify an existing data session; Identify the PDU sessions associated with data services; Select data execution nodes for data services.

9. The data session management method according to claim 8, wherein, The receiving of the second request message includes: The receiving terminal sends a first data session establishment or modification request message or a data service request message; or, Receive a data session context establishment or modification request message or a data service request message sent by the first network function entity; or Receive data service request messages sent by the data service requester.

10. The data session management method according to claim 8 or 9, wherein, The second request message contains one or more of the following: PDU session identifier, data service identifier, and data service network identifier.

11. The data session management method according to claim 8, wherein, The selection of data execution nodes for data services includes: Based on the service requirements of the data service, and the context information of the data service network identifier and / or the PDU session associated with the data service, a data execution node is selected.

12. The data session management method according to claim 8 or 11, wherein, The method further includes: Based on the business processing logic of the data service, the selected data execution nodes are organized in an orderly manner to construct the data service transmission path.

13. The data session management method according to claim 12, wherein, The constructed data service transmission path includes: A second data session establishment or modification request message is sent to the data execution node. The second data session establishment or modification request message contains configuration instructions related to the data service. The configuration instructions are used to indicate data operations related to the data service.

14. The data session management method according to claim 12, wherein, The data execution node includes one or more of the following: terminal, access network entity, and core network functional entity, and the number of each type of data execution node is one or more.

15. The data session management method according to claim 14, wherein, The data service transmission path includes one or more of the following: The data service transmission path between the terminal and the access network entity; Data service transmission path between the terminal and core network functional entities; Data service transmission path between access network entities and core network functional entities; Data service transmission path between terminals, access network entities, and core network functional entities; Data service transmission path between terminals; Data service transmission paths between access network entities; Data service transmission paths between core network functional entities.

16. The data session management method according to claim 8 or 11, wherein, The method further includes: A first data session establishment request message is sent to the first data execution node. The first data session establishment request message contains data transmission protocol information. The first data execution node is a network-side node that provides data.

17. The data session management method according to claim 16, wherein, The method further includes: Receive the address information of the data provision channel sent by the first data execution node; A second data session establishment request message is sent to the second data execution node. The second data session establishment request message contains the address information of the data providing channel. The second data execution node is the node that receives the data.

18. The data session management method according to claim 16, wherein, The first data session establishment request message also includes information about the second data execution node, which is the node that receives the data.

19. The data session management method according to claim 8 or 11, wherein, The method further includes: A third data session establishment request message is sent to the second data execution node. The third data session establishment request message contains the address information of the data provision channel; the second data execution node is the node receiving the data.

20. A terminal, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Based on the service requirements of the data service, a first request message is sent to the first network function entity. The first request message is used to trigger the network to create a new data session for the data service or modify an existing data session. Based on the network, a new or modified data session is created for the data service, and the data service is transmitted.

21. A data session management function entity, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Receive a second request message, which is a data session establishment or modification request message, a data session context establishment or modification request message, or a data service request message; Based on the second request message, perform one or more of the following operations: Create a new data session for data services or modify an existing data session; Identify the PDU sessions associated with data services; Select data execution nodes for data services.

22. A processor-readable storage medium storing a program for causing a processor to perform the method of any one of claims 1 to 7, or to perform the method of any one of claims 8 to 19.

Images