A data transmission method and device, a network device, a storage medium and a program product

Abstract

The application discloses a data transmission method and device, a network device, a storage medium and a program product. The method comprises the following steps: a first network device sends a data channel establishment request to a second network device, wherein the data channel establishment request is used for requesting to establish a data channel between the first network device and the second network device; wherein one of the first network device and the second network device is a RAN node, and the other is a core network node; the first network device receives a data channel establishment response sent by the second network device, wherein the data channel establishment response comprises a data channel ID of establishment success or a data channel ID of establishment failure.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method and apparatus, network equipment, storage medium, and program product. Background Technology

[0002] Currently, the establishment of a data channel from User Equipment (UE) to Radio Access Network (RAN), then to User Plane Function (UPF), and finally to Data Network (DN) is achieved through the Protocol Data Unit (PDU) session resource establishment process. This data channel is bound to a specific UE, meaning that the data channel is used for data transmission of a specific UE and is not suitable for data transmission unrelated to the UE.

[0003] With the development of wireless communication technology, the sixth generation (6G) mobile communication technology is under development. Looking towards the future of 6G, the network will support new services such as Artificial Intelligence (AI) and sensing. These new services require the transmission of a large amount of user-unrelated data between the RAN and the core network (CN). The data channels established using the current method cannot meet the data transmission needs between the RAN and CN that are independent of the user. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of this application provide a data transmission method and apparatus, a network device, a computer storage medium, and a computer program product.

[0005] The data transmission method provided in this application includes:

[0006] A first network device sends a data channel establishment request to a second network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0007] The first network device receives a data channel establishment response sent by the second network device, the data channel establishment response including a data channel identifier (ID) for successful establishment or a data channel ID for failed establishment.

[0008] The data transmission method provided in this application includes:

[0009] The second network device receives a data channel establishment request sent by the first network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0010] The second network device sends a data channel establishment response to the first network device, the data channel establishment response including a successfully established data channel ID or a failed data channel ID.

[0011] The data transmission apparatus provided in this application embodiment is applied to a first network device, and the apparatus includes:

[0012] The first sending unit is configured to send a data channel establishment request to the second network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0013] The first receiving unit is configured to receive a data channel establishment response sent by the second network device, wherein the data channel establishment response includes a data channel ID that was successfully established or a data channel ID that failed to be established.

[0014] The data transmission apparatus provided in this application embodiment is applied to a second network device, and the apparatus includes:

[0015] The second receiving unit is configured to receive a data channel establishment request sent by the first network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. In this case, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0016] The second sending unit is used to send a data channel establishment response to the first network device. The data channel establishment response includes a data channel ID that was successfully established or a data channel ID that failed to be established.

[0017] The network device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the above-described data transmission methods.

[0018] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute any of the above-described data transmission methods.

[0019] The computer program product provided in this application includes computer program instructions that cause a computer to execute any of the above-described data transmission methods.

[0020] In the technical solution of this application embodiment, one of the first network device and the second network device is a RAN node, and the other network device is a core network node. Through the interaction between the first network device and the second network device, a data channel is established between the RAN and the core network. Since the establishment of this data channel does not involve the UE, the data channel can meet the data transmission needs between the RAN and the core network that are unrelated to the UE. Attached Figure Description

[0021] Figure 1(a) is a schematic diagram of the NG-U protocol stack;

[0022] Figure 1(b) is a schematic diagram of the NG-C protocol stack;

[0023] Figure 2 This is a schematic diagram of the PDU session resource establishment process;

[0024] Figure 3 This is a schematic flowchart of the data transmission method provided in an embodiment of this application;

[0025] Figure 4 This is a flowchart illustrating the data transmission method provided in the embodiments of this application. Figure 2 ;

[0026] Figure 5 This is a flowchart illustrating the data transmission method provided in the embodiments of this application. Figure 3 ;

[0027] Figure 6 This is a schematic diagram of the structure of the data transmission device provided in the embodiments of this application;

[0028] Figure 7 This is a schematic diagram of the structure of the data transmission device provided in the embodiments of this application. Figure 2 ;

[0029] Figure 8 This is a schematic structural diagram of a network device provided in an embodiment of this application;

[0030] Figure 9 This is a schematic structural diagram of the chip according to an embodiment of this application. Detailed Implementation

[0031] It should be noted that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "indication" mentioned in this article can be direct indication, indirect indication, or an indication of a related relationship. For example, A indicating B can mean that A directly indicatives B, for example, B can be obtained through A; it can also mean that A indirectly indicatives B, for example, A indicatives C, B can be obtained through C; or it can mean that there is a related relationship between A and B.

[0032] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application will be described below.

[0033] 1. NG Interface Protocol Stack

[0034] The NG interface refers to the interface between the RAN and the core network. The NG interface is divided into the NG user plane (NG-U) interface and the NG control plane (NG-C) interface. The protocol stack corresponding to the NG-U interface is called the NG-U protocol stack, and the protocol stack corresponding to the NG-C interface is called the NG-C protocol stack.

[0035] In 5G, the NG-U protocol stack between the RAN and UPF is shown in Figure 1(a). From bottom to top, it includes the following protocol layers: Physical Layer, Data Link Layer, IP Layer, User Datagram Protocol (UDP) Layer, GPRS Tunneling Protocol User Plane (GTP-U) Layer, and User Plane PDUs. The NG-U protocol stack provides user data transmission functions between the RAN and UPF. The transport network layer (including the physical layer and data link layer) is based on IP and uses the GTP-U layer above UDP / IP to transmit PDUs between the RAN and UPF.

[0036] In 5G, the NG-C protocol stack between the RAN and the Access and Mobility Management Function (AMF) is shown in Figure 1(b). From bottom to top, it includes the following protocol layers: Physical Layer, Data Link Layer, IP Layer, Stream Control Transmission Protocol (SCTP) Layer, and Next Generation Application Protocol (NG-AP) Layer. The transport network layer (including the physical layer and data link layer) is based on IP, and the SCTP layer is used on top of IP to provide reliable signaling transmission. The signaling transmitted through the NG-C interface includes UE-related signaling and non-UE-related signaling, which are used to provide functions such as NG interface management, UE context management, and PDU session management.

[0037] 2. PDU Session Resource Management

[0038] PDU session resource management includes PDU session resource creation, PDU session resource release, and PDU session resource modification. For example... Figure 2 As shown, Figure 2 This diagram illustrates the PDU session resource establishment process. The AMF sends a PDU session resource establishment request to the next-generation RAN (NG-RAN) node. After receiving the PDU session resource establishment request, the NG-RAN node sends a PDU session resource establishment response to the AMF, thereby establishing the PDU session resource.

[0039] The PDU session resource establishment process is used to allocate corresponding resources for one or more PDU sessions and corresponding Quality of Service (QoS) flows for the UE on the Uu interface (the interface between the UE and the RAN) and the NG-U interface (the interface between the RAN and the UPF), and to establish the corresponding Data Radio Bearer (DRB). Messages in this PDU session resource establishment process (such as PDU session resource establishment requests and PDU session resource establishment responses) are implemented using UE-related signaling. The RAN obtains the uplink transport address of the PDU session user data based on the user plane transport layer information in the PDU session establishment request message, and carries the user plane transport layer information used by the PDU session through the PDU session resource establishment response message.

[0040] 3. GTP-U header format

[0041] The general GTP-U packet header format is shown in Table 1 below, which includes the following information: Version, Message Type, Length, Tunnel Endpoint Identifier, Sequence Number, N-PDU Number, and Next ExtensionHeader Type.

[0042]

[0043] Table 1: GTP-U header format

[0044] To support the transmission of 5G PDU session parameters, better process user plane data, and meet performance requirements, a PDU Session Container extension header is defined in related technologies for G-PDUs on N3 and N9 user plane interfaces. The format of the downlink PDU Session Container extension header is shown in Table 2 below, including the following information: PDU Type, QMP, SNP, MSNP, Spare, PPP, RQI, QoS Flow Identifier, PPI, Downlink Sending Time Stamp, Downlink QFI Sequence Number, Downlink MBS QFI Sequence Number, and Padding.

[0045]

[0046] Table 2: Downlink PDU Session Container Extension Header Format

[0047] In the aforementioned related technologies, the data channel from UE to RAN to UPF to DN is established through the PDU session resource establishment process. This data channel is bound to a specific UE, meaning that it is used for data transmission of that specific UE and is not applicable to data transmission unrelated to the UE. Messages related to the PDU session may include the user's IP information, QoS information, destination address, etc., all of which are specific to the UE. Therefore, the PDU session is a session specific to a particular UE.

[0048] Looking towards 6G, networks will support new services such as AI and sensing, which may require the transmission of large amounts of data between the RAN and the core network. For example, multiple base stations may upload data to the core network for AI model training and inference; base stations may upload sensing results to the core network for collaborative sensing; and the core network may transmit AI models to base stations to utilize their computing power for computation. These processes require the transmission of large amounts of data between the RAN and the core network. This data is typically unrelated to any specific UE and is unsuitable for transmission using user plane data channels oriented towards PDU sessions. Although the NG-AP protocol supports the transmission of non-UE-related signaling, it struggles to handle large volumes of non-UE-related data transmission.

[0049] Therefore, in order to meet the non-UE-related data transmission requirements between the RAN and the core network, the technical solution of this application proposes a UE-independent data channel between the RAN and the core network to meet the efficient transmission of UE-independent data.

[0050] It should be noted that the data channel described in this embodiment refers to the user plane transmission channel between the first network device and the second network device, that is, the two ends of the data channel are the first network device and the second network device. The first network device and / or the second network device includes a data generation module / data processing module, or is connected to a data generation module / data processing module.

[0051] In some implementations, the first network device includes / is connected to a data processing module (also referred to as a processing module), and the second network device includes / is connected to a data generation module (also referred to as a generation module). The second network device generates data through the data generation module and sends the data to the first network device through a data channel; after receiving the data sent by the second network device, the first network device routes the data to the corresponding data processing module for processing.

[0052] In some implementations, the second network device includes / is connected to a data processing module (also referred to as a processing module), and the first network device includes / is connected to a data generation module (also referred to as a generation module). The first network device generates data through the data generation module and sends the data to the second network device through a data channel; after receiving the data sent by the first network device, the second network device routes the data to the corresponding data processing module for processing.

[0053] It should be noted that the data channel described in this application embodiment is a UE-independent data channel, which does not involve the establishment of radio bearers and related resources between the UE and the RAN node.

[0054] It should be noted that, in the embodiments of this application, one of the first network device and the second network device described is a RAN node, and the other network device is a core network node.

[0055] In some implementations, the first network device is a RAN node, and the second network device is a core network node. Accordingly, the data channel establishment request / data channel release request is initiated by the RAN node (or RAN).

[0056] In other implementations, the first network device is a core network node, and the second network device is a RAN node. Accordingly, the data channel establishment request / data channel release request is initiated by the core network node (or the core network).

[0057] It should be noted that the description of "node" in this application embodiment can also be replaced with "device", "network element", "network function", or "functional entity", etc.

[0058] It should be noted that the RAN node described in the embodiments of this application can be a base station. The core network node described in the embodiments of this application can be a UPF or other user plane network element.

[0059] Figure 3 This is a schematic flowchart of the data transmission method provided in this application embodiment, as shown below. Figure 3 As shown, the data transmission method includes the following steps:

[0060] Step 301: The first network device sends a data channel establishment request to the second network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0061] In some implementations, the data channel establishment request includes one or more of the following information: data channel ID, data type transmitted by the data channel, task ID corresponding to the data transmitted by the data channel, first transport layer information associated with the data channel, data requirements transmitted by the data channel, and encryption information of the data transmitted by the data channel; wherein, the first transport layer information includes a first IP address and / or a first tunnel endpoint identifier (TEID) assigned by the first network device; wherein, the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

[0062] The "Data Channel ID" in the data channel establishment request represents the identifier of the data channel to be established. The Data Channel ID is used to uniquely identify the data channel, facilitating subsequent data transmission and management related to that data channel (such as data channel release).

[0063] The "data type" in the data channel establishment request represents the type of data to be transmitted or the type of data to be transmitted through the requested data channel. The data type is related to the nature of the data or the task it corresponds to. For example, data types are categorized as AI model data, perception data, etc. AI model data can correspond to tasks such as model training / update or model inference, while perception data can correspond to perception tasks (such as perception data collection, target tracking, or environmental perception).

[0064] The "Task ID" in the data channel establishment request represents the task ID corresponding to the data to be transmitted through the requested data channel. The Task ID identifies a specific type of task, such as a model update task or a sensor data collection task.

[0065] The "first transport layer information" in the data channel establishment request includes a first IP address and / or a first TEID assigned by the first network device; wherein the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

[0066] The "data requirements" in the data channel establishment request include, for example, data accuracy requirements and data timeliness requirements.

[0067] The "encryption information of the data" in the data channel establishment request includes, for example, indications of whether the data is encrypted, encryption parameters, encryption algorithms, etc.

[0068] Step 302: The first network device receives a data channel establishment response sent by the second network device. The data channel establishment response includes a data channel ID that indicates successful establishment or a data channel ID that indicates failed establishment.

[0069] If the data channel is successfully established, the data channel establishment response includes a successfully established data channel ID. In some implementations, if the data channel establishment response includes a successfully established data channel ID, the data channel establishment response also includes second transport layer information associated with the data channel; wherein the second transport layer information includes a second IP address and / or a second TEID assigned by the second network device; wherein the second IP address and / or the second TEID is used by the second network device to receive data sent by the first network device.

[0070] In the event that data channel establishment fails, the data channel establishment response includes the ID of the failed data channel. In some implementations, if the data channel establishment response includes the ID of the failed data channel, the data channel establishment response also includes the reason for the data channel establishment failure.

[0071] In the embodiments of this application, the data channel establishment request / data channel establishment response can be carried in an existing signaling message or sent through a separate signaling message.

[0072] In some implementations, the data transmitted via the data channel is encapsulated in a GTP-U PDU, wherein the GTP-U PDU has a first extended header, which includes the data type and / or task ID corresponding to the data.

[0073] Here, considering that the same data channel may transmit data of different types and / or belonging to different tasks, the GTP-U PDU carries a newly defined first extended header in addition to the packet header (the packet header format can be referred to the GTP-U packet header format shown in Table 1 above). The first extended header may be, but is not limited to, called the RAN-CN Data Extension Header. The GTP-U PDU is used for non-UE related data transmission between the RAN and the core network.

[0074] Referring to Table 3 below, the first extended header includes a Data Type field indicating the data type transmitted by the GTP-U PDU, and a TaskID field indicating the task identifier corresponding to the GTP-U PDU. This supports the transmission of different types of data and / or data belonging to different tasks on the same data channel. This design also supports collaborative processing of multi-node tasks. Specifically, multiple nodes can collaboratively process data of the same data type based on the Data Type field, or data with the same task identifier based on the Task ID field. In Table 3, the Data Type field occupies 8 bits. Data Type = 00000001 can be predefined to indicate that the data type transmitted by the GTP-U PDU is AI data, Data Type = 00000010 indicates that the data type transmitted by the GTP-U PDU is perception data, and Data Type = 00000011 indicates that the data transmitted by the GTP-U PDU is status monitoring data. It should be noted that Table 3 is only an example; the number of bits occupied by the Data Type field and the Task ID field can be more or less than 8 bits.

[0075]

[0076] Table 3: First Extended Packet Header Format

[0077] In some embodiments, the method further includes: a first network device receiving a GTP-U PDU sent by a second network device through a data channel, wherein the GTP-U PDU encapsulates data; the first network device parsing the first extended header of the GTP-U PDU and routing the data to a target processing module for processing according to the data type and / or task ID in the first extended header.

[0078] It should be noted that the number of second network devices can be one or more.

[0079] In one example, there are two network devices: network device 1 corresponds to the first network device, and network devices 2 and 3 correspond to the second network devices. Assume that network device 1 needs to receive data from network devices 2 and 3 to complete the target task. After network device 1 establishes data channels with network devices 2 and 3 respectively, the following data transmission process begins:

[0080] 1. Network devices 2 and 3, based on the data type and task ID carried in the data channel establishment request, as well as the first transport layer information (i.e., the first IP address and / or first TEID allocated by the first network device), encapsulate the data to be transmitted into a GTP-U PDU and send it to network device 1. The GTP-U PDU carries the data in its payload, as well as the data type and task ID in its first extension header. Furthermore, the first transport layer information (i.e., the first IP address and / or first TEID allocated by the first network device) is also carried in the extension header. This first transport layer information guides the transmission of the GTP-U PDU to network device 1.

[0081] 2. After receiving GTP-U PDUs from Network Devices 2 and 3, Network Device 1 parses the packet header and the first extended packet header of the GTP-U PDU. Based on the data type and / or task ID in the first extended packet header, it routes the data packet to the corresponding processing module for processing. Here, different data types and / or task IDs are associated with different processing modules. For example, an AI data / model update task is associated with an AI model update module, and a perception data / perception data analysis task is associated with a perception data analysis module. Based on this, data packets can be routed to the corresponding processing modules for processing according to the data type and / or task ID; the corresponding processing modules then collaboratively process the data from different devices (i.e., Network Devices 2 and 3).

[0082] The technical solution of this application embodiment establishes a data channel between the RAN and the core network through the interaction of data channel establishment requests and responses between the first network device and the second network device. Since the establishment of this data channel does not involve the UE, it is not limited by any specific UE and is not bound to a radio bearer, thus adapting to a wider range of application scenarios and meeting the UE-independent data transmission needs between the RAN and the core network. Furthermore, the technical solution of this application embodiment allows both the RAN and the core network to initiate data channel establishment requests as needed, thereby meeting diverse service requirements.

[0083] Figure 4 This is a flowchart illustrating the data transmission method provided in the embodiments of this application. Figure 2 It should be noted that, Figure 4 The relevant solutions can be implemented independently or in conjunction with... Figure 3 The relevant solutions are implemented in combination; when Figure 4 Related solutions and Figure 3 When related solutions are implemented in combination, Figure 4 The relevant solutions can be implemented in Figure 3 Following the relevant plan; such as Figure 4 As shown, the data transmission method includes the following steps:

[0084] Step 401: The first network device sends a data channel release request to the second network device. The data channel release request is used to request the release of the data channel between the first network device and the second network device.

[0085] In some implementations, the data channel release request includes a data channel ID. Here, the "data channel ID" in the data channel release request represents the identifier of the data channel to be released. The data channel ID is used to uniquely identify the data channel, ensuring that the first network device and the second network device accurately identify and release the correct data channel.

[0086] It should be noted that the released data channel is the previously established data channel. In some implementations, this can be achieved through the above... Figure 3 The relevant scheme establishes a data channel between the first network device and the second network device.

[0087] Step 402: The first network device receives the data channel release response sent by the second network device.

[0088] In some implementations, if the data channel is released successfully, the data channel release response includes the data channel ID that was successfully released.

[0089] In some implementations, in the event that releasing the data channel fails, the data channel release response includes the data channel ID that failed to be released.

[0090] In this application embodiment, the data channel release request / data channel release response can be sent in an existing signaling message or sent through a separate signaling message.

[0091] The technical solution of this application embodiment realizes the release of data channels between the RAN and the core network through the interaction of data channel release request and data channel release response between the first network device and the second network device, thereby achieving effective management of data channels.

[0092] Figure 5 This is a flowchart illustrating the data transmission method provided in the embodiments of this application. Figure 3 ,like Figure 5 As shown, the data transmission method includes the following steps:

[0093] Step 501: The second network device receives a data channel establishment request sent by the first network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0094] In some implementations, the data channel establishment request includes one or more of the following information: data channel ID, data type transmitted by the data channel, task ID corresponding to the data transmitted by the data channel, first transport layer information associated with the data channel, data requirements transmitted by the data channel, and encryption information of the data transmitted by the data channel; wherein, the first transport layer information includes a first IP address and / or a first tunnel endpoint identifier (TEID) assigned by the first network device; wherein, the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

[0095] The "Data Channel ID" in the data channel establishment request represents the identifier of the data channel to be established. The Data Channel ID is used to uniquely identify the data channel, facilitating subsequent data transmission and management related to that data channel (such as data channel release).

[0096] The "data type" in the data channel establishment request represents the type of data to be transmitted or the type of data to be transmitted through the requested data channel. The data type is related to the nature of the data or the task it corresponds to. For example, data types are categorized as AI model data, perception data, etc. AI model data can correspond to tasks such as model training / update or model inference, while perception data can correspond to perception tasks (such as perception data collection, target tracking, or environmental perception).

[0097] The "Task ID" in the data channel establishment request represents the task ID corresponding to the data to be transmitted through the requested data channel. The Task ID identifies a specific type of task, such as a model update task or a sensor data collection task.

[0098] The "first transport layer information" in the data channel establishment request includes a first IP address and / or a first TEID assigned by the first network device; wherein the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

[0099] The "data requirements" in the data channel establishment request include, for example, data accuracy requirements and data timeliness requirements.

[0100] The "encryption information of the data" in the data channel establishment request includes, for example, indications of whether the data is encrypted, encryption parameters, encryption algorithms, etc.

[0101] Step 502: The second network device sends a data channel establishment response to the first network device. The data channel establishment response includes the data channel ID of successful establishment or the data channel ID of failed establishment.

[0102] If the data channel is successfully established, the data channel establishment response includes a successfully established data channel ID. In some implementations, if the data channel establishment response includes a successfully established data channel ID, the data channel establishment response also includes second transport layer information associated with the data channel; wherein the second transport layer information includes a second IP address and / or a second TEID assigned by the second network device; wherein the second IP address and / or the second TEID is used by the second network device to receive data sent by the first network device.

[0103] In the event that data channel establishment fails, the data channel establishment response includes the ID of the failed data channel. In some implementations, if the data channel establishment response includes the ID of the failed data channel, the data channel establishment response also includes the reason for the data channel establishment failure.

[0104] In the embodiments of this application, the data channel establishment request / data channel establishment response can be carried in an existing signaling message or sent through a separate signaling message.

[0105] In some implementations, the data transmitted via the data channel is encapsulated in a GTP-U PDU, wherein the GTP-U PDU has a first extended header, which includes the data type and / or task ID corresponding to the data.

[0106] Here, considering that the same data channel may transmit data of different types and / or belonging to different tasks, the GTP-U PDU carries a newly defined first extended header in addition to the packet header (the packet header format can be referred to the GTP-U packet header format shown in Table 1 above). The first extended header may be, but is not limited to, called RAN-CN Data ExtensionHeader. The GTP-U PDU is used for non-UE related data transmission between the RAN and the core network.

[0107] In some embodiments, the method further includes: the second network device encapsulating the data to be transmitted in a GTP-UPDU, and encapsulating the data type and / or task ID corresponding to the data in the first extended packet header of the GTP-UPDU; the second network device sending the GTP-UPDU to the first network device through the data channel.

[0108] The technical solution of this application embodiment establishes a data channel between the RAN and the core network through the interaction of data channel establishment requests and responses between the first network device and the second network device. Since the establishment of this data channel does not involve the UE, it is not limited by any specific UE and is not bound to a radio bearer, thus adapting to a wider range of application scenarios and meeting the UE-independent data transmission needs between the RAN and the core network. Furthermore, the technical solution of this application embodiment allows both the RAN and the core network to initiate data channel establishment requests as needed, thereby meeting diverse service requirements.

[0109] In some embodiments, the method further includes: a second network device receiving a data channel release request sent by a first network device, the data channel release request being used to request the release of a data channel between the first network device and the second network device; and the second network device sending a data channel release response to the first network device.

[0110] In some implementations, the data channel release request includes a data channel ID. Here, the "data channel ID" in the data channel release request represents the identifier of the data channel to be released. The data channel ID is used to uniquely identify the data channel, ensuring that the first network device and the second network device accurately identify and release the correct data channel.

[0111] In some implementations, if the data channel release is successful, the data channel release response includes the ID of the successfully released data channel. If the data channel release fails, the data channel release response includes the ID of the failed data channel.

[0112] In this application embodiment, the data channel release request / data channel release response can be sent in an existing signaling message or sent through a separate signaling message.

[0113] The technical solution of this application embodiment realizes the release of data channels between the RAN and the core network through the interaction of data channel release request and data channel release response between the first network device and the second network device, thereby achieving effective management of data channels.

[0114] Figure 6 This is a schematic diagram of the structure of the data transmission device provided in this application embodiment, applied to a first network device, such as... Figure 6 As shown, the data transmission device includes:

[0115] The first sending unit 601 is used to send a data channel establishment request to the second network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node and the other network device is a core network node.

[0116] The first receiving unit 602 is configured to receive a data channel establishment response sent by the second network device, wherein the data channel establishment response includes a data channel ID that was successfully established or a data channel ID that failed to be established.

[0117] In some implementations, the data channel establishment request includes one or more of the following information: data channel ID, data type transmitted by the data channel, task ID corresponding to the data transmitted by the data channel, first transport layer information associated with the data channel, data requirements for the data transmitted by the data channel, and encryption information for the data transmitted by the data channel.

[0118] The first transport layer information includes a first IP address and / or a first TEID allocated by the first network device; wherein the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

[0119] In some implementations, if the data channel establishment response includes a successfully established data channel ID, then the data channel establishment response further includes second transport layer information associated with the data channel; wherein the second transport layer information includes a second IP address and / or a second TEID allocated by the second network device; wherein the second IP address and / or the second TEID is used by the second network device to receive data sent by the first network device; or, if the data channel establishment response includes a failed data channel ID, then the data channel establishment response further includes a reason for the data channel establishment failure.

[0120] In some embodiments, the first sending unit 601 is configured to send a data channel release request to the second network device, the data channel release request being used to request the release of the data channel between the first network device and the second network device;

[0121] The first receiving unit 602 is used to receive the data channel release response sent by the second network device.

[0122] In some implementations, the data channel release request includes a data channel ID.

[0123] In some implementations, the data transmitted by the data channel is encapsulated in a GTP-U PDU, wherein the GTP-U PDU has a first extended header, which includes the data type and / or task ID corresponding to the data.

[0124] In some embodiments, the first receiving unit 602 is configured to receive a GTP-U PDU sent by the second network device through the data channel, wherein the GTP-U PDU encapsulates data.

[0125] The device further includes a first processing unit 603, configured to parse the first extended header of the GTP-U PDU and route the data to a target processing module for processing based on the data type and / or task ID in the first extended header.

[0126] Those skilled in the art should understand that Figure 6 The functions of each unit in the data transmission device shown can be understood by referring to the relevant description of the aforementioned method. Figure 6 The functions of each unit in the data transmission device shown can be implemented by a program running on a processor or by specific logic circuits.

[0127] Figure 7 This is a schematic diagram of the structure of the data transmission device provided in the embodiments of this application. Figure 2 It is used in second network devices, such as Figure 7 As shown, the data transmission device includes:

[0128] The second receiving unit 701 is used to receive a data channel establishment request sent by the first network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. In this case, one of the first network device and the second network device is a RAN node, and the other network device is a core network node.

[0129] The second sending unit 702 is used to send a data channel establishment response to the first network device. The data channel establishment response includes a data channel ID that was successfully established or a data channel ID that failed to be established.

[0130] In some implementations, the data channel establishment request includes one or more of the following information: data channel ID, data type transmitted by the data channel, task ID corresponding to the data transmitted by the data channel, first transport layer information associated with the data channel, data requirements for the data transmitted by the data channel, and encryption information for the data transmitted by the data channel.

[0131] The first transport layer information includes a first IP address and / or a first TEID allocated by the first network device; wherein the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

[0132] In some implementations, if the data channel establishment response includes a successfully established data channel ID, then the data channel establishment response further includes second transport layer information associated with the data channel; wherein the second transport layer information includes a second IP address and / or a second TEID allocated by the second network device; wherein the second IP address and / or the second TEID is used by the second network device to receive data sent by the first network device; or, if the data channel establishment response includes a failed data channel ID, then the data channel establishment response further includes a reason for the data channel establishment failure.

[0133] In some embodiments, the second receiving unit 701 is configured to receive a data channel release request sent by the first network device, the data channel release request being used to request the release of the data channel between the first network device and the second network device;

[0134] The second sending unit 702 is used to send a data channel release response to the first network device.

[0135] In some implementations, the data channel release request includes a data channel ID.

[0136] In some implementations, the data transmitted by the data channel is encapsulated in a GTP-U PDU, wherein the GTP-U PDU has a first extended header, which includes the data type and / or task ID corresponding to the data.

[0137] In some embodiments, the apparatus further includes: a second processing unit 703, configured to encapsulate the data to be transmitted in a GTP-U PDU, and encapsulate the data type and / or task ID corresponding to the data in the first extended packet header of the GTP-U PDU;

[0138] The second sending unit 702 is used to send the GTP-U PDU to the first network device through the data channel.

[0139] Those skilled in the art should understand that Figure 7 The functions of each unit in the data transmission device shown can be understood by referring to the relevant description of the aforementioned method. Figure 7 The functions of each unit in the data transmission device shown can be implemented by a program running on a processor or by specific logic circuits.

[0140] Figure 8 This is a schematic structural diagram of a network device 800 provided in an embodiment of this application. Figure 8 The network device 800 shown includes a processor 810, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0141] Optionally, such as Figure 8 As shown, the network device 800 may further include a memory 820. The processor 810 can retrieve and run computer programs from the memory 820 to implement the methods described in this embodiment.

[0142] The memory 820 can be a separate device independent of the processor 810, or it can be integrated into the processor 810.

[0143] Optionally, such as Figure 8 As shown, the network device 800 may also include a transceiver 830, which the processor 810 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0144] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0145] Optionally, the network device 800 may specifically be the first network device in the embodiments of this application, and the network device 800 may implement the corresponding processes implemented by the first network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0146] Optionally, the network device 800 may specifically be a second network device in the embodiments of this application, and the network device 800 may implement the corresponding processes implemented by the second network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0147] Figure 9 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 9 The chip 900 shown includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0148] Optionally, such as Figure 9 As shown, chip 900 may further include memory 920. Processor 910 can retrieve and run computer programs from memory 920 to implement the methods described in this embodiment.

[0149] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0150] Optionally, the chip 900 may also include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0151] Optionally, the chip 900 may also include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0152] Optionally, the chip can be applied to the first network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0153] Optionally, the chip can be applied to the second network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the second network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0154] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0155] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0156] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0157] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0158] This application also provides a computer-readable storage medium for storing computer programs.

[0159] Optionally, the computer-readable storage medium can be applied to the first network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0160] Optionally, the computer-readable storage medium can be applied to the second network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the second network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0161] This application also provides a computer program product, including computer program instructions.

[0162] Optionally, the computer program product can be applied to the first network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0163] Optionally, the computer program product can be applied to the second network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the second network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0164] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0165] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0166] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0167] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0168] In addition, the functional units in the various embodiments of this application 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.

[0169] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion 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.) to execute all or part of the steps of the methods described in the various embodiments of this application. 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.

[0170] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A data transmission method, characterized in that, The method includes: A first network device sends a data channel establishment request to a second network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a Radio Access Network (RAN) node, and the other network device is a core network node. The first network device receives a data channel establishment response sent by the second network device, the data channel establishment response including a data channel identifier ID for successful establishment or a data channel ID for failed establishment.

2. The method according to claim 1, characterized in that, The data channel establishment request includes one or more of the following information: data channel ID, data type transmitted by the data channel, task ID corresponding to the data transmitted by the data channel, first transport layer information associated with the data channel, data requirements for the data transmitted by the data channel, and encryption information of the data transmitted by the data channel. The first transport layer information includes a first IP address and / or a first tunnel endpoint identifier (TEID) allocated by the first network device; wherein the first IP address and / or the first TEID are used by the first network device to receive data sent by the second network device.

3. The method according to claim 1, characterized in that, If the data channel establishment response includes a successfully established data channel ID, then the data channel establishment response further includes second transport layer information associated with the data channel; wherein the second transport layer information includes a second IP address and / or a second TEID allocated by the second network device; wherein the second IP address and / or the second TEID is used by the second network device to receive data sent by the first network device; or, If the data channel establishment response includes the ID of the data channel that failed to establish, then the data channel establishment response also includes the reason for the failure to establish the data channel.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first network device sends a data channel release request to the second network device, the data channel release request being used to request the release of the data channel between the first network device and the second network device; The first network device receives a data channel release response sent by the second network device; The data channel release request includes the data channel ID.

5. The method according to any one of claims 1 to 4, characterized in that, The data transmitted through the data channel is encapsulated in a General Packet Radio Service Tunneling Protocol User Plane GTP-U Protocol Data Unit (PDU), wherein the GTP-U PDU has a first extended header, which includes the data type and / or task ID corresponding to the data.

6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The first network device receives a GTP-UPDU sent by the second network device through the data channel, wherein the GTP-UPDU contains data. The first network device parses the first extended header of the GTP-U PDU and routes the data to the target processing module for processing based on the data type and / or task ID in the first extended header.

7. A data transmission method, characterized in that, The method includes: The second network device receives a data channel establishment request sent by the first network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node. The second network device sends a data channel establishment response to the first network device, the data channel establishment response including a successfully established data channel ID or a failed data channel ID.

8. The method according to claim 7, characterized in that, The data channel establishment request includes one or more of the following information: data channel ID, data type transmitted by the data channel, task ID corresponding to the data transmitted by the data channel, first transport layer information associated with the data channel, data requirements for the data transmitted by the data channel, and encryption information of the data transmitted by the data channel. The first transport layer information includes a first IP address and / or a first TEID allocated by the first network device; wherein the first IP address and / or the first TEID is used by the first network device to receive data sent by the second network device.

9. The method according to claim 7, characterized in that, If the data channel establishment response includes a successfully established data channel ID, then the data channel establishment response further includes second transport layer information associated with the data channel; wherein the second transport layer information includes a second IP address and / or a second TEID allocated by the second network device; wherein the second IP address and / or the second TEID is used by the second network device to receive data sent by the first network device; or, If the data channel establishment response includes the ID of the data channel that failed to establish, then the data channel establishment response also includes the reason for the failure to establish the data channel.

10. The method according to any one of claims 7 to 9, characterized in that, The method further includes: The second network device receives a data channel release request sent by the first network device, the data channel release request being used to request the release of the data channel between the first network device and the second network device; The second network device sends a data channel release response to the first network device; The data channel release request includes the data channel ID.

11. The method according to any one of claims 7 to 9, characterized in that, The data transmitted through the data channel is encapsulated in a GTP-U PDU, wherein the GTP-U PDU has a first extended header, which includes the data type and / or task ID corresponding to the data.

12. The method according to any one of claims 7 to 9, characterized in that, The method further includes: The second network device encapsulates the data to be transmitted in a GTP-U PDU, and encapsulates the data type and / or task ID corresponding to the data in the first extended packet header of the GTP-U PDU; The second network device sends the GTP-UPDU to the first network device through the data channel.

13. A data transmission device, characterized in that, Applied to a first network device, the device includes: The first sending unit is configured to send a data channel establishment request to the second network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. Among them, one of the first network device and the second network device is a RAN node, and the other network device is a core network node. The first receiving unit is configured to receive a data channel establishment response sent by the second network device, wherein the data channel establishment response includes a data channel ID that was successfully established or a data channel ID that failed to be established.

14. A data transmission device, characterized in that, Applied to a second network device, the device includes: The second receiving unit is configured to receive a data channel establishment request sent by the first network device. The data channel establishment request is used to request the establishment of a data channel between the first network device and the second network device. In this case, one of the first network device and the second network device is a RAN node, and the other network device is a core network node. The second sending unit is used to send a data channel establishment response to the first network device. The data channel establishment response includes a data channel ID that was successfully established or a data channel ID that failed to be established.

15. A network device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 12.

16. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 12.

17. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 12.

Images