Configuration Release

By enabling wireless devices to manage uplink grant configurations through RRC release messages and cell selection, the method optimizes data transmission in RRC inactive or idle states, addressing inefficiencies in existing systems and enhancing network resource utilization.

JP7594763B2Active Publication Date: 2024-12-05OFINNO LLC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023505716
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-07-29
Filing Date
2021-07-29
Publication Date
2024-12-05
Estimated Expiration
2041-07-29

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing configured uplink grant configurations for wireless devices in RRC inactive or idle states, leading to inefficiencies and potential data transmission issues.

Method used

The method involves a wireless device transmitting a configured uplink grant configuration request to a base station, receiving a radio resource control (RRC) release message, transitioning to an RRC inactive or idle state, and selectively releasing or configuring uplink grant configurations based on cell selection and RRC messages to optimize data transmission.

Benefits of technology

This approach enhances data transmission efficiency by allowing dynamic management of uplink grants in RRC inactive or idle states, improving network resource utilization and reducing unnecessary configurations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007594763000001
    Figure 0007594763000001
  • Figure 0007594763000002
    Figure 0007594763000002
  • Figure 0007594763000003
    Figure 0007594763000003
Patent Text Reader

Abstract

Embodiments may be configured to operate as needed. The disclosed mechanisms may be executed when certain criteria are met, for example, in a wireless device, a base station, a wireless environment, a network, a combination of the above, etc. The wireless device receives a first radio resource control release message from a first base station, the first radio resource control release message including a first configured grant configuration for a first cell for a radio resource control disconnected state of the wireless device. The wireless device transmits a second radio resource control message via a second cell, the second radio resource control release message including a release indication for the first configured grant configuration.
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 058,134, filed July 29, 2020, which is incorporated by reference in its entirety herein. Summary of the Invention [Means for solving the problem]

[0002] In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or how the disclosed technology may be practiced in environments and scenarios. It will be apparent to one skilled in the relevant art that various changes in form and details may be made without departing from the scope. Indeed, after reading the specification, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the exemplary embodiments. The embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further embodiments within the scope of the present disclosure. The figures that highlight features and advantages are shown by way of example only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, the actions listed in any flowchart may be rearranged in some embodiments or used only as options.

[0003] The embodiments may be configured to operate as desired. The disclosed mechanisms may be executed when certain criteria are met, for example, in a wireless device, a base station, a wireless environment, a network, a combination of the above, etc. Exemplary criteria may be based at least in part, for example, on wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. Once one or more criteria are met, various exemplary embodiments may be applied. Thus, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0004] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Wireless devices may have some specific capabilities depending on the category and / or capabilities of the wireless devices. When the disclosure refers to a base station communicating with multiple wireless devices, the disclosure may refer to a subset of all wireless devices in the coverage area. The disclosure may refer to multiple wireless devices of a given LTE or 5G release, for example, that include a given capability and are in a given sector of the base station. Multiple wireless devices in the disclosure may refer to selected multiple wireless devices and / or a subset of all wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in a coverage area that may not comply with the disclosed methods. For example, those wireless devices or base stations perform based on older releases of LTE or 5G technology. The present invention provides, for example, the following: (Item 1) 1. A method comprising: transmitting, by the wireless device to a first base station, a configured uplink grant configuration request; receiving, by the wireless device via a first cell of the first base station while the wireless device is in an RRC inactive state or an RRC idle state, a first radio resource control (RRC) release message including a plurality of configured uplink grant configurations for data transmission, the plurality of configured uplink grant configurations corresponding to a plurality of configured uplink grant configuration identifiers; transitioning, by the wireless device and based on the first RRC release message, to the RRC inactive state or the RRC idle state; communicating, by the wireless device while in the RRC inactive state or the RRC idle state, with the first base station via the first cell based on a first configured uplink grant configuration of the plurality of configured uplink grant configurations; selecting, by the wireless device while in the RRC inactive state or the RRC idle state, a second cell of a second base station; by the wireless device to the second base station and based on the selection of the second cell, a first cell identifier of the first cell; a first configured uplink grant configuration identifier of the first configured uplink grant configuration; and transmitting a second RRC message indicating a release indication for the first configured uplink grant configuration; and releasing, by the wireless device, the first configured uplink grant configuration. (Item 2) the first configured uplink grant configuration identifier, an identity of the configured uplink grant configuration of the first configured uplink grant; A Radio Network Temporary Identifier RNTI of the first configured uplink grant; A resume identity of the wireless device; and 2. The method of claim 1, further comprising at least one serving temporary mobile subscribed identity (S-TMSI) of the wireless device. (Item 3) the first configured uplink grant configuration comprising: radio resource information of the first configured uplink grant; and a start time of the first configured uplink grant; The method according to any one of items 1 to 2, further comprising a periodicity of the first configured uplink grant. (Item 4) The first cell identifier of the first cell, a physical cell identity of the first cell; and 4. The method according to any one of items 1 to 3, comprising at least one global cell identity of the first cell. (Item 5) 1. A method comprising: receiving, by a wireless device via a first cell of a first base station, a first radio resource control (RRC) release message including one or more configured uplink grant configurations for data transmission in an RRC inactive state or an RRC idle state, the one or more configured uplink grant configurations corresponding to one or more configured uplink grant configuration identifiers; communicating, by the wireless device while in the RRC inactive state or the RRC idle state, with the first base station based on a first configured uplink grant configuration of the one or more configured grant configurations; selecting, by the wireless device while in the RRC inactive state or the RRC idle state, a second cell; by the wireless device via the second cell; a first cell identifier of the first cell; a first configured uplink grant configuration identifier of the first configured uplink grant configuration; and transmitting a second RRC message indicating a release indication for the first configured uplink grant configuration. (Item 6) 6. The method of claim 5, further comprising sending a configured uplink grant configuration request by the wireless device to the first base station. (Item 7) The method according to any of items 5 to 6, further comprising: transitioning, by the wireless device and based on the first RRC release message, to the RRC inactive state or the RRC idle state. (Item 8) the first configured uplink grant configuration identifier, an identity of the configured uplink grant configuration of the first configured uplink grant; A Radio Network Temporary Identifier RNTI of the first configured uplink grant; A resume identity of the wireless device; and A method according to any of items 5 to 7, comprising at least one Serving Temporary Mobile Subscribe Identity (S-TMSI) of the wireless device. (Item 9) the first configured uplink grant configuration comprising: radio resource information of the first configured uplink grant; and a start time of the first configured uplink grant; 9. The method according to any one of items 5 to 8, further comprising a periodicity of the first configured uplink grant. (Item 10) The first cell identifier of the first cell, a physical cell identity of the first cell; and 10. The method according to any one of items 5 to 9, comprising at least one global cell identity of the first cell. (Item 11) 1. A method comprising: receiving, by the wireless device from a first base station, a first radio resource control (RRC) release message including a first configured uplink grant configuration of a first cell for an RRC disconnected state of the wireless device; and transmitting, by the wireless device via a second cell, a second RRC message including a release indication for the first configured uplink grant configuration. (Item 12) 12. The method of claim 11, wherein the RRC non-connected state is an RRC inactive state or an RRC idle state. (Item 13) 13. The method according to any one of items 11 to 12, further comprising transmitting, by the wireless device, a configured uplink grant configuration request. (Item 14) 14. The method according to any one of items 11 to 13, wherein the first RRC release message is received from the first base station. (Item 15) 15. The method according to any one of items 11 to 14, wherein the second cell belongs to a second base station. (Item 16) 16. The method according to any one of items 11 to 15, wherein the first configured uplink grant configuration corresponds to a first configured uplink grant configuration identifier. (Item 17) the first configured uplink grant configuration identifier, a configured identity of the first configured uplink grant; A Radio Network Temporary Identifier RNTI of the first configured uplink grant; A resume identity of the wireless device; and 17. The method of claim 16, further comprising at least one serving temporary mobile subscribed identity (S-TMSI) of the wireless device. (Item 18) The configuration of the first configured uplink grant, a physical cell identity of the first cell; and 18. The method according to any one of items 11 to 17, comprising at least one global cell identity of the first cell. (Item 19) 19. The method according to any one of items 11 to 18, wherein the first RRC release message includes a plurality of configured uplink grant configurations corresponding to a plurality of configured uplink grant configuration identifiers. (Item 20) 20. The method according to any one of items 11 to 19, wherein the first configured uplink grant configuration is one of the plurality of configured uplink grant configurations. (Item 21) 21. The method according to any one of items 11 to 20, wherein the first configured uplink grant configuration is for data transmission by the wireless device in the RRC unconnected state via the first cell. (Item 22) the first configured uplink grant configuration comprising: radio resource information of the first configured uplink grant; and a start time of the first configured uplink grant; 22. The method according to any one of items 11 to 21, further comprising a periodicity of the first configured uplink grant. (Item 23) 23. The method according to any of items 11 to 22, wherein the first configured uplink grant configuration configures a configured grant including one or more periodic uplink resources for transmission of uplink data by the wireless device. (Item 24) 24. The method according to any of items 11 to 23, further comprising: transitioning to an RRC disconnected state by the wireless device and based on the first RRC release message. (Item 25) 25. The method of claim 24, wherein the transition is based on a suspension configuration received in the first RRC release message. (Item 26) 26. The method according to any of claims 11 to 25, further comprising communicating by the wireless device via the first cell based on the first configured uplink grant configuration while in the RRC unconnected state. (Item 27) 27. The method of claim 26, wherein the communicating in the RRC non-connected state is associated with a small data transmission SDT procedure of the wireless device. (Item 28) 28. The method according to any one of items 11 to 27, wherein the second cell is different from the first cell. (Item 29) 29. The method according to any one of items 11 to 28, wherein the first configured uplink grant configuration for the RRC non-connected state is associated with the small data transmission SDT procedure. (Item 30) 30. The method of any one of items 11 to 29, further comprising, while in the RRC unconnected state, selecting, by the wireless device, the second cell based on a signal quality of the second cell exceeding a threshold. (Item 31) 31. The method according to any one of items 11 to 30, wherein the second RRC message indicates a first cell identifier of the first cell. (Item 32) The first cell identifier of the first cell, a physical cell identity of the first cell; and 32. The method of claim 31, further comprising at least one global cell identity of the first cell. (Item 33) the second RRC message, RRC Setup Request message, RRC setup complete message, a configured uplink grant configuration release request message, and 33. The method according to any one of items 11 to 32, comprising at least one configured uplink grant configuration request message. (Item 34) transmitting the second RRC message, While the RRC connection of the wireless device is suspended, or 34. The method according to any one of items 11 to 33, wherein the RRC connection of the wireless device is released. (Item 35) 35. The method of claim 34, further comprising: releasing the suspended RRC connection based on detecting a failure to resume the suspended RRC connection. (Item 36) 36. The method according to any of items 11 to 35, wherein the one or more second RRC messages indicate a first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 37) 37. The method of any of items 11 to 36, further comprising releasing, by the wireless device, the first configured uplink grant configuration. (Item 38) Said releasing, determining to establish or re-establish an RRC connection via the second cell; receiving a confirmation indication that the configured uplink grant is released; or 38. The method of claim 37, based on at least one of receiving an RRC response message in response to the second RRC message. (Item 39) A wireless device comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform a method according to any one of items 1 to 38. (Item 40) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of items 1 to 38. (Item 41) 1. A method comprising: sending, by a first base station to the wireless device, a first radio resource control (RRC) release message including a first configured uplink grant (configured uplink grant configuration) of a first cell for an RRC disconnected state of the wireless device; receiving, by the first base station, one or more messages from the second base station including a release indication for the first configured uplink grant configuration of the first cell; Releasing the first configured uplink grant configuration based on the one or more messages. (Item 42) 42. The method of claim 41, further comprising receiving a configured uplink grant configuration request from the wireless device, and transmitting the first configured uplink grant configuration based on the receiving. (Item 43) 43. A method according to any one of items 41 to 42, wherein the first configured uplink grant configuration corresponds to a first configured uplink grant configuration identifier. (Item 44) the first configured uplink grant configuration identifier, a configured identity of the first configured uplink grant; A Radio Network Temporary Identifier RNTI of the first configured uplink grant; A resume identity of the wireless device; and Item 44. The method of item 43, including at least one serving temporary mobile subscribed identity (S-TMSI) of the wireless device. (Item 45) 45. A method according to any one of items 41 to 44, further comprising transitioning an RRC state of the wireless device to the RRC disconnected state by the first base station and based on the sending of the first RRC release message. (Item 46) 46. ​​The method according to any one of items 41 to 45, further comprising communicating with the wireless device via the first cell by the first base station based on the first configured uplink grant configuration while the wireless device is in the RRC unconnected state. (Item 47) Item 47. The method of item 46, wherein the communicating in the RRC non-connected state is associated with a small data transmission SDT procedure of the wireless device. (Item 48) 48. The method according to any one of items 41 to 47, wherein the one or more messages include a first cell identifier of the first cell. (Item 49) 49. The method according to any of items 41 to 48, wherein the one or more messages include a first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 50) 50. A method according to any one of items 41 to 49, wherein the RRC non-connected state is an RRC inactive state or an RRC idle state. (Item 51) 1. A method comprising: receiving, by the second base station, from the wireless device via the second cell, a second RRC message including a release indication for the first configured uplink grant configuration of the first cell; and transmitting, by the second base station to a first base station associated with the first cell, one or more messages including the release indication for the first configured uplink grant configuration of the first cell. (Item 52) the second RRC message, RRC Setup Request message, RRC setup complete message, a configured uplink grant configuration release request message, and Item 52. The method of item 51, comprising at least one configured uplink grant configuration request message. (Item 53) 53. The method according to any of items 51 to 52, wherein the second RRC message indicates a first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 54) 54. The method according to any of items 51 to 53, wherein the second RRC message indicates a first cell identifier of the first cell. (Item 55) 55. The method of claim 54, further comprising determining that the first base station is associated with the first cell based on the first cell identifier. (Item 56) 56. The method of claim 55, wherein the sending of the one or more messages to the first base station is based on determining that the first base station is associated with the first cell. (Item 57) 57. The method according to any of items 51 to 56, wherein the sending of the one or more messages to the first base station is based on the second RRC message including the release indication. (Item 58) A base station comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the base station to perform a method according to any one of items 41 to 57. (Item 59) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of items 41 to 57. (Item 60) 1. A system comprising: 1. A wireless device, comprising: one or more processors; and when executed by the one or more processors, the wireless device comprises: receiving a first radio resource control (RRC) release message from a first base station, the first radio resource control (RRC) release message including a first configured uplink grant configuration of a first cell for an RRC disconnected state of the wireless device; and a memory storing instructions to execute: transmitting, via a second cell, to a second base station, a second RRC message including a release indication for the first configured uplink grant configuration; and the first base station, comprising: one or more processors; and when executed by the one or more processors, the first base station, transmitting the first RRC release message; receiving one or more messages from a second base station including a release indication of the first configured uplink grant configuration; and and a memory storing instructions to perform releasing the first configured uplink grant configuration based on the one or more RRC messages. the second base station, comprising one or more processors, and when executed by the one or more processors, the second base station receiving the second RRC message from the wireless device via the second cell, the second RRC message including the release indication for the first configured uplink grant configuration of the first cell; and and a second base station including a memory storing instructions to cause the first base station to transmit the one or more messages including the release indication for the first configured uplink grant configuration. (Item 61) 1. A method comprising: receiving, by a base station central unit BS-CU, from a base station distributed unit BS-DU associated with the first cell, a first configured uplink grant configuration of the first cell for an RRC non-connected state of the wireless device; sending, by the BS-CU, a first radio resource control (RRC) release message to the wireless device, the first radio resource control (RRC) release message including the first configured uplink grant configuration of the first cell; receiving, by the BS-CU, from the wireless device via a second cell, a second RRC message including a release indication for the first configured uplink grant configuration of the first cell; and transmitting to the BS-DU a message indicating a release of the first configured uplink grant configuration. (Item 62) the second cell is associated with the BS-DU; or Item 62. The method of item 61, wherein the BS-DU is a first BS-DU, and the second cell is associated with a second BS-DU different from the first BS-DU. (Item 63) 63. The method according to any of items 61 to 62, wherein the second RRC message includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 64) 64. The method according to any of items 61 to 63, wherein the second RRC message indicates a first cell identifier of the first cell. (Item 65) Item 65. The method of item 64, further comprising determining that the BS-DU is associated with the first cell based on the first cell identifier. (Item 66) Item 66. The method of item 65, wherein the sending of the message to the BS-DU is based on determining that the BS-DU is associated with the first cell. (Item 67) The message, a first configured uplink grant configuration identifier of the first configured uplink grant configuration; and 67. A method according to any one of items 61 to 66, comprising at least one first cell identifier of the first cell. (Item 68) 68. A method according to any of items 61 to 67, wherein the sending of the message to the BS-DU is based on the second RRC message including the release indication. (Item 69) Item 69. A method according to any one of items 61 to 68, wherein the first configured uplink grant configuration for the RRC non-connected state is associated with a small data transmission SDT procedure. (Item 70) 70. A method according to any one of items 61 to 69, wherein the RRC non-connected state is an RRC inactive state or an RRC idle state. (Item 71) 1. A method comprising: sending, by a base station central unit BS-CU, a first radio resource control (RRC) release message to the wireless device, the first radio resource control (RRC) release message including a first configured uplink grant configuration of a first cell for an RRC disconnected state of the wireless device; receiving, by the BS-CU, from the wireless device via a second cell, a second RRC message including a release indication for the first configured uplink grant configuration of the first cell; sending a message to a base station distributed unit BS-DU associated with the first cell, indicating a release of the first configured uplink grant configuration. (Item 72) Item 72. The method of item 71, further comprising receiving, by the BS-CU, the first configured uplink grant configuration of the first cell from the BS-DU. (Item 73) Item 73. The method of item 72, wherein the receiving the first configured uplink grant configuration of the first cell is prior to the sending of the first RRC release message to the wireless device. (Item 74) 74. A method according to any one of items 71 to 73, wherein the message includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 75) 75. A method according to any one of items 71 to 74, wherein the message includes a first cell identifier of the first cell. (Item 76) 76. A method according to any one of items 71 to 75, wherein the second cell is associated with the BS-DU. (Item 77) 76. A method according to any of items 71 to 75, wherein the BS-DU is a first BS-DU, and the second cell is associated with a second BS-DU different from the first BS-DU. (Item 78) the second RRC message, RRC Setup Request message, RRC setup complete message, a configured uplink grant configuration release request message, and 78. The method according to any of items 71 to 77, comprising at least one configured uplink grant configuration request message. (Item 79) 79. The method according to any of items 71 to 78, wherein the second RRC message includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 80) the first configured uplink grant configuration identifier, a configured identity of the first configured uplink grant; A Radio Network Temporary Identifier RNTI of the first configured uplink grant; A resume identity of the wireless device; and 80. The method of claim 79, further comprising at least one serving temporary mobile subscribed identity (S-TMSI) of the wireless device. (Item 81) 81. The method according to any of items 71 to 80, wherein the second RRC message indicates a first cell identifier of the first cell. (Item 82) The first cell identifier of the first cell, a physical cell identity of the first cell; and Item 82. The method of item 81, including at least one global cell identity of the first cell. (Item 83) 83. The method of claim 82, further comprising determining that the BS-DU is associated with the first cell based on the first cell identifier. (Item 84) Item 84. The method of item 83, wherein the sending of the message to the BS-DU is based on the determining that the BS-DU is associated with the first cell. (Item 85) 85. A method according to any of items 71 to 84, wherein the sending of the message to the BS-DU is based on the second RRC message including the release indication. (Item 86) 86. The method according to any of items 71 to 85, wherein the second cell is different from the first cell. (Item 87) 87. A method according to any one of items 71 to 86, wherein the first configured uplink grant configuration for the RRC non-connected state is associated with a small data transmission SDT procedure. (Item 88) 88. A method according to any one of items 71 to 87, wherein the RRC non-connected state is an RRC inactive state or an RRC idle state. (Item 89) A base station central unit, comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the base station central unit to perform the method according to any one of items 61 to 88. (Item 90) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any of items 61 to 88. (Item 91) 1. A method comprising: Sending, by a base station distributed unit BS-DU, to a base station central unit BS-CU, a first configured uplink grant configuration of a first cell for an RRC disconnected state of the wireless device; receiving a message from the BS-CU indicating a release of the first configured uplink grant configuration; Releasing the first configured uplink grant configuration of the first cell by the BS-DU and based on the message. (Item 92) Item 92. The method of item 91, further comprising receiving a configured uplink grant configuration request from the wireless device by the BS-DU, and transmitting the first configured uplink grant configuration to the BS-CU is based on the receiving. (Item 93) Item 93. The method of item 92, further comprising: determining, by the BS-DU based on the configured uplink grant configuration request, the first configured uplink grant configuration of the first cell; and transmitting the first configured uplink grant configuration based on the determining. (Item 94) A method according to any one of items 91 to 93, further comprising transmitting, by the BS-DU, to the BS-CU, a plurality of configured uplink grant configurations corresponding to a plurality of configured uplink grant configuration identifiers. (Item 95) Item 95. The method of item 94, wherein the first configured uplink grant configuration is one of the plurality of configured uplink grant configurations. (Item 96) 96. A method according to any of items 91 to 95, wherein the first configured uplink grant configuration is for data transmission by the wireless device in the RRC unconnected state via the first cell. (Item 97) the first configured uplink grant configuration comprising: radio resource information of the first configured uplink grant; and a start time of the first configured uplink grant; 97. The method according to any of items 91 to 96, further comprising a periodicity of the first configured uplink grant. (Item 98) Item 98. A method according to any of items 91 to 97, wherein the first configured uplink grant configuration corresponds to a first configured uplink grant configuration identifier. (Item 99) 99. The method of claim 98, wherein the message indicating the release of the first configured uplink grant indicates the first configured uplink grant configuration identifier of the first configured uplink grant configuration. (Item 100) the first configured uplink grant configuration identifier, a configured identity of the first configured uplink grant; A Radio Network Temporary Identifier RNTI of the first configured uplink grant; A resume identity of the wireless device; and A method according to any of items 98 to 99, comprising at least one serving temporary mobile subscribed identity (S-TMSI) of the wireless device. (Item 101) A method according to any of items 91 to 100, further comprising communicating with the wireless device via the first cell by the BS-DU based on the first configured uplink grant configuration while the wireless device is in the RRC unconnected state. (Item 102) Item 102. The method of item 101, wherein the communicating in the RRC non-connected state is associated with a small data transmission SDT procedure of the wireless device. (Item 103) Item 91. A method according to any one of items 91 to 102, wherein the RRC non-connected state is an RRC inactive state or an RRC idle state. (Item 104) 104. The method according to any of items 91 to 103, wherein the message indicating the release of the first configured uplink grant configuration indicates a first cell identifier of the first cell. (Item 105) Item 105. The method of item 104, wherein the first cell identifier of the first cell includes a physical cell identity of the first cell. (Item 106) Item 106. A method according to any one of items 104 to 105, wherein the first cell identifier of the first cell includes a physical cell identity of the first cell and a global cell identity of the first cell. (Item 107) 107. A method according to any of items 91 to 106, wherein the first configured uplink grant configuration configures a configured grant including one or more periodic uplink resources for transmission of uplink data by the wireless device. (Item 108) A base station distributed unit including one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the base station central unit to perform a method according to any one of items 91 to 107. (Item 109) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 91 to 107. (Item 110) 1. A system comprising: a base station central unit (BS-CU), comprising: one or more processors; and when executed by the one or more processors, the BS-CU comprises: receiving, from a base station distributed unit BS-DU associated with the first cell, a first configured uplink grant configuration of the first cell for an RRC disconnected state of a wireless device; sending a first radio resource control (RRC) release message to a wireless device, the first radio resource control (RRC) release message including the first configured uplink grant configuration of the first cell; receiving a second RRC message from the wireless device via a second cell, the second RRC message including a release indication for the first configured uplink grant configuration of the first cell; and a BS-CU including: a memory storing instructions to cause the BS-DU to transmit a message indicating a release of the first configured uplink grant configuration; and The BS-DU, when executed by one or more processors, comprises: sending the first configured uplink grant configuration of the first cell to the BS-CU; receiving the message from the BS-CU indicating a release of the first configured uplink grant configuration of the first cell; The system includes a BS-DU and a memory storing instructions to execute releasing the first configured uplink grant configuration of the first cell based on the message. (Item 111) 1. A method comprising: Transmitting, by the wireless device and via the second cell of the base station, a request for configuration of a configured grant of the first cell; receiving a radio resource control (RRC) release message from the base station, the radio resource control (RRC) release message including the configuration of the configured grant for the first cell; transmitting one or more uplink packets using the configured grant and via the first cell. (Item 112) The cell identity of the first cell, the request for the configuration of the configured grant; and Item 112. The method of item 111, which is included in at least one of the configurations of the configured grant. (Item 113) The cell identity of the first cell: Physical Cell Identity, or A method according to any one of items 111 to 112, including at least one global cell identity. (Item 114) said transmitting said request the second cell is a serving cell of the wireless device; and Item 114. The method according to any of items 111 to 113, wherein the first cell is a non-serving cell of the wireless device. (Item 115) Item 115. The method of any of items 111 to 114, wherein the transmitting the request includes transmitting the request while the wireless device is in an RRC connected state. (Item 116) Based on the RRC release message, from the RRC connected state, RRC inactive state, or 116. The method according to any one of items 111 to 115, further comprising transitioning to an RRC idle state. (Item 117) Item 117. The method of item 116, wherein the transmitting one or more uplink packets includes transmitting one or more uplink packets while the wireless device is in the RRC inactive state or the RRC idle state. (Item 118) Item 118. The method of any of items 116 to 117, wherein the transitioning includes transitioning after suspending an RRC connection of the wireless device based on a suspension configuration indicating suspension of an RRC connection. (Item 119) Item 119. The method of item 118, wherein the RRC release message further includes the suspension configuration. (Item 120) 110. The method according to any one of items 118 to 119, wherein the pause configuration includes a next hop sequence count (NCC) value. (Item 121) Item 121. The method of item 120, further comprising deriving a security key for the wireless device based on the NCC value. (Item 122) Item 122. The method of item 121, wherein the transmitting the one or more uplink packets includes transmitting the one or more uplink packets using the security key. (Item 123) Based on the security key, the one or more uplink packets are Integrity protected uplink packets, and The method according to any one of items 121 to 122, wherein the at least one is an encrypted uplink packet. (Item 124) The configuration of the configured grant: the identity of said configuration; A Radio Network Temporary Identifier (RNTI) for the configured grant; and radio resource information of the configured grant; and a start time of the configured grant; the periodicity of the configured grant; and a configured grant window duration. (Item 125) 125. The method of claim 124, further comprising initiating the configured grant window based on the transmitting of the one or more uplink packets. (Item 126) 125. The method of any of items 123 to 124, further comprising monitoring a physical downlink control channel for a response to the one or more uplink packets until the configured grant window expires. (Item 127) The radio resource information of the configured grant is Physical uplink shared channel configuration parameters, Physical downlink control channel configuration parameters, Physical uplink control channel configuration parameters, Downlink carrier configuration parameters, and A method according to any one of items 124 to 126, including at least one uplink carrier configuration parameter. (Item 128) 128. The method according to any of items 111 to 127, wherein the second cell is different from the first cell. (Item 129) A wireless device comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform a method according to any one of items 111 to 128. (Item 130) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 111 to 128. (Item 131) 1. A method comprising: receiving, by the base station, from the wireless device via the second cell, a request for configuration of a configured grant for the first cell; and transmitting to the wireless device a radio resource control (RRC) release message including the configuration of the configured grant for the first cell. (Item 132) The cell identity of the first cell, the request for the configuration of the configured grant; and Item 132. The method of item 131, which is included in at least one of the configurations of the configured grant. (Item 133) The cell identity of the first cell: Physical Cell Identity, or 133. A method according to any one of items 131 to 132, including at least one global cell identity. (Item 134) said receiving said request the second cell is a serving cell of the wireless device; and Item 134. The method according to any of items 131 to 133, wherein the first cell is a non-serving cell of the wireless device. (Item 135) Item 135. The method of any of items 131 to 134, wherein receiving the request includes receiving the request while the wireless device is in an RRC connected state. (Item 136) by the base station and based on the RRC release message, changing the RRC state of the wireless device from the RRC connected state to RRC inactive state, or 136. The method according to any one of items 131 to 135, further comprising transitioning to an RRC idle state. (Item 137) Item 137. The method of item 136, wherein the receiving one or more uplink packets includes receiving one or more uplink packets while the wireless device is in the RRC inactive state or the RRC idle state. (Item 138) Item 138. The method of any of items 136 to 137, wherein the transitioning includes transitioning after suspending an RRC connection of the wireless device based on a suspension configuration indicating suspension of an RRC connection. (Item 139) Item 139. The method of item 138, wherein the RRC release message further includes the suspension configuration. (Item 140) 130. The method according to any of items 138 to 139, wherein the pause configuration includes a next hop sequence count (NCC) value. (Item 141) Item 141. The method of item 140, further comprising deriving a security key for the wireless device based on the NCC value. (Item 142) Item 142. The method of item 141, wherein the receiving the one or more uplink packets includes transmitting the one or more uplink packets using the security key. (Item 143) Based on the security key, the one or more uplink packets are Integrity protected uplink packets, and The method according to any one of items 141 to 142, wherein the at least one is an encrypted uplink packet. (Item 144) The configuration of the configured grant: the identity of said configuration; A Radio Network Temporary Identifier (RNTI) for the configured grant; and radio resource information of the configured grant; and a start time of the configured grant; the periodicity of the configured grant; and a configured grant window duration. (Item 145) 145. The method of claim 144, further comprising initiating the configured grant window based on the receiving of the one or more uplink packets. (Item 146) The radio resource information of the configured grant is Physical uplink shared channel configuration parameters, Physical downlink control channel configuration parameters, Physical uplink control channel configuration parameters, Downlink carrier configuration parameters, and A method according to any one of items 144 to 145, including at least one uplink carrier configuration parameter. (Item 147) 147. The method according to any of items 131 to 146, wherein the second cell is different from the first cell. (Item 148) A base station comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the base station to perform a method according to any one of items 131 to 147. (Item 149) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 131 to 147. (Item 150) 1. A system comprising: 1. A wireless device, comprising: one or more processors; and when executed by the one or more processors, the wireless device comprises: transmitting, via the second cell of the base station, a request for configuration of a configured grant of the first cell; receiving a radio resource control (RRC) release message from the base station, the radio resource control (RRC) release message including the configuration of the configured grant for the first cell; and a memory storing instructions to transmit one or more uplink packets using the configured grant and via the first cell; and The base station, comprising: one or more processors; and when executed by the one or more processors, the base station is provided with: receiving the request from the wireless device via the second cell; and a memory storing instructions that cause the wireless device to transmit the RRC release message. [Brief description of the drawings]

[0005] Some examples of various embodiments of the present disclosure are described herein with reference to the drawings.

[0006] [Figure 1] 1A and 1B show an example of a mobile communication network in which embodiments of the present disclosure may be implemented.

[0007] [Diagram 2] 2A and 2B show the New Radio (NR) user plane and control plane protocol stacks, respectively.

[0008] [Diagram 3] FIG. 3 shows an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

[0009] [Figure 4] FIG. 4A shows an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

[0010] FIG. 4B shows an example format of a MAC subheader in a MAC PDU.

[0011] [Diagram 5] 5A and 5B show the mapping between downlink and uplink logical, transport and physical channels, respectively.

[0012] [Figure 6] FIG. 6 is an exemplary diagram illustrating RRC state transitions of a UE.

[0013] [Figure 7] FIG. 7 shows an example of the structure of an NR frame in which OFDM symbols are grouped.

[0014] [Figure 8] FIG. 8 shows an example of a slot configuration in the time and frequency domain of an NR carrier.

[0015] [Figure 9] FIG. 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0016] [Figure 10] FIG. 10A shows three carrier aggregation configurations with two component carriers.

[0017] FIG. 10B shows an example of how aggregation cells can be arranged into one or more PUCCH groups.

[0018] [Figure 11] FIG. 11A shows an example of an SS / PBCH block structure and location.

[0019] FIG. 11B shows an example of CSI-RS mapped to the time and frequency domain.

[0020] [Figure 12] 12A and 12B show examples of three downlink and uplink beam management procedures, respectively.

[0021] [Figure 13] 13A, 13B, and 13C show a four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure, respectively.

[0022] [Figure 14]FIG. 14A shows an example of a CORESET configuration for bandwidth portions.

[0023] FIG. 14B shows an example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing.

[0024] [Figure 15] FIG. 15 illustrates an embodiment of a wireless device communicating with a base station.

[0025] [Figure 16] 16A, 16B, 16C, and 16D show example structures for uplink and downlink transmissions.

[0026] [Figure 17] FIG. 17 shows an example of an RRC connection re-establishment procedure.

[0027] [Figure 18] FIG. 18 shows an example of an RRC connection resumption procedure.

[0028] [Figure 19] FIG. 19 shows an example of a constructed grant.

[0029] [Figure 20] FIG. 20 shows an example of a user plane configured grant and a control plane configured grant.

[0030] [Figure 21] FIG. 21 shows an example of releasing configured grant (CG) configuration parameters.

[0031] [Figure 22] FIG. 22 shows an example of an enhanced CG release procedure.

[0032] [Figure 23] FIG. 23 shows an example of an enhanced CG release procedure for failure to resume an RRC connection.

[0033] [Figure 24] FIG. 24 shows an example of CG release in a CU DU architecture.

[0034] [Diagram 25] FIG. 25 shows an example of a CG configuration request including a cell identity. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] As used herein, the terms "a" and "an" and similar terms are interpreted as "at least one" and "one or more." Similarly, any term ending with the suffix "(s)" should be interpreted as "at least one" and "one or more." As used herein, the term "may" is interpreted as "may be, for example." In other words, the term "may" indicates that the phrase following the term "may" is one example of multiple suitable possibilities, and may or may not be used by one or more of the various embodiments. As used herein, the terms "comprises" and "consists of" recite one or more components of a described element. The term "comprises" is interchangeable with "includes" and does not exclude unrecited components included in a described element. In contrast, "consists of" provides a complete recitation of one or more components of a described element. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on." As used herein, the term "and / or" refers to any possible combination of the listed elements. For example, "A, B, and / or C" can refer to A, B, C, A and B, A and C, B and C, or A, B, and C.

[0036] If A and B are sets and every element of A is also an element of B, then A is said to be a subset of B. Only non-empty sets and subsets are considered herein. For example, possible subsets of B={cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "based at least on") indicates that the phrase following the term "based on" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "adopted / used" (or, equivalently, "at least adopted / used") indicates that the phrase following the phrase "adopted / used" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments.

[0037] The term configured may relate to the capacity of a device, whether the device is in an operational or non-operational state. Configured may also refer to a particular setting of a device that affects the operational characteristics of the device, whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device, whether the device is in an operational or non-operational state, to provide the device with a particular characteristic. A term such as "a control message originating in a device" may mean that the control message has parameters that can be used to configure a particular characteristic in the device or can be used to implement a particular action in the device, whether the device is in an operational or non-operational state.

[0038] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) can contain one or more information objects, which can contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, which contains parameter (IE)K, which contains parameter (IE)J, then N contains K and N contains J. In an example embodiment, when one or more messages contain multiple parameters, it means that a parameter of the multiple parameters is included in at least one of the one or more messages, but need not be included in each of the one or more messages.

[0039] Furthermore, many features presented above are described as optional through the use of "may" or through the use of parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe each and every variation that may be obtained by selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such variations. For example, a system described as having three optional features can be embodied in seven ways, i.e., with only one of the three possible features, any two of the three features, or three of the three features.

[0040] Many of the elements described in the disclosed embodiments may be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, which may be behaviorally equivalent. For example, a module may be implemented in software routines written in a computer language configured to run on a hardware machine (C, C++, Fortran, Java, Basic, Matlab, etc.) or Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It may also be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using Hardware Description Languages ​​(HDLs) such as Verilog or VHSIC Hardware Description Language (VHDL), which configure the connections between the internal hardware modules with fewer functions of the programmable device. To achieve a functional modular result, the above techniques are often used in combination.

[0041] 1A illustrates an example of a mobile communication network 100 in which an embodiment of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As shown in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0042] The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interfacing function, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0043] The RAN 104 may connect the CN 102 to the wireless devices 106 via wireless communication over the air interface. As part of the wireless communication, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless devices 106 over the air interface is known as the downlink, and the communication direction from the wireless devices 106 to the RAN 104 over the air interface is known as the uplink. The downlink transmission may be separated from the uplink transmission using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0044] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-portable) device for which wireless communication is required or available. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicular roadside unit (RSU), a relay node, an automobile, and / or any combination thereof. The term wireless device encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit / receive unit (WTRU), and / or wireless communication device.

[0045] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater or relay node used to extend the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, e.g., associated with WiFi or other suitable wireless communication standard), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0046] The base stations included in the RAN 104 may include one or more sets of antennas for communicating over the air interface with the wireless devices 106. For example, one or more base stations may include three sets of antennas for controlling three cells (or sectors) respectively. The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive a transmission from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide wireless coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0047] In addition to three sector sites, other implementations of base stations are possible. For example, one or more base stations of the RAN 104 may be implemented as sector sites having more or less than three sectors. One or more base stations of the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to multiple remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of ​​a donor node. The baseband processing unit coupled to the RRHs may be part of a centralized or cloud RAN architecture, and the baseband processing unit may be centralized or virtualized within a pool of baseband processing units. The repeater node may amplify and rebroadcast the wireless signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the wireless signal received from the donor node and remove noise before amplifying and rebroadcasting the wireless signal.

[0048] The RAN 104 may be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations may be used to provide small coverage areas, e.g., coverage areas that overlap with relatively large coverage areas provided by macrocell base stations. Small coverage areas may be provided in areas of high data traffic (or so-called hot spots) or areas where macrocell coverage is weak. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

[0049] The Third Generation Partnership Project (3GPP®) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 of FIG. 1A. To date, 3GPP® has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to a RAN of a 3GPP® 5G network, referred to as Next Generation RAN (NG-RAN). The embodiments may be applicable to the RAN of other mobile communication networks, such as the RAN 104 of FIG. 1A, RANs of earlier 3G and 4G networks, and future networks yet to be specified (e.g., a 3GPP® 6G network). NG-RAN implements the 5G radio access technology known as New Radio (NR), and may be provisioned to implement other radio access technologies, including 4G radio access technologies or non-3GPP radio access technologies.

[0050] FIG. 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN run by a network operator. As shown in FIG. 1B, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and a UE 156A and a UE 156B (collectively, UE 156). These components may be implemented and operate in the same or similar manner as the corresponding components described with respect to FIG. 1A.

[0051] 5G-CN 152 provides UE 156 with an interface to one or more DNs, such as a public DN (e.g., Internet), a private DN, and / or an intra-operator DN. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs of 3GPP 4G networks, the base of 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as a network function that provides services via interfaces to other network functions. The network functions of 5G-CN 152 may be implemented in several ways: as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0052] As shown in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, as shown in FIG. 1B as one component AMF / UPF 158 for ease of explanation. The UPF 158B may act as a gateway between the NG-RAN 154 and one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic usage reporting, uplink classification to support routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggers. The UPF 158B may act as an anchor point for intra / inter radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-homed PDU sessions. The UE 156 may be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0053] The AMF 158A may perform functions such as termination of Non-Access Stratum (NAS) signaling, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access grant including checking roaming rights, mobility management control (subscription and policy), support for network slicing, and / or selection of a Session Management Function (SMF). NAS may refer to a function operating between the CN and the UE, and AS may refer to a function operating between the UE and the RAN.

[0054] 5G-CN 152 may include one or more additional network functions not shown in FIG. 1B for clarity. For example, 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

[0055] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via wireless communication over the air interface. The NG-RAN 154 may include one or more gNBs (collectively gNB 160), illustrated as gNB 160A and gNB 160B, and / or one or more ng-eNBs (collectively ng-eNB 162), illustrated as ng-eNB 162A and ng-eNB 162B. The gNBs 160 and ng-eNB 162 may more generally be referred to as base stations. The gNBs 160 and ng-eNB 162 may include one or more sets of antennas for communicating with the UE 156 over the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas for controlling three cells (or sectors), respectively. Together, the gNB160 and ng-eNB162 cells may provide radio coverage to the UE156 over a wide geographic area to support UE mobility.

[0056] As shown in FIG. 1B, the gNB 160 and / or the ng-eNB 162 may be connected to the 5G-CN 152 by an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an Internet Protocol (IP) transport network. The gNB 160 and / or the ng-eNB 162 may be connected to the UE 156 by a Uu interface. For example, as shown in FIG. 1B, the gNB 160A may be connected to the UE 156A by a Uu interface. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces may be used by the network elements of FIG. 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data of interest to a user. The control plane may process signaling messages of interest to the network elements.

[0057] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by an NG User Plane (NG-U) interface. The NG-U interface may provide for the provision of user plane PDUs between the gNB 160A and the UPF 158B (e.g., non-guaranteed delivery). The gNB 160A may be connected to the AMF 158A using an NG Control Plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, forwarding of NAS messages, paging, PDU session management, and configuration forwarding and / or alert message transmission.

[0058] The gNB 160 may provide NR user plane and control plane protocol terminations towards the UE 156 on the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations towards the UE 156A on the Uu interface associated with a first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UE 156 on the Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B on the Uu interface associated with a second protocol stack.

[0059] The 5G-CN 152 has been described as being configured to handle NR and 4G radio access. Those skilled in the art will appreciate that it may be possible for the NR to connect to a 4G core network in a mode known as "non-standalone operation." In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0060] 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with protocol stacks that the network elements use to exchange data and signaling messages. The protocol stacks may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

[0061] Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks, respectively, for the Uu interface between a UE 210 and a gNB 220. The protocol stacks shown in Figures 2A and 2B may be the same or similar to those used for the Uu interface between a UE 156A and a gNB 160A shown in Figure 1B, for example.

[0062] 2A shows an NR user plane protocol stack including five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above the PHYs 211 and 221 include media access control layers (MAC) 212 and 222, radio link control layers (RLC) 213 and 223, packet data convergence protocol layers (PDCP) 214 and 224, and service data application protocol layers (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0063] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow processing. The UE 210 may receive services via a PDU session, which may be a logical connection between the UE 210 and the DN. The PDU session may have one or more QoS flows. The UPF (e.g., UPF 158B) of the CN may map IP packets to one or more QoS flows of the PDU session based on the QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers via reflected mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI) that can be observed by the SDAP 215 at the UE 210 to determine mapping / demapping between QoS flows and data radio bearers.

[0064] PDCP 214 and PDCP 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP 214 and 224 may perform retransmission of untransmitted packets, in-sequence delivery and resequencing of packets, and elimination of duplicate received packets, for intra-gNB handover, for example. PDCP 214 and 224 may perform packet duplication to improve the likelihood of a packet being received and to eliminate any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0065] Although not shown in FIG. 3, the PDCPs 214 and 224 may perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells, or more generally, two cell groups, a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by a cell group in dual connectivity. The PDCPs 214 and 224 may map / demap the split radio bearer between the RLC channels belonging to the cell group.

[0066] The RLCs 213 and 223 may perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC may perform one or more of the indicated functions. This RLC configuration may be per logical channel independent of numerology and / or transmission time interval (TTI) duration. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as services to the PDCPs 214 and 224, respectively.

[0067] The MAC 212 and MAC 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by dynamic scheduling. Scheduling may be performed at the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction, priority handling between logical channels of the UE 210 by logical channel prioritization, and / or padding through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in case of carrier aggregation (CA)). The MAC 212 and MAC 222 may support one or more numerologies and / or transmission timings. In one embodiment, mapping restrictions on logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As shown in Figure 3, MACs 212 and 222 can offer logical channels to RLCs 213 and 223 as services.

[0068] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions to transmit and receive information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels to the MACs 212 and 222 as a service.

[0069] 4A illustrates an example of a downlink data flow through an NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs at the gNB 220. The uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow illustrated in FIG. 4A.

[0070] The downlink data flow in FIG. 4A begins when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to the first radio bearer 402 and maps IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in FIG. 4A) is added to the IP packets. Data units from / to the higher protocol layer are called service data units (SDUs) of the lower protocol layer, and data units to / from the lower protocol layer are called protocol data units (PDUs) of the higher protocol layer. As shown in FIG. 4A, the data units from the SDAP 225 are the SDUs of the lower protocol layer PDCP 224 and the PDUs of the SDAP 225.

[0071] The remaining protocol layers in FIG. 4A may perform the relevant functions (e.g., with respect to FIG. 3), add corresponding headers, and forward the respective outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to MAC 222. MAC 222 may multiplex several RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, the MAC subheader may be distributed throughout the MAC PDU, as shown in FIG. 4A. In LTE, the MAC subheader may be placed entirely at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated delays because the MAC PDU subheaders may be calculated before the complete MAC PDU is assembled.

[0072] 4B shows an example format of a MAC subheader in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (e.g., in bytes) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCID) field to identify the logical channel that the MAC SDU initiated to assist in the demultiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0073] FIG. 4B further illustrates a MAC Control Element (CE) inserted into a MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into a MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs, such as buffer status reports and power headroom reports, activation / deactivation MAC CEs, such as for PDCP duplicate detection activation / deactivation, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components, discontinuous reception (DRX)-related MAC CEs, timing advancement MAC CEs, and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader of a similar format as described for the MAC SDU and may be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

[0074] Before describing the NR control plane protocol stack, we first describe logical, transport, and physical channels and the mapping between channel types. One or more channels may be used to perform functions related to the NR control plane protocol stack, as described below.

[0075] 5A and 5B show the mapping between logical, transport, and physical channels for the downlink and uplink, respectively. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels, which carry control and configuration information in the NR control plane, or as traffic channels, which carry data in the NR user plane. Logical channels can be classified as dedicated logical channels, which are dedicated to a particular UE, or as common logical channels, which can be used by multiple UEs. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - a paging control channel (PCCH) for indicating paging messages used to page UEs whose location is not known to the network at cell level; - a Broadcast Control Channel (BCCH) for carrying system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which may be used by UEs to obtain information about how the cell is configured and how to operate within the cell; - a Common Control Channel (CCCH) for transmitting control messages along with random access; - a Dedicated Control Channel (DCCH) for transmitting control messages to and from a specific UE for configuring the UE; - A Dedicated Traffic Channel (DTCH) for transmitting user data to and from a specific UE.

[0076] Transport channels are used between the MAC and PHY layers and may be defined by how they transmit the information they transmit over the air interface. The set of transport channels defined by NR includes, for example: - a paging channel (PCH) for transmitting paging messages originating from the PCCH; - a Broadcast Channel (BCH) for carrying the MIB from the BCCH; - a Downlink Shared Channel (DL-SCH) for transmission of downlink data and signaling messages, including SIBs from the BCCH; - an uplink shared channel (UL-SCH) for transmitting uplink data and signaling messages; - A Random Access Channel (RACH) that allows a UE to connect to the network without prior scheduling.

[0077] The PHY can pass information between processing levels of the PHY using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY generates control information to support the lower level operation of the PHY and may provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR includes, for example: - a Physical Broadcast Channel (PBCH) to carry the MIB from the BCH; - a Physical Downlink Shared Channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH; - a Physical Downlink Control Channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; - a Physical Uplink Shared Channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some examples, Uplink Control Information (UCI), as described below; - a physical uplink control channel (PUCCH) for carrying UCI, which may include a HARQ acknowledgement, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a scheduling request (SR); - A Physical Random Access Channel (PRACH) for random access.

[0078] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by NR include the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), the Channel State Information Reference Signal (CSI-RS), the Demodulation Reference Signal (DMRS), the Sounding Reference Signal (SRS), and the Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0079] 2B shows an example of an NR control plane protocol stack. In FIG. 2B, the NR control plane protocol stack may use the first four protocol layers that are the same / similar to the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource control (RRC) 216 and 226, and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0080] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., AMF 158A), or more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages called NAS messages. There is no direct path between the UE 210 and the AMF 230 over which NAS messages can be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0081] The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220, or more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220 via signaling messages called RRC messages. The RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex the control plane and user plane data within the same transport block (TB). The RRCs 216 and 226 may provide control plane functions such as broadcasting system information related to the AS and the NAS, paging initiated by the CN or the RAN, establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN, security functions including key management, establishment, configuration, maintenance, and release of signaling and data radio bearers, mobility functions, QoS management functions, control of UE measurement reporting and reporting, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing an RRC connection, the RRCs 216 and 226 may establish an RRC context, which may involve setting parameters for communications between the UE 210 and the RAN.

[0082] FIG. 6 is an example diagram illustrating RRC state transitions of a UE. The UE may be the same as or similar to the wireless device 106 shown in FIG. 1A, the UE 210 shown in FIG. 2A and FIG. 2B, or any other wireless device described in this disclosure. As shown in FIG. 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0083] In the RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of one or more base stations included in the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the gNB 220 shown in FIG. 2A and FIG. 2B, or any other base station described in this disclosure. The base station to which the UE is connected may have an RRC context for the UE. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example, one or more AS contexts, one or more radio link configuration parameters, bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. In the RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC Connected 602 to RRC Idle 604 via a Connection Release procedure 608 or to RRC Inactive 606 via a Connection Deactivation procedure 610.

[0084] In RRC Idle 604, no RRC context may be established for the UE. In RRC Idle 604, the UE may not have an RRC connection with a base station. During RRC Idle 604, the UE may be in a sleep state most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once every discontinuous reception cycle) to monitor for paging messages from the RAN. UE mobility may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC Idle 604 to RRC Connected 602 via a connection establishment procedure 612, which may involve a random access procedure as discussed in more detail below.

[0085] In RRC Inactive 606, previously established RRC context is maintained in the UE and base station. This allows for faster transition to RRC Connection 602 with reduced signaling overhead compared to transition from RRC Idle 604 to RRC Connection 602. In RRC Inactive 606, the UE is in a sleep state and UE mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connection 602 by a Connection Resume procedure 614 or to RRC Idle 604 via a Connection Release procedure 616 that is the same as or similar to the Connection Release procedure 608.

[0086] The RRC states may be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to allow the network to inform the UE of events via paging messages without broadcasting the paging messages throughout the entire mobile communication network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 may allow the network to track the UE on a cell group level, so that paging messages may be broadcast on cells of the cell group in which the UE is currently located instead of the entire mobile communication network. The mobility management mechanisms in RRC Idle 604 and RRC Inactive 606 track the UE on a cell group level. They may do so using different granularity of grouping. For example, there may be three levels of granularity of cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

[0087] The tracking area may be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0088] The RAN area may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. The RAN notification area may include one or more cell identities, a list of RAIs, or a list of TAIs. In one embodiment, a base station may belong to one or more RAN notification areas. In one embodiment, a cell may belong to one or more RAN notification areas. If the UE moves through cell reselection to a cell that is not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the RAN notification area of ​​the UE.

[0089] A base station that stores an RRC context for a UE or a last serving base station for the UE may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the UE at least during the time the UE remains in the RAN notification area of ​​the anchor base station and / or during the time the UE remains in RRC inactive 606.

[0090] A gNB, such as gNB 160 in FIG. 1B, can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU can include RRC, PDCP, and SDAP. The gNB-DU can include RLC, MAC, and PHY.

[0091] In NR, physical signals and physical channels (FIGS. 5A and 5B) may be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data on F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), which are called source symbols and are split into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block that transforms them to the time domain. The IFFT block may take F source symbols, one at a time, from each of the F parallel symbol streams and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time domain samples that represent a sum of the F orthogonal subcarriers. The F time domain samples may form a single OFDM symbol. After some processing (e.g., adding a cyclic prefix) and upconversion, the OFDM symbols provided by the IFFT block may be transmitted over the air interface at a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This processing produces Discrete Fourier Transform (DFT) pre-coded OFDM symbols, which can be used by UEs in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0092] FIG. 7 shows an example of an NR frame configuration in which OFDM symbols are grouped. The NR frame may be identified by a system frame number (SFN). The SFN may repeat at a period of 1024 frames. As shown, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each of which is 1 ms in duration. The subframes may be divided into slots, each of which includes, for example, 14 OFDM symbols per slot.

[0093] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. In NR, flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to cells with carrier frequencies in the mm-wave range). Numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0094] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 illustrates this numerology-dependent slot duration and slot-per-subframe transmission structure (for ease of illustration, a numerology with 240 kHz subcarrier spacing is not shown in Figure 7). Subframes in NR may be used as numerology-independent time references, while slots may be used as units around which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR is decoupled from slot duration and may start with any OFDM symbol and end with as many symbols as necessary for transmission. These partial slot transmissions may be referred to as minislot or subslot transmissions.

[0095] FIG. 8 shows an example of a slot configuration in the time and frequency domain of an NR carrier. A slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans 12 consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such limitations, if used, may limit an NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, and the 400 MHz bandwidth may be set based on the 400 MHz per carrier bandwidth limitation.

[0096] Figure 8 shows a single numerology used across the entire bandwidth of an NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0097] NR may support a wide range of carrier bandwidths (e.g., up to 400 MHz with 120 kHz subcarrier spacing). Not all UEs may be able to receive the full carrier bandwidth (e.g., hardware limitations, etc.). Also, receiving the full carrier bandwidth may be prohibitive from a UE power consumption perspective. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its reception bandwidth based on the amount of traffic the UE plans to receive. This is called bandwidth adaptation.

[0098] NR defines a bandwidth portion (BWP) to support UEs that cannot receive the entire carrier bandwidth and to support bandwidth adaptation. In one embodiment, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via the RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the BWPs configured for a serving cell may be active. These one or more BWPs may be referred to as the active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0099] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0100] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), the base station may configure the UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domain where the UE can find control information. The search space may be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, the base station may configure the UE with a common search space on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

[0101] For an uplink BWP in a set of configured uplink BWPs, the BS may configure the UE with one or more resource sets for one or more PUCCH transmissions. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) in the downlink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

[0102] One or more BWP indicator fields may be provided in the downlink control information (DCI). The value of the BWP indicator field may indicate which BWP of a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

[0103] The base station may semi-statically configure the UE with a default downlink BWP in a set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP for the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0104] The base station may configure the UE with a BWP inactivity timer value for the PCell. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer when (a) the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for paired spectrum operation, or (b) the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than a default downlink BWP or an uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI for a certain period of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., increasing it from zero to the BWP inactivity timer value or decreasing it from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may be switched from the active downlink BWP to the default downlink BWP.

[0105] In one embodiment, a base station may semi-statically configure a UE with one or more BWPs, and the UE may switch the active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as the active BWP and / or in response to expiration of a BWP inactivity timer (e.g., if the second BWP is a default BWP).

[0106] Downlink and uplink BWP switching (BWP switching refers to switching from a currently active BWP to a currently not active BWP) may be performed independently in paired spectrum. In unpaired spectrum, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or initiation of random access.

[0107] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between the BWPs at a switching point. In the example of FIG. 9, the UE may switch from BWP 902 to BWP 904 at switching point 908. The switching at switching point 908 may occur for any suitable reason, for example, in response to expiration of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 906 at switching point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch from the active BWP 906 to BWP 904 at switching point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 902 at switching point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0108] If the UE is configured for a secondary cell with a default downlink BWP in the set of configured downlink BWPs and timer values, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell, e.g., the UE may use timer values ​​and default downlink BWPs for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell.

[0109] To provide a larger data rate, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit simultaneously to and from the same UE. The aggregated carriers in CA may be called component carriers (CCs). When using CA, there are many serving cells for the UE and one cell for the CC. The CC can have three configurations in the frequency domain:

[0110] 10A shows three CA configurations with two CCs. In the intra-band, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located immediately adjacent to each other in the frequency band. In the intra-band, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in frequency bands by a gap. In the intra-band configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0111] In one embodiment, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell of a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. Being able to aggregate more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic in the downlink than in the uplink.

[0112] When using CA, one of the aggregation cells of the UE may be referred to as a primary cell (PCell). The PCell may be a serving cell to which the UE initially connects in RRC connection establishment, re-establishment, and / or handover. The PCell may provide the UE with NAS mobility information and security inputs. The UE may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). The other aggregation cells of the UE may be referred to as secondary cells (SCells). In one embodiment, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0113] A configured SCell for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of a SCell may mean that PDCCH and PDSCH reception on the SCell is deactivated and PUSCH, SRS, and CQI transmission on the SCell is deactivated. A configured SCell may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCell (e.g., among a subset of configured SCells) for a UE is activated or deactivated. A configured SCell may be deactivated in response to expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0114] Downlink control information such as a cell's scheduling assignment and scheduling grant may be transmitted on the cell corresponding to the assignment and grant, known as self-scheduling. DCI for a cell may be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregation cells (e.g., HARQ acknowledgement and channel state feedback such as CQI, PMI, and / or RI) may be transmitted on the PUCCH of the PCell. A large number of aggregated downlink CCs may overload the PUCCH of the PCell. A cell may be divided into multiple PUCCH groups.

[0115] FIG. 10B illustrates an example of how aggregation cells may be configured into one or more PUCCH groups. The PUCCH group 1010 and the PUCCH group 1050 may each include one or more downlink CCs. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs, PCell 1011, SCell 1012, and SCell 1013. The PUCCH group 1050 includes three downlink CCs, PCell 1051, SCell 1052, and SCell 1053, in this example. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary SCells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted on the uplink of PSCell 1061. In one embodiment, if the aggregation cells depicted in FIG. 10B are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI associated with downlink CCs may be overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, the overload may be prevented.

[0116] A cell including a downlink carrier and an optional uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may identify the downlink carrier and / or uplink carrier of a cell, depending on, for example, the context in which the physical cell ID is used. The physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. The cell index may be determined using an RRC message. In this disclosure, the physical cell ID may be referred to as a carrier ID. The cell index may be referred to as a carrier index. For example, when this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell including the first downlink carrier. The same concept may apply, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification may mean that the cell including the first carrier is activated.

[0117] In CA, the multi-carrier nature of the PHY may be exposed to the MAC. In one embodiment, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment / grant per serving cell. The transport block and potential HARQ retransmissions of the transport block may be mapped to the serving cell.

[0118] In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more Reference Signals (RS) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS as shown in FIG. 5A) to the UE. In the uplink, the UE may transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS as shown in FIG. 5B). The PSS and SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and SSS may be provided in a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station may periodically transmit bursts of the SS / PBCH block.

[0119] FIG. 11A illustrates an example of a structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). A burst may be transmitted periodically (e.g., every two frames or every 20 ms). A burst may be limited to a half frame (e.g., the first half frame having a duration of 5 ms). It will be appreciated that FIG. 11A is an example, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, location of the burst within a frame) may be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH block is transmitted, the numerology or subcarrier spacing of the cell, configuration by the network (e.g., using RRC signaling), or any other suitable factor. In one example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the wireless network configures the UE to assume a different subcarrier spacing.

[0120] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in the example of FIG. 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., the last two symbols) and may span one OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., over the next three OFDM symbols) and may span 240 subcarriers.

[0121] The location of the SS / PBCH block in the time and frequency domain may not be known to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier for a PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain period of time (e.g., 20 ms), the UE may search for a PSS at a different frequency location within the carrier as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domain, the UE may determine the location of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In one embodiment, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on the synchronization raster. In one embodiment, cell selection / search and / or reselection may be based on the CD-SSB.

[0122] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the PSS and SSS sequences, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it was transmitted according to a transmission pattern, where the SS / PBCH block is a known distance from a frame boundary.

[0123] The PBCH may use QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include an indication of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a Master Information Block (MIB) used to provide one or more parameters to the UE. The MIB may be used by the UE to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. The SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating that SIB1 is not present, the UE may point to a frequency, and the UE may search for an SS / PBCH block on the frequency to which the UE is pointed.

[0124] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCL'd) (e.g., have the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume that the QCL's for the SS / PBCH block transmissions have different SS / PBCH block indices.

[0125] SS / PBCH blocks (e.g., blocks within a half frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). In one embodiment, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0126] In one embodiment, within the frequency span of a carrier, a base station may transmit multiple SS / PBCH blocks. In one embodiment, a first PCI of a first SS / PBCH block of the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or may be the same.

[0127] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more of the same / similar CSI-RS. The UE may measure one or more CSI-RS. The UE may estimate downlink channel conditions and / or generate a CSI report based on measurements of one or more downlink CSI-RS. The UE may provide the CSI report to the base station. The base station may perform link adaptation using feedback provided by the UE (e.g., estimated downlink channel conditions).

[0128] A base station may semi-statically configure a UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with a location and periodicity in the time and frequency domain. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the UE that CSI-RS resources in a CSI-RS resource set are activated and / or deactivated.

[0129] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with the timing and / or periodicity of the CSI reports. For aperiodic CSI reporting, the base station may request the CSI reports. For example, the base station may instruct the UE to measure configured CSI-RS resources and provide a CSI report on the measurements. For semi-persistent CSI reporting, the base station may configure the UE to periodically transmit and selectively start or stop periodic reports. The base station may configure the UE with the CSI-RS resource set and CSI reports using RRC signaling.

[0130] The CSI-RS configuration may include, for example, one or more parameters indicating up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and control resource set (CORESET) if the downlink CSI-RS and CORESET are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside of a physical resource block (PRB) configured for CORESET. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and SS / PBCH block if the downlink CSI-RS and SS / PBCH block are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside of a PRB configured for the SS / PBCH block.

[0131] The downlink DMRS may be transmitted by a base station and may be used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontloaded DMRS symbols of the PDSCH. The DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, the DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, the DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. The wireless network may support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM). The DMRS position, DMRS pattern, and / or scrambling sequence may be the same or different. The base station may transmit the downlink DMRS and corresponding PDSCH using the same precoding matrix. The UE may use one or more downlink DMRS for coherent demodulation / channel estimation of the PDSCH.

[0132] In one embodiment, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0133] The PDSCH may include one or more layers. The UE may assume that at least one symbol with a DMRS is present on one or more layers of the PDSCH. Higher layers may configure up to three DMRS for the PDSCH.

[0134] The downlink PT-RS may be transmitted by the base station and may be used by the UE for phase noise compensation. Whether the downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by DCI. If configured, the dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters including at least the MCS. The NR network may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be restricted to the scheduled time / frequency period of the UE. The downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0135] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit the uplink DMRS on a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies similar to the range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to transmit on one or more symbols of the PUSCH and / or the PUCCH. The base station may semi-statically configure the UE with a number (e.g., a maximum number) of frontloaded DMRS symbols for the PUSCH and / or the PUCCH that the UE may use to schedule single-symbol DMRS and / or dual-symbol DMRS. An NR network may support a common DMRS structure for the downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS location, DMRS pattern, and / or scrambling sequence for the DMRS may be the same or different.

[0136] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on one or more layers of the PUSCH. In one embodiment, higher layers may configure up to three DMRSs for the PUSCH.

[0137] An uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not be present depending on the RRC configuration of the UE. The presence and / or pattern of the uplink PT-RS may be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)) that may be indicated by RRC signaling and / or DCI. If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters including at least the MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS may be restricted to the scheduled time / frequency period of the UE.

[0138] The SRS may be transmitted by the UE to the base station for channel condition estimation to support uplink channel dependent scheduling and / or link adaptation. The SRS transmitted by the UE may enable the base station to estimate uplink channel conditions at one or more frequencies. The base station scheduler may use the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The SRS resource set applicability may be configured by higher layer (e.g., RRC) parameters. For example, if the higher layer parameters indicate beam management, the SRS resources in one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodicity, aperiodicity, and / or the like) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources in the SRS resource set. An NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, which may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In one embodiment, at least one DCI format may be used for the UE to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In one embodiment, if the PUSCH and SRS are transmitted in the same slot, the UE may be configured to transmit the SRS after the transmission of the PUSCH and the corresponding uplink DMRS.

[0139] The base station may quasi-statistically configure the UE with one or more SRS configuration parameters indicating at least one of an SRS resource configuration identifier, a number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), a slot, minislot, and / or subframe level periodicity, an offset for periodic and / or aperiodic SRS resources, a number of OFDM symbols in the SRS resource, a starting OFDM symbol of the SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a periodic shift, and / or an SRS sequence ID.

[0140] The antenna ports are defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. When a first symbol and a second symbol are transmitted on the same antenna port, a receiver may infer a channel (e.g., fade gain, multipath delay, and / or the like) for carrying a second symbol on an antenna port from the channel for carrying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi-collocated (QCLed) if one or more large-scale characteristics of the channel on which the first symbol on the first antenna port is conveyed can be inferred from the channel on which the second symbol of the second antenna port is transmitted. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

[0141] In a channel using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurement based on a downlink reference signal (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform a downlink beam measurement procedure after an RRC connection is set up with the base station.

[0142] FIG. 11B illustrates an example of a channel state information reference signal (CSI-RS) mapped to the time and frequency domain. The squares illustrated in FIG. 11B may span resource blocks (RBs) within the bandwidth of a cell. The base station may transmit one or more RRC messages including a CSI-RS resource configuration parameter indicating one or more CSI-RS. One or more of the following parameters may be set by higher layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) location within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and radio frame periodicity), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-collocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0143] The three beams shown in FIG. 11B may be configured for a UE in a UE-specific configuration. Three beams are shown in FIG. 11B (Beam #1, Beam #2, and Beam #3), and more or less beams may be configured. Beam #1 may be assigned with CSI-RS 1101, which may be transmitted on one or more subcarriers in the RB of the first symbol. Beam #2 may be assigned with CSI-RS 1102, which may be transmitted on one or more subcarriers in the RB of the second symbol. Beam #3 may be assigned with CSI-RS 1103, which may be transmitted on one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station may transmit another CSI-RS associated with another UE's beam using other subcarriers (e.g., not used to transmit CSI-RS 1101) in the same RB. By using time domain multiplexing (TDM), the beam used for a UE may be configured such that the UE's beam uses symbols from the other UE's beam.

[0144] The CSI-RS (e.g., CSI-RS 1101, 1102, 1103) shown in FIG. 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, the UE may measure the reference signal received power (RSRP) of the configured CSI-RS resources. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In one embodiment, the base station may determine one or more transmission configuration indication (TCI) states including some reference signals based on the reported measurement results. In one embodiment, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In one embodiment, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE may determine a spatial domain filter of a transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam correspondence capability, the UE may perform an uplink beam selection procedure to determine a spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured for the UE by the base station. The base station may select and indicate an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

[0145] In a beam management procedure, the UE may evaluate (e.g., measure) channel quality of one or more beam pair links, including a transmit beam transmitted by the base station and a receive beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters including, for example, one or more beam identities (e.g., beam index, reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (RI).

[0146] FIG. 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements at a transmit (Tx) beam of a transmit receive point (TRP) (or multiple TRPs) to support selection of, for example, one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at a TRP may include a Tx beam sweep for a set of beams (shown as an ellipse rotating counterclockwise as shown by the dashed arrows in the top rows of P1 and P2). Beamforming at a UE may include a Rx beam sweep for a set of beams (shown as an ellipse rotating clockwise as shown by the dashed arrows in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements at a Tx beam of a TRP (shown as an ellipse rotating counterclockwise as shown by the dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller set of beams than used in procedure P1 or using narrower beams than used in procedure P1, which may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beams at the UE.

[0147] FIG. 12B shows examples of three uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used, for example, to enable the base station to perform measurements on the UE's Tx beams to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown as ellipses rotated clockwise as shown by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station may include, for example, a Rx beam sweep from a set of beams (shown as ellipses rotated counterclockwise as shown by dashed arrows in the top rows of U1 and U2). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or base station may implement procedure U2 using a smaller set of beams than used in procedure P1, or using narrower beams than used in procedure P1. This may be called beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0148] The UE may initiate a Beam Failure Recovery (BFR) procedure based on the detection of a beam failure. The UE may transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., has an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, a timer expires, and / or the like).

[0149] The UE may measure the quality of the beam-pair link using one or more reference signals (RSs), including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam-pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resources. The base station may indicate that the RS resources are quasi-co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resources and one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fade, and / or the like) from a transmission to the UE over the RS resources are similar or identical to the channel characteristics from a transmission to the UE over the channel.

[0150] The network (e.g., gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in RRC_IDLE state and / or a UE in RRC_INACTIVE state may initiate a random access procedure to request a connection setup to the network. The UE may initiate a random access procedure from the RRC_CONNECTED state. The UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no PUCCH resources available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). The UE may initiate a random access procedure to request one or more system information blocks (SIBs) (e.g., SIB2, SIB3, and / or other system information such as similar). The UE may initiate a random access procedure for a beam failure recovery request. The network may initiate a random access procedure to establish time alignment for handover and / or for SCell addition.

[0151] FIG. 13A shows a four-step contention-based random access procedure. Before the procedure begins, the base station may transmit a configuration message 1310 to the UE. FIG. 13A includes the transmission of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

[0152] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of general parameters (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated) for one or more random access procedures. The base station may broadcast or multicast the one or more RRC messages to the one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in RRC_CONNECTED and / or RRC_INACTIVE states). The UE may determine time-frequency resources and / or uplink transmit power for transmission of Msg1 1311 and / or Msg3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314.

[0153] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of Msg1 1311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunities and / or the number of preambles mapped to the SS / PBCH blocks.

[0154] The one or more RACH parameters provided in the configuration message 1310 may be used to determine the uplink transmission power of Msg1 1311 and / or Msg3 1313. For example, the one or more RACH parameters may indicate a reference power for the preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between the transmissions of Msg1 1311 and Msg3 1313, and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds for which the UE may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier).

[0155] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., Group A and / or Group B). The preamble group may include one or more preambles. The UE may determine the preamble group based on a path loss measurement and / or a size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select one or more reference signals and / or at least one preamble associated with the selected preamble group, for example, if an association between the one or more preambles and the at least one reference signal is configured by the RRC message.

[0156] The UE may determine the preamble based on one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or a size of Msg3 1313. As another example, the one or more RACH parameters may indicate one or more thresholds for determining a preamble format, a maximum number of preamble transmissions, and / or one or more preamble groups (e.g., Group A and Group B). The base station may configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) using the one or more RACH parameters. If an association is configured, the UE may determine a preamble to include in Msg1 1311 based on the association. Msg1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH occasion and one or more reference signals.

[0157] The UE may perform a preamble retransmission if no response is received after the preamble transmission. The UE may increase the uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a path loss measurement and / or a target received preamble power configured by the network. The UE may decide to retransmit the preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step of the preamble retransmission. The ramping step may be the amount of incremental increase of the uplink transmit power for the retransmission. If the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as the previous preamble transmission, the UE may ramp up the uplink transmit power. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that the random access procedure has completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (eg, preambleTransMax).

[0158] Msg2 1312 received by the UE may include an RAR. In some scenarios, Msg2 1312 may include multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 was received by the base station. Msg2 1312 may include a time alignment command that the UE may use to adjust the UE's transmission timing, a scheduling grant for the transmission of Msg3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may begin a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg2 1312. The UE may determine when to start the time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be within a common search space (e.g., Type1-PDCCH common search space) configured by the RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used in response to one or more events that initiate the random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity on which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on an OFDM symbol index, a slot index, a frequency domain index, and / or a UL carrier indicator of the PRACH opportunity. Examples of the RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0s≦t_id<14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier). The UE may transmit Msg3 1313 in response to successful reception of Msg2 1312 (e.g., using resources identified in Msg2 1312). Msg3 1313 may be used for contention resolution, for example, in the contention-based random access procedure shown in FIG. 13A. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide the UE with a corresponding RAR. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Contention resolution (e.g., use of Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier) ​​in Msg3 1313.

[0159] Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If a TC-RNTI is included in Msg3 1313 (e.g., the UE is in an RRC_IDLE state or is otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU sent (e.g., transmitted) in Msg3 1313 or otherwise includes a corresponding UE contention resolution identity MAC CE, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was successfully completed.

[0160] The UE may be configured with a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) may be supported on the uplink carrier. For example, the base station may configure the UE with two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier. For random access in a cell configured with the SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. The UE may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313) in one or more instances. For example, the UE may determine and / or switch uplink carriers for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (eg, listen-before-talk).

[0161] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, the base station may transmit a configuration message 1320 to the UE before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. FIG. 13B includes the transmission of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312, respectively, illustrated in FIG. 13A. As can be seen from FIG. 13A and FIG. 13B, the contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0162] The contention-free random access procedure shown in Figure 13B may be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. For example, the base station may indicate or assign to the UE the preamble to be used for Msg1 1321. The UE may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0163] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure shown in FIG. 13B, the UE may determine that the random access procedure is successfully completed after or in response to transmitting Msg1 1321 and receiving the corresponding Msg2 1322. The UE may determine that the random access procedure is successfully completed, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE may determine that the random access procedure is successfully completed, for example, if the UE receives an RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or if the RAR includes a MAC sub-PDU including a preamble identifier. The UE may determine the response as an indication of confirmation to the SI request.

[0164] Figure 13C shows another two-step random access procedure. Similar to the random access procedure shown in Figures 13A and 13B, the base station can transmit a configuration message 1330 to the UE before the procedure begins. The configuration message 1330 can be similar in some respects to the configuration message 1310 and / or the configuration message 1320. Figure 13C includes the transmission of two messages, namely, Msg A 1331 and Msg B 1332.

[0165] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may include content similar and / or equivalent to the content of Msg3 1313 shown in FIG. 13A. The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar and / or equivalent to the content of Msg2 1312 (e.g., RAR) shown in FIG. 13A and 13B and / or the content of Msg4 1314 shown in FIG. 13A.

[0166] The UE may initiate the two-step random access procedure of FIG. 13C for licensed and / or unlicensed spectrum. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors may be the radio access technology in use (e.g., LTE, NR, and / or the like), whether the UE has a valid TA, the cell size, the RRC state of the UE, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

[0167] The UE may determine radio resources and / or uplink transmit power for the preamble 1341 and / or the transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate a modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or the transport block 1342. The time-frequency resources for transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0168] The transport block 1342 may include data (e.g., delay sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a UE identifier for contention resolution, and / or an RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE and / or the UE identifier in Msg B 1332 matches the UE identifier (e.g., transport block 1342) in Msg A 1331.

[0169] The UE and the base station may exchange control signaling, which may be referred to as L1 / L2 control signaling, and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0170] The downlink control signaling may include downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or any other suitable signaling. A UE may receive the downlink control signaling in a payload transmitted by a base station on a Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a Group Common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0171] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. If the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may include a modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a Radio Network Temporary Identifier (RNTI), which is a 16-bit value.

[0172] DCIs may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of a dynamic schedule and / or a random access of a PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Encodings of other RNTIs configured in the UE by the base station include Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0173] Depending on the purpose and / or content of the DCI, the base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 may be used for scheduling the PUSCH in the cell. DCI format 0_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 0_1 ​​may be used for scheduling the PUSCH in the cell (e.g., has a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling the PDSCH in the cell. DCI format 1_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 1_1 may be used for scheduling the PDSCH in the cell (e.g., has a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of UEs. DCI format 2_1 may be used to inform a group of UEs of the physical resource blocks and / or OFDM symbols that the UE assumes are not intended for transmission to the UE. DCI format 2_2 may be used for transmission of transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

[0174] After scrambling the DCI with the RNTI, the base station may process the DCI using channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. Based on the payload size of the DCI and / or the coverage of the base station, the base station may transmit the DCI via the PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (called an aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may include a number of resource element groups (REGs) (e.g., 6). A REG may include a resource block within an OFDM symbol. The mapping of the coded and modulated DCI onto resource elements may be based on a mapping of CCEs and REGs (e.g., CCE to REG mapping).

[0175] FIG. 14A illustrates an example of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which a UE attempts to decode DCI using one or more search spaces. A base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at a first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in a slot. A fourth CORESET 1404 occurs at a seventh symbol of a slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0176] FIG. 14B illustrates an example of CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be interleaved (e.g., for the purpose of providing frequency diversity) or non-interleaved (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by an RRC configuration. A CORESET may be configured with an antenna port quasi-co-location (QCL) parameter. The QCL parameter of an antenna port may indicate the QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0177] The base station may send an RRC message to the UE including configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate the number of PDCCH candidates monitored per aggregation level, a PDCCH monitoring periodicity and a PDCCH monitoring pattern, one or more DCI formats monitored by the UE, and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0178] As shown in FIG. 14B, the UE may determine time-frequency resources of the CORESET based on the RRC message. The UE may determine CCE-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine the number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE may monitor a set of PDCCH candidates according to configuration parameters of the search space sets. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to a monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., number of CCEs in a common search space, number of PDCCH candidates, and / or number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. The decoding may be referred to as blind-blind-combined-blind decoding. The UE may determine a valid DCI for the UE in response to a CRC check (e.g., scrambling bits to CRC parity bits of the DCI matching the RNTI value). The UE may process information included in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, and / or the like).

[0179] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a hybrid automatic repeat request (HARQ) acknowledgement for the received DL-SCH transport block. The UE may transmit the HARQ acknowledgement after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating a channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. The base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for the downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available to be transmitted to the base station. The UE may transmit the UCI (e.g., a HARQ acknowledgement (HARQ-ACK), a CSI report, an SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). A UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0180] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or less bits. The UE may transmit UCI on PUCCH resources using PUCCH format 0 if the transmission is more than one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy between 4-14 OFDM symbols and may include two or less bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is more than one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy between 4 and 14 OFDM symbols and may include more than 2 bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy between 4 and 14 OFDM symbols and may include more than 2 bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code.

[0181] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE, for example, using an RRC message. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. A PUCCH resource set may be configured with a PUCCH resource set index, multiple PUCCH resources with PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, the UE may select one of the multiple PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is less than or equal to two, the UE may select a first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than 2 and less than or equal to the first configuration value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configuration value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

[0182] After determining a PUCCH resource set from the multiple PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., DCI format 1_0 or DCI format 1_1) received on a PDCCH. The 3-bit PUCCH resource indicator of the DCI may indicate one of the eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0183] FIG. 15 illustrates an example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the disclosure. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1A, the mobile communication network 150 shown in FIG. 1B, or other communication network. Only one wireless device 1502 and one base station 1504 are shown in FIG. 15. However, it will be understood that the mobile communication network may include multiple UEs and / or multiple base stations having the same or similar configuration as that shown in FIG. 15.

[0184] The base station 1504 may connect the wireless device 1502 to a core network (not shown) via wireless communication over an air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. The downlink transmission may be separated from the uplink transmission using FDD, TDD, and / or some combination of the two duplexing techniques.

[0185] In the downlink, data transmitted from the base station 1504 to the wireless device 1502 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data transmitted from the wireless device 1502 to the base station 1504 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, with respect to Figures 2A, 2B, 3, and 4A, the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer. Layer 3 may include, for example, with respect to Figure 2B, the RRC layer.

[0186] After being processed by the processing system 1508, data to be transmitted to the wireless device 1502 may be provided to a transmit processing system 1510 of the base station 1504. Similarly, after being processed by the processing system 1518, data to be transmitted to the base station 1504 may be provided to a transmit processing system 1520 of the wireless device 1502. The transmit processing system 1510 and the transmit processing system 1520 may implement Layer 1 OSI functions. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple input multiple output (MIMO) or multi-antenna processing, and / or the like.

[0187] In the base station 1504, a receive processing system 1512 may receive uplink transmissions from the wireless device 1502. In the wireless device 1502, a receive processing system 1522 may receive downlink transmissions from the base station 1504. The receive processing system 1512 and the receive processing system 1522 may implement the OSI functions of Layer 1. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

[0188] 15, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to implement one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0189] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518 to perform one or more functions discussed in the present application. Although not shown in FIG. 15 , transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that may be executed to perform one or more of their respective functions.

[0190] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or the one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0191] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data and / or provide user output data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0192] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of: scrambling, modulating scramble bits to generate complex-valued symbols, mapping complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding the complex-valued symbols, mapping the precoded complex-valued symbols onto resource elements, generating complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or the like. In one example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, if transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated according to FIG. 16A. These functions are illustrated as examples, and it is anticipated that other mechanisms may be implemented in various embodiments.

[0193] 16B shows an example structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for an antenna port. Filtering may be used before transmission.

[0194] 16C illustrates an exemplary structure of a downlink transmission. A baseband signal representing a physical downlink channel can perform one or more functions. The one or more functions can include scrambling of coded bits in a codeword to be transmitted on the physical channel, modulation of the scrambled bits to generate complex-valued modulation symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, precoding of the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping of the complex-valued modulation symbols of the antenna ports to resource elements, generation of a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are illustrated as examples, and it is anticipated that other mechanisms can be implemented in various embodiments.

[0195] 16D shows another example structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be used before transmission.

[0196] The wireless device may receive one or more messages (e.g., RRC messages) from a base station including configuration parameters for multiple cells (e.g., primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations for dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include physical, MAC, RLC, PCDP, SDAP, RRC layer parameters for configuring the wireless device. For example, the configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may include parameters indicating values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0197] A timer may begin execution when started and continue to execute until stopped or expires. A timer may be started if not running or restarted if running. A timer may be associated with a value (e.g., a timer may be started or restarted from a value, or may be started from zero and expire when the value is reached). A timer's duration may not be updated until the timer is stopped or expires (e.g., by BWP switching). A timer may be used to measure a period / window of a process. When this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of multiple ways to implement a timer may be used to measure the period / window of a procedure. For example, a random access response window timer may be used to measure a window time for receiving a random access response. In one embodiment, the time difference between two timestamps may be used instead of the start and expiration of the random access response window timer. When a timer is restarted, the process for measuring the time window may be restarted. Other example implementations may be provided for restarting the measurement of the time window.

[0198] The UE may receive an RRC release message including a suspension configuration parameter (or a suspension indication), where the suspension configuration parameter includes a resume identity and an NCC value. Based on the suspension configuration parameter, the UE may suspend the RRC connection. Based on the RRC release message, the UE may transition from an RRC connected state to either an RRC inactive state or an RRC idle state. Based on the RRC connection suspended in an RRC idle state, the UE is in an RRC idle state with a suspended RRC connection.

[0199] The RRC connection establishment may include the establishment of a signaling radio bearer 1 (SRB1). The base station may complete the RRC connection establishment before completing the S1 connection establishment (e.g., before receiving UE context information from a core network entity (e.g., AMF)). Access Stratum (AS) security is not activated during the initial stage of the RRC connection. During the initial stage of the RRC connection, the base station may configure the UE to perform measurement reporting. The UE may send a corresponding measurement report upon successful AS security activation. The UE may receive or accept a handover message (e.g., handover command) when AS security is activated.

[0200] After starting the initial (AS) security activation procedure, the base station may initiate the establishment of SRB2 and DRB. For example, the base station may initiate the establishment of SRB2 and DRB before receiving a confirmation of the initial security activation from the UE. The base station may apply cryptographic and integrity protection to the RRC (connection) reconfiguration message, which is used to establish the SRB2 and DRB. The base station may release the RRC connection based on the initial security activation and / or radio bearer establishment failure. For example, the security activation and DRB establishment may be triggered by a joint S1 procedure, which may not support partial success. For SRB2 and DRB, (AS) security may be activated from the beginning. For example, the base station may not be able to establish these bearers before activating security.

[0201] The UE-RRC layer may initiate an RRC connection establishment procedure, an RRC connection resumption procedure, or an RRC connection re-establishment procedure. Based on initiation of the RRC connection establishment procedure or the RRC connection resumption procedure, the UE may perform one or more procedures, where the one or more procedures include at least one of: performing a unified access control procedure (e.g., an access barring check) for the access attempt of the RRC establishment / resumption procedure at the serving cell; applying default configuration parameters and configurations / parameters provided by SIB1 (e.g., applying the default configurations and configurations / parameters provided by SIB1 based on the access attempt being granted); e.g., performing transmission of a random access preamble to the serving cell based on the access attempt being granted; transmitting an RRC request message to the serving cell (e.g., transmitting an RRC request message to the serving cell based on determining that reception of the random access response is successful); starting a timer based on the transmission of the RRC request message; receiving an RRC response message or an RRC rejection message from the serving cell (e.g., in response to the RRC request message); or transmitting an RRC completion message (e.g., in response to receiving the RRC response message, transmitting an RRC completion message). For the RRC connection re-establishment procedure, the UE for the access attempt of the RRC re-establishment procedure may not perform a unified access procedure (eg, access barring check).

[0202] Based on the initiation of the RRC connection re-establishment procedure, the UE may stop one or more prohibition timers T309 for all access categories if one or more prohibition timers T309 are running. Based on stopping the one or more prohibition timers T309, the UE may determine to prohibit all access categories from being relaxed. The UE may perform an RRC connection re-establishment procedure based on prohibiting all access categories from being relaxed. For example, the UE may send an RRC re-establishment request without prohibition based on prohibiting all access categories from being relaxed.

[0203] To initiate an RRC connection establishment / resumption / re-establishment procedure, the UE-RRC layer may use the parameters in the received SIB1. The UE-RRC layer may use the L1 parameter values ​​and the time alignment timer in SIB1. The UE-RRC layer may perform a unified access control procedure using the UAC barring information in SIB1. Based on the unified access control procedure, the UE-RRC layer may determine whether the access attempts of those RRC procedures are barred or granted. Based on determining that the access attempts are allowed, the UE-RRC layer may decide to send an RRC request message to the base station. The UE-NAS layer may or may not provide the S-TMSI as the UE identity. The UE-RRC layer may set the UE identity in the RRC request message.

[0204] For the RRC Setup Request message, the UE in RRC idle state may initiate an RRC connection establishment procedure. Based on the initiation of the RRC connection establishment procedure, the UE-RRC layer in RRC idle state may set the UE identity to the S-TMSI if the UE-NAS layer provides the S-TMSI. Otherwise, the UE-RRC layer in RRC idle state may draw a 39-bit random value and set the UE identity to the random value.

[0205] In the RRC Resume Request message, a UE in RRC inactive or RRC idle state with a suspended RRC connection may initiate an RRC connection resume procedure. The UE may initiate an RRC connection procedure to resume the (suspended) RRC connection in an RRC inactive or idle state, or may perform / start UP small data transmission. Based on the initiation of the RRC connection resume procedure, the UE may select an access category based on a trigger condition of the RRC connection resume procedure, and perform a unified access control procedure based on the access category. Based on the unified access control procedure, the UE may consider the access attempt of the RRC connection resume procedure as granted. Based on considering the access attempt as granted, the UE may apply default L1 parameter values ​​specified in the corresponding physical layer specification, except for parameters whose values ​​are provided in SIB1, apply a default SRB1 configuration, apply a CCCH configuration, apply a common time alignment timer included in SIB1, apply a default MAC cell group configuration, start timer T319, and start transmitting an RRC Resume Request message.

[0206] Based on the initiation of the transmission of the RRC Resume Request message, the UE may restore the stored configuration parameters and the stored security keys from the (stored) UE inactive AS context, except for the master cell group configuration parameters, the MR-DC related configuration parameters (e.g., secondary cell group configuration parameters), and the PDCP configuration parameters. The configuration parameters may include at least one of the C-RNTI used in the source PCell, the global cell identity and the physical cell identity of the source PCell, and all other parameters configured, except for those in the reconfiguration with synchronization and the serving cell configuration common parameters in the SIB. The current (restored) K associated with the stored NCC value. gNB Or based on the next hop (NH) parameter, the UE determines the next hop gNBBased on the base station's new key, the UE may derive new keys for security keys (e.g., K and K , respectively) for integrity protection and ciphering of the RRC signaling. RRCenc and K. RRCint ), and security keys for integrity protection and encryption of user plane data (e.g., K UPint and K. UPenc ) can be derived. The constructed algorithm and K RRCint and K. UPint Based on the configured algorithm, and K, the UE may configure the lower layers (e.g., the PDCP layer) to apply integrity protection to all radio bearers except SRB0. RRCenc and K. UPenc Based on this, the UE may configure the lower layers (eg, the PDCP layer) to apply ciphering to all radio bearers except SRB0.

[0207] Based on the security key / parameter, the UE-RRC layer in RRC inactive or idle state may set the resume MAC-I value to the 16 least significant bits of the MAC-I calculated based on the variable resume MAC input, the security key of the integrity protection for the RRC layer in the UE inactive AS context, the previously configured integrity protection algorithm, and other security parameters (e.g., count, bearer, and direction). The variable resume MAC input may include at least one of the physical cell identity of the source cell, the C-RNTI of the source cell, and the cell identity of the target cell (e.g., selected cell), where the cell identity is the cell identity in the system information block (e.g., SIB1) of the target cell (e.g., selected cell). The UE-RRC layer in RRC inactive or idle state may re-establish a PDCP entity for one or more bearers. The UE-RRC layer may resume one or more bearers. For example, based on the resumption of the RRC connection, the UE-RRC layer may resume SRB1. Based on the execution of the UP small data transmission, the UE-RRC layer may resume one or more SRBs and DRBs. The UE may configure the content of an RRC resume request message. The RRC resume request message may include at least one of a resume identity, a resume MAC-I, or a resume cause. The resume cause may include at least one of an emergency, a high priority access, an mt access, a mo signaling, a mo data, a mo voice call, a mo sms, a ran update, a mps priority access, or a mcs priority access.

[0208] For the RRC re-establishment request message, the UE in the RRC connected state may initiate an RRC connection re-establishment procedure. Based on the initiation of the RRC connection re-establishment procedure, the UE-RRC layer in the RRC connected state may include the physical cell identity and short MAC-I of the source PCell in the RRC re-establishment message. The UE-RRC layer in the RRC connected state may set the short MAC-I to the 16 least significant bits of the MAC-I calculated based on a variable short MAC input, a security key of the integrity protection for the RRC layer, and the integrity protection algorithm used on the source PCell or PCell where the re-establishment was triggered, and other security parameters (e.g., count, bearer, and direction). The variable short MAC input may include at least one of the physical cell identity of the source PCell, the C-RNTI of the source PCell, and the cell identity of the target cell (e.g., selected cell), where the cell identity is the cell identity of the system information block (e.g., SIB1) of the target cell (e.g., selected cell). The UE-RRC layer in RRC CONNECTED state can re-establish the PDCP and RLC entities for SRB1 and apply default SRB1 configuration parameters for SRB1. The UE-RRC layer in RRC CONNECTED state can suspend integrity protection and ciphering for SRB1 and configure lower layers (e.g., the PDCP layer) to resume SRB1.

[0209] The UE-RRC layer may send an RRC request message to a lower layer (e.g., a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer) for transmission, where the RRC request message may be an RRC setup request message, an RRC resume request message, or an RRC re-establishment message.

[0210] The UE-RRC layer may receive an RRC SETUP message in response to the RRC RESUME REQUEST message or the RRC RE-ESTABLISH REQUEST message. Based on the RRC SETUP message, the UE-RRC layer may discard the stored AS context, the suspension configuration parameters, and the current AS security context. The UE-RRC layer may release radio resources for all established RBs except SRB0, including the release of the RLC entity, the associated PDCP entity, and the SDAP. The UE-RRC layer may release the RRC configurations except the default L1 parameter values, the default MAC cell group configuration, and the CCCH configuration. The UE-RRC layer may indicate a fallback of the RRC connection to the upper layer (e.g., the NAS layer). If the timer T380 is running where it is a periodic RNA update timer, the UE-RRC layer may stop the timer T380.

[0211] The UE-RRC layer may receive an RRC Setup message in response to an RRC Setup Request message, an RRC Resume Request message, or an RRC Re-establishment Request message. The RRC Setup message may include cell group configuration parameters and radio bearer configuration parameters. The radio bearer configuration parameters may include at least one of signaling bearer configuration parameters, data radio bearer configuration parameters, and / or security configuration parameters. The security configuration parameters may include security algorithm configuration parameters and a key with an indication of whether the radio bearer configuration parameters use a master key or a secondary key. The signaling radio bearer configuration parameters may include one or more signaling radio bearer configuration parameters. Each signaling radio configuration parameter may include at least one of an SRB identity, a PDCP configuration parameter, a re-establish PDCP indication, and / or a discard PDCP indication. The data radio bearer configuration parameters may include one or more data radio bearer configuration parameters. Each data radio configuration parameter may include at least one of a drb identity, a PDCP configuration parameter, an SDAP configuration parameter, a re-establishment PDCP indication, and / or a recovery PDCP indication. The radio bearer configuration in the RRC setup message may include a signaling radio configuration parameter of SIB1. Based on the RRC setup message, the UE-RRC layer may establish an SRB1. Based on the RRC setup message, the UE-RRC layer may perform a cell group configuration or a radio bearer configuration. The UE-RRC layer may stop an inhibit timer and a wait timer for the cell that transmits the RRC setup message. Based on receiving the RRC setup message, the UE-RRC layer may perform one or more of transitioning to an RRC connected state, stopping a cell reselection procedure, considering the current cell where the UE transmitted the RRC setup message to be a PCell, or / and transmitting an RRC setup complete message.

[0212] The UE-RRC layer may receive an RRC Resume message in response to the RRC Resume Request message. Based on the RRC Resume message, the UE-RRC layer may destroy the UE inactive AS context and release the suspension configuration parameters, except for the RAN notification area information. Based on the configuration parameters of the RRC Resume message, the UE-RRC layer may perform cell group configuration, radio bearer configuration, security key update procedure, and measurement configuration procedure. Based on receiving the RRC Resume message, the UE-RRC layer may perform one or more of the following: indicating to upper layers (e.g., the NAS layer) that the suspended RRC connection has been resumed, resuming SRB2, all DRBs and measurements, entering an RRC Connected state, stopping the cell (re)selection procedure, considering the current cell sending the RRC Resume message to be the PCell, and / or sending an RRC Resume Complete message by setting the content of the RRC Resume Complete message.

[0213] A UE-RRC layer in an RRC inactive or idle state may receive an RRC reject message in response to an RRC setup request message or an RRC resume request message. The RRC reject message may include a wait timer. Based on the wait timer, the UE-RRC layer may set a timer value to the wait timer and start timer T302. Based on the RRC reject message, the UE-RRC layer may inform upper layers (e.g., the UE-NAS layer) about the failure of the RRC connection setup or RRC connection resume. The UE-RRC layer may reset the MAC and release the default MAC cell group configuration. Based on the RRC reject received in response to a request from the upper layer, the UE-RRC layer may inform upper layers (e.g., the NAS layer) that the access barring is applicable to all access categories except categories "0" and "2".

[0214] A UE-RRC layer in an RRC inactive or idle state may receive an RRC reject message in response to an RRC resume resumption request message. Based on the RRC reject message, the UE-RRC layer may discard the current security keys. The UE-RRC layer may set the pending rna update value to true if the resume was triggered by an RNA update.

[0215] A UE-RRC layer in an RRC inactive or idle state may perform a cell (re)selection procedure while performing an RRC procedure to establish an RRC connection. Based on cell selection or cell reselection, the UE-RRC layer may change the cell on the camped UE and stop the RRC procedure. The UE-RRC layer may inform upper layers (e.g., the NAS layer) about the failure of the RRC procedure.

[0216] A UE in an RRC idle state or an RRC inactive state can perform one of two procedures, such as initial cell selection and cell selection, by utilizing the stored information. If the UE does not have cell information stored for the selected PLMN, the UE may perform initial cell selection. Otherwise, the UE may perform cell selection by utilizing the stored information. For initial cell selection, the UE may scan all RF channels in the NR band according to its capabilities to find a suitable cell. Based on the results of the scan, the UE may search for the strongest cell on each frequency. The UE may select a cell that is a suitable cell. For cell selection by utilizing the stored information, the UE may request information of the stored frequency and, optionally, information about cell parameters from previously received measurement control information elements or previously detected cells. Based on the stored information, the UE may search for a suitable cell and select the suitable cell if the UE finds a suitable cell. If the UE does not find a suitable cell, the UE may perform initial cell selection.

[0217] The base station may configure cell selection criteria for cell selection. The UE may seek to identify a suitable cell for cell selection. A suitable cell is a cell on which the UE can camp to obtain normal service. A suitable cell is a cell that meets the following conditions: (1) the measured cell attributes meet the cell selection criteria, (2) the cell PLMN is the selected PLMN, registered or equivalent PLMN, (3) the cell is not barred or reserved, and (4) the cell is not part of a tracking area that is in the list of "barred tracking areas for roaming". The RRC layer in the UE may inform the NAS layer in the UE of the cell selection and reselection results based on changes in the received system information related to the NAS. For example, the cell selection and reselection results may be the cell identity, the tracking area code, and the PLMN identity.

[0218] A UE in an RRC connected state may detect a failure of connection with a base station. A UE in an RRC connected state may activate AS security with the base station before detecting the failure. The failure includes at least one of the following: Radio Link Failure (RLF), reconfiguration with synchronization failure, mobility failure from new radio (NR), integrity check failure indication from lower layers (e.g., PDCP layer) for signaling radio bearer 1 (SRB1) or signaling radio bearer 2 (SRB2), or RRC connection reconfiguration failure.

[0219] The radio link failure may be a radio link failure of the primary cell of the base station. The base station may send a reconfiguration with synchronization in an RRC message to the UE in the RRC connected state. The reconfiguration with synchronization may include a reconfiguration timer (e.g., T304). Based on receiving the reconfiguration synchronization, the UE may start a reconfiguration timer and perform a reconfiguration with synchronization (e.g., handover). Based on the expiration of the reconfiguration timer, the UE determines a reconfiguration synchronization failure. The base station may send a mobility from NR command message to the UE in the RRC connected state. Based on receiving the mobility from NR command message, the UE may perform a handover from NR to a cell using another RAT (e.g., E-UTRA). The UE may determine a mobility from NR failure based on at least one of the following conditions being met: If the UE cannot establish a connection to the target radio access technology, or if the UE cannot comply with any part of the configuration included in the mobility from NR command message, or if there is a protocol error in the inter-RAT information included in the mobility from NR message.

[0220] Upon detecting the failure, the UE in the RRC connected state may initiate an RRC connection re-establishment procedure. Upon initiating the RRC connection re-establishment procedure, the UE may start timer T311, stop all radio bearers except SRB0, and reset the MAC (layer). Upon initiating the RRC connection re-establishment procedure, the UE in the RRC connected state may release the MCG SCell, and release the special cell (SpCell) configuration parameters and the multi-radio dual connectivity (MR-DC) related configuration parameters. For example, upon initiating the RRC connection re-establishment procedure, the UE may release the master cell group configuration parameters.

[0221] Based on the initiation of the RRC connection re-establishment procedure, the UE in the RRC connected state may perform a cell selection procedure. Based on the cell selection procedure, the UE may select a cell. Based on the selection of a suitable cell, the UE in the RRC connected state may stop timer 311 and start timer T301. Based on the selection of a suitable cell, the UE in the RRC connected state may stop the prohibition timer T390 for all access categories. Based on the stop of the prohibition timer T390, the UE in the RRC connected state may consider that the prohibition for all access categories is relaxed for the cell. Based on the selection of the cell, the UE in the RRC connected state may apply default L1 parameter values ​​except for the parameters provided in SIB1, apply the default MAC cell group configuration, apply the CCCH configuration, apply the timer alignment timer in SIB1, and start transmitting an RRC re-establishment request message. Based on the initiation of transmission of the RRC re-establishment request message, the UE in the RRC connected state (RRC layer) may re-establish PDCP for SRB1, re-establish RLC for SRB1, apply the default SRB configuration for SRB1, configure the lower layer (PDCP layer) to stop integrity protection and ciphering for SRB1, resume SRB1, and send an SRC re-establishment request message to the lower layer (PDCP layer) for transmission. The RRC re-establishment request message may include at least one of the C-RNTI used in the source PCell, the physical cell identity (PCI) of the source PCell, the short MAC-I, or a re-establishment cause. The re-establishment cause may include at least one of a reconfiguration failure, a handover failure, or other failure.

[0222] The UE in the RRC connected state may stop the timer T301 based on receiving an RRC response message in response to the RRC re-establishment request message. The RRC response message may include at least one of an RRC re-establishment message, an RRC setup message, or an RRC re-establishment rejection message. The UE in the RRC connected state may stop the timer T301 when the selected cell becomes unsuitable.

[0223] Based on the cell selection procedure triggered by initiating the RRC connection re-establishment procedure, the UE in the RRC connected state can select an inter-RAT cell. Based on the selection of the inter-RAT cell, the UE in the RRC connected state (UE-AS layer) can transition to the RRC IDLE state and provide a release cause "RRC connection failure" to the upper layer of the UE (UE-NAS layer).

[0224] Upon expiration of T311 or T301, the UE (UE-AS layer) may transition to an RRC idle state and provide a release cause of "RRC connection failure" to upper layers of the UE (UE-NAS layer).

[0225] Based on receiving the release cause "RRC connection failure", if the UE in RRC idle state has no signaling pending and no user data pending, the UE (UE-NAS layer) may perform a NAS signaling connection restoration procedure. Based on performing the NAS signaling connection restoration procedure, the UE in RRC idle state may initiate a registration procedure by sending a registration request message to the AMF.

[0226] Based on receiving the release cause "RRC connection failure", the UE in RRC idle state (UE-NAS layer) can perform a service request procedure by sending a service request message to the AMF when the UE has signaling pending or user data pending.

[0227] Based on receiving the RRC re-establishment request message, the target base station may check whether the UE context of the UE is available locally. Based on the UE context not being available locally, the target base station may perform an acquire UE context procedure by sending an acquire UE context request message to the source base station (last serving base station) of the UE.

[0228] In the RRC connection re-establishment procedure, the acquire UE context request message may include at least one of a UE context ID, an integrity protection parameter, or a new cell identifier. The UE context ID may include at least one of a C-RNTI that includes the RRC re-establishment request message, and a PCI of the source PCell (last serving PCell). The integrity protection parameter of the RRC re-establishment procedure may be a short MAC-I. The new cell identifier may be an identifier of the target cell, where the target cell is the cell for which the RRC connection is requested to be re-established. The new cell identifier is a cell identity in a system information block (e.g., SIB1) of the target cell (e.g., the selected cell).

[0229] In the RRC connection re-establishment procedure, based on receiving the acquire UE context request message, the source base station can check the acquire UE context request message. If the source base station can identify the UE context by the UE context ID and successfully verify the UE by the integrity protection included in the acquire UE context request message, and decide to provide the UE context to the target base station, the source base station can respond to the target base station with an acquire UE context response message. If the source base station cannot identify the UE context by the UE context ID or the integrity protection included in the acquire UE context request message is not valid, the source base station can respond to the target base station with an acquire UE context failure message.

[0230] In the RRC connection re-establishment procedure, the get UE context response message may include at least one of the following: Xn Application Protocol (XnAP) ID of the target base station, XnAP ID of the source base station, Global Unique AMF Identifier (GUAMI), or UE context information (e.g., get UE context information UE context response). The UE context information may include at least one of the following: NG-C UE-related signaling criteria, UE security capability, AS security information, UE aggregated maximum bit rate, PDU sessions to be set up list, RRC context, mobility constraint list, or RAT / mobility selection priority index. The NG-C UE-related signaling criteria may be an NG application protocol ID assigned in the AMF of the UE on the NG-C connection with the source base station. The AS security information may be the ... gNBThe PDU session to be set up in the list may include a security key and a number of next hop chains (NCC) value. The PDU session to be set up in the list may include PDU session resource related information used in the UE context of the source base station. The PDU session resource related information may include a PDU session ID, a PDU session resource aggregation maximum bit rate, a security indication, a PDU session type, or a QoS flow to be set up in the list. The security indication may include a user plane integrity protection indication and a confidentiality protection indication, which indicate a requirement of user plane (UP) integrity protection and encryption for the corresponding PDU session, respectively. The security indication may also include at least one of an indication of whether UP integrity protection is applied to the PDU session, an indication of whether UP encryption is applied to the PDU session, and a maximum integrity protection data rate value per UE for the integrity protected DRB (uplink and downlink). The PDU session type may indicate at least one of Internet Protocol version 4 (IPv4), IPv6, IPv4v6, Ethernet, or unstructured. The QoS flows set up in the list may include at least one of a QoS flow identifier, a QoS flow level QoS parameter (QoS parameter that applies to the QoS flow), or a bearer identity.

[0231] In the RRC connection re-establishment procedure, the acquire UE context failure message may include at least the XnAP ID and a cause value of the target base station.

[0232] In the RRC connection re-establishment procedure, based on receiving the acquire UE context response message, the target base station may send an RRC re-establishment message to the UE. The RRC re-establishment message may include at least a network hop chain number (NCC) value.

[0233] Upon receiving the RRC re-establishment message, the UE determines the current K gNBor based on at least one of the next hop (NH) parameters, the base station (K gNB Based on the base station's new security key and the previously configured integrity protection algorithm, the UE may derive a new security key for the RRC signaling (K RRCint ) and the security key for protecting the integrity of the user plane (UP) data (K UPint ) can be derived. Based on the base station's new security key and the previously configured encryption algorithm, the UE can derive a security key for integrity protection of the RRC signaling (K RRCenc ) and the security key for encryption of User Plane (UP) data (K UPenc ) can be used to derive a security key for encrypting K RRCint Based on the previously configured integrity protection algorithm and K, the UE may verify the integrity protection of the RRC re-establishment message. Based on the verification failure, the UE (UE-AS layer) may transition to the RRC IDLE state and provide a release cause of "RRC connection failure" to the upper layer of the UE (UE-NAS layer). Based on the success of the verification, the UE may verify the integrity protection of the RRC re-establishment message based on the previously configured integrity protection algorithm and K. RRCint and configures the SRB1 to resume integrity protection based on the previously configured encryption algorithm and K RRCenc The UE may be configured to resume ciphering of SRB1 based on the received SRB_RESET_CONFIGURATION_TIME. The UE may send an RRC re-establishment complete message to the target base station.

[0234] Based on receiving the acquire UE context failure message, the target base station may send an RRC release message to the UE. For example, based on the acquire UE context failure message including an RRC release message, the target base station may send an RRC release message to the UE. Based on receiving the acquire UE context failure message, the target base station may send an RRC setup message or an RRC reject message. Based on receiving the acquire UE context failure message, the target base station may not send a response message to the UE.

[0235] FIG. 17 illustrates an example of an RRC connection re-establishment procedure. A UE in an RRC connected state may transmit and receive data to and from a first base station (e.g., a source base station) via cell 1, where cell 1 is a primary cell (PCell) of the first base station. The UE may detect a failure of a connection with the first base station. Based on the failure, the UE may initiate an RRC re-establishment procedure. Based on the initiation of the RRC connection re-establishment procedure, the UE may start timer T311, stop all radio bearers except SRB0, and / or reset the MAC (layer). Based on the initiation of the RRC connection re-establishment procedure, the UE may release the MCG SCell, release the special cell (SpCell) configuration parameters and the multi-radio dual connectivity (MR-DC) related configuration parameters. Based on the initiation of the RRC connection re-establishment procedure, the UE may perform a cell selection procedure. Based on the cell selection procedure, the UE may select cell 2 of a second base station (e.g., a target base station), where cell 2 is a suitable cell. Based on the selection of the suitable cell, the UE may stop timer T311 and start timer T301. Based on the selection of the appropriate cell, the UE may stop one or more prohibition timers T309(s) for all access categories if one or more prohibition timers T309(s) are running. Based on stopping one or more prohibition timers T309(s), the UE may consider that the prohibition for all access categories is relaxed for the cell. Based on the selection of the cell, the UE may apply default L1 parameter values ​​except for parameters provided in SIB1, apply default MAC cell group configuration, apply CCCH configuration, apply timer alignment timer in SIB1, and start transmitting an RRC re-establishment request message. The RRC re-establishment message may include at least one of a C-RNTI used in the source PCell (e.g., cell 1), a physical cell identity (PCI) of the source PCell, a short MAC-I, or a re-establishment cause.Based on initiating the transmission of the RRC re-establishment request message, the UE (RRC layer) may re-establish PDCP for SRB1, re-establish RLC for SRB1, apply a default SRB configuration for SRB1, configure the lower layer (PDCP layer) to stop integrity protection and ciphering for SRB1, resume SRB1, and send an SRC re-establishment request message to the lower layer (PDCP layer) for transmission. Based on receiving the RRC re-establishment request message, the UE may send an RRC re-establishment request message to the second base station via cell 2. Based on receiving the RRC re-establishment request message, the second base station may check whether the UE context of the UE is locally available. Based on the UE context not being locally available, the second base station may perform an acquire UE context procedure by sending an acquire UE context request message to the source base station of the UE. The acquire UE context request message may include at least one of a UE context ID, an integrity protection parameter, or a new cell identifier. The UE context ID may include at least one of the C-RNTI containing the RRC re-establishment request message and the PCI of the source PCell (last serving PCell). The integrity protection parameter of the RRC re-establishment procedure may be the short MAC-I. The new cell identifier may be an identifier of the target cell, where the target cell is the cell to which the RRC connection is requested to be re-established. The new cell identifier is a cell identity in a system information block (e.g., SIB1) of the target cell (e.g., the selected cell). The source base station may check the acquire UE context request message based on receiving the acquire UE context request message. If the source base station can identify the UE context by the C-RNTI, successfully verify the UE by the short MAC-I, and determine to provide the UE context to the second base station, the source base station may respond with an acquire UE context response message to the second base station. The acquire UE context response message may include at least the GUAMI or the UE context information.Based on receiving the acquire UE context response message, the second base station may send an RRC re-establishment message to the UE. The RRC re-establishment message may include a network hop chain number (NCC) value. Based on receiving the RRC re-establishment message, the UE may receive a current K associated with the NCC value. gNB or based on at least one of the next hop (NH) parameters, the base station (K gNB ) can derive a new security key for the base station (K gNB ) and the previously configured security algorithm, the UE may then use RRC signaling (e.g., RRCint , and K RRCenc ), and user plane (UP) data (e.g., K UPint , and K UPenc ) can be used to derive security keys for integrity protection and encryption of RRC signaling (K RRCint Based on the security key for integrity protection of K), the UE may verify the integrity protection of the RRC re-establishment message. Based on the successful verification, the UE may verify the integrity protection of the RRC re-establishment message based on the previously configured integrity protection algorithm and K RRCint and resuming integrity protection for one or more bearers (e.g., signaling radio bearers or RRC messages) based on a previously configured encryption algorithm and K. RRCencBased on the received SpCell configuration parameter, the UE may configure to resume ciphering of one or more bearers. The second base station may send a first RRC reconfiguration message. The RRC first reconfiguration message may include an SpCell configuration parameter. Based on receiving the SpCell configuration parameter, the UE may start transmitting and receiving data with the second base station. The UE may send an RRC reestablishment complete message to the second base station. The RRC reestablishment complete message may include a measurement report. Based on receiving the measurement report, the second base station may decide to configure an SCell and / or a secondary cell group (e.g., an SCG or a PSCell). Based on the determination, the second base station may send a second RRC reconfiguration message including the SCell configuration parameter and / or the MR-DC related configuration parameter. Based on receiving the second RRC reconfiguration message, the UE may transmit and receive data via the SCell and / or the SCG.

[0236] The RRC reconfiguration message may include at least one of cell group configuration parameters of the MCG and / or SCG, radio bearer configuration parameters, or AS security key parameters.

[0237] The target base station may receive an RRC Resume Request message. Based on receiving the RRC Resume Request message, the target base station may check whether a UE context of the UE is available locally. Based on the UE context not being available locally, the target base station may perform a UE context procedure by sending a Get UE Context Request message to a source base station (last serving base station) of the UE. The Get UE Context Request message may include at least one of a UE context ID, an integrity protection parameter, a new cell identifier, or a resume cause, where the resume cause is in the RRC Resume Request message.

[0238] In the RRC connection resumption procedure, based on receiving the acquire UE context request message, the source base station can check the acquire UE context request message. If the source base station can identify the UE context by the UE context ID and successfully verify the UE by the integrity protection included in the acquire UE context request message, and decide to provide the UE context to the target base station, the source base station can respond to the target base station with an acquire UE context response message. If the source base station cannot identify the UE context by the UE context ID, or the integrity protection included in the acquire UE context request message is not valid, or the source base station decides not to provide the UE context to the target base station, the source base station can respond to the target base station with an acquire UE context failure message.

[0239] In the RRC connection resumption procedure, the acquire UE context failure message may include at least the XnAP ID of the target base station, an RRC release message, or a cause value.

[0240] In the RRC connection resumption procedure, based on receiving the Acquire UE Context Response message, the target base station may send an RRC resume message to the UE. The RRC resume message may include at least one of radio bearer configuration parameters, cell group configuration parameters of the MCG and / or SCG, measurement configuration parameters, or an sk counter, where the sk counter is equal to or smaller than K gNB is used to derive a security key for the secondary base station based on the

[0241] Based on receiving the acquire UE context failure message, the target base station may send an RRC release message to the UE. For example, based on the acquire UE context failure message including an RRC release message, the target base station may send an RRC release message to the UE. Based on receiving the acquire UE context failure message, the target base station may send an RRC setup message or an RRC reject message. Based on receiving the acquire UE context failure message, the target base station may not send a response message to the UE.

[0242] FIG. 18 illustrates an example of an RRC connection resumption procedure. A UE in an RRC connected state may transmit and receive data to and from a first base station (a source base station) via cell 1. The first base station may decide to transition the UE in an RRC connected state to an RRC inactive state. Based on the decision, the base station may send an RRC release message including a suspension configuration parameter. Based on receiving the RRC release message including the suspension configuration parameter, the UE may renew a current security key (e.g., K gNB and K. RRCintThe UE may store the QoS flow to DRB mapping rule, the QoS flow to DRB mapping rule, the C-RNTI used in the source PCell, the global cell identity and physical cell identity of the source PCell, and all other parameters configured except for those in the reconfiguration with synchronization and the serving cell configuration common parameters of the SIB. The robust header compression (ROHC) state may include ROHC states for all PDCP entities (or all bearers), where each PDCP entity per bearer (or each bearer) may have one ROHC state. The QoS flow to DRB mapping rule may be the QoS flow to DRB mapping rule for all data radio bearers (DRBs), and each DRB may have one QoS according to the DRB mapping rule. Based on receiving an RRC release message including the pause configuration parameters, the UE may suspend all SRBs and DRBs except SRB0. Based on the reception of the RRC release message including the suspension configuration parameters, the UE may start timer T380, enter an RRC inactive state, and perform a cell selection procedure. Based on the cell selection procedure, the UE may select cell 2 of a second base station (target base station). The UE in the RRC inactive state may initiate an RRC connection resumption procedure. The UE may perform a unified access control procedure. Based on the unified access control procedure, the UE may consider the access attempt of the RRC connection resumption procedure as granted. The UE may apply default L1 parameter values ​​specified in the corresponding physical layer specification except for parameters whose values ​​are provided in SIB1, apply a default SRB1 configuration, apply a CCCH configuration, apply a common time alignment timer included in SIB1, apply a default MAC cell group configuration, start timer T319, and start transmitting an RRC resumption request message.Based on the initiation of the transmission of the RRC Resume Request message, the UE may restore the stored configuration parameters and the stored security keys from the (stored) UE inactive AS context. For example, the UE may restore the stored configuration parameters and the stored security keys (e.g., K) from the stored UE inactive AS context, except for the master cell group configuration parameters, the MR-DC related configuration parameters (e.g., secondary cell group configuration parameters), and the PDCP configuration parameters. gNB and K. RRCint ) can be restored. The current (restored) K associated with the stored NCC value gNB Or based on the next hop (NH) parameter, the UE determines the next hop gNB Based on the base station's new key, the UE may derive new keys for security keys (e.g., K and K , respectively) for integrity protection and ciphering of the RRC signaling. RRCenc and K. RRCint ), and security keys for integrity protection and encryption of user plane data (e.g., K UPint and K. UPenc ) can be derived. RRCint and K. UPint Based on the configured algorithm, and K, the UE (RRC layer) may configure the lower layer (e.g., the PDCP layer) to apply integrity protection to all radio bearers except SRB0. RRCenc and K. UPencBased on the RRC Resume Request message, the UE may re-establish a PDCP entity for one or more bearers, resume one or more bearers, and send an RRC Resume Request message to the lower layers. Based on the RRC Resume Request message, the second base station may check whether a UE context for the UE is locally available. Based on the UE context not being locally available, the second base station may perform a UE context procedure by sending a Get UE Context Request message to the first base station (last serving base station) for the UE. The Get UE Context Request message may include at least one of a resume identity, a resume MAC-I, or a resume cause. Based on receiving the acquire UE context request message, the first base station may check the acquire UE context request message. If the first base station can identify the UE context by the UE context ID, successfully verify the UE by the resume MAC-I, and determine to provide the UE context to the second base station, the first base station may respond with an acquire UE context response message to the second base station. Based on receiving the acquire UE context response message, the second base station may send an RRC resume message to the UE. Based on receiving the RRC resume message, the UE may restore the master cell group configuration parameters, secondary cell group configuration parameters, and PDCP configuration parameters to the UE inactive AS context.Based on the restoration of the master cell group configuration parameters and / or secondary cell group configuration parameters, the UE may configure the SCells of the MCG and / or SCG by configuring lower layers to consider the restored MCG and / or SCG SCells to be in a deactivated state, destroy the UE inactive AS context, and release the suspension configuration parameters. The UE may transmit and receive data via the SCells and / or SCG.

[0243] A UE in RRC idle state can use early security restart when the UE resumes a suspended RRC connection and at least one of the following conditions is met. The conditions may include: the UE initiates small data transmission (UP) based on UP EDT conditions being met, the UE initiates small data transmission (SDT) procedure (UP) using a configured grant (CG) (e.g., pre-configured uplink resource / grant PUR) based on UP CG conditions being met, the UE resumes a suspended RRC connection in 5G-CN, the UE supports early security restart, the system information block includes a support indication for early security restart, and the UE has a saved value of NCC (next hop chain count) provided in an RRC release message including a suspension configuration parameter (or suspension indication) during the aforementioned suspension procedure. Resumption of the suspended RRC connection may include at least one of initiating an RRC connection resume procedure and sending an RRC resume request message.

[0244] A UE in RRC idle state may initiate an RRC connection resumption procedure to resume a suspended RRC connection. Based on the use of early security restart, the UE can recover the PDCP state, re-establish PDCP entities for all SRBs and all DRBs, and resume all SRBs and all DRBs.

[0245] A UE in an RRC inactive or idle state may send an RRC request message. Based on the transmission of the RRC request message, the UE (UE-RRC layer) may start an RRC timer (e.g., T300 or T319). A UE in an RRC inactive or idle state may receive an RRC response message in response to the RRC request message. Based on the reception of the RRC response message, a UE in an RRC inactive or idle state may stop an RRC timer.

[0246] A UE in RRC inactive or idle state may detect a failure to resume a (suspended) RRC connection while an RRC timer is running. The failure may include at least one of the following: an RRC timer expiry, cell (re)selection, receipt of an RRC reject message, and an SRB1 or SRB2 integrity check failure.

[0247] The UE may initiate an RRC connection establishment procedure in an RRC idle state to establish an RRC connection. Upon initiation, the UE may send an RRC Setup Request message to the base station. Upon sending, the UE may start an RRC timer. Upon detecting a failure to resume the RRC connection when the RRC timer is running and the RRC request message is not an RRC resume request message (an RRC Setup Request is sent), the UE in the RRC idle state may perform at least one of resetting the MAC, releasing the MAC configuration (parameters), and re-establishing RLC for one or more established bearers.

[0248] The UE may initiate an RRC connection resumption procedure in an RRC idle state to resume a suspended RRC connection. Upon initiation, the UE may send an RRC resume request message to the base station. Upon transmission, the UE may start an RRC timer. Upon detecting a failure to resume the RRC connection when the RRC timer is running and the RRC request message is an RRC resume request message (RRC resume request message transmission), the UE may reset the MAC. Upon an RRC timer expiring or a failure being cell (re)selection, receiving an RRC reject message, the RRC reject message including an RRC pause indication, the UE may perform the following: If the UE has resumed the RRC connection after the early security security restart, the UE may stop the early security security restart. Otherwise, the UE may re-establish RLC for one or more established / suspended radio bearers and stop SRB1.

[0249] Aborting the early security restart may include at least one of deleting (or discarding) security keys, re-establishing RLC entities for one or more SRBs and DRBs, suspending one or more SRBs and DRBs except for signaling radio bearer 0 (SRB0), and configuring to stop integrity protection and ciphering.

[0250] Based on the RRC timer expiring, the UE in the RRC inactive state may perform at least one of resetting the MAC, destroying the UE inactive AS context, releasing the suspension configuration parameters, deleting (or destroying) security keys, releasing all radio resources, and transitioning to the RRC idle state, where releasing all radio resources may include releasing the MAC configuration (parameters), the RLC entity, the PDCP entity, and the SDAP for one or more established bearers, and transitioning to the RRC idle state.

[0251] Based on cell (re)selection when the RRC timer is running, a UE in an RRC inactive state may perform at least one of resetting the MAC, destroying the UE inactive AS context, releasing the suspension configuration parameters, deleting (or destroying) security keys, releasing all radio resources, and transitioning to an RRC idle state, where releasing all radio resources may include releasing the MAC configuration (parameters), the RLC entity, the PDCP entity, and the SDAP for one or more established bearers, and transitioning to an RRC idle state.

[0252] If the RRC timer is running, the UE in the RRC inactive or idle state may receive an RRC reject message. Based on receiving the RRC reject message, the UE in the RRC inactive or idle state may stop the RRC timer. Based on the RRC reject message not including an RRC pause indication and the RRC request message being an RRC resume request message, the UE in the RRC idle state may perform at least one of resetting the MAC, tearing down the UE inactive AS context, releasing all radio resources, and transitioning to an RRC idle state, where releasing all radio resources may include releasing the MAC configuration (parameters), the RLC entity, the PDCP entity, and the SDAP for the established bearer or bearers. Based on the RRC reject message and the RRC request message not being an RRC resume request message, the UE in the RRC idle state may perform at least one of resetting the MAC and releasing default MAC configuration parameters. Based on the RRC rejection message, the UE in the RRC inactive state may perform at least one of the following: reset MAC, release default MAC configuration (parameters), delete (or discard) security keys, suspend the RRC connection, and maintain the RRC inactive state.

[0253] An integrity check failure occurs when an RRC timer is running and the UE is in an RRC inactive or idle state. For example, a UE in an RRC inactive or idle state may detect an integrity check failure of SRB1 or SRB2 when an RRC timer is running. Based on the integrity check failure and the RRC request message being an RRC resume request message, the UE in an RRC idle state performs at least one of resetting the MAC, destroying the UE inactive AS context, releasing all radio resources, and transitioning to an RRC idle state, where releasing all radio resources may include releasing the MAC configuration (parameters), the RLC entity, the PDCP entity, and the SDAP for one or more established bearers. Based on the integrity check failure and the RRC request message being an RRC Resume Request message, the UE in the RRC Inactive state may perform at least one of resetting MAC, destroying UE inactive AS context, releasing suspension configuration parameters, deleting (or destroying) security keys, releasing all radio resources, and transitioning to an RRC Idle state, where releasing all radio resources may include releasing the MAC configuration (parameters), the RLC entity, the PDCP entity, and the SDAP for one or more established bearers, and transitioning to an RRC Idle state.

[0254] An RRC idle UE may detect a failure to resume an RRC connection when an RRC timer is running. An RRC idle UE may (re)suspend one or more radio bearers (or RRC connections) based on the failure. Based on the stopping of one or more radio bearers, an RRC idle UE may send an RRC RESUME REQUEST message to resume an RRC connection. For example, based on suspending one or more radio bearers, an RRC idle UE may send an RRC RESUME REQUEST message to a base station when the UE has data or signals to send or receive a paging message from the base station. An RRC idle UE may not suspend one or more radio bearers (or RRC connections) based on a failure (e.g., release of all radio resources). Based on not suspending one or more radio bearers (or RRC connections), an RRC idle UE may release all radio resources and send an RRC SETUP REQUEST message. For example, based on not pausing one or more radio bearers (or RRC connections), a UE in an RRC idle state may send an RRC setup request message to the base station when the UE has data or signaling to send or receive a paging message from the base station.

[0255] The base station may initiate an RRC connection release procedure to transition the RRC state of the UE from an RRC connected state to an RRC idle state, from an RRC connected state to an RRC inactive state, from an RRC inactive state to an RRC inactive state when the UE attempts to resume, or from an RRC inactive state to an RRC idle state when the UE attempts to resume. The RRC connection procedure may also be used to release the RRC connection of the UE and redirect the UE to another frequency. The base station may transmit an RRC release message including a suspension configuration parameter when transitioning the RRC state of the UE to an RRC inactive state. The suspension configuration parameter may include at least one of a resume identity, an RNA configuration, a RAN paging cycle, or a network hop chain number (NCC) value, and the RNA configuration may include an RNA notification area information, or a periodic RNA update timer value (e.g., a T380 value). The base station may use the resume identity (e.g., an inactive-RNTI (I-RNTI)) to identify the UE context when the UE is in an RRC inactive state.

[0256] If the base station has a fresh, unused pair of {NCC, next hop (NH)}, the base station may include the NCC in the suspension configuration parameters. Otherwise, the base station may include the current K gNB The suspension configuration parameter may include the same NCC associated with the AS. The NCC is used for AS security. After the base station sends an RRC release message including the suspension configuration parameter to the UE, the base station may RRCenc , K UPenc ), and K UPint However, the current AS key K RRCint If the transmitted NCC value is fresh and belongs to an unused {NCC, NH} pair, the base station may store the {NCC, NH} pair in the current UE AS security context and may retain the current AS key K gNB The transmitted NCC value can be deleted if the current K gNB If the NCC value associated with the current AS key KgNB and the NCC. The base station may store the transmitted resumption identity along with the current UE context, including the remainder of the AS security context.

[0257] Upon receiving the RRC Release message including the suspension configuration parameters from the base station, the UE may verify that the integrity of the received RRC Release message including the suspension configuration parameters is correct by checking the PDCP MAC-I. If this verification is successful, the UE retrieves the received NCC value and saves it as the NCC stored with the current UE context. The UE may then retrieve the current AS key K RRCenc , K UPenc , and K UPint However, the current AS key K RRCint The stored NCC value can hold the current K gNB If the NCC value associated with the current AS key K is different from the NCC value associated with the current AS key K, the UE gNB The stored NCC can be deleted from the current K gNB If the received resumption identity is equal to the NCC value associated with the AS, then the UE shall retain the current AS key KgNB. The UE may store the received resumption identity together with the current UE context, including the remaining part of the AS security context, for the next state transition.

[0258] Upon receiving the RRC release message including the suspension configuration parameters, the UE may reset the MAC, release the default MAC cell group configuration, and re-establish an RLC entity for one or more bearers. Upon receiving the RRC release message including the suspension configuration parameters, the UE may store the current configuration parameters and the current security keys in the UE inactive AS context. For example, the UE may store some of the current configuration parameters. The stored current configuration parameters may include the Robust Header Compression (ROHC) state, the Quality of Service (QoS) flow to DRB mapping rule, the C-RNTI used in the source PCell, the global cell identity and the physical cell identity of the source PCell, and all other parameters configured except for those in the reconfiguration with synchronization and the serving cell configuration common parameters of the SIB. The stored security keys may be stored in the RRC release message including the suspension configuration parameters. gNB and K. RRCint The RRC release message may include at least one of: a) configuring a cell specific parameter of the UE's serving cell in SIB1 using the serving cell configuration common parameter in the SIB; b) configuring a cell specific parameter of the UE's serving cell in SIB2 using the serving cell configuration common parameter in the SIB; c) configuring a cell specific parameter of the UE's serving cell in SIB3 using the serving cell configuration common parameter in the SIB; d) configuring a cell specific parameter of the UE's serving cell in SIB4 using the serving cell configuration common parameter in the SIB; e) configuring a cell specific parameter of the UE's serving cell in SIB5 using the serving cell configuration common parameter in the SIB; f) configuring a cell specific parameter of the UE's serving cell in SIB6 using the serving cell configuration common parameter in the SIB; f) configuring a cell specific parameter of the UE's serving cell in SIB7 using the serving cell configuration common parameter in the SIB; f) configuring a cell specific parameter of the UE's serving cell in SIB8 using the serving cell configuration common parameter in the SIB; f) configuring a cell specific parameter of the UE's serving cell in SIB1 ...

[0259] The UE may receive an RRC release message from a base station of a serving cell (or PCell). Based on the RRC release message, the UE may perform a UE action for the RRC release message from the base station. The UE may delay the UE action for the RRC release message for a certain time (e.g., 60 ms) from the time of receiving the RRC release message or from the time of successfully acknowledging the reception of the RRC release message. The UE may send a HARQ acknowledgement to the base station to acknowledge the RRC release message. Based on the RLC protocol data unit (PDU) including the RLC release message and the RLC PDU including a polling bit, the UE may send an RLC message (e.g., a status report) to the base station to acknowledge the RRC release message.

[0260] The UE action in response to an RRC release message from the base station may include at least one of suspending the RRC connection, releasing the RRC connection, a cell (re)selection procedure, and / or idle / inactive measurements.

[0261] The RRC release message from the base station may include a suspension configuration parameter. Based on the suspension configuration parameter, the UE may perform a suspension of the RRC connection. The suspension of the RRC connection may include at least one of a media access control (MAC) reset (or MAC reset), a release of a default MAC cell group configuration, a re-establishment of an RLC entity for one or more radio bearers, a saving of current configuration parameters and current security keys, a suspension of one or more bearers, where the bearers include a signaling radio bearer and a data radio bearer, and / or a transition to an RRC idle state or an RRC inactive state.

[0262] Based on the MAC reset, the UE may perform at least one of: stopping all timers running at the UE-MAC layer, considering all time alignment timers as expired, setting new data indicators (NDIs) for all uplink HARQ processes to a value of 0, stopping ongoing RACH procedures, discarding explicitly signaled contention-free random access resources if any, flushing the Msg3 buffer, canceling triggered scheduling request procedures, canceling triggered buffer status reporting procedures, canceling triggered power headroom reporting procedures, flushing soft buffers for all DL HARQ processes, considering the next received transmission for TB as the first transmission for each DL HARQ process, and / or releasing the temporary C-RNTI.

[0263] Based on deeming the time alignment timer to have expired, the UE may perform at least one of: flushing all HARQ buffers for all serving cells, notifying RRC to release PUCCH for all serving cells (if configured), notifying RRC to release SRS for all serving cells (if configured), clearing any configured downlink assignments and configured uplink grants, clearing any PUSCH resources for semi-persistent CSI reporting, and / or deeming all running time alignment timers to have expired.

[0264] The default MAC cell group configuration parameters may include buffer status report (BSR) configuration parameters for the base station's cell group (e.g., BSR timers) and power headroom report (PHR) configuration parameters for the base station's cell group (e.g., PHR timers or PHR transmit power factor change parameters).

[0265] Re-establishing the RLC entity may include at least one of discarding all RLC SDUs, RLC SDU segments, and RLC PDUs (if present), stopping and resetting all timers of the RLC entity, and resetting all state variables of the RLC entity to their initial values.

[0266] The RRC release message from the base station may not include the suspension configuration parameter. Based on the RRC release message not including the suspension configuration parameter, the UE may perform a release of the RRC connection. For example, based on the RRC release message not including the suspension configuration parameter, the RRC release message may indicate a release of the RRC connection. The UE may perform a release RRC connection. The release of the RRC connection may include at least one of a MAC reset (or a MAC reset), a discard of stored configuration parameters and stored security keys (or a discard of stored UE inactive AS contexts), a release of the suspension configuration parameter, a release of all radio resources including the RLC entity, the MAC configuration, and associated PDCP entities, a release of SDAPs for all established radio bearers, and / or a transition to an RRC idle state.

[0267] The RRC release message may be an RRC Early Data Complete message.

[0268] The UE may transmit or receive a small amount of data without transitioning from an RRC idle state or an RRC inactive state to an RRC connected state based on performing a small data transmission. Performing a small data communication may include at least one of initiating a small data communication, transmitting a small data, and / or receiving a response message while remaining in an RRC idle state or an RRC inactive state (e.g., without transitioning to an RRC connected state).

[0269] For example, based on the small data transmission, a UE in an RRC idle state or an RRC inactive state may perform initiation of small data transmission. In response to the initiation of small data transmission, a UE in an RRC idle state or an RRC inactive state may perform small data transmission. In response to the transmission of the small data, the UE may receive a response message. For example, the response message may include downlink data (or downlink signaling). For example, based on the small data transmission, a UE in an RRC idle state or an RRC inactive state may perform small data transmission. In response to the transmission of the small data, a UE in an RRC idle state or an RRC inactive state may receive a response message. Transmitting the small data may include at least one of transmitting at least one of an RRC request message, uplink data (or uplink signaling), or a buffer status report (BSR). For example, transmitting the small data may include transmitting an RRC request message. For example, transmitting the small data may include transmitting an RRC request message and uplink data. For example, transmitting the small data may include transmitting an RRC request message, the first uplink data, and a BSR requesting uplink resources for the second uplink data. The RRC request message may include at least one of an RRC resume request message, or an RRC early data request message. The response message may include at least one of an RRC response message in response to the RRC request message, downlink data, or an acknowledgement for the uplink data (e.g., the first uplink data), or uplink resources for the uplink data (e.g., the second uplink data). The RRC response message to the RRC request message may include at least one of an RRC release message, an RRC early data complete message, an RRC setup message, an RRC resume message, or an RRC reject message.

[0270] Based on receiving the RRC release message, a UE in RRC idle or RRC inactive state may transition to RRC idle or RRC inactive state or may remain in RRC idle or RRC inactive state. Based on receiving the RRC early data complete message, a UE in RRC idle or RRC inactive state may transition to (or remain in) RRC idle state. Based on receiving the RRC release message or RRC early data complete message, a UE may consider the transmission of small data to be successful. Based on receiving the RRC setup message or RRC resume message, a UE in RRC idle or RRC inactive state may transition to RRC connected state. Based on receiving the RRC setup message or RRC resume message, a UE may consider the transmission of small data to be successful. Based on receiving the RRC reject message, a UE in RRC idle or RRC inactive state may transition to RRC idle state. Based on receiving the RRC reject message, a UE may consider the transmission of small data to be unsuccessful.

[0271] Based on receiving the first RRC release message, the UE may transition to an RRC inactive or idle state. A UE in an RRC inactive or idle state may perform a small data transmission. A UE in an RRC inactive or idle state may have small data to transmit or may initiate / trigger a small data transmission based on receiving a paging message. The paging message may indicate a small data transmission. Based on performing a small data transmission, a UE in an RRC idle or RRC inactive state may transmit uplink data via Msg3. Msg3 may be a message transmitted on a UL-SCH including a C-RNTI MAC CE or a CCCH SDU, optionally multiplexed with a DTCH. For example, the CCCH SDU may be associated with a UE Contention Resolution Identity as part of a random access procedure. For example, a UE in an RRC idle or RRC inactive state may transmit a CCCH SDU using a preconfigured uplink resource (PUR). The CCCH SDU may include at least one of an RRC request message and uplink data (e.g., the first uplink data). The DTCH may include uplink data (e.g., first uplink data). Based on performing the small data transmission, the UE in the RRC idle state or the RRC inactive state may receive downlink data in response to the small data transmission without transitioning to an RRC connected state. For example, based on performing the small data transmission, the UE in the RRC idle state or the RRC inactive state may transmit an RRC request message and receive at least one of an RRC response message and / or downlink data in response to the RRC request message. The RRC release message may include a second RRC release message, and the RRC release message may include the downlink data. Based on the second RRC release message, the UE may transition to an RRC inactive or idle state.

[0272] The small data transmission may include a user plane (UP) small data transmission and a control plane (CP) small data transmission. Based on the UP small data transmission, a UE in an RRC idle state or an RRC inactive state may transmit uplink data via a user plane (e.g., DTCH). Based on the CP small data transmission, a UE in an RRC idle state or an RRC inactive state may transmit uplink data via a control plane (e.g., CCCH). Based on the UP small data transmission, a base station of the UE may receive downlink data via a user plane from a UPF of the UE. Based on the CP small data transmission, a base station of the UE may receive downlink data via a control plane from an AMF of the UE. In response to the CCCH SDU and / or the DTCH SDU, the base station may transmit a response message to a UE in an RRC idle state or an RRC inactive state.

[0273] The small data transmission may include at least one of initiating a small data transmission, transmitting small data, and receiving a response message. The UP small data transmission may include at least one of initiating a UP small data transmission, transmitting a UP small data, and receiving a response message. The CP small data transmission may include at least one of transmitting CP small data via the control plane and receiving a response message.

[0274] Initiating the small data transmission may include initiating a UP small data transmission. Transmitting the small data may include at least one of transmitting UP small data and / or transmitting CP small data via a control plane. The response message may be a response message in response to at least one of the RRC request message and / or the (first) uplink data.

[0275] For a UP small data transmission, the DTCH SDU may include uplink data. For example, for a UP small data transmission, the UE may transmit a DTCH SDU multiplexed with a CCCH SDU. For example, for a UP small data transmission, the CCCH SDU may include at least one of uplink data and an RRC request message. For example, for a UP small data transmission, the RRC request message may be an RRC Resume Request message. For a CP small data transmission, the UE may transmit a CCCH SDU including uplink data. For example, for a CP small data transmission, the RRC request message includes uplink data. For example, for a CP small data transmission, the RRC request message may be an RRC Early Data Request message.

[0276] In one embodiment, a small data transmission (SDT) procedure may include an exchange of user data between a wireless device and a base station while the wireless device is in a non-connected state (e.g., a Radio Resource Control (RRC) non-connected state) (e.g., an idle state, an inactive state, etc.). The amount of data exchanged in an SDT transmission of an SDT procedure may be less than a threshold amount of data. An SDT procedure may include a small amount of data and / or one SDT transmission in a series of SDT transmissions. For example, using an SDT procedure, a wireless device and / or a base station may transmit and / or receive data via a user plane (UP) or a control plane (CP) while the wireless device remains in a non-connected state (e.g., idle, inactive, etc.). For example, using an SDT procedure, a wireless device may transmit and / or receive data without completing a connection setup or resumption procedure (and without control plane signaling related to the setup and / or resumption). The data may include user data and signaling.

[0277] In one embodiment, a wireless device may require a grant to transmit data (e.g., uplink data) associated with an SDT procedure. The wireless device may receive the grant from / through a base station. The grant may be an uplink grant for one or more uplink resources, and the wireless device may transmit the data (e.g., uplink data) using the one or more uplink resources. The grant may be a dynamic uplink grant or a configured uplink grant for one or more uplink resources. A dynamic uplink grant may indicate one or more specific uplink resources to be used for uplink transmission at a particular time. A configured uplink grant may indicate resources that are recurring, intermittent, and / or periodic. For example, a configured uplink grant configuration may indicate a periodicity of the configured uplink grant, and one or more uplink resources of the configured uplink grant configuration may be periodically reused. For example, a configured uplink grant may be configured / activated, and resources associated with the configured uplink grant may be used until the configured uplink grant is released / deactivated. As an example, a dynamic uplink grant may indicate resources at time k, while a configured uplink grant may grant resources at time k+nT, where T is the duration of the configured uplink grant and n is an integer [0,1,2,...].

[0278] In one embodiment, the wireless device may obtain the uplink grant via a physical or MAC signal (e.g., a DCI or a random access (RA) response) indicating the uplink grant. For example, in a random access (RA) based procedure (e.g., an early data transmission (EDT) procedure), the wireless device may transmit an RA preamble requesting one or more uplink resources. Based on the RA preamble, the wireless device may receive an uplink grant indicating one or more uplink resources for transmitting small data.

[0279] In one embodiment, the wireless device may obtain an uplink grant based on a configured uplink grant. The configured uplink grant may be associated with a configured uplink grant configuration (e.g., a preconfigured uplink resource (PUR) configuration). The wireless device may receive the configured uplink grant configuration via an RRC message (e.g., an RRC release message). The configured uplink grant configuration may indicate a grant of one or more uplink resources, and the wireless device may use and / or reuse the one or more uplink resources (e.g., the preconfigured uplink resources) to transmit small data.

[0280] For a configured uplink grant transmission (e.g., an uplink transmission using pre-configured uplink resources (PUR)), the UE may send a configured uplink grant configuration request message to the base station, where the configured uplink grant configuration request message includes at least one of a requested number of configured uplink grant opportunities (the number may be one or infinite), a requested periodicity of the configured uplink grant, a requested transport block size (TBS) for the configured uplink grant, and / or a requested time offset for the first configured uplink grant opportunity.

[0281] The base station may transmit a configured uplink grant configuration (parameters) including the pre-configured uplink resources to the UE. For example, in response to a configured uplink grant configuration request message, the base station may transmit the configured uplink grant configuration parameters including the pre-configured uplink resources to the UE. For example, the base station may transmit an RRC release message including the configured uplink grant configuration parameters to the UE.

[0282] The configured uplink grant configuration parameters may include at least one of an indication to set up or release the configured uplink grant configuration parameters, a number of configured uplink grant opportunities, a configured uplink grant resource identifier (configured uplink grant RNTI), a configured uplink grant configuration identity (configured uplink grant configID), a value of a time offset for the first configured uplink grant opportunity (configured uplink grant start time), a configured uplink grant resource periodicity (configured uplink grant periodicity), a configured uplink grant response window duration (configured uplink grant response window time), a serving cell RSRP change threshold in dB for TA validation (configured uplink grant change threshold) (thresholds include an RSRP increase threshold and an RSRP decrease threshold), a value of a configured uplink grant time alignment timer, and / or a configured uplink grant physical configuration parameter. The configured uplink grant physical configuration parameters may include at least one of the following: A PUSCH configuration parameter of the configured uplink grant, a PDCCH configuration parameter of the configured uplink grant, a PUCCH configuration parameter of the configured uplink grant, a downlink carrier configuration parameter used for the configured uplink grant, and / or an uplink carrier frequency of the uplink carrier used for the configured uplink grant. The configured uplink grant RNTI may be assigned to multiple UEs. The configured uplink grant configID may be unique for one base station.

[0283] The UE may decide to start the SDT using the configured uplink grant (CG-based SDT) based on the configured uplink grant conditions being met. The configured uplink grant conditions may include at least one of: the UE has valid configured uplink grant configuration parameters, the UE has a valid Timing Alignment (TA) value, the serving cell's system information indicates configured uplink grant support, the establishment or resumption request is for a mobile call and the establishment cause is mo data or mo exception data or delay tolerant access, the UE supports the configured uplink grant, the size of the resulting MAC PDU including the total uplink data is expected to be equal to or smaller than the TBS configured for the configured uplink grant, and the UE has a saved NCC value provided in an RRC release message including the suspension configuration parameters during the aforementioned suspension procedure.

[0284] The UE may determine a timing alignment value for small data transmissions for a configured uplink grant that is valid based on a TA verification condition for the configured uplink grant being satisfied. The TA verification condition for the configured uplink grant may include at least one of a time alignment timer for the configured uplink grant being running or a serving cell RSRP not increasing beyond an RSRP increase threshold and not decreasing beyond an RSRP increase threshold.

[0285] In response to receiving the configured uplink grant configuration parameters, the UE may store or replace the configured uplink grant configuration parameters provided by the configured uplink grant configuration parameters based on an indication requesting to set up the configured uplink grant configuration parameters. In response to receiving the configured uplink grant configuration parameters, the UE may start a time alignment timer for the configured uplink grant with a value of the time alignment timer for the configured uplink grant and configure the configured uplink grant configuration parameters. For example, based on an indication requesting to set up the configured uplink grant configuration parameters, the UE may start a time alignment timer for the configured uplink grant with a value of the time alignment timer for the configured uplink grant and configure the configured uplink grant configuration parameters. In response to receiving the configured uplink grant configuration parameters, the UE may discard the configured uplink grant configuration parameters based on an indication requesting to release the configured uplink grant configuration parameters. In response to configuring the configured uplink grant configuration parameters, the UE may generate a configured uplink grant based on the configured uplink grant configuration parameters. For example, based on the configured uplink grant configuration parameters, the UE may determine when to generate the configured uplink grant. For example, based on the start time of the configured uplink grant and the periodicity of the configured uplink grant, the UE may determine when to generate the configured uplink grant. For example, based on the PUSCH configuration parameters, the UE may determine the configured uplink grant (transmit a block). For example, based on the PUSCH configuration parameters, the UE may determine the configured uplink grant (transmit a block).

[0286] FIG. 19 illustrates an example of data transmission based on a configured uplink grant (e.g., pre-configured uplink resources (PUR)). Based on receiving a first RRC release message, the UE may transition to an RRC disconnected state (e.g., an RRC idle state or an RRC inactive state). As shown in FIG. 19, the UE may transmit a configuration request for configuration of a configured uplink grant ("CUG" in the figure). The UE may receive a configured uplink grant configuration parameter via an RRC release message. The previous RRC release message may be the first RRC release message. In response to receiving the configured uplink grant configuration parameter, the UE in the RRC idle state or the RRC inactive state may start a configured uplink grant time alignment timer with a value of the configured uplink grant time alignment timer and configure the configured uplink grant configuration parameter. In response to configuring the configured uplink grant configuration parameter, the UE in the RRC idle state or the RRC inactive state may generate a configured uplink grant based on the configured uplink grant configuration parameter. Based on the first RRC release message, the UE may perform a cell (re)selection procedure. Based on the cell (re)selection procedure, the UE in the RRC idle state or the RRC inactive state may select cell 2 of the second base station (target base station). The UE in the RRC idle state or the RRC inactive state may have first uplink data in an uplink buffer or receive a paging message. The UE in the RRC idle state or the RRC inactive state may determine to perform small data transmission based on the UP configured uplink grant condition or the CP configured uplink grant condition being met.For example, in response to having the first uplink data or receiving a paging message, a UE in an RRC idle state or an RRC inactive state may determine to perform a small data transmission based on a UP configured uplink grant condition or a CP configured uplink grant condition being met. Based on the determination, the UE may perform the small data transmission. Based on the uplink resource / grant for the configured uplink grant, the UE may perform the small data transmission. For example, a UE in an RRC idle state or an RRC inactive state may transmit at least one of an RRC request message and / or the first uplink data using an uplink resource for the configured uplink grant. For example, based on the small transmission, a UE in an RRC idle state or an RRC inactive state may transmit an Msg3 including at least one of a CCCH SDU and / or a DTCH SDU, where the CCCH SDU includes the RRC request message and the DTCH SDU includes the first uplink data. In response to transmitting the small data using the configured uplink grant, the UE (UE-MAC entity) may start a configured uplink grant response window timer with the configured uplink grant response window time. Upon starting, the UE may monitor a PDCCH identified by the configured uplink grant RNTI until the configured uplink grant response window timer expires. The UE (UE-MAC entity) may receive a downlink message (e.g., DCI) identified by the configured uplink grant RNTI on the PDCCH. Upon receiving a downlink message indicating an uplink grant for retransmission, the UE may restart the configured uplink grant response window timer in the last subframe (e.g., 4 subframes) of the PUSCH transmission indicating an uplink grant pulse time gap.Based on the re-initiation, the UE in RRC idle or RRC inactive state may monitor the PDCCH identified by the configured uplink grant RNTI until the configured uplink grant response window timer expires. Based on receiving a downlink message indicating an L1 (Layer 1) ACK for the configured uplink grant, the UE in RRC idle or RRC inactive state may stop the configured uplink grant response window timer and consider the small data transmission using the configured uplink grant successful. Based on receiving a downlink message indicating a fallback for the configured uplink grant, the UE in RRC idle or RRC inactive state may stop the configured uplink grant response window timer and consider the small data transmission using the configured uplink grant failed. Based on receiving a downlink message indicating a PDCCH transmission (downlink grant or downlink assignment) for the configured uplink grant RNTI and / or MAC PDU including the uplink data being successfully decoded, the UE in the RRC idle or RRC inactive state may stop the configured uplink grant response window timer and consider the small data transmission using the configured uplink grant to be successful. Based on the PDCCH transmission, the UE in the RRC idle or RRC inactive state may receive at least one of an RRC response message and downlink data, the RRC response message being at least one of an RRC release message or an RRC early data completion message. Based on not receiving any downlink message until the configured uplink grant response window timer expires, the UE in the RRC idle or RRC inactive state may consider the small data transmission using the configured uplink grant to be unsuccessful. Based on considering the small data transmission using the configured uplink grant to be unsuccessful, the UE may perform a random access procedure. For example, the random access procedure may include an EDT RACH procedure.

[0287] FIG. 20 illustrates an example of a UP configured uplink grant and a CP configured uplink grant. The UE in the RRC connected state may communicate with the first base station based on the first configuration parameter and the first security key. The first base station may send an RRC release message to the UE. Based on receiving the RRC release message including the first suspension configuration parameter, the UE may perform suspension of the RRC connection based on the first suspension configuration parameter. The UE may transition to an RRC idle state or an RRC inactive state. The UE may receive the configured uplink grant configuration parameter via a previous RRC release message. The previous RRC release message may be an RRC release message. In response to receiving the configured uplink grant configuration parameter, the UE in the RRC idle state or the RRC inactive state may start a configured uplink grant time alignment timer with a value of the configured uplink grant time alignment timer and configure the configured uplink grant configuration parameter. In response to the configuration of the configured uplink grant configuration parameters, the UE in the RRC idle state or the RRC inactive state may generate a configured uplink grant based on the configured uplink grant configuration parameters. Based on the RRC release message, the UE in the RRC idle state or the RRC inactive state may perform a cell (re)selection procedure. Based on the cell (re)selection procedure, the UE in the RRC idle state or the RRC inactive state may select cell 2 of the second base station (target base station). The UE in the RRC idle state or the RRC inactive state may determine to start a UP small data transmission based on the UP configured uplink grant conditions being met. Based on the decision to start a UP small data transmission, the UE in the RRC idle state or the RRC inactive state may perform starting a UP small data transmission using the first pause configuration parameters.Based on the (pre-configured) uplink resources for the configured uplink grant, the UE in RRC idle state or in RRC inactive state may transmit UP small data using the first suspension configuration parameter. For example, the UE in RRC idle state or in RRC inactive state may transmit uplink data using the uplink resources for the configured uplink grant.

[0288] In the example of FIG. 20, a UE in an RRC connected state may communicate with a first base station based on the first configuration parameter and the first security key. The first base station may send an RRC release message to the UE. Based on receiving the RRC release message that does not include the first pause configuration parameter, the UE may perform a release RRC connection based on the RRC release message. The UE may transition to an RRC idle state. The UE may receive a configured uplink grant configuration parameter via a previous RRC release message. The previous RRC release message may be an RRC release message. In response to receiving the configured uplink grant configuration parameter, the UE in an RRC idle state may start a configured uplink grant time alignment timer with a value of the configured uplink grant time alignment timer and configure the configured uplink grant configuration parameter. In response to configuring the configured uplink grant configuration parameter, the UE RRC idle state may generate a configured uplink grant for the configured uplink grant based on the configured uplink grant configuration parameter. Based on the RRC release message, the UE in an RRC idle state may perform a cell (re)selection procedure. Based on the cell (re)selection procedure, the RRC idle UE may select cell 2 of the second base station (target base station). The RRC idle UE may determine to transmit CP small data via the control plane based on the CP configured uplink grant condition being met. Based on the determination, the RRC idle UE may transmit the CP small data via the control plane. For example, based on the (pre-configured) uplink resources for the configured uplink grant, the RRC idle UE may transmit the CP small data via the control plane. For example, the RRC idle UE may transmit at least one of an RRC request message and / or uplink data using the uplink resources for the configured uplink grant.For example, the RRC request message may be an RRC Early Data Request message and / or may include uplink data.

[0289] The first base station (source base station) sends an RRC release message to the wireless device, where the RRC release message includes a suspension configuration and a configuration of at least one configured uplink grant of the first cell. The suspension configuration may include a resume identity. Based on the RRC release message, the first base station may store a mapping of the resume identity and the configuration of at least one configured uplink grant of the first cell. Based on the suspension configuration, the wireless device may suspend the RRC connection. The wireless device may decide to resume the RRC connection. Based on the decision, the wireless device that stops the RRC connection may send an RRC resume request message including the resume identity. The resume identity may be delivered to the first base station based on the UE context procedure. Based on the resume identity, the first base station may release the configuration.

[0290] The UE may receive a configured uplink grant configuration (parameters) of the first cell. The configured uplink grant configuration may include at least one of a configured uplink grant configuration identity, a configured uplink grant of the first cell. In the figures, the configured uplink grant configuration identifier may be abbreviated as "CULG-configID" for brevity. The UE may transmit an RRC setup request message via the first cell without using the configured uplink grant of the first cell. Based on transmitting an RRC setup message with the configured uplink grant configuration without using the configured uplink grant, the UE may transmit an RRC setup complete message including the configured uplink grant configuration identifier. In response to receiving the RRC setup message, the UE may transmit an RRC setup complete message. The UE may receive an RRC setup message in response to the RRC setup request message. Based on receiving the configured uplink grant configuration identifier, the base station of the first cell may identify a configured uplink grant configuration associated with the configured uplink grant configuration identifier. Based on the identification of the configured uplink grant configuration, the base station may manage the configured uplink grant configuration. For example, the management may include releasing. The configured uplink grant configuration identifier is a unique identity for each base station.

[0291] In the existing technology, the wireless device may receive a first configured uplink grant configuration of the first cell from a first base station. Based on receiving the first configured uplink grant configuration of the first cell, the wireless device may store the first configured uplink grant configuration of the first cell. The wireless device in an RRC idle state may select a second cell. For example, the second cell may be selected for connection based on a signal strength of the second cell. The wireless device may initiate a random access procedure on the second cell, the random access procedure including an RRC connection establishment procedure. Based on the initiation of the random access procedure, the wireless device may disconnect from the first cell and / or release the first configured uplink grant configuration of the first cell. The first base station may not recognize that the first configured uplink grant is no longer being used. The first base station may maintain the first configured uplink grant configuration parameters. Based on maintaining the first configured uplink grant configuration parameters, the first cell continues to allocate resources associated with the first configured uplink grant, which may waste the allocated resources by preventing other network entities from using them.

[0292] FIG. 21 illustrates an example of a wireless device release of configured uplink grant configuration parameters. A wireless device in an RRC connected state may send a configured uplink grant configuration request message to a first base station via a first cell. The first base station may send an RRC release message including the configured uplink grant configuration (parameters) to the wireless device. The first base station may store the configured uplink grant configuration. Based on the RRC release message, the wireless device may transition to an RRC idle state. The wireless device may select a second cell based on cell (re)selection. The wireless device may initiate a random access procedure via the second cell, where the random access procedure includes an RRC connection establishment procedure. Based on the random access procedure, the wireless device may release the configured uplink grant configuration. The first base station may not recognize that the configured uplink grant configuration is released by the wireless device. The first base station may maintain the configured uplink grant configuration, and the first cell may continue to allocate the configured uplink grant of the wireless device.

[0293] In an embodiment of the present disclosure, a wireless device in an RRC idle state may transmit one or more RRC messages indicating releasing at least one configured uplink grant of the first cell to the second base station. The second base station may transmit one or more RRC messages to the first base station based on the first cell being a cell of the first base station. Based on the one or more RRC messages, the first base station may release the configured uplink grant configuration of the first cell. Based on the embodiment, the first base station may avoid wasting radio resources by unnecessarily allocating the configured uplink grant.

[0294] In one embodiment, the UE may select a second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may transmit one or more RRC messages indicating releasing at least one configured uplink grant of one or more configurations (configured uplink grant configurations) of the first cell. Based on the determination, the UE may transmit one or more RRC messages indicating releasing one or more configurations (configured uplink grant configurations) of the first cell.

[0295] In one embodiment, the one or more RRC messages may include at least one of: one or more cell identities of the first cell, or one or more configured uplink grant configuration identifiers, a resumption identity.

[0296] In one embodiment, the UE may select the second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may initiate an RRC procedure to establish the RRC connection. For example, based on the initiation via the second cell, the UE may determine to release at least one of the one or more configurations of the at least one configured uplink grant of the first cell or at least one of the one or more configurations of the at least one configured uplink grant of the first cell. Based on the determination, the UE may transmit one or more RRC messages indicating the release of at least one configured uplink grant of the one or more configurations of the first cell or at least one of the one or more configurations of the at least one configured uplink grant of the first cell. The RRC procedure includes an RRC connection establishment procedure.

[0297] In one embodiment, from the first cell, the UE may receive at least one first Radio Resource Control (RRC) message including one or more configurations of at least one configured uplink grant of the first cell. The one or more RRC messages may include at least one of one or more cell identities of the one or more configured cells, one or more configured uplink grant configuration identifiers of the one or more configurations. The one or more configurations may not include a configuration of the second cell and a cell identity of the second cell.

[0298] In one embodiment, based on receiving the one or more configurations, the UE may store the one or more configurations. For example, the at least one first RRC message may include an RRC release message. Based on the RRC release message, the UE may transition from an RRC connected state to an RRC idle state. The RRC release message may include the one or more configurations. The configuration may be an indication that the UE maintains the stored configured uplink grant configuration.

[0299] In one embodiment, based on at least one of determining that the second cell is different from the first cell and determining to establish an RRC connection via the second cell, the UE may determine to release at least one of one or more configured uplink grants of the first cell or one or more configurations of the at least one configured uplink grant of the first cell.

[0300] In one embodiment, the one or more RRC messages may include one or more cell identities of the first cell, where the first cell may include one or more cells associated with one or more configurations. For example, the UE may select the second cell. The UE may initiate an RRC procedure to establish an RRC connection via the second cell. Based on the initiation, the UE may determine to release at least one of the one or more configurations of the at least one configured uplink grant of the first cell or the one or more configurations of the at least one configured uplink grant of the first cell. Based on the determination, the UE may transmit one or more RRC messages including the one or more cell identities of the first cell. For example, the UE may transmit the one or more cell identities of the first cell to indicate the release of the at least one configured uplink grant of the first cell or the one or more configurations of the first cell.

[0301] In one embodiment, the UE may transmit one or more RRC messages including one or more configured uplink grant configuration identities of the wireless device. For example, the UE may transmit one or more RRC messages including the one or more configured uplink grant configuration identifiers based on at least one of determining that the one or more RRC messages are not responsive to transmission using at least one configured uplink grant of the one or more configured uplink grant configuration identifiers and determining to release at least one configured uplink grant or one or more configured uplink grant configurations of the one or more configured uplink grant configuration identifiers. For example, the UE may transmit one or more RRC messages including one or more configured uplink grant configuration identifiers associated with the first cell based on at least one of determining to establish an RRC connection via the second cell and transmitting one or more RRC messages that do not use at least one configured uplink grant of the configuration of the second cell. For example, the UE may transmit one or more RRC messages including one or more configured uplink grant configuration identifiers of one or more configurations of the first cell based on transmitting one or more RRC messages (e.g., an RRC Setup Request message) that are not in response to a transmission using at least one configured uplink grant of one or more configurations. The configurations may include the configured uplink grant configuration identifiers.

[0302] In one embodiment, the UE may transmit one or more RRC messages including at least one of one or more cell identities of the first cell and one or more configured uplink grant configuration identifiers of the one or more configurations.

[0303] In one embodiment, the one or more RRC messages may include at least one of one or more cell identities of the first cell and one or more configured uplink grant configuration identifiers of one or more configurations of the first cell. For example, the UE may select the second cell. The UE may initiate an RRC procedure to establish an RRC connection via the second cell. Based on the initiation, the UE may determine to release at least one of the at least one configured uplink grant of the one or more configurations of the at least one configured uplink grant of the first cell or one or more configurations of the at least one configured uplink grant of the first cell. Based on the determination, the UE may transmit one or more RRC messages.

[0304] In one embodiment, the at least one first RRC message may include one or more configurations of the at least one configured uplink grant. The one or more configured configured uplink grant configurations may each include one configured uplink grant configuration identifier. Each configured uplink grant configuration may be associated with at least one cell identity. The UE may transmit one or more RRC messages indicating releasing at least one of the one or more configured uplink grants of the first cell of the one or more configurations or one or more configurations of the at least one configured uplink grant of the first cell. The one or more RRC messages may include a list of configured uplink grant configuration identifiers and at least one cell identity associated with a single configuration. For example, the UE may transmit one or more RRC messages including a list associated with the first cell. The first cell may include one or more cells different from the second cell.

[0305] In one embodiment, the UE may receive three configurations, where the first configuration includes a configuration of at least one configured uplink grant of a first cell, the second configuration includes a configuration of at least one configured uplink grant of a second cell, and the third configuration includes a configuration of at least one configured uplink grant of a third cell. The UE may select the second cell. The UE may decide to establish an RRC connection via the second cell. Based on the determination, the UE may transmit one or more RRC messages indicating at least one configured uplink grant of the first configuration and the third configuration, or at least one release of the first configuration and the third configuration. The one or more RRC messages may include at least one of a configured uplink grant configuration identifier of the first configuration and a cell identity of the first cell, and a configured uplink grant configuration identifier of the third configuration and a cell identity of the third cell. The UE may decide to establish an RRC connection not using a configured uplink grant of the second configuration. For example, the UE may not transmit one or more RRC messages (e.g., an RRC Setup Request message) that are not in response to a transmission using at least one configured uplink grant of the second configuration. Based on the determination, the one or more RRC messages may include at least one of a configured uplink grant configuration identifier of the second configuration and a cell identity of the second cell. Based on the determination, the UE may decide to release at least one configured uplink grant of the second configuration or at least one of the second configurations. Based on the determination, the one or more RRC messages may include at least one of a configured uplink grant configuration identifier of the second configuration and a cell identity of the second cell. For example, the UE may transmit one or more RRC messages without using at least one configured uplink grant of the first configuration or the third configuration.For example, the UE may transmit one or more RRC messages (e.g., an RRC Setup Request message) that are not responsive to a transmission using at least one configured uplink grant of the first configuration or the third configuration. Based on the transmission, the UE may determine to release the first configuration and the third configuration. The UE may determine to use a configured uplink grant of the second configuration to transmit the one or more RRC messages. Based on the determination, the one or more RRC messages may include a list including at least one of a configured uplink grant configuration identifier of the first configuration and a cell identity of the first configuration, a configured uplink grant configuration identifier of the third configuration and a cell identity of the third configuration.

[0306] In one embodiment, the UE may receive a confirmation indication that one or more configurations are to be released in response to the one or more RRC messages. The UE may release one or more configurations of the at least one configured uplink grant based on at least one of receiving the confirmation indication or receiving an RRC response message in response to the one or more RRC messages. For example, the UE may receive an RRC response message in response to the one or more RRC messages. The RRC response message may include the confirmation indication. Based on the RRC response message, the UE may release the one or more configurations.

[0307] In one embodiment, the confirmation indication may include one or more indications. The indication may indicate that one of the one or more configurations is to be released. The UE may receive a confirmation indication including the one or more indications. Based on the one or more indications, the UE may release one or more configurations associated with the one or more indications. For example, the UE may retain one or more configurations based on at least one of not receiving a confirmation indication (e.g., one or more indications) associated with the one or more configurations or receiving an indication to retain the one or more configurations. The RRC response message may include an indication. For example, the UE may suspend one or more configurations based on at least one of not receiving a confirmation indication (e.g., one or more indications) associated with the one or more configurations or receiving an indication to stop the one or more configurations. The UE may receive an indication to resume the one or more configurations (e.g., the suspended one or more configurations). Based on receiving an indication to resume the one or more configurations, the UE may resume the one or more configurations associated with the resume indication. The indication to maintain or suspend or resume may include a configured uplink grant configuration ID. The RRC response message may include an indication or a confirmation indication.

[0308] In one embodiment, the UE may select the second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may initiate an RRC procedure to establish the RRC connection. For example, based on the initiation via the second cell, the UE may determine to release at least one of the configured uplink grants of one or more configurations of the first cell, or at least one of the one or more configurations of the first cell. Based on the determination, the UE may transmit one or more RRC messages indicating the release of at least one of the configured uplink grants of one or more configurations of the first cell, or at least one of the one or more configurations of the first cell. The RRC procedure includes an RRC connection establishment procedure.

[0309] In one embodiment, the UE may transmit one or more RRC messages including one or more cell identities of the one or more configurations and at least one of one or more configured uplink grant configuration identifiers of the one or more configurations. The one or more configurations may not include a configuration of the second cell. The UE may receive an RRC response message in response to the one or more RRC messages. Based on the RRC response message, the UE may release the one or more configurations. For example, based on determining to establish an RRC connection via the second cell, the UE may release at least one of the configured uplink grant of the first cell of the one or more configurations, or one or more configurations of the configured uplink grant of the first cell of the one or more configurations. The UE may transmit one or more RRC messages indicating releasing at least one of the configured uplink grant of the first cell of the one or more configurations, or one or more configurations of the configured uplink grant of the first cell of the one or more configurations. Based on the RRC response message, the UE may release the one or more configurations. For example, the UE may store at least one of the configured uplink grant configuration identifiers of the one or more configurations, one or more cell identities associated with the one or more configurations. For example, based on determining to establish an RRC connection via the second cell, the UE may store at least one of a configured uplink grant configuration identifier of the one or more configurations, one or more cell identities associated with the one or more configurations. In response to storing, the UE may release the one or more configurations. In response to releasing, the UE may transmit one or more RRC messages including at least one of the one or more cell identities of the one or more configurations, one or more configured uplink grant configuration identifiers of the one or more configurations.

[0310] In one embodiment, the one or more RRC messages may include at least one of an RRC setup request message, an RRC setup complete message, a configured uplink grant configuration request message, a configured uplink grant configuration release request message, and a UE information request message.

[0311] In one example, the UE may receive an RRC setup message in response to the RRC setup request message. The UE may send an RRC setup complete message in response to the RRC setup message.

[0312] In one embodiment, the RRC SETUP REQUEST message may include at least one of a Serving Temporary Mobile Subscriber Identity (S-TMSI) or a random value for contention resolution.

[0313] In one embodiment, the RRC Setup Complete message may include at least one of one or more cell identities of a cell associated with the one or more configurations and one or more configured uplink grant configuration identifiers of the one or more configurations. For example, the RRC Setup Complete message may include a list of configured uplink grant configuration identifiers and cell identities associated with the configured uplink grant configuration identifiers, where the configured uplink grant configuration identifiers are configured uplink grant configuration identifiers of the one or more configurations.

[0314] In one embodiment, the configured uplink grant configuration release request message may include at least one of one or more configured cell identities and one or more configured configured uplink grant configuration identifiers. For example, the configured uplink grant configuration release request message may include configured uplink grant configuration identifiers and a list of cell identities associated with the configured uplink grant configuration identifiers, where the configured uplink grant configuration identifiers are the one or more configured configured uplink grant configuration identifiers. The UE may transmit the configured uplink grant configuration release request message in response to transitioning to the RRC connected state. For example, the UE may transmit the configured uplink grant configuration release request message via SRB2.

[0315] In one embodiment, based on receiving the RRC setup message, the UE may release at least one of the one or more configured uplink grants of the first cell or one or more configurations of the at least one configured uplink grant of the first cell.

[0316] In one embodiment, the UE may select the second cell, eg, a UE in RRC idle state may select the second cell based on cell (re)selection.

[0317] In one embodiment, the second cell is different from the first cell. The second base station of the second cell may be different from the first base station of the first cell.

[0318] In one embodiment, the cell identity may include at least one of a physical cell identity or a global cell identity. For example, the cell identity of the first cell may include at least one of a physical cell identity or a global cell identity.

[0319] In one embodiment, the UE may determine to establish an RRC connection based on at least one of having uplink data to transmit or receiving a paging message, For example, the UE may initiate an RRC procedure to establish an RRC connection based on at least one of having uplink data to transmit or receiving a paging message.

[0320] In one embodiment, the RRC response message may include at least one of an RRC SETUP message, an RRC RECONFIGURATION message, and a UE INFO...

Claims

1. A method comprising: A base station central unit (BS-CU) receives one or more radio resource control (RRC) messages from a wireless device, the one or more RRC messages comprising: a resume identity for the wireless device; indicating a release, by the wireless device, of a first configured uplink grant configuration of a first cell for an RRC inactive state or an RRC idle state of the wireless device; sending a message to a base station distributed unit (BS-DU) associated with the first cell indicating the release of the first configured uplink grant configuration; A method comprising:

2. The method of claim 1, further comprising the BS-CU receiving the first configured uplink grant configuration of the first cell from the BS-DU.

3. The method of claim 1, wherein the message indicating the release includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration.

4. The method of claim 1, wherein the message indicating the release includes a first cell identifier of the first cell.

5. The method of claim 1, further comprising determining that the first cell is associated with the BS-DU.

6. The method of claim 1, wherein the message indicating the release is an F1 application protocol message. determining, based on a first cell identifier, that the BS-DU is associated with the first cell; transmitting the message to the BS-DU based on determining that the BS-DU is associated with the first cell; The method of claim 1 further comprising:

8. The method of claim 1, wherein the first configured uplink grant configuration for the RRC inactive state or the RRC idle state is associated with a small data transmission (SDT) procedure.

9. A base station central unit (BS-CU), comprising one or more processors and a memory for storing instructions, the instructions, when executed by the one or more processors, receiving one or more radio resource control (RRC) messages from a wireless device, the one or more RRC messages comprising: a resume identity for the wireless device; indicating a release, by the wireless device, of a first configured uplink grant configuration of a first cell for an RRC inactive state or an RRC idle state of the wireless device; sending a message to a base station distributed unit (BS-DU) associated with the first cell indicating the release of the first configured uplink grant configuration; The BS-CU causes the BS-CU to perform the above.

10. The BS-CU of claim 9, wherein the instruction further causes the BS-CU to receive the first configured uplink grant configuration of the first cell from the BS-DU.

11. A BS-CU as described in claim 9, wherein the message indicating the release includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration.

12. The BS-CU of claim 9, wherein the message indicating the release includes a first cell identifier of the first cell.

13. A BS-CU as described in claim 9, wherein the instruction further causes the BS-CU to determine that the first cell is associated with the BS-DU.

14. The BS-CU of claim 9, wherein the message indicating the release is an F1 application protocol message.

15. The instruction comprises: determining, based on a first cell identifier, that the BS-DU is associated with the first cell; transmitting the message to the BS-DU based on determining that the BS-DU is associated with the first cell; The BS-CU of claim 9, further comprising:

16. The BS-CU of claim 9, wherein the first configured uplink grant configuration for the RRC inactive state or the RRC idle state is associated with a small data transmission (SDT) procedure.

17. A non-transitory computer-readable medium containing instructions that, when executed by one or more processors, receiving one or more radio resource control (RRC) messages from a wireless device, the one or more RRC messages comprising: a resume identity for the wireless device; indicating a release, by the wireless device, of a first configured uplink grant configuration of a first cell for an RRC inactive state or an RRC idle state of the wireless device; sending a message to a base station distributed unit (BS-DU) associated with the first cell indicating the release of the first configured uplink grant configuration; A non-transitory computer-readable medium that causes the one or more processors to

18. The non-transitory computer-readable medium of claim 17, wherein the instructions cause the one or more processors to receive from the BS-DU the first configured uplink grant configuration for the first cell.

19. The non-transitory computer-readable medium of claim 17, wherein the message indicating the release includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration.

20. The message indicating the release comprises: a first configured uplink grant configuration identifier of the first configured uplink grant configuration; or a first cell identifier of the first cell; 20. The non-transitory computer readable medium of claim 17, comprising at least one of:

Citation Information

Patent Citations

  • Maintaining, suspending, or modifying existing PUR configuration in response to a UE entering into RRC connected mode

    US20220167457A1

  • NAS Recovery in a Wireless Communication Network

    US20220361275A1