Method and apparatus for transmission using Preconfigured Uplink Resources while in RRC idle or RRC inactive in a wireless communication system

• US 10,701,702 B2
• Filed: 12/16/2019
• Issued: 06/30/2020
• Est. Priority Date: 10/31/2018
• Status: Active Grant

• Current Assignee: ASUSTek Computer, Inc.
• Original Assignee: ASUSTek Computer, Inc.
• Inventors: Shih, Tun-Huai, Ou, Meng-Hui, Guo, Yu-Hsuan
• Primary Examiner(s): Huynh, Dung B
• Application Number:
  US16/715,550
• Publication Number:
  US 20200137761A1
• Time in Patent Office: 197 Days
• CPC Class Codes: H04W 72/21 in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/53 based on regulatory allocation policies
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/25 Maintenance of established connections
• CPC Class Codes: H04W 76/27 Transitions between radio resource control [RRC] states

Abstract

A method and apparatus are disclosed from the perspective of a User Equipment (UE). In one embodiment, the method includes receiving, from a network node, a configuration of Preconfigured Uplink Resources (PUR), when the UE is in RRC_CONNECTED state, wherein the PUR is used for a transmission when the UE is in RRC_IDLE state. The method also includes determining to generate a first Radio Resource Control (RRC) message or a second RRC message for the transmission based on whether the transmission is to be transmitted using the PUR or not, wherein the first RRC message includes a UE identity and the second RRC message does not include the UE identity. The method further includes performing the transmission including the first RRC message or the second RRC message when the UE is in RRC_IDLE state.

Claims

1. A method of a User Equipment (UE), comprising:

receiving, from a network node, a configuration of Preconfigured Uplink Resources (PUR) including a first Radio Network Temporary Identifier (RNTI) when the UE is in RRC_CONNECTED state;

determining to use the PUR for transmitting a first Radio Resource Control (RRC) message, or to initiate a Random Access (RA) procedure for transmitting the first RRC message based on whether the PUR is available or not;

transmitting, using the PUR, the first RRC message when the UE is in RRC_IDLE or RRC_INACTIVE state;

receiving, from the network node, a second RRC message in response to transmission of the first RRC message; and

entering RRC_CONNECTED state and setting a Cell Radio Network Temporary Identifier (C-RNTI) to a value of the first RNTI, in response to reception of the second RRC message,

wherein the UE determines whether the PUR is available or not at least based on if Time Alignment (TA) is valid, and wherein whether the TA is valid or not is at least based on Serving Cell Reference Signal Received Power (RSRP) changes.

2. The method of claim 1, further comprising:

determining whether to set the C-RNTI to the value of the first RNTI based on whether the second RRC message includes a second RNTI or not.

3. The method of claim 2, wherein the UE sets the C-RNTI to a value of the second RNTI if the second RRC message includes the second RNTI, and the UE sets the C-RNTI to the value of the first RNTI if the second RRC message does not include the second RNTI.

4. The method of claim 1, wherein the C-RNTI is used for monitoring Physical Downlink Control Channel (PDCCH) in RRC_CONNECTED state.

5. The method of claim 1, wherein the first RNTI is used for monitoring Physical Downlink Control Channel (PDCCH) in RRC_IDLE or RRC_INACTIVE state.

6. The method of claim 1, wherein the second RRC message is scheduled by a downlink assignment addressed to the first RNTI.

7. The method of claim 1, wherein the first RRC message is for a RRC connection establishment procedure or a RRC connection resume procedure and the UE enters RRC_CONNECTED state via the RRC connection establishment procedure or the RRC connection resume procedure without performing the RA procedure.

8. The method of claim 1, wherein the first RRC message is a RRCEarlyDataRequest, RRCConnectionRequest, or RRCConnectionResumeRequest message.

9. The method of claim 1, wherein the second RRC message is a RRCConnectionSetup, or RRCConnectionResume message.

10. A User Equipment (UE), comprising:

a control circuit;

a processor installed in the control circuit; and

a memory installed in the control circuit and operatively coupled to the processor;

wherein the processor is configured to execute a program code stored in the memory to;

receive, from a network node, a configuration of Preconfigured Uplink Resources (PUR) including a first Radio Network Temporary Identifier (RNTI) when the UE is in RRC_CONNECTED state;

determine to use the PUR for transmitting a first Radio Resource Control (RRC) message, or to initiate a Random Access (RA) procedure for transmitting the first RRC message based on whether the PUR is available or not;

transmit, using the PUR, the first RRC message when the UE is in RRC_IDLE or RRC_INACTIVE state;

receive, from the network node, a second RRC message in response to transmission of the first RRC message; and

enter RRC_CONNECTED state and set a Cell Radio Network Temporary Identifier (C-RNTI) to a value of the first RNTI, in response to reception of the second RRC message,

wherein the UE determines whether the PUR is available or not at least based on if Time Alignment (TA) is valid, and wherein whether the TA is valid or not is at least based on Serving Cell Reference Signal Received Power (RSRP) changes.

11. The UE of claim 10, wherein the processor is further configured to execute a program code stored in the memory to:

determine whether to set the C-RNTI to the value of the first RNTI based on whether the second RRC message includes a second RNTI or not.

12. The UE of claim 11, wherein the UE sets the C-RNTI to a value of the second RNTI if the second RRC message includes the second RNTI, and the UE sets the C-RNTI to the value of the first RNTI if the second RRC message does not include the second RNTI.

13. The UE of claim 10, wherein the C-RNTI is used for monitoring Physical Downlink Control Channel (PDCCH) in RRC_CONNECTED state.

14. The UE of claim 10, wherein the first RNTI is used for monitoring Physical Downlink Control Channel (PDCCH) in RRC_IDLE or RRC_INACTIVE state.

15. The UE of claim 10, wherein the second RRC message is scheduled by a downlink assignment addressed to the first RNTI.

16. The UE of claim 10, wherein the first RRC message is for a RRC connection establishment procedure or a RRC connection resume procedure and the UE enters RRC_CONNECTED state via the RRC connection establishment procedure or the RRC connection resume procedure without performing the RA procedure.

17. The UE of claim 10, wherein the first RRC message is a RRCEarlyDataRequest, RRCConnectionRequest, or RRCConnectionResumeRequest message.

18. The UE of claim 10, wherein the second RRC message is a RRCConnectionSetup, or RRCConnectionResume message.