WO2019134566A1 - 无线通信设备和方法 - Google Patents

无线通信设备和方法 Download PDF

Info

Publication number
WO2019134566A1
WO2019134566A1 PCT/CN2018/123834 CN2018123834W WO2019134566A1 WO 2019134566 A1 WO2019134566 A1 WO 2019134566A1 CN 2018123834 W CN2018123834 W CN 2018123834W WO 2019134566 A1 WO2019134566 A1 WO 2019134566A1
Authority
WO
WIPO (PCT)
Prior art keywords
edt
rrc
random access
layer
data
Prior art date
Application number
PCT/CN2018/123834
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 EP18898427.2A priority Critical patent/EP3737201A4/en
Priority to MX2020007043A priority patent/MX2020007043A/es
Priority to US16/959,761 priority patent/US11596019B2/en
Publication of WO2019134566A1 publication Critical patent/WO2019134566A1/zh
Priority to CONC2020/0009089A priority patent/CO2020009089A2/es

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and more particularly, to a wireless communication device and related method for small data transmission.
  • NB-IoT Narrow Band Internet
  • MTC Machine Type Communication
  • the amount of data to be transmitted by a small packet service over a period of time is relatively small (for example, 1000 bits), that is, it can be transmitted through a transport block of a physical layer, and the data transmission in the existing mechanism must complete the connection with the air interface.
  • the RRC connection state can be completed, which makes the signaling overhead for transmitting small data packets relatively large.
  • the user terminal data of the MTC or NB-IoT is huge, more serious signaling overhead is caused. At the same time, excessive signaling overhead also leads to unnecessary user terminal energy consumption.
  • Radio Resource Control RRC
  • small data and random access message 3 can be sent together in a random access procedure.
  • the UE needs to fall back from the ongoing small data transmission process to the traditional data transmission process. That is, the connection state is entered through the RRC connection setup/recovery process for data transmission. For example, since the network side buffers more data of the UE to be transmitted to the UE, the network side may require the UE to enter the RRC connected state from the ongoing small data transmission process to receive more downlink data. At this point, the UE needs to fall back to the traditional data transmission process.
  • the present disclosure is directed to a method of regressing from an ongoing small data transfer process to a conventional data transfer process and corresponding apparatus.
  • a method performed by a user equipment comprising: transmitting a random access preamble for EDT on a channel resource for early data transmission "EDT”; receiving a random access response "RAR" If the EDT transmission cannot be performed according to the received RAR, the fallback to the non-EDT process is performed.
  • performing the fallback to the non-EDT process includes transmitting, by the medium access control "MAC” layer, a first backoff indication to the radio resource control "RRC" layer.
  • performing a fallback to the non-EDT process includes at least one of the following:
  • the media access control "MAC" layer empties the data in the multiplexed composite entity
  • the MAC layer clears the data in the message 3 cache;
  • the MAC layer interrupts or suspends the current random access procedure until an indication of the upper layer is received.
  • the method further includes at least one of the following:
  • the RRC layer When receiving the first backoff indication from the MAC layer, the RRC layer sends a second backoff indication to the MAC layer;
  • the RRC layer When receiving the first backoff indication from the MAC layer, the RRC layer instructs the MAC layer to replace the data in the cache with new data; or
  • the RRC layer Upon receiving the first backoff indication from the MAC layer, the RRC layer instructs the RLC layer to reconstruct the RLC entity.
  • performing the fallback to the non-EDT process further comprises, after transmitting the message 3, initiating a random access contention resolution timer not for EDT.
  • performing a fallback to the non-EDT process includes at least one of the following:
  • a method performed by a user equipment comprising: transmitting a random access preamble for EDT on a channel resource for early data transmission "EDT"; performing EDT transmission; if receiving To the message indicating the rollback to the non-EDT process, a rollback to the non-EDT process is performed.
  • performing a fallback to a non-EDT process includes performing a radio resource control "RRC" connection setup procedure.
  • RRC radio resource control
  • performing a fallback to the non-EDT process includes at least one of the following:
  • a user device in accordance with another aspect of the present disclosure, includes a processor and a memory.
  • the memory is communicatively coupled to the processor.
  • the memory stores instructions that, when executed by the processor, cause the user device to perform a method according to the methods described herein.
  • FIG. 1A is a flow chart illustrating a method performed by a user device in accordance with one embodiment of the present disclosure.
  • FIG. 1B is a flow chart illustrating a method performed by a user device in accordance with one embodiment of the present disclosure.
  • FIG. 2 is a block diagram showing a user equipment in accordance with one embodiment of the present disclosure.
  • the base station in the present disclosure may be any type of base station, including a Node B, an enhanced base station eNB, or a 5G communication system base station gNB, or a micro base station, a pico base station, a macro base station, a home base station, etc.; the cell may also be any of the above.
  • Random Access Response The second message in the random access process. After receiving the random access preamble of the UE, the base station may respond to the reception of the random access preamble by sending a random access response message.
  • the random access response message includes a time advance domain, an uplink grant domain, a UE identification domain, and the like.
  • message 3 refers collectively to the uplink transmission sent by the UE on the uplink resource indicated by the uplink grant included in the RAR. It can refer to the third transmission in the contention-based random access procedure, or the first uplink transmission after the non-contention based random access procedure.
  • Message 4 In the random access process, the downlink message used in response to the message 3 is sent by the base station to the UE, and the UE performs random access competition analysis based on the message to determine whether the random access is successful.
  • control plane cellular evolution packet service optimization cp-CIoT-EPS
  • -Optimisation control plane cellular evolution packet service optimization
  • up-CIoT-EPS-Optimisation the data of the application layer is transmitted as a non-access stratum (NAS) data packet on a signaling radio bearer (SRB) of the control plane.
  • the signaling radio bearer refers to SRB1 or SRB1bis before R14.
  • the UE includes a NAS packet for transmission in the RRC connection setup complete message after completing the random access procedure.
  • This optimization scheme can be referred to simply as a control plane optimization scheme or a control plane scheme.
  • the data of the application layer is still transmitted on the data radio bearer (DRB) in the RRC connected state, but the data is transmitted in the same manner as the data transmission in the legacy system.
  • the UE and the eNB suspend the RRC connection (indicated by the RRC Connection Release message including the suspension indication), save the UE context, and enter the RRC idle state.
  • the UE initiates an RRC connection recovery procedure to the eNB.
  • the UE sends an RRC connection recovery request message to the base station to initiate connection recovery, and the base station sends an RRC connection recovery message to the UE to indicate that the RRC connection is restored. Then, the UE feeds back the RRC connection recovery complete message to the base station to respond.
  • This scheme can also be referred to as a user plane optimization scheme or a user plane scheme.
  • the UE saves the RRC idle state of the UE context. Although it is also called the RRC idle state, it can actually be regarded as an intermediate state of an RRC idle state and a connected state. This intermediate state, in the 5G NR system, can be considered as its defined RRC inactive state (RRC_inactive).
  • the small data transmission optimization scheme in R15 is based on the above two optimization schemes and is further optimized for the characteristics of small data transmission.
  • the optimized content is mainly to transmit small data along with the message 3 in the random access process, because the optimization method can complete the data transmission at an earlier time than the traditional data transmission method. So called early data transmission, in this disclosure, small data can be equated with early data.
  • the base station initiates a physical random access resource, such as a random access preamble, and a transport block size (TBS) threshold used by the EDT through system information broadcast.
  • TBS transport block size
  • the TBS threshold is configured for each enhanced coverage level (or coverage enhancement level). The process of EDT is briefly described below.
  • the UE determines whether the EDT condition is met, for example, whether the TBS including the data packet is less than or equal to the TBS threshold corresponding to the current enhanced coverage level, and if yes, the UE uses the EDT-specific preamble.
  • a random access procedure is initiated on an EDT specific Physical Random Access Channel (PRACH).
  • PRACH Physical Random Access Channel
  • the base station receives the EDT-specific preamble on the EDT-specific PRACH resource, and knows that the UE is initiating the EDT process, the base station allocates an uplink grant available for small data transmission in the RAR.
  • the UE determines whether the uplink grant in the RAR is sufficient to accommodate the entire small data packet. If yes, the UE includes the small data in the message 3 and performs uplink transmission on the resource corresponding to the uplink grant together with the RRC message. If not, the UE falls back to the traditional non-EDT process, that is, the small data packet is not included in the message 3 for transmission, that is, only the RRC message is transmitted in the message 3 to request the RRC connection establishment/recovery, and it is expected that Data is transmitted after the RRC connection is established/restored.
  • the base station may notify the UE that the data transmission has been completed by sending a message 4 (such as an RRC connection release message or an RRC EDT completion message). Keep in RRC idle state. If the network side determines or has additional data to transmit, the base station may instruct the UE to perform the RRC connected state by sending another message 4 (such as RRC connection establishment or RRC connection recovery).
  • a message 4 such as an RRC connection release message or an RRC EDT completion message.
  • the base station may instruct the UE to perform the RRC connected state by sending another message 4 (such as RRC connection establishment or RRC connection recovery).
  • the UE sends the message 3 containing the small data in step 3, and receives the message 4 indicating that the UE performs the RRC connected state in step 4, the UE falls back to the traditional non-EDT process and enters the RRC connected state. Otherwise, the UE considers that the small data transmission is completed and continues the RRC idle state.
  • the user data is included in the RRC message and transmitted through SRB0. If the user plane scheme is used, the user data and the RRC message are multiplexed into a same MAC protocol data unit (PDU) for transmission at the Medium Access Control (MAC) layer, and the user data is The RRC message is transmitted through the SRB0 through the DRB transmission, which requires the UE to recover (or re-activate) the DRB and security when the EDT process is triggered, and apply the wireless configuration before the RRC suspension to each protocol layer.
  • PDU MAC protocol data unit
  • MAC Medium Access Control
  • the UE performs a fallback in the following three cases:
  • Case 1 (in step 4 or 5 above) the message 4 received by the UE is an RRC connection setup message, instructing the UE to establish a new RRC connection;
  • Case 2 (in step 4 or 5 above) the message 4 received by the UE is an RRC connection recovery message, indicating that the UE restores the previous RRC connection;
  • the size of the uplink grant in the RAR received by the UE is not large enough to accommodate the entire transport block containing the small data packet.
  • the entire transport block containing the small data packet refers to the entire transport block including the small data and the RRC message in the message 3 and its corresponding MAC header.
  • the entire transport block including the small data packet refers to a Small Data Packet Data Collection Protocol (PDCP) Service Data Unit (SDU) or a PDCP PDU and an RRC message.
  • PDCP Small Data Packet Data Collection Protocol
  • SDU Service Data Unit
  • RRC message Radio Resource Control Protocol
  • the following embodiments are mainly described based on the above-described fallback situation, but it should be noted that the following embodiments are still applicable in other cases.
  • the foregoing RRC connection setup request or RRC connection recovery request message may be replaced with an RRC connection re-establishment request message, RRC connection establishment or RRC connection recovery.
  • the message may be replaced with an RRC Connection Reestablishment message, and the RRC Connection Setup Complete or RRC Connection Recovery Complete message may be replaced with an RRC Connection Reestablishment Complete message.
  • the UE may include an NB-IoT UE, a bandwidth reduced low complexity UE, a UE in enhanced coverage, and other UEs (eg, 5G NR UEs).
  • FIG. 1A is a flow chart illustrating a method performed by a user device in accordance with one embodiment of the present disclosure.
  • step S110 the user equipment UE transmits a random access preamble for EDT on a channel resource for early data transmission "EDT".
  • step S120 the user equipment UE receives the random access response "RAR".
  • step S130 if the user equipment UE determines that the EDT transmission cannot be performed according to the received RAR, the fallback to the non-EDT process is performed.
  • the first fallback indication may be sent by the medium access control "MAC” layer to the radio resource control "RRC" layer.
  • the RRC layer may send a second backoff indication to the MAC layer, or the RRC layer may instruct the MAC layer to replace the data in the cache with new data, or The RRC layer may instruct the RLC layer to reconstruct the RLC entity.
  • performing a fallback to the non-EDT process may include emptying the data in the multiplexed composite entity by the media access control "MAC" layer.
  • the MAC layer may clear the data in the Message 3 buffer.
  • the MAC layer may interrupt or suspend the current random access procedure until an indication of the upper layer is received.
  • performing the fallback to the non-EDT process may include at least one of: interrupting the data radio bearer "DRB” and signaling radio bearer “SRB”; releasing all radio resource control “RRC” configurations; clearing packet data aggregation Protocol "PDCP” status; rebuild the PDCP entity; or use the default configuration.
  • DRB data radio bearer
  • SRB signaling radio bearer
  • RRC radio resource control
  • performing the fallback to the non-EDT process may further include: after transmitting the message 3, starting a random access contention resolution timer not used for the EDT.
  • the example scenario 1 can be applied, for example, to the fallback case 3 described above.
  • the UE in the EDT process receives the RAR
  • the uplink grant (UL grant) included in the RAR is insufficient to accommodate the entire data to be transmitted
  • the UE performs the following operations.
  • the “data to be transmitted” may be the total amount of data to be sent in the uplink buffer plus the corresponding MAC header (or MAC subheader), including the upper control layer (Common Control Channel, CCCH).
  • CCCH Common Control Channel
  • the entire data to be transmitted may be a PDCP SDU or PDCP PDU to be transmitted in the uplink buffer.
  • the control plane scheme it can also refer to the NAS PDU.
  • “In the EDT process” can be further understood as the random access preamble in the random access procedure is selected by the MAC entity and used for early data (transmission).
  • the UE may fall back to the non-EDT random access procedure and/or the RRC connection setup/recovery process, and apply the traditional non-EDT random access procedure or the RRC connection setup/recovery procedure to enter the RRC connected state to implement data transmission.
  • This sample scenario can be applied to control plane scenarios and user plane scenarios. Specifically, when the UE performs the rollback, the UE may first perform one or more of the following operations:
  • Operation 1 The UE MAC layer indicates the first backoff indication to the upper layer.
  • the first backoff indication is also referred to as an "EDT failure indication” or an “EDT not applicable/inappropriate” indication, and the purpose is for the MAC layer to notify the upper layer that the EDT cannot be continued.
  • Operation 2 The MAC entity clears the data in the multiplexed combined entity.
  • operation 2 may be performed.
  • the data in the multiplexing combined entity is from RRC messages (ie, SRB data) carried by the upper layer on the common control channel and/or user plane data (ie, DRB data) on the dedicated control channel.
  • RRC messages ie, SRB data
  • user plane data ie, DRB data
  • operation 2 is performed in a control plane scheme.
  • Operation 3 The MAC layer clears the message 3 cache (data in).
  • operation 3 may be performed.
  • Operation 4 The MAC interrupts/suspends the current RA until an indication of the upper layer is received.
  • Operation 4 can also be described as the transmission of the MAC delay message 3 until a second backoff indication from the upper layer is received. Alternatively, it can also be described as MAC waiting until a second backoff indication from the upper layer is received.
  • the second backoff indication is used to indicate that the underlying backs up to a non-EDT operation. Rather, it is used to instruct the MAC layer to perform a random access procedure in a non-EDT mode of operation (continue) or to instruct the RLC layer to perform RLC entity re-establishment. In this operation, the MAC continues the current random access procedure (subsequent operation) after receiving the second backoff indication from the upper layer.
  • the subsequent operations may, for example, set the TC-RNTI to the value received in the RAR, obtain the MAC PDU to be transmitted from the multiplexing combining entity and store it in the message 3 buffer, and the like.
  • Operation 5 When receiving the first backoff indication from the bottom layer, the RRC performs a fallback operation, that is, performs an operation of rolling back to the flow not adopting the EDT, including indicating a second backoff indication to the bottom layer.
  • Operation 6 When receiving the first backoff indication from the bottom layer, the RRC performs a fallback operation, that is, performs an operation of rolling back to the process not adopting the EDT, instructing the underlying layer to replace the data in the cache with new data.
  • a fallback operation that is, performs an operation of rolling back to the process not adopting the EDT, instructing the underlying layer to replace the data in the cache with new data.
  • Operation 7 When receiving the first backoff indication from the bottom layer, that is, performing an operation of rolling back to the flow not adopting the EDT, the RRC instructs the bottom layer to re-establish the underlying entity.
  • operation 7 is performed if the UE is using the control plane scheme or has previously submitted an RRC early data transmission request to the lower layer for transmission.
  • the bottom layer may be an RLC layer.
  • Operation 8 When receiving the reconfiguration indication or the second backoff indication of the RRC layer, the RLC performs RLC entity re-establishment.
  • Operation 9 The MAC entity replaces the data in the cache with new data received from the upper layer.
  • the following operation 10 can also be performed.
  • the MAC layer may initiate a random access competition resolution timer (ra-contention resolution Timer).
  • the random access contention resolution timer refers to a contention resolution timer that is not used for the random access procedure of the EDT.
  • the premise here is that the system defines two random access contention resolution timers, one for the random access procedure for EDT and the other for the non-EDT random access procedure, which refers to the latter.
  • the bottom layer may be a MAC layer or an RLC layer or a PDCP layer
  • the upper layer may be an RRC layer.
  • the RLC/PDCP entity corresponding to the RLC/PDCP entity SRB and more specifically, the RLC/PDCP entity corresponding to the SRB0.
  • the RLC/PDCP entity may be an RLC/PDCP entity corresponding to the SRB or the DRB.
  • the RAR may be an RAR in a contention based random access procedure. That is to say, the UE needs to determine that the current random access procedure is a contention-based random access procedure when performing the above operations. For example, when the random access preamble in the random access procedure is selected by the MAC entity, or the random access preamble is explicitly assigned (as explicitly assigned by ra-PreambleIndex) but not all zeros (such as 000000).
  • Example scenario 2 can be applied to the fallback case 3 described above.
  • the UE in the EDT process receives the RAR
  • the uplink grant (UL grant) included in the RAR is insufficient to accommodate the entire data to be transmitted
  • the UE performs the following operations.
  • the "data to be transmitted” may be the total amount of data to be sent in the uplink buffer plus its corresponding MAC header (or MAC subheader), including the RRC message (ie, SRB data) carried by the upper layer on the common control channel. And/or user plane data (ie DRB data) on a dedicated control channel.
  • the entire data to be transmitted may be a PDCP SDU or PDCP PDU to be transmitted in the uplink buffer, and may also refer to a NAS PDU for a control plane scheme.
  • “In the EDT process” can be further understood as the random access preamble in the random access procedure is selected by the MAC entity and used for early data (transmission).
  • the UE may fall back to the non-EDT random access procedure and/or the RRC connection recovery procedure, and apply the traditional non-EDT random access procedure or the RRC connection recovery procedure to enter the RRC connected state to implement data transmission.
  • This example scenario can be applied to a user plane scenario.
  • the UE RRC may perform one or more of the following operations:
  • Operation 1 Suspend DRB and SRB.
  • DRB refers to all DRBs or all activated DRBs
  • SRB refers to all SRBs or all SRBs that do not include SRB0.
  • Operation 2 Release all RRC configurations.
  • release all RRC configurations refers to releasing the stored radio resource configuration that is restored when the EDT process is triggered, such as RLC layer configuration, PDCP layer configuration, and the like.
  • Release can also be understood as not being used; that is, “release” is not to release the UE context saved by the UE, that is, the UE is still retaining the saved UE context.
  • RRC Configuration can also be equivalent to wireless configuration or radio resource configuration.
  • Operation 3 Clear the PDCP status.
  • the PDCP status may be a RObust Header Compression (ROHC) state, a PDCP sequence number state, or a PDCP superframe number.
  • ROHC RObust Header Compression
  • Operation 4 Rebuild the PDCP entity.
  • the PDCP entity may refer to a PDCP entity corresponding to the DRB and/or a PDCP entity corresponding to the SRB.
  • Operation 5 Adopt the default configuration specified by the protocol.
  • a default physical layer channel configuration (defined in section 9.2.4 of the specification 36.331 in the LTE protocol), with a default semi-persistent scheduling configuration (in the LTE protocol in specification 36.331)
  • the definition of 9.2.3 is based on the default MAC layer configuration (defined in Section 9.2.2 of the specification 36.331 in the LTE protocol).
  • the UE or UE RRC may perform the operations in this example scenario when the UE is using the user plane scheme or has submitted an RRC Connection Recovery message to the lower layer to transmit.
  • FIG. 1B is a flow chart illustrating a method performed by a user device in accordance with one embodiment of the present disclosure.
  • step S150 the user equipment UE transmits a random access preamble for EDT on a channel resource for early data transmission "EDT".
  • the user equipment UE performs EDT transmission.
  • step S170 if the user equipment UE receives a message indicating a fallback to the non-EDT process, a fallback to the non-EDT process is performed.
  • performing a fallback to a non-EDT process may include performing a radio resource control "RRC" connection setup procedure.
  • RRC radio resource control
  • performing the fallback to the non-EDT process may include at least one of: releasing the data radio bearer "DRB” and the signaling radio bearer “SRB”; releasing all radio resource control “RRC” configurations; clearing the packet data aggregation Protocol "PDCP” status; or default configuration.
  • Example scenario 3 can be applied to the fallback case 1 described above.
  • the UE that is in the EDT random access procedure may perform the following operations when the RRC message included in the received message 4 is an RRC connection setup message.
  • "In the EDT process" can be further understood as the random access preamble in the random access procedure is selected by the MAC entity and used for early data (transmission).
  • the UE may fall back to the non-EDT RRC procedure, and perform corresponding operations of the traditional non-EDT RRC setup procedure to enter the RRC connected state.
  • This example scenario can be applied to a user plane scenario.
  • the UE RRC may perform one or more of the following operations:
  • Operation 1 Release DRB and SRB.
  • DRB refers to all DRBs or all activated DRBs
  • SRB refers to all SRBs or all SRBs that do not include SRB0.
  • Operation 2 Release all RRC configurations.
  • release all RRC configurations refers to releasing the stored radio resource configuration that is restored when the EDT process is triggered, such as RLC layer configuration, PDCP layer configuration, and the like.
  • Release can also be understood as not being adopted, that is, also including releasing the UE context saved by the UE.
  • RRC Configuration can also be equivalent to wireless configuration or radio resource configuration.
  • Operation 3 Clear the PDCP status.
  • the PDCP status may be a RObust Header Compression (ROHC) state, a PDCP sequence number state, or a PDCP superframe number.
  • ROHC RObust Header Compression
  • Operation 4 Adopt the default configuration specified by the protocol.
  • a default physical layer channel configuration (defined in section 9.2.4 of the specification 36.331 in the LTE protocol), with a default semi-persistent scheduling configuration (in the LTE protocol in specification 36.331)
  • the definition of 9.2.3 is based on the default MAC layer configuration (defined in Section 9.2.2 of the specification 36.331 in the LTE protocol).
  • the UE RRC may perform the operations in this example scenario when the UE is using the user plane scheme or when the received RRC Connection Setup message is a response to the RRC Connection Recovery Request message for use in the EDT process.
  • FIG. 2 is a block diagram showing a user equipment UE 20 in accordance with one embodiment of the present disclosure.
  • the UE 20 includes a processor 210 and a memory 220.
  • Processor 210 can include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 220 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a nonvolatile memory (such as a flash memory), or other memory.
  • Program instructions are stored on the memory 220.
  • the instructions when executed by the processor 210, can perform the above-described methods (e.g., the methods illustrated in Figures 1A-1B) performed by the user equipment as described in detail in this disclosure.
  • the program running on the device may be a program that causes a computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
  • the program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
  • a volatile memory such as a random access memory RAM
  • HDD hard disk drive
  • non-volatile memory such as a flash memory
  • a program for realizing the functions of the embodiments of the present disclosure may be recorded on a computer readable recording medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology.
  • present disclosure is not limited to the above embodiment. Although various examples of the embodiments have been described, the present disclosure is not limited thereto.
  • Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

Abstract

本公开提供了一种由用户设备执行的方法。该方法包括：在用于早期数据传输"EDT"的物理随机接入信道资源上发送用于EDT的随机接入前导；接收随机接入响应"RAR"；以及如果根据所接收的RAR中的上行许可确定无法执行EDT传输，则执行向非EDT过程的回退。还提供了一种相应的用户设备。

Description

无线通信设备和方法 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及一种小数据传输的无线通信设备和相关方法。
背景技术
2017年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#75次全会上，一个关于窄带物联网(NarrowBand Internet Of things，NB-IoT)进一步增强的新工作项目(参见RP-170852：New WID on Further NB-IoT enhancements)和一个关于机器类通信(Machine Type Communication：MTC)更进一步增强的新的工作项目(参见非专利文献：RP-170732：New WID on Even further enhanced MTC for LTE)获得批准。这两个研究项目的目标之一是针对小数据包业务的传输进行增强。考虑小数据包业务在一段时间内所要传输的数据量比较小(比如1000比特)，即通过一个物理层的传输块即可传完，而现有机制中数据传输都必须在完成与空口的连接进行RRC连接状态之后才能完成，这使得用于传输小数据包的信令开销比较大，考虑到MTC或NB-IoT的用户终端数据庞大，导致了更严重的信令开销。同时，过大的信令开销也导致了不必要的用户终端能耗。
为了使得能以较少的信令开销来完成小数据包的传输，并实现用户终端(User Equipment，UE)的节能，在版本15的小数据传输增强中，提出UE可以不进入无线资源控制(Radio Resource Control，RRC)连接态来实现数据传输。比如，可以在随机接入过程中将小数据和随机接入消息3一起发送。
但是，在一些情况下，UE需要从正在进行的小数据传输过程回退到传统数据传输过程。即，通过RRC连接建立/恢复过程进入连接态进行数据传输。例如，由于网络侧缓存了UE的更多的数据要传给UE，网络侧会要求UE从正在进行的小数据传输过程进入RRC连接态以接收更多的下行数据。此时，UE需要回退到传统的数据传输过程。
发明内容
本公开旨在提供一种从正在进行的小数据传输过程回退到传统数据传输过程的方法以及相应的设备。
根据本公开的一个方面，提供了一种由用户设备执行的方法，包括：在用于早期数据传输“EDT”的信道资源上发送用于EDT的随机接入前导；接收随机接入响应“RAR”；如果根据所接收的RAR确定无法执行EDT传输，则执行向非EDT过程的回退。
在一个实施例中，执行向非EDT过程的回退包括由媒体接入控制“MAC”层向无线资源控制“RRC”层发送第一回退指示。
在一个实施例中，执行向非EDT过程的回退包括以下至少一项：
媒体接入控制“MAC”层清空复用组合实体中的数据；
MAC层清空消息3缓存中的数据；或者
MAC层中断或暂停当前的随机接入过程，直到收到上层的指示。
在一个实施例中，该方法还包括以下至少一项：
当接收到来自MAC层的第一回退指示时，RRC层向MAC层发送第二回退指示；
当接收到来自MAC层的第一回退指示时，RRC层指示MAC层用新数据替换掉缓存中的数据；或者
当接收到来自MAC层的第一回退指示时，RRC层指示RLC层重建RLC实体。
在一个实施例中，执行向非EDT过程的回退还包括：在发送了消息3之后，启动不用于EDT的随机接入竞争解决定时器。
在一个实施例中，执行向非EDT过程的回退包括以下至少一项：
中断数据无线承载“DRB”和信令无线承载“SRB”；
释放所有的无线资源控制“RRC”配置；
清除分组数据汇聚协议“PDCP”状态；
重建PDCP实体；或者
采用默认配置。
根据本公开的另一个方面，提供了一种由用户设备执行的方法，包括：在用于早期数据传输“EDT”的信道资源上发送用于EDT的随机接入前 导；执行EDT传输；如果接收到指示向非EDT过程回退的消息，则执行向非EDT过程的回退。
在一个实施例中，执行向非EDT过程的回退包括执行无线资源控制“RRC”连接建立过程。
在一个实施例中，执行向非EDT过程的回退包括以下至少一项：
释放数据无线承载“DRB”和信令无线承载“SRB”；
释放所有的无线资源控制“RRC”配置；
清除分组数据汇聚协议“PDCP”状态；或者
采用默认配置。
根据本公开的另一个方面，提供了一种用户设备，包括处理器和存储器。所述存储器与所述处理器通信耦合。所述存储器上存储有指令，当所述指令在由所述处理器运行时，使所述用户设备执行根据本文所述的方法。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1A是示出了根据本公开一个实施例的由用户设备执行的方法的流程图。
图1B是示出了根据本公开一个实施例的由用户设备执行的方法的流程图。
图2是示出了根据本公开一个实施例的用户设备的框图。
具体实施方式
根据结合附图对本公开示例性实施例的以下详细描述，本公开的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。
在本公开中，术语“包括”和“含有”及其派生词意为包括而非限制；术语“或”是包含性的，意为“和/或”。
在本说明书中，下述用于描述本公开原理的各种实施例只是说明，不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本公开的示例性实施例。下述描述包 括多种具体细节来帮助理解，但这些细节应认为仅仅是示例性的。因此，本领域普通技术人员应认识到，在不背离本公开的范围和精神的情况下，可以对本文中描述的实施例进行多种改变和修改。此外，为了清楚和简洁起见，省略了公知功能和结构的描述。此外，贯穿附图，相同参考数字用于相似功能和操作。
下文以LTE移动通信系统及其后续的演进版本作为示例应用环境，具体描述了根据本公开的多个实施方式。然而，需要指出的是，本公开不限于以下实施方式，而是可适用于更多其它的无线通信系统，如NB-IoT系统中、MTC系统中，也可以用于5G下一代无线通信系统(New Radio，NR)中。
本公开中的基站可以是任何类型基站，包含Node B、增强基站eNB，也可以是5G通信系统基站gNB、或者微基站、微微基站、宏基站、家庭基站等；所述小区也可以是上述任何类型基站下的小区。
不同的实施例之间也可以结合工作。
下面先对本公开涉及到的一些概念和进行说明。值得注意的是，在下文的描述中的一些命名仅是实例说明性的，而不是限制性的，也可以作其他命名。
随机接入响应(Random Access Response，RAR)：随机接入过程中的第二条消息。基站会在接收到UE的随机接入前导之后，通过发送随机接入响应消息来对该随机接入前导的接收进行响应。随机接入响应消息中包括时间提前域、上行许可域、UE标识域等。
消息3：随机接入过程中的第三条消息。在本公开中，消息3统指UE在RAR中包含的上行许可所指示的上行资源上所发送的上行传输。既可以指基于竞争的随机接入过程中的第三条传输，也可以指基于非竞争的随机接入过程后的第一个上行传输。
消息4：随机接入过程中，用于响应消息3的下行消息，由基站发送给UE，UE基于该消息进行随机接入竞争解析，确定本次随机接入是否成功。
用户面优化方案和控制面优化方案：
实际上，在R15之前的通信系统中，已经支持两种优化的数据传输方案，以用来降低数据传输的信令开销和UE能耗，称控制面蜂窝演进分组服 务优化(cp-CIoT-EPS-Optimisation)和用户面蜂窝演进分组服务优化(up-CIoT-EPS-Optimisation)。在控制面蜂窝演进分组服务优化方案中，应用层的数据作为一个非接入层(Non Access Stratum，NAS)数据包包含在控制面的信令无线承载(Signalling Radio Bearer，SRB)上传输，所述信令无线承载在R14之前指的是SRB1或SRB1bis，如UE在完成随机接入过程后在RRC连接建立完成消息中包含一个NAS数据包进行发送。这种优化方案可简称为控制面优化方案或控制面方案。在用户面蜂窝演进分组服务优化方案中，仍和传统系统中的数据传输一样应用层的数据在RRC连接状态下的数据无线承载((user)Data Radio Bearer，DRB)上传输，但在当数据传输完成后，UE和eNB挂起(suspend)RRC连接(通过包含挂起指示的RRC连接释放消息来指示)，保存UE上下文，进入RRC空闲状态。当UE要进行数据传输时，UE向eNB发起RRC连接恢复流程(在该流程中，UE向基站发送RRC连接恢复请求消息来发起连接恢复，基站向UE发送RRC连接恢复消息来指示其恢复RRC连接，继而UE向基站反馈RRC连接恢复完成消息以进行响应)，因为UE和eNB上保存了UE上下文，通过该流程可以恢复其RRC连接、DRB和安全，无需重新建立RRC连接、DRB和安全。这种方案也可简称用户面优化方案或用户面方案。其中UE保存了UE上下文的RRC空闲态，虽然也称RRC空闲态，但实际上可以看做一个RRC空闲态和连接态的一个中间状态。这个中间状态，在5G NR系统中，可以认为是其定义的RRC非活动状态(RRC_inactive)。
早期数据传输(Early Data Transmission，EDT)：
R15中的小数据传输优化方案基于上述两种优化方案并针对小数据传输的特性做了进一步的优化。对于上行数据传输来说，优化的内容主要是在随机接入过程中伴随消息3一起传输小数据，因为这种优化方式相较传统数据传输方式而言，能够在更早的时刻完成数据传输，所以称为早期数据传输，本公开中，小数据可等同于早期数据。在支持EDT优化方案的小区中，基站通过系统信息广播发起EDT所使用的物理随机接入资源如随机接入前导preamble，以及传输块尺寸(Transport Block Size，TBS)门限值。所述TBS门限值是对每个增强覆盖等级(或称覆盖增强等级)配置的。下面简单描述下EDT的过程。
1.当UE要进行上行传输时，UE判断是否满足EDT的条件，比如包含数据包的TBS是否小于或等于当前增强覆盖等级所对应的TBS门限值，如果是，则UE使用EDT特定的preamble在EDT特定的物理随机接入信道资源(Physical Random Access Channel，PRACH)上发起随机接入过程。
2.基站在EDT特定的PRACH资源上接收到EDT特定的preamble，得知UE正在发起EDT过程，则基站会在RAR中分配可用于小数据传输的上行许可。
3.接收到RAR后，UE判断RAR中的上行许可是否足够容纳整个小数据包，如果是，则UE将小数据包含在消息3中和RRC消息一起在上行许可所对应的资源上进行上行传输；如果否，则UE回退(fallback)到传统非EDT过程，即不将小数据包包含在消息3中一起传输，即消息3中仅传输RRC消息，以请求RRC连接建立/恢复，期望在RRC连接建立/恢复之后传输数据。
4.基站在接收到包含小数据的消息3后，若没有额外的数据传输，则基站可以通过发送一种消息4(如RRC连接释放消息或RRC EDT完成消息)告知UE数据传输已完成，可以保持在RRC空闲态。若基于网络侧的决定或有额外的数据要传，则基站可以通过发送另一种消息4(如RRC连接建立或RRC连接恢复)指示UE进行RRC连接态。
5.如果UE在步骤3中发送了包含小数据的消息3，并接收到了步骤4所述指示UE进行RRC连接态的消息4，则UE回退到传统非EDT流程，并进入RRC连接态。否则，UE认为小数据传输完成，继续RRC空闲态。
在EDT过程中，若是基于控制面方案，则用户数据包含在RRC消息中通过SRB0传输。若是基于用户面方案，则用户数据和RRC消息在媒体接入控制(Medium Access Control，MAC)层完成复用组包成同一个MAC协议数据单元(Protocol Data Unit，PDU)进行传输，用户数据是通过DRB传输而RRC消息是通过SRB0传输的，这就要求UE在触发EDT过程时就要恢复(或称(重新)激活)DRB和安全，以及对各协议层应用RRC挂起之前的无线配置。
基于上述，UE在下述三种情况下会执行回退：
情况1：(上述步骤4或5中)UE接收到的消息4为RRC连接建立消息，指示UE建立新的RRC连接；
情况2：(上述步骤4或5中)UE接收到的消息4为RRC连接恢复消息，指示UE恢复之前的RRC连接；
情况3：(上述步骤3中)UE接收到的RAR中的上行许可的大小不足以容纳包含小数据包的整个传输块。优选地，所述包含小数据包的整个传输块指的是包含小数据和消息3中的RRC消息以及其对应的MAC头在内的整个传输块。备选地，所述包含小数据包的整个传输块指的是小数据分组数据汇聚协议(Packet Data Covergence Protocol，PDCP)服务数据单元(Service Data Unit，SDU)或PDCP PDU和RRC消息。
下述各实施例主要基于上述回退情况进行描述，但需要注意的是，下述实施例在其他情况下仍然适用。比如，在RRC连接重建立的过程中进行的EDT到非EDT的回退，此时上述RRC连接建立请求或RRC连接恢复请求消息可以替换成RRC连接重建立请求消息，RRC连接建立或RRC连接恢复消息可以替换成RRC连接重建立消息，而RRC连接建立完成或RRC连接恢复完成消息可以替换成RRC连接重建立完成消息。
本公开下述实施例中，指示/通知或知会/信息可以互换。UE可以包括NB-IoT UE、带宽降低低复杂度UE、增强覆盖中的UE、以及其他UE(如5G NR UE)。
图1A是示出了根据本公开一个实施例的由用户设备执行的方法的流程图。
在步骤S110，用户设备UE在用于早期数据传输“EDT”的信道资源上发送用于EDT的随机接入前导。
在步骤S120，用户设备UE接收随机接入响应“RAR”。
在步骤S130，如果用户设备UE根据所接收的RAR确定无法执行EDT传输，则执行向非EDT过程的回退。
例如，可以由媒体接入控制“MAC”层可以向无线资源控制“RRC”层发送第一回退指示。在此情况下，当接收到来自MAC层的第一回退指示时，RRC层可以向MAC层发送第二回退指示，或者RRC层可以指示MAC层用新数据替换掉缓存中的数据，或者RRC层可以指示RLC层重建 RLC实体。
备选地，执行向非EDT过程的回退可以包括由媒体接入控制“MAC”层清空复用组合实体中的数据。备选地，MAC层可以清空消息3缓存中的数据。备选地，MAC层可以中断或暂停当前的随机接入过程，直到收到上层的指示。
备选地，执行向非EDT过程的回退可以包括以下至少一项：中断数据无线承载“DRB”和信令无线承载“SRB”；释放所有的无线资源控制“RRC”配置；清除分组数据汇聚协议“PDCP”状态；重建PDCP实体；或者采用默认配置。
优选地，执行向非EDT过程的回退还可以包括：在发送了消息3之后，启动不用于EDT的随机接入竞争解决定时器。
以下，通过示例场景1和2来详细说明图1A中所示的方法的细节。
示例场景1
示例场景1例如可应用于上述回退情况3。优选地，正处于EDT过程中的UE在接收到RAR时，当RAR中所包含的上行许可(UL grant)不足以容纳整个将要传输的数据时，UE执行以下操作。其中，“整个将要传输的数据”可以是上行缓存中所要发送的数据加上其对应的MAC头(或MAC子头)的总量，包含来自上层承载在公共控制信道(Common Control Channel，CCCH)上的RRC消息(即SRB数据)和/或专用控制信道(Dedicated Traffic Channel，DTCH)上的用户面数据(即DRB数据)。备选地，“整个将要传输的数据”可以是上行缓存中将要发送的PDCP SDU或PDCP PDU。对于控制面方案来说，也可以指NAS PDU。“正处于EDT过程中”可以进一步理解为随机接入过程中的随机接入前导是由MAC实体所选择的并用于早期数据(传输)。
在此示例场景中，UE可以回退到非EDT的随机接入过程和/或RRC连接建立/恢复过程，应用传统非EDT的随机接入流程或RRC连接建立/恢复流程进入RRC连接态以实现数据传输。此示例场景可应用于控制面方案和用户面方案。具体地，当UE执行回退时，UE可以首先执行下述操作中的一种或多种：
操作1：UE MAC层向上层指示第一回退指示。
其中，第一回退指示也称为“EDT失败指示”或“EDT不适用/不合适”指示，其目的用于MAC层通知上层无法继续进行EDT。
操作2：MAC实体清空复用组合实体中的数据。
优选地，在所述RAR是当前随机接入过程中所成功收到的第一个RAR的情况下，可以执行操作2。所述复用组合实体中的数据来自上层承载在公共控制信道上的RRC消息(即SRB数据)和/或专用控制信道上的用户面数据(即DRB数据)。优选地，在控制面方案中执行操作2。
操作3：MAC层清空消息3缓存(中的数据)。
优选地，在所述RAR不是当前随机接入过程中所成功收到的第一个RAR的情况下，可以执行操作3。
操作4：MAC中断/暂停当前的RA直到收到上层的指示。
操作4也可描述为MAC延迟(delay)消息3的发送，直到收到来自上层的第二回退指示。或者，也可描述为MAC等待直到收到来自上层的第二回退指示。第二回退指示用于指示底层回退到非EDT操作。更确切地，用于指示MAC层采用非EDT操作方式(继续)执行随机接入过程，或用于指示RLC层进行RLC实体重建。在本操作中，即MAC在收到来自上层的第二回退指示后才继续当前的随机接入过程(的后续操作)。所述后续操作例如可以将TC-RNTI设置为RAR中所接收到的值、从复用组合实体中获取将要传输的MAC PDU并存储在消息3缓存中，等等。
在执行了操作1之后，还可以执行以下操作5-7中的一项或多项：
操作5：当接收到从底层来的第一回退指示时，RRC执行回退操作，即执行回退到不采用EDT的流程的操作，包括向底层指示第二回退指示。
操作6：当接收到从底层来的第一回退指示时，RRC执行回退操作，即执行回退到不采用EDT的流程的操作，指示底层用新数据替换掉缓存中的数据。
操作7：当接收到从底层来的第一回退指示时，即执行回退到不采用EDT的流程的操作，RRC指示底层进行重建(re-establishment)底层实体。优选地，在若UE正在使用控制面方案或者说之前已经向下层递交了RRC早期数据传输请求来发送时执行操作7。优选地，所述底层可以是RLC层。
在执行了操作5或7之后，还可以执行以下操作8。
操作8：当收到RRC层的重建指示或第二回退指示时，RLC执行RLC 实体重建。
在执行了操作6之后，还可以执行以下操作9。
操作9：MAC实体用从上层收到的新数据替换掉缓存中的数据。
优选地，还可以执行以下操作10。
操作10：一旦消息3发送，MAC层可以启动随机接入竞争解决定时器(ra-contentionresolutionTimer)。该随机接入竞争解决定时器指的是不用于EDT的随机接入过程的竞争解决定时器。这里的前提是系统定义两个随机接入竞争解决定时器，一个用于EDT的随机接入过程中，另一个用于非EDT的随机接入过程中，该操作中指的是后者。
在此示例场景中，底层可以为MAC层或RLC层或PDCP层，上层可以为RRC层。在控制面方案中，RLC/PDCP实体SRB对应的RLC/PDCP实体，更具体地是指SRB0对应的RLC/PDCP实体。在用户面方案中，RLC/PDCP实体可以是SRB或DRB对应的RLC/PDCP实体。
在一个示例中，RAR可以是基于竞争的随机接入过程中的RAR。也就是说，UE在执行上述操作时需要判断当前随机接入过程是基于竞争的随机接入过程。比如，当随机接入过程中的随机接入前导是由MAC实体所选的，或随机接入前导是显式指派的(如通过ra-PreambleIndex显式指派)但不是全零(如000000)。
示例场景2
示例场景2可应用于上述回退情况3。优选地，正处于EDT过程中的UE在接收到RAR时，当RAR中所包含的上行许可(UL grant)不足以容纳整个将要传输的数据时，UE执行下述操作。“整个将要传输的数据”可以是上行缓存中所要发送的数据加上其对应的MAC头(或MAC子头)的总量，包含来自上层承载在公共控制信道上的RRC消息(即SRB数据)和/或专用控制信道上的用户面数据(即DRB数据)。备选地，“整个将要传输的数据”可以是上行缓存中将要发送的PDCP SDU或PDCP PDU，对于控制面方案来说，也可以指NAS PDU。“正处于EDT过程中”可以进一步理解为随机接入过程中的随机接入前导是由MAC实体所选择的并用于早期数据(传输)。
在此示例场景中，UE可以回退到非EDT的随机接入过程和/或RRC连 接恢复过程，应用传统非EDT的随机接入流程或RRC连接恢复流程进入RRC连接态以实现数据传输。本示例场景可应用于用户面方案。
具体地，当UE执行回退时(即执行回退到不用于EDT的流程的操作时)，UE RRC可以执行下述操作中的一种或多种：
操作1：中断(suspend)DRB和SRB。
DRB指所有DRB或者所有激活的DRB，SRB指所有SRB或指不包含SRB0在内的所有SRB。
操作2：释放所有RRC配置。
在UE正在使用用户面方案时，“释放所有RRC配置”指的是释放掉在触发EDT流程时所恢复使用的所存储的无线资源配置，比如RLC层配置、PDCP层配置等。“释放”也可理解为不采用；即，“释放”并不是要把UE所保存UE上下文释放掉，即UE仍在保留所保存的UE上下文。“RRC配置”也可等同于无线配置或无线资源配置。
操作3：清除PDCP状态。
PDCP状态可以是鲁棒头压缩(RObust Header Compression，ROHC)状态、PDCP序列号状态或PDCP超级帧号等。
操作4：重建PDCP实体。
优选地，PDCP实体可以指DRB对应的PDCP实体和/或SRB对应的PDCP实体。
操作5：采用协议所规定的默认配置。
例如，可以采用下述一项或多项：采用默认物理层信道配置(在LTE协议中在规范36.331中的9.2.4章节定义)、采用默认半静态调度配置(在LTE协议中在规范36.331中的9.2.3章节定义)、采用默认MAC层配置(在LTE协议中在规范36.331中的9.2.2章节定义)等。
优选地，在当UE正在使用用户面方案时或已经递交了RRC连接恢复消息到下层去发送时，UE或UE RRC可以执行本示例场景中的操作。
图1B是示出了根据本公开一个实施例的由用户设备执行的方法的流程图。
在步骤S150，用户设备UE在用于早期数据传输“EDT”的信道资源上发送用于EDT的随机接入前导。
在步骤S160，用户设备UE执行EDT传输。
在步骤S170，如果用户设备UE接收到指示向非EDT过程回退的消息，则执行向非EDT过程的回退。
例如，执行向非EDT过程的回退可以包括执行无线资源控制“RRC”连接建立过程。
备选地，执行向非EDT过程的回退可以包括以下至少一项：释放数据无线承载“DRB”和信令无线承载“SRB”；释放所有的无线资源控制“RRC”配置；清除分组数据汇聚协议“PDCP”状态；或者采用默认配置。
以下，通过示例场景3来详细说明图1B中所示的方法的细节。
示例场景3
示例场景3可应用于上述回退情况1。优选地，正处于EDT随机接入过程中的UE在接收到的消息4中包含的RRC消息为RRC连接建立消息时，可以执行下述操作。“正处于EDT过程中”可以进一步理解为随机接入过程中的随机接入前导是由MAC实体所选择的并用于早期数据(传输)。
通过本示例场景，UE可以回退到非EDT的RRC过程，并执行传统非EDT的RRC建立过程的相应操作，进入RRC连接态。本示例场景可应用于用户面方案。
具体地，当UE执行回退时(即执行回退到不用于EDT的流程的操作时)，UE RRC可以执行下述操作中的一种或多种：
操作1：释放(release)DRB和SRB。
DRB指所有DRB或者所有激活的DRB，SRB指所有SRB或指不包含SRB0在内的所有SRB。
操作2：释放所有RRC配置。
在UE正在使用用户面方案时，“释放所有RRC配置”指的是释放掉在触发EDT流程时所恢复使用的所存储的无线资源配置，比如RLC层配置、PDCP层配置等。“释放”也可理解为不采用，即也包括要把UE所保存UE上下文释放掉。“RRC配置”也可等同于无线配置或无线资源配置。
操作3：清除PDCP状态。
PDCP状态可以是鲁棒头压缩(RObust Header Compression，ROHC)状态、PDCP序列号状态或PDCP超级帧号等。
操作4：采用协议所规定的默认配置。
例如，可以包括下述一项或多项：采用默认物理层信道配置(在LTE协议中在规范36.331中的9.2.4章节定义)、采用默认半静态调度配置(在LTE协议中在规范36.331中的9.2.3章节定义)、采用默认MAC层配置(在LTE协议中在规范36.331中的9.2.2章节定义)等。
优选地，在当UE正在使用用户面方案时或当收到的RRC连接建立消息是对用于EDT过程中的RRC连接恢复请求消息的响应时，UE RRC可以执行本示例场景中的操作。
图2是示出了根据本公开一个实施例的用户设备UE 20的框图。如图2所示，该UE 20包括处理器210和存储器220。处理器210例如可以包括微处理器、微控制器、嵌入式处理器等。存储器220例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器220上存储有程序指令。该指令在由处理器210运行时，可以执行本公开详细描述的由用户设备执行的上述方法(例如图1A-1B中所示的方法)。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门 或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备执行的方法，包括：
    在用于早期数据传输“EDT”的物理随机接入信道资源上发送用于EDT的随机接入前导；
    接收随机接入响应“RAR”；以及
    如果根据所接收的RAR中的上行许可确定无法执行EDT传输，则执行向非EDT过程的回退。
  2. 根据权利要求1所述的方法，其中，执行向非EDT过程的回退包括：由媒体接入控制“MAC”层向无线资源控制“RRC”层发送第一回退指示。
  3. 根据权利要求1所述的方法，其中，执行向非EDT过程的回退包括以下至少一项：
    媒体接入控制“MAC”层清空复用组合实体中的数据；
    MAC层清空消息3缓存中的数据；或者
    MAC层中断或暂停当前的随机接入过程，直到收到上层的指示。
  4. 根据权利要求2所述的方法，还包括以下至少一项：
    当接收到来自MAC层的第一回退指示时，RRC层向MAC层发送第二回退指示；
    当接收到来自MAC层的第一回退指示时，RRC层指示MAC层用新数据替换掉缓存中的数据；或者
    当接收到来自MAC层的第一回退指示时，RRC层指示RLC层重建RLC实体。
  5. 根据权利要求1-4中任意一项所述的方法，其中，执行向非EDT过程的回退还包括：在发送了消息3之后启动不用于EDT的随机接入竞争解决定时器。
  6. 根据权利要求1所述的方法，其中，执行向非EDT过程的回退包括以下至少一项：
    中断数据无线承载“DRB”和信令无线承载“SRB”；
    释放所有的无线资源控制“RRC”配置；
    清除分组数据汇聚协议“PDCP”状态；
    重建PDCP实体；或者
    采用默认配置。
  7. 一种由用户设备执行的方法，包括：
    在用于早期数据传输“EDT”的物理随机接入信道资源上发送用于EDT的随机接入前导；
    执行EDT传输；以及
    如果接收到指示向非EDT过程回退的消息，则执行向非EDT过程的回退。
  8. 根据权利要求7所述的方法，其中，执行向非EDT过程的回退包括：执行无线资源控制“RRC”连接建立过程。
  9. 根据权利要求7所述的方法，其中，执行向非EDT过程的回退包括以下至少一项：
    释放数据无线承载“DRB”和信令无线承载“SRB”；
    释放所有的无线资源控制“RRC”配置；
    清除分组数据汇聚协议“PDCP”状态；或者
    采用默认配置。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，与所述处理器通信耦合，所述存储器上存储有指令；
    其中，所述指令在由所述处理器运行时，使所述用户设备执行根据权利要求1-9中任意一项所述的方法。
PCT/CN2018/123834 2018-01-05 2018-12-26 无线通信设备和方法 WO2019134566A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP18898427.2A EP3737201A4 (en) 2018-01-05 2018-12-26 WIRELESS COMMUNICATION DEVICE AND PROCEDURE
MX2020007043A MX2020007043A (es) 2018-01-05 2018-12-26 Dispositivo y metodo de comunicacion inalambrica.
US16/959,761 US11596019B2 (en) 2018-01-05 2018-12-26 Wireless communication device and method
CONC2020/0009089A CO2020009089A2 (es) 2018-01-05 2020-07-23 Dispositivo y método de comunicación inalámbrica

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810013245.6A CN110012557A (zh) 2018-01-05 2018-01-05 无线通信设备和方法
CN201810013245.6 2018-01-05

Publications (1)

Publication Number Publication Date
WO2019134566A1 true WO2019134566A1 (zh) 2019-07-11

Family

ID=67144330

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123834 WO2019134566A1 (zh) 2018-01-05 2018-12-26 无线通信设备和方法

Country Status (6)

Country Link
US (1) US11596019B2 (zh)
EP (1) EP3737201A4 (zh)
CN (1) CN110012557A (zh)
CO (1) CO2020009089A2 (zh)
MX (1) MX2020007043A (zh)
WO (1) WO2019134566A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111800886A (zh) * 2019-07-12 2020-10-20 维沃移动通信有限公司 一种随机接入过程回退方法、设备及系统
US11064356B2 (en) * 2018-03-16 2021-07-13 Apple Inc. Security framework for MSG3 and MSG4 in early data transmission
WO2021192882A1 (en) * 2020-03-27 2021-09-30 Nec Corporation Communication system
WO2022015108A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for random access procedure for small data transmission in wireless communication
US11582634B2 (en) * 2020-08-20 2023-02-14 Qualcomm Incorporated Transport block size (TBS) configuration for small data transfer
EP4207916A4 (en) * 2020-09-28 2024-02-14 Guangdong Oppo Mobile Telecommunications Corp Ltd SMALL DATA TRANSMISSION METHOD AND APPARATUS AND TERMINAL DEVICE

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11570819B2 (en) 2018-02-02 2023-01-31 Sony Corporation Telecommunications apparatus and methods
EP3755067A4 (en) * 2018-02-14 2020-12-30 Huawei Technologies Co., Ltd. INFORMATION PROCESSING METHOD AND DEVICE
WO2019216370A1 (ja) 2018-05-09 2019-11-14 京セラ株式会社 通信制御方法、無線端末、及び基地局
US11438797B2 (en) * 2018-05-17 2022-09-06 Lg Electronics Inc. Method and apparatus for discarding data among associated transmission buffers in wireless communication system
TWI728420B (zh) * 2018-08-07 2021-05-21 財團法人資訊工業策進會 在隨機存取程序進行提早資料傳輸的基地台與使用者設備
KR20200088161A (ko) * 2019-01-14 2020-07-22 삼성전자주식회사 이동통신 시스템에서 2 단계 랜덤 엑세스 과정을 통해 사용자 데이터를 전송하는 방법 및 장치
CN111836396B (zh) * 2019-08-06 2022-02-08 维沃移动通信有限公司 一种随机接入请求资源的选择方法、终端及网络设备
CN112351470B (zh) * 2019-08-07 2022-04-05 华为技术有限公司 一种接入限制检测方法和装置
CN111800888B (zh) * 2019-08-13 2022-04-19 维沃移动通信有限公司 一种sdt处理方法、设备及系统
CN110809902B (zh) * 2019-09-30 2023-10-10 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质
CN113079583A (zh) * 2020-01-06 2021-07-06 夏普株式会社 由用户设备执行的方法及用户设备
CN115299165A (zh) * 2020-04-15 2022-11-04 Oppo广东移动通信有限公司 一种数据传输方法、终端设备、网络设备
CN114071479A (zh) * 2020-08-06 2022-02-18 维沃移动通信有限公司 数据传输类型的设定方法和终端
CN116830780A (zh) * 2021-01-14 2023-09-29 欧芬诺有限责任公司 非活动上下文管理
CN115443735A (zh) * 2021-04-01 2022-12-06 北京小米移动软件有限公司 小数据传输sdt退回到非sdt的处理方法及其装置

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008155688A1 (en) * 2007-06-20 2008-12-24 Koninklijke Philips Electronics N.V. Method for allocating transmission resources in a telecommunication system, a primary station and a secondary station for carrying out the method.
CN101616488A (zh) * 2008-06-23 2009-12-30 华为技术有限公司 一种增强随机接入的控制方法、装置及系统
EP3893426A1 (en) * 2009-04-23 2021-10-13 Interdigital Patent Holdings, Inc. Method and apparatus for random access in multicarrier wireless communications
EP2609695B1 (en) * 2010-08-27 2019-10-02 LG Electronics Inc. Mac pdu signaling and operating methods for access class barring and back-off control for large-scale radio access network
US8885458B2 (en) * 2011-07-13 2014-11-11 Telefonaktiebolaget L M Ericsson (Publ) Simplified signaling for small data transmissions
CN102984806A (zh) * 2011-09-02 2013-03-20 普天信息技术研究院有限公司 一种随机接入过程中回退控制参数的设置和更新方法
KR20170101046A (ko) * 2016-02-26 2017-09-05 현대자동차주식회사 분할된 차량 네트워크에서 통신 방법
CN109644089B (zh) * 2016-06-15 2022-04-26 康维达无线有限责任公司 用于新无线电的无许可上行链路传输
US10681738B2 (en) * 2016-12-16 2020-06-09 Ofinno, Llc Random access in a wireless device and wireless network
CN108632987B (zh) * 2017-03-17 2021-06-08 华硕电脑股份有限公司 无线通信中应用于随机接入程序的后退机制的方法和设备
US11096221B2 (en) * 2017-04-03 2021-08-17 Telefonaktiebolaget Lm Ericsson (Publ) Transmission of early data in message 3 (MSG3) via a dual grant
US20180324869A1 (en) * 2017-05-04 2018-11-08 Qualcomm Incorporated Uplink early data transmission
US20180324854A1 (en) * 2017-05-04 2018-11-08 Qualcomm Incorporated Uplink small data transmission for enhanced machine-type-communication (emtc) and internet of things (iot) communication
US10397833B2 (en) * 2017-07-27 2019-08-27 Lg Electronics Inc. Method and apparatus for performing EDT
WO2019031820A1 (en) * 2017-08-08 2019-02-14 Lg Electronics Inc. METHOD AND APPARATUS FOR MANAGING FAILURE OF EARLY DATA TRANSMISSION IN A WIRELESS COMMUNICATION SYSTEM
US11350445B2 (en) * 2017-08-10 2022-05-31 Kyocera Corporation Communication control method for controlling a user equipment to perform early data transmission
US20230199617A1 (en) * 2017-10-26 2023-06-22 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for enabling and disabling early data transmission
CN111149411B (zh) * 2017-11-15 2023-04-28 Lg电子株式会社 在无线通信系统中在随机接入过程期间执行早期数据传输的方法及其设备
EP3711442B1 (en) * 2017-11-16 2023-05-10 Telefonaktiebolaget LM Ericsson (Publ) Replay protection for resume procedure
AU2018366476A1 (en) * 2017-11-16 2020-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Method for allocating resource grant
WO2019104459A1 (en) * 2017-11-28 2019-06-06 Nokia Shanghai Bell Co., Ltd. Early data transmission

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "R2-1710888, Email discussion report: [99#45][NB-IoT/ MTC] Early data transmission", 3GPP TSG-RAN WG2 MEETING #99BIS, 13 October 2017 (2017-10-13), XP051342903 *
QUALCOMM INCORPORATED: "R2-1713713, Discussion on some FFSes on EDT", 3GPP TSG-RAN WG2 MEETING #100, 1 December 2017 (2017-12-01), XP051372372 *
See also references of EP3737201A4 *
SIERRA WIRELESS S A: "PRACH for EDT requests", 3GPP DRAFT; R2-1711555, vol. RAN WG2, 13 October 2017 (2017-10-13), XP051355604 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11064356B2 (en) * 2018-03-16 2021-07-13 Apple Inc. Security framework for MSG3 and MSG4 in early data transmission
CN111800886A (zh) * 2019-07-12 2020-10-20 维沃移动通信有限公司 一种随机接入过程回退方法、设备及系统
CN111800886B (zh) * 2019-07-12 2022-04-08 维沃移动通信有限公司 一种随机接入过程回退方法、设备及系统
EP3986078A4 (en) * 2019-07-12 2022-07-06 Vivo Mobile Communication Co., Ltd. BACKOFF METHOD FOR RANDOM ACCESS AND DEVICES AND SYSTEM
JP2022539902A (ja) * 2019-07-12 2022-09-13 維沃移動通信有限公司 ランダムアクセスプロセスバックオフ方法、機器及びシステム
JP7386962B2 (ja) 2019-07-12 2023-11-27 維沃移動通信有限公司 ランダムアクセスプロセスバックオフ方法、機器及びシステム
WO2021192882A1 (en) * 2020-03-27 2021-09-30 Nec Corporation Communication system
JP2022542270A (ja) * 2020-03-27 2022-09-30 日本電気株式会社 通信システム
JP7318797B2 (ja) 2020-03-27 2023-08-01 日本電気株式会社 通信システム
WO2022015108A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for random access procedure for small data transmission in wireless communication
US11582634B2 (en) * 2020-08-20 2023-02-14 Qualcomm Incorporated Transport block size (TBS) configuration for small data transfer
EP4207916A4 (en) * 2020-09-28 2024-02-14 Guangdong Oppo Mobile Telecommunications Corp Ltd SMALL DATA TRANSMISSION METHOD AND APPARATUS AND TERMINAL DEVICE

Also Published As

Publication number Publication date
MX2020007043A (es) 2020-09-07
US20200374966A1 (en) 2020-11-26
CO2020009089A2 (es) 2020-08-10
US11596019B2 (en) 2023-02-28
EP3737201A4 (en) 2021-09-08
EP3737201A1 (en) 2020-11-11
CN110012557A (zh) 2019-07-12

Similar Documents

Publication Publication Date Title
WO2019134566A1 (zh) 无线通信设备和方法
CN110312296B (zh) 用户设备执行的方法、基站执行的方法、用户设备和基站
WO2019134593A1 (zh) 用户设备和相关方法
US11350445B2 (en) Communication control method for controlling a user equipment to perform early data transmission
TWI678124B (zh) 使用者設備和相關方法
JP5671033B2 (ja) 無線通信システムにおいて物理ダウンリンクチャネルのモニタ動作を制御する方法
EP3651503A1 (en) Communication control method
CN110958688B (zh) 用户设备及其执行的方法、基站及其执行的方法
JP6130435B2 (ja) Ｍａｃのリセットおよび再構成
JP5295365B2 (ja) ランダムアクセス手順の失敗を検出する方法
TWI622312B (zh) 處理無線資源控制連結的裝置及方法
TWI483640B (zh) 不連續接收功能之應用方法及其相關通訊裝置
TWI731805B (zh) 無線通訊系統中釋放預配置的上行鏈路資源（pur）的方法和設備
WO2019194296A1 (ja) 通信制御方法
CN111757471A (zh) 用户设备及其执行的预配置上行资源发送方法
US10973080B2 (en) Radio terminal, processor, and base station
TW201803400A (zh) 處理與基地台的通訊的裝置及方法
WO2020151650A1 (zh) 无线链路控制层的重置方法和用户设备
WO2019153937A1 (zh) 无线通信方法和设备
CN115119341A (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: 18898427

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

Country of ref document: EP

Effective date: 20200805