Improvements in user equipment reachability behavior in mobile communications in a suspended non-access stratum signaling state

Abstract

Improved techniques are described for user equipment reachability behavior in a suspended non-access stratum signaling state in mobile communications. A device (e.g., user equipment) changes from idle mode with a suspend indication to the idle mode (without the suspend indication). The device starts a periodic registration update timer in response to the change.

Description

[0001] Cross-references

[0002] This disclosure claims priority to Indian Patent Applications No. 202421028645, No. 202421031135 and No. 202421075736, filed on 8 April 2024, 18 April 2024 and 7 October 2024, respectively, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure relates generally to mobile communications, and more specifically to improvements in the reachability behavior of user equipment (UE) in a suspended non-access stratum (NAS) signaling state during mobile communications. Background Technology

[0004] In wireless communications such as mobile communications under the current 3rd Generation Partnership Project (3GPP) specifications, when using User Plane Cellular Internet of Things (CIoT) EPS optimization, the suspension of NAS signaling connections can be initiated by the network in either Evolved Packet System (EPS) Mobility Management (EMM) connection mode or 5th Generation (5G) Mobility Management (5GMM) connection mode. The resumption of the suspended NAS signaling connection is initiated by the UE.

[0005] Upon receiving an indication from a lower layer that a radio resource control (RRC) connection has been suspended, the UE must enter either an EMM-IDLE mode with a suspension indication or a 5GMM-IDLE mode with a suspension indication, and the UE will not consider the NAS signaling connection released or the secure exchange of NAS messages terminated. On the other hand, a periodic registration update procedure is used to periodically notify the network of the UE's availability or reachability on 3GPP access. This procedure is controlled in the UE by a periodic registration update timer, designated T3512 in the case of 5G New Radio (NR) or T3412 in the case of 4th Generation (4G) Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0006] According to the current 3GPP specification, timer T3412 is started by a UE in EMM-REGISTERED state when leaving EMM-CONNECTED mode. Similarly, timer T3512 is started by a UE in 5GMM-REGISTERED state when leaving 5GMM-CONNECTED mode. When NAS signaling is suspended by the network, the UE must: (1) enter EMM-IDLE mode with a suspension indication and start timer T3412 to perform periodic updates with the network; or (2) enter 5GMM-IDLE mode with a suspension indication and start timer T3512 to perform periodic updates with the network. In addition, according to the current 3GPP specification, the UE must perform a periodic tracking area update (TAU) when timer T3412 expires in EMM-IDLE mode, or perform a periodic registration update when timer T3512 expires in 5GMM-IDLE mode.

[0007] However, at the time of this disclosure, no UE behavior was specified regarding how the UE should periodically update its presence to the network when timer T3412 expires in an EMM-IDLE mode with a pause indication or when timer T3512 expires in a 5GMM-IDLE mode with a pause indication. Therefore, an improved solution is needed for UE reachability behavior in paused NAS signaling states in mobile communications. Summary of the Invention

[0008] The following summary is merely exemplary and is not intended to be limiting in any way. That is, it is provided to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments are further described in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0009] One object of this disclosure is to provide solutions or schemes for addressing the problems described herein. More specifically, it is believed that the various schemes proposed in this disclosure provide improved solutions for UE reachability behavior in suspended NAS signaling states in mobile communications. It is believed that implementations of one or more of the schemes proposed herein can solve or otherwise mitigate the problems described above.

[0010] In one aspect, a method may involve the UE changing from an idle mode with a pause indication to an idle mode without the pause indication. The method may also involve the UE initiating a periodic registration update timer in response to the change.

[0011] On the other hand, one approach could involve the UE changing from an idle mode with a pause indication to an idle mode without the pause indication. The approach could also involve the UE performing an operation regarding a periodically registered update timer in response to this change.

[0012] It is worth noting that while the descriptions provided herein may be within the context of certain radio access technologies, networks, and network topologies such as 5G NR / Beyond Fifth-Generation (B5G) mobile communications, the proposed concepts, schemes, and any variations / derivatives thereof may be, implemented, and carried out in other types of radio access technologies, networks, and network topologies such as, but not limited to, 4G / Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Vehicle-to-Everything (V2X), and non-terrestrial network (NTN) communications. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0013] The accompanying drawings are included to provide a further understanding of this disclosure and are incorporated in and constitute a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0014] Figure 1 This is a diagram of an example network environment in which various solutions and schemes according to this disclosure can be implemented.

[0015] Figure 2 This is a block diagram of an example communication system based on the scheme proposed in this disclosure.

[0016] Figure 3 This is a flowchart of a second example program based on the scheme proposed in this disclosure.

[0017] Figure 4 This is a flowchart of a second example program based on the scheme proposed in this disclosure. Detailed Implementation

[0018] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely examples of the claimed subject matter, which may be embodied in various forms. This disclosure may be embodied in many different forms and should not be construed as limiting it to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that the description of this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0019] Overview

[0020] The embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions for improving UE reachability behavior in suspended NAS signaling states during mobile communications. According to this disclosure, multiple possible solutions may be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of these possible solutions may be implemented in one or another combination.

[0021] Figure 1 An example network environment 100 is shown where various solutions and schemes according to this disclosure can be implemented. Figures 2 to 4 Examples of implementing various proposed schemes in a network environment 100 according to this disclosure are shown below. Figures 1 to 4 Describe the various proposed solutions.

[0022] See Figure 1 Network environment 100 may involve a UE 110, such as a mobile device or smartphone, that wirelessly communicates with wireless network 120 as part of a communication network. Wireless network 120 may be one or more public land mobile networks (PLMNs) including 5G / NR domains, 4G / LTE domains, and second / third generation (2G / 3G) domains. UE 110 may initially wirelessly communicate with wireless network 120 via a base station or network node 125 (e.g., eNB, gNB, or transmit-receive point (TRP)). In network environment 100, UE 110 and wireless network 120 may implement various schemes for improving UE reachability behavior under suspended NAS signaling states in mobile communications, as described herein.

[0023] It is worth noting that although the various proposed schemes may be described individually or separately below, in actual implementations, some or all of the proposed schemes may be used in combination or otherwise implemented in combination. Of course, each of the proposed schemes may also be used individually or separately or otherwise implemented. Furthermore, as used herein, "lower layer" may refer to layers in the 5GMM protocol stack below the radio resource control (RRC) layer, such as the packet data convergence protocol (PDCP) layer, radio control link (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, or similar layers.

[0024] Under the first scheme proposed according to this disclosure, when T3412 expires in EMM-IDLE mode with a pause indication and / or T3512 expires in 5GMM-IDLE mode with a pause indication, the NAS can request the lower layer to resume the suspended RRC connection, and UE 110 and network 120 can enter either EMM-CONNECTED or 5GMM-CONNECTED state. Upon entering 5GMM-CONNECTED mode, network 120 can stop its mobility reachability timer. In any case, if RRC connection resumption fails and UE 110 enters either EMM-IDLE or 5GMM-IDLE without a pause indication, UE 110 can execute the periodic tracking area update procedure in the EMM or the periodic registration update procedure in the 5GMM.

[0025] Under the second scheme proposed according to this disclosure, when T3412 expires in EMM-IDLE mode with a suspension indication and / or T3512 expires in 5GMM-IDLE mode with a suspension indication, the NAS can request the lower layer to resume the suspended RRC connection, and UE 110 and network 120 can enter either EMM-CONNECTED state or 5GMM-CONNECTED state without a suspension indication. Alternatively or additionally, if RRC connection resumption fails and UE 110 can enter either EMM-IDLE or 5GMM-IDLE state without a suspension indication, in both cases, UE 110 can perform a periodic tracking area update procedure in the EMM or a periodic registration update procedure in the 5GMM.

[0026] Under the third scheme proposed in this disclosure, when T3412 expires in EMM-IDLE mode with a pause indication and / or T3512 expires in 5GMM-IDLE mode with a pause indication, the NAS can request the lower layer to release or terminate the RRC connection, and the UE 110 and network 120 can enter EMM-IDLE mode without a pause indication or 5GMM-IDLE mode without a pause indication. Furthermore, the UE 110 can perform a periodic tracking area update procedure or a periodic registration of updated procedures.

[0027] Under the fourth scheme proposed in this disclosure, when UE 110 enters 5GMM-IDLE mode with a pause indication, UE 110 can initiate T3512. Alternatively or additionally, when T3512 expires, UE 110 in 5GMM-IDLE mode with a pause indication on 3GPP access can perform a periodic registration procedure, unless UE 110 is registered for emergency service. Alternatively or additionally, if UE 110 enters EMM-IDLE mode with a pause indication, UE 110 can initiate T3412. Alternatively or additionally, when T3412 expires, UE 110 in EMM-IDLE mode with a pause indication on 3GPP access can perform a periodic TAU, unless UE 110 is registered for emergency service.

[0028] Under the fifth scheme proposed in this disclosure, UE 110 may apply the same or similar behavior to that in 5GMM-IDLE mode without a pause indication for the start, stop, and expiration of timer T3512 in 5GMM-IDLE mode with a pause indication. Alternatively or additionally, UE 110 may apply the same or similar behavior to that in EMM-IDLE mode without a pause indication for the start, stop, and expiration of timer T3412 in EMM-IDLE mode with a pause indication.

[0029] Under the sixth scheme proposed according to this disclosure, UE 110 in 5GMM-IDLE mode with a pause indication can behave as in 5GMM-IDLE, and / or except for processing related to N1 NAS signaling connection and / or secure exchange of NAS messages and / or directly restoring the connection for uplink signaling. Similarly, UE 110 in EMM-IDLE mode with a pause indication can behave as in EMM-IDLE, and / or except for processing related to NAS signaling connection and / or secure exchange of NAS messages and / or directly restoring the connection for uplink signaling.

[0030] Under the seventh scheme proposed in this disclosure, when UE 110 enters an idle mode with a pause indication, UE 110 may not activate T3512 in the 5th Generation System (5GS) or T3412 in the Evolved Packet System (EPS).

[0031] Under the eighth scheme proposed according to this disclosure, when UE 110 moves from or changes from an idle mode with a pause indication (e.g., 5GMM-IDLE or EMM-IDLE) to an idle mode, UE 110 can initiate T3512 in 5GS (or T3412 in EPS). Under this proposed scheme, UE 110 can apply 5GMM connection behavior to the idle mode with a pause indication for periodically registering update-related procedures or methods. For example, if during the registration process, the Access and Mobility Management Function (AMF) of Network 120 does not indicate "Support for Strict Periodic Registration Timer" in the Mobile Initiated Connection Only (MICO) indication element (IE) to UE 110, then timer T3512 can be reset and start with its initial value when UE 110 changes from 5GMM-CONNECTED mode or 5GMM-IDLE mode with pause indication on 3GPP access to 5GMM-IDLE mode on 3GPP access. Furthermore, timer T3512 can be stopped when UE 110 enters 5GMM-CONNECTED mode, 5GMM-IDLE mode with pause indication, or 5GMM-DEREGISTERED state on 3GPP access.

[0032] Under the ninth scheme proposed in this disclosure, when UE 110 moves or changes from an idle mode with a pause indication to an idle mode (or idle mode) without a pause indication, UE 110 can initiate a NAS procedure (e.g., if no NAS procedure is in progress). This NAS procedure can be, for example, a tracking area update procedure in EPS, or a mobility registration update procedure in 5G or 6G. The idle mode with a pause indication can be an EMM-IDLE mode with a pause indication, a 5GMM-IDLE mode with a pause indication, or a 6GMM-IDLE mode with a pause indication.

[0033] Example Implementation

[0034] Figure 2An example communication system 200 having at least one example device 210 and one example device 220 according to an embodiment of the present disclosure is illustrated. Each of devices 210 and 220 can perform various functions to implement the schemes, techniques, procedures, and methods described herein for improving UE reachability behavior in a suspended NAS signaling state in mobile communications, including the various schemes described above with respect to the various proposed designs, concepts, schemes, systems, and methods described above, including network environment 100, and the procedures described below.

[0035] Each of devices 210 and 220 can be part of an electronic device, which can be a network device or UE (e.g., UE 110), such as a portable or mobile device, wearable device, vehicle unit or vehicle, wireless communication device, or computing device. For example, each of devices 210 and 220 can be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing equipment such as a tablet computer, laptop computer, or notebook computer. Each of devices 210 and 220 can also be part of a machine-type device, which can be an IoT device, such as a non-movable or fixed device, home appliance, roadside unit (RSU), wired communication device, or computing device. For example, each of devices 210 and 220 can be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. When implemented in or as a network device, device 210 and / or device 220 may be implemented in an eNB in ​​an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IoT network.

[0036] In some implementations, each of devices 210 and 220 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more complex instruction-set computing (CISC) processors, or one or more reduced instruction-set computing (RISC) processors. In the various embodiments described above, each of devices 210 and 220 may be implemented in or as a network device or UE. Each of devices 210 and 220 may include... Figure 2 At least some of the components shown are, for example, processor 212 and processor 222, respectively. Each of devices 210 and 220 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solution of this disclosure, and therefore, for the sake of brevity, such components of devices 210 and 220 are not described in detail. Figure 2 It is shown in the text and is not described in the following text.

[0037] In one aspect, each of processors 212 and 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "a processor" is used herein to refer to processors 212 and 222, each of processors 212 and 222 may include multiple processors in some embodiments and a single processor in other embodiments, according to this disclosure. In another aspect, each of processors 212 and 222 may be implemented as hardware (and optionally firmware) having electronic components including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, configured and arranged to achieve a specific purpose according to this disclosure. In other words, in at least some embodiments, each of processors 212 and 222 is a dedicated machine specifically designed, arranged, and configured to perform a specific task, including tasks related to improved UE reachability behavior in suspended NAS signaling states during mobile communications, according to various embodiments of this disclosure.

[0038] In some embodiments, device 210 may further include a transceiver 216 coupled to processor 212. Transceiver 216 may be capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 216 may be capable of wirelessly communicating with different types of wireless networks using different radio access technologies (RATs). In some embodiments, transceiver 216 may be equipped with multiple antenna ports (not shown), such as, for example, four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 220 may further include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 226 may be capable of wirelessly communicating with different types of UE / wireless networks using different RATs. In some embodiments, transceiver 226 may be equipped with multiple antenna ports (not shown), such as, for example, four antenna ports. In other words, transceiver 226 can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0039] In some embodiments, device 210 may further include memory 214 coupled to and accessible by processor 212 and storing data therein. In some embodiments, device 220 may further include memory 224 coupled to and accessible by processor 222 and storing data therein. Each of memory 214 and memory 224 may include a type of random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively or additionally, each of memory 214 and memory 224 may include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of memories 214 and 224 may include a type of non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0040] Each of devices 210 and 220 may be a communication entity capable of communicating with each other using various proposed schemes according to this disclosure. For illustrative purposes and without limitation, the capabilities of device 210 as a UE (e.g., UE 110) and device 220 as a network node (e.g., network node 125) of a network (e.g., a wireless network 120 as a 5G / NR mobile network) are described below in the context of example procedures 300 and 400.

[0041] Example Process

[0042] Figure 3 An example program 300 according to an embodiment of the present disclosure is shown. Program 300 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, program 300 may represent one aspect of proposed concepts and schemes regarding improvements to UE reachability behavior in a suspended NAS signaling state in mobile communications, according to the present disclosure. Program 300 may include one or more operations, actions, or functions as shown in one or more of program blocks 310 and sequence blocks 320. Although shown as discrete program blocks, the individual program blocks of program 300 may be divided into additional program blocks, merged into fewer program blocks, or deleted, depending on the desired implementation. Furthermore, the program blocks / subprogram blocks of program 300 may be arranged in... Figure 3 The program can be executed in the order shown, or alternatively in a different order. Additionally, one or more of the program blocks / subroutines of program 300 can be executed repeatedly or iteratively. Program 300 can be implemented by or in devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, program 300 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity such as a network (e.g., wireless network 120) or a base station (e.g., network node 125). Program 300 may begin with program block 310.

[0043] At program block 310, program 300 may involve the processor 212 of device 210, which is UE 110, changing from an idle mode with a pause indication to the idle mode (without the pause indication). Program 300 may proceed from program block 310 to program block 320.

[0044] At program block 320, program 300 may involve processor 212 starting a periodic registration update timer in response to the change.

[0045] In some implementations, when starting the periodic registration update timer, program 300 may involve processor 212 starting timer T3512 or timer T3412.

[0046] In some implementations, when changed, program 300 may involve processor 212: (a) changing from a 5GMM-IDLE mode with the pause instruction to the 5GMM-IDLE mode; or (b) changing from an EMM-IDLE mode with the pause instruction to the EMM-IDLE mode.

[0047] Figure 4 An example program 400 according to an embodiment of the present disclosure is shown. Program 400 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, program 400 may represent one aspect of proposed concepts and schemes regarding improvements to UE reachability behavior in a suspended NAS signaling state in mobile communications according to the present disclosure. Program 400 may include one or more operations, actions, or functions as shown in one or more of program blocks 410 and 420. Although shown as discrete program blocks, the individual program blocks of program 400 may be divided into additional program blocks, merged into fewer program blocks, or deleted, depending on the desired implementation. Furthermore, the program blocks / subprogram blocks of program 400 may be arranged in... Figure 4 The program is executed in the order shown, or alternatively in a different order. Additionally, one or more of the program blocks / subroutines of program 400 may be executed repeatedly or iteratively. Program 400 may be implemented by or in devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, program 400 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity such as a network (e.g., wireless network 120) or a base station (e.g., network node 125). Program 400 may begin with program block 410.

[0048] At program block 410, program 400 may involve the processor 212 of device 210, which is UE 110, changing from an idle mode with a pause indication to the idle mode (without the pause indication). Program 400 may proceed from program block 410 to program block 420.

[0049] At block 420, program 400 may involve processor 212 performing operations related to periodically registering and updating timers in response to the change.

[0050] In some implementations, when performing the operation concerning the periodic registration update timer, program 400 may involve processor 212 starting the periodic registration update timer.

[0051] In some implementations, when starting the periodic registration update timer, program 400 may involve processor 212 starting timer T3512 or timer T3412.

[0052] In some implementations, when changed, program 400 may involve processor 212: (a) changing from a 5GMM-IDLE mode with the pause instruction to the 5GMM-IDLE mode; or (b) changing from an EMM-IDLE mode with the pause instruction to the EMM-IDLE mode.

[0053] In some implementations, program 400 may also involve processor 212 not starting the periodic registration update timer when the UE enters the idle mode with the pause indication.

[0054] In some implementations, in response to the idle mode having the pause indication being a 5GMM-IDLE mode having the pause indication, program 400 may also involve processor 212 acting as in 5GMM-IDLE mode, except for processing one or more of the following: (a) NAS signaling connection (e.g., N1 NAS signaling connection); (b) secure exchange of one or more NAS messages; and (c) directly restoring the NAS signaling connection for uplink signaling.

[0055] In some implementations, in response to the idle mode having the pause indication being an EMM-IDLE mode having the pause indication, program 400 may also involve processor 212 acting as in 5GMM-IDLE mode, except for processing one or more of the following: (a) NAS signaling connection (e.g., N1 NAS signaling connection); (b) secure exchange of one or more NAS messages; and (c) directly restoring the NAS signaling connection for uplink signaling.

[0056] In some embodiments, prior to this change, program 400 may also involve processor 212 applying the same or similar behavior to the start, stop, and expiration of the periodic registration update timer in the idle mode with the pause indication, as in the idle mode without the pause indication. In some embodiments, the periodic registration update timer may include a T3512 timer or a T3412 timer.

[0057] Additional notes

[0058] The topics described herein sometimes illustrate different components contained within or connected to different other components. It should be understood that such depicted architectures are merely examples, and many other architectures that achieve the same functionality can indeed be implemented. Conceptually, any arrangement of components that achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined herein to achieve a particular function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interacting components and / or wirelessly interactive and / or logically interacting and / or logically interactive components.

[0059] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, the various singular / plural arrangements are explicitly stated herein.

[0060] Furthermore, those skilled in the art will understand that, in general, the terms used herein, particularly in the appended claims (e.g., in the body of the appended claims), are typically intended to be “open-ended” terms; for example, the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “including but not limited to,” and so on. Those skilled in the art will also understand that if there is an intent to indicate a specific number recited in the introduced claim, such intent will be explicitly stated in that claim, and where no such statement exists, such intent is not present. For example, to aid understanding, the appended claims below may contain the use of the introductory phrases “at least one” and “one or more” to introduce the recitation of the claim. However, the use of such phrases should not be construed as implying that the introduction of a claim recount by the indefinite article "a (a)" or "an" limits any particular claim containing such an introduced claim recount to an embodiment containing only one such recount, even when the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a (a)" or "an," for example, "a (a)" and / or "an" should be interpreted as meaning "at least one" or "one or more"; the same applies to the use of definite articles used to introduce a claim recount. Furthermore, even when a specific number of introduced claims is explicitly stated, those skilled in the art will recognize that such statements should be interpreted as meaning at least the number stated; for example, in the absence of other modifiers, simply stating "two recounts" means at least two recounts, or two or more recounts. Furthermore, in cases where conventions such as "at least one of A, B, and C" are used, generally, such structures are intended to be understood by those skilled in the art as the meaning of that convention. For example, "a system having at least one of A, B, and C" will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In cases where conventions such as "at least one of A, B, or C" are used, generally, such structures are intended to be understood by those skilled in the art as the meaning of that convention. For example, "a system having at least one of A, B, or C" will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will also understand that, whether in the specification, claims, or drawings, any transition words and / or phrases that present two or more alternative terms should be understood to contemplate the possibility of including one, any, or both of these terms.For example, the phrase “A or B” would be understood to include the possibility of “A” or “B” or “A and B”.

[0061] Based on the foregoing, it will be understood that various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: The user equipment's processor changes from an idle mode with a pause indicator to that idle mode; as well as The processor initiates a periodic registration update timer in response to the change.

2. The method of claim 1, wherein starting the periodic registration update timer includes starting the T3512 timer or the T3412 timer.

3. The method of claim 1, wherein the change comprises: Change from the fifth-generation mobility management idle mode with the pause instruction to the fifth-generation mobility management idle mode; or Change from the Evolved Packet System Mobility Management idle mode with the pause instruction to the Evolved Packet System Mobility Management idle mode.

4. A method comprising: The user equipment's processor changes from an idle mode with a pause indicator to that idle mode; as well as The processor performs operations related to periodically registering and updating the timer in response to this change.

5. The method of claim 4, wherein performing operations related to the periodic registration update timer includes starting the periodic registration update timer.

6. The method of claim 5, wherein starting the periodic registration update timer includes starting the T3512 timer or the T3412 timer.

7. The method of claim 4, wherein the change comprises changing from a fifth-generation mobility management idle mode having the pause instruction to the fifth-generation mobility management idle mode.

8. The method of claim 4, wherein the change comprises changing from an EPC Mobility Management Idle Mode having the pause instruction to the EPC Mobility Management Idle Mode.

9. The method of claim 4, further comprising: When the user equipment enters the idle mode with the pause instruction, the processor does not start the periodic registration update timer.

10. The method of claim 4, wherein the idle mode having the pause indication includes a fifth-generation mobility management idle mode having the pause indication, further comprising: The processor behaves as if it were in fifth-generation mobility management idle mode, except for one or more of the following: Non-access stratum signaling connection; Secure exchange of one or more non-access stratum messages; and The non-access stratum signaling connection is directly restored for uplink signaling.

11. The method of claim 4, wherein the idle mode in response to the pause indication includes an Evolved Packet System Mobility Management idle mode with the pause indication, further comprising: The processor behaves as if it were in the Evolved Packet System Mobility Management idle mode, except for one or more of the following: Non-access stratum signaling connection; Secure exchange of one or more non-access stratum messages; and The non-access stratum signaling connection is directly restored for uplink signaling.

12. The method of claim 4, further comprising, prior to the change: The processor applies the same or similar behavior to that in the idle mode without the pause indication for starting, stopping, and expiring the periodic registration update timer in the idle mode with the pause indication.

13. The method of claim 12, wherein the periodic registration update timer includes a T3512 timer or a T3412 timer.

14. An apparatus that can be implemented in a user equipment, comprising: A transceiver, configured to perform wireless communication; as well as A processor, coupled to the transceiver and configured to perform a plurality of operations, including: Change from the idle mode with the pause indicator to this idle mode; as well as In response to this change, perform operations related to periodically registering and updating timers.

15. The apparatus of claim 14, wherein performing an operation with respect to the periodic registration update timer includes starting the periodic registration update timer, and wherein starting the periodic registration update timer includes starting timer T3512 or timer T3412.

16. The apparatus of claim 14, wherein the change includes Change from the fifth-generation mobility management idle mode with the pause instruction to the fifth-generation mobility management idle mode; or Change from the Evolved Packet System Mobility Management idle mode with the pause instruction to the Evolved Packet System Mobility Management idle mode.

17. The apparatus of claim 14, wherein the processor is further configured to perform an operation including: When the user equipment enters the idle mode with the pause indication, the periodic registration update timer is not started.

18. The apparatus of claim 14, wherein, In response to the idle mode having the pause indication, including a fifth-generation mobility management idle mode having the pause indication, the processor is further configured to perform a plurality of operations, the plurality of operations including: The processor behaves as if it were in fifth-generation mobility management idle mode, except for one or more of the following: Non-access stratum signaling connection; Secure exchange of one or more non-access stratum messages; and The non-access stratum signaling connection is directly restored for uplink signaling.

19. The apparatus of claim 14, wherein, In response to the idle mode having the pause indication, including the Evolved Packet System Mobility Management idle mode having the pause indication, the processor is further configured to perform a plurality of operations, the plurality of operations including: The processor behaves as if it were in the Evolved Packet System Mobility Management idle mode, except for one or more of the following: Non-access stratum signaling connection; Secure exchange of one or more non-access stratum messages; and The non-access stratum signaling connection is directly restored for uplink signaling.

20. The apparatus of claim 14, wherein prior to the change, the processor is further configured to perform a plurality of operations, the plurality of operations including: The processor applies the same or similar behavior to that in the idle mode without the pause indication for starting, stopping, and expiring the periodic registration update timer in the idle mode with the pause indication. The periodic registration update timer includes either the T3512 timer or the T3412 timer.

Images