Data transmission method, apparatus and system

Abstract

The embodiments of the present application relate to the technical field of communications. Provided are a data transmission method, apparatus and system. The method comprises: a terminal device receiving first configuration information from a network device, wherein the first configuration information is used by the terminal device to perform initial data transmission, or is used by the terminal device to perform subsequent data transmission after executing the initial data transmission; and the terminal device sending data to the network device on the basis of the first configuration information in an RRC inactive state. The first configuration information received by the terminal device can indicate the initial data transmission of the terminal device, and can also indicate the subsequent data transmission of the terminal device after the initial data transmission is performed. When the first configuration information comprises uplink grant resources, the network device can flexibly configure the uplink grant resources for the terminal device as needed, and a process does not need to be triggered repeatedly for multiple data transmissions, thereby reducing the number of pieces of air interface signaling, and enhancing the system capacity of an uplink.

Description

Data transmission method, device and system

[0001] The present application claims priority to the Chinese patent application No. 202410411588.3, filed on April 7, 2024, and entitled "A data transmission method, device and system", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a data transmission method, device and system. BACKGROUND

[0003] In the internet of things (IoT), 5th generation mobile communication technology (5G) and subsequent evolved system architecture such as 6G, non-terrestrial network (NTN) technology is introduced, which can provide seamless coverage for terminal devices by deploying base stations or part of base station functions on non-ground network devices such as high-altitude platforms or satellites, especially in places where it is impossible to deploy base stations such as the sea, desert and air, thereby improving the reliability of the system. However, in narrow band internet of things (NB-IoT), the uplink of NTN is affected by the large signaling overhead of the corresponding system downlink and the tight coupling between the downlink signaling.

[0004] Currently, the early data transmission (EDT) and preconfigured uplink resource (PUR) are usually used to improve the efficiency and response speed of data transmission in wireless communication systems. Among them, EDT allows terminal devices to send data based on the scheduling instruction included in the random access response, while PUR allows terminal devices to use preconfigured resources for data transmission without receiving scheduling instructions. However, when multiple data transmissions are involved, multiple EDT and PUR need to be initiated, resulting in a large amount of air signaling transmission and affecting the data transmission efficiency of the system. SUMMARY

[0005] The present application provides a data transmission method, device and system, which configures preconfigured uplink resources or configured grant resources for terminal devices by network devices, so that terminal devices do not need to trigger the process multiple times when performing multiple uplink data transmissions, thereby reducing the number of air signaling and enhancing the capacity of the uplink of narrow band internet of things non-terrestrial network.

[0006] The technical solutions are as follows:

[0007] In a first aspect, an embodiment of the present application provides a data transmission method, which comprises the following steps: a terminal device receives first configuration information from a network device, the first configuration information being used for the terminal device to perform initial data transmission or subsequent data transmission after performing the initial data transmission; and the terminal device transmits data to the network device according to the first configuration information in an RRC non-connected state.

[0008] In the prior art, the preconfigured uplink resource and the early data transmission are both for small packet data transmission in an RRC_IDLE state. For the preconfigured uplink resource, it is small packet data transmission without a physical random access channel, and the preconfigured uplink resource can be initiated only in a last serving cell. For the early data transmission, random access can be initiated in any cell supporting the early data transmission to perform the early data transmission. However, one early data transmission and one preconfigured uplink resource support only one uplink data transmission and optional one downlink data transmission. If the terminal device needs to perform multiple uplink data transmissions, the terminal device needs to initiate the preconfigured uplink resource and the early data transmission multiple times, resulting in a large amount of air interface signaling transmission. In the data transmission method provided by the embodiment of the present application, the first configuration information received by the terminal device can indicate initial data transmission of the terminal device or subsequent data transmission of the terminal device after the initial data transmission. The terminal device transmits data in the RRC non-connected state according to the first configuration information. In this way, the network device flexibly configures uplink grant resources for the terminal device on demand, multiple data transmissions do not need to trigger the process multiple times, the number of air interface signaling is reduced, and the system capacity of the uplink is enhanced.

[0009] In a possible implementation, the method provided by the embodiment of the present application further comprises the following steps: the terminal device receives the first configuration information from the network device through a system message, the first configuration information comprising one or more uplink grant resources, each of the one or more uplink grant resources corresponding to one radio network temporary identifier, or corresponding to one or more geographical areas, or corresponding to one or more beams. This facilitates the terminal device to perform initial data transmission and optional subsequent data transmission directly according to the first configuration information.

[0010] In a possible implementation, in the case where the first configuration information comprises the uplink grant resource, before the terminal device receives the first configuration information from the network device, the method provided by the embodiment of the present application comprises the following steps: the terminal device receives random access resources from the network device through a system message, the random access resources being used for the terminal device to acquire the first configuration information based on random access. The terminal device transmits data to the network device for the first time. In this way, the preconfigured uplink resource based on random access can be implemented.

[0011] In a possible implementation, the method provided by the embodiment of the present application includes: a terminal device receiving first indication information from a network device through a system message, the first indication information including information for indicating a condition for determining whether to trigger preconfigured uplink resource based random access, and / or information for indicating a search space or a timer for monitoring a physical downlink control channel. The terminal device can determine whether to trigger preconfigured uplink resource based random access.

[0012] In a possible implementation, before the terminal device acquires an uplink grant resource based on random access, the method provided by the embodiment of the present application further includes: the terminal device receiving a first message from the network device. The first message is used to indicate that the terminal device enters an RCC idle state, and the first message does not include first configuration information.

[0013] In a possible implementation, the terminal device acquires an uplink grant resource based on random access, and the method provided by the embodiment of the present application further includes: the terminal device indicating a subsequent data transmission requirement, including: the terminal device receiving an uplink grant resource in a random access response received from the network device, the terminal device sending a second message to the network device based on the uplink grant resource, the second message including a buffer status report or subsequent data transmission request information indicated by the terminal device, wherein the second message is used for initial data transmission. Alternatively, the terminal device sends a buffer status report to the network device using a medium access control channel unit. Alternatively, after receiving a response for conflict resolution from the network device, the terminal device sends user equipment assistance information to the network device.

[0014] In a possible implementation, in a case where the uplink grant resource included in the first configuration information is a configured grant resource, the terminal device performs subsequent data transmission after performing initial data transmission, including: in a case where the terminal device performs data transmission based on a control plane, the terminal device sends an uplink information transfer message or an RRC early data request message without carrying a service temporary mobile user identifier to the network device. Alternatively, in a case where the terminal device performs data transmission based on a user plane, the terminal device sends data to the network device, or sends an RRC connection resume request message, and the RRC connection resume request message does not carry a first identifier, the first identifier being used by the network device to identify a terminal device context corresponding to the terminal device. Data transmission can be implemented on the control plane and the user plane respectively.

[0015] In a possible implementation, in a case where the one or more uplink grant resources included in the first configuration information are configured grant resources, the method provided by the embodiments of the present application includes: the terminal device receives second indication information from the network device, the second indication information being used for indicating one or more of the following: one or more cell identities corresponding to the first configured grant resource of the terminal device, or a radio network temporary identifier corresponding to the first configured grant resource, or a radio network temporary identifier used for data retransmission corresponding to the first configured grant resource, or a time advance validity condition, or a condition for the terminal device to judge and trigger data transmission in the RRC non-connected state, or a search space for the terminal device to listen to a physical downlink control channel or a timer. The first configured grant resource is one of the one or more uplink grant resources.

[0016] In a possible implementation, the method provided by the embodiments of the present application includes: the terminal device receives an initial data transmission response from the network device, the initial data transmission response being one of the following: downlink data, or received physical layer acknowledgement information or downlink control information of a physical downlink control channel addressed to a radio network temporary identifier, or received physical layer acknowledgement information or downlink control information of a physical downlink control channel addressed to a cell radio network temporary identifier, or downlink control information of a physical downlink control channel addressed to a radio network temporary identifier used for data retransmission.

[0017] In a possible implementation, in a case where the terminal device performs subsequent data transmission after performing initial data transmission, the method provided by the embodiments of the present application further includes: the terminal device receives a dynamic grant from the network device. The terminal device sends data to the network device according to the dynamic grant. This facilitates the terminal device to perform subsequent data transmission in advance of data transmission.

[0018] In a second aspect, the embodiments of the present application provide a data transmission method, which includes: a network device sends first configuration information to a terminal device, the first configuration information being used for the terminal device to perform initial data transmission or the terminal device to perform subsequent data transmission after performing initial data transmission. The network device receives data sent by the terminal device in the RRC non-connected state.

[0019] In a possible implementation, the method provided by the embodiments of the present application includes: a network device sends first configuration information to a terminal device, the first configuration information including one or more uplink grant resources, each of the one or more uplink grant resources corresponding to one radio network temporary identifier, or one or more geographical areas, or one or more beams.

[0020] In a possible implementation, in the case that the first configuration information comprises the uplink grant resource, before the network device sends the first configuration information to the terminal device, the method provided by the embodiment of the application comprises: the network device sends random access resource to the terminal device, the random access resource being used for the terminal device to acquire the uplink grant resource based on random access. The network device receives data sent by the terminal device for the first time.

[0021] In a possible implementation, the method provided by the embodiment of the application comprises: the network device sends first indication information to the terminal device, the first indication information being used for indicating a condition for judging a trigger of the preconfigured uplink resource, and / or being used for indicating a search space or a timer for listening to a physical downlink control channel.

[0022] In a possible implementation, before the terminal device acquires the uplink grant resource based on random access, the method provided by the embodiment of the application further comprises: the network device sends a first message to the terminal device, the first message being used for indicating that the terminal device enters an RCC idle state, and the first message not comprising the first configuration information.

[0023] In a possible implementation, the terminal device acquires the uplink grant resource based on random access, and the method provided by the embodiment of the application further comprises: the network device receives a second message sent by the terminal device based on the uplink grant resource, the second message comprising terminal device indication buffer status report or subsequent data transmission request information, wherein the second message is used for initial data transmission. Alternatively, the network device receives a buffer status report sent by the terminal device using a medium access control channel unit. Alternatively, after the network device accepts a response of conflict resolution, the network device receives user equipment auxiliary information from the terminal device.

[0024] In a possible implementation, in the case that the uplink grant resource comprised in the first configuration information is a configured grant resource, the terminal device performs subsequent data transmission after performing initial data transmission, comprising: in the case that the terminal device performs control plane-based data transmission, the network device receives an uplink information transmission message from the terminal device, or an RRC early data request message not carrying a service temporary mobile user identifier. Alternatively, in the case that the terminal device performs control plane-based data transmission, the network device receives data from the terminal device, or an RRC connection recovery request message, the RRC connection recovery request message not carrying a first identifier, the first identifier being used for the network device to identify a terminal device context corresponding to the terminal device.

[0025] In a possible implementation, in a case where the one or more uplink grant resources comprised in the first configuration information are configured grant resources, the method provided by the embodiments of the present application comprises: the network device sending second indication information to the terminal device, the second indication information being used for indicating one or more of the following: one or more cell identities corresponding to the first configured grant resources, or a radio network temporary identifier corresponding to the first configured grant resources, or a radio network temporary identifier RNTI corresponding to the first configured grant resources and used for data retransmission, or a time advance validity condition, or a condition for the terminal device to judge and trigger data transmission in the RRC non-connected state, or a search space for the terminal device to listen to a physical downlink control channel or a timer. The first configured grant resource is one of the one or more uplink grant resources.

[0026] In a possible implementation, the method provided by the embodiments of the present application further comprises: the network device sending an initial data transmission response to the terminal device, the initial data transmission response being one of the following: downlink data, or physical layer acknowledgement information or downlink control information of a physical downlink control channel addressed to a radio network temporary identifier, or physical layer acknowledgement information or downlink control information of a physical downlink control channel addressed to a cell radio network temporary identifier, or downlink control information of a physical downlink control channel addressed to a radio network temporary identifier for data retransmission.

[0027] In a possible implementation, in a case where the terminal device performs subsequent data transmission after performing initial data transmission, the method provided by the embodiments of the present application comprises: the network device sending a dynamic grant to the terminal device. The network device receives data subsequently sent by the terminal device.

[0028] In a third aspect, the embodiments of the present application provide a data transmission apparatus, which can implement the method in the first aspect or any possible implementation manner of the first aspect, and thus can achieve the beneficial effects of the first aspect or any possible implementation manner of the first aspect. The communication apparatus can be a terminal device, or a device supporting the terminal device to implement the method in the first aspect or any possible implementation manner of the first aspect, for example, a chip applied to the terminal device. The apparatus can implement the above method by software, hardware, or by hardware executing corresponding software.

[0029] In an example, the data transmission apparatus is a terminal device or a chip or chip system applied in the terminal device, and the apparatus comprises a communication module and a processing module, wherein the communication module is configured to receive or send information / data, and the processing module is configured to process the information / data. The communication module is configured to receive first configuration information from a network device, and the first configuration information is used for initial data transmission of the terminal device or subsequent data transmission of the terminal device after performing the initial data transmission. The processing module is configured to send data to the network device according to the first configuration information in an RRC non-connected state.

[0030] In a possible implementation, the communication module is configured to receive the first configuration information from the network device. The first configuration information comprises one or more uplink grant resources, each of the one or more uplink grant resources corresponds to one radio network temporary identifier, or corresponds to one or more geographical areas, or corresponds to one or more beams.

[0031] In a possible implementation, in a case where the first configuration information comprises the uplink grant resource, before the terminal device receives the first configuration information from the network device, the communication module is configured to receive random access resources from the network device. The random access resources are used for the terminal device to acquire the uplink grant resource based on random access. The communication module is further configured to initially send data to the network device.

[0032] In a possible implementation, the communication module is configured to receive first indication information from the network device. The first indication information comprises a condition for indicating that the uplink grant resource is acquired based on random access, and / or a search space or a timer for indicating that a physical downlink control channel is listened to.

[0033] In a possible implementation, the communication module is configured to receive a first message from the network device. The first message is used for indicating that the terminal device enters an RCC idle state, and the first message does not comprise the first configuration information.

[0034] In a possible implementation, the communication module is configured to indicate a subsequent data transmission requirement. The processing module is configured to send a second message to the network device based on the uplink grant resource. The second message comprises terminal device indication buffer status reporting or subsequent data transmission request information, and the second message is used for initial data sending. Alternatively, the processing module is configured to send the buffer status reporting to the network device using a medium access control channel unit. Alternatively, the processing module is configured to send user equipment auxiliary information to the network device after accepting a response of conflict resolution from the network device.

[0035] In a possible implementation, in a case where the terminal device performs control plane based data transmission, the communication module is configured to send an uplink information transfer message or an RRC early data request message without carrying a service temporary mobile user identity to the network device. Alternatively, in a case where the terminal device performs user plane based data transmission, the communication module is configured to send data to the network device or send an RRC connection resume request message without carrying a first identity, which is used by the network device to identify a terminal device context corresponding to the terminal device.

[0036] In a possible implementation, in a case where the one or more uplink grant resources included in the first configuration information are configured grant resources, the communication module is configured to receive second indication information from the network device. The second indication information is used to indicate one or more of the following: one or more cell identities corresponding to the first configured grant resource of the terminal device, or a radio network temporary identity corresponding to the first configured grant resource, or a radio network temporary identity used for data retransmission corresponding to the first configured grant resource, or a time advance validity condition, or a condition for the terminal device to judge and trigger data transmission in an RRC non-connected state, or a search space for the terminal device to monitor a physical downlink control channel or a timer. The first configured grant resource is one of the one or more uplink grant resources.

[0037] In a possible implementation, the communication module is configured to receive an initial data transmission response from the network device. The initial data transmission response can be: downlink data, or a physical layer acknowledgement information or a physical downlink control channel downlink control information addressed to the radio network temporary identity, or a physical layer acknowledgement information or a physical downlink control channel downlink control information addressed to a cell radio network temporary identity, or a physical downlink control channel downlink control information addressed to a radio network temporary identity for data retransmission.

[0038] In a possible implementation, in a case where the terminal device performs subsequent data transmission after performing initial data transmission, the communication module is configured to receive a dynamic grant from the network device. The processing module is configured to send data to the network device according to the dynamic grant.

[0039] In a fourth aspect, an embodiment of the present application provides a data transmission apparatus, which can implement the method in the second aspect or any possible implementation manner of the second aspect, and thus can achieve the beneficial effects of the second aspect or any possible implementation manner of the second aspect. The communication apparatus can be a network device, or an apparatus that supports the network device to implement the method in the second aspect or any possible implementation manner of the first aspect, for example, a chip applied to the network device. The apparatus can implement the above method by software, hardware, or by hardware executing corresponding software.

[0040] In an example, the data transmission apparatus is a network device or a chip or chip system applied in the network device, the apparatus comprises a communication module and a processing module, wherein the communication module is configured to receive or send information / data, and the processing module is configured to process the information / data. The communication module is configured to send first configuration information to a terminal device, the first configuration information being used for the terminal device to perform initial data transmission or subsequent data transmission after performing initial data transmission. The communication module is further configured to receive data sent by the terminal device in an RRC non-connected state.

[0041] In a possible implementation, the communication module is configured to send the first configuration information to the terminal device, the first configuration information comprising one or more uplink grant resources, each of the one or more uplink grant resources corresponding to one radio network temporary identifier, or one or more geographical areas, or one or more beams.

[0042] In a possible implementation, in the case that the first configuration information comprises the uplink grant resource, before the terminal device receives the first configuration information from the network device, the communication module is configured to send random access resources to the terminal device, the random access resources being used for the terminal device to acquire the uplink grant resource based on random access. The communication module is further configured to receive data sent by the terminal device for the first time.

[0043] In a possible implementation, the communication module is configured to send first indication information to the terminal device, the first indication information being used to indicate a condition for judging a trigger of the preconfigured uplink resource, and / or being used to indicate a search space or a timer for monitoring a physical downlink control channel.

[0044] In a possible implementation, the communication module is configured to send a first message to the terminal device, the first message being used to indicate that the terminal device enters an RRC idle state, and the first message does not comprise the first configuration information.

[0045] In a possible implementation, the communication module is configured to receive a second message sent by the terminal device based on the uplink grant resource, the second message comprising buffer status report or subsequent data transmission request information indicated by the terminal device, wherein the second message is used for initial data transmission. Alternatively, the communication module is configured to receive a buffer status report sent by the terminal device using a medium access control channel unit. Alternatively, after receiving a response of conflict resolution from the network device, the communication module is configured to receive user equipment assistance information from the terminal device.

[0046] In a possible implementation, in a case where the terminal device performs control plane based data transmission, the communication module is configured to receive an uplink information transmission message from the terminal device, or an RRC early data request message without carrying a service temporary mobile user identity. Alternatively, the communication module is configured to receive data from the terminal device, or an RRC connection resume request message without carrying a first identity, where the first identity is used by the network device to identify a terminal device context corresponding to the terminal device.

[0047] In a possible implementation, in a case where the one or more uplink grant resources included in the first configuration information are configured grant resources, the communication module is configured to send, to the terminal device, second indication information, where the second indication information is used to indicate one or more of the following: one or more cell identities corresponding to first configured grant resources of the terminal device, or a radio network temporary identity corresponding to the first configured grant resources, or a radio network temporary identity RNTI used for data retransmission corresponding to the first configured grant resources, or a time advance validity condition, or a condition for the terminal device to judge and trigger data transmission in an RRC non-connected state, or a search space for the terminal device to monitor a physical downlink control channel, or a timer. The first configured grant resource is one of the one or more uplink grant resources.

[0048] In a possible implementation, the communication module is configured to send, to the terminal device, an initial data transmission response, where the initial data transmission response can be: downlink data, or physical layer acknowledgement information or downlink control information of a physical downlink control channel addressed to a radio network temporary identity, or physical layer acknowledgement information or downlink control information of a physical downlink control channel addressed to a cell radio network temporary identity, or downlink control information of a physical downlink control channel addressed to a radio network temporary identity for data retransmission.

[0049] In a possible implementation, in a case where the terminal device performs subsequent data transmission after performing initial data transmission, the communication module is configured to send, to the terminal device, a dynamic grant. The communication module is further configured to receive data subsequently sent by the terminal device.

[0050] In a fifth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program or instructions, and when the computer program or instructions run on a computer, the computer program or instructions cause the computer to perform a data transmission method as described in any possible implementation of the first aspect to the first aspect. The computer can be a terminal device.

[0051] In a sixth aspect, an embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores a computer program or instructions, when the computer program or instructions run on a computer, the computer program or instructions make the computer execute a data transmission method described in any possible implementation manner of the second aspect to the second aspect. The computer can be a network device.

[0052] In a seventh aspect, an embodiment of the present application provides a computer program product including instructions, when the instructions run on a computer, the computer executes a data transmission method described in the first aspect or various possible implementation manners of the first aspect.

[0053] In an eighth aspect, an embodiment of the present application provides a computer program product including instructions, when the instructions run on a computer, the computer executes a data transmission method described in the second aspect or various possible implementation manners of the second aspect.

[0054] In a ninth aspect, an embodiment of the present application provides a communication apparatus for implementing various methods in any possible design of the first aspect and the second aspect. The communication apparatus can be the terminal device, or a device including the terminal device, or a component (for example, a chip) applied to the terminal device. Alternatively, the communication apparatus can be the network device, or a device including the network device, or a component (for example, a chip) applied to the network device. The communication apparatus includes modules or units corresponding to the above methods, and the modules or units can be implemented by hardware, software or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. It should be understood that the communication apparatus described in the ninth aspect can further include a bus and a memory for storing codes and data. Optionally, at least one processor is coupled to the bus and the memory.

[0055] In a tenth aspect, an embodiment of the present application provides a communication apparatus, and the communication apparatus includes at least one processor. When the communication apparatus runs, the processor executes computer program or instructions stored in the memory, so that the communication apparatus executes any method in any possible design of the first aspect or any possible design of the first aspect. For example, the communication apparatus can be a terminal device, or a chip applied to the terminal device.

[0056] In a eleventh aspect, an embodiment of the present application provides a communication apparatus, comprising at least one processor. The at least one processor and the memory are coupled. When the communication apparatus is running, the processor executes computer-executed instructions or programs stored in the memory, so that the communication apparatus executes the method in any one of various possible designs of the second aspect or any one of the second aspect.

[0057] It should be understood that the memory described in any one of the tenth aspect to the eleventh aspect can also be replaced by a storage medium, and the embodiments of the present application do not limit this.

[0058] In a possible implementation, the memory described in any one of the tenth aspect to the eleventh aspect can be a memory inside the communication apparatus. Of course, the memory can also be located outside the communication apparatus, but the at least one processor can still execute the computer-executed instructions or programs stored in the memory.

[0059] In a twelfth aspect, an embodiment of the present application provides a communication apparatus, comprising one or more modules for implementing the method in any one of the first aspect and the second aspect. The one or more modules can correspond to each step in the method in any one of the first aspect and the second aspect.

[0060] In a thirteenth aspect, an embodiment of the present application provides a chip system, comprising a processor for reading and executing computer programs stored in a memory to execute the method in the first aspect and any possible implementation thereof. Optionally, the chip system can be a single chip or a chip module composed of multiple chips. Optionally, the chip system further comprises a memory, and the memory is connected to the processor through a circuit or a wire. Further optionally, the chip system further comprises a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0061] In a fourteenth aspect, an embodiment of the present application provides a chip system, comprising a processor for reading and executing computer programs stored in a memory to execute the method in the second aspect and any possible implementation thereof. Optionally, the chip system can be a single chip or a chip module composed of multiple chips. Optionally, the chip system further comprises a memory, and the memory is connected to the processor through a circuit or a wire. Further optionally, the chip system further comprises a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0062] In a fifteenth aspect, an embodiment of the present application provides a communication system, comprising: a terminal device and a network device. The terminal device is configured to perform the method in the first aspect and any possible implementation manner thereof, and the network device is configured to perform the method in the second aspect and any possible implementation manner thereof.

[0063] Any of the apparatuses or computer storage media or computer program products or chips or communication systems provided above are configured to perform the corresponding method provided above, thus achieving the beneficial effects of the corresponding solutions provided above, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0064] FIG. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application;

[0065] FIG. 2 is a schematic diagram of multiple scenarios of a RAN architecture based on an NTN system according to an embodiment of the present application;

[0066] FIG. 3a is a schematic diagram of a user plane protocol stack of a terminal device and a gNB according to an embodiment of the present application;

[0067] FIG. 3b is a schematic diagram of a control plane protocol stack of a terminal device and a gNB according to an embodiment of the present application;

[0068] FIG. 4 is a schematic diagram of RRC state transition of a terminal device according to an embodiment of the present application;

[0069] FIG. 5 is a schematic diagram of an O-RAN architecture according to an embodiment of the present application;

[0070] FIG. 6a is a schematic diagram of a four-step random access according to an embodiment of the present application;

[0071] FIG. 6b is a schematic diagram of a two-step random access according to an embodiment of the present application;

[0072] FIG. 7a is a schematic diagram of MO-EDT for control plane cellular IoT EPS optimization according to an embodiment of the present application;

[0073] FIG. 7b is a schematic diagram of MO-EDT for control plane cellular IoT 5G system optimization according to an embodiment of the present application;

[0074] FIG. 7c is a schematic diagram of MO-EDT for user plane cellular IoT EPS optimization according to an embodiment of the present application;

[0075] FIG. 7d is a schematic diagram of MO-EDT for user plane cellular IoT 5G system optimization according to an embodiment of the present application;

[0076] FIG. 8a is a schematic diagram of a PUR configuration request and PUR configuration according to an embodiment of the present application;

[0077] FIG. 8b is a schematic diagram of data transmission using PUR for control plane cellular IoT EPS optimization according to an embodiment of the present application;

[0078] FIG. 8c is a schematic diagram of data transmission using PUR for control plane cellular IoT 5GS optimization according to an embodiment of the present application;

[0079] FIG. 8d is a schematic diagram of data transmission using PUR for user plane cellular IoT EPS optimization according to an embodiment of the present application;

[0080] FIG. 8e is a schematic diagram of data transmission using PUR for user plane cellular IoT 5GS optimization according to an embodiment of the present application;

[0081] FIG. 9 is a schematic diagram of a data transmission method according to an embodiment of the present application;

[0082] FIG. 10 is a schematic diagram of a data transmission method based on RA-PUR according to an embodiment of the present application;

[0083] FIG. 11 is a schematic diagram of a data transmission method based on CG-EDT according to an embodiment of the present application;

[0084] FIG. 12 is a schematic diagram of a communication apparatus according to an embodiment of the present application;

[0085] FIG. 13 is a schematic diagram of a hardware structure of a communication apparatus according to an embodiment of the present application;

[0086] FIG. 14 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0087] FIG. 15 is a schematic diagram of a network device according to an embodiment of the present application;

[0088] FIG. 16 is a schematic diagram of a chip structure according to an embodiment of the present application. DETAILED DESCRIPTION

[0089] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the same items or similar items with basically the same functions and effects are distinguished by using "first", "second", etc. For example, the first message and the second message are only used to distinguish different symbols, and the order is not limited. Those skilled in the art can understand that "first", "second", etc. do not limit the quantity and execution order, and "first", "second", etc. also do not necessarily mean different.

[0090] It should be noted that the terms "exemplary" or "for example" when used in this specification mean "serving as an example, instance, or illustration," and should not necessarily be construed as preferred or advantageous over other embodiments or suitable designs. Rather, use of these terms is intended to present concepts in a concrete manner.

[0091] The technical solutions of the present application can be applied to various communication systems, such as a long time evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a public land mobile network (PLMN) system, a device to device (D2D) network system or a machine to machine (M2M) network system, a 5th-generation (5G) communication system, and a 6th-generation (6G) communication system, etc.

[0092] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, as the network architecture evolves and new service scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems. In the embodiments of the present application, the methods provided are taken as examples for application in IoT or 5G networks.

[0093] In the present application, “at least one” means one or more, “multiple” means two or more. “And / or” describes the association relationship of the associated objects, which means that there can be three kinds of relationships, for example, A and / or B can represent: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects before and after it. “At least one of the following” or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

[0094] As shown in FIG. 1, the embodiment of the present application provides a communication system, which includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one network device 110 (such as 110a and 110b in FIG. 1) and at least one terminal device 120 (such as at least one of 120a-120i in FIG. 1) in communication with the network device 110. The network device 110 is connected to the core network 200 through wireless or wired means. The core network device in the core network 200 and the network device 110 in the RAN 100 can be different physical devices respectively, or can be the same physical device integrated with the core network logic function and the radio access network logic function.

[0095] The RAN 100 can be a 3rd generation partnership project (3GPP) related cellular system, for example, a 4G, 5G mobile communication system, a non-terrestrial network (NTN) system, or a future-oriented evolution system (such as a 6G mobile communication system). The RAN 100 can also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, and can also be a communication system integrating two or more of the above systems.

[0096] The present application takes RAN 100 as an example of an NTN system. At present, due to the fact that a traditional terrestrial network (TN) cannot provide seamless coverage for a user equipment (UE), especially in places such as the sea, desert, and sky where base stations cannot be deployed, an NTN system is proposed in an internet of things (IoT), 5G, and subsequent evolution system architecture (such as 6G) to achieve global seamless network coverage. In an NTN, a satellite is one of the key infrastructures. Satellites are generally divided into the following three types according to the orbital height: a geostationary earth orbit (GEO) satellite, also known as a synchronous orbit satellite or a high-orbit satellite; a medium earth orbit (MEO) satellite, also simply referred to as a medium-orbit satellite; and a low earth orbit (LEO) satellite, also simply referred to as a low-orbit satellite.

[0097] The orbital height of a GEO satellite is 35786 km. The main advantage of a GEO satellite is that it is relatively stationary on the ground and provides a large coverage area.

[0098] The orbital height of a MEO satellite is 2000 km to 35786 km. Global coverage can be achieved using a relatively small number of MEO satellites. At present, MEO satellites are mainly used for positioning and navigation.

[0099] The orbital height of a LEO satellite is 300 km to 2000 km. LEO satellites have a lower orbital height than MEO satellites and GEO satellites, have smaller data propagation delays, have smaller power losses, and have lower launch costs.

[0100] For a MEO satellite or a LEO satellite, a cell providing coverage can be divided into a quasi-earth-fixed cell and an earth-moving cell. In a quasi-earth-fixed cell, a moving satellite adjusts its beam to form a cell. The position of the cell on the ground is stationary for a certain period of time. In an earth-moving cell, the satellite does not dynamically adjust its beam direction. The cell covered by the beam of the satellite moves with the movement of the satellite.

[0101] Scenarios of NTN-based NG-RAN architectures include the following:

[0102] As shown in (a) of FIG. 2, it is a scenario of transparent satellite architecture, in which the satellite functions as radio frequency filtering and frequency conversion and amplification, that is, the satellite mainly functions as a physical layer relay, regenerates the physical layer signal, and does not have other higher protocol layers.

[0103] As shown in (b) of FIG. 2, it is a scenario of a regenerative satellite without an inter-satellite link (ISL), in which the satellite has the processing function of a base station, and the satellite communicates as a base station.

[0104] As shown in (c) of FIG. 2, it is a scenario of a regenerative satellite with an inter-satellite link (ISL), in which the satellite has the processing function of a base station, and the satellite also communicates as a base station. It can be understood that the difference between the scenario shown in (b) of FIG. 2 and the scenario shown in (c) of FIG. 2 is that there is an ISL.

[0105] As shown in (d) of FIG. 2, it is a scenario of a regenerative satellite with the processing function of a distributed unit (DU) of a base station, in which the satellite communicates as a DU.

[0106] In the RAN 100, the terminal device 120 can be connected to the network device 110 in a wireless manner, and can access to the core network 200 through the network device 110. It should be understood that the RAN 100 can further include other network devices, for example, a wireless relay device and / or a wireless backhaul device (not shown in FIG. 1).

[0107] In the RAN 100, the terminal device 120 can be connected to the network device 110 in a wireless manner, and can access to the core network 200 through the network device 110. It should be understood that the RAN 100 can further include other network devices, for example, a wireless relay device and / or a wireless backhaul device (not shown in FIG. 1).

[0108] As shown in FIG. 3a and FIG. 3b, taking a base station (such as a satellite based on the RAN architecture of the NTN system) as an example, FIG. 3a shows the user plane protocol stack of the communication between the terminal device (such as the terminal device 120a-120i) and the base station, and the user plane protocol stack of the terminal device and the base station includes, from top to bottom, a service data adaptation protocol (SDAP), a packet data convergence protocol (PDCP), a radio link control (RLC), a medium access control (MAC) layer and a physical (PHY) layer. As shown in FIG. 3b, the control plane protocol stack of the communication between the terminal device and the base station is shown, and the control plane protocol stack of the terminal device includes, from top to bottom, a non-access (NAS) layer, a radio resource control (RRC) layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. The control plane protocol stack of the AMF network element includes a NAS layer. FIG. 3a and FIG. 3b take the protocol stack of each device shown as an example of the protocol stack of NR.

[0109] As can be seen from FIG. 3a and FIG. 3b, the common point of the user plane (UP) protocol stack and the control plane (CP) protocol stack of the terminal device or the base station is that they both include an RLC layer, a MAC layer and a PHY layer.

[0110] For the RRC layer, in the long term evolution (LTE) system, there are two radio resource control states of terminal devices, which are RRC-connected (RRC_CONNECTED) state and RRC-idle (RRC_IDLE) state. After the terminal device is powered on, the terminal device is first in the RRC_IDLE state. If the terminal device initiates an RRC connection establishment request and successfully establishes an RRC connection with the base station, the terminal device enters the RRC_CONNECTED state, and then can communicate with the core network device. If the terminal device initiates an RRC connection establishment request and fails, or the terminal device releases the RRC connection, the terminal device enters the RRC_IDLE state. In the RRC_IDLE state, if the core network device has data to send to the terminal device, the core network device needs to send a paging message to the terminal device. When the terminal device receives the paging message for paging the terminal device, the terminal device initiates an RRC connection establishment process, and the terminal device enters the RRC_CONNECTED state to receive the data.

[0111] In order to reduce signaling overhead and terminal device power consumption, in the 5G communication system, in addition to the RRC-connected state and the RRC-idle state, the terminal device has a third state, that is, the radio resource control-inactive (RRC_INACTIVE) state. In the RRC_INACTIVE state, the terminal device is in a power-saving sleep state, but the terminal device still retains part of the radio access network (RAN) context (for example, security context, terminal device capability information, etc.), and always maintains the connection between the 5G core network and the RAN. That is, the terminal device in the RRC_INACTIVE state always maintains the connection between the 5G core network and the base station. Therefore, when communication with the terminal device is needed, the terminal device can quickly change from the RRC_INACTIVE state to the RRC_CONNECTED state. In other words, "terminal devices with infrequent data transmission are usually kept in the RRC_INACTIVE state by the network".

[0112] The same point of the RRC_IDLE state and the RRC_INACTIVE state is that the terminal device cannot perform data transmission in the RRC_IDLE state and the RRC_INACTIVE state, and if the terminal device needs to transmit data, the terminal device needs to switch from the RRC_IDLE state or the RRC_INACTIVE state to the RRC_CONNECTED. The difference between the RRC_IDLE state and the RRC_INACTIVE state is that the terminal device switches from the RRC_INACTIVE state to the RRC_CONNECTED state is different from the terminal device switching from the RRC_IDLE state to the RRC_CONNECTED state. Because the terminal device switches from the RRC_CONNECTED state to the RRC_IDLE state, the context of the core network is released, that is, the context applied when the terminal device switches from the RRC_IDLE state to the RRC_CONNECTED state is released. However, when the terminal device switches from the RRC_INACTIVE state to the RRC_CONNECTED state, the terminal device does not release the context, thereby reducing the signaling overhead between the network device and the terminal device. The reduction of signaling message reception reduces the power consumption caused by blind detection of the terminal device and the transmission time caused by air interface transmission. Therefore, the time used by the terminal device to enter the RRC_CONNECTED state from the RRC_INACTIVE state is shorter than the time used by the terminal device to enter the RRC_CONNECTED state from the RRC_IDLE state, and the signaling is less, thereby enabling the terminal device to quickly enter the RRC_CONNECTED state from the RRC_INACTIVE state, and reducing the signaling overhead.

[0113] When the terminal device is in different RRC states, different operations are performed. As shown in FIG. 4, FIG. 4 shows the flow of conversion between the above three RRC states:

[0114] The terminal device starts in the RRC_IDLE state, and when the terminal device needs to perform data transmission, the terminal device performs a random access process to establish an RRC connection with the base station, and starts data transmission after entering the RRC_CONNECTED state. In the process of initiating random access, the terminal device sends an RRC connection establishment request message (for example, RRCSetupRequest) to the base station. The terminal device receives the connection establishment message (for example, RRCSetup) sent by the base station to establish (setup) the RRC connection.

[0115] When the terminal device does not need to perform data transmission subsequently, the base station can release the terminal device to enter the RRC_IDLE state or the RRC_INACTIVE state.

[0116] For example, the base station sends a release message (e.g., RRCRelease with suspend indication) with a suspend indication to the terminal device, so that the terminal device enters the RRC_INACTIVE state.

[0117] For another example, the base station sends a release message (e.g., RRCRelease) to the terminal device, so that the terminal device enters the RRC_IDLE state.

[0118] In addition, the terminal device in the RRC_INACTIVE state can also return to the RRC_CONNECTED state through a resume message. For example, the terminal device sends an RRC connection resume request message (e.g., RRCResumeRequest) and receives a connection resume message (e.g., RRCResume) sent by the base station. Similarly, the base station can also release the terminal device so that the terminal device enters the RRC_IDLE state.

[0119] Specifically, the characteristics of each RRC state of the terminal device are as follows:

[0120] RRC_IDLE state: PLMN selection, system information broadcast, cell reselection, called paging initiated by the 5G core (5GC), DRX configured by the non access stratum (NAS) for core network paging.

[0121] RRC_INACTIVE state: public land mobile network (PLMN) selection, system information broadcast, cell reselection, called paging initiated by the next generation (NG)-radio access network (RAN), RAN-based Notification Area (RNA) managed by the NG-RAN, discontinuous reception (DRX) configured by the NG-RAN for RAN paging, establishment of user plane and control plane between the 5GC and the NG-RAN, both the NG-RAN and the terminal device save the access stratum (AS) context of the terminal device, and the NG-RAN knows the RNA where the terminal device is located.

[0122] RRC_CONNECTED state: connection between a user plane and a control plane of a 5G core (5GC) and an NG-RAN is established, both the NG-RAN and the terminal device save an AS layer context of the terminal device, the NG-RAN knows a cell to which the terminal device belongs, the terminal device can send or receive unicast data, and mobility of the terminal device is controlled by the network, including measurement.

[0123] In the embodiments of the present application, the network device is a network side device with wireless transceiving function. The network device can be an apparatus for providing wireless communication function for the terminal device in the RAN, referred to as RAN device. For example, the network device 110 can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; or can be a module or unit completing part of the function of the base station, for example, can be a central unit (CU), or can be a distributed unit (DU). Here, the CU completes the function of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the function of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the function of part of the physical layer or the entire physical layer. For specific description of the above-mentioned protocol layers, reference can be made to the relevant technical specifications of the 3rd generation partnership project (3GPP). The network device 110 can be a macro base station, or can be a micro base station or an indoor station, or can be a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device 110.

[0124] In the embodiments of the present application, taking O-RAN as an example, as shown in FIG. 5, FIG. 5 shows an architecture schematic diagram of O-RAN. The main feature of the O-RAN architecture is the separation of software and hardware, which realizes the virtualization of network functions and the standardization of hardware. Optionally, the O-RAN can also introduce artificial intelligence (AI).

[0125] In the ORAN system, the central unit (CU) can also be referred to as an open CU (O-CU). The distributed unit (DU) can also be referred to as an open DU (O-DU). The control unit control plane (CU-CP) can also be referred to as an open CU-CP (O-CU-CP). The control unit user plane (CU-UP) can also be referred to as an open CU-UP (O-CU-UP). The radio unit (RU) can also be referred to as an open RU (O-RU). In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. Any of the CU (or CU-CP, CU-UP), DU and RU in the present application can be realized by a software module, a hardware module, or a combination of a software module and a hardware module.

[0126] The access network device of the ORAN and the corresponding relationship of the protocol layer functions that can be implemented by the access network device can be referred to the following table:

[0127] In the embodiments of the present application, the terminal device is a user-side device with wireless transceiving function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted, and can also be a sensor type device. It can also be deployed on the water surface (such as ships, etc.). It can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). The terminal device can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile, remote station, remote terminal, mobile equipment, user terminal, wireless telecom equipment, user agent, user equipment, or user device. The terminal can be a station (STA) in a wireless local area network (WLAN), a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a terminal device in a next-generation communication system (for example, a fifth-generation (5G) communication network) or a terminal device in a future evolved public land mobile network (PLMN) network, etc. Among them, 5G can also be referred to as new radio (NR).

[0128] In addition, the terminal device can also be a wearable device, which is a portable device directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also has powerful functions through software support and data interaction, cloud interaction. The general wearable smart device includes a full function, large size, and can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and only focuses on a certain application function, which needs to be used with other devices such as a smart phone, such as various smart wristbands, smart jewelry, and the like. For example, a smart watch, a smart wristband, a pedometer, and the like. A vehicle-mounted device (for example, a car, a bicycle, an electric vehicle, an airplane, a ship, a train, a high-speed rail, and the like), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (for example, a refrigerator, a television, an air conditioner, an electric meter, and the like), a smart robot, a plant device, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, a flight device (for example, a smart robot, a hot air balloon, a drone, an airplane), and the like. In this application, in order to facilitate description, a chip deployed in the above device, such as a system on a chip (SOC), a baseband chip, or other chips with communication functions can also be referred to as a terminal.

[0129] In the embodiments of the present application, the roles of the network device and the terminal device can be relative. For example, the terminal device 120h in FIG. 1 can be configured as a mobile network device, and some terminal devices can access the radio access network through the terminal device 120h. At this time, the terminal device 120h is a network device. However, for the network device 110a in FIG. 1, the terminal device 120h is a terminal device, that is, the network device 110a and the terminal device 120h communicate through a wireless air interface protocol. Of course, the network device 110a and the terminal device 120h can also communicate through an interface protocol between network devices. At this time, the terminal device 120h is also a network device relative to the network device 110a. Therefore, the network device and the terminal device can be collectively referred to as a communication apparatus. The network devices 110a and 110b in FIG. 1 can be referred to as a communication apparatus with a network device function, and the terminal devices 120a-120i in FIG. 1 can be referred to as a communication apparatus with a terminal device function.

[0130] The network device and the terminal device, the network device and the network device, and the terminal device and the terminal device can communicate through a licensed spectrum, an unlicensed spectrum, or both. They can communicate through a spectrum below 6 gigahertz (GHz), a spectrum above 6 GHz, or both. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0131] In the embodiments of the present application, the functions of the network device can also be performed by a module (such as a chip) in the network device or a control subsystem containing network device functions. The control subsystem containing network device functions can be a control center in the above-mentioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. The functions of the terminal device can also be performed by a module (such as a chip or a modem) in the terminal device or a device containing terminal device functions.

[0132] Currently, the terminal in the RRC_INACTIVE state or the RRC_IDLE state does not support data transmission, that is, the terminal in the RRC_INACTIVE state or the RRC_IDLE state needs to resume the RRC connection to enter the RRC_CONNECTED state through the random access process before data transmission.

[0133] In the embodiments of the present application, the network device can support multiple random access modes. The following briefly introduces the four-step random access mode (4-step RA) and the two-step random access mode (2-step RA) currently supported by the terminal and the network device. With the development of communication technology, more other random access modes will appear in the future, and the multiple random access modes described here can be included.

[0134] As an example, when the terminal is not configured with the resource of contention free random access (CFRA), the terminal will autonomously select to perform contention based random access (CBRA), such as 4-step RA or 2-step RA, based on the size relationship between the current reference signal receiving power (RSRP) measurement value and the threshold specified in the protocol.

[0135] As shown in FIG. 6a, FIG. 6a shows a schematic diagram of a four-step random access process, which includes the following steps:

[0136] The terminal in the RRC_IDLE state sends a random access preamble (also referred to as message one (Msg1)) to the base station (for example, the terminal can send a preamble to the base station on a random access channel). The base station sends a random access response message (RAR), also referred to as message two (Msg2), to the terminal after detecting the random access preamble. The terminal sends an uplink message, also referred to as message three (Msg3), through a data channel (for example, a physical uplink shared channel (PUSCH)) on the allocated uplink resource according to the indication of Msg2. In order to solve the conflict, the base station returns a conflict resolution message (also referred to as Msg4) to the terminal that successfully accesses after successfully receiving a Msg3, and the Msg4 carries a unique identity in the Msg3 to specify the terminal that successfully accesses. For CBRA, the base station broadcasts a set of available preambles of the network device and the time-frequency resource for sending Msg1 through a broadcast message before the terminal performs random access. The terminal includes the following steps when performing random access:

[0137] Step 601a: The terminal sends Msg1, also referred to as message one, to the base station on time-frequency resource 1.

[0138] In the message 1, a random access preamble is included, for example, the terminal can send the random access preamble to the base station on the random access channel.

[0139] The terminal can inform the base station of its random access request through the random access preamble. The random access preamble includes any preamble selected by the terminal from the preamble set configured by the network device.

[0140] Step 602a: the base station sends a message 2, also known as message 2, to the terminal. In the message 2, a random access response (RAR) is included.

[0141] It can be understood that the terminal will listen to the PDCCH within the RAR time window to receive the RAR sent by the base station. If the terminal does not receive the RAR replied by the base station within the RAR time window, the terminal considers that the random access process fails. The RAR includes the random access preamble, the time-frequency location of sending the message 3, the temporary cell radio network temporary identifier (TC-RNTI), etc. The base station demodulates the preamble sent by the terminal. The base station calculates the scrambling code of the message 2 according to the identification of the demodulated preamble and the time-frequency resource of receiving the message 1. The scrambling code can be the random access radio network temporary identifier (RA-RNTI). The base station determines the time-frequency resource of sending the message 3 by the terminal. The base station carries the identification of the preamble and the time-frequency resource of sending the message 3 in the message 2. The base station sends the message 2 to the terminal after scrambling the message 2 with the calculated scrambling code.

[0142] Step 603a: if the terminal receives the RAR, the terminal will send an uplink message 3, also known as message 3, on the data channel (for example, the physical uplink shared channel (PUSCH)) according to the indication of the message 2 on the allocated time-frequency resource based on the current different RRC states and different scenarios of the terminal.

[0143] In the message 3, the identification of the terminal and different RRC messages are carried. For example, when the terminal is in the RRC_INACTIVE state, the terminal can send an RRCResumerequest to resume the RRC connection.

[0144] Since multiple terminals send message 3 on the same time-frequency resource, interference will occur. In order to solve the conflict, after the base station successfully receives one Msg3, the base station returns a conflict resolution message (also referred to as Msg4) to the terminal that successfully accesses, as shown in step 604a. The Msg4 is used to inform the terminal that the random access is successful.

[0145] As shown in FIG. 6b, FIG. 6b shows a schematic diagram of a two-step random access process, which includes the following steps:

[0146] Step 601b, the terminal sends a message A (MsgA). The MsgA includes a random access preamble and an RRC message carried in the Msg3 of the 4-step RA described above.

[0147] Step 602b, the base station sends a message B (MsgB) to the terminal. The MsgB includes a RAR, which is used to inform the terminal whether the contention resolution is successful.

[0148] Currently, in the data transmission process of a communication system, the efficiency and reliability of data transmission are improved by the following scheme.

[0149] Scheme one, currently, small packet data transmission can be performed through 4-step RA. In the LTE system, a method for supporting data transmission of a terminal in an RRC_IDLE state has been standardized, which is referred to as early data transmission (EDT) for short, including mobile originated early data transmission (MO-EDT) and mobile terminated early data transmission (MT-EDT). The main idea is that the terminal can perform uplink data transmission in the RRC_IDLE state.

[0150] MO-EDT is used for single uplink data transmission and optional downlink data transmission in the random access (RA) process. MO-EDT is triggered when the upper layer or high layer has requested to establish or resume the RRC connection, or the uplink data size is less than or equal to the transport block size indicated in the system message. MT-EDT is used for single downlink data transmission in the random access process. MT-EDT is initiated by the core network (mobility management entity (MME) or access and mobility management function (AMF)) when the terminal device and the network device both support MT-EDT and the terminal device has single downlink data transmission.

[0151] In which, the transmission of the control plane MO-EDT has the following characteristics: uplink user data can be sent through the non-access layer (NAS) message connected by the RRC EarlyDataRequest message on the common control channel (CCCH); downlink user data can be transmitted in the NAS message connected by the RRC EarlyDataComplete message on the CCCH; there is no need to switch to the RRC_CONNECTED state.

[0152] In a possible example, as shown in FIG. 7a, a MO-EDT schematic diagram based on control plane cellular internet of things (CIoT) evolved packet system (EPS) optimization. When the terminal device requests to establish a connection for mobile originated data, the terminal device initiates the MO-EDT procedure and selects the random access preamble configured for EDT. In which, the mobile originated data comes from the upper layer or high layer, and the specific steps are as follows:

[0153] Step 1, the terminal device sends the RRC EarlyDataRequest message and user data.

[0154] Step 2, the base station (eNB) sends the initial terminal device message (Initial UE message) to forward the NAS message and establish the S1-AP connection.

[0155] Step 3, the MME requests the serving gateway (S-GW) to activate the bearer for the terminal device.

[0156] Step 4, the MME sends the uplink data to the S-GW.

[0157] Step 5, if there is downlink data, the S-GW sends the downlink data to the MME.

[0158] Step 6a, if the downlink data is received from the S-GW, the MME forwards the data to the base station, and can also indicate whether more data is expected.

[0159] Step 6b, if no downlink data is received from the S-GW, the MME triggers the connection establishment indication and indicates whether further data is expected.

[0160] Step 7, If no further data is expected, the base station can send an RRC Early Data Complete (RRCEarlyDataComplete) message on the CCCH to keep the terminal device in RRC_IDLE state. If downlink data is received, the downlink data is included in the RRCEarlyDataComplete message.

[0161] Step 8, The base station releases the S1-AP connection and activates the bearer.

[0162] In another possible example, as shown in FIG. 7b is a MO-EDT schematic diagram based on control plane cellular internet of things (CIoT) 5G system optimization. When the terminal device requests a mobile-originated data connection, the terminal device initiates the MO-EDT procedure and selects a random access preamble configured for EDT, wherein the mobile-originated data comes from an upper layer or a higher layer, and the specific steps are as follows:

[0163] Step 1, The terminal device sends an RRC Early Data Request (RRCEarlyDataRequest) message and user data.

[0164] Step 2, The base station (ng-eNB) sends an Initial UE message to forward the NAS message. It includes a protocol data unit (PDU) session identifier and data. In this process, the base station can indicate that this connection is triggered for EDT.

[0165] Step 3, The AMF network element determines the PDU session contained in the NAS message.

[0166] Step 4, The AMF network element sends the PDU session and the uplink data to the session management function (SMF) network element, and the SMF network element forwards the uplink data to the user plane function (UPF) network element.

[0167] Step 5, If there is downlink data, the UPF network element forwards the downlink data to the SMF network element, and the SFM network element forwards the downlink data to the AMF network element.

[0168] Step 6a, If downlink data is received from the SMF network element, the AMF network element forwards the data to the base station through a downlink NAS transmission procedure, and can also indicate whether more data is expected.

[0169] Step 6b, if no downlink data is received from the SMF network element, the AMF network element triggers the connection establishment indication procedure and indicates whether further data is expected.

[0170] Step 7, if no further data is expected, the base station sends an RRC early data complete (RRCEarlyDataComplete) message on the CCCH to keep the terminal device in the RRC_IDLE state; if downlink data is received, the downlink data is included in the RRCEarlyDataComplete message.

[0171] Step 8, the base station starts the AN release procedure.

[0172] Wherein, the transmission of the user plane MO-EDT has the following characteristics: the terminal device is in the RRC_IDLE state and there is a valid PUR resource; the next hop chaining count (NCC) is provided to the terminal device in the RRCConnectionRelease message carrying the suspension indication; the uplink user data is sent on the dedicated traffic channel (DTCH) multiplexed with the RRCConnectionResumeRequest message on the CCCH; the downlink user data can be transmitted on the DTCH multiplexed with the RRCConnectionRelease message on the dedicated control channel (DCCH); the shortMAC-I is calculated as the authentication token of the RRCConnectionResumeRequest message using the integrity key from the previous connection; the uplink and downlink user data are encrypted, wherein the key is derived based on the NCC provided in the RRCConnectionRelease message of the previous RRC connection; the RRCConnectionRelease message is integrity protected and encrypted using the newly derived key; the uplink user data can be sent through the NAS message connected by the RRCEarlyDataRequest message on the CCCH, and the downlink user data can be transmitted in the NAS message connected by the RRCEarlyDataComplete message on the CCCH; there is no need to switch to the RRC_CONNECTED state.

[0173] In one possible example, as shown in FIG. 7c, a MO-EDT schematic diagram based on the user plane CIoT EPS optimization. When the terminal device requests to resume the mobile originated data, the terminal device initiates the MO-EDT procedure and selects the random access preamble configured for EDT. Wherein, the mobile originated data comes from the upper layer or high layer, and the specific steps are as follows:

[0174] Step 1, the terminal device sends an RRC connection resume request (RRCConnectionResumeRequest) message to the base station (eNB), including the terminal device's Resume ID, establishment reason and authentication token. The terminal device resumes all signaling radio bearers (SRBs) and data radio bearers (DRBs), derives new security keys using the NextHopChainingCount provided in the previous RRC connection's RRCConnectionRelease message, and re-establishes AS security. User data is encrypted and transmitted on the DTCH channel, multiplexed with the RRCConnectionResumeRequest message on the CCCH channel. If enabled in the cell, the terminal device can indicate AS release assistance information.

[0175] Step 2, the base station initiates the terminal device context resume request (UE Context Resume Request) procedure, resumes the S1-AP connection, and reactivates the S1-U bearer.

[0176] Step 3, the MME requests the S-GW to reactivate the S1-U bearer for the terminal device.

[0177] Step 4, the MME confirms the terminal device context resume to the base station.

[0178] Step 5, the base station sends uplink data to the S-GW.

[0179] Step 6, if there is downlink data, the S-GW sends the downlink data to the base station.

[0180] Step 7, if there is no further data expected, the base station can initiate suspension of the S1 connection and deactivation of the S1-U bearer.

[0181] Step 8, the base station sends an RRC connection release (RRCConnectionRelease) message to keep the terminal device in RRC_IDLE state. The message includes the releaseCause saved by the terminal device as rrc-Suspend, recoverID, NextHopChainingCount and drb-ContinueROHC. If downlink data is received in step 6, it is encrypted and transmitted on the DTCH channel, which is multiplexed with the RRCConnectionRelease message on the DCCH channel. The procedure ends after receiving HARQ (ARQ) feedback confirming successful DL transmission.

[0182] In another possible example, as shown in FIG. 7d is a MO-EDT diagram based on user plane CIoT 5G system optimization. When the terminal device requests to resume mobile originated data, the terminal device initiates the MO-EDT procedure and selects the random access preamble configured for EDT, and the specific steps are as follows:

[0183] Step 1, the terminal device sends an RRC connection resume request (RRCConnectionResumeRequest) message to the base station (ng-eNB), including the wireless network temporary identifier of the terminal device, the resume cause and the authentication token. The terminal device resumes all SRBs and DRBs, derives a new security key using the NextHopChainingCount provided in the previous connection RRCConnectionRelease message, and re-establishes AS security. User data is transmitted on the DTCH channel after encryption, multiplexed with the RRCConnectionResumeRequest message on the CCCH channel. The UE can indicate AS release assistance information.

[0184] Step 2, the base station sends the uplink data to the UPF network element.

[0185] Step 3, the base station sends the NG-AP: UE Context Resume Request message to the AMF network element to resume the connection. If the terminal device includes the AS release assistance information indicating no further uplink / downlink higher layer PDU in step 1, the base station can request to immediately transition to RRC_IDLE and suspend.

[0186] Step 4, if the AMF network element does not receive the request to immediately migrate to suspended RRC_IDLE in step 3, or the AMF network element knows that there is downlink data or signaling suspended, the AMF network element requests the SMF network element to resume the PDU session.

[0187] Step 5, the AMF network element sends the UE Context Resume Response to the base station. If the AMF network element receives the request to immediately migrate to RRC_IDLE with Suspend in step 3, and there is no downlink data or signaling suspended, the AMF network element contains the Suspend indication, and keeps the terminal device in CM_IDLE with Suspend.

[0188] Step 6, if the AMF network element contains the Suspend indication in step 5, the base station goes to step 8. If the AMF network element does not contain the suspend indication in step 1, and the terminal device contains the AS release assistance information indicating a single downlink data transmission after uplink transmission only, the base station can wait for the downlink data to arrive, and goes to step 7.

[0189] Step 7, the base station initiates an NG-AP: UE Context Suspend procedure to notify the AMF network element of the RRC connection suspension. The AMF network element requests the SMF network element to suspend the PDU session, and the SMF network element requests the UPF network element to release the tunnel information for the terminal device.

[0190] Step 8, the base station sends an RRCConnectionRelease message to keep the terminal device in an RRC_IDLE state. The message includes the releaseCause saved by the terminal device as rrc-Suspend, I-RNTI, NextHopChainingCount, and drb-ContinueROHC. If downlink data is received in step 6, it is transmitted in ciphering on a DTCH channel, which is multiplexed with the RRCConnectionRelease message on a DCCH channel. The process ends after receiving HARQ feedback (ARQ) to confirm that the DL transmission is successful.

[0191] Scheme II, the terminal device transmits small packet data through a preconfigured uplink resource (PUR). This method can be used when both the base station and the terminal support PUR. The terminal transmits data through a preconfigured uplink resource and does not have to perform a random access procedure.

[0192] For PUR, when in an RRC_CONNECTED state, the terminal device can request to configure a PUR or release a PUR configuration. The base station can decide to configure a PUR based on the terminal device's request, the terminal device's subscription information, and / or local policies. The PUR is only valid in the cell where the PUR configuration is received. When in an RRC_IDLE state, the PUR configuration is maintained. When the upper layer requests to establish or resume an RRC connection, the terminal device has a valid PUR, and meets the specified timing advance (TA) verification conditions, the PUR transmission is used. The transmission using the PUR allows a preconfigured uplink resource to be used for one uplink transmission from an RRC_IDLE state without performing a random access procedure. When the upper layer requests to establish or resume an RRC connection, and the terminal device has a valid PUR for transmission, and the TA verification criteria, the transmission using the PUR is triggered.

[0193] Figure 8a shows a diagram of PUR configuration request and PUR configuration. The terminal device is in RRC_CONNECTED state and the cell enables PUR. The terminal device sends a PURConfigurationRequest message to indicate the requested resource information (e.g. number of occurrences, periodicity, time offset, transport block size, RRC acknowledgement or layer 1 acknowledgement preference, etc.) to the base station to indicate the PUR requirement. Alternatively, the terminal device can indicate to the base station to release the PUR configuration in the PURConfigurationRequest message. When the base station moves the terminal device to RRC_IDLE state, based on the previous terminal device PUR configuration request, subscription information and / or local policy, the base station can decide to provide the terminal device with PUR resources or release the existing PUR resources. The base station includes the detailed information of the PUR configuration or the PUR release indication in the RRCConnectionRelease message. For the terminal device using control plane PUR transmission, the base station can provide the PUR configuration including the PUR configuration ID; when the terminal device does not use the PUR resource to establish the RRC connection, the terminal device includes the PUR configuration ID(s) in the RRCConnectionSetupComplete message. When the terminal device accesses another cell which does not support PUR or when the PUR resource is not used within the configured consecutive number of times, the terminal device and the base station can implicitly release the PUR configuration.

[0194] The control plane PUR transmission has the following characteristics: the uplink user data is sent using the PUR resource on the CCCH through the NAS message connected by the RRC EarlyDataRequest message; if there is no downlink data, the base station can terminate the process by sending a layer 1 acknowledgement, a MAC time advance command, an RRC EarlyDataComplete message without user data; the downlink user data can be transmitted on the CCCH in the NAS message connected by the RRC EarlyDataComplete message; there is no need to switch to the RRC_CONNECTED state for PUR transmission.

[0195] In one possible example, figure 8b shows a diagram of data transmission using PUR for control plane CIoT EPS optimization. The terminal device confirms that the PUR resource is valid (e.g. the PUR is enabled in the cell, the valid time advance, etc.). The terminal device has verified that the PUR resource is valid according to the configured condition. The specific steps are as follows:

[0196] Step 1, the terminal device sends RRC EarlyDataRequest message and user data, wherein the terminal device transmits on PUR resource. If the uplink data is too large to be contained in RRC EarlyDataRequest, the terminal device can send RRCConnectionRequest using PUR resource. The procedure will fall back to the traditional RRC connection establishment procedure, and a new cell radio network temporary identifier can be allocated. After step 1, the base station can request the terminal device to abort the transmission using PUR by sending layer 1 fallback indication. The terminal device operation after receiving the layer 1 fallback indication is performed by the terminal device.

[0197] Steps 2-6 are the same as steps 2-6 in FIG. 7a.

[0198] Step 7a, if the base station realizes that there is no downlink data or signaling to be processed, the base station can send layer 1 confirmation to the terminal device. Optionally, the layer 1 confirmation includes time advance adjustment to update the TA and terminate the procedure.

[0199] Step 7b, if the base station realizes that there is no further data or signaling, the base station sends a time advance command to update the TA and terminate the procedure.

[0200] Steps 7c-8 are the same as steps 7-8 in FIG. 7a.

[0201] In another possible example, as shown in FIG. 8c is a data transmission diagram using PUR for control plane CIoT 5GS optimization. The terminal device confirms that the PUR resource is valid (such as enabling PUR in the cell, valid time advance, etc.). The terminal device has verified that the PUR resource is valid according to the configured conditions. The specific steps are as follows: step 1 is the same as step 1 in FIG. 7a. Steps 2-6 are the same as steps 2-6 in FIG. 7b. Steps 7a-7b are the same as steps 1 in FIG. 8b. Steps 7c-8 are the same as steps 7-8 in FIG. 7b.

[0202] Among them, the user plane PUR transmission has the following characteristics: the terminal device is in RRC_IDLE state and there is valid PUR resource; the NCC is provided to the terminal device in the RRCConnectionRelease message carrying the suspension indication; the uplink user data is sent on the DTCH multiplexed with the RRCConnectionResumeRequest message on the CCCH; the downlink user data can be transmitted on the DTCH multiplexed with the RRCConnectionRelease message on the DCCH; the uplink and downlink user data are encrypted, wherein the key is derived based on the NCC provided in the RRCConnectionRelease message of the previous RRC connection; the RRCConnectionRelease message is integrity protected and encrypted using the newly derived key; there is no need to switch to the RRC_CONNECTED state for PUR transmission.

[0203] In one possible example, as shown in FIG. 8d, a data transmission diagram using PUR for user plane CIoT EPS optimization. First, the terminal device confirms that the PUR resource is valid (for example, PUR is enabled in the cell, valid time alignment, etc.). The terminal device has verified that the PUR resource is valid according to the configured conditions. The specific steps are as follows: step 1 is the same as step 1 of FIG. 7a, the difference is that the terminal device transmits not the resource allocated in the random access response, but transmits on the PUR resource. Steps 2-7 are the same as steps 2-7 in FIG. 7a. Step 8 is the same as step 8 in FIG. 7a, but can also include a time advance command.

[0204] In another possible example, as shown in FIG. 8e, a data transmission diagram using PUR for user plane CIoT 5GS optimization. First, the terminal device confirms that the PUR resource is valid (for example, PUR is enabled in the cell, valid time alignment, etc.). The terminal device has verified that the PUR resource is valid according to the configured conditions. The specific steps are as follows: step 1 is the same as step 1 in FIG. 8d. Steps 2-7 are the same as steps 2-7 in FIG. 8b. Step 8 is the same as step 8 in FIG. 8c, but can also include a time advance command.

[0205] In the prior art, both PUR and EDT are small packet data transmission in RRC_IDLE state. PUR is PRACH-free small packet data transmission, and can only be initiated in the last serving cell. EDT data transmission can be initiated in any cell supporting EDT. In addition, one triggering of EDT and PUR supports only one uplink data transmission and optional one downlink data transmission. If the terminal device needs to perform multiple uplink data transmissions, it needs to initiate PUR and EDT multiple times, resulting in a large amount of air interface signaling transmission.

[0206] To solve the above problems, the present application provides a data transmission method, device and system. By configuring a preconfigured uplink resource or a configured grant resource for the terminal device, the terminal device does not need to trigger the process multiple times when performing multiple uplink data transmissions. When using EDT for data transmission, the number of random access initiations can be reduced, the sending of RRC EarlyDataComplete message can be reduced, and when using PUR for data transmission, the terminal device is not limited to the last serving cell, enabling the terminal device to perform PUR transmission in a new cell, reducing the sending of RRC EarlyDataComplete / RRCConnectionSetup message, reducing the number of air interface signaling, and enhancing the uplink capacity of narrowband internet of things non-terrestrial network.

[0207] A data transmission method provided by the embodiments of the present application will be described in detail below with reference to FIGS. 9-11.

[0208] It should be noted that the names of messages between various network elements in the following embodiments of the present application or the names of various parameters in the messages are only examples, and other names can also be used in specific implementations, which are not limited in the embodiments of the present application.

[0209] It should be noted that the embodiments of the present application can be mutually borrowed or referred to each other. For example, the same or similar steps, method embodiments, communication system embodiments and device embodiments can be mutually referred to, without limitation.

[0210] In the embodiments of the present application, the specific structure of the execution subject of the data transmission method is not particularly limited, as long as the program recording the code of the data transmission method of the present application can be run to communicate according to the data transmission method of the present application. For example, the execution subject of the data transmission method provided by the present application can be a functional module capable of calling and executing a program in a terminal device, or a communication device applied in a terminal device, such as a chip, a chip system, an integrated circuit, etc. These chips, chip systems, and integrated circuits can be arranged inside the terminal device or independent of the terminal device, which is not limited in the present application. The execution subject of the method for indicating data transmission provided by the present application can be a functional module capable of calling and executing a program in a network device, or a communication device applied in a network device, such as a chip, a chip system, an integrated circuit, etc. These chips, chip systems, and integrated circuits can be arranged inside the network device or independent of the network device, which is not limited in the present application. The following embodiments take the execution subject of the data transmission method as a terminal device and the execution subject of the data transmission method as a network device as examples for description. The schemes of the following embodiments can be combined for use without conflict.

[0211] As shown in FIG. 9, FIG. 9 shows a data transmission method provided by an embodiment of the present application, which includes the following steps:

[0212] In step 901, the terminal device receives first configuration information from the network device. Correspondingly, the network device sends the first configuration information to the terminal device. The first configuration information is used for the terminal device to perform initial data transmission, or the terminal device to perform subsequent data transmission after performing initial data transmission.

[0213] In the embodiments of the present application, the first configuration information can include uplink grant information, which is used to indicate the uplink grant parameter used by the terminal device for data transmission. For example, the uplink grant parameter includes one or more of the following parameters: channel element mode (CE mode), physical uplink shared channel (PUSCH) resource unit number, PUSCH physical resource block (PRB) allocation information, PUSCH modulation and coding mode, and PUSCH repetition number. The uplink grant parameter can also include other parameters, which are not limited in the present application.

[0214] In the embodiments of the present application, the first configuration information for the terminal device to perform initial data transmission means that the terminal device sends data to the network device for the first time according to the first configuration information after receiving the first configuration information. The first configuration information for the terminal device to perform subsequent data transmission after performing initial data transmission means that the terminal device sends data to the network device according to the first configuration information after sending data to the network device for the first time according to the first configuration information.

[0215] In a possible implementation, in step 901, the network device sends the first configuration information to the terminal device in the form of a dedicated message. Correspondingly, the terminal device receives only one first configuration information sent by the network device. For example, the network device sends specific first configuration information to the terminal device, and the terminal device receives the first configuration information from the network device.

[0216] In a possible embodiment, the first configuration information can be a random access response (RAR), and the RAR carries uplink grant resources.

[0217] In a possible embodiment, in the case that the terminal device performs initial data transmission according to the RAR, the first configuration information can be a preconfigured uplink resource (PUR), the PUR includes uplink grant resources, and the PUR can further include one or more of the following parameters: a PUR period, a number of opportunities, and a bias, and the terminal device performs data transmission according to the PUR.

[0218] In a possible embodiment, the first configuration information can be a configured grant (CG) resource, and the terminal device performs initial data transmission through the CG resource. The CG resource is used for early data transmission (EDT).

[0219] As an example, the terminal device receives an RRC connection release (RRCConnectionRelease) message from the network device, which includes a CG resource for EDT. The terminal device evaluates the CG resource to be valid, triggers EDT, and sends data to the network device for the first time through the CG resource.

[0220] In a possible embodiment, the first configuration information can be dynamic grant information, and the DCI indicating the dynamic grant information addresses to the EDT-RNTI, and the terminal device performs subsequent data transmission through the dynamic grant resource, on the premise that the terminal device performs initial data transmission through the CG resource.

[0221] For example, the DCI indicating the dynamic grant information addresses to the cell-RNTI in the EDT transmission based on the user plane.

[0222] In another possible implementation, the step 901 in the embodiment of the present application can be implemented in the following manner: the network device sends the first configuration information to the terminal device in the form of broadcast. Correspondingly, the terminal device receives the first configuration information broadcast from the network device. For example, the network device sends multiple first configuration information to multiple terminal devices, and one terminal device selects one of the multiple first configuration information for initial data transmission or subsequent data transmission after receiving the multiple first configuration information sent by the network device.

[0223] In a possible embodiment, the first configuration information can be one or more preconfigured uplink resources (PURs), and each of the one or more PURs includes an uplink grant resource, and the terminal device can perform subsequent data transmission according to the uplink grant resource.

[0224] It can be understood that, in the case that the network device sends the uplink grant information to the terminal device in the form of broadcast system message and the terminal device enters the RRC_IDLE state, the terminal device does not need to perform random access, otherwise, the terminal device needs to perform random access to obtain the uplink grant information from the network device.

[0225] The step 902 is that the terminal device sends data to the network device according to the first configuration information in the RRC connected state. Correspondingly, the network device receives the data sent from the terminal device.

[0226] In a possible embodiment, the first configuration information is a RAR carrying an uplink grant resource, the terminal device performs initial data transmission in a message 3 (Msg3) according to the RAR, that is, the terminal device performs initial data transmission to the network device through the Msg3, and correspondingly, the network device receives the data initially sent from the terminal device.

[0227] For example, in control plane transmission, the terminal device sends an RRC early data request (RRCEarlyDataRequest) message to the network device, and correspondingly, the network device receives the RRC early data request (RRCEarlyDataRequest) message from the terminal device.

[0228] For another example, in user plane data transmission, the terminal device sends an RRC connection resume request (RRCConnectionResumeRequest) message to the network device, and correspondingly, the network device receives the RRC connection resume request (RRCConnectionResumeRequest) message from the terminal device.

[0229] In a possible embodiment, in the case that the terminal device performs initial data transmission through the RAP carrying the uplink grant resource, the first configuration information is PUR, and the terminal device performs subsequent data transmission according to the PUR. Correspondingly, the network device receives the data transmitted by the terminal device. In order to distinguish the initial data transmission and the subsequent data transmission of the terminal device, the data can be transmitted through different messages.

[0230] For example, in control plane data transmission, the terminal device sends an uplink information transmission (ULInformationTransfer) message, or an RRC early data request (RRCEarlyDataRequest) message without carrying a service temporary mobile subscriber identity (S-TMSI), or other RRC messages for sending NAS to the network device. Correspondingly, the network device receives the uplink information transmission (ULInformationTransfer) message, or the RRC early data request (RRCEarlyDataRequest) message without carrying the service temporary mobile subscriber identity (S-TMSI), or other RRC messages for sending NAS from the terminal device.

[0231] For another example, in user plane transmission, the terminal device sends user data to the network device, or sends an RRC connection resume request (RRCConnectionResumeRequest) message without carrying a resume identifier (Resume ID) / inactive-radio network temporary identifier (I-RNTI).

[0232] The Resume ID / I-RNTI is used to identify or index the terminal device context in the network device, and the terminal device context is composed of two parts, the first part is used to identify the network device identifier, and the second part is used to identify the terminal device context established or stored by the network device.

[0233] It can be understood that the first part and the second part are only names, and the first part can be used to identify the terminal device context established or stored by the network device, and the second part can be used to identify the network device identifier, which is not limited in the embodiments of the present application.

[0234] It can be understood that the terminal device context can only include the first part or only include the second part. For example, the terminal device sends subsequent data transmission requirements, and can not need to send S-TMSI to identify the terminal device, but is identified by the terminal device identifier (such as UE S1 ID) between the network device and the core network. The terminal device receives downlink control information addressed to the cell radio network temporary identifier within the timer of listening to the physical downlink control channel, and then the data transmission is successful, otherwise the data transmission fails. Optionally, the terminal device retransmits at the next preconfigured uplink resource occasion.

[0235] In a possible embodiment, the first configuration information is a CG resource, and the terminal device performs initial data transmission according to the CG resource.

[0236] For example, when the data transmission is based on the control plane, the terminal device sends an RRC early data request (RRCEarlyDataRequest) message to the network device, and correspondingly, the network device receives the RRC early data request (RRCEarlyDataRequest) message from the terminal device. For another example, when the user plane transmission, the terminal device sends an RRC connection resume request (RRCConnectionResumeRequest) message to the network device, and correspondingly, the network device receives the RRC connection resume request (RRCConnectionResumeRequest) message from the terminal device.

[0237] In a possible embodiment, when the terminal device performs initial data transmission according to the CG resource, the first configuration information is dynamic authorization information, and the terminal device performs subsequent data transmission according to the dynamic authorization information.

[0238] For example, the terminal device can perform subsequent data transmission at a fixed CG occasion (CG occasion), or the terminal device performs transmission through dynamic authorization resources.

[0239] The data transmission method provided by the embodiments of the present application, because in the prior art, the preconfigured uplink resource and the early data transmission are both small packet data transmission in the RRC_IDLE state. For the preconfigured uplink resource, it is small packet data transmission without physical random access channel, and can only initiate the preconfigured uplink resource in the last serving cell. For the early data transmission, random access can be initiated in any cell supporting early data transmission to perform early data transmission. However, triggering early data transmission and preconfigured uplink resource only supports one uplink data transmission and optional one downlink data transmission. If the terminal device needs to perform multiple uplink data transmissions, the preconfigured uplink resource and the early data transmission need to be initiated multiple times, resulting in a large amount of air interface signaling transmission. Therefore, in the method, the first configuration information received by the terminal device can indicate initial data transmission of the terminal device, or can indicate subsequent data transmission of the terminal device after the initial data transmission, and the terminal device performs data transmission in the RRC non-connected state according to the first configuration information. The first configuration information includes uplink authorization resources, so that the network device flexibly configures uplink authorization resources for the terminal device on demand, multiple data transmissions do not need to trigger the process multiple times, reduces the number of air interface signaling, and enhances the system capacity of the uplink.

[0240] In a possible embodiment of the present application, the terminal device receives the first configuration information from the network device through a system message. Correspondingly, the network device sends the first configuration information to the terminal device through a system message. The first configuration information includes one or more uplink grant resources, each of the one or more uplink grant resources corresponds to a radio network temporary identifier, or corresponds to one or more geographical areas, or corresponds to one or more beams.

[0241] The uplink grant resource can be associated with a radio network temporary identifier, which is used to identify an uplink grant resource. For example, a first radio network temporary identifier corresponds to a first uplink grant resource. The terminal device sends data to the network device through the first uplink grant resource. The network device can send a physical layer or MAC layer command scrambled with the first radio network temporary identifier. The terminal device receives the physical layer or MAC command, which is addressed to the first radio network temporary identifier. The terminal device thus parses the command, thereby realizing the network device managing and scheduling the terminal device using the uplink grant resource.

[0242] As an example, the first configuration information includes a plurality of uplink grant resources, wherein an uplink grant resource X in the plurality of uplink grant resources corresponds to a radio network temporary identifier X. For example, an identifier of a PUR or a radio network temporary identifier of a PUR is used to identify a PUR configuration information, or in other words, to identify an uplink grant resource.

[0243] The uplink grant resource can be associated with a specific geographical area, and the specific geographical area includes one or more geographical areas. Each geographical area can be indicated by a reference point position and a radius, or by a beam. It can be understood that the corresponding uplink grant resource can only be used when the terminal device enters one or more geographical areas. This helps the network to manage the coverage and optimize resource allocation.

[0244] As an example, the first configuration information includes a plurality of uplink grant resources, wherein an uplink grant resource X in the plurality of uplink grant resources corresponds to a geographical area A, or corresponds to geographical areas A-C. For example, a PUR corresponds to one or more geographical areas.

[0245] As a specific implementation, the terminal device receives a plurality of PURs indicated by a broadcast system message. The terminal device applies the PUR corresponding to the geographical area based on the location of the terminal device to perform data transmission.

[0246] In a possible implementation, if multiple terminal devices compete, for example, two terminal devices use the same PUR for data transmission, the terminal device fails to successfully transmit data, at which time the terminal device can attempt to transmit data at the next PUR occasion, or the terminal device can also attempt to transmit at a PUR occasion of other PUR configurations corresponding to the geographic area.

[0247] The manner in which the terminal device determines that the data is unsuccessfully transmitted can be:

[0248] Manner one: the network device configures a timer for detecting PUR data transmission failure in a broadcast system message, and the terminal device starts the timer at the initial data time. Before the timer expires, if the terminal device still fails to successfully transmit data, it is determined that the PUR data transmission fails.

[0249] Manner two: the network device configures a maximum number of transmission times of PUR data in a broadcast system message. After the terminal device attempts the maximum number of times, it is determined that the PUR data transmission fails.

[0250] The uplink grant resource can be associated with a specific beam. By associating the uplink grant resource with the beam, the network device can guide the terminal device to use the best beam for data transmission, thereby improving the communication quality.

[0251] As an example, the first configuration information includes a plurality of uplink grant resources, wherein an uplink grant resource X in the plurality of uplink grant resources corresponds to a beam A, or corresponds to beams A-C.

[0252] In a possible embodiment of the present application, in the case where the first configuration information includes the uplink grant resource, before the terminal device receives the first configuration information from the network device, the method provided by the embodiment of the present application includes: the terminal device receives random access resources from the network device through a system message. Correspondingly, the network device sends the random access resources to the terminal device through the system message. The random access resources are used by the terminal device to acquire the first configuration information based on random access. The terminal device initially transmits data to the network device.

[0253] The random access resources are used for preconfigured uplink resources (PUR), including but not limited to time-frequency resources of a physical random access channel (PRACH) and a preamble.

[0254] In a possible implementation, the network device broadcasts first information to the terminal device. Correspondingly, the terminal device receives the first information from the network device. The first information is used to indicate the random access resources of the PUR.

[0255] In a possible embodiment of the present application, the terminal device receives the first indication information from the network device through the system message while the network device sends the random access resource to the terminal device through the system message. Correspondingly, the network device sends the first indication information to the terminal device through the system message. The first indication information includes the condition for determining whether to acquire the uplink grant resource based on the random access, and / or the search space or the timer for monitoring the PDCCH.

[0256] In the present application, the condition for indicating the terminal device to determine the trigger of the PUR includes but is not limited to the data volume, the RSRP threshold, which is not limited in the present application.

[0257] In the present application, the timer for monitoring the PDCCH is used for the terminal device to determine whether the current data transmission is successful and whether the data retransmission is needed.

[0258] In a possible implementation, the terminal device initially sends data to the network device, including: the terminal device triggers the preconfigured uplink resource based on the random access, and sends the random access preamble for the preconfigured uplink resource to the network device. The terminal device receives the random access response from the network device, and the random access response carries the uplink grant resource. The terminal device initially sends data to the network device according to the uplink grant resource. The terminal device receives the message 4 (Msg4) from the network device, and the message 4 is used to indicate that the terminal device completes the random access.

[0259] In a possible embodiment of the present application, before the terminal device acquires the uplink grant resource based on the random access, the method provided in the present application further includes: the terminal device receives the first message from the network device. Correspondingly, the network device sends the first message to the terminal device. The first message is used to indicate that the terminal device enters the RCC idle state, and the first message does not include the first configuration information.

[0260] As an example, the first message is the RCC connection release (RRCConnectionRelease) message, which does not include the preconfigured uplink resource, or includes the preconfigured uplink resource but the preconfigured uplink resource is invalid, which is not limited in the present application.

[0261] For example, the network device sends an RRCConnectionRelease message to the terminal device to trigger the terminal device to enter an RCC_IDLE state. In the case that the RRCConnectionRelease message does not carry a PUR or carries an invalid PUR, the terminal device triggers a random access-based PUR and sends a random access preamble for the PUR to the network device. The terminal device receives a random access response from the network device, which includes a temporary C-RNTI. The terminal device sends data to the network device for the first time in a message 3 (Msg3) according to an uplink grant resource carried in the random access response.

[0262] In a possible embodiment of the present application, the terminal device acquires an uplink grant resource based on random access. The method provided in the embodiment of the present application further includes that the terminal device indicates a subsequent data transmission requirement.

[0263] The terminal device indicates the subsequent data transmission requirement, which means that the terminal device sends data to the network device again according to a requirement after sending data to the network device for the first time based on the uplink grant resource acquired by the terminal device based on random access.

[0264] The subsequent data transmission requirement includes but is not limited to a preconfigured uplink resource period, a bias, a preconfigured uplink resource occasion number, and transport block size (TBS) information. It can be understood that the subsequent data transmission requirement can also be referred to as a preconfigured uplink resource requirement or a preconfigured uplink resource configuration requirement, which is not limited in the examples of the present application.

[0265] In a possible implementation, in the case that the terminal device receives an uplink grant resource from the random access response of the network device, the terminal device indicating the subsequent data transmission requirement can be implemented in the following manner:

[0266] Method one: The terminal device sends a second message to the network device based on the uplink grant resource. Correspondingly, the network device receives the second message from the terminal device. The second message includes a buffer status report (BSR) or subsequent data transmission request information indicated by the terminal device, and the second message is used for initial data transmission.

[0267] As an example, when the terminal device sends data to the network device for the first time according to the random access response carrying the uplink grant resource, the terminal device sends a BSR or information for indicating subsequent data transmission to the network device.

[0268] In a possible implementation, when performing data transmission based on a user plane, the terminal device sends data to the network device for the first time through Msg3, and the network device obtains subsequent data transmission requirements of the terminal device sent before the terminal device enters an RRC_IDLE state (i.e., the terminal device is in an RRC_CONNECTED state) after receiving the Msg3.

[0269] In a second method, the terminal device sends a buffer status report to the network device by using a medium access control channel element (MAC CE). Correspondingly, the network device receives the buffer status report from the terminal device.

[0270] As an example, the terminal device sends the BSR to the network device by using the MAC CE in a process of triggering preconfigured uplink resources based on random access.

[0271] In a third method, after receiving a response of conflict resolution from the network device, the terminal device sends user equipment assistance information (UEAssistanceInformation, UAI) to the network device. Correspondingly, the network device receives the UAI from the terminal device.

[0272] As an example, after receiving a message 4 (Msg4) from the network device for instructing the terminal device to complete random access, the terminal device sends a UAI message to the network device for indicating subsequent data transmission requirements.

[0273] In a possible embodiment of the present application, in a case where the uplink grant resource included in the first configuration information is a configured grant resource, the terminal device performs subsequent data transmission after performing initial data transmission, including: in a case where the terminal device performs data transmission based on a control plane, the terminal device sends an uplink information transfer message or an RRC early data request message without carrying a service temporary mobile user identifier to the network device. Alternatively, in a case where the terminal device performs data transmission based on a control plane, the terminal device sends data or an RRC connection resume request message to the network device, and the RRC connection resume request message does not carry a first identifier used by the network device to identify a terminal device context corresponding to the terminal device. For specific implementation manners, refer to the above embodiments, which are not described here again.

[0274] In a possible embodiment of the present application, in a case where the one or more uplink grant resources included in the first configuration information are configured grant resources, the method provided in the embodiment of the present application includes: the terminal device receives second indication information from the network device. Correspondingly, the network device sends the second indication information to the terminal device.

[0275] The second indication information is used for indicating one or more of the following: one or more cell identities corresponding to the first configured grant resource of the terminal device, or a radio network temporary identifier (RNTI) corresponding to the first configured grant resource, or a radio network temporary identifier (CS-RNTI) for data retransmission corresponding to the first configured grant resource, or a timing advance (TA) validity condition, or a condition for the terminal device to determine a trigger for data transmission in an RRC non-connected state, or a search space or a timer for the terminal device to monitor a physical downlink control channel. The first configured grant resource is one of one or more uplink grant resources.

[0276] As an example, the terminal device receives the configuration grant information for early data transmission and the second indication information. Correspondingly, the network device sends the configuration grant information for early data transmission and the second indication information to the terminal device.

[0277] For example, the network device sends the CG information for EDT and the second indication information to the terminal device through an RRCConnectionRelease message. The second indication information is used for indicating one or more of the following: an EDT-RNTI, or an RNTI for EDT retransmission, or a TA validity condition (such as a TA timer, a reference signal received power (RSRP) change threshold, an RSRP threshold, a distance change threshold) for EDT, or a condition (such as a data volume, an RSRP threshold) for determining a trigger for EDT, or a search space or a timer for the terminal device to monitor a PDCCH.

[0278] In one possible embodiment of the present application, the method provided by the embodiments of the present application further includes: the terminal device receives an initial data transmission response from the network device. Correspondingly, the network device sends the initial data transmission response to the terminal device.

[0279] The initial data transmission response can be: downlink data, or a physical layer acknowledgement (L1 ACK) or a downlink control information (DCI) of a physical downlink control channel (PDCCH) addressed to a radio network temporary identifier, or a physical layer acknowledgement (L1 ACK) or a downlink control information (DCI) of a physical downlink control channel (PDCCH) addressed to a cell radio network temporary identifier (C-RNTI), or a downlink control information (DCI) of a physical downlink control channel (PDCCH) addressed to a radio network temporary identifier (CS-RNTI) for data retransmission.

[0280] In a possible implementation, the terminal device and the network device support hybrid automatic repeat request (HARQ) of the EDT, and after the terminal device initially transmits data to the network device through the configured grant, the network device transmits an initial data transmission response to the terminal device according to the received data.

[0281] It should be noted that the initial data transmission response is a received physical layer acknowledgement (L1 ACK) or downlink control information (DCI) of a physical downlink control channel (PDCCH) addressed to a wireless network temporary identifier, which is applicable to user plane EDT and control plane EDT; the initial data transmission response is a received physical layer acknowledgement (L1 ACK) or downlink control information (DCI) of a physical downlink control channel (PDCCH) addressed to a cell wireless network temporary identifier (C-RNTI), which is only applicable to user plane EDT; and the initial data transmission response is DCI of a PDCCH addressed to a CS-RNTI, wherein the uplink grant resource included in the DCI is used for data retransmission.

[0282] In a possible embodiment of the present application, in the case that the terminal device performs subsequent data transmission after performing initial data transmission, the method further comprises: the terminal device receives a dynamic grant from the network device. Correspondingly, the network device transmits a dynamic grant to the terminal device. The terminal device transmits data to the network device according to the dynamic grant. Correspondingly, the network device receives data from the terminal device.

[0283] As an example, the network device configures a dynamic grant for the terminal device, and indicates that DCI of the dynamic grant is addressed to the EDT-RNTI.

[0284] Optionally, for user plane EDT transmission, the DCI of the dynamic grant can also be addressed to the C-RNTI.

[0285] As an example, the terminal device performs subsequent data transmission at a fixed CG occasion (CG occasion), or transmits data through a dynamic grant resource.

[0286] In a possible embodiment of the present application, before the terminal device transmits data to the network device according to the dynamic grant, the request for dynamic scheduling can be implemented in the following ways:

[0287] Method one: when the terminal device transmits data to the network device based on an uplink grant resource (such as performing initial data transmission through a configured grant or transmitting data to the network device through a dynamic grant), the terminal device indicates a BSR or indicates allocation of an uplink grant resource.

[0288] As an example, when the terminal device initially transmits data to the network device according to the configured grant, the terminal device transmits the BSR to the network device or transmits the uplink grant resource.

[0289] Option 2: The terminal device transmits the buffer status report to the network device using a medium access control channel element (MAC CE).

[0290] As an example, the terminal device transmits the BSR to the network device using the MAC-CE in the process of early data transmission.

[0291] The following takes the network device as a base station (ng-eNB) as an example to illustrate the preconfigured resource (PUR) based on random access (RA) and the early data transmission (EDT) based on configured grant (CG) in two cases:

[0292] Case 1: Preconfigured uplink resource based on random access

[0293] Referring to FIG. 10, FIG. 10 is a flowchart of a data transmission method based on PUR according to the RA, and the method comprises the following steps:

[0294] Step 1001: The base station broadcasts a system message to the terminal device, including random access resources. Correspondingly, the terminal device receives the system message from the base station, including the random access resources. The random access resources are used for PUR.

[0295] Optionally, the base station can also broadcast first indication information to the terminal device. Correspondingly, the terminal device receives the first indication information from the base station. As an example, the first indication information is used to indicate the condition for judging the trigger of PUR, or the search space or timer for the user equipment to listen to the PDCCH.

[0296] The random access resources include PRACH time-frequency resources and a preamble.

[0297] Step 1002: The terminal device evaluates the condition based on RA and triggers the PUR process based on RA.

[0298] As an example, the base station triggers the user equipment to enter the RRC_IDLE state and judges whether there is PUR.

[0299] In a possible implementation, the base station sends an RRCConnectionRelease message to the user equipment, wherein in the case that the PUR configuration is not carried in the RRCConnectionRelease message or the PUR configuration carried is invalid, the user equipment triggers the PUR based on RA and determines the random access preamble for PUR when the uplink data arrives.

[0300] Step 1003, the terminal device sends a random access preamble to the base station. Correspondingly, the base station receives the random access preamble from the terminal device.

[0301] Step 1004, the terminal device receives a RA response (RAR) from the base station. Correspondingly, the base station sends the RAR to the terminal device.

[0302] The RAR carries an uplink grant resource and a temporary C-RNTI.

[0303] Step 1005, the terminal device sends a message 3 (Msg3) to the base station according to the uplink grant resource carried in the RAR. Correspondingly, the base station receives the Msg3 from the terminal device.

[0304] It can be understood that the terminal device sends the message 3 to the base station for the first time, and the data sent by the terminal device to the base station is included in the Msg3.

[0305] In a possible implementation, in the case of sending data based on the control plane, the terminal device sends an RRC EarlyDataRequest message to the base station. Correspondingly, the base station receives the RRC EarlyDataRequest message from the terminal device.

[0306] In another possible implementation, in the case of sending data based on the user plane, the terminal device sends an RRCConnectionResumeRequest message to the base station. Correspondingly, the base station receives the RRCConnectionResumeRequest message from the terminal device.

[0307] Step 1006, the terminal device sends a subsequent data transmission indication to the base station. Correspondingly, the base station receives the subsequent data transmission indication from the terminal device.

[0308] In a possible implementation, when the terminal device sends data to the base station for the first time, that is, in step 1005, the terminal device sends a BSR or a subsequent PUR request information to the base station. Correspondingly, the base station receives the BSR or the subsequent PUR request information from the terminal device. The PUR request information includes one or more of a PUR period, an offset, a number of PUR occasions, and TBS information, which are not limited in the embodiments of the present application.

[0309] In another possible implementation, in the procedure that the terminal device evaluates the RA-based condition and triggers the RA-based PUR, i.e., step 1002, the terminal device sends a BSR to the base station through a MAC-CE. Correspondingly, the base station receives the BSR from the terminal device.

[0310] In another possible implementation, after the terminal device completes the random access procedure, i.e., after step 1007, the terminal device sends a UAI message to the base station to indicate the PUR request information. Correspondingly, the base station receives the UAI message from the terminal device.

[0311] In another possible implementation, in the case of user plane transmission data, after the terminal device sends data to the base station for the first time, the base station obtains the PUR request information sent by the terminal device before entering the RRC_IDLE state.

[0312] Step 1007, the terminal device receives a message 4 (Msg4) from the base station. Correspondingly, the base station sends the Msg4 to the terminal device. The Msg4 is used to indicate that the terminal device successfully completes the RA procedure.

[0313] It can be understood that when the RA procedure is successfully completed, it indicates that the terminal device completes the initial transmission of data.

[0314] Step 1008, the terminal device receives a PUR configuration from the base station. Correspondingly, the base station sends the PUR configuration to the terminal device. The PUR configuration includes one or more of the following: a period of the PUR, a bias, a number of PUR occasions, uplink grant information, a PUR-RNTI, a PUR configuration ID, a number of consecutive PUR occasions that can be skipped before the PUR is implicitly released, and a search space configuration of the PUR.

[0315] In a possible implementation, the base station sends the PUR configuration to the terminal device in the form of a broadcast system message. It should be noted that in the case that the base station sends the PUR configuration to the terminal device in the form of a broadcast system message, steps 1002-1007 can be skipped. Specifically, the base station sends multiple PUR configurations to the terminal device, wherein one PUR configuration ID or one PUR RNTI is used to identify one PUR configuration. When the terminal device receives the multiple PUR configurations indicated by the broadcast system message, the terminal device selects one of the PUR configurations to send data.

[0316] In another possible implementation, the base station sends the PUR configuration to the terminal device in a dedicated RRC message. Specifically, the base station sends an RRC message to the terminal device, and the RRC message is used to indicate the PUR configuration. The RRC message can be an RRC message that is not encrypted and / or integrity protected, or can be an RRC message that is encrypted and / or integrity protected.

[0317] Step 1009, the terminal device sends data to the base station according to the PUR configuration. Correspondingly, the base station receives the data from the terminal device.

[0318] The data in step 1009 is data that is subsequently sent by the terminal device.

[0319] In a possible implementation, in the case of sending data based on the control plane, the terminal device sends an ULInformationTransfer message, or an RRC EarlyDataRequest message that does not carry an S-TMSI, or other RRC messages that carry NAS to the base station.

[0320] In another possible implementation, in the case of sending data based on the user plane, the terminal device sends user data, or an RRCConnectionResumeRequest message that does not carry a Resume ID / I-RNTI to the base station.

[0321] Step 1010, the terminal device receives third indication information from the base station. Correspondingly, the base station sends the third indication information to the terminal device.

[0322] The third indication information is used to indicate the end of the PUR, or is used to indicate that the terminal device enters the RRC_CONNECTED state.

[0323] Case 2, early data transmission based on configured grant

[0324] Referring to FIG. 11, FIG. 11 is a flow diagram of a data transmission method based on CG-EDT, and the method comprises the following steps:

[0325] Step 1101, the terminal device receives CG configuration information from the base station. Correspondingly, the base station sends the configuration information of the CG to the terminal device.

[0326] The configuration information of the CG is used for EDT.

[0327] In a possible implementation, the base station sends an RRCConnectionRelease message to the terminal device. Correspondingly, the terminal device receives the RRCConnectionRelease message from the base station. The RRCConnectionRelease message includes CG configuration information for EDT.

[0328] Optionally, the terminal device can further receive second indication information from the base station. Correspondingly, the base station sends the second indication information to the terminal device. The second indication information is used to determine an EDT-RNTI, or a CS-RNTI for EDT retransmission, or a TA validity condition for EDT, or a condition for triggering EDT, or a search space or a timer for PDCCH monitoring of the terminal device. For details, refer to the above embodiments, which are not described here again.

[0329] In step 1102, the terminal device evaluates that the CG resource is valid, and triggers an EDT procedure.

[0330] In step 1103, the terminal device sends data to the base station for the first time. Correspondingly, the base station receives the data from the terminal device.

[0331] As an example, the terminal device sends data to the base station through the CG resource.

[0332] In a possible implementation, in the case of sending data based on the control plane, the terminal device sends an RRCEarlyDataRequest message to the base station. Correspondingly, the base station receives the RRCEarlyDataRequest message from the terminal device.

[0333] In another possible implementation, in the case of sending data based on the user plane, the terminal device sends an RRCConnectionResumeRequest message to the base station. Correspondingly, the base station receives the RRCConnectionResumeRequest message from the terminal device.

[0334] It should be noted that the cell in which the terminal device triggering EDT is located can be a cell sending the CG configuration, or a last RRC connection cell of the terminal device; or can be another cell negotiated by the last RRC connection cell, for example, the other cell provides the CG configuration to the last RRC connection cell, and sends the CG configuration to the terminal device via the last RRC connection cell.

[0335] In step 1104, the terminal device receives an initial data transmission response from the base station. Correspondingly, the base station sends the initial data transmission response to the terminal device.

[0336] As an example, the terminal device and the base station support hybrid automatic repeat request of EDT, and the initial data transmission response can be one or more of the following: downlink data; or L1 ACK or DCI of PDCCH addressed to EDT-RNTI; or DCI of PDCCH addressed to C-RNTI received in user plane EDT transmission; or DCI of PDCCH addressed to CS-RNTI, which is not limited in the embodiments of the present application.

[0337] Wherein, the L1 ACK and the DCI addressed to the EDT-RNTI are applicable to both user plane EDT and control plane EDT; the L1 ACK and the DCI addressed to the C-RNTI are only applicable to user plane EDT. It is worth noting that the DCI of the PDCCH addressed to the CS-RNTI includes an uplink grant for data retransmission.

[0338] Step 1105, the terminal device receives the dynamic grant resource from the base station. Correspondingly, the base station sends the dynamic grant resource to the terminal device.

[0339] As an example, the DCI indicating the dynamic grant resource is addressed to the EDT-RNTI, and the DCI can also be addressed to the C-RNTI in user plane EDT transmission.

[0340] Step 1106, the terminal device sends data to the base station. Correspondingly, the base station receives data from the terminal device.

[0341] Wherein, the data sent by the terminal device to the base station in step 1106 is the data subsequently sent by the terminal device.

[0342] As an example, the terminal device sends data to the base station at a fixed CG occasion, or the terminal device sends data to the base station through a dynamic grant resource.

[0343] In the embodiments of the present application, before the terminal device transmits through the dynamic grant resource, the method further comprises: the terminal device requests dynamic scheduling from the base station.

[0344] In a possible implementation, when the terminal device sends data to the base station, such as steps 1103 and 1106, the terminal device sends a BSR or information for indicating allocation of an uplink grant resource to the base station.

[0345] In another possible implementation, in the EDT process, such as step 1102, the terminal device sends a BSR to the base station using a MAC-CE.

[0346] Step 1107, the terminal device receives third indication information from the base station. Correspondingly, the base station sends the third indication information to the terminal device.

[0347] The third indication information is used for indicating the end of EDT, or is used for indicating the terminal device to enter an RRC_CONNECTED state.

[0348] The above mainly introduces the scheme of the embodiments of the present application from the perspective of interaction between various network elements. It can be understood that, in order to implement the above functions, each network element, such as a terminal, a network device, etc., includes a corresponding structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application of the technical solution and design constraints. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0349] The embodiments of the present application can divide the functional units of the terminal device and the network device according to the above method examples. For example, each functional unit can be divided according to each function, or two or more functions can be integrated in one processing unit. The integrated unit can be realized in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division. When actually implemented, there can be another division manner.

[0350] The above describes the method of the embodiments of the present application in combination with FIGS. 9 to 11. The communication device provided by the embodiments of the present application for executing the above method is described below. Those skilled in the art can understand that the method and the device can be combined and referenced with each other, and the communication device provided by the embodiments of the present application can execute the steps performed by the terminal device and the network device in the above analysis method.

[0351] In the case of using integrated units, FIG. 12 shows the communication device involved in the above embodiments. The communication device 120 can include a communication module 1201 and a processing module 1202.

[0352] In an optional implementation manner, the communication device 120 can further include a storage module 1203 for storing program codes and data of the communication device.

[0353] In an aspect, the communication apparatus 120 is a terminal device, or a chip applied in a terminal device. In this case, the communication module 1201 is configured to support the communication apparatus to communicate with an external network element (e.g., a network device). For example, the communication module 1201 is configured to perform the signal transceiving operation of the terminal device in the method embodiments described above. The processing module 1202 is configured to perform the signal processing operation of the terminal device in the method embodiments described above.

[0354] In an example, the communication module 1201 is configured to perform the sending action performed by the terminal device in step 902 of FIG. 9 of the embodiments described above. The communication module 1201 is configured to perform the receiving action performed by the terminal device in step 901 of FIG. 9 of the embodiments described above.

[0355] In a possible embodiment, the processing module 1202 is configured to perform the processing action performed by the terminal device in step 902 of FIG. 9 of the embodiments described above.

[0356] In another aspect, the communication apparatus 120 is a network device, or a chip applied in a network device. In this case, the communication module 1201 is configured to support the communication apparatus to communicate with an external network element (e.g., a terminal device). For example, the communication module 1201 is configured to perform the signal transceiving operation of the network device in the method embodiments described above. The processing module 1202 is configured to perform the signal processing operation of the network device in the method embodiments described above.

[0357] In an example, the communication module 1201 is configured to perform the receiving action performed by the network device in step 902 of FIG. 9 of the embodiments described above. The communication module 1201 is configured to perform the sending action performed by the network device in step 901 of FIG. 9 of the embodiments described above.

[0358] The processing module 1202 can be a processor or a controller, for example, a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device, transistor logic, hardware component, or any combination thereof. It can implement or execute various example logical blocks, modules, and circuits described in connection with the disclosure. The processor can also be a combination of computing components, such as one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on. The communication module can be a transceiver, a transceiving circuit, or a communication interface, and so on. The storage module can be a memory.

[0359] When the processing module 1202 is the processor 1301 or the processor 1305, the communication module 1201 is the transceiver 1303, and the storage module 1203 is the memory 1302, the communication apparatus involved in the disclosure can be the communication device shown in FIG. 13.

[0360] FIG. 13 shows a schematic diagram of a hardware structure of a communication device according to an embodiment of the present application. The hardware structure of the terminal device and the network device according to the embodiments of the present application can refer to the structure shown in FIG. 13. The communication device includes a processor 1301, a communication line 1304, and at least one transceiver (for example, transceiver 1303 is shown in FIG. 13).

[0361] The processor 1301 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the embodiments of the present application.

[0362] The communication line 1304 can include a path for transmitting information between the above-mentioned components.

[0363] The transceiver 1303 uses any transceiver device to communicate with other devices or communication networks, such as Ethernet, a radio access network (RAN), a wireless local area network (WLAN), etc.

[0364] Optionally, the communication device can further include a memory 1302.

[0365] The memory 1302 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory 1302 can exist independently, and be connected to the processor 1301 through the communication line 1304. The memory 1302 can also be integrated with the processor 1301.

[0366] The memory 1302 is configured to store computer-executed instructions for implementing the solutions of the present application, and the processor 1301 is configured to control the execution. The processor 1301 is configured to execute the computer-executed instructions stored in the memory 1302, so as to implement the communication method provided in the following embodiments of the present application.

[0367] Optionally, the computer-executed instructions in the embodiments of the present application can also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

[0368] In a specific implementation, as an embodiment, the processor 1301 can include one or more CPUs, for example, CPU0 and CPU1 in FIG. 13.

[0369] In a specific implementation, as an embodiment, the communication device can include multiple processors, for example, the processor 1301 and the processor 1302 in FIG. 13. Each of the processors can be a single-CPU processor or a multi-CPU processor. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (for example, computer program instructions).

[0370] The embodiments of the present application further provide a communication apparatus, which includes a radio resource control (RRC) signaling interaction module, a medium access control (MAC) signaling interaction module, and a physical layer (PHY) signaling and data interaction module. The RRC signaling interaction module is configured to send and receive RRC signaling, the MAC signaling interaction module is configured to send and receive MAC-CE signaling, and the PHY signaling and data interaction module is configured to send and receive uplink / downlink control signaling and uplink / downlink data.

[0371] The embodiments of the present application further provide a communication apparatus, which can be a terminal device or a chip. The communication apparatus can be used to execute the above-mentioned method embodiments.

[0372] When the communication device is a terminal device, Fig. 14 shows a simplified structural schematic diagram of the terminal device. For the convenience of understanding and illustration, in Fig. 14, the terminal device takes a mobile phone as an example. As shown in Fig. 14, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device. The processor is mainly used for processing communication protocols and communication data, controlling the terminal device, executing software programs, processing data of the software programs, and the like. The memory is mainly used for storing software programs and data. The radio frequency circuit is mainly used for conversion between a baseband signal and a radio frequency signal and processing of the radio frequency signal. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. The input and output device, such as a touch screen, a display screen, a keyboard, and the like, is mainly used for receiving data input by a user and outputting data to the user. It should be noted that some types of terminal devices can not have the input and output device.

[0373] When data needs to be sent, the processor performs baseband processing on the data to be sent, and outputs a baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and transmits a radio frequency signal in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For the convenience of illustration, only one memory and one processor are shown in Fig. 14. In actual terminal device products, there can be one or more processors and one or more memories. The memory can also be referred to as a storage medium or a storage device, and the like. The memory can be independent of the processor or integrated with the processor. The embodiments of the present application do not limit this.

[0374] In the embodiments of the present application, the antenna and the radio frequency circuit having the functions of receiving and transmitting can be regarded as a transceiving unit of the terminal device, and the processor having the processing function can be regarded as a processing unit of the terminal device.

[0375] As shown in Fig. 14, the terminal device includes a transceiving unit 1410 and a processing unit 1420. The transceiving unit 1410 can also be referred to as a transceiver, a transceiver, a transceiving device, and the like. The processing unit 1420 can also be referred to as a processor, a processing board, a processing module, a processing device, and the like. Optionally, the devices in the transceiving unit 1410 for implementing the receiving function can be regarded as a receiving unit, and the devices in the transceiving unit 1410 for implementing the transmitting function can be regarded as a transmitting unit, that is, the transceiving unit 1410 includes the receiving unit and the transmitting unit. The transceiving unit can also be referred to as a transceiver, a transceiver, or a transceiving circuit, and the like. The receiving unit can also be referred to as a receiver, a receiver, or a receiving circuit, and the like. The transmitting unit can also be referred to as a transmitter, a transmitter, or a transmitting circuit, and the like.

[0376] For example, in an implementation, the processing unit 1420 is configured to perform the above-described method embodiments. The transceiver unit 1410 is configured to perform the transceiving operations related to the above-described method embodiments.

[0377] It should be understood that FIG. 14 is merely an example but not a limitation. The above-described terminal device including a transceiver unit and a processing unit can not depend on the structure shown in FIG. 14.

[0378] When the communication apparatus is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface. The processing unit can be a processor or a microprocessor integrated in the chip or an integrated circuit.

[0379] Embodiments of the present disclosure further provide a communication apparatus, which can be a network device or a chip. The communication apparatus can be configured to perform the above-described method embodiments. When the communication apparatus is a network device, the network device can be a base station.

[0380] FIG. 15 shows a simplified structure diagram of a base station. The base station includes a 1510 part and a 1520 part. The 1510 part is mainly configured to transceive radio frequency signals and convert the radio frequency signals and baseband signals. The 1520 part is mainly configured to perform baseband processing and control the base station. The 1510 part can be referred to as a transceiver unit, a transceiver, a transceiving circuit, or a transceiver, etc. The 1520 part is usually the control center of the base station and can be referred to as a processing unit, which is configured to control the base station to perform the processing operations of the network device side in the above-described method embodiments.

[0381] The transceiver unit of the 1510 part, which can also be referred to as a transceiver or a transceiver, etc., includes an antenna and a radio frequency unit, where the radio frequency unit is mainly configured to perform radio frequency processing. Optionally, the devices in the 1510 part for realizing the receiving function can be regarded as a receiving unit, and the devices for realizing the transmitting function can be regarded as a transmitting unit, i.e., the 1510 part includes a receiving unit and a transmitting unit. The receiving unit can also be referred to as a receiver, a receiver, or a receiving circuit, etc. The transmitting unit can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0382] The 1520 part can include one or more single boards, each of which can include one or more processors and one or more memories. The processors are configured to read and execute the programs in the memories to realize the baseband processing functions and control the base station. If there are multiple single boards, the single boards can be interconnected to enhance the processing capability. As an optional implementation, multiple single boards can share one or more processors, or multiple single boards can share one or more memories, or multiple single boards can share one or more processors at the same time.

[0383] For example, in an implementation, the 1520 part is configured to perform the above-mentioned method embodiments. The 1510 part is configured to perform the above-mentioned method embodiments related transceiving operations. For example, the 1510 part is configured to transmit or receive DFT-s-OFDM symbols or SC-QAM symbols.

[0384] It should be understood that FIG. 15 is merely an example but not a limitation. The above-mentioned network device including transceiving units and processing units can not depend on the structure shown in FIG. 15.

[0385] FIG. 16 is a structure diagram of a chip 160 according to an embodiment of the present application. The chip 160 includes one or more (including two) processors 1610 and a communication interface 1630.

[0386] Optionally, the chip 160 further includes a memory 1640, which can include read-only memory and random access memory, and provides operation instructions and data for the processor 1610. Part of the memory 1640 can further include non-volatile random access memory (NVRAM).

[0387] In some embodiments, the memory 1640 stores the following elements, execution modules or data structures, or their subsets, or their extended sets.

[0388] In the embodiments of the present application, corresponding operations are performed by calling operation instructions stored in the memory 1640 (which can be stored in an operating system).

[0389] In a possible implementation, the structure of the terminal and the network device is similar, and different devices can use different chips to implement respective functions.

[0390] The processor 1610 controls the processing operation of any of the terminal and the network device, and the processor 1610 can also be referred to as a central processing unit (CPU).

[0391] The memory 1640 can include read-only memory and random access memory, and provides instructions and data for the processor 1610. Part of the memory 1640 can further include NVRAM. For example, the memory 1640, the communication interface 1630 and the memory 1640 are coupled together through a bus system 1620, which can include a data bus, a power supply bus, a control bus and a state signal bus, etc. However, for the purpose of clear illustration, all kinds of buses are marked as the bus system 1620 in FIG. 16.

[0392] The method disclosed in the embodiments of the present application can be applied to the processor 1610 or implemented by the processor 1610. The processor 1610 can be an integrated circuit chip having a signal processing capability. In implementation, the steps of the method disclosed above can be completed by an integrated logic circuit or an instruction in a form of software in the processor 1610. The processor 1610 disclosed above can be a general processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed by the processor 1610. The general processor can be a microprocessor or the processor can also be any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware code executed by the processor or a combination of hardware and software modules in the processor. The software module can be located in a storage medium such as a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an electrically programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, or a storage device. The storage medium is located in the storage 1640, and the processor 1610 reads information in the storage 1640 and combines the hardware to complete the steps of the methods disclosed above.

[0393] In a possible implementation, the communication interface 1630 is configured to perform the receiving and transmitting of the terminal device in the embodiments shown in FIG. 9. The processor 1610 is configured to perform the processing of the network device in the embodiments shown in FIG. 9.

[0394] In a possible implementation, the communication interface 1630 is configured to perform the receiving and transmitting of the terminal device in the embodiments shown in FIG. 10. The processor 1610 is configured to perform the processing of the network device in the embodiments shown in FIG. 10.

[0395] In a possible implementation, the communication interface 1630 is configured to perform the receiving and transmitting of the terminal device in the embodiments shown in FIG. 11. The processor 1610 is configured to perform the processing of the network device in the embodiments shown in FIG. 11.

[0396] The communication module above can be a communication interface of the apparatus, configured to receive signals from other apparatuses. For example, when the apparatus is implemented in the form of a chip, the communication module is a communication interface of the chip, configured to receive signals or send signals from or to other chips or apparatuses.

[0397] In an aspect, a computer-readable storage medium is provided, which stores instructions when the instructions are executed, functions as shown in FIGS. 9-11 executed by a terminal device are implemented.

[0398] In an aspect, a computer program product is provided, which includes instructions when the instructions are executed, functions as shown in FIGS. 9-11 executed by a network device are implemented.

[0399] In an aspect, a chip is provided, which is applied to a terminal device, and the chip includes at least one processor and a communication interface, the communication interface is coupled with the at least one processor, and the processor is configured to execute instructions to implement functions as shown in FIGS. 9-11 executed by a terminal device.

[0400] In an aspect, a chip is provided, which is applied to a terminal device, and the chip includes at least one processor and a communication interface, the communication interface is coupled with the at least one processor, and the processor is configured to execute instructions to implement functions as shown in FIGS. 9-11 executed by a network device.

[0401] Embodiments of the present application provide a communication system, which includes a terminal device and a network device. Wherein the terminal device is configured to implement functions as shown in FIGS. 9-11 executed by a terminal device, and the network device is configured to implement functions as shown in FIGS. 9-11 executed by a network device.

[0402] Embodiments of the present application provide a communication system, which includes a terminal device and a network device. Wherein the terminal device is configured to implement functions as shown in FIGS. 9-11 executed by a terminal device, and the network device is configured to implement functions as shown in FIGS. 9-11 executed by a network device.

[0403] The above-mentioned any one of the communication devices provided in the related content of the explanation and the beneficial effects can be referred to the corresponding method embodiments provided in the above, and will not be repeated here.

[0404] In the embodiments of the present application, the terminal device or the network device comprises a hardware layer, an operating system layer running above the hardware layer, and an application layer running on the operating system layer. The hardware layer comprises hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as a main memory). The operating system can be any one or more computer operating systems that implement business processing through a process, for example, a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, and instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as the execution subject can communicate according to the method provided by the embodiments of the present application by running a program in which the code of the method provided by the embodiments of the present application is recorded. For example, the execution subject of the method provided by the embodiments of the present application can be a terminal device or a network device, or a functional module capable of calling and executing a program in the terminal device or the network device.

[0405] In addition, various aspects or features of the disclosure can be realized as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, or key drive, etc.). Additionally, various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine- readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and / or carrying instruction(s) and / or data.

[0406] It should be appreciated that the processor mentioned in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0407] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM) and direct memory bus random access memory (DR RAM).

[0408] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.

[0409] It should be noted that the memory described herein is intended to include, but not be limited to, the and any other suitable type of memory.

[0410] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0411] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0412] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0413] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0414] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0415] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0416] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A data transmission method, characterized in that: The method comprises: The terminal device receives first configuration information from the network device, where the first configuration information is used for the terminal device to perform initial data transmission, or for the terminal device to perform subsequent data transmission after performing the initial data transmission; The terminal device sends data to the network device according to the first configuration information in the RRC non-connected state.

2. The method according to claim 1, characterized in that The method comprises: The terminal device receives the first configuration information from the network device through a system message, where the first configuration information includes one or more uplink authorization resources, and each of the one or more uplink authorization resources corresponds to a wireless network temporary identifier, or to one or more geographical areas, or to one or more beams.

3. The method according to claim 1, characterized in that In a case where the first configuration information includes uplink authorized resources, before the terminal device receives the first configuration information from the network device, the method includes: The terminal device receives a random access resource from the network device through a system message, where the random access resource is used by the terminal device to obtain the uplink authorization resource based on random access; The terminal device sends data to the network device for the first time.

4. The method according to claim 3, characterized in that The method further comprises: The terminal device receives first indication information from the network device through a system message, and the first indication information includes a condition for indicating whether to obtain the uplink authorization resource based on random access, and / or a search space or timer for monitoring the physical downlink control channel.

5. The method according to claim 3 or 4, characterized in that Before the terminal device obtains the uplink authorization resource based on random access, the method further includes: The terminal device receives a first message from the network device, where the first message is used to instruct the terminal device to enter an RCC idle state, and the first message does not include the first configuration information.

6. The method according to any one of claims 3 to 5, characterized in that The terminal device obtains the uplink authorization resource based on random access, and the method further includes: The terminal device indicates a subsequent data transmission requirement, including: The terminal device sends a second message to the network device based on the uplink granted resource, where the second message includes a buffer status report or subsequent data transmission request information indicated by the terminal device, wherein the second message is used for initial data transmission; or The terminal device sends a buffer status report to the network device using a medium access control channel unit; or After receiving a conflict resolution response from the network device, the terminal device sends user equipment auxiliary information to the network device.

7. The method according to any one of claims 1 to 6, characterized in that In a case where the uplink authorization resource included in the first configuration information is a configuration authorization resource, the terminal device performs subsequent data transmission after performing the initial data transmission, including: In the case where the terminal device performs data transmission based on the control plane, the terminal device sends an uplink information transfer message, or an RRC advance data request message that does not carry a service temporary mobile user identity to the network device; or, When the terminal device performs user-plane-based data transmission, the terminal device sends data to the network device, or sends an RRC connection recovery request message. The RRC connection recovery request message does not carry a first identifier, and the first identifier is used by the network device to identify the terminal device context corresponding to the terminal device.

8. The method according to any one of claims 1 to 3, characterized in that In a case where the one or more uplink authorization resources included in the first configuration information are configuration authorization resources, the method includes: The terminal device receives second indication information from the network device, where the second indication information is used to indicate one or more of the following: one or more cell identifiers corresponding to the first configured authorization resource of the terminal device, or a wireless network temporary identifier corresponding to the first configured authorization resource, or a wireless network temporary identifier for data retransmission corresponding to the first configured authorization resource, or a timing advance validity condition, or a condition for the terminal device to determine whether to trigger data transmission in an RRC non-connected state, or a search space or timer for the terminal device to monitor a physical downlink control channel; The first configured authorization resource is one of the one or more uplink authorization resources.

9. The method according to claim 8, characterized in that The method further comprises: The terminal device receives an initial data transmission response from the network device, and the initial data transmission response may be: downlink data, or physical layer confirmation information addressed to the wireless network temporary identifier or downlink control information of the physical downlink control channel, or physical layer confirmation information addressed to the cell wireless network temporary identifier or downlink control information of the physical downlink control channel, or downlink control information addressed to the wireless network temporary identifier of the data retransmission.

10. The method according to claim 9, characterized in that In a case where the terminal device performs subsequent data transmission after performing the initial data transmission, the method further includes: The terminal device receives a dynamic authorization from the network device; The terminal device sends data to the network device according to the dynamic authorization.

11. A data transmission method, characterized in that: The method comprises: The network device sends first configuration information to the terminal device, where the first configuration information is used by the terminal device when performing an initial data transmission, or when the terminal device performs a subsequent data transmission after performing the initial data transmission; The network device receives data sent by the terminal device in an RRC non-connected state.

12. The method according to claim 11, characterized in that The method comprises: The network device sends the first configuration information to the terminal device, and the first configuration information includes one or more uplink authorization resources, each of the one or more uplink authorization resources corresponds to a wireless network temporary identifier, or one or more geographical areas, or one or more beams.

13. The method according to claim 11, characterized in that In a case where the first configuration information includes uplink authorization resources, before the network device sends the first configuration information to the terminal device, the method includes: The network device sends a random access resource to the terminal device, where the random access resource is used by the terminal device to obtain the uplink authorization resource based on random access; The network device receives data initially sent from the terminal device.

14. The method according to claim 13, wherein: The method further comprises: The network device sends first indication information to the terminal device, where the first indication information is used to indicate a condition for determining triggering the pre-configured uplink resource and / or to indicate a search space or timer for monitoring a physical downlink control channel.

15. The method according to claim 13 or 14, characterized in that Before the terminal device obtains the uplink authorization resource based on random access, the method further includes: The network device sends a first message to the terminal device, where the first message is used to instruct the terminal device to enter the RCC idle state, and the first message does not include the first configuration information.

16. The method according to any one of claims 13 to 15, characterized in that: The terminal device obtains the uplink authorization resource based on random access, and the method further includes: The network device receives a second message sent by the terminal device based on the uplink granted resource, where the second message includes a buffer status report or subsequent data transmission request information indicated by the terminal device, wherein the second message is used for initial data transmission; or The network device receives a buffer status report sent by the terminal device using a medium access control channel unit; or After receiving a conflict resolution response from the network device, the network device receives user equipment assistance information from the terminal device.

17. The method according to any one of claims 11 to 16, characterized in that: In a case where the uplink authorization resource included in the first configuration information is a configuration authorization resource, the terminal device performs subsequent data transmission after performing the initial data transmission, including: In the case where the terminal device performs data transmission based on the control plane, the network device receives an uplink information transmission message from the terminal device, or an RRC advance data request message that does not carry a service temporary mobile user identity; or In the case where the terminal device performs control plane-based data transmission, the network device receives data from the terminal device, or an RRC connection recovery request message, and the RRC connection recovery request message does not carry a first identifier, and the first identifier is used by the network device to identify the terminal device context corresponding to the terminal device.

18. The method according to any one of claims 11 to 13, characterized in that: In a case where the one or more uplink authorization resources included in the first configuration information are configuration authorization resources, the method includes: The network device sends second indication information to the terminal device, where the second indication information is used to indicate one or more of the following: one or more cell identifiers corresponding to the first configured authorization resource of the terminal device, or a wireless network temporary identifier corresponding to the first configured authorization resource, or a wireless network temporary identifier RNTI for data retransmission corresponding to the first configured authorization resource, or a timing advance validity condition, or a condition for the terminal device to determine whether to trigger data transmission in an RRC non-connected state, or a search space or timer for the terminal device to monitor a physical downlink control channel; The first configured authorization resource is one of the one or more uplink authorization resources.

19. The method according to claim 18, characterized in that The method further comprises: The network device sends an initial data transmission response to the terminal device, and the initial data transmission response can be: downlink data, or physical layer confirmation information addressed to the wireless network temporary identifier or downlink control information of the physical downlink control channel, or physical layer confirmation information addressed to the cell wireless network temporary identifier or downlink control information of the physical downlink control channel, or downlink control information addressed to the physical downlink control channel of the wireless network temporary identifier for data retransmission.

20. The method according to claim 19, wherein In a case where the terminal device performs subsequent data transmission after performing the initial data transmission, the method includes: The network device sends a dynamic authorization to the terminal device; The network device receives data subsequently sent by the terminal device.

21. A data transmission device, characterized in that: The device includes: a communication module and a processing module; In which, the processing module is used to execute the processing actions performed by the terminal device in the data transmission method described in any one of claims 1 to 10, and the communication module is used to execute the receiving or sending actions performed by the terminal device in the data transmission method described in any one of claims 1 to 10.

22. A data transmission device, characterized in that: The device includes: a communication module and a processing module; In which, the processing module is used to execute the processing actions performed by the terminal device in the data transmission method described in any one of claims 11 to 20, and the communication module is used to execute the receiving or sending actions performed by the terminal device in the data transmission method described in any one of claims 11 to 20.

23. A communication system, characterized in that: The system includes: a terminal device and a network device; The terminal device is used to implement the data transmission method according to any one of claims 1 to 10, and the multiple network devices include a first network device, which is used to implement the data transmission method according to any one of claims 11 to 20.

24. A communication device, characterized in that: The communication device includes a memory and a processor, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory enables the processor to perform the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 20.

25. A chip, characterized in that: The chip includes at least one processor and a communication interface, the communication interface is coupled to the at least one processor, the at least one processor is used to run a computer program or instruction to implement the method according to any one of claims 1 to 11, and the method according to any one of claims 11 to 20, and the communication interface is used to communicate with other modules outside the chip.

26. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed, the method according to any one of claims 1 to 10 or the method according to any one of claims 11 to 20 is implemented.

Images