Data transmission method and apparatus, and device

Abstract

The present application relates to the technical field of communications, and discloses a data transmission method and apparatus, and a device. The data transmission method of embodiments of the present application comprises: a first device sends first communication content to a second device in a non-connected state, wherein the first communication content carries first data, and the first communication content is further used for indicating that data subsequent to the first data needs to be sent to the second device.

Description

Data transmission method, device and equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410036590.7 filed in China on January 10, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data transmission method, apparatus and device. Background Art

[0004] The device state can often include a connected state and a disconnected state, wherein the disconnected state can include an idle state (IDLE state) and an inactive state (INACTIVE state). In related technologies, devices often send and receive data in the connected state. This results in poor data transmission performance of the device. Summary of the Invention

[0005] The embodiments of the present application provide a data transmission method, apparatus, and device, which can solve the problem of poor data transmission performance of the device.

[0006] In a first aspect, a data transmission method is provided, comprising:

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

[0008] In a second aspect, a data transmission method is provided, comprising:

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

[0010] In a third aspect, a data transmission device is provided, comprising:

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

[0012] In a fourth aspect, a data transmission device is provided, comprising:

[0013] The first receiving module is 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 is further configured to indicate that subsequent data to be sent to the second device is after the first data.

[0014] In a fifth aspect, a device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data transmission method on the first device side provided in an embodiment of the present application are implemented.

[0015] In the sixth aspect, a device is provided, comprising a processor and a communication interface, wherein 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 also used to indicate that subsequent data is to be sent to the second device after the first data.

[0016] In the seventh aspect, a device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data transmission method on the second device side provided in the embodiment of the present application are implemented.

[0017] In the eighth aspect, a device is provided, including a processor and a communication interface, wherein 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 also used to indicate that subsequent data is to be sent to the second device after the first data.

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

[0019] In the tenth aspect, a wireless communication system is provided, including: a first device and a second device, wherein the first device can be used to execute the steps of the data transmission method on the first device side provided in the embodiment 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 embodiment of the present application.

[0020] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a program or instruction to implement the data transmission method on the first device side provided in the embodiment of the present application, or to implement the steps of the data transmission method on the second device side provided in the embodiment of the present application.

[0021] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the data transmission method on the first device side provided in the embodiment 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 embodiment of the present application.

[0022] In an embodiment of the present application, a first device transmits first communication content to a second device in a non-connected state. The first communication content carries first data and is also used to indicate that subsequent data is to be sent to the second device after the first data. This allows data to be transmitted in a non-connected state, thereby improving the transmission performance of the device. Moreover, because the first communication content is also used to indicate that subsequent data is to be sent to the second device after the first data, multiple data transmissions can be supported, further improving the transmission performance of the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0024] FIG2 is a diagram illustrating instructions for a reader and a tag provided in an embodiment of the present application;

[0025] FIG3 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0026] FIG4 is a flowchart of another data transmission method provided in an embodiment of the present application;

[0027] FIG5 is a structural diagram of a data transmission device provided in an embodiment of the present application;

[0028] FIG6 is a structural diagram of another data transmission device provided in an embodiment of the present application;

[0029] FIG7 is a structural diagram of a communication device provided in an embodiment of the present application;

[0030] FIG8 is a structural diagram of another communication device provided in an embodiment of the present application;

[0031] FIG9 is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0033] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, 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 more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0034] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0035] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0036] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (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 (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), a teller machine, a self-service machine, an Internet of Things (IoT) device, or an ambient IoT (A-IoT) device, etc., a terminal-side device. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.

[0037] The network-side device 12 may include an access network device or a core network device, wherein 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. Among them, the base station can 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0038] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0039] In some embodiments, 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:

[0040] Device A: It is a passive device with no energy storage and no independent signal generation / amplification, i.e. backscatter transmission.

[0041] Device B: Semi-passive device, also belongs to the passive device category. It has energy storage but no independent signal generation, i.e. backscatter transmission. The use of stored energy may include amplification of the reflected signal.

[0042] Device C: Active device, with energy storage and independent signal generation, that is, active RF components for transmission.

[0043] In some embodiments, the A-IoT device may be a tag or other low-power IoT device.

[0044] In some embodiments, a non-tag terminal or network-side device can serve as a tag reader, and the tag can be a radio frequency identification (RFID) tag.

[0045] In some embodiments, information transmission between a reader and a tag may be as shown in FIG2 , and reader operation instructions may be as shown in Table 1:

[0046] Table 1:

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

[0048] Table 2:

[0049] It should be noted that the above Tables 1 and 2 are only examples for illustrating the information transmission between the reader and the tag. In the embodiments of the present application, there is no specific limitation on the information transmission between the reader and the tag.

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

[0051] Please refer to FIG3 , which is a flowchart of a data transmission method provided in an embodiment of the present application. As shown in FIG3 , the method includes the following steps:

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

[0053] The first device may be a terminal or a network-side device, such as an AIoT device or an IoT device, which is not limited in this embodiment of the present application. The second device may be a network-side device or a terminal, or a tag reader.

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

[0055] The first device in the non-connected state sends the first communication content to the second device, such as the terminal in the non-connected state sends 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 sends 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 may include but is not limited to communication content of at least one of the following protocol layers:

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

[0059] The non-connected state may be an idle state or an inactive state.

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

[0061] The above indication that subsequent data is to be sent to the second device after the first data may indicate that the first device has subsequent data to be sent to the second device after the first data in a non-connected state, thereby enabling multiple data transmissions in a non-connected state.

[0062] In some embodiments, the indication that subsequent data is to be sent to the second device after the first data may not be limited to the non-connected state, and may simply indicate that subsequent data is to be sent to the second device after the first data. For example, the RRC state may also be controlled by a network-side device. If determined by a network-side device algorithm, such as in a light load situation or other situation, when the first device indicates subsequent data, the first device may be switched to a connected state (CONNECTED) for subsequent data transmission.

[0063] The subsequent data may also be referred to as connection data, and may 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. It can be an explicit indication, such as carrying indication information in the first communication content, and the 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 through the format of the first communication content or multiplexing the indication field of the first communication content, etc., indicating that there is subsequent data to be sent to the second device after the first data.

[0065] In an embodiment of the present application, the above steps can be used to transmit data in a non-connected state 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 optional implementation manner, the first communication content includes at least one of the following:

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

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

[0069] In this implementation, the first data may be carried by at least one of an RRC message or a MAC PDU.

[0070] In this embodiment, the above-mentioned RRC message or MAC PDU can be used to indicate that subsequent data will be sent to the second device after the first data, or the first communication content may include other content in addition to the above-mentioned RRC message or MAC PDU, such as a MAC control unit (Control Element, CE) or a MAC subheader, and the MAC CE or MAC subheader may be used to indicate that subsequent data will be sent to the second device after the first data.

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

[0072] RRC Early Data Request message or RRC Early Data Response message;

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

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

[0075] The RRC early data response may be an RRC Early Data Complete message.

[0076] Among them, the above-mentioned RRC uplink message and RRC downlink message can be understood as the RRC messages newly defined in the embodiments of the present application, such as the RRC continuous data request (RRC Continuous Data Request) message and the RRC continuous data response (RRC Continuous Data Response) message.

[0077] In the above implementation, continuous data transmission can be achieved through multiple messages to improve the flexibility of data transmission.

[0078] As an optional implementation manner, 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 a non-connected state, where 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] No subsequent data is to be sent to the second device after the second data.

[0082] The second data is at least one data packet, at least one data block or at least one data segment following the first data.

[0083] When it is indicated that subsequent data is to be sent to the second device after the second data, three or more consecutive data transmissions may be implemented; when it is indicated that no subsequent data is to be sent to the second device after the second data, two consecutive data transmissions may be implemented, thereby improving 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] The RRC uplink message and the RRC early data transmission request message are different RRC messages, and the RRC downlink message and the RRC early data transmission response message are different RRC messages.

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

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

[0089] For example, for multiple continuous uplink data, 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, is used. Alternatively, a new MAC PDU format is designed to carry high-layer data, and a Release Assistance Information (RAI) format or an end marker is used to assist in the release. The RAI format may be the newly defined RAI format in the embodiment of the present application, and may include the following methods:

[0090] The first method is: N RRC Early Data Request messages carry higher-layer data, and the RAI format / End marker is used to complete the transmission.

[0091] The second method: RRC Early Data Request message + RRC Continuous Data Request message multiple combinations carry higher-layer data, and assist RAI format / End marker to complete the transmission;

[0092] The third method: N RRC Continuous Data Request messages, optionally with the auxiliary RAI format / End marker to complete the transmission;

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

[0094] The auxiliary RAI format / End marker transmission can be understood as the RAI format / End marker carried in the above message or MAC PDU.

[0095] For multiple consecutive downlink data, RRC Early Data Complete or a new RRC message (i.e., the above-mentioned RRC downlink message) is used, such as RRC Continuous Data Response. Alternatively, a new MAC PDU is designed to carry higher-layer data and assisted by a new RAI format / End marker. This can be done in the following ways:

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

[0097] The second method: N RRC Continuous Data Response messages carry higher-layer data, supplemented by the RAI format / End marker to complete the transmission.

[0098] The third method: RRC Early Data Complete and RRC Continuous Data Response are combined to carry higher-layer data, optionally supplemented by the RAI format / End marker to complete the transmission.

[0099] The fourth method: N MAC new format PDUs each carry higher-layer data, assisted by the RAI format / End marker to complete the transmission.

[0100] The RAI format / End marker function may include at least one of the following:

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

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

[0103] Finally, a similar RRC connection release is performed.

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

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

[0106] There are multiple data in the high-level data;

[0107] High-level data needs to be transmitted in segments;

[0108] The high-level data has only one data, and the size of the data is greater than a preset threshold;

[0109] The link quality is the preset quality;

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

[0111] The above-mentioned target conditions, preset thresholds, and preset qualities may be agreed upon in a protocol or configured on the network side, or determined by the first device itself.

[0112] The above-mentioned high-level data has only one data, and the fact that the size of the data is greater than the preset threshold may indicate that the size of the data is large and needs to be transmitted in segments.

[0113] The link quality being the preset quality may indicate that the link quality is poor. If the link quality does not meet the threshold, multiple attempts may be required.

[0114] In this implementation, when the first device determines that the target condition is met, the first device sends the first communication content to the second device in a non-connected state. This allows continuous data transmission according to actual needs to improve device transmission performance.

[0115] Optionally, the method further includes:

[0116] When the first device determines that the target condition is not met, the first device sends a third communication content to the 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 downlink.

[0117] The fact that the data transmission process corresponding to the third communication content can only transmit data once in the uplink or downlink can be understood as follows: when the third communication content is used for data transmission, only uplink data can be transmitted once or downlink data can be transmitted once in a non-connected state, i.e., continuous data transmission cannot be achieved. For example, the data transmission process corresponding to the third communication content uses Small Data Transmission (SDT) or Early Data Transmission (EDT).

[0118] In this implementation, when the target condition is not met, the third communication content can be sent to the second device, thereby achieving discontinuous data transmission to save device resources.

[0119] As an optional implementation manner, the first device sending the first communication content to the second device in a non-connected state includes:

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

[0121] Determining, based on the data that has arrived at the RRC layer, that the service transmission requirement is multiple data transmission;

[0122] Determining that segmented transmission is required based on data that has arrived at the RRC layer;

[0123] Determining whether there is subsequent data transmission based on the service type or the indication received by the RRC layer;

[0124] It is not possible to determine whether there will be subsequent data transmission based on the service type or the indication received by the RRC layer.

[0125] Among them, the above-mentioned judgment that the service transmission requirement is multiple data transmission based on the data that has reached the RRC layer can be that the RRC layer determines that the data that has reached the RRC layer cannot be completed through one data transmission, or it determines that there is subsequent data based on the data that has reached the RRC layer.

[0126] The above-mentioned determination based on the data that has reached the RRC layer that segmented transmission is required may be that the RRC layer determines that the data that has reached the RRC layer cannot be completed through one transmission, such as the data size is too large and needs to be transmitted in segments.

[0127] The above-mentioned determination based on the service type that there is subsequent data transmission may mean that there are multiple data of the service type.

[0128] In this implementation, since the target judgment result is obtained, the first device sends the first communication content to the second device in a non-connected state, which can achieve continuous data transmission according to actual needs to improve the transmission performance of the device.

[0129] As an optional implementation manner, the first communication content indicates that subsequent data is 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] Information about the number of data items carried by the first communication content, where the information about the number of data items is represented as a plurality of data items;

[0132] a non-end marker carried by the first communication content;

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

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

[0135] The data quantity information carried by the first communication content may be the total data quantity information or the remaining untransmitted data quantity information.

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

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

[0138] The tail segment identifier corresponds to multiple values, which are used to indicate whether it is a tail segment or not, such as 0 for a tail segment and 1 for a non-tail segment. The value of the tail segment identifier carried by the first communication content indicates that it is not a tail segment, that is, it indicates that subsequent data after the first data is to be sent to the second device. If 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 that it is a tail segment.

[0139] In an optional implementation, it may be implemented to indicate in a variety of ways that subsequent data is to be sent to the second device after the first data, so as to improve the flexibility of data transmission.

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

[0141] Transmitting the first communication content in a transparent transmission mode (TM), an acknowledged mode (AM), or an unacknowledged mode (UM);

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

[0143] Multiple business transmission demands are carried out simultaneously, and the multiple business transmission demands include the business transmission demand to which the first data belongs.

[0144] The segmented transmission of the first data carried by the first communication content can be understood as segmentation at the RLC layer, that is, the first data is data segments obtained by segmentation at the RLC layer. In some implementations, segmentation can also be performed at the RRC layer, which is not limited.

[0145] The aforementioned multiple service transmission requirements may be carried out simultaneously, or multiple service transmission requirements may overlap during the transmission process, which may be determined by triggers from higher layers, 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 may be used to correspond to different services to meet different requirements. When different service data are transmitted at the bottom layer, multiple Hybrid Automatic Repeat Request (HARQ) processes may also be used to avoid waiting. For example, two Hybrid Automatic Repeat Request (HARQ) processes can transmit different service data using different HARQ processes. For example, HARQ process 1 sends service data 1 in the first time slot, and HARQ process 2 immediately sends service data 2 in the second time slot. For example, time slot 2 = time slot 1 + 1. Taking into account feedback and retransmission processes, HARQ process 1 for service data 1 can, if all goes well, take time slot 1 + 4 (successful first transmission without retransmission) or even time slot 1 + 12 (successful first retransmission) to complete. In this process, service data 2 in HARQ process 2 significantly overlaps with HARQ process 1, and service data 2 may even complete before service data 2. This means that although service data 2 should be transmitted after service data 1 according to arrival order or priority, the existence of different processes allows for simultaneous or overlapping processing, eliminating the need for service data 2 to wait.

[0146] The above-mentioned multiple data transmission requirements may be mapped to different RLC entities for processing.

[0147] In the above implementation, the RLC layer can be used to implement transmission in multiple transmission modes to improve the flexibility of data transmission, and multiple service transmission requirements can be performed 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 transmits the first data and subsequent data of the first data in sequence of serial numbers (SN), where the initial value of SN is 0.

[0149] In this implementation, since the initial value of SN is 0, it can be achieved that the device in the non-connected state can have the same understanding of SN as the opposite device, so as to improve data performance. For example: when the first device initiates a new small data transmission, the initial SN value of the RLC entity starts from 0, that is, the first data packet SN=0, the second data packet SN=1, and so on, and the same AIoT device acts as the receiving end this time, and the initial value of the SN variable of the receiving entity also starts from 0, that is, the next expected data packet SN=0; Conversely, when the network side or the reader side performs a new small data transmission process with an AIoT device, the initial SN variable of the RLC receiving end also starts from 0, that is, the next expected data packet SN=0, including the first DL data packet of the network side as the sending end performing this small data transmission also SN=0, and then increases in sequence.

[0150] Optionally, when the service transmission requirement corresponding to the RLC entity is transmitted, performing one of the following processes on the RLC entity:

[0151] Delete, reset, clear.

[0152] The service transmission requirement corresponding to the above-mentioned RLC entity may 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 demand corresponding to the RLC entity is transmitted completely, the resources of the RLC layer can be saved.

[0154] Optionally, when 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.

[0155] The 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 a protocol agreement or pre-configuration.

[0158] In this implementation, since the transmission configuration adopted for different service transmission requirements is a protocol agreement or pre-configuration, this avoids the use of RRC dedicated signaling configuration, which requires establishing an RRC connection, activating access stratum (AS) layer security and other operations to save device power consumption.

[0159] As an optional implementation manner, the first communication content is communication content sent in at least one of the following processes:

[0160] Random access procedure, initial registration, attach, non-access stratum (NAS) context establishment, NAS security activation.

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

[0162] In this implementation, continuous data transmission can be achieved 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 connection 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, the first device sends the first communication content to the second device in the non-connected state, including:

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

[0165] The method further comprises:

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

[0167] The uplink synchronization adjustment information may be an uplink timing adjustment (TA), which is used to make a subsequent uplink timing advance.

[0168] The C-RNTI is used for data scheduling of the first device, and the first device may always use the 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, wherein 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] Cache information.

[0172] The above-mentioned first communication content also includes MAC CE or MAC subheader (MAC subheader), which may mean that the first communication content includes the above-mentioned RRC message or MAC PDU, and also includes MAC CE or MAC subheader.

[0173] In which case, when the MAC CE or MAC subheader does not indicate that subsequent data is to be sent to the second device after the first data, the indication may be performed using the implementation method described above.

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

[0175] The MAC CE or MAC subheader may carry a bit or LCID indicating the cache information or that subsequent data is to be sent to the second device after the first data. For example, the MAC CE or MAC subheader may carry at least one of the following:

[0176] First indication bit, LCID, second indication bit;

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

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

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

[0180] The first indication bit may be one or more bits, and the second indication bit may be one or more bits.

[0181] For example: a small number of bits in the MAC CE or MAC subheader display indications: for example, the values ​​of bit 1 / 0 respectively indicate whether multiple data transmission is being transmitted, and the values ​​of bit 1 / 0 respectively indicate whether it is the last uplink (UL) data packet. For example, 2-bit 00 represents single data transmission, 01 represents UL multiple data transmission non-end packet, 10 represents the end packet of UL multiple data transmission, 11 represents that downlink data is still expected, etc.

[0182] Different LCID values ​​represent different meanings. For example, LCID=0 represents a single small data transmission scenario, and LCID=4 represents a multi-data small data transmission scenario.

[0183] Alternatively, more bits can be used to represent buffer size information. For example, the first byte of the MAC subheader carries the LCID or multiple data indicator, while the second byte carries subsequent buffer size information. Furthermore, the expected data block size can be indicated, also in coded form. For example, 3 bits are used to indicate the data block size, with 000 representing data block size 1, 001 representing data block size 2, and 010 representing data block size 3. The remaining 5 bits are used to indicate the number of subsequent data packets. This allows the network to determine the subsequent data volume by multiplying the data block size by the number of packets. Furthermore, the network can accurately determine the approximate size of each packet, facilitating more flexible scheduling.

[0184] In the above implementation, since the MAC CE or MAC subheader indicates that there is subsequent data to be sent to the second device after the first data, this can make the continuous transmission of the indicated data more flexible, and the indication of cache information can enable the second device to better understand the cache of the first device, which is beneficial for the second device to better transmit data with the first device.

[0185] As an optional implementation manner, when the first device has no more data to transmit 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] The fact that the first device is no longer transmitting data in the resources allocated for the subsequent data may mean that the subsequent data transmission is completed.

[0187] The first device skipping the resource may also be understood as the first device ignoring the resource.

[0188] The above-mentioned indication of the completion of the subsequent data transmission being sent to the second device may be indicated by an end mark or BS=0 indicating that the subsequent data transmission is completed.

[0189] By sending an indication that the subsequent data transmission is completed to the second device, the second device can perform corresponding release, such as releasing information such as C-RNTI, clearing the timer and cache, so as to save resources.

[0190] In some implementations, the resources allocated for the subsequent data may be resources allocated when the number of subsequent data is difficult to determine. For example, when the first device is currently sending UL data, it only has a small amount of data. After the transmission is successful, it receives downlink (DL) data, and the corresponding DL data will generate a subsequent UL response. By analogy, when the UE continuously sends and receives data, the network side can continuously allocate uplink resources to the first device. Of course, the allocation of uplink resources needs to take into account the processing delay after the first device receives the downlink data, the delay in generating uplink data, etc., and allocate according to the recommended or reported data block size. In this way, flexible resource allocation can be achieved.

[0191] As an optional implementation manner, the MAC layer of the first device maintains one or more HARQ processes according to the service transmission requirements to which the first data belongs.

[0192] The one or more HARQ processes are used to perform HARQ feedback, retransmission or repeated transmission (repetition) and other operations on the service transmission requirements.

[0193] In the case where the first device is an AIoT device, the MAC layer maintains one or two HARQ processes for the service transmission requirements of the first data. In this way, since only one or two HARQ processes are maintained at the MAC layer for the service transmission requirements of the first data, the complexity of data transmission can be reduced. For example, if the first device is an AIoT device, and AIoT devices are simple, one or two HARQ processes are sufficient.

[0194] In some implementations, the application of two HARQ processes can be expanded. For situations where the amount of data is slightly larger or concurrent, two HARQ processes can be processed simultaneously to further reduce latency.

[0195] As an optional implementation manner, 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] The data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

[0198] The subsequent data indication is used to indicate that subsequent data is 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 segment indication is used to indicate at least one of the following:

[0202] Segment transmission, segment sequence number, total number of segments, and end segment marker.

[0203] The type of the service transmission requirement may be continuous small data in IDLE state or continuous Common Control Channel (CCCH) small data in IDLE state.

[0204] The above tail segment flag may be used to indicate whether the data in the current communication content is a tail segment.

[0205] In this embodiment, since at least one of the above items is indicated in the above MAC PDU, the second device can better understand the data that the first device needs to send, which is beneficial for the second device to better transmit data 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 embodiment of the present application, the implementation of the first communication content may also be applied to the second communication content. For example, the MAC PDU included in the second communication content may also include at least one of the following:

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

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

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

[0210] The first device receives, in a non-connected state, third communication content sent by the second device, where 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 the non-connected state may be performed before or after step 301. For example, the first communication content may be sent first, the second communication content may be received, and the third communication content may be sent. Alternatively, the third communication content may be received first and the first communication content may be sent. In some embodiments, the third communication content may be directly received and then the first communication content or the second communication content may be sent or not.

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

[0215] Indicating that subsequent data is to be sent to the first device after the third data enables 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, in a non-connected state, fourth communication content sent by the second device, where 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] The content and indication method of the third communication content and the fourth communication content may refer to the indication method of the first communication content. For example, the third communication content or the fourth communication content includes at least one of the following:

[0220] RRC message, MAC PDU.

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

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

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

[0224] The RRC uplink message and the RRC early data transmission request message are different RRC messages, and the RRC downlink message and the RRC early data transmission 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] The RRC uplink message and the RRC early data transmission request message are different RRC messages, and the RRC downlink message and the RRC early data transmission response message are different RRC messages.

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

[0229] the format of the communication;

[0230] Information about the number of data items carried in the communication content, where the information about the number of data items is represented as multiple data items;

[0231] Non-end markers carried in the communication content;

[0232] Data segment information carried by the communication content.

[0233] The data segmentation information may include at least one of the following:

[0234] Segment sequence number, tail segment identifier, and 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 subheader, wherein the MAC CE or the MAC subheader is used to indicate at least one of the following:

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

[0237] Cache information.

[0238] The MAC CE or MAC subheader may carry at least one of the following:

[0239] First indication bit, LCID, second indication bit;

[0240] 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] Data type indication, subsequent data indication, cache information indication, data length indication, segmentation indication;

[0245] 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 indicator is used to indicate the size of the data carried by the MAC PDU;

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

[0250] Segment transmission, segment sequence number, total number of segments, and end segment marker.

[0251] In an embodiment of the present application, a first device transmits first communication content to a second device in a non-connected state. The first communication content carries first data and is also used to indicate that subsequent data is to be sent to the second device after the first data. This allows data to be transmitted in a non-connected state, thereby improving the transmission performance of the device. Moreover, because the first communication content is also used to indicate that subsequent data is to be sent to the second device after the first data, multiple data transmissions can be supported, further improving the transmission performance of the device.

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

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

[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] The RRC uplink message and the RRC early data transmission request message are different RRC messages, and the RRC downlink message and the RRC early data transmission 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 second communication content sent by the first device in the unconnected state, where the second communication content carries second data and is further used to indicate:

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

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

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

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

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

[0267] Optionally, the first communication content indicates that subsequent data is 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] Information about the number of data items carried by the first communication content, where the information about the number of data items is represented as a plurality of data items;

[0270] a non-end marker carried by the first communication content;

[0271] The data segment 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, and total number of segments, where the value of the tail segment identifier indicates that subsequent data is to be sent to the second device after the first data.

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

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

[0276] The method further comprises:

[0277] The second device sends a message 2 Msg2 or a message BMsgB in a 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 identifier C-RNTI.

[0278] Optionally, the first communication content further includes a MAC control element CE or a MAC subheader, where the MAC CE or the MAC subheader 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] Cache information.

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

[0282] First indication bit, LCID, second indication bit;

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

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

[0285] The second indication bit is used to indicate cache 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, cache information indication, data length indication, segmentation indication;

[0288] 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 subsequent data is to be sent to the second device after the first data;

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

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

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

[0293] Segment transmission, segment sequence number, total number of segments, and end segment marker.

[0294] Optionally, the method further includes:

[0295] The second device sends third communication content to the first device in the unconnected state, where 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 in at least one of the following processes:

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

[0300] It should be noted that this embodiment is an implementation of the second device corresponding to the embodiment shown in Figure 3. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 3. In order to avoid repeated description, this embodiment will not be repeated.

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

[0302] Example 1:

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

[0304] When there is only one data packet in the current high-layer data transmission, and it is determined that the conditions for single EDT / SDT transmission are met, such as the size of the data packet is lower than the configured threshold, or the link quality meets the threshold, the RRC layer can carry this independent data packet with 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 transmitted in segments, or the link quality does not meet the threshold and multiple attempts may be required, the new message RRC Continuous Data Request can be used to carry high-layer data packets sequentially or in segments.

[0305] When the current high-level data transmission requirement can be clearly indicated to the RRC layer, there may be subsequent continuous data, such as the first UL data, followed by the first downlink data, followed by the second uplink data, and so on. 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-level data packets in sequence. Otherwise, if it cannot be determined or there is no clear indication, the existing RRC Early Data Request message can still be selected to carry the only first UL data;

[0306] Since AIoT devices are a new type of device and their business requirements are very different from those of general terminals, when AIoT devices choose to transmit small uplink data, they can directly select the new message RRC Continuous Data Request to carry high-level data packets in sequence without any additional judgment. Whether there will be subsequent data is determined by other instructions.

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

[0308] For example, the selection of a new message format itself indicates that the transmission is not one-time, and when there is no further clear end marker, it indicates that there will be subsequent data;

[0309] For example, if N small data items have already arrived, or if it can be preliminarily determined that there are N small data items in total based on the type of service initiated, the number of N small data items or a non-end marker can be explicitly notified to indicate N-1 subsequent data items or to indicate that the subsequent data items are not yet finished.

[0310] For example, when the arriving data block is large and needs to be segmented, the segmented data itself needs to carry information such as a sequence number, a non-tail segment identifier, or an indication of the total number of segments due to the need for reassembly, 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 Data Response can also be used to carry corresponding DL data in the scenario of continuous small data transmission, and the End marker or release identifier can be extended in the RRC message. When the identifier is not carried, it means that the configuration on the terminal side can continue to apply. When the network side carries the End marker or release identifier, it means explicit release.

[0312] Next, the RLC layer is used for processing. For AIoT devices, if the data transmission is small, the RLC layer is not necessarily required. RLC TM can be used for transparent transmission, that is, no RLC layer is involved in the transmission. However, if the data needs to be segmented (although the RRC layer can also be segmented, the efficiency is not as high as the RLC layer, so either one can be considered), or if the data has reliability and continuity requirements, the simplified RLC UM or RLC AM method can be considered for processing. If the RLC layer is used, at least one of the following can be considered:

[0313] The functions of UM / AM of the RLC layer, such as segmentation, ARQ or in-order delivery, are all performed in a sequential SN manner. When an AIoT device in IDLE state communicates with the opposite network side or Reader, this embodiment can synchronize the initialization and assignment operations of SN. One feasible way is that when the AIoT device initiates a new small data transmission, the initial SN value of the RLC entity starts from 0, that is, the first data packet SN=0, the second data packet SN=1, and so on, and the same AIoT device serves as the receiving end this time, and the initial value of the SN variable of the receiving entity also starts from 0, that is, the next expected data packet SN=0; Conversely, when the network side or the reader side performs a new small data transmission process with an AIoT device, the initial SN variable of the RLC receiving end also starts from 0, that is, the next expected data packet SN=0, including the first DL data packet of the network side as the sending end performing this small data transmission also SN=0, and then increases in sequence;

[0314] When the AIoT device and the network / Reader complete the transmission of all small data, the RLC entity is deleted, reset, or cleared until the next time there is a need for new small data transmission, and the SN variable is initialized to 0 again.

[0315] Since the SN of the RLC layer is only used for data reassembly, ARQ, sorting and other operations and does not involve secure input, there is no additional requirement for non-duplication. In addition, during a small data transmission process, the AIoT device is restricted from changing the serving cell. Otherwise, the unfinished process will be terminated directly and a new small data transmission process will be restarted in the new cell. Therefore, there is no need for cross-cell processing.

[0316] It can also support multiple different small data transmission processes (also known as service transmission requirements) simultaneously. For example, if the LCID (logical channel identification) is 0, it corresponds to the RLC TM mode, that is, no RLC layer functions are required and the MAC can be directly delivered to the RRC layer. If the LCID is 1, it corresponds to an RLC UM mode transmission. The two ends of the RLC entity, or the RLC transmitting entity and the receiving entity, can maintain the SN variable starting from 0 until the small data transmission is completed. Another LCID of 2 can also correspond to an RLC AM mode transmission. The two ends of the RLC entity, or the RLC transmitting entity and the receiving entity, can maintain the SN variable starting from 0 until the small data transmission is completed. 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 embodiment can be carried out simultaneously) without having to wait for the previous one to end before the next one.

[0317] The biggest difference between the above-mentioned simultaneous operation and traditional terminals is that traditional terminals establish multiple DRBs and multiple RLC entities for transmission at the same time, but the establishment process requires the configuration of RRC dedicated signaling. The terminal needs to establish an RRC connection, activate AS layer security, etc., and establish it on demand. In order to avoid entering the connected state, AIoT devices cannot use dedicated signaling configuration, so a simple agreement can be made in the protocol, LCID 0 transmits data type, RLC parameters, LCID 1 transmits data type, RLC parameters, etc.; AIoT selects it as needed, and after the previous small data transmission is completed, LCID1 is released. When the next small data transmission with similar requirements is initiated, LCID1 can be used again, and released and used cyclically;

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

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

[0320] The MAC layer is responsible for implementing the RACH process, which supports two-step random access (2-step RACH) and four-step random access (4-step RACH). It sends the first small data packet to the network in Msg3 or MsgA, and obtains the uplink synchronization TA and C-RNTI 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 declared successful. The TA and C-RNTI obtained in Msg2 and MsgB of the RACH process are exclusive to the device. The device can use TA as the timing advance for subsequent uplinks, and C-RNTI can be used for subsequent data scheduling.

[0322] For example, after completing the RACH process, the network side can use the C-RNTI to schedule the first downlink data. The downlink data can be a response to the uplink data in the RACH process or independent downlink data. After that, the C-RNTI can be used for subsequent uplink and downlink UE-specific data scheduling until it is implicitly or explicitly released, ending the small data transmission.

[0323] In addition, the MAC layer can further indicate subsequent data, cache reporting, end marker, end indication, etc. through MAC CE or bits in the MAC subheader, which can include the following methods:

[0324] In the MAC subheader or MAC CE, a small number of bits indicate: for example, bits 1 / 0 indicate whether multiple data is being transmitted, and bits 1 / 0 indicate whether it is the last uplink data packet. For example, 2 bits 00 indicate single data transmission, 01 indicates a non-end packet of UL multiple data transmission, 10 indicates the end packet of UL multiple data transmission, and 11 indicates that downlink data is still expected.

[0325] Alternatively, different LCID values ​​may represent different meanings. For example, LCID = 0 represents a single small data transmission scenario, and LCID = 4 represents a multi-data small data transmission scenario.

[0326] Or use more bits to represent buffer size information. For example, the first byte of the MAC subheader carries the LCID or multiple data indication, and the second byte carries the subsequent buffer size information. The buffer size encoding must be an independent table, and the table of ordinary UE cannot be used. Because ordinary UE has a large amount of data, a specially customized AIoT-specific buffer size table is required. In addition, the size of the expected data block can also be indicated. It can also be in an 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, the data block size multiplied by the number can also know the subsequent data volume, and the approximate size of each data packet can be accurately known, which facilitates more flexible scheduling;

[0327] In particular, when the number of subsequent data packets is difficult to judge, for example, when the AIoT device currently sends UL data, it only has a unique small data. After the transmission is successful, it receives DL data, and the corresponding DL data will generate a subsequent UL response. And so on. When the AIoT device continuously sends and receives data, the network side can continuously allocate uplink resources to the AIoT device. Of course, the allocation of uplink resources needs to consider the processing delay after the AIoT device receives the downlink data, the delay in generating uplink data, etc., and allocate according to the recommended or reported data block size;

[0328] 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 inform the network side that there is no more uplink through the End marker indication or the MAC indication of BS=0. The network side can then 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 each release their own stored C-RNTI and other information, clear the timer and cache, etc., and reset each to the initialization state. Explicit release means that the network informs the AIoT device to release this process through an explicit MAC CE or DCI or even RRC.

[0329] After the MAC layer successfully obtains the C-RNTI during the RACH process, it needs to continuously monitor the scheduling of the C-RNTI, obtain uplink and downlink resource scheduling, and send and receive data until the release is successful. Then, the C-RNTI is cleared and the monitoring is abandoned.

[0330] In the process of AIoT devices using their own C-RNTI for exclusive scheduling, there are some abnormal situations that will cause the process to end early. For example, the link quality of the AIoT device is poor due to mobility or network coverage problems, such as RSRP being lower than a certain threshold, or meeting a threshold for the number of consecutive failures. At this time, the AIoT device can release C-RNTI and other timers, status information, etc. on its own, return to the IDLE state, and re-initiate after reselecting the cell as needed; for the network side, it can also be based on the judgment of link quality, or when C-RNTI scheduling accumulates for a period of time or times without any response from the AIoT device side, it is judged that the AIoT device has released itself, and the network side can also release it accordingly;

[0331] The MAC layer also maintains the processing of the HARQ process. Due to the simplicity of AIoT devices, 1-2 HARQ processes are sufficient. One HARQ process can already meet the needs of HARQ feedback, retransmission, and repetition operations. Two HARQ processes can further expand applications. For slightly larger amounts of data or concurrent situations, two HARQ processes can be processed simultaneously to further reduce latency. However, this requires the capabilities of AIoT devices and can be an optional configuration.

[0332] In particular, in this embodiment, the problem of continuous transmission of high-level data is solved. When the AIoT device link is stable and does not involve switching mobility for a period of time, data can be continuously sent and received. Therefore, the basic processes such as the initial registration, attach, NAS context establishment, and NAS security activation of the AIoT device can also be used directly. In this way, the AIoT device can completely remove the RRC connected state (RRC CONNECTED) and complete all small data transmission requirements in the IDLE state, further reducing the complexity of the device and system.

[0333] Example 2:

[0334] This embodiment introduces a method of using MAC PDU (such as the MAC PDU newly defined in the embodiment of this application) to carry high-level small data, further simplifying the processing flow, reducing overhead, and achieving better system efficiency and equipment simplification.

[0335] Since there is no RRC connection established and no AS layer security operations activated during the continuous transmission of small data in the pure IDLE state, the RRC layer's only role is data encapsulation and data routing. If the MAC PDU can be designed to replace this encapsulation and routing function in this embodiment, further layer operations will be simplified.

[0336] Design a MAC PDU that contains at least one or a combination of the following information:

[0337] Data type indication: This field is mainly used to indicate the type of this MAC PDU. If compatibility with the protocol definition is considered, the definition of LCID can be adopted or reused. A special LCID is specified or configured in the protocol for continuous small data transmission of AIoT to carry high-level continuous data of IDLE devices. Of course, because AIoT devices are likely to use different cell / carrier / frequency resources for access than ordinary terminals, AIoT devices can also be specially designed with lower bit overhead, just to distinguish different data types in various transmission scenarios of AIoT devices, such as distinguishing single small data in IDLE state, continuous small data in IDLE state, (continuous) CCCH small data in IDLE state, small data of different bearers / logical channels in INACTIVE state, small data of different bearers / logical channels in CONNECTED state, etc.

[0338] Whether there is 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 number of existing (subsequent) data packets, the expected data packet size, the expected resource block size, and other information, or a combination thereof, in order to facilitate the network side to better judge the data arrival of the AIoT device, thereby providing scheduling resources that better meet the needs;

[0339] The Length Indicator (LI) field is used to indicate the size of the higher-layer payload contained in the MAC PDU, typically in bytes. For small data, a large size is not necessary. This field is not mandatory or guaranteed to be present. For simple services that allow for good data block shaping, i.e., when the data size is agreed upon, the LI can be omitted, simplifying the packetization instructions through agreement between the terminal and the base station.

[0340] The payload part of the data block is the high-level valid data (such as the first data and the second data mentioned above), which is generally arranged in whole bytes;

[0341] In particular, if the segmentation function is to be supported and compatible with scenarios where the higher-layer data is larger than the resource block size, the segmentation function must also be supported, and fields such as segment indication, segment sequence number, total number of segments, and tail segment flag must be introduced to support segmented transmission.

[0342] In this embodiment of the MAC PDU, since the packetization and processing of the RRC layer are omitted, the RLC layer can also be omitted because it is located above the MAC, thereby reducing the number of layers and increasing efficiency.

[0343] As listed in the first embodiment, the content of the MAC layer processing part, in addition to the packet assembly, the content of the MAC layer transmission control is basically also applicable to this embodiment and will not be repeated here.

[0344] Example 3:

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

[0346] For the RRC layer, operations may be performed based on at least one of the following principles:

[0347] When there is only one data packet in the current high-level data transmission, and it is determined that the conditions for single EDT / SDT transmission are met, such as the size of the data packet is lower than the configured threshold, or the link quality meets the threshold, the RRC layer can carry this independent data packet with 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 transmitted in segments, or the link quality does not meet the threshold and may require multiple attempts, the message RRC Early Data Request can also be used to carry high-level data packets in sequence or in segments. In particular, a special RAI indication is added by the RRC layer or a special RAI / BSR / End marker indication is added by the MAC layer to distinguish it from the case of a single data packet, informing the network side that there is subsequent data and it cannot be released immediately.

[0348] When the current high-level data transmission requirement can be clearly indicated to the RRC layer, there may be subsequent continuous data, such as the first UL data, followed by the first downlink data, followed by the second uplink data, and so on. This exceeds the existing maximum transmission scale of one uplink data plus one downlink data. Therefore, the RRC Early Data Request message can be used to carry high-level data packets in sequence;

[0349] Since AIoT devices are a new type of device and their business requirements are very different from those of general terminals, when AIoT devices choose to transmit small uplink data, they can directly use the RRC Early Data Request message to carry high-level data packets in sequence without any additional judgment. As for whether there will be subsequent data, it will be determined through other instructions. Or, at this time, the agreement between the AIoT device and the network side is that there will be subsequent data by default, and it is necessary to wait for a clear end marker / RAI / BSR indication before it ends.

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

[0351] For example, although the existing message format is selected, special agreements are made for AIoT scenarios, with non-one-time transmission as the default, and when there is no further clear end marker identification, it indicates that there is subsequent data;

[0352] For example, if N small data items have already arrived, or if it can be preliminarily determined that there are N small data items in total based on the type of service initiated, the number of N small data items or a non-end marker can be explicitly notified to indicate N-1 subsequent data items or to indicate that the subsequent data items are not yet finished.

[0353] For example, if the arriving data block is large and needs to be segmented, the segmented data itself needs to carry information such as a sequence number, a non-last segment identifier, or an indication of the total number of segments for the purpose of reassembly, indicating N-1 subsequent segmented data, or indicating that the subsequent segmented data has not yet ended;

[0354] Of course, the combined use of RRC Early Data Request and RRC Continuous Data Request is not ruled out. For example, when there is only one data in the cache, the RRC Early Data Request message is encapsulated, but after the network side receives it, the AIoT device can also be configured to continue, unless an explicit single data or end indication is received. When there are multiple data to be transmitted in the cache, RRC Continuous Data Request is used, which also explicitly informs the network side to a certain extent that there must be subsequent data.

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

[0356] Alternatively, for downlink, the message formats RRC Early Data Request and RRC Continuous Data Request can be used together to carry 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;

[0357] In this embodiment, since the high-layer data is encapsulated at the RRC layer, the processing at the RLC layer and the processing at the MAC layer in the first embodiment are still applicable and will not be described in detail here.

[0358] The above embodiment provides a multi-data transmission method for AIoT devices, which allows AIoT devices to avoid state conversion and perform multi-data transmission, ensuring the feasibility and efficiency of transmission, expanding coverage, and reducing the complexity and power consumption of AIoT devices and improving system efficiency while ensuring transmission effects.

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

[0360] The data transmission method provided in the embodiment of the present application can be executed by a data transmission device. In the embodiment of the present application, the data transmission method performed by a data transmission device is taken as an example to illustrate the data transmission device provided in the embodiment of the present application.

[0361] Please refer to FIG5 , which is a structural diagram of a data transmission device provided in an embodiment of the present application. As shown in FIG5 , the data transmission device 500 includes:

[0362] The first sending module 501 is configured to send first communication content to a second device in a non-connected state, where the first communication content carries first data and indicates that subsequent data to be sent to the second device is to follow the first data.

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

[0364] Radio Resource Control RRC message, Media Access Control MAC Protocol Data Unit PDU.

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

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

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

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

[0369] Optionally, the device further includes:

[0370] The second sending module is 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:

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

[0372] No subsequent data is to be sent to the second device after the second data.

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

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

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

[0376] 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, wherein the target condition includes at least one of the following:

[0377] There are multiple data in the high-level data;

[0378] High-level data needs to be transmitted in segments;

[0379] The high-level data has only one data, and the size of the data is greater than a preset threshold;

[0380] The link quality is the preset quality;

[0381] The RRC layer or the MAC layer receives an indication that there is a possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication that there is continuous data transmission.

[0382] Optionally, the device further includes:

[0383] A third sending module is used 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 downlink.

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

[0385] When the RRC layer of the first device obtains a target determination result, the first communication content is sent to the second device in a non-connected state, wherein the target determination result includes at least one of the following:

[0386] Determining, based on the data that has arrived at the RRC layer, that the service transmission requirement is multiple data transmission;

[0387] Determining that segmented transmission is required based on data that has arrived at the RRC layer;

[0388] Determining whether there is subsequent data transmission based on the service type or the indication received by the RRC layer;

[0389] It is not possible to determine whether there will be subsequent data transmission based on the service type or the indication received by the RRC layer.

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

[0391] the format of the first communication content;

[0392] Information about the number of data items carried by the first communication content, where the information about the number of data items is represented as a plurality of data items;

[0393] a non-end marker carried by the first communication content;

[0394] The data segment information carried by the first communication content.

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

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

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

[0398] The first communication content is transmitted in a transparent transmission mode TM, an acknowledgement mode AM or an unacknowledgement mode UM;

[0399] Transmitting the first data carried by the first communication content in segments;

[0400] Multiple business transmission demands are carried out simultaneously, and the multiple business transmission demands include the business transmission demand to which the first data belongs.

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

[0402] Optionally, when the service transmission requirement corresponding to the RLC entity is transmitted, performing one of the following processes on the RLC entity:

[0403] Delete, reset, clear.

[0404] Optionally, when 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.

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

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

[0407] The device further comprises:

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

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

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

[0411] Cache information.

[0412] Optionally, the MAC CE or MAC subheader carries at least one of the following:

[0413] First indication bit, LCID, second indication bit;

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

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

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

[0417] Optionally, when the first device has no more data to transmit 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 completed.

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

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

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

[0421] The data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

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

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

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

[0425] The segment indication is used to indicate at least one of the following:

[0426] Segment transmission, segment sequence number, total number of segments, and end segment marker.

[0427] Optionally, the device further includes:

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

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

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

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

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

[0433] The above-mentioned data transmission device can improve the transmission performance of the equipment.

[0434] 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 of an electronic device, such as an integrated circuit or chip. For example, the electronic device may be a terminal, or may be a device other than a terminal. For example, the terminal may include, but is not limited to, the types of terminals listed in the embodiments of the present application, and the other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0435] The data transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0436] Please refer to FIG6 , which is a structural diagram of another data transmission device provided in an embodiment of the present application. As shown in FIG6 , the data transmission device 600 includes:

[0437] The first receiving module 601 is 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 indicates that subsequent data will be sent to the second device after the first data.

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

[0439] RRC message, MAC PDU.

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

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

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

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

[0444] Optionally, the device further includes:

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

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

[0447] No subsequent data is to be sent to the second device after the second data.

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

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

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

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

[0452] the format of the first communication content;

[0453] Information about the number of data items carried by the first communication content, where the information about the number of data items is represented as a plurality of data items;

[0454] a non-end marker carried by the first communication content;

[0455] The data segment information carried by the first communication content.

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

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

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

[0459] receiving a message 3 Msg3 or a message AMsgA in a random access process sent by a first device in a non-connected state, wherein the Msg3 or MsgA carries the first data;

[0460] The device further comprises:

[0461] The second sending module is used to send message 2 Msg2 or message BMsgB 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 identifier C-RNTI.

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

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

[0464] Cache information.

[0465] Optionally, the MAC CE or MAC subheader carries at least one of the following:

[0466] First indication bit, LCID, second indication bit;

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

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

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

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

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

[0472] The data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

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

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

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

[0476] The segment indication is used to indicate at least one of the following:

[0477] Segment transmission, segment sequence number, total number of segments, and end segment marker.

[0478] Optionally, the device further includes:

[0479] The first sending module is 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:

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

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

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

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

[0484] The above-mentioned data transmission device can improve the transmission performance of the equipment.

[0485] The data transmission device in the embodiment of the present application can 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 can be a terminal or a network-side device.

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

[0487] Optionally, as shown in Figure 7, an embodiment of the present application also provides a communication device 700, including a processor 701 and a memory 702, and the memory 702 stores programs or instructions that can be run on the processor 701. For example, when the communication device 700 is a first device, the program or instruction is executed by the processor 701 to implement the various steps of the above-mentioned data transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0488] An embodiment of the present application also provides a communication device, including a processor and a communication interface, wherein the communication interface is configured to send a first communication content to a second device in a non-connected state, wherein the first communication content carries first data, and the first communication content is further configured to indicate that subsequent data is to be sent to the second device after the first data. This communication device embodiment corresponds to the aforementioned data transmission method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this communication device embodiment and can achieve the same technical effects.

[0489] Specifically, FIG8 is a schematic diagram of the hardware structure of a device for implementing an embodiment of the present application.

[0490] The device 800 includes but is not limited to: 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 at least some of the components of the processor 810.

[0491] Those skilled in the art will appreciate that device 800 may also include a power source (such as a battery) to power various components. The power source may be logically connected to processor 810 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The device structure shown in FIG8 does not limit the device. The device may include more or fewer components than shown, or may combine certain components or arrange the components differently, which will not be described in detail here.

[0492] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and 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 a touch panel 8071 and at least one of 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. 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 repeated here.

[0493] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, 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, and the like.

[0494] 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, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 809 may include a volatile memory or a non-volatile memory, or the memory 809 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0495] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0496] In this embodiment, the above device is a first device, and the first device is specifically used as a terminal for example:

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

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

[0499] Radio Resource Control RRC message, Media Access Control MAC Protocol Data Unit PDU.

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

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

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

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

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

[0505] Sending 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:

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

[0507] No subsequent data is to be sent to the second device after the second data.

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

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

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

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

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

[0513] There are multiple data in the high-level data;

[0514] High-level data needs to be transmitted in segments;

[0515] The high-level data has only one data, and the size of the data is greater than a preset threshold;

[0516] The link quality is the preset quality;

[0517] The RRC layer or the MAC layer receives an indication that there is a possibility of continuous data transmission, or the RRC layer or the MAC layer receives an indication that there is continuous data transmission.

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

[0519] When the first device determines that the target condition is not met, a third communication content is sent to the 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 downlink.

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

[0521] When the RRC layer of the first device obtains a target determination result, the first communication content is sent to the second device in a non-connected state, wherein the target determination result includes at least one of the following:

[0522] Determining, based on the data that has arrived at the RRC layer, that the service transmission requirement is multiple data transmission;

[0523] Determining that segmented transmission is required based on data that has arrived at the RRC layer;

[0524] Determining whether there is subsequent data transmission based on the service type or the indication received by the RRC layer;

[0525] It is not possible to determine whether there will be subsequent data transmission based on the service type or the indication received by the RRC layer.

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

[0527] the format of the first communication content;

[0528] Information about the number of data items carried by the first communication content, where the information about the number of data items is represented as a plurality of data items;

[0529] a non-end marker carried by the first communication content;

[0530] The data segment information carried by the first communication content.

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

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

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

[0534] The first communication content is transmitted in a transparent transmission mode TM, an acknowledgement mode AM or an unacknowledgement mode UM;

[0535] Transmitting the first data carried by the first communication content in segments;

[0536] Multiple business transmission demands are carried out simultaneously, and the multiple business transmission demands include the business transmission demand to which the first data belongs.

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

[0538] Optionally, when the service transmission requirement corresponding to the RLC entity is transmitted, performing one of the following processes on the RLC entity:

[0539] Delete, reset, clear.

[0540] Optionally, when 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.

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

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

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

[0544] In a non-connected state, a message 2 Msg2 or a message BMsgB in a random access process is received through the MAC layer, where the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or a cell radio network temporary identifier C-RNTI.

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

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

[0547] Cache information.

[0548] Optionally, the MAC CE or MAC subheader carries at least one of the following:

[0549] First indication bit, LCID, second indication bit;

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

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

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

[0553] Optionally, when the first device has no more data to transmit 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 completed.

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

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

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

[0557] The data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

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

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

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

[0561] The segment indication is used to indicate at least one of the following:

[0562] Segment transmission, segment sequence number, total number of segments, and end segment marker.

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

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

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

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

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

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

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

[0570] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned data transmission method and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0571] It should be noted that the above-mentioned device can also implement the steps in the method shown in FIG. 4 , or can implement the method executed by each module shown in FIG. 6 .

[0572] The present application also provides an embodiment of a device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG4 . This network-side device embodiment corresponds to the aforementioned data transmission method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this device embodiment and can achieve the same technical effects.

[0573] An embodiment of the present application also provides a device, including a processor and a communication interface, wherein 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 also used to indicate that subsequent data is to be sent to the second device after the first data.

[0574] Specifically, embodiments of the present application also provide a device. As shown in Figure 9, device 900 includes an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

[0575] The data transmission method in the above embodiment may be implemented in the baseband device 93 , which includes a baseband processor.

[0576] The baseband device 93 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, 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 network device operations shown in the above method embodiment.

[0577] The device may further include a network interface 96, such as a Common Public Radio Interface (CPRI).

[0578] Specifically, the device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and executable on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute the methods executed by the modules shown in FIG6 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0579] In this embodiment, the above device is the second device, and the second device is specifically used as a network-side device for example.

[0580] The radio frequency device 92 is used to receive first communication content sent by a first device in a non-connected state, where the first communication content carries first data and is also used to indicate that subsequent data will be sent to the second device after the first data.

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

[0582] RRC message, MAC PDU.

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

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

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

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

[0587] 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:

[0588] The second device receives second communication content sent by the first device in the unconnected state, where the second communication content carries second data and is further used to indicate:

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

[0590] No subsequent data is to be sent to the second device after the second data.

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

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

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

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

[0595] the format of the first communication content;

[0596] Information about the number of data items carried by the first communication content, where the information about the number of data items is represented as a plurality of data items;

[0597] a non-end marker carried by the first communication content;

[0598] The data segment information carried by the first communication content.

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

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

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

[0602] receiving a message 3 Msg3 or a message AMsgA in a random access process sent by a first device in a non-connected state, wherein the Msg3 or MsgA carries the first data;

[0603] Radio frequency device 92:

[0604] Sending message 2 Msg2 or message BMsgB 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 identifier C-RNTI.

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

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

[0607] Cache information.

[0608] Optionally, the MAC CE or MAC subheader carries at least one of the following:

[0609] First indication bit, LCID, second indication bit;

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

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

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

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

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

[0615] The data type indication is used to indicate the type of service transmission requirement to which the first data belongs;

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

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

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

[0619] The segment indication is used to indicate at least one of the following:

[0620] Segment transmission, segment sequence number, total number of segments, and end segment marker.

[0621] Optionally, the radio frequency device 92:

[0622] Sending third communication content to the first device in the unconnected state, where the third communication content carries third data, and the third communication content is further used to indicate:

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

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

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

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

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

[0628] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0629] It should be noted that the above-mentioned device can also implement the steps in the method shown in FIG3 , or can implement the method executed by each module shown in FIG5 .

[0630] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0632] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0633] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0634] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned data transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0635] An embodiment of the present application further provides a wireless communication system, including: a first device and a second device, wherein the first device can be used to execute the steps of the data transmission method on the first device side provided in the embodiment 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 embodiment of the present application.

[0636] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

[0638] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A data transmission method, wherein, 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 Medium 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, wherein 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, wherein 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 one piece of data in the uplink or downlink.

8. The method according to any one of claims 1 to 4, wherein, 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 determined that the service transmission requirement is multi-data transmission; Based on the data that has reached the RRC layer, it is determined 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, wherein, 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 by the first communication content, and the number-of-data information is represented as multiple data; The non-ending flag carried by the first communication content; The data segmentation information carried by the first communication content.

10. The method according to claim 9, wherein, 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, wherein The radio link control (RLC) layer of the first device performs at least one of the following transmission processes: Transmit the first communication content in transparent mode (TM), acknowledged mode (AM), or unacknowledged mode (UM); Perform segmented transmission on the first data carried by 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 transfers the first data and the subsequent data of the first data in the order of sequence number (SN), where the initial value of SN is 0.

13. The method according to claim 12, wherein, 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, wherein, 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, wherein, 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 the 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 the Msg2 or MsgB carries at least one of uplink synchronization adjustment information or cell radio network temporary identifier (C-RNTI).

16. The method according to any one of claims 1 to 15, wherein, 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: First indication bit, LCID, 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, wherein, 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.

19. The method according to any one of claims 1 to 18, wherein 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, wherein In the 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; Among them, 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, segment sequence number, total number of segments, end segment flag.

21. The method according to any one of claims 1 to 20, wherein, 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, wherein, 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, wherein, 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, Medium Access Control (MAC) Protocol Data Unit (PDU).

25. The method according to claim 23 or 24, wherein, 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, wherein 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, and the data number information represents multiple data; The non-ending mark 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, wherein 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 identity (C-RNTI).

28. The method according to any one of claims 23 to 27, wherein 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, wherein 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, tail segment flag.

30. The method according to any one of claims 23 to 29, wherein 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, wherein, 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, wherein, 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 apparatus according to claim 32, wherein, 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, wherein 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 apparatus according to claim 34, wherein, 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 downlink.

36. The device according to any one of claims 32 to 35, wherein, 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, wherein, 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 apparatus 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, wherein, 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. An apparatus, wherein, Comprises a processor and a memory, where the memory stores a program or instructions that can run on the processor, and when the program or instructions are executed by the processor, the steps of the data transmission method according to any one of claims 1 to 22 are implemented, or when the program or instructions are executed by the processor, the steps of the data transmission method according to any one of claims 23 to 31 are implemented.

41. A readable storage medium, wherein, The program or instructions are stored on the readable storage medium, and when the program or instructions are executed by the processor, the steps of the data transmission method according to any one of claims 1 to 22 are implemented, or the steps of the data transmission method according to any one of claims 23 to 31 are implemented.

Images