WO2019029747A1 - 一种数据传输方法及装置、计算机可读存储介质 - Google Patents

一种数据传输方法及装置、计算机可读存储介质 Download PDF

Info

Publication number
WO2019029747A1
WO2019029747A1 PCT/CN2018/100247 CN2018100247W WO2019029747A1 WO 2019029747 A1 WO2019029747 A1 WO 2019029747A1 CN 2018100247 W CN2018100247 W CN 2018100247W WO 2019029747 A1 WO2019029747 A1 WO 2019029747A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
terminal
base station
data transmission
message
Prior art date
Application number
PCT/CN2018/100247
Other languages
English (en)
French (fr)
Inventor
陆婷
戴博
沙秀斌
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP18845080.3A priority Critical patent/EP3668190A4/en
Priority to US16/638,311 priority patent/US11357054B2/en
Publication of WO2019029747A1 publication Critical patent/WO2019029747A1/zh
Priority to US17/738,180 priority patent/US11751255B2/en
Priority to US18/223,753 priority patent/US20230363009A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/085—Random access procedures, e.g. with 4-step access with collision treatment collision avoidance

Definitions

  • the present application relates to communication technologies, such as a data transmission method and apparatus, and a computer readable storage medium.
  • the energy consumption of the terminal is crucial.
  • the UE when the UE is in an idle state (RRC_IDLE) and data needs to be transmitted, the UE first triggers a random access procedure to establish or restore a Radio Resource Control (RRC) connection with the network, and the UE can initially follow the data.
  • RRC Radio Resource Control
  • the RRC connection setup complete or RRC recovery complete message is sent to the base station together.
  • the UE will then remain in the connected state (RRC_CONNECTED) for a period of time, waiting for the base station to release the UE.
  • the UE may first initiate random access because of loss of time synchronization or no uplink resources, and send data to the base station after the random access procedure is completed.
  • An embodiment of the present application provides a data transmission method and apparatus, and a computer readable storage medium.
  • An embodiment of the present application provides a data transmission method, including: a terminal sending a random access prefix to a base station, and receiving a random access response sent by the base station; the terminal sending a first request message carrying uplink data to the Base station.
  • An embodiment of the present application provides a data transmission apparatus including a memory and a processor, wherein the memory stores a program, and the program implements the data transmission method when read and executed by the processor.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program executable by at least one processor to implement the data transmission method described above.
  • An embodiment of the present invention provides a data transmission method, including: receiving, by a base station, a random access prefix sent by a terminal, and sending a random access response to the terminal; and receiving, by the base station, a first request for carrying uplink data sent by the terminal Message.
  • the first S1 interface message is one of: an initial user equipment information message, a user equipment context recovery request message, an uplink non-access stratum transmission message, a path switch request message, and a newly defined S1 interface message.
  • the second S1 interface message is one of the following: a connection establishment indication message, a user equipment context recovery response message, a downlink non-access stratum transmission message, a path switch request acknowledgement message, and a newly defined S1 interface message.
  • An embodiment of the present application provides a data transmission apparatus including a memory and a processor, wherein the memory stores a program, and the program implements the data transmission method when read and executed by the processor.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program executable by at least one processor to implement the data transmission method described above.
  • An embodiment of the present application provides a data transmission method, including: when a terminal is in an idle state, in a random access procedure, sending a first request message to a base station, and receiving a second response message sent by the base station, from the The second response message acquires downlink data.
  • An embodiment of the present application provides a data transmission apparatus, including a memory and a processor, where the memory stores a program, and when the program is read and executed by the processor, the following operations are performed: when the terminal is in an idle state, After the first request message is sent to the base station, the second response message sent by the base station is received, and the downlink data is obtained from the second response message.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program, the at least one program being executable by at least one processor to implement the following steps:
  • the terminal When the terminal is in the idle state, in the random access process, after sending the first request message to the base station, the second response message sent by the base station is received, and the downlink data is obtained from the second response message.
  • An embodiment of the present application provides a data transmission method, including: in a process in which a terminal is in an idle state for performing random access, the base station receives a first request message sent by the terminal, and if the base station has downlink data that needs to be sent to the terminal, The base station carries the downlink data when sending the second response message to the terminal.
  • An embodiment of the present application provides a data transmission apparatus including a memory and a processor, wherein the memory stores a program, and the program implements the data transmission method when read and executed by the processor.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program executable by at least one processor to implement the data transmission method described above.
  • An embodiment of the present application provides a data transmission method, including: in a process in which a terminal is in an idle state for performing random access, after receiving a first S1 interface message sent by a base station, the network side sends a second S1 interface to the base station.
  • the message that the second S1 interface message carries downlink data that needs to be sent to the terminal.
  • An embodiment of the present application provides a data transmission apparatus including a memory and a processor, wherein the memory stores a program, and the program implements the data transmission method when read and executed by the processor.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program executable by at least one processor to implement the data transmission method described above.
  • An embodiment of the present invention provides a data transmission method, including: when a terminal is in a connected state, the terminal receives a physical downlink control channel command sent by a base station, and obtains, by using the physical downlink control channel command, the base station to allocate the a non-contention resource of the terminal, using a random access prefix corresponding to the non-competitive resource to initiate a random access; the terminal receiving a random access response sent by the base station, and carrying the downlink in the random access response When the indication information of the data, the terminal receives the downlink data.
  • An embodiment of the present application provides a data transmission apparatus, including a memory and a processor, where the memory stores a program, and when the program is read and executed by the processor, the following operations are performed: when the terminal is in a connected state, Receiving a physical downlink control channel command sent by the base station, acquiring a non-contention resource allocated by the base station to the terminal from the physical downlink control channel command, and using the random access prefix corresponding to the non-contention resource to initiate random access; And receiving the random access response sent by the base station, and receiving the downlink data when the random access response carries the indication information that simultaneously sends the downlink data.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program, the at least one program being executable by at least one processor to implement the following steps: the terminal is in a connected state Receiving a physical downlink control channel command sent by the base station, acquiring, from the physical downlink control channel command, the non-contention resource allocated by the base station to the terminal, and using the random access prefix corresponding to the non-contention resource to initiate random connection And receiving the random access response sent by the base station, and receiving the downlink data when the random access response carries the indication information that simultaneously sends the downlink data.
  • An embodiment of the present application provides a data transmission method, including: when a terminal is in a connected state, a base station sends a physical downlink control channel command to the terminal, where the physical downlink control channel command carries the base station and is allocated to the terminal 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, where the random access response carries At the same time, the indication information of the downlink data is sent, and the downlink data is delivered at the same time.
  • An embodiment of the present application provides a data transmission apparatus, including a memory and a processor, where the memory stores a program, and when the program is read and executed by the processor, the following operations are performed: when the terminal is in a connected state, Sending 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; and receiving, by the terminal, a random access prefix corresponding to the non-contention resource After the initiated random access, the random access response is sent to the terminal, and the random access response carries the indication information of simultaneously transmitting the downlink data, and simultaneously delivers the downlink data.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program, the at least one program being executable by at least one processor to implement the following steps: the terminal is in a connected state Sending 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; and receiving, by the terminal, a random connection corresponding to the non-competition resource After the random access initiated by the prefix is sent, the random access response is sent to the terminal, and the random access response carries the indication information of simultaneously transmitting the downlink data, and simultaneously delivers the downlink data.
  • FIG. 3 is a flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a data transmission method according to Embodiment 1 of the present application.
  • FIG. 6 is a flowchart of a data transmission method according to Embodiment 2 of the present application.
  • FIG. 7 is a flowchart of a data transmission method according to Embodiment 3 of the present application.
  • FIG. 8 is a flowchart of a data transmission method according to Embodiment 4 of the present application.
  • FIG. 9 is a flowchart of a data caching method according to Embodiment 5 of the present application.
  • FIG. 10 is a flowchart of a data transmission method according to an embodiment of the present disclosure (first sending a second response message, and then sending a first S1 interface message);
  • FIG. 11 is a flowchart of a data transmission method according to Embodiment 6 of the present application.
  • FIG. 12 is a flowchart of another data transmission method according to Embodiment 6 of the present application.
  • FIG. 13 is a flowchart of a data transmission method according to Embodiment 7 of the present application.
  • FIG. 14 is a flowchart of a data transmission method according to Embodiment 9 of the present application.
  • FIG. 15 is a flowchart of another data transmission method according to Embodiment 9 of the present application.
  • FIG. 17 is a flowchart of a data transmission method according to Embodiment 11 of the present application.
  • FIG. 18 is a schematic diagram of resource division according to Embodiment 12 of the present application.
  • FIG. 19 is a schematic diagram of another resource division according to Embodiment 12 of the present application.
  • FIG. 20 is a schematic diagram of another resource division according to Embodiment 12 of the present application.
  • FIG. 21 is a schematic diagram of another resource division according to Embodiment 12 of the present application.
  • the UE is in the RRC_IDLE state, and uses the CP scheme to upload data after the random access procedure, including steps 101 to 105.
  • step 101 the UE sends an Msg1 message to an evolved Node B (eNB) carrying a random access prefix (Preamble).
  • eNB evolved Node B
  • step 102 the eNB sends an Msg2 message to the UE, and carries a random access response (RAR).
  • RAR random access response
  • the UE sends an Msg3 message to the eNB, and carries an RRC Connection Request (RRCConnectionRequest) and a System Architecture Evolutionary Mobile Subscriber Identity (S-TMSI).
  • RRCConnectionRequest RRC Connection Request
  • S-TMSI System Architecture Evolutionary Mobile Subscriber Identity
  • step 104 the eNB sends an Msg4 message to the UE, carrying an RRC Connection Setup message (RRCConnectionSetup).
  • RRCConnectionSetup an RRC Connection Setup message
  • step 105 the UE sends an Msg5 message to the eNB, carrying an RRC Connection Setup Complete message (RRCConnectionSetupComplete and uplink data (UL data).
  • RRCConnectionSetupComplete RRC Connection Setup Complete message
  • UL data uplink data
  • the UE is in the RRC_IDLE state, and uses the UP scheme to upload data after the random access procedure, including steps 201 to 206.
  • step 201 the UE sends an Msg1 message to the eNB, carrying a random access prefix (Preamble).
  • Preamble a random access prefix
  • step 202 the eNB sends an Msg2 message to the UE, and carries a random access response (RAR).
  • RAR random access response
  • the UE sends an Msg3 message to the eNB, and carries an RRC connection recovery request (RRCConnectionResumeRequest) and a recovery identifier (ResumeID).
  • RRCConnectionResumeRequest RRC connection recovery request
  • ResumeID recovery identifier
  • step 204 the eNB sends an Msg4 message to the UE, carrying an RRC Connection Recovery message (RRCConnectionResume).
  • RRCConnectionResume an RRC Connection Recovery message
  • step 205 the UE sends an Msg5 message to the eNB, carrying an RRC Connection Recovery Complete message (RRCConnectionResumeComplete).
  • RRCConnectionResumeComplete an RRC Connection Recovery Complete message
  • step 206 the UE sends uplink data to the eNB.
  • the terminal when the terminal sends uplink data to the base station, the RRC connection needs to be established or restored, and the terminal sends the uplink data to the base station after the RRC connection is successfully established or restored.
  • a static or low mobility UE may only need to send one data packet at a time, and the time interval between two data packet transmissions is longer. In this case, the UE enters RRC_CONNECTED. After the state, only one data packet is sent, but the base station signal is continuously monitored for a period of time in the RRC_CONNECTED state.
  • the terminal When the terminal sends the data once, it returns to the RRC_IDLE state, and even returns to the Power Save Mode (PSM) state, and re-initiates the RRC establishment or recovery request when the data is transmitted next time.
  • the data transmission method in the related art causes unnecessary power consumption in the terminal. Therefore, the embodiment of the present application provides a data transmission scheme to improve the energy consumption of the terminal uploading data in the related art.
  • An embodiment of the present application provides a data transmission method, as shown in FIG. 3, including step 301, step 302, and step 303.
  • step 301 the terminal sends a random access prefix to the base station, and receives a random access response sent by the base station.
  • step 302 the terminal sends a first request message (Msg3) carrying uplink data to the base station.
  • Msg3 a first request message
  • the method further includes the step 303, the terminal receiving the second response message (Msg4) returned by the base station, and determining that the conflict resolution is successful,
  • Msg4 returned by the base station
  • the terminal is maintained in an idle state, and the temporary wireless network temporary identifier allocated by the base station is used as a temporary identifier of the cell wireless network, and the temporary identifier of the cell wireless network is reserved for the first duration.
  • the conflict resolution identifier carried in the second response message is used to determine whether the conflict is successfully resolved.
  • multiple terminals may send the same first request message to the base station, but the base station can only detect one, and the base station carries the detected first request message in the second response message. Part of the information, only one of the plurality of terminals determines that the second response message belongs to itself, and the above process is a conflict resolution process.
  • the second response message carries at least one of: a conflict resolution identifier; a high layer acknowledgement information (acknowledgment or non-acknowledgement) for the uplink data; an uplink data failure indication; an uplink data retransmission indication; And user business data.
  • the first request message further carries one or a combination of the following: whether the indication information of the S1 interface needs to be preferentially established; whether the indication information of the high layer acknowledgement information of the uplink data needs to be received; and the mobility for registering the terminal is used for identifying The terminal identification information of the management entity; the access layer security information; and the connection establishment reason corresponding to the data transmission.
  • the terminal after receiving the second response message returned by the base station and obtaining the cell radio network temporary identifier, the terminal further includes: searching, by the terminal, in the public search space, or transmitting the second response message scheduling information.
  • the space uses the cell radio network temporary identifier to detect one of the following: a physical downlink control channel, uplink scheduling information, and downlink scheduling information.
  • the physical downlink control channel may also carry uplink scheduling information or downlink scheduling information.
  • the terminal after receiving the second response message returned by the base station, the terminal further includes: if the terminal still has uplink data to be transmitted, the terminal sends the first request message carrying the uplink data to the The base station.
  • the terminal Before the terminal sends the random access prefix to the base station, the terminal also selects a random access prefix or selects a resource for sending a random access prefix.
  • the sending, by the terminal, 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 the uplink data transmission resource to the base station. .
  • the terminal sends a random access prefix for requesting an uplink data transmission resource to the base station, and the terminal selects a random access prefix in the random access prefix set for requesting the uplink data transmission resource, and the selected one is selected.
  • the random access prefix is sent to the base station; or the terminal selects a random access resource in the random access resource set for requesting the uplink data transmission resource, and uses the selected random access resource to randomly access A prefix is sent to the base station.
  • the terminal meets the first preset condition, including one or a combination of the following: the uplink data to be sent by the terminal is greater than the carrying data decision threshold; and the wireless link condition of the terminal meets the link condition threshold.
  • the service type of the uplink data to be sent by the terminal belongs to a preset service type.
  • the method further includes: acquiring, by the terminal, one of the following or a combination thereof from a system message sent by the base station: a carrying data decision threshold; a link condition threshold; and a preset service type information, where
  • the carrying data decision threshold includes: a carrying data threshold configured for all coverage levels, or a carrying data decision threshold configured for each coverage level.
  • the method further includes: the terminal not receiving the second response message returned by the base station; the second response message returned by the terminal base station received by the terminal, and The second response message carries an uplink data failure indication or an uplink data retransmission indication; and when the terminal does not receive the random access response returned by the base station, the current random access fails, and the terminal re-initiates random access .
  • the re-initiating the random access by the terminal includes: determining, by the terminal, the random access prefix for requesting the uplink data transmission resource to perform random access, or selecting the non-request for the request according to at least one of the following:
  • the random access prefix of the uplink data transmission resource performs random access: the number of failures of random access; the sequence number of failures of random access; the downlink measurement value obtained by the terminal; the coverage level; the number of repetitions.
  • the number of repetitions is the configuration information obtained by the terminal. Downstream measurements such as reference signal received power values, of course, may be other values.
  • the terminal re-initiates random access in one of the following ways:
  • the terminal In the current coverage level, when the number of failures of the random access prefix for requesting the uplink data transmission resource to perform the random access failure reaches the corresponding failure number threshold, the terminal replaces the coverage level to the maximum coverage level.
  • the method for sending a random access prefix for random access may be performed according to a sending manner in the related art.
  • the terminal sends a non-request for uplink data transmission when the number of failures of the random access prefix for requesting the uplink data transmission resource to perform the random access failure reaches the corresponding failure number threshold at the current coverage level.
  • the random access prefix of the resource or the random access prefix is sent to perform random access; if the failure still fails and the number of failures reaches the corresponding failure number threshold, the terminal changes to the next coverage level greater than the current coverage level, according to the previous
  • the same random access mode under the coverage level performs random access at the coverage level until the random access succeeds, or the terminal reaches the maximum coverage level, according to the same random access mode as the previous coverage level at the maximum coverage level. Random access is performed.
  • the method for sending a random access prefix for random access may be performed according to a sending manner in the related art.
  • the terminal when the terminal carries the uplink data to perform the random access failure failure number in the first request message, the terminal replaces the coverage level to the maximum coverage level, and then sends and carries the carrier.
  • the first request message of the RRC message is randomly accessed.
  • the terminal sends a first request message carrying a radio resource control message when the number of failures of the first request message carrying the uplink data to the random access failure reaches the corresponding failure number threshold.
  • Perform random access if it still fails and the number of failures reaches the corresponding failure number threshold, the terminal changes to the next coverage level greater than the current coverage level, and the coverage is in the same random access mode as the previous coverage level.
  • the level is randomly accessed until the random access succeeds, or the terminal reaches the maximum coverage level, and random access is performed at the maximum coverage level according to the same random access method as the previous coverage level.
  • the terminal When the number of failures of the random access prefix for requesting the uplink data transmission resource to perform the random access failure reaches the corresponding failure number threshold, the terminal sends a random access prefix that is not used for requesting the uplink data transmission resource to perform random connection. In.
  • the terminal sends a random access prefix that is not used for requesting the uplink data transmission resource to perform random access; the terminal arrives at the failure number of the random access prefix for requesting the uplink data transmission resource to perform random access failure.
  • the failure number threshold and when the reference signal received by the terminal receives the power value in the second predefined range, the terminal changes to the next coverage level, and sends a random access prefix for requesting the uplink data transmission resource for random access.
  • the terminal After transmitting the random access prefix for requesting the uplink data transmission resource to perform random access failure, the terminal sends a random access prefix that is not used for requesting the uplink data transmission resource, and the terminal is not used in the sending After the random access prefix of the uplink data transmission resource is requested to perform the random access failure, the random access prefix for requesting the uplink data transmission resource is randomly used for random access; the previous mode is repeated, and the number of failed access times reaches the corresponding failure number.
  • the terminal changes 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 succeeds, or the terminal reaches the maximum coverage level. Random access is performed at the maximum coverage level according to the same random access method as the previous coverage level.
  • the method further includes: receiving, by the terminal, a system message broadcasted by the base station or a dedicated message sent by the base station to the terminal, to obtain a threshold number of failures corresponding to each coverage level.
  • the method before the terminal re-initiates the random access, the method further includes: the terminal acquiring operation indication information from the base station, and determining, according to the operation indication information, a manner of re-initiating random access.
  • the method before the terminal performs one of the following operations, the method further includes: the terminal acquiring operation indication information from the base station, and determining, according to the operation indication information, that the first request for carrying the uplink data is sent The operation after the message fails to perform random access.
  • the first request message when the terminal is in a connected state before sending the random access prefix, the first request message further carries one or a combination of the following: a cell radio network temporary identifier, a radio resource control message, and Request a release indication.
  • the method when the terminal is in the connected state before sending the random access prefix, the method further includes: the terminal receiving the second response message returned by the base station, and after determining that the conflict resolution is successful, the terminal is autonomous. Release the RRC connection and transfer to the idle state; or, the terminal receives the second response message returned by the base station, and after determining that the conflict resolution is successful, the terminal processes the wireless carried in the second response message The resource control releases the message and moves to the idle state.
  • the sending, by the terminal, the first request message carrying the uplink data to the base station includes: the terminal acquiring the indication information carried in the random access response, when the second preset condition is met, The terminal sends a first request message carrying the uplink data to the base station.
  • the method further includes: the terminal acquiring the indication information carried in the random access response, and when the third preset condition is met, the terminal sends the first request that carries the radio resource control message. A message to the base station.
  • the second predetermined condition is that the indication information is the data amount information of the uplink authorization, the data quantity information of the uplink authorization is greater than the uplink authorization threshold, or the indication information indicates the terminal When the first request message is sent, the uplink data is directly sent;
  • the third preset condition is that the indication information is the data quantity information of the uplink authorization; or the data quantity information of the uplink authorization is less than or equal to the uplink authorization threshold; or The indication information indicates that the terminal carries a radio resource control message when sending the first request message.
  • the uplink authorization threshold is an uplink authorization threshold corresponding to a state before the terminal sends the random access prefix, or is a state before the terminal sends the random access prefix. And the uplink authorization threshold corresponding to the coverage level.
  • the uplink authorization threshold corresponding to the connected terminal is greater than the uplink authorization threshold corresponding to the idle terminal.
  • the method further includes: after receiving the second response message returned by the base station, the terminal establishes a radio resource control connection according to the radio resource control response message carried in the second response message, or The radio resource control connection is restored, or the radio resource control connection is re-established, and the terminal moves to the connected state.
  • An embodiment of the present application provides a data transmission method, as shown in FIG. 4, including steps 401 to 404.
  • step 401 the base station receives the random access prefix sent by the terminal, and sends a random access response to the terminal.
  • step 402 the base station receives a first request message that is sent by the terminal and carries uplink data.
  • the base station after receiving the first request message that is sent by the terminal and carrying the uplink data, the base station further includes: the base station sending a second response message to the terminal, where the second response message carries the following One or a combination of the information: a conflict resolution identifier, a high layer acknowledgement information for the uplink data, an uplink data transmission failure indication, an uplink data retransmission indication, and user service data.
  • the first request message further carries one or a combination of the following: preferentially establishing indication information of the S1 interface, and receiving indication information of the high layer acknowledgement information of the uplink data, the terminal identification information, Information for identifying a mobility management entity registered by the terminal, access layer security information, and a connection establishment reason corresponding to the data transmission.
  • the method further includes step 403 and step 404.
  • step 403 when the first request message carries the indication information of the S1 interface, the base station sends the first S1 interface message carrying the uplink data to the network side.
  • step 404 the base station receives the second S1 interface message returned by the network side, obtains high layer acknowledgement information from the second S1 interface message, and sends the high layer acknowledgement information to the terminal.
  • 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.
  • the method further includes: the base station sending operation indication information to the terminal by using a system message or a dedicated message, where the operation indication information is used to indicate that the terminal re-rans random access after random access failure The way.
  • the method for re-performing random access includes one of the following: preferentially replacing the coverage level to perform random access again; preferentially transmitting a random access prefix that is not used for requesting uplink data transmission resources or transmitting a random access prefix to perform random access again And re-performing random access by first transmitting the first request message carrying the radio resource control message.
  • the method for sending a random access prefix for random access may be performed according to a sending manner in the related art.
  • the base station when the terminal is in a connected state, and the first request message further carries a radio resource control message, the base station, after receiving the first request message that is sent by the terminal and carrying the uplink data, further includes: The base station sends a second response message to the terminal, where the second response message carries a radio resource control re-establishment message.
  • the base station after receiving the first request message that is sent by the terminal and carrying the uplink data, further includes: The base station sends a second response message to the terminal, where the second response message carries a radio resource control release message.
  • the method further includes: sending, by the base station, a carrying data decision threshold to the terminal by using a system message or a dedicated message.
  • the carrying data determining threshold is used by the terminal for determining, in a random access prefix set for requesting an uplink data transmission resource, or selecting to send in a random access prefix set not used for requesting an uplink data transmission resource.
  • a random access prefix to the base station; or the carrying data determination threshold is used by the terminal to determine in a random access resource set for requesting an uplink data transmission resource, or not to request an uplink data transmission resource
  • a random access prefix is selected from the set of random access resources to be sent to the base station.
  • the carrying data decision threshold includes: a carrying data threshold configured for all coverage levels, or a carrying data decision threshold configured for each coverage level.
  • the random access response carries indication information, where the indication information indicates a manner in which the terminal sends a first request message, and the base station receives a first request that is sent by the terminal to carry uplink data.
  • the message includes: when the second preset condition is met, the base station receives the first request message that is sent by the terminal and carries the uplink data; when the third preset condition is met, the base station receives the carried wireless The first request message of the resource control message.
  • the second predetermined condition is that the indication information is the data amount information of the uplink authorization, the data quantity information of the uplink authorization is greater than the uplink authorization threshold, or the indication information indicates the terminal
  • the uplink data is directly sent when the first request message is sent.
  • the third preset condition is that the indication information is the data quantity information of the uplink authorization, the data quantity information of the uplink authorization is less than or equal to the uplink authorization threshold, or the indication information indicates that the terminal is sending the first request.
  • the message carries a radio resource control message.
  • the uplink authorization threshold is: an uplink authorization threshold corresponding to a state of the terminal before sending the random access prefix; or the uplink authorization threshold is: the terminal is sending the random The status before the prefix is accessed and the uplink authorization threshold corresponding to the coverage level. That is, the same uplink authorization threshold can be configured for multiple coverage levels, or different uplink authorization thresholds can be configured for multiple coverage levels.
  • the uplink authorization threshold corresponding to the connected terminal is greater than the uplink authorization threshold corresponding to the idle terminal.
  • the base station when the terminal is in an idle state, further includes: the base station sending a second response message to the terminal, where The second response message carries a radio resource control response message.
  • An embodiment of the present application provides a data transmission method, including: when a terminal is in an idle state, in a random access procedure, sending a first request message to a base station, and receiving a second response message sent by the base station, from the The second response message acquires downlink data.
  • An embodiment of the present application provides a data transmission method, including: in a process in which a terminal is in an idle state for performing random access, the base station receives a first request message sent by the terminal, and if the base station has downlink data that needs to be sent to the terminal, The base station carries the downlink data when sending the second response message to the terminal.
  • the base station buffers the downlink data when receiving the downlink data that is sent by the network side and needs to be sent to the terminal.
  • An embodiment of the present application provides a data transmission method, including: in a process in which a terminal is in an idle state for performing random access, after receiving a first S1 interface message sent by a base station, the network side sends a second S1 interface to the base station.
  • the message that the second S1 interface message carries downlink data that needs to be sent to the terminal.
  • the method further includes: before the terminal is in an idle state to initiate random access, the network side receives downlink data that is sent by the application layer and needs to be sent to the terminal, and buffers the downlink data.
  • An embodiment of the present invention provides a data transmission method, including: when a terminal is in a connected state, the terminal receives a physical downlink control channel command sent by a base station, and obtains, by using the physical downlink control channel command, the base station to allocate the a non-contention resource of the terminal, using a random access prefix corresponding to the non-competitive resource to initiate a random access; the terminal receiving a random access response sent by the base station, and carrying the downlink in the random access response When the indication information of the data, the terminal receives the downlink data.
  • An embodiment of the present application provides a data transmission method, including: when a terminal is in a connected state, a base station sends a physical downlink control channel command to the terminal, where the physical downlink control channel command carries the base station and is allocated to the terminal 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, where the random access response carries At the same time, the indication information of the downlink data is sent, and the downlink data is delivered at the same time.
  • Embodiment 1 Base flow of idle uplink data, control plane scheme
  • This embodiment provides an idle state uplink data transmission scheme with no state transition.
  • the UE When the UE is in the RRC_IDLE state, the UE sends a random access prefix for requesting the resource for transmitting the uplink data. After receiving the random access response sent by the base station and obtaining the uplink authorization, the UE simultaneously sends the uplink data to the base station when sending the first request message. After the UE receives the second response message sent by the base station and determines that the conflict resolution is successful, the UE considers that the uplink data transmission is successful, and the UE maintains the RRC_IDLE state.
  • the UE may consider the Temporary Media Access Control (MAC) layer identifier Temporal-Radio Network Tempory Identity (T-RNTI) assigned by the base station as the formal MAC layer identifier cell radio network temporary identifier.
  • the C-RNTI is reserved for the first time in the RRC_IDLE state.
  • the first duration may be preset or may be configured by the network side for the UE.
  • the UE is in the RRC_IDLE state, and uses a Control Plane (CP) scheme, as shown in FIG. 5, including steps 501 to 507.
  • CP Control Plane
  • step 501 when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the uplink data resource, that is, requesting the uplink data transmission resource.
  • step 502 the base station sends a random access response to the UE.
  • the random access response carries a temporary MAC layer identifier T-RNTI allocated by the base station to the UE.
  • step 503 after receiving the random access response and obtaining the uplink grant, the UE simultaneously sends the uplink data to the base station when sending the first request message (Msg3).
  • Msg3 may carry only the identifier including the core network identifier (for example, referred to as a data destination address identifier) and uplink data, and does not carry an RRC message.
  • the related art is different in the related art, in which Msg3 needs to carry an RRC message, such as an RRC connection setup request message, an RRC connection recovery request message, or a new RRC connection public request message, for triggering establishment or restoration of an RRC connection. In the example, no RRC message is carried.
  • the UE should carry the identifier allocated by the core network to the UE, such as the S-TMSI, or can identify the UE, while transmitting the uplink data packet through the Msg3.
  • the information of the attached Mobility Management Entity (MME) is given to the base station, for example, a data destination address identifier or a Globally Unique Mobility Management Entity Identifier (GUMMEI).
  • the UE may also carry the access layer security information to the base station, such as ul-NAS-MAC, ul-NAS-Count, while the access layer security information may be based on the non-access layer (Non Access Stratum, NAS) layer security information obtained.
  • Msg3 can also carry the connection establishment cause, for example, the connection establishment reason for transmitting the uplink data.
  • RLC Radio Link Control
  • HARQ Hybrid Automatic Repeat Request
  • step 504 the base station sends a first SI interface message carrying the uplink data to the network side.
  • the first S1 interface message is a Data Transmission Req.
  • the first S1 interface message may also be an initial user equipment information (INITIAL UE MESSAGE) message; or a user equipment context recovery request (UE CONTEXT RESUME REQUEST) message; or, uplink non-access A layer transfer (UPLINK NAS TRANSPORT) message; or a 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, a Mobility Management Entity (MME) attached to the UE.
  • MME Mobility Management Entity
  • the base station may also send the access layer security information to the MME at the same time.
  • step 505 the network side sends a second S1 interface message to the base station.
  • the second S1 interface message is a Data Transmission Ack.
  • the second S1 interface message may also be a Connection Establishment Indication message; or a UE CONTEXT RESUME RESPONSE message; or a downlink non-access layer transmission (DOWNLINK NAS TRANSPORT) A message; or a PATH SWITCH REQUEST ACKNOWLEDGE message; or the second S1 interface message may be another newly defined S1 interface message.
  • the second S1 interface message carries high layer acknowledgement information (acknowledgment/non-acknowledgement) for the uplink data, and may also include downlink access layer security information.
  • high layer acknowledgement information acknowledgement/non-acknowledgement
  • the base station transmits a second response message (Msg4) to the terminal.
  • the second response message carries a contention resolution ID, such as carried by the MAC layer control unit.
  • the second response message (Msg4) may only carry the conflict resolution identifier and does not carry the RRC message.
  • the second response message carries Ack/Nack for UL data or an uplink data retransmission indication (DataResendIND).
  • step 507 after receiving the second response message sent by the base station and determining that the conflict resolution is successful according to the conflict resolution ID, the UE considers that the uplink data transmission is successful and remains in the RRC_IDLE state.
  • the base station first sends a second response message to the terminal, and then sends the 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 related technologies.
  • the first S1 interface message may be sent before the second response message according to the indication of the UE, and the S1 interface for the UE and the UE context establishment are not triggered.
  • the Msg4 needs to carry an RRC message, such as an RRC connection setup message, an RRC connection recovery message, or a new RRC connection public response message, to complete the RRC setup or RRC recovery process.
  • the Msg4 may not need to carry the RRC message. .
  • the UE and the base station need to use an extended collision resolution timer.
  • the extended conflict resolution timer may be statically configured, or the base station broadcasts a plurality of collision resolution timer durations in the system message, and the UE and the base station select one of the uses according to the corresponding indication.
  • the UE may consider the temporary MAC layer identifier T-RNTI allocated by the base station in step 502 as the formal MAC layer identifier C-RNTI.
  • the C-RNTI is also reserved for a period of time. The specific retention time may be preset or may be configured by the network side for the UE. During this time, the UE always randomly accesses the RAR's Calling Search Space (CSS), or demodulates the physical channel with C-RNTI in a newly defined CSS search space dedicated to Msg3 data transmission. .
  • SCS Calling Search Space
  • the UE if the UE receives the second response message of 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 fails, and the UE re-initiates the random access procedure to transmit. data.
  • the base station may include an uplink data transmission failure indication, or uplink, in the second response message sent to the UE. Data retransmission indication.
  • the collision resolution is determined according to the conflict resolution ID, and the temporary MAC layer identifier T-RNTI allocated by the UE base station is regarded as the formal MAC layer identifier C-RNTI, but
  • the second response message includes an uplink data transmission failure indication or an uplink data retransmission indication, and the UE needs to re-initiate the random access procedure to transmit data, and the Msg3 carries the C-RNTI.
  • Embodiment 2 Base flow of idle uplink data, user plane scheme
  • the UE is in the RRC_IDLE state.
  • this embodiment adopts a User Plane (UP) scheme, as shown in FIG. 6, and includes steps 601 to 607.
  • UP User Plane
  • step 601 when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the resource of the uplink data.
  • step 602 the UE receives the random access response sent by the base station and obtains an uplink grant.
  • step 603 when the UE sends the first request message (Msg3), the uplink data is simultaneously sent to the base station.
  • the UE adopts the UP scheme, and the UE performs the suspend operation when the RRC connection is released.
  • the UE has the stored UE context and the recovery identifier (ResumeID).
  • the UE carries the restoration identifier while transmitting the uplink data through the Msg3.
  • Msg3 may carry only the identifier including the core network identifier (for example, called data destination address identifier, or GUMMEI information) and uplink data, and does not carry the RRC message.
  • the Msg3 needs to carry an RRC message, such as an RRC connection setup request message, an RRC connection recovery request message, or a new RRC connection public request message, for triggering establishment or restoration of the RRC connection. , does not carry RRC messages.
  • the UE may also carry the access layer security information to the base station while transmitting the uplink data packet, and the access layer security information may be obtained according to the NAS layer security information.
  • the UE may also carry a connection establishment cause, such as a connection establishment cause indicating transmission of uplink data.
  • step 604 the base station sends a first SI interface message carrying uplink data to the network side.
  • the first S1 interface message is a Data Transmission Req.
  • the network side is, for example, a Mobility Management Entity (MME) attached to the UE.
  • MME Mobility Management Entity
  • the base station may also send the access layer security information to the MME at the same time.
  • the base station searches for the UE context stored on the base station side according to the recovery identifier, and sends a first S1 interface message to the MME according to the MME information attached to the UE included in the UE context.
  • step 605 the network side sends a second S1 interface message to the base station.
  • the second S1 interface message is a data transmission acknowledgement (Data Transmission Ack), carries high-level acknowledgement information (confirmed/non-confirmed) to the uplink data, and may also include downlink access layer security information.
  • Data Transmission Ack data transmission acknowledgement
  • high-level acknowledgement information confirmeded/non-confirmed
  • step 606 the base station sends a second response message (Msg4) to the terminal.
  • the second response message carries the conflict resolution identifier, such as carried by the MAC layer control unit.
  • the second response message (Msg4) may only carry the conflict resolution identifier and does not carry the RRC message.
  • step 607 after receiving the second response message sent by the base station and determining that the conflict resolution is successful according to the conflict resolution ID, the UE considers that the uplink data transmission is successful and maintains the RRC_IDLE state.
  • Embodiment 3 continuous transmission of idle state data
  • the UE may not be able to transmit all the data to be transmitted in the initial random access process, and the UE may continue to send the first request message carrying the uplink data to the base station in the RRC_IDLE state and the C-RNTI state, and the base station sends the second response message. Give the UE with the confirmation of the uplink data. This process can be exchanged several times until the data transfer to be transmitted is completed.
  • steps 701 to 712 are included.
  • Steps 701-707 are the same as steps 501-507; wherein step 703 can also carry a buffer status report indicating that there is still data to be sent.
  • step 708 the base station allocates a new uplink grant to the terminal by using a Physical Downlink Control Channel (PDCCH) transmission, and the PDCCH transmission uses the cell radio network temporary identifier to scramble.
  • PDCCH Physical Downlink Control Channel
  • 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.
  • step 710 the base station sends a first SI interface message carrying uplink data to the network side.
  • step 711 the network side sends a second S1 interface message to the base station.
  • step 712 if the second S1 interface message includes an acknowledgement of the uplink data, the base station sends an acknowledgement of the uplink data to the terminal.
  • the steps 708-712 can be repeated several times until all the data transmissions to be transmitted by the terminal are completed.
  • Embodiment 4 Downstream cache data is sent in Msg4, CP scheme and UP scheme are unified
  • NB-IoT Narrow Band Internet of Things
  • eMTC Internet of Things
  • the network side can buffer the downlink data for a period of time and send it to the UE. During this period, if the network side receives the first S1 interface message, the second S1 interface message can be sent.
  • the downlink data buffered by the central office is sent to the base station.
  • the base station may include downlink data in the second response message and send the data to the UE, where the downlink data may be included in the newly defined media access control control.
  • the base station may include downlink data in the second response message and send the data to the UE, where the downlink data may be included in the newly defined media access control control.
  • the base station may include downlink data in the second response message and send the data to the UE, where the downlink data may be included in the newly defined media access control control.
  • MAC CE Media Access Control Control Element
  • IE Data Container Information Element
  • the downlink data flow is transmitted for the random access procedure, and includes steps 801 to 808.
  • step 801 when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the resource of the uplink data.
  • step 802 the UE receives the random access response sent by the base station and obtains an uplink grant.
  • step 803 the UE simultaneously transmits uplink data to the base station when transmitting the first request message (Msg3).
  • the UE should carry the identifier allocated by the core network to the UE, such as the S-TMSI, or can identify the UE, while transmitting the uplink data packet through the Msg3.
  • the information of the attached MME is sent to the base station, for example, as a data destination address identifier, or a Globally Unique MME Identifier (GUMMEI).
  • GUMMEI Globally Unique MME Identifier
  • the UE may also carry the access layer security information to the base station while transmitting the uplink data packet, and the access layer security information may be obtained according to the NAS layer security information.
  • the UE performs a suspend operation on the last RRC connection release, and has a stored UE context and a recovery identifier, and the UE carries the resume identifier while transmitting uplink data through the Msg3.
  • step 804 the base station checks if there is downlink data that needs to be sent to the terminal, and if so, includes it in the second response message.
  • step 805 the base station sends a first SI interface message carrying the uplink data to the network side.
  • the first S1 interface message is a Data Transmission Req.
  • the network side is, for example, a Mobility Management Entity (MME) attached to the UE.
  • MME Mobility Management Entity
  • the base station may also send the access layer security information to the MME at the same time.
  • step 806 the network side checks if there is downlink data that needs to be sent to the terminal, and if so, it is included in the second S1 interface message.
  • step 807 the network side sends a second S1 interface message carrying downlink data to the base station.
  • the second S1 interface message is a Data Transmission Ack.
  • the second S1 interface message may also carry high-level acknowledgement information (confirmation/non-confirmation) on the uplink data, and may also include downlink access layer security information.
  • step 808 the base station sends a second response message (Msg4) carrying the downlink data to the terminal.
  • Msg4 a second response message
  • Embodiment 5 (downstream data buffer)
  • the network side can buffer the downlink data for a period of time. Trigger the sending of the S1 interface paging message.
  • the network side sends the data to the base station.
  • the terminal may be in an idle state, and the base station may buffer the downlink data for a period of time without triggering an air interface paging message.
  • FIG. 9 it is a downlink data buffering flowchart, which includes steps 901 to 904.
  • step 901 the application layer has downlink data sent to the network side.
  • the network side determines that the user is in the idle state of the S1 interface, and the downlink data is tolerable by the delay.
  • the network side can buffer the downlink data for a period of time without triggering the S1 interface paging message transmission.
  • the cache duration can be a preset value.
  • 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.
  • the base station determines that the terminal is in an idle state, and the downlink data is tolerable, and the base station may buffer the downlink data for a period of time without triggering the air interface paging message transmission.
  • the cache duration can be a preset value.
  • FIG. 10 is another implementation manner of Embodiment 1 or Embodiment 2. This embodiment includes steps 1001 to 1009.
  • step 1001 when the UE is in the RRC_IDLE state, the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the resource of the uplink data.
  • step 1002 the UE receives the random access response sent by the base station and obtains an uplink grant.
  • step 1003 when the UE sends the first request message (Msg3), the uplink data is simultaneously sent to the base station.
  • the Msg3 may carry a terminal identifier, such as an S-TMSI or a recovery identifier, or may carry an identifier (for example, a GUMMEI information or a data destination address identifier) including the core network registered by the terminal, and uplink data, and does not carry an RRC message.
  • a terminal identifier such as an S-TMSI or a recovery identifier
  • an identifier for example, a GUMMEI information or a data destination address identifier
  • the UE may also carry the access layer security information to the base station while transmitting the uplink data packet, and the access layer security information may be obtained according to the NAS layer security information.
  • the UE can also carry the connection establishment cause.
  • step 1004 the base station sends a second response message (Msg4) to the terminal.
  • the second response message carries the conflict resolution identifier, such as carried by the MAC layer control unit.
  • the second response message may only carry the conflict resolution identifier and does not carry the RRC message.
  • step 1005 after receiving the second response message sent by the base station and determining that the conflict resolution is successful according to the conflict resolution ID, the UE maintains the RRC_IDLE state, and uses the temporary wireless network temporary identifier allocated by the base station as the temporary identifier of the cell wireless network. And saving the cell wireless network temporary identifier for the first duration.
  • step 1006 the base station sends a first SI interface message carrying uplink data to the network side.
  • the first S1 interface message is a Data Transmission Req.
  • step 1007 the network side sends a second S1 interface message to the base station.
  • the second S1 interface message is a data transmission acknowledgement (Data Transmission Ack), and carries a high layer acknowledgement information (confirmation/non-confirmation) on the uplink data.
  • Data Transmission Ack data transmission acknowledgement
  • high layer acknowledgement information confirmation/non-confirmation
  • step 1008 the base station transmits downlink assignment information to the terminal through the PDCCH transmission, and the PDCCH transmission uses the cell radio network temporary identifier to scramble.
  • the terminal uses the cell radio network temporary identifier to demodulate the PDCCH transmission, acquires downlink assignment information, and uses the downlink assignment information to receive downlink data sent by the base station to the terminal, where the downlink data may be high layer acknowledgement information of the uplink data.
  • Embodiment 6 The terminal determines the transmission mode of the Msg3 according to the information in the RAR (with data or with RRC message, the CP solution is combined with the UP solution)
  • the UE When the UE is in the RRC_IDLE state, the UE sends a random access prefix in the random access procedure for requesting the resource for transmitting the 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.
  • the base station carries an indication in the random access response, which is used to indicate the manner in which the first request message is sent.
  • the indication may be an implicit indication, such as data amount information included in the uplink grant, for example, may be a transport block size (TB size) in an uplink grant (UL grant) field in the RAR message.
  • the indication such as the data volume information of the uplink authorization
  • the UE directly sends the uplink data to the base station when sending the first request message.
  • the UE encapsulates the uplink data according to the data volume information of the uplink grant and sends the uplink data to the base station. If the data to be sent of the UE exceeds the data amount of the uplink grant, the UE may use the data amount information of the uplink grant.
  • the data to be sent is split into multiple segments and sent in sequence. If the indication (such as the uplink authorized data volume information) 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, where the RRC message may be an RRC connection setup request, and the RRC connection is The recovery request message, or the RRC connection public request message.
  • the indication such as the uplink authorized data volume information
  • the UE sends a first request message to the base station, and the first request message carries an RRC message, where the RRC message may be an RRC connection setup request, and the RRC connection is The recovery request message, or the RRC connection public request message.
  • the indication may also be an explicit indication that the UE directly sends the uplink data when sending the first request message, or instructs the UE to initiate a normal RRC connection establishment or RRC recovery procedure.
  • the uplink authorization threshold may be a preset value of the static configuration, or may be configured by the base station, for example, by using a newly defined field in the system message, and may be dynamically adjusted.
  • the uplink authorization threshold is set to 200 bits.
  • the uplink grant threshold may be configured separately for each coverage level.
  • the base station may allocate a suitable uplink grant to the terminal according to the terminal request in the random access response, and carry another indication information.
  • the indication information indicates that if the UE fails to send the uplink data directly when sending the first request message, the UE should use the random access prefix or the random access resource that sends the uplink data unsolicited when the random access is initiated again. That is, the UE should initiate random access for a normal RRC connection setup or RRC recovery procedure.
  • 11 is an implementation of directly transmitting uplink data to a base station when a UE sends a first request message. As shown in FIG. 11, the UE is in an RRC_IDLE state, and includes steps 1100 to 1106.
  • step 1100 the base station sends an uplink authorization threshold T_ULgrant through the system message.
  • step 1101 the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the resource of the uplink data.
  • step 1102 the base station sends a random access response to the UE, carrying a large uplink grant.
  • step 1103 the UE determines that the data amount information included in the uplink grant is greater than the uplink grant threshold, and when the UE sends the first request message (Msg3), the uplink data is simultaneously sent to the base station.
  • Msg3 the first request message
  • the UE performs a suspend operation on the last RRC connection release, and has a stored UE context and a recovery identifier.
  • the UE carries the restoration identifier while transmitting the uplink data through the Msg3.
  • the UE should carry the identifier of the core network to the UE, such as the S-TMSI, or the information of the MME to which the UE is attached, such as the GUMMEI information, to the base station while transmitting the uplink data packet through the Msg3.
  • step 1104 the base station sends a first SI interface message carrying the uplink data to the network side.
  • step 1105 the network side sends a second S1 interface message to the base station.
  • step 1106 the base station sends a second response message (Msg4) to the terminal.
  • the UE sends the first request message to the base station, and the first request message carries the RRC message, and the UE receives the RRC message.
  • the RRC connection should be established or restored, and transferred to the RRC_CONNECTED state, as shown in FIG. 12, including steps 1200 to 1208.
  • step 1200 the base station sends an uplink authorization threshold T_ULgrant through the system message.
  • step 1201 the UE sends a random access prefix to the base station in the random access procedure for requesting the resource for transmitting the uplink data.
  • the base station sends a random access response to the UE, and carries a smaller uplink grant data amount information (without exceeding an uplink grant threshold).
  • the UE determines that the data volume information of the uplink grant is less than or equal to the uplink grant threshold, and the UE sends a first request message (Msg3) to the base station, and carries an RRC connection public request message; the public request message may be an existing RRC connection request.
  • the Msg3 message also carries the identifier that the core network allocates to the UE, for example, the S-TMSI, or the information that can identify the MME to which the UE is attached to the base station; or carries the recovery identifier.
  • step 1204 the base station sends a first SI interface message to the network side.
  • step 1205 the network side sends a second S1 interface message to the base station.
  • the base station sends a second response message (Msg4) to the terminal, carrying an RRC connection public response message.
  • the public response message may be an existing RRC Connection Setup message, an RRC Connection Recovery message, or a newly defined RRC Connection Public Response message.
  • step 1207 the UE establishes an RRC connection and enters an RRC_CONNECTED state.
  • step 1208 the UE sends an Msg5 message to the base station, carrying the uplink data.
  • Embodiment 7 After sending Msg3+ data, the terminal can process the Msg4+RRC message
  • the base station may actively send an RRC initiated RRC connection setup or recovery procedure, and the terminal is transferred to the RRC_CONNECTED state, that is, the base station sends the RRC message carrying the first
  • the second response message is sent to the UE, and the RRC message may be an RRC connection setup, an RRC connection recovery, or an RRC connection public response message.
  • the RRC connection should be established or restored and transferred to the RRC_CONNECTED state.
  • the UE usually needs to send an RRC request message to receive an RRC response message
  • the RRC request message may be an RRC connection setup request message, an RRC connection recovery request message, or a new RRC connection public request message, the RRC response message. It may be an RRC Connection Setup message, an RRC Connection Recovery message, or a new RRC Connection Public Reply message.
  • the RRC response message may be processed even if the UE does not send the RRC request message.
  • step 1300 to step 1308 are included.
  • step 1300 the base station sends an uplink authorization threshold T_ULgrant through the system message.
  • step 1301 the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the uplink data resource.
  • step 1302 the base station sends a random access response to the UE.
  • step 1003 when the UE sends the first request message (Msg3), the uplink data is simultaneously sent to the base station.
  • the UE should carry the identifier of the core network to the UE, such as the S-TMSI, or the information that can identify the MME to which the UE is attached to the base station, or carry the recovery identifier, while transmitting the uplink data packet through the Msg3.
  • the identifier of the core network such as the S-TMSI, or the information that can identify the MME to which the UE is attached to the base station, or carry the recovery identifier, while transmitting the uplink data packet through the Msg3.
  • step 1304 the base station sends a first SI interface message carrying uplink data to the network side.
  • step 1305 the network side sends a second S1 interface message to the base station.
  • the base station sends a second response message (Msg4) to the base station, carrying an RRC connection public response message.
  • the public response message may be an existing RRC Connection Setup message, an RRC Connection Recovery message, or a newly defined RRC Connection Public Response message.
  • step 1307 the UE establishes an RRC connection and enters an RRC_CONNECTED state.
  • step 1308 the UE sends an Msg5 message to the base station.
  • the UE Under a certain coverage level, if the UE attempts to transmit the uplink data (the first format Msg3) a certain number of times while transmitting the first request message, the UE preferentially replaces the coverage level. When the coverage level reaches the maximum, the UE then proceeds to attempt to send a first request message carrying an RRC message to establish or restore an RRC connection (second format Msg3). Or, under a certain coverage level, if the UE attempts to send the uplink data (the first format) while transmitting the first request message fails a certain number of times, the UE preferentially turns to the attempt to send the first request message carrying the RRC message to establish or The RRC connection is restored (the second format Msg3). If the UE still fails, the UE directly selects the next coverage level according to the configured number of failures. Under the new coverage level, the UE still performs random access attempts according to the above sequence. .
  • the base station can broadcast operational indication information in the system message. If the UE is instructed to preferentially replace the coverage level, the number of attempts of the UE to adopt the second format Msg3 at the maximum coverage level may be indicated, or whether the number of attempts is the same as the number of attempts to adopt the second format Msg3. If the UE is instructed to preferentially switch to another format Msg3, it may indicate the number of attempts for each format at the current coverage level, or indicate the proportion of each format attempt in the total number of attempts.
  • the UE may terminate or suspend the power boosting operation in advance each time random access is performed. For example, the UE first determines whether the Msg3 format used this time is the same as the previous one, and determines whether to terminate or suspend the power boosting operation in advance according to the judgment result.
  • An example of an adjustment power boost operation is as follows:
  • the power boosting process is terminated or suspended early.
  • the UE decides whether to terminate or suspend the power boosting operation in advance according to the reason for the failure of the last access attempt.
  • Another example of adjusting the power boost operation is as follows:
  • the UE After the UE attempts to adopt the first format Msg3, the UE decides whether to terminate or suspend the power boosting process in advance according to the reason for the failure. If a certain type of failure occurs (such as a conflict resolution failure), the UE does not increase the uplink transmit power, but merely tries again.
  • a certain type of failure such as a conflict resolution failure
  • the UE When the UE is in the RRC_IDLE state, the UE sends a random access prefix in the random access procedure for requesting the resource for transmitting the uplink data. After the UE obtains the uplink grant, the UE directly sends the uplink data to the base station when the first request message is sent in the random access process.
  • the UE When the UE sends the random access prefix selected in the random access prefix set P1 for requesting the uplink data transmission resource at the current coverage level, but fails to receive the second response message sent by the base station (the second response message should be If the large UL grant is included, so that the UE sends the uplink data and does not perform state transition while transmitting the first request message, or the collision resolution fails in the subsequent process, and the random access attempt fails, the UE needs to initiate the random again. During the access process, the UE needs to repeatedly send the random access prefix in P1. When the repeated transmission reaches a certain number of times N1, the number of times N1 is a preset value corresponding to the current coverage level or configured by the network side for the UE.
  • the UE starts to use the random access prefix in the random access prefix set P2 that is not used to request the uplink data transmission resource. If the random access prefix in P2 is sent, the second response message sent by the base station is not received (the second response message should include a smaller UL grant for the UE to send the first request message including the RRC message to establish The RRC connection is restored, or the collision resolution fails in the subsequent process, and the random access attempt fails.
  • the UE repeatedly sends the random access prefix in the P2. When the repeated transmission reaches a certain number of times N2, the The number of times N2 is a preset value corresponding to the current coverage level or configured by the network side for the UE, and the UE skips to the next coverage level, and repeats the above process again.
  • the terminal uses the random access prefix set P1 for random access, if the random access attempt fails because the random access response is not received, the UE marks the failure reason S1, if the conflict is resolved because the conflict is resolved in the subsequent process. If the random access attempt fails, the UE marks the failure reason S2.
  • the terminal may increase the uplink transmit power according to the configuration parameter. However, when the UE fails with the cause of S2, there may be multiple UEs that attempt to send uplink data while sending the first request message, and the system load is heavy. If the transmit power is still increased during retransmission, the system may be caused. The conflict is exacerbated, so at the next attempt, the UE does not increase the uplink transmit power, but merely tries again.
  • Embodiment 9 parallel uplink data transmission and RRC connection re-establishment process
  • the RRC re-establishment process may be triggered due to reasons such as RLF, and the UE needs to initiate a random access procedure.
  • the RRC is re-established, there may be uplink data to be transmitted or retransmitted.
  • the uplink data may be sent at the same time as the re-establishment, that is, the parallel uplink data transmission and the RRC connection re-establishment process are performed.
  • the UE is in the RRC_CONNECTED state, and uses the CP scheme to transmit the uplink data flow in the random access procedure, including step 1406 of step 1401.
  • step 1401 the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the resource of the uplink data.
  • step 1402 the base station sends a random access response to the UE.
  • the UE sends a first request message (Msg3) to the base station, and carries an RRC connection public request message and uplink data.
  • the RRC connection public request message may be an existing RRC connection re-establishment request message, or may be new.
  • the RRC connects to the public request message.
  • the Msg3 message further carries an identifier that is allocated by the core network to the UE, for example, S-TMSI, or information that can identify the MME to which the UE is attached to the base station; for example, in the GUMMEI step 1404, the base station sends a first SI interface message carrying the uplink data to the Network side.
  • S-TMSI an identifier that is allocated by the core network to the UE
  • information that can identify the MME to which the UE is attached to the base station for example, in the GUMMEI step 1404, the base station sends a first SI interface message carrying the uplink data to the Network side.
  • step 1405 the network side sends a second S1 interface message to the base station.
  • the base station sends a second response message (Msg4) to the terminal, carrying an RRC connection public response message.
  • the RRC connection public response message may be an existing RRC connection re-establishment message or a new RRC connection public response message.
  • step 1501 the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the resource of the uplink data.
  • step 1502 the base station sends a random access response to the UE.
  • the UE sends a first request message (Msg3) to the base station, and carries an RRC connection public request message and uplink data.
  • the RRC connection public request message may be an existing RRC connection re-establishment request message, or may be new.
  • the RRC connects to the public request message.
  • the Msg3 message also carries a re-establishment terminal identifier (Reestablish-UEID).
  • step 1504 the base station sends a first SI interface message carrying uplink data to the network side.
  • step 1505 the network side sends a second S1 interface message to the base station.
  • the base station sends a second response message (Msg4) to the terminal, carrying an RRC connection public response message.
  • the RRC connection public response message may be an existing RRC connection re-establishment message or a new RRC connection public response message.
  • Embodiment 10 (quick release after transmitting uplink data in the connected state)
  • the UE When the UE is in the RRC_CONNECTED state and there is data to be transmitted, and the UE is in an out-of-synchronization state or has no uplink resources, the UE needs to initiate a random access procedure.
  • the UE may be considered to complete the data transmission as soon as possible and may initiate the fast RRC.
  • the UE will simultaneously send uplink data to the base station when transmitting the first request message.
  • the UE may be considered to send a normal preamble, and then trigger a complete RRC connection establishment procedure. Transfer data after completion. .
  • the UE After the UE sends the first request message and the uplink data, if the second response message sent by the base station is received and it is determined that the conflict resolution is successful, the UE releases the RRC_IDLE state autonomously.
  • the base station After receiving the first request message and the uplink data, the base station may trigger the fast release, and the second response message sent by the base station to the UE carries the RRC release message, and the release message should be in the radio link control acknowledge mode (Radio Link Control Acknowledged Mode). , RLC AM) mode transmission.
  • RLC AM Radio Link Control Acknowledged Mode
  • the UE receives the second response message, first determines that the conflict resolution is successful, and then processes the RRC release message and sends an ACK (Acknowledgement) acknowledgement to the message, after which the base station sends an RRCConnectionRelease message to the terminal, and the terminal is released to the RRC_IDLE state. If the conflict resolution fails, the UE does not process the RRC message carried by the second response message.
  • the RRC release message in the related art can only be sent through SRB1. In this application, the RRC release message can be sent through SRB0.
  • the base station broadcasts different uplink grant thresholds for the idle state and the connected state through the system message, and the connection state should have a stricter uplink grant threshold, that is, the uplink grant threshold should ensure that when the UE initiates random access data in the connected state, All the data to be transmitted should be transmitted and the connection should be released as soon as possible.
  • the uplink authorization threshold of the connected state is greater than the upstream authorization threshold of the idle state.
  • step 1601 to step 1607 are included.
  • step 1601 the UE sends a random access prefix to the base station in the random access procedure, for requesting to send the uplink data resource.
  • step 1602 the base station transmits a random access response to the UE.
  • Msg3 first request message carrying the uplink data
  • the Msg3 message also carries the cell wireless network temporary identifier.
  • step 1604 the base station sends a first SI interface message carrying the uplink data to the network side.
  • step 1605 the network side sends a second S1 interface message to the base station.
  • step 1606 the base station sends a second response message (Msg4) to the terminal, carrying an RRC connection release message.
  • step 1607 the UE processes Msg4 first, then processes the connection release message, and then the UE releases to the RRC_IDLE state.
  • Embodiment 11 non-competitive access Msg2 carries downlink data
  • the base station 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 to the UE to trigger the random access procedure.
  • the PDCCH order includes a non-contention resource allocated by the base station to the UE.
  • the base station searches for the information of the UE, and the base station sends a random access response to the UE.
  • the random access response includes an indication that the downlink data is simultaneously sent to the UE, and the UE uses the received downlink grant to receive the downlink data, and then the UE may send the first request message to the base station, including the acknowledgement of the received downlink data.
  • the UE needs to preferentially process the Tracking Area (TA) information, complete the synchronization process, and then process the downlink data packet.
  • TA Tracking Area
  • the UE is in the RRC_CONNECTED state, and includes steps 1701 to 1706.
  • step 1700 the network side sends downlink data to the base station.
  • step 1701 the base station sends a PDCCH order to the UE, and carries the non-competitive resources allocated by the base station to the UE.
  • step 1702 the UE sends a random access prefix corresponding to the non-contention resource to the base station.
  • step 1703 the base station sends a random access response to the UE, and simultaneously delivers the downlink data, where the random access response carries indication information, indicating that downlink data is simultaneously delivered.
  • step 1704 after receiving the random access response, the UE sends the first request message (Msg3) to the base station, and carries the acknowledgement information about the downlink data, after receiving the downlink data by using the received downlink grant.
  • Msg3 the first request message
  • step 1705 the base station sends a first SI interface message to the network side, and carries acknowledgement information about the downlink data.
  • step 1706 the network side sends a second S1 interface message to the base station.
  • the UE When the UE is in the RRC_IDLE state, the UE sends a random access prefix in the random access procedure for requesting the resource for transmitting the uplink data.
  • the UE determines whether a resource for transmitting uplink data can be requested by the following manner.
  • the base station configures a carry data decision threshold T_ULdataRA for each coverage level.
  • T_ULdataRA a carry data decision threshold
  • the UE selects a random access prefix in the random access prefix set P1 for requesting the uplink data transmission resource, and the UL data to be transmitted buffered by the UE.
  • the UE selects a random access prefix in the random access prefix set P2 that is not used to request the uplink data transmission resource.
  • P1 and P2 are divided as follows:
  • Manner 1 Select a resource that does not belong to the PRACH resource configured for each coverage level as P1.
  • the base station configures at least one set of data transmission physical resource block (PRB) resources for the R15 UE, and all the PRBs are different from the physical random access channel/paging physical resource block configured for the R14 UE (Physical Random Access Channel/paging) Physical Resource Block, PRACH/paging PRB) As P1, all PRACH/paging PRBs configured for R14 UEs at this time can be regarded as P2.
  • PRB data transmission physical resource block
  • P1 Physical Random Access Channel/paging Physical Resource Block
  • P2 Physical Random Access Channel/paging Physical Resource Block
  • each set of data transmission PRB resources is used to indicate a certain uplink data size requirement.
  • three sets of data transmission PRB resources are configured, which are respectively identified as group A, group B, and group C.
  • Each group of data transmission PRB resources includes at least one PRB.
  • the UE When the UE selects any one of the PRBs in the group A, it indicates that the UE requests to simultaneously send uplink data of a size of [DataSizeMinGroupA, DataSizeMaxGroupA] when transmitting the first request message;
  • the PRACH time domain and subcarrier resources for different coverage levels may be divided.
  • the base station configures the sub-carriers that are not configured to the R14 UEs as the P1 for the R15 UE, and the sub-carrier resources are not included in the PRACH resources of the R15 UE.
  • the sub-carrier configured for the R14 UE can be regarded as P2.
  • the subcarrier in P1 can be divided into at least one set of data transmission subcarrier resources, and three sets of data transmission subcarrier resources are configured, which are respectively identified as group A, group B, and group C. Each group of data transmission subcarrier resources includes at least one subcarrier.
  • CE1_CBRA_S in FIG. 18 identifies a contention random access resource for indicating Msg3 transmission in single-tone mode under level 1, and CE1_CBRA_M flag is used to indicate multi-tone under coverage level 1.
  • the mode transmits the contending random access resource of Msg3, and the CE1_CFRA flag covers the non-competitive resource of level 1.
  • the CE2_CBRA identifier covers all the contention random access resources under level 2, and the CE2_CFRA flag covers the non-competitive resources of level 2.
  • the CE3_CBRA identifier covers all the contention random access resources under level 3, and the CE3_CFRA flag covers the non-competitive resources of level 3.
  • Mode 2 Select a resource belonging to a Physical Random Access Channel (PRACH) resource configured for each coverage level as P1.
  • PRACH Physical Random Access Channel
  • the base station divides the unused subcarrier resources in the non-contention resources under each coverage level into at least one set of data transmission subcarrier resources:
  • the non-competitive resources calculated by (nprach-NumSubcarriers-nprach-NumCBRA-StartSubcarriers) should be a continuous value in the parameter configuration of R14, according to the R14 technology, the UE and the terminal use the mod operation to ensure the UE after replacing the coverage level.
  • the Subcarriers that the base station can know are still used, so that the actually used non-contention Subcarriers will be discontinuous, so it is possible for the base station to configure the unused subcarrier resources in the non-contention resources under each coverage level as P1_CE1.
  • the CE1_CFRA flag covers non-competitive resources of level 1.
  • the CE1_CFRA_A1 to the CE1_CFRA_A3 respectively identify resources that have not been configured for the existing terminal in the non-contention resource of the level 1 and can be configured as the random access resource for requesting the uplink data transmission resource for the coverage level 1.
  • the CE2_CBRA flag covers all competing resources of level 2.
  • the CE2_CFRA flag covers non-competitive resources of level 2.
  • the CE3_CBRA_S identifies the contention random access resource for indicating the transmission of Msg3 in the single-tone mode under the coverage level 3.
  • the CE3_CBRA_M identifies the contention random access resource for indicating the multi-tone mode transmission Msg3 under the coverage level 3.
  • the CE3_CFRA flag covers the level 3 Non-competitive resources.
  • the base station may configure the non-competitive resource in each coverage level to be the P1 for the R15 UE, provided that the base station can distinguish the connected state by using the implementation manner. Random access and random access initiated by the idle state UE. As shown in FIG. 20, CE1_CBRA_S in FIG. 20 identifies a contention random access resource for indicating the transmission of Msg3 in the single-tone mode under level 1 and CE1_CBRA_M identifies a contention random access for indicating multi-tone mode transmission Msg3 under coverage level 1. Incoming resources, the CE1_CFRA flag covers non-competitive resources of level 1.
  • CE1_CFRA_A1 to CE1_CFRA_A3 respectively identify some resources in the non-contention resources of level 1 that have been allocated to existing terminals. If the base station can distinguish between the existing terminal and the new terminal, the part of the resources may be configured to be used for the coverage level 1 for requesting the uplink data transmission resource.
  • the CE2_CBRA flag covers all competing random access resources under level 2.
  • the CE2_CFRA flag covers non-competitive resources of level 2.
  • the CE3_CBRA_S identifies the contention random access resource for indicating the transmission of Msg3 in the single-tone mode under the coverage level 3.
  • the CE3_CBRA_M identifies the contention random access resource for indicating the multi-tone mode transmission Msg3 under the coverage level 3.
  • the CE3_CFRA flag covers the level 3 Non-competitive resources.
  • the base station divides the subcarrier resources configured for the Multi-tone Msg3 in the contention resources in each coverage level into at least one group of data transmission subcarrier resources.
  • CE1_CBRA_S in FIG. 21 identifies a contention random access resource for indicating the transmission of Msg3 in the single-tone mode under the coverage level 1
  • CE1_CBRA_M identifies the contention random connection for indicating the multi-tone mode transmission Msg3 under the coverage level 1.
  • the CE1_CFRA flag covers non-competitive resources of level 1.
  • the CE2_CBRA identifier covers all the contention random access resources under level 2, and the CE2_CFRA flag covers the non-competitive resources of level 2.
  • the CE3_CBRA_S identifies the contention random access resource for indicating the transmission of Msg3 in the single-tone mode under the coverage level 3.
  • the CE3_CBRA_M identifies the contention random access resource for indicating the multi-tone mode transmission Msg3 under the coverage level 1.
  • the CE3_CFRA flag covers non-competitive resources of level 3.
  • CE3_CBRA_A1 to CE3_CBRA_A3 indicate that a part of resources are configured from CE3_CBRA_M for identifying random access resources for requesting uplink data transmission resources that can be used for coverage level 3.
  • An embodiment of the present application provides a data transmission apparatus, including a memory and a processor, where the memory stores a program, and when the program is read and executed by the processor, the data transmission described in any of the foregoing embodiments is implemented. method.
  • An embodiment of the present application provides a computer readable storage medium storing at least one program, the at least one program being executable by at least one processor to implement the method described in any of the above embodiments. Data transmission method.
  • 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 the like, and the program code can be stored. Medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种数据传输方法、装置及计算机可读存储介质，所述数据传输方法包括：终端发送随机接入前缀给基站，并接收所述基站发送的随机接入响应；所述终端发送携带上行数据的第一请求消息至所述基站。

Description

一种数据传输方法及装置、计算机可读存储介质
本申请要求在2017年08月11日提交中国专利局、申请号为201710687283.5的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，例如一种数据传输方法及装置、计算机可读存储介质。
背景技术
机器对机器(Machine to Machine，M2M)通信系统中，终端(User Equipment，UE)节能是至关重要的。在相关技术中，当UE处于空闲态(RRC_IDLE)有数据需要发送时，UE首先触发随机接入过程建立或恢复与网络的无线资源控制(Radio Resource Control，RRC)连接，UE最早可以将数据随RRC连接建立完成或RRC恢复完成消息一起发送给基站。之后UE将维持在连接态(RRC_CONNECTED)一段时间，等待基站将UE释放。当UE处于RRC_CONNECTED状态有数据需要发送时，UE有可能因为失去时间同步或没有上行资源，而需要先发起随机接入，并在随机接入过程完成后将数据发送给基站。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请一实施例提供了一种数据传输方法及装置，以及一种计算机可读存储介质。
本申请一实施例提供了一种数据传输方法包括：终端发送随机接入前缀给基站，并接收所述基站发送的随机接入响应；所述终端发送携带上行数据的第一请求消息至所述基站。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述数据传输方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现上述数据传输方法。
本申请一实施例提供一种数据传输方法，包括：基站接收终端发送的随机接入前缀，发送随机接入响应至所述终端；所述基站接收所述终端发送的携带上行数据的第一请求消息。
在一实施例中，所述第一S1接口消息为如下之一：初始用户设备信息消息，用户设备上下文恢复请求消息，上行链路非接入层传输消息，路径切换请求消息，以及新定义的S1接口消息。
所述第二S1接口消息为如下之一：连接建立指示消息，用户设备上下文恢复响应消息，下行链路非接入层传输消息，路径切换请求确认消息，以及新定义的S1接口消息。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述数据传输方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现上述数据传输方法。
本申请一实施例提供一种数据传输方法，包括：终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，执行如下操作：在终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息后，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如下步骤：
在终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息后，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
本申请一实施例提供一种数据传输方法，包括：在终端处于空闲态进行随 机接入的过程中，基站接收终端发送的第一请求消息，如果基站有需要发送给所述终端的下行数据，所述基站发送第二响应消息给所述终端时携带所述下行数据。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述数据传输方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现上述数据传输方法。
本申请一实施例提供一种数据传输方法，包括：在终端处于空闲态进行随机接入的过程中，网络侧接收到基站发送的第一S1接口消息后，向所述基站发送第二S1接口消息，所述第二S1接口消息中携带需要发送给所述终端的下行数据。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述数据传输方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现上述数据传输方法。
本申请一实施例提供一种数据传输方法，包括：终端处于连接态时，所述终端接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述非竞争资源对应的随机接入前缀发起随机接入；所述终端接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，所述终端接收下行数据。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，执行如下操作：在终端处于连接态时，接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述非竞争资源对应的随机接入前缀发起随机接入；接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，接收下行数据。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如 下步骤：在终端处于连接态时，接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述非竞争资源对应的随机接入前缀发起随机接入；接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，接收下行数据。
本申请一实施例提供一种数据传输方法，包括：在终端处于连接态时，基站发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带所述基站分配给所述终端的非竞争资源；所述基站接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，执行如下操作：在终端处于连接态时，发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带所述基站分配给所述终端的非竞争资源；接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如下步骤：在终端处于连接态时，发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带所述基站分配给所述终端的非竞争资源；接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
附图用来提供对本申请技术方案的理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的 限制。
图1为相关技术中一种随机接入实现流程图；
图2为相关技术中另一种随机接入实现流程图；
图3为本申请一实施例提供的数据传输方法流程图；
图4为本申请一实施例提供的数据传输方法流程图；
图5为本申请实施例一提供的数据传输方法流程图；
图6为本申请实施例二提供的数据传输方法流程图；
图7为本申请实施例三提供的数据传输方法流程图；
图8为本申请实施例四提供的数据传输方法流程图；
图9为本申请实施例五提供的数据缓存方法流程图；
图10为本申请一实施例提供的数据传输方法流程图(先发第二响应消息，再发第一S1接口消息)；
图11为本申请实施例六提供的一种数据传输方法流程图；
图12为本申请实施例六提供的另一种数据传输方法流程图；
图13为本申请实施例七提供的数据传输方法流程图；
图14为本申请实施例九提供的一种数据传输方法流程图；
图15为本申请实施例九提供的另一种数据传输方法流程图；
图16为本申请实施例十提供的数据传输方法流程图；
图17为本申请实施例十一提供的数据传输方法流程图；
图18为本申请实施例十二提供的资源划分示意图；
图19为本申请实施例十二提供的另一资源划分示意图；
图20为本申请实施例十二提供的另一资源划分示意图；
图21为本申请实施例十二提供的另一资源划分示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
如图1所示，为相关技术中UE处于RRC_IDLE状态，使用CP方案在随机 接入过程之后上传数据，包括步骤101至步骤105。
在步骤101中，UE发送Msg1消息给演进型基站(enhanced Node B，eNB)，携带随机接入前缀(Preamble)。
在步骤102中，eNB发送Msg2消息给UE，携带随机接入响应(Radom Access Response，RAR)。
在步骤103中，UE发送Msg3消息给eNB，携带RRC连接请求(RRCConnectionRequest)和系统架构演进临时移动用户标识(SAE-Temporary Mobile Subscriber Identity，S-TMSI)。
在步骤104中，eNB发送Msg4消息给UE，携带RRC连接建立消息(RRCConnectionSetup)。
在步骤105中，UE发送Msg5消息给eNB，携带RRC连接建立完成消息(RRCConnectionSetupComplete和上行数据(UL data)。
如图2所示，为相关技术中UE处于RRC_IDLE状态，使用UP方案在随机接入过程之后上传数据，包括步骤201至步骤206。
在步骤201中，UE发送Msg1消息给eNB，携带随机接入前缀(Preamble)。
在步骤202中，eNB发送Msg2消息给UE，携带随机接入响应(Radom Access Response，RAR)。
在步骤203中，UE发送Msg3消息给eNB，携带RRC连接恢复请求(RRCConnectionResumeRequest)和恢复标识(ResumeID)。
在步骤204中，eNB发送Msg4消息给UE，携带RRC连接恢复消息(RRCConnectionResume)。
在步骤205中，UE发送Msg5消息给eNB，携带RRC连接恢复完成消息(RRCConnectionResumeComplete)。
在步骤206中，UE发送上行数据给eNB。
相关技术中，终端向基站发送上行数据时需要建立或恢复RRC连接，RRC连接建立或恢复成功之后终端才发送上行数据给基站。在一大类应用中，例如抄表业务，静止或低移动性的UE可能每次只需要发送一个数据包，两次数据包发送之间的时间间隔较长，这种情况下，UE进入RRC_CONNECTED状态后仅仅发送一个数据包，但是却要在RRC_CONNECTED状态维持一段时间连续监听基站信号。当终端发送完一次数据后，即回到RRC_IDLE状态，甚至回到节 能模式(Power Save Mode，PSM)状态，在下一次发送数据时重新发起RRC的建立或恢复请求。相关技术中的数据传输方法会在终端造成不必要的耗电。因此，本申请实施例提供一种数据的传输方案，以改善相关技术中终端上传数据能耗较高的情况。
本申请一实施例提供一种数据传输方法，如图3所示，包括步骤301，步骤302和步骤303。
在步骤301中，终端发送随机接入前缀给基站，接收所述基站发送的随机接入响应。
在步骤302中，所述终端发送携带上行数据的第一请求消息(Msg3)至所述基站。
所述终端在发送所述随机接入前缀前为空闲态时，所述方法还包括步骤303，所述终端接收所述基站返回的第二响应消息(Msg4)，判断冲突解决成功后，所述终端维持在空闲态，且将所述基站分配的临时无线网络临时标识作为小区无线网络临时标识，将小区无线网络临时标识保留第一时长。其中，根据第二响应消息中携带的冲突解决标识判断冲突是否解决成功。
其中，在进行数据传输时，可能会有多个终端发送相同的第一请求消息给基站，但基站只能检测到一个，基站会在第二响应消息中携带检测到的第一请求消息中的部分信息，多个终端中只有一个终端会判定这个第二响应消息是属于自己的，上述过程即为冲突解决的过程。
在一实施例中，所述第二响应消息中携带以下至少之一：冲突解决标识；对所述上行数据的高层确认信息(确认或非确认)；上行数据失败指示；上行数据重传指示；以及用户业务数据。
所述第一请求消息中还携带如下之一或其组合：是否需要优先建立S1接口的指示信息；是否需要接收所述上行数据的高层确认信息的指示信息；用于识别终端所注册的移动性管理实体的终端识别信息；接入层安全信息；以及对应于数据传输的连接建立原因。
在一实施例中，所述终端接收到所述基站返回的第二响应消息且获得小区无线网络临时标识后，还包括：所述终端在公共搜索空间，或传输第二响应消息调度信息的搜索空间，使用所述小区无线网络临时标识检测以下之一：物理下行控制信道，上行调度信息，以及下行调度信息。
其中，物理下行控制信道中也可能携带上行调度信息或下行调度信息。
在一实施例中，所述终端接收到所述基站返回的第二响应消息后，还包括：如果所述终端还有上行数据需要传输，所述终端再次发送携带上行数据的第一请求消息至所述基站。
所述终端发送随机接入前缀给基站前，还选择随机接入前缀或者选择发送随机接入前缀的资源。
在一实施例中，所述终端发送随机接入前缀给基站包括：当所述终端满足第一预设条件时，所述终端发送用于请求上行数据传输资源的随机接入前缀给所述基站。
其中，所述终端发送用于请求上行数据传输资源的随机接入前缀给基站包括：所述终端在用于请求上行数据传输资源的随机接入前缀集合中选择一个随机接入前缀，将所选的随机接入前缀发送给所述基站；或者，所述终端在用于请求上行数据传输资源的随机接入资源集合中选择一个随机接入资源，使用所选的随机接入资源将随机接入前缀发送给所述基站。
在一实施例中，所述终端满足第一预设条件包括以下之一或其组合：所述终端待发送的上行数据大于携带数据判决门限；所述终端的无线链路条件满足链路条件门限；以及所述终端待发送的上行数据的业务类型属于预设业务类型。
在一实施例中，所述方法还包括，所述终端从基站发送的系统消息中获取所述如下之一或其组合：携带数据判决门限；链路条件门限；以及预设业务类型信息，其中，所述携带数据判决门限包括：配置给全部覆盖等级的一个携带数据门限，或者每个覆盖等级分别配置的携带数据判决门限。
在一实施例中，所述方法还包括以下之一：所述终端未接收到所述基站返回的第二响应消息；所述终端接收到的所述终端基站返回的第二响应消息且所述第二响应消息中携带上行数据失败指示或上行数据重传指示；以及所述终端未接收到所述基站返回的随机接入响应时，本次随机接入失败，所述终端重新发起随机接入。
在一实施例中，所述终端重新发起随机接入包括：所述终端根据以下至少之一确定，选择用于请求上行数据传输资源的随机接入前缀进行随机接入，或者选择非用于请求上行数据传输资源的随机接入前缀进行随机接入：随机接入的失败次数；随机接入的失败次数序号；终端获得的下行测量值；覆盖等级； 重复次数。重复次数是终端获得的配置信息。下行测量值比如参考信号接收功率值，当然，也可是其他值。
在一实施例中，所述终端按如下方式之一重新发起随机接入：
在当前覆盖等级下，所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端更换覆盖等级至最大覆盖等级后，发送非用于请求上行数据传输资源的随机接入前缀或者发送随机接入前缀进行随机接入。其中，发送随机接入前缀进行随机接入的方式可以按照相关技术中的发送方式进行。
在当前覆盖等级下，所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端发送非用于请求上行数据传输资源的随机接入前缀或者发送随机接入前缀进行随机接入；如果仍然失败且失败次数到达对应的失败次数阈值时，所述终端更换至大于当前覆盖等级的下一覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在该覆盖等级进行随机接入，直到随机接入成功，或者所述终端到达最大覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在最大覆盖等级下进行随机接入。其中，发送随机接入前缀进行随机接入的方式可以按照相关技术中的发送方式进行。
在当前覆盖等级下，所述终端在所述第一请求消息中携带上行数据进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端更换覆盖等级至最大覆盖等级后，发送携带无线资源控制消息的第一请求消息进行随机接入。
在当前覆盖等级下，所述终端在所述第一请求消息中携带上行数据进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端发送携带无线资源控制消息的第一请求消息进行随机接入；如果仍然失败且失败次数到达对应的失败次数阈值时，所述终端更换至大于当前覆盖等级的下一覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在该覆盖等级进行随机接入，直到随机接入成功，或者所述终端到达最大覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在最大覆盖等级下进行随机接入。
所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值时，发送非用于请求上行数据传输资源的随机接入前缀进行随机接入。
所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值，并且终端测量的参考信号接收功率值在第一预定义范围时，所述终端发送非用于请求上行数据传输资源的随机接入前缀进行随机接入；所述终端在所述发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值，并且终端测量的参考信号接收功率值在第二预定义范围时，所述终端更换至下一覆盖等级，发送用于请求上行数据传输资源的随机接入前缀进行随机接入。
所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败后，发送非用于请求上行数据传输资源的随机接入前缀，以及，所述终端在所述发送非用于请求上行数据传输资源的随机接入前缀进行随机接入失败后，发送用于请求上行数据传输资源的随机接入前缀进行随机接入；重复前面方式，当接入失败次数到达对应的失败次数阈值时，所述终端更换至下一覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在该覆盖等级进行随机接入，直到随机接入成功，或者所述终端到达最大覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在最大覆盖等级下进行随机接入。
在一实施例中，所述方法还包括：所述终端通过接收基站广播的系统消息或基站发送给终端的专用消息，获取每个覆盖等级对应的失败次数阈值。
在一实施例中，在所述终端重新发起随机接入前，还包括：所述终端从所述基站获取操作指示信息，根据所述操作指示信息确定重新发起随机接入的方式。
在一实施例中，在所述终端执行如下操作之一前，还包括：所述终端从所述基站获取操作指示信息，根据所述操作指示信息确定在发送所述携带上行数据的第一请求消息进行随机接入失败后的操作。
在一实施例中，在所述终端进行随机接入之前，根据如下至少之一决定是否终止暂停功率提升操作：本次随机接入的第一请求消息的格式与前一次进行随机接入时的第一请求消息的格式是否相同。本次随机接入发送随机接入前缀的方式与前一次进行随机接入时发送随机接入前缀的方式是否相同；其中，所述发送随机接入前缀的方式包括发送用于请求上行数据传输资源的随机接入前缀和发送非用于请求上行数据传输资源的随机接入前缀。以及前一次进行随机 接入时的失败原因。
在一实施例中，所述终端在发送所述随机接入前缀前为连接态时，所述第一请求消息中还携带如下之一或其组合：小区无线网络临时标识、无线资源控制消息以及请求释放指示。
在一实施例中，终端在发送所述随机接入前缀前为连接态时，还包括：所述终端接收到所述基站返回的第二响应消息，在判断冲突解决成功后，所述终端自主释放无线资源控制连接，并转移到空闲态；或者，所述终端接收到所述基站返回的第二响应消息，在判断冲突解决成功后，所述终端处理所述第二响应消息中携带的无线资源控制释放消息，并转移到空闲态。
在一实施例中，所述终端发送携带上行数据的第一请求消息至所述基站包括：所述终端获取所述随机接入响应中携带的指示信息，当满足第二预设条件时，所述终端发送携带所述上行数据的第一请求消息至所述基站。
在一实施例中，所述方法还包括：所述终端获取所述随机接入响应中携带的指示信息，当满足第三预设条件时，所述终端发送携带无线资源控制消息的第一请求消息至所述基站。
在一实施例中，所述满足第二预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息大于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时直接发送上行数据；所述满足第三预设条件为：所述指示信息为上行授权的数据量信息；或者所述上行授权的数据量信息小于等于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时携带无线资源控制消息。
在一实施例中，所述上行授权门限为所述终端在发送所述随机接入前缀前的状态所对应的上行授权门限；或者，为所述终端在发送所述随机接入前缀前的状态及所在覆盖等级所对应的上行授权门限。
在一实施例中，与连接态终端对应的上行授权门限大于与空闲态终端对应的上行授权门限。
在一实施例中，所述方法还包括：所述终端接收到所述基站返回的第二响应消息后，根据所述第二响应消息中携带的无线资源控制响应消息建立无线资源控制连接，或者恢复无线资源控制连接，或者重建立无线资源控制连接，所述终端转移到连接态。
本申请一实施例提供一种数据传输方法，如图4所示，包括步骤401至步骤404。
在步骤401中，基站接收终端发送的随机接入前缀，并发送随机接入响应至所述终端。
在步骤402中，所述基站接收所述终端发送的携带上行数据的第一请求消息。
在一实施例中，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：所述基站发送第二响应消息给所述终端，所述第二响应消息中携带如下信息之一或其组合：冲突解决标识，对所述上行数据的高层确认信息，上行数据发送失败指示，上行数据重传指示，以及用户业务数据。
在一实施例中，所述第一请求消息中还携带如下之一或其组合：优先建立S1接口的指示信息，需要接收所述上行数据的高层确认信息的指示信息，所述终端识别信息，用于识别终端所注册的移动性管理实体的信息，接入层安全信息，以及对应于数据传输的连接建立原因。
在一实施例中，所述方法还包括步骤403和步骤404。
在步骤403中，当所述第一请求消息中携带优先建立S1接口的指示信息时，所述基站发送携带所述上行数据的第一S1接口消息给网络侧。
在步骤404中，所述基站接收到所述网络侧返回的第二S1接口消息，从所述第二S1接口消息中获取高层确认信息，将所述高层确认信息发送给所述终端。
在一实施例中，所述方法还包括：所述基站在所述第二S1接口消息中收到下行数据时，所述基站将所述下行数据发送给所述终端。
在一实施例中，所述方法还包括：所述基站通过系统消息或专用消息发送操作指示信息给终端，所述操作指示信息用于指示所述终端在随机接入失败后重新进行随机接入的方式。
所述重新进行随机接入的方式包括如下之一：优先更换覆盖等级重新进行随机接入；优先发送非用于请求上行数据传输资源的随机接入前缀或者发送随机接入前缀重新进行随机接入；以及优先发送携带无线资源控制消息的第一请求消息重新进行随机接入。其中，发送随机接入前缀进行随机接入的方式可以按照相关技术中的发送方式进行。
在一实施例中，所述终端处于连接态且所述第一请求消息中还携带无线资 源控制消息时，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：所述基站发送第二响应消息给所述终端，所述第二响应消息中携带无线资源控制重建立消息。
在一实施例中，所述终端处于连接态且所述第一请求消息中还携带请求释放指示时，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：所述基站发送第二响应消息给所述终端，所述第二响应消息中携带无线资源控制释放消息。
在一实施例中，所述方法还包括：所述基站通过系统消息或专用消息下发携带数据判决门限给所述终端。其中，所述携带数据判断门限用于所述终端判断，在用于请求上行数据传输资源的随机接入前缀集合中，或者在非用于请求上行数据传输资源的随机接入前缀集合中选择发送给所述基站的随机接入前缀；或者，所述携带数据判断门限用于所述终端判断在用于请求上行数据传输资源的随机接入资源集合中，或者在非用于请求上行数据传输资源的随机接入资源集合中选择随机接入资源来发送给所述基站的随机接入前缀。其中，所述携带数据判决门限包括：配置给全部覆盖等级的一个携带数据门限，或者每个覆盖等级分别配置的携带数据判决门限。
在一实施例中，所述随机接入响应中携带指示信息，所述指示信息指示所述终端发送第一请求消息的发送方式；所述基站接收所述终端发送的携带上行数据的第一请求消息包括：当满足第二预设条件时，所述基站接收所述终端发送的携带上行数据的第一请求消息；当满足第三预设条件时，所述基站接收所述终端发送的携带无线资源控制消息的第一请求消息。
在一实施例中，所述满足第二预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息大于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时直接发送上行数据。
所述满足第三预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息小于等于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时携带无线资源控制消息。
在一实施例中，所述上行授权门限为：所述终端在发送所述随机接入前缀前的状态所对应的上行授权门限；或者所述上行授权门限为：所述终端在发送所述随机接入前缀前的状态及所在覆盖等级所对应的上行授权门限。即可以为 多个覆盖等级配置相同的上行授权门限，也可以为多个覆盖等级分别配置不同的上行授权门限。
在一实施例中，与连接态终端对应的上行授权门限大于与空闲态终端对应的上行授权门限。
在一实施例中，所述终端为空闲态时，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：所述基站发送第二响应消息给所述终端，所述第二响应消息中携带无线资源控制响应消息。
本申请一实施例提供一种数据传输方法，包括：终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
本申请一实施例提供一种数据传输方法，包括：在终端处于空闲态进行随机接入的过程中，基站接收终端发送的第一请求消息，如果基站有需要发送给所述终端的下行数据，所述基站发送第二响应消息给所述终端时携带所述下行数据。
在一实施例中，在所述终端处于空闲态发起随机接入之前，所述基站收到网络侧发送的需要发送给所述终端的下行数据时，缓存该下行数据。
本申请一实施例提供一种数据传输方法，包括：在终端处于空闲态进行随机接入的过程中，网络侧接收到基站发送的第一S1接口消息后，向所述基站发送第二S1接口消息，所述第二S1接口消息中携带需要发送给所述终端的下行数据。
在一实施例中，所述方法还包括：在所述终端处于空闲态发起随机接入之前，所述网络侧收到应用层发送的需要发送给所述终端的下行数据，缓存该下行数据。
本申请一实施例提供一种数据传输方法，包括：终端处于连接态时，所述终端接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述非竞争资源对应的随机接入前缀发起随机接入；所述终端接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，所述终端接收下行数据。
本申请一实施例提供一种数据传输方法，包括：在终端处于连接态时，基站发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带 所述基站分配给所述终端的非竞争资源；所述基站接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
下面通过实施例说明本申请。
实施例一(空闲态发上行数据基本流程，控制面方案)
本实施例提供一种无状态转移的空闲态上行数据传输方案。当UE处于RRC_IDLE状态时，UE发送随机接入前缀，用于请求发送上行数据的资源。当UE收到基站发送的随机接入响应并得到上行授权后，在发送第一请求消息时同时发送上行数据给基站。当UE收到基站发送的第二响应消息并确定冲突解决成功后，UE认为本次上行数据发送成功，UE会维持在RRC_IDLE状态。同时UE可将基站分配的临时媒体接入控制(Media Access Control，MAC)层标识临时无线网络临时标识(Tempory-Radio Network Tempory Identity，T-RNTI)视为正式的MAC层标识小区无线网络临时标识(Cell-Radio Network Temmporary Identify，C-RNTI)，UE在RRC_IDLE状态将C-RNTI保留第一时长，第一时长可以是预设的，也可以是由网络侧为UE配置的。
本实施例中，UE处于RRC_IDLE状态，使用控制面(Control Plane，CP)方案，如图5所示，包括步骤501至步骤507。
在步骤501，当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源，即请求上行数据传输资源。
在步骤502，基站发送随机接入响应给UE。
所述随机接入响应中携带基站分配给UE的临时MAC层标识T-RNTI。
在步骤503，UE接收到随机接入响应并得到上行授权后，发送第一请求消息(Msg3)时同时发送上行数据给基站。
Msg3可以仅携带包含核心网标识的标识(例如称为数据目标地址标识)和上行数据，不携带RRC消息。与相关技术不同之处在于，相关技术中Msg3需要携带RRC消息，例如RRC连接建立请求消息，RRC连接恢复请求消息，或新的RRC连接公共请求消息，用于触发建立或恢复RRC连接，本实施例中，不携带RRC消息。
如果UE在上次RRC连接释放时没有存储UE上下文(即使用CP方案)，UE在通过Msg3发送上行数据包的同时应携带核心网给UE分配的标识，例如S-TMSI，或能够标识UE所附着的移动性管理实体(Mobility Management Entity，，MME)的信息给基站，例如称为数据目标地址标识，或全局唯一移动管理实体标识信息(Globally Unique Mobility Management Entity Identifier，GUMMEI)。UE在发送上行数据包的同时还可以携带接入层安全信息给基站，例如ul-NAS-MAC，ul-NAS-Count，该接入层安全信息可以是根据非接入层(Non Access Stratum，NAS)层安全信息获得的。Msg3还可以携带连接建立原因，例如表示传输上行数据的连接建立原因。
UE可以在第一请求消息中包含是否需要优先建立S1接口的指示信息(例如如果UE认为该上行数据需要高层确认，在这种情况下，还可以认为UE发送的上行数据不需要无线链路控制(Radio Link Control，RLC)和混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)层确认，仅需等待高层确认即可)。如果需要优先建立S1接口，可以携带IND_needforS1＝YES信息，该指示也可以作为UE是否需要接收所述上行数据的高层确认信息的指示信息。
在步骤504，基站发送携带上行数据的第一SI接口消息至网络侧。
比如，第一S1接口消息为数据传输请求(Data Transmission Req)。
在其他实施例中，所述第一S1接口消息还可以为初始用户设备信息(INITIAL UE MESSAGE)消息；或者，用户设备上下文恢复请求(UE CONTEXT RESUME REQUEST)消息；或者，上行链路非接入层传输(UPLINK NAS TRANSPORT)消息；或者，路径切换请求(PATH SWITCH REQUEST)消息；或者，第一S1接口消息还可以为其他新定义的S1接口消息。所述网络侧比如为UE附着的移动性管理实体(Mobility Management Entity，MME)。
如果UE有同时携带接入层安全信息给基站，则基站也可以同时将该接入层安全信息发送给MME。
在步骤505，网络侧发送第二S1接口消息至基站。
比如，第二S1接口消息为数据传输确认(Data Transmission Ack)。
或者，第二S1接口消息还可以为连接建立指示(Connection Establishment Indication)消息；或者，用户设备上下文恢复响应(UE CONTEXT RESUME RESPONSE)消息；或者，下行链路非接入层传输(DOWNLINK NAS  TRANSPORT)消息；或者，路径切换请求确认(PATH SWITCH REQUEST ACKNOWLEDGE)消息；或者，第二S1接口消息还可以为其他新定义的S1接口消息。
第二S1接口消息携带对所述上行数据的高层确认信息(确认/非确认)，还可以包含下行接入层安全信息。
在步骤506，基站发送第二响应消息(Msg4)至终端。
其中，第二响应消息中携带冲突解决标识(contention resolution ID)，比如由MAC层控制单元携带。
其中，第二响应消息(Msg4)中可以仅携带冲突解决标识，而不携带RRC消息。
其中，第二响应消息中携带高层确认信息(Ack/Nack for UL data)，或者，上行数据重传指示(DataResendIND)。
在步骤507中，UE收到基站发送的第二响应消息并根据冲突解决ID确定冲突解决成功后，认为本次上行数据发送成功，维持在RRC_IDLE状态。
相关技术中，基站先发送第二响应消息给终端，再发送第一S1接口消息给MME，且第一S1接口消息通常触发基站和MME建立针对UE的S1接口及UE上下文，与相关技术相比，本实施例中第一S1接口消息可以根据UE指示先于第二响应消息发送，且不触发针对UE的S1接口及UE上下文建立。
相关技术中Msg4需要携带RRC消息，例如RRC连接建立消息，RRC连接恢复消息，或新的RRC连接公共应答消息，用于完成RRC建立或RRC恢复流程，本申请中，Msg4可以不需要携带RRC消息。
在一实施例中，如果UE在发送上行数据包的同时携带需要优先建立S1接口的指示，则UE和基站需要使用延长的冲突解决定时器。该延长的冲突解决定时器可以静态配置，或由基站在系统消息中广播多个冲突解决定时器时长，UE和基站根据相应的指示选择其一使用。
在一实施例中，UE可以将步骤502中，基站分配的临时MAC层标识T-RNTI视为正式的MAC层标识C-RNTI。UE在维持在RRC_IDLE状态时，也将C-RNTI保留一段时间，具体保留时间可以是预设的，也可以是由网络侧为UE配置的。在这段时间里，UE始终在随机接入响应RAR的呼叫搜索空间(Calling Search Space，CSS)，或者在一个新定义的专用于Msg3传数据的CSS搜索空间，用 C-RNTI解调物理信道。
在一实施例中，如果UE收到基站的第二响应消息但判定冲突解决失败，或未收到第二响应消息，则UE认为本次上行数据发送失败，UE重新发起随机接入流程来传输数据。
在一实施例中，如果第二S1接口消息中未包含对上行数据的确认，或指示上行数据发送失败，则基站在发送给UE的第二响应消息中可以包含上行数据发送失败指示，或上行数据重传指示。
在一实施例中，如果UE收到基站的第二响应消息，根据冲突解决ID确定冲突解决成功，且UE基站分配的临时MAC层标识T-RNTI视为正式的MAC层标识C-RNTI，但是第二响应消息中包含上行数据发送失败指示，或上行数据重传指示，则UE需要重新发起随机接入流程来传输数据，Msg3中携带C-RNTI。
实施例二(空闲态发上行数据基本流程，用户面方案)
本实施例中，UE处于RRC_IDLE状态，与实施例一相比，本实施例采用用户面(User Plane，UP)方案，如图6所示，包括步骤601至步骤607。
在步骤601中，当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤602中，UE收到基站发送的随机接入响应并得到上行授权。
在步骤603中，UE发送第一请求消息(Msg3)时同时发送上行数据给基站。
本实施例采用UP方案，UE在上次RRC连接释放时执行了挂起操作，有存储的UE上下文及恢复标识(ResumeID)，UE在通过Msg3发送上行数据的同时携带该恢复标识。
Msg3可以仅携带包含核心网标识的标识(例如称为数据目标地址标识，或GUMMEI信息)和上行数据，不携带RRC消息。与相关技术相比，相关技术中Msg3需要携带RRC消息，例如RRC连接建立请求消息，RRC连接恢复请求消息，或新的RRC连接公共请求消息，用于触发建立或恢复RRC连接，本实施例中，不携带RRC消息。
UE在发送上行数据包的同时还可以携带接入层安全信息给基站，该接入层安全信息可以是根据NAS层安全信息获得的。
UE还可以携带连接建立原因，例如表示传输上行数据的连接建立原因。
UE可以在第一请求消息中包含是否需要优先建立S1接口的指示信息(例如如果UE认为该上行数据需要高层确认，在这种情况下，还可以认为UE发送的上行数据不需要RLC和HARQ层确认，仅需等待高层确认即可)如果需要优先建立S1接口，则携带IND_needforS1＝YES信息。该指示也可以作为UE是否需要接收所述上行数据的高层确认信息的指示信息。
在步骤604中，基站发送携带上行数据的第一SI接口消息至网络侧。
比如，第一S1接口消息为数据传输请求(Data Transmission Req)。
所述网络侧比如为UE附着的移动性管理实体(Mobility Management Entity，MME)。
如果UE有同时携带接入层安全信息给基站，则基站也可以同时将该接入层安全信息发送给MME。
基站根据恢复标识查找到基站侧存储的UE上下文，根据UE上下文中包含的UE附着的MME信息，向该MME发送第一S1接口消息。
在步骤605中，网络侧发送第二S1接口消息至基站。
比如，第二S1接口消息为数据传输确认(Data Transmission Ack)，携带对所述上行数据的高层确认信息(确认/非确认)，还可以包含下行接入层安全信息。
在步骤606中，基站发送第二响应消息(Msg4)至终端。
其中，第二响应消息中携带冲突解决标识，比如由MAC层控制单元携带。
其中，第二响应消息(Msg4)中可以仅携带冲突解决标识，而不携带RRC消息。
在步骤607中，UE收到基站发送的第二响应消息并根据冲突解决ID确定冲突解决成功后，UE认为本次上行数据发送成功，维持在RRC_IDLE状态。
实施例三(空闲态数据连续发送)
UE在初始随机接入过程中可能无法传输完所有待传数据，则UE在RRC_IDLE状态且具有C-RNTI的状态下，可以继续发送携带上行数据第一请求消息给基站，基站发送第二响应消息给UE，同时携带对上行数据的确认。这一流程可以交互数次，直到待传输数据传输完成为止。
如图7所示，包括步骤701至步骤712。
步骤701～707与步骤501～507相同；其中步骤703还可以携带缓冲区状态 报告，指示还有数据需要发送。
在步骤708，基站通过物理下行控制信道(Physical Downlink Control Channel，PDCCH)传输分配新的上行授权至终端，该PDCCH传输用小区无线网络临时标识加扰。
在步骤709中，终端使用小区无线网络临时标识解调PDCCH传输，获取上行授权，并用该上行授权发送上行数据给基站。
在步骤710中，基站发送携带上行数据的第一SI接口消息至网络侧。
在步骤711中，网络侧发送第二S1接口消息至基站。
在步骤712中，如果第二S1接口消息中包含对上行数据的确认，所述基站将该对上行数据的确认发送至终端。
其中，步骤708～712可重复执行数次，直到终端所有待传输数据传输完成。
实施例四(下行缓存数据在Msg4发送，CP方案和UP方案合一)
网络侧如果有下行数据要发送给M2M，例如窄带物联网(Narrow Band Internet of Things，NB-IoT，NB-IoT)或物联网的应用场景(enhanced Machine Type Communication，eMTC)用户，且如果这些数据是延迟容忍(delay tolerance)的，那么网络侧可以将这些下行数据缓存一段时间再发送给UE，在这段时间内，如果网络侧收到第一S1接口消息，则可以在第二S1接口消息中将缓存的下行数据发给基站。如果基站收到第二S1接口消息后，尚未发送第二响应消息给UE，则基站可以在第二响应消息中包含下行数据发送给UE，该下行数据可以包含在新定义的媒体接入控制控制单元(Media Access Control Control Element，MAC CE)中，或新定义的数据容器信息单元(Information Element，IE)中。
如图8所示，为随机接入过程传下行数据流程，包括步骤801至步骤808。
在步骤801中，当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤802中，UE收到基站发送的随机接入响应并得到上行授权。
在步骤803中，UE在发送第一请求消息(Msg3)时同时发送上行数据给基站。
如果UE在上次RRC连接释放时没有存储UE上下文(即使用CP方案)，UE在通过Msg3发送上行数据包的同时应携带核心网给UE分配的标识，例如 S-TMSI，或能够标识UE所附着的MME的信息给基站，例如称为数据目标地址标识，或全局唯一MME标识信息(Globally Unique MME Identifier，GUMMEI)。UE在发送上行数据包的同时还可以携带接入层安全信息给基站，该接入层安全信息可以是根据NAS层安全信息获得的。或者，UE在上次RRC连接释放时执行了挂起操作，有存储的UE上下文及恢复标识，UE在通过Msg3发送上行数据的同时携带该恢复标识。
在步骤804中，基站检查是否有下行数据需要发送给终端，如果有，则将其包含在第二响应消息中。
在步骤805中，基站发送携带上行数据的第一SI接口消息至网络侧。
比如，第一S1接口消息为数据传输请求(Data Transmission Req)。
所述网络侧比如为UE附着的移动管理实体(Mobility Management Entity，MME)。
如果UE有同时携带接入层安全信息给基站，则基站也可以同时将该接入层安全信息发送给MME。
在步骤806中，网络侧检查是否有下行数据需要发送给终端，如果有，则将其包含在第二S1接口消息中。
在步骤807中，网络侧发送携带下行数据的第二S1接口消息至基站。
比如，第二S1接口消息为数据传输确认(Data Transmission Ack)。
比如，第二S1接口消息还可携带对所述上行数据的高层确认信息(确认/非确认)，还可以包含下行接入层安全信息。
在步骤808中，基站发送携带下行数据的第二响应消息(Msg4)至终端。
第二响应消息中携带的其他信息请参考步骤506。
实施例五(下行数据缓存)
网络侧如果有下行数据要发送给M2M(NB-IoT或eMTC)用户且用户处于S1接口空闲态，且如果这些数据是时延可容忍的，那么网络侧可以将这些下行数据缓存一段时间，不触发S1接口寻呼消息发送。或者，网络侧如果有下行数据要发送给M2M(NB-IoT或eMTC)用户且用户处于S1接口连接态，则网络侧将数据发送给基站。但此时终端可能处于空口空闲态，那么基站可以将这些下行数据缓存一段时间，不触发空口寻呼消息发送。
如图9所示，为下行数据缓存流程图，包括步骤901至步骤904。
在步骤901中，应用层有下行数据发送到网络侧。
在步骤902中，网络侧判断用户处于S1接口空闲态，且这些下行数据是时延可容忍的，那么网络侧可以将这些下行数据缓存一段时间，不触发S1接口寻呼消息发送。缓存时长可以为预设值。
在步骤903中，网络侧判断用户处于S1接口连接态，则将该下行数据发送到基站。
在步骤904中，基站判断终端处于空口空闲态，且这些下行数据是时延可容忍的，那么基站可以将这些下行数据缓存一段时间，不触发空口寻呼消息发送。缓存时长可以为预设值。
图10是实施例一或实施例二的另一实现方式。本实施例包括步骤1001至步骤1009。
在步骤1001中，当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤1002中，UE收到基站发送的随机接入响应并得到上行授权。
在步骤1003中，UE发送第一请求消息(Msg3)时同时发送上行数据给基站。
Msg3可以携带终端标识，例如S-TMSI或恢复标识，也可以携带包含终端注册的核心网的标识(例如，GUMMEI信息或称为数据目标地址标识)和上行数据，不携带RRC消息。
UE在发送上行数据包的同时还可以携带接入层安全信息给基站，该接入层安全信息可以是根据NAS层安全信息获得的。UE还可以携带连接建立原因。
在步骤1004中，基站发送第二响应消息(Msg4)至终端。
其中，第二响应消息中携带冲突解决标识，比如由MAC层控制单元携带。
其中，第二响应消息中可以仅携带冲突解决标识，而不携带RRC消息。
在步骤1005中，UE收到基站发送的第二响应消息并根据冲突解决ID确定冲突解决成功后，UE维持在RRC_IDLE状态，且将所述基站分配的临时无线网络临时标识作为小区无线网络临时标识，将所述小区无线网络临时标识保留第一时长。
在步骤1006中，基站发送携带上行数据的第一SI接口消息至网络侧。
比如，第一S1接口消息为数据传输请求(Data Transmission Req)。
在步骤1007中，网络侧发送第二S1接口消息至基站。
比如，第二S1接口消息为数据传输确认(Data Transmission Ack)，携带对所述上行数据的高层确认信息(确认/非确认)。
在步骤1008中，基站通过PDCCH传输发送下行指配信息至终端，该PDCCH传输用小区无线网络临时标识加扰。
在步骤1009中，终端使用小区无线网络临时标识解调PDCCH传输，获取下行指配信息，并用该下行指配信息接收基站发送给终端的下行数据，该下行数据可以为上行数据的高层确认信息。
实施例六(终端根据RAR中的信息确定Msg3的发送方式(带数据或带RRC消息，CP方案与UP方案合一)
当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀，用于请求发送上行数据的资源。基站控制是否为UE建立或恢复RRC连接，以及是否将UE转移到RRC_CONNECTED状态。
基站在随机接入响应中携带指示，用于指示第一请求消息的发送方式。
该指示可以为隐式的指示，例如上行授权中所包含的数据量信息，例如可以为RAR消息中上行授权(UL grant)字段中的传输块大小(TB size)。当该指示(如上行授权的数据量信息)超过某一门限(后文称为上行授权门限)，则UE发送第一请求消息时直接发送上行数据给基站。UE在发送第一请求消息时，应按照上行授权的数据量信息封装上行数据并发送给基站，如果UE的待发送数据超过上行授权的数据量信息，则UE可以按照上行授权的数据量信息将待发送数据拆分成多个片段依次发送。如果该指示(如上行授权的数据量信息)未超过上行授权门限，则UE发送第一请求消息给基站，且第一请求消息中携带RRC消息，该RRC消息可以是RRC连接建立请求，RRC连接恢复请求消息，或RRC连接公共请求消息。
或者，该指示也可以为一个显式的指示，指示UE在发送第一请求消息时直接发送上行数据，或者指示UE发起普通的RRC连接建立或RRC恢复流程。
上行授权门限可以是静态配置的预设值，也可以由基站配置，比如通过系 统消息中新定义的字段来发送给UE，且可以动态调整，例如配置上行授权门限为200比特。在一实施例中，上行授权门限可以为每个覆盖等级单独配置。
或者，基站可以在随机接入响应中按照终端请求为终端分配合适的上行授权，同时携带另一指示信息。该指示信息指示如果UE本次在发送第一请求消息时直接发送上行数据出现失败，则UE应在后续再次发起随机接入时，使用非请求发送上行数据的随机接入前缀或随机接入资源，即UE应发起用于普通的RRC连接建立或RRC恢复流程的随机接入。
图11为UE发送第一请求消息时直接发送上行数据给基站的实现，如图11所示，UE处于RRC_IDLE状态，包括步骤1100至步骤1106。
在步骤1100中，基站通过系统消息下发上行授权门限T_ULgrant。
在步骤1101中，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤1102中，基站发送随机接入响应给UE，携带较大的上行授权。
在步骤1103中，UE判断上行授权中所包含的数据量信息大于上行授权门限，UE发送第一请求消息(Msg3)时同时发送上行数据给基站。
如果采用UP方案，UE在上次RRC连接释放时执行了挂起操作，有存储的UE上下文及恢复标识，UE在通过Msg3发送上行数据的同时携带该恢复标识。如果采用CP方案，UE在通过Msg3发送上行数据包的同时应携带核心网给UE分配的标识，例如S-TMSI，或能够标识UE所附着的MME的信息，例如GUMMEI信息，给基站。
在步骤1104中，基站发送携带上行数据的第一SI接口消息至网络侧。
在步骤1105中，网络侧发送第二S1接口消息至基站。
在步骤1106中，基站发送第二响应消息(Msg4)至终端。
如果随机接入响应中的指示(如上行授权的数据量信息)未超过上行授权门限，则UE发送第一请求消息给基站，且第一请求消息中携带RRC消息，UE收到携带RRC消息的第二响应消息后，应建立或恢复RRC连接，并转移到RRC_CONNECTED状态，如图12所示，包括步骤1200至步骤1208。
在步骤1200中，基站通过系统消息下发上行授权门限T_ULgrant。
在步骤1201中，UE在随机接入过程中发送随机接入前缀给基站，用于请 求发送上行数据的资源。
在步骤1202中，基站发送随机接入响应给UE，携带较小的上行授权数据量信息(不超过上行授权门限)。
在步骤1203中，UE判断上行授权的数据量信息小于等于上行授权门限，UE发送第一请求消息(Msg3)给基站，携带RRC连接公共请求消息；该公共请求消息可以是已有的RRC连接请求消息，RRC连接恢复请求消息，或者新定义的RRC连接公共请求消息。
Msg3消息中还携带核心网给UE分配的标识，例如S-TMSI，或能够标识UE所附着的MME的信息给基站；或者，携带恢复标识。
在步骤1204中，基站发送第一SI接口消息至网络侧。
在步骤1205中，网络侧发送第二S1接口消息至基站。
在步骤1206中，基站发送第二响应消息(Msg4)至终端，携带RRC连接公共响应消息。该公共响应消息可以是已有的RRC连接建立消息，RRC连接恢复消息，或者新定义的RRC连接公共响应消息。
在步骤1207中，UE建立RRC连接，进入RRC_CONNECTED状态。
在步骤1208中，UE发送Msg5消息给基站，携带上行数据。
实施例七(终端发送Msg3+数据后，可以处理Msg4+RRC消息)
即便基站在第一请求消息中没有收到RRC连接建立请求或RRC恢复请求消息，基站仍可以主动发送RRC发起RRC连接建立或恢复流程，将终端转移到RRC_CONNECTED状态，即基站发送携带RRC消息的第二响应消息给UE，该RRC消息可以是RRC连接建立，RRC连接恢复，或RRC连接公共响应消息。当UE收到该第二响应消息后，应建立或恢复RRC连接，并转移到RRC_CONNECTED状态。
相关技术中，必须UE通常需要先发送RRC请求消息才能接收RRC响应消息，该RRC请求消息可以是RRC连接建立请求消息，RRC连接恢复请求消息，或新的RRC连接公共请求消息，该RRC响应消息可以是RRC连接建立消息，RRC连接恢复消息，或新的RRC连接公共应答消息。本实施例中，即使UE没有发送过RRC请求消息，也可以处理RRC响应消息，
如图13所示，包括步骤1300至步骤1308。
在步骤1300中，基站通过系统消息下发上行授权门限T_ULgrant。
在步骤1301中，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤1302中，基站发送随机接入响应给UE。
在步骤1003中，UE发送第一请求消息(Msg3)时同时发送上行数据给基站。
UE在通过Msg3发送上行数据包的同时应携带核心网给UE分配的标识，例如S-TMSI，或能够标识UE所附着的MME的信息给基站；或者，携带恢复标识。
在步骤1304中，基站发送携带上行数据的第一SI接口消息至网络侧。
在步骤1305中，网络侧发送第二S1接口消息至基站。
在步骤1306中，基站发送第二响应消息(Msg4)至基站，携带RRC连接公共响应消息。该公共响应消息可以是已有的RRC连接建立消息，RRC连接恢复消息，或者新定义的RRC连接公共响应消息。
在步骤1307中，UE建立RRC连接，进入RRC_CONNECTED状态。
在步骤1308中，UE发送Msg5消息给基站。
实施例八
在某一覆盖等级下，如果UE尝试在发送第一请求消息的同时发送上行数据(第一格式Msg3)失败一定次数后，UE优先更换覆盖等级。当覆盖等级达到最大时，UE再转为尝试发送携带RRC消息的第一请求消息来建立或恢复RRC连接(第二格式Msg3)。或者，在某一覆盖等级下，如果UE尝试在发送第一请求消息的同时发送上行数据(第一格式)失败一定次数后，UE优先转为尝试发送携带RRC消息的第一请求消息来建立或恢复RRC连接(第二格式Msg3)，如果仍然失败，则UE根据配置的失败次数，达到失败次数就直接选择下一覆盖等级，在新的覆盖等级下，UE仍然按照上述顺序进行随机接入尝试。
基站可以在系统消息中广播操作指示信息。如果指示UE优先更换覆盖等级，可以指示UE在最大覆盖等级采用第二格式Msg3的尝试次数，或指示该尝试次数是否与采用第二格式Msg3的尝试次数相同。如果指示UE优先转为尝试另一格式Msg3，则可以指示在当前覆盖等级下每种格式的尝试次数，或指示每种格 式尝试次数在总的尝试次数中的占比。
在某一覆盖等级下，如果存在功率提升操作，在每次进行随机接入时，UE可以提前终止或暂停功率提升操作。例如，UE首先判断本次采用的Msg3格式与上次是否相同，根据判断结果来决定是否提前终止或暂停功率提升操作。一种调整功率提升操作的示例如下：
如果采用与上次不同的Msg3格式，不增加功率，或者，如果采用与上次不同的Msg3格式，且上次为第一格式Msg3，本次为第二格式Msg3，不增加功率。即提前终止或暂停功率提升过程。
或者，UE根据上次接入尝试的失败原因来决定是否提前终止或暂停功率提升操作。另一种调整功率提升操作的示例如下：
UE尝试采用第一格式Msg3失败后，UE根据失败原因来决定是否提前终止或暂停功率提升过程。如果出现某一类失败原因(例如冲突解决失败)，则UE不增加上行发射功率，而仅仅是作再次尝试。
当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀，用于请求发送上行数据的资源。当UE得到上行授权后，UE在随机接入过程中发送第一请求消息时直接发送上行数据给基站。
当UE在当前覆盖等级发送用于请求上行数据传输资源的随机接入前缀集合P1中选择的随机接入前缀，但是因为未能收到基站发来的第二响应消息(该第二响应消息应包含较大的UL grant以便UE在发送第一请求消息的同时发送上行数据且不进行状态转移)，或者在后续流程中冲突解决失败而导致本次随机接入尝试失败，则UE需要再次发起随机接入过程，此时UE需要重复发送P1中的随机接入前缀，当这种重复发送达到一定次数N1时，该次数N1为与当前覆盖等级相对应的预设值或由网络侧为UE配置，UE开始使用不用于请求上行数据传输资源的随机接入前缀集合P2中的随机接入前缀。如果发送P2中的随机接入前缀后，因为未能收到基站发来的第二响应消息(该第二响应消息应包含较小的UL grant以便UE发送包含RRC消息的第一请求消息来建立或恢复RRC连接)，或者在后续流程中冲突解决失败而导致本次随机接入尝试失败，则UE会重复发送该P2中的随机接入前缀，当这种重复发送达到一定次数N2时，该次数N2为与当前覆盖等级相对应的预设值或由网络侧为UE配置，UE则跳到下一覆盖等级，再次重复上述流程。
当终端使用随机接入前缀集合P1进行随机接入时，如果因为未收到随机接入响应而导致本次随机接入尝试失败，则UE标记失败原因S1，如果因为在后续流程中冲突解决失败而导致本次随机接入尝试失败，则UE标记失败原因S2。当UE出现原因为S1的失败时，终端再次使用P1中的随机接入前缀进行随机接入时，可以按照配置参数增加上行发射功率。但是当UE出现原因为S2的失败时，可能存在多个UE在尝试在发送第一请求消息的同时发送上行数据，系统负荷较重，此时如果仍然在重发时增加发射功率，可能导致系统冲突加剧，因此在下次尝试时，UE不增加上行发射功率，而仅仅是作再次尝试。
实施例九(并行的上行数据传输及RRC连接重建立过程)
当UE处于在RRC_CONNECTED状态，可能因RLF等原因触发RRC重建立过程，此时UE需要发起随机接入过程。当RRC重建立时可能有待传输或重传的上行数据，此时可以在重建立的同时发送上行数据，即执行并行的上行数据传输及RRC连接重建立过程。
如图14所示，为UE处于RRC_CONNECTED状态，使用CP方案在随机接入过程传输上行数据流程，包括步骤1401之步骤1406。
在步骤1401中，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤1402中，基站发送随机接入响应给UE。
在步骤1403中，UE发送第一请求消息(Msg3)给基站，携带RRC连接公共请求消息和上行数据；该RRC连接公共请求消息可以是已有的RRC连接重建立请求消息，也可以是新的RRC连接公共请求消息。
所述Msg3消息中还携带核心网给UE分配的标识，例如S-TMSI，或能够标识UE所附着的MME的信息给基站；例如GUMMEI步骤1404，基站发送携带上行数据的第一SI接口消息至网络侧。
在步骤1405中，网络侧发送第二S1接口消息至基站。
在步骤1406中，基站发送第二响应消息(Msg4)至终端，携带RRC连接公共响应消息。该RRC连接公共响应消息可以是已有的RRC连接重建立消息，也可以是新的RRC连接公共响应消息。
如图15所示，为使用UP方案在随机接入过程传输上行数据流程，包括步骤1501至步骤1506。
在步骤1501中，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤1502中，基站发送随机接入响应给UE。
在步骤1503中，UE发送第一请求消息(Msg3)给基站，携带RRC连接公共请求消息和上行数据；该RRC连接公共请求消息可以是已有的RRC连接重建立请求消息，也可以是新的RRC连接公共请求消息。
Msg3消息中还携带重建立终端标识(Reestablish-UEID)。
在步骤1504中，基站发送携带上行数据的第一SI接口消息至网络侧。
在步骤1505中，网络侧发送第二S1接口消息至基站。
在步骤1506中，基站发送第二响应消息(Msg4)至终端，携带RRC连接公共响应消息。该RRC连接公共响应消息可以是已有的RRC连接重建立消息，也可以是新的RRC连接公共响应消息。
实施例十(连接态发送上行数据后快速释放)
当UE处于在RRC_CONNECTED状态且有数据需要发送，且UE处于失步状态或没有上行资源时，UE需要发起随机接入过程。
如果UE发送用于请求发送上行数据的资源的随机接入前缀，且UE收到基站发送的随机接入响应并得到足够的上行授权，可以认为UE和基站协商尽快完成数据发送并可以发起快速RRC连接释放，UE将在发送第一请求消息时同时发送上行数据给基站。
如果UE发送不用于请求发送上行数据的资源的随机接入前缀，或者UE未得到基站足够的上行授权，可以认为UE发送普通的前缀(preamble)，然后触发完整的RRC连接建立流程，在连接建立完成后再传输数据。。
UE发送完第一请求消息及上行数据后，如果收到基站发送的第二响应消息并确定冲突解决成功，UE自主释放到RRC_IDLE状态。
UE发送第一请求消息及上行数据时，可以携带请求释放指示，比如BSR＝0，指示基站可以释放。基站收到第一请求消息及上行数据后，可以触发快速释放，在基站给UE发送的第二响应消息中携带RRC释放消息，该释放消息应以无线 链路控制应答模式(Radio Link Control Acknowledged Mode，RLC AM)模式发送。UE收到第二响应消息，首先确定冲突解决成功，之后处理RRC释放消息并对该消息发送ACK(Acknowledgement)确认，之后基站发送RRCConnectionRelease消息给终端，终端被释放到RRC_IDLE状态。如果冲突解决失败，则UE不会处理第二响应消息携带的RRC消息。与相关技术相比，相关技术中RRC释放消息只能通过SRB1发送，本申请中RRC释放消息可以通过SRB0发送。
基站通过系统消息广播针对空闲态和针对连接态的不同的上行授权门限，连接态应有更严格的上行授权门限，即该上行授权门限应保证当UE在连接态发起随机接入传数据时，应尽可能一次传完所有待传输数据并释放连接，连接态的上行授权门限大于空闲态的上行授权门限。
如图16所示，包括步骤1601至步骤1607。
在步骤1601中，UE在随机接入过程中发送随机接入前缀给基站，用于请求发送上行数据的资源。
在步骤1602中，基站发送随机接入响应给UE。
在步骤1603中，UE发送携带上行数据的第一请求消息(Msg3)给基站，携带请求释放指示，比如BSR＝0。
Msg3消息中还携带小区无线网络临时标识。
在步骤1604中，基站发送携带上行数据的第一SI接口消息至网络侧。
在步骤1605中，网络侧发送第二S1接口消息至基站。
在步骤1606中，基站发送第二响应消息(Msg4)至终端，携带RRC连接释放消息。
在步骤1607中，UE先处理Msg4，再处理连接释放消息，然后UE释放到RRC_IDLE状态。
实施例十一(非竞争接入Msg2携带下行数据)
当UE处于在RRC_CONNECTED状态时，如果网络侧有下行数据要发送给UE但发现UE处于非同步状态，则基站需要发送PDCCH命令(order)给UE来触发随机接入过程。
PDCCH order中包含基站分配给UE的非竞争资源，当UE使用该非竞争资 源对应的随机接入前缀发起随机接入时，基站查找到该UE的信息，则基站给UE发送随机接入响应，随机接入响应中包含指示，指示同时发送下行数据给UE，UE使用收到的下行授权去接收下行数据，之后UE可以发送第一请求消息给基站，包含对收到的下行数据的确认。UE需要优先处理追踪区(Tracking Area，TA)信息，完成同步过程，之后再处理下行数据包。
如图17所示，UE处于RRC_CONNECTED状态，包括步骤1701至步骤1706。
在步骤1700中，网络侧下发下行数据至基站。
在步骤1701中，基站发送PDCCH order给UE，携带基站分配给UE的非竞争资源。
在步骤1702中，UE发送该非竞争资源对应的随机接入前缀给基站。
在步骤1703中，基站发送随机接入响应给UE，同时下发所述下行数据，所述随机接入响应中携带指示信息，指示同时下发下行数据。
在步骤1704中，UE接收到所述随机接入响应后，使用收到的下行授权接收所述下行数据后，发送第一请求消息(Msg3)给基站，携带对所述下行数据的确认信息。
在步骤1705中，基站发送第一SI接口消息至网络侧，携带对所述下行数据的确认信息。
在步骤1706中，网络侧发送第二S1接口消息至基站。
实施例十二
当UE处于RRC_IDLE状态时，UE在随机接入过程中发送随机接入前缀，用于请求发送上行数据的资源。UE通过如下方式判定是否可以请求发送上行数据的资源。
基站配置针对每个覆盖等级的携带数据判决门限T_ULdataRA。当UE缓存的待发送UL数据大于或等于该携带数据判决门限时，UE在用于请求上行数据传输资源的随机接入前缀集合P1中选择一个随机接入前缀，当UE缓存的待发送UL数据小于该携带数据判决门限时，UE在非用于请求上行数据传输资源的随机接入前缀集合P2中选择一个随机接入前缀。
P1和P2通过如下方式划分：
方式1：选择不属于针对每个覆盖等级配置的PRACH资源的资源作为P1。
例如，基站为R15UE配置至少一组数据传输物理资源块(Physical Resource Block，PRB)资源，所有PRB不同于为R14 UE配置的物理随机接入信道/寻呼物理资源块(Physical Random Access Channel/paging Physical Resource Block，PRACH/paging PRB)作为P1，此时所有为R14 UE配置的PRACH/paging PRB可以视为P2。当配置多组数据传输PRB资源时，每组数据传输PRB资源用于指示某一上行数据大小需求。例如，配置三组数据传输PRB资源，分别标识为组A，组B，组C。每组数据传输PRB资源包含至少一个PRB，当UE选择组A中任一个PRB时，表示UE请求在发送第一请求消息时同时发送大小介于[DataSizeMinGroupA，DataSizeMaxGroupA]的上行数据；每个PRB下可以划分针对不同覆盖等级的PRACH时域和子载波(subcarrier)资源。
基站为R15UE配置所有未配置给R14 UE的subcarrier作为P1，且为R15UE配置的每个覆盖等级的PRACH资源中不再包含subcarrier资源，此时为R14 UE配置的subcarrier可以视为P2。P1中的subcarrier可以划分为至少一组数据传输subcarrier资源，配置三组数据传输subcarrier资源，分别标识为组A，组B，组C。每组数据传输subcarrier资源包含至少一个subcarrier，当UE选择组A中任一个subcarrier时，表示UE请求在发送第一请求消息时同时发送大小介于[DataSizeMinGroupA，DataSizeMaxGroupA]的上行数据；当R15UE选定subcarrier后，还需选定与其所处覆盖等级相应的PRACH资源。如图18所示，图18中CE1_CBRA_S标识覆盖等级1下用于指示单频(single-tone)方式传输Msg3的竞争随机接入资源，CE1_CBRA_M标识覆盖等级1下用于指示多品(multi-tone)方式传输Msg3的竞争随机接入资源，CE1_CFRA标识覆盖等级1的非竞争资源。CE2_CBRA标识覆盖等级2下所有竞争随机接入资源，CE2_CFRA标识覆盖等级2的非竞争资源。CE3_CBRA标识覆盖等级3下所有竞争随机接入资源，CE3_CFRA标识覆盖等级3的非竞争资源。
方式2：选择属于针对每个覆盖等级配置的物理随机接入信道(Physical Random Access Channel，PRACH)资源的某个资源作为P1。
例如，基站将每个覆盖等级下的非竞争资源内未使用的subcarrier资源划分成至少一组数据传输subcarrier资源：
虽然在R14的参数配置中，依靠(nprach-NumSubcarriers-nprach-NumCBRA-StartSubcarriers)计算得到的非竞争资源应是一段连续数值， 但是根据R14技术，UE和终端使用mod运算来保证更换覆盖等级后UE仍然使用基站可以获知的Subcarriers，这样实际使用的非竞争Subcarriers将是不连续的，因此基站有可能将每个覆盖等级下的非竞争资源内未使用的subcarrier资源配置为P1_CE1。见图19所示，图19中CE1_CBRA_S标识覆盖等级1下用于指示single-tone方式传输Msg3的竞争随机接入资源，CE1_CBRA_S标识覆盖等级1下用于指示multi-tone方式传输Msg3的竞争随机接入资源，CE1_CFRA标识覆盖等级1的非竞争资源。CE1_CFRA_A1～CE1_CFRA_A3分别标识覆盖等级1的非竞争资源中尚未给已有终端配置的资源，可配置为用于覆盖等级1的用于请求上行数据传输资源的随机接入资源。CE2_CBRA标识覆盖等级2的所有竞争资源。CE2_CFRA标识覆盖等级2的非竞争资源。CE3_CBRA_S标识覆盖等级3下用于指示single-tone方式传输Msg3的竞争随机接入资源，CE3_CBRA_M标识覆盖等级3下用于指示multi-tone方式传输Msg3的竞争随机接入资源.CE3_CFRA标识覆盖等级3的非竞争资源。P1 for all CEs(P1_CE1)标识所有子载波资源中尚未配置给已有终端的资源，可配置为用于所有覆盖等级的用于请求上行数据传输资源的随机接入资源。在一实施例中，所有覆盖等级下用于请求上行数据传输资源的随机接入资源的总和为：P1＝P1_CE1+P1_CE2+P1_CE3。
如果每个覆盖等级下的非竞争资源内不存在未使用的subcarrier资源，基站可以将每个覆盖等级下的非竞争资源都为R15UE配置为P1，前提是基站通过实现方式能够区分连接态UE发起的随机接入和空闲态UE发起的随机接入。如图20所示，图20中CE1_CBRA_S标识覆盖等级1下用于指示single-tone方式传输Msg3的竞争随机接入资源，CE1_CBRA_M标识覆盖等级1下用于指示multi-tone方式传输Msg3的竞争随机接入资源，CE1_CFRA标识覆盖等级1的非竞争资源。CE1_CFRA_A1～CE1_CFRA_A3分别标识覆盖等级1的非竞争资源中的部分资源，这部分资源已经配置给已有终端。如果基站可以区分已有终端和新终端，则这部分资源有可能配成可用于覆盖等级1的用于请求上行数据传输资源的随机接入资源。CE2_CBRA标识覆盖等级2下所有竞争随机接入资源。CE2_CFRA标识覆盖等级2的非竞争资源。CE3_CBRA_S标识覆盖等级3下用于指示single-tone方式传输Msg3的竞争随机接入资源，CE3_CBRA_M标识覆盖等级3下用于指示multi-tone方式传输Msg3的竞争随机接入资源.CE3_CFRA标识覆盖等级3的非竞争资源。
基站将每个覆盖等级下的竞争资源中的为Multi-tone Msg3配置的subcarrier资源划分成至少一组数据传输subcarrier资源。如图21所示，图21中CE1_CBRA_S标识覆盖等级1下用于指示single-tone方式传输Msg3的竞争随机接入资源，CE1_CBRA_M标识覆盖等级1下用于指示multi-tone方式传输Msg3的竞争随机接入资源，CE1_CFRA标识覆盖等级1的非竞争资源。CE2_CBRA标识覆盖等级2下所有竞争随机接入资源，CE2_CFRA标识覆盖等级2的非竞争资源。CE3_CBRA_S标识覆盖等级3下用于指示single-tone方式传输Msg3的竞争随机接入资源，CE3_CBRA_M标识覆盖等级1下用于指示multi-tone方式传输Msg3的竞争随机接入资源。CE3_CFRA标识覆盖等级3的非竞争资源。CE3_CBRA_A1～CE3_CBRA_A3表示从CE3_CBRA_M中配置部分资源用于标识可用于覆盖等级3的用于请求上行数据传输资源的随机接入资源。
只有支持multi-tone Msg3传输的UE才允许在发送第一请求消息的同时发送上行数据。
本申请一实施例提供一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述任一实施例所述的数据传输方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现上述任一实施例所述的数据传输方法。
所述计算机可读存储介质包括：U盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、移动硬盘、磁碟或者光盘等多种可以存储程序代码的介质。

Claims (60)

  1. 一种数据传输方法，包括：
    终端发送随机接入前缀给基站，并接收所述基站发送的随机接入响应；
    所述终端发送携带上行数据的第一请求消息至所述基站。
  2. 如权利要求1所述的数据传输方法，所述终端在发送所述随机接入前缀前为空闲态时，所述方法还包括：
    所述终端接收所述基站返回的第二响应消息，判断冲突解决成功后，所述终端维持在空闲态，且将所述随机接入响应中携带的由所述基站分配的临时无线网络临时标识作为小区无线网络临时标识，将所述小区无线网络临时标识保留第一时长。
  3. 如权利要求1所述的数据传输方法，其中，第二响应消息中携带以下至少之一：
    冲突解决标识；对所述上行数据的高层确认信息；上行数据失败指示；上行数据重传指示；以及用户业务数据。
  4. 如权利要求1所述的数据传输方法，其中，所述第一请求消息中还携带如下之一或其组合：
    是否需要优先建立S1接口的指示信息；是否需要接收所述上行数据的高层确认信息的指示信息；用于识别所述终端所注册的移动性管理实体的信息；终端识别信息；接入层安全信息；以及对应于数据传输的连接建立原因。
  5. 如权利要求2所述的数据传输方法，所述终端接收到所述基站返回的第二响应消息且获得所述小区无线网络临时标识后，还包括：
    所述终端在公共搜索空间，或传输第二响应消息调度信息的搜索空间，使用所述小区无线网络临时标识检测以下之一：
    物理下行控制信道，上行调度信息，以及下行调度信息。
  6. 如权利要求1所述的数据传输方法，其中，所述终端发送随机接入前缀给基站包括：
    当所述终端满足第一预设条件时，所述终端发送用于请求上行数据传输资源的随机接入前缀给所述基站。
  7. 如权利要求6所述的数据传输方法，其中，所述终端发送用于请求上行数据传输资源的随机接入前缀给基站包括：
    所述终端在用于请求上行数据传输资源的随机接入前缀集合中选择一个随 机接入前缀，将所选的随机接入前缀发送给所述基站；或者，
    所述终端在用于请求上行数据传输资源的随机接入资源集合中选择一个随机接入资源，使用所选的随机接入资源将随机接入前缀发送给所述基站。
  8. 如权利要求6所述的数据传输方法，其中，所述终端满足第一预设条件包括以下之一或其组合：
    所述终端待发送的上行数据大于携带数据判决门限；
    所述终端的无线链路条件满足链路条件门限；以及
    所述终端待发送的上行数据的业务类型属于预设业务类型。
  9. 如权利要求6所述的数据传输方法，所述方法还包括，所述终端从基站发送的系统消息中获取所述如下之一或其组合：
    携带数据判决门限；
    链路条件门限；以及
    预设业务类型信息；
    其中，所述携带数据判决门限包括：配置给全部覆盖等级的一个携带数据门限，或者每个覆盖等级分别配置的携带数据判决门限。
  10. 如权利要求1所述的数据传输方法，所述方法还包括以下之一：
    所述终端未接收到所述基站返回的第二响应消息；，
    所述终端接收到的所述基站返回的第二响应消息且所述第二响应消息中携带上行数据失败指示或上行数据重传指示；以及
    所述终端未接收到所述基站返回的随机接入响应时，本次随机接入失败，所述终端重新发起随机接入。
  11. 如权利要求10所述的数据传输方法，其中，所述终端重新发起随机接入包括：
    所述终端根据以下至少之一确定，选择用于请求上行数据传输资源的随机接入前缀进行随机接入，或者选择非用于请求上行数据传输资源的随机接入前缀进行随机接入：
    随机接入的失败次数；随机接入的失败次数序号；终端获得的下行测量值；覆盖等级；以及重复次数。
  12. 如权利要求10所述的数据传输方法，所述终端按如下方式之一重新发起随机接入：
    在当前覆盖等级下，所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端更换覆盖等级至最大覆盖等级后，发送非用于请求上行数据传输资源的随机接入前缀或者发送随机接入前缀进行随机接入；
    在当前覆盖等级下，所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端发送非用于请求上行数据传输资源的随机接入前缀或者发送随机接入前缀进行随机接入；如果仍然失败且失败次数到达对应的失败次数阈值时，所述终端更换至大于当前覆盖等级的下一覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在该覆盖等级进行随机接入，直到随机接入成功，或者所述终端到达最大覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在最大覆盖等级下进行随机接入；
    在当前覆盖等级下，所述终端在所述第一请求消息中携带上行数据进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端更换覆盖等级至最大覆盖等级后，发送携带无线资源控制消息的第一请求消息进行随机接入；
    在当前覆盖等级下，所述终端在所述第一请求消息中携带上行数据进行随机接入失败的失败次数到达对应的失败次数阈值时，所述终端发送携带无线资源控制消息的第一请求消息进行随机接入；如果仍然失败且失败次数到达对应的失败次数阈值时，所述终端更换至大于当前覆盖等级的下一覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在该覆盖等级进行随机接入，直到随机接入成功，或者所述终端到达最大覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在最大覆盖等级下进行随机接入；
    所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值时，发送非用于请求上行数据传输资源的随机接入前缀进行随机接入；
    所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值，并且终端测量的参考信号接收功率值在第一预定义范围时，所述终端发送非用于请求上行数据传输资源的随机接入前缀进行随机接入；所述终端在所述发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败的失败次数到达对应的失败次数阈值，并且终端测 量的参考信号接收功率值在第二预定义范围时，所述终端更换至下一覆盖等级，发送用于请求上行数据传输资源的随机接入前缀进行随机接入；
    所述终端在发送用于请求上行数据传输资源的随机接入前缀进行随机接入失败后，发送非用于请求上行数据传输资源的随机接入前缀，以及，所述终端在所述发送非用于请求上行数据传输资源的随机接入前缀进行随机接入失败后，发送用于请求上行数据传输资源的随机接入前缀进行随机接入；重复前面方式，当接入失败次数到达对应的失败次数阈值时，所述终端更换至下一覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在该覆盖等级进行随机接入，直到随机接入成功，或者所述终端到达最大覆盖等级，按照与之前的覆盖等级下相同的随机接入方式在最大覆盖等级下进行随机接入。
  13. 如权利要求12所述的数据传输方法，所述方法还包括：
    所述终端通过接收所述基站广播的系统消息或所述基站发送给所述终端的专用消息，获取每个覆盖等级对应的失败次数阈值。
  14. 如权利要求1或12所述的数据传输方法，在所述终端重新发起随机接入前，还包括：
    所述终端从所述基站获取操作指示信息，根据所述操作指示信息确定重新发起随机接入的方式。
  15. 如权利要求1或12所述的数据传输方法，在所述终端进行随机接入之前，根据如下至少之一决定是否终止或暂停功率提升操作：
    本次随机接入的第一请求消息的格式与前一次进行随机接入时的第一请求消息的格式是否相同；
    本次随机接入发送随机接入前缀的方式与前一次进行随机接入时发送随机接入前缀的方式是否相同；其中，所述发送随机接入前缀的方式包括：发送用于请求上行数据传输资源的随机接入前缀和发送非用于请求上行数据传输资源的随机接入前缀；以及
    前一次进行随机接入时的失败原因。
  16. 如权利要求1所述的数据传输方法，其中，所述终端在发送所述随机接入前缀前为连接态时，所述第一请求消息中还携带如下之一或其组合：
    小区无线网络临时标识、无线资源控制消息以及请求释放指示。
  17. 如权利要求16所述的数据传输方法，所述终端在发送所述随机接入前缀前为连接态时，还包括：
    所述终端接收所述基站返回的第二响应消息，在判断冲突解决成功后，所述终端自主释放无线资源控制连接，并转移到空闲态；
    或者，所述终端接收所述基站返回的第二响应消息，在判断冲突解决成功后，所述终端处理所述第二响应消息中携带的无线资源控制释放消息，并转移到空闲态。
  18. 如权利要求1所述的数据传输方法，其中，所述终端发送携带上行数据的第一请求消息至所述基站包括：
    所述终端获取所述随机接入响应中携带的指示信息，当满足第二预设条件时，所述终端发送携带所述上行数据的第一请求消息至所述基站。
  19. 如权利要求1或18所述的数据传输方法，所述方法还包括：
    所述终端获取所述随机接入响应中携带的指示信息，当满足第三预设条件时，所述终端发送携带无线资源控制消息的第一请求消息至所述基站。
  20. 如权利要求19所述的数据传输方法，其中，
    所述满足第二预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息大于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时直接发送上行数据；
    所述满足第三预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息小于等于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时携带无线资源控制消息。
  21. 如权利要求20所述的数据传输方法，其中，所述上行授权门限为所述终端在发送所述随机接入前缀前的状态所对应的上行授权门限；或者为所述终端在发送所述随机接入前缀前的状态及所在覆盖等级所对应的上行授权门限。
  22. 如权利要求20所述的数据传输方法，其中，与连接态终端对应的上行授权门限大于与空闲态终端对应的上行授权门限。
  23. 如权利要求1至13任一所述的数据传输方法，所述方法还包括：
    所述终端接收到所述基站返回的第二响应消息后，根据所述第二响应消息中携带的无线资源控制响应消息建立无线资源控制连接，或者恢复无线资源控制连接，或者重建立无线资源控制连接，所述终端转移到连接态。
  24. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求1至23任一所述的数据传输方法。
  25. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求1至23任一所述的数据传输方法。
  26. 一种数据传输方法，包括：
    基站接收终端发送的随机接入前缀，并发送随机接入响应至所述终端；
    所述基站接收所述终端发送的携带上行数据的第一请求消息。
  27. 如权利要求26所述的数据传输方法，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括，所述基站发送第二响应消息给所述终端，所述第二响应消息中携带如下信息之一或其组合：
    冲突解决标识；对所述上行数据的高层确认信息；上行数据发送失败指示；上行数据重传指示；以及用户业务数据。
  28. 如权利要求26所述的数据传输方法，其中，所述第一请求消息中还携带如下之一或其组合：
    优先建立S1接口的指示信息；需要接收所述上行数据的高层确认信息的指示信息；终端识别信息；用于识别终端所注册的移动性管理实体的信息；接入层安全信息；以及对应于数据传输的连接建立原因。
  29. 如权利要求28所述的数据传输方法，所述方法还包括：
    当所述第一请求消息中携带优先建立S1接口的指示信息，或者携带需要接收所述上行数据的高层确认信息的指示信息时，所述基站发送携带所述上行数据的第一S1接口消息给网络侧；
    所述基站接收所述网络侧返回的第二S1接口消息，所述基站如果从所述第二S1接口消息中获取到高层确认信息，则将所述高层确认信息发送给所述终端。
  30. 如权利要求29所述的数据传输方法，所述方法还包括：
    所述基站在所述第二S1接口消息中收到下行数据时，所述基站将所述下行数据发送给所述终端。
  31. 如权利要求29或30所述的数据传输方法，其中，
    所述第一S1接口消息为如下之一：初始用户设备信息消息，用户设备上下 文恢复请求消息，上行链路非接入层传输消息，路径切换请求消息，以及新定义的S1接口消息；
    所述第二S1接口消息为如下之一：连接建立指示消息，用户设备上下文恢复响应消息，下行链路非接入层传输消息，路径切换请求确认消息，以及新定义的S1接口消息。
  32. 如权利要求26所述的数据传输方法，所述方法还包括：
    所述基站通过系统消息或专用消息发送操作指示信息给所述终端，所述操作指示信息用于指示所述终端在随机接入失败后重新进行随机接入的方式。
  33. 如权利要求32所述的数据传输方法，其中，所述重新进行随机接入的方式包括如下之一：
    优先更换覆盖等级重新进行随机接入；
    优先发送非用于请求上行数据传输资源的随机接入前缀或者发送随机接入前缀重新进行随机接入；以及
    优先发送携带无线资源控制消息的第一请求消息重新进行随机接入。
  34. 如权利要求26至30任一所述的数据传输方法，所述终端处于连接态且所述第一请求消息中还携带无线资源控制消息时，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：
    所述基站发送第二响应消息给所述终端，所述第二响应消息中携带无线资源控制重建立消息。
  35. 如权利要求26至30任一所述的数据传输方法，所述终端处于连接态且所述第一请求消息中还携带请求释放指示时，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：
    所述基站发送第二响应消息给所述终端，所述第二响应消息中携带无线资源控制释放消息。
  36. 如权利要求26至30任一所述的数据传输方法，其中，所述方法还包括：
    所述基站通过系统消息或专用消息下发携带数据判决门限给所述终端；
    其中，所述携带数据判断门限用于所述终端判断，在用于请求上行数据传输资源的随机接入前缀集合中，或者在非用于请求上行数据传输资源的随机接入前缀集合中选择发送给所述基站的随机接入前缀；或者，所述携带数据判断 门限用于所述终端判断，在用于请求上行数据传输资源的随机接入资源集合中，或者在非用于请求上行数据传输资源的随机接入资源集合中选择随机接入资源来发送给所述基站的随机接入前缀；
    其中，所述携带数据判决门限包括：配置给全部覆盖等级的一个携带数据门限，或者每个覆盖等级分别配置的携带数据判决门限。
  37. 如权利要求26至30任一所述的数据传输方法，其中，
    所述随机接入响应中携带指示信息，所述指示信息指示所述终端发送第一请求消息的发送方式；
    所述基站接收所述终端发送的携带上行数据的第一请求消息包括：
    当满足第二预设条件时，所述基站接收所述终端发送的携带上行数据的第一请求消息；
    当满足第三预设条件时，所述基站接收所述终端发送的携带无线资源控制消息的第一请求消息。
  38. 如权利要求37所述的数据传输方法，其中，
    所述满足第二预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息大于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时直接发送上行数据；
    所述满足第三预设条件为：所述指示信息为上行授权的数据量信息，所述上行授权的数据量信息小于等于上行授权门限；或者所述指示信息指示所述终端在发送第一请求消息时携带无线资源控制消息。
  39. 如权利要求38所述的数据传输方法，其中，所述上行授权门限为：所述终端在发送所述随机接入前缀前的状态所对应的上行授权门限；或者所述上行授权门限为：所述终端在发送所述随机接入前缀前的状态及所在覆盖等级所对应的上行授权门限。
  40. 如权利要求38所述的数据传输方法，其中，与连接态终端对应的上行授权门限大于与空闲态终端对应的上行授权门限。
  41. 如权利要求26至30任一所述的数据传输方法，所述终端为空闲态时，所述基站接收所述终端发送的携带上行数据的第一请求消息后，还包括：
    所述基站发送第二响应消息给所述终端，所述第二响应消息中携带无线资源控制响应消息。
  42. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求26至41任一所述的数据传输方法。
  43. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求26至41任一所述的数据传输方法。
  44. 一种数据传输方法，包括：
    终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
  45. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，执行如下操作：
    在终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息后，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
  46. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如下步骤：
    在终端处于空闲态时，在随机接入过程中，向基站发送第一请求消息后，接收所述基站发送的第二响应消息，从所述第二响应消息中获取下行数据。
  47. 一种数据传输方法，包括：
    在终端处于空闲态进行随机接入的过程中，基站接收终端发送的第一请求消息，如果基站有需要发送给所述终端的下行数据，所述基站发送第二响应消息给所述终端时携带所述下行数据。
  48. 如权利要求47所述的数据传输方法，所述方法还包括；
    在所述终端处于空闲态发起随机接入之前，所述基站收到网络侧发送的需要发送给所述终端的下行数据时，缓存该下行数据。
  49. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求47或48所述的数据传输方法。
  50. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求47或48所述的数据传输方法。
  51. 一种数据传输方法，包括：
    在终端处于空闲态进行随机接入的过程中，网络侧接收到基站发送的第一S1接口消息后，向所述基站发送第二S1接口消息，所述第二S1接口消息中携带需要发送给所述终端的下行数据。
  52. 如权利要求51所述的所述方法，所述方法还包括：
    在所述终端处于空闲态发起随机接入之前，所述网络侧收到应用层发送的需要发送给所述终端的下行数据，缓存该下行数据。
  53. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求51或52所述的数据传输方法。
  54. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求51或52所述的数据传输方法。
  55. 一种数据传输方法，包括：
    终端处于连接态时，所述终端接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述非竞争资源对应的随机接入前缀发起随机接入；
    所述终端接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，所述终端接收下行数据。
  56. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，执行如下操作：
    在终端处于连接态时，所述终端接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述非竞争资源对应的随机接入前缀发起随机接入；
    所述终端接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，接收所述下行数据。
  57. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如下步骤：
    在终端处于连接态时，接收基站发送的物理下行控制信道命令，从所述物理下行控制信道命令中获取所述基站分配给所述终端的非竞争资源，使用所述 非竞争资源对应的随机接入前缀发起随机接入；
    接收所述基站发送的随机接入响应，当所述随机接入响应中携带同时下发下行数据的指示信息时，接收下行数据。
  58. 一种数据传输方法，包括：
    在终端处于连接态时，基站发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带所述基站分配给所述终端的非竞争资源；
    所述基站接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
  59. 一种数据传输装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，执行如下操作：
    在终端处于连接态时，发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带所述基站分配给所述终端的非竞争资源；
    接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
  60. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如下步骤：
    在终端处于连接态时，发送物理下行控制信道命令给所述终端，所述物理下行控制信道命令中携带所述基站分配给所述终端的非竞争资源；
    接收到所述终端使用所述非竞争资源对应的随机接入前缀发起的随机接入后，发送随机接入响应给所述终端，所述随机接入响应中携带同时下发下行数据的指示信息，同时下发下行数据。
PCT/CN2018/100247 2017-08-11 2018-08-13 一种数据传输方法及装置、计算机可读存储介质 WO2019029747A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP18845080.3A EP3668190A4 (en) 2017-08-11 2018-08-13 METHOD AND DEVICE FOR DATA TRANSFER AND COMPUTER-READABLE STORAGE MEDIUM
US16/638,311 US11357054B2 (en) 2017-08-11 2018-08-13 Data transmission method and apparatus, and computer readable storage medium
US17/738,180 US11751255B2 (en) 2017-08-11 2022-05-06 Data transmission method in a wireless communication network
US18/223,753 US20230363009A1 (en) 2017-08-11 2023-07-19 Data transmission method and apparatus, and computer readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710687283.5A CN109392061B (zh) 2017-08-11 2017-08-11 一种数据传输方法及装置、计算机可读存储介质
CN201710687283.5 2017-08-11

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/638,311 A-371-Of-International US11357054B2 (en) 2017-08-11 2018-08-13 Data transmission method and apparatus, and computer readable storage medium
US17/738,180 Continuation US11751255B2 (en) 2017-08-11 2022-05-06 Data transmission method in a wireless communication network

Publications (1)

Publication Number Publication Date
WO2019029747A1 true WO2019029747A1 (zh) 2019-02-14

Family

ID=65270910

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/100247 WO2019029747A1 (zh) 2017-08-11 2018-08-13 一种数据传输方法及装置、计算机可读存储介质

Country Status (4)

Country Link
US (3) US11357054B2 (zh)
EP (1) EP3668190A4 (zh)
CN (2) CN115297535A (zh)
WO (1) WO2019029747A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113518467A (zh) * 2020-04-10 2021-10-19 大唐移动通信设备有限公司 数据传输方法、装置及终端
US20220086878A1 (en) * 2019-05-31 2022-03-17 Huawei Technologies Co., Ltd. Uplink scheduling method and apparatus, network device, and readable storage medium

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115297535A (zh) * 2017-08-11 2022-11-04 中兴通讯股份有限公司 一种数据传输方法及装置、计算机可读存储介质
US11291042B2 (en) * 2017-09-29 2022-03-29 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for configuring random access
CN109756991B (zh) * 2017-11-06 2021-11-19 华为技术有限公司 通信方法及装置
US11240849B2 (en) * 2017-11-24 2022-02-01 Sony Group Corporation Early data transmission in a random access procedure
US11197324B2 (en) * 2018-02-23 2021-12-07 Qualcomm Incorporated NR RACH MSG3 and MSG4 resource configuration for CV2X
CN110708750B (zh) * 2018-07-09 2021-06-22 华为技术有限公司 一种功率调整方法、终端及存储介质
JP7209332B2 (ja) * 2018-08-30 2023-01-20 パナソニックＩｐマネジメント株式会社 無線通信システム、基地局および無線通信方法
WO2020067970A1 (en) * 2018-09-24 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Early mobile-terminated data transmission
US11259331B2 (en) 2018-09-27 2022-02-22 Ofinno, Llc RACH type switching
TWI704826B (zh) * 2018-09-28 2020-09-11 財團法人資訊工業策進會 用於行動通訊系統之使用者裝置及基地台
US20200404541A1 (en) * 2019-06-19 2020-12-24 Qualcomm Incorporated System and method for flow control and acknowledgement transmission
CN112291848B (zh) * 2019-07-23 2023-09-26 上海华为技术有限公司 一种终端能力配置的方法及通信装置
WO2021022529A1 (zh) * 2019-08-07 2021-02-11 Oppo广东移动通信有限公司 通信方法和通信装置
CN110536472A (zh) * 2019-08-08 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置及计算机可读存储介质
WO2021028031A1 (en) * 2019-08-14 2021-02-18 Nokia Technologies Oy Apparatus, method, and computer program
WO2021031108A1 (en) * 2019-08-20 2021-02-25 Qualcomm Incorporated Mobile-originated data over dedicated preconfigured uplink resource while in an idle mode or an inactive mode
WO2021179178A1 (zh) * 2020-03-10 2021-09-16 北京小米移动软件有限公司 数据传输方法、装置及存储介质
CN112075118B (zh) * 2020-08-05 2024-06-21 北京小米移动软件有限公司 随机接入的方法、装置、设备及存储介质
CN112055324B (zh) * 2020-08-26 2023-08-18 陈一丰 一种用于物联网的番茄种植大棚温度控制方法及系统
CN116530204A (zh) * 2020-08-31 2023-08-01 欧芬诺有限责任公司 小数据传输的后续数据信息
CN114340044A (zh) * 2020-10-10 2022-04-12 展讯通信（上海）有限公司 物理层标识管理方法与装置、终端和管理设备
CN114599114A (zh) * 2020-12-07 2022-06-07 上海朗帛通信技术有限公司 一种被用于中继无线通信中的方法和装置
US20240049331A1 (en) * 2020-12-15 2024-02-08 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for transmitting data, communication device, and storage medium
CN114828269A (zh) * 2021-01-21 2022-07-29 大唐移动通信设备有限公司 数据传输方法及装置、终端、接入网设备
CN113260085B (zh) * 2021-06-21 2021-11-09 北京智联安科技有限公司 一种提高上行数据传输效率的方法及装置
CN114374962B (zh) * 2022-01-18 2024-04-09 亿咖通(湖北)技术有限公司 自组网的通信方法、终端、车辆及存储介质
CN117793941B (zh) * 2024-02-26 2024-06-18 深圳国人无线通信有限公司 随机接入场景中优化基站与终端通信连接的方法和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101873707A (zh) * 2009-04-24 2010-10-27 大唐移动通信设备有限公司 下行数据调度方法及系统
CN101932117A (zh) * 2009-06-20 2010-12-29 中兴通讯股份有限公司 中继节点的随机接入方法
CN101953185B (zh) * 2009-04-08 2015-05-06 华为技术有限公司 小区信息的传递方法、网络设备和系统
CN106465401A (zh) * 2014-02-28 2017-02-22 Lg电子株式会社 在无线通信系统中发送具有低延迟的上行链路数据的方法和设备

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2427005B1 (en) * 2009-04-27 2017-11-15 Huawei Technologies Co., Ltd. Judging method, device and system of random access contention resolution
CN101895986A (zh) * 2009-05-21 2010-11-24 中兴通讯股份有限公司 本地ip接入中实现寻呼的方法及系统
CN102055700B (zh) * 2009-10-28 2015-06-03 中兴通讯股份有限公司 载波聚合中分量载波配置的方法及装置
CN102083228B (zh) 2010-02-11 2015-05-20 电信科学技术研究院 一种中继系统的随机接入方法和设备
CN102917468A (zh) * 2011-08-01 2013-02-06 中兴通讯股份有限公司 非冲突随机接入的方法及系统、网络侧网元、用户设备
US8718667B2 (en) * 2011-08-05 2014-05-06 Apple, Inc. Adaptive random access channel retransmission
CN102300331B (zh) * 2011-08-19 2013-11-27 电信科学技术研究院 数据传输方法和设备
US9001720B2 (en) * 2011-08-31 2015-04-07 Maarten Menzo Wentink Power save with data fetch time, with end of data indication, and with more data acknowledgement
US9338681B2 (en) * 2012-08-10 2016-05-10 Industrial Technology Research Institute Method for reporting minimization drive test measurement data
US9125112B2 (en) * 2013-08-06 2015-09-01 Blackberry Limited Communicating radio resource configuration information
KR101851490B1 (ko) * 2014-07-08 2018-04-23 엘지전자 주식회사 무선랜에서 다른 bss에서 전송된 프레임을 기반으로 파워 세이브 모드로 동작하는 방법 및 장치
US9723651B2 (en) * 2014-11-10 2017-08-01 Qualcomm Incorporated Enhanced connection management for multiple access networks
JP6961484B2 (ja) * 2015-08-13 2021-11-05 株式会社Ｎｔｔドコモ 端末、無線通信方法及びシステム
EP4164316B1 (en) * 2015-09-25 2024-07-24 Telefonaktiebolaget LM Ericsson (publ) Methods providing ul grants including time domain configuration and related wireless terminals and network nodes
WO2018185654A1 (en) * 2017-04-03 2018-10-11 Telefonaktiebolaget Lm Ericsson (Publ) Transmission of early data in message 3 (msg3) via a dual grant
EP3607801B1 (en) * 2017-04-04 2021-12-22 LG Electronics Inc. Apparatus and method for performing a random access procedure
US10397833B2 (en) * 2017-07-27 2019-08-27 Lg Electronics Inc. Method and apparatus for performing EDT
US11350445B2 (en) * 2017-08-10 2022-05-31 Kyocera Corporation Communication control method for controlling a user equipment to perform early data transmission
CN115297535A (zh) * 2017-08-11 2022-11-04 中兴通讯股份有限公司 一种数据传输方法及装置、计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101953185B (zh) * 2009-04-08 2015-05-06 华为技术有限公司 小区信息的传递方法、网络设备和系统
CN101873707A (zh) * 2009-04-24 2010-10-27 大唐移动通信设备有限公司 下行数据调度方法及系统
CN101932117A (zh) * 2009-06-20 2010-12-29 中兴通讯股份有限公司 中继节点的随机接入方法
CN106465401A (zh) * 2014-02-28 2017-02-22 Lg电子株式会社 在无线通信系统中发送具有低延迟的上行链路数据的方法和设备

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220086878A1 (en) * 2019-05-31 2022-03-17 Huawei Technologies Co., Ltd. Uplink scheduling method and apparatus, network device, and readable storage medium
EP3965512A4 (en) * 2019-05-31 2022-07-06 Huawei Technologies Co., Ltd. UPLINK PLANNING METHOD AND DEVICE, NETWORK DEVICE AND READABLE STORAGE MEDIA
US12101764B2 (en) * 2019-05-31 2024-09-24 Huawei Technologies Co., Ltd. Uplink scheduling method and apparatus, network device, and readable storage medium
CN113518467A (zh) * 2020-04-10 2021-10-19 大唐移动通信设备有限公司 数据传输方法、装置及终端
CN113518467B (zh) * 2020-04-10 2024-04-16 大唐移动通信设备有限公司 数据传输方法、装置及终端

Also Published As

Publication number Publication date
US11751255B2 (en) 2023-09-05
CN115297535A (zh) 2022-11-04
EP3668190A4 (en) 2021-08-18
US20200229235A1 (en) 2020-07-16
CN109392061B (zh) 2022-08-09
EP3668190A1 (en) 2020-06-17
US20220264657A1 (en) 2022-08-18
CN109392061A (zh) 2019-02-26
US11357054B2 (en) 2022-06-07
US20230363009A1 (en) 2023-11-09

Similar Documents

Publication Publication Date Title
US11751255B2 (en) Data transmission method in a wireless communication network
CN110476474B (zh) 用于执行随机接入过程的设备和方法
KR101616605B1 (ko) 멀티캐리어 무선 통신에서의 임의 접속을 위한 방법 및 장치
CN109587769B (zh) 一种数据传输方法及装置、搜索空间优化方法及装置
RU2768363C2 (ru) Способ передачи данных и устройство
JP6074053B2 (ja) 無線通信システムにおけるバックオフを実行する方法及び装置
KR101449823B1 (ko) 무선 통신 시스템에서 랜덤접속 절차를 수행하는 방법 및 장치
WO2018166331A1 (zh) 一种资源分配方法和装置以及终端设备
KR101789327B1 (ko) 무선 통신 시스템에서 상향링크 전송방법 및 장치
CN110945957A (zh) 执行随机接入过程的方法和装置
TWI430693B (zh) 隨機存取通道最佳化的方法及其相關通訊裝置
KR20160002983A (ko) 무선 통신 시스템에서 랜덤 액세스 절차를 수행하기 위한 방법 및 장치
TW201507424A (zh) 雙連結中分配無線網路暫時識別的方法
US20230105318A1 (en) Method and apparatus for performing communication in wireless communication system
WO2010127520A1 (zh) 随机接入方法以及基站
CN116368920A (zh) 用于在小数据传输期间处理非小数据传输无线电承载的方法及其装置
WO2021023311A1 (zh) 数据传输方法、装置及计算机可读存储介质
KR20090043434A (ko) 무선통신 시스템에서 랜덤 액세스 과정 수행 방법
CN109587766B (zh) 按需系统信息请求响应、接收方法及装置、基站
WO2019062582A1 (zh) 一种信息获取方法及终端
US12114390B2 (en) Method and apparatus for handling random access failures in RRC inactive state
JP6446710B2 (ja) 基地局装置、端末装置、無線通信方法および集積回路

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18845080

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018845080

Country of ref document: EP

Effective date: 20200311