Data sending method, data receiving method, communication device, and storage medium

Abstract

The present application relates to the technical field of communications, and provides a data sending method, a data receiving method, a communication device, and a storage medium. The data sending method comprises: mapping to a data radio bearer (DRB) data to be transmitted; and sending said data to a second node by means of the DRB.

Description

Data sending method, data receiving method, communication device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 1, 2023, with application number 202311663890.X and invention name “Data sending method, data receiving method, communication device and storage medium”. The entire contents of the Chinese patent application are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a data sending method, a data receiving method, a communication device, and a storage medium. Background Art

[0004] The application of artificial intelligence (AI) technology in wireless communications has promoted the intelligent development of mobile communication networks and vertical industries. At the same time, the application of AI technology has also placed new demands on the capabilities of current mobile communication networks. For example, AI technology requires workflows such as data collection, data preprocessing, model training, model inference, and model evaluation.

[0005] Current AI technology is typically applied in the wireless communications field using "patch" and "plug-in" methods. These methods are difficult to better integrate with mobile communication networks, resulting in low actual data transmission efficiency.

[0006] Summary of the Invention

[0007] On the one hand, a data sending method is provided, which is applied to a first node, including: mapping the data to be transmitted to a data radio bearer DRB; and sending the data to be transmitted to a second node through the DRB.

[0008] On the other hand, another data receiving method is provided, which is applied to the second node, including: receiving the data to be transmitted sent by the first node on the DRB, and the first node is responsible for mapping the data to be transmitted to the DRB.

[0009] On the other hand, a first node is provided, comprising: a processing unit and a communication unit; the processing unit is used to map the data to be transmitted to the data radio bearer DRB; and the communication unit is used to send the data to be transmitted to the second node through the DRB.

[0010] On the other hand, a second node is provided, comprising: a processing unit and a communication unit; the communication unit is used to receive the data to be transmitted sent by the first node on the DRB, and the first node is responsible for mapping the data to be transmitted to the DRB.

[0011] On the other hand, a communication device is provided, comprising: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; when the processor executes the computer program, it implements the data sending method described in any of the above embodiments, or executes the data receiving method described in any of the above embodiments.

[0012] On the other hand, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the data sending method described in any of the above embodiments is implemented, or the data receiving method described in any of the above embodiments is executed.

[0013] On the other hand, a computer program product is provided, which includes computer program instructions, and when the computer program instructions are executed by a processor, the computer program instructions implement the data sending method described in any of the above embodiments, or execute the data receiving method described in any of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the present application, the following briefly introduces the drawings required for use in some embodiments of the present application. Obviously, the drawings described below are only drawings of some embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0015] FIG1 is an architecture diagram of a communication system provided by some embodiments of the present application;

[0016] FIG2 is a flow chart of a data sending method provided in some embodiments of the present application;

[0017] FIG3 is a flowchart of another data sending method provided in some embodiments of the present application;

[0018] FIG4 is a flowchart of another data sending method provided in some embodiments of the present application;

[0019] FIG5 is a flow chart of a data receiving method provided in some embodiments of the present application;

[0020] FIG6 is a flowchart of another data receiving method provided in some embodiments of the present application;

[0021] FIG7 is a structural diagram of a first node provided in some embodiments of the present application;

[0022] FIG8 is a structural diagram of a second node provided in some embodiments of the present application;

[0023] FIG9 is a structural diagram of a communication device provided in some embodiments of the present application. DETAILED DESCRIPTION

[0024] The following will be combined with the accompanying drawings to clearly and completely describe the technical solutions in this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0025] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0026] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the quantity of the technical features indicated. Therefore, a feature specified as "first" or "second" may explicitly or implicitly include one or more of the features.

[0027] In the description of this application, unless otherwise specified, " / " means "or." For example, A / B can mean A or B. "And / or" in this document is simply a description of an association between related objects, indicating that three relationships can exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, and B exists alone. Furthermore, "at least one" means one or more, and "a plurality" means two or more.

[0028] The following explains the terms involved in the embodiments of the present application to facilitate readers' understanding.

[0029] (1) Quality of service rule (QoS rule)

[0030] A QoS rule instructs the user equipment (UE) to map uplink user plane data packets to a QoS flow. The UE (Service Data Adaptation Protocol (SDAP) layer) then maps the uplink QoS flow to a data radio bearer (DRB).

[0031] The access and mobility management function (AMF) sends the QoS rules information element (IE) to the UE through the protocol data unit (PDU) session establishment / modification procedure.

[0032] The QoS rules information element includes multiple QoS rules, each of which is associated with one or more packet filter sets. A packet filter set is usually represented in the form of a filter list in a QoS rule.

[0033] For example, the QoS rules information element is shown in Table 1 below:

[0034] Table 1 QoS rules information element

[0035] The QoS rules IEI is a unique identifier for the QoS rules information element, typically represented by one octet. The AMF and UE can use the QoS rules IEI to identify and reference the QoS rules information element. The length of the QoS rules IE indicates the size of the QoS rules information element. QoS rule 1 to QoS rule n represent multiple QoS rules included in the QoS rules information element.

[0036] For example, taking QoS rule 1 in Table 1 as an example, the content of the QoS rule is shown in Table 2 below:

[0037] Table 2 QoS rule

[0038] The QoS rule identifier is used to identify the QoS rule, the QoS rule length is used to indicate the size of the QoS rule, and the rule operation code is used to define the operation instruction, such as creating a new QoS rule. The DQR bit is used to indicate whether the QoS rule is the default QoS rule. The packet filter number is used to identify the number of packet filters in the QoS rule. The packet filter list is used to carry packet filter information. The QoS rule priority (precedence) is used to define the priority of the QoS rule, and the QoS flow identifier is used to identify the QoS flow.

[0039] (2) Packet filter set

[0040] Currently, there are two types of packet filter sets: Internet Protocol (IP) packet filter sets and Ethernet packet filter sets. Packet filter sets are typically used to map data streams to QoS flows based on configured data mapping rules, allowing data to be transmitted according to the corresponding QoS rules.

[0041] The data packet filter set includes various packet filters, which are used to define specific data filtering rules.

[0042] Currently, a packet filter consists of the following fields:

[0043] Packet filter direction (2 bits): used to define the direction of the packet filter, where the direction type includes upstream, downstream, or upstream and downstream.

[0044] Packet filter identifier (4 bits): used to identify each packet filter.

[0045] The length of the packet filter contents (1 octet) is used to define the length of the packet filter contents.

[0046] The packet filter contents itself (variable number of octets): defines the specific content information of the packet filter.

[0047] There is a certain correspondence between the identifier and type of the packet filter, and each type corresponds to different packet filter content. For example, a packet filter of the IPv4 remote address type has the IPv4 address and address mask information as its content. The following is a partial correspondence between identifiers and types:

[0048] 0 0 0 0 0 0 0 1Match-all type

[0049] 0 0 0 1 0 0 0 0 IPv4 remote address type

[0050] 0 0 0 1 0 0 0 1 IPv4 local address type

[0051] 0 0 1 0 0 0 0 1 IPv6 remote address / prefix length type

[0052] 0 0 1 0 0 0 1 1 IPv6 local address / prefix length type

[0053] 0 0 1 1 0 0 0 0 Protocol identifier / Next header type

[0054] 0 1 0 0 0 0 0 0Single local port type

[0055] 0 1 0 0 0 0 0 1Local port range type

[0056] 0 1 0 1 0 0 0 0Single remote port type

[0057] 0 1 0 1 0 0 0 1Remote port range type

[0058] 0 1 1 0 0 0 0 0Security parameter index type

[0059] 0 1 1 1 0 0 0 0 Type of service / Traffic class type

[0060] 1 0 0 0 0 0 0 0Flow label type

[0061] 1 0 0 0 0 0 0 1Destination MAC address type

[0062] 1 0 0 0 0 0 1 0 Source MAC address type

[0063] 1 0 0 0 0 0 1 1 802.1Q (a standard protocol) customer tag (C-TAG) virtual local area network identifier (VID) type

[0064] 1 0 0 0 0 1 0 0 802.1Q service tag (S-TAG) VID type

[0065] 1 0 0 0 0 1 0 1 802.1Q C-TAG priority field / drop eligible indicator (PCP / DEI) type

[0066] 1 0 0 0 0 1 1 0 802.1Q S-TAG PCP / DEI type

[0067] 1 0 0 0 0 1 1 1Ethertype

[0068] For example, in conjunction with the packet filter list in Table 2 above, when the rule operation code indicates "create a new QoS rule" or "modify an existing QoS rule and add a packet filter" or "modify an existing QoS rule and replace all packet filters", the contents of the packet filter set are as shown in Table 3 below:

[0069] Table 3 Packet filter list

[0070] The packet filter list includes packet filters 1 to N, and each packet filter includes fields such as direction, identifier, length, and content.

[0071] (3) Packet detection rule (PDR)

[0072] The PDR is used to define the detection and classification rules for data packets, which also include packet filter sets.

[0073] The session management function (SMF) sends the PDR to the user plane function (UPF) through the N4 session management process of the N4 air interface (for example, the N4 session establishment process or the N4 session modification process).

[0074] The UPF maps downlink data packets to QoS flows through the PDR. The 5G radio access network (NG-RAN) then maps the downlink QoS flows to DRBs.

[0075] For example, the content of the PDR includes:

[0076] 1. Uplink or downlink packet filter of the service data flow (SDF) template;

[0077] 2. PDR priority;

[0078] 3. QoS implementation rules, such as SDF maximum bit rate, guaranteed flow bit rate (GFBR), and guaranteed bit rate (GBR) QoS flow maximum bit rate;

[0079] 4. Rules for forwarding behavior;

[0080] 5. Reflective QoS indication.

[0081] The application of AI technology in wireless communications has promoted the intelligent development of mobile communication networks and vertical industries. At the same time, the application of AI technology has also placed new demands on the capabilities of current mobile communication networks. For example, AI technology requires workflows such as data collection, data preprocessing, model training, model inference, and model evaluation.

[0082] Facing the future vision of ubiquitous intelligence, that is, the scenario of the integrated application of technologies such as the Internet, Internet of Things, big data, and artificial intelligence, future wireless communication networks need to have inherent AI capabilities to achieve a deep integration design of the computing power, data, algorithms, connections and network functions, protocols and processes required for AI services.

[0083] Current AI technologies are typically applied in wireless communications using a "patch-based" or "plug-in" approach, centralizing AI-related processing on cloud servers. However, for wireless communications scenarios such as air interface-related channel state information (CSI) feedback optimization, beam management, and positioning, these approaches require uploading large amounts of data from the UE or RAN to the cloud server. This consumes significant communication resources and introduces significant interaction latency, making it impossible to meet the real-time requirements of these scenarios.

[0084] In summary, the current solution is difficult to better integrate with the mobile communication network, and the actual data transmission efficiency is low.

[0085] Future-oriented wireless network architectures must support endogenous AI, meaning they must provide a complete operating environment for AI technology throughout its lifecycle. This support will also shift the source of data generation. Data will not only be generated by applications and servers, but also by network devices such as UEs and RANs. Therefore, these network devices must also possess capabilities for data collection, model training, and storage, and must also implement appropriate data transmission solutions.

[0086] In view of this, an embodiment of the present application provides a data transmission method, in which a first node maps the data to be transmitted to a DRB and sends the data to be transmitted to a second node through the DRB. In the prior art, the data of a terminal usually needs to be transmitted to the target device via network links such as the access network, bearer network, core network, and backbone network. In this process, the core network network elements (such as AMF, SMF, UPF, etc.) usually instruct and manage the data transmission between the terminal and other network devices such as the access network device.

[0087] However, for air interface-related intelligent or perception application scenarios, such as CSI feedback optimization, beam management, and positioning, which mainly involve scenarios where the terminal interacts with the base station, the existing technology requires the terminal or base station to upload the relevant data to the network side for processing, which takes up a lot of communication resources and has high interaction latency, making it difficult to meet the timeliness requirements of some scenarios. In contrast, the data transmission method provided in this application involves only the first node and the second node in most of the processes, and only a small part of the data transmission is required to be indicated and managed by other network devices, which saves signaling overhead while ensuring timeliness, thereby improving data transmission efficiency.

[0088] The following will describe in detail the implementation of the embodiment of the present application in conjunction with the accompanying drawings.

[0089] FIG1 is an architecture diagram of a communication system 10 provided in an embodiment of the present application. As shown in FIG1 , the communication system 10 includes: a terminal 101 and a base station 102 .

[0090] The terminal 101 is connected to the base station 102 via a communication link. The communication link may be a wired communication link or a wireless communication link, which is not limited in this application.

[0091] The technical solutions of the embodiments of the present application can be applied to various communication systems 10, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. The term "system" and "network" are interchangeable. A CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000. UTRA can include wideband CDMA (WCDMA) technology and other CDMA variants. CDMA2000 can cover interim standard (IS) 2000 (IS-2000), IS-95, and IS-856 standards. A TDMA system can implement wireless technologies such as global system for mobile communications (GSM). The OFDMA system can implement wireless technologies such as evolved universal radio terrestrial access (Evolved UTRA, E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA, etc. UTRA and E-UTRA are UMTS and UMTS evolved versions. 3GPP's long term evolution (LTE) and various versions based on LTE evolution are new versions of UMTS using E-UTRA. The communication system 10 can also be a 5G communication system, a new radio (NR), and a 6G communication system. In addition, the communication system 10 can also be applicable to future-oriented communication technologies, all of which are applicable to the technical solutions provided in the embodiments of the present application.

[0092] Terminal 101 is a device with wireless communication capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on water (such as on ships). It can also be deployed in the air (for example, on airplanes, balloons, and satellites). Terminal 101, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), and terminal device, is a device that provides voice and / or data connectivity to users. For example, terminal 101 includes handheld devices with wireless connection capabilities, vehicle-mounted devices, etc. Currently, the terminal 101 can be: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an in-vehicle device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a TV, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, an aerial device (such as an intelligent robot, a hot air balloon, a drone, an airplane), etc. In one possible application scenario of the present application, the terminal is a terminal that often works on the ground, such as an in-vehicle device. In this application, for the sake of convenience, chips deployed in the above-mentioned devices, such as system-on-a-chip (SOC), baseband chips, etc., or other chips with communication functions may also be referred to as terminals.

[0093] The terminal 101 may be a vehicle with corresponding communication functions, or a vehicle-mounted communication device, or other embedded communication devices, or a user's handheld communication device, including a mobile phone, a tablet computer, etc.

[0094] As an example, in an embodiment of the present application, the terminal 101 can also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0095] The base station 102 is a device located at the access network side of the above-mentioned communication system and has wireless transceiver functions or a chip or chip system that can be set in the device. The base station 102 includes, but is not limited to, an access point (AP) in a WiFi system, such as a home gateway, a router, a server, a switch, a bridge, etc., an evolved NodeB (eNB), a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home NodeB, HNB), a base band unit (BBU), a wireless relay node, a wireless backhaul node, a transmission point (TRP or TP), etc. It can also be a 5G base station, such as a gNB in ​​a new radio (NR) system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), a roadside unit (roadside unit) with base station functions. The base station 102 also includes base stations in different networking modes, such as a master evolved NodeB (MeNB) and a secondary eNB (SeNB) or a secondary gNB (SgNB). The base station 102 also includes different types, such as a ground base station, an aerial base station, and a satellite base station.

[0096] The technical solution provided in this application is applied to the data transmission process between the terminal 101 and the base station 102, especially in the scenario where data transmission is performed on the generated data to be transmitted after the terminal 101 and the base station 102 themselves generate data to be transmitted (such as data used for artificial intelligence models, data generated by artificial intelligence models, perception data, etc.).

[0097] Exemplary data transmission scenarios may include the following:

[0098] Case 1: The terminal 101 is configured to send a first data request message to the base station 102. Correspondingly, the base station 102 is configured to receive the first data request message from the terminal 101.

[0099] The first data request message is used to request the base station 102 to send data to be transmitted.

[0100] Exemplarily, the data to be transmitted is local data generated by the base station 102 itself, such as a training model generated locally by the base station 102, intermediate results of inference, and other data.

[0101] The base station 102 is configured to send data to be transmitted to the terminal 101. Correspondingly, the terminal 101 is configured to receive data to be transmitted from the base station 102.

[0102] Case 2: The terminal 101 is configured to send a second data request message to the base station 102. Correspondingly, the base station 102 is configured to receive the second data request message from the terminal 101.

[0103] The second data request message is used to request base station 102 to authorize terminal 101 to send data to be transmitted to base station 102. Similarly, the data to be transmitted is local data generated by base station 102 itself, such as training models generated locally by terminal 101, intermediate inference results, and other data.

[0104] The base station 102 is further configured to confirm whether the terminal 101 is authorized to send data to be transmitted.

[0105] The terminal 101 is further configured to send data to be transmitted to the base station 102. Correspondingly, the base station 102 is configured to receive data to be transmitted from the terminal 101.

[0106] Case 3: The base station 102 is configured to send a third data request message to the terminal 101. Correspondingly, the terminal 101 is configured to receive the third data request message from the base station 102.

[0107] The third data request message is used to request the terminal 101 to send data to be transmitted.

[0108] The terminal 101 is configured to send data to be transmitted to the base station 102. Correspondingly, the base station 102 is configured to receive the data to be transmitted from the terminal 101.

[0109] Case 4: The base station 102 is configured to send a fourth data request message to the terminal 101. Correspondingly, the terminal 101 is configured to receive the fourth data request message from the base station 102.

[0110] The fourth data request message is used to request the terminal 101 to authorize the base station 102 to send data to be transmitted to the terminal 101.

[0111] The terminal 101 is further configured to confirm whether the base station 102 is authorized to send data to be transmitted.

[0112] The base station 102 is configured to send data to be transmitted to the terminal 101. Correspondingly, the terminal 101 is configured to receive data to be transmitted from the base station 102.

[0113] Currently, the terminal 101 and the base station 102 usually establish a data radio bearer (DRB) to transmit data, so the terminal 101 and the base station 102 need to have certain computing power, storage and data processing capabilities.

[0114] Among them, the terminal 101 and the base station 102 need to realize the mapping of the data file / flow to be transmitted to the QoS flow to the DRB, or the mapping of the data file / flow to be transmitted to the DRB, so as to realize the transmission of the data to be transmitted between the terminal 101 and the base station 102.

[0115] It should be pointed out that the various embodiments of the present application can refer to each other, for example, the same or similar steps, method embodiments, system embodiments and device embodiments can refer to each other without limitation.

[0116] FIG2 is a flow chart of a data transmission method provided in an embodiment of the present application. As shown in FIG2 , the method includes the following steps:

[0117] Step 201: The first node maps the data to be transmitted to a data radio bearer (DRB).

[0118] The first node may be an access network related node device, such as a base station or a terminal, and the data to be transmitted may be local data generated by the first node.

[0119] Currently, the application of AI technology in wireless communications is a development trend for future mobile communication networks. The application of AI technology places new demands on the capabilities of current mobile communication networks, such as workflow requirements for data collection, data preprocessing, model training, model inference, and model evaluation.

[0120] In response to the above technical scenarios, the present application provides a data sending method to realize data transmission between the terminal and the base station for the relevant data generated by AI technology.

[0121] Exemplarily, the data to be transmitted may include at least one of the following: data used for the artificial intelligence model, data generated by the artificial intelligence model, and perception data.

[0122] Step 202: The first node sends data to be transmitted to the second node through the DRB.

[0123] The second node may be an access network related node device, such as a base station or a terminal.

[0124] In a possible implementation, the first node is a base station and the second node is a terminal. Alternatively, the first node is a terminal and the second node is a base station.

[0125] When the first node is a base station and the second node is a terminal, the base station can map the data to be transmitted to the DRB after generating the data to be transmitted, and send the data to be transmitted to the terminal through the DRB.

[0126] When the first node is a terminal and the second node is a base station, the terminal can generate the data to be transmitted by itself, map the data to be transmitted to the DRB according to the quality of service rule (QoS Rule) indicated by the base station, and send the data to be transmitted to the base station through the DRB.

[0127] As can be seen from the two scenarios above, the data to be transmitted primarily involves interaction between two node devices, the terminal and the base station, and no other node devices are required to participate in the data transmission process. In existing technologies, data transmission passes through network links such as the access network, bearer network, core network, and backbone network, with the core network's relevant network elements managing and configuring the data transmission process.

[0128] Obviously, for the above-mentioned scenarios involved in the embodiments of the present application, the solution of transmitting data to core network elements such as UPF for data mapping will cause additional resource overhead and increase transmission delay.

[0129] In summary, an embodiment of the present application provides a data transmission method, in which a first node maps the data to be transmitted to a DRB and sends the data to be transmitted to a second node through the DRB. In the prior art, the data of a terminal usually needs to be transmitted to the target device via network links such as the access network, bearer network, core network, and backbone network. In this process, the core network network elements (such as AMF, SMF, UPF, etc.) usually instruct and manage the data transmission between the terminal and other network devices such as the access network device.

[0130] However, for air interface-related intelligent or perception application scenarios, such as CSI feedback optimization, beam management, and positioning, which mainly involve scenarios where the terminal interacts with the base station, the existing technology requires the terminal or base station to upload the relevant data to the network side for processing, which takes up a lot of communication resources and has high interaction latency, making it difficult to meet the timeliness requirements of some scenarios. In contrast, most of the processes of the data transmission method provided in this application only involve the first node and the second node, and other network devices do not need to participate, or only provide instructions for data transmission, which saves signaling overhead while ensuring timeliness, thereby improving data transmission efficiency.

[0131] The following describes the process of first node data mapping.

[0132] As a possible embodiment of the present application, in combination with FIG. 2 , as shown in FIG. 3 , the above step 201 can be implemented through the following step 301 .

[0133] Step 301: The first node maps the data to be transmitted to the DRB based on the data mapping rule.

[0134] The data mapping rules are used to filter and group the data.

[0135] In one possible implementation, the data mapping rule includes at least one of the following:

[0136] Identification of data mapping rules;

[0137] The length of the data mapping rule;

[0138] Indication information used to indicate whether it is a default data mapping rule;

[0139] The number of packet filters;

[0140] The priority value of the data mapping rule;

[0141] The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule;

[0142] Packet filter list.

[0143] Exemplarily, the identifier of the data mapping rule may be a QoS rule ID field, which is used to identify the data mapping rule.

[0144] The length of the data mapping rule may be a length of QoS rule field, which is used to represent the content length of the data mapping rule.

[0145] The indication information for indicating whether it is the default data mapping rule may be a DQR bit field. For example, when the DQR bit value is 1, it indicates that the corresponding data mapping rule is the default data mapping rule. When the DQR bit value is 0, it indicates that the corresponding data mapping rule is not the default data mapping rule.

[0146] The number of packet filters may be a number of packet filters field, which is used to indicate the number of packet filters in the data mapping rule.

[0147] The priority value of the data mapping rule may be a QoS rule precedence field, which is used to represent the relative priority of the data mapping rule, that is, the order in which data is matched with multiple data mapping rules.

[0148] The identifier of the QoS flow associated with the data mapping rule may be a QoS flow identifier field (QFI), which is used to identify a QoS flow. The identifier of the DRB associated with the data mapping rule may be a DRB identifier, which is used to identify a DRB. Multiple data mapping rules can be associated with the same QFI or the same DRB identifier.

[0149] The packet filter list may be a packet filter list field, which is used to carry packet filter information.

[0150] In one possible implementation, the packet filter list includes at least one of the following:

[0151] The direction of the packet filter;

[0152] The identifier of the packet filter;

[0153] The contents of the packet filter.

[0154] The packet filter direction field can be the packet filter direction field, which is used to indicate the data flow direction mapped by the packet filter, including upstream, downstream, or both upstream and downstream directions. The packet filter identifier field can be the packet filter identifier field, which is used to identify the packet filter. The packet filter content is used to carry specific data packet filtering condition information.

[0155] The packet filters in the packet filter list are packet filters in the data packet filter set. Current packet filter sets include IP packet filter sets and Ethernet packet filter sets. However, these two packet filter sets are mainly for end-to-end data transmission and are not applicable to local data between the terminal and the base station involved in this application.

[0156] In this regard, an embodiment of the present application provides a RAN-based packet filter set: a local data filter set (local data filter set) for implementing packet filtering of data generated within a base station or a terminal.

[0157] The local data packet filter set includes one or more packet filters, which are used to map the data to be transmitted of the first node or the second node to the QoS flow or to the DRB.

[0158] In one possible implementation, the content of the packet filter includes at least one of the following:

[0159] Source IP address type;

[0160] Target IP address type;

[0161] Source port number;

[0162] Destination port number;

[0163] Source component identification;

[0164] Target component identification;

[0165] Service type.

[0166] The source IP address type may be a type of source IP address field, which is used to match the source IP address of the data flow. The destination IP address type may be a type of destination IP address field, which is used to match the destination IP address of the data flow.

[0167] The source port number can be the source port number field, which is used to match the source port number of the data flow. The destination port number can be the destination port number field, which is used to match the destination port number of the data flow.

[0168] The source component identifier may be a source assembly ID field, which is used to match the source component of a data stream. The destination component identifier may be a destination assembly ID field, which is used to match the destination component of a data stream. Embodiments of the present application can use the source and destination components to match data to be transmitted between a terminal and a base station.

[0169] The service type can be a type of service field, which is used to match the service corresponding to the data flow. Exemplary service types can include AI model training, AI model reasoning, and perception services.

[0170] In this way, the first node in this application can map data of different source / destination addresses, source / destination ports, source / destination components or service types to the corresponding QoS flow or DRB based on the data mapping rules, so as to achieve priority protection for different sources (source address, source port, source component), different destinations (destination address, destination port, destination component) and different service types.

[0171] Currently, for end-to-end downlink data, the UPF usually maps downlink user data to the QoS flow. At the same time, the SMF sends the QoS configuration to the base station, and the base station maps the QoS flow to the DRB based on the QoS configuration.

[0172] For end-to-end uplink data, the SMF sends QoS to the terminal, and the terminal maps the uplink user data to the QoS flow according to the data mapping rules. After that, the terminal (SDAP layer) maps the QoS flow to the DRB.

[0173] The mapping of data flow to QoS flow belongs to the operation of non-access stratum (NAS) level, and the mapping of QoS flow to DRB belongs to the operation of access stratum (AS) level.

[0174] The data to be transmitted in the embodiments of the present application mainly involves data transmission between the base station and the terminal. Therefore, the first node in the present application can map the data to be transmitted to the QoS flow and then map the QoS flow to the DRB, or it can directly map the data to be transmitted to the DRB.

[0175] In a possible implementation, the first node maps the data to be transmitted directly to the DRB based on the first data mapping rule.

[0176] Exemplarily, the first data mapping rule may include an identifier of the DRB associated with the first data mapping rule.

[0177] In another possible implementation, the first node maps the to-be-transmitted data to a Quality of Service (QoS) flow based on the second data mapping rule. Thereafter, the first node maps the QoS flow to a DRB.

[0178] Exemplarily, the second data mapping rule may include an identifier of a QoS flow associated with the second data mapping rule.

[0179] The following describes a process in which the first node sends a data mapping rule to the second node.

[0180] As a possible embodiment of the present application, in combination with FIG. 2 , as shown in FIG. 4 , the method further includes the following steps 401 - 402 .

[0181] Step 401: A first node receives a first message sent by a second node.

[0182] The first message is used to request establishment of a data transmission connection.

[0183] As can be seen from the above scheme, after the first node generates data to be transmitted, it can use data mapping rules to map the data to the DRB for data transmission. Similarly, after the second node generates data to be transmitted, it also needs to map the data to be transmitted using data mapping rules. Therefore, the second node can obtain the data mapping rules from the first node via a message request.

[0184] It should be noted that the process of the second node sending the data to be transmitted to the first node can refer to the relevant technical solution of the first node sending the data to be transmitted to the second node in the embodiment of the present application, and this application will not elaborate on this.

[0185] Step 402: The first node sends a second message to the second node.

[0186] The second message is used to respond to the first message. After receiving the first message, the first node may send the second message to the second node to instruct the second node to establish a data transmission connection.

[0187] It should be noted that this application does not limit the order in which steps 401-402 are executed relative to step 201. The first node and the second node only need to establish a data transmission connection before transmitting the data to be transmitted. Therefore, steps 401-402 can be executed before or after step 201. Figure 4 only uses the example of steps 401-402 being executed before step 201 to illustrate the data transmission method provided by this application.

[0188] In a possible implementation, the second message includes a data mapping rule.

[0189] Exemplarily, the second message is a radio resource control (RRC) message or a media access control element (MAC control element, MAC CE).

[0190] Currently, in the existing technology, the AMF sends data mapping rules to the terminal through the PDU session establishment / modification process. The data mapping rules are carried on the NAS message.

[0191] Since the present application mainly involves data transmission between the first node and the second node, the second message can be an AS message such as an RRC message or a MAC CE. In this way, the present application can directly send the data mapping rules from the first node to the second node without going through other network element devices (such as the core network network element AMF, etc.). At the same time, access layer level messages such as RRC messages and MAC CE have lower signaling delays and smaller signaling overheads than non-access layer level messages. Therefore, the above-mentioned scheme of the present application can further reduce the consumption of additional communication resources and ensure the timeliness of data transmission.

[0192] Among them, for the RRC message, the second message in this application can adopt a new data transmission message format, or can be based on the message format of the current NAS message.

[0193] As an example, for an RRC message using a new data transmission message format, the Abstract Syntax Notation (ASN.1) encoding format of the data mapping rule in the second message in this application is as follows:

[0194] The QoSRulelist field is used to represent the QoS rule list, which is expressed in the form of a sequence. The QoSRule field is used to represent the QoS rule, which is expressed in the form of a sequence.

[0195] The LocalDataMappingContents field is used to represent the content of the data mapping rule, including fields such as source / destination IP address type, source / destination port number type, source / destination component identifier, and service type.

[0196] As another example, for the encapsulated NAS message carried by the current RRC message, the encoding format of the data mapping rule in the second message in this application is shown in Table 4 below:

[0197] Table 4 Data mapping rules

[0198] It should be noted that when the data mapping rule is the first data mapping rule (ie, the data mapping rule that directly maps the data to be transmitted to the DRB), the QFI / DRB identifier in Table 4 selects the DRB identifier field to be associated with the corresponding DRB.

[0199] When the data mapping rule is the second data mapping rule (ie, the data mapping rule for mapping the data to be transmitted to the QoS flow), the QFI / DRB identifier in Table 4 selects the QFI field to be associated with the corresponding QoS flow.

[0200] As another example, for the second message using the MAC CE message format, the encoding format of the data mapping rule in this application is shown in Table 5 below:

[0201] Table 5 Data mapping rules

[0202] It should be noted that, when the data mapping rule is the first data mapping rule (ie, the data mapping rule that directly maps the data to be transmitted to the DRB), the QFI / RB identifier in Table 5 selects the RB identifier field to be associated with the corresponding DRB.

[0203] When the data mapping rule is the second data mapping rule (ie, the data mapping rule for mapping the data to be transmitted to the QoS flow), the QFI / RB identifier in Table 5 selects the QFI field to be associated with the corresponding QoS flow.

[0204] FIG5 is a flow chart of a data receiving method provided in an embodiment of the present application. As shown in FIG5 , the method includes the following steps:

[0205] Step 501: The second node receives the data to be transmitted sent by the first node on the DRB.

[0206] The first node is responsible for mapping the data to be transmitted to the DRB.

[0207] In a possible implementation, the first node is a base station and the second node is a terminal. Alternatively, the first node is a terminal and the second node is a base station.

[0208] Based on the above technical solution, an embodiment of the present application provides a data receiving method, in which a second node receives data to be transmitted sent by a first node on a DRB. The first node is responsible for mapping the data to be transmitted to the DRB. In the prior art, the data of the terminal usually needs to be transmitted to the target device through network links such as the access network, bearer network, core network, and backbone network. In this process, the core network network elements (such as AMF, SMF, UPF, etc.) usually instruct and manage the data transmission between the terminal and other network devices such as the access network device.

[0209] However, for air interface-related intelligent or perception application scenarios, such as CSI feedback optimization, beam management, and positioning, which mainly involve scenarios where the terminal interacts with the base station, the existing technology requires the terminal or base station to upload the relevant data to the network side for processing, which takes up a lot of communication resources and has high interaction latency, making it difficult to meet the timeliness requirements of some scenarios. In contrast, the data transmission method provided in this application only involves the first node and the second node, and other network devices do not need to participate, or only provide data transmission instructions, which saves signaling overhead while ensuring timeliness, thereby improving data transmission efficiency.

[0210] The following describes a process in which the second node receives the data mapping rule sent by the second node.

[0211] As a possible embodiment of the present application, in combination with FIG5 , as shown in FIG6 , the method further includes the following steps 601 - 602 .

[0212] Step 601: The second node sends a first message to the first node.

[0213] The first message is used to request establishment of a data transmission connection.

[0214] For details, please refer to the relevant description in the above step 401, which will not be repeated here.

[0215] Step 602: The second node receives the second message sent by the first node.

[0216] The second message is used to respond to the first message.

[0217] In a possible implementation, the second message includes a data mapping rule.

[0218] For details on the data mapping rules, please refer to the above descriptions and will not be elaborated here.

[0219] Exemplarily, the second message is a radio resource control (RRC) message or a media access control element (MAC control element, MAC CE).

[0220] Currently, in the existing technology, the AMF sends data mapping rules to the terminal through the PDU session establishment / modification process. The data mapping rules are carried on the NAS message.

[0221] Since the present application mainly involves data transmission between the first node and the second node, the second message can be an AS message such as an RRC message or a MAC CE. In this way, the present application can directly send the data mapping rules from the first node to the second node without going through other network element devices (such as the core network network element AMF, etc.). At the same time, access layer level messages such as RRC messages and MAC CE have lower signaling delays and smaller signaling overheads than non-access layer level messages. Therefore, the above-mentioned scheme of the present application can further reduce the consumption of additional communication resources and ensure the timeliness of data transmission.

[0222] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in conjunction with the algorithm steps of each example described in the embodiments of the present application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0223] In the embodiment of the present application, the communication device can be divided into functional modules according to the above method embodiment. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above-mentioned integrated module can be implemented in the form of hardware or software. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0224] For example, taking the communication device as the first node in the above method embodiment as an example, Figure 7 is a schematic diagram of the structure of a first node provided in an embodiment of the present application. The first node can execute the data transmission method provided in the above method embodiment. As shown in Figure 7, the first node 70 includes: a processing unit 701 and a communication unit 702.

[0225] The processing unit 701 is configured to map the data to be transmitted to a data radio bearer DRB.

[0226] The communication unit 702 is configured to send data to be transmitted to the second node via the DRB.

[0227] In some embodiments, the processing unit 701 is configured to map the data to be transmitted to the DRB based on a data mapping rule.

[0228] In some embodiments, the processing unit 701 is configured to map the data to be transmitted directly to the DRB based on a first data mapping rule.

[0229] In some embodiments, the processing unit 701 is configured to map the data to be transmitted to a Quality of Service (QoS) flow based on a second data mapping rule; and map the QoS flow to a DRB.

[0230] In some embodiments, the communication unit 702 is used to receive a first message sent by the second node, where the first message is used to request to establish a data transmission connection; the communication unit 702 is used to send a second message to the second node, where the second message is used to respond to the first message.

[0231] In some embodiments, the second message includes data mapping rules.

[0232] In some embodiments, the second message is a radio resource control RRC message or a medium access control element MAC CE.

[0233] In some embodiments, the data mapping rule includes at least one of the following:

[0234] Identification of data mapping rules;

[0235] The length of the data mapping rule;

[0236] Indication information used to indicate whether it is a default data mapping rule;

[0237] The number of packet filters;

[0238] The priority value of the data mapping rule;

[0239] The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule;

[0240] Packet filter list.

[0241] In some embodiments, the packet filter list includes at least one of the following:

[0242] The direction of the packet filter;

[0243] The identifier of the packet filter;

[0244] The contents of the packet filter.

[0245] In some embodiments, the data to be transmitted includes at least one of the following: data used for the artificial intelligence model, data generated by the artificial intelligence model, and perception data.

[0246] In some embodiments, the first node 70 is a base station and the second node is a terminal.

[0247] Taking the communication device as the second node in the above method embodiment as an example, Figure 8 is a schematic diagram of the structure of a second node provided in an embodiment of the present application. The second node can execute the data receiving method provided in the above method embodiment. As shown in Figure 8, the second node 80 includes: a processing unit 801 and a communication unit 802.

[0248] The communication unit 802 is used to receive the data to be transmitted sent by the first node on the DRB. The first node is responsible for mapping the data to be transmitted to the DRB.

[0249] In some embodiments, the communication unit 802 is used to send a first message to the first node, where the first message is used to request to establish a data transmission connection; the communication unit 802 is used to receive a second message sent by the first node, where the second message is used to respond to the first message.

[0250] In some embodiments, the second message includes data mapping rules.

[0251] In some embodiments, the second message is a radio resource control RRC message or a medium access control element MAC CE.

[0252] In some embodiments, the data mapping rule includes at least one of the following:

[0253] Identification of data mapping rules;

[0254] The length of the data mapping rule;

[0255] Indication information used to indicate whether it is a default data mapping rule;

[0256] The number of packet filters;

[0257] The priority value of the data mapping rule;

[0258] The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule;

[0259] Packet filter list.

[0260] In some embodiments, the packet filter list includes at least one of the following:

[0261] The direction of the packet filter;

[0262] The identifier of the packet filter;

[0263] The contents of the packet filter.

[0264] In some embodiments, the data to be transmitted includes at least one of the following: data used for the artificial intelligence model, data generated by the artificial intelligence model, and perception data.

[0265] In some embodiments, the first node is a base station and the second node 80 is a terminal.

[0266] In the case of implementing the functions of the above-mentioned integrated modules in hardware, this embodiment of the present application provides another possible structure of the communication device involved in the above-mentioned embodiment. As shown in Figure 9, the communication device 90 includes: a processor 902 and a bus 904. Optionally, the communication device may also include a memory 901; optionally, the communication device may also include a communication interface 903.

[0267] Processor 902 may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of this application. Processor 902 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of this application. Processor 902 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0268] The communication interface 903 is used to connect to other devices via a communication network, such as Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0269] The memory 901 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0270] As a possible implementation, the memory 901 can exist independently of the processor 902. The memory 901 can be connected to the processor 902 via a bus 904 and used to store instructions or program codes. When the processor 902 calls and executes the instructions or program codes stored in the memory 901, it can implement the data sending method provided in the embodiment of the present application, or implement the data receiving method provided in the embodiment of the present application.

[0271] In another possible implementation, the memory 901 may also be integrated with the processor 902 .

[0272] Bus 904 can be an extended industry standard architecture (EISA) bus, etc. Bus 904 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG9 shows only one thick line, but this does not mean that there is only one bus or one type of bus.

[0273] Some embodiments of the present application provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium), which stores computer program instructions. When the computer program instructions are executed on a computer, the computer executes the data sending method described in any of the above embodiments, or executes the data receiving method described in any of the above embodiments.

[0274] Exemplarily, the above-mentioned computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described herein may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0275] An embodiment of the present application provides a computer program product containing instructions. When the computer program product is run on a computer, the computer is caused to execute the data sending method described in any one of the above embodiments, or execute the data receiving method described in any one of the above embodiments.

[0276] The above is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A data sending method, applied to a first node, the method comprising: Mapping the data to be transmitted to the data radio bearer DRB; The data to be transmitted is sent to the second node through the DRB.

2. The method according to claim 1, wherein: Mapping the data to be transmitted to the data radio bearer DRB includes: Based on data mapping rules, the data to be transmitted is mapped to the DRB.

3. The method according to claim 2, wherein: The mapping the data to be transmitted to the DRB based on the data mapping rule includes: Based on the first data mapping rule, the data to be transmitted is directly mapped to the DRB.

4. The method according to claim 2, wherein: The mapping the data to be transmitted to the DRB based on the data mapping rule includes: Based on the second data mapping rule, mapping the data to be transmitted to a quality of service flow QoS flow; Map the QoS flow to the DRB.

5. The method according to claim 1, wherein: Before sending the data to be transmitted to the second node through the DRB, the method further includes: receiving a first message sent by the second node, where the first message is used to request establishment of a data transmission connection; A second message is sent to the second node, where the second message is used to respond to the first message.

6. The method according to claim 5, wherein: The second message includes data mapping rules.

7. The method according to claim 5, wherein: The second message is a radio resource control RRC message or a media access control element MAC CE.

8. The method according to claim 2 or 6, wherein: The data mapping rule includes at least one of the following: an identification of the data mapping rule; The length of the data mapping rule; Indication information used to indicate whether it is a default data mapping rule; The number of packet filters; a priority value of the data mapping rule; The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule; List of packet filters.

9. The method according to claim 8, wherein: The packet filter list includes at least one of the following: The direction of the packet filter; The identifier of the packet filter; The contents of the packet filter.

10. The method according to claim 1, wherein: The data to be transmitted includes at least one of the following: data used for the artificial intelligence model, data generated by the artificial intelligence model, and perception data.

11. The method according to claim 1, wherein: The first node is a base station, and the second node is a terminal.

12. A data receiving method, applied to a second node, the method comprising: Receive the data to be transmitted sent by the first node on the DRB, and the first node is responsible for mapping the data to be transmitted to the DRB.

13. The method according to claim 12, wherein: Before receiving the data to be transmitted sent by the first node on the DRB, the method further includes: Sending a first message to the first node, where the first message is used to request to establish a data transmission connection; A second message sent by the first node is received, where the second message is used to respond to the first message.

14. The method according to claim 13, wherein: The second message includes data mapping rules.

15. The method according to claim 13, wherein: The second message is a radio resource control RRC message or a media access control element MAC CE.

16. The method according to claim 14, wherein: The data mapping rule includes at least one of the following: an identification of the data mapping rule; The length of the data mapping rule; Indication information used to indicate whether it is a default data mapping rule; The number of packet filters; a priority value of the data mapping rule; The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule; List of packet filters.

17. The method according to claim 16, wherein: The packet filter list includes at least one of the following: The direction of the packet filter; The identifier of the packet filter; The contents of the packet filter.

18. The method according to claim 12, wherein: The data to be transmitted includes at least one of the following: data used for the artificial intelligence model, data generated by the artificial intelligence model, and perception data.

19. The method according to claim 12, wherein: The first node is a base station, and the second node is a terminal.

20. A communication device, comprising: Memory and processor; Memory and processor coupling; The memory is used to store instructions executable by the processor; When the processor executes the instructions, the processor performs the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 19.

21. A computer-readable storage medium having computer instructions stored thereon, wherein when the computer instructions are executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 11, or to execute the method according to any one of claims 12 to 19.

Images