DRX cycle
By having the UE select and report the appropriate DRX cycle, the power consumption and latency issues when the UE moves between cells are resolved, achieving synchronization between the network and the UE and efficient power management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-01
- Publication Date
- 2026-03-13
AI Technical Summary
When a user equipment (UE) moves from one cell to another, existing technologies fail to effectively manage changes in the discontinuous reception (DRX) cycle, resulting in unnecessary power consumption and latency because the network is unaware of the UE's location change.
By selecting and reporting appropriate DRX cycles, including idle or inactive DRX cycles, the UE notifies network nodes of changes in its currently used DRX cycle, ensuring network synchronization with the UE and reducing unnecessary power consumption and latency.
By dynamically managing the DRX cycle, power waste of the UE when it is not paging the network is reduced, ensuring synchronization between the network and the UE and reducing latency.
Smart Images

Figure CN121666873A_ABST
Abstract
Description
Technical Field
[0001] Examples of this disclosure relate to discontinuous reception (DRX) cycles. Some of these examples involve selecting a DRX cycle or an extended DRX (eDRX) cycle for use. Background Technology
[0002] Discontinuous reception (DRX) allows user equipment to intermittently monitor control or paging channels and sleep the rest of the time. Extended DRX (eDRX) can be used to extend the cycle and provide further power savings. Different nodes or cells within a network may have different DRX / eDRX capabilities or configurations. Summary of the Invention
[0003] According to various, but not necessarily all, examples of this disclosure, an apparatus may be provided comprising: Components used to determine one or more discontinuous reception periods configured for the device; The component for making a selection, wherein the selection is made from one or more discontinuous reception periods configured for use by the device, selecting a discontinuous reception period for use by the device; and A component used to report the selected discontinuous reception period to network nodes.
[0004] The device may include: a component for making another selection of a discontinuous reception period for use by the device, wherein the other selection is made from one or more discontinuous reception periods configured for use by the device; Components for determining the change between one selection and another selection in one or more discontinuous reception cycles to be used by the device; and A component for reporting the alternative selection of the discontinuous reception period based on the determination that a change exists in the discontinuous reception period to be used by the device.
[0005] Making this alternative choice can be at least partially in response to at least one of the following: The device performs a selection or reselection of different cells, wherein the different cells are cells that are different from the current cell of the device; Changes were detected in the system information.
[0006] The selection and / or another selection performed by the device may be based at least in part on system information for the cell used by the device.
[0007] The device may include components for receiving requests from network nodes that report which discontinuous reception cycle is in use.
[0008] The selection component can be used to select discontinuous reception periods when the device is idle or inactive.
[0009] The apparatus may include: a component for receiving paging signals from a network node using a selected discontinuous reception period.
[0010] Discontinuous reception periods can be one of the following: Discontinuous reception during idle periods; Discontinuous reception during idle extension; Inactive and discontinuous reception; Inactive extended discontinuous reception; Inactive Enhanced Extended Discontinuous Reception.
[0011] The selected discontinuous reception period can be reported as discontinuous reception using at least one of the following: Media access control signaling; Radio resource control signaling; Non-access stratum signaling.
[0012] The selected discontinuous reception period can be reported as discontinuous reception using one of the following: Media access control element; Common control channel logical channel identifier; Common control channel extended logical channel identifier; One or more information elements within a radio resource control message.
[0013] Radio resource control messages may include connection establishment messages or connection restoration messages.
[0014] A connection establishment message or a connection recovery message may include at least one of the following: Radio resource control establishment message; Radio resource control recovery message.
[0015] The device may include a component for transmitting an indication of discontinuous reception cycles that the device will use in idle and / or inactive states, wherein the indication is transmitted to the network when the device is in a connected state.
[0016] The device may include user equipment.
[0017] Based on various, but not necessarily all, examples of this disclosure, a method may be provided that includes: Determine one or more discontinuous reception periods to be configured for the device; Select the discontinuous reception period for use by the device from one or more discontinuous reception periods configured for the device. Report the selected discontinuous reception period to the network nodes.
[0018] According to various, but not necessarily all, examples of this disclosure, a computer program may be provided that includes instructions that, when executed by a device, cause the device to perform at least the following operations: Determine one or more discontinuous reception periods to be configured for discontinuous reception by the device; Select a discontinuous reception period for use by the device from one or more discontinuous reception periods configured for the device; and Report the selected discontinuous reception period to the network nodes.
[0019] Based on various, but not necessarily all, examples of this disclosure, examples of this disclosure may provide a network node comprising: Components for receiving reports from selected discontinuous reception periods being used by the device; and A component for paging the device using a selected discontinuous reception period.
[0020] Discontinuous reception periods can be reported in response to changes in the discontinuous reception periods that will be used by the device.
[0021] The network node may include components for sending a request to the device to request the device to report the discontinuous reception period that the device is using.
[0022] The network node may include components for sending an indication of a discontinuous reception cycle being used by the device to another network node.
[0023] This network node may include access nodes.
[0024] Selection and / or reselection can be made by the device based at least in part on system information for the cell used by the device.
[0025] Based on various, but not necessarily all, examples of this disclosure, a method may be provided that includes: Receive reports on the selected discontinuous reception period being used by the device; and Use the selected discontinuous reception period to page the device.
[0026] Based on various, but not necessarily all, examples of this disclosure, a computer program may be provided that includes instructions that, when executed by a network node, cause the network node to perform at least the following operations: Receive reports of the selected discontinuous reception period being used by the device; and
[0027] Use the selected discontinuous reception period to page the device.
[0028] While the examples and optional features of this disclosure have been described separately, it should be understood that this disclosure includes all possible combinations and permutations of them. It should be understood that the various examples of this disclosure may include any or all of the features described with respect to other examples of this disclosure, and vice versa. Furthermore, it should be understood that any one or more of the features, in any combination, may be implemented / included / performed as needed and appropriately by means of apparatus, method, and / or computer program instructions. Attached Figure Description
[0029] Some examples will now be described with reference to the accompanying drawings, in which:
[0030] Figure 1 An example network is shown;
[0031] Figure 2A and Figure 2B Example methods are shown;
[0032] Figure 3 An example signaling diagram is shown; and
[0033] Figure 4 An example controller is shown.
[0034] The accompanying drawings are not necessarily drawn to scale. For clarity and brevity, some features and views in the drawings may be shown schematically or enlarged to scale. For example, for ease of illustration, the dimensions of some elements in the drawings may be enlarged relative to other elements. Corresponding reference numerals are used in the drawings to designate the corresponding features. For clarity, not all reference numerals are shown in all figures. definition
[0035] CCCH Common Control Channel
[0036] CE control elements
[0037] CN Core Network
[0038] DRX discontinuous reception
[0039] eDRX Extended DRX
[0040] eLCID Extended Logical Channel Identifier
[0041] E-UTRA Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access
[0042] gNB NR base station
[0043] LCID (Logical Channel Identifier)
[0044] MAC Media Access Control
[0045] NAS Non-Access Layer
[0046] O-RAN Open Radio Access Network
[0047] PO paging timing
[0048] PTW Paging Time Window
[0049] RAN (Radio Access Network)
[0050] RF (Radio Frequency)
[0051] RRC Radio Resource Control
[0052] UE User Equipment Detailed Implementation
[0054] Figure 1 An example of a network 100, such as a 5G NR network, is illustrated. Network 100 includes various different types of entities 110, 120, and 130. These different types of entities may include terminal devices 110, network nodes 120 and core network nodes 130, and / or any other suitable type of entity.
[0055] Network node 120 can be configured to communicate with terminal device 110. One or more core network nodes 130 communicate with network node 120. In some examples, one or more core network nodes 130 communicate with terminal device 110.
[0056] In some examples, one or more core network nodes 130 can communicate with each other. In some examples, one or more network nodes 120 can communicate with each other.
[0057] Network 100 may be a cellular network comprising multiple cells 122. Each cell is served by network node 120. Network node 120 can provide access nodes. In this example, the interface between terminal device 110 and network node 120 defining cell 122 is wireless interface 124.
[0058] Network node 120 includes one or more cellular radio transceivers. Terminal device 110 includes one or more cellular radio transceivers.
[0059] In the illustrated example, cellular network 100 is a 3GPP network, in which terminal device 110 is a user equipment (UE), and network node 120 may be an access node, such as a base station (gNB).
[0060] The term "user equipment" is used to specify mobile devices that include smart cards for authentication / encryption, such as a Subscriber Identity Module (SIM). In some examples, the term "user equipment" is used to specify mobile devices that include circuitry embedded as part of the user equipment for authentication / encryption, such as a software SIM.
[0061] Network node 120 can be a base station. Network node 120 can be any suitable type of base station. A base station is an access node. Network node 120 can be a network entity responsible for radio transmissions to and from UE 110 within one or more cells. Network node 120 can be a network element in a radio access network (RAN), an open radio access network (O-RAN), an evolved universal mobile communications system (UMTS) terrestrial radio access network (E-UTRA), or any other suitable type of network.
[0062] Core network node 130 may be part of a core network. Core network node 130 may be configured to manage connectivity-related functions of UE 110. For example, core network node 130 may be configured to manage functions such as connectivity, mobility, authentication, authorization, and / or other suitable functions.
[0063] exist Figure 1 In the example, core network node 130 is shown as a single entity. In some examples, core network node 130 may be distributed across multiple entities. For example, core network node 130 may be cloud-based or distributed in any other suitable manner.
[0064] For example, network 100 can be a 4G or 5G network. It could be, for example, a New Radio (NR) network using a gNB or eNB as access node 120. New Radio is 3GPP's designation for 5G technology. In this case, network device 120 may include gNodeB (gNB) 120, which is configured to provide user plane and control plane protocol termination to UE 110, and / or perform any other suitable functions. gNBs 120 interconnect with each other via interface 126. gNBs 120 also connect to core network device 130 via N2 interface 128. Other types of networks and interfaces may also be used in other examples. Other types of networks may include next-generation mobile communication networks, such as 6G networks.
[0065] DRX and eDRX can be used by entities within network 100. DRX enables terminal devices (such as UE 110) to monitor the control channel or paging channel intermittently, while remaining in sleep mode the rest of the time. Extended DRX (eDRX) can be used to extend the cycle and provide further power savings.
[0066] Network 100 can indicate the DRX and eDRX cycles that can be used by UE 110. For example, the network can indicate whether a certain type of DRX or eDRX cycle is allowed. For example, 3GPP Release 17 specifies... eDRX- AllowedIdle and eDRX-AllowedInactive :
[0067] eDRX-AllowedIdle
[0068] The presence of this field indicates that extended DRX is allowed for core network (CN) paging within the cell for UEs in RRC_IDLE or RRC_INACTIVE states. If eDRX-AllowedIdle If it does not exist, the UE should stop using extended DRX for CN paging under RRC_IDLE or RRC_INACTIVE.
[0069] eDRX-AllowedInactive
[0070] The presence of this field indicates that extended DRX is permitted for Radio Access Network (RAN) paging within the cell for UEs in RRC_INACTIVE mode. If it is not present, the UE should stop using extended DRX for RAN paging in RRC_INACTIVE mode.
[0071] Problems may arise if UE 110 camps in a cell that does not allow the eDRX cycle being used by UE 110. For example, if UE 110, in an idle or inactive state, selects a different cell as its anchor cell, that different cell can be configured for UE 110 to use a different DRX cycle or eDRX cycle than UE 110 is currently using. This could result in a change in the DRX or eDRX cycle that UE 110 will use. Since UE 110 does not notify the radio access network (RAN) of the cell it is camping in, the core network 130 or the RAN may not be aware of this change.
[0072] As an illustrative example, UE 110 can move from a first cell that allows idle eDRX to a second cell that does not. In this example, when UE 110 moves to the second cell, UE 110 will monitor paging according to idle eDRX, but the core network 130 is unaware of this and will assume that UE 110 is still monitoring paging according to idle eDRX. In this case, UE 110's power will be unnecessarily consumed because the core network 130 will perform paging according to the eDRX cycle. In addition to unnecessary power loss, unnecessary delays will also occur because UE 110 is monitoring paging at a frequency higher than expected by the core network 130, and therefore the core network 130 needs to wait until the next paging opportunity according to the eDRX cycle before it can perform paging.
[0073] The examples disclosed herein are intended to address these issues.
[0074] Figure 2A and Figure 2B Example methods that can be implemented based on the examples in this disclosure are shown.
[0075] Figure 2A An example method that can be implemented by a device is shown. This device can be a terminal device, such as UE 110.
[0076] The method includes: at block 200, determining that one or more DRX / eDRX cycles are configured for the device. The one or more DRX / eDRX cycles may include DRX and eDRX cycles, or any other suitable DRX cycle type. The DRX / eDRX cycle may include at least one of the following: idle discontinuous reception; idle extended discontinuous reception; inactive discontinuous reception; inactive extended discontinuous reception; inactive enhanced extended discontinuous reception; or any other suitable DRX / eDRX cycle type.
[0077] In some examples, the DRX / eDRX cycle can be the default paging cycle used for cell 122. In this example, the same DRX / eDRX cycle will be used by all devices within cell 122. In other examples, the DRX / eDRX cycle can be specific to a device or a subset of devices within cell 122. In this example, different DRX / eDRX cycles will be used by different devices within cell 122.
[0078] At block 202, the method includes: selecting a DRX / eDRX cycle from one or more DRX / eDRX cycles configured for use by the device. This selection may be based at least in part on system information for the cell used by the device;
[0079] The DRX / eDRX cycle to be used by the device can be selected when the device is idle or inactive.
[0080] The DRX / eDRX used by the device can be selected, at least in part, based on system information for the cell used by the device. For example, the system information for the cell used by the device can indicate the allowed DRX / eDRX cycles for that cell, and the device can select one of the allowed DRX / eDRX cycles. The system information may include information allowed by idle eDRX, inactive eDRX, and inactive enhanced eDRX. In some examples, multiple DRX cycles other than eDRX are always allowed in the cell. In some examples, the system information providing DRX / eDRX information may include RRC messages, such as system information block messages.
[0081] The cell used by the device is the cell that the device uses to maintain network connectivity. This is the cell where the UE is currently camped (in RRC_IDLE or RRC_INACTIVE state) and the cell that the UE will use to access the network (in RRC_CONNECTED mode) when a connection trigger exists (e.g., data transmission).
[0082] At box 204, the method includes reporting the selected DRX / eDRX to network node 120. The network node 120 to which the report is sent may be the device's anchor network node, or any other suitable network node 120. In some examples, network node 120 may be an access node for the cell where the device is camped.
[0083] The selected DRX / eDRX can be reported to network node 120 using any suitable type of signaling. In some examples, control signaling can be used to report the selected DRX / eDRX to network node 120. In some examples, control signaling can be between the device and access node 120. In some examples, control signaling can be between the device and core network 130. In some examples, at least one of the following can be used to report the selected DRX / eDRX: Media Access Control (MAC) signaling; Radio Resource Control (RRC) signaling; Non-Access Stratum (NAS) signaling, or any other suitable type of signaling.
[0084] In some examples, at least one of the following can be used to report the selected DRX / eDRX: MAC control element (CE), common control channel (CCCH) logical channel identifier (LCID) value, CCCH extended logical channel identifier (eLCID) value, or one or more information elements within an RRC message. For example, one or more information elements in an RRC message may include an establishment cause value or a recovery cause value.
[0085] In examples where RRC messages are used to report the selected DRX / eDRX period, the RRC message may include a connection establishment message, a connection recovery message, or any other suitable type of message. The connection establishment message or connection recovery message includes at least one of the following: an RRC establishment message; an RRC recovery message. In some examples, the device may initiate an RRC establishment or RRC recovery procedure to report the selected DRX / eDRX period to network node 120.
[0086] The method may include Figure 2A The box is not shown in the image. In some examples, the method may include making an alternative selection of the DRX / eDRX cycle. This alternative selection is made from one or more discontinuous reception cycles configured for the device. This alternative selection may be made at a later point in time than the first selection. The device may be configured to determine a change in one or more DRX / eDRX cycles that the device will use. The determined change may be a change in the DRX / eDRX cycle in use. For example, it may be a switch from using eDRX to using DRX, or any other suitable type of change. For example, the change in the DRX / eDRX cycle in use may be a change from inactive (enhanced) eDRX to inactive DRX, or a change from inactive enhanced eDRX to inactive eDRX.
[0087] Changes in the DRX / eDRX cycle that the device will use can be determined using any suitable method or process. For example, changes can be determined by reading system information for cell 122 used by the device and comparing that system information with the DRX / eDRX cycle configured for the device. Specifically, the DRX / eDRX in the system information needs to be compared with the DRX / eDRX cycle configured for the device.
[0088] In an example of determining a change in one or more DRX / eDRX periods, the device can be configured to trigger a report of a selected discontinuous reception period based on the determination that a change exists in the DRX / eDRX that the device will use. For example, if the selection of the DRX / eDRX period causes a change, then this change can be reported; however, if the selection of the DRX / eDRX period does not cause a change, then this change does not need to be reported.
[0089] There are several scenarios that could lead to changes in the DRX / eDRX cycles that a device will use. For example, changes may occur when a device selects or reselects a different cell, one that is different from the device's current cell. For instance, if a device moves from a first cell to a second cell, it may not be configured with the allowed DRX / eDRX on the second cell. This means the device needs to change or update the DRX / eDRX cycle it is using. In some examples, changes may also be caused by changes in the cell's system information. Changes in system information can include network changes to the allowed status of one or more DRX / eDRX cycles for one or more cells. Changes in DRX / eDRX cycles can be determined after any of these events occur.
[0090] There may be scenarios where reporting of the selected DRX / eDRX may not be triggered. For example, if all DRX / eDRX cycles configured for the device are allowed in different cells selected or reselected by the device, or if system information changes, then reporting of the selected DRX / eDRX is unnecessary because it has already been allowed. For instance, if system information changes to allow all types of DRX / eDRX, then reporting of the DRX / eDRX is unnecessary because all DRX / eDRX cycles configured for the device will be allowed.
[0091] In some examples, the method may include receiving a request from a network node to report which discontinuous reception period is being used for discontinuous reception. This request can be received using dedicated signaling. For example, the request can be made using an RRC reconfiguration or RRC release message. In some examples, the request can be received using broadcast signaling (such as system information). In some examples, a report can be sent in response to the request.
[0092] After the device has reported the DRX / eDRX cycle in use, it can receive paging signals from the network node. The selected DRX / eDRX cycle reported to the network node can be used to receive paging signals.
[0093] In some examples, reporting on a selected DRX / eDRX cycle can be performed while the device is in a CONNECTED state. For example, the device can be configured to send a report on the DRX / eDRX that the device will use in idle and / or inactive states, where this indication is sent to the network node when the device is in a connected state. For example, this indication can be sent using a UE Assistance Information Message (RRC message).
[0094] Figure 2B An example method that can be implemented by a network node (such as gNB 120 or core network node 130) is shown. Figure 2B Methods and Figure 2A This method corresponds to the method used by the network node 120 that receives the report of the selected DRX / eDRX cycle.
[0095] The method includes, at block 210, receiving a report of the selected DRX / eDRX cycle being used by the receiving device. The device may be a terminal device, such as UE 110. The device may reside within a cell including network node 120.
[0096] In some examples, the DRX / eDRX period is reported in response to changes in the DRX / eDRX period that the device will use. This determination can be performed by the device itself. In this case, network node 120 may only receive a report of the selected DRX / eDRX period when a change occurs.
[0097] At block 212, the method includes paging the device using a selected DRX / eDRX cycle.
[0098] The method may include Figure 2B The box is not shown in the image. In some examples, the method may include sending a request to the device to ask the device to report a discontinuous reception period that the device is using.
[0099] In some examples, network node 120 can be configured to share information about the reported DRX / eDRX cycle with other nodes in network 100. For example, network node 120 can be configured to send an indication to another network node of the discontinuous reception cycle being used by the device. This other network node can be access node 120 or core network node 130. For example, network node 120 receiving a report from a device can be configured to send an indication of the DRX / eDRX cycle being used by the device to the anchor gNB 120 of the device in RRC_INACTIVE mode. In this example, the report can indicate that the device is using a specific DRX cycle in RRC_INACTIVE mode, such as RRC_INACTIVE DRX or RRC_INACTIVE (enhanced) eDRX. In some examples, the device can send a report to a CN for a device in RRC_IDLE mode. In this example, the report can indicate that the device is using a specific DRX cycle in RRC_IDLE mode, such as RRC_IDLE DRX or RRC_IDLE eDRX.
[0100] Reporting the selected DRX / eDRX cycle from this device to network node 120 helps ensure that the device is synchronized with the Radio Access Network (RAN) and / or Core Network (CN). This reduces power waste caused by the device monitoring for paging when the network is not paging. It also ensures that the network waits for paging intervals no longer than necessary, thereby reducing latency.
[0101] Figure 3 An example signaling diagram is shown that can be used to implement examples of this disclosure.
[0102] exist Figure 3 In the example, signaling is shown to be between UE 110, first cell 122_1, and second cell 122_2. First cell 122_1 and second cell 122_2 may be provided by different gNBs 120. In some examples, first cell 122_1 and second cell 122_2 may be provided by the same gNB 120.
[0103] At box 300_1, the first cell 122_1 signals permitted eDRX modes. Permitted eDRX modes are those indicated as permissible in the system information for a given cell. Similarly, at box 300_2, the second cell 122_2 signals permitted eDRX mode signaling. For example, based on whether these eDRX modes are permitted in the corresponding cell 122, the corresponding cell may include in the system information... eDRX-AllowedIdle or eDRX-AllowedInactive .
[0104] In this illustrative example, cell 122_1 is allowed to signal eDRX in both idle and inactive modes. In this case, cell 122_1 will signal... eDRX-AllowedIdle and eDRX- AllowedInactive Both. Second cell 122_2 transmits via signaling: eDRX is enabled in idle mode but not in inactive mode. In this case, second cell 122_2 will transmit via signaling. eDRX-AllowedIdle But no signal is sent. eDRX-AllowedInactive .
[0105] In this example, the first cell 122_1 is the anchor cell 122 of UE 110. The second cell 122_2 can be the cell that UE 110 moves to or the cell where it is camped.
[0106] At box 302, UE 110 is released from active mode by the first cell 122_1. UE 110 can be released to idle mode or inactive mode. UE 110 can be released to idle mode or inactive mode using DRX / eDRX configuration. That is, one or more DRX / eDRX cycles are configured for UE 110.
[0107] In this scenario, one or more DRX / eDRX cycles are configured for UE 110, including DRX / eDRX cycles permitted by the first cell 122_1. Therefore, the configuration of one or more DRX / eDRX cycles for UE 110 can include eDRX idle, eDRX inactive, and / or enhanced eDRX inactive.
[0108] At box 304, the network may allow or request UE 110 to report the DRX / eDRX cycle that UE 110 is using. This may be an optional box. That is, not all examples in this disclosure require the use of this box.
[0109] The network can use any appropriate signaling to request UE 110 to report the DRX / eDRX cycle that UE 110 is using. In some examples, dedicated signaling can be used to make the request. For example, an RRC reconfiguration or RRC release message sent to UE 110 via cell 122_1 can be used to make the request. In some examples, broadcast signaling (such as system information) can be used to make the request.
[0110] At box 306, the UE reselects to the second cell 122_2. For example, UE 110 may remain in idle or inactive mode while camped in the second cell 122_2. In this scenario, since UE 110 is not in active mode, the network may not know that UE 110 is camped in a different cell, and there is no handover process. If UE 110 is triggered to initiate an RRC connection procedure, the first cell 122_1 will remain the cell that UE 110 will use.
[0111] At box 308, UE 110 acquires system information for the second cell 122_2. UE 110 can then determine whether the DRX / eDRX cycle configured for UE 110 is permitted in the second cell 122_2. UE 110 can determine whether the DRX / eDRX cycle is permitted by comparing the acquired system information with the information indicating the DRX / eDRX cycle configured for UE 110 at box 302.
[0112] In this scenario, two different scenarios may occur. In the first scenario, UE 110 is in idle mode and will therefore use eDRX idle. This is permitted in both cell 122_1 and cell 122_2. In this scenario, at box 310, UE 110 will continue to use the eDRX cycle. Specifically, UE 110 will continue with the eDRX idle cycle. There will be no changes to the currently used eDRX cycle. In this scenario, no new DRX / eDRX cycle is selected, and it is not necessary to report the currently used DRX / eDRX cycle.
[0113] In the second scenario, UE 110 is in inactive mode and will therefore use eDRX inactivity. This is permitted in cell 122_1 but not in cell 122_2. In this case, at box 312, UE 110 will begin using a DRX cycle. Specifically, UE 110 will change from an eDRX inactive cycle to a DRX inactive cycle. In this case, a new DRX / eDRX cycle has been selected, and therefore it is beneficial to report the selected DRX / eDRX cycle.
[0114] At box 314, the UE determines whether the DRX period has changed. This can be determined by comparing the system information for cell 122_2 with the DRX / eDRX period originally configured for UE 110.
[0115] In the first scenario mentioned above, the DRX / eDRX period used will remain unchanged, and therefore, it is not necessary to report the selected DRX / eDRX period. In the second scenario mentioned above, the DRX / eDRX period used changes, and therefore the method continues to box 316, and UE 110 will report the selected DRX / eDRX period to the second cell 122_2. The selected DRX / eDRX can be reported to the second cell 122_2 using any suitable type of signaling. In some examples, the selected DRX / eDRX can be reported to the second cell 122_2 using control signaling between UE 110 and network node 120.
[0116] At box 318, the second cell 122_2 confirms the report of the selected DRX / eDRX cycle.
[0117] At box 320, the second cell 122_2 can indicate to the anchor gNB 120 of UE 110 the DRX / eDRX cycle used by UE 110. In this scenario, the gNB 120 of the second cell 122_2 can indicate to the gNB 120 of the first cell 122_1 that UE 110 is currently using an inactive DRX.
[0118] Once the selected DRX / eDRX cycle is reported to the network, the network can use the selected DRX / eDRX cycle to page UE 110 at block 322. In this case, both cell 122_1 and cell 122_2 use inactive DRX cycles to synchronize UE 110 with the network.
[0119] Tables 1 through 4 illustrate how the device can select which DRX / eDRX cycle to use in various scenarios. In these tables, the "UE Configuration" column indicates the initial configuration for the UE. "Is eDRX-AllowedIdle broadcast?", "Is eDRX-AllowedInactive broadcast?", and "Is enhancedeDRX-AllowedIdle broadcast?" indicate whether they have been signaled to the UE: these modes are allowed. "Yes" in this column indicates that the corresponding mode is allowed, while "No" indicates that the corresponding mode is not allowed. The "UE Selection" column indicates the eDRX cycle mode selected by UE 110 based on the allowed modes.
[0120] The device can use system information for the cell to determine whether the corresponding type of DRX / eDRX is allowed. The cell can be the cell where the device is camped. Then, by comparing the DRX / eDRX currently configured for the device with the allowed eDRX modes, the device can choose whether to maintain the current DRX / eDRX cycle or select a different DRX / eDRX cycle.
[0121] When making any DRX / eDRX cycle selection, the device can use a process that compares the DRX / eDRX currently configured for the device with the allowed eDRX modes. Table 1: UEs in RRC_IDLE state Table 2: UEs in RRC_INACTIVE state Table 3: UEs in RRC_INACTIVE state Table 4: UEs in RRC_INACTIVE state
[0122] In some examples, UE 110 may be allowed to use eDRX cycles permitted by the previously used cell, even if the given eDRX cycle is not permitted on the currently used cell. This eDRX cycle can be an idle eDRX, an inactive eDRX, or an inactive enhanced eDRX. In this case, UE 110 may be configured with one or more of the following: idle eDRX, inactive eDRX, or inactive enhanced eDRX.
[0123] In some examples, UE 110 can be configured to apply an (e)DRX cycle for paging selected when entering idle or inactive mode. In such examples, the DRX cycle or eDRX cycle can be selected based on the cell in which UE 110 is released into idle mode or suspended into inactive mode (i.e., the cell that is UE 110's PCell cell / primary cell when UE 110 receives the RRRCrease message). For example, if UE 110, configured with idle eDRX, is released into IDLE mode and signaled in a given cell (which is UE 110's PCell cell / primary cell when UE 110 receives the RRRCrease message),... eDRX-AllowedIdle Then UE 110 applies idle eDRX, regardless of whether it reselects to transmit an unused signal. eDRX-AllowedIdle This can happen even if idle eDRX is not allowed in a given cell. In some examples, if a UE 110 configured with inactive (enhanced) eDRX is suspended in inactive mode, and in a given cell (when UE 110 receives a cell with...) suspendConfig When the RRCRelease message is sent, the cell is the PCell cell / primary cell of UE 110. eDRX-AllowedInactive (Or the corresponding IE for inactive enhanced eDRX), then UE 110 applies inactive (enhanced) eDRX, regardless of whether it is reselected to transmit an unused signal. eDRX-AllowedInactive Or, correspondingly, cells that do not send signals for inactive enhanced eDRX (this can happen even if inactive (enhanced) eDRX is not permitted).
[0124] In some examples, UE 110 calculates and monitors paging opportunities (POs) in the cell it camps on, based on the DRX cycle it should select in that cell. That is, the DRX cycle is based on the DRX cycle selected when entering idle / inactive mode, while the PO is determined based on the DRX cycle that UE 110 will use in the target cell (based on the target cell configuration). In some examples, UE 110 may be required to monitor one or more POs before, within, and / or after the paging monitoring window (e.g., paging time window (PTW)) of the eDRX cycle being used.
[0125] In some examples, new instructions can be specified for the network to instruct UE 110 to reapply / reselect the DRX period according to the configuration provided in a given cell. For example, such instructions can be provided in system information, paging messages, or short messages (DCIs). In some examples, upon receiving the instruction, if UE 110 changes the used / applied / selected DRX period, UE 110 triggers an RRC establishment / recovery procedure. For example, UE 110 can trigger a Tracking / Registration Area Update or RAN Area Update procedure.
[0126] Figure 4 An example controller 400 is shown. Controller 400 can be provided within an entity such as UE 110, a network node such as gNB 120, or any other suitable device. The implementation of controller 400 can be a controller circuit system. Controller 400 can be implemented entirely in hardware, can have some software components (including firmware only), or can be a combination of software and hardware (including firmware).
[0127] like Figure 4 As illustrated, the controller 400 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 406 in a general-purpose or special-purpose processor 402. The computer program 406 can be stored on a computer-readable storage medium (disk, memory, etc.) for execution by the processor 402.
[0128] Processor 402 is configured to read data from memory 404 and write data to memory 404. Processor 402 may also include an output interface through which processor 402 outputs data and / or commands, and processor 402 may also include an input interface through which processor 402 inputs data and / or commands.
[0129] Memory 404 stores computer program 406, which includes computer program instructions (computer program code) for controlling the operation of the device when loaded onto processor 402. The computer program instructions of computer program 406 provide logic and routines that enable the device to perform the methods illustrated in the figures. Processor 402 is able to load and execute computer program 406 by reading memory 404.
[0130] The controller 400 can be provided in a device such as UE 110. In this example, the controller 400 therefore includes: at least one processor 402; and at least one memory 404 storing instructions that, when executed by the at least one processor 402, cause the device to perform at least the following: It is determined that one or more discontinuous reception cycles are configured for device discontinuous reception; Select 202 from one or more discontinuous reception periods configured for use by the device: a discontinuous reception period for use by the device; and Report the selected discontinuous reception period to the network node.
[0131] Controller 400 may be provided in a network node such as gNB 120. In this example, controller 400 therefore includes: at least one processor 402; and at least one memory 404 storing instructions that, when executed by at least processor 402, cause the network node to perform at least the following: Receive 210 a report of the selected discontinuous reception period being used by the device; and The device is paged using the discontinuous reception period selected by 212.
[0132] The computer program 406 can reach the device via any suitable delivery mechanism 408. The delivery mechanism 408 can be, for example, a machine-readable medium, a computer-readable medium, a non-transient computer-readable storage medium, a computer program product, a memory device, a recording medium (such as a CD-ROM or a digital versatile optical disc (DVD)), or a solid-state storage device, or it can be an article of manufacture that includes or tangibly embodies the computer program 406. The delivery mechanism can be a signal configured to reliably transmit the computer program 406. The device can propagate or transmit the computer program 406 as a computer data signal.
[0133] Computer program 406 may include computer program instructions for causing the device to perform at least the following operations: It is determined that one or more discontinuous reception cycles are configured for device discontinuous reception; Select 202 from one or more discontinuous reception periods configured for use by the device: a discontinuous reception period for use by the device; and Report the selected discontinuous reception period to the network node.
[0134] Computer program 406 may include: computer program instructions for causing the device to perform at least the following operations, or for performing at least the following: Receive 210 a report of the selected discontinuous reception period being used by the device; and The device is paged using the discontinuous reception period selected by 212.
[0135] Computer program instructions may be included in a computer program, a non-transient computer-readable medium, a computer program product, or a machine-readable medium. In some, but not all, examples, computer program instructions may be distributed across more than one computer program.
[0136] Although memory 404 is illustrated as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cache storage.
[0137] Although processor 402 is illustrated as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which may be integrated or removable. Processor 402 may be a single-core or multi-core processor.
[0138] References to “computer-readable storage media,” “computer program products,” “tangible computer programs,” or “controllers,” “computers,” “processors,” etc., should be understood to encompass not only computers with different architectures (such as single-processor / multi-processor architectures and sequential (von Neumann) / parallel architectures) but also special-purpose circuits (such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other processing circuitry systems). References to computer programs, instructions, code, etc., should be understood to encompass software used in programmable processors or firmware, such as the programmable content of hardware devices, whether instructions for processors or configuration settings for fixed-function devices, gate arrays, or programmable logic devices.
[0139] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Implementation using only hardware circuitry (such as implementation using only analog and / or digital circuitry). (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; (ii) Any portion of (multiple) hardware processors and software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g. firmware) to operate, but may be absent when the software is not required to operate.
[0140] This definition of "circuit system" applies to all uses of the term in this application, including all uses in any claim. As another example, as used herein, the term "circuit system" also covers only the implementation of hardware circuitry or processors and their accompanying software and / or firmware. For example, and where applicable to specific claim elements, the term "circuit system" also covers baseband integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.
[0141] The stages illustrated in the figure may represent steps in the method and / or code segments in computer program 406. The specific order of the boxes illustrated does not necessarily imply a necessary or preferred order, and the order and arrangement of the boxes may be changed. Furthermore, some boxes may be omitted.
[0142] The term “include” as used in this document has an inclusive rather than exclusive meaning. That is, any reference to X including Y indicates that X may include only one Y or may include more than one Y. If the intention is to use “include” with an exclusive meaning, it will be clearly stated in the context by referring to “includes only one…” or by using “consisting of…”.
[0143] In this description, the terms "connection," "coupling," and "communication," and their derivatives, refer to operational connection / coupling / communication. It should be understood that any number or combination of intermediate components (including the absence of intermediate components) may exist, providing direct or indirect connection / coupling / communication. Any such intermediate component may include hardware and / or software components.
[0144] As used herein, the term "determine" or "determining" (and its grammatical variations) can include, but is not limited to: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (e.g., searching in a table, database, or other data structure), ascertaining, etc. Furthermore, "determining" can also include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), obtaining, etc. Additionally, "determining" can also include resolving, selecting, confirming, etc.
[0145] In this description, various examples are referenced. The description of features or functions associated with an example indicates which features or functions exist in that example. The use of the terms "example," "for example," "may," or "possibly" in the text indicates that, whether explicitly stated or not, these features or functions exist at least in the described example, whether or not they are described as examples, and they may, but not necessarily, exist in some or all other examples. Therefore, "example," "for example," "may," or "possibly" refers to a specific instance of a class of examples. An instance's attribute can be an attribute of only that instance, an attribute of that class, or an attribute of a subclass of a class that includes some, but not all, instances in that class. Therefore, it is implicitly revealed that features described by reference to one example rather than another may be used in that other example as part of a feasible combination where possible, but are not necessarily required to be used in that other example.
[0146] Although examples have been described with reference to various examples in the preceding paragraphs, it should be understood that modifications may be made to the given examples without departing from the scope of the claims.
[0147] The features described above may be used in combinations other than those explicitly described above.
[0148] Although some features have been described with reference to certain characteristics, those features can also be performed by other features, whether or not they are described.
[0149] Although features have been described with reference to some examples, those features may also exist in other examples, whether or not they are described.
[0150] The terms “a,” “an,” or “the” as used in this document have an inclusive rather than exclusive meaning. That is, any reference to X including (a / an / the) Y indicates that X may include only one Y or may include more than one Y, unless the context clearly indicates the opposite. If the use of “a,” “an,” or “the” with an exclusive meaning is intended, it will be clearly stated in the context. In some cases, “at least one” or “one or more” may be used to emphasize the inclusive meaning, but the omission of these terms should not be construed as inferring any exclusive meaning.
[0151] The presence of a feature (or combination of features) in a claim is a reference to that feature or combination of features itself, and also to features (equivalent features) that achieve substantially the same technical effect. Equivalent features include, for example, features that are variations and achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.
[0152] In this specification, adjectives or adjective phrases are used to refer to various examples to describe the characteristics of the examples. Such descriptions of characteristics associated with examples indicate that the characteristic exists exactly as described in some examples and substantially as described in others.
[0153] The foregoing description describes some examples of this disclosure; however, those skilled in the art will recognize that there are alternative structural and methodological features that provide equivalent functionality to specific examples of such structures and features described above, and for the purposes of brevity and clarity, these alternative structural and methodological features have been omitted from the foregoing description. Nevertheless, unless such alternative structural or methodological features are expressly excluded in the foregoing description of the examples of this disclosure, the foregoing description should be interpreted as implicitly including reference to these alternative structural and methodological features that provide equivalent functionality.
[0154] Although the foregoing specification makes efforts to draw attention to those features considered important, it should be understood that an applicant may seek protection by means of the claims for any patentable feature or combination of features mentioned above and / or shown in the drawings, regardless of whether such features are emphasized above.
Claims
1. An apparatus comprising: Components for determining one or more discontinuous reception periods configured for the device; The component is used to make a selection, which is to select a discontinuous reception period for use by the device from one or more discontinuous reception periods configured for the device; as well as A component used to report the selected discontinuous reception period to network nodes.
2. The apparatus according to claim 1, comprising: Components for making another selection of discontinuous reception cycles for use by the device, wherein the other selection is made from the one or more discontinuous reception cycles configured for use by the device; Components for determining the change between the selection and the other selection in one or more discontinuous reception cycles to be used by the device; as well as A component for triggering a report on the other selection of the discontinuous reception period based on the determination that a change exists in the discontinuous reception period to be used by the device.
3. The apparatus of claim 2, wherein making the other selection is at least partially responsive to at least one of the following: The device performs selection or reselection of different cells, wherein the different cells are cells different from the current cell of the device; or Changes were detected in the system information.
4. The apparatus of claim 2 or 3, wherein the selection and / or the other selection is made at least in part based on system information for the cell used by the apparatus.
5. The apparatus according to any one of the preceding claims, wherein the apparatus comprises: A component for receiving requests from the network node, the requests being used to report which discontinuous reception period is being used.
6. The apparatus according to any one of the preceding claims, wherein the component for making the selection and / or the other selection is used to select the discontinuous reception period when the apparatus is in an idle or inactive state.
7. The apparatus according to any one of the preceding claims, the apparatus comprising: A component for receiving paging signals from the network node using the selected discontinuous reception period.
8. The apparatus according to any one of the preceding claims, wherein the discontinuous reception period is one of the following: Discontinuous reception during idle periods; Discontinuous reception during idle extension; Inactive and discontinuous reception; Inactive extended discontinuous reception; Inactive Enhanced Extended Discontinuous Reception.
9. The apparatus according to any one of the preceding claims, wherein the selected discontinuous reception period is reported using at least one of the following: Media access control signaling; Radio resource control signaling; Non-access stratum signaling.
10. The apparatus according to any one of the preceding claims, wherein the selected discontinuous reception period is reported using one of the following: Media access control element; Common control channel logical channel identifier; Common control channel extended logical channel identifier; One or more information elements within a radio resource control message.
11. The apparatus of claim 10, wherein the radio resource control message includes a connection establishment message or a connection restoration message, and wherein the connection establishment message or connection restoration message includes at least one of the following: Radio resource control establishment message; Radio resource control recovery message.
12. The apparatus according to any one of the preceding claims, wherein the apparatus comprises: A component for sending an indication of the discontinuous reception period that the device will use in an idle and / or inactive state, wherein the indication is sent to the network when the device is in a connected state.
13. A network node, comprising: A component for receiving reports of selected discontinuous reception periods being used by the device; as well as A component for paging the device using the selected discontinuous reception period.
14. The network node according to claim 13, wherein the network node comprises: A component for sending a request to a device, the request being used to ask the device to report the discontinuous reception period being used by the device.
15. The network node according to any one of claims 13 to 14, wherein the network node comprises: A component for sending an indication to another network node of the discontinuous reception period being used by the device.