Data transmission method, device and equipment

Abstract

The invention discloses a data transmission method, device and equipment, and belongs to the technical field of communication, and the data transmission method comprises the steps that first equipment sends first communication content to second equipment in a non-connection state, the first communication content carries first data, and the second equipment sends the first communication content to the second equipment; and the first communication content is also used for indicating that subsequent data is to be sent to the second equipment after the first data.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a data transmission method, apparatus, and device. Background Art

[0002] The state of a device can often include a connected state and a non-connected state. Among them, the non-connected state can include an idle state (IDLE state) and an inactive state (INACTIVE state). In related technologies, a device often sends and receives data in the connected state. This results in relatively poor data transmission performance of the device. Summary of the Invention

[0003] Embodiments of this application provide a data transmission method, apparatus, and device, which can solve the problem of relatively poor data transmission performance of a device.

[0004] In a first aspect, a data transmission method is provided, including:

[0005] A first device sends first communication content to a second device in a non-connected state, the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0006] In a second aspect, a data transmission method is provided, including:

[0007] A second device receives the first communication content sent by the first device in the non-connected state, the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0008] In a third aspect, a data transmission apparatus is provided, including:

[0009] A first sending module, configured to send first communication content to a second device in a non-connected state, the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0010] In a fourth aspect, a data transmission apparatus is provided, including:

[0011] A first receiving module, configured to receive the first communication content sent by the first device in the non-connected state, the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0012] In a fifth aspect, a device is provided, which includes a processor and a memory. The memory stores a program or instructions that can be run on the processor. When the program or instructions are executed by the processor, the steps of the data transmission method on the first device side provided in the embodiments of the present application are implemented.

[0013] In a sixth aspect, a device is provided, including a processor and a communication interface. The communication interface is used to send first communication content to a second device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0014] In a seventh aspect, a device is provided, which includes a processor and a memory. The memory stores a program or instructions that can be run on the processor. When the program or instructions are executed by the processor, the steps of the data transmission method on the second device side provided in the embodiments of the present application are implemented.

[0015] In an eighth aspect, a device is provided, including a processor and a communication interface. The communication interface is used to receive first communication content sent by a first device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0016] In a ninth aspect, a readable storage medium is provided. A program or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, the steps of the data transmission method on the first device side provided in the embodiments of the present application are implemented, or the steps of the data transmission method on the second device side provided in the embodiments of the present application are implemented.

[0017] In a tenth aspect, a wireless communication system is provided, including: a first device and a second device. The first device can be used to execute the steps of the data transmission method on the first device side provided in the embodiments of the present application, and the second device can be used to execute the steps of the data transmission method on the second device side provided in the embodiments of the present application.

[0018] In an eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instructions to implement the data transmission method on the first device side provided in the embodiments of the present application, or to implement the steps of the data transmission method on the second device side provided in the embodiments of the present application.

[0019] In a twelfth aspect, there is provided a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the steps of the data transmission method on the first device side provided in the embodiments of the present application, or the program / program product is executed by at least one processor to implement the steps of the data transmission method on the second device side provided in the embodiments of the present application.

[0020] In the embodiments of the present application, the first device sends first communication content to the second device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data. This can achieve data transmission in a non-connected state to improve the transmission performance of the device. Moreover, since the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data, this can support multiple data transmissions and further improve the transmission performance of the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0022] Figure 2 is an instruction indication diagram of a reader and a tag provided in the embodiments of the present application;

[0023] Figure 3 is a flowchart of a data transmission method provided in the embodiments of the present application;

[0024] Figure 4 is a flowchart of another data transmission method provided in the embodiments of the present application;

[0025] Figure 5 is a structural diagram of a data transmission device provided in the embodiments of the present application;

[0026] Figure 6 is a structural diagram of another data transmission device provided in the embodiments of the present application;

[0027] Figure 7 is a structural diagram of a communication device provided in the embodiments of the present application;

[0028] Figure 8 is a structural diagram of another communication device provided in the embodiments of the present application;

[0029] Figure 9 is a structural diagram of another communication device provided in the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0030] The following will clearly describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application fall within the scope of protection of the present application.

[0031] The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects. For example, the first object can be one or multiple. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates an "or" relationship between the associated objects before and after.

[0032] The term "indicate" in the present application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly informs the receiver of specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0033] It should be noted that the technology described in the embodiments of this application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and 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 the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th Generation (6 th Generation, 6G) communication system.

[0034] Figure 1The block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines, or furniture, etc.), a game console, a personal computer (PC), an ATM, a self-service machine, an internet of things (IoT) device, or an ambient internet of things (A-IoT) device, etc., which are terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be called a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip, or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application.

[0035] The network-side device 12 may include an access network device or a core network device. Among them, the access network device may also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc. Among them, the base station may be referred to as Node B (NB), Evolved Node B (eNB), the 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, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0036] The core network device may include, but is not limited to, at least one of the following: core network nodes, core network functions, 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 (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of this application, only the core network devices in the NR system are taken as examples for introduction, and the specific types of core network devices are not limited.

[0037] In some embodiments, according to the A-IoT devices can be classified based on energy source, energy storage capability, passive or active transmission, etc., and can be divided into the following device types:

[0038] Device A: Belongs to a passive device, has no energy storage, and has no independent signal generation / amplification, i.e., backscatter transmission;

[0039] Device B: A semi - passive device, which also belongs to the large category of passive devices. It has energy storage and no independent signal generation, i.e., backscatter transmission. The use of the stored energy can include the amplification of the reflected signal;

[0040] Device C: An active device, which has energy storage and independent signal generation, i.e., an active radio frequency component for transmission.

[0041] In some embodiments, the A - IoT device can be a tag or other low - power IoT devices.

[0042] In some embodiments, a non - tag terminal or network - side device can act as a reader for a tag, and the tag can be a Radio Frequency Identification (RFID) tag.

[0043] In some embodiments, the information transmission between the reader and the tag can be as Figure 2 shown, and the reader operation instructions can be as shown in Table 1:

[0044] Table 1:

[0045]

[0046] In some embodiments, the status of the tag is as shown in Table 2:

[0047] Table 2:

[0048]

[0049] It should be noted that the above Table 1 and Table 2 only give examples of the information transfer between the reader and the tag. In the embodiments of the present application, the information transfer between the reader and the tag is not specifically limited.

[0050] Next, in conjunction with the accompanying drawings, through some embodiments and their application scenarios, a data transmission method, apparatus, and device provided by the embodiments of the present application will be described in detail.

[0051] Please refer to Figure 3 , Figure 3 which is a flowchart of a data transmission method provided by the embodiments of the present application. As Figure 3 shown, it includes the following steps:

[0052] Step 301: The first device sends the first communication content to the second device in the non-connected state. The first communication content carries the first data, and the first communication content is also used to indicate that there is subsequent data to be sent to the second device after the first data.

[0053] Among them, the above-mentioned first device can be a terminal or a network-side device, such as an AIoT device or an IoT device, etc., and the embodiments of this application do not limit this. The above-mentioned second device can be a network-side device or a terminal, or a reader of a tag.

[0054] The first device sending the first communication content to the second device in the non-connected state can include:

[0055] The first device in the non-connected state sends the first communication content to the second device, such as a terminal in the non-connected state sending the first communication content to the network-side device; or

[0056] The first device sends the first communication content to the second device in the non-connected state, such as the network-side device sending the first communication content to the terminal in the non-connected state.

[0057] The first communication content is the communication content sent by the first device to the second device, and can include, but is not limited to, the communication content of at least one of the following protocol layers:

[0058] Radio Resource Control (RRC) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer.

[0059] The above non-connected state can be the idle state or the inactive state.

[0060] The above first data can be at least one data packet, at least one data block or at least one data segment.

[0061] The above indication that there is subsequent data to be sent to the second device after the first data can be an indication that the first device has subsequent data to be sent to the second device after the first data in the non-connected state, so as to achieve multiple data transmissions in the non-connected state.

[0062] In some embodiments, the indication that there is subsequent data to be sent to the second device after the first data is not limited to the non-connected state, but only indicates that there is subsequent data to be sent to the second device after the first data. For example, the RRC state can also be controlled by the network-side device. If the network-side device algorithm determines that, in cases such as light load or other situations, when the first device indicates subsequent data, the first device can be switched to the connected state (CONNECTED) for subsequent data transmission.

[0063] Among them, the subsequent data mentioned above can also be called consecutive data, and can be one or more data, such as one or more data packets, one or more data blocks, or one or more data segments.

[0064] The above-mentioned first communication content is also used to indicate that there is subsequent data to be sent to the second device after the first data, which can be an explicit indication. For example, indication information is carried in the first communication content, and this indication information indicates that there is subsequent data to be sent to the second device after the first data; or it can be an implicit indication, such as indicating that there is subsequent data to be sent to the second device after the first data through the format of the first communication content or by multiplexing the indication field of the first communication content.

[0065] In the embodiments of the present application, data can be transmitted in the non-connected state through the above steps to improve the transmission performance of the device. And since the first communication content is also used to indicate that there is subsequent data to be sent to the second device after the first data, this can support multiple data transmissions and further improve the transmission performance of the device.

[0066] As an alternative embodiment, the first communication content includes at least one of the following:

[0067] RRC message, MAC protocol data unit (PDU).

[0068] Among them, the above-mentioned MAC PDU can be a newly defined MAC PDU in the embodiments of the present application.

[0069] In this embodiment, it can be realized that at least one of the RRC message or the MAC PDU carries the above-mentioned first data.

[0070] In this embodiment, it is possible to indicate, through the above RRC message or MAC PDU, that there is subsequent data to be sent to the second device after the first data. It is also possible that, in addition to the above RRC message or MAC PDU, the first communication content includes other content, such as a MAC control element (CE) or a MAC sub-header, and the MAC CE or MAC sub-header is used to indicate that there is subsequent data to be sent to the second device after the first data.

[0071] In some embodiments, the above RRC message includes at least one of the following:

[0072] An RRC early data request message, or an RRC early data response message;

[0073] An RRC uplink message, or an RRC downlink message;

[0074] Among them, the RRC uplink message and the RRC early data request message are different RRC messages, and the RRC downlink message and the RRC early data response message are different RRC messages.

[0075] Among them, the above RRC early data response may be an RRC early data complete message.

[0076] Among them, the above RRC uplink message and RRC downlink message can be understood as RRC messages newly defined in the embodiments of the present application, such as an RRC continuous data request message and an RRC continuous data response message.

[0077] In the above embodiment, it is possible to achieve continuous data transmission through multiple messages to improve the flexibility of data transmission.

[0078] As an alternative embodiment, after the first device sends the first communication content to the second device in the non-connected state, the method further includes:

[0079] The first device sends second communication content to the second device in the non-connected state, the second communication content carries second data, and the second communication content is further used to indicate:

[0080] There is subsequent data to be sent to the second device after the second data; or,

[0081] There is no subsequent data to be sent to the second device after the second data.

[0082] Wherein, the above-mentioned second data is at least one data packet, at least one data block or at least one data segment after the above-mentioned first data.

[0083] In the case of indicating that there is subsequent data to be sent to the second device after the second data, data continuous transmission can be achieved 3 times or more; in the case of indicating that there is no subsequent data to be sent to the second device after the second data, data continuous transmission can be achieved 2 times. To improve data transmission performance.

[0084] Optionally, the first communication content includes: an RRC early transmission data request message, or an RRC early transmission data response message;

[0085] The second communication content includes: an RRC uplink message, or an RRC downlink message;

[0086] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0087] In this embodiment, different messages can be used for transmission during data continuous transmission to improve the compatibility of data transmission.

[0088] In some embodiments, the above-mentioned first communication content and second communication content can also be the same message, such as both being the above-mentioned RRC uplink message or RRC downlink message, or the above-mentioned first communication content includes a MAC PDU.

[0089] For example: for multiple consecutive uplink data, adopt an RRC Early Data Request or a new RRC message (i.e., the above-mentioned RRC uplink message), such as an RRC Continuous Data Request, or design a new MAC PDU format to carry high-layer data and assist in the release assistance information (RAI) format or end marker method for transmission, where the RAI format can be the newly defined RAI format in the embodiments of the present application and can include the following methods:

[0090] The first method: N RRC Early Data Request messages respectively carry high-layer data, and assist the RAI format / End marker to complete the transmission;

[0091] The second method: various combinations of RRC Early Data Request messages + RRC Continuous Data Request messages carry high-layer data respectively, and assist the RAI format / End marker to complete the transmission;

[0092] The third method: N RRC Continuous Data Request messages, optionally, assist the RAI format / Endmarker to complete the transmission;

[0093] The fourth method: N new MAC PDUs carry high-layer data respectively, and assist the RAI format / End marker to complete the transmission.

[0094] Among them, the above-mentioned assisting the RAI format / End marker to complete the transmission can be understood as that the above-mentioned message or MAC PDU carries the RAI format / End marker

[0095] For multiple consecutive downlink data, adopt RRC Early Data Complete or a new RRC message (i.e., the above-mentioned RRC downlink message), such as RRC Continuous Data Response, or design a new MAC PDU to carry high-layer data, and assist the new RAI format / End marker to carry out, which can include the following methods:

[0096] The first method: N RRC Early Data Complete messages carry high-layer data respectively, and assist the RAI format / End marker to complete the transmission;

[0097] The second method: N RRC Continuous Data Response messages carry high-layer data respectively, and assist the RAI format / End marker to complete the transmission;

[0098] The third method: Combinations of RRC Early Data Complete and RRC Continuous Data Response carry high-layer data respectively, optionally, assist the RAI format / End marker to complete the transmission;

[0099] The fourth method: N new MAC format PDUs carry high-layer data respectively, and assist the RAI format / End marker to complete the transmission.

[0100] Among them, the functions of the above-mentioned RAI format / End marker can include at least one of the following:

[0101] The first device stops the relevant timer and resets the MAC entity;

[0102] The last message may carry redirection information, IDLE mobility information, etc.;

[0103] Finally, an operation similar to RRC connection release is performed.

[0104] As an optional implementation manner, the first device sends first communication content to the second device in the non-connected state, including:

[0105] When the first device determines that the target condition is met, the first device sends first communication content to the second device in the non-connected state, where the target condition includes at least one of the following:

[0106] There are multiple pieces of high-layer data;

[0107] The high-layer data needs to be segmented for transmission;

[0108] There is only one piece of high-layer data, and the size of the one piece of data is greater than a preset threshold;

[0109] The link quality is a preset quality;

[0110] The RRC layer or the MAC layer receives an indication of the possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication of continuous data transmission.

[0111] Among them, the above-mentioned target condition, preset threshold, and preset quality may be agreed upon by the protocol or configured by the network side, or determined by the first device itself.

[0112] The above-mentioned situation that there is only one piece of high-layer data and the size of the one piece of data is greater than the preset threshold may indicate that the size of this one piece of data is large and needs to be segmented for transmission.

[0113] The above-mentioned situation that the link quality is the preset quality may indicate that the link quality is poor. For example, if the link quality does not meet the threshold, multiple attempts may be required.

[0114] In this implementation manner, since when the first device determines that the target condition is met, the first device sends first communication content to the second device in the non-connected state, continuous data transmission can be adopted according to actual needs, so as to improve the transmission performance of the device.

[0115] Optionally, the method further includes:

[0116] When the first device determines that the target condition is not met, the first device sends third communication content to the second device in the non-connected state. The third communication content carries third data, and the data transmission process corresponding to the third communication content can only transmit one piece of data in the uplink or downlink.

[0117] Among them, it can be understood that the data transmission process corresponding to the above third communication content can only transmit data once in the uplink or downlink. That is, when using the above third communication content for data transmission, only one uplink data or one downlink data can be transmitted in the non-connected state, which means that continuous data transmission cannot be achieved. For example, the data transmission process corresponding to the above third communication content is to use Small Data Transmission (SDT) or Early Data Transmission (EDT).

[0118] In this embodiment, it is possible to send the third communication content to the second device when the target condition is not met, thereby achieving discontinuous data transmission to save device resources.

[0119] As an optional embodiment, the first device sends the first communication content to the second device in the non-connected state, including:

[0120] When the RRC layer of the first device obtains the target judgment result, the first device sends the first communication content to the second device in the non-connected state, where the target judgment result includes at least one of the following:

[0121] Based on the data that has reached the RRC layer, it is judged that the service transmission requirement is for multi-data transmission;

[0122] Based on the data that has reached the RRC layer, it is judged that segmented transmission is required;

[0123] Based on the service type or the indication received by the RRC layer, it is judged that there is subsequent data transmission;

[0124] Based on the service type or the indication received by the RRC layer, it is impossible to judge whether there is subsequent data transmission.

[0125] Among them, the above judgment that the service transmission requirement is for multi-data transmission based on the data that has reached the RRC layer may be that the RRC layer judges that the data that has reached the RRC layer cannot be completed by one data transmission, or based on the data that has reached the RRC layer, it is judged that there is still subsequent data.

[0126] The above judgment that segmented transmission is required based on the data that has reached the RRC layer may be that the RRC layer judges that the data that has reached the RRC layer cannot be completed by one transmission, such as when the data size is too large and segmented transmission is required.

[0127] The above judgment that there is subsequent data transmission based on the service type may be that there are multiple data of this service type.

[0128] In this embodiment, since the first device sends the first communication content to the second device in a non-connected state when the target judgment result is obtained, data can be continuously transmitted according to actual needs, thereby improving the transmission performance of the device.

[0129] As an optional embodiment, the first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following:

[0130] The format of the first communication content;

[0131] The data number information carried by the first communication content, and the data number information represents multiple data;

[0132] The non-ending mark carried by the first communication content;

[0133] The data segmentation information carried by the first communication content.

[0134] The format of the first communication content mentioned above can be understood as the format for continuous data transmission, that is, when it is indicated by this format that it is not a one-time transmission, or when there is no further clear ending mark in this format, it indicates that there is subsequent data.

[0135] The data number information carried by the first communication content mentioned above can be the total data number information or the remaining untransmitted data number information.

[0136] In some embodiments, the above data segmentation information includes at least one of the following:

[0137] Segment sequence number, tail segment identifier, total number of segments, and the value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

[0138] Among them, the above tail segment identifier corresponds to multiple values, and these multiple values are used to indicate whether it is a tail segment or not. For example, 0 indicates a tail segment and 1 indicates not a tail segment. The value of the tail segment identifier carried by the first communication content indicates not a tail segment, that is, it indicates that there is subsequent data to be sent to the second device after the first data. And when the second communication content indicates that there is no subsequent data to be sent to the second device after the second data, the value of the tail segment identifier in the second communication content indicates a tail segment.

[0139] In an optional embodiment, it can be realized that there are multiple ways to indicate that there is subsequent data to be sent to the second device after the first data, so as to improve the flexibility of data transmission.

[0140] As an optional embodiment, the RLC layer of the first device performs at least one of the following transmission processes:

[0141] Transmit the first communication content in Transparent Mode (TM), Acknowledged Mode (AM), or Unacknowledged Mode (UM);

[0142] Transmit the first data carried in the first communication content in segments;

[0143] Multiple service transmission requirements are carried out simultaneously, and the multiple service transmission requirements include the service transmission requirement to which the first data belongs.

[0144] The above-mentioned transmission of the first data carried in the first communication content in segments can be understood as segmenting at the RLC layer, that is, the above-mentioned first data is a data segment obtained by segmenting at the RLC layer. In some embodiments, the segmentation can also be performed at the RRC layer, which is not limited herein.

[0145] The above-mentioned multiple service transmission requirements being carried out simultaneously can be that multiple service transmission requirements are parallel, or there is an overlap in the transmission process of multiple service transmission requirements, and these can be determined by the trigger of a higher layer such as the application layer. Generally speaking, if different service transmissions have different Quality of Service (QoS) requirements or different transmission parameter requirements, different bearers or different LCIDs can be used to correspond to different services to meet different requirements. When different service data are transmitted at the bottom layer, a multi-Hybrid Automatic Repeat Request (HARQ) process processing method can also be adopted to avoid waiting. For example: 2 Hybrid Automatic Repeat Request (HARQ) processes, different service data can adopt different HARQ processes for transmission. For example, HARQ process 1 sends the data 1 of service 1 in the first time slot, and HARQ process 2 immediately sends the data 2 of service 2 in the second time slot. For example, the second time slot = the first time slot + 1, and for the HARQ process 1 of the data 1 of service 1, considering processes such as feedback and retransmission, if everything goes smoothly, it will take at least the first time slot + 4 (successful transmission without retransmission), or even the first time slot + 12 (successful first retransmission) to truly complete. In the above process, the data 2 of service 2 of HARQ process 2 has a large overlap with HARQ process 1, and even the data 2 of service 2 ends first. That is, although the data 2 of service 2 needs to be transmitted after the data 1 of service 1 according to the arrival order or priority order, due to the existence of different processes, simultaneous or overlapping processing can be performed, avoiding the waiting of the data 2 of service 2.

[0146] Among them, the above-mentioned multiple data transmission requirements can be mapped to different RLC entities for processing.

[0147] In the above implementation, through the above RLC layer, multiple transmission modes can be used for transmission to improve the flexibility of data transmission, and multiple service transmission requirements are carried out simultaneously, which can improve the efficiency of data transmission.

[0148] Optionally, when the RLC layer adopts the AM or UM transmission mode, the RLC entity of the RLC layer delivers the first data and the subsequent data of the first data in the order of the serial number (SN), where the initial value of SN is 0.

[0149] In this implementation, since the initial value of SN is 0, it can be ensured that devices in the non-connected state can have the same understanding of SN as the peer device, so as to improve data performance. For example: when a first device initiates a new small data transmission, the initial value of SN of the RLC entity starts from 0, that is, the SN of the first data packet is 0, the SN of the second data packet is 1, and so on. Similarly, when an AIoT device is the receiving end of this time, the initial value of the SN variable of the receiving entity also starts from 0, that is, the SN of the next expected received data packet is 0; correspondingly, when the network side or the reader side conducts a new small data transmission with an AIoT device, the initial variable of SN at the RLC receiving end also starts from 0, that is, the SN of the next expected received data packet is 0, including that the SN of the first DL data packet when the network side is the sending end during this small data transmission is also 0, and the subsequent ones increase in sequence.

[0150] Optionally, when the service transmission requirements corresponding to the RLC entity are completed, perform one of the following operations on the RLC entity:

[0151] Delete, reset, clear.

[0152] Among them, the service transmission requirements corresponding to the above RLC entity can be at least one service transmission requirement executed by the RLC entity.

[0153] Since the RLC entity is deleted, reset or cleared when the service transmission requirements corresponding to the RLC entity are completed, this can save the resources of the RLC layer.

[0154] Optionally, when multiple service transmission requirements are carried out simultaneously, different service transmission requirements use different logical channel identities (LCIDs), and the transmission configurations used by different service transmission requirements are protocol agreements or pre-configurations.

[0155] Among them, the above transmission configuration may include at least one of the following:

[0156] Transmission data type, RLC parameters, etc.

[0157] In addition, different LCIDs may correspond to different RLC entities, and the configuration of each RLC entity is agreed upon by the protocol or pre-configured.

[0158] In this embodiment, since the transmission configuration adopted for different service transmission requirements is agreed upon by the protocol or pre-configured, the configuration of RRC dedicated signaling is avoided, and the configuration of RRC dedicated signaling requires operations such as establishing an RRC connection and activating the security of the Access Stratum (AS) layer, so as to save the power consumption of the device.

[0159] As an alternative embodiment, the first communication content is the communication content sent during at least one of the following processes:

[0160] Random access process, initial registration, attachment, Non-access stratum (NAS) context establishment, NAS security activation.

[0161] The above second communication content, as well as the third communication content in the following embodiments, can both be the communication content transmitted during at least one of the above processes.

[0162] In this embodiment, it is possible to achieve continuous data transmission during the random access process, initial registration, attachment, NAS context establishment, or NAS security activation process, so that the first device or the second device can completely remove the RRC connected state (CONNECTED state) and complete all data transmission requirements in the non-connected state, further reducing the complexity of the device and the system.

[0163] Taking the random access process as an example below, the first device sends the first communication content to the second device in the non-connected state, including:

[0164] The first device sends Message 3 (Msg3) or Message A (MsgA) in the random access process to the second device through the MAC layer in the non-connected state, where the Msg3 or MsgA carries the first data;

[0165] The method further includes:

[0166] The first device receives, at the MAC layer in the non-connected state, a message (2Msg2) or a message B (MsgB) during the random access procedure, where the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or a Cell Radio Network Temporary Identity (C-RNTI).

[0167] Among them, the above uplink synchronization adjustment information may be uplink timing adjustment (Time Alignment, TA) for subsequent uplink timing advance.

[0168] The above C-RNTI is used for data scheduling of the first device, and the first device may always use this C-RNTI in the service transmission requirements of the first data.

[0169] As an optional implementation manner, the first communication content further includes a MAC CE or a MAC subheader, where the MAC CE or the MAC subheader is used to indicate at least one of the following:

[0170] There is subsequent data to be sent to the second device after the first data;

[0171] Buffering information.

[0172] The above first communication content further including a MAC CE or a MAC subheader (MAC subheader) may mean that in addition to the above RRC message or MAC PDU, the first communication content further includes a MAC CE or a MAC subheader.

[0173] Among them, in the case where the above MAC CE or MAC subheader does not indicate that there is subsequent data to be sent to the second device after the first data, this indication may be made by using the implementation manner introduced above.

[0174] The above buffering information may be buffering size (buffer size, BS) information.

[0175] Among them, the above MAC CE or MAC subheader may carry bit positions or LCIDs to indicate the above buffering information or that there is subsequent data to be sent to the second device after the first data. For example: the MAC CE or MAC subheader carries at least one of the following:

[0176] A first indication bit, an LCID, a second indication bit;

[0177] Among them, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0178] The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0179] The second indication bit is used to indicate cache information.

[0180] Wherein, the above first indication bit can be one or more bits, and the above second indication bit can be one or more bits.

[0181] For example: in the MAC CE or MAC sub-header, a small number of bit positions are used to indicate: for example, the values of bit positions 1 / 0 are respectively whether there is multi-data transmission, and the values of bit positions 1 / 0 are respectively whether it is the last uplink (UL) data packet indication. Another example is that 2 bit positions 00 represent single-data transmission, 01 represents UL multi-data transmission non-ending packet, 10 represents the ending packet of UL multi-data transmission, and 11 represents expecting downlink data, etc.

[0182] With different values of the LCID, it represents different meanings. For example, LCID = 0 represents a scenario of a single small data transmission, and LCID = 4 represents a scenario of a multi-data small data transmission;

[0183] Or more bit positions are used to represent buffer size information. For example, the first byte of the MAC sub-header carries the LCID or multi-data indication, and the second byte carries the subsequent buffer size information. In addition, the size of the expected data block can also be indicated, and it can also be in encoded form. For example, 3 bit positions are used to indicate the data block size, 000 represents data block size 1, 001 represents data block size 2, 010 represents data block size 3, etc. The remaining 5 bit positions are used to indicate the number of subsequent data packets. In this way, for the network side, by multiplying the data block size by the number, it can also know the subsequent data volume, and can accurately know approximately how much the size of each data packet is, which is convenient for more flexible scheduling.

[0184] In the above embodiments, since it is indicated through the MAC CE or MAC sub-header that there is subsequent data to be sent to the second device after the first data, this can make the indication of continuous data transmission more flexible, and the indication of cache information can enable the second device to better understand the cache of the first device, which is conducive to the second device being able to perform better data transmission with the first device.

[0185] As an alternative embodiment, when there is no data transmission by the first device in the resources allocated for the subsequent data, the first device skips the resources or sends an indication to the second device that the subsequent data transmission is complete.

[0186] Among them, for the resources allocated for the subsequent data, the first device no longer participates in data transmission when the subsequent data transmission is completed.

[0187] The first device skipping the resources can also be understood as the first device ignoring the resources.

[0188] The indication of the completion of the subsequent data transmission sent to the second device can be an end marker indication or a BS = 0 indication to indicate the completion of the subsequent data transmission.

[0189] By sending the indication of the completion of the subsequent data transmission to the second device, the second device can perform corresponding releases, such as releasing information such as C-RNTI, clearing timers and caches, to save resources.

[0190] In some embodiments, the resources allocated for the subsequent data can be resources allocated when the number of subsequent data is difficult to determine. For example, when the first device has only a single small piece of data during the current UL data transmission, after successful transmission, it receives downlink (DL) data, and the corresponding DL data will generate subsequent UL responses, and so on. When the UE continuously has data transmission and reception, the network side can continuously allocate uplink resources for the first device. Of course, the allocation of uplink resources needs to consider the processing delay after the first device receives the downlink data, the delay in generating uplink data, etc., and is allocated according to the recommended or reported data block size. This can achieve flexible resource allocation.

[0191] As an alternative embodiment, the MAC layer of the first device maintains one or more HARQ processes for the service transmission requirements to which the first data belongs.

[0192] Among them, the one or more HARQ processes are used to perform operations such as HARQ feedback, retransmission, or repetition for the service transmission requirements.

[0193] When the first device is an AIoT device, the MAC layer maintains one or two HARQ processes for the service transmission requirements to which the first data belongs. In this way, since only one or two HARQ processes are maintained for the service transmission requirements to which the first data belongs at the MAC layer, the complexity of data transmission can be reduced. For example, the first device is an AIoT device, and the AIoT device is simple, so 1-2 HARQ processes are sufficient.

[0194] In some embodiments, for 2 HARQ processes, they can be extended for application. For cases with slightly more data volume or concurrency, the processing of 2 HARQ processes can be performed simultaneously to further reduce latency.

[0195] As an alternative implementation, when the first communication content includes a MAC PDU, the MAC PDU includes at least one of the following:

[0196] Data type indication, subsequent data indication, cache information indication, data length indication, segmentation indication;

[0197] Among them, the data type indication is used to indicate the type of service transmission requirements to which the first data belongs;

[0198] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0199] The cache information indication is used to indicate cache information;

[0200] The data length indication is used to indicate the size of the first data carried by the MAC PDU;

[0201] The segmentation indication is used to indicate at least one of the following:

[0202] Segmented transmission, segmentation sequence number, total number of segments, end segment flag.

[0203] Among them, the type of the above service transmission requirements may be continuous small data in the IDLE state or continuous small data of the IDLE state Common Control Channel (CCCH), etc.

[0204] The above end segment flag can be used to indicate whether the data in the current communication content is an end segment.

[0205] In this implementation, since the above MAC PDU indicates the above at least one item, the second device can better understand the data that the first device needs to send, which is beneficial for the second device to better perform data transmission with the first device, thereby improving the data transmission performance between the first device and the second device.

[0206] It should be noted that in the embodiments of the present application, the implementation of the above first communication content can also be applied to the above second communication content. For example, the MAC PDU included in the above second communication content can also include at least one of the following:

[0207] Data type indication, subsequent data indication, cache information indication, data length indication, segmentation indication.

[0208] Only the values in the second communication device and the first communication content may be different.

[0209] As an alternative implementation, the method further includes:

[0210] The first device receives third communication content sent by the second device in a non-connected state. The third communication content carries third data, and the third communication content is further used to indicate:

[0211] There is subsequent data to be sent to the first device after the third data; or,

[0212] There is no subsequent data to be sent to the first device after the third data.

[0213] The first device receiving the third communication content sent by the second device in a non-connected state described above can be executed before or after step 301. For example: first send the first communication content, then receive the second communication content, and then send the third communication content, or first receive the third communication content, and then send the first communication content. Additionally, in some embodiments, the above third communication content can also be directly received, and then the above first communication content or second communication content may or may not be sent.

[0214] Among them, the above third communication content can be a reply content of the above first communication content or the first communication content is a reply content of the above third communication content. For example: the first communication content includes an RRC early transmission data request message, and the third communication content includes an RRC early transmission data response message. Another example: the first communication content includes an RRC uplink message, and the third communication content includes an RRC downlink message. Another example: the first communication content includes an uplink MAC PDU, and the third communication content includes a downlink MAC PDU, or vice versa.

[0215] Among them, indicating that there is subsequent data to be sent to the first device after the third data can enable the first device to continuously receive data, such as continuously receiving downlink data in a non-connected state to improve the transmission performance of the device. For example: after the first device receives the third communication content sent by the second device in a non-connected state, the method further includes:

[0216] The first device receives fourth communication content sent by the second device in a non-connected state. The fourth communication content carries fourth data, and the fourth communication content is further used to indicate:

[0217] There is subsequent data to be sent to the first device after the fourth data; or,

[0218] There is no subsequent data to be sent to the first device after the fourth data.

[0219] Among them, the content included in the third communication content and the fourth communication content, as well as the indication method, can refer to the indication method of the above first communication content. For example: the third communication content or the fourth communication content includes at least one of the following:

[0220] RRC messages, MAC PDUs.

[0221] The above RRC messages may include at least one of the following:

[0222] An RRC early transmission data request message, or an RRC early transmission data response message;

[0223] An RRC uplink message, or an RRC downlink message;

[0224] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0225] For another example: The third communication content includes: an RRC early transmission data request message, or an RRC early transmission data response message;

[0226] The fourth communication content includes: an RRC uplink message, or an RRC downlink message;

[0227] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0228] For another example: The third communication content or the fourth communication content indicates that there is subsequent data to be sent to the first device through at least one of the following:

[0229] The format of the communication content;

[0230] The data quantity information carried by the communication content, and the data quantity information is represented as multiple data;

[0231] The non-ending mark carried by the communication content;

[0232] The data segmentation information carried by the communication content.

[0233] Wherein, the above data segmentation information may include at least one of the following:

[0234] Segment sequence number, tail segment identifier, total number of segments.

[0235] For another example: The third communication content or the fourth communication content further includes a MAC CE or a MAC sub-header, wherein the MAC CE or the MAC sub-header is used to indicate at least one of the following:

[0236] There is subsequent data to be sent to the first device;

[0237] Buffering information.

[0238] Among them, the above MAC CE or MAC sub-header may carry at least one of the following:

[0239] A first indication bit, an LCID, a second indication bit;

[0240] Among them, the first indication bit is used to indicate that there is subsequent data to be sent to the first device;

[0241] The LCID is used to indicate that there is subsequent data to be sent to the first device;

[0242] The second indication bit is used to indicate cache information.

[0243] For another example: when the third communication content or the fourth communication content includes a MAC PDU, the MAC PDU includes at least one of the following:

[0244] A data type indication, a subsequent data indication, a cache information indication, a data length indication, a segmentation indication;

[0245] Among them, the data type indication is used to indicate the type of service transmission requirement to which the data belongs;

[0246] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device;

[0247] The cache information indication is used to indicate cache information;

[0248] The data length indication is used to indicate the size of the data carried by the MAC PDU;

[0249] The segmentation indication is used to indicate at least one of the following:

[0250] Segmented transmission, segmented sequence number, total number of segments, end segment flag.

[0251] In an embodiment of the present application, a first device sends a first communication content to a second device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data. This can realize data transmission in a non-connected state to improve the transmission performance of the device. Moreover, since the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data, this can support multiple data transmissions and further improve the transmission performance of the device.

[0252] Please refer to Figure 4 , Figure 4 which is a flowchart of another data transmission method provided by an embodiment of the present application. As Figure 4 shown, it includes the following steps:

[0253] Step 401: The second device receives the first communication content sent by the first device in the non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0254] Optionally, the first communication content includes at least one of the following:

[0255] RRC message, MAC PDU.

[0256] Optionally, the RRC message includes at least one of the following:

[0257] RRC early transmission data request message, or RRC early transmission data response message;

[0258] RRC uplink message, or RRC downlink message;

[0259] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0260] Optionally, after the second device receives the first communication content sent by the first device in the non-connected state, the method further includes:

[0261] The second device receives the second communication content sent by the first device in the non-connected state. The second communication content carries second data, and the second communication content is further used to indicate:

[0262] There is subsequent data to be sent to the second device after the second data; or,

[0263] There is no subsequent data to be sent to the second device after the second data.

[0264] Optionally, the first communication content includes: RRC early transmission data request message, or RRC early transmission data response message;

[0265] The second communication content includes: RRC uplink message, or RRC downlink message;

[0266] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0267] Optionally, the first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following:

[0268] The format of the first communication content;

[0269] The number of data carried by the first communication content, and the number of data information is represented as multiple data;

[0270] The non-ending flag carried by the first communication content;

[0271] The data segmentation information carried by the first communication content.

[0272] Optionally, the data segmentation information includes at least one of the following:

[0273] Segment sequence number, tail segment identifier, total number of segments, and the value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

[0274] Optionally, the second device receives the first communication content sent by the first device in a non-connected state, including:

[0275] The second device receives message 3 (Msg3) or message A (MsgA) in the random access process sent by the first device in a non-connected state, where the Msg3 or MsgA carries the first data;

[0276] The method further includes:

[0277] The second device sends message 2 (Msg2) or message B (MsgB) in the random access process to the first device, and the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or cell radio network temporary identifier (C-RNTI).

[0278] Optionally, the first communication content further includes a MAC control element (CE) or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following:

[0279] There is subsequent data to be sent to the second device after the first data;

[0280] Buffering information.

[0281] Optionally, the MAC CE or MAC sub-header carries at least one of the following:

[0282] A first indication bit, a logical channel ID (LCID), a second indication bit;

[0283] Wherein, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0284] The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0285] The second indication bit is used to indicate caching information.

[0286] Optionally, when the first communication content includes a MAC PDU, the MAC PDU includes at least one of the following:

[0287] Data type indication, subsequent data indication, caching information indication, data length indication, segmentation indication;

[0288] Among them, the data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

[0289] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0290] The caching information indication is used to indicate caching information;

[0291] The data length indication is used to indicate the size of the first data carried by the MAC PDU;

[0292] The segmentation indication is used to indicate at least one of the following:

[0293] Segmented transmission, segmentation sequence number, total number of segments, end segment flag.

[0294] Optionally, the method further includes:

[0295] The second device sends third communication content to the first device in a non-connected state. The third communication content carries third data, and the third communication content is further used to indicate:

[0296] There is subsequent data to be sent to the first device after the third data; or,

[0297] There is no subsequent data to be sent to the first device after the third data.

[0298] Optionally, the first communication content is communication content received during at least one of the following processes:

[0299] Initial registration, attachment, non-access stratum NAS context establishment, NAS security activation.

[0300] It should be noted that this embodiment, as the implementation manner of the second device corresponding to the embodiment shown in Figure 3 The specific implementation manner can refer to the relevant description of the embodiment shown in Figure 3 For the sake of avoiding repeated description, this embodiment will not be elaborated here.

[0301] The following uses the first device as an AIoT device to illustrate the method provided by the embodiments of the present application through multiple embodiments:

[0302] Embodiment 1:

[0303] In the embodiments of the present application, a new message (i.e., a message newly defined in the embodiments of the present application, such as the RRC message in the above embodiments) is used for illustration. Specifically, for the new RRC message, the RRC Continuous Data Request and RRC Continuous Data Response messages are used for illustration. Other message names are not excluded, as long as they are different from the message names defined in the protocol. For the RRC layer, it can operate based on at least one of the following principles:

[0304] When there is only one data packet in the current high-layer data transmission, if it is determined that the conditions for single-time EDT / SDT transmission are met, such as the size of the data packet being lower than the configured threshold, or the link quality meeting the threshold, etc., the RRC layer can carry the current independent data packet using the existing message RRC Early Data Request message. Otherwise, for example, when there are more than 1 data packet, or the data packet size is large and needs to be segmented for transmission, etc., or the link quality does not meet the threshold and multiple attempts may be required, etc., the new message RRC Continuous Data Request can be used to carry the high-layer data packets sequentially, or in segments, etc.;

[0305] When the high-layer data transmission requirement in this time can be clearly indicated to the RRC layer and there is a possibility of subsequent continuous data, such as the first UL data, followed by the first downlink data, and then the second UL data, etc., this has exceeded the existing transmission scale of at most one uplink data plus one downlink data. Therefore, the new message RRC Continuous Data Request can be used to carry the high-layer data packets sequentially. Otherwise, if it cannot be determined or there is no clear indication, for the only first UL data, the existing RRC Early Data Request message can still be selected for carrying;

[0306] Since the AIoT device is a new type of device and its service requirements are also very different from those of general terminals, when the AIoT device selects to perform uplink small data transmission, it can directly select the new message RRC Continuous Data Request to carry the high-layer data packets sequentially without any additional judgment, and as for whether there is subsequent continuous data, it is indicated by other means;

[0307] In the RRC layer, if it is possible to determine, based on the data that has arrived, that this is a multi-packet transmission process, or that a large data packet needs to be segmented for transmission, or even if only the first small piece of data has arrived, but based on the service type or indication, it is known that this is a process with subsequent series of transmissions, or it is impossible to determine whether there are subsequent series of transmissions, then explicit or implicit indications of subsequent data can be carried in the data packets in the RRC layer, including but not limited to:

[0308] For example, selecting the new message format itself already indicates non-one-time transmission, and when there is no further explicit end marker identification, it implies that there is subsequent data;

[0309] For example, if N small pieces of data have arrived in the data that has arrived, or it can be initially judged based on the type of service initiated this time that there are a total of N small pieces of data, then the number information of the N small pieces of data, or non-end marker identification can be explicitly informed, indicating N - 1 subsequent data, or indicating that the subsequent data has not ended;

[0310] For example, in the case where the data block that has arrived is large and needs to be segmented, the segmented data itself needs to carry information such as sequence numbers, non-tail segment identification, or total number of segments indication for recombination needs, indicating N - 1 subsequent segmented data, or indicating that the subsequent segmented data has not ended.

[0311] Correspondingly, for the downlink, a new message format, RRC Continuous DataResponse, can also be adopted to carry the corresponding DL data in the scenario of continuous small data transmission, and the Endmarker or release identification is extended in the RRC message. When this identification is not carried, it means that the configurations on the terminal side can continue to apply. When the network side carries the End marker or release identification, it means explicit release.

[0312] Next, it is the processing of the RLC layer. For AIoT devices, if all are small data transmissions, the RLC layer is not necessarily mandatory. The RLC TM method can be directly used for transparent transmission, that is, without the participation of the RLC layer in the transmission. However, if data segmentation is involved (although the RRC layer can also segment but the efficiency is not as high as that of the RLC layer, so the two can be considered as an alternative), or if there are requirements for data reliability and continuity, then the simplified methods of RLC UM or RLC AM can be considered for processing. If the RLC layer is involved, at least one of the following can be considered:

[0313] The functions of the RLC layer in UM / AM mode, such as segmentation, ARQ, or in-sequence delivery, etc., are all carried out by using the sequential SN method. For an AIoT device in the IDLE state, when communicating with the peer network side or Reader, this embodiment can synchronize the initialization and assignment operations of the SN. A feasible way is that when the AIoT device initiates a new small data transmission, the initial value of the SN of the RLC entity starts from 0, that is, the SN of the first data packet is 0, the SN of the second data packet is 1, and so on incrementally. Similarly, when the AIoT device is the receiving end of this transmission, the initial value of the SN variable of the receiving entity also starts from 0, that is, the SN of the next data packet expected to be received is 0. On the contrary, during a new small data transmission process between the network side or the Reader side and an AIoT device, the initial variable of the SN of the RLC receiving end also starts from 0, that is, the SN of the next data packet expected to be received is 0, including the first DL data packet sent by the network side as the sending end during this small data transmission also has SN = 0, and subsequent ones incrementally;

[0314] When the AIoT device and the network side / Reader side complete all transmissions of this small data, the RLC entity is deleted or reset or cleared until there is a new demand for small data transmission next time, and then starts from initializing the SN variable to 0 again;

[0315] Since the SN of the RLC layer is only used for data reorganization, ARQ, sorting and other operations and does not involve secure input, there is no need for additional requirements such as non-repetition. Moreover, during a small data transmission process, it is restricted that the AIoT device cannot change the serving cell. Otherwise, the unfinished process is directly ended and a new small data transmission process starts in the new cell. Therefore, there is no need for cross-cell processing either;

[0316] It can also support multiple different small data transmission processes (which can also be called service transmission requirements) at the same time. For example, when the LCID (logical channel Identification) is 0, it corresponds to the RLC TM mode, that is, the RLC layer functions are not required and can be directly delivered by the MAC to the RRC layer. When the LCID is 1, it corresponds to a transmission in the RLC UM mode. Both ends of the RLC entity or the RLC sending end entity and the receiving end entity can maintain the SN variable starting from 0 until the end of this small data transmission; another LCID is 2, which can also correspond to a transmission in the RLC AM mode. Both ends of the RLC entity or the RLC sending end entity and the receiving end entity can maintain the SN variable starting from 0 until the end of this small data transmission. The advantage of this is that multiple small data transmission processes can be carried out simultaneously (that is, multiple service transmission requirements in the above embodiments are carried out simultaneously), without waiting for the previous one to end before starting the next one;

[0317] The biggest difference between the above simultaneous mode and traditional terminals is that traditional terminals establish multiple DRBs and multiple RLC entities for transmission simultaneously, but the establishment process requires configuration through RRC dedicated signaling. The terminal needs to establish an RRC connection, activate AS layer security, etc., and establish them as needed. In order to avoid entering the connected state, AIoT devices cannot use dedicated signaling configuration. Therefore, simple agreements can be made in the protocol, such as LCID 0 for data transmission type and RLC parameters, LCID 1 for data transmission type and RLC parameters, etc.; AIoT can select as needed according to requirements. After the previous small data transmission ends and LCID1 is released, when initiating a small data transmission with a similar requirement next time, LCID1 can be used again, and it can be released and used in a cycle;

[0318] Of course, for the sake of simplicity in design and operation, it can be stipulated that an AIoT device only initiates one small data transmission process at a time. After the previous one ends, the next one starts. In this way, only one LCID is activated and used each time, and it can still be used in a cycle;

[0319] For the MAC layer, the MAC layer can perform at least one of the following:

[0320] The MAC layer is responsible for implementing the RACH process, which can support two-step random access (2-step RACH) and four-step random access (4-step RACH). The first small data packet is sent to the network in Msg3 or MsgA, and uplink synchronization TA and C-RNTI are obtained during the RACH process for subsequent data scheduling and transmission;

[0321] Msg4 or MsgB of the RACH process can complete contention resolution, which means that the RACH process of the AIoT device is successful. The TA and C-RNTI obtained in Msg2 and MsgB of the RACH process are specific to this device. This device can use TA as the subsequent uplink timing advance, and C-RNTI can be used for subsequent data scheduling; for example, after the network side completes the RACH process, it can use C-RNTI to schedule the first downlink data. This downlink data can be a response to the uplink data in the RACH process or an independent downlink data. After that, this C-RNTI can also be used for subsequent uplink and downlink UE-specific data scheduling until it is implicitly or explicitly released, and then this small data transmission ends;

[0322] In addition, the MAC layer can also further indicate subsequent data, cache reporting, End marker, end indication, etc. through MAC CE or the bit in the MAC subheader, and the following methods can be included;

[0323] In the MAC subheader or MAC CE, a small number of bits are used to display indications. For example, the values of bit 1 / 0 represent whether it is multi-data transmission or not, and the values of bit 1 / 0 represent whether it is the last uplink (UL) data packet indication. Another example is that 2 bits 00 represent single-data transmission, 01 represents a non-ending UL multi-data transmission packet, 10 represents the ending packet of UL multi-data transmission, and 11 represents waiting for downlink data, etc.;

[0324] Or different values of LCID represent different meanings. For example, LCID = 0 represents a scenario of a single small-data transmission, and LCID = 4 represents a scenario of multi-data small-data transmission;

[0325] Or more bits are used to represent buffer size information. For example, the first byte of the MAC subheader carries LCID or multi-data indication, and the second byte carries subsequent buffer size information. And the encoding of the buffer size must be an independent table and cannot use the table of ordinary UEs because the data volume of ordinary UEs is large. A buffer size table dedicated to AIoT needs to be specially customized. In addition, the size of the expected data block can also be indicated in encoded form. For example, 3 bits are used to indicate the data block size, 000 represents data block size 1, 001 represents data block size 2, 010 represents data block size 3..., and the remaining 5 bits are used to indicate the number of subsequent data packets. In this way, for the network side, by multiplying the data block size by the number, it can also know the subsequent data volume and can accurately know the approximate size of each data packet, which is convenient for more flexible scheduling;

[0326] Particularly, when it is difficult to judge the number of subsequent data packets. For example, when an AIoT device has only a single small data during the current UL data transmission, after the transmission is successful, it receives DL data, and the corresponding DL data will generate subsequent UL responses, and so on. When the AIoT device continuously has data sending and receiving, the network side can continuously allocate uplink resources for the AIoT device. Of course, the allocation of uplink resources needs to consider the processing delay after the AIoT device receives downlink data, the delay in generating uplink data, etc., and allocate according to the recommended or reported data block size;

[0327] When there is no more data to be transmitted in the UL resources allocated by the network, the AIoT device can skip / ignore the uplink resources, or explicitly indicate through the End marker or the MAC indication of BS=0 to inform the network side that there is no more uplink. Then the network side can know that the small data transmission process is over and can release it explicitly or implicitly. Implicit release means that after the UE skips the uplink resources or indicates the end to the network side, the UE and the network side release their stored C-RNTI and other information respectively, clear the timers and caches, etc., and reset to the initial state. Explicit release means that the network further informs the AIoT device to release this process through an explicit MAC CE or DCI or even RRC.

[0328] After the MAC layer successfully obtains the C-RNTI during the RACH process, it needs to continuously monitor the scheduling of this C-RNTI, obtain the uplink and downlink resource scheduling, and perform data transmission and reception until the release is successful, then clear the C-RNTI and stop listening.

[0329] During the process of the AIoT device using its own C-RNTI for dedicated scheduling, there are also some abnormal situations that will cause this process to end prematurely. For example, due to the movement of the AIoT device or network coverage problems, the link quality of the AIoT device is poor. For example, when the RSRP is lower than a certain threshold, or when the number of consecutive failures meets the threshold, etc. At this time, the AIoT device can release the C-RNTI and other timers, status information, etc. by itself, return to the IDLE state, and then reselect the cell again according to the need and initiate again. For the network side, it can also judge based on the link quality, or when there is no response from the AIoT device side after the C-RNTI scheduling accumulates for a period of time or a certain number of times, it is judged that the AIoT device has released itself, and the network side can also release accordingly.

[0330] The MAC layer also maintains the processing of the HARQ process. Since the AIoT device is simple, 1-2 HARQ processes are sufficient. One HARQ process can already meet the needs of HARQ feedback / retransmission / repetition and other operations. Two HARQ processes can be further extended for applications. For slightly more data volume or concurrent situations, the processing of 2 HARQ processes can be carried out simultaneously to further reduce the latency, but there are requirements for the capabilities of the AIoT device and it can be an optional configuration.

[0331] Specifically, in this embodiment, the problem of continuous transmission of high-layer data is solved. During a period when the AIoT device link is stable and does not involve handover mobility, continuous data transceiver can be performed. Therefore, from the basic processes such as the initial registration, attach, NAS context establishment, and NAS security activation of the AIoT device, this process can also be directly used. In this way, the AIoT device can completely remove the RRC connected state and complete all small data transmission requirements in the IDLE state, further reducing the complexity of the device and the system.

[0332] Embodiment 2:

[0333] This embodiment introduces a method of using a MAC PDU (such as the MAC PDU newly defined in the embodiment of the present application) to carry high-layer small data, further simplifying the processing flow, reducing the overhead, and obtaining better system efficiency and improvement in device minimization.

[0334] Since there is no RRC connection establishment and AS layer security activation operation during the continuous small data transmission process in the pure IDLE state, the real role of the RRC layer is only data encapsulation and data routing. Then, if this embodiment can design a MAC PDU to replace this encapsulation and routing function, more hierarchical operations will be simplified.

[0335] Design a MAC PDU, including at least one or a combination of the following information:

[0336] Data type indication. This field is mainly used to describe the type of this MAC PDU. If considering compatibility with the definitions already in the protocol, the definition of LCID can be adopted or reused. For the continuous small data transmission of AIoT, a dedicated LCID can be specified or configured in the protocol to carry the high-layer continuous data of IDLE devices. Of course, since AIoT devices are likely to access different cell / carrier / frequency resources from ordinary terminals, AIoT devices can also be specifically designed with lower bit overhead to distinguish different data types for various transmission scenarios of AIoT devices, such as distinguishing single small data in the IDLE state, continuous small data in the IDLE state, (continuous) CCCH small data in the IDLE state, small data of different bearers / logical channels in the INACTIVE state, and small data of different bearers / logical channels in the CONNECTED state, etc.

[0337] Is there subsequent data or cache size indication? This indication information is mainly used to indicate whether this is a single small data, multiple small data, continuous small data, whether it is the last packet, the existing (subsequent) cache size, the existing (subsequent) number of data packets, the expected data packet size, the expected resource block size, etc., either alone or in combination. This is to facilitate the network side to better judge the data arrival of the AIoT device, so as to provide scheduling resources that better meet the requirements;

[0338] Length Indicator (LI) of the data block. This field is mainly used to indicate the size of the upper-layer payload contained in the MAC PDU, usually in bytes. For small data, a large size is not required. Of course, this field is not mandatory or necessarily present. When the service is relatively simple and good data block shaping can be performed, that is, the data size is agreed upon, the LI indication can be omitted, and the packet assembly indication can be simplified through the agreement between the terminal and the base station;

[0339] The payload part of the data block. This part is the upper-layer valid data (such as the first data and the second data above), usually arranged in whole bytes;

[0340] Specifically, if the segmentation function needs to be supported to be compatible with the scenario where the upper-layer data is larger than the resource block size, the segmentation function also needs to be supported, and fields such as segmentation indication, segmentation sequence number, total number of segments, and tail segment mark are introduced to support segmented transmission;

[0341] In this embodiment of the MAC PDU, since the packet assembly and processing of the RRC layer are omitted, and the RLC layer can also be omitted because it is above the MAC layer, the number of layers is reduced and the efficiency is increased.

[0342] As listed in Embodiment 1, the content regarding the processing part of the MAC layer, which is the content regarding the transmission control of the MAC layer other than packet assembly, basically also applies to this example and will not be elaborated here.

[0343] Embodiment 3:

[0344] This embodiment mainly describes the enhancement and improvement based on the defined message types and transmission mechanisms in the protocol to achieve continuous transmission of small data.

[0345] For the RRC layer, it can operate based on at least one of the following principles:

[0346] When there is only one data packet in the current high-layer data transmission and it is determined that the conditions for single-shot EDT / SDT transmission are met, such as the size of the data packet being lower than the configured threshold, or the link quality meeting the threshold, etc., the RRC layer can carry the current independent data packet using the existing message RRC Early Data Request message. Otherwise, for example, when there are more than one data packet, or the data packet size is large and needs to be segmented for transmission, etc., or the link quality does not meet the threshold and multiple attempts may be required, the message RRC Early Data Request can also be used to carry the high-layer data packets sequentially, or in segments, etc. Specifically, special RAI indications are added by the RRC layer or special RAI / BSR / End marker, etc. indications of the MAC layer are used to distinguish from the case of a single data packet, informing the network side that there is subsequent data and it cannot be released immediately;

[0347] When the high-layer data transmission requirements in this instance can be clearly indicated to the RRC layer and there is a possibility of subsequent continuous data, such as the first UL data, followed by the first DL data, and then followed by the second UL data, etc., which has exceeded the existing transmission scale of at most one UL data plus one DL data, the message RRC Early Data Request can be used to carry the high-layer data packets sequentially;

[0348] Since AIoT devices are a new type of device and their service requirements are also very different from those of general terminals, when an AIoT device selects to perform uplink small data transmission, it can directly use the message RRC Early Data Request to carry the high-layer data packets sequentially without any additional judgment. As for whether there is subsequent data, it is indicated by other means, or the convention between the AIoT device and the network side at this time is that subsequent data is default, and it needs to wait for a clear end marker / RAI / BSR indication to end;

[0349] In the RRC layer, if it can be determined from the data that has arrived that this is a multi-packet transmission process, or a large data packet needs to be segmented for transmission, or even if only the first small piece of data has arrived, but based on the service type or indication, it is known that this is a process with subsequent series of transmissions, or it is impossible to determine whether there is a subsequent series of transmissions, then explicit or implicit indications of subsequent data can be carried in the data packets of the RRC layer, including but not limited to:

[0350] For example, although the existing message format is selected, special agreements are made for the AIoT scenario, which is defaulted to non-one-time transmission, and when there is no further clear end marker identification, it indicates that there is subsequent data;

[0351] For example, in the arrived data, if N small data have arrived, or based on the type of service initiated this time, it can be preliminarily judged that there are a total of N small data, then the number information of the N small data, or the non-end marker identification can be explicitly informed to indicate N-1 subsequent data, or indicate that the subsequent data has not ended;

[0352] For example, in the case where the arrived data block is large and needs to be segmented, the segmented data itself needs to carry sequence numbers, non-tail segment identifiers, or total segment number indications, etc. due to the need for recombination, to indicate N-1 subsequent segmented data, or indicate that the subsequent segmented data has not ended;

[0353] Of course, it is not excluded that RRC Early Data Request and RRC Continuous Data Request are used in combination. For example, when there is only one data in the cache currently, it is encapsulated with an RRC Early Data Request message. However, after the network side receives it, it can also configure continuously for the AIoT device unless an explicit single data or end indication is received. When there are multiple data to be transmitted in the cache, use RRC Continuous Data Request, which also explicitly informs the network side to a certain extent that there must be subsequent data.

[0354] Correspondingly, for the downlink, the message format RRC Early Data Complete can also be adopted to carry the corresponding DL data in the scenario of continuous small data transmission, and an End marker or release identifier is extended in the RRC message. When this identifier is not carried, it means that the configurations on the AIoT device side can continue to be used. When the network side carries an Endmarker or release identifier, it means explicit release;

[0355] Or, for the downlink, the message formats RRC Early Data Request and RRC Continuous Data Request can also be used in combination to carry the corresponding DL data in the scenario of continuous small data transmission. When using RRC Continuous Data Request, the AIoT device can retain the configuration and continue to use it. When using RRC Early Data Request, it means explicit release;

[0356] In this embodiment, since the encapsulation of high-layer data is performed at the RRC layer, the processing of the RLC layer and the MAC layer in Embodiment 1 is still applicable and will not be elaborated here.

[0357] In the above embodiments, a multi-data transmission method for an AIoT device is given, enabling the AIoT device to perform multi-data transmission without state transition, ensuring the feasibility and efficiency of the transmission, expanding the coverage, reducing the complexity and power consumption of the AIoT device while guaranteeing the transmission effect, and improving the system efficiency.

[0358] In addition, for the minimalist and low-power design of AIoT devices, devices in the non-connected state can perform multi-data transmission, maintain on-demand sorting between data, obtain basic uplink synchronization and C-RNTI allocation in a manner similar to UL-SDT / EDT, and explicitly report the subsequent data volume to obtain continuous scheduling to complete multiple data transmissions.

[0359] In the embodiments of the present application, the execution subject of the provided data transmission method can be a data transmission device. In the embodiments of the present application, taking the data transmission device executing the data transmission method as an example, the data transmission device provided by the embodiments of the present application is described.

[0360] Please refer to Figure 5 , Figure 5 which is a structural diagram of a data transmission device provided by the embodiments of the present application. As Figure 5 shown, the data transmission device 500 includes:

[0361] A first sending module 501, configured to send first communication content to a second device in the non-connected state, where the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0362] Optionally, the first communication content includes at least one of the following:

[0363] Radio Resource Control (RRC) message, Media Access Control (MAC) protocol data unit (PDU).

[0364] Optionally, the RRC message includes at least one of the following:

[0365] RRC early transmission data request message, or RRC early transmission data response message;

[0366] RRC uplink message, or RRC downlink message;

[0367] wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0368] Optionally, the device further includes:

[0369] A second sending module, configured to send second communication content to the second device in a non-connected state, where the second communication content carries second data, and the second communication content is further used to indicate:

[0370] There is subsequent data to be sent to the second device after the second data; or,

[0371] There is no subsequent data to be sent to the second device after the second data.

[0372] Optionally, the first communication content includes: an RRC early transmission data request message, or an RRC early transmission data response message;

[0373] The second communication content includes: an RRC uplink message, or an RRC downlink message;

[0374] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0375] Optionally, the first sending module 501 is configured to send the first communication content to the second device in a non-connected state when the first device determines that a target condition is met, where the target condition includes at least one of the following:

[0376] There are multiple pieces of high-layer data;

[0377] The high-layer data needs to be segmented for transmission;

[0378] There is only one piece of high-layer data, and the size of the one piece of data is greater than a preset threshold;

[0379] The link quality is a preset quality;

[0380] The RRC layer or the MAC layer receives an indication of the possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication of continuous data transmission.

[0381] Optionally, the apparatus further includes:

[0382] A third sending module, configured to send third communication content to the second device in a non-connected state when the first device determines that the target condition is not met, where the third communication content carries third data, and the data transmission process corresponding to the third communication content can only transmit data once in the uplink or the downlink.

[0383] Optionally, the sending the first communication content to the second device in a non-connected state includes:

[0384] When the target judgment result is obtained at the RRC layer of the first device, the first communication content is sent to the second device in the non-connected state, where the target judgment result includes at least one of the following:

[0385] Based on the data that has reached the RRC layer, it is judged that the service transmission requirement is for multi-data transmission;

[0386] Based on the data that has reached the RRC layer, it is judged that segmented transmission is required;

[0387] Based on the service type or the indication received by the RRC layer, it is judged that there is subsequent data transmission;

[0388] Based on the service type or the indication received by the RRC layer, it is impossible to judge whether there is subsequent data transmission.

[0389] Optionally, the first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following:

[0390] The format of the first communication content;

[0391] The data number information carried by the first communication content, and the data number information indicates multiple data;

[0392] The non-ending mark carried by the first communication content;

[0393] The data segmentation information carried by the first communication content.

[0394] Optionally, the data segmentation information includes at least one of the following:

[0395] Segment sequence number, tail segment identifier, total number of segments, and the value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

[0396] Optionally, the radio link control (RLC) layer of the first device performs at least one of the following transmission processes:

[0397] Transmit the first communication content in the transparent mode (TM), acknowledged mode (AM), or unacknowledged mode (UM);

[0398] Perform segmented transmission on the first data carried by the first communication content;

[0399] Multiple service transmission requirements are carried out simultaneously, and the multiple service transmission requirements include the service transmission requirement to which the first data belongs.

[0400] Optionally, when the RLC layer adopts the AM or UM transmission mode, the RLC entity of the RLC layer transfers the first data and subsequent data of the first data in the order of sequence number SN, where the initial value of SN is 0.

[0401] Optionally, when the service transmission requirements corresponding to the RLC entity are completed, perform one of the following operations on the RLC entity:

[0402] Delete, reset, clear.

[0403] Optionally, when multiple service transmission requirements are carried out simultaneously, different service transmission requirements adopt different logical channel identifiers LCID, and the transmission configurations adopted by different service transmission requirements are protocol agreements or pre-configurations.

[0404] Optionally, sending the first communication content to the second device in the non-connected state includes:

[0405] Sending message 3 Msg3 or message A MsgA in the random access process to the second device through the MAC layer in the non-connected state, where the Msg3 or MsgA carries the first data;

[0406] The device further includes:

[0407] A second receiving module, configured to receive message 2 Msg2 or message B MsgB in the random access process through the MAC layer in the non-connected state, where the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or cell radio network temporary identifier C-RNTI.

[0408] Optionally, the first communication content further includes a MAC control element CE or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following:

[0409] There is subsequent data to be sent to the second device after the first data;

[0410] Buffering information.

[0411] Optionally, the MAC CE or MAC sub-header carries at least one of the following:

[0412] A first indication bit, LCID, a second indication bit;

[0413] Wherein, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0414] The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0415] The second indication bit is used to indicate caching information.

[0416] Optionally, when there is no more data transmission by the first device in the resources allocated for the subsequent data, the first device skips the resources or sends an indication to the second device that the subsequent data transmission is complete.

[0417] Optionally, the MAC layer of the first device maintains one or more Hybrid Automatic Repeat reQuest (HARQ) processes for the service transmission requirements to which the first data belongs.

[0418] Optionally, when the first communication content includes a MAC PDU, the MAC PDU includes at least one of the following:

[0419] Data type indication, subsequent data indication, caching information indication, data length indication, segmentation indication;

[0420] Among them, the data type indication is used to indicate the type of the service transmission requirements to which the first data belongs;

[0421] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0422] The caching information indication is used to indicate caching information;

[0423] The data length indication is used to indicate the size of the first data carried by the MAC PDU;

[0424] The segmentation indication is used to indicate at least one of the following:

[0425] Segmented transmission, segment sequence number, total number of segments, end segment marker.

[0426] Optionally, the device further includes:

[0427] A first receiving module, configured to receive third communication content sent by a second device in a non-connected state, where the third communication content carries third data, and the third communication content is further used to indicate:

[0428] There is subsequent data to be sent to the first device after the third data; or,

[0429] There is no subsequent data to be sent to the first device after the third data.

[0430] Optionally, the first communication content is communication content sent during at least one of the following processes:

[0431] Initial registration, attachment, non-access stratum (NAS) context establishment, NAS security activation.

[0432] The above data transmission device can improve the transmission performance of the device.

[0433] In the embodiments of the present application, the data transmission device may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. For example: the electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of terminals listed in the embodiments of the present application, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0434] The data transmission device provided in the embodiments of the present application can implement Figure 3 each process implemented by the method embodiment shown, and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0435] Please refer to Figure 6 , Figure 6 is a structural diagram of another data transmission device provided in the embodiments of the present application. As Figure 6 shown, the data transmission device 600 includes:

[0436] A first receiving module 601, configured to receive first communication content sent by a first device in a non-connected state, where the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0437] Optionally, the first communication content includes at least one of the following:

[0438] RRC message, MAC PDU.

[0439] Optionally, the RRC message includes at least one of the following:

[0440] RRC early transmission data request message, or RRC early transmission data response message;

[0441] RRC uplink message, or RRC downlink message;

[0442] Among them, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0443] Optionally, the device further includes:

[0444] A second receiving module, configured to receive second communication content sent by a first device in a non-connected state, where the second communication content carries second data, and the second communication content is further used to indicate:

[0445] There is subsequent data to be sent to the second device after the second data; or,

[0446] There is no subsequent data to be sent to the second device after the second data.

[0447] Optionally, the first communication content includes: an RRC early transmission data request message, or an RRC early transmission data response message;

[0448] The second communication content includes: an RRC uplink message, or an RRC downlink message;

[0449] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0450] Optionally, the first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following:

[0451] The format of the first communication content;

[0452] The data number information carried by the first communication content, where the data number information represents multiple data;

[0453] The non-ending mark carried by the first communication content;

[0454] The data segmentation information carried by the first communication content.

[0455] Optionally, the data segmentation information includes at least one of the following:

[0456] Segment sequence number, tail segment identifier, total number of segments, and the value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

[0457] Optionally, receiving the first communication content sent by the first device in a non-connected state includes:

[0458] Receiving message 3 (Msg3) or message A (MsgA) in the random access process sent by the first device in a non-connected state, where the Msg3 or MsgA carries the first data;

[0459] The apparatus further includes:

[0460] A second transmission module, configured to send Message 2 (Msg2) or Message B (MsgB) in a random access procedure to the first device, where the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or a cell radio network temporary identifier (C-RNTI).

[0461] Optionally, the first communication content further includes a MAC control element (CE) or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following:

[0462] There is subsequent data to be sent to the second device after the first data;

[0463] Buffering information.

[0464] Optionally, the MAC CE or MAC sub-header carries at least one of the following:

[0465] A first indication bit, a logical channel ID (LCID), a second indication bit;

[0466] Wherein, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0467] The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0468] The second indication bit is used to indicate buffering information.

[0469] Optionally, when the first communication content includes a MAC protocol data unit (PDU), the MAC PDU includes at least one of the following:

[0470] A data type indication, a subsequent data indication, a buffering information indication, a data length indication, a segmentation indication;

[0471] Wherein, the data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

[0472] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0473] The buffering information indication is used to indicate buffering information;

[0474] The data length indication is used to indicate the size of the first data carried by the MAC PDU;

[0475] The segmentation indication is used to indicate at least one of the following:

[0476] Segmented transmission, segmentation sequence number, total number of segments, tail segment flag.

[0477] Optionally, the device further includes:

[0478] A first sending module, configured to send third communication content to the first device in a non-connected state, where the third communication content carries third data, and the third communication content is further used to indicate:

[0479] There is subsequent data to be sent to the first device after the third data; or,

[0480] There is no subsequent data to be sent to the first device after the third data.

[0481] Optionally, the first communication content is the communication content received during at least one of the following processes:

[0482] Initial registration, attachment, non-access stratum (NAS) context establishment, NAS security activation.

[0483] The above data transmission device can improve the transmission performance of the device.

[0484] The data transmission device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or a network-side device.

[0485] The data transmission device provided in the embodiments of the present application can implement Figure 4 each process implemented by the method embodiment shown and achieve the same technical effect. To avoid repetition, details are not described here again.

[0486] Optionally, as Figure 7 shown, the embodiments of the present application further provide a communication device 700, including a processor 701 and a memory 702. A program or instruction that can run on the processor 701 is stored on the memory 702. For example, when the communication device 700 is the first device, when the program or instruction is executed by the processor 701, each step of the above data transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, details are not described here again.

[0487] The embodiments of the present application further provide a communication device, including a processor and a communication interface. The communication interface is configured to send first communication content to a second device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data. The communication device embodiment corresponds to the above data transmission method embodiment. Each implementation process and implementation manner of the above method embodiment can be applied to the communication device embodiment, and the same technical effect can be achieved.

[0488] Specifically, Figure 8Schematic diagram of the hardware structure of a device according to an embodiment of the present application.

[0489] The device 800 includes, but is not limited to, at least some components such as a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, and a processor 810.

[0490] Those skilled in the art can understand that the device 800 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 810 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 8 The device structure shown does not limit the device. The device may include more or fewer components than shown, or combine some components, or have different component arrangements, which will not be elaborated here.

[0491] It should be understood that in the embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042. The graphics processing unit 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. The other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0492] In the embodiment of the present application, after the radio frequency unit 801 receives downlink data from a network-side device, it can be transmitted to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network-side device. Generally, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0493] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include volatile memory or non-volatile memory, or the memory 809 may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), and a direct rambus RAM (DRRAM). The memory 809 in the embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

[0494] The processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 810.

[0495] In this embodiment, the above device is a first device, and specifically, the first device is taken as an example of a terminal for illustration:

[0496] The radio frequency unit 801 is used to send first communication content to a second device in a non-connected state. The first communication content carries first data, and the first communication content is also used to indicate that there is subsequent data to be sent to the second device after the first data.

[0497] Optionally, the first communication content includes at least one of the following:

[0498] Radio Resource Control (RRC) message, Media Access Control (MAC) protocol data unit (PDU).

[0499] Optionally, the RRC message includes at least one of the following:

[0500] RRC early transmission data request message, or RRC early transmission data response message;

[0501] RRC uplink message, or RRC downlink message;

[0502] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0503] Optionally, the radio frequency unit 801 is further configured to:

[0504] Send second communication content to the second device in the non-connected state, where the second communication content carries second data, and the second communication content is further used to indicate:

[0505] There is subsequent data to be sent to the second device after the second data; or,

[0506] There is no subsequent data to be sent to the second device after the second data.

[0507] Optionally, the first communication content includes: RRC early transmission data request message, or RRC early transmission data response message;

[0508] The second communication content includes: RRC uplink message, or RRC downlink message;

[0509] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0510] Optionally, sending the first communication content to the second device in the non-connected state includes:

[0511] When the first device determines that the target condition is met, send the first communication content to the second device in the non-connected state, where the target condition includes at least one of the following:

[0512] There are multiple pieces of high-layer data;

[0513] High-layer data needs to be segmented for transmission;

[0514] There is only one piece of high-layer data, and the size of the one piece of data is greater than a preset threshold;

[0515] The link quality is a preset quality;

[0516] The RRC layer or the MAC layer receives an indication of the possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication of continuous data transmission.

[0517] Optionally, the radio frequency unit 801 is further configured to:

[0518] In the case where the first device determines that the target condition is not satisfied, send third communication content to the second device in the non-connected state, the third communication content carries third data, and the data transmission process corresponding to the third communication content can only transmit one piece of data in the uplink or the downlink.

[0519] Optionally, the sending of the first communication content to the second device in the non-connected state includes:

[0520] In the case where the RRC layer of the first device obtains a target judgment result, send the first communication content to the second device in the non-connected state, where the target judgment result includes at least one of the following:

[0521] Based on the data that has reached the RRC layer, it is determined that the service transmission requirement is multi-data transmission;

[0522] Based on the data that has reached the RRC layer, it is determined that segmented transmission is required;

[0523] Based on the service type or the indication received by the RRC layer, it is determined that there is subsequent data transmission;

[0524] Based on the service type or the indication received by the RRC layer, it is impossible to make a judgment on whether there is subsequent data transmission.

[0525] Optionally, the first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following:

[0526] The format of the first communication content;

[0527] The number-of-data information carried by the first communication content, where the number-of-data information indicates multiple pieces of data;

[0528] The non-ending mark carried by the first communication content;

[0529] The data segmentation information carried by the first communication content.

[0530] Optionally, the data segmentation information includes at least one of the following:

[0531] Segment sequence number, tail segment identifier, and total number of segments. The value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

[0532] Optionally, the radio link control (RLC) layer of the first device performs at least one of the following transmission processes:

[0533] Transmit the first communication content using the transparent mode (TM), acknowledged mode (AM), or unacknowledged mode (UM);

[0534] Perform segmented transmission on the first data carried in the first communication content;

[0535] Multiple service transmission requirements are carried out simultaneously, and the multiple service transmission requirements include the service transmission requirement to which the first data belongs.

[0536] Optionally, in the case where the RLC layer uses the AM or UM transmission mode, the RLC entity of the RLC layer transfers the first data and the subsequent data of the first data in the order of the sequence number (SN), where the initial value of SN is 0.

[0537] Optionally, in the case where the service transmission requirement corresponding to the RLC entity is completed, perform one of the following processes on the RLC entity:

[0538] Delete, reset, or clear.

[0539] Optionally, in the case where multiple service transmission requirements are carried out simultaneously, different service transmission requirements use different logical channel identifiers (LCIDs), and the transmission configurations used by different service transmission requirements are protocol agreements or pre-configurations.

[0540] Optionally, sending the first communication content to the second device in the non-connected state includes:

[0541] In the non-connected state, send message 3 (Msg3) or message A (MsgA) in the random access procedure to the second device through the MAC layer, where Msg3 or MsgA carries the first data;

[0542] The radio frequency unit 801 is further configured to:

[0543] In the non-connected state, receive message 2 (Msg2) or message B (MsgB) in the random access procedure through the MAC layer, where Msg2 or MsgB carries at least one of the uplink synchronization adjustment information or the cell radio network temporary identifier (C-RNTI).

[0544] Optionally, the first communication content further includes a MAC control element (CE) or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following:

[0545] There is subsequent data to be sent to the second device after the first data;

[0546] Buffering information.

[0547] Optionally, the MAC CE or MAC sub - header carries at least one of the following:

[0548] A first indication bit, an LCID, a second indication bit;

[0549] Among them, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0550] The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0551] The second indication bit is used to indicate buffering information.

[0552] Optionally, in the case where there is no more data transmission by the first device in the resources allocated for the subsequent data, the first device skips the resources or sends an indication that the subsequent data transmission is complete to the second device.

[0553] Optionally, the MAC layer of the first device maintains one or more hybrid automatic repeat request (HARQ) processes for the service transmission requirements to which the first data belongs.

[0554] Optionally, in the case where the first communication content includes a MAC PDU, the MAC PDU includes at least one of the following:

[0555] Data type indication, subsequent data indication, buffering information indication, data length indication, segmentation indication;

[0556] Among them, the data type indication is used to indicate the type of the service transmission requirements to which the first data belongs;

[0557] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0558] The buffering information indication is used to indicate buffering information;

[0559] The data length indication is used to indicate the size of the first data carried by the MAC PDU;

[0560] The segmentation indication is used to indicate at least one of the following:

[0561] Segmented transmission, segment sequence number, total number of segments, end - segment flag.

[0562] Optionally, the radio frequency unit 801 is further configured to:

[0563] Receive third communication content sent by a second device in a non-connected state, where the third communication content carries third data, and the third communication content is further used to indicate:

[0564] There is subsequent data to be sent to the first device after the third data; or,

[0565] There is no subsequent data to be sent to the first device after the third data.

[0566] Optionally, the first communication content is communication content sent during at least one of the following processes:

[0567] Initial registration, attachment, non-access stratum (NAS) context establishment, NAS security activation.

[0568] The above device can improve the transmission performance of the device.

[0569] It can be understood that the implementation processes of the various implementation manners mentioned in this embodiment can refer to the relevant descriptions of the above data transmission method, and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0570] It should be noted that the above device can also implement Figure 4 the steps in the method shown, or can implement Figure 6 the methods executed by the respective modules shown.

[0571] This application embodiment further provides a device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the steps of the method embodiment as shown in Figure 4 This network side device embodiment corresponds to the above data transmission method embodiment. The various implementation processes and implementation manners of the above method embodiment can all be applied to this device embodiment, and the same technical effects can be achieved.

[0572] This application embodiment further provides a device, including a processor and a communication interface. Among them, the communication interface is configured to receive first communication content sent by a first device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0573] Specifically, this application embodiment further provides a device. As shown in Figure 9As shown, the device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. The antenna 91 is connected to the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92. After processing the received information, the radio frequency device 92 sends it out through the antenna 91.

[0574] In the above embodiments, the data transmission method can be implemented in the baseband device 93, which includes a baseband processor.

[0575] The baseband device 93 may include, for example, at least one baseband board, on which a plurality of chips are provided, such as Figure 9 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 and execute the operations of the network device shown in the above method embodiments.

[0576] The device may further include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).

[0577] Specifically, the device 900 in the embodiments of the present application further includes: instructions or programs stored on the memory 95 and executable on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute Figure 6 the methods executed by the modules shown, and achieves the same technical effects. To avoid repetition, it will not be described herein again.

[0578] In this embodiment, the above device is a second device. Specifically, taking the second device as a network-side device as an example:

[0579] Among them, the radio frequency device 92 is used to receive the first communication content sent by the first device in the non-connected state. The first communication content carries the first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

[0580] Optionally, the first communication content includes at least one of the following:

[0581] RRC message, MAC PDU.

[0582] Optionally, the RRC message includes at least one of the following:

[0583] RRC early transmission data request message, or RRC early transmission data response message;

[0584] RRC uplink message, or RRC downlink message;

[0585] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0586] Optionally, after receiving the first communication content sent by the first device in the non-connected state, the radio frequency device 92 is further configured to:

[0587] The second device receives the second communication content sent by the first device in the non-connected state, the second communication content carries second data, and the second communication content is further used to indicate:

[0588] There is subsequent data to be sent to the second device after the second data; or,

[0589] There is no subsequent data to be sent to the second device after the second data.

[0590] Optionally, the first communication content includes: an RRC early transmission data request message, or an RRC early transmission data response message;

[0591] The second communication content includes: an RRC uplink message, or an RRC downlink message;

[0592] Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

[0593] Optionally, the first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following:

[0594] The format of the first communication content;

[0595] The data number information carried by the first communication content, and the data number information is expressed as multiple data;

[0596] The non-ending mark carried by the first communication content;

[0597] The data segmentation information carried by the first communication content.

[0598] Optionally, the data segmentation information includes at least one of the following:

[0599] Segment sequence number, tail segment identifier, total number of segments, and the value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

[0600] Optionally, receiving the first communication content sent by the first device in the non-connected state includes:

[0601] Receiving message 3 (Msg3) or message A (MsgA) in the random access process sent by the first device in the non-connected state, where the Msg3 or MsgA carries the first data;

[0602] Radio frequency device 92:

[0603] Sending message 2 (Msg2) or message B (MsgB) in the random access process to the first device, where the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or a cell radio network temporary identity (C-RNTI).

[0604] Optionally, the first communication content further includes a MAC control element (CE) or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following:

[0605] There is subsequent data to be sent to the second device after the first data;

[0606] Buffering information.

[0607] Optionally, the MAC CE or MAC sub-header carries at least one of the following:

[0608] A first indication bit, a logical channel ID (LCID), a second indication bit;

[0609] Wherein, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0610] The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0611] The second indication bit is used to indicate buffering information.

[0612] Optionally, when the first communication content includes a MAC protocol data unit (PDU), the MAC PDU includes at least one of the following:

[0613] Data type indication, subsequent data indication, buffering information indication, data length indication, segmentation indication;

[0614] Wherein, the data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

[0615] The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data;

[0616] The buffering information indication is used to indicate buffering information;

[0617] The data length indication is used to indicate the size of the first data carried by the MAC PDU;

[0618] The segmentation indication is used to indicate at least one of the following:

[0619] Segmented transmission, segmented sequence number, total number of segments, end segment flag.

[0620] Optionally, the radio frequency device 92:

[0621] Sends third communication content to the first device in a non-connected state, the third communication content carries third data, and the third communication content is further used to indicate:

[0622] There is subsequent data to be sent to the first device after the third data; or,

[0623] There is no subsequent data to be sent to the first device after the third data.

[0624] Optionally, the first communication content is the communication content received in at least one of the following processes:

[0625] Initial registration, attachment, non-access stratum NAS context establishment, NAS security activation.

[0626] The above device can improve the transmission performance of the device.

[0627] It can be understood that the implementation processes of the various implementation manners mentioned in this embodiment can refer to the relevant descriptions of the method embodiments above, and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0628] It should be noted that the above device can also implement Figure 3 the steps in the method shown, or can implement Figure 5 the methods executed by the various modules shown.

[0629] The embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements each process of the above data transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0630] Among them, the processor is the processor in the terminal in the above embodiment. The readable storage medium includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disc, etc. In some examples, the readable storage medium can be a non-transitory readable storage medium.

[0631] Another embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run programs or instructions to implement each process of the above data transmission method embodiment, and can achieve the same technical effects. To avoid repetition, details are not described herein again.

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

[0633] Another embodiment of the present application further provides a computer program / program product. The computer program / program product is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the above data transmission method embodiment, and can achieve the same technical effects. To avoid repetition, details are not described herein again.

[0634] Another embodiment of the present application further provides a wireless communication system, including: a first device and a second device. The first device can be used to execute the steps of the data transmission method on the first device side provided in the embodiments of the present application, and the second device can be used to execute the steps of the data transmission method on the second device side provided in the embodiments of the present application.

[0635] It should be noted that in this article, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including that element. In addition, it should be pointed out that the methods and devices in the embodiments of the present application are not limited to performing functions in the order shown or discussed. They may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0636] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disc, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0637] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. All these embodiments fall within the protection scope of the present application.

Claims

1. A data transmission method, characterized in that, Including: A first device sends first communication content to a second device in a non-connected state. The first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

2. The method according to claim 1, wherein The first communication content includes at least one of the following: A radio resource control (RRC) message, a media access control (MAC) protocol data unit (PDU).

3. The method according to claim 2, wherein The RRC message includes at least one of the following: An RRC early transmission data request message, or an RRC early transmission data response message; An RRC uplink message, or an RRC downlink message; Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

4. The method according to any one of claims 1 to 3, characterized in that, After the first device sends the first communication content to the second device in the non-connected state, the method further includes: The first device sends second communication content to the second device in the non-connected state. The second communication content carries second data, and the second communication content is further used to indicate: There is subsequent data to be sent to the second device after the second data; or, There is no subsequent data to be sent to the second device after the second data.

5. The method according to claim 4, wherein The first communication content includes: an RRC early transmission data request message, or an RRC early transmission data response message; The second communication content includes: an RRC uplink message, or an RRC downlink message; Wherein, the RRC uplink message and the RRC early transmission data request message are different RRC messages, and the RRC downlink message and the RRC early transmission data response message are different RRC messages.

6. The method according to any one of claims 1 to 5, characterized in that, The first device sending the first communication content to the second device in the non-connected state includes: When the first device determines that a target condition is met, the first device sends the first communication content to the second device in the non-connected state. Wherein, the target condition includes at least one of the following: There are multiple pieces of high-layer data; High-layer data needs to be segmented for transmission; There is only one piece of high-layer data, and the size of the one piece of data is greater than a preset threshold; The link quality is a preset quality; The RRC layer or the MAC layer receives an indication of the possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication of continuous data transmission.

7. The method according to claim 6, wherein The method further includes: When the first device determines that the target condition is not met, the first device sends third communication content to the second device in the non-connected state. The third communication content carries third data, and the data transmission process corresponding to the third communication content can only transmit data once in the uplink or downlink.

8. The method according to any one of claims 1 to 4, characterized in that, The first device sending the first communication content to the second device in the non-connected state includes: When the RRC layer of the first device obtains a target judgment result, the first device sends the first communication content to the second device in the non-connected state. Wherein, the target judgment result includes at least one of the following: Based on the data that has reached the RRC layer, it is judged that the service transmission requirement is multi-data transmission; Based on the data that has reached the RRC layer, it is judged that segmentation for transmission is required; Judge that there is subsequent data transmission according to the service type or the indication received by the RRC layer; It is impossible to judge whether there is subsequent data transmission according to the service type or the indication received by the RRC layer.

9. The method according to any one of claims 1 to 8, characterized in that, The first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following: The format of the first communication content; The number-of-data information carried in the first communication content, and the number-of-data information is represented as multiple data; The non-ending mark carried in the first communication content; The data segmentation information carried in the first communication content.

10. The method according to claim 9, characterized in that, The data segmentation information includes at least one of the following: Segment sequence number, tail segment identifier, total number of segments, and the value of the tail segment identifier indicates that there is subsequent data to be sent to the second device after the first data.

11. The method according to any one of claims 1 to 10, characterized in that, The radio link control (RLC) layer of the first device performs at least one of the following transmission processes: Transmit the first communication content using the transparent mode (TM), acknowledged mode (AM), or unacknowledged mode (UM); Perform segmented transmission on the first data carried in the first communication content; Multiple service transmission requirements are carried out simultaneously, and the multiple service transmission requirements include the service transmission requirement to which the first data belongs.

12. The method according to claim 11, wherein In the case where the RLC layer uses the AM or UM transmission mode, the RLC entity of the RLC layer delivers the first data and the subsequent data of the first data in the order of the sequence number (SN), where the initial value of SN is 0.

13. The method according to claim 12, characterized in that, In the case where the service transmission requirement corresponding to the RLC entity is completed, perform one of the following processes on the RLC entity: Delete, reset, clear.

14. The method according to any one of claims 11 to 13, characterized in that, In the case where multiple service transmission requirements are carried out simultaneously, different service transmission requirements use different logical channel identifiers (LCIDs), and the transmission configurations used by different service transmission requirements are protocol-agreed or pre-configured.

15. The method according to any one of claims 1 to 14, characterized in that The first device sends the first communication content to the second device in the non-connected state, including: The first device sends message 3 (Msg3) or message A (MsgA) in the random access process to the second device through the MAC layer in the non-connected state, where Msg3 or MsgA carries the first data; The method further includes: The first device receives message 2 (Msg2) or message B (MsgB) in the random access process through the MAC layer in the non-connected state, and Msg2 or MsgB carries at least one of the uplink synchronization adjustment information or the cell radio network temporary identifier (C-RNTI).

16. The method according to any one of claims 1 to 15, characterized in that, The first communication content further includes a MAC control element (CE) or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following: There is subsequent data to be sent to the second device after the first data; Buffering information.

17. The method according to claim 16, wherein The MAC CE or MAC sub-header carries at least one of the following: A first indication bit, an LCID, a second indication bit; Wherein, the first indication bit is used to indicate that there is subsequent data to be sent to the second device after the first data; The LCID is used to indicate that there is subsequent data to be sent to the second device after the first data; The second indication bit is used to indicate caching information.

18. The method according to any one of claims 1 to 17, characterized in that, In a case where there is no more data transmission by the first device in the resources allocated for the subsequent data, the first device skips the resources or sends an indication that the subsequent data transmission is complete to the second device.

19. The method according to any one of claims 1 to 18, characterized in that, The MAC layer of the first device maintains one or more Hybrid Automatic Repeat reQuest (HARQ) processes for the service transmission requirements to which the first data belongs.

20. The method according to any one of claims 1 to 19, characterized in that, In a case where the first communication content includes a MAC PDU, the MAC PDU includes at least one of the following: Data type indication, subsequent data indication, caching information indication, data length indication, segmentation indication; Wherein, the data type indication is used to indicate the type of the service transmission requirements to which the first data belongs; The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data; The caching information indication is used to indicate caching information; The data length indication is used to indicate the size of the first data carried by the MAC PDU; The segmentation indication is used to indicate at least one of the following: Segmented transmission, segmentation sequence number, total number of segments, tail segment marker.

21. The method according to any one of claims 1 to 20, characterized in that, The method further includes: The first device receives third communication content sent by the second device in a non-connected state, the third communication content carries third data, and the third communication content is further used to indicate: There is subsequent data to be sent to the first device after the third data; or, There is no subsequent data to be sent to the first device after the third data.

22. The method according to any one of claims 1 to 14 or 16 to 21, characterized in that The first communication content is the communication content sent in at least one of the following processes: Initial registration, attachment, non-access stratum (NAS) context establishment, NAS security activation.

23. A data transmission method, characterized in that Including: The second device receives first communication content sent by the first device in a non-connected state, the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

24. The method according to claim 23, wherein The first communication content includes at least one of the following: Radio Resource Control (RRC) message, Media Access Control (MAC) Protocol Data Unit (PDU).

25. The method according to claim 23 or 24, characterized in that, After the second device receives the first communication content sent by the first device in a non-connected state, the method further includes: The second device receives second communication content sent by the first device in a non-connected state, the second communication content carries second data, and the second communication content is further used to indicate: There is subsequent data to be sent to the second device after the second data; or, There is no subsequent data to be sent to the second device after the second data.

26. The method according to any one of claims 23 to 25, characterized in that The first communication content indicates that there is subsequent data to be sent to the second device after the first data through at least one of the following: The format of the first communication content; The data number information carried by the first communication content, the data number information representing multiple data; The non-ending marker carried by the first communication content; The data segmentation information carried by the first communication content.

27. The method according to any one of claims 23 to 26, characterized in that, The second device receives the first communication content sent by the first device in a non-connected state, including: The second device receives Message 3 (Msg3) or Message A (MsgA) in a random access procedure sent by the first device in a non-connected state, where the Msg3 or MsgA carries the first data; The method further includes: The second device sends Message 2 (Msg2) or Message B (MsgB) in a random access procedure to the first device, where the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or a cell radio network temporary identifier (C-RNTI).

28. The method according to any one of claims 23 to 27, characterized in that, The first communication content further includes a MAC control element (CE) or a MAC sub-header, where the MAC CE or MAC sub-header is used to indicate at least one of the following: There is subsequent data to be sent to the second device after the first data; Buffering information.

29. The method according to any one of claims 23 to 28, characterized in that, When the first communication content includes a MAC protocol data unit (PDU), the MAC PDU includes at least one of the following: Data type indication, subsequent data indication, buffering information indication, data length indication, segmentation indication; Wherein, the data type indication is used to indicate the type of service transmission requirement to which the first data belongs; The subsequent data indication is used to indicate that there is subsequent data to be sent to the second device after the first data; The buffering information indication is used to indicate buffering information; The data length indication is used to indicate the size of the first data carried by the MAC PDU; The segmentation indication is used to indicate at least one of the following: Segmented transmission, segmentation sequence number, total number of segments, end segment flag.

30. The method according to any one of claims 23 to 29, characterized in that The method further includes: The second device sends third communication content to the first device in a non-connected state, the third communication content carries third data, and the third communication content is further used to indicate: There is subsequent data to be sent to the first device after the third data; or, There is no subsequent data to be sent to the first device after the third data.

31. The method according to any one of claims 23 to 26 or 28 to 30, characterized in that, The first communication content is the communication content received in at least one of the following processes: Initial registration, attachment, non-access stratum (NAS) context establishment, NAS security activation.

32. A data transmission device, characterized in that, Including: A first sending module, configured to send first communication content to a second device in a non-connected state, the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to the second device after the first data.

33. The device according to claim 32, characterized in that, The apparatus further includes: A second sending module, configured to send second communication content to the second device in a non-connected state, the second communication content carries second data, and the second communication content is further used to indicate: There is subsequent data to be sent to the second device after the second data; or, There is no subsequent data to be sent to the second device after the second data.

34. The device according to claim 32 or 33, characterized in that, The first sending module is configured to send the first communication content to the second device in a non-connected state when the first device determines that a target condition is met, where the target condition includes at least one of the following: There are multiple pieces of high-layer data; High-layer data needs to be segmented for transmission; There is only one piece of high-layer data, and the size of the one piece of data is greater than a preset threshold; The link quality is a preset quality; The RRC layer or the MAC layer receives an indication of the possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication of continuous data transmission.

35. The device according to claim 34, characterized in that, The device further includes: A third sending module, configured to, when the first device determines that the target condition is not satisfied, send third communication content to a second device in a non-connected state, where the third communication content carries third data, and the data transmission process corresponding to the third communication content can only transmit data once in the uplink or the downlink.

36. The device according to any one of claims 32 to 35, characterized in that, The device further includes: A first receiving module, configured to receive third communication content sent by a second device in a non-connected state, where the third communication content carries third data, and the third communication content is further used to indicate: There is subsequent data to be sent to the first device after the third data; or, There is no subsequent data to be sent to the first device after the third data.

37. A data transmission device, characterized in that, Includes: A first receiving module, configured to receive first communication content sent by a first device in a non-connected state, where the first communication content carries first data, and the first communication content is further used to indicate that there is subsequent data to be sent to a second device after the first data.

38. The device according to claim 37, wherein, The device further includes: A second receiving module, configured to receive second communication content sent by a first device in a non-connected state, where the second communication content carries second data, and the second communication content is further used to indicate: There is subsequent data to be sent to the second device after the second data; or, There is no subsequent data to be sent to the second device after the second data.

39. The device according to claim 37 or 38, characterized in that, The device further includes: A first sending module, configured to send third communication content to the first device in a non-connected state, where the third communication content carries third data, and the third communication content is further used to indicate: There is subsequent data to be sent to the first device after the third data; or, There is no subsequent data to be sent to the first device after the third data.

40. A device, characterized in that, Comprising a processor and a memory, where the memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the data transmission method according to any one of claims 1 to 22, or when the program or instruction is executed by the processor, it implements the steps of the data transmission method according to any one of claims 23 to 31.

41. A readable storage medium, characterized in that, The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, it implements the steps of the data transmission method according to any one of claims 1 to 22, or implements the steps of the data transmission method according to any one of claims 23 to 31.

Images