Data transmission method and apparatus, communication device and storage medium

Abstract

The present application belongs to the technical field of communications. Disclosed are a data transmission method and apparatus, a communication device and a storage medium. The data transmission method in the embodiments of the present application comprises: a terminal sending a first message by means of a first bearer, and / or receiving a second message by means of the first bearer, wherein the first message includes first data of at least one Internet-of-Things device, and the second message includes second data that needs to be sent to the at least one Internet-of-Things device; and the first bearer meets at least one of the following: the first bearer being a bearer dedicated to transmitting data of an Internet-of-Things device, the first message sent by means of the first bearer further including identification information used for identifying the Internet-of-Things device to which the first data belongs, and the second message received by means of the first bearer further including identification information used for identifying an Internet-of-Things device which receives the second data.

Description

A data transmission method, apparatus, communication device, and storage medium

[0001] Cross-reference of related applications

[0002] This application claims priority to Chinese Patent Application No. 202411906679.0, filed on December 23, 2024, entitled "A Data Transmission Method, Apparatus, Communication Equipment and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a data transmission method, apparatus, communication equipment, and storage medium. Background Technology

[0004] The Ambient Internet of Things (AIoT), also known as the Ambient Power-enabled IoT, corresponds to IoT services. In this technology, IoT devices are powered through energy harvesting. These devices may not have batteries or may have limited energy storage capacity (e.g., using a capacitor). Energy sources for harvesting include radio waves, light, motion, heat, or other suitable energy sources.

[0005] Currently, for some IoT services, IoT devices may need to communicate with core network equipment. For example, IoT devices need to report data to core network equipment, and core network equipment needs to send data to IoT devices to control them. Data transmission between IoT devices and core network equipment can be forwarded through intermediate nodes, such as terminals and access network equipment. However, current technologies do not provide methods for how intermediate nodes should forward data from IoT devices. Summary of the Invention

[0006] This application provides a data transmission method, apparatus, communication device, and storage medium, and provides a method for intermediate nodes to forward data from Internet of Things (IoT) devices.

[0007] Firstly, a data transmission method is provided, the method comprising:

[0008] The terminal sends a first message through the first bearer, and / or receives a second message through the first bearer;

[0009] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device.

[0010] The first bearer satisfies at least one of the following:

[0011] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0012] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0013] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0014] Secondly, a data transmission method is provided, the method comprising:

[0015] The access network device receives a first message through the first bearer and / or sends a second message through the first bearer;

[0016] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device.

[0017] The first bearer satisfies at least one of the following:

[0018] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0019] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0020] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0021] Thirdly, a data transmission device is provided for use in a terminal, the device comprising:

[0022] Transmitting module and / or receiving module;

[0023] The sending module is used to send a first message through the first bearer;

[0024] The receiving module is used to receive the second message through the first bearer;

[0025] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device;

[0026] The first bearer satisfies at least one of the following:

[0027] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0028] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0029] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0030] Fourthly, a data transmission apparatus is provided, applied to access network equipment, the apparatus comprising:

[0031] Transmitting module and / or receiving module;

[0032] The receiving module is used to receive a first message through a first bearer;

[0033] The sending module is used to send a second message through the first bearer;

[0034] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device;

[0035] The first bearer satisfies at least one of the following:

[0036] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0037] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0038] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0039] Fifthly, an apparatus for data transmission is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0040] In a sixth aspect, a communication device is provided, the communication device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first or second aspect.

[0041] In a seventh aspect, a communication device is provided, including a processor and a communication interface;

[0042] When the communication device is a terminal, the communication interface is used to: send a first message through a first bearer, and / or receive a second message through the first bearer;

[0043] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device.

[0044] The first bearer satisfies at least one of the following:

[0045] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0046] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0047] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0048] In addition, when the communication device is an access network device, the communication interface is used to: receive a first message through a first bearer, and / or send a second message through the first bearer;

[0049] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device.

[0050] The first bearer satisfies at least one of the following:

[0051] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0052] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0053] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0054] Eighthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0055] A ninth aspect provides a wireless communication system, comprising: a terminal and an access network device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the access network device is configured to perform the steps of the method described in the second aspect.

[0056] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0057] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0058] In this embodiment of the application, the terminal is able to send a first message through a first bearer and / or receive a second message through the first bearer; wherein, the first message includes first data of at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device;

[0059] The first load-bearing condition satisfies at least one of the following:

[0060] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0061] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0062] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0063] As can be seen, in the embodiments of this application, a new or independent bearer can be configured for the message carrying the data of the IoT device. That is, a first bearer dedicated to transmitting the data of the IoT device can be established. In this way, when there is data of the IoT device that needs to be forwarded, the terminal can transmit the message carrying the data of the IoT device through the new or independent first bearer, providing a method for the terminal to act as an intermediate node to forward the data of the IoT device.

[0064] The first message may also include the identification information of the IoT device to which the first data belongs, so that the data of different IoT devices can be distinguished by the identification information in the first message; the second message may also include the identification information of the IoT device receiving the second data, so that the identification information in the second message can be used to distinguish which data needs to be sent to which IoT devices.

[0065] Therefore, the embodiments of this application not only provide a method for forwarding data from IoT devices when the terminal acts as an intermediate node, but also enable data differentiation by carrying the identification information of the corresponding IoT devices, thereby further improving the accuracy of IoT data forwarding. Attached Figure Description

[0066] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0067] Figure 2 is a schematic diagram of the inventory process of the Tag Device in an embodiment of this application;

[0068] Figure 3 is one of the schematic diagrams of the topology of the environmental Internet of Things in the embodiments of this application;

[0069] Figure 4 is a second schematic diagram of the topology of the environmental Internet of Things in the embodiments of this application;

[0070] Figure 5 is a flowchart of a data transmission method in an embodiment of this application;

[0071] Figure 6 is a schematic diagram of the architecture of gNB Reader in the implementation of this application;

[0072] Figure 7 is a schematic diagram of the architecture of the UE Reader in the embodiment of this application;

[0073] Figure 8 is a flowchart illustrating the first example in an embodiment of this application;

[0074] Figure 9 is a flowchart illustrating a second example in an embodiment of this application;

[0075] Figure 10 is a flowchart illustrating the third example in the embodiments of this application;

[0076] Figure 11 is a flowchart of another data transmission method in an embodiment of this application;

[0077] Figure 12 is a flowchart of another data transmission method in an embodiment of this application;

[0078] Figure 13 is a structural block diagram of a data transmission device according to an embodiment of this application;

[0079] Figure 14 is a structural block diagram of another data transmission device in an embodiment of this application;

[0080] Figure 15 is a structural block diagram of another data transmission device in an embodiment of this application;

[0081] Figure 16 is a structural block diagram of a communication device according to an embodiment of this application;

[0082] Figure 17 is a structural block diagram of a terminal according to an embodiment of this application;

[0083] Figure 18 is a structural block diagram of a network-side device according to an embodiment of this application;

[0084] Figure 19 is a structural block diagram of another network-side device in an embodiment of this application. Specific Implementation

[0085] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0086] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0087] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0088] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, 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), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0089] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.

[0090] Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, wireless local area network (WLAN) access points (APs), or wireless Fidelity (WiFi) nodes, etc. The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0091] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0092] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0093] To facilitate understanding of the data transmission method in the embodiments of this application, the following related content will be introduced first:

[0094] I. Environmental Internet of Things (IoT), also known as Passive Internet of Things

[0095] "Passive Internet of Things" does not require a power source or batteries; it can perform computing and communication simply by collecting energy from the environment and can operate for extended periods.

[0096] The collected energy includes radio frequency energy, light energy, heat energy, and mechanical vibration energy. Radio Frequency Identification (RFID) and Near Field Communication (NFC) technologies are both based on short-range radio frequency energy harvesting and are widely used in public transportation cards, Electronic Toll Collection (ETC) systems, industrial equipment monitoring, wirelessly powered handheld devices, and wearable low-power devices.

[0097] II. Low-power Internet of Things (IoT) devices

[0098] Low-power IoT devices are a type of IoT device characterized by low overall power consumption, including low-power signal reception and low-power signal transmission. Due to their low overall power consumption, the energy for communication can be derived from the environment, such as wind power, kinetic energy, heat energy, and radio frequency (RF) signals. Low-power IoT devices can also be referred to as AIoT terminals, passive IoT devices, or response devices.

[0099] Low-power IoT devices can transmit signals in either method one or method two as follows:

[0100] Method 1: Signal transmission via backscattered RF signals; these devices can also be called electronic tags or radio frequency identification (RFID) tags.

[0101] Method 2: Some active tags have the ability to actively generate signals, but in order to achieve low power consumption of the device, the power consumption is generally less than 0 milliwatt decibels (dBm), for example, less than or equal to -10dBm.

[0102] III. AIoT Terminals

[0103] AIoT terminals have ultra-low complexity and ultra-low power consumption.

[0104] AIoT terminals can be classified based on factors such as energy source, energy storage capability, and whether they are passively or actively transmitting energy. Specifically, they can include the following three types of devices:

[0105] Device Type A: This is a passive device with no energy storage and no independent signal generation / amplification capability; it uses backscatter transmission. The power consumption of the terminal during signal reception or transmission is less than 1 microwatt or less than 10 microwatts.

[0106] Device Type B: A semi-passive device, also belonging to the broader category of passive devices; it has energy storage but lacks independent signal generation capabilities, i.e., it transmits via backscatter. The use of stored energy can include amplifying the reflected signal. Because it can store energy, the terminal can amplify the backscattered signal after collecting sufficient electrical energy, thus covering a longer distance. The power consumption of the terminal during signal reception or transmission falls between that of Type A and Type B.

[0107] Device Type C: Active Device; It features energy storage and independent signal generation capabilities, i.e., an active radio frequency component used for transmission. The communication capabilities of this type of terminal are similar to traditional IoT terminals. The power consumption of the terminal during signal reception or transmission is less than 1 milliwatt, or less than 10 milliwatts.

[0108] In addition, AIoT devices are cheaper and simpler. For example, a simple chip or barcode can be attached to luggage, items or pets for location tracking, and can be used for logistics, warehousing, pet management and other purposes.

[0109] Alternatively, it can be fixed to various industrial and medical equipment for equipment management;

[0110] Alternatively, they can be attached to cattle and sheep on livestock farms for ranch management;

[0111] Alternatively, it can be installed in a specific location for environmental monitoring and alarm processing, etc.

[0112] IV. Information Transmission Between Readers and Tag Devices in RFID

[0113] RFID is a traditional backscatter communication system whose primary design goal is to identify and read data from Base Station Controller (BSC) devices (i.e., Tag Devices) within the reader's coverage area. Since RFID was initially used for automated inventory management of large quantities of goods, the process of identifying and reading data from Tag Devices is also known as inventory management.

[0114] Taking an Evolved Packet Core (EPC) RFID system defined by the air interface protocol (ISO 18000-6c) as an example, Figure 2 illustrates a schematic diagram of the inventory process for a Tag Device. After the Reader sends a query command, the Tag Device responds with a reply. Taking RN16 as an example, the Tag Device generates a 16-bit random number and sends it to the Reader. Then, the Reader sends this sequence to the Tag Device via an ACK command. After the Tag Device successfully verifies RN16 in the ACK, it sends subsequent data (such as protocol control (PC)) to the reader.

[0115] In this context, RN16 represents a 16-bit random number; PacketCRC in Figure 2 represents packet cyclic redundancy check, and CW represents continuous wave; continuous wave illumination is one of the main power supply methods for AIoT devices.

[0116] In addition, the Reader's operation instructions are shown in Table 1.

[0117] Table 1 Examples of Operation Instructions

[0118] V. AIoT Topology Diagram

[0119] Figures 3 and 4 show two typical network topologies in AIoT communication. Figure 3 shows a scenario where the base station acts as a Reader, communicating directly with a passive IoT terminal (i.e., an AIoT terminal). Figure 4 shows a scenario where the base station communicates with an AIoT terminal through an intermediate node, where the intermediate node can be a UE Reader, and the existing Uu interface is reused between the UE Reader and the base station.

[0120] The data transmission method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0121] Referring to Figure 5, an embodiment of this application provides a data transmission method, which may include the following step 501:

[0122] Step 501: The terminal sends a first message through the first bearer and / or receives a second message through the first bearer.

[0123] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device.

[0124] The first bearer satisfies at least one of the following:

[0125] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0126] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0127] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0128] It should be noted that the aforementioned first bearer can also be understood as a newly established bearer, or a signaling bearer different from the existing signaling bearers. The existing signaling bearers may include SRB0, SRB1, SRB2, SRB3, SRB4, and SRB5; in this case, the first bearer may be referred to as SRB6, for example.

[0129] As can be seen, in the embodiments of this application, a new or independent bearer can be defined or configured, or a bearer dedicated to transmitting messages including data from IoT devices can be defined or configured.

[0130] Optionally, the first message and / or the second message are Radio Resource Control (RRC) messages. That is, an RRC message can carry data from at least one IoT device, thereby transmitting the RRC message via the aforementioned first bearer.

[0131] It's important to note that if a terminal uses RRC messages to forward data from IoT devices and carries new messages using SRB1 according to existing rules, these new RRC messages carrying IoT device data will have the same priority and transmission attributes as traditional SRB1 messages. Furthermore, within the same SRB1, these new RRC messages need to be sorted and delivered in order, which contradicts the attribute principles between IoT device data and traditional RRC messages. For example, messages carried on SRB1 may have high priority, but typical IoT device data doesn't require such high priority. Therefore, using SRB1 to carry IoT device data not only fails to meet priority requirements but also preempts resources from other high-priority data. Clearly, transmitting RRC messages carrying IoT device data via SRB1 undermines system fairness and efficiency, negatively impacting overall transmission efficiency.

[0132] In this embodiment, a new or independent bearer can be defined or configured, or a bearer dedicated to transmitting messages including data from IoT devices can be used. This way, the data from IoT devices and traditional RRC messages are not sequentially related, thus avoiding errors such as incorrect delivery and sorting of IoT device data and traditional SRB1 signaling, thereby preventing delays and impacts on the transmission quality and performance of critical SRB1 signaling. In other words, by using a new, independent, or dedicated bearer to transmit IoT device data, the embodiments of this application can avoid the aforementioned problems arising from transmitting IoT device data via SRB1.

[0133] Optionally, the first message and / or the second message are RRC messages specifically designed to carry data from IoT devices. That is, new message types can be designed to differentiate them from existing Uu interface RRC messages. For example, in the uplink direction, uplink IoT data transfer (UL AIoT Data Transfer) messages can carry (or include) data from IoT devices; in the downlink direction, downlink IoT data transfer (DL AIoT Data Transfer) messages can carry (or include) data from IoT devices.

[0134] As can be seen from step 501 above, in the embodiments of this application, a new or independent bearer can be configured for the message carrying the data of the Internet of Things (IoT) device. That is, a first bearer dedicated to transmitting the data of the IoT device can be established. In this way, when there is data of the IoT device that needs to be forwarded, the terminal can transmit the message carrying the data of the IoT device through the new or independent first bearer, providing a method for the terminal to act as an intermediate node to forward the data of the IoT device.

[0135] The first message may also include the identification information of the IoT device to which the first data belongs, so that the data of different IoT devices can be distinguished by the identification information in the first message; the second message may also include the identification information of the IoT device receiving the second data, so that the identification information in the second message can be used to distinguish which data needs to be sent to which IoT devices.

[0136] Therefore, the embodiments of this application not only provide a method for forwarding data from IoT devices when the terminal acts as an intermediate node, but also enable data differentiation by carrying the identification information of the corresponding IoT devices, thereby further improving the accuracy of IoT data forwarding.

[0137] Furthermore, the first bearer is dedicated to transmitting data from IoT devices. That is, the first bearer is different from the existing signaling bearers, meaning that the first bearer is independent of the existing signaling bearers. In this way, when there is data from IoT devices that needs to be forwarded, the terminal can transmit messages containing data from IoT devices through the new, independent, or dedicated first bearer. This avoids interference between messages containing data from IoT devices and traditional messages on the existing SRB when transmitting messages containing data from IoT devices through the existing SRB.

[0138] Furthermore, to facilitate understanding of the data transmission method of this application embodiment, the architecture to which the data transmission method of this embodiment can be applied is now described as follows:

[0139] Figure 6 shows a schematic diagram of the architecture of a gNB Reader. The gNB Reader and the AIoT Device transmit data through the AIoT interface, while the gNB and the AIoT Core Network (CN) transmit data between the AIoT Device and the core network through the NG interface.

[0140] Figure 7 shows a schematic diagram of a UE Reader architecture. It primarily transmits data between the AIoT Device and the AIoT CN, with the UE Reader and gNB serving as necessary relay nodes. Because the UE Reader can be a device located close to the Device and possesses a degree of mobility, it effectively extends the coverage of AIoT data transmission. This avoids the problem of insufficient coverage caused by the fixed location and limited number of gNBs when acting as Readers, which could prevent some AIoT devices from effectively communicating with the network.

[0141] In the two architectures shown in Figures 6 and 7, to ensure low cost and low implementation complexity for AIoT devices, the AIoT devices do not need to distinguish between the gNB Reader and the UE Reader communicating with them; that is, they maintain the same protocol stack and operations. Similarly, if the interface between the gNB and the CN can also reuse the same interface operations in both architectures, the standardization workload and complexity can be further reduced.

[0142] In the architecture shown in Figure 7, the UE Reader can carry data packets of the AIoT Device in its own RRC messages to complete AIoT data interaction with the gNB. In this case, the UE can use the data transmission method of this embodiment to forward AIoT data; that is, the UE Reader can transmit RRC messages carrying data packets of the AIoT Device through SRB6. This extends network coverage for the AIoT Device, ensuring communication success rate and low latency performance.

[0143] It should be noted that in Figures 6 and 7, MAC represents Media Access Control, PHY represents the Physical Layer, NGAP represents the control protocol of the interface between the CN and gNB, SCTP represents Flow Control Transport Protocol, IP represents Internet Protocol, L2 represents the Data Link Layer, L1 represents the Physical Layer, RRC represents Radio Resource Control, PDCP represents Packet Data Convergence Protocol, RLC represents Radio Link Layer Control Protocol, NG represents the interface between the gNB and the CN, and Uu represents the interface between the UE and the gNB.

[0144] Furthermore, if the terminal carries IoT device data through the first and / or second messages, it can include the IoT device's identification information within these messages to distinguish data from different IoT devices, thus ensuring accurate uplink and downlink forwarding. For example, in the architecture shown in Figure 7, the UE Reader needs to place AIoT Device data within its own RRC message for uplink and downlink transmission, completing the transmission of AIoT Device data between the UE and gNB. Therefore, a key issue needs to be addressed: how to distinguish data from different AIoT Devices within the RRC message of the Uu interface.

[0145] For uplink (UL), the UE Reader transmits data from different AIoT devices to the gNB in ​​the same or different RRC messages. The gNB needs to know which AIoT devices these data belong to, so that the AIoT device data can be identified in the channel (i.e., transmission channel) between the gNB and the CN, so that it can be transmitted in the channel of the corresponding AIoT device.

[0146] For downlink (DL), the gNB transmits data from different AIoT devices in the same or different RRC messages to the UE Reader. The UE Reader needs to know which AIoT devices these data belong to in order to transmit the data to the corresponding AIoT devices one-to-one on the AIoT interface.

[0147] As can be seen from the above, distinguishing AIoT Device data in RRC messages plays a very important role.

[0148] In the embodiments of this application, the identification information of the corresponding IoT device can be carried in the first message and / or the second message, thereby enabling accurate transmission of data to the IoT device in both the uplink and downlink directions.

[0149] Optionally, the terminal sends a first message through a first bearer and / or receives a second message through the first bearer, including:

[0150] The terminal sends the first message through the first bearer and / or receives the second message through the first bearer according to the transmission parameter information of the first bearer.

[0151] Therefore, it can be seen that the terminal can transmit the first message through the first bearer based on the transmission parameter information of the first bearer.

[0152] Optionally, the transmission parameter information includes at least one of the following H-1 to H-3:

[0153] H-1: The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold; the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices (e.g., at least one of SRB1, SRB2, SRB3, SRB4, SRB5); or the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers. That is, it can be understood that the priority of the first bearer can be relatively low; optionally, the smaller the priority value, the higher the priority level.

[0154] H-2: The guaranteed bit rate of the first bearer, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinite (i.e., the guaranteed bit rate is not infinite), or is less than or equal to the second threshold.

[0155] H-3: Configuration information for the first bearer to support unacknowledged UM mode transmission.

[0156] Optionally, the transmission parameter information is agreed upon through a protocol, configured by the access network device, or reconfigured by the access network device.

[0157] It is understood that the transmission parameter information of the first bearer may include at least one parameter, of which at least some parameters can be agreed upon by the protocol, and at least some parameters can be configured or reconfigured by the access network equipment. The protocol-agreed transmission parameters can also be understood as the default transmission parameters.

[0158] In some embodiments, the default transmission parameters may include at least one of the items shown in Table 2.

[0159] Table 2 Example of default transmission parameters for the first bearer

[0160] In some embodiments, when an access network device establishes a first bearer, it may send at least some parameters from the transmission parameter information of the first bearer to the terminal.

[0161] In some embodiments, when an access network device receives an updated transmission request from a core network device, it reconfigures at least some parameters in the transmission parameter information of the first bearer; wherein, the updated transmission request may refer to an updated transmission request of the original service or a transmission request of a new service. For example, if a new AIoT service is added, the Physical Resource Block (PBR) parameters can be improved to better complete the transmission.

[0162] Optionally, the transmission parameter information includes N parameters, where N is greater than or equal to 1;

[0163] When the first configuration information includes a first parameter, the terminal uses the value of the first parameter included in the first configuration information, wherein the first configuration information is used to configure the first bearer, and the first parameter includes at least some of the parameters among the N parameters;

[0164] Alternatively, if the first parameter is not included in the first configuration information, the terminal uses the value of the first parameter as agreed in the protocol.

[0165] Therefore, for any parameter of the first bearer, if the parameter exists in the first configuration information, the terminal uses the value of the parameter in the first configuration information; otherwise, the terminal uses the value of the parameter agreed upon by the protocol (i.e., the default value of the parameter).

[0166] Optionally, the first configuration information is used to establish the first bearer; for example, the first configuration information is an RRC reconfiguration message (RRC Reconfiguration Msg).

[0167] In some embodiments, the terminal sends the first message through the first bearer and / or receives the second message through the first bearer according to the transmission parameter information of the first bearer, including one of the following A-1 to A-3:

[0168] Item A-1: ​​When the terminal receives the first configuration information and the first configuration information includes the values ​​of the N parameters, the terminal sends the first message through the first bearer and / or receives the second message through the first bearer according to the values ​​of the N parameters included in the first configuration information.

[0169] That is, if the first configuration information received by the terminal includes the values ​​of the above N parameters, that is, the access network device has configured all the parameter values ​​of the first bearer for the terminal, then regardless of whether the protocol specifies the transmission parameters of the first bearer (i.e., whether the first bearer has default transmission parameters), the terminal will use the parameter values ​​in the first configuration information.

[0170] Item A-2: When the terminal receives the first configuration information, and the first configuration information includes the value of the first parameter, the terminal sends the first message through the first bearer and / or receives the second message through the first bearer according to the value of the first parameter and the value of the second parameter agreed upon in the protocol, wherein at least some of the N parameters are included, and the second parameter includes parameters other than the first parameter among the N parameters;

[0171] If the first configuration information received by the terminal includes Y transmission parameters (Y less than N), it means that the access network device has configured some parameters of the first bearer for the terminal, and the protocol specifies Z transmission parameters of the first bearer (i.e., the first bearer has Z default transmission parameters). Among them, the Y transmission parameters and the Z transmission parameters may or may not have an intersection. If they have an intersection, the terminal uses the Y transmission parameters and the parameters of the Z transmission parameters other than the intersection. If they do not have an intersection, the terminal uses the Y transmission parameters and the Z transmission parameters.

[0172] Item A-3: If the transmission parameters of the first bearer are not included in the first configuration information of the terminal, the terminal sends the first message through the first bearer and / or receives the second message through the first bearer according to the transmission parameter information of the first bearer agreed in the protocol.

[0173] In summary, for the first bearer, some default values ​​for transmission parameters can be pre-configured in the protocol, and new transmission parameter values ​​can also be configured by the access network device. When the access network device configures new transmission parameter values, the newly configured values ​​are used as the final parameter values. If the access network device does not configure new transmission parameter values, the default values ​​are used. Therefore, in this embodiment, the transmission parameters of the first bearer can be configured as needed.

[0174] It should be noted that in some embodiments, if there are messages carrying data from IoT devices, they are transmitted on the newly configured first bearer. The advantage is that the transmission parameters of the first bearer can be configured as needed. For example, if the first bearer transmits IoT data, this data generally does not have a high priority and does not need to have the highest priority like SRB1's priority 1. Instead, a reasonable priority parameter value is set according to the transmission content. This ensures the fairness of data within a terminal, so that important UP and CP data can be transmitted first, while IoT data does not compete for their resources.

[0175] Optionally, the method further includes:

[0176] The terminal sends a release request, wherein the release request is used to request the release of the first bearer.

[0177] Therefore, it can be seen that the terminal can actively request the release of the first bearer.

[0178] In some embodiments, after the data transmission task of the IoT device is completed, the terminal can proactively report the completion of the data transmission task to the access network device, after which the access network device can release the first bearer. In this case, the indication that the data transmission task of the IoT device has ended can be understood as a release request for the first bearer.

[0179] Optionally, the identification information includes at least one of the following B-1 to B-3:

[0180] Item B-1: First identifier, which includes: a global identifier (e.g., Upper Layer ID) used by IoT devices and core network devices to identify IoT devices;

[0181] It should be noted that the Upper Layer ID is a permanent identifier (such as EPC ID) or a temporary identifier (such as Temp device ID) used by the core network device (CN) and the IoT device to identify the IoT device; in short, it can uniquely identify an IoT device between the CN and the IoT device.

[0182] In some embodiments, the Uu interface (i.e., between the terminal and the access network device) can borrow the Upper Layer ID as the identification information of the IoT device to which the first data carried in the first message (e.g., an RRC message) transmitted via the Uu interface belongs. Thus, each IoT device data corresponds to at least two fields: a Device ID and a data field. The Device ID field has a fixed length, such as 98 bits, determined based on the length of the Upper Layer ID, while the data field (i.e., the field carrying the IoT device's data) has a variable length and can hold different data sizes.

[0183] The Upper Layer ID can be reported by the IoT device to the terminal through the Random Access Channel (RACH) of the AIoT interface. For example, the Upper Layer ID is included in Msg3 of the 3-step RACH or Msg1 of the 2-step RACH. The Upper Layer ID can be extracted as the identification information of the IoT device.

[0184] Item B-2: Second identifier, which includes: a temporary identifier (e.g., Access Stratum (AS) ID) used by the terminal and the IoT device to identify the IoT device at the IoT interface;

[0185] It should be noted that AS ID is an ID used to identify each IoT device on the IoT interface (i.e., AIoT interface) between the terminal and the IoT device. (It can also be understood as an identifier for the IoT interface between the terminal and the IoT device.) For example, the AS ID can serve as a scheduling identifier for IoT devices on the IoT interface. If the AS ID is carried in a Reader to Device (R2D) message, it means that the R2D message contains data from the IoT device corresponding to that AS ID. In addition, if the R2D message carries scheduling resources for Device to Reader (D2R), it indicates that the resources allocated by the terminal to the IoT device corresponding to that AS ID are used for its D2R transmission.

[0186] The AS ID can be generated by the IoT device during the RACH process and confirmed and guaranteed to be unique by the terminal, or it can be directly assigned to the IoT device by the terminal. In short, the AS ID is used on the IoT interface to uniquely identify an IoT device under a terminal, and the length of the AS ID is generally 16 bits.

[0187] In some embodiments, the Uu interface can borrow the AS ID as identification information of the IoT device to which the first data carried in the first message (e.g., RRC message) transmitted by the Uu interface belongs. In this way, each IoT device data corresponds to at least two fields: one field is the Device AS ID, and the other field is the data field. The Device ID field has a fixed length, such as 16 bits, which can be determined based on the length of the AS ID, while the data field has a variable length and can carry different data sizes.

[0188] Item B-3: Third identifier, which includes: a local identifier (e.g., Local Device ID) used by the terminal and the access network device to identify the IoT device.

[0189] The Local Device ID is a dedicated ID used to identify each IoT device via the Uu interface between the terminal and the access network device. For example, this Local Device ID can be assigned by the terminal or requested from the access network device and assigned by the access network device. In short, this Local Device ID is used on the Uu interface to uniquely identify an IoT device under a single terminal. The length of the Local Device ID is determined by the maximum number of IoT devices under a single terminal, and can be, for example, 8 or 12 bits.

[0190] In some embodiments, the Uu interface can use the Local Device ID as the identification information of the IoT device to which the first data carried in the first message (e.g., RRC message) transmitted by the Uu interface belongs. In this way, each IoT device data corresponds to at least two fields: one field is the Local Device ID and the other field is the data field. The Local Device ID field can be determined to have a fixed length, such as 8 or 12 bits, depending on the device size. The data field is of variable length and can carry different data sizes.

[0191] The following section describes different scenarios where different identifiers are used to distinguish IoT devices between terminals and access network equipment:

[0192] Scenario 1: The second indicator distinguishes the upward direction:

[0193] Optionally, if the identification information included in the first message includes the second identifier, the second identifier included in the first message is the second identifier obtained by the terminal when receiving the first data through the IoT interface.

[0194] That is, when the terminal and the access network device distinguish IoT devices through the second identifier, when the terminal receives the first data sent by the IoT device through the IoT interface, the terminal can obtain the second identifier of the IoT interface that received the first data; thus, the terminal can carry the first data to be transmitted and the second identifier in the first message sent to the access network device.

[0195] Upon receiving the first message from the terminal, the access network device can obtain the corresponding identifier of the first channel based on the correspondence between the second identifier and the identifier of the first channel, and then send the first data and the identifier of the first channel to the core network device; thus, the transmission of the first data from the IoT device to the core network device is realized. The first channel is the transmission channel between the access network device and the core network device; for example, the first channel can be an NG pipe.

[0196] Scenario 2: The first indicator distinguishes the upward direction.

[0197] Optionally, if the identification information included in the first message includes the first identifier, the first identifier included in the first message is determined based on the first correspondence and the second identifier obtained by the terminal when receiving the first data at the IoT interface. The first correspondence includes the correspondence between the second identifier and the first identifier.

[0198] That is, when the terminal and the access network device distinguish IoT devices through the first identifier, when the terminal receives the first data sent by the IoT device through the IoT interface, the terminal can obtain the second identifier of the IoT interface that received the first data; thus, based on the above-mentioned first correspondence (i.e., the correspondence between the second identifier and the first identifier), the terminal can obtain the first identifier corresponding to the second identifier, and then carry the first data to be transmitted and the first identifier in the first message sent to the access network device.

[0199] Upon receiving the first message from the terminal, the access network device can obtain the corresponding identifier of the first channel based on the correspondence between the first identifier and the identifier of the first channel, and then send the first data and the identifier of the first channel to the core network device; thus, the transmission of the first data from the IoT device to the core network device is realized. The first channel is the transmission channel between the access network device and the core network device; for example, the first channel can be an NG pipe.

[0200] Scenario 3: The third indicator distinguishes the upward direction.

[0201] Optionally, if the identification information included in the first message includes the third identifier, the third identifier included in the first message is determined based on the second correspondence and the second identifier obtained by the terminal when receiving the first data at the IoT interface. The second correspondence includes the correspondence between the second identifier and the third identifier.

[0202] That is, when the terminal and the access network device distinguish IoT devices through a third identifier, when the terminal receives the first data sent by the IoT device through the IoT interface, the terminal can obtain the second identifier of the IoT interface that received the first data; thus, based on the above-mentioned second correspondence (i.e., the correspondence between the second identifier and the third identifier), the terminal can obtain the third identifier corresponding to the second identifier, and then carry the first data to be transmitted and the third identifier in the first message sent to the access network device.

[0203] Upon receiving the first message from the terminal, the access network device can obtain the corresponding identifier of the first channel based on the correspondence between the third identifier and the identifier of the first channel, and then send the first data and the identifier of the first channel to the core network device; thus, the transmission of the first data from the IoT device to the core network device is realized. The first channel is the transmission channel between the access network device and the core network device; for example, the first channel can be an NG pipe.

[0204] Scenario 4: Distinguished by the second indicator in the downlink direction.

[0205] Optionally, if the identification information included in the second message includes the second identifier, the second identifier included in the second message is used to carry the second data when the terminal sends the second data to the corresponding IoT device.

[0206] In the case where IoT devices are distinguished by a second identifier between the terminal and the access network device, if the core network device has second data that needs to be transmitted to the IoT device, it can send the second data and the corresponding identifier of the first channel to the access network device. In this way, the access network device can obtain the corresponding second identifier and terminal identifier according to the correspondence between the second identifier, the terminal identifier and the identifier of the first channel, and then send a second message including the second data and the second identifier to the terminal through the first bearer; wherein, the first channel is the transmission channel between the access network device and the core network device.

[0207] In this process, after the terminal receives the second message sent by the access network device through the first bearer, it can obtain the second identifier from the second message. Thus, the terminal can determine which IoT device the second data carried in the second message needs to be sent to, and can then transmit the second data to the corresponding IoT device through the IoT interface corresponding to the second identifier. This completes the transmission of the second data from the core network device to the IoT device.

[0208] Scenario 5: Distinguished by the first indicator in the downlink direction.

[0209] Optionally, the method further includes:

[0210] If the identification information included in the second message includes the first identifier, the terminal determines the second identifier based on the first correspondence and the first identifier included in the second message. The second identifier is carried by the terminal when sending the second data to the corresponding IoT device, and the first correspondence includes the correspondence between the second identifier and the first identifier.

[0211] In the case where IoT devices are distinguished by a first identifier between the terminal and the access network device, if the core network device has second data that needs to be transmitted to the IoT device, it can send the second data and the corresponding identifier of the first channel to the access network device. In this way, the access network device can obtain the corresponding first identifier and terminal identifier according to the correspondence between the first identifier, the terminal identifier and the identifier of the first channel, and then send a second message including the second data and the first identifier to the terminal through the first bearer; wherein, the first channel is the transmission channel between the access network device and the core network device.

[0212] In this process, after the terminal receives the second message sent by the access network device through the first bearer, it can obtain the first identifier from the second message. Based on the aforementioned first correspondence, it can then obtain the second identifier of the IoT interface corresponding to the first identifier. Thus, the terminal can determine which IoT device the second data carried in the second message needs to be sent to, and can then transmit the second data to the corresponding IoT device through the IoT interface corresponding to the second identifier. This completes the transmission of the second data from the core network device to the IoT device.

[0213] Scenario 6: Distinguished by the third indicator in the downward direction.

[0214] Optionally, the method further includes:

[0215] If the identification information included in the second message includes the third identifier, the terminal determines the second identifier based on the second correspondence and the third identifier included in the first message. The second identifier is carried by the terminal when sending the second data to the corresponding IoT device, and the second correspondence includes the correspondence between the second identifier and the third identifier.

[0216] In the case where IoT devices are distinguished by a third identifier between the terminal and the access network device, if the core network device has second data that needs to be transmitted to the IoT device, it can send the second data and the corresponding identifier of the first channel to the access network device. In this way, the access network device can obtain the corresponding third identifier and terminal identifier according to the correspondence between the third identifier, the terminal identifier and the identifier of the first channel, and then send a second message including the second data and the third identifier to the terminal through the first bearer; wherein, the first channel is the transmission channel between the access network device and the core network device.

[0217] In this process, after the terminal receives the second message sent by the access network device through the first bearer, it can obtain the third identifier from the second message. Based on the aforementioned second correspondence, it can then obtain the second identifier of the IoT interface corresponding to the third identifier. Thus, the terminal can determine which IoT device the second data carried in the second message needs to be sent to, and can transmit the second data to the corresponding IoT device through the IoT interface corresponding to the second identifier. This completes the transmission of the second data from the core network device to the IoT device.

[0218] Optionally, the method further includes:

[0219] When the terminal receives the first data packet from the IoT device, the terminal establishes or stores the first correspondence between the second identifier and the first identifier obtained when the terminal receives the first data packet.

[0220] Therefore, it can be seen that the first correspondence can be established during the transmission of the first data packet of an IoT device, so that subsequent data packets can be transmitted based on the first correspondence.

[0221] Optionally, the method further includes:

[0222] When the terminal receives the first data packet from the IoT device, the terminal assigns the third identifier to the IoT device to which the first data packet belongs, or the terminal requests the third identifier of the IoT device to which the first data packet belongs from the access network device.

[0223] Optionally, the method further includes:

[0224] The terminal establishes or stores the second correspondence between the third identifier and the second identifier obtained when the terminal receives the first data packet.

[0225] Therefore, it can be seen that the second correspondence can be established during the transmission of the first data packet of an IoT device, so that subsequent data packets can be transmitted based on the second correspondence.

[0226] To facilitate understanding of situations one through six above, the following examples are provided:

[0227] As a first example: In the UE's RRC message, each data item carries the Upper Layer ID of the corresponding Device; specifically, as shown in Figure 8, the first Device UL data item is the reported Upper Layer ID (e.g., EPC ID). That is, the UE Reader can record the correspondence between the Upper Layer ID and the AS ID of the AIoT interface, and send the Upper Layer ID and Device UL data in the RRC message to the gNB.

[0228] After receiving the RRC message, the gNB establishes an NG channel for the Device, assigns a gNB NGAP Device ID as the identifier for the NG channel, records the correspondence between the UE identifier, Upper Layer ID, and gNB NGAP Device ID, and sends the Device UL data and gNB NGAP Device ID to the CN.

[0229] After receiving the Device UL data and gNB NGAP Device ID, the CN assigns an AMF NGAP Device ID to the Device as the NG pipe identifier, records the mapping between the AMF NGAP Device ID and the Upper Layer ID, and replies to the gNB with a DL response. This DL response carries both the gNB NGAP Device ID and the AMF NGAP Device ID. It should be noted that the NG pipe is dual-identified; that is, the NG pipe is identified by both the gNB NGAP Device ID and the AMF NGAP Device ID. The gNB uses the gNB NGAP Device ID, and the CN uses the AMF NGAP Device ID. The CN can also record both the gNB NGAP Device ID and the AMF NGAP Device ID of the NG pipe.

[0230] The above process implements the transmission of the first Device UL data from the Device to the CN, and during this process, the UE, gNB, and CN respectively record the required correspondences described above. It should be noted that the first Device UL data report needs to include the Device's Upper Layer ID, such as the EPC ID. This way, after receiving the first Device data, the CN can authenticate it based on the EPC ID. Once authentication is successful, subsequent Device UL data reports will not need to include the EPC ID.

[0231] After receiving the DL response, the gNB can obtain the Upper Layer ID and UE identifier corresponding to the gNB NGAP Device ID carried in the DL response based on the recorded correspondence between the UE identifier, Upper Layer ID and gNB NGAP Device ID, and then send a DL response carrying the Upper Layer ID to the UE Reader.

[0232] After receiving the DL response, the UE Reader can obtain the AS ID corresponding to the Upper Layer ID based on the recorded correspondence between the Upper Layer ID and the AS ID, and then send a DL response carrying the AS ID to the Device.

[0233] It is understandable that after the CN receives the aforementioned UL data, if it needs to send DL data to the Device, the aforementioned DL response can carry the required DL data, and / or the DL data can be transmitted from the CN to the Device through the same transmission process as the aforementioned DL response.

[0234] As can be seen from the above, after establishing the above correspondence, each node forwards data according to the correspondence, and the data that uniquely identifies a Device can ensure that the data forwarding of UL and DL is correct.

[0235] It should be noted that in the first example, the Upper Layer ID is reused as the data identifier for the Uu interface, which may pose certain security risks, or the Upper Layer ID may not be visible to other nodes besides the Device and CN. Therefore, the solution in the first example may not be applicable to all scenarios.

[0236] As a second example, in the UE's RRC message, each data item carries the Local Device ID of the corresponding Device. Specifically, as shown in Figure 9, the first Device UL data item is the reported Local Device ID. That is, the UE Reader can record the correspondence between the Local Device ID and the AS ID identifier of the AIoT interface, and send the Local Device ID and Device UL data in the RRC message to the gNB.

[0237] After receiving the RRC message, the gNB establishes an NG channel for the Device, assigns a gNB NGAP Device ID as the identifier for the NG channel, records the correspondence between the UE identifier, Local Device ID, and gNB NGAP Device ID, and sends the Device UL data and gNB NGAP Device ID to the CN.

[0238] After receiving the Device UL data and gNB NGAP Device ID, CN assigns an AMF NGAP Device ID to the Device as an NG pipeline identifier, records the correspondence between the AMF NGAP Device ID and the Upper Layer ID, and replies to gNB with a DL response, which carries the gNB NGAP Device ID and the AMF NGAP Device ID.

[0239] The above process implements the transmission of the first Device UL data from the Device to the CN, and during this process, the UE, gNB, and CN respectively record the required correspondences described above. It should be noted that the first Device UL data report needs to include the Device's Upper Layer ID, such as the EPC ID. This way, after receiving the first Device data, the CN can authenticate it based on the EPC ID. Once authentication is successful, subsequent Device UL data reports will not need to include the EPC ID.

[0240] After receiving the DL response, the gNB can obtain the Local Device ID and UE identifier corresponding to the gNB NGAP Device ID carried in the DL response based on the recorded correspondence between the UE identifier, Local Device ID and gNB NGAP Device ID, and then send a DL response carrying the Upper Layer ID to the UE Reader.

[0241] After receiving the DL response, the UE Reader can obtain the AS ID corresponding to the Local Device ID based on the recorded correspondence between the Local Device ID and the AS ID, and then send a DL response carrying the AS ID to the Device.

[0242] It is understandable that after the CN receives the aforementioned UL data, if it needs to send DL data to the Device, the aforementioned DL response can carry the required DL data, and / or the DL data can be transmitted from the CN to the Device through the same transmission process as the aforementioned DL response.

[0243] As can be seen from the above, after establishing the above correspondence, each node forwards data according to the correspondence, and the data that uniquely identifies a Device can ensure that the data forwarding of UL and DL is correct.

[0244] It should be noted that the second example uses a dedicated Local Device ID for data identification of the Uu interface, and a dedicated ID yields the best results. The only potential issue is that if the base station allocation principle must be followed, there will be some signaling interaction latency. If the UE Reader can be assigned a Local Device ID, the performance will be better.

[0245] As a third example: In the UE's RRC message, each data item carries the corresponding Device's AIoT AS ID; specifically, as shown in Figure 10, the first Device UL data item is the reported AS ID, that is: the UE Reader sends the AS ID and Device UL data in the RRC message to the gNB;

[0246] After receiving the RRC message, the gNB establishes an NG channel for the Device, assigns a gNB NGAP Device ID as the identifier for the NG channel, records the correspondence between the UE identifier, AS ID, and gNB NGAP Device ID, and sends the Device UL data and gNB NGAP Device ID to the CN.

[0247] After receiving the Device UL data and gNB NGAP Device ID, CN assigns an AMF NGAP Device ID to the Device as an NG pipeline identifier, records the correspondence between the AMF NGAP Device ID and the Upper Layer ID, and replies to gNB with a DL response, which carries the gNB NGAP Device ID and the AMF NGAP Device ID.

[0248] The above process implements the transmission of the first Device UL data from the Device to the CN, and during this process, the gNB and CN respectively record the required correspondences described above. It should be noted that the first Device UL data report needs to include the Device's Upper Layer ID, such as the EPC ID. This way, after receiving the first Device data, the CN can authenticate it based on the EPC ID. Once authentication is successful, subsequent Device UL data reports will not need to include the EPC ID.

[0249] After receiving the DL response, the gNB can obtain the AS ID and UE identifier corresponding to the gNB NGAP Device ID carried in the DL response based on the recorded correspondence between the UE identifier, AS ID and gNB NGAP Device ID, and then send a DL response carrying the AS ID to the UE Reader.

[0250] After receiving the DL response, the UE Reader can send a DL response carrying the AS ID to the Device.

[0251] It is understandable that after the CN receives the aforementioned UL data, if it needs to send DL data to the Device, the aforementioned DL response can carry the required DL data, and / or the DL data can be transmitted from the CN to the Device through the same transmission process as the aforementioned DL response.

[0252] It should be noted that the third example reuses the AIoT AS ID as the data identifier for the Uu interface, which raises the issue of cross-domain ID usage. Specifically, the AS ID allocated and maintained by the AIoT interface is extended to the Uu interface for continued use. However, when the AIoT interface uses Cyclic Frequency Reuse Algorithm (CFRA) and does not need to maintain an AS ID, the Uu interface has no identifier that can be reused. Therefore, the solution in the second example may not be applicable to all scenarios.

[0253] Furthermore, a common point exists in the first, second, and third examples mentioned above: when the gNB records the correspondence, since both the Local ID and AS ID are uniquely valid under a single UE Reader, it is necessary to distinguish and record the UE dimension. This UE dimension can be identified by the UE's Cell Network Temporary Identity (C-RNTI). Thus, when the downlink gNB performs addressing, it finds the corresponding C-RNTI based on the gNB NGAP Device ID, thereby locating the corresponding UE, and then uses the Local ID / AS ID to determine which device it is. Although the Upper Layer ID has a valid range exceeding that of a single UE Reader, it still needs to be recorded because the gNB must first transmit it to the UE to locate the device. For example, the C-RNTI can be used to find and distinguish different UE Readers.

[0254] Optionally, the terminal sends a first message through a first bearer and / or receives a second message through the first bearer, including:

[0255] If at least one of the integrity protection and encryption functions of the first bearer is not enabled (or disabled), the terminal sends a first message through the first bearer and / or receives a second message through the first bearer.

[0256] It should be noted that, regarding air interface security, according to traditional rules, signaling and data of SRB2 and Data Radio Bearer (DRB) can only be transmitted after air interface security is activated. Furthermore, following these rules, both SRB2 and SRB1 have integrity protection and encryption enabled by default; DRB has encryption by default, while integrity protection is optional. Specifically, for RRC signaling in SRB1, each signaling item is specified as allowed to be transmitted before security activation. For example, RRC setup-related signaling, being basic RRC connection establishment signaling, cannot be transmitted after security activation due to timing constraints. Some signaling items with low security requirements but time-sensitive characteristics can be specified to be transmitted as soon as the connection is established, without waiting for security activation.

[0257] Among them, messages carrying AIoT data (such as RRC messages) no longer have security functions in the AIoT interface in the architecture shown in Figure 7 (i.e., the UE Reader scenario) because AIoT data supports end-to-end secure operation. Therefore, the requirement for air interface security for messages carrying AIoT data is not great. Thus, messages carrying AIoT data (such as the UL AIoT Data Transfer and DL AIoT Data Transfer mentioned above) can be transmitted before security is activated. That is, the first message can be sent through the first bearer and / or the second message can be received through the first bearer even if at least one of the integrity protection and encryption functions of the first bearer is not enabled.

[0258] Optionally, the method further includes:

[0259] The terminal receives second configuration information and, based on the second configuration information, disables or enables at least one of the integrity protection and encryption functions of the first bearer.

[0260] Therefore, after the first bearer is established, the terminal can enable or disable the integrity protection and encryption functions of the first bearer according to the instructions of the received second configuration information. For example, if the integrity protection and encryption functions of the first bearer are enabled by default, the second configuration information can instruct at least one of the integrity protection and encryption functions to be disabled. In this case, the first bearer has low security requirements. Alternatively, if the integrity protection and encryption functions of the first bearer are disabled by default, the second configuration information can instruct at least one of the integrity protection and encryption functions to be enabled. In this case, the first bearer has high security requirements. Thus, if the first bearer has low security requirements, at least one of the integrity protection and encryption functions can be disabled, thereby reducing processing latency.

[0261] Optionally, the method further includes:

[0262] Before the first bearer is established, the terminal sends a third message through the second bearer and / or receives a fourth message through the second bearer;

[0263] The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device.

[0264] The second bearer is not dedicated to transmitting data from IoT devices.

[0265] Optionally, the second bearer includes SRB1.

[0266] It should be noted that when the first bearer requires configuration via an RRC Reconfiguration message, since the RRC Reconfiguration message is transmitted only after security activation, in order to transmit data from early IoT devices, a small number of messages carrying IoT device data (such as UL AIoT Data Transfer and DL AIoT Data Transfer messages) can be carried in SRB1 and transmitted in a non-security-activated manner before the first bearer is established, in order to shorten transmission latency.

[0267] Optionally, the method further includes:

[0268] If the first bearer exists and the cell handover conditions are met, the terminal performs a cell handover.

[0269] It should be noted that in traditional UE processing, when a regular UE only has SRB1 and SRB2, but no DRB or MBS Radio Bearer (MRB), it means the UE has no data transmission. In this case, the UE is not allowed to perform cell handover. Therefore, due to UE movement, the RRC connection in the source cell needs to be released, and a new RRC connection needs to be established in the new cell. However, exceptions exist for special cases such as Integrated Access and Backhaul (IAB) and Network-Controlled Repeater (NCR), because in IAB and NCR scenarios, the network node reuses the UE's process and does not have its own data.

[0270] For UE Readers, cell handover is not permitted unless otherwise specified. For example, if a UE Reader enters the RRC connected (RRC_CONNECTED) state solely as a node forwarding AIoT data, and SRB1, SRB2, and the aforementioned first bearer are configured, but there is no DRB, then cell handover is not permitted. This would be detrimental to the service continuity of AIoT data forwarding. Therefore, the rule allowing handover should include the case of SRB6. That is, if the first bearer exists, then the terminal needs to perform cell handover if the cell handover conditions are met to ensure the service continuity of AIoT data forwarding.

[0271] In some embodiments, the reconfiguration signaling (e.g., the masterCellGroup configuration field in the reconfiguration signaling) includes handover information (e.g., reconfigurationWithSync) only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or SRB6, or, for IAB and NCR, SRB2, are set up and not suspended.

[0272] Optionally, the method further includes:

[0273] After the terminal performs cell handover, it retains the entity and cache of the first bearer.

[0274] It should be noted that currently, during cell handover, the SRB is handled as follows: the SRB entity in the source cell is deleted, no data is retained, and a new SRB entity is created in the target cell. This approach is reasonable and simple for traditional SRBs that only carry signaling, since messages from the source cell are no longer valid in the target cell, making deletion appropriate. However, for the aforementioned first bearer, since it carries AIoT data between IoT devices and core network equipment and does not become invalid due to cell change, it can be retained from a service continuity perspective. Therefore, after the terminal performs cell handover, the entity and cache of the first bearer can be retained to meet the service continuity requirements of AIoT data forwarding.

[0275] Optionally, after the terminal performs a cell handover, it retains the entity and cache of the first bearer, including:

[0276] If the terminal supports data forwarding and / or L2 transmission state retention, the terminal retains the entity and cache of the first bearer after performing cell handover.

[0277] Therefore, the cell handover process of the first bearer can be configured separately. For example, if the UE supports data forwarding and / or L2 transmission status maintenance, the entity and cache of the first bearer can be maintained after cell handover so that AIoT data can be continuously transmitted before and after handover, thereby improving forwarding performance.

[0278] Referring to Figure 11, an embodiment of this application provides a data transmission method, which may include the following step 1101:

[0279] Step 1101: The access network device receives a first message through the first bearer and / or sends a second message through the first bearer.

[0280] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device.

[0281] The first bearer satisfies at least one of the following:

[0282] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0283] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0284] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0285] It should be noted that the aforementioned first bearer can also be understood as a newly established bearer, or a signaling bearer different from the existing signaling bearers. The existing signaling bearers may include SRB0, SRB1, SRB2, SRB3, SRB4, and SRB5; in this case, the first bearer may be referred to as SRB6, for example.

[0286] As can be seen, in the embodiments of this application, a new or independent bearer can be defined or configured, or a bearer dedicated to transmitting messages including data from IoT devices can be defined or configured.

[0287] Optionally, the first message and / or the second message are Radio Resource Control (RRC) messages. That is, an RRC message can carry data from at least one IoT device, thereby transmitting the RRC message via the aforementioned first bearer.

[0288] It's important to note that if a terminal uses RRC messages to forward data from IoT devices and carries new messages using SRB1 according to existing rules, these new RRC messages carrying IoT device data will have the same priority and transmission attributes as traditional SRB1 messages. Furthermore, within the same SRB1, these new RRC messages need to be sorted and delivered in order, which contradicts the attribute principles between IoT device data and traditional RRC messages. For example, messages carried on SRB1 may have high priority, but typical IoT device data doesn't require such high priority. Therefore, using SRB1 to carry IoT device data not only fails to meet priority requirements but also preempts resources from other high-priority data. Clearly, transmitting RRC messages carrying IoT device data via SRB1 undermines system fairness and efficiency, negatively impacting overall transmission efficiency.

[0289] In this embodiment, a new or independent bearer can be defined or configured, or a bearer dedicated to transmitting messages including data from IoT devices can be used. This way, the data from IoT devices and traditional RRC messages are not sequentially related, thus avoiding errors such as incorrect delivery and sorting of IoT device data and traditional SRB1 signaling, thereby preventing delays and impacts on the transmission quality and performance of critical SRB1 signaling. In other words, by using a new, independent, or dedicated bearer to transmit IoT device data, the embodiments of this application can avoid the aforementioned problems arising from transmitting IoT device data via SRB1.

[0290] Optionally, the first message and / or the second message are RRC messages specifically designed to carry data from IoT devices. That is, new message types can be designed to differentiate them from existing Uu interface RRC messages. For example, in the uplink direction, uplink IoT data transfer (UL AIoT Data Transfer) messages can carry (or include) data from IoT devices; in the downlink direction, downlink IoT data transfer (DL AIoT Data Transfer) messages can carry (or include) data from IoT devices.

[0291] As can be seen from step 1101 above, in the embodiments of this application, a new or independent bearer can be configured for the message carrying the data of the Internet of Things (IoT) device. That is, a first bearer dedicated to transmitting the data of the IoT device can be established. In this way, when there is data of the IoT device that needs to be forwarded, the terminal can transmit the message carrying the data of the IoT device through the new or independent first bearer, providing a method for the terminal to act as an intermediate node to forward the data of the IoT device.

[0292] The first message may also include the identification information of the IoT device to which the first data belongs, so that the data of different IoT devices can be distinguished by the identification information in the first message; the second message may also include the identification information of the IoT device receiving the second data, so that the identification information in the second message can be used to distinguish which data needs to be sent to which IoT devices.

[0293] Therefore, the embodiments of this application not only provide a method for forwarding data from IoT devices when the terminal acts as an intermediate node, but also enable data differentiation by carrying the identification information of the corresponding IoT devices, thereby further improving the accuracy of IoT data forwarding.

[0294] Furthermore, the first bearer is dedicated to transmitting data from IoT devices. That is, the first bearer is different from the existing signaling bearers, meaning that the first bearer is independent of the existing signaling bearers. In this way, when there is data from IoT devices that needs to be forwarded, the terminal can transmit messages containing data from IoT devices through the new, independent, or dedicated first bearer. This avoids interference between messages containing data from IoT devices and traditional messages on the existing SRB when transmitting messages containing data from IoT devices through the existing SRB.

[0295] Optionally, the method further includes:

[0296] The access network device establishes the first bearer.

[0297] In some embodiments, when an access network device receives a service request, it establishes the first bearer based on the transmission requirements carried in the service request.

[0298] In some embodiments, when an access network device establishes a first bearer, it may send at least some of the transmission parameters of the first bearer to the terminal.

[0299] Optionally, the method further includes:

[0300] The access network device configures or reconfigures the transmission parameter information of the first bearer.

[0301] In some embodiments, when the access network device receives an updated transmission request from the core network device, it reconfigures at least some parameters in the transmission parameter information of the first bearer; wherein, the updated transmission request may refer to the updated transmission request of the original service or the transmission request of the new service. For example, if a new AIoT service is added, the PBR parameter can be improved to better complete the transmission.

[0302] Optionally, the transmission parameter information includes at least one of the following H-1 to H-3:

[0303] H-1: The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold; the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices (e.g., at least one of SRB1, SRB2, SRB3, SRB4, SRB5); or the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers. That is, it can be understood that the priority of the first bearer can be relatively low; optionally, the smaller the priority value, the higher the priority level.

[0304] H-2: The guaranteed bit rate of the first bearer, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinite (i.e., the guaranteed bit rate is not infinite), or is less than or equal to the second threshold.

[0305] H-3: Configuration information for the first bearer to support unacknowledged UM mode transmission.

[0306] Optionally, the method further includes:

[0307] The access network device releases the first bearer;

[0308] or,

[0309] When the access network device receives a release request, the access network device releases the first bearer, wherein the release request is used to request the release of the first bearer.

[0310] Therefore, the release of the first bearer can be controlled by the network side, or it can be released after receiving a release request from the terminal.

[0311] In some embodiments, when the access network device receives an instruction from the core network device indicating the end of data forwarding or release of IoT devices, it releases the first bearer.

[0312] In some embodiments, after the data transmission task of the IoT device is completed, the terminal can proactively report the completion of the data transmission task to the access network device, after which the access network device can release the first bearer. In this case, the indication that the data transmission task of the IoT device has ended can be understood as a release request for the first bearer.

[0313] Optionally, the identification information includes at least one of the following B-1 to B-3:

[0314] Item B-1: First identifier, which includes: a global identifier used by IoT devices and core network devices to identify IoT devices;

[0315] Item B-2: Second identifier, which includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface;

[0316] Item B-3: Third identifier, which includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

[0317] It should be noted that the relevant explanations regarding items B-1 to B-3 can be found in the previous text and will not be repeated here.

[0318] Optionally, the method further includes:

[0319] The access network device determines the identifier of the first channel based on the third correspondence and the identification information included in the first message. The third correspondence includes the correspondence between the identification information and the identifier of the first channel. The identifier of the first channel is carried by the access network device when sending the first data to the core network device. The first channel is the transmission channel between the access network device and the core network device.

[0320] In some embodiments, when the IoT device is distinguished between the terminal and the access network device by a second identifier, when the terminal receives the first data sent by the IoT device through the IoT interface, the terminal can obtain the second identifier of the IoT interface that received the first data; thereby, the first data to be transmitted and the second identifier can be carried in the first message sent to the access network device.

[0321] Upon receiving the first message from the terminal, the access network device can obtain the corresponding identifier of the first channel based on the correspondence between the second identifier and the identifier of the first channel, and then send the first data and the identifier of the first channel to the core network device; thus, the transmission of the first data from the IoT device to the core network device is realized. The first channel is the transmission channel between the access network device and the core network device; for example, the first channel can be an NG pipe.

[0322] In some embodiments, when the IoT device is distinguished between the terminal and the access network device by a first identifier, when the terminal receives the first data sent by the IoT device through the IoT interface, the terminal can obtain the second identifier of the IoT interface that received the first data; thereby, based on the first correspondence (i.e., the correspondence between the second identifier and the first identifier), the terminal can obtain the first identifier corresponding to the second identifier, and then carry the first data to be transmitted and the first identifier in the first message sent to the access network device.

[0323] Upon receiving the first message from the terminal, the access network device can obtain the corresponding identifier of the first channel based on the correspondence between the first identifier and the identifier of the first channel, and then send the first data and the identifier of the first channel to the core network device; thus, the transmission of the first data from the IoT device to the core network device is realized. The first channel is the transmission channel between the access network device and the core network device; for example, the first channel can be an NG pipe.

[0324] In some embodiments, when the IoT device is distinguished between the terminal and the access network device by a third identifier, when the terminal receives the first data sent by the IoT device through the IoT interface, the terminal can obtain the second identifier of the IoT interface that received the first data; thereby, based on the above-mentioned second correspondence (i.e., the correspondence between the second identifier and the third identifier), the third identifier corresponding to the second identifier can be obtained, and then the first data to be transmitted and the third identifier can be carried in the first message sent to the access network device.

[0325] Upon receiving the first message from the terminal, the access network device can obtain the corresponding identifier of the first channel based on the correspondence between the third identifier and the identifier of the first channel, and then send the first data and the identifier of the first channel to the core network device; thus, the transmission of the first data from the IoT device to the core network device is realized. The first channel is the transmission channel between the access network device and the core network device; for example, the first channel can be an NG pipe.

[0326] Optionally, the identification information included in the second message is determined based on the third correspondence and the identifier of the first channel obtained by the access network device when receiving the second data. The first channel is the transmission channel between the access network device and the core network device. The third correspondence includes the correspondence between the identification information and the identifier of the first channel.

[0327] In some embodiments, where the IoT device is distinguished between the terminal and the access network device by a second identifier, if the core network device has second data that needs to be transmitted to the IoT device, it can send the second data and the corresponding identifier of the first channel to the access network device. In this way, the access network device can obtain the corresponding second identifier and terminal identifier according to the correspondence between the second identifier, the terminal identifier and the identifier of the first channel, and then send a second message including the second data and the second identifier to the terminal through the first bearer; wherein, the first channel is the transmission channel between the access network device and the core network device.

[0328] In this process, after the terminal receives the second message sent by the access network device through the first bearer, it can obtain the second identifier from the second message. Thus, the terminal can determine which IoT device the second data carried in the second message needs to be sent to, and can then transmit the second data to the corresponding IoT device through the IoT interface corresponding to the second identifier. This completes the transmission of the second data from the core network device to the IoT device.

[0329] In some embodiments, when the IoT device is distinguished between the terminal and the access network device by a first identifier, if the core network device has second data that needs to be transmitted to the IoT device, it can send the second data and the corresponding identifier of the first channel to the access network device. In this way, the access network device can obtain the corresponding first identifier and terminal identifier according to the correspondence between the first identifier, the terminal identifier and the identifier of the first channel, and then send a second message including the second data and the first identifier to the terminal through the first bearer; wherein, the first channel is the transmission channel between the access network device and the core network device.

[0330] In this process, after the terminal receives the second message sent by the access network device through the first bearer, it can obtain the first identifier from the second message. Based on the aforementioned first correspondence, it can then obtain the second identifier of the IoT interface corresponding to the first identifier. Thus, the terminal can determine which IoT device the second data carried in the second message needs to be sent to, and can then transmit the second data to the corresponding IoT device through the IoT interface corresponding to the second identifier. This completes the transmission of the second data from the core network device to the IoT device.

[0331] In some embodiments, where the IoT device is distinguished between the terminal and the access network device by a third identifier, if the core network device has second data that needs to be transmitted to the IoT device, it can send the second data and the corresponding identifier of the first channel to the access network device. In this way, the access network device can obtain the corresponding third identifier and terminal identifier according to the correspondence between the third identifier, the terminal identifier and the identifier of the first channel, and then send a second message including the second data and the third identifier to the terminal through the first bearer; wherein, the first channel is the transmission channel between the access network device and the core network device.

[0332] In this process, after the terminal receives the second message sent by the access network device through the first bearer, it can obtain the third identifier from the second message. Based on the aforementioned second correspondence, it can then obtain the second identifier of the IoT interface corresponding to the third identifier. Thus, the terminal can determine which IoT device the second data carried in the second message needs to be sent to, and can transmit the second data to the corresponding IoT device through the IoT interface corresponding to the second identifier. This completes the transmission of the second data from the core network device to the IoT device.

[0333] Optionally, the access network device receives a first message through a first bearer and / or sends a second message through the first bearer, including:

[0334] If at least one of the integrity protection and encryption functions of the first bearer is not enabled (i.e., disabled), the access network device receives the first message through the first bearer and / or sends the second message through the first bearer.

[0335] Among them, messages carrying AIoT data (such as RRC messages) do not have security functions in the AIoT interface in the architecture shown in Figure 7 (i.e., the UE Reader scenario) because AIoT data supports end-to-end secure operation. Therefore, the requirement for air interface security for messages carrying AIoT data is not great, and it is permissible to transmit messages carrying AIoT data before security is activated. That is, the first message can be received through the first bearer and / or the second message can be sent through the first bearer even if at least one of the integrity protection and encryption functions of the first bearer is not enabled.

[0336] Optionally, the method further includes:

[0337] The access network device receives third configuration information and, based on the third configuration information, disables or enables at least one of the integrity protection and encryption functions of the first bearer.

[0338] Therefore, after the first bearer is established, the access network device can enable or disable the integrity protection and encryption functions of the first bearer according to the instructions of the received third configuration information. For example, if the integrity protection and encryption functions of the first bearer are enabled by default, the third configuration information can instruct at least one of the integrity protection and encryption functions to be disabled. In this case, the first bearer has low security requirements. Alternatively, if the integrity protection and encryption functions of the first bearer are disabled by default, the third configuration information can instruct at least one of the integrity protection and encryption functions to be enabled. In this case, the first bearer has high security requirements. Thus, if the first bearer has low security requirements, at least one of the integrity protection and encryption functions can be disabled to reduce processing latency.

[0339] Optionally, the third configuration information is sent by the core network device.

[0340] Optionally, the method further includes:

[0341] Before the first bearer is established, the access network device receives a third message through the second bearer and / or sends a fourth message through the second bearer;

[0342] The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device.

[0343] The second bearer is not dedicated to transmitting data from IoT devices.

[0344] Optionally, the second signaling bearer includes SRB1.

[0345] It should be noted that when the first bearer requires configuration via an RRC Reconfiguration message, since the RRC Reconfiguration message is transmitted only after security activation, in order to transmit data from early IoT devices, a small number of messages carrying IoT device data (such as UL AIoT Data Transfer and DL AIoT Data Transfer messages) can be carried in SRB1 and transmitted in a non-security-activated manner before the first bearer is established, in order to shorten transmission latency.

[0346] Referring to Figure 12, an embodiment of this application provides a data transmission method, which may include the following steps 1201 and / or 1202:

[0347] Step 1201: The core network device receives a fifth message sent by the access network device, wherein the fifth message includes an identifier of a first channel and first data of at least one IoT device, and the first channel is a transmission channel between the core network device and the access network device.

[0348] Step 1202: The core network device sends a sixth message to the access network device, wherein the sixth message includes the identifier of the first channel and second data that needs to be sent to at least one IoT device.

[0349] It should be noted that in the transmission channel (such as NG pipe) between core network equipment and access network equipment, one transmission channel corresponds to one IoT device.

[0350] Therefore, in this embodiment of the application, the access network device and the core network device can distinguish the data of different IoT devices through the identifier of the first channel, thereby realizing the transmission of IoT device data between the access network device and the core network device.

[0351] Optionally, the identifier of the first channel included in the sixth message is determined based on the correspondence between the first identifier and the identifier of the first channel, and the second identifier of the IoT device used to receive the second data; the first identifier is a global identifier used by the IoT device and the core network device to identify the IoT device.

[0352] It should be noted that examples of the specific process of transmitting IoT device data between core network devices and access network devices can be found in the first, second, and third examples mentioned above, and will not be repeated here.

[0353] The data transmission method provided in this application can be executed by a data transmission device. This application uses a data transmission device executing the data transmission method as an example to illustrate the data transmission device provided in this application.

[0354] This application provides a data transmission device. As an example, the data transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0355] The data transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0356] Specifically, referring to Figure 13, when the data transmission device is a terminal or a component within a terminal, the data transmission device 130 includes:

[0357] Transmitting module 1301 and / or receiving module 1302;

[0358] The sending module 1301 is used to send a first message through the first bearer;

[0359] The receiving module 1302 is used to receive a second message through the first bearer;

[0360] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device;

[0361] The first bearer satisfies at least one of the following:

[0362] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0363] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0364] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0365] Optionally, the sending module 1301 sends a first message through a first bearer, including:

[0366] Based on the transmission parameter information of the first bearer, the first message is sent through the first bearer;

[0367] The receiving module 1302 receives the second message through the first bearer, including:

[0368] The first message is sent through the first bearer based on the transmission parameter information of the first bearer.

[0369] Optionally, the transmission parameter information includes at least one of the following:

[0370] The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold, the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices, and the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers.

[0371] The first bearer has a guaranteed bit rate, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinitely large, or is less than or equal to a second threshold;

[0372] The first bearer supports configuration information for unacknowledged UM mode transmission.

[0373] Optionally, the transmission parameter information is agreed upon through a protocol, configured by the access network device, or reconfigured by the access network device.

[0374] Optionally, the transmission parameter information includes N parameters, where N is greater than or equal to 1;

[0375] When the first configuration information includes a first parameter, the sending module 1301 and / or the receiving module 1302 use the value of the first parameter included in the first configuration information, wherein the first configuration information is used to configure the first bearer, and the first parameter includes at least some of the parameters among the N parameters.

[0376] or,

[0377] If the first parameter is not included in the first configuration information, the sending module 1301 and / or the receiving module 1302 shall use the value of the first parameter as agreed in the protocol.

[0378] Optionally, the first message and / or the second message are Radio Resource Control (RRC) messages dedicated to carrying data from IoT devices.

[0379] Optionally, the sending module 1301 is further configured to: send a release request, wherein the release request is used to request the release of the first bearer.

[0380] Optionally, the identification information includes at least one of the following:

[0381] The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices;

[0382] The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface;

[0383] The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

[0384] Optionally, if the identification information included in the first message includes the second identifier, the second identifier included in the first message is the second identifier obtained by the receiving module 1302 when receiving the first data through the IoT interface.

[0385] Optionally, if the identification information included in the first message includes the first identifier, the first identifier included in the first message is determined based on the first correspondence and the second identifier obtained by the receiving module 1302 when receiving the first data at the IoT interface. The first correspondence includes the correspondence between the second identifier and the first identifier.

[0386] Optionally, if the identification information included in the first message includes the third identifier, the third identifier included in the first message is determined based on the second correspondence and the second identifier obtained by the receiving module 1302 when receiving the first data at the IoT interface. The second correspondence includes the correspondence between the second identifier and the third identifier.

[0387] Optionally, if the identification information included in the second message includes the second identifier, the second identifier included in the second message is carried by the sending module 1301 when sending the second data to the corresponding IoT device.

[0388] Optionally, the device further includes:

[0389] The processing module is configured to determine the second identifier based on a first correspondence and the first identifier included in the second message when the identifier information included in the second message includes the first identifier. The second identifier is carried by the sending module 1301 when sending the second data to the corresponding IoT device. The first correspondence includes the correspondence between the second identifier and the first identifier.

[0390] Optionally, the device further includes:

[0391] The processing module is configured to determine the second identifier based on the second correspondence and the third identifier included in the first message when the identifier information included in the second message includes the third identifier, wherein the second identifier is carried by the sending module 1301 when sending the second data to the corresponding IoT device, and the second correspondence includes the correspondence between the second identifier and the third identifier.

[0392] Optionally, the device further includes:

[0393] The processing module is configured to, when the receiving module 1302 receives the first data packet from the IoT device, establish or store the first correspondence between the second identifier and the first identifier obtained by the receiving module 1302 when receiving the first data packet.

[0394] Optionally, the device further includes:

[0395] The processing module is configured to assign the third identifier to the IoT device to which the first data packet belongs when the receiving module 1302 receives the first data packet from the IoT device;

[0396] Alternatively, the sending module 1301 is further configured to request the third identifier of the IoT device to which the first data packet belongs from the access network device.

[0397] Optionally, the device further includes a processing module for establishing or storing the second correspondence between the third identifier and the second identifier obtained by the receiving module 1302 when receiving the first data packet.

[0398] Optionally, the sending module 1301 sends a first message through a first bearer, including:

[0399] The first message is sent through the first bearer if at least one of the integrity protection and encryption functions of the first bearer is not enabled;

[0400] The receiving module 1302 receives the second message through the first bearer, including:

[0401] The second message is received through the first bearer if at least one of the integrity protection and encryption functions of the first bearer is not enabled.

[0402] Optionally, the receiving module 1302 is further configured to:

[0403] Receive the second configuration information;

[0404] The device further includes a processing module for disabling or enabling at least one of the integrity protection and encryption functions of the first bearer based on the second configuration information.

[0405] Optionally, the sending module 1301 is further configured to: send a third message via a second bearer before the first bearer is established;

[0406] And / or, the receiving module 1302 is further configured to: receive a fourth message via the second bearer before the first bearer is established;

[0407] The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device.

[0408] The second bearer is not dedicated to transmitting data from IoT devices.

[0409] Optionally, the device further includes:

[0410] The processing module is used to perform cell handover when the first bearer exists and the cell handover conditions are met.

[0411] Optionally, the processing module is further configured to:

[0412] After the cell handover is performed, the entity and cache of the first bearer are retained.

[0413] Referring to Figure 14, when the data transmission device is an access network device or a component within an access network device, the data transmission device 140 includes:

[0414] Transmitting module 1401 and / or receiving module 1402;

[0415] The receiving module 1402 is used to receive a first message through a first bearer;

[0416] The sending module 1401 is used to send a second message through the first bearer;

[0417] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device;

[0418] The first bearer satisfies at least one of the following:

[0419] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0420] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0421] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0422] Optionally, the device further includes a processing module for establishing the first bearer.

[0423] Optionally, the sending module 1401 is further configured to: configure or reconfigure the transmission parameter information of the first bearer.

[0424] Optionally, the transmission parameter information includes at least one of the following:

[0425] The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold, the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices, and the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers.

[0426] The first bearer has a guaranteed bit rate, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinitely large, or is less than or equal to a second threshold;

[0427] The first bearer supports configuration information for unacknowledged UM mode transmission.

[0428] Optionally, the device further includes a processing module for performing at least one of the following:

[0429] Release the first carrier;

[0430] Alternatively, if the receiving module 1402 receives a release request, the first bearer is released, wherein the release request is used to request the release of the first bearer.

[0431] Optionally, the first message and / or the second message are Radio Resource Control (RRC) messages dedicated to carrying data from IoT devices.

[0432] Optionally, the identification information includes at least one of the following:

[0433] The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices;

[0434] The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface;

[0435] The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

[0436] Optionally, the device further includes:

[0437] The processing module is configured to determine the identifier of the first channel based on the third correspondence and the identification information included in the first message, wherein the third correspondence includes the correspondence between the identification information and the identifier of the first channel, the identifier of the first channel is carried by the sending module 1401 when sending the first data to the core network device, and the first channel is the transmission channel between the access network device and the core network device.

[0438] Optionally, the identification information included in the second message is determined based on the third correspondence and the identifier of the first channel obtained by the receiving module 1402 when receiving the second data. The first channel is the transmission channel between the access network device and the core network device. The third correspondence includes the correspondence between the identification information and the identifier of the first channel.

[0439] Optionally, the receiving module 1402 receives the first message through the first bearer, including: receiving the first message through the first bearer when at least one of the integrity protection and encryption functions of the first bearer is not enabled;

[0440] The sending module 1401 sends a second message through the first bearer, including: sending a second message through the first bearer when at least one of the integrity protection and encryption functions of the first bearer is not enabled.

[0441] Optionally, the receiving module 1402 is further configured to: receive third configuration information;

[0442] The device further includes a processing module for disabling or enabling at least one of the integrity protection and encryption functions of the first bearer based on the third configuration information.

[0443] Optionally, the receiving module 1402 is further configured to: receive a third message via a second bearer before the first bearer is established;

[0444] And / or, the sending module 1401 is further configured to: send a fourth message via the second bearer before the first bearer is established;

[0445] The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device.

[0446] The second bearer is not dedicated to transmitting data from IoT devices.

[0447] Referring to Figure 15, when the data transmission device is a core network device or a component within a core network device, the data transmission device 150 includes:

[0448] Transmitting module 1501 and / or receiving module 1502;

[0449] The receiving module 1502 is used to: receive a fifth message sent by the access network device, wherein the fifth message includes an identifier of a first channel and first data of at least one Internet of Things device, and the first channel is a transmission channel between the core network device and the access network device;

[0450] The sending module 1501 is used to send a sixth message to the access network device, wherein the sixth message includes the identifier of the first channel and second data to be sent to at least one Internet of Things device.

[0451] Optionally, the identifier of the first channel included in the sixth message is determined based on the correspondence between the first identifier and the identifier of the first channel, and the second identifier of the IoT device used to receive the second data; the first identifier is a global identifier used by the IoT device and the core network device to identify the IoT device.

[0452] The data transmission device provided in this application embodiment can implement the various processes implemented in the method embodiments of FIG5, FIG11 and FIG12, and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0453] As shown in Figure 16, this application embodiment also provides a communication device 1600, including a processor 1601 and a memory 1602. The memory 1602 stores a program or instructions that can run on the processor 1601. For example, when the communication device 1600 is a terminal, the program or instructions executed by the processor 1601 implement the various steps of the data transmission method embodiment applied to the terminal described above, and achieve the same technical effect. When the communication device 1600 is a network-side device, the program or instructions executed by the processor 1601 implement the various steps of the data transmission method embodiment applied to the access network device or core network device described above, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0454] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG5. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the data transmission device shown in FIG13. Specifically, FIG17 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0455] The terminal 1700 includes, but is not limited to, at least some of the following components: radio frequency unit 1701, network module 1702, audio output unit 1703, input unit 1704, sensor 1705, display unit 1706, user input unit 1707, interface unit 1708, memory 1709, and processor 1710.

[0456] Those skilled in the art will understand that terminal 1700 may also include a power supply (such as a battery) for powering various components. The power supply may be logically connected to processor 1710 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 17 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0457] It should be understood that, in this embodiment, the input unit 1704 may include a graphics processor 17041 and a microphone 17042. The graphics processor 17041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1706 may include a display panel 17061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1707 includes at least one of a touch panel 17071 and other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include a touch detection device and a touch controller. Other input devices 17072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0458] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1701 can transmit it to the processor 1710 for processing; in addition, the radio frequency unit 1701 can send uplink data to the network-side device. Typically, the radio frequency unit 1701 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0459] The memory 1709 can be used to store software programs or instructions, as well as various data. The memory 1709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1709 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1709 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0460] Processor 1710 may include one or more processing units; optionally, processor 1710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1710.

[0461] The radio frequency unit 1701 is used to: transmit a first message through a first bearer, and / or receive a second message through the first bearer;

[0462] The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device;

[0463] The first bearer satisfies at least one of the following:

[0464] The first bearer is a bearer specifically used for transmitting data from IoT devices;

[0465] The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs;

[0466] The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

[0467] Optionally, the radio frequency unit 1701 transmits a first message via a first bearer, including:

[0468] Based on the transmission parameter information of the first bearer, the first message is sent through the first bearer;

[0469] The radio frequency unit 1701 receives a second message through the first bearer, including:

[0470] The first message is sent through the first bearer based on the transmission parameter information of the first bearer.

[0471] Optionally, the transmission parameter information includes at least one of the following:

[0472] The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold, the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices, and the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers.

[0473] The first bearer has a guaranteed bit rate, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinitely large, or is less than or equal to a second threshold;

[0474] The first bearer supports configuration information for unacknowledged UM mode transmission.

[0475] Optionally, the transmission parameter information is agreed upon through a protocol, configured by the access network device, or reconfigured by the access network device.

[0476] Optionally, the transmission parameter information includes N parameters, where N is greater than or equal to 1;

[0477] When the first configuration information includes a first parameter, the radio frequency unit 1701 uses the value of the first parameter included in the first configuration information, wherein the first configuration information is used to configure the first bearer, and the first parameter includes at least some of the parameters among the N parameters.

[0478] Alternatively, if the first parameter is not included in the first configuration information, the radio frequency unit 1701 uses the value of the first parameter as agreed in the protocol.

[0479] Optionally, the first message and / or the second message are Radio Resource Control (RRC) messages dedicated to carrying data from IoT devices.

[0480] Optionally, the radio frequency unit 1701 is further configured to: send a release request, wherein the release request is used to request the release of the first bearer.

[0481] Optionally, the identification information includes at least one of the following:

[0482] The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices;

[0483] The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface;

[0484] The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

[0485] Optionally, if the identification information included in the first message includes the second identifier, the second identifier included in the first message is the second identifier obtained by the radio frequency unit 1701 when receiving the first data through the IoT interface.

[0486] Optionally, if the identification information included in the first message includes the first identifier, the first identifier included in the first message is determined based on the first correspondence and the second identifier obtained by the radio frequency unit 1701 when receiving the first data at the IoT interface. The first correspondence includes the correspondence between the second identifier and the first identifier.

[0487] Optionally, if the identification information included in the first message includes the third identifier, the third identifier included in the first message is determined based on the second correspondence and the second identifier obtained by the radio frequency unit 1701 when receiving the first data at the IoT interface. The second correspondence includes the correspondence between the second identifier and the third identifier.

[0488] Optionally, if the identification information included in the second message includes the second identifier, the second identifier included in the second message is carried by the radio frequency unit 1701 when sending the second data to the corresponding IoT device.

[0489] Optionally, the processor 1710 is used for:

[0490] If the identification information included in the second message includes the first identification, the second identification is determined according to the first correspondence and the first identification included in the second message. The second identification is carried by the radio frequency unit 1701 when sending the second data to the corresponding IoT device. The first correspondence includes the correspondence between the second identification and the first identification.

[0491] Optionally, the processor 1710 is also used for:

[0492] If the identification information included in the second message includes the third identifier, the second identifier is determined according to the second correspondence and the third identifier included in the first message. The second identifier is carried by the radio frequency unit 1701 when sending the second data to the corresponding IoT device. The second correspondence includes the correspondence between the second identifier and the third identifier.

[0493] Optionally, the processor 1710 is also used for:

[0494] When the radio frequency unit 1701 receives the first data packet from the Internet of Things device, it establishes or stores the first correspondence between the second identifier and the first identifier obtained when the radio frequency unit 1701 receives the first data packet.

[0495] Optionally, the processor 1710 is further configured to: assign the third identifier to the IoT device to which the first data packet belongs when the radio frequency unit 1701 receives the first data packet from the IoT device;

[0496] Alternatively, the radio frequency unit 1701 is further configured to: request the third identifier of the IoT device to which the first data packet belongs from the access network device.

[0497] Optionally, the processor 1710 is further configured to establish or store the second correspondence between the third identifier and the second identifier obtained by the radio frequency unit 1701 when receiving the first data packet.

[0498] Optionally, the radio frequency unit 1701 transmits a first message via a first bearer, including:

[0499] The first message is sent through the first bearer if at least one of the integrity protection and encryption functions of the first bearer is not enabled;

[0500] The radio frequency unit 1701 receives a second message through the first bearer, including:

[0501] The second message is received through the first bearer if at least one of the integrity protection and encryption functions of the first bearer is not enabled.

[0502] Optionally, the radio frequency unit 1701 is further configured to:

[0503] Receive the second configuration information;

[0504] The processor 1710 is further configured to: disable or enable at least one of the integrity protection and encryption functions of the first bearer according to the second configuration information.

[0505] Optionally, the radio frequency unit 1701 is further configured to: send a third message via the second bearer before the first bearer is established;

[0506] And / or, the radio frequency unit 1701 is further configured to: receive a fourth message via the second bearer before the first bearer is established;

[0507] The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device.

[0508] The second bearer is not dedicated to transmitting data from IoT devices.

[0509] Optionally, the processor 1710 is further configured to: perform cell handover when the first bearer is present and the cell handover conditions are met.

[0510] Optionally, the processor 1710 is further configured to: retain the entity and cache of the first bearer after performing a cell handover.

[0511] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0512] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG11. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0513] Specifically, this application embodiment also provides a network-side device, which can be the data transmission device shown in FIG14. As shown in FIG18, the network-side device 1800 includes: an antenna 181, a radio frequency device 182, a baseband device 183, a processor 184, and a memory 185. The antenna 181 is connected to the radio frequency device 182. In the uplink direction, the radio frequency device 182 receives information through the antenna 181 and sends the received information to the baseband device 183 for processing. In the downlink direction, the baseband device 183 processes the information to be transmitted and sends it to the radio frequency device 182. The radio frequency device 182 processes the received information and transmits it through the antenna 181.

[0514] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 183, which includes a baseband processor.

[0515] The baseband device 183 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG18. One of the chips is, for example, a baseband processor, which is connected to the memory 185 via a bus interface to call the program in the memory 185 and execute the network device operation shown in the above method embodiment.

[0516] The network-side device may also include a network interface 186, such as a Common Public Radio Interface (CPRI).

[0517] Specifically, the network-side device 1800 in this application embodiment further includes: instructions or programs stored in memory 185 and executable on processor 184. Processor 184 calls the instructions or programs in memory 185 to execute the methods executed by each module shown in FIG14 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0518] Specifically, this application also provides a network-side device. As shown in FIG19, the network-side device 1900 includes a processor 1901, a network interface 1902, and a memory 1903. The network-side device may be the data transmission device shown in FIG15. The network interface 1902 is, for example, a Common Public Radio Interface (CPRI).

[0519] Specifically, the network-side device 1900 in this application embodiment further includes: instructions or programs stored in memory 1903 and executable on processor 1901. Processor 1901 calls the instructions or programs in memory 1903 to execute the methods executed by each module shown in FIG15 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0520] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0521] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0522] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0524] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0525] This application also provides a wireless communication system, including: a terminal and an access network device, wherein the terminal can be used to execute the steps of the data transmission method applied to the terminal as described above, and the network-side device can be used to execute the steps of the data transmission method applied to the access network device as described above.

[0526] Optionally, the wireless communication system further includes a core network device, which is used to perform the steps of the data transmission method applied to the core network device described above.

[0527] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0528] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0529] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A data transmission method, wherein, The method includes: The terminal sends a first message through the first bearer, and / or receives a second message through the first bearer; The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device. The first bearer satisfies at least one of the following: The first bearer is a bearer specifically used for transmitting data from IoT devices; The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs; The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

2. The method according to claim 1, wherein, The terminal sends a first message through a first bearer and / or receives a second message through the first bearer, including: The terminal sends the first message through the first bearer and / or receives the second message through the first bearer according to the transmission parameter information of the first bearer.

3. The method according to claim 2, wherein, The transmission parameter information includes at least one of the following: The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold, the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices, and the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers. The first bearer has a guaranteed bit rate, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinitely large, or is less than or equal to a second threshold; The first bearer supports configuration information for unacknowledged UM mode transmission.

4. The method according to claim 2 or 3, wherein, The transmission parameter information is agreed upon through a protocol, configured through access network equipment, or reconfigured through access network equipment.

5. The method according to any one of claims 2 to 4, wherein, The transmission parameter information includes N parameters, where N is greater than or equal to 1; When the first configuration information includes a first parameter, the terminal uses the value of the first parameter included in the first configuration information, wherein the first configuration information is used to configure the first bearer, and the first parameter includes at least some of the parameters among the N parameters; or, If the first parameter is not included in the first configuration information, the terminal uses the value of the first parameter as agreed in the protocol.

6. The method according to any one of claims 1 to 5, wherein, The first message and / or the second message are Radio Resource Control (RRC) messages specifically used to carry data from IoT devices.

7. The method according to any one of claims 1 to 6, wherein, The method further includes: The terminal sends a release request, wherein the release request is used to request the release of the first bearer.

8. The method according to any one of claims 1 to 7, wherein, The identification information includes at least one of the following: The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices; The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface; The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

9. The method according to claim 8, wherein, If the identification information included in the first message includes the second identifier, then the second identifier included in the first message is the second identifier obtained by the terminal when receiving the first data through the IoT interface.

10. The method according to claim 8 or 9, wherein, When the identification information included in the first message includes the first identifier, the first identifier included in the first message is determined based on the first correspondence and the second identifier obtained by the terminal when receiving the first data at the IoT interface. The first correspondence includes the correspondence between the second identifier and the first identifier.

11. The method according to any one of claims 8 to 10, wherein, If the identification information included in the first message includes the third identifier, the third identifier included in the first message is determined based on the second correspondence and the second identifier obtained by the terminal when receiving the first data at the IoT interface. The second correspondence includes the correspondence between the second identifier and the third identifier.

12. The method according to any one of claims 8 to 11, wherein, If the identification information included in the second message includes the second identifier, the second identifier included in the second message is used by the terminal to carry the second data when sending the second data to the corresponding IoT device.

13. The method according to claim 10, wherein, The method further includes: When the terminal receives the first data packet from the IoT device, the terminal establishes or stores the first correspondence between the second identifier and the first identifier obtained when the terminal receives the first data packet.

14. The method according to claim 11, wherein, The method further includes: When the terminal receives the first data packet from the IoT device, the terminal assigns the third identifier to the IoT device to which the first data packet belongs, or the terminal requests the third identifier of the IoT device to which the first data packet belongs from the access network device.

15. The method according to claim 14, wherein, The method further includes: The terminal establishes or stores the second correspondence between the third identifier and the second identifier obtained when the terminal receives the first data packet.

16. The method according to any one of claims 1 to 15, wherein, The terminal sends a first message through a first bearer and / or receives a second message through the first bearer, including: If at least one of the integrity protection and encryption functions of the first bearer is not enabled, the terminal sends a first message through the first bearer and / or receives a second message through the first bearer.

17. The method according to claim 16, wherein, The method further includes: The terminal receives second configuration information and, based on the second configuration information, disables or enables at least one of the integrity protection and encryption functions of the first bearer.

18. The method according to any one of claims 1 to 17, wherein, The method further includes: Before the first bearer is established, the terminal sends a third message through the second bearer and / or receives a fourth message through the second bearer; The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device. The second bearer is not dedicated to transmitting data from IoT devices.

19. The method according to any one of claims 1 to 18, wherein, The method further includes: If the first bearer exists and the cell handover conditions are met, the terminal performs a cell handover.

20. The method according to claim 19, wherein, The method further includes: After the terminal performs cell handover, it retains the entity and cache of the first bearer.

21. A data transmission method, wherein, The method includes: The access network device receives a first message through the first bearer and / or sends a second message through the first bearer; The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device. The first bearer satisfies at least one of the following: The first bearer is a bearer specifically used for transmitting data from IoT devices; The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs; The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

22. The method according to claim 21, wherein, The method further includes: The access network device establishes the first bearer.

23. The method according to claim 21 or 22, wherein, The method further includes: The access network device configures or reconfigures the transmission parameter information of the first bearer.

24. The method according to claim 23, wherein, The transmission parameter information includes at least one of the following: The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold, the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices, and the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers. The first bearer has a guaranteed bit rate, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinitely large, or is less than or equal to a second threshold; The first bearer supports configuration information for unacknowledged UM mode transmission.

25. The method according to any one of claims 21 to 24, wherein, The method further includes: The access network device releases the first bearer; or, When the access network device receives a release request, the access network device releases the first bearer, wherein the release request is used to request the release of the first bearer.

26. The method according to any one of claims 21 to 25, wherein, The first message and / or the second message are Radio Resource Control (RRC) messages specifically used to carry data from IoT devices.

27. The method according to any one of claims 21 to 26, wherein, The identification information includes at least one of the following: The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices; The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface; The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

28. The method according to any one of claims 21 to 27, wherein, The method further includes: The access network device determines the identifier of the first channel based on the third correspondence and the identification information included in the first message. The third correspondence includes the correspondence between the identification information and the identifier of the first channel. The identifier of the first channel is carried by the access network device when sending the first data to the core network device. The first channel is the transmission channel between the access network device and the core network device.

29. The method according to any one of claims 21 to 28, wherein, The access network device receives a first message through a first bearer and / or sends a second message through the first bearer, including: If at least one of the integrity protection and encryption functions of the first bearer is not enabled, the access network device receives the first message through the first bearer and / or sends the second message through the first bearer.

30. The method according to claim 29, wherein, The method further includes: The access network device receives third configuration information and, based on the third configuration information, disables or enables at least one of the integrity protection and encryption functions of the first bearer.

31. The method according to any one of claims 21 to 30, wherein, The method further includes: Before the first bearer is established, the access network device receives a third message through the second bearer and / or sends a fourth message through the second bearer; The third message includes third data from at least one IoT device, and the fourth message includes fourth data that needs to be sent to at least one IoT device. The second bearer is not dedicated to transmitting data from IoT devices.

32. A data transmission device, wherein, Applied to a terminal, the device includes: Transmitting module and / or receiving module; The sending module is used to send a first message through the first bearer; The receiving module is used to receive the second message through the first bearer; The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device; The first bearer satisfies at least one of the following: The first bearer is a bearer specifically used for transmitting data from IoT devices; The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs; The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

33. The apparatus according to claim 32, wherein, The sending module sends a first message through a first bearer, including: Based on the transmission parameter information of the first bearer, the first message is sent through the first bearer; The receiving module receives the second message through the first bearer, including: The first message is sent through the first bearer based on the transmission parameter information of the first bearer.

34. The apparatus according to claim 33, wherein, The transmission parameter information includes at least one of the following: The priority of the first bearer, wherein the priority of the first bearer satisfies at least one of the following: the priority value of the first bearer is greater than or equal to a first threshold, the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the bearers not dedicated to transmitting data of IoT devices, and the priority value of the first bearer is greater than or equal to the priority value of at least a portion of the data bearers. The first bearer has a guaranteed bit rate, wherein the guaranteed bit rate satisfies at least one of the following: is a specific value that is not infinitely large, or is less than or equal to a second threshold; The first bearer supports configuration information for unacknowledged UM mode transmission.

35. The apparatus according to any one of claims 32 to 34, wherein, The identification information includes at least one of the following: The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices; The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface; The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

36. The apparatus according to claim 35, wherein, If the identification information included in the first message includes the second identifier, the second identifier included in the first message is: the second identifier obtained by the receiving module when receiving the first data through the IoT interface.

37. The apparatus according to claim 35 or 36, wherein, When the identification information included in the first message includes the first identifier, the first identifier included in the first message is determined based on the first correspondence and the second identifier obtained by the receiving module when receiving the first data at the IoT interface. The first correspondence includes the correspondence between the second identifier and the first identifier.

38. The apparatus according to any one of claims 35 to 37, wherein, If the identification information included in the first message includes the third identifier, the third identifier included in the first message is determined based on the second correspondence and the second identifier obtained by the receiving module when receiving the first data at the IoT interface. The second correspondence includes the correspondence between the second identifier and the third identifier.

39. The apparatus according to any one of claims 35 to 38, wherein, If the identification information included in the second message includes the second identifier, the second identifier included in the second message is carried by the sending module when sending the second data to the corresponding IoT device.

40. The apparatus according to claim 37, wherein, The device further includes: The processing module is configured to, when the receiving module receives the first data packet from the IoT device, establish or store the first correspondence between the second identifier and the first identifier obtained by the receiving module when receiving the first data packet.

41. The apparatus according to claim 38, wherein, The device further includes: The processing module is configured to assign the third identifier to the IoT device to which the first data packet belongs when the receiving module receives the first data packet from the IoT device; or, The sending module is also used to request the third identifier of the IoT device to which the first data packet belongs from the access network device.

42. The apparatus according to any one of claims 32 to 41, wherein, The sending module sends a first message through a first bearer, including: The first message is sent through the first bearer if at least one of the integrity protection and encryption functions of the first bearer is not enabled; The receiving module receives the second message through the first bearer, including: The second message is received through the first bearer if at least one of the integrity protection and encryption functions of the first bearer is not enabled.

43. The apparatus according to any one of claims 32 to 42, wherein, The device further includes: The processing module is used to perform cell handover when the first bearer exists and the cell handover conditions are met.

44. A data transmission device, wherein, Applied to access network equipment, the device includes: Transmitting module and / or receiving module; The receiving module is used to receive a first message through a first bearer; The sending module is used to send a second message through the first bearer; The first message includes first data from at least one IoT device, and the second message includes second data that needs to be sent to at least one IoT device; The first bearer satisfies at least one of the following: The first bearer is a bearer specifically used for transmitting data from IoT devices; The first message sent through the first bearer also includes: identification information for identifying the IoT device to which the first data belongs; The second message received through the first bearer also includes: identification information for identifying the IoT device receiving the second data.

45. The apparatus according to claim 44, wherein, The identification information includes at least one of the following: The first identifier includes: a global identifier used by IoT devices and core network devices to identify IoT devices; The second identifier includes: a temporary identifier used by the terminal and the IoT device to identify the IoT device at the IoT interface; The third identifier includes: a local identifier used by the terminal and the access network device to identify the Internet of Things device.

46. ​​The apparatus according to claim 44 or 45, wherein, The device further includes: The processing module is configured to determine the identifier of the first channel based on the third correspondence and the identification information included in the first message, wherein the third correspondence includes the correspondence between the identification information and the identifier of the first channel, the identifier of the first channel is carried by the sending module when sending the first data to the core network device, and the first channel is the transmission channel between the access network device and the core network device.

47. The apparatus according to any one of claims 44 to 46, wherein, The receiving module receives a first message through a first bearer, including: receiving a first message through a first bearer when at least one of the integrity protection and encryption functions of the first bearer is not enabled; The sending module sends a second message through the first bearer, including: sending a second message through the first bearer when at least one of the integrity protection and encryption functions of the first bearer is not enabled.

48. A communication device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the data transmission method as described in any one of claims 1 to 20, or being executed to implement the steps of the data transmission method as described in any one of claims 21 to 31.

49. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the data transmission method as described in any one of claims 1 to 20, or, when executed, implement the steps of the data transmission method as described in any one of claims 21 to 31.

Images