WO2018059438A1 - 消息传输方法、设备和*** - Google Patents

消息传输方法、设备和*** Download PDF

Info

Publication number
WO2018059438A1
WO2018059438A1 PCT/CN2017/103661 CN2017103661W WO2018059438A1 WO 2018059438 A1 WO2018059438 A1 WO 2018059438A1 CN 2017103661 W CN2017103661 W CN 2017103661W WO 2018059438 A1 WO2018059438 A1 WO 2018059438A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc
message
downlink message
uplink
downlink
Prior art date
Application number
PCT/CN2017/103661
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 EP17854888.9A priority Critical patent/EP3512290B1/en
Publication of WO2018059438A1 publication Critical patent/WO2018059438A1/zh
Priority to US16/370,675 priority patent/US20190230732A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • 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/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side
    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • Embodiments of the present application relate to the field of communications, and more particularly, to a message transmission method, apparatus, and system.
  • a user equipment enters a connection state from an idle (IDLE) state, and needs to perform a radio resource control (RRC) connection establishment process and a connection recovery process. , the connection rebuild process or the connection reconfiguration process.
  • RRC radio resource control
  • the random access procedure is initialized, and the UE selects a physical random access channel (PRACH) resource and a corresponding sequence (Preamble) code;
  • PRACH physical random access channel
  • Preamble sequence
  • the network device processes and receives the Preamble
  • the network device replies to a random access response (RAR) message
  • the UE receives the RAR message and processes it, and the RAR message includes the uplink grant (UL Grant) of the next uplink message.
  • UL Grant uplink grant
  • the UE sends an RRC Connection Resume Request message on the UL Grant
  • the network device processes after receiving the RRC Connection Resume Request message
  • the UE receives the RRC Connection Resume message and processes it;
  • the UE transmits an RRC Connection Resume Complete message.
  • the RRC connection establishment process, the RRC connection reconfiguration process, and the RRC connection reestablishment process of the LTE are similar to the above process, except that the specific message is a message related to the connection process or connection reestablishment.
  • the RRC protocol of LTE stipulates that the processing delay of the RRC Connection Resume message received by the UE in step 9 is 15 ms, and the control plane delay of the 5G request from the IDLE state to the CONNECTED state is 10 ms, and the RRC connection recovery process of the current LTE, RRC The connection establishment process, the RRC connection reconfiguration process, or the RRC connection reestablishment process are all not satisfying the 5G delay requirement.
  • the embodiment of the present invention provides a message transmission method, device, and system, which can reduce the delay between receiving an RRC downlink message and feeding back an RRC uplink response message, so that the control plane delay can meet a shorter delay requirement.
  • a message transmission method includes: transmitting an RRC downlink message; pre-allocating and transmitting an RRC uplink response message corresponding to the RRC downlink message in a time range of an RRC process delay of the RRC downlink message.
  • Uplink authorization receiving, on the uplink resource indicated by the uplink grant, the RRC uplink response message sent by the UE from the RRC layer.
  • the sending time of the uplink grant is after the sending time of the RRC downlink message
  • the sending time of the uplink grant is no later than the acknowledgement message of the RRC downlink message. Receive time.
  • the acknowledgement message of the RRC downlink message is the media access control MAC layer.
  • the feedback message; or, when the RRC downlink message is sent in the acknowledge mode AM, the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the uplink authorization of the RRC uplink response message corresponding to the RRC downlink message is pre-allocated and sent in the time range of the RRC process delay of the RRC downlink message.
  • the uplink grant is sent in a physical layer downlink control channel PDCCH that transmits a downlink resource allocation of the RRC downlink message.
  • the uplink authorization of the RRC uplink response message corresponding to the RRC downlink message is pre-allocated and sent in the time range of the RRC process delay of the RRC downlink message.
  • the uplink grant is sent in a message packet that sends the RRC downlink message.
  • the specific implementation is: the message packet adopts a data format of a MAC PDU, and the RRC downlink message is stored in a MAC SDU of the MAC PDU.
  • the uplink grant is stored in the MAC CE in the MAC PDU.
  • the specific implementation is as follows: when the RRC downlink message is sent by the AM, the MAC SDU in the message packet stores the RRC downlink message. A packet data packet after the RLC packet; or, when the RRC downlink message is sent by the TM, the MAC SDU in the message packet stores the entire content of the RRC downlink message.
  • the RRC uplink response message is further used.
  • the UE is instructed to acknowledge receiving the RRC downlink message, where the UE does not send the acknowledgement message of the RRC downlink message.
  • the specific implementation is: the wireless The resource control process delay RRC procedureDelay is equal to zero.
  • the RRC downlink The message and the RRC uplink response message belong to an RRC process instance of the same RRC processing identifier.
  • a network device in a second aspect, includes: a sending module, configured to send an RRC downlink message; and a processing module, configured to pre-allocate the RRC downlink in a time range of an RRC process delay of the RRC downlink message An uplink grant of the RRC uplink response message corresponding to the message; the sending module is further configured to delay the RRC process
  • the uplink authorization is sent in the time range, and the receiving module is configured to receive, by using the uplink resource indicated by the uplink authorization, the RRC uplink response message sent by the UE from the RRC layer.
  • the sending time of the uplink grant is after the sending time of the RRC downlink message
  • the sending time of the uplink grant is not later than the acknowledgement message of the RRC downlink message. Receive time.
  • the acknowledgement message of the RRC downlink message is the media access control MAC layer.
  • the feedback message; or, when the RRC downlink message is sent in the acknowledge mode AM, the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the sending module is specifically configured to: send the uplink authorization in a physical layer downlink control channel PDCCH that sends a downlink resource allocation of the RRC downlink message.
  • the sending module is specifically configured to: send the uplink authorization in a message packet that sends the RRC downlink message.
  • the specific implementation is as follows: the message packet adopts a data format of a MAC PDU, and the RRC downlink message is stored in a MAC SDU of the MAC PDU.
  • the uplink grant is stored in the MAC CE in the MAC PDU.
  • the specific implementation is as follows: when the RRC downlink message is sent by the AM, the MAC SDU in the message packet stores the RRC downlink message. A packet data packet after the RLC packet; or, when the RRC downlink message is sent by the TM, the MAC SDU in the message packet stores the entire content of the RRC downlink message.
  • the RRC uplink response message is further used.
  • the UE is instructed to acknowledge receiving the RRC downlink message, where the UE does not send the acknowledgement message of the RRC downlink message.
  • the specific implementation is: the wireless The resource control process delay RRC procedureDelay is equal to zero.
  • the RRC downlink The message and the RRC uplink response message belong to an RRC process instance of the same RRC processing identifier.
  • another network device comprising a processor, a transmitter and a receiver for performing any of the possible implementations of the first aspect or the first aspect by the transmitter and the receiver Methods.
  • a computer readable storage medium for storing a computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a method for transmitting a message comprising: receiving an RRC downlink message sent by a network device; receiving, in a time range of an RRC process delay of the RRC downlink message, the network device pre-allocated and sent An uplink grant of the RRC uplink response message corresponding to the RRC downlink message; and the RRC uplink response message is sent from the RRC layer on the uplink resource indicated by the uplink grant.
  • the receiving time of the uplink grant is after the receiving time of the RRC downlink message
  • the receiving time of the uplink grant is no later than the acknowledgement message of the RRC downlink message.
  • the acknowledge message of the RRC downlink message is the media access control MAC layer.
  • the feedback message; or, when the RRC downlink message is sent in the acknowledge mode AM, the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the RRC uplink response message corresponding to the RRC downlink message that is pre-allocated and sent by the network device is received in a time range of the RRC process delay of the RRC downlink message.
  • the uplink authorization is specifically implemented as: receiving the uplink authorization in a physical layer downlink control channel PDCCH that receives the downlink resource allocation of the RRC downlink message.
  • the RRC uplink response message corresponding to the RRC downlink message that is pre-allocated and sent by the network device is received in a time range of the RRC process delay of the RRC downlink message.
  • the uplink authorization is specifically implemented as: receiving the uplink authorization in a message packet that receives the RRC downlink message.
  • the specific implementation is as follows: the message packet adopts a data format of a MAC PDU, and the RRC downlink message is stored in a MAC SDU of the MAC PDU.
  • the uplink grant is stored in the MAC CE in the MAC PDU.
  • the specific implementation is: when the RRC downlink message is sent by the AM, the MAC SDU in the message packet stores the RRC downlink message.
  • the RRC uplink response message is further used. Receiving, by the indication, the RRC downlink message, where the network device does not receive the acknowledgement message of the RRC downlink message.
  • the specific implementation is: the wireless The resource control process delay RRC procedureDelay is equal to zero.
  • the RRC downlink The message and the RRC uplink response message belong to an RRC process instance of the same RRC processing identifier.
  • a user equipment configured to receive an RRC downlink message sent by the network device; and the receiving module is further configured to: within a time range of an RRC process delay of the RRC downlink message And receiving, by the network device, an uplink grant of the RRC uplink response message corresponding to the RRC downlink message that is pre-allocated and sent by the network device; the processing module is configured to determine an uplink resource of the uplink grant indication, and the sending module is configured to use the uplink authorization indication The RRC uplink response message is sent from the RRC layer on the resource.
  • the receiving time of the uplink grant is after the receiving time of the RRC downlink message
  • the receiving time of the uplink grant is no later than the acknowledgement message of the RRC downlink message.
  • the RRC downlink message acknowledge message is the media access control MAC layer.
  • the feedback message; or, when the RRC downlink message is sent in the acknowledge mode AM, the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the receiving module is specifically configured to: receive the RRC The uplink grant is received in the physical layer downlink control channel PDCCH of the downlink resource allocation of the downlink message.
  • the receiving module is specifically configured to: receive the uplink authorization in a message packet that receives the RRC downlink message.
  • the specific implementation is as follows: the message packet adopts a data format of a MAC PDU, and the RRC downlink message is stored in a MAC SDU of the MAC PDU.
  • the uplink grant is stored in the MAC CE in the MAC PDU.
  • the specific implementation is: when the RRC downlink message is sent by the AM, the MAC SDU in the message packet stores the RRC downlink message.
  • the RRC uplink response message is further used. Receiving, by the indication, the RRC downlink message, where the network device does not receive the acknowledgement message of the RRC downlink message.
  • the specific implementation is: the wireless The resource control process delay RRC procedureDelay is equal to zero.
  • the RRC downlink The message and the RRC uplink response message belong to an RRC process instance of the same RRC processing identifier.
  • another user equipment comprising a processor, a transmitter and a receiver, for performing any of the possible implementations of the fifth or fifth aspect by the transmitter and the receiver Methods.
  • a computer readable storage medium for storing a computer program comprising instructions for performing the method of any of the fifth or fifth aspects of the possible implementation.
  • a communication system comprising:
  • the user equipment in the seventh aspect or any possible implementation manner of the seventh aspect is not limited.
  • the message input method, device, and system in the embodiment of the present application sends an uplink grant of the RRC uplink response message at a receiving time of the acknowledgment message of the RRC downlink message, so that the UE side can send the RRC uplink response.
  • the message does not need to wait for the network device to allocate an uplink grant, thereby reducing the delay between receiving the RRC downlink message and the feedback RRC uplink response message, so that the control plane delay can meet the shorter delay requirement.
  • FIG. 1 is an interaction flowchart of a prior art RRC recovery process.
  • FIG. 2 is a flow chart of a method for transmitting an RRC message according to an embodiment of the present application.
  • FIG. 3 is an interaction flowchart of an RRC process according to an embodiment of the present application.
  • FIG. 5 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • FIG. 6 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • FIG. 7 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • FIG. 8 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • FIG. 9 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a user equipment according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a network device according to another embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a user equipment according to another embodiment of the present application.
  • Figure 14 is a system block diagram of a communication system of one embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • UE User Equipment
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • PLMN public land mobile network
  • the network device may be a device for communicating with the mobile device, and the network device may be a Global System of Mobile communication (GSM) or a base station in a Code Division Multiple Access (CDMA) (Base Transceiver Station, BTS), which may also be a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), or an evolved base station in Long Term Evolution (LTE) (Evolutional Node B) , an eNB or an eNodeB) or an access point, or an in-vehicle device, a wearable device, a network-side device in a future 5G network, or a network device in a future evolved Public Land Mobile Network (PLMN) network.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • Evolutional Node B an eNB or an eNode
  • the LTE system is taken as an example, and the technical terms involved in the embodiments of the present application are first introduced.
  • Radio Link Control Each RLC entity is configured by RRC, and has three modes according to the service type: Transparent Mode (TM), Unacknowledged Mode (UM), and acknowledge mode ( Acknowledged Mode, AM).
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM acknowledge mode
  • SRB Signalling Radio Bearer
  • the RLC provides a Radio Bearer (RB) to the upper layer; otherwise, the RB service is PDCP. Or BMC bearer.
  • PDCP Packet Data Convergence Protocol
  • BMC Broadcast/Multicast Control
  • Transparent mode The sending entity does not add any additional control protocol overhead on the high-level data, and only decides whether to perform the segmentation operation according to the service type. If there is an error in the Protocol Data Unit (PDU) received by the receiving entity, it will be submitted after the error flag or directly discarded and reported to the upper layer according to the configuration.
  • the TM mode service has real-time voice services and the like.
  • Non-Confirmed Mode The sending entity adds the necessary control protocol overhead on the upper layer PDU and then transmits it but does not guarantee delivery to the peer entity and does not use the retransmission protocol.
  • the receiving entity submits the received error data as an error, or directly discards and reports to the upper layer. Since the RLC PDU contains a sequence number, it is able to detect the integrity of the higher layer PDU.
  • the UM mode services include cell broadcast and IP telephony.
  • AM Acknowledgement Mode
  • the transmitting entity transmits the necessary control protocol overhead on the upper layer PDU and guarantees delivery to the peer entity. Since the RLC of the AM mode has an automatic repeat-request capability, if the RLC layer receives the erroneous RLC PDU, it notifies the sender's RLC to retransmit the PDU. Since the RLC PDU contains sequence number information, the RLC of the AM mode also supports the sequential/out-of-order delivery of data to higher layers.
  • the AM mode is a standard mode for packet data transmission services, and the AM mode services include www and email downloads.
  • FIG. 1 is an interaction flowchart of an RRC recovery process of LTE in the prior art.
  • the UE after receiving the RRC downlink message, that is, the RRC Connection Resume message sent by the network device, the UE first performs Cyclic Redundancy Check (CRC) decoding on the physical layer. After the decoding is correct, the acknowledgement message (Acknowledgement, ACK) is sent, otherwise the Negative ACKnowledgment (NACK) is fed back. If the RLC layer on the network device side performs packet transmission on the RRC Connection Resume message, in addition to performing ACK/NACK feedback on each physical packet at the physical layer, it is also required to be in the RLC header according to the network device in the RLC layer.
  • CRC Cyclic Redundancy Check
  • the Polling setting determines whether or not to feed back a Status Report. If the network device polls the position 1 in the RLC header of the last segment of the RLC layer, the UE will feed back the Status Report. In the implementation, after the network device polling is set, it is known that the UE sends the Status Report, so after the downlink device is sent the downlink RRC Connection Resume message, the network device may then send an uplink scheduling DCI for scheduling the uplink resource of the Status report; The UE will send a Status Report after receiving the last RLC PDU.
  • the network device receives the Status Report and confirms that the RRC Connection Resume message is correctly received, and sends the uplink scheduled DCI, including the UL Grant that sends the RRC Connection Resume Complete message.
  • the UE receives the DCI for scheduling the RRC Connection Resume Complete message, and after the decoding succeeds, sends the RRC Connection Resume Complete message.
  • the RRC Connection Resume message when the RRC Connection Resume message is received from the UE and the RRC Connection Resume Complete message is sent by the UE, it takes about 15 ms, and the control plane delay from the IDLE state to the CONNECTED state is 10 ms.
  • the RRC recovery process of LTE cannot meet the control plane delay requirement of 5G.
  • the RRC connection establishment process, the RRC connection reconfiguration process, or the RRC connection reestablishment process of the LTE is similar to the RRC connection recovery process, and cannot meet the 5G control plane delay requirement.
  • FIG. 2 is a flow chart of a message transmission method of one embodiment of the present application.
  • the method of Figure 2 is performed by a network device.
  • the method of Figure 2 includes:
  • the network device can send an RRC downlink message to the UE.
  • the uplink authorization of the RRC uplink response message corresponding to the RRC downlink message is pre-allocated and sent in the time range of the RRC process delay of the RRC downlink message.
  • an uplink grant (UL Grant) is used to indicate an uplink scheduling resource allocated by the network device for the RRC uplink response message.
  • the network device pre-allocates and sends the uplink authorization of the RRC uplink response message corresponding to the RRC downlink message in the time range of the RRC procedure delay of the RRC downlink message, where Before receiving the RRC downlink message acknowledgement message, the network device pre-allocates the uplink grant for the RRC uplink response message corresponding to the RRC downlink message and sends the uplink grant to the UE.
  • the RRC procedure delay of the RRC downlink message includes a scenario in which the RRC process delay is 0, and the uplink grant is the same as the RRC downlink message. Sent on the subframe.
  • the RRC uplink response message refers to a feedback message of an RRC downlink message sent by the UE at the RRC layer.
  • the RRC downlink message and the RRC uplink response message belong to an RRC process instance of the same RRC-Transaction Identifier.
  • the network device pre-allocates the uplink grant of the RRC uplink response message in the time range of the RRC process delay and sends the uplink grant to the UE, so that the UE side can wait for the network device to allocate the uplink grant when sending the RRC uplink response message. Therefore, the delay between receiving the RRC downlink message and the feedback RRC uplink response message by the UE is reduced, so that the control plane delay can meet the shorter delay requirement.
  • the sending time of the uplink grant is after the sending time of the RRC downlink message
  • the sending time of the uplink grant is no later than the receiving time of the acknowledgment message of the RRC downlink message.
  • the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the acknowledgement message of the RRC downlink message is a feedback message of the media access control MAC layer.
  • the step 220 is specifically implemented to: send the uplink authorization in a physical downlink control channel (PDCCH) of a downlink resource allocation (DL Assignment) that sends the RRC downlink message.
  • PDCCH physical downlink control channel
  • DL Assignment downlink resource allocation
  • the uplink grant of the RRC uplink response message may be sent in the same downlink control channel (PDCCH) as the downlink resource allocation (DL Assignment) of the RRC downlink message.
  • the network device may send the uplink grant of the RRC uplink response message and the downlink resource allocation of the RRC downlink message to the UE through a downlink control information (DCI).
  • DCI downlink control information
  • the uplink grant of the RRC uplink response message and the downlink resource of the RRC downlink message are sent to the UE in the same message, so that the UE can obtain the RRC uplink response message before sending the acknowledgement message of the RRC downlink message.
  • the uplink grant thereby saving the time for the UE to wait for the uplink grant of the RRC uplink response message by the network device.
  • step 220 is specifically implemented to: send the uplink authorization in a message packet that sends the RRC downlink message.
  • the message packet may adopt a data format of a Medium Access Control (MAC) Protocol Data Unit (PDU).
  • MAC Medium Access Control
  • PDU Protocol Data Unit
  • the MAC PDU consists of a string of bytes (8 bits).
  • a MAC PDU may contain one MAC header, 0 to multiple MACSDUs, 0 to multiple MAC control units, and possibly padding.
  • the RRC downlink message is stored in a MAC Service Data Unit (SDU) in the MAC PDU
  • the uplink authorization is stored in a MAC Control Element (Control Element, CE) in the MAC PDU. in.
  • SDU Service Data Unit
  • CE MAC Control Element
  • the MAC SDU in the message packet stores a packet data packet after the RRC downlink message is RLC-packed.
  • the packet data packet may be any one of the RRC downlink messages after the RLC packet.
  • the uplink grant may be sent together with the first data packet after the RLC packet is sent by the RRC downlink message, or may be delivered together with the last data packet after the RRC downlink message is sent by the RLC packet.
  • the MAC SDU in the message packet stores the entire content of the RRC downlink message.
  • the uplink authorization of the RRC uplink response message and the RRC downlink message are sent to the UE in the same message, so that the UE receives the uplink authorization of the RRC uplink response message while receiving the RRC downlink message, thereby saving The time when the UE waits for the network device to allocate the uplink grant of the RRC uplink response message.
  • the RRC uplink response message is further used to indicate that the UE confirms receiving the RRC downlink message, where the UE The acknowledgment message of the RRC downlink message is not sent.
  • the RRC procedure delay RRC procedureDelay may take a value of 0.
  • the radio resource control procedure delay RRC procedureDelay value greater than 0 is also allowed.
  • the RRC downlink message when the RRC downlink message is sent by the AM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message; or The RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the RRC downlink message when the RRC downlink message is sent by the TM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message;
  • the RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • there may be other RRC connection procedures for transmitting RRC messages in the TM which are not described in detail in the embodiments of the present application.
  • the downlink resource allocation of the RRC downlink message includes multiple downlink resource allocations, and the downlink resource allocation carried in the first message may be any one of the multiple downlink resource allocations.
  • the downlink resource allocation carried in the first message may be any one of the multiple downlink resource allocations.
  • the downlink resource allocation of the RRC downlink message includes one downlink resource allocation, and the uplink grant of the RRC uplink response message is delivered together with the downlink resource allocation.
  • the method may further include: receiving an RRC request message sent by the UE.
  • the network device may send an RRC downlink message corresponding to the RRC request message to the UE.
  • the network device may also actively send an RRC downlink message to the UE, which is not limited herein.
  • the RRC request message is an RRC process instance that belongs to the same RRC processing identifier corresponding to the RRC downlink message and the RRC uplink response message.
  • the RRC request message is an RRC Connection Resume Request message
  • the RRC downlink message is RRC a connection setup message
  • the RRC uplink response message is an RRC Connection Setup Complete message
  • the RRC request message is an RRC Connection Setup Request message
  • the RRC downlink message is an RRC Connection Reestablishment message
  • the RRC uplink response message When it is an RRC Connection Reestablishment Complete message, the RRC request message is an RRC Connection Reestablishment Request message, and the like.
  • the network device may determine that the UE fails to receive or decode the RRC downlink message, and may not execute. Step 230.
  • FIG. 3 is an interaction flowchart of an RRC process according to an embodiment of the present application.
  • the RRC connection recovery process is taken as an example for illustration.
  • the method includes:
  • the UE sends an RRC connection recovery request message to the network device.
  • the UE may send an RRC Connection Resume Request message to the network device.
  • the steps performed by the network device and the UE before the step 301 and the step 301 may refer to the prior art, and details are not repeatedly described herein.
  • the network device sends a downlink resource allocation and an uplink authorization.
  • the network device may send an uplink grant (UL Grant) of the RRC uplink response message while transmitting the downlink resource allocation (DL Assignment) of the RRC downlink message to the UE.
  • UL Grant uplink grant
  • DL Assignment downlink resource allocation
  • the network device may send the UL Grant of the RRC Assignment and RRC Connection Resume Complete messages of the RRC Connection Resume message to the UE.
  • the network device can send the DL Assignment and the UL Grant through a DCI message.
  • a DL Assignment may be obtained, where the DL Assignment indicates a downlink resource for receiving an RRC Connection Resume message, and the UE may also obtain a UL Grant, which is used to send an RRC Connection Resume Complete.
  • the uplink resource of the message may be obtained.
  • the network device sends an RRC connection recovery message in an AM mode on the downlink resource indicated by the downlink resource allocation.
  • the network device may be on the downlink resource indicated by the DL Assignment of the RRC Connection Resume message.
  • the UE sends the RRC Connection Resume message.
  • the RLC layer of the network device transmits an RRC Connection Resume message in the AM mode.
  • the RLC layer of the network device performs packet transmission on the RRC Connection Resume message and polls the position 1 in the RLC header of the last segment of the RLC layer. If the network device polls the position 1 in the RLC header of the last segment of the RLC layer, the UE will feed back the RLC layer acknowledgement message.
  • the UE sends a MAC layer acknowledgement message.
  • the RRC Connection Resume message sent by the network device may be received on the downlink resource indicated by the DL Assignment.
  • the UE When the network side device sends the RRC Connection Resume message in the AM mode in the RLC layer, the UE receives multiple physical packets of the RRC Connection Resume message on the physical layer, that is, the MAC layer, and the UE needs to perform ACK/NACK for each physical packet. Feedback, the ACK/NACK feedback may be referred to as a MAC layer acknowledgement message.
  • the UE sends an RLC acknowledgement message and an RRC connection recovery complete message on the uplink resource indicated by the uplink grant.
  • the UE side needs to feed back the RLC acknowledge message at the RLC layer in addition to performing ACK/NACK feedback on each physical packet at the MAC layer.
  • the UE may decide whether to feed back the RLC acknowledgement message according to the polling setting condition of the network device in the RLC header. If the network device polls the position 1 in the RLC header of the last segment of the RLC layer, the UE needs to feed back the RLC acknowledgement message.
  • the UE may send the RRC Connection Resume Complete message on the uplink resource indicated by the uplink grant, and also send the RLC acknowledge message on the uplink resource indicated by the uplink grant. That is to say, the UE may send an RRC Connection Resume Complete message and an RLC acknowledgement message on the uplink resource indicated by the uplink grant.
  • the RLC acknowledgement message may be a State Report of the RRC Connection Resume message.
  • the RRC Connection Resume Complete message and the State Report may be sent in one MAC PDU.
  • the RRC Connection Resume Complete message and the RLC acknowledgement message are sent separately, for example, the RRC Connection Resume Complete message may also be sent before the RLC acknowledgement message, or after the RLC acknowledgement message, and so on.
  • the sending time of the RRC Connection Resume Complete message depends on the time of the uplink resource indicated by the UL Grant allocated by the network device for the RRC Connection Resume Complete message.
  • the uplink grant of the RRC Connection Resume Complete and the downlink resource assignment of the RRC Connection Resume message it can be ensured that the uplink grant is sent at a receiving time of the acknowledgement message no later than the RRC Connection Resume message, so that The UE side does not need to wait for the delay of the network device to configure the uplink grant when sending the RRC Connection Resume Complete message, thereby reducing the control plane delay on the UE side.
  • the UE when the RRC Connection Resume message is transmitted in the AM mode, the UE can also send the RLC acknowledgment message of the RRC Connection Resume message and the RRC Connection Resume Complete message together on the uplink resource indicated by the uplink grant. Save the overhead of scheduling resources.
  • FIG. 4 is an interaction flowchart of an RRC procedure of another embodiment of the present application.
  • the RRC connection recovery process is taken as an example for illustration.
  • the method includes:
  • the UE sends an RRC connection recovery request message to the network device.
  • the UE may send an RRC Connection Resume Request message to the network device, requesting to initiate an RRC connection recovery process.
  • the steps performed by the network device and the UE before the step 401 and the step 401 may refer to the prior art, and details are not repeatedly described herein.
  • the network device sends a downlink resource allocation.
  • the network device may send a downlink resource allocation (DL Assignment) of the RRC downlink message to the UE.
  • DL Assignment downlink resource allocation
  • the network device may send a DL Assignment of the RRC Connection Resume message to the UE.
  • the network device can send the DL Assignment through a DCI message.
  • the specific implementation can refer to the prior art.
  • a DL Assignment is obtained, which indicates a downlink resource for receiving the RRC Connection Resume message.
  • the network side device sends an RRC connection recovery message and an uplink authorization in an AM mode on the downlink resource allocation.
  • the network device sends an RRC Connection Resume message and a UL Grant of the RRC Connection Resume Complete message in the downlink resource indicated by the DL Assignment.
  • the UL Grant may be assembled into a MAC PDU and sent to the UE in the form of a MAC Control Element and an RRC Connection Resume message.
  • the RLC layer of the network device may send an RRC Connection Resume message in an AM mode, that is, the RLC layer of the network device transmits the MAC PDU in an AM mode.
  • the RLC layer of the network device performs packet transmission on the RRC Connection Resume message, and polls the position 1 in the RLC header of the last segment of the RLC layer. If the network device polls the position 1 in the RLC header of the last segment of the RLC layer, the UE will feed back the RLC layer acknowledgement message.
  • the UL Grant may be sent together with any one of the segments after the RLC packet, for example, the UL Grant may be sent together with the first segment after the RLC packet by the RRC downlink message. Or the UL Grant may be sent with the last segment of the RRC downlink message after the RLC packet, and so on.
  • the segment of the RRC downlink message after the RLC packet includes part of the RRC downlink message.
  • the UE may decode and obtain the DL Assignment, and receive the MAC PDU sent by the network device on the downlink resource indicated by the DL Assignment, where the MAC PDU includes part of the content of the RRC Connection Resume message and the UL Grant.
  • the UE sends a MAC layer acknowledgement message.
  • the UE when the network side device sends the RRC Connection Resume message in the AM mode at the RLC layer, the UE receives multiple physical packets of the RRC Connection Resume message on the physical layer, that is, the MAC layer, and the UE needs to ACK/NACK feedback is performed for each physical packet, and the ACK/NACK feedback may be referred to as a MAC layer acknowledgement message.
  • the UE sends an RRC connection recovery complete message on the uplink resource indicated by the uplink grant.
  • the UE sends an RLC layer acknowledgement message.
  • the UE When the UE sends the last MAC layer acknowledgement message, indicating that the UE has completely received the RRC connection recovery message, At this time, the UE may send an RLC layer acknowledgement message.
  • the time of the uplink resource indicated by the uplink grant may be before the time when the UE sends the MAC layer acknowledgement message before the time when the UE sends the RLC layer acknowledgement message.
  • the uplink authorization of the RRC uplink response message and the RRC downlink message are sent to the UE in the same message, so that the UE receives the uplink authorization of the RRC uplink response message while receiving the RRC downlink message, thereby saving The time when the UE waits for the network device to allocate the uplink grant of the RRC uplink response message.
  • FIG. 5 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • the RRC connection establishment process is taken as an example for illustration.
  • the method includes:
  • the UE sends an RRC connection setup request message to the network device.
  • the UE may send an RRC Connection Setup Request message to the network device requesting to initiate an RRC connection setup procedure.
  • the steps performed by the network device and the UE before the step 501 and the step 501 may refer to the prior art, and details are not repeatedly described herein.
  • the network device sends a downlink resource allocation and an uplink authorization.
  • the network device may send an uplink grant (UL Grant) of the RRC uplink response message while transmitting the downlink resource allocation (DL Assignment) of the RRC downlink message to the UE.
  • UL Grant uplink grant
  • DL Assignment downlink resource allocation
  • the network device may send the DL Assignment of the RRC Connection Setup message and the UL Grant of the RRC Connection Setup Complete message to the UE.
  • the network device can send the DL Assignment and the UL Grant through a DCI message.
  • a DL Assignment for receiving an RRC Connection Setup message may be obtained, while obtaining a UL Grant for transmitting an RRC Connection Setup Complete message.
  • the network device sends an RRC connection setup message in a TM mode on the downlink resource indicated by the downlink resource allocation.
  • the network device may send the RRC Connection Setup message to the UE on the downlink resource indicated by the DL Assignment of the RRC Connection Setup message.
  • the RLC layer of the network device may transmit the RRC Connection Setup message in the TM mode.
  • the UE may decode and obtain the DL Assignment, and receive an RRC Connection Setup message sent by the network device on the downlink resource indicated by the DL Assignment.
  • the RRC Connection Setup message can be transmitted in the data format of the MAC PDU.
  • the UE sends a MAC layer acknowledgement message.
  • the UE may also feed back a MAC layer acknowledgement message, that is, an ACK/NACK message of the RRC Connection Setup message, on the uplink resource indicated by the UL Grant.
  • a MAC layer acknowledgement message that is, an ACK/NACK message of the RRC Connection Setup message
  • the UE sends an RRC connection setup complete message on the uplink resource indicated by the uplink grant.
  • the UE may send an RRC uplink response message, that is, an RRC Connection Setup Complete message, on the uplink resource indicated by the UL Grant.
  • the uplink grant can be guaranteed not later than the RRC.
  • the receiving time of the acknowledgment message of the Connection Setup message is sent, so that the UE side does not need to wait for the delay of the network device to configure the uplink grant when sending the RRC Connection Setup Complete message, thereby reducing the control plane delay on the UE side.
  • FIG. 6 is an interaction flowchart of an RRC process according to still another embodiment of the present application.
  • the RRC connection establishment process is taken as an example for illustration.
  • the method includes:
  • the UE sends an RRC connection setup request message to the network device.
  • the UE may send an RRC Connection Setup Request message to the network device requesting to initiate an RRC connection setup procedure.
  • the steps performed by the network device and the UE before the step 601 and the step 601 may refer to the prior art, and details are not repeatedly described herein.
  • the network device sends a downlink resource allocation.
  • the network device may send a downlink resource allocation (DL Assignment) of the RRC downlink message to the UE.
  • DL Assignment downlink resource allocation
  • the network device may send the DLAssignment of the RRC Connection Setup message to the UE.
  • the network device can send the DL Assignment through a DCI message.
  • the specific implementation can refer to the prior art.
  • the network device sends an RRC connection setup message and an uplink grant in a TM mode on the downlink resource indicated by the downlink resource allocation.
  • the network device sends the RRC Connection Setup message in the TM mode and the UL Grant of the RRC Connection Setup Complete message on the downlink resource indicated by the DL Assignment.
  • the UL Grant may be assembled into a MAC PDU and sent to the UE in the form of a MAC Control Element and an RRC Connection Setup message.
  • the MAC PDU includes the entire contents of the RRC Connection Setup message and the UL Grant.
  • the UE may decode and obtain the DL Assignment, and receive, on the downlink resource indicated by the DL Assignment, a MAC PDU sent by the network device, where the MAC PDU includes the entire content of the RRC Connection Setup message and the UL Grant.
  • the UE sends a MAC layer acknowledgement message.
  • the UE sends an RRC connection setup complete message on the uplink resource indicated by the uplink grant.
  • steps 604 and 605 For the specific implementation of the steps 604 and 605, reference may be made to the steps 504 and 505 of FIG. 5, and details are not described herein again.
  • the UE side by sending the uplink authorization of the RRC Connection Setup Complete and the downlink resource allocation of the RRC Connection Setup message, the UE side does not need to wait for the delay of the network device to configure the uplink authorization when sending the RRC Connection Setup Complete message. Therefore, the RRC Connection Setup Complete message can be sent within the time range of the RRC process delay, reducing the control plane delay on the UE side.
  • FIG. 7 is an interaction flowchart of an RRC procedure according to an embodiment of the present application.
  • the RRC connection recovery process is taken as an example for illustration.
  • the method includes:
  • the UE sends an RRC connection recovery request message to the network device.
  • the network device sends a downlink resource allocation.
  • the network device sends an RRC connection recovery message in an AM mode on the downlink resource indicated by the downlink resource allocation.
  • the network device sends an uplink authorization.
  • the network device After the network device sends the RRC connection recovery message by the AM, the network device sends the uplink authorization before receiving the RLC acknowledgement message.
  • the network device if the network device sends an RRC downlink message in the TM, the network device sends the uplink grant before receiving the MAC acknowledgement message.
  • the UE sends a MAC layer acknowledgement message and an RLC layer acknowledgement message, and sends an RRC connection recovery complete message on the uplink resource indicated by the uplink grant.
  • step 705 For the specific implementation of the step 705, reference may be made to the steps 304 and 305 of FIG. 3 or the steps 404 to 406 of FIG. 4, and details are not described herein again.
  • the RLC acknowledge message of the RRC Connection Resume is sent, so that the UE side does not need to wait for the network device configuration when sending the RRC Connection Resume Complete message.
  • the delay of the uplink grant, so that the RRC Connection Resume Complete message can be sent within the time range of the RRC process delay, reducing the control plane delay on the UE side.
  • the MAC layer acknowledgement message or the RLC layer acknowledgement message fed back by the UE side includes a NACK message, it indicates that the UE does not correctly receive the RRC downlink message, and at this time, the UE may not send the RRC. Upstream response message.
  • the network device receives the NACK message sent by the UE side from the MAC layer or the RLC layer, the network device can know that the pre-assigned uplink authorization is wasted.
  • FIG. 8 is an interaction flowchart of an RRC process according to an embodiment of the present application.
  • the RRC connection recovery process is taken as an example for illustration.
  • the method includes:
  • the UE sends an RRC connection recovery request message to the network device.
  • the network device sends a downlink resource allocation and an uplink authorization.
  • the network device sends an RRC connection recovery message in an AM mode on the downlink resource indicated by the downlink resource allocation.
  • steps 801-803 For the specific implementation of the steps 801-803, reference may be made to the steps 301-303 of FIG. 3, and details are not described herein again.
  • the UE sends an RRC connection recovery complete message on the uplink resource indicated by the uplink grant.
  • the RRC connection recovery complete message may be directly sent to the network device without sending an ACK acknowledgement message of the MAC layer and an ACK acknowledgement message of the RLC layer.
  • the network side device may determine that the RRC connection recovery message is successfully sent.
  • the network device sends an RRC downlink message in the RRC process of the embodiment of the present application, and the UE correctly receives the RRC downlink message sent by the network device, the UE may not send the MAC layer ACK acknowledgement message directly to the UE.
  • the network device sends an RRC uplink response message.
  • steps 801-803 can also be replaced with the flow shown in steps 401-403 of the embodiment shown in FIG.
  • an RRC connection re-establishment (RRC Connection Reestablishment) process is an RRC procedure for transmitting an RRC downlink message in a TM manner
  • the RRC process of the RRC connection reconfiguration process such as the RRC connection reconfiguration process, is used to send the RRC process of the RRC downlink message, and so on.
  • RRC connection reconfiguration process such as the RRC connection reconfiguration process
  • FIG. 9 is a flow chart of a message transmission method of one embodiment of the present application.
  • the method of Figure 9 is performed by a UE.
  • the method of Figure 9 includes:
  • the user equipment receives the uplink grant of the RRC uplink response message that is pre-allocated and sent by the network device in the time range of the RRC process delay, so that the network device does not need to wait for the network device to allocate the uplink grant when sending the RRC uplink response message.
  • the delay between receiving the RRC downlink message and the feedback RRC uplink response message is reduced, so that the control plane delay can meet the shorter delay requirement.
  • the receiving time of the uplink grant is after the receiving time of the RRC downlink message
  • the receiving time of the uplink grant is not later than the acknowledgement message of the RRC downlink message
  • the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the acknowledgement message of the RRC downlink message is a feedback message of the media access control MAC layer.
  • step 920 is specifically implemented to: receive the uplink grant in a physical layer downlink control channel PDCCH that receives a downlink resource allocation of the RRC downlink message.
  • the uplink grant of the RRC uplink response message may be sent in the same downlink control channel (PDCCH) as the downlink resource allocation (DL Assignment) of the RRC downlink message.
  • the network device may send the uplink grant of the RRC uplink response message and the downlink resource allocation of the RRC downlink message to the UE through a downlink control information (DCI).
  • DCI downlink control information
  • the uplink grant of the RRC uplink response message and the downlink resource allocation of the RRC downlink message are received in the same message, so that the UE can obtain the uplink grant of the RRC uplink response message before sending the acknowledgement message of the RRC downlink message. Therefore, the time for the UE to wait for the uplink grant of the RRC uplink response message by the network device is saved.
  • step 920 is specifically implemented to: receive the uplink grant in a message packet that receives the RRC downlink message.
  • the message packet may adopt a data format of a Medium Access Control (MAC) Protocol Data Unit (PDU).
  • MAC Medium Access Control
  • PDU Protocol Data Unit
  • the MAC PDU consists of a string of bytes (8 bits).
  • a MAC PDU may contain one MAC header, 0 to multiple MACSDUs, 0 to multiple MAC control units, and possibly padding.
  • the RRC downlink message is stored in a MAC Service Data Unit (SDU) in the MAC PDU
  • the uplink authorization is stored in a MAC Control Element (Control Element, CE) in the MAC PDU. in.
  • SDU Service Data Unit
  • CE MAC Control Element
  • the MAC SDU in the message packet A packet data packet after the RRC downlink message is RLC-packed is stored.
  • the packet data packet may be any one of the RRC downlink messages after the RLC packet.
  • the uplink grant may be sent together with the first data packet after the RLC packet is sent by the RRC downlink message, or may be delivered together with the last data packet after the RRC downlink message is sent by the RLC packet.
  • the MAC SDU in the message packet stores the entire content of the RRC downlink message.
  • the uplink authorization and the RRC downlink message of the RRC uplink response message are received in the same message, so that the UE receives the uplink authorization of the RRC uplink response message while receiving the RRC downlink message, thereby saving the UE waiting.
  • the RRC uplink response message is further used to indicate to acknowledge receiving the RRC downlink message, where the network device does not receive the The confirmation message of the RRC downlink message.
  • the RRC procedure delay RRC procedureDelay may take a value of 0.
  • the radio resource control procedure delay RRC procedureDelay value greater than 0 is also allowed.
  • the RRC downlink message when the RRC downlink message is sent by the AM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message; or The RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the RRC downlink message when the RRC downlink message is sent by the TM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message;
  • the RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • there may be other RRC connection procedures for transmitting RRC messages in the TM which are not described in detail in the embodiments of the present application.
  • the downlink resource allocation of the RRC downlink message includes multiple downlink resource allocations, and the downlink resource allocation carried in the first message may be any one of the multiple downlink resource allocations. .
  • the downlink resource allocation of the RRC downlink message includes one downlink resource allocation, and the uplink grant of the RRC uplink response message is delivered together with the downlink resource allocation.
  • the method may further include: sending an RRC request message.
  • the RRC request message is an RRC process instance that belongs to the same RRC processing identifier corresponding to the RRC downlink message and the RRC uplink response message.
  • the RRC The request message is an RRC Connection Resume Request message
  • the RRC downlink message is an RRC Connection Setup message and the RRC uplink response message is an RRC Connection Setup Complete message
  • the RRC request message is an RRC connection setup request (RRC) a connection setup request) message
  • RRC RRC connection setup request
  • the RRC downlink message is an RRC Connection Reestablishment message
  • the RRC uplink response message is an RRC Connection Reestablishment Complete message
  • the RRC request message is an RRC Connection Reestablishment Request message, etc. .
  • FIG. 9 The specific implementation of the method shown in FIG. 9 can be referred to the embodiment shown in FIG. 3-8, and details are not described herein again.
  • the UE may feed back the NACK message. At this time, the UE does not perform step 930.
  • FIG. 10 is a schematic structural diagram of a network device 1000 according to an embodiment of the present application.
  • the network device 1000 may include: a sending module 1001, a processing module 1003, and a receiving module 1002.
  • the sending module 1001 is configured to send an RRC downlink message.
  • the processing module 1003 is configured to pre-allocate an uplink grant of the RRC uplink response message corresponding to the RRC downlink message within a time range of the RRC process delay of the RRC downlink message.
  • the sending module 1001 is further configured to send the uplink authorization.
  • the receiving module 1002 is configured to receive, by using the uplink resource indicated by the uplink grant, the RRC uplink response message sent by the UE from the RRC layer.
  • the network device pre-allocates the uplink grant of the RRC uplink response message in the time range of the RRC process delay and sends the uplink grant to the UE, so that the UE side can wait for the network device to allocate the uplink grant when sending the RRC uplink response message. Therefore, the delay between receiving the RRC downlink message and the feedback RRC uplink response message by the UE is reduced, so that the control plane delay can meet the shorter delay requirement.
  • the sending time of the uplink grant is after the sending time of the RRC downlink message
  • the sending time of the uplink grant is no later than the receiving time of the acknowledgment message of the RRC downlink message.
  • the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the acknowledgement message of the RRC downlink message is a feedback message of the media access control MAC layer.
  • the sending module 1001 is specifically configured to send the uplink in a physical downlink control channel (PDCCH) of a downlink resource allocation (DL Assignment) that sends the RRC downlink message.
  • PDCCH physical downlink control channel
  • DL Assignment downlink resource allocation
  • the uplink grant of the RRC uplink response message and the downlink resource of the RRC downlink message are sent to the UE in the same message, so that the UE can obtain the RRC uplink response message before sending the acknowledgement message of the RRC downlink message.
  • the uplink grant thereby saving the time for the UE to wait for the uplink grant of the RRC uplink response message by the network device.
  • the sending module 1001 is specifically configured to: send the uplink authorization in a message packet that sends the RRC downlink message.
  • the message packet may adopt a data format of a Medium Access Control (MAC) Protocol Data Unit (PDU).
  • MAC Medium Access Control
  • PDU Protocol Data Unit
  • the MAC PDU consists of a string of bytes (8 bits).
  • a MAC PDU can contain a MAC Head, 0 to multiple MACSDUs, 0 to multiple MAC control units, and possibly padding.
  • the RRC downlink message is stored in a MAC Service Data Unit (SDU) in the MAC PDU
  • the uplink authorization is stored in a MAC Control Element (Control Element, CE) in the MAC PDU. in.
  • SDU Service Data Unit
  • CE MAC Control Element
  • the MAC SDU in the message packet stores a packet data packet after the RRC downlink message is RLC-packed.
  • the packet data packet may be any one of the RRC downlink messages after the RLC packet.
  • the uplink grant may be sent together with the first data packet after the RLC packet is sent by the RRC downlink message, or may be delivered together with the last data packet after the RRC downlink message is sent by the RLC packet.
  • the MAC SDU in the message packet stores the entire content of the RRC downlink message.
  • the uplink authorization of the RRC uplink response message and the RRC downlink message are sent to the UE in the same message, so that the UE receives the uplink authorization of the RRC uplink response message while receiving the RRC downlink message, thereby saving The time when the UE waits for the network device to allocate the uplink grant of the RRC uplink response message.
  • the RRC uplink response message is further used to indicate that the UE confirms receiving the RRC downlink message, where the UE The acknowledgment message of the RRC downlink message is not sent.
  • the RRC procedure delay RRC procedureDelay may take a value of 0.
  • the radio resource control procedure delay RRC procedureDelay value greater than 0 is also allowed.
  • the RRC downlink message when the RRC downlink message is sent by the AM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message; or The RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the RRC downlink message when the RRC downlink message is sent by the TM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message;
  • the RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • there may be other RRC connection procedures for transmitting RRC messages in the TM which are not described in detail in the embodiments of the present application.
  • the downlink resource allocation of the RRC downlink message includes multiple downlink resource allocations, and the downlink resource allocation carried in the first message may be any one of the multiple downlink resource allocations. .
  • the downlink resource allocation of the RRC downlink message includes one downlink resource allocation, and the uplink grant of the RRC uplink response message is delivered together with the downlink resource allocation.
  • the receiving module 1002 is specifically configured to: receive an RRC request message sent by the UE.
  • the network device may send an RRC downlink message corresponding to the RRC request message to the UE.
  • the network device may also actively send an RRC downlink message to the UE, which is not limited herein.
  • the RRC request message is an RRC process instance that belongs to the same RRC processing identifier corresponding to the RRC downlink message and the RRC uplink response message.
  • the RRC request message is an RRC Connection Resume Request message
  • the RRC downlink message is RRC a connection setup message
  • the RRC uplink response message is an RRC Connection Setup Complete message
  • the RRC request message is an RRC Connection Setup Request message
  • the RRC downlink message is an RRC Connection Reestablishment message
  • the RRC uplink response message When it is an RRC Connection Reestablishment Complete message, the RRC request message is an RRC Connection Reestablishment Request message, and the like.
  • the network device 1000 can also perform the method of FIG. 2 and implement the functions of the network device in the embodiment shown in FIG. 3-8, and details are not described herein again.
  • FIG. 11 is a schematic structural diagram of a user equipment 1100 according to an embodiment of the present application.
  • the user equipment 1100 may include: a receiving module 1101, a processing module 1003, and a sending module 1102.
  • the receiving module 1101 is configured to receive an RRC downlink message sent by the network device.
  • the receiving module 1101 is further configured to receive, in a time range of the RRC process delay of the RRC downlink message, an uplink grant of the RRC uplink response message corresponding to the RRC downlink message that is previously allocated and sent by the network device.
  • the processing module 1003 is configured to determine an uplink resource of the uplink grant indication.
  • the sending module 1102 is configured to send the RRC uplink response message from the RRC layer on the uplink resource indicated by the uplink grant.
  • the user equipment receives the uplink grant of the RRC uplink response message that is pre-allocated and sent by the network device in the time range of the RRC process delay, so that the network device does not need to wait for the network device to allocate the uplink grant when sending the RRC uplink response message.
  • the delay between receiving the RRC downlink message and the feedback RRC uplink response message is reduced, so that the control plane delay can meet the shorter delay requirement.
  • the receiving time of the uplink grant is after the receiving time of the RRC downlink message
  • the receiving time of the uplink grant is not later than the acknowledgement message of the RRC downlink message
  • the acknowledgement message of the RRC downlink message is a feedback message of the radio link control RLC layer.
  • the acknowledgement message of the RRC downlink message is a feedback message of the media access control MAC layer.
  • the receiving module 1101 is specifically configured to: receive the uplink grant in a physical layer downlink control channel PDCCH that receives a downlink resource allocation of the RRC downlink message.
  • the uplink grant of the RRC uplink response message may be sent in the same downlink control channel (PDCCH) as the downlink resource allocation (DL Assignment) of the RRC downlink message.
  • the network device may send the uplink grant of the RRC uplink response message and the downlink resource allocation of the RRC downlink message to the UE through a downlink control information (DCI).
  • DCI downlink control information
  • the uplink grant of the RRC uplink response message and the downlink resource allocation of the RRC downlink message are received in the same message, so that the UE can obtain the uplink grant of the RRC uplink response message before sending the acknowledgement message of the RRC downlink message. Therefore, the time for the UE to wait for the uplink grant of the RRC uplink response message by the network device is saved.
  • the receiving module 1101 is specifically configured to: receive the uplink authorization in a message packet that receives the RRC downlink message.
  • the message packet may adopt a data format of a Medium Access Control (MAC) Protocol Data Unit (PDU).
  • MAC Medium Access Control
  • PDU Protocol Data Unit
  • the MAC PDU consists of a string of bytes (8 bits).
  • a MAC PDU may contain one MAC header, 0 to multiple MACSDUs, 0 to multiple MAC control units, and possibly padding.
  • the RRC downlink message is stored in a MAC Service Data Unit (SDU) in the MAC PDU
  • the uplink authorization is stored in a MAC Control Element (Control Element, CE) in the MAC PDU. in.
  • SDU Service Data Unit
  • CE MAC Control Element
  • the MAC SDU in the message packet stores a packet data packet after the RRC downlink message is RLC-packed.
  • the packet data packet may be any one of the RRC downlink messages after the RLC packet.
  • the uplink grant may be sent together with the first data packet after the RLC packet is sent by the RRC downlink message, or may be delivered together with the last data packet after the RRC downlink message is sent by the RLC packet.
  • the MAC SDU in the message packet stores the entire content of the RRC downlink message.
  • the uplink authorization and the RRC downlink message of the RRC uplink response message are received in the same message, so that the UE receives the uplink authorization of the RRC uplink response message while receiving the RRC downlink message, thereby saving the UE waiting.
  • the RRC uplink response message is further used to indicate to acknowledge receiving the RRC downlink message, where the network device does not receive the The confirmation message of the RRC downlink message.
  • the RRC procedure delay RRC procedureDelay may take a value of 0.
  • the radio resource control procedure delay RRC procedureDelay value greater than 0 is also allowed.
  • the RRC downlink message when the RRC downlink message is sent by the AM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC Connection Resume Complete message; or The RRC downlink message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message, and the RRC uplink response message may be an RRC Connection Reconfiguration Complete message, and so on.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the RRC downlink message when the RRC downlink message is sent by the TM, the RRC downlink message may be an RRC Connection Resume message, and the RRC uplink response message may be an RRC connection recovery complete (RRC The RRC Connection Reconfiguration message may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration Complete) message, and the RRC Connection Reconfiguration Complete message may be an RRC Connection Reconfiguration Complete message.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • there may be other RRC connection procedures for transmitting RRC messages in the TM which are not described in detail in the embodiments of the present application.
  • the downlink resource allocation of the RRC downlink message includes multiple downlink resource allocations, and the downlink resource allocation carried in the first message may be any one of the multiple downlink resource allocations. .
  • the downlink resource allocation of the RRC downlink message includes one downlink resource allocation, and the uplink grant of the RRC uplink response message is delivered together with the downlink resource allocation.
  • the sending module 1102 is further configured to: send an RRC request message.
  • the RRC request message is an RRC process instance that belongs to the same RRC processing identifier corresponding to the RRC downlink message and the RRC uplink response message.
  • the RRC request message is an RRC Connection Resume Request message
  • the RRC downlink message is RRC a connection setup message
  • the RRC uplink response message is an RRC Connection Setup Complete message
  • the RRC request message is an RRC Connection Setup Request message
  • the RRC downlink message is an RRC Connection Reestablishment message
  • the RRC uplink response message When it is an RRC Connection Reestablishment Complete message, the RRC request message is an RRC Connection Reestablishment Request message, and the like.
  • the user equipment 1100 can also perform the method shown in FIG. 9 and implement the functions of the user equipment in the embodiment shown in FIG. 3-8, and details are not described herein again.
  • FIG. 12 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application.
  • Network device 1200 can include a processor 1202, a transmitter 1201, and a receiver 1204.
  • the network device 1200 may be a network side device such as a base station.
  • the receiver 1204, the transmitter 1201, and the processor 1202 are connected to each other through a bus 1206 system.
  • the bus 1206 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 12, but it does not mean that there is only one bus or one type of bus.
  • transmitter 1201 and receiver 1204 can be coupled to antenna 1205.
  • the network device 1200 may further include a memory 1203 for storing a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 1203 can include read only memory and random access memory and provides instructions and data to processor 1202.
  • the memory 1203 may include a high-speed random access memory (RAM), and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1202 is configured to perform the following operations, and optionally execute the program stored in the memory 1203, and specifically, to perform the following operations:
  • Processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1202 or an instruction in a form of software.
  • the processor 1202 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., or may be a digital signal processor (DSP), dedicated.
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1203, and the processor 1202 reads the information in the memory 1203 and completes the steps of the above method in combination with its hardware.
  • FIG. 13 is a schematic structural diagram of a user equipment 1300 according to an embodiment of the present application.
  • User equipment 1300 can include a processor 1302, a transmitter 1301, and a receiver 1304.
  • Receiver 1304, transmitter 1301 and processor 1302 are interconnected by a bus 1306 system.
  • the bus 1306 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 13, but it does not mean that there is only one bus or one type of bus.
  • transmitter 1301 and receiver 1304 can be coupled to antenna 1305.
  • the user equipment 1300 may further include a memory 1303 for storing a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 1303 can include read only memory and random access memory and provides instructions and data to processor 1302.
  • the memory 1303 may include a high speed random access memory (RAM), and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1302 is configured to perform the following operations, optionally executing the program stored in the memory 1303, and specifically for performing the following operations:
  • the RRC uplink response message is sent from the RRC layer on the uplink resource indicated by the uplink grant.
  • the method performed by the user equipment disclosed in the embodiment shown in FIG. 3-9 of the present application may be applied to the processor 1302 or implemented by the processor 1302.
  • the processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1302 or an instruction in a form of software.
  • the processor 1302 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., or may be a digital signal processor (DSP), dedicated.
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • other programmable Logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1303, and the processor 1302 reads the information in the memory 1303 and completes the steps of the above method in combination with its hardware.
  • the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be caused to perform the method of the embodiment shown in FIG. 2.
  • Another embodiment of the present application also provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device includes multiple applications When the device is executed, the portable electronic device can be caused to perform the method of the embodiment shown in FIG.
  • the communication device 1400 can include a network device 1401 and a user device 1402.
  • the network device 1401 may be the network device 1000 shown in FIG. 10 or the network device 1200 shown in FIG. 12; the user device 1402 may be the user device 1000 shown in FIG. 11, or the user device 1300 shown in FIG.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including Several instructions to make a computer device (can be a personal meter) A computer, server, or network device, etc.) performs all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

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

Abstract

本申请实施例提供了一种消息输方法、设备和***，该方法包括：发送RRC下行消息；在该RRC下行消息的RRC过程时延的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权；在该上行授权指示的上行资源上接收UE从RRC层发送的该RRC上行响应消息。本申请实施例的消息输方法、设备和***，能够减少UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。

Description

消息传输方法、设备和***
本申请要求于2016年09月30日提交中国专利局、申请号为201610877439.1、申请名称为“消息传输方法、设备和***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及消息传输方法、设备和***。
背景技术
在长期演进(long term evolution，LTE)***中，用户设备(user equipment，UE)从空闲(IDLE)态进入连接态需要进行无线资源控制(radio resource control，RRC)的连接建立过程、连接恢复过程、连接重建过程或连接重配置过程。以RRC连接恢复过程为例,其空口的通信过程如下：
(1)随机接入(random access)过程初始化,UE选择物理随机接入信道(physical random access channel，PRACH)资源以及对应的序列(Preamble)码；
(2)在PRACH资源上发送Preamble；
(3)网络设备处理接收到Preamble；
(4)网络设备回复随机接入响应(random access response，RAR)消息；
(5)UE接收RAR消息并处理，RAR消息中包含了下一条上行消息的上行授权(UL Grant)；
(6)UE在UL Grant上发送RRC连接恢复请求(RRC Connection Resume Request)消息；
(7)网络设备收到RRC Connection Resume Request消息后进行处理；
(8)网络设备回复RRC连接恢复(RRC Connection Resume)消息；
(9)UE收到RRC Connection Resume消息并处理；
(10)UE发送RRC连接恢复完成(RRC Connection Resume Complete)消息。
LTE的RRC连接建立过程、RRC连接重配置过程、RRC连接重建过程与上述过程类似，区别仅在于具体的消息是与连接过程或连接重建相关的消息。
LTE的RRC协议中规定，步骤9中UE收到RRC Connection Resume消息的处理时延为15ms，而5G要求从IDLE态到CONNECTED态的控制面时延是10ms，当前LTE的RRC连接恢复过程、RRC连接建立过程、RRC连接重配置过程或者RRC连接重建过程都是不满足5G的时延需求。
因此，需要一种合适的方案，能够缩短UE接收并处理RRC信令消息的处理时延。
发明内容
本申请实施例提供一种消息输方法、设备和***，能够减少UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。
第一方面，提出了一种消息传输方法，该方法包括：发送RRC下行消息；在该RRC下行消息的RRC过程时延的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权；在该上行授权指示的上行资源上接收UE从RRC层发送的该RRC上行响应消息。
结合第一方面，在第一种可能的实现方式中，当该上行授权的发送时间在该RRC下行消息的发送时间之后时，该上行授权的发送时间不晚于该RRC下行消息的确认消息的接收时间。
结合第一方面的第一种可能的实现方式，在第二种可能的实现方式中，当该RRC下行消息以透明传输模式TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
结合第一方面，在第三种可能的实现方式中，在该RRC下行消息的RRC过程时延的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权具体实现为：在发送该RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中发送该上行授权。
结合第一方面，在第四种可能的实现方式中，在该RRC下行消息的RRC过程时延的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权具体实现为：在发送该RRC下行消息的消息包中发送该上行授权。
结合第一方面的第四种可能的实现方式，在第五种可能的实现方式中，具体实现为：该消息包采用MAC PDU的数据格式，该RRC下行消息存储于MAC PDU的MAC SDU中，该上行授权存储于MAC PDU中的MAC CE。
结合第一方面的第五种可能的实现方式，在第六种可能的实现方式中，具体实现为：当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包；或者，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
结合第一方面的第三种可能的实现方式至第一方面的第六种可能的实现方式中任一种可能的实现方式，在第七种可能的实现方式中，该RRC上行响应消息还用于指示该UE确认接收该RRC下行消息，其中，该UE未发送该RRC下行消息的确认消息。
结合第一方面的第三种可能的实现方式至第一方面的第七种可能的实现方式中任一种可能的实现方式，，在第八种可能的实现方式中，具体实现为：该无线资源控制过程时延RRC procedureDelay等于0。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第八种可能的实现方式中任一种可能的实现方式，在第九种可能的实现方式中，该RRC下行消息和该RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
第二方面，提出了一种网络设备，该网络设备包括：发送模块，用于发送RRC下行消息；处理模块，用于在该RRC下行消息的RRC过程时延的时间范围内预先分配该RRC下行消息对应的RRC上行响应消息的上行授权；该发送模块还用于在该RRC过程时延的 时间范围内发送该上行授权；接收模块，用于在该上行授权指示的上行资源上接收UE从RRC层发送的该RRC上行响应消息。
结合第二方面，在第一种可能的实现方式中，当该上行授权的发送时间在该RRC下行消息的发送时间之后时，该上行授权的发送时间不晚于该RRC下行消息的确认消息的接收时间。
结合第二方面的第一种可能的实现方式，在第二种可能的实现方式中，当该RRC下行消息以透明传输模式TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
结合第二方面，在第三种可能的实现方式中，该发送模块具体用于：在发送该RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中发送该上行授权。
结合第二方面，在第四种可能的实现方式中，该发送模块具体用于：在发送该RRC下行消息的消息包中发送该上行授权。
结合第二方面的第四种可能的实现方式，在第五种可能的实现方式中，具体实现为：该消息包采用MAC PDU的数据格式，该RRC下行消息存储于MAC PDU的MAC SDU中，该上行授权存储于MAC PDU中的MAC CE。
结合第二方面的第五种可能的实现方式，在第六种可能的实现方式中，具体实现为：当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包；或者，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
结合第二方面的第三种可能的实现方式至第二方面的第六种可能的实现方式中任一种可能的实现方式，在第七种可能的实现方式中，该RRC上行响应消息还用于指示该UE确认接收该RRC下行消息，其中，该UE未发送该RRC下行消息的确认消息。
结合第二方面的第三种可能的实现方式至第二方面的第七种可能的实现方式中任一种可能的实现方式，，在第八种可能的实现方式中，具体实现为：该无线资源控制过程时延RRC procedureDelay等于0。
结合第二方面或第二方面的第一种可能的实现方式至第二方面的第八种可能的实现方式中任一种可能的实现方式，在第九种可能的实现方式中，该RRC下行消息和该RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
第三方面，提供了另一种网络设备，包括处理器、发射机和接收机，该处理器用于执行通过该发射机和该接收机执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提出了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第五方面，提出了一种消息传输方法，该方法包括：接收网络设备发送的RRC下行消息；在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权；在该上行授权指示的上行资源上从RRC层发送该RRC上行响应消息。
结合第五方面，在第一种可能的实现方式中，当该上行授权的接收时间在该RRC下行消息的接收时间之后时，该上行授权的接收时间不晚于该RRC下行消息的确认消息。
结合第五方面的第一种可能的实现方式，在第二种可能的实现方式中，当该RRC下行消息以透明传输模式TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
结合第五方面，在第三种可能的实现方式中，在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权具体实现为：在接收该RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中接收该上行授权。
结合第五方面，在第四种可能的实现方式中，在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权具体实现为：在接收该RRC下行消息的消息包中接收该上行授权。
结合第五方面的第四种可能的实现方式，在第五种可能的实现方式中，具体实现为：该消息包采用MAC PDU的数据格式，该RRC下行消息存储于MAC PDU的MAC SDU中，该上行授权存储于MAC PDU中的MAC CE。
结合第五方面的第五种可能的实现方式，在第六种可能的实现方式中，具体实现为：当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包；或者，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
结合第五方面的第三种可能的实现方式至第五方面的第六种可能的实现方式中任一种可能的实现方式，在第七种可能的实现方式中，该RRC上行响应消息还用于指示确认接收该RRC下行消息，其中，该网络设备不会接收到该RRC下行消息的确认消息。
结合第五方面的第三种可能的实现方式至第五方面的第七种可能的实现方式中任一种可能的实现方式，，在第八种可能的实现方式中，具体实现为：该无线资源控制过程时延RRC procedureDelay等于0。
结合第五方面或第五方面的第一种可能的实现方式至第五方面的第八种可能的实现方式中任一种可能的实现方式，在第九种可能的实现方式中，该RRC下行消息和该RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
第六方面，提出了一种用户设备，该用户设备包括：接收模块，用于接收网络设备发送的RRC下行消息；该接收模块还用于在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权；处理模块，用于确定该上行授权指示的上行资源；发送模块，用于在该上行授权指示的上行资源上从RRC层发送该RRC上行响应消息。
结合第六方面，在第一种可能的实现方式中，当该上行授权的接收时间在该RRC下行消息的接收时间之后时，该上行授权的接收时间不晚于该RRC下行消息的确认消息。
结合第六方面的第一种可能的实现方式，在第二种可能的实现方式中，当该RRC下行消息以透明传输模式TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
结合第六方面，在第三种可能的实现方式中，该接收模块具体用于：在接收该RRC 下行消息的下行资源分配的物理层下行控制信道PDCCH中接收该上行授权。
结合第六方面，在第四种可能的实现方式中，该接收模块具体用于：在接收该RRC下行消息的消息包中接收该上行授权。
结合第六方面的第四种可能的实现方式，在第五种可能的实现方式中，具体实现为：该消息包采用MAC PDU的数据格式，该RRC下行消息存储于MAC PDU的MAC SDU中，该上行授权存储于MAC PDU中的MAC CE。
结合第六方面的第五种可能的实现方式，在第六种可能的实现方式中，具体实现为：当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包；或者，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
结合第六方面的第三种可能的实现方式至第六方面的第六种可能的实现方式中任一种可能的实现方式，在第七种可能的实现方式中，该RRC上行响应消息还用于指示确认接收该RRC下行消息，其中，该网络设备不会接收到该RRC下行消息的确认消息。
结合第六方面的第三种可能的实现方式至第六方面的第七种可能的实现方式中任一种可能的实现方式，，在第八种可能的实现方式中，具体实现为：该无线资源控制过程时延RRC procedureDelay等于0。
结合第六方面或第六方面的第一种可能的实现方式至第六方面的第八种可能的实现方式中任一种可能的实现方式，在第九种可能的实现方式中，该RRC下行消息和该RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
第七方面，提供了另一种用户设备，包括处理器、发射机和接收机，该处理器用于执行通过该发射机和该接收机执行第五方面或第五方面的任意可能的实现方式中的方法。
第八方面，提出了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第五方面或第五方面的任意可能的实现方式中的方法的指令。
第九方面，提出了一种通信***，包括：
第二方面或第二方面的任意可能的实现方式中的网络设备，以及
第六方面或第六方面的任意可能的实现方式中用户设备；或者
第三方面或第三方面的任意可能的实现方式中的网络设备，以及
第七方面或第七方面的任意可能的实现方式中用户设备。
基于以上技术方案，本申请实施例的消息输方法、设备和***，在不晚于RRC下行消息的确认消息的接收时间上发送RRC上行响应消息的上行授权，使得UE侧能够在发送RRC上行响应消息时不需要等待网络设备分配上行授权，从而减少了UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。
附图说明
图1是现有技术RRC恢复过程的交互流程图。
图2是本申请的一个实施例RRC消息的传输方法流程图。
图3是本申请的一个实施例RRC过程的交互流程图。
图4是本申请的另一个实施例RRC过程的交互流程图。
图5是本申请的再一个实施例RRC过程的交互流程图。
图6是本申请的再一个实施例RRC过程的交互流程图。
图7是本申请的再一个实施例RRC过程的交互流程图。
图8是本申请的再一个实施例RRC过程的交互流程图。
图9是本申请的再一个实施例RRC过程的交互流程图。
图10是本申请的一个实施例网络设备的结构示意图。
图11是本申请的一个实施例用户设备的结构示意图。
图12是本申请的另一个实施例网络设备的结构示意图。
图13是本申请的另一个实施例用户设备的结构示意图。
图14是本申请的一个实施例通信***的***框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请的技术方案，可以应用于各种通信***，例如：全球移动通讯***(Global System of Mobile communication,GSM)，码分多址***(Code Division Multiple Access，CDMA)，宽带码分多址(Wideband Code Division Multiple Access Wireless，WCDMA)，通用分组无线业务(General Packet Radio Service，GPRS)，长期演进(Long Term Evolution，LTE)等。
用户设备(User Equipment，UE)，也可称之为移动终端(Mobile Terminal)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备。
网络设备可以是用于与移动设备通信的设备，网络设备可以是全球移动通讯(Global System of Mobile communication，GSM)或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)中的基站(NodeB，NB)，还可以是长期演进(Long Term Evolution，LTE)中的演进型基站(Evolutional Node B，eNB或eNodeB)或接入点，或者车载设备、可穿戴设备，未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的网络设备。
在介绍本申请提供的实施例之前，为便于理解，以LTE***为例，先介绍本申请实施例所涉及的技术术语。
无线链路控制(Radio Link Control，RLC)：每个RLC实体由RRC配置，并且根据业务类型有三种模式：透明模式(Transparent Mode，TM)、非确认模式(Unacknowledged Mode，UM)、确认模式(Acknowledged Mode，AM)。在控制平面，RLC向上层提供的业务为无线信令承载(Signalling Radio Bearer，SRB)；在用户平面，当分组数据汇 聚协议(Packet Data Convergence Protocol，PDCP)和广播与组播控制(Broadcast/Multicast Control，BMC)协议没有被该业务使用时，RLC向上层提供无线承载(Radio Bearer，RB)；否则RB业务由PDCP或BMC承载。
透明模式(TM)：发送实体在高层数据上不添加任何额外控制协议开销，仅根据业务类型决定是否进行分段操作。接收实体接收到的协议数据单元(Protocol Data Unit，PDU)如果出现错误，则根据配置，在错误标记后递交或者直接丢弃并向高层报告。TM模式的业务有实时语音业务等。
非确认模式(UM)：发送实体在高层PDU上添加必要的控制协议开销，然后进行传送但并不保证传递到对等实体，且没有使用重传协议。接收实体对所接收到的错误数据标记为错误后递交，或者直接丢弃并向高层报告。由于RLC PDU包含有顺序号，因此能够检测高层PDU的完整性。UM模式的业务有小区广播和IP电话等。
确认模式(AM)：发送实体在高层PDU上添加必要的控制协议开销后进行传送，并保证传递到对等实体。因为AM模式的RLC具有自动重传请求(Automatic Repeat-Request)能力，如果RLC层接收到错误的RLC PDU，就通知发送方的RLC重传这个PDU。由于RLC PDU中包含有顺序号信息，AM模式的RLC还支持数据向高层的顺序/乱序递交。AM模式是分组数据传输业务的标准模式，AM模式的业务有www和电子邮件下载等。
图1是现有技术中LTE的RRC恢复过程的交互流程图。如图1所示，在LTE的RRC恢复过程中，UE收到网络设备发送的RRC下行消息即RRC Connection Resume消息后，先在物理层进行循环冗余校验(Cyclical Redundancy Check，CRC)解码，解码正确后反馈确认消息(Acknowledgement，ACK)，否则反馈非确认消息(Negative ACKnowledgment，NACK)。若网络设备侧的RLC层对RRC Connection Resume消息进行了切包传输，除了在物理层对每一个物理包进行ACK/NACK反馈外，还需要在RLC层根据网络设备在RLC头(Header)中轮询(Polling)置位情况决定是否反馈状态报告(Status Report)。如果网络设备在RLC层最后一个片段(Segment)的RLC header中polling位置1，则UE会反馈Status Report。在实现上，由于网络设备polling置位后知道UE会发送Status Report，所以网络设备可以在发送完下行RRC Connection Resume消息后，接着会发送上行调度DCI，用于调度发送Status report的上行资源；而UE会在收到最后一个RLC PDU后发送Status Report。假设所有包传输正确，网络设备接收Status Report并确认RRC Connection Resume消息被正确接收后，发送上行调度的DCI，包含了发送RRC Connection Resume Complete消息的UL Grant。UE在Status Report发送成功后再去接收调度RRC Connection Resume Complete消息的DCI，解码成功后发送RRC Connection Resume Complete消息。
如图1的交互流程图所示，从UE接收RRC Connection Resume消息到UE发送RRC Connection Resume Complete消息，大约需要耗时15ms，而5G要求从IDLE态到CONNECTED态的控制面时延是10ms，当前LTE的RRC恢复过程不能满足5G的控制面时延需求。LTE的RRC连接建立过程、RRC连接重配置过程或者RRC连接重建过程过程与RRC连接恢复过程类似，也不能满足5G的控制面时延需求。
图2是本申请的一个实施例的消息传输方法的流程图。图2的方法由网络设备执行。图2的方法包括：
210，发送RRC下行消息。
网络设备可向UE发送RRC下行消息。
220，在该RRC下行消息的RRC过程时延的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权。
应理解，本申请实施例中，上行授权(UL Grant)用于指示网络设备为该RRC上行响应消息分配的上行调度资源。
应理解，本申请实施例中，网络设备在该RRC下行消息的RRC过程时延(RRC Procedure Delay)的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权，是指网络设备在接收到RRC下行消息的确认消息之前，提前为该RRC下行消息对应的RRC上行响应消息预先分配上行授权并发送给UE。
应理解，本申请实施例中，该RRC下行消息的RRC过程时延(RRC Procedure Delay)的时间范围内包括RRC过程时延为0的场景，此时，该上行授权与该RRC下行消息在同一子帧上发送。
应理解，该RRC上行响应消息是指UE在RRC层发送的RRC下行消息的反馈消息。具体地，该RRC下行消息和该RRC上行响应消息属于同一个RRC处理标识(RRC-TransactionIdentifier)的RRC过程实例。
230，在该上行授权指示的上行资源上接收该UE发送的该RRC上行响应消息。
本申请实施例中，网络设备在RRC过程时延的时间范围内预先分配RRC上行响应消息的上行授权并发送给UE，使得UE侧能够在发送RRC上行响应消息时不需要等待网络设备分配上行授权，从而减少了UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。
可选地，作为一个实施例，当该上行授权的发送时间在该RRC下行消息的发送时间之后时，该上行授权的发送时间不晚于该RRC下行消息的确认消息的接收时间。
可选地，在本申请实施例的另一种具体实现方式中，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
或者，可选地，在本申请实施例的一种具体实现方式中，当该RRC下行消息以TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息。
可选地，作为另一个实施例，步骤220具体实现为：在发送该RRC下行消息的下行资源分配(DL Assignment)的物理层下行控制信道(Physical Downlink Control Channel，PDCCH)中发送该上行授权。
应理解，本申请实施例中，该RRC上行响应消息的上行授权可以和该RRC下行消息的下行资源分配(DL Assignment)在同一下行控制信道(Physical Downlink Control Channel，PDCCH)中发送。例如，网络设备可以通过一个下行控制信息(Downlink control information，DCI)，将RRC上行响应消息的上行授权和RRC下行消息的下行资源分配一起发送给UE。
本申请实施例中，通过将RRC上行响应消息的上行授权和RRC下行消息的下行资源分配在同一条消息中发送给UE，使得UE在发送RRC下行消息的确认消息之前即可得到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，作为另一个实施例，步骤220具体实现为：在发送该RRC下行消息的消息包中发送该上行授权。
应理解，该消息包可以采用媒体接入控制(Medium Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)的数据格式。
MAC PDU，是由按字节(8bit)排布的字符串组成。一个MAC PDU可包含一个MAC头、0至多个MACSDU、0至多个MAC控制单元以及可能的填充(padding)。
在本申请实施例中，该RRC下行消息存储于该MAC PDU中的MAC服务数据单元(Service Data Unit，SDU)中，该上行授权存储于该MAC PDU中的MAC控制元素(Control Element，CE)中。
可选地，作为一个实施例，当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包。
应理解，该分组数据包可以是RRC下行消息经RLC分组后任意一个数据包。例如，该上行授权可以和RRC下行消息经RLC分组后第一个数据包一起下发，也可以和RRC下行消息经RLC分组后最后一个数据包一起下发。
或者，可选地，作为另一个实施例，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
应理解，当该RRC下行消息以TM发送时，RRC下行消息的所有内容都通过一个MAC PDU传输，该MAC PDU中还携带者该上行授权的信息。
本申请实施例中，通过将RRC上行响应消息的上行授权和RRC下行消息在同一条消息中发送给UE，使得UE在接收到RRC下行消息的同时接收到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，当网络设备将该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该RRC上行响应消息还用于指示该UE确认接收该RRC下行消息，其中，该UE未发送该RRC下行消息的确认消息。
应理解，当网络设备将该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该无线资源控制过程时延RRC procedureDelay可以取值为0。当然，该无线资源控制过程时延RRC procedureDelay取值大于0也是允许的。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者，该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。当然，还可能存在其它以AM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以TM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。类似的，还可能存在其它以TM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息的下行资源分配包括多个下行资源分配，该第一消息中携带的下行资源分配可以是该多个下行资源分配中的任意 一个。
或者，当该RRC下行消息以TM发送时，该RRC下行消息的下行资源分配包括1个下行资源分配，RRC上行响应消息的上行授权和该下行资源分配一起下发。
当然，应理解，部分RRC过程是以RRC请求消息开始的。此时，在步骤210之前，该方法还可包括：接收该UE发送的RRC请求消息。
网络设备在接收到UE发送的RRC请求消息，可向UE发送RRC请求消息对应的RRC下行消息。当然，应理解，网络设备也可能主动向UE发送RRC下行消息，本申请实施例在此不作限制。
应理解，该RRC请求消息是和RRC下行消息及RRC上行响应消息相对应的，属于同一个RRC处理标识的RRC过程实例。例如，当该RRC下行消息为RRC Connection Resume消息，该RRC上行响应消息为RRC Connection Resume Complete消息时，该RRC请求消息为RRC连接恢复请求(RRC Connection Resume Request)消息；当该RRC下行消息为RRC Connection Setup消息，该RRC上行响应消息为RRC Connection Setup Complete消息时，该RRC请求消息为RRC连接建立请求(RRC Connection Setup Request)消息；当该RRC下行消息为RRC Connection Reestablishment消息，该RRC上行响应消息为RRC Connection Reestablishment Complete消息时，该RRC请求消息为RRC连接重建立请求(RRC Connection Reestablishment Request)消息，等等。
应理解，在图2所示实施例中，如果网络设备在步骤220之后接收到UE从MAC层或RLC层发送的NACK消息，则网络设备即可确定UE接收或解码RRC下行消息失败，可不执行步骤230。
下面，将结合具体的实施例，对本申请实施例的方法做进一步地描述。
图3是本申请的一个实施例RRC过程的交互流程图。本申请实施例中，以RRC连接恢复过程为例进行举例说明。如图3所示，该方法包括：
301，UE向网络设备发送RRC连接恢复请求消息。
UE可向网络设备发送RRC连接恢复请求(RRC Connection Resume Request)消息。
应理解，本申请实施例中，步骤301及步骤301之前网络设备和UE执行的步骤可参考现有技术，本申请实施例在此不再赘述。
302，网络设备发送下行资源分配和上行授权。
网络设备在成功收到UE发送的RRC Connection Resume Request消息后，可在向UE发送RRC下行消息的下行资源分配(DL Assignment)的同时发送RRC上行响应消息的上行授权(UL Grant)。
具体地，在本申请实施例中，网络设备可向UE发送RRC Connection Resume消息的DL Assignment和RRC Connection Resume Complete消息的UL Grant。网络设备可通过一条DCI消息发送该DL Assignment和该UL Grant。
应理解，当UE在成功解码DCI后，可获得DL Assignment，该DL Assignment指示用于接收RRC Connection Resume消息的下行资源，同时UE还可获得UL Grant，该UL Grant指示用于发送RRC Connection Resume Complete消息的上行资源。
303，网络设备在下行资源分配指示的下行资源上以AM模式发送RRC连接恢复消息。
网络设备可在RRC Connection Resume消息的DL Assignment指示的下行资源上，向 UE发送该RRC Connection Resume消息。
应理解，在RRC连接恢复过程中，网络设备的RLC层以AM模式发送RRC Connection Resume消息。网络设备的RLC层对RRC Connection Resume消息进行切包传输，并在RLC层最后一个分片(Segment)的RLC头(header)中轮询(polling)位置1。如果网络设备在RLC层最后一个片段(Segment)的RLC header中polling位置1，则UE会反馈RLC层确认消息。
304，UE发送MAC层确认消息。
当UE解码获得DL Assignment后，可在该DL Assignment指示的下行资源上接收网络设备发送的RRC Connection Resume消息。
当网络侧设备在RLC层以AM模式发送该RRC Connection Resume消息，UE在物理层即MAC层上会收到该RRC Connection Resume消息的多个物理包，UE需要对每一个物理包进行ACK/NACK反馈，该ACK/NACK反馈可称为MAC层确认消息。
305，UE在上行授权指示的上行资源上发送RLC确认消息和RRC连接恢复完成消息。
当网络设备的RLC层对RRC Connection Resume消息进行切包传输时，UE侧除了在MAC层对每一个物理包进行ACK/NACK反馈外，还需要在RLC层反馈RLC确认消息。
UE可根据网络设备在RLC header中polling置位情况决定是否反馈RLC确认消息。如果网络设备在RLC层最后一个Segment的RLC header中polling位置1，则UE需要反馈RLC确认消息。
可选地，UE可在该上行授权指示的上行资源上发送该RRC Connection Resume Complete消息，同时还在在上行授权指示的上行资源上发送该RLC确认消息。也即是说，UE可在该上行授权指示的上行资源上发送RRC Connection Resume Complete消息和RLC确认消息。具体地，该RLC确认消息可以是该RRC Connection Resume消息的状态报告(State Report)。在本申请实施例中，RRC Connection Resume Complete消息和State Report可以用一个MAC PDU中发送。
当然，应理解，RRC Connection Resume Complete消息和RLC确认消息以分开发送，例如，RRC Connection Resume Complete消息还可以在RLC确认消息之前发送，或者在RLC确认消息之后发送，等等。RRC Connection Resume Complete消息的发送时间取决于网络设备为RRC Connection Resume Complete消息分配的UL Grant所指示的上行资源所在的时间。
本申请实施例中，通过将RRC Connection Resume Complete的上行授权和RRC Connection Resume消息的下行资源分配一起发送，从而能够保证上行授权在不晚于RRC Connection Resume消息的确认消息的接收时间上发送，使得UE侧在发送RRC Connection Resume Complete消息时不需要额外等待网络设备配置上行授权的时延，从而减少了UE侧的控制面时延。
此外，本申请实施例中，当RRC Connection Resume消息以AM模式传输时，UE通过将RRC Connection Resume消息的RLC确认消息和RRC Connection Resume Complete消息在该上行授权指示的上行资源上一起发送，还能够节约上行调度资源的开销。
图4是本申请的另一个实施例RRC过程的交互流程图。本申请实施例中，以RRC连接恢复过程为例进行举例说明。如图4所示，该方法包括：
401，UE向网络设备发送RRC连接恢复请求消息。
UE可向网络设备发送RRC连接恢复请求(RRC Connection Resume Request)消息，请求发起RRC连接恢复过程。
应理解，本申请实施例中，步骤401及步骤401之前网络设备和UE执行的步骤可参考现有技术，本申请实施例在此不再赘述。
402，网络设备发送下行资源分配。
网络设备在成功收到UE发送的RRC Connection Resume Request消息后，可向UE发送RRC下行消息的下行资源分配(DL Assignment)。
具体地，在本申请实施例中，网络设备可向UE发送RRC Connection Resume消息的DL Assignment。网络设备可通过一条DCI消息发送该DL Assignment。其具体实现可参考现有技术。
应理解，当UE在成功解码DCI后，可获得DL Assignment，该DL Assignment指示用于接收RRC Connection Resume消息的下行资源。
403，网络侧设备在下行资源分配上以AM模式发送RRC连接恢复消息和上行授权。
本申请实施例中，网络设备在该DL Assignment指示的下行资源发送RRC Connection Resume消息，以及RRC Connection Resume Complete消息的UL Grant。
具体地，该UL Grant可以以MAC Control Element的形式与RRC Connection Resume消息组装成一个MAC PDU发送给UE。
与步骤303类似，网络设备的RLC层可采用AM模式发送RRC Connection Resume消息，即网络设备的RLC层以AM模式传输该MAC PDU。本申请实施例中，网络设备的RLC层对RRC Connection Resume消息进行切包传输，并在RLC层最后一个分片(Segment)的RLC头(header)中轮询(polling)位置1。如果网络设备在RLC层最后一个片段(Segment)的RLC header中polling位置1，则UE会反馈RLC层确认消息。
应理解，本申请实施例中，该UL Grant可以和该RRC下行消息经RLC分组后的任何一个Segment一起发送，例如该UL Grant可以和该RRC下行消息经RLC分组后的第1个Segment一起发送，或者该UL Grant可以和该RRC下行消息经RLC分组后的最后1个Segment一起发送，等等。其中，该RRC下行消息经RLC分组后的任何一个Segment都包含着该RRC下行消息的部分内容。
相应地，UE可解码获得DL Assignment上，并在该DL Assignment指示的下行资源上接收网络设备发送的MAC PDU，该MAC PDU中包含RRC Connection Resume消息的部分内容和该UL Grant。
404，UE发送MAC层确认消息。
如图3的步骤304所述，当网络侧设备在RLC层以AM模式发送该RRC Connection Resume消息，UE在物理层即MAC层上会收到该RRC Connection Resume消息的多个物理包，UE需要对每一个物理包进行ACK/NACK反馈，该ACK/NACK反馈可称为MAC层确认消息。
405，UE在上行授权指示的上行资源上发送RRC连接恢复完成消息。
406，UE发送RLC层确认消息。
当UE发送最后一个MAC层确认消息，表明UE已经完全接收RRC连接恢复消息， 此时，UE可发送RLC层确认消息。
应理解，上行授权所指示的上行资源的时间可在UE发送MAC层确认消息的时间之后，在UE发送RLC层确认消息的时间之前。
本申请实施例中，通过将RRC上行响应消息的上行授权和RRC下行消息在同一条消息中发送给UE，使得UE在接收到RRC下行消息的同时接收到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
图5是本申请的再一个实施例RRC过程的交互流程图。本申请实施例中，以RRC连接建立流程为例进行举例说明。如图5所示，该方法包括：
501，UE向网络设备发送RRC连接建立请求消息。
UE可向网络设备发送RRC Connection Setup Request消息，请求发起RRC连接建立过程。
应理解，本申请实施例中，步骤501及步骤501之前网络设备和UE执行的步骤可参考现有技术，本申请实施例在此不再赘述。
502，网络设备发送下行资源分配和上行授权。
网络设备在成功收到UE发送的RRC Connection Setup Request消息后，可在向UE发送RRC下行消息的下行资源分配(DL Assignment)的同时发送RRC上行响应消息的上行授权(UL Grant)。
具体地，在本申请实施例中，网络设备可向UE发送RRC Connection Setup消息的DL Assignment和RRC Connection Setup Complete消息的UL Grant。网络设备可通过一条DCI消息发送该DL Assignment和该UL Grant。
应理解，当UE在成功解码DCI后，可获得用于接收RRC Connection Setup消息的DL Assignment，同时获得用于发送RRC Connection Setup Complete消息的UL Grant。
503，网络设备在下行资源分配指示的下行资源上以TM模式发送RRC连接建立消息。
网络设备可在RRC Connection Setup消息的DL Assignment指示的下行资源上，向UE发送该RRC Connection Setup消息。
应理解，在RRC连接建立过程中，网络设备的RLC层可采用TM模式发送RRC Connection Setup消息。
相应地，UE可解码获得该DL Assignment，并在该DL Assignment指示的下行资源上，接收网络设备发送的RRC Connection Setup消息。该RRC Connection Setup消息可以采用MAC PDU的数据格式传输。
504，UE发送MAC层确认消息。
如果UE正确接收到RRC Connection Setup消息，UE还可在该UL Grant指示的上行资源上反馈MAC层确认消息，即RRC Connection Setup消息的ACK/NACK消息。
505，UE在上行授权指示的上行资源上发送RRC连接建立完成消息。
当UE在DL Assignment指示的下行资源上接收到该RRC Connection Setup消息后，可在该UL Grant指示的上行资源上发送RRC上行响应消息即RRC Connection Setup Complete消息。
本申请实施例中，通过将RRC Connection Setup Complete的上行授权和RRC Connection Setup消息的下行资源分配一起发送，从而能够保证上行授权在不晚于RRC  Connection Setup消息的确认消息的接收时间上发送，使得UE侧在发送RRC Connection Setup Complete消息时不需要额外等待网络设备配置上行授权的时延，从而减少了UE侧的控制面时延。
图6是本申请的再一个实施例RRC过程的交互流程图。本申请实施例中，以RRC连接建立过程为例进行举例说明。如图6所示，该方法包括：
601，UE向网络设备发送RRC连接建立请求消息。
UE可向网络设备发送RRC Connection Setup Request消息，请求发起RRC连接建立过程。
应理解，本申请实施例中，步骤601及步骤601之前网络设备和UE执行的步骤可参考现有技术，本申请实施例在此不再赘述。
602，网络设备发送下行资源分配。
网络设备在成功收到UE发送的RRC Connection Setup Request消息后，可向UE发送RRC下行消息的下行资源分配(DL Assignment)。
具体地，在本申请实施例中，网络设备可向UE发送RRC Connection Setup消息的DLAssignment。网络设备可通过一条DCI消息发送该DL Assignment。其具体实现可参考现有技术。
应理解，当UE在成功解码DCI后，可获得用于接收RRC Connection Setup消息的DL Assignment。
603，网络设备在下行资源分配指示的下行资源上以TM模式发送RRC连接建立消息和上行授权。
本申请实施例中，网络设备在该DL Assignment指示的下行资源上以TM模式发送RRC Connection Setup消息，以及RRC Connection Setup Complete消息的UL Grant。
具体地，该UL Grant可以以MAC Control Element的形式与RRC Connection Setup消息组装成一个MAC PDU发送给UE。该MAC PDU中包括RRC Connection Setup消息的全部内容和该UL Grant。
相应地，UE可解码获得该DL Assignment，并在该DL Assignment指示的下行资源上，接收网络设备发送的MAC PDU，该MAC PDU中包含RRC Connection Setup消息的全部内容和该UL Grant。
604，UE发送MAC层确认消息。
605，UE在上行授权指示的上行资源上发送RRC连接建立完成消息。
步骤604、605的具体实现可参考图5的步骤504、505，本申请实施例在此不再赘述。
本申请实施例中，通过将RRC Connection Setup Complete的上行授权和RRC Connection Setup消息的下行资源分配一起发送，使得UE侧在发送RRC Connection Setup Complete消息时不需要额外等待网络设备配置上行授权的时延，从而使得RRC Connection Setup Complete消息能够在RRC过程时延的时间范围内发送，减少了UE侧的控制面时延。
图7是本申请的一个实施例RRC过程的交互流程图。本申请实施例中，以RRC连接恢复过程为例进行举例说明。如图7所示，该方法包括：
701，UE向网络设备发送RRC连接恢复请求消息。
702，网络设备发送下行资源分配。
703，网络设备在下行资源分配指示的下行资源上以AM模式发送RRC连接恢复消息。
步骤701-703的具体实现可参考现有技术，本申请实施例在此不再赘述。
704，网络设备发送上行授权。
当网络设备以AM发送RRC连接恢复消息后，网络设备在接收到RLC确认消息之前，发送该上行授权。
应理解，该RRC过程中，如果网络设备以TM发送RRC下行消息，则网络设备在接收到MAC确认消息之前，发送该上行授权。
705，UE发送MAC层确认消息和RLC层确认消息，并在上行授权指示的上行资源上发送RRC连接恢复完成消息。
步骤705的具体实现可参考图3的步骤304、305，或图4的步骤404-406，本申请实施例在此不再赘述。
本申请实施例中，通过将RRC Connection Resume Complete的上行授权在RRC Connection Resume消息之后，RRC Connection Resume的RLC确认消息之前发送，使得UE侧在发送RRC Connection Resume Complete消息时不需要额外等待网络设备配置上行授权的时延，从而使得RRC Connection Resume Complete消息能够在RRC过程时延的时间范围内发送，减少了UE侧的控制面时延。
应理解，在图3-7所示实施例中，如果UE侧反馈的MAC层确认消息或RLC层确认消息中包括NACK消息，则表明UE没有正确接收RRC下行消息，此时，UE可不发送RRC上行响应消息。相应地，当网络设备接收到UE侧从MAC层或RLC层发送的NACK消息，则网络设备可知道预先分配的上行授权浪费了。
图8是本申请的一个实施例RRC过程的交互流程图。本申请实施例中，以RRC连接恢复过程为例进行举例说明。如图8所示，该方法包括：
801，UE向网络设备发送RRC连接恢复请求消息。
802，网络设备发送下行资源分配和上行授权。
803，网络设备在下行资源分配指示的下行资源上以AM模式发送RRC连接恢复消息。
步骤801-803的具体实现可参考图3的步骤301-303，本申请实施例在此不再赘述。
804，UE在上行授权指示的上行资源上发送RRC连接恢复完成消息。
本申请实施例中，当UE正确接收到网络设备发送的RRC连接恢复消息后，可不发送MAC层的ACK确认消息和RLC层的ACK确认消息，直接向网络设备发送RRC连接恢复完成消息。
相应的，网络侧设备在接收到该RRC连接恢复完成消息后，即可确定RRC连接恢复消息发送成功。
当然，应理解，如果本申请实施例的RRC过程中网络设备以TM发送RRC下行消息，且UE正确接收到到网络设备发送的RRC下行消息后，UE可不发送MAC层的ACK确认消息，直接向网络设备发送RRC上行响应消息。
此外，应理解，步骤801-803的流程也可用图4所示实施例的步骤401-403所示的流程代替。
应理解，本申请的RRC过程并不局限于图3-8所示的流程。例如，RRC连接重建立(RRC Connection Reestablishment)过程等以TM的方式发送RRC下行消息的RRC过程， 或者是RRC连接重配置(RRC Connection Reconfiguration)过程等以AM的方式发送RRC下行消息的RRC过程，等等，其具体实现可参考图3-8所示实施例，本申请实施例在此不再赘述。
图9是本申请的一个实施例的消息传输方法的流程图。图9的方法由UE执行。图9的方法包括：
910，接收网络设备发送的RRC下行消息。
920，在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权。
930，在该上行授权指示的上行资源上从RRC层发送该RRC上行响应消息。
本申请实施例中，用户设备在RRC过程时延的时间范围内接收网络设备预先分配并发送的RRC上行响应消息的上行授权，从而能够在发送RRC上行响应消息时不需要等待网络设备分配上行授权，减少了UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。
可选地，作为一个实施例，当该上行授权的接收时间在该RRC下行消息的接收时间之后时，该上行授权的接收时间不晚于该RRC下行消息的确认消息。
可选地，在本申请实施例的另一种具体实现方式中，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
或者，可选地，在本申请实施例的一种具体实现方式中，当该RRC下行消息以TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息。
可选地，作为另一个实施例，步骤920具体实现为：在接收该RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中接收该上行授权。
应理解，本申请实施例中，该RRC上行响应消息的上行授权可以和该RRC下行消息的下行资源分配(DL Assignment)在同一下行控制信道(Physical Downlink Control Channel，PDCCH)中发送。例如，网络设备可以通过一个下行控制信息(Downlink control information，DCI)，将RRC上行响应消息的上行授权和RRC下行消息的下行资源分配一起发送给UE。
本申请实施例中，通过在同一条消息中接收RRC上行响应消息的上行授权和RRC下行消息的下行资源分配，使得UE在发送RRC下行消息的确认消息之前即可得到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，作为另一个实施例，步骤920具体实现为：在接收该RRC下行消息的消息包中接收该上行授权。
应理解，该消息包可以采用媒体接入控制(Medium Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)的数据格式。
MAC PDU，是由按字节(8bit)排布的字符串组成。一个MAC PDU可包含一个MAC头、0至多个MACSDU、0至多个MAC控制单元以及可能的填充(padding)。
在本申请实施例中，该RRC下行消息存储于该MAC PDU中的MAC服务数据单元(Service Data Unit，SDU)中，该上行授权存储于该MAC PDU中的MAC控制元素(Control Element，CE)中。
可选地，作为一个实施例，当该RRC下行消息以AM发送时，该消息包中的MAC SDU 存储着该RRC下行消息经RLC分组后的一个分组数据包。
应理解，该分组数据包可以是RRC下行消息经RLC分组后任意一个数据包。例如，该上行授权可以和RRC下行消息经RLC分组后第一个数据包一起下发，也可以和RRC下行消息经RLC分组后最后一个数据包一起下发。
或者，可选地，作为另一个实施例，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
应理解，当该RRC下行消息以TM发送时，RRC下行消息的所有内容都通过一个MAC PDU传输，该MAC PDU中还携带者该上行授权的信息。
本申请实施例中，通过在同一条消息中接收RRC上行响应消息的上行授权和RRC下行消息，使得UE在接收到RRC下行消息的同时接收到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，当该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该RRC上行响应消息还用于指示确认接收该RRC下行消息，其中，该网络设备不会接收到该RRC下行消息的确认消息。
应理解，当该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该无线资源控制过程时延RRC procedureDelay可以取值为0。当然，该无线资源控制过程时延RRC procedureDelay取值大于0也是允许的。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者，该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。当然，还可能存在其它以AM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以TM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。类似的，还可能存在其它以TM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息的下行资源分配包括多个下行资源分配，该第一消息中携带的下行资源分配可以是该多个下行资源分配中的任意一个。
或者，当该RRC下行消息以TM发送时，该RRC下行消息的下行资源分配包括1个下行资源分配，RRC上行响应消息的上行授权和该下行资源分配一起下发。
当然，应理解，部分RRC过程是以RRC请求消息开始的。此时，在步骤910之前，该方法还可包括：发送RRC请求消息。
应理解，该RRC请求消息是和RRC下行消息及RRC上行响应消息相对应的，属于同一个RRC处理标识的RRC过程实例。例如，当该RRC下行消息为RRC Connection Resume消息，该RRC上行响应消息为RRC Connection Resume Complete消息时，该RRC 请求消息为RRC连接恢复请求(RRC Connection Resume Request)消息；当该RRC下行消息为RRC Connection Setup消息，该RRC上行响应消息为RRC Connection Setup Complete消息时，该RRC请求消息为RRC连接建立请求(RRC Connection Setup Request)消息；当该RRC下行消息为RRC Connection Reestablishment消息，该RRC上行响应消息为RRC Connection Reestablishment Complete消息时，该RRC请求消息为RRC连接重建立请求(RRC Connection Reestablishment Request)消息，等等。
图9所示的方法的具体实现可参考图3-8所示实施例，本申请实施例在此不再赘述。
当然，应理解，如果UE未能够正确接收并解码RRC下行消息，UE可反馈NACK消息。此时，UE不会执行步骤930。
图10是本申请实施例网络设备1000的结构示意图。如图10所示，网络设备1000可包括：发送模块1001、处理模块1003和接收模块1002。
发送模块1001，用于发送RRC下行消息。
处理模块1003，用于在该RRC下行消息的RRC过程时延的时间范围内预先分配该RRC下行消息对应的RRC上行响应消息的上行授权。
该发送模块1001还用于发送该上行授权。
接收模块1002，用于在该上行授权指示的上行资源上接收UE从RRC层发送的该RRC上行响应消息。
本申请实施例中，网络设备在RRC过程时延的时间范围内预先分配RRC上行响应消息的上行授权并发送给UE，使得UE侧能够在发送RRC上行响应消息时不需要等待网络设备分配上行授权，从而减少了UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。
可选地，作为一个实施例，当该上行授权的发送时间在该RRC下行消息的发送时间之后时，该上行授权的发送时间不晚于该RRC下行消息的确认消息的接收时间。
可选地，在本申请实施例的另一种具体实现方式中，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
或者，可选地，在本申请实施例的一种具体实现方式中，当该RRC下行消息以TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息。
可选地，作为另一个实施例，该发送模块1001具体用于：在发送该RRC下行消息的下行资源分配(DL Assignment)的物理层下行控制信道(Physical Downlink Control Channel，PDCCH)中发送该上行授权。
本申请实施例中，通过将RRC上行响应消息的上行授权和RRC下行消息的下行资源分配在同一条消息中发送给UE，使得UE在发送RRC下行消息的确认消息之前即可得到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，作为另一个实施例，该发送模块1001具体用于：在发送该RRC下行消息的消息包中发送该上行授权。
应理解，该消息包可以采用媒体接入控制(Medium Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)的数据格式。
MAC PDU，是由按字节(8bit)排布的字符串组成。一个MAC PDU可包含一个MAC 头、0至多个MACSDU、0至多个MAC控制单元以及可能的填充(padding)。
在本申请实施例中，该RRC下行消息存储于该MAC PDU中的MAC服务数据单元(Service Data Unit，SDU)中，该上行授权存储于该MAC PDU中的MAC控制元素(Control Element，CE)中。
可选地，作为一个实施例，当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包。
应理解，该分组数据包可以是RRC下行消息经RLC分组后任意一个数据包。例如，该上行授权可以和RRC下行消息经RLC分组后第一个数据包一起下发，也可以和RRC下行消息经RLC分组后最后一个数据包一起下发。
或者，可选地，作为另一个实施例，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
应理解，当该RRC下行消息以TM发送时，RRC下行消息的所有内容都通过一个MAC PDU传输，该MAC PDU中还携带者该上行授权的信息。
本申请实施例中，通过将RRC上行响应消息的上行授权和RRC下行消息在同一条消息中发送给UE，使得UE在接收到RRC下行消息的同时接收到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，当网络设备将该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该RRC上行响应消息还用于指示该UE确认接收该RRC下行消息，其中，该UE未发送该RRC下行消息的确认消息。
应理解，当网络设备将该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该无线资源控制过程时延RRC procedureDelay可以取值为0。当然，该无线资源控制过程时延RRC procedureDelay取值大于0也是允许的。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者，该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。当然，还可能存在其它以AM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以TM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。类似的，还可能存在其它以TM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息的下行资源分配包括多个下行资源分配，该第一消息中携带的下行资源分配可以是该多个下行资源分配中的任意一个。
或者，当该RRC下行消息以TM发送时，该RRC下行消息的下行资源分配包括1个下行资源分配，RRC上行响应消息的上行授权和该下行资源分配一起下发。
当然，应理解，该接收模块1002具体用于：接收该UE发送的RRC请求消息。
网络设备在接收到UE发送的RRC请求消息，可向UE发送RRC请求消息对应的RRC下行消息。当然，应理解，网络设备也可能主动向UE发送RRC下行消息，本申请实施例在此不作限制。
应理解，该RRC请求消息是和RRC下行消息及RRC上行响应消息相对应的，属于同一个RRC处理标识的RRC过程实例。例如，当该RRC下行消息为RRC Connection Resume消息，该RRC上行响应消息为RRC Connection Resume Complete消息时，该RRC请求消息为RRC连接恢复请求(RRC Connection Resume Request)消息；当该RRC下行消息为RRC Connection Setup消息，该RRC上行响应消息为RRC Connection Setup Complete消息时，该RRC请求消息为RRC连接建立请求(RRC Connection Setup Request)消息；当该RRC下行消息为RRC Connection Reestablishment消息，该RRC上行响应消息为RRC Connection Reestablishment Complete消息时，该RRC请求消息为RRC连接重建立请求(RRC Connection Reestablishment Request)消息，等等。
网络设备1000还可执行图2的方法，并实现网络设备在图3-8所示实施例的功能，本申请实施例在此不再赘述。
图11是本申请实施例用户设备1100的结构示意图。如图11所示，用户设备1100可包括：接收模块1101、处理模块1003和发送模块1102。
接收模块1101，用于接收网络设备发送的RRC下行消息。
该接收模块1101还用于在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权。
该处理模块1003用于确定上行授权指示的上行资源。
发送模块1102，用于在该上行授权指示的上行资源上从RRC层发送该RRC上行响应消息。
本申请实施例中，用户设备在RRC过程时延的时间范围内接收网络设备预先分配并发送的RRC上行响应消息的上行授权，从而能够在发送RRC上行响应消息时不需要等待网络设备分配上行授权，减少了UE从接收RRC下行消息到反馈RRC上行响应消息之间的时延，使得控制面时延能够满足更短的时延要求。
可选地，作为一个实施例，当该上行授权的接收时间在该RRC下行消息的接收时间之后时，该上行授权的接收时间不晚于该RRC下行消息的确认消息。
可选地，在本申请实施例的另一种具体实现方式中，当该RRC下行消息以确认模式AM发送时，该RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
或者，可选地，在本申请实施例的一种具体实现方式中，当该RRC下行消息以TM发送时，该RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息。
可选地，作为另一个实施例，该接收模块1101具体用于：在接收该RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中接收该上行授权。
应理解，本申请实施例中，该RRC上行响应消息的上行授权可以和该RRC下行消息的下行资源分配(DL Assignment)在同一下行控制信道(Physical Downlink Control Channel，PDCCH)中发送。例如，网络设备可以通过一个下行控制信息(Downlink control information，DCI)，将RRC上行响应消息的上行授权和RRC下行消息的下行资源分配一起发送给UE。
本申请实施例中，通过在同一条消息中接收RRC上行响应消息的上行授权和RRC下行消息的下行资源分配，使得UE在发送RRC下行消息的确认消息之前即可得到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，作为另一个实施例，该接收模块1101具体用于：在接收该RRC下行消息的消息包中接收该上行授权。
应理解，该消息包可以采用媒体接入控制(Medium Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)的数据格式。
MAC PDU，是由按字节(8bit)排布的字符串组成。一个MAC PDU可包含一个MAC头、0至多个MACSDU、0至多个MAC控制单元以及可能的填充(padding)。
在本申请实施例中，该RRC下行消息存储于该MAC PDU中的MAC服务数据单元(Service Data Unit，SDU)中，该上行授权存储于该MAC PDU中的MAC控制元素(Control Element，CE)中。
可选地，作为一个实施例，当该RRC下行消息以AM发送时，该消息包中的MAC SDU存储着该RRC下行消息经RLC分组后的一个分组数据包。
应理解，该分组数据包可以是RRC下行消息经RLC分组后任意一个数据包。例如，该上行授权可以和RRC下行消息经RLC分组后第一个数据包一起下发，也可以和RRC下行消息经RLC分组后最后一个数据包一起下发。
或者，可选地，作为另一个实施例，当该RRC下行消息以TM发送时，该消息包中的MAC SDU存储着该RRC下行消息的全部内容。
应理解，当该RRC下行消息以TM发送时，RRC下行消息的所有内容都通过一个MAC PDU传输，该MAC PDU中还携带者该上行授权的信息。
本申请实施例中，通过在同一条消息中接收RRC上行响应消息的上行授权和RRC下行消息，使得UE在接收到RRC下行消息的同时接收到RRC上行响应消息的上行授权，从而节省了UE等待网络设备分配RRC上行响应消息的上行授权的时间。
可选地，当该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该RRC上行响应消息还用于指示确认接收该RRC下行消息，其中，该网络设备不会接收到该RRC下行消息的确认消息。
应理解，当该上行授权与该RRC下行消息或RRC下行消息的下行资源分配一起发送时，该无线资源控制过程时延RRC procedureDelay可以取值为0。当然，该无线资源控制过程时延RRC procedureDelay取值大于0也是允许的。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC Connection Resume Complete)消息；或者，该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。当然，还可能存在其它以AM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以TM发送时，该RRC下行消息可以是RRC连接恢复(RRC Connection Resume)消息，该RRC上行响应消息可以是RRC连接恢复完成(RRC  Connection Resume Complete)消息；或者该RRC下行消息可以是RRC连接重配置(RRC Connection Reconfiguration)消息，该RRC上行响应消息可以是RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，等等。类似的，还可能存在其它以TM传输RRC消息的RRC连接过程，本申请实施例不再一一赘述。
应理解，当该RRC下行消息以AM发送时，该RRC下行消息的下行资源分配包括多个下行资源分配，该第一消息中携带的下行资源分配可以是该多个下行资源分配中的任意一个。
或者，当该RRC下行消息以TM发送时，该RRC下行消息的下行资源分配包括1个下行资源分配，RRC上行响应消息的上行授权和该下行资源分配一起下发。
当然，应理解，部分RRC过程是以RRC请求消息开始的。此时，该发送模块1102还用于：发送RRC请求消息。
应理解，该RRC请求消息是和RRC下行消息及RRC上行响应消息相对应的，属于同一个RRC处理标识的RRC过程实例。例如，当该RRC下行消息为RRC Connection Resume消息，该RRC上行响应消息为RRC Connection Resume Complete消息时，该RRC请求消息为RRC连接恢复请求(RRC Connection Resume Request)消息；当该RRC下行消息为RRC Connection Setup消息，该RRC上行响应消息为RRC Connection Setup Complete消息时，该RRC请求消息为RRC连接建立请求(RRC Connection Setup Request)消息；当该RRC下行消息为RRC Connection Reestablishment消息，该RRC上行响应消息为RRC Connection Reestablishment Complete消息时，该RRC请求消息为RRC连接重建立请求(RRC Connection Reestablishment Request)消息，等等。
用户设备1100还可执行图9所示的方法，并实现用户设备在图3-8所示实施例的功能，本申请实施例在此不再赘述。
图12是本申请实施例网络设备1200的结构示意图。网络设备1200可包括处理器1202、发射机1201和接收机1204。在具体的应用中，该网络设备1200可以是基站等网络侧设备。
接收机1204、发射机1201和处理器1202通过总线1206***相互连接。总线1206可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。具体的应用中，发射机1201和接收机1204可以耦合到天线1205。
可选地，网络设备1200还可包括存储器1203，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1203可以包括只读存储器和随机存取存储器，并向处理器1202提供指令和数据。存储器1203可能包含高速随机存取存储器(Random-Access Memory，RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少1个磁盘存储器。
处理器1202，用于执行以下操作，可选地，执行存储器1203所存放的程序，并具体用于执行以下操作：
发送RRC下行消息；
在该RRC下行消息的RRC过程时延的时间范围内预先分配并发送该RRC下行消息对应的RRC上行响应消息的上行授权；
在该上行授权指示的上行资源上接收UE从RRC层发送的该RRC上行响应消息。
上述如本申请图2-8所示实施例揭示的网络设备执行的方法可以应用于处理器1202中，或者由处理器1202实现。处理器1202可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1202中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1202可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1203，处理器1202读取存储器1203中的信息，结合其硬件完成上述方法的步骤。
图13是本申请实施例用户设备1300的结构示意图。用户设备1300可包括处理器1302、发射机1301和接收机1304。
接收机1304、发射机1301和处理器1302通过总线1306***相互连接。总线1306可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图13中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。具体的应用中，发射机1301和接收机1304可以耦合到天线1305。
可选地，用户设备1300还可包括存储器1303，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1303可以包括只读存储器和随机存取存储器，并向处理器1302提供指令和数据。存储器1303可能包含高速随机存取存储器(Random-Access Memory，RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少1个磁盘存储器。
处理器1302，用于执行以下操作，可选地，执行存储器1303所存放的程序，并具体用于执行以下操作：
接收网络设备发送的RRC下行消息；
在该RRC下行消息的RRC过程时延的时间范围内，接收该网络设备预先分配并发送的该RRC下行消息对应的RRC上行响应消息的上行授权；
在该上行授权指示的上行资源上从RRC层发送该RRC上行响应消息。
上述如本申请图3-9所示实施例揭示的用户设备执行的方法可以应用于处理器1302中，或者由处理器1302实现。处理器1302可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1302中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1302可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或者其他可编程 逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1303，处理器1302读取存储器1303中的信息，结合其硬件完成上述方法的步骤。
本申请实施例还提出了一种计算机可读存储介质，该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图2所示实施例的方法。
本申请实施例还提出了另一种计算机可读存储介质，该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图7所示实施例的方法。
图14是本申请实施例通信***1400的***框图。其中，通信设备1400可包括网络设备1401和用户设备1402。该网络设备1401可以是图10所示的网络设备1000，或图12所示的网络设备1200；该用户设备1402可以是图11所示的用户设备1000，或图13所示的用户设备1300。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计 算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (41)

  1. 一种消息传输方法，其特征在于，包括：
    发送无线资源控制RRC下行消息；
    在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内预先分配并发送所述RRC下行消息对应的RRC上行响应消息的上行授权；
    在所述上行授权指示的上行资源上接收用户设备UE从RRC层发送的所述RRC上行响应消息。
  2. 如权利要求1所述的方法，其特征在于，
    当所述上行授权的发送时间在所述RRC下行消息的发送时间之后时，所述上行授权的发送时间不晚于所述RRC下行消息的确认消息的接收时间。
  3. 如权利要求2所述的方法，其特征在于，
    当所述RRC下行消息以透明传输模式TM发送时，所述RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者
    当所述RRC下行消息以确认模式AM发送时，所述RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
  4. 如权利要求1所述的方法，其特征在于，在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内预先分配并发送所述RRC下行消息对应的RRC上行响应消息的上行授权包括：
    在发送所述RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中发送所述上行授权。
  5. 如权利要求1所述的方法，其特征在于，在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内预先分配并发送所述RRC下行消息对应的RRC上行响应消息的上行授权包括：
    在发送所述RRC下行消息的消息包中发送所述上行授权。
  6. 如权利要求5所述的方法，其特征在于，所述消息包采用媒体接入控制MAC协议数据单元PDU的数据格式，所述RRC下行消息存储于所述MAC PDU的MAC服务数据单元SDU中，所述上行授权存储于MAC PDU中的MAC控制元素CE。
  7. 如权利要求6所述的方法，其特征在于，
    当所述RRC下行消息以AM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息经RLC分组后的一个分组数据包；或者
    当所述RRC下行消息以TM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息的全部内容。
  8. 如权利要求4-7中任一项所述的方法，其特征在于，所述RRC上行响应消息还用于指示所述UE确认接收所述RRC下行消息，其中，所述UE未发送所述RRC下行消息的确认消息。
  9. 如权利要求4-8中任一项所述的方法，其特征在于，
    所述无线资源控制过程时延RRC procedureDelay等于0。
  10. 如权利要求1-9中任一项所述的方法，其特征在于，
    所述RRC下行消息和所述RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
  11. 一种消息传输方法，其特征在于，包括：
    接收网络设备发送的无线资源控制RRC下行消息；
    在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内，接收所述网络设备预先分配并发送的所述RRC下行消息对应的RRC上行响应消息的上行授权；
    在所述上行授权指示的上行资源上从RRC层发送所述RRC上行响应消息。
  12. 如权利要求11所述的方法，其特征在于，
    当所述上行授权的接收时间在所述RRC下行消息的接收时间之后时，所述上行授权的接收时间不晚于所述RRC下行消息的确认消息。
  13. 如权利要求12所述的方法，其特征在于，
    当所述RRC下行消息以透明传输模式TM发送时，所述RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者
    当所述RRC下行消息以确认模式AM发送时，所述RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
  14. 如权利要求11所述的方法，其特征在于，在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内预先分配并发送所述RRC下行消息对应的RRC上行响应消息的上行授权包括：
    在接收所述RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中接收所述上行授权。
  15. 如权利要求11所述的方法，其特征在于，在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内预先分配并发送所述RRC下行消息对应的RRC上行响应消息的上行授权包括：
    在接收所述RRC下行消息的消息包中接收所述上行授权。
  16. 如权利要求15所述的方法，其特征在于，所述消息包采用媒体接入控制MAC协议数据单元PDU的数据格式，所述RRC下行消息存储于所述MAC PDU的MAC服务数据单元SDU中，所述上行授权存储于MAC PDU中的MAC控制元素CE。
  17. 如权利要求16所述的方法，其特征在于，
    当所述RRC下行消息以AM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息经RLC分组后的一个分组数据包；或者
    当所述RRC下行消息以TM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息的全部内容。
  18. 如权利要求14-17中任一项所述的方法，其特征在于，所述RRC上行响应消息还用于指示确认接收所述RRC下行消息，其中，所述网络设备不会接收到所述RRC下行消息的确认消息。
  19. 如权利要求14-18中任一项所述的方法，其特征在于，
    所述无线资源控制过程时延RRC procedureDelay等于0。
  20. 如权利要求11-19中任一项所述的方法，其特征在于，
    所述RRC下行消息和所述RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
  21. 一种网络设备，其特征在于，包括：
    发送模块，用于发送无线资源控制RRC下行消息；
    处理模块，用于在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内预先分配所述RRC下行消息对应的RRC上行响应消息的上行授权；
    所述发送模块还用于在所述RRC Procedure Delay的时间范围内发送所述上行授权；
    接收模块，用于在所述上行授权指示的上行资源上接收用户设备UE从RRC层发送的所述RRC上行响应消息。
  22. 如权利要求21所述的网络设备，其特征在于，
    当所述上行授权的发送时间在所述RRC下行消息的发送时间之后时，所述上行授权的发送时间不晚于所述RRC下行消息的确认消息的接收时间。
  23. 如权利要求22所述的网络设备，其特征在于，
    当所述RRC下行消息以透明传输模式TM发送时，所述RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者
    当所述RRC下行消息以确认模式AM发送时，所述RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
  24. 如权利要求21所述的网络设备，其特征在于，所述发送模块具体用于：
    在发送所述RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中发送所述上行授权。
  25. 如权利要求21所述的网络设备，其特征在于，
    在发送所述RRC下行消息的消息包中发送所述上行授权。
  26. 如权利要求25所述的网络设备，其特征在于，所述消息包采用媒体接入控制MAC协议数据单元PDU的数据格式，所述RRC下行消息存储于所述MAC PDU的MAC服务数据单元SDU中，所述上行授权存储于MAC PDU中的MAC控制元素CE。
  27. 如权利要求26所述的网络设备，其特征在于，当所述RRC下行消息以AM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息经RLC分组后的一个分组数据包；或者
    当所述RRC下行消息以TM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息的全部内容。
  28. 如权利要求24-27中任一项所述的网络设备，其特征在于，所述RRC上行响应消息还用于指示所述UE确认接收所述RRC下行消息，其中，所述UE未发送所述RRC下行消息的确认消息。
  29. 如权利要求24-28中任一项所述的网络设备，其特征在于，
    所述无线资源控制过程时延RRC procedureDelay等于0。
  30. 如权利要求21-29中任一项所述的网络设备，其特征在于，
    所述RRC下行消息和所述RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
  31. 一种用户设备，其特征在于，包括：
    接收模块，用于接收网络设备发送的无线资源控制RRC下行消息；
    所述接收模块还用于在所述RRC下行消息的无线资源控制过程时延RRC Procedure Delay的时间范围内，接收所述网络设备预先分配并发送的所述RRC下行消息对应的RRC上行响应消息的上行授权；
    处理模块，用于确定所述上行授权指示的上行资源；
    发送模块，用于在所述上行授权指示的上行资源上从RRC层发送所述RRC上行响应消息。
  32. 如权利要求31所述的用户设备，其特征在于，
    当所述上行授权的接收时间在所述RRC下行消息的接收时间之后时，所述上行授权的接收时间不晚于所述RRC下行消息的确认消息。
  33. 如权利要求32所述的用户设备，其特征在于，
    当所述RRC下行消息以透明传输模式TM发送时，所述RRC下行消息的确认消息是媒体接入控制MAC层的反馈消息；或者
    当所述RRC下行消息以确认模式AM发送时，所述RRC下行消息的确认消息是无线链路控制RLC层的反馈消息。
  34. 如权利要求31所述的用户设备，其特征在于，所述接收模块具体用于：在接收所述RRC下行消息的下行资源分配的物理层下行控制信道PDCCH中接收所述上行授权。
  35. 如权利要求31所述的用户设备，其特征在于，所述接收模块具体用于：在接收所述RRC下行消息的消息包中接收所述上行授权。
  36. 如权利要求35所述的用户设备，其特征在于，所述消息包采用媒体接入控制MAC协议数据单元PDU的数据格式，所述RRC下行消息存储于所述MAC PDU的MAC服务数据单元SDU中，所述上行授权存储于MAC PDU中的MAC控制元素CE。
  37. 如权利要求36所述的用户设备，其特征在于，
    当所述RRC下行消息以AM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息经RLC分组后的一个分组数据包；或者
    当所述RRC下行消息以TM发送时，所述消息包中的MAC SDU存储着所述RRC下行消息的全部内容。
  38. 如权利要求34-37中任一项所述的用户设备，其特征在于，
    所述RRC上行响应消息还用于指示确认接收所述RRC下行消息，其中，所述网络设备不会接收到所述RRC下行消息的确认消息。
  39. 如权利要求34-38中任一项所述的用户设备，其特征在于，所述无线资源控制过程时延RRC procedureDelay等于0。
  40. 如权利要求31-39中任一项所述的用户设备，其特征在于，所述RRC下行消息和所述RRC上行响应消息属于同一个RRC处理标识的RRC过程实例。
  41. 一种通信***，其特征在于，包括：
    如权利要求21-30中任一项所述的网络设备；以及
    如权利要求31-40中任一项所述的用户设备。
PCT/CN2017/103661 2016-09-30 2017-09-27 消息传输方法、设备和*** WO2018059438A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17854888.9A EP3512290B1 (en) 2016-09-30 2017-09-27 Message transmission method, device and system
US16/370,675 US20190230732A1 (en) 2016-09-30 2019-03-29 Message transmission method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610877439.1A CN108307519B (zh) 2016-09-30 2016-09-30 消息传输方法、设备和***
CN201610877439.1 2016-09-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/370,675 Continuation US20190230732A1 (en) 2016-09-30 2019-03-29 Message transmission method, device, and system

Publications (1)

Publication Number Publication Date
WO2018059438A1 true WO2018059438A1 (zh) 2018-04-05

Family

ID=61763125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/103661 WO2018059438A1 (zh) 2016-09-30 2017-09-27 消息传输方法、设备和***

Country Status (4)

Country Link
US (1) US20190230732A1 (zh)
EP (1) EP3512290B1 (zh)
CN (1) CN108307519B (zh)
WO (1) WO2018059438A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019215675A1 (en) * 2018-05-10 2019-11-14 Telefonaktiebolaget Lm Ericsson (Publ) Fallback for random access early data transmission
WO2020102975A1 (en) * 2018-11-20 2020-05-28 Qualcomm Incorporated Random access channel (rach) -less procedure

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110235512B (zh) * 2017-01-24 2023-08-18 瑞典爱立信有限公司 无线通信网络中的控制平面延迟减小
AU2017444445A1 (en) * 2017-12-27 2020-08-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. SRB transmission method and device
CN111526599B (zh) * 2019-02-01 2022-05-31 华为技术有限公司 一种无线资源控制rrc消息发送方法及装置
EP4002925A4 (en) * 2019-08-02 2022-07-13 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR TRANSMITTING DATA
WO2021134680A1 (zh) * 2019-12-31 2021-07-08 华为技术有限公司 一种数据传输方法及装置
CN114600551A (zh) * 2020-01-23 2022-06-07 Oppo广东移动通信有限公司 Rrc消息的处理方法、装置、用户设备及网络设备
WO2024144935A1 (en) * 2022-12-27 2024-07-04 Google Llc User equipment requested downlink and uplink scheduling

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2701319A2 (en) * 2011-04-05 2014-02-26 Samsung Electronics Co., Ltd. Method and apparatus for reducing uplink transmission delay in wireless communication system using carrier aggregation
CN105191199A (zh) * 2013-03-16 2015-12-23 高通股份有限公司 用于调度lte蜂窝***中的经延迟ack/nack的设备和方法

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7068636B2 (en) * 2002-06-21 2006-06-27 Asustek Computer Inc. Method for determining RLC entity re-establishment during SRNS relocation
KR101050258B1 (ko) * 2008-03-20 2011-07-19 이노베이티브 소닉 리미티드 Ｒｒｃ 연결 프로시저를 향상시키기 위한 방법 및 장치
RU2476001C2 (ru) * 2008-04-28 2013-02-20 Фудзицу Лимитед Способ обработки соединения в системе беспроводной связи, и базовая станция беспроводной связи и терминал беспроводной связи
CN101730061B (zh) * 2008-10-31 2012-06-27 大唐移动通信设备有限公司 业务建立与小区更新的同步处理方法、装置及***
CN102210190B (zh) * 2008-11-10 2015-05-06 黑莓有限公司 针对承载类型选择是否发送请求更节约能量的状态或模式的指示信息的方法和装置
US7917137B2 (en) * 2009-02-04 2011-03-29 Nokia Corporation Optimization of uplink resource grant procedure and apparatus
CN101888684A (zh) * 2009-05-14 2010-11-17 中兴通讯股份有限公司 无线资源控制连接重建失败后快速连接建立的方法及***
JP5388955B2 (ja) * 2010-06-21 2014-01-15 株式会社Ｎｔｔドコモ 通信制御方法、通信システム、及び基地局装置
CN102316582A (zh) * 2010-07-06 2012-01-11 中兴通讯股份有限公司 一种上行资源分配方法及***
KR20120071456A (ko) * 2010-12-23 2012-07-03 한국전자통신연구원 사물 통신 단말을 위한 호 처리 방법
US8830828B2 (en) * 2011-05-31 2014-09-09 Innovative Sonic Corporation Method and apparatus to prevent RAN (radio access network) overload for legacy networks in a wireless communication system
WO2013176473A1 (ko) * 2012-05-21 2013-11-28 삼성전자 주식회사 이동통신 시스템에서 데이터를 송수신하는 방법 및 장치
KR102047796B1 (ko) * 2012-10-08 2019-11-22 삼성전자 주식회사 이동통신 시스템에서 단말의 성능을 보고하는 방법 및 장치
US9537718B2 (en) * 2013-03-15 2017-01-03 Cisco Technology, Inc. Segment routing over label distribution protocol
US9992739B2 (en) * 2013-06-28 2018-06-05 Telefonaktiebolaget L M Ericsson (Publ) Proactive radio resource allocation
WO2015008962A1 (en) * 2013-07-17 2015-01-22 Lg Electronics Inc. Method for reporting a radio link control re-transmission failure and a device therefor
KR101892717B1 (ko) * 2014-02-16 2018-08-29 엘지전자 주식회사 무선 통신 시스템에서 상향링크 데이터 전송 방법 및 이를 위한 장치
US10368287B2 (en) * 2015-05-04 2019-07-30 Lg Electronics Inc. Method and apparatus for reselecting cell in wireless communication system
US20170041766A1 (en) * 2015-08-05 2017-02-09 Qualcomm Incorporated Media access control segmentation and packet data convergence protocol delivery notification with enhanced component carriers
KR102257786B1 (ko) * 2016-04-20 2021-05-28 콘비다 와이어리스, 엘엘씨 이동성 시그널링 로드 감소
CN109479268B (zh) * 2016-08-17 2023-08-22 联想创新有限公司（香港) 用于进一步emtc的资源指配指示

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2701319A2 (en) * 2011-04-05 2014-02-26 Samsung Electronics Co., Ltd. Method and apparatus for reducing uplink transmission delay in wireless communication system using carrier aggregation
CN105191199A (zh) * 2013-03-16 2015-12-23 高通股份有限公司 用于调度lte蜂窝***中的经延迟ack/nack的设备和方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PANASONIC: "Report of Offline Discussion about Definition of RRC Procedure Delay", R2-084850 TSG-RAN WORKING GROUP 2 MEETING #63, 22 August 2008 (2008-08-22), XP050319785 *
See also references of EP3512290A4

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019215675A1 (en) * 2018-05-10 2019-11-14 Telefonaktiebolaget Lm Ericsson (Publ) Fallback for random access early data transmission
US11882548B2 (en) 2018-05-10 2024-01-23 Telefonaktiebolaget Lm Ericsson (Publ) Fallback for random access early data transmission
WO2020102975A1 (en) * 2018-11-20 2020-05-28 Qualcomm Incorporated Random access channel (rach) -less procedure
EP3884704A4 (en) * 2018-11-20 2022-08-03 Qualcomm Incorporated RIGHT ACCESS CHANNEL (RACH) FREE METHOD

Also Published As

Publication number Publication date
US20190230732A1 (en) 2019-07-25
EP3512290B1 (en) 2021-08-25
CN108307519B (zh) 2021-05-11
EP3512290A4 (en) 2019-08-07
EP3512290A1 (en) 2019-07-17
CN108307519A (zh) 2018-07-20

Similar Documents

Publication Publication Date Title
WO2018059438A1 (zh) 消息传输方法、设备和***
WO2019192596A1 (zh) 传输数据的方法及其装置和***
JP7233582B2 (ja) 通信装置、処理装置及びデータユニットを送信する方法
WO2018059590A1 (zh) 数据处理方法、装置及***
US7864719B2 (en) Method of generating lower layer data block in wireless mobile communication system
WO2018202037A1 (zh) 传输数据的方法、终端设备和网络设备
US10869328B2 (en) Data transmission method, terminal device, and network device
WO2016183705A1 (zh) 授权辅助接入***中用于传输上行数据的方法和装置
WO2017041591A1 (zh) 建立、拆除块确认通信机制的方法和装置
WO2020151637A1 (zh) 通信方法以及装置
WO2019242665A1 (zh) 一种传输数据的方法和装置
WO2018171711A1 (zh) 重传处理方法和设备
CN111480359A (zh) 用于发送数据单元的通信设备、处理设备及方法
WO2019192516A1 (zh) 一种传输数据的方法、装置和***
WO2020143731A1 (zh) 用于传输数据的方法、通信设备和网络设备
JP5567128B2 (ja) Ａｒｑフィードバック情報伝送及び受信方法
TWI744346B (zh) 傳輸反饋信息的方法、終端設備和基站
WO2018166517A1 (zh) 一种数据传输方法、数据发送设备及数据接收设备
WO2014166053A1 (zh) 一种通讯方法和终端
WO2021056581A1 (zh) 上行信号的发送和接收方法以及装置
WO2014026386A1 (zh) 数据包传输方法和装置
WO2019076207A1 (zh) 数据传输的确认方法及设备
WO2020199778A1 (zh) 一种通信方法及通信装置
US10143035B2 (en) Device and method of handling communication with communication device
WO2018103637A1 (zh) 数据处理的方法、发送设备和接收设备

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: 17854888

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: 2017854888

Country of ref document: EP

Effective date: 20190410