Data transmission method, data receiving method, communication device and storage medium
By mapping the data to be transmitted to DRB and sent through DRB in the field of wireless communication, the problem of inefficient data transmission in AI technology applications is solved, and more efficient data transmission and lower delay are achieved.
Patent Information
- Application Number
- CN202311663890.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-01
- Publication Date
- 2025-06-03
AI Technical Summary
When the prior art uses AI technology in the field of wireless communication, data transmission efficiency is low and there is a high interaction delay, making it difficult to meet the timeliness requirements of some scenarios.
A data transmission method is provided. The first node maps the data to be transmitted onto the data wireless bearer DRB and sends the data to be transmitted to the second node through the DRB, reducing dependence on other network devices and saving signaling overhead.
It improves data transmission efficiency, ensures timeliness, reduces dependence on core network elements, and reduces the use of communication resources.
Smart Images

Figure CN120091297A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technologies, and in particular, to a data sending method, a data receiving method, a communication device, and a storage medium. Background Art
[0002] The application of artificial intelligence (AI) technology in the field of wireless communication has promoted the intelligent development of mobile communication networks and vertical industries. At the same time, the application of artificial intelligence technology has also put forward new capacity requirements for the current mobile communication network. For example, workflow requirements such as data collection, data preprocessing, model training, model inference, and model evaluation involved in AI technology.
[0003] Currently, AI technology is usually applied in the field of wireless communication in a "patchwork" and "plug-in" manner. The above methods are difficult to better combine with the mobile communication network, and the actual data transmission efficiency is low. Summary of the Invention
[0004] Embodiments of this application provide a data sending method, a data receiving method, a communication device, and a storage medium, which can solve the problem of low data transmission efficiency in related technologies.
[0005] On the one hand, a data sending method is provided, which is applied to a first node and includes: mapping data to be transmitted to a data radio bearer (DRB); sending the data to be transmitted to a second node through the DRB.
[0006] On the other hand, another data receiving method is provided, which is applied to a second node and includes: receiving the data to be transmitted sent by the first node on the DRB, where the first node is responsible for mapping the data to be transmitted to the DRB.
[0007] On the other hand, a first node is provided, including: a processing unit and a communication unit; the processing unit is used to map the data to be transmitted to a data radio bearer (DRB); the communication unit is used to send the data to be transmitted to a second node through the DRB.
[0008] On the other hand, a second node is provided, including: 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, where the first node is responsible for mapping the data to be transmitted to the DRB.
[0009] On the other hand, a communication device is provided, including: 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.
[0010] In another aspect, there is provided a computer-readable storage medium having computer program instructions stored thereon. 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.
[0011] In another aspect, there is provided a computer program product, which includes computer program instructions. 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.
[0012] In the embodiments of the present application, the first node maps the data to be transmitted onto a DRB and sends the data to be transmitted to the second node through the DRB. In the prior art, the data of a terminal usually needs to be transmitted to a target device through network links such as an access network, a bearer network, a core network, and a backbone network. During this process, the data transmission between the terminal and other network devices such as access network devices is usually indicated and managed by core network elements (such as AMF, SMF, UPF, etc.). However, for air interface-related intelligent or sensing application scenarios, such as CSI feedback optimization, beam management, and positioning, which mainly involve the interaction between the terminal and the base station, in the prior art, relevant data needs to be uploaded to the network side by the terminal or the base station for processing, occupying a large amount of communication resources, and there are problems such as high interaction latency and difficulty in meeting the timeliness requirements of some scenarios. In contrast, most of the processes of the data sending method provided in the present application only involve the first node and the second node, and there is no need or only a small part of the indication and management of data transmission by other network devices, saving signaling overhead while also ensuring timeliness, thereby improving the data transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] In order to more clearly illustrate the technical solutions in the present application, the drawings required to be used in some embodiments of the present application will be briefly introduced below. Obviously, the drawings in the following description are only the drawings of some embodiments of the present application, and those of ordinary skill in the art can also obtain other drawings based on these drawings.
[0014] Figure 1 It is an architecture diagram of a communication system provided in some embodiments of the present application;
[0015] Figure 2 It is a flowchart of a data sending method provided in some embodiments of the present application;
[0016] Figure 3 It is a flowchart of another data sending method provided in some embodiments of the present application;
[0017] Figure 4Flowchart of another data sending method provided by some embodiments of the present application;
[0018] Figure 5 Flowchart of a data receiving method provided by some embodiments of the present application;
[0019] Figure 6 Flowchart of another data receiving method provided by some embodiments of the present application;
[0020] Figure 7 Structural diagram of a first node provided by some embodiments of the present application;
[0021] Figure 8 Structural diagram of a second node provided by some embodiments of the present application;
[0022] Figure 9 Structural diagram of a communication device provided by some embodiments of the present application. Detailed implementation manners
[0023] Next, the technical solutions in the present application will be clearly and completely described in conjunction with the accompanying drawings in the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.
[0024] It should be noted that in the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly, using words such as "exemplary" or "for example" is intended to present related concepts in a specific manner.
[0025] Hereinafter, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of such features.
[0026] In the description of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The "and / or" herein is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, "at least one" means one or more, and "a plurality" means two or more.
[0027] The following explains the terms involved in the embodiments of the present application to facilitate readers' understanding.
[0028] (1) Quality of Service rule (QoS rule)
[0029] The QoS rule is used to indicate that the user equipment (UE) maps the uplink user plane data packets to a QoS flow. Subsequently, the UE (service data adaptation protocol (SDAP) layer) maps the uplink QoS flow to a data radio bearer (DRB).
[0030] The access and mobility management function network element (AMF) sends a QoS rules information element (IE) to the UE through the protocol data unit (PDU) session establishment / modification procedure.
[0031] Among them, the QoS rules IE includes multiple QoS rules, and each QoS rule is associated with one or more packet filter sets. The packet filter set is usually represented in the form of a packet filter list in the QoS rule.
[0032] Exemplarily, the QoS rules IE is shown in Table 1 below:
[0033] Table 1 QoS rules IE
[0034]
[0035] Among them, the QoS rules IEI is the unique identifier used to identify the QoS rule information element, usually represented by 1 octet. The AMF and the UE can identify and reference the QoS rule information element through the QoS rules IEI. The length of the QoS rules IE is used to indicate the size of the QoS rules IE. QoS rule 1 to QoS rule n are used to represent the multiple QoS rules included in the QoS rules IE.
[0036] Exemplarily, 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]
[0039]
[0040] Among them, 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, the rule opcode 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 number of packet filters is used to identify the number of packet filters in the QoS rule. The packet filter list is used to carry the packet filter information. The QoS rule precedence is used to define the priority level of the QoS rule, and the QoS flow identifier is used to identify the QoS flow.
[0041] (2) Packet filter set
[0042] Currently, there are two types of packet filter sets. One is the internet protocol (IP) packet filter set, and the other is the ethernet packet filter set. The packet filter set is usually used to map the data flow to the QoS flow according to the configured data mapping rules, so that the data can be transmitted according to the corresponding QoS rules.
[0043] The packet filter set contains multiple packet filters. The packet filter is used to define specific data filtering rules.
[0044] Currently, the packet filter consists of the following fields:
[0045] Packet filter direction (2 bits): Used to define the direction of the packet filter, where the direction types include upstream, downstream, or upstream and downstream.
[0046] Packet filter identifier (4 bits): Used to identify each packet filter.
[0047] Length of the packet filter contents (1 octet): Used to define the length of the packet filter contents.
[0048] Packet filter contents itself (variable number of octets): Used to define the specific content information of the packet filter.
[0049] Among them, there is a certain correspondence between the identifier and type of the packet filter, and each type corresponds to different packet filter contents. For example, for a packet filter of IPv4 remote address type, the contents of this packet filter are the IPv4 address and the address mask information. The following is the correspondence between some identifiers and types:
[0050] 0 0 0 0 0 0 0 1 Match-all type
[0051] 0 0 0 1 0 0 0 0 IPv4 remote address type
[0052] 0 0 0 1 0 0 0 1 IPv4 local address type
[0053] 0 0 1 0 0 0 0 1 IPv6 remote address / prefix length type
[0054] 0 0 1 0 0 0 1 1 IPv6 local address / prefix length type
[0055] 0 0 1 1 0 0 0 0 Protocol identifier / Next header type
[0056] 0 1 0 0 0 0 0 0 Single local port type
[0057] 0 1 0 0 0 0 0 1 Local port range type
[0058] 0 1 0 1 0 0 0 0 Single remote port type
[0059] 0 1 0 1 0 0 0 1 Remote port range type
[0060] 0 1 1 0 0 0 0 0 Security parameter index type
[0061] 0 1 1 1 0 0 0 0 Type of service / Traffic classtype
[0062] 1 0 0 0 0 0 0 0 Flow label type
[0063] 1 0 0 0 0 0 0 1 Destination MAC address type
[0064] 1 0 0 0 0 0 1 0 Source MAC address type
[0065] 1 0 0 0 0 0 1 1 802.1Q (a standard protocol) customer tag (C-TAG) virtual local area network identifier (VID) type
[0066] 1 0 0 0 0 1 0 0 802.1Q service tag (S-TAG) VID type
[0067] 1 0 0 0 0 1 0 1 802.1Q C-TAG priority codepoint / drop eligible indicator (PCP / DEI) type
[0068] 1 0 0 0 0 1 1 0 802.1Q S-TAG PCP / DEI type
[0069] 1 0 0 0 0 1 1 1 Ethertype type
[0070] Exemplarily, in combination 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 content of the packet filter set is shown in Table 3 below:
[0071] Table 3 Packet Filter List
[0072]
[0073]
[0074] Among them, the packet filter list includes packet filters 1 - packet filter N, and each packet filter includes fields such as direction, identification, length, content, etc.
[0075] (3) Packet Detection Rule (PDR)
[0076] PDR is used to define the detection and classification rules for data packets. Among them, the PDR also includes a packet filter set.
[0077] The Session Management Function (SMF) sends the PDR to the User Plane Function (UPF) through the N4 session management process (such as the N4 session establishment process or the N4 session modification process) of the N4 interface.
[0078] The UPF maps the downlink data packets to the QoS flow through the PDR. Then, the 5G Next Generation Radio Access Network (NG-RAN) maps the downlink QoS flow to the DRB.
[0079] Exemplarily, the content in the PDR includes:
[0080] 1. The uplink or downlink packet filter of the Service Data Flow (SDF) template;
[0081] 2. The PDR priority;
[0082] 3. QoS implementation rules, such as the maximum bit rate of the SDF, the guaranteed flow bit rate (GFBR), and the maximum bit rate of the guaranteed bit rate (GBR) QoS flow;
[0083] 4. Forwarding behavior rules;
[0084] 5. Reflected QoS indication.
[0085] The application of AI technology in the field of wireless communication has promoted the intelligent development of mobile communication networks and vertical industries. At the same time, the application of artificial intelligence technology has also put forward new capacity requirements for the current mobile communication network. For example, the workflow requirements involved in data collection, data preprocessing, model training, model inference, model evaluation, etc. in AI technology.
[0086] Facing the future vision of intelligent ubiquity, that is, the scenario of the integrated application of technologies such as the Internet, the Internet of Things, big data, and artificial intelligence, future wireless communication networks need to have built-in AI capabilities to achieve the deep integration design of the computing power, data, algorithms, connections, network functions, protocols, and processes required for AI services.
[0087] Currently, AI technology is usually applied in the field of wireless communication in a "patching" and "plug-in" manner, that is, concentrating AI-related processing on cloud servers. However, for scenarios in the field of wireless communication, such as the optimization of channel state information (CSI) feedback related to the air interface, beam management, and positioning, etc., the above method requires a large amount of data to be uploaded from the UE or RAN to the cloud server, which will consume a large amount of communication resources and there is a large interaction delay, and it cannot meet the real-time requirements of the above scenarios.
[0088] In summary, the current solutions are difficult to be better combined with mobile communication networks, and the actual data transmission efficiency is low.
[0089] The future wireless network architecture needs to support built-in AI, that is, to provide a complete operating environment for the entire life cycle of AI technology inside the network architecture. After supporting built-in AI, the data generation sources will also change. In addition to applications / servers, data generation will also include network devices such as UEs and RANs. Therefore, network devices such as UEs and RANs also need to have functions such as data collection, model training, and model storage, and at the same time, corresponding data transmission solutions are also required.
[0090] In view of this, an embodiment of the present application provides a data sending method. A first node maps 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, data of a terminal usually needs to be transmitted to a target device through network links such as an access network, a bearer network, a core network, and a backbone network. During this process, a core network element (such as an AMF, an SMF, a UPF, etc.) usually instructs and manages the data transmission between the terminal and other network devices such as an access network device.
[0091] However, for intelligent or sensing application scenarios related to the air interface, such as CSI feedback optimization, beam management, and positioning, which mainly involve scenarios of interaction between a terminal and a base station, the prior art needs to upload relevant data to the network side through the terminal or the base station for processing, occupying a large amount of communication resources, and there are problems of high interaction delay and difficulty in meeting the timeliness requirements of some scenarios. In contrast, most of the processes of the data sending method provided by the present application only involve the first node and the second node, and do not require or only require a small part of the indication and management of data transmission by other network devices, saving signaling overhead while ensuring timeliness, thereby improving the data transmission efficiency.
[0092] The implementation manners of the embodiments of the present application will be described in detail below with reference to the accompanying drawings of the specification.
[0093] Figure 1 It is an architecture diagram of a communication system 10 provided by an embodiment of the present application. As Figure 1 shown, the communication system 10 includes: a terminal 101 and a base station 102.
[0094] Among them, the terminal 101 and the base station 102 are connected through a communication link. The communication link can be a wired communication link or a wireless communication link, and the present application does not limit this.
[0095] 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 FDMA (SC-FDMA), and other systems. The term "system" can be interchanged with "network". CDMA systems can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA can include Wideband CDMA (WCDMA) technology and other CDMA variant technologies. CDMA2000 can cover Interim Standard (IS) 2000 (IS-2000), IS-95, and IS-856 standards. TDMA systems can implement wireless technologies such as Global System for Mobile Communication (GSM), etc. OFDMA systems can implement wireless technologies such as Evolved Universal Terrestrial Radio Access (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 its evolved versions. 3GPP's Long Term Evolution (LTE) and various versions evolved based on LTE are new versions of UMTS using E-UTRA. The communication system 10 can also be a 5G communication system, New Radio (NR), and 6G communication system. In addition, the communication system 10 can also be applicable to future-oriented communication technologies, and the technical solutions provided by the embodiments of the present application are applicable to all of them.
[0096] The terminal 101 is a device with wireless communication capabilities that can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted. It can also be deployed on water (such as ships, etc.). It can also be deployed in the air (such as airplanes, balloons, satellites, etc.). The terminal 101 is also known as user equipment (UE), mobile station (MS), mobile terminal (MT), and terminal device, etc. It is a device that provides voice and / or data connectivity to users. For example, the terminal 101 includes handheld devices, vehicle-mounted devices, etc. with wireless connection capabilities. Currently, the terminal 101 can be: a mobile phone, a tablet computer, a laptop computer, a palm computer, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), a vehicle-mounted device (such as a car, a bicycle, an electric vehicle, 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.), a smart 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, a flying device (such as a smart robot, a hot air balloon, a drone, an airplane), etc. In a possible application scenario of this application, the terminal is a terminal that often works on the ground, such as a vehicle-mounted device. In this application, for the convenience of description, the chips deployed in the above devices, such as a System-On-a-Chip (SOC), a baseband chip, etc., or other chips with communication capabilities can also be called a terminal.
[0097] The terminal 101 can be a vehicle with corresponding communication capabilities, or a vehicle-mounted communication device, or other embedded communication devices, or it can be a user's handheld communication device, including a mobile phone, a tablet computer, etc.
[0098] As an example, in the embodiment of the present application, the terminal 101 may also be a wearable device. A wearable device, also known as a wearable intelligent device, is a general term for devices developed by applying wearable technologies to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that can be directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for physical sign monitoring.
[0099] The base station 102 is a device located on the access network side of the above communication system and having a wireless transceiver function, or a chip or chip system that can be disposed in the device. The base station 102 includes, but is not limited to: access points (APs) in a WiFi system, such as home gateways, routers, servers, switches, bridges, etc., evolved NodeBs (eNBs), radio network controllers (RNCs), NodeBs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs, or home NodeBs, HNBs), base band units (BBUs), wireless relay nodes, wireless backhaul nodes, transmission and reception points (TRPs or TPs), 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 (including multiple antenna panels) of antenna panels of a base station in a 5G system, or it can also be a network node constituting a gNB or a transmission point, such as a base band unit (BBU), or a distributed unit (DU), a road side unit (RSU) with base station functions, or an NG radio access network (NG-Ran) device, etc. The base station 102 also includes base stations in different networking modes, such as master evolved NodeBs (MeNBs), secondary eNBs (SeNBs, or secondary gNBs, SgNBs). The base station 102 also includes different types, such as terrestrial base stations, aerial base stations, and satellite base stations, etc.
[0100] 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 after the terminal 101 and the base station 102 itself generate data to be transmitted (such as data for an artificial intelligence model, data generated by an artificial intelligence model, perception data, etc.), data transmission is performed for the generated data to be transmitted.
[0101] Exemplarily, the data transmission scenario may include the following situations:
[0102] Scenario 1: The terminal 101 is used to send a first data request message to the base station 102. Correspondingly, the base station 102 is used to receive the first data request message from the terminal 101.
[0103] The first data request message is used to request the base station 102 to send the data to be transmitted.
[0104] Exemplarily, the data to be transmitted is local data generated by the base station 102 itself, such as data like the training model locally generated by the base station 102, intermediate results of inference, etc.
[0105] The base station 102 is used to send the data to be transmitted to the terminal 101. Correspondingly, the terminal 101 is used to receive the data to be transmitted from the base station 102.
[0106] Scenario 2: The terminal 101 is used to send a second data request message to the base station 102. Correspondingly, the base station 102 is used to receive the second data request message from the terminal 101.
[0107] The second data request message is used to request the base station 102 to authorize the terminal 101 to send the data to be transmitted to the base station 102. Similarly, the data to be transmitted is local data generated by the base station 102 itself, such as data like the training model locally generated by the terminal 101, intermediate results of inference, etc.
[0108] The base station 102 is further used to confirm whether to authorize the terminal 101 to send the data to be transmitted.
[0109] The terminal 101 is further used to send the data to be transmitted to the base station 102. Correspondingly, the base station 102 is used to receive the data to be transmitted from the terminal 101.
[0110] Scenario 3: The base station 102 is used to send a third data request message to the terminal 101. Correspondingly, the terminal 101 is used to receive the third data request message from the base station 102.
[0111] The third data request message is used to request the terminal 101 to send the data to be transmitted.
[0112] The terminal 101 is used to send the data to be transmitted to the base station 102. Correspondingly, the base station 102 is used to receive the data to be transmitted from the terminal 101.
[0113] Scenario 4: The base station 102 is used to send a fourth data request message to the terminal 101. Correspondingly, the terminal 101 is used to receive the fourth data request message from the base station 102.
[0114] The fourth data request message is used to request the terminal 101 to authorize the base station 102 to send the data to be transmitted to the terminal 101.
[0115] The terminal 101 is further configured to confirm whether to authorize the base station 102 to send the data to be transmitted.
[0116] The base station 102 is configured to send the data to be transmitted to the terminal 101. Correspondingly, the terminal 101 is configured to receive the data to be transmitted from the base station 102.
[0117] Currently, the terminal 101 and the base station 102 usually perform data transmission by establishing a data radio bearer (DRB). Therefore, the terminal 101 and the base station 102 need to have a certain computing power, storage, and data processing capabilities.
[0118] Among them, the terminal 101 and the base station 102 need to implement the mapping of the data file / stream to be transmitted to the QoS flow to the DRB, or the mapping of the data file / stream 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.
[0119] It should be noted that the embodiments of the present application can learn from or refer to each other. For example, the same or similar steps, method embodiments, system embodiments, and device embodiments can all refer to each other without limitation.
[0120] Figure 2 This is a flowchart of a data sending method provided by an embodiment of the present application. As Figure 2 shown, the method includes the following steps:
[0121] Step 201, the first node maps the data to be transmitted onto a data radio bearer DRB.
[0122] Among them, the first node may be an access network related node device, such as a base station or a terminal. The data to be transmitted is local data generated by the first node.
[0123] Currently, applying AI technology in the field of wireless communication is a development trend of future mobile communication networks. The application of AI technology poses new capability requirements for the current mobile communication network, such as workflow requirements for data collection, data preprocessing, model training, model inference, model evaluation, etc. involved in AI technology.
[0124] In view of the above technical scenarios, the present application provides a data sending method to realize the data transmission of related data generated by AI technology between the terminal and the base station.
[0125] Exemplarily, the data to be transmitted may include at least one of the following: data for an artificial intelligence model, data generated by an artificial intelligence model, and perception data.
[0126] Step 202, the first node sends the data to be transmitted to the second node through the DRB.
[0127] Among them, the second node may be a node device related to the access network, such as a base station or a terminal.
[0128] In a possible implementation, the first node is a base station and the second node is a terminal. Or, the first node is a terminal and the second node is a base station.
[0129] When the first node is a base station and the second node is a terminal, after the base station generates the data to be transmitted by itself, it can map the data to be transmitted onto the DRB and send the data to be transmitted to the terminal through the DRB.
[0130] When the first node is a terminal and the second node is a base station, after the terminal generates the data to be transmitted by itself, it can map the data to be transmitted onto 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.
[0131] From the above two scenarios, it can be seen that the data to be transmitted mainly involves the interaction between two node devices, namely the terminal and the base station, and no other node devices are required to participate in the above data transmission process. In the prior art, when data is transmitted, it passes through network links such as the access network, bearer network, core network, and backbone network, and the relevant network elements in the core network manage and configure the data transmission process.
[0132] Obviously, for the above scenarios involved in the embodiments of the present application, the solution of transmitting data to core network network elements such as UPF for data mapping will cause additional resource overhead and increase the transmission delay.
[0133] In summary, the embodiments of the present application provide a data sending method, in which the first node maps the data to be transmitted onto the DRB and sends the data to be transmitted to the second node through 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. During this process, the relevant network elements in the core network (such as network elements such as AMF, SMF, and UPF) usually indicate and manage the data transmission between the terminal and other network devices such as access network devices.
[0134] However, for air interface related intelligent or sensing application scenarios, such as CSI feedback optimization, beam management, and positioning, which mainly involve the interaction between the terminal and the base station, the prior art needs to upload relevant data to the network side through the terminal or the base station for processing, occupying a large amount of communication resources, and there are problems such as high interaction delay and difficulty in meeting the timeliness requirements of some scenarios. In contrast, most of the processes of the data sending method provided by the present application only involve the first node and the second node, and other network devices do not need to participate, or only provide indications for data transmission, saving signaling overhead while ensuring timeliness, thereby improving the data transmission efficiency.
[0135] Next, the process of the first node data mapping will be introduced.
[0136] As a possible embodiment of the present application, in combination with Figure 2 , as Figure 3 shown, the above step 201 can be implemented through the following step 301.
[0137] Step 301: The first node maps the data to be transmitted to the DRB based on the data mapping rule.
[0138] Among them, the data mapping rule is used to filter and group the data.
[0139] In a possible implementation manner, the data mapping rule includes at least one of the following:
[0140] The identifier of the data mapping rule;
[0141] The length of the data mapping rule;
[0142] The indication information used to indicate whether it is the default data mapping rule;
[0143] The number of packet filters;
[0144] The priority value of the data mapping rule;
[0145] The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule;
[0146] The packet filter list.
[0147] Exemplarily, the identifier of the data mapping rule can be the QoS rule ID field, which is used to identify the data mapping rule.
[0148] The length of the data mapping rule can be the length of QoS rule field, which is used to characterize the content length of the data mapping rule.
[0149] The indication information used to indicate whether it is the default data mapping rule can be the 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.
[0150] The number of packet filters can be the number of packet filters field, which is used to characterize the number of packet filters in the data mapping rule.
[0151] The priority value of the data mapping rule can be the QoS rule precedence field, which is used to characterize the relative priority of the data mapping rule, that is, the matching order of the data with multiple data mapping rules.
[0152] The identifier of the QoS flow associated with the data mapping rule can be the QoS flow identifier field (QFI), which is used to identify a QoS flow. The identifier of the DRB associated with the data mapping rule can be the 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.
[0153] The packet filter list can be the packet filter list field, which is used to carry packet filter information.
[0154] In a possible implementation, the packet filter list includes at least one of the following:
[0155] The direction of the packet filter;
[0156] The identifier of the packet filter;
[0157] The content of the packet filter.
[0158] Among them, the direction of the packet filter can be the packet filter direction field, which is used to characterize the data flow direction mapped by the packet filter, including the uplink direction, the downlink direction, or the uplink and downlink directions. The identifier of the packet filter can be the packet filter identifier field, which is used to identify the packet filter. The content of the packet filter is used to carry the conditional information of specific data packet filtering.
[0159] The packet filters in the packet filter list are the packet filters in the data packet filter set. The current data packet filter set includes an IP packet filter set and an Ethernet packet filter set. However, the above two data packet filter sets are mainly for end-to-end data transmission and are not applicable to the local data between the terminal and the base station involved in this application.
[0160] In response to this, the embodiments of this application provide a RAN-based data packet filter set: the local data packet filter set (localdata filter set) is used to implement the packet filtering of the data generated inside the base station or the terminal.
[0161] Among them, the local data packet filter set includes one or more packet filters, which are used to map the data to be transmitted by the first node or the second node to a QoS flow or to a DRB.
[0162] In a possible implementation, the content of the packet filter includes at least one of the following:
[0163] Source IP address type;
[0164] Destination IP address type;
[0165] Source port number;
[0166] Destination port number;
[0167] Source component identifier;
[0168] Destination component identifier;
[0169] Service type.
[0170] Among them, the source IP address type can be the type of source IP address field, which is used to match the source IP address of the data stream. The destination IP address type can be the type of destination IP address field, which is used to match the destination IP address of the data stream.
[0171] The source port number can be the source port number field, which is used to match the source port number of the data stream. The destination port number can be the destination port number field, which is used to match the destination port number of the data stream.
[0172] The source component identifier can be the source assembly ID field, which is used to match the source component of the data stream. The destination component identifier can be the destination assembly ID field, which is used to match the destination component of the data stream. In the embodiments of the present application, the data to be transmitted between the terminal and the base station can be matched through the source component and the destination component.
[0173] The service type can be the type of service field, which is used to match the service corresponding to the data stream. Exemplarily, the service type can include services such as AI model training, AI model inference, and perception.
[0174] In this way, the first node in the present application can map the 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 rule, so as to achieve the priority guarantee for different sources (source address, source port, source component), different destinations (destination address, destination port, destination component), and different service types.
[0175] Currently, for end-to-end downlink data, the UPF usually maps the 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 according to this QoS configuration.
[0176] For end-to-end uplink data, the SMF sends the QoS to the terminal, and the terminal maps the uplink user data to the QoS flow according to this data mapping rule. Then, the terminal (SDAP layer) maps the QoS flow to the DRB.
[0177] Among them, the mapping of the data stream to the QoS flow belongs to the operation at the non-access stratum (NAS) level, and the mapping of the QoS flow to the DRB belongs to the operation at the access stratum (AS) level.
[0178] For the data to be transmitted in the embodiments of the present application, it mainly involves the data transmission between the base station and the terminal. Therefore, in the present application, the first node can map the data to be transmitted to the QoS flow and then map the QoS flow to the DRB, or directly map the data to be transmitted to the DRB.
[0179] In a possible implementation manner, the first node directly maps the data to be transmitted to the DRB based on the first data mapping rule.
[0180] Exemplarily, the first data mapping rule may include the identifier of the DRB associated with the first data mapping rule.
[0181] In another possible implementation manner, the first node maps the data to be transmitted to the Quality of Service flow (QoS flow) based on the second data mapping rule. Then, the first node maps the QoS flow to the DRB.
[0182] Exemplarily, the second data mapping rule may include the identifier of the QoS flow associated with the second data mapping rule.
[0183] Next, the process of the first node sending the data mapping rule to the second node will be introduced.
[0184] As a possible embodiment of the present application, in combination with Figure 2 , as Figure 4 shown, this method further includes the following steps 401-402.
[0185] Step 401: The first node receives the first message sent by the second node.
[0186] Among them, the first message is used to request the establishment of a data transmission connection.
[0187] As can be seen from the above solution, after the first node generates the data to be transmitted, it can map the data to be transmitted to the DRB through the data mapping rule for data transmission. Similarly, after the second node generates the data to be transmitted, it also needs to perform mapping through the data mapping rule. Therefore, the second node can obtain the data mapping rule from the first node by means of a message request.
[0188] It should be noted that for the process of the second node sending the data to be transmitted to the first node, the relevant technical solutions of the first node sending the data to be transmitted to the second node in the embodiments of the present application can be referred to, and the present application will not elaborate on this.
[0189] Step 402: The first node sends a second message to the second node.
[0190] Among them, the second message is used to respond to the first message. When the first node receives the first message, it can send a second message to the second node to instruct the second node to establish a data transmission connection.
[0191] It should be noted that the present application does not limit the execution order of step 401 - step 402 and the above 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, step 401 - step 402 can be executed before the above step 201 or after step 201. Figure 4 Only taking the case where step 401 - step 402 is executed before step 201 as an example, the data sending method provided by the present application will be described.
[0192] In a possible implementation manner, the second message includes a data mapping rule.
[0193] Exemplarily, the second message is a radio resource control (RRC) message or a media access control unit (MAC control element, MAC CE).
[0194] Currently, in the prior art, the AMF sends a data mapping rule to the terminal through the PDU session establishment / modification process. This data mapping rule is carried on the NAS message.
[0195] Since the present application mainly involves data transmission between a first node and a second node, the second message may 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 rule from the first node to the second node without passing through other network element devices (such as the core network element AMF, etc.). At the same time, messages at the access layer such as RRC messages and MAC CE have lower signaling latency and smaller signaling overhead compared to messages at the non-access layer. Therefore, the above solution of the present application can further reduce the consumption of additional communication resources and ensure the timeliness of data transmission.
[0196] Among them, for the RRC message, the second message in the present application can adopt a new data transmission message format or be based on the message format of the current NAS message.
[0197] An example is that for an RRC message adopting a new data transmission message format, the Abstract Syntax Notation One (ASN.1) encoding format of the data mapping rule in the second message in the present application is as follows:
[0198]
[0199]
[0200] Among them, the QoSRulelist field is used to represent the QoS rule list and is represented in the form of a sequence. The QoSRule field is used to represent the QoS rule and is represented in the form of a sequence.
[0201] The LocalDataMappingContents field is used to represent the content of the data mapping rule, which includes fields such as source / destination IP address type, source / destination port number type, source / destination component identifier, and service type.
[0202] Another example is that for the current RRC message carrying the encapsulated NAS message, the encoding format of the data mapping rule in the second message in the present application is as shown in Table 4 below:
[0203] Table 4 Data Mapping Rule
[0204]
[0205] It should be noted that when the data mapping rule is the first data mapping rule (i.e., 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 associate with the corresponding DRB.
[0206] When the data mapping rule is the second data mapping rule (i.e., the data mapping rule that maps the data to be transmitted to the QoS flow), the QFI / DRB identifier in Table 4 selects the QFI field to associate with the corresponding QoS flow.
[0207] In another example, for the second message in the MAC CE message format, the coding format of the data mapping rule in this application is shown in Table 5 below:
[0208] Table 5 Data mapping rule
[0209]
[0210]
[0211] It should be noted that when the data mapping rule is the first data mapping rule (i.e., 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 associate with the corresponding DRB.
[0212] When the data mapping rule is the second data mapping rule (i.e., the data mapping rule that maps the data to be transmitted to the QoS flow), the QFI / RB identifier in Table 5 selects the QFI field to associate with the corresponding QoS flow.
[0213] Figure 5 It is a flowchart of a data receiving method provided by an embodiment of this application. As Figure 5 shown, the method includes the following steps:
[0214] Step 501, the second node receives the data to be transmitted sent by the first node on the DRB.
[0215] Among them, the first node is responsible for mapping the data to be transmitted onto the DRB.
[0216] 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.
[0217] Based on the above technical solution, an embodiment of this application provides a data receiving method, where the second node receives 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 onto 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. During this process, the core network elements (such as AMF, SMF, UPF, etc.) usually indicate and manage the data transmission between the terminal and other network devices such as access network devices.
[0218] However, for air interface-related intelligent or sensing application scenarios, such as CSI feedback optimization, beam management, and positioning, which mainly involve scenarios of interaction between the terminal and the base station, the existing technologies need to upload relevant data to the network side through the terminal or the base station for processing, occupying a large amount of communication resources, and there are problems of high interaction latency and difficulty in meeting the timeliness requirements of some scenarios. In contrast, the data sending 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 instructions for data transmission, saving signaling overhead while ensuring timeliness, thereby improving the data transmission efficiency.
[0219] Next, the process of the second node receiving the data mapping rule sent by the second node will be introduced.
[0220] As a possible embodiment of this application, in combination with Figure 5 , as Figure 6 shown, the method further includes the following steps 601 - step 602.
[0221] Step 601, the second node sends a first message to the first node.
[0222] Among them, the first message is used to request the establishment of a data transmission connection.
[0223] Specifically, reference can be made to the relevant description in step 401 above, and details will not be elaborated here.
[0224] Step 602, the second node receives a second message sent by the first node.
[0225] Among them, the second message is used to respond to the first message.
[0226] In a possible implementation manner, the second message includes a data mapping rule.
[0227] Among them, the relevant solutions for the data mapping rule can be referred to the above relevant description, and details will not be elaborated here.
[0228] Exemplarily, the second message is a radio resource control (RRC) message or a media access control element (MAC CE).
[0229] Currently, in the existing technology, the AMF sends the data mapping rule to the terminal through the PDU session establishment / modification process. This data mapping rule is carried on the NAS message.
[0230] Since the present application mainly involves data transmission between a first node and a 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 rule from the first node to the second node without passing through other network element devices (such as the core network element AMF, etc.). At the same time, access layer messages such as RRC messages and MAC CEs have lower signaling latency and smaller signaling overhead compared to non-access layer messages. Therefore, the above solution of the present application can further reduce the consumption of additional communication resources and ensure the timeliness of data transmission.
[0231] It can be understood that in order for a communication device to implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining 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 certain function is executed in the form of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.
[0232] The embodiments of the present application can divide the communication device into function modules according to the above method embodiments. For example, each function module can be divided corresponding to each function, or two or more functions can be integrated into one function module. The above integrated module can be implemented in the form of hardware or software. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation. The following takes the example of dividing each function module corresponding to each function for illustration.
[0233] For example, taking the communication device as the first node in the above method embodiment as an example, Figure 7 is a schematic structural diagram of a first node provided by an embodiment of the present application. The first node can execute the data sending method provided by the above method embodiment. As Figure 7 shown, the first node 70 includes: a processing unit 701 and a communication unit 702.
[0234] The processing unit 701 is configured to map the data to be transmitted onto a data radio bearer (DRB).
[0235] The communication unit 702 is configured to send the data to be transmitted to the second node through the DRB.
[0236] In some embodiments, the processing unit 701 is configured to map the data to be transmitted onto the DRB based on a data mapping rule.
[0237] In some embodiments, the processing unit 701 is configured to directly map the data to be transmitted to the DRB based on the first data mapping rule.
[0238] In some embodiments, the processing unit 701 is configured to map the data to be transmitted to a Quality of Service flow (QoS flow) based on the second data mapping rule, and map the QoS flow to the DRB.
[0239] In some embodiments, the communication unit 702 is configured to receive a first message sent by a second node, where the first message is used to request the establishment of a data transmission connection, and the communication unit 702 is configured to send a second message to the second node, where the second message is used to respond to the first message.
[0240] In some embodiments, the second message includes a data mapping rule.
[0241] In some embodiments, the second message is a Radio Resource Control (RRC) message or a Medium Access Control Control Element (MAC CE).
[0242] In some embodiments, the data mapping rule includes at least one of the following:
[0243] The identifier of the data mapping rule;
[0244] The length of the data mapping rule;
[0245] The indication information used to indicate whether it is a default data mapping rule;
[0246] The number of packet filters;
[0247] The priority value of the data mapping rule;
[0248] The identifier of the QoS flow associated with the data mapping rule, or the identifier of the DRB associated with the data mapping rule;
[0249] The packet filter list.
[0250] In some embodiments, the packet filter list includes at least one of the following:
[0251] The direction of the packet filter;
[0252] The identifier of the packet filter;
[0253] The content of the packet filter.
[0254] In some embodiments, the data to be transmitted includes at least one of the following: data for an artificial intelligence model, data generated by an artificial intelligence model, and perception data.
[0255] In some embodiments, the first node 70 is a base station, and the second node is a terminal.
[0256] Taking the communication device as the second node in the above method embodiment as an example, Figure 8 FIG. is a schematic structural diagram of a second node provided by an embodiment of the present application. The second node can execute the data receiving method provided by the above method embodiment. As Figure 8 shown, the second node 80 includes: a processing unit 801 and a communication unit 802.
[0257] The communication unit 802 is configured 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 onto the DRB.
[0258] In some embodiments, the communication unit 802 is configured 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 configured to receive a second message sent by the first node, where the second message is used to respond to the first message.
[0259] In some embodiments, the second message includes a data mapping rule.
[0260] In some embodiments, the second message is a radio resource control (RRC) message or a media access control control element (MAC CE).
[0261] In some embodiments, the data mapping rule includes at least one of the following:
[0262] An identifier of the data mapping rule;
[0263] The length of the data mapping rule;
[0264] An indication information for indicating whether it is a default data mapping rule;
[0265] The number of packet filters;
[0266] The priority value of the data mapping rule;
[0267] An identifier of a QoS flow associated with the data mapping rule, or an identifier of a DRB associated with the data mapping rule;
[0268] A packet filter list.
[0269] In some embodiments, the packet filter list includes at least one of the following:
[0270] The direction of the packet filter;
[0271] The identifier of the packet filter;
[0272] The content of the packet filter.
[0273] In some embodiments, the data to be transmitted includes at least one of the following: data for an artificial intelligence model, data generated by the artificial intelligence model, and sensing data.
[0274] In some embodiments, the first node is a base station and the second node 80 is a terminal.
[0275] When the functions of the above integrated modules are implemented in the form of hardware, another possible structure of the communication device involved in the above embodiments is provided by the embodiments of the present application. As Figure 9 shown, the communication device 90 includes: a processor 902, and a bus 904. Optionally, the communication device may further include a memory 901; optionally, the communication device may further include a communication interface 903.
[0276] The processor 902 may be used to implement or execute various exemplary logic blocks, modules, and circuits described in connection with the embodiments of the present application. The 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 devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in connection with the embodiments of the present application. The 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, etc.
[0277] The communication interface 903 is used to connect to other devices through a communication network. The communication network may be an Ethernet, a radio access network, a wireless local area network (WLAN), etc.
[0278] 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 magnetic 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.
[0279] As a possible implementation, the memory 901 may exist independently of the processor 902. The memory 901 may be connected to the processor 902 via a bus 904 and is used to store instructions or program codes. When the processor 902 calls and executes the instructions or program codes stored in the memory 901, the data sending method provided by the embodiments of the present application or the data receiving method provided by the embodiments of the present application can be implemented.
[0280] In another possible implementation, the memory 901 may also be integrated with the processor 902.
[0281] The bus 904 may be an extended industry standard architecture (EISA) bus or the like. The bus 904 may be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 9 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.
[0282] Some embodiments of the present application provide a computer-readable storage medium (for example, a non-transitory computer-readable storage medium). Computer program instructions are stored in the computer-readable storage medium. When the computer program instructions 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.
[0283] Exemplarily, the above computer-readable storage medium may include, but is not limited to: magnetic storage devices (such as hard disks, floppy disks or magnetic tapes, etc.), optical discs (such as Compact Disks (CDs), Digital Versatile Disks (DVDs), etc.), smart cards and flash memory devices (such as Erasable Programmable Read-Only Memories (EPROMs), cards, sticks or key drives, etc.). The various computer-readable storage media described in the present application 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 that can store, contain and / or carry instructions and / or data.
[0284] The embodiments of the present application provide a computer program product containing instructions. When the computer program product runs 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.
[0285] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A data sending method, characterized in that, applied to a first node, the method includes: mapping data to be transmitted onto a data radio bearer (DRB); sending the data to be transmitted to a second node through the DRB.
2. The method according to claim 1, characterized in that, the mapping of the data to be transmitted onto the data radio bearer (DRB) includes: mapping the data to be transmitted onto the DRB based on a data mapping rule.
3. The method according to claim 2, characterized in that, the mapping of the data to be transmitted onto the DRB based on the data mapping rule includes: directly mapping the data to be transmitted onto the DRB based on a first data mapping rule.
4. The method according to claim 2, characterized in that, the mapping of the data to be transmitted onto the DRB based on the data mapping rule includes: mapping the data to be transmitted onto a quality of service flow (QoS flow) based on a second data mapping rule; mapping the QoS flow onto the DRB.
5. The method according to claim 1, characterized in that, 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, the first message being used to request the establishment of a data transmission connection; sending a second message to the second node, the second message being used to respond to the first message.
6. The method according to claim 5, characterized in that, the second message includes a data mapping rule.
7. The method according to claim 5, characterized in that, 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, characterized in that, the data mapping rule includes at least one of the following: the identifier of the data mapping rule; the length of the data mapping rule; indication information for indicating whether it is a default data mapping rule; the number of packet filters; the 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; a packet filter list.
9. The method according to claim 8, characterized in that, the packet filter list includes at least one of the following: the direction of the packet filter; the identifier of the packet filter; the content of the packet filter.
10. The method according to claim 1, characterized in that, the data to be transmitted includes at least one of the following: data for an artificial intelligence model, data generated by an artificial intelligence model, and sensing data.
11. The method according to claim 1, characterized in that, the first node is a base station and the second node is a terminal.
12. A data receiving method, characterized in that, applied to a second node, the method includes: receiving data to be transmitted sent by a first node on a DRB, the data to be transmitted being mapped onto the DRB by the first node.
13. The method according to claim 12, characterized in that, 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 the establishment of a data transmission connection; Receiving a second message sent by the first node, where the second message is used to respond to the first message.
14. The method according to claim 13, wherein, the second message includes a data mapping rule.
15. The method according to claim 13, wherein, the second message is a Radio Resource Control (RRC) message or a Medium Access Control Element (MAC CE).
16. The method according to claim 14, wherein, the data mapping rule includes at least one of the following: the identifier of the data mapping rule; the length of the data mapping rule; indication information for indicating whether it is a default data mapping rule; the number of packet filters; the 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; a packet filter list.
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 content 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 for an artificial intelligence model, data generated by an 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, wherein, it includes: a memory and a processor; the memory is coupled to the processor; the memory is used to store instructions executable by the processor; when the processor executes the instructions, it executes the method according to any one of claims 1 to 11, or executes the method according to any one of claims 12 to 19.
21. A computer-readable storage medium, wherein, computer instructions are stored on the computer-readable storage medium, and when the computer instructions run on a computer, the computer is caused to execute the method according to any one of claims 1 to 11, or execute the method according to any one of claims 12 to 19.
Citation Information
Cited By
Data sending method, data receiving method, communication device, and storage medium
EP4815613A1