In response to the UE entering RRC connected mode, maintain, suspend or modify the existing PUR configuration
By negotiating between user equipment and base station, the PUR configuration of user equipment in RRC connection mode is solved, the overlap between PUR configuration and RRC connection is achieved, flexible management of resources and effective update of configuration is achieved, and the Network efficiency and flexibility.
Patent Information
- Application Number
- CN202080028941.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-02-15
- Filing Date
- 2020-02-11
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-02-11
AI Technical Summary
The prior art is difficult to handle overlapping scenarios between the uplink resource (PUR) configuration preconfigured by a user equipment in idle mode and the radio resource control (RRC) connection, especially in the case of temporary RRC connections. Configuration issues.
Through negotiation between user equipment and base station, determine how to handle existing PUR configuration in RRC connection mode, including pausing, maintaining or modifying PUR configuration, combining PUR and PUSCH resources, releasing or postponing PUR transmission, ensuring the effectiveness of resources Utilization and configuration updates.
It realizes flexible management of PUR configuration in RRC connection mode, ensures optimized utilization of resources, avoids configuration failure and resource waste, and improves network flexibility and efficiency.
Smart Images

Figure CN113692779B_ABST
Abstract
Description
Technical Field
[0001] The present invention generally relates to communications using preconfigured uplink resources (PUR) for user equipment (UE), and more particularly to a radio resource control (RRC) connection for a UE configured with a PUR. Background Art
[0002] This section is intended to provide a background or context for the invention disclosed below. The description herein may include concepts that can be pursued, but not necessarily concepts that have been previously conceived, implemented, or described. Therefore, unless explicitly indicated herein, what is described in this section is not prior art to the description in this application and cannot be admitted as prior art by inclusion in this section. At the beginning of the detailed description section, the abbreviations that may be found in the specification and / or the drawings are defined as follows.
[0003] A new work item (WI) for further enhancement of Machine Type Communication (MTC) / Narrowband Internet of Things (NB-IoT) was approved for Release 16 (Rel-16). One of the goals of this WI is to support transmission on preconfigured uplink resources (PUR) for user equipment (UE) with valid timing advance in idle mode or connected mode. Currently, only dedicated PUR (D-PUR) in idle mode is supported. Dedicated means that a unique or dedicated time-frequency resource is reserved for each UE configured with a PUR. In RAN1#95, the following D-PUR agreement related to the examples in this article was formulated.
[0004] The first agreement is as follows: For dedicated PURs in idle mode, uplink (UL) grants for hybrid automatic repeat request (HARQ) retransmissions are transmitted in the MTC physical downlink control channel (MPDCCH) search space. Details on the search space (e.g., UE-specific search space (USS) or common search space (CSS)) are for further study (FFS).
[0005] The second protocol is as follows: For dedicated PUR in idle mode, the UE may expect an explicit acknowledgment (ACK) when the PUR transmission is successfully decoded by the eNB. Whether the ACK is sent on the MPDCCH (layer 1) and / or the physical downlink shared channel (PDSCH) (layer 2 / 3) is for further discussion. This will be included in the contact statement (LS) to RAN2, RAN4.
[0006] The third protocol is as follows: For a dedicated PUR in idle mode, when the PUR transmission is not successfully decoded by the eNB, the UE may expect the following:
[0007] 1) UL grant for retransmission on MPDCCH, or
[0008] 2)FFS:NACK, or
[0009] 3) FFS: No explicit ACK.
[0010] In the RAN2 email discussion discussing various D-PUR related signaling, email discussion [104#43][eMTC&NB-IoT R16] D-PUR report, the following question was raised:
[0011] Question 26. Are there other scenarios for the version assigned by D-PUR and ways to apply it?
[0012] An internal review of this issue by the inventors raised another undisclosed question:
[0013] How should Radio Resource Control (RRC) connections between and overlapping PUR opportunities be handled? Summary of the invention
[0014] This section is intended to include examples and is not intended to be limiting.
[0015] In an exemplary embodiment, a method is disclosed, which includes determining at a user equipment configured with an idle mode configuration for using preconfigured uplink resources that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection. The method includes performing, by the user equipment, initial access to a network for the radio resource control connection. The method also includes transitioning, by the user equipment, from the radio resource control idle mode to the radio resource control connected mode. The method includes the user equipment performing, at least for a duration of the radio resource control connected mode, one of suspending the idle mode configuration or maintaining the idle mode configuration.
[0016] Additional exemplary embodiments include a computer program comprising code for performing the method of the previous paragraph when the computer program is run on a processor. A computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer readable medium carrying computer program code implemented therein for use with a computer. Another example is a computer program according to this paragraph, wherein the program can be directly loaded into the internal memory of a computer.
[0017] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, together with the one or more processors, cause the apparatus to at least perform the following operations: determine at a user equipment configured with an idle mode configuration for using preconfigured uplink resources that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection; perform initial access to a network for the radio resource control connection by the user equipment; transition from the radio resource control idle mode to the radio resource control connected mode by the user equipment; and perform one of suspending the idle mode configuration or maintaining the idle mode configuration by the user equipment for at least the duration of the radio resource control connected mode.
[0018] An exemplary computer program product includes a computer-readable storage medium carrying computer program code implemented therein for use with a computer. The computer program code includes: code for determining at a user equipment configured with an idle mode configuration for using preconfigured uplink resources that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection; code for performing, by the user equipment, initial access to a network for the radio resource control connection; code for transitioning, by the user equipment, from the radio resource control idle mode to the radio resource control connected mode; and code for the user equipment to perform one of suspending the idle mode configuration or maintaining the idle mode configuration for at least the duration of the radio resource control connected mode.
[0019] In another exemplary embodiment, an apparatus includes: a component for determining, at a user equipment configured with an idle mode configuration for using preconfigured uplink resources, that data not associated with the preconfigured uplink resources will be sent or received via a radio resource control connection; a component for performing initial access to a network by the user equipment for the radio resource control connection; a component for transitioning from a radio resource control idle mode to a radio resource control connected mode by the user equipment; and a component for the user equipment to perform one of suspending the idle mode configuration or maintaining the idle mode configuration for at least the duration of the radio resource control connected mode.
[0020] In an exemplary embodiment, a method is disclosed, the method including receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection. The method includes determining, at the base station, that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources. The method also includes converting, by the base station, the user equipment from the RRC idle mode to the RRC connected mode. The method includes performing communications between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or the RRC connection corresponding to the conversion to the RRC connected mode.
[0021] Additional exemplary embodiments include a computer program comprising code for performing the method of the previous paragraph when the computer program is run on a processor. A computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer readable medium carrying computer program code implemented therein for use with a computer. Another example is a computer program according to this paragraph, wherein the program can be directly loaded into the internal memory of a computer.
[0022] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, together with the one or more processors, cause the apparatus to at least perform the following operations: receiving an initial access to a network for a radio resource control (RRC) connection at a base station in a wireless communication network; determining at the base station that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources; converting the user equipment from the RRC idle mode to the RRC connected mode by the base station; and performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or the RRC connection corresponding to the conversion to the RRC connected mode.
[0023] An exemplary computer program product includes a computer-readable storage medium carrying computer program code implemented therein for use with a computer. The computer program code includes: code for receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection; code for determining, at the base station, that a user equipment is configured with an idle mode configuration for use of preconfigured uplink resources; code for converting, by the base station, the user equipment from the RRC idle mode to the RRC connected mode; and code for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or the RRC connection corresponding to the conversion to the RRC connected mode.
[0024] In another exemplary embodiment, an apparatus includes: a component for receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection; a component for determining, at the base station, that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources; a component for transitioning, by the base station, the user equipment from the RRC idle mode to the RRC connected mode; and a component for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or the RRC connection corresponding to the transition to the RRC connected mode. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] In the attached picture:
[0026] Figure 1 is a block diagram of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced;
[0027] Figure 2 is a logic flow diagram for an RRC connection with a PUR configuration according to an exemplary embodiment;
[0028] Figure 3 is an illustration of a scenario addressed by an exemplary embodiment;
[0029] Figure 4 is a signaling diagram between a UE and an eNB in an exemplary embodiment and illustrating two methods of RRC reconfiguration;
[0030] Figure 5 is an illustration of another scenario in which a UE transmits packets associated with a D-PUR via an EDT procedure prior to a D-PUR opportunity in an exemplary embodiment;
[0031] Figure 6 is a logic flow chart for maintaining, suspending or modifying an existing PUR configuration executed by a UE in response to the UE entering an RRC connected mode; and
[0032] Figure 7 A logic flow diagram is provided for maintaining, suspending or modifying an existing PUR configuration executed by a network element in response to a UE entering RRC connected mode. DETAILED DESCRIPTION
[0033] The following abbreviations that may be found in the specification and / or drawings are defined as follows:
[0034] 3GPP Third Generation Partnership Project
[0035] 5G Fifth Generation
[0036] 5GC 5G Core Network
[0037] ACK
[0038] AMF Access and Mobility Management Function
[0039] comm. communication
[0040] CSS Public Search Space
[0041] CU Central Unit
[0042] DCI Downlink Control Identifier
[0043] D-PUR Dedicated pre-configured uplink resources
[0044] D-PUR-RNTI D-PUR Radio Network Temporary Identifier
[0045] DU Distributed Unit
[0046] EDT Early Data Transfer
[0047] eNB (or ENB) Evolved Node B (e.g., LTE base station)
[0048] EN-DC E-UTRA-NR Dual Connectivity
[0049] en-gNB or En-gNB A node that provides NR user plane and control plane protocol termination to the UE and acts as a secondary node in EN-DC
[0050] E-UTRA Evolved Universal Terrestrial Radio Access, also known as LTE wireless access technology
[0051] FFS For further study
[0052] gNB (or gNodeB) is a base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC via the NG interface.
[0053] HARQ Hybrid Automatic Repeat Request
[0054] I / F Interface
[0055] IMSI International Mobile Subscriber Identity
[0056] IoT
[0057] LTE Long Term Evolution
[0058] MAC Media Access Control
[0059] MME Mobility Management Entity
[0060] MO Mobile Origination
[0061] MPDCCH MTC Physical Downlink Control Channel
[0062] MT Mobile Termination
[0063] MTC Machine Type Communication
[0064] NACK Negative Acknowledgement
[0065] NB-IoT Narrowband Internet of Things
[0066] ng or NG new generation
[0067] ng-eNB or NG-eNB Next Generation eNB
[0068] NPDCCH NB-IoT Physical Data Control Channel
[0069] NPUSCH-F2 NPUSCH format 2
[0070] NR New Radio
[0071] N / W or NW network
[0072] PDCP Packet Data Convergence Protocol
[0073] PDSCH Physical Downlink Shared Channel
[0074] PHY Physical Layer
[0075] PUR Preconfigured Uplink Resources
[0076] PUSCH Physical Uplink Shared Channel
[0077] RAN Radio Access Network
[0078] Rel version
[0079] RLC Radio Link Control
[0080] RNTI Radio Network Temporary Identifier
[0081] RRH Remote Radio Head
[0082] RRC Radio Resource Control
[0083] RU Radio Unit
[0084] Rx Receiver
[0085] SDAP Service Data Adaptation Protocol
[0086] SGW Service Gateway
[0087] SMF session management functions
[0088] SPS Semi-Persistent Scheduling
[0089] S-TMSI System Architecture Evolution - Temporary Mobile Subscriber Identity
[0090] TA Timing Advance
[0091] TS Technical Specifications
[0092] Tx Transmitter
[0093] UE User Equipment (e.g., wireless device)
[0094] UL Uplink
[0095] UPF User Plane Function
[0096] USS UE-specific search space
[0097] WI Work Items
[0098] WUS wake-up signal
[0099] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. All embodiments described in this detailed description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention, and do not limit the scope of the invention which is defined by the claims.
[0100] For ease of reference, the remainder of the disclosure is divided into several sections. The first section describes a possible exemplary system, the second section describes an exemplary process, the third section describes additional exemplary details, and the fourth and final section has additional comments.
[0101] I. Possible Exemplary Systems
[0102] The exemplary embodiments herein describe techniques for maintaining, suspending or modifying an existing PUR configuration in response to a UE entering an RRC connected mode (also referred to herein as a state).Additional description of these techniques is presented after a system in which the exemplary embodiments may be used is described.
[0103] Steering Figure 1 , which shows a block diagram of one possible and non-limiting exemplary system in which exemplary embodiments may be practiced. A user equipment (UE) 110, a radio access network (RAN) node 170, and (multiple) network elements 190 are illustrated. Figure 1In the embodiment of the present invention, a user equipment (UE) 110 wirelessly communicates with a wireless network 100. A UE is a wireless device that can access a wireless network and is likely to be an MTC / IoT UE device. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected by one or more buses 127. Each of the one or more transceivers 130 includes a receiver (Rx) 132 and a transmitter (Tx) 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of wires on a motherboard or integrated circuit, optical fiber or other optical communication devices, etc. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a PUR communication (Comm) module 140, which includes one or both of the 140-1 and / or 140-2 parts, which can be implemented in a variety of ways. The PUR Comm module 140 may be implemented in hardware as a PUR communication module 140-1, such as being implemented as part of one or more processors 120. The PUR communication module 140-1 may also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, the PUR communication module 140 may be implemented as a PUR communication module 140-2, which is implemented as a computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and the computer program code 123 may be configured to perform one or more operations as described herein with the user equipment 110 with the one or more processors 120. The UE 110 communicates with the RAN node 170 via the wireless link 111.
[0104] The RAN node 170 is a base station that provides access to the wireless network 100 by wireless devices such as the UE 110. The RAN node 170 may be, for example, a base station for 5G (also known as New Radio (NR)), or a base station for LTE, an eNB (evolved Node B). The following assumes the latter (eNB), but 5G is also possible. In 5G, the RAN node 170 may be a NG-RAN node, which is defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (e.g., (multiple) network elements 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. An NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and (multiple) distributed units (DU) (gNB-DU), of which DU 195 is shown. Note that a DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of the gNB or the RRC and PDCP protocols of the en-gNB, and controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. The F1 interface is illustrated as reference numeral 198, although reference numeral 198 also illustrates a link between a remote element of the RAN node 170 and a centralized element of the RAN node 170, such as a link between a gNB-CU 196 and a gNB-DU 195. The gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of the gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-CU supports one or more cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface 198 connected to the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of the RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under the control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved Node B) base station for LTE (Long Term Evolution) or any other suitable base station.
[0105] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (multiple N / WI / F) 161, and one or more transceivers 160 interconnected by one or more buses 157. Each of the one or more transceivers 160 includes a receiver (Rx) 162 and a transmitter (Tx) 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include (multiple) processors 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory / memories and (multiple) processors and / or other hardware, but these are not shown.
[0106] The RAN node 170 includes a PUR communication (Comm.) module 150, which includes one or both of the 150-1 and / or 150-2 parts, which can be implemented in a variety of ways. The PUR Comm module 150 can be implemented in hardware as a PUR communication module 150-1, such as being implemented as part of one or more processors 152. The PUR communication module 150-1 can also be implemented as an integrated circuit or through other hardware such as a programmable gate array. In another example, the PUR communication module 150 can be implemented as a PUR communication module 150-2, which is implemented as a computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and the computer program code 153 can be configured to, together with one or more processors 120, cause the RAN node 170 to perform one or more operations as described herein. Note that the functionality of the PUR communication module 150 can be distributed, such as distributed between the DU 195 and the CU 196, or implemented only in the DU 195.
[0107] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more RAN nodes 170 communicate using, for example, link 176. Link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other appropriate interfaces for other standards.
[0108] The one or more buses 157 may be an address bus, a data bus, or a control bus, and may include any interconnection mechanism, such as a series of wires on a motherboard or integrated circuit, an optical fiber or other optical communication device, a wireless channel, etc. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for a gNB implementation for 5G, while other elements of the RAN node 170 may be physically located at a different location from the RRH / DU, and the one or more buses 157 may be partially implemented as, for example, a fiber optic cable or other appropriate network connection to connect other elements of the RAN node 170 (e.g., a central unit (CU), gNB-CU) to the RRH / DU 195. Reference numeral 198 also indicates those appropriate network links (multiple).
[0109] The wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to further networks, such as a telephone network and / or a data communication network (e.g., the Internet), via one or more links 181. Such core network functions for 5G may include access and (multiple) mobility management functions ((multiple) AMFs) and / or user plane functions (UPFs) and / or (multiple) session management functions ((multiple) SMFs). Such core network functions for LTE may include MME (mobile management entity) / SGW (serving gateway) functions. These are merely exemplary functions that may be supported by (multiple) network elements 190, and it is noted that both 5G and LTE functions may be supported. The RAN node 170 is coupled to the network element 190 via a link 131. The link 131 may be implemented, for example, as an NG interface for 5G or an S1 interface for LTE or other appropriate interfaces for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected by one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and computer program code 173 are configured to, together with the one or more processors 175, cause the network element 190 to perform one or more operations.
[0110] Wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functions into a single, software-based managed entity, a virtual network. Network virtualization is related to platform virtualization, often in conjunction with resource virtualization. Network virtualization is categorized as external, combining many networks or portions of networks into virtual units, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities resulting from network virtualization are still implemented to some extent using hardware such as processors 152 or 175 and memories 155 and 171, and that such virtualized entities also produce technical effects.
[0111] Computer readable memories 125, 155, and 171 may be of any type suitable for the local technical environment and may be implemented using any appropriate data storage technology, such as semiconductor-based storage devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. Computer readable memories 125, 155, and 171 may be components for performing storage functions. Processors 120, 152, and 175 may be of any type suitable for the local technical environment and may include one or more processors in a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Processors 120, 152, and 175 may be components for performing functions, such as controlling UE 110, RAN node 170, and other functions as described herein.
[0112] Generally, various embodiments of user device 110 may include, but are not limited to, cellular phones such as smart phones with wireless communication capabilities, tablet computers, personal digital assistants (PDAs), portable computers with wireless communication capabilities, image capture devices such as digital cameras with wireless communication capabilities, gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, Internet appliances allowing wireless Internet access and browsing, tablet computers with wireless communication capabilities, and portable units or terminals including such functional combinations.
[0113] II. Exemplary Process
[0114] Having thus introduced a suitable but non-limiting technical context for the practice of exemplary embodiments of this invention, the exemplary embodiments will now be described with greater specificity.
[0115] We envision that devices using PUR may have long quiet periods in idle mode between PUR transmissions. For example, a home smart meter device using PUR may wait a full week before sending a compressed summary of usage for that week. But during that week between PUR transmissions, urgent unscheduled events, such as temporary power cuts or network-initiated updates from the device (e.g., UE) side, may require the same device to establish a temporary RRC connection with the network. What has not been discussed and may influence the standard is how to handle such scenarios, and whether the pre-existing PUR configuration should be allowed to continue, or whether the pre-existing PUR configuration should be reconfigured.
[0116] As mentioned above, the closest question raised so far in this area is the following: "Q26. Are there other scenarios for the release of D-PUR allocation and methods for applying the release?" Furthermore, in the RAN2 email discussions discussing the various D-PUR related signaling mentioned above, the issue of how to handle D-PUR configuration in the context of a temporary RRC connection has not been discussed.
[0117] The exemplary embodiments address how to handle a scenario where an RRC connection with a network is to be established by a UE and the UE already has an existing PUR configuration and the data for the RRC connection is not associated with the PUR configuration. In more detail, the exemplary embodiments provide examples of how to operate (e.g., establish, modify, release) (e.g., new, spontaneous, unscheduled) RRC connections in parallel with preconfigured UL resources (PUR) in NB-IoT (MTC / IoT UE devices and base stations). The PUR configuration can be dedicated (i.e., the UE is assigned a dedicated or unique time / frequency resource) or shared (i.e., several UEs are assigned the same or overlapping time / frequency resources). Although much of the disclosure herein relates to D-PUR, it should be noted that the techniques described herein are generally applicable to PURs, including, for example, shared PURs (S-PURs). A dedicated PUR is also referred to as a contention-free PUR (i.e., there is no contention on the time / frequency resources), while a shared PUR is also referred to as a contention-based PUR (i.e., there may be contention on the time / frequency resources because multiple UEs are assigned the same or overlapping time / frequency resources). Two situations may occur: 1) an RRC transmission (e.g., a transmission scheduled by the eNB when the UE is in RRC connected mode) overlaps with a D-PUR transmission and the UE is reconfigured to defer the D-PUR transmission or to combine (e.g., include) the data of the D-PUR transmission into an RRC transmission; and 2) the RRC transmission precedes the next scheduled D-PUR transmission and the UE may anticipate the data transmission foreseen in the D-PUR, e.g., and sends the data of the D-PUR in the RRC transmission. The first situation (1) is, for example, Figure 3 is illustrated in , and the second case (2) is for example in Figure 5 is shown in the figure.
[0118] Regarding additional details on PURs, consider the following. Dedicated preconfigured UL resources are defined as PUSCH resources used by a single UE: the PUSCH resources are time-frequency resources; and the dedicated PUR is contention-free. Contention-free shared preconfigured UL resources (CFS PURs) are defined as PUSCH resources used simultaneously by more than one UE: the PUSCH resources are at least time-frequency resources; and the CFS PUR is contention-free. Contention-based shared preconfigured UL resources (CBS PURs) are defined as PUSCH resources used simultaneously by more than one UE: the PUSCH resources are at least time-frequency resources; and the CBS PUR is contention-based (the CBS PUR may require contention resolution). All of these types of PURs can be addressed by the techniques presented herein.
[0119] The following is a description of actions taken by the UE 110 and the RAN node 170, which will be referred to as the eNB 170 below. Figure 2 , which is a logic flow diagram of an RRC connection with a PUR configuration according to an exemplary embodiment. Figure 2 The operations of one or more exemplary methods, the results of execution of computer program instructions implemented on a computer readable memory, functions performed by logic implemented in hardware, and / or interconnected components for performing functions according to exemplary embodiments are illustrated. The UE 110 performs the functions in the blocks under the control of the PUR communication module 140, and the eNB 170 performs the functions in the blocks under the control of its PUR communication module 150.
[0120] Continue to describe Figure 2 Before. Note that whether PUR and RRC transmissions use the same or different resources depends on the eNB. PUR resources are preconfigured (i.e. fixed), while RRC resources are dynamic (i.e. scheduled by the eNB). When the UE performs a PUR transmission, the UE always knows where to transmit based on the existing PUR configuration. When the UE performs an RRC transmission, the resources are provided by the eNB per transmission via the scheduling grant DCI.
[0121] Assume that UE 110 is in idle mode and has been configured with a PUR configuration. See block 210. Mobile originated (MO) or mobile terminated (MT) data arrives (e.g., UE is paged or performs random access). See block 215. Initial access is made by UE 110, which is then configured (by the network) to be in RRC connected mode for data transfer. See block 220.
[0122] In block 225, the network (e.g., eNB 170) determines that the UE has an ongoing PUR configuration configured. Methods for implementing this include, but are not limited to, the following methods:
[0123] 1) After full RRC connection establishment, the network (eg, eNB 170) can determine it from the IMSI / S-TMSI.
[0124] 2) During RRC connection establishment, the UE may forward an identifier, such as the PURRNTI allocated during PUR configuration and / or a UE-specific identifier (which may be important for shared PURs), indicating what PUR configuration (dedicated or shared) the identifier is allocated in. Alternatively, the network may also determine it from the IMSI / S-TMSI during RRC connection establishment.
[0125] There may be an explicit indication / negotiation between the network and the UE for idle mode PUR configuration. That is, an indication (or negotiation) that helps the network associate the existing PUR configuration with the same UE now transitioning to RRC connected mode. Reference box 230 describes it. There may be an explicit indication / negotiation between the network and the UE. Reference box 230 describes it.
[0126] In block 230, in the absence of explicit indication / negotiation between the network and the UE, one of the following options may be adopted:
[0127] a) When the UE is in RRC connected mode, the UE maintains its idle mode PUR configuration and may continue to use that configuration during RRC connected mode (i.e., the UE may continue to use the time / frequency resources allocated in the PUR configuration). See block 235. Note that if the UE does not continue to use that configuration, it is up to the UE to determine whether to request and obtain another PUR configuration.
[0128] When the UE continues to use the time / frequency resources allocated in the PUR configuration to transmit uplink data, it is assumed that there is a search space associated with the PUR configuration for the UE to receive DCI and / or ACK / NACK. In addition, the UE will also be configured with a control channel search space associated with connected mode transmission and reception. Note that the overlap of PDSCH with PUR DCI is only an issue for half-duplex devices that cannot transmit (PUSCH) and receive (DCI) simultaneously. Therefore, in the case where the PUSCH or PDSCH allocated in RRC connected mode (half-duplex devices only) overlaps with the PUR DCI search space and / or PUR PUSCH, the following options exist:
[0129] 1) The UE monitors only one control channel search space at a time and the connected mode search space takes precedence over the D-PUR search space.Depending on the configuration of the PDSCH and search space, the UE may continue to monitor both the PUR and connected mode PDSCH search spaces.
[0130] 2) When there is a connection mode transmission, the PUR counter / timer used for PUR release is paused or reset.
[0131] b) The UE suspends its use of the idle mode PUR configuration for the duration of the RRC connection, but continues to maintain the PUR configuration in its context. See block 240. That is, although the UE is not allowed to use the PUR (the use is "suspended") while the UE is in RRC connected mode, the UE does not discard the configuration information. When the UE is released back to RRC idle mode (i.e., after the duration of the RRC connection), the UE resumes the use of the PUR configuration. Therefore, when the UE is released back to idle mode, if the validity of the PUR configuration has not expired, the UE resumes its use of the PUR configuration with the updated TA value.
[0132] With explicit indication / negotiation between the network and the UE, via layer 2 and / or layer 3 signaling, the network may perform one of the following operations with respect to the UE idle mode PUR configuration (see block 245):
[0133] 1) Start immediately (i.e., in response to the UE transitioning to RRC connected mode or state) and suspend PURs (i.e., authorization / applicability for the UE to suspend PUR configuration) for the duration of the time the UE is in RRC connected mode (see block 250). For "immediate" suspension of PURs, there is always a response time, based on processing indications, etc. Therefore, in response to the UE transitioning to RRC connected mode, PURs will be suspended, and ideally will be performed as quickly as the UE can suspend PURs. While the UE is in RRC connected mode, the eNB 170 can reallocate resources. Although the UE does not have access to the PUR during the time the UE is in RRC connected mode, the UE maintains the PUR configuration in its context. When the UE is in RRC connected mode, the PUR counter / timer for PUR release is either suspended or continues to run. If the PUR counter / timer for PUR release is suspended when the UE is in RRC connected mode, they can be continued again after the UE leaves RRC connected mode. When the UE is released back to idle mode, the validity of the PUR configuration is restored if the configuration has not expired.
[0134] 2) Release the PUR with immediate (eg, fast, in response to indication / negotiation) transfer of data intended for the PUR but via the RRC connection. See block 252. That is, release of the PUR means that these PUR configurations are no longer reserved for the UE.
[0135] 3) Release the PUR without immediate (eg, quickly, in response to an indication / negotiation) transmission of data intended for the PUR. See block 254.
[0136] 4) Combine resources over PUSCH and PUR sessions. See block 256. In other words, the UE uses both PUR and PUSCH (granted in the RRC connection) to transmit uplink data intended for PUR.
[0137] 5) Make PUSCH resources overlap with PUR sessions maximally. See block 258. For this block, the granted PUSCH resources are made to overlap with the PUR as much as possible. The idea is to make the same UE reuse the previously granted PUR as much as possible.
[0138] 6) Manage the HARQ processes associated with the dedicated connection to allow PUR HARQ process transmissions to occur in parallel with the dedicated connection. See block 260. That is, when the PUR transmission regions overlap, the dedicated mode UE is restricted to a single HARQ process mode. This is necessary if the UE wants to continue PUR transmissions independently along with the dedicated mode.
[0139] If the PUR session is still ongoing, the UE shall update the saved PUR TA to the latest value before releasing the RRC connection and transitioning to idle mode. See block 265.
[0140] If SPS is supported for dedicated mode transmission, the eNB may configure the UE as one of the following (see block 270):
[0141] 1) Push the resource location of the D-PUR transmission beyond the SPS resource location. See block 275.
[0142] 2) Postpone SPS transmission beyond the D-PUR resource location. See block 280.
[0143] In block 285, if an RRC connection or EDT is established just before the D-PUR opportunity to deliver the same data intended for the D-PUR because the conditions for the PUR at the UE are not met (e.g., the timing advance value is no longer valid at the UE) and if the RRC connection is completed before the D-PUR opportunity itself (e.g., this is possible if uplink data, e.g., in the form of sensor reports, is available in advance before the D-PUR opportunity to check the validity of the PUR usage), then:
[0144] 1) The UE indicates to the RRC connection / EDT that it intends to send D-PUR data associated with the next PUR opportunity. See block 290.
[0145] 2) On successful packet transmission, the eNB and UE also release PUSCH resources for the upcoming PUR occasions. See block 295. However, the remaining D-PUR occasions are valid because the UE has received a valid timing advance via this process.
[0146] III. Additional Exemplary Details
[0147] One scenario addressed by the exemplary embodiment is Figure 3 Medium picture. Figure 3 Three PUR allocations 340-1, 340-2 and 340-3 are shown, as well as corresponding D-PURs 320-1, 320-2 and 320-3 in each PUR allocation 340. The dedicated RRC connection 310 established for non-PUR transmission overlaps the D-PUR 320-1 already assigned to the UE. There is an RRC connection request for non-PUR transmission (see reference numeral 330), which means that the corresponding dedicated RRC connection 310 will completely overlap the D-PUR 320-1.
[0148] Figure 4 , two different RRC configurations for modifying D-PUR resources for a dedicated connection or SPS are illustrated, Figure 4is a signaling diagram between a UE and an eNB and illustrates two methods for RRC reconfiguration. There is an RRC connection establishment message 410 from the UE 110 to the eNB 170. There are two examples of the RRC reconfiguration message 420. For the RRC reconfiguration message 420-1, the message includes a D-PUR resource state of release / postponement / combination with a dedicated PUSCH. This is method 1 430-1. That is, the D-PUR resource should be one of the following: released ("release"); postponed ("postponed"); or combined with a dedicated PUSCH ("combined with a dedicated PUSCH"). Postponement means that the use of the D-PUR is postponed until a position after the RRC connection is released. At the same time, "suspend" is used to indicate that the D-PUR is not used during the RRC connection, but the configuration is still maintained so that the configuration can be used after the RRC connection is released. Combining with a dedicated PUSCH means using both the PUR and PUSCH resources authorized in the RRC connection to transmit data intended for the PUR.
[0149] For the RRC reconfiguration message 420-2, the message includes an SPS configuration for D-PUR conflict with a value of one of the deferred SPS / deferred D-PUR. This is method 2 430-2. This is useful, for example, for Figure 3 The case shown in , where D-PUR and dedicated RRC connections overlap. The value of "deferred SPS" means that the SPS transmission is postponed until outside the D-PUR resource location (see e.g. Figure 2 The value of "deferred D-PUR" means that the resource location for D-PUR transmission is postponed until outside the SPS resource location (see e.g. Figure 2 275).
[0150] There is a case where the UE sends packets associated with D-PUR before the D-PUR opportunity via the EDT procedure. Figure 5 , which is an illustration of another scenario in which the UE transmits packets associated with a D-PUR (in a dedicated RRC connection 310) prior to a D-PUR opportunity 320-1 via an EDT procedure in an exemplary embodiment. Figure 5 Reference numeral 530 and blocks 285, 290 and 295. This may occur if the UE determines that the UE does not meet the validity criteria for using D-PUR transmission. In this case, as part of the RRC connection release, the eNB also indicates (see reference numeral 520) to release the next D-PUR instance. The additional D-PUR instance is valid because the UE has a valid timing advance via the EDT procedure. This is also applicable to the RRC connection establishment case.
[0151] See also Figure 6, which is a logic flow diagram for maintaining, suspending or modifying an existing PUR configuration executed by a UE in response to the UE entering RRC connected mode. The figure illustrates the operation of one or more exemplary methods according to exemplary embodiments, the execution results of computer program instructions implemented on a computer readable memory, the functions performed by logic implemented in hardware, and / or interconnected components for performing functions. For example, the blocks in the figure are executed by UE 110 under at least part of the control of PUR communication (Comm.) module 140.
[0152] In block 610, the process begins with, at a user equipment configured with an idle mode configuration for use of preconfigured uplink resources, determining that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection. In block 620, the process continues with the user equipment performing an initial access to the network for the radio resource control connection. In block 630, the UE 110 performs a transition from the radio resource control idle mode to the radio resource control connected mode. In block 640, the UE 110 performs one of suspending the idle mode configuration or maintaining the idle mode configuration for at least the duration of the radio resource control connected mode.
[0153] In the following example, Figure 6 The method is called Example 1.
[0154] Example 2. The method according to example 1, wherein the transition by the user equipment from the radio resource control idle mode to the radio resource control connected mode has been initiated by paging reception.
[0155] Example 3. A method according to any one of Examples 1 or 2, wherein the method includes the user equipment maintaining its idle mode configuration when the user equipment is in a radio resource control connected mode, and the user equipment does one of the following: continues to use the configuration or does not continue to use the configuration after the radio resource control connected mode.
[0156] Example 4. A method according to any one of Examples 1 or 2, wherein the method includes the user equipment suspending its use of the idle mode configuration for the duration of the radio resource connection mode, but continuing to maintain the idle mode configuration in its context, and in response to the idle mode configuration being still valid, using the idle mode configuration after the radio resource connection mode ends.
[0157] Example 5. The method according to any one of Examples 1 to 4, wherein the method further comprises:
[0158] In response to a radio resource control (RRC) connection being established by a user equipment for establishing the RRC connection for data transmission, receiving at the user equipment and from the network a preconfigured uplink resource (PUR) resource state of one of: (i) released or (ii) deferred or (iii) combined with a dedicated physical uplink shared channel (PUSCH) for the RRC connection; and
[0159] The user equipment performs a corresponding one of the following operations: (i) releasing the PUR resources configured for idle mode; (ii) postponing transmission on the PUR resources configured for idle mode until after transmission on the RRC connection; or (iii) transmitting data in one or both of the PUR or PUSCH resources authorized in the RRC connected mode.
[0160] Example 6. The method according to any one of Examples 1 to 4, wherein the method further comprises:
[0161] In response to an RRC connection being established by a user equipment for establishing a radio resource control connection for transmission of data, receiving at the user equipment and from a network a semi-persistent scheduling (SPS) configuration for a preconfigured uplink (PUR) conflict having a value of one of a deferred SPS or a deferred PUR; and
[0162] The user equipment performs a corresponding one of the following operations: postpones the resource location for PUR transmission to outside the SPS resource location; or postpones the SPS transmission to outside the PUR resource location.
[0163] Steering Figure 7 , which is a logic flow diagram for maintaining, suspending or modifying an existing PUR configuration executed by a network element in response to a UE entering RRC connected mode. The figure illustrates the operation of one or more exemplary methods according to exemplary embodiments, the execution results of computer program instructions implemented on a computer readable memory, the functions performed by logic implemented in hardware, and / or interconnected components for performing functions. For example, the blocks in the figure are executed by a network element, which is assumed to be a base station, at least in part under the control of a PUR communication (Comm.) module 150.
[0164] In block 710, the process begins by receiving an initial access to the network for a radio resource control (RRC) connection at a base station in a wireless communication network. In block 720, the base station determines that the user equipment is configured with an idle mode configuration for using preconfigured uplink resources. In block 730, the base station performs a transition of the user equipment from the RRC idle mode to the RRC connected mode. In block 740, the base station performs communication between the base station and the user equipment to perform one or more actions to modify one or both of the RRC connection corresponding to the transition to the RRC connected mode or the idle mode configuration of the user equipment.
[0165] In the following example, Figure 7 The method is referred to as Example 7.
[0166] Example 8. The method according to Example 7, wherein the method comprises:
[0167] In response to an RRC connection being established by a user equipment for establishing a radio resource control connection, a preconfigured uplink resource (PUR) resource state of one of the following is sent by the network and towards the user equipment: (i) released or (ii) postponed or (iii) combined with a dedicated physical uplink shared channel (PUSCH) for RRC connection, so that the user equipment performs a corresponding one of the following operations: (i) releases PUR resources configured for idle mode; (ii) postpones transmission on PUR resources configured for idle mode until after transmission on the RRC connection; or (iii) transmits data in one or both of the PUR or PUSCH resources authorized in RRC connected mode.
[0168] Example 9. The method of Example 7, wherein the method includes, in response to an RRC connection being established by a user equipment for establishing a radio resource control connection for transmission of data, sending, by the network and toward the user equipment, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict, the PUR conflict having a value of one of deferred SPS or deferred PUR, so that the user equipment performs a corresponding one of the following operations: postponing a resource location for PUR transmission outside the SPS resource location; or postponing the SPS transmission outside the D-PUR resource location.
[0169] Example 10. A method according to any one of Examples 7 to 9, wherein performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: causing the user equipment to suspend preconfigured uplink resources (PUR) in response to the user equipment transitioning to an RRC connected mode and for a duration that the user equipment is in the RRC connected mode.
[0170] Example 11. A method according to any one of Examples 7 to 9, wherein performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: enabling the user equipment to release a preconfigured uplink resource (PUR) when having data intended for the PUR but transmitted via an RRC connection, the transmission being in response to the user equipment transitioning to an RRC connected mode.
[0171] Example 12. A method according to any one of Examples 7 to 9, wherein performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: causing the user equipment to release a preconfigured uplink resource (PUR) in the absence of a transmission of data intended for the PUR, the transmission being in response to the user equipment transitioning to an RRC connected mode.
[0172] Example 13. A method according to any one of Examples 7 to 9, wherein performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: causing resources to be combined via a physical uplink shared channel (PUSCH) and a preconfigured uplink resource (PUR) session, wherein the PUSCH session is used for the radio resource control connection.
[0173] Example 14. A method according to any one of Examples 7 to 9, wherein performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: maximally overlapping PUSCH resources with a preconfigured uplink resource (PUR) session, wherein a physical uplink shared channel (PUSCH) resource is a resource used for an RRC connection.
[0174] Example 15. A method according to any one of Examples 7 to 9, wherein performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: managing a hybrid automatic repeat request (HARQ) process associated with the RRC connection to allow a preconfigured uplink resource (PUR) HARQ process transmission to occur in parallel with the RRC connection.
[0175] Example 16. The method of any of Examples 7 to 15, wherein the communication is performed using one or both of layer 2 or layer 3 signaling.
[0176] Example 17. A computer program comprising code for performing the method of any one of Examples 1 to 16 when the computer program is run on a computer.
[0177] Example 18. The computer program according to Example 17, wherein the computer program is a computer program product comprising a computer readable medium carrying computer program code embodied therein for use with a computer.
[0178] Example 19. The computer program according to example 17, wherein the computer program is directly loadable into an internal memory of a computer.
[0179] 20. An apparatus comprising:
[0180] means for determining, at a user equipment configured with an idle mode configuration for using preconfigured uplink resources, that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection;
[0181] means for performing, by a user equipment, an initial access to a network for a radio resource control connection;
[0182] means for transitioning, by a user equipment, from a radio resource control idle mode to a radio resource control connected mode; and
[0183] Means for the user equipment to perform one of suspending idle mode configuration or maintaining idle mode configuration at least for a duration of a radio resource control connected mode.
[0184] Example 21. The apparatus of Example 20, wherein the transition by the user equipment from the radio resource control idle mode to the radio resource control connected mode has been initiated by paging reception.
[0185] Example 22. An apparatus according to any one of Examples 20 or 21, wherein the apparatus includes a component for causing the user equipment to maintain its idle mode configuration when the user equipment is in a radio resource control connection mode, and a component for performing one of the following: continuing to use the configuration or not continuing to use the configuration after the radio resource control connection mode.
[0186] Example 23. An apparatus according to any of Examples 20 or 21, wherein the apparatus includes a component for a user equipment to suspend its use of an idle mode configuration for the duration of a radio resource connection mode but continue to maintain the idle mode configuration in its context, and in response to the idle mode configuration being still valid, to use the idle mode configuration after the radio resource connection mode ends.
[0187] Example 24. The device according to any one of Examples 20 to 23, wherein the device further comprises:
[0188] means for receiving, at the user equipment and from the network, one of the following pre-configured uplink resource (PUR) resource states: (i) released or (ii) deferred or (iii) combined with a dedicated physical uplink shared channel (PUSCH) for the RRC connection, in response to a radio resource control (RRC) connection established by the user equipment for establishing the RRC connection for transmission of data; and
[0189] A component for a user equipment to perform a corresponding one of the following operations: (i) releasing PUR resources configured for idle mode; (ii) deferring transmission on PUR resources configured for idle mode until after transmission on RRC connection; or (iii) transmitting data in one or both of PUR or PUSCH resources authorized in RRC connected mode.
[0190] Example 25. The device according to any one of Examples 20 to 23, wherein the device further comprises:
[0191] In response to an RRC connection being established by a user equipment for establishing a radio resource control connection for transmission of data, means for receiving, at the user equipment and from a network, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict having a value of one of a deferred SPS or a deferred PUR; and
[0192] A component for the user equipment to perform a corresponding one of the following operations: postpone the resource location for PUR transmission to outside the SPS resource location; or postpone the SPS transmission to outside the PUR resource location.
[0193] Example 26. A user equipment comprising any of the apparatuses according to Examples 20 to 25.
[0194] Example 27. An apparatus comprising:
[0195] means for receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection;
[0196] means for determining, at a base station, that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources;
[0197] means for transitioning, by a base station, a user equipment from an RRC idle mode to an RRC connected mode; and
[0198] Means for performing communications between a base station and a user equipment to perform one or more actions to modify one or both of an idle mode configuration of the user equipment or an RRC connection corresponding to a transition to an RRC connected mode.
[0199] Example 28. The apparatus of Example 27, wherein the apparatus comprises:
[0200] In response to an RRC connection being established by a user equipment for establishing a radio resource control connection, a component is sent by the network and to the user equipment one of the following pre-configured uplink resource (PUR) resource states: (i) released or (ii) postponed or (iii) combined with a dedicated physical uplink shared channel (PUSCH) for RRC connection, so that the user equipment performs a corresponding one of the following operations: (i) releases the PUR resources configured for idle mode; (ii) postpones transmission on the PUR resources configured for idle mode until after transmission on the RRC connection; or (iii) transmits data in one or both of the PUR or PUSCH resources authorized in RRC connected mode.
[0201] Example 29. An apparatus according to Example 27, wherein the apparatus includes: a component for the following operations: in response to an RRC connection being established by a user equipment for establishing a radio resource control connection for transmission of data, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict is sent by the network and toward the user equipment, the PUR conflict having a value of one of a deferred SPS or a deferred PUR, so that the user equipment performs a corresponding one of the following operations: postponing a resource location for PUR transmission outside the SPS resource location; or postponing the SPS transmission outside the D-PUR resource location.
[0202] Example 30. An apparatus according to any one of Examples 27 to 29, wherein a component for performing communication between a base station and a user equipment performs one or more actions to modify one or both of the configurations in a radio resource control connection or an idle connected mode of the user equipment and further includes: a component for causing the user equipment to suspend preconfigured uplink resources (PUR) in response to the user equipment transitioning to an RRC connected mode and for the duration that the user equipment is in the RRC connected mode.
[0203] Example 31. An apparatus according to any one of Examples 27 to 29, wherein the device for performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: a component for causing the user equipment to release a preconfigured uplink resource (PUR) in the event of a transmission having data intended for use with the PUR but via an RRC connection, the transmission being in response to the user equipment transitioning to an RRC connected mode.
[0204] Example 32. An apparatus according to any one of Examples 27 to 29, wherein the component for performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: a component for causing the user equipment to release a preconfigured uplink resource (PUR) in the absence of a transmission of data intended for the PUR, the transmission being in response to the user equipment transitioning to an RRC connected mode.
[0205] Example 33. An apparatus according to any one of Examples 27 to 29, wherein the component for performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment also includes: a component for causing resources to be combined via a physical uplink shared channel (PUSCH) and a preconfigured uplink resource (PUR) session, wherein the PUSCH session is used for the radio resource control connection.
[0206] Example 34. An apparatus according to any one of Examples 27 to 29, wherein the component for performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment further includes: a component for maximally overlapping PUSCH resources with a preconfigured uplink resource (PUR) session, wherein the physical uplink shared channel (PUSCH) resources are resources for an RRC connection.
[0207] Example 35. An apparatus according to any one of Examples 27 to 29, wherein the component for performing communication between a base station and a user equipment to perform one or more actions to modify one or both of a radio resource control connection or an idle mode configuration of the user equipment also includes: a component for managing a hybrid automatic repeat request (HARQ) process associated with an RRC connection to allow a preconfigured uplink resource (PUR) HARQ process transmission to occur in parallel with the RRC connection.
[0208] Example 36. The apparatus of any one of Examples 27 to 35, wherein the communication is performed using one or both of layer 2 or layer 3 signaling.
[0209] Example 37. A user equipment comprising any of the apparatuses of Examples 27 to 36.
[0210] Example 38. A wireless communication system comprising an apparatus according to any one of Examples 20 to 25 and an apparatus according to any one of Examples 27 to 36.
[0211] Exemplary advantages, technical effects, and inventive aspects include one or more of the following:
[0212] 1) Definition of priority rules between PUR and PDSCH / PUSCH;
[0213] 2) Definition of rules that allow the network to suspend / reset the PUR release counter / timer in case of RRC connection;
[0214] 3) L2 / L3 allows the UE / network to decide how to handle PUR signaling after the RRC connection is established;
[0215] 4) The network supports the mechanism of combining PUSCH and PUR resources;
[0216] 5) A mechanism for the UE to deliver all PUR data via dedicated scheduling of an RRC connection, where the resources assigned to D-PUR can also be reused for scheduling;
[0217] 6) A mechanism to postpone SPS or D-PUR when scheduling overlaps for both RRC connections; and / or
[0218] 7) A mechanism to deliver data transmission intended for a D-PUR opportunity via RRC connection / EDT prior to a D-PUR opportunity, and implicitly release the associated D-PUR (eg, required in case of invalidation of the D-PUR prior to the transmission).
[0219] For (1), some embodiments are described above in which D-PUR is suspended or released during the RRC connection. This can be understood as a rule that prioritizes PUSCH (authorized in the RRC connection) over PUR. In other embodiments, the UE combines both PUR and PUSCH resources authorized in the RRC connection. This can be interpreted as another priority rule.
[0220] IV. Additional Comments
[0221] As used in this application, the term "circuitry" may refer to one or more or all of the following:
[0222] (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry) and
[0223] (b) a combination of hardware circuitry and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware and (ii) any portion of hardware processor(s) working together with software (including digital signal processor(s), software and memory(s) to cause a device (such as a mobile phone or server) to perform various functions, and
[0224] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) for operation, but the software may not be present when not required for operation.
[0225] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or a processor (or multiple processors) or a portion of a hardware circuit or a processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to a particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device. Similarly, for (2), in some embodiments, the rules for counters / timers are described as part of the rules that apply to the PUR.
[0226] The embodiments of this document may be implemented in software (executed by one or more processors), hardware (e.g., application specific integrated circuits), or a combination of software and hardware. In an example embodiment, the software (e.g., application logic, instruction set) is maintained on any of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" can be any medium or component that can contain, store, communicate, propagate, or transmit instructions for use by or in conjunction with an instruction execution system, apparatus, or device such as a computer, having, for example, a computer program product. Figure 1 An example of a computer as described and depicted in . Computer-readable media may include computer-readable storage media (e.g., memory 125, 155, 171 or other devices), which may be any medium or component that can contain, store, and / or transmit instructions for use by or in conjunction with an instruction execution system, apparatus, or device such as a computer. Computer-readable storage media do not include propagating signals.
[0227] If desired, the different functions discussed herein may be performed in different orders and / or simultaneously with each other. In addition, if desired, one or more of the above functions may be optional or may be combined.
[0228] While various aspects are set out above, other aspects include other combinations of features from the described embodiments, and not just the combinations described above.
[0229] It should also be noted herein that although the above describes exemplary embodiments of the present invention, these descriptions should not be viewed in a limiting sense. Rather, various changes and modifications are possible without departing from the scope of the present invention.
Claims
1. A method for communication, comprising: at a user equipment configured with an idle mode configuration for using preconfigured uplink resources, determining that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection; performing, by the user equipment, initial access to a network for the radio resource control connection; transitioning, by the user equipment, from a radio resource control idle mode to a radio resource control connected mode; as well as At least during the duration of the radio resource control connected mode, the user equipment performs one of the following: suspending the idle mode configuration or maintaining the idle mode configuration.
2. The method according to claim 1, wherein the transition from the radio resource control idle mode to the radio resource control connected mode by the user equipment has been initiated by paging reception.
3. The method of claim 1, wherein the method comprises the user equipment maintaining its idle mode configuration when the user equipment is in a radio resource control connected mode, and the user equipment performing one of the following: continuing to use the configuration or not continuing to use the configuration after the radio resource control connected mode.
4. The method according to claim 1, wherein the method comprises: The user equipment suspends its use of the idle mode configuration for the duration of the radio resource connection mode, but continues to maintain the idle mode configuration in its context, and in response to the idle mode configuration being still valid, uses the idle mode configuration after the radio resource connection mode ends.
5. The method according to any one of claims 1 to 4, wherein the method further comprises: receiving, at the user equipment and from the network, a preconfigured uplink resource (PUR) resource state of one of: (i) released or (ii) deferred or (iii) combined with a dedicated physical uplink shared channel (PUSCH) for use with the RRC connection, in response to a radio resource control (RRC) connection being established by the user equipment for establishing the RRC connection for transmission of the data; and The user equipment performs a corresponding one of the following operations: (i) releasing the PUR resources used for the idle mode configuration; (ii) postponing transmission on the PUR resources used for the idle mode configuration until after transmission on the RRC connection; or (iii) transmitting data in one or both of the PUR or the PUSCH resources authorized in the RRC connected mode.
6. The method according to any one of claims 1 to 4, wherein the method further comprises: receiving, at the user equipment and from the network, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict having a value of one of a deferred SPS or a deferred PUR, in response to an RRC connection being established by the user equipment for establishing the radio resource control connection for transmission of the data; and The user equipment performs a corresponding one of the following operations: postpones a resource location for PUR transmission to outside the SPS resource location; or postpones the SPS transmission to outside the PUR resource location.
7. A method for communication, comprising: receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection; determining, at the base station, that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources; The base station converts the user equipment from the RRC idle mode to the RRC connected mode; as well as Communication is performed between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or the RRC connection corresponding to the transition to the RRC connected mode.
8. The method according to claim 7, wherein the method comprises: In response to an RRC connection being established by the user equipment for establishing a radio resource control connection, a preconfigured uplink resource (PUR) resource state is sent by the network and towards the user equipment to: (i) release or (ii) postpone or (iii) combine with a dedicated physical uplink shared channel (PUSCH) for use with the RRC connection, so that the user equipment performs a corresponding one of the following operations: (i) release the PUR resources used for the idle mode configuration; (ii) postpone transmission on the PUR resources used for the idle mode configuration until after the transmission on the RRC connection; or (iii) transmit data in one or both of the PUR or the PUSCH resources authorized in the RRC connection mode.
9. The method according to claim 7, wherein the method comprises: In response to an RRC connection being established by the user equipment for establishing the radio resource control connection for transmission of data, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict is sent by the network and toward the user equipment, the PUR conflict having a value of one of deferred SPS or deferred PUR, so that the user equipment performs a corresponding one of the following operations: postponing a resource location for PUR transmission outside the SPS resource location; or postponing the SPS transmission outside a dedicated PUR (D-PUR) resource location.
10. The method according to any one of claims 7 to 9, wherein performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: In response to the user equipment transitioning to the RRC connected mode and for a duration that the user equipment is in the RRC connected mode, causing the user equipment to suspend preconfigured uplink resources (PUR).
11. The method according to any one of claims 7 to 9, wherein performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: The user equipment is caused to release a preconfigured uplink resource (PUR) if having a transmission regarding data intended for the PUR but via the RRC connection, the transmission being responsive to the user equipment transitioning to the RRC connected mode.
12. The method according to any one of claims 7 to 9, wherein performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: The user equipment is caused to release a preconfigured uplink resource (PUR) without transmission of data intended for the PUR, the transmission being responsive to the user equipment transitioning to the RRC connected mode.
13. The method according to any one of claims 7 to 9, wherein performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Resources are caused to be combined via a physical uplink shared channel (PUSCH) and a preconfigured uplink resource (PUR) session, wherein the PUSCH session is for the radio resource control connection.
14. The method according to any one of claims 7 to 9, wherein performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: A physical uplink shared channel (PUSCH) resource is maximally overlapped with the preconfigured uplink resource (PUR) session, wherein the PUSCH resource is a resource for the RRC connection.
15. The method according to any one of claims 7 to 9, wherein performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: A hybrid automatic repeat request (HARQ) process associated with the RRC connection is managed to allow the preconfigured uplink resource (PUR) HARQ process transmission to occur in parallel with the RRC connection.
16. The method of any one of claims 7 to 9, wherein the communicating is performed using one or both of layer 2 or layer 3 signaling.
17. A computer program product, comprising a computer program, wherein the computer program performs the method according to any one of claims 1 to 16 when being executed on a computer.
18. The computer program product of claim 17, wherein the computer program product comprises a computer readable medium carrying computer program code embodied therein for use with the computer.
19. The computer program product according to claim 17, wherein the computer program is directly loadable into an internal memory of the computer.
20. An apparatus for communication, comprising: means for determining, at a user equipment configured with an idle mode configuration for using preconfigured uplink resources, that data not associated with said preconfigured uplink resources is to be sent or received via a radio resource control connection; means for performing, by the user equipment, initial access to a network for the radio resource control connection; means for transitioning, by the user equipment, from a radio resource control idle mode to a radio resource control connected mode; as well as Means for the user equipment to perform one of the following, at least for a duration of the radio resource control connected mode: suspend the idle mode configuration or maintain the idle mode configuration.
21. The apparatus of claim 20, wherein the transition from the radio resource control idle mode to the radio resource control connected mode by the user equipment has been initiated by paging reception.
22. An apparatus according to any one of claims 20, wherein the apparatus comprises a component for the user equipment to maintain its idle mode configuration when the user equipment is in a radio resource control connected mode, and a component for performing one of the following: continuing to use the configuration or not continuing to use the configuration after the radio resource control connected mode.
23. An apparatus according to any one of claim 20, wherein the apparatus includes a component for the following operations: the user equipment suspends its use of the idle mode configuration for the duration of the radio resource connection mode, but continues to maintain the idle mode configuration in its context, and in response to the idle mode configuration being still valid, uses the idle mode configuration after the radio resource connection mode ends.
24. The device according to any one of claims 20 to 23, wherein the device further comprises: means for: in response to a radio resource control (RRC) connection being established by the user equipment for establishing the RRC connection for transmission of the data, receiving at the user equipment and from the network a preconfigured uplink resource (PUR) resource state of one of: (i) released or (ii) deferred or (iii) combined with a dedicated physical uplink shared channel (PUSCH) for the RRC connection; and A component for the user equipment to perform a corresponding one of the following operations: (i) releasing the PUR resources used for the idle mode configuration; (ii) postponing transmission on the PUR resources used for the idle mode configuration until after transmission on the RRC connection; or (iii) transmitting data in one or both of the PUR or the PUSCH resources authorized in the RRC connected mode.
25. The device according to any one of claims 20 to 23, wherein the device further comprises: means for receiving, at the user equipment and from the network, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict having a value of one of a deferred SPS or a deferred PUR, in response to an RRC connection being established by the user equipment for establishing the radio resource control connection for transmission of the data; and A component for the user equipment to perform a corresponding one of the following operations: postpone the resource location for PUR transmission to outside the SPS resource location; or postpone the SPS transmission to outside the PUR resource location.
26. A user equipment comprising any of the apparatuses according to claims 20 to 25.
27. An apparatus for communication, comprising: means for receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection; means for determining, at the base station, that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources; means for converting, by the base station, the user equipment from an RRC idle mode to an RRC connected mode; as well as Means for performing communications between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or an RRC connection corresponding to transitioning to the RRC connected mode.
28. The apparatus of claim 27, wherein the apparatus comprises: A component for the following operations: in response to an RRC connection being established by the user equipment for establishing a radio resource control connection, a preconfigured uplink resource (PUR) resource state is sent by the network and towards the user equipment to: (i) release or (ii) postpone or (iii) combine with a dedicated physical uplink shared channel (PUSCH) for use with the RRC connection, so that the user equipment performs a corresponding one of the following operations: (i) release the PUR resources used for the idle mode configuration; (ii) postpone transmission on the PUR resources used for the idle mode configuration until after the transmission on the RRC connection; or (iii) transmit data in one or both of the PUR or the PUSCH resources authorized in the RRC connection mode.
29. An apparatus according to claim 27, wherein the apparatus includes a component for the following operations: in response to an RRC connection being established by the user equipment for establishing the radio resource control connection for the transmission of data, a semi-persistent scheduling (SPS) configuration for a preconfigured uplink resource (PUR) conflict is sent by the network and toward the user equipment, the PUR conflict having a value of one of a deferred SPS or a deferred PUR, so that the user equipment performs a corresponding one of the following operations: postponing a resource location for PUR transmission outside the SPS resource location; or postponing the SPS transmission outside a dedicated PUR (D-PUR) resource location.
30. The apparatus of any one of claims 27 to 29, wherein the means for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Means for causing the user equipment to suspend preconfigured uplink resources (PUR) in response to the user equipment transitioning to the RRC connected mode and for a duration that the user equipment is in the RRC connected mode.
31. The apparatus of any one of claims 27 to 29, wherein the means for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Means for causing the user equipment to release a preconfigured uplink resource (PUR) if there is a transmission of data for the PUR intended for use but via the RRC connection, the transmission being responsive to the user equipment transitioning to the RRC connected mode.
32. The apparatus of any one of claims 27 to 29, wherein the means for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Means for causing the user equipment to release a preconfigured uplink resource (PUR) in the absence of a transmission of data intended for the PUR, the transmission being responsive to the user equipment transitioning to the RRC connected mode.
33. The apparatus of any one of claims 27 to 29, wherein the means for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Means for causing resources to be combined via a physical uplink shared channel (PUSCH) and a preconfigured uplink resource (PUR) session for the radio resource control connection.
34. The apparatus of any one of claims 27 to 29, wherein the means for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Means for maximally overlapping a physical uplink shared channel (PUSCH) resource with the preconfigured uplink resource (PUR) session, wherein the physical uplink shared channel (PUSCH) resource is a resource for the RRC connection.
35. The apparatus of any one of claims 27 to 29, wherein the means for performing communication between the base station and the user equipment to perform one or more actions to modify one or both of the radio resource control connection or the idle mode configuration of the user equipment further comprises: Means for managing a hybrid automatic repeat request (HARQ) process associated with the RRC connection to allow the preconfigured uplink resource (PUR) HARQ process transmission to occur in parallel with the RRC connection.
36. An apparatus according to any one of claims 27 to 29, wherein the communicating is performed using one or both of layer 2 or layer 3 signalling.
37. A base station comprising any of the devices according to claims 27 to 36.
38. A wireless communication system, comprising the apparatus according to any one of claims 20 to 25 and the apparatus according to any one of claims 27 to 36.
39. An apparatus for communication, comprising one or more processors and one or more memories, the one or more memories comprising computer program code, the one or more memories and the computer program code being configured to, together with the one or more processors, cause the apparatus to perform at least the following operations: at a user equipment configured with an idle mode configuration for using preconfigured uplink resources, determining that data not associated with the preconfigured uplink resources is to be sent or received via a radio resource control connection; performing, by the user equipment, initial access to a network for the radio resource control connection; transitioning, by the user equipment, from a radio resource control idle mode to a radio resource control connected mode; as well as At least during the duration of the radio resource control connected mode, the user equipment performs one of the following: suspending the idle mode configuration or maintaining the idle mode configuration.
40. An apparatus for communication, comprising one or more processors and one or more memories, the one or more memories comprising computer program code, the one or more memories and the computer program code being configured to, together with the one or more processors, cause the apparatus to perform at least the following operations: receiving, at a base station in a wireless communication network, an initial access to the network for a radio resource control (RRC) connection; determining, at the base station, that a user equipment is configured with an idle mode configuration for using preconfigured uplink resources; The base station converts the user equipment from the RRC idle mode to the RRC connected mode; as well as Communication is performed between the base station and the user equipment to perform one or more actions to modify one or both of the idle mode configuration of the user equipment or the RRC connection corresponding to the transition to the RRC connected mode.
