Service-free optimization in non-access stratum signaling connections and mobile communications

Abstract

Relates to a non-access-strata (non-access-strata) method in mobile communication, in particular to a non-access-strata (non-access-strata; the invention relates to a technique for NAS signaling connection and no-service optimization. A device (e.g., user equipment; (e.g., UE)) into a NO-CELL-AVAILABLE state due to the unavailable period being activated. The device also releases the N1 NAS signaling connection locally.

Description

[0001] Cross-references

[0002] This disclosure prioritizes Indian Patent Application No. 202321061015, filed on September 11, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically to non-access-stratum (NAS) signaling connectivity and no-service optimization in mobile communications. Background Technology

[0004] In current Generation Partnership Project (3GPP) specifications for wireless communications (e.g., mobile communications), if the user equipment (UE) and network support unavailability cycles, and an event is triggered within the UE causing it to become unavailable for a certain period, the UE can store its Generation Mobility Management (5GMM) and Generation Session Management (5GSM) contexts in the Universal Subscriber Identity Module (USIM) or non-volatile memory for reuse after the unavailability cycle. To activate an unavailability cycle, the UE provides the duration of the unavailability cycle during the registration or deregistration process (see 3GPP Technical Specification (TS) 23.501 and 3GPP TS 23.502). Support for unavailability cycles is negotiated during the registration process. If the UE provided an unreachable period duration during the previous registration or deregistration process, the network's Access & Mobility Management Function (AMF) will consider the UE unreachable until it re-registers to obtain normal service without providing an unreachable period duration. During the registration process, the AMF can determine the value of the periodic registration update timer (T3512) based on the unreachable period duration and provide it to the UE. After the registration process is completed with the UE providing the unreachable period duration, the AMF releases the N1 signaling connection.

[0005] However, when a UE enters the NO-CELL-AVAILABLE state for one or more predefined reasons, and the UE is in connected mode or N1 non-access-stratum (NAS) mode signaling has not yet been released, the UE's behavior is undefined. Therefore, solutions for NAS signaling connectivity and no-service optimization are needed in mobile communications. Summary of the Invention

[0006] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further described in the detailed description below. Therefore, the following abstract is not intended to define the essential features of the claims, nor is it intended to define the scope of the claims.

[0007] The purpose of this disclosure is to provide solutions or strategies for addressing the problems described herein. More specifically, the various strategies proposed in this disclosure are believed to provide solutions related to NAS signaling connectivity and serverless optimization in mobile communications. It is believed that implementations of one or more strategies proposed in this disclosure can solve or mitigate the aforementioned problems.

[0008] One approach involves the UE entering a NO-CELL-AVAILABLE state due to an activated unavailable cycle. Another approach involves the UE locally releasing the N1 NAS signaling connection.

[0009] On the other hand, one approach may involve the UE entering a NO-CELL-AVAILABLE state for a predefined reason. Another approach may involve the UE releasing the N1 NAS signaling connection.

[0010] It is worth noting that although the content described in this article may be presented in the context of certain wireless access technologies, networks, and network topologies, such as 5G... th generation (5) th This refers to Generation (5G) / New Radio (NR) / Beyond Fifth-Generation (B5G) mobile communications, but the proposed concepts, strategies, and any variations / derivatives thereof can be implemented, used, or implemented by other types of radio access technologies, networks, and network topologies, such as, but not limited to, 4G. th generation (4) thGeneration (4G) / Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrowband 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

[0011] The accompanying drawings are included in this disclosure to provide a further understanding of the disclosure and are incorporated into and constitute a part of this disclosure. The drawings illustrate embodiments of the 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.

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

[0013] Figure 2 This is a block diagram of an example communication system, consistent with an implementation of this disclosure.

[0014] Figure 3 This is a flowchart of a second example process, consistent with an implementation of this disclosure.

[0015] Figure 4 This is a flowchart of a second example process, consistent with an implementation of this disclosure. Detailed Implementation

[0016] Detailed embodiments and implementations of the claims of this application are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the subject matter of the claims and may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to 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.

[0017] Overview

[0018] The implementation of this disclosure relates to various technologies, methods, schemes, and / or solutions related to non-access-stratum (NAS) signaling connectivity and no-service optimization in mobile communications. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in some combination.

[0019] Figure 1 An example network environment 100 is shown, in which various solutions and schemes of this disclosure can be implemented. Figures 2 to 4 This document demonstrates implementation examples of various proposed solutions in network environment 100, based on this disclosure. The following description of the various proposed solutions will be combined with… Figures 1 to 4 Please provide an explanation.

[0020] See Figure 1 Network environment 100 may involve a UE 110 (e.g., a mobile device or smartphone) wirelessly communicating with a wireless network 120 (as part of a communication network). Wireless network 120 may be a Public Land Mobile Network (PLMN) encompassing 5G / NR and 4G / LTE domains. UE 110 may initially communicate wirelessly with wireless network 120 via a base station or network node 125 (e.g., eNB, gNB, or transmit-receive point (TRP)). As described herein, in network environment 100, UE 110 and wireless network 120 may implement various schemes related to NAS signaling connectivity and no-service optimization in mobile communications, in accordance with this disclosure.

[0021] It is worth noting that although the various proposed schemes may be described separately or individually below, in actual implementation, some or all of the proposed schemes may be used in combination or implemented. Of course, each proposed scheme may also be used or implemented individually or separately. In addition, as mentioned in this article, the lower layer may refer to the layers below the radio resource control (RRC) layer in the 5GMM protocol stack, such as the packet data convergence protocol (PDCP) layer, radio control link (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.

[0022] According to the scheme proposed in this disclosure, when UE 110 enters the NO-CELL-AVAILABLE state for one or more predefined reasons, UE 110 may perform one or more of a number of possible operations. These operations include: (1) starting the T3540 timer; (2) locally releasing the N1 NAS signaling connection (e.g., releasing the N1 NAS signaling connection without notifying the radio network 120); (3) activating an unavailable period when the N1 NAS signaling connection is released by the radio network 120 or due to the expiration of the T3540 timer; and (4) entering the NO-CELL state when the N1 NAS signaling connection is released by the radio network 120 or due to the expiration of the T3540 timer. The one or more reasons may include: the duration of the unavailable period activated by the UE; and / or the unavailable period activated for discontinuous coverage; and / or the unavailable period activated for other reasons (e.g., section 5.3.26 of 3GPP TS 24.501); and / or the access stratum (AS) being deactivated by 3GPP access; and / or the unavailable period being activated; and / or the AS being deactivated for discontinuous coverage; and / or the AS being deactivated for other reasons (e.g., section 5.3.26 of 3GPP TS 24.501); and / or the UE's current timestamp being greater than or equal to the start of the unavailable period.

[0023] As an example of implementation, when UE 110 enters the 5GMM-DEREGISTERED.PLMN-SEARCH, 5GMM-REGISTERED.PLMN-SEARCH, 5GMM-DEREGISTERED.NO-CELL-AVAILABLE, or 5GMM-REGISTERED.CELL-AVAILABLE state, if the T3540 timer is not running, UE 110 can locally release the N1 NAS signaling connection. As another example of implementation, when UE 110 activates an unavailable period through the registration procedure, after the procedure is successfully completed and the N1 NAS signaling connection is released, UE 110 can enter the 5GMM-REGISTERED.NO-CELL-AVAILABLE state. As yet another example of implementation, when UE 110 activates an unavailable period through the deregistration procedure, after the procedure is successfully completed and the N1 NAS signaling connection is released, UE 110 can enter the 5GMM-DEREGISTERED.NO-CELL-AVAILABLE state.

[0024] Exemplary Implementation

[0025] Figure 2An example communication system 200 is shown, comprising at least one example device 210 and at least one example device 220, implemented according to the present disclosure. Devices 210 and 220 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to NAS signaling connectivity and No-Service optimization in mobile communications, including the schemes related to the various proposed designs, concepts, schemes, systems, and methods, including network environment 100, and the processes described below.

[0026] Both devices 210 and 220 can be part of an electronic device, which can be a network device or a UE (e.g., UE 110), such as a portable or mobile device, wearable device, in-vehicle device or vehicle, wireless communication device, or computing device. For example, 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 device such as a tablet, laptop, or notebook computer. Devices 210 and 220 can also be part of a machine-type device, which can be an IoT device, such as a non-mobile or fixed device, home appliance, roadside unit (RSU), wired communication device, or computing device. For example, devices 210 and 220 can be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. When implemented as a network device, devices 210 and / or 220 can be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IoT network.

[0027] In some implementations, devices 210 and 220 may take the form of 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 all the above-mentioned embodiments, devices 210 and 220 may be implemented as network devices or UEs. Devices 210 and 220 may each include... Figure 2 At least some components are shown, such as processor 212 and processor 222. Devices 210 and 220 may also include one or more other components unrelated to the solutions presented in this disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity, Figure 2 These components are not shown and will not be described below.

[0028] On one hand, 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 "processor" is used herein to refer to processors 212 and 222, each of processors 212 and 222 may include multiple processors in some implementations and a single processor in other implementations, according to this disclosure. On the other hand, each of processors 212 and 222 may be implemented in hardware (and optionally firmware) and includes electronic components, such as, 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 variable capacitors, which are configured and arranged according to this disclosure to achieve a particular purpose. In other words, in at least some implementations, each of processors 212 and 222 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to NAS signaling connectivity and No-Service optimization in mobile communications, according to various implementations of this disclosure.

[0029] In some implementations, device 210 may further include a transceiver 216 coupled to processor 212. Transceiver 216 can wirelessly transmit and receive data. In some implementations, transceiver 216 can wirelessly communicate with different types of wireless networks using different radio access technologies (RATs). In some implementations, transceiver 216 may be equipped with multiple antenna ports (not shown), such as 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 implementations, device 220 may further include a transceiver 226 coupled to processor 222. Transceiver 226 may contain transceivers capable of wirelessly transmitting and receiving data. In some implementations, transceiver 226 can wirelessly communicate with different types of UE / wireless networks using different RATs. In some implementations, transceiver 226 may be equipped with multiple antenna ports (not shown), such as four antenna ports. In other words, transceiver 226 can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0030] In some implementations, device 210 may further include a memory 214 coupled to and accessible by processor 212 for storing data. In some implementations, device 220 may further include a memory 224 coupled to and accessible by processor 222 for storing data. Each of memory 214 and memory 224 may include a 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 read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of memories 214 and 224 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0031] Each of devices 210 and 220 may be a communication entity capable of communicating using various schemes proposed according to this disclosure. For the purpose of illustration 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 conjunction with example flows 300 and 400.

[0032] Example Process

[0033] Figure 3Example flow 300 implemented according to this disclosure is illustrated. Flow 300 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 300 may represent one aspect of proposed concepts and schemes related to NAS signaling connectivity and no-service optimization in mobile communications according to this disclosure. Flow 300 may include one or more operations, actions, or functions, as shown in flow blocks 310 and 320. Although represented as discrete flow blocks, the individual flow blocks of flow 300 may be divided into more flow blocks, merged into fewer flow blocks, or omitted, depending on the required implementation. Furthermore, the flow blocks / sub-flow blocks of flow 300 may be arranged according to... Figure 3 The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 300 can be executed repeatedly or iteratively. Process 300 can be implemented by devices 210 and 220 or any variations thereof. For illustrative purposes only and without limitation, process 300 is described below as device 210 as a UE (e.g., UE 110) and device 220 as a communication entity (e.g., network node or base station (e.g., network node 125)) of a network (e.g., wireless network 120). Process 300 may begin with process block 310.

[0034] At 310, process 300 may involve the processor 212 of device 210 entering a NO-CELL-AVAILABLE state due to an unavailable cycle being activated. Process 300 can then continue from 310 to 320.

[0035] At 320, process 300 may involve the processor 212 of device 210 releasing the N1 NAS signaling connection via transceiver 216.

[0036] In some implementations, upon release, process 300 may involve the processor 212 of device 210 locally releasing the N1 NAS signaling connection without notifying the network.

[0037] Figure 4 Example flow 400 implemented according to this disclosure is illustrated. Flow 400 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 400 may represent one aspect of proposed concepts and schemes related to NAS signaling connectivity and no-service optimization in mobile communications according to this disclosure. Flow 400 may include one or more operations, actions, or functions, as shown in flow blocks 410 and 420. Although represented as discrete flow blocks, the individual flow blocks of flow 400 may be divided into more flow blocks, merged into fewer flow blocks, or omitted, depending on the required implementation. Furthermore, the flow blocks / sub-flow blocks of flow 400 may be arranged according to... Figure 4The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 400 can be executed repeatedly or iteratively. Process 400 can be implemented by devices 210 and 220 or any variations thereof. For illustrative purposes only and without limitation, process 400 is described below as device 210 as a UE (e.g., UE 110) and device 220 as a network (e.g., wireless network 120) communication entity (e.g., a network node or base station (e.g., network node 125)). Process 400 may begin with process block 410.

[0038] At 410, process 400 may involve the processor 212 of device 210 entering a NO-CELL-AVAILABLE state for a predefined reason. Process 400 can then continue from 410 to 420.

[0039] At 420, process 400 may involve the processor 212 of device 210 releasing the N1 NAS signaling connection via transceiver 216.

[0040] In some implementations, upon release, process 400 may involve the processor 212 of device 210 locally releasing the N1 NAS signaling connection without notifying the network (e.g., via wireless network 120 of device 220 as network node 125).

[0041] In some implementations, the predefined reason may include the duration of the UE activation unavailability period.

[0042] In some implementations, the predefined reason can include activating an unavailable cycle for discontinuous coverage.

[0043] In some implementations, the predefined reason can include activating the unavailable cycle for reasons other than discontinuous coverage.

[0044] In some implementations, the predefined reason may include deactivating the AS for 3GPP access.

[0045] In some implementations, the predefined reason may include the activation of an unavailable cycle.

[0046] In some implementations, the predefined reason may include deactivating the AS for discontinuous coverage.

[0047] In some implementations, the predefined reason can include reasons other than discontinuous coverage to activate the AS.

[0048] In some implementations, the predefined reason may include the current timestamp of device 210 being greater than or equal to the start of an unavailable period.

[0049] In some implementations, process 400 may also involve processor 212 starting the T3540 timer.

[0050] In some implementations, process 400 may also involve processor 212 activating an unavailable cycle when the N1 NAS signaling connection is released by the network or due to the expiration of the T3540 timer.

[0051] In some implementations, process 400 may also involve processor 212 entering a NO-CELL state when the N1 NAS signaling connection is released by the network or due to the expiration of the T3540 timer.

[0052] Additional notes

[0053] The topics described herein sometimes demonstrate that different components are contained within or connected to different other components. It should be understood that such architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associating can also be considered “operably connected” or “operably coupled” to achieve the desired function, and any two components that can be so associating can also be considered “operably coupled” to achieve the desired function. Specific examples of operable coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0054] Furthermore, regarding the use of almost all plural and / or singular terms in this article, those skilled in the art can appropriately convert plural to singular and / or singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed in this article.

[0055] Furthermore, those skilled in the art will understand that the terminology used herein, particularly in appended claims, such as the body portion of appended claims, is generally intended as “open” terms. For example, the word “comprising” should be interpreted as “including but not limited to,” the word “having” should be interpreted as “at least having,” and the word “including” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also further understand that if a specific quantity defining the claim is expressly stated in the claim, that intention is explicitly stated in the claim; otherwise, that intention does not exist. For example, for ease of understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce the claim definition. However, the use of such phrases should not be interpreted as limiting any particular claim containing such a definition to only one such definition, even if the same claim contains the introductory phrases “one or more” or “at least one” and indefinite articles such as “a,” for example, “a” should be interpreted as “at least one” or “one or more”; the same applies to definite articles used to introduce the claim definition. Furthermore, even when a specific quantity is explicitly stated in the introductory claims, those skilled in the art will recognize that such a statement should be interpreted as at least the stated quantity. For example, the phrase "two limitations" alone, without other modifiers, implies at least two limitations, or two or more limitations. Additionally, when using conventions such as "at least one A, B, and C," such structures are generally intended to be interpreted in a way that those skilled in the art would understand. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Similarly, when using conventions such as "at least one A, B, or C," such structures are generally intended to be interpreted in a way that those skilled in the art would understand. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Those skilled in the art will further understand that virtually any extractive term and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include the possibility of containing only one term, any two terms, or all of the terms. For example, the phrase "A or B" would be understood to include the possibility of containing "A" or "B" or "A and B".

[0056] As can be seen from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications can 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: Because the unavailable cycle is activated, the user equipment's processor enters the NO-CELL-AVAILABLE state; as well as The processor releases the N1 non-access stratum signaling connection.

2. The method of claim 1, wherein the release includes locally releasing the N1 non-access stratum signaling connection without notifying the network.

3. A method, comprising: Due to a predefined reason, the user equipment's processor enters a NO-CELL-AVAILABLE state; as well as The processor releases the N1 non-access stratum signaling connection.

4. The method of claim 3, wherein the release includes locally releasing the N1 non-access stratum signaling connection without notifying the network.

5. The method of claim 3, wherein the predefined reason includes the duration of the user equipment activation unavailability period.

6. The method of claim 3, wherein the predefined reason includes activating an unavailable period for discontinuous coverage.

7. The method of claim 3, wherein the predefined reason includes activating an unavailable period for reasons other than discontinuous coverage.

8. The method of claim 3, wherein the predefined reason includes deactivating the access layer for third-generation partner program access.

9. The method of claim 3, wherein the predefined reason includes an unavailable cycle being activated.

10. The method of claim 3, wherein the predefined reason includes deactivating the access layer for discontinuous coverage.

11. The method of claim 3, wherein the predefined reason includes deactivating the access layer for reasons other than discontinuous coverage.

12. The method of claim 3, wherein the predefined reason includes the user equipment’s current timestamp being greater than or equal to the start of an unavailable period.

13. The method of claim 3, further comprising: The T3540 timer is started by this processor.

14. The method of claim 3, further comprising: When the N1 non-access stratum signaling connection is released by the network or due to the expiration of the T3540 timer, the processor activates an unavailable period.

15. The method of claim 3, further comprising: When the N1 non-access stratum signaling connection is released by the network or due to the expiration of the T3540 timer, the processor enters the NO-CELL state.

Images