A data transmission method and device, and a computer-readable storage medium

Abstract

The present application proposes a data transmission method, device and computer-readable storage medium, wherein the data transmission method comprises: a terminal sends a random access prefix to a base station, and receives a random access response from the base station; the terminal sends a first request message carrying uplink data to the base station. In the present application, data is transmitted during the random access process, which saves power consumption of the terminal.

Description

[0001] This application is a divisional application of patent application with application number 201710687283.5 (the filing date of the original application is August 11, 2017, and the name of the invention is A data transmission method and device, computer-readable storage medium). Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a data transmission method and device, and a computer-readable storage medium. Background Art

[0003] In machine-to-machine (M2M) communication systems, UE (User Equipment) energy saving is crucial. In the prior art, when the UE is in an idle state (RRC_IDLE) and has data to send, the UE first triggers a random access process to establish or restore an RRC (Radio Resource Control) connection with the network. The UE can send data to the base station as early as the RRC connection establishment completion or RRC recovery completion message. After that, the UE will remain in the connected state (RRC_CONNECTED) for a period of time, waiting for the base station to release the UE. When the UE is in the RRC_CONNECTED state and has data to send, the UE may need to initiate random access first due to loss of time synchronization or lack of uplink resources, and send the data to the base station after the random access process is completed.

[0004] like Figure 1 As shown, in the related art, the UE is in the RRC_IDLE state and uses the CP scheme to upload data after the random access process, including:

[0005] Step 101, the UE sends a Msg1 message to the eNB, carrying a random access prefix (Preamble);

[0006] Step 102, the eNB sends a Msg2 message to the UE, carrying a random access response (RAR).

[0007] Step 103, the UE sends a Msg3 message to the eNB, carrying an RRC connection request (RRCConnectionRequest) and an S-TMSI (SAE-Temporary Mobile Subscriber Identity, System Architecture Evolution Temporary Mobile Subscriber Identity);

[0008] Step 104, the eNB sends a Msg4 message to the UE, carrying an RRC connection establishment message (RRCConnectionSetup);

[0009] Step 105: The UE sends a Msg5 message to the eNB, carrying an RRC connection setup complete message (RRCConnectionSetupComplete and uplink data (UL data).

[0010] like Figure 2 As shown, in the related art, the UE is in the RRC_IDLE state, and uses the UP scheme to upload data after the random access process, including:

[0011] Step 201, the UE sends a Msg1 message to the eNB, carrying a random access prefix (Preamble);

[0012] Step 202, the eNB sends a Msg2 message to the UE, carrying a random access response (RAR).

[0013] Step 203, the UE sends a Msg3 message to the eNB, carrying an RRC connection resume request (RRCConnectionResumeRequest) and a resume identifier (ResumeID);

[0014] Step 204, the eNB sends a Msg4 message to the UE, carrying an RRC connection resumption message (RRCConnectionResume);

[0015] Step 205, the UE sends a Msg5 message to the eNB, carrying an RRC connection resumption complete message (RRCConnectionResumeComplete);

[0016] Step 206: The UE sends uplink data to the eNB.

[0017] In a large class of applications, such as meter reading services, a stationary or low-mobility UE may only need to send one data packet each time, and the time interval between two data packet transmissions is long. In this case, the UE only sends one data packet after entering the RRC_CONNECTED state, but it has to maintain the RRC_CONNECTED state for a period of time to continuously monitor the base station signal, which will cause unnecessary power consumption.

[0018] In the above application, after the terminal sends data once, it returns to the RRC_IDLE state, or even to the PSM (Power Save Mode) state, and may not interact with the network for a long time. During this period, the network side may have downlink data to send to the user. Therefore, it is necessary to provide a downlink data transmission solution. Summary of the invention

[0019] At least one embodiment of the present invention provides a data transmission method and device, and a computer-readable storage medium to reduce terminal power consumption.

[0020] In order to achieve the purpose of the present invention, at least one embodiment of the present invention provides a data transmission method including:

[0021] The terminal sends a random access prefix to the base station, and receives a random access response from the base station;

[0022] The terminal sends a first request message carrying uplink data to the base station.

[0023] In an optional embodiment, when the terminal is in an idle state before sending the random access prefix, the method further includes: the terminal receives a second response message returned by the base station, and after determining that the conflict is successfully resolved, the terminal maintains an idle state, and uses the temporary wireless network temporary identifier assigned by the base station carried in the random access response as the cell wireless network temporary identifier, and retains the cell wireless network temporary identifier for a first duration.

[0024] In an optional embodiment, the second response message carries at least one of the following: a conflict resolution identifier, high-level confirmation information for the uplink data, or an uplink data failure indication, or an uplink data retransmission indication, or user service data.

[0025] In an optional embodiment, the first request message also carries one of the following or a combination thereof: indication information on whether the S1 interface needs to be established first, indication information on whether high-layer confirmation information of the uplink data needs to be received, information for identifying the mobility management entity registered by the terminal, terminal identification information, access layer security information, and a connection establishment reason corresponding to data transmission.

[0026] In an optional embodiment, after the terminal receives the second response message returned by the base station and obtains the cell radio network temporary identifier, the method further includes:

[0027] The terminal uses the cell radio network temporary identifier to detect a physical downlink control channel in a common search space or a search space for transmitting the second response message scheduling information, or detects uplink or downlink scheduling information.

[0028] In an optional embodiment, the terminal sending the random access prefix to the base station includes:

[0029] When the terminal meets the first preset condition, the terminal sends a random access prefix for requesting uplink data transmission resources to the base station.

[0030] In an optional embodiment, the terminal sending a random access prefix for requesting uplink data transmission resources to the base station includes:

[0031] The terminal selects a random access prefix from a random access prefix set used to request uplink data transmission resources, and sends the selected random access prefix to the base station, or,

[0032] The terminal selects a random access resource from a random access resource set used to request uplink data transmission resources, and uses the selected random access resource to send a random access prefix to the base station.

[0033] In an optional embodiment, the terminal satisfies the first preset condition including one of the following or a combination thereof: the uplink data to be sent by the terminal is greater than the data carrying decision threshold; the wireless link condition of the terminal satisfies the link condition threshold; the service type of the uplink data to be sent by the terminal belongs to the preset service type.

[0034] In an optional embodiment, the method also includes that the terminal obtains one of the following or a combination thereof from a system message sent by the base station: a data carrying decision threshold, a link condition threshold, and preset service type information, wherein the data carrying decision threshold includes a data carrying decision threshold configured for all coverage levels or a data carrying decision threshold configured for each coverage level.

[0035] In an optional embodiment, the method also includes: the terminal does not receive a second response message returned by the base station, or the terminal receives a second response message returned by the terminal base station and the second response message carries an uplink data failure indication or an uplink data retransmission indication, or the terminal does not receive a random access response returned by the base station, the random access fails, and the terminal re-initiates random access.

[0036] In an optional embodiment, the terminal re-initiating random access includes:

[0037] The terminal determines, based on at least one of the number of random access failures, the number of random access failures sequence, the downlink measurement value obtained by the terminal, the coverage level, and the number of repetitions, whether to send a random access prefix for requesting uplink data transmission resources for random access, or to select a random access prefix not for requesting uplink data transmission resources for random access.

[0038] In an optional embodiment, the terminal re-initiates random access in one of the following ways:

[0039] Under the current coverage level, when the number of failures of the terminal in sending a random access prefix for requesting uplink data transmission resources for random access reaches the corresponding failure number threshold, the terminal changes the coverage level to the maximum coverage level, and then sends a random access prefix not for requesting uplink data transmission resources or sends a random access prefix in an existing manner for random access;

[0040] At the current coverage level, when the number of failures of the terminal in sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, the terminal sends a random access prefix not for requesting uplink data transmission resources or sends a random access prefix in an existing manner for random access. If it fails and the number of failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level greater than the current coverage level, and performs random access at the coverage level in the same random access method as at the previous coverage level until the random access succeeds, or, when the maximum coverage level is reached, random access is performed at the maximum coverage level in the same random access method as at the previous coverage level;

[0041] Under the current coverage level, when the number of failures of the terminal carrying uplink data in the first request message for random access reaches the corresponding failure number threshold, the terminal changes the coverage level to the maximum coverage level and then sends the first request message carrying the radio resource control message for random access;

[0042] At the current coverage level, when the number of failures of the terminal carrying uplink data in the first request message for random access reaches the corresponding failure number threshold, the terminal sends a first request message carrying a radio resource control message for random access. If it fails and the number of failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level greater than the current coverage level, and performs random access at the coverage level in the same random access method as the previous coverage level until the random access is successful, or reaches the maximum coverage level, and performs random access at the maximum coverage level in the same random access method as the previous coverage level;

[0043] When the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, the terminal sends a random access prefix not for requesting uplink data transmission resources for random access;

[0044] When the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, and the reference signal received power value measured by the terminal is in a first predefined range, the terminal sends a random access prefix not for requesting uplink data transmission resources for random access; when the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold and the reference signal received power value measured by the terminal is in a second predefined range, the terminal switches to the next coverage level and sends a random access prefix for requesting uplink data transmission resources for random access;

[0045] After the terminal fails to perform random access by sending a random access prefix for requesting uplink data transmission resources, the terminal sends a random access prefix that is not used to request uplink data transmission resources, and after the terminal fails to perform random access by sending a random access prefix that is not used to request uplink data transmission resources, the terminal sends a random access prefix for requesting uplink data transmission resources for random access, and repeats the previous method. When the number of access failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level, and performs random access at the coverage level according to the same random access method as the previous coverage level, until the random access is successful, or reaches the maximum coverage level, and performs random access at the maximum coverage level according to the same random access method as the previous coverage level.

[0046] In an optional embodiment, the method further includes: the terminal acquiring the failure number threshold corresponding to each coverage level by receiving a system message broadcast by the base station or a dedicated message sent by the base station to the terminal.

[0047] In an optional embodiment, before the terminal re-initiates random access, the method further includes: the terminal obtains operation instruction information from the base station, and determines a method for re-initiating random access according to the operation instruction information.

[0048] In an optional embodiment, before the terminal performs random access, it determines whether to terminate or suspend the power boost operation according to at least one of the following:

[0049] Whether the format of the first request message of this random access is the same as the format of the first request message of the previous random access;

[0050] whether the manner of sending the random access prefix in this random access is the same as the manner of sending the random access prefix in the previous random access; the manner of sending the random access prefix includes sending a random access prefix for requesting uplink data transmission resources and sending a random access prefix not for requesting uplink data transmission resources;

[0051] The reason for the previous random access failure.

[0052] In an optional embodiment, when the terminal is in a connected state before sending the random access prefix, the first request message also carries one of the following or a combination thereof: a cell wireless network temporary identifier, a wireless resource control message, and a request release indication.

[0053] In an optional embodiment, when the terminal is in a connected state before sending the random access prefix, the terminal further includes:

[0054] The terminal receives the second response message returned by the base station, determines that the conflict is successfully resolved, and autonomously releases the radio resource control connection and transfers to an idle state;

[0055] Alternatively, the terminal receives a second response message returned by the base station, and after determining that the conflict is successfully resolved, processes the radio resource control release message carried in the second response message and transfers to the idle state.

[0056] In an optional embodiment, the terminal sending a first request message carrying uplink data to the base station includes:

[0057] The terminal obtains the indication information carried in the random access response, and when a second preset condition is met, sends a first request message carrying the uplink data to the base station.

[0058] In an optional embodiment, the method further includes:

[0059] The terminal obtains the indication information carried in the random access response, and when a third preset condition is met, sends a first request message carrying a radio resource control message to the base station.

[0060] In an optional embodiment, the second preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is greater than an uplink authorization threshold; or, the indication information indicates that the terminal directly sends uplink data when sending the first request message;

[0061] The third preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is less than or equal to an uplink authorization threshold; or, the indication information indicates that the terminal carries a wireless resource control message when sending the first request message.

[0062] In an optional embodiment, the uplink authorization threshold is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix; or, is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix and the coverage level.

[0063] In an optional embodiment, the uplink authorization threshold corresponding to the connected state terminal is greater than the uplink authorization threshold corresponding to the idle state terminal.

[0064] In an optional embodiment, the method also includes: after the terminal receives the second response message returned by the base station, establishing, or restoring, or re-establishing a wireless resource control connection according to the wireless resource control response message carried in the second response message, and transferring to a connected state.

[0065] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the above-mentioned data transmission method is implemented.

[0066] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned data transmission method.

[0067] An embodiment of the present invention provides a data transmission method, including:

[0068] The base station receives a random access prefix sent by the terminal, and sends a random access response to the terminal;

[0069] The base station receives a first request message carrying uplink data sent by the terminal.

[0070] In an optional embodiment, after the base station receives the first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries one of the following information or a combination thereof: a conflict resolution identifier, high-level confirmation information for the uplink data, or an uplink data sending failure indication, or an uplink data retransmission indication, or user service data.

[0071] In an optional embodiment, the first request message also carries one of the following or a combination thereof: indication information for establishing the S1 interface first, indication information for receiving high-layer confirmation information of the uplink data, terminal identification information for identifying the mobility management entity to which the terminal is registered, access layer security information, and connection establishment reason corresponding to data transmission.

[0072] In an optional embodiment, the method also includes: when the first request message carries indication information for prioritizing establishment of the S1 interface, or carries indication information for the need to receive high-layer confirmation information of the uplink data, the base station sends a first S1 interface message carrying the uplink data to the network side, the base station receives a second S1 interface message returned by the network side, and if the base station obtains high-layer confirmation information from the second S1 interface message, the base station sends the high-layer confirmation information to the terminal.

[0073] In an optional embodiment, the method further includes: when the base station receives downlink data in the second S1 interface message, the base station sends the downlink data to the terminal.

[0074] In an optional embodiment, the first S1 interface message is one of the following messages: an initial user equipment information message, a user equipment context recovery request message, an uplink non-access layer transmission message, a path switch request message, and a newly defined S1 interface message.

[0075] The second S1 interface message is one of the following messages: a connection establishment indication message, a user equipment context recovery response message, a downlink non-access layer transmission message, a path switching request confirmation message, and a newly defined S1 interface message.

[0076] In an optional embodiment, the method further includes: the base station sending operation instruction information to the terminal through a system message or a dedicated message, wherein the operation instruction information is used to instruct the terminal on a way to re-perform random access after random access fails.

[0077] In an optional embodiment, the method of re-performing random access includes one of the following: preferentially changing the coverage level to re-perform random access; preferentially sending a random access prefix that is not used to request uplink data transmission resources or sending a random access prefix in an existing manner to re-perform random access; preferentially sending a first request message carrying a wireless resource control message to re-perform random access.

[0078] In an optional embodiment, when the terminal is in a connected state and the first request message also carries a wireless resource control message, after the base station receives the first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries a wireless resource control re-establishment message.

[0079] In an optional embodiment, when the terminal is in a connected state and the first request message also carries a request release indication, after the base station receives the first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries a wireless resource control release message.

[0080] In an optional embodiment, the method also includes, the base station sending a data carrying decision threshold to the terminal via a system message or a dedicated message, the data carrying decision threshold being used by the terminal to determine whether to select a random access prefix to be sent to the base station from a random access prefix set for requesting uplink data transmission resources or from a random access prefix set not for requesting uplink data transmission resources; or, the data carrying decision threshold being used by the terminal to determine whether to select a random access resource from a random access resource set for requesting uplink data transmission resources or from a random access resource set not for requesting uplink data transmission resources to send a random access prefix to the base station; the data carrying decision threshold includes a data carrying threshold configured for all coverage levels or a data carrying decision threshold configured for each coverage level respectively.

[0081] In an optional embodiment, the random access response carries indication information, and the indication information indicates a sending mode of the terminal to send the first request message;

[0082] The receiving, by the base station, of a first request message carrying uplink data and sent by the terminal includes:

[0083] When a second preset condition is met, the base station receives a first request message carrying uplink data sent by the terminal;

[0084] The method further includes: when a third preset condition is met, the base station receives a first request message carrying a radio resource control message sent by the terminal.

[0085] In an optional embodiment, the second preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is greater than an uplink authorization threshold; or, the indication information instructs the terminal to directly send uplink data when sending the first request message.

[0086] The third preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is less than or equal to an uplink authorization threshold; or, the indication information indicates that the terminal carries a wireless resource control message when sending the first request message.

[0087] In an optional embodiment, the uplink authorization threshold is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix; or, is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix and the coverage level.

[0088] In an optional embodiment, the uplink authorization threshold corresponding to the connected state terminal is greater than the uplink authorization threshold corresponding to the idle state terminal.

[0089] In an optional embodiment, when the terminal is in an idle state, after the base station receives a first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries a wireless resource control response message.

[0090] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the above-mentioned data transmission method is implemented.

[0091] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned data transmission method.

[0092] An embodiment of the present invention provides a data transmission method, including:

[0093] When the terminal is in an idle state, during a random access process, the terminal sends a first request message to a base station, receives a second response message sent by the base station, and obtains downlink data from the second response message.

[0094] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the program performs the following operations:

[0095] When the terminal is in an idle state, in a random access process, after sending a first request message to a base station, a second response message sent by the base station is received, and downlink data is obtained from the second response message.

[0096] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the following steps:

[0097] When the terminal is in an idle state, in a random access process, after sending a first request message to a base station, a second response message sent by the base station is received, and downlink data is obtained from the second response message.

[0098] An embodiment of the present invention provides a data transmission method, including:

[0099] When the terminal is in an idle state and performs random access, the base station receives a first request message sent by the terminal. If the base station has downlink data to be sent to the terminal, the base station sends a second response message to the terminal carrying the downlink data.

[0100] In an optional embodiment, the method further includes, before the terminal initiates random access in an idle state, when the base station receives downlink data that needs to be sent to the terminal and is sent by the network side, buffering the downlink data.

[0101] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the above-mentioned data transmission method is implemented.

[0102] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned data transmission method.

[0103] An embodiment of the present invention provides a data transmission method, including:

[0104] During the process of random access when the terminal is in an idle state, after receiving a first S1 interface message sent by a base station, the network side sends a second S1 interface message to the base station, where the second S1 interface message carries downlink data to be sent to the terminal.

[0105] In an optional embodiment, the method further includes, before the terminal initiates random access in an idle state, the network side receives downlink data sent by an application layer that needs to be sent to the terminal, and caches the downlink data.

[0106] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the above-mentioned data transmission method is implemented.

[0107] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned data transmission method.

[0108] An embodiment of the present invention provides a data transmission method, including:

[0109] When the terminal is in a connected state, the terminal receives a physical downlink control channel command sent by the base station, obtains a non-contention resource allocated by the base station to the terminal from the physical downlink control channel command, and initiates random access using a random access prefix corresponding to the non-contention resource;

[0110] The terminal receives a random access response sent by the base station, and when the random access response carries indication information of simultaneously sending downlink data, the terminal receives the downlink data.

[0111] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the program performs the following operations:

[0112] When the terminal is in a connected state, receiving a physical downlink control channel command sent by a base station, obtaining a non-contention resource allocated by the base station to the terminal from the physical downlink control channel command, and initiating random access using a random access prefix corresponding to the non-contention resource;

[0113] A random access response sent by the base station is received, and when the random access response carries indication information of simultaneously sending downlink data, downlink data is received.

[0114] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the following steps:

[0115] When the terminal is in a connected state, receiving a physical downlink control channel command sent by a base station, obtaining a non-contention resource allocated by the base station to the terminal from the physical downlink control channel command, and initiating random access using a random access prefix corresponding to the non-contention resource;

[0116] A random access response sent by the base station is received, and when the random access response carries indication information of simultaneously sending downlink data, downlink data is received.

[0117] An embodiment of the present invention provides a data transmission method, including:

[0118] When the terminal is in a connected state, the base station sends a physical downlink control channel command to the terminal, where the physical downlink control channel command carries a non-contention resource allocated by the base station to the terminal;

[0119] After receiving the random access initiated by the terminal using the random access prefix corresponding to the non-contention resource, the base station sends a random access response to the terminal, wherein the random access response carries indication information for simultaneously sending downlink data, and simultaneously sends downlink data.

[0120] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the program performs the following operations:

[0121] When the terminal is in a connected state, sending a physical downlink control channel command to the terminal, wherein the physical downlink control channel command carries a non-contention resource allocated by the base station to the terminal;

[0122] After receiving the random access initiated by the terminal using the random access prefix corresponding to the non-contention resource, a random access response is sent to the terminal, wherein the random access response carries indication information of simultaneously sending downlink data, and the downlink data is sent simultaneously.

[0123] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the following steps:

[0124] When the terminal is in a connected state, sending a physical downlink control channel command to the terminal, wherein the physical downlink control channel command carries a non-contention resource allocated by the base station to the terminal;

[0125] After receiving the random access initiated by the terminal using the random access prefix corresponding to the non-contention resource, a random access response is sent to the terminal, wherein the random access response carries indication information for simultaneously sending downlink data, and the downlink data is sent simultaneously.

[0126] Compared with the prior art, the technical solution provided by the present application realizes the transmission of uplink data and downlink data during the random access process, thereby reducing the power consumption of the terminal.

[0127] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0128] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0129] Figure 1 A flowchart for implementing random access in the related art;

[0130] Figure 2Another random access implementation flow chart in the related art;

[0131] Figure 3 A flow chart of a data transmission method provided by an embodiment of the present invention;

[0132] Figure 4 A flow chart of a data transmission method provided by an embodiment of the present invention;

[0133] Figure 5 A flow chart of a data transmission method provided in Embodiment 1 of the present invention;

[0134] Figure 6 A flow chart of a data transmission method provided in Embodiment 2 of the present invention;

[0135] Figure 7 A flow chart of a data transmission method provided in Embodiment 3 of the present invention;

[0136] Figure 8 A flow chart of a data transmission method provided in Embodiment 4 of the present invention;

[0137] Fig. 9 A flow chart of a data caching method provided in Embodiment 5 of the present invention;

[0138] Fig.10 A flow chart of a data transmission method provided in Embodiment 6 of the present invention (first sending a second response message, then sending a first S1 interface message);

[0139] Fig.11 A flow chart of a data transmission method provided in Embodiment 6 of the present invention;

[0140] Fig.12 A flow chart of a data transmission method provided in Embodiment 6 of the present invention;

[0141] Fig.13 A flow chart of a data transmission method provided in Embodiment 7 of the present invention;

[0142] Fig.14 A flow chart of a data transmission method provided in Embodiment 9 of the present invention;

[0143] Fig.15 A flow chart of a data transmission method provided in Embodiment 9 of the present invention;

[0144] Fig.16 A flow chart of a data transmission method provided in Embodiment 10 of the present invention;

[0145] Fig.17 A flow chart of a data transmission method provided in Embodiment 11 of the present invention;

[0146] Fig.18 A schematic diagram of resource allocation provided in Embodiment 12 of the present invention;

[0147] Fig.19 Another resource division schematic diagram provided in Embodiment 12 of the present invention;

[0148] Fig. 20 Another resource division schematic diagram provided in Embodiment 12 of the present invention;

[0149] Fig.21 Another resource partitioning diagram provided for the twelfth embodiment of the present invention. DETAILED DESCRIPTION

[0150] The following will describe the embodiments of the present application in conjunction with the accompanying drawings. The following will describe the present application in conjunction with the accompanying drawings of the embodiments, and the examples cited are only used to explain the present application and are not used to limit the scope of the present application.

[0151] In order to make the purpose, technical solution and advantages of the present invention more clear, the embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily without conflict.

[0152] The steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions. Also, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described can be performed in a sequence different from that shown here.

[0153] An embodiment of the present invention provides a data transmission method, such as Figure 3 As shown, including:

[0154] Step 301: The terminal sends a random access prefix to a base station, and receives a random access response sent by the base station;

[0155] Step 302: The terminal sends a first request message (Msg3) carrying uplink data to the base station.

[0156] When the terminal is in an idle state before sending the random access prefix, the method further includes: step 303, the terminal receives a second response message (Mg4) returned by the base station, and after determining that the conflict is successfully resolved, the terminal maintains the idle state, and uses the temporary wireless network temporary identifier assigned by the base station as the cell wireless network temporary identifier, and retains the cell wireless network temporary identifier for a first duration. Wherein, judging whether the conflict is successfully resolved is based on the conflict resolution identifier carried in the second response message.

[0157] In an optional embodiment, the second response message carries at least one of the following: a conflict resolution identifier, high-level confirmation information (confirmation or non-confirmation) for the uplink data, or an uplink data failure indication, or an uplink data retransmission indication.

[0158] The first request message also carries one of the following or a combination thereof: indication information on whether the S1 interface needs to be established first, indication information on whether high-level confirmation information of the uplink data needs to be received, terminal identification information for identifying the mobility management entity to which the terminal is registered, access layer security information, and connection establishment reasons corresponding to data transmission.

[0159] After the terminal receives the second response message returned by the base station and obtains the cell radio network temporary identifier, the method further includes:

[0160] In an optional embodiment, the terminal uses the cell radio network temporary identifier to detect a physical downlink control channel, or detects uplink or downlink scheduling information, in a common search space or a search space for transmitting second response message scheduling information.

[0161] In an optional embodiment, after the terminal receives the second response message returned by the base station, the method further includes:

[0162] If the terminal still has uplink data to be transmitted, the terminal again sends the first request message carrying the uplink data to the base station.

[0163] Before sending the random access prefix to the base station, the terminal further selects a random access prefix or selects a resource for sending the random access prefix.

[0164] In an optional embodiment, the terminal sending the random access prefix to the base station includes:

[0165] When the terminal meets the first preset condition, the terminal sends a random access prefix for requesting uplink data transmission resources to the base station.

[0166] The terminal sending a random access prefix for requesting uplink data transmission resources to the base station includes:

[0167] The terminal selects a random access prefix from a random access prefix set used to request uplink data transmission resources, and sends the selected random access prefix to the base station, or,

[0168] The terminal selects a random access resource from a random access resource set used to request uplink data transmission resources, and uses the selected random access resource to send a random access prefix to the base station.

[0169] In an optional embodiment, the terminal satisfies the first preset condition including one of the following or a combination thereof: the uplink data to be sent by the terminal is greater than the data carrying decision threshold; the wireless link condition of the terminal satisfies the link condition threshold; the service type of the uplink data to be sent by the terminal belongs to the preset service type.

[0170] In an optional embodiment, the method also includes that the terminal obtains one of the following or a combination thereof from a system message sent by the base station: a data carrying decision threshold, a link condition threshold, and preset service type information, wherein the data carrying decision threshold includes a data carrying decision threshold configured for all coverage levels or a data carrying decision threshold configured for each coverage level.

[0171] In an optional embodiment, the method also includes: the terminal does not receive a second response message returned by the base station, or the terminal receives a second response message returned by the terminal base station and the second response message carries an uplink data failure indication or an uplink data retransmission indication, or the terminal does not receive a random access response returned by the base station, the random access fails, and the terminal re-initiates random access.

[0172] In an optional embodiment, the terminal re-initiating random access includes:

[0173] The terminal determines whether to send a random access prefix for requesting uplink data transmission resources for random access or to select a random access prefix not for requesting uplink data transmission resources for random access based on at least one of the number of random access failures, the number of random access failures sequence, the downlink measurement value obtained by the terminal, the coverage level, and the number of repetitions. The number of repetitions is configuration information obtained by the terminal. The downlink measurement value is, for example, a reference signal received power value, and of course, it can also be other values.

[0174] In an optional embodiment, the terminal re-initiates random access in one of the following ways:

[0175] Under the current coverage level, when the number of failures of the terminal in sending a random access prefix for requesting uplink data transmission resources for random access reaches the corresponding failure number threshold, the terminal changes the coverage level to the maximum coverage level, and then sends a random access prefix not for requesting uplink data transmission resources or sends a random access prefix in an existing manner for random access;

[0176] At the current coverage level, when the number of failures of the terminal in sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, the terminal sends a random access prefix not for requesting uplink data transmission resources or sends a random access prefix in an existing manner for random access. If it fails and the number of failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level greater than the current coverage level, and performs random access at the coverage level in the same random access method as at the previous coverage level until the random access succeeds, or, when the maximum coverage level is reached, random access is performed at the maximum coverage level in the same random access method as at the previous coverage level;

[0177] Under the current coverage level, when the number of failures of the terminal carrying uplink data in the first request message for random access reaches the corresponding failure number threshold, the terminal changes the coverage level to the maximum coverage level and then sends the first request message carrying the radio resource control message for random access;

[0178] At the current coverage level, when the number of failures of the terminal carrying uplink data in the first request message for random access reaches the corresponding failure number threshold, the terminal sends a first request message carrying a radio resource control message for random access. If it fails and the number of failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level greater than the current coverage level, and performs random access at the coverage level in the same random access method as the previous coverage level until the random access is successful, or reaches the maximum coverage level, and performs random access at the maximum coverage level in the same random access method as the previous coverage level;

[0179] When the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, the terminal sends a random access prefix not for requesting uplink data transmission resources for random access;

[0180] When the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, and the reference signal received power value measured by the terminal is in a first predefined range, the terminal sends a random access prefix not for requesting uplink data transmission resources for random access; when the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold and the reference signal received power value measured by the terminal is in a second predefined range, the terminal switches to the next coverage level and sends a random access prefix for requesting uplink data transmission resources for random access;

[0181] After the terminal fails to perform random access by sending a random access prefix for requesting uplink data transmission resources, the terminal sends a random access prefix that is not used to request uplink data transmission resources, and after the terminal fails to perform random access by sending a random access prefix that is not used to request uplink data transmission resources, the terminal sends a random access prefix for requesting uplink data transmission resources for random access, and repeats the previous method. When the number of access failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level, and performs random access at the coverage level according to the same random access method as the previous coverage level, until the random access is successful, or reaches the maximum coverage level, and performs random access at the maximum coverage level according to the same random access method as the previous coverage level.

[0182] In an optional embodiment, the method further includes: the terminal acquiring the failure number threshold corresponding to each coverage level by receiving a system message broadcast by the base station or a dedicated message sent by the base station to the terminal.

[0183] In an optional embodiment, before the terminal re-initiates random access, the method further includes: the terminal obtains operation instruction information from the base station, and determines a method for re-initiating random access according to the operation instruction information.

[0184] In an optional embodiment, before the terminal performs one of the following operations, it also includes: the terminal obtains operation indication information from the base station, and determines the operation after sending the first request message carrying uplink data for random access fails according to the operation indication information.

[0185] In an optional embodiment, before the terminal performs random access, it determines whether to terminate the suspension of the power boost operation according to at least one of the following:

[0186] Whether the format of the first request message of this random access is the same as the format of the first request message of the previous random access;

[0187] whether the manner of sending the random access prefix in this random access is the same as the manner of sending the random access prefix in the previous random access; the manner of sending the random access prefix includes sending a random access prefix for requesting uplink data transmission resources and sending a random access prefix not for requesting uplink data transmission resources;

[0188] The reason for the previous random access failure.

[0189] In an optional embodiment, when the terminal is in a connected state before sending the random access prefix, the first request message also carries one of the following or a combination thereof: a cell wireless network temporary identifier, a wireless resource control message, and a request release indication.

[0190] In an optional embodiment, when the terminal is in a connected state before sending the random access prefix, the terminal further includes:

[0191] After the terminal receives the second response message returned by the base station and determines that the conflict is successfully resolved, the terminal autonomously releases the radio resource control connection and transfers to an idle state;

[0192] Alternatively, the terminal receives the second response message returned by the base station, determines that the conflict is successfully resolved, processes the radio resource control release message carried in the second response message, and transfers to the idle state.

[0193] In an optional embodiment, the terminal sending a first request message carrying uplink data to the base station includes:

[0194] The terminal obtains the indication information carried in the random access response, and when a second preset condition is met, sends a first request message carrying the uplink data to the base station.

[0195] In an optional embodiment, the method further includes:

[0196] The terminal obtains the indication information carried in the random access response, and when a third preset condition is met, sends a first request message carrying a radio resource control message to the base station.

[0197] In an optional embodiment, the second preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is greater than an uplink authorization threshold; or, the indication information indicates that the terminal directly sends uplink data when sending the first request message;

[0198] The third preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is less than or equal to an uplink authorization threshold; or, the indication information indicates that the terminal carries a wireless resource control message when sending the first request message.

[0199] In an optional embodiment, the uplink authorization threshold is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix; or, is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix and the coverage level.

[0200] In an optional embodiment, the uplink authorization threshold corresponding to the connected state terminal is greater than the uplink authorization threshold corresponding to the idle state terminal.

[0201] In an optional embodiment, the method also includes: after the terminal receives the second response message returned by the base station, establishing, or restoring, or re-establishing a wireless resource control connection according to the wireless resource control response message carried in the second response message, and transferring to a connected state.

[0202] An embodiment of the present invention provides a data transmission method, such as Figure 4 As shown, including:

[0203] Step 401: The base station receives a random access prefix sent by a terminal and sends a random access response to the terminal;

[0204] Step 402: The base station receives a first request message carrying uplink data sent by the terminal.

[0205] In an optional embodiment, after the base station receives the first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries one of the following information or a combination thereof: a conflict resolution identifier, high-level confirmation information for the uplink data, or an uplink data sending failure indication, or an uplink data retransmission indication, or user service data.

[0206] In an optional embodiment, the first request message also carries one of the following or a combination thereof: indication information for establishing the S1 interface first, indication information for receiving high-layer confirmation information of the uplink data, the terminal identification information for identifying the mobility management entity to which the terminal is registered, access layer security information, and a connection establishment reason corresponding to data transmission.

[0207] In an optional embodiment, the method further includes:

[0208] Step 403: When the first request message carries indication information of establishing the S1 interface first, the base station sends a first S1 interface message carrying the uplink data to the network side;

[0209] Step 404: The base station receives the second S1 interface message returned by the network side, obtains high-layer confirmation information from the second S1 interface message, and sends the high-layer confirmation information to the terminal.

[0210] In an optional embodiment, the method further includes: when the base station receives downlink data in the second S1 interface message, the base station sends the downlink data to the terminal.

[0211] In an optional embodiment, the method further includes: the base station sending operation instruction information to the terminal through a system message or a dedicated message, wherein the operation instruction information is used to instruct the terminal on a way to re-perform random access after random access fails.

[0212] The method of re-performing random access includes one of the following: preferentially changing the coverage level for re-performing random access; preferentially sending a random access prefix that is not used to request uplink data transmission resources or sending a random access prefix in an existing manner for re-performing random access, and preferentially sending a first request message carrying a wireless resource control message for re-performing random access.

[0213] In an optional embodiment, when the terminal is in a connected state and the first request message also carries a wireless resource control message, after the base station receives the first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries a wireless resource control re-establishment message.

[0214] In an optional embodiment, when the terminal is in a connected state and the first request message also carries a request release indication, after the base station receives the first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries a wireless resource control release message.

[0215] In an optional embodiment, the method also includes, the method also includes, the base station sends a data carrying decision threshold to the terminal through a system message or a dedicated message, the data carrying decision threshold is used by the terminal to determine whether to select a random access prefix to be sent to the base station from a random access prefix set for requesting uplink data transmission resources or from a random access prefix set not for requesting uplink data transmission resources; or, the data carrying decision threshold is used by the terminal to determine whether to select a random access resource from a random access resource set for requesting uplink data transmission resources or from a random access resource set not for requesting uplink data transmission resources to send a random access prefix to the base station; the data carrying decision threshold includes a data carrying threshold configured for all coverage levels or a data carrying decision threshold configured for each coverage level.

[0216] In an optional embodiment, the random access response carries indication information, and the indication information indicates a sending mode of the terminal to send the first request message;

[0217] The receiving, by the base station, of a first request message carrying uplink data and sent by the terminal includes:

[0218] When a second preset condition is met, the base station receives a first request message carrying uplink data sent by the terminal;

[0219] The method further includes: when a third preset condition is met, the base station receives a first request message carrying a radio resource control message sent by the terminal.

[0220] In an optional embodiment, the second preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is greater than an uplink authorization threshold; or, the indication information instructs the terminal to directly send uplink data when sending the first request message.

[0221] The third preset condition is satisfied as follows: the indication information is uplink authorized data volume information, and the uplink authorized data volume information is less than or equal to an uplink authorization threshold; or, the indication information indicates that the terminal carries a wireless resource control message when sending the first request message.

[0222] In an optional embodiment, the uplink authorization threshold is the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix; or, the uplink authorization threshold corresponding to the state of the terminal before sending the random access prefix and the coverage level. That is, the same uplink authorization threshold can be configured for each coverage level, and the uplink authorization threshold can also be configured for each coverage level.

[0223] In an optional embodiment, the uplink authorization threshold corresponding to the connected state terminal is greater than the uplink authorization threshold corresponding to the idle state terminal.

[0224] In an optional embodiment, when the terminal is in an idle state, after the base station receives a first request message carrying uplink data sent by the terminal, the base station also sends a second response message to the terminal, and the second response message carries a wireless resource control response message.

[0225] An embodiment of the present invention provides a data transmission method, including:

[0226] When the terminal is in an idle state, during a random access process, the terminal sends a first request message to a base station, receives a second response message sent by the base station, and obtains downlink data from the second response message.

[0227] An embodiment of the present invention provides a data transmission method, including:

[0228] When the terminal is in an idle state and performs random access, the base station receives a first request message sent by the terminal. If the base station has downlink data to be sent to the terminal, the base station sends a second response message to the terminal carrying the downlink data.

[0229] In an optional embodiment, before the terminal initiates random access in an idle state, when the base station receives downlink data that needs to be sent to the terminal and is sent by the network side, the base station caches the downlink data.

[0230] An embodiment of the present invention provides a data transmission method, including:

[0231] During the process of random access when the terminal is in an idle state, after receiving a first S1 interface message sent by a base station, the network side sends a second S1 interface message to the base station, where the second S1 interface message carries downlink data to be sent to the terminal.

[0232] In an optional embodiment, the method further includes, before the terminal initiates random access in an idle state, the network side receives downlink data sent by an application layer that needs to be sent to the terminal, and caches the downlink data.

[0233] An embodiment of the present invention provides a data transmission method, including:

[0234] When the terminal is in a connected state, the terminal receives a physical downlink control channel command sent by the base station, obtains a non-contention resource allocated by the base station to the terminal from the physical downlink control channel command, and initiates random access using a random access prefix corresponding to the non-contention resource;

[0235] The terminal receives a random access response sent by the base station, and when the random access response carries indication information of simultaneously sending downlink data, the terminal receives the downlink data.

[0236] An embodiment of the present invention provides a data transmission method, including:

[0237] When the terminal is in a connected state, the base station sends a physical downlink control channel command to the terminal, where the physical downlink control channel command carries a non-contention resource allocated by the base station to the terminal;

[0238] After receiving the random access initiated by the terminal using the random access prefix corresponding to the non-contention resource, the base station sends a random access response to the terminal, wherein the random access response carries indication information for simultaneously sending downlink data, and simultaneously sends downlink data.

[0239] The present application is further described below through specific examples.

[0240] Embodiment 1 (Basic flow of sending uplink data in idle state, CP solution)

[0241] This embodiment provides an idle uplink data transmission scheme with stateless transfer. When the UE is in the RRC_IDLE state, the UE sends a random access prefix to request resources for sending uplink data. After the UE receives the random access response sent by the base station and obtains the uplink authorization, it sends the uplink data to the base station at the same time as sending the first request message. When the UE receives the second response message sent by the base station and determines that the conflict is successfully resolved, the UE considers that the uplink data is successfully sent, and the UE will remain in the RRC_IDLE state. At the same time, the UE can regard the temporary MAC layer identifier T-RNTI (Tempory-Radio Network Tempory Identity) assigned by the base station as the formal MAC (Media Access Control) layer identifier C-RNTI. The UE retains the C-RNTI for a first duration in the RRC_IDLE state. The first duration can be preset or configured for the UE by the network side.

[0242] In this embodiment, the UE is in the RRC_IDLE state and uses the CP (Control Plane) solution, such as Figure 5 As shown, including:

[0243] Step 501, when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in a random access process to request resources for sending uplink data, that is, to request uplink data transmission resources;

[0244] Step 502: The base station sends a random access response to the UE;

[0245] The random access response carries a temporary MAC layer identifier T-RNTI allocated by the base station to the UE;

[0246] Step 503, after receiving the random access response and obtaining the uplink authorization, the UE sends the uplink data to the base station while sending the first request message (Msg3);

[0247] Msg3 may only carry an identifier including a core network identifier (e.g., a data target address identifier) ​​and uplink data, but not an RRC message. The difference from the related art is that Msg3 in the related art needs to carry an RRC message, such as an RRC connection establishment request message, an RRC connection recovery request message, or a new RRC connection common request message, which is used to trigger the establishment or recovery of an RRC connection. In this embodiment, no RRC message is carried.

[0248] If the UE did not store the UE context when the last RRC connection was released (i.e., using the CP solution), the UE should carry the identifier assigned to the UE by the core network, such as S-TMSI, or information that can identify the MME to which the UE is attached to the base station, such as the data target address identifier, or GUMMEI information (Globally Unique MME Identifier) ​​when sending an uplink data packet through Msg3. The UE can also carry access layer security information to the base station, such as ul-NAS-MAC, ul-NAS-Count, while sending an uplink data packet. The access layer security information can be obtained based on NAS (Non Access Stratum) layer security information. Msg3 can also carry a connection establishment reason, such as a connection establishment reason indicating the transmission of uplink data.

[0249] The UE may include in the first request message indication information of whether it is necessary to establish the S1 interface first (for example, if the UE believes that the uplink data requires high-level confirmation, in this case, it may be further considered that the uplink data sent by the UE does not require RLC (Radio Link Control) and HARQ (Hybrid Automatic Repeat Request) layer confirmation, and only needs to wait for high-level confirmation). If it is necessary to establish the S1 interface first, IND_needforS1=YES information may be carried, and this indication may also be used as indication information of whether the UE needs to receive high-level confirmation information of the uplink data.

[0250] Step 504, the base station sends a first SI interface message carrying uplink data to the network side;

[0251] For example, the first S1 interface message is a data transmission request (Data Transmission Req);

[0252] In other embodiments, the first S1 interface message may also be an initial user equipment information (INITIAL UE EMESSAGE) message; or a user equipment context recovery request (UE CONTEXT RESUME REQUEST) message; or an uplink non-access layer transmission (UPLINK NAS TRANSPORT) message; or a path switch request (PATH SWITCH REQUEST) message; or, the first S1 interface message may also be other newly defined S1 interface messages. The network side is, for example, an MME (Mobility Management Entity) to which the UE is attached.

[0253] If the UE carries access layer security information to the base station at the same time, the base station may also send the access layer security information to the MME at the same time.

[0254] Step 505, the network side sends a second S1 interface message to the base station;

[0255] For example, the second S1 interface message is Data Transmission Ack;

[0256] Alternatively, the second S1 interface message may also be a connection establishment indication (Connection Establishment Indication) message; or a user equipment context recovery response (UE CONTEXT RESUME RESPONSE) message; or a downlink non-access layer transmission (DOWNLINK NAS TRANSPORT) message; or a path switch request confirmation (PATH SWITCH REQUEST ACKNOWLEDGE) message; or, the second S1 interface message may also be other newly defined S1 interface messages.

[0257] The second S1 interface message carries high-layer confirmation information (confirmation / non-confirmation) of the uplink data, and may also include downlink access layer security information.

[0258] Step 506: The base station sends a second response message (Msg4) to the terminal.

[0259] The second response message carries a contention resolution ID, for example, carried by a MAC layer control unit;

[0260] Among them, the second response message (Msg4) may carry only the conflict resolution identifier but not the RRC message;

[0261] The second response message carries high-level confirmation information (Ack / Nack for UL data) or uplink data retransmission indication (DataResendIND). Step 507: After the UE receives the second response message sent by the base station and determines that the conflict resolution is successful according to the conflict resolution ID, it considers that the uplink data transmission is successful and maintains the RRC_IDLE state.

[0262] In the related art, the base station first sends a second response message to the terminal, and then sends a first S1 interface message to the MME, and the first S1 interface message usually triggers the base station and the MME to establish an S1 interface and a UE context for the UE. Compared with the related art, in this embodiment, the first S1 interface message can be sent before the second response message according to the UE instruction, and does not trigger the establishment of the S1 interface and the UE context for the UE.

[0263] In the related art, Msg4 needs to carry an RRC message, such as an RRC connection establishment message, an RRC connection recovery message, or a new RRC connection public response message, to complete the RRC establishment or RRC recovery process. In this application, Msg4 may not need to carry an RRC message.

[0264] In an optional embodiment, if the UE carries an indication that the S1 interface needs to be established preferentially while sending an uplink data packet, the UE and the base station need to use an extended conflict resolution timer. The extended conflict resolution timer can be statically configured, or the base station broadcasts multiple conflict resolution timer lengths in a system message, and the UE and the base station select one to use according to the corresponding indication.

[0265] In an optional embodiment, the UE may regard the temporary MAC layer identifier T-RNTI allocated by the base station in step 502 as the formal MAC layer identifier C-RNTI. When the UE is maintained in the RRC_IDLE state, the C-RNTI is also retained for a period of time. The specific retention time may be preset or configured for the UE by the network side. During this period, the UE always uses the C-RNTI to demodulate the physical channel in the CSS search space of the RAR or in a newly defined CSS search space dedicated to Msg3 data transmission.

[0266] In an optional embodiment, if the UE receives the second response message from the base station but determines that the conflict resolution fails, or does not receive the second response message, the UE considers that the uplink data transmission has failed, and the UE re-initiates a random access process to transmit data.

[0267] In an optional embodiment, if the second S1 interface message does not include confirmation of uplink data, or indicates uplink data transmission failure, the base station may include an uplink data transmission failure indication, or an uplink data retransmission indication, in a second response message sent to the UE.

[0268] In an optional embodiment, if the UE receives a second response message from the base station, it determines that the conflict resolution is successful based on the conflict resolution ID, and the temporary MAC layer identifier T-RNTI allocated by the UE base station is regarded as the official MAC layer identifier C-RNTI, but the second response message contains an uplink data sending failure indication, or an uplink data retransmission indication, then the UE needs to re-initiate a random access process to transmit data, and Msg3 carries the C-RNTI.

[0269] Embodiment 2 (Basic flow of sending uplink data in idle state, UP solution)

[0270] In this embodiment, the UE is in the RRC_IDLE state. Compared with Embodiment 1, this embodiment adopts the UP (User Plane) solution, such as Figure 6 As shown, including:

[0271] Step 601, when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in a random access process to request resources for sending uplink data;

[0272] Step 602: The UE receives a random access response sent by the base station and obtains an uplink authorization;

[0273] Step 603, the UE sends uplink data to the base station while sending the first request message (Msg3);

[0274] This embodiment adopts the UP solution. The UE performs a suspension operation when the last RRC connection is released. There is a stored UE context and a resume identifier (ResumeID). The UE carries the resume identifier while sending uplink data through Msg3.

[0275] Msg3 may only carry an identifier including a core network identifier (e.g., a data target address identifier, or GUMMEI information) and uplink data, and does not carry an RRC message. Compared with the related art, in which Msg3 needs to carry an RRC message, such as an RRC connection establishment request message, an RRC connection recovery request message, or a new RRC connection common request message, which is used to trigger the establishment or recovery of an RRC connection, in this embodiment, no RRC message is carried.

[0276] When sending an uplink data packet, the UE may also carry access layer security information to the base station. The access layer security information may be obtained according to the NAS layer security information.

[0277] The UE may also carry a connection establishment reason, for example, a connection establishment reason indicating transmission of uplink data.

[0278] The UE may include in the first request message the indication information of whether it is necessary to establish the S1 interface first (for example, if the UE believes that the uplink data requires high-level confirmation, in this case, it may be further considered that the uplink data sent by the UE does not require RLC and HARQ layer confirmation, and only needs to wait for high-level confirmation). If it is necessary to establish the S1 interface first, IND_needforS1=YES information is carried. This indication may also be used as the indication information of whether the UE needs to receive high-level confirmation information of the uplink data.

[0279] Step 604, the base station sends a first SI interface message carrying uplink data to the network side;

[0280] For example, the first S1 interface message is a data transmission request (Data Transmission Req);

[0281] The network side is, for example, an MME (Mobility Management Entity) to which the UE is attached.

[0282] If the UE carries access layer security information to the base station at the same time, the base station may also send the access layer security information to the MME at the same time.

[0283] The base station searches for the UE context stored on the base station side according to the recovery identifier, and sends the first S1 interface message to the MME according to the MME information to which the UE is attached contained in the UE context.

[0284] Step 605, the network side sends a second S1 interface message to the base station;

[0285] For example, the second S1 interface message is a data transmission confirmation (Data Transmission Ack), which carries high-layer confirmation information (confirmation / non-confirmation) of the uplink data, and may also include downlink access layer security information.

[0286] Step 606: The base station sends a second response message (Msg4) to the terminal.

[0287] The second response message carries a conflict resolution identifier, for example, carried by a MAC layer control unit;

[0288] Among them, the second response message (Msg4) may carry only the conflict resolution identifier but not the RRC message;

[0289] Step 607: After the UE receives the second response message sent by the base station and determines that the conflict is successfully resolved according to the conflict resolution ID, the UE considers that the uplink data is successfully sent and maintains the RRC_IDLE state.

[0290] Embodiment 3 (continuous transmission of idle data)

[0291] The UE may not be able to transmit all the data to be transmitted during the initial random access process. In this case, the UE can continue to send a first request message carrying uplink data to the base station in the RRC_IDLE state and with C-RNTI, and the base station sends a second response message to the UE, carrying confirmation of the uplink data. This process can be repeated several times until the transmission of the data to be transmitted is completed.

[0292] like Figure 7 As shown, including:

[0293] Steps 701 to 707 are the same as steps 501 to 507; wherein step 703 may also carry a buffer status report, indicating that there is still data to be sent;

[0294] Step 708: The base station allocates a new uplink grant to the terminal via PDCCH (Physical Downlink Control Channel), and the PDCCH transmission is scrambled with the cell radio network temporary identifier;

[0295] Step 709, the terminal uses the cell radio network temporary identifier to demodulate the PDCCH transmission, obtains an uplink grant, and uses the uplink grant to send uplink data to the base station;

[0296] Step 710, the base station sends a first SI interface message carrying uplink data to the network side;

[0297] Step 711, the network side sends a second S1 interface message to the base station;

[0298] Step 712: If the second S1 interface message includes confirmation of the uplink data, the base station sends the confirmation of the uplink data to the terminal.

[0299] Steps 708 to 712 may be repeatedly executed several times until all data to be transmitted by the terminal are transmitted.

[0300] Embodiment 4 (Downlink buffer data is sent in Msg4, CP / UP solution is integrated)

[0301] If the network side has downlink data to send to M2M (NB-IoT or eMTC) users, and if these data are delay tolerant, the network side can cache these downlink data for a period of time before sending them to the UE. During this period of time, if the network side receives the first S1 interface message, the cached downlink data can be sent to the base station in the second S1 interface message. If the base station has not sent the second response message to the UE after receiving the second S1 interface message, the base station can include the downlink data in the second response message and send it to the UE. The downlink data can be included in the newly defined MAC CE or the newly defined data container IE (Information Element).

[0302] like Figure 8 As shown in FIG. 1 , the random access process is a downlink data transmission process, including:

[0303] Step 801, when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in a random access process to request resources for sending uplink data;

[0304] Step 802: The UE receives a random access response sent by the base station and obtains an uplink authorization;

[0305] Step 803, the UE sends uplink data to the base station simultaneously with sending the first request message (Msg3);

[0306] If the UE did not store the UE context when the last RRC connection was released (i.e., using the CP solution), the UE should carry the identifier assigned to the UE by the core network, such as S-TMSI, or information that can identify the MME to which the UE is attached to the base station, such as the data target address identifier, or GUMMEI information (Globally Unique MME Identifier) ​​when sending an uplink data packet via Msg3. The UE can also carry access layer security information to the base station when sending an uplink data packet. The access layer security information can be obtained based on the NAS layer security information. Alternatively, the UE performed a suspend operation when the last RRC connection was released, and there is a stored UE context and recovery identifier. The UE carries the recovery identifier when sending uplink data via Msg3.

[0307] Step 804, the base station checks whether there is downlink data to be sent to the terminal, and if so, includes it in the second response message;

[0308] Step 805, the base station sends a first SI interface message carrying uplink data to the network side;

[0309] For example, the first S1 interface message is a data transmission request (Data Transmission Req);

[0310] The network side is, for example, an MME (Mobility Management Entity) to which the UE is attached.

[0311] If the UE carries access layer security information to the base station at the same time, the base station may also send the access layer security information to the MME at the same time.

[0312] Step 806, the network side checks whether there is downlink data to be sent to the terminal, and if so, includes it in the second S1 interface message;

[0313] Step 807, the network side sends a second S1 interface message carrying downlink data to the base station;

[0314] For example, the second S1 interface message is Data Transmission Ack.

[0315] For example, the second S1 interface message may also carry high-layer confirmation information (confirmation / non-confirmation) of the uplink data, and may also include downlink access layer security information.

[0316] Step 808: The base station sends a second response message (Msg4) carrying downlink data to the terminal.

[0317] For other information carried in the second response message, please refer to step 506.

[0318] Embodiment 5 (Downlink Data Cache)

[0319] If the network has downlink data to send to an M2M (NB-IoT or eMTC) user and the user is in the S1 interface idle state, and if the delay of this data is tolerable, the network can cache this downlink data for a period of time without triggering the sending of the S1 interface paging message. Alternatively, if the network has downlink data to send to an M2M (NB-IoT or eMTC) user and the user is in the S1 interface connected state, the network will send the data to the base station. However, the terminal may be in the air interface idle state at this time, so the base station can cache this downlink data for a period of time without triggering the sending of the air interface paging message.

[0320] like Fig. 9 As shown, it is a downlink data buffering flow chart, including:

[0321] Step 901, the application layer sends downlink data to the network side;

[0322] Step 902: The network determines that the user is in the S1 interface idle state and the downlink data has a tolerable delay, so the network can cache the downlink data for a period of time and does not trigger the S1 interface paging message to be sent. The cache period can be a preset value.

[0323] Step 903: The network side determines that the user is in the S1 interface connection state, and then sends the downlink data to the base station;

[0324] Step 904: the base station determines that the terminal is in an air interface idle state and the downlink data has a tolerable delay, then the base station can cache the downlink data for a period of time and does not trigger the sending of an air interface paging message. The cache period can be a preset value.

[0325] Fig.10 This is another implementation of the first or second embodiment.

[0326] Step 1001, when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in a random access process to request resources for sending uplink data;

[0327] Step 1002: The UE receives a random access response sent by the base station and obtains an uplink authorization;

[0328] Step 1003, the UE sends uplink data to the base station simultaneously when sending the first request message (Msg3);

[0329] Msg3 may carry a terminal identifier, such as an S-TMSI or a recovery identifier, or an identifier of the core network including terminal registration (eg, GUMMEI information or a data target address identifier) ​​and uplink data, but does not carry an RRC message.

[0330] When sending an uplink data packet, the UE may also carry access layer security information to the base station, and the access layer security information may be obtained based on the NAS layer security information. The UE may also carry a connection establishment reason.

[0331] Step 1004: The base station sends a second response message (Msg4) to the terminal.

[0332] The second response message carries a conflict resolution identifier, for example, carried by a MAC layer control unit;

[0333] The second response message may carry only a conflict resolution identifier but not an RRC message;

[0334] Step 1005, after the UE receives the second response message sent by the base station and determines that the conflict is successfully resolved according to the conflict resolution ID, the UE maintains the RRC_IDLE state, and uses the temporary wireless network temporary identifier assigned by the base station as the cell wireless network temporary identifier, and retains the cell wireless network temporary identifier for the first duration.

[0335] Step 1006, the base station sends a first SI interface message carrying uplink data to the network side;

[0336] For example, the first S1 interface message is a data transmission request (Data Transmission Req);

[0337] Step 1007, the network side sends a second S1 interface message to the base station;

[0338] For example, the second S1 interface message is a data transmission confirmation (Data Transmission Ack), which carries high-layer confirmation information (confirmation / non-confirmation) of the uplink data.

[0339] Step 1008, the base station sends downlink assignment information to the terminal via PDCCH transmission, and the PDCCH transmission is scrambled with the cell radio network temporary identifier;

[0340] Step 1009, the terminal uses the cell radio network temporary identifier to demodulate the PDCCH transmission, obtains downlink assignment information, and uses the downlink assignment information to receive downlink data sent by the base station to the terminal. The downlink data may be high-layer confirmation information of uplink data.

[0341] Embodiment 6 (the terminal determines the sending mode of Msg3 (with data or with RRC message) according to the information in RAR, and the CP / UP solution is integrated)

[0342] When the UE is in the RRC_IDLE state, the UE sends a random access prefix during the random access process to request resources for sending uplink data. The base station controls whether to establish or restore an RRC connection for the UE and whether to transfer the UE to the RRC_CONNECTED state.

[0343] The base station carries an indication in the random access response, which is used to indicate the sending method of the first request message.

[0344] The indication may be an implicit indication, such as the data volume information contained in the uplink authorization (e.g., the TB size (transport block size) in the UL grant (uplink authorization) field in the RAR message). When the indication (such as the data volume information of the uplink authorization) exceeds a certain threshold (hereinafter referred to as the uplink authorization threshold), the UE directly sends the uplink data to the base station when sending the first request message. When sending the first request message, the UE shall encapsulate the uplink data according to the data volume information of the uplink authorization and send it to the base station. If the data to be sent by the UE exceeds the data volume information of the uplink authorization, the UE may split the data to be sent into multiple fragments according to the data volume information of the uplink authorization and send them in sequence. If the indication (such as the data volume information of the uplink authorization) does not exceed the uplink authorization threshold, the UE sends the first request message to the base station, and the first request message carries an RRC message, which may be an RRC connection establishment request, an RRC connection recovery request message, or an RRC connection common request message.

[0345] Alternatively, the indication may also be an explicit indication, instructing the UE to directly send uplink data when sending the first request message, or instructing the UE to initiate a normal RRC connection establishment or RRC recovery process.

[0346] The uplink authorization threshold can be a statically configured preset value, or can be configured by the base station, such as by sending a newly defined field in a system message to the UE, and can be dynamically adjusted, such as configuring the uplink authorization threshold to 200 bits. Further, the uplink authorization threshold can be configured separately for each coverage level.

[0347] Alternatively, the base station may allocate an appropriate uplink authorization to the terminal according to the terminal request in the random access response, and carry another indication information at the same time. The indication information indicates that if the UE fails to directly send uplink data when sending the first request message this time, the UE should use the random access prefix or random access resource for non-requested uplink data transmission when initiating random access again later, that is, the UE should initiate random access for a normal RRC connection establishment or RRC recovery process.

[0348] Fig.11 The implementation of directly sending uplink data to the base station when the UE sends the first request message, such as Fig.11 As shown, the UE is in the RRC_IDLE state, including:

[0349] Step 1100, the base station sends an uplink grant threshold T_ULgrant through a system message;

[0350] Step 1101: The UE sends a random access prefix to a base station during a random access process to request resources for sending uplink data.

[0351] Step 1102, the base station sends a random access response to the UE, carrying a larger uplink grant;

[0352] Step 1103, the UE determines that the data volume information included in the uplink authorization is greater than the uplink authorization threshold, and the UE sends the uplink data to the base station at the same time when sending the first request message (Mg3);

[0353] If the UP solution is adopted, the UE performed a suspension operation when the last RRC connection was released, and there is a stored UE context and recovery flag. The UE carries the recovery flag while sending uplink data through Msg3. If the CP solution is adopted, the UE should carry the flag assigned to the UE by the core network, such as S-TMSI, or information that can identify the MME to which the UE is attached, such as GUMMEI information, to the base station while sending uplink data packets through Msg3.

[0354] Step 1104, the base station sends a first SI interface message carrying uplink data to the network side;

[0355] Step 1105, the network side sends a second S1 interface message to the base station;

[0356] Step 1106: The base station sends a second response message (Msg4) to the terminal.

[0357] If the indication in the random access response (such as the amount of data authorized in the uplink) does not exceed the uplink authorization threshold, the UE sends a first request message to the base station, and the first request message carries an RRC message. After the UE receives the second response message carrying the RRC message, it should establish or restore the RRC connection and transfer to the RRC_CONNECTED state, such as Fig.12 As shown, including:

[0358] Step 1200, the base station sends an uplink grant threshold T_ULgrant through a system message;

[0359] Step 1201: The UE sends a random access prefix to a base station during a random access process to request resources for sending uplink data.

[0360] Step 1202: The base station sends a random access response to the UE, carrying a small amount of uplink authorized data information (not exceeding the uplink authorization threshold);

[0361] Step 1203, the UE determines that the data volume information of the uplink authorization is less than or equal to the uplink authorization threshold, and the UE sends a first request message (Msg3) to the base station, carrying an RRC connection public request message; the public request message can be an existing RRC connection request message, an RRC connection recovery request message, or a newly defined RRC connection public request message.

[0362] The Msg3 message also carries an identifier assigned by the core network to the UE, such as S-TMSI, or information that can identify the MME to which the UE is attached to the base station; or carries a recovery identifier.

[0363] Step 1204, the base station sends a first S1 interface message to the network side;

[0364] Step 1205, the network side sends a second S1 interface message to the base station;

[0365] Step 1206: The base station sends a second response message (Msg4) to the terminal, carrying an RRC connection common response message. The common response message may be an existing RRC connection establishment message, an RRC connection recovery message, or a newly defined RRC connection common response message.

[0366] Step 1207, the UE establishes an RRC connection and enters the RRC_CONNECTED state;

[0367] Step 1208: The UE sends a Msg5 message to the base station, carrying uplink data.

[0368] Embodiment 7 (After the terminal sends Msg3+data, it can process Msg4+RRC message)

[0369] Even if the base station does not receive the RRC connection establishment request or RRC recovery request message in the first request message, the base station can still actively send RRC to initiate the RRC connection establishment or recovery process and transfer the terminal to the RRC_CONNECTED state, that is, the base station sends a second response message carrying an RRC message to the UE, and the RRC message can be an RRC connection establishment, RRC connection recovery, or RRC connection common response message. After the UE receives the second response message, it should establish or restore the RRC connection and transfer to the RRC_CONNECTED state.

[0370] In the related art, a UE usually needs to send an RRC request message before receiving an RRC response message. The RRC request message may be an RRC connection establishment request message, an RRC connection recovery request message, or a new RRC connection common request message. The RRC response message may be an RRC connection establishment message, an RRC connection recovery message, or a new RRC connection common response message. In this embodiment, even if the UE has not sent an RRC request message, it can still process the RRC response message.

[0371] like Fig.13 As shown, including:

[0372] Step 1300, the base station sends an uplink grant threshold T_ULgrant through a system message;

[0373] Step 1301: The UE sends a random access prefix to a base station during a random access process to request resources for sending uplink data.

[0374] Step 1302: The base station sends a random access response to the UE.

[0375] Step 1003, the UE sends uplink data to the base station simultaneously when sending the first request message (Msg3);

[0376] When the UE sends an uplink data packet via Msg3, it should carry the identifier assigned to the UE by the core network, such as S-TMSI, or information that can identify the MME to which the UE is attached to the base station; or carry the recovery identifier

[0377] Step 1304, the base station sends a first SI interface message carrying uplink data to the network side;

[0378] Step 1305, the network side sends a second S1 interface message to the base station;

[0379] Step 1306: The base station sends a second response message (Msg4) to the base station, carrying an RRC connection common response message. The common response message may be an existing RRC connection establishment message, an RRC connection recovery message, or a newly defined RRC connection common response message.

[0380] Step 1307: The UE establishes an RRC connection and enters the RRC_CONNECTED state.

[0381] Step 1308: The UE sends a Msg5 message to the base station.

[0382] Embodiment 8

[0383] At a certain coverage level, if the UE fails a certain number of times in trying to send uplink data (first format Msg3) while sending the first request message, the UE will prioritize changing the coverage level. When the coverage level reaches the maximum, the UE will switch to trying to send the first request message carrying the RRC message to establish or restore the RRC connection (second format Msg3). Alternatively, at a certain coverage level, if the UE fails a certain number of times in trying to send uplink data (first format) while sending the first request message, the UE will prioritize switching to trying to send the first request message carrying the RRC message to establish or restore the RRC connection (second format Msg3). If it still fails, the UE can switch to the next coverage level according to the existing mechanism. At the new coverage level, the UE will still make random access attempts in the above order.

[0384] The base station may broadcast the operation instruction information in the system message. If the UE is instructed to change the coverage level first, the number of attempts of the UE using the second format Msg3 at the maximum coverage level may be further indicated, or whether the number of attempts is the same as the number of attempts using the second format Msg3. If the UE is instructed to switch to another format Msg3 first, the number of attempts of each format at the current coverage level may be further indicated, or the proportion of the number of attempts of each format in the total number of attempts may be indicated.

[0385] At a certain coverage level, if there is a power boost operation, the UE can terminate or suspend the power boost operation in advance each time a random access is performed. For example, the UE first determines whether the Msg3 format used this time is the same as the last time, and decides whether to terminate or suspend the power boost operation in advance based on the determination result. An example of adjusting the power boost operation is as follows:

[0386] If a different Msg3 format is used from the last one, the power will not be increased, or if a different Msg3 format is used from the last one, and the last one was the first format Msg3, and this time it is the second format Msg3, the power will not be increased, that is, the power boost process is terminated or suspended in advance.

[0387] Alternatively, the UE decides whether to terminate or suspend the power boost operation in advance according to the failure reason of the last access attempt. Another example of adjusting the power boost operation is as follows:

[0388] After the UE fails to use the first format Msg3, the UE decides whether to terminate or suspend the power boost process in advance according to the failure reason. If a certain type of failure reason occurs (such as conflict resolution failure), the UE does not increase the uplink transmission power, but only tries again.

[0389] When the UE is in the RRC_IDLE state, the UE sends a random access prefix in the random access process to request resources for sending uplink data. After the UE obtains uplink authorization, the UE directly sends uplink data to the base station when sending the first request message in the random access process.

[0390] When the UE sends a random access prefix selected in the random access prefix set P1 for requesting uplink data transmission resources in the current coverage level, but fails to receive the second response message sent by the base station (the second response message should include a larger UL grant so that the UE can send uplink data while sending the first request message and does not perform state transfer), or the conflict resolution fails in the subsequent process, resulting in the failure of this random access attempt, the UE needs to initiate the random access process again. At this time, the UE needs to repeatedly send the random access prefix in P1. When this repeated transmission reaches a certain number N1, the number N1 is a preset value corresponding to the current coverage level or is configured by the network side for the UE, and the UE starts to use the random access prefix in the random access prefix set P2 that is not used to request uplink data transmission resources. If after sending the random access prefix in P2, the random access attempt fails because the second response message sent by the base station is not received (the second response message should include a smaller UL grant so that the UE can send a first request message including an RRC message to establish or restore an RRC connection) or the conflict resolution fails in the subsequent process, the UE will repeatedly send the random access prefix in P2. When such repeated transmission reaches a certain number N2, which is a preset value corresponding to the current coverage level or configured by the network side for the UE, the UE jumps to the next coverage level and repeats the above process again.

[0391] When the terminal uses the random access prefix set P1 for random access, if the random access attempt fails due to failure to receive a random access response, the UE marks the failure reason S1. If the random access attempt fails due to a conflict resolution failure in a subsequent process, the UE marks the failure reason S2. When the UE fails due to reason S1, it can be processed according to the existing mechanism, that is, when the terminal uses the random access prefix in P1 for random access again, the uplink transmit power can be increased according to the configuration parameters. However, when the UE fails due to reason S2, there may be multiple UEs trying to send uplink data while sending the first request message, and the system load is heavy. At this time, if the transmit power is still increased during retransmission, it may cause the system conflict to intensify. Therefore, in the next attempt, the UE does not increase the uplink transmit power, but only tries again.

[0392] Embodiment 9 (Parallel uplink data transmission and RRC connection re-establishment process)

[0393] When the UE is in the RRC_CONNECTED state, the RRC re-establishment process may be triggered due to RLF or other reasons. At this time, the UE needs to initiate a random access process. When the RRC is re-established, there may be uplink data to be transmitted or retransmitted. At this time, uplink data can be sent while re-establishing, that is, parallel uplink data transmission and RRC connection re-establishment process are performed.

[0394] like Fig.14 As shown, the UE is in the RRC_CONNECTED state and uses the CP scheme to transmit uplink data in the random access process, including:

[0395] Step 1401: The UE sends a random access prefix to a base station during a random access process to request resources for sending uplink data.

[0396] Step 1402, the base station sends a random access response to the UE;

[0397] Step 1403, the UE sends a first request message (Msg3) to the base station, carrying an RRC connection common request message and uplink data; the RRC connection common request message can be an existing RRC connection re-establishment request message or a new RRC connection common request message.

[0398] The Msg3 message also carries an identifier assigned by the core network to the UE, such as an S-TMSI, or information that can identify the MME to which the UE is attached to the base station; for example, in GUMMEI step 1404, the base station sends a first SI interface message carrying uplink data to the network side;

[0399] Step 1405, the network side sends a second S1 interface message to the base station;

[0400] Step 1406: The base station sends a second response message (Msg4) to the terminal, carrying an RRC connection common response message. The RRC connection common response message may be an existing RRC connection re-establishment message or a new RRC connection common response message.

[0401] like Fig.15 As shown in FIG. 1 , the process of transmitting uplink data in a random access process using the UP scheme includes:

[0402] Step 1501: The UE sends a random access prefix to a base station during a random access process to request resources for sending uplink data.

[0403] Step 1502: The base station sends a random access response to the UE.

[0404] Step 1503, the UE sends a first request message (Msg3) to the base station, carrying an RRC connection common request message and uplink data; the RRC connection common request message can be an existing RRC connection re-establishment request message or a new RRC connection common request message.

[0405] The Msg3 message also carries the reestablishment terminal identifier (Reestablish-UEID);

[0406] Step 1504, the base station sends a first SI interface message carrying uplink data to the network side;

[0407] Step 1505, the network side sends a second S1 interface message to the base station;

[0408] Step 1506: The base station sends a second response message (Msg4) to the terminal, carrying an RRC connection common response message. The RRC connection common response message may be an existing RRC connection re-establishment message or a new RRC connection common response message.

[0409] Embodiment 10 (Quickly releasing after sending uplink data in connected state)

[0410] When the UE is in the RRC_CONNECTED state and has data to send, and the UE is out of synchronization or has no uplink resources, the UE needs to initiate a random access procedure.

[0411] If the UE sends a random access prefix for requesting resources for sending uplink data, and the UE receives a random access response sent by the base station and obtains sufficient uplink authorization, it can be considered that the UE and the base station have negotiated to complete data sending as soon as possible and can initiate a fast RRC connection release. The UE will send uplink data to the base station at the same time as sending the first request message.

[0412] If the UE sends a random access prefix that is not used to request resources for sending uplink data, or the UE does not obtain sufficient uplink authorization from the base station, it can be considered that the UE and the base station will establish an RRC connection according to the existing process and send data in subsequent processes.

[0413] After the UE sends the first request message and uplink data, if it receives the second response message sent by the base station and determines that the conflict is successfully resolved, the UE autonomously releases to the RRC_IDLE state.

[0414] When the UE sends the first request message and uplink data, it can carry a request release indication, such as BSR=0, indicating that the base station can release. After receiving the first request message and uplink data, the base station can trigger a quick release, and carry an RRC release message in the second response message sent by the base station to the UE. The release message should be sent in RLC AM mode. When the UE receives the second response message, it first determines that the conflict is resolved successfully, then processes the RRC release message and sends an ACK confirmation to the message, and then the UE and the base station are released to the RRC_IDLE state according to the existing standards. If the conflict resolution fails, the UE will not process the RRC message carried by the second response message. Compared with the related art, the RRC release message in the related art can only be sent through SRB1, and the RRC release message in the present application can be sent through SRB0.

[0415] The base station broadcasts different uplink authorization thresholds for the idle state and the connected state through system messages. The connected state should have a stricter uplink authorization threshold, that is, the uplink authorization threshold should ensure that when the UE initiates random access to transmit data in the connected state, it should transmit all the data to be transmitted at one time and release the connection as much as possible. The uplink authorization threshold of the connected state is greater than the uplink authorization threshold of the idle state.

[0416] like Fig.16 As shown, including:

[0417] Step 1601: The UE sends a random access prefix to a base station during a random access process to request resources for sending uplink data.

[0418] Step 1602: The base station sends a random access response to the UE.

[0419] Step 1603, the UE sends a first request message (Msg3) carrying uplink data to the base station, carrying a request release indication, such as BSR=0;

[0420] The Msg3 message also carries the temporary identification of the cell wireless network.

[0421] Step 1604, the base station sends a first S1 interface message carrying uplink data to the network side;

[0422] Step 1605, the network side sends a second S1 interface message to the base station;

[0423] Step 1606: The base station sends a second response message (Msg4) to the terminal, carrying an RRC connection release message.

[0424] Step 1607, the UE first processes Msg4, then processes the connection release message, and then the UE is released to the RRC_IDLE state.

[0425] Embodiment 11 (Non-contention access Msg2 carrying downlink data)

[0426] When the UE is in the RRC_CONNECTED state, if the network side has downlink data to send to the UE but finds that the UE is in an asynchronous state, the base station needs to send a PDCCH order (command) to the UE to trigger a random access process.

[0427] The PDCCH order contains non-contention resources allocated by the base station to the UE. When the UE initiates random access using the random access prefix corresponding to the non-contention resource, the base station finds the information of the UE, and then the base station sends a random access response to the UE. The random access response contains an indication that downlink data is sent to the UE at the same time. The UE uses the received downlink authorization to receive the downlink data, and then the UE can send a first request message to the base station, including confirmation of the received downlink data. The UE needs to process the TA information first, complete the synchronization process, and then process the downlink data packet.

[0428] like Fig.17 As shown, the UE is in the RRC_CONNECTED state, including:

[0429] Step 1700: The network side sends downlink data to the base station;

[0430] Step 1701, the base station sends a PDCCH order to the UE, carrying the non-contention resources allocated by the base station to the UE;

[0431] Step 1702, the UE sends a random access prefix corresponding to the non-contention resource to the base station;

[0432] Step 1703: The base station sends a random access response to the UE and sends the downlink data at the same time, wherein the random access response carries indication information indicating that the downlink data is to be sent at the same time;

[0433] Step 1704: After receiving the random access response, the UE uses the received downlink grant to receive the downlink data, and then sends a first request message (Mg3) to the base station, carrying confirmation information for the downlink data;

[0434] Step 1705: The base station sends a first S1 interface message to the network side, carrying confirmation information of the downlink data;

[0435] Step 1706: The network side sends a second S1 interface message to the base station.

[0436] Embodiment 12

[0437] When the UE is in the RRC_IDLE state, the UE sends a random access prefix during the random access process to request resources for sending uplink data. The UE determines whether it can request resources for sending uplink data in the following way:

[0438] The base station configures a data carrying decision threshold T_ULdataRA for each coverage level. When the UL data to be sent in the UE buffer is greater than or equal to the data carrying decision threshold, the UE selects a random access prefix from the random access prefix set P1 used to request uplink data transmission resources, otherwise, the UE selects a random access prefix from the random access prefix set P2 not used to request uplink data transmission resources.

[0439] P1 and P2 are divided as follows:

[0440] Method 1: Select a resource that is not a PRACH resource configured for each coverage level as P1, for example:

[0441] The base station configures one or more groups of data transmission PRB resources (all PRBs are different from the PRACH / paging PRBs configured for R14 UEs) as P1 for R15 UEs. At this time, all PRACH / paging PRBs configured for R14 UEs can be regarded as P2. When multiple groups of data transmission PRB resources are configured, each group of data transmission PRB resources is used to indicate a certain uplink data size requirement. For example, three groups of data transmission PRB resources are configured, which are identified as Group A, Group B, and Group C respectively. Each group of data transmission PRB resources contains one or more PRBs. When the UE selects any PRB in Group A, it means that the UE requests to send uplink data of a size between [DataSizeMinGroupA, DataSizeMaxGroupA] at the same time when sending the first request message; each PRB can be further divided into PRACH time domain and subcarrier (subcarrier) resources for different coverage levels, which is the same as the existing method.

[0442] The base station configures all subcarriers that are not configured for R14 UE as P1 for R15 UE, and the PRACH resources for each coverage level configured for R15 UE no longer include subcarrier resources. At this time, the subcarrier configured for R14 UE can be regarded as P2. The subcarriers in P1 can be further divided into one or more groups of data transmission subcarrier resources, and three groups of data transmission subcarrier resources are configured, which are identified as Group A, Group B, and Group C respectively. Each group of data transmission subcarrier resources contains one or more subcarriers. When the UE selects any subcarrier in Group A, it means that the UE requests to send uplink data with a size between [DataSizeMinGroupA, DataSizeMaxGroupA] at the same time when sending the first request message; after the R15 UE selects the subcarrier, it needs to further select the PRACH resources corresponding to its coverage level. For example Fig.18 As shown, Fig.18 CE1_CBRA_S indicates the contention random access resources for Msg3 transmitted in single-tone mode at coverage level 1, CE1_CBRA_M indicates the contention random access resources for Msg3 transmitted in multi-tone mode at coverage level 1, and CE1_CFRA indicates the non-contention resources for coverage level 1. CE2_CBRA indicates all contention random access resources at coverage level 2, and CE2_CFRA indicates the non-contention resources for coverage level 2. CE3_CBRA indicates all contention random access resources at coverage level 3, and CE3_CFRA indicates the non-contention resources for coverage level 3.

[0443] Method 2: Select a resource belonging to the PRACH resources configured for each coverage level as P1, for example:

[0444] The base station further divides the unused subcarrier resources in the non-contention resources at each coverage level into one or more groups of data transmission subcarrier resources:

[0445] Although in the parameter configuration of R14, the non-contention resources calculated by (nprach-NumSubcarriers-nprach-NumCBRA-StartSubcarriers) should be a continuous value, according to the R14 technology, the UE and the terminal use mod operations to ensure that the UE still uses the Subcarriers known to the base station after changing the coverage level. In this way, the non-contention Subcarriers actually used will be discontinuous. Therefore, the base station may configure the unused subcarrier resources in the non-contention resources under each coverage level as P1_CE1. See Fig.19 As shown, Fig.19CE1_CBRA_S identifies the contention random access resources for single-tone transmission of Msg3 at coverage level 1, CE1_CBRA_S identifies the contention random access resources for multi-tone transmission of Msg3 at coverage level 1, and CE1_CFRA identifies the non-contention resources at coverage level 1. CE1_CFRA_A1 to CE1_CFRA_A3 respectively identify the resources that have not been configured for existing terminals in the non-contention resources at coverage level 1, and can be configured as random access resources for requesting uplink data transmission resources at coverage level 1. CE2_CBRA identifies all contention resources at coverage level 2. CE2_CFRA identifies the non-contention resources at coverage level 2. CE3_CBRA_S identifies the contention random access resources for single-tone transmission of Msg3 at coverage level 3, and CE3_CBRA_M identifies the contention random access resources for multi-tone transmission of Msg3 at coverage level 3. CE3_CFRA identifies the non-contention resources at coverage level 3. P1 for all CEs (P1_CE1) identifies the resources in all subcarrier resources that have not been configured for existing terminals and can be configured as random access resources for requesting uplink data transmission resources for all coverage levels. Further, the sum of random access resources for requesting uplink data transmission resources at all coverage levels is: P1 = P1_CE1 + P1_CE2 + P1_CE3.

[0446] If there are no unused subcarrier resources in the non-contention resources at each coverage level, the base station can configure the non-contention resources at each coverage level as P1 for R15 UE, provided that the base station can distinguish between random access initiated by connected UE and random access initiated by idle UE through implementation. Fig. 20 As shown, Fig. 20CE1_CBRA_S identifies the contention random access resources for indicating the transmission of Msg3 in single-tone mode at coverage level 1, CE1_CBRA_M identifies the contention random access resources for indicating the transmission of Msg3 in multi-tone mode at coverage level 1, and CE1_CFRA identifies the non-contention resources at coverage level 1. CE1_CFRA_A1 to CE1_CFRA_A3 respectively identify some resources in the non-contention resources at coverage level 1, which have been configured for existing terminals. If the base station can distinguish between existing terminals and new terminals, these resources may be configured as random access resources for requesting uplink data transmission resources at coverage level 1. CE2_CBRA identifies all contention random access resources at coverage level 2. CE2_CFRA identifies the non-contention resources at coverage level 2. CE3_CBRA_S identifies coverage level 3 and is used to indicate contention random access resources for transmitting Msg3 in single-tone mode. CE3_CBRA_M identifies coverage level 3 and is used to indicate contention random access resources for transmitting Msg3 in multi-tone mode. CE3_CFRA identifies non-contention resources for coverage level 3.

[0447] The base station further divides the subcarrier resources configured for Multi-tone Msg3 in the contention resources under each coverage level into one or more groups of data transmission subcarrier resources. Fig.21 As shown, Fig.21 CE1_CBRA_S identifies the contention random access resources for single-tone transmission of Msg3 at coverage level 1, CE1_CBRA_M identifies the contention random access resources for multi-tone transmission of Msg3 at coverage level 1, and CE1_CFRA identifies the non-contention resources at coverage level 1. CE2_CBRA identifies all contention random access resources at coverage level 2, and CE2_CFRA identifies the non-contention resources at coverage level 2. CE3_CBRA_S identifies the contention random access resources for single-tone transmission of Msg3 at coverage level 3, and CE3_CBRA_M identifies the contention random access resources for multi-tone transmission of Msg3 at coverage level 1. CE3_CFRA identifies the non-contention resources at coverage level 3. CE3_CBRA_A1 to CE3_CBRA_A3 indicate that some resources are configured from CE3_CBRA_M to identify random access resources that can be used for requesting uplink data transmission resources at coverage level 3.

[0448] Only UE supporting multi-tone Msg3 transmission is allowed to send uplink data while sending the first request message.

[0449] An embodiment of the present invention provides a data transmission device, including a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the data transmission method described in any of the above embodiments is implemented.

[0450] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the data transmission method described in any of the above embodiments.

[0451] The computer-readable storage medium includes: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0452] Although the embodiments disclosed in the present invention are as above, the contents described are only embodiments adopted to facilitate understanding of the present invention and are not intended to limit the present invention. Any technician in the field to which the present invention belongs can make any modifications and changes in the form and details of implementation without departing from the spirit and scope disclosed in the present invention, but the patent protection scope of the present invention shall still be subject to the scope defined in the attached claims.

[0453] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A data transmission method, characterized in that: include: The terminal sends a random access prefix to the base station, and receives a random access response from the base station; The terminal sends a first request message carrying uplink data to the base station; The terminal sending a random access prefix to the base station includes: When the terminal meets the first preset condition, the terminal sends a random access prefix for requesting uplink data transmission resources to the base station; The method further includes: when the terminal does not receive a second response message returned by the base station, or when the terminal receives a second response message returned by the terminal base station and the second response message carries an uplink data failure indication or an uplink data retransmission indication, or when the terminal does not receive a random access response returned by the base station, the current random access fails, and the terminal re-initiates random access; The terminal re-initiating random access includes: The terminal determines, based on at least one of the number of random access failures, the number of random access failures sequence, the downlink measurement value obtained by the terminal, the coverage level, and the number of repetitions, whether to send a random access prefix for requesting uplink data transmission resources for random access, or to select a random access prefix not for requesting uplink data transmission resources for random access.

2. The data transmission method according to claim 1, characterized in that: The second response message carries at least one of the following: a conflict resolution identifier, high-layer confirmation information for the uplink data, or user service data.

3. The data transmission method according to claim 1, characterized in that: The first request message also carries one of the following or a combination thereof: indication information on whether the S1 interface needs to be established first, indication information on whether high-level confirmation information of the uplink data needs to be received, information for identifying the mobility management entity registered by the terminal, terminal identification information, access layer security information, and the reason for establishing the connection corresponding to data transmission.

4. The data transmission method according to claim 1, characterized in that: After the terminal receives the second response message returned by the base station and obtains the cell radio network temporary identifier, the method further includes: The terminal uses the cell radio network temporary identifier to detect a physical downlink control channel in a common search space or a search space for transmitting the second response message scheduling information, or detects uplink or downlink scheduling information.

5. The data transmission method according to claim 1, characterized in that: The terminal sending a random access prefix for requesting uplink data transmission resources to the base station includes: The terminal selects a random access prefix from a random access prefix set used to request uplink data transmission resources, and sends the selected random access prefix to the base station, or, The terminal selects a random access resource from a random access resource set used to request uplink data transmission resources, and uses the selected random access resource to send a random access prefix to the base station.

6. The data transmission method according to claim 1, characterized in that: The terminal satisfies the first preset condition including one of the following or a combination thereof: the uplink data to be sent by the terminal is greater than the data carrying decision threshold; the wireless link condition of the terminal satisfies the link condition threshold; the service type of the uplink data to be sent by the terminal belongs to the preset service type.

7. The data transmission method according to claim 1, characterized in that: The method also includes that the terminal obtains one or a combination of the following from the system message sent by the base station: a data carrying decision threshold, a link condition threshold, and preset service type information, wherein the data carrying decision threshold includes a data carrying decision threshold configured for all coverage levels or a data carrying decision threshold configured for each coverage level.

8. The data transmission method according to claim 1, characterized in that: The terminal re-initiates random access in one of the following ways: Under the current coverage level, when the number of failures of the terminal in sending a random access prefix for requesting uplink data transmission resources for random access reaches the corresponding failure number threshold, the terminal changes the coverage level to the maximum coverage level, and then sends a random access prefix not for requesting uplink data transmission resources or sends a random access prefix in an existing manner for random access; At the current coverage level, when the number of failures of the terminal in sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, the terminal sends a random access prefix not for requesting uplink data transmission resources or sends a random access prefix in an existing manner for random access. If it fails and the number of failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level greater than the current coverage level, and performs random access at the coverage level in the same random access method as at the previous coverage level until the random access succeeds, or, when the maximum coverage level is reached, random access is performed at the maximum coverage level in the same random access method as at the previous coverage level; Under the current coverage level, when the number of failures of the terminal carrying uplink data in the first request message for random access reaches the corresponding failure number threshold, the terminal changes the coverage level to the maximum coverage level and then sends the first request message carrying the radio resource control message for random access; At the current coverage level, when the number of failures of the terminal carrying uplink data in the first request message for random access reaches the corresponding failure number threshold, the terminal sends a first request message carrying a radio resource control message for random access. If it fails and the number of failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level greater than the current coverage level, and performs random access at the coverage level in the same random access method as the previous coverage level until the random access is successful, or reaches the maximum coverage level, and performs random access at the maximum coverage level in the same random access method as the previous coverage level; When the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, the terminal sends a random access prefix not for requesting uplink data transmission resources for random access; When the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold, and the reference signal received power value measured by the terminal is in a first predefined range, the terminal sends a random access prefix not for requesting uplink data transmission resources for random access; when the number of failures of sending a random access prefix for requesting uplink data transmission resources for random access reaches a corresponding failure number threshold and the reference signal received power value measured by the terminal is in a second predefined range, the terminal switches to the next coverage level and sends a random access prefix for requesting uplink data transmission resources for random access; After the terminal fails to perform random access by sending a random access prefix for requesting uplink data transmission resources, the terminal sends a random access prefix not for requesting uplink data transmission resources, and after the terminal fails to perform random access by sending a random access prefix not for requesting uplink data transmission resources, the terminal sends a random access prefix for requesting uplink data transmission resources for random access, repeating the previous method, when the number of access failures reaches the corresponding failure number threshold, the terminal switches to the next coverage level, and performs random access at the coverage level according to the same random access method as the previous coverage level, until the random access is successful, or, reaches the maximum coverage level, and performs random access at the maximum coverage level according to the same random access method as the previous coverage level.

9. The data transmission method according to claim 8, characterized in that: The method further includes: the terminal acquiring the failure number threshold corresponding to each coverage level by receiving a system message broadcast by the base station or a dedicated message sent by the base station to the terminal.

10. The data transmission method according to claim 1, characterized in that: Before the terminal re-initiates random access, the method further includes: the terminal acquiring operation instruction information from the base station, and determining a method for re-initiating random access according to the operation instruction information.

11. The data transmission method according to claim 1, characterized in that: Before the terminal performs random access, determining whether to terminate or suspend the power boost operation according to at least one of the following: Whether the format of the first request message of this random access is the same as the format of the first request message of the previous random access; whether the manner of sending the random access prefix in this random access is the same as the manner of sending the random access prefix in the previous random access; the manner of sending the random access prefix includes sending a random access prefix for requesting uplink data transmission resources and sending a random access prefix not for requesting uplink data transmission resources; The reason for the previous random access failure.

12. The data transmission method according to claim 1, characterized in that: When the terminal is in a connected state before sending the random access prefix, the first request message further carries one of the following or a combination thereof: a cell wireless network temporary identifier, a radio resource control message, and a release request indication.

13. The data transmission method according to claim 12, characterized in that: When the terminal is in a connected state before sending the random access prefix, the terminal further includes: The terminal receives the second response message returned by the base station, determines that the conflict is successfully resolved, and autonomously releases the radio resource control connection and transfers to an idle state; Alternatively, the terminal receives a second response message returned by the base station, and after determining that the conflict is successfully resolved, processes the radio resource control release message carried in the second response message and transfers to the idle state.

14. The data transmission method according to claim 1, characterized in that: The terminal sends a first request message carrying uplink data to the base station, including: When the terminal is in an idle state, during a random access process, the terminal sends a first request message to a base station, receives a second response message sent by the base station, and obtains downlink data from the second response message.

15. The data transmission method according to claim 1, characterized in that: include: During the process of random access when the terminal is in an idle state, after receiving a first S1 interface message sent by a base station, the network side sends a second S1 interface message to the base station, where the second S1 interface message carries downlink data to be sent to the terminal.

16. The data transmission method according to claim 15, characterized in that: The method further includes, before the terminal initiates random access in an idle state, the network side receives downlink data sent by an application layer and needs to be sent to the terminal, and caches the downlink data.

17. The data transmission method according to claim 1, characterized in that: include: When the terminal is in a connected state, the terminal receives a physical downlink control channel command sent by the base station, obtains a non-contention resource allocated by the base station to the terminal from the physical downlink control channel command, and initiates random access using a random access prefix corresponding to the non-contention resource; The terminal receives a random access response sent by the base station, and when the random access response carries indication information of simultaneously sending downlink data, the terminal receives the downlink data.

18. A data transmission device, characterized in that: The invention comprises a memory and a processor, wherein the memory stores a program, and when the program is read and executed by the processor, the program executes a data transmission method, wherein the data transmission method comprises: The terminal sends a random access prefix to the base station, and receives a random access response from the base station; The terminal sends a first request message carrying uplink data to the base station; The terminal sending the random access prefix to the base station includes: When the terminal meets the first preset condition, the terminal sends a random access prefix for requesting uplink data transmission resources to the base station; The method further includes: when the terminal does not receive a second response message returned by the base station, or when the terminal receives a second response message returned by the terminal base station and the second response message carries an uplink data failure indication or an uplink data retransmission indication, or when the terminal does not receive a random access response returned by the base station, the current random access fails, and the terminal re-initiates random access; The terminal re-initiating random access includes: The terminal determines, based on at least one of the number of random access failures, the number of random access failures sequence, the downlink measurement value obtained by the terminal, the coverage level, and the number of repetitions, whether to send a random access prefix for requesting uplink data transmission resources for random access, or to select a random access prefix not for requesting uplink data transmission resources for random access.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to transmit the data transmission method according to claim 1.

20. A data transmission method, characterized in that: include: The terminal sends a random access prefix to the base station, and receives a random access response from the base station; The terminal sends a first request message carrying uplink data to the base station; The terminal sending the random access prefix to the base station includes: When the terminal meets the first preset condition, the terminal sends a random access prefix for requesting uplink data transmission resources to the base station; Wherein, when the terminal is in a connected state before sending the random access prefix, the first request message further carries one of the following or a combination thereof: a cell wireless network temporary identifier, a radio resource control message, and a request release indication; When the terminal is in a connected state before sending the random access prefix, the terminal further includes: The terminal receives the second response message returned by the base station, determines that the conflict is successfully resolved, and autonomously releases the radio resource control connection and transfers to an idle state; Alternatively, the terminal receives a second response message returned by the base station, and after determining that the conflict is successfully resolved, processes the radio resource control release message carried in the second response message and transfers to the idle state.

Images