User equipment, network node and method for indicating unavailable cycle start time in congested communication network

Abstract

A user equipment (UE), a network node and a method are provided for indicating an MM procedure to activate an unavailable period during an enabled non-access stratum (NAS) congestion in a wireless communication network. The method comprises the following steps: detecting that a timer T3346 is running or is stopped; and reporting, by a user equipment (UE), an unavailability message and indicating a start time of the unavailability period while the timer T3346 is running or deactivated.

Description

[0001] This application claims the benefit of Indian Provisional Application Serial No. 202321056544, filed on August 23, 2023, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure generally relates to a user equipment, a network node, and a method thereof, and more specifically to a user equipment, a network node, and a method for indicating the start time of an unavailable period in a congested communication network. Background Technology

[0003] Before an event that renders a user equipment (UE) unavailable begins, the UE includes an indication and an unavailability type, a start time of the unavailability period (if known), and a duration of the unavailability period (if known), and triggers a mobility registration update or a UE-initiated deregistration process.

[0004] However, the behavior of the UE is not yet defined when the UE needs to indicate the start time of the "unavailable period" and the backoff timer (e.g., T3346) is running. Summary of the Invention

[0005] This disclosure relates to a user equipment (UE), a network node, and a method for indicating the start time of an unavailable period in a congested communication network.

[0006] According to one embodiment, a method is provided in a wireless communication network to indicate a MM procedure to activate an unavailability period during an enabled Non-Access Stratum (NAS) congestion. The method includes detecting whether a timer T3346 is running or deactivated; and having a user equipment (UE) report an unavailability message and indicate the start time of the unavailability period while the timer T3346 is running or deactivated.

[0007] According to another embodiment, a user equipment (UE) is provided. The UE includes a transceiver and a processor. The transceiver is configured to wirelessly communicate with a network node. The processor is coupled to the transceiver. The processor is configured to perform operations including detecting whether a timer T3346 is running or deactivated; and reporting an unavailability message and indicating the start time of an unavailability period while the timer T3346 is running or deactivated.

[0008] According to another alternative embodiment, a network node is provided. The network node includes a base transceiver unit (BTS) and a base station controller (BSC). The BTS is configured to wirelessly communicate with a user equipment (UE). The BSC is coupled to the BTS. The BSC is configured to perform operations including detecting whether a timer T3346 is running or disabled; and controlling the network node not to reject a registration process request indicating the start time of an unavailable period, even if the timer T3346 is running or a NAS congestion is enabled. Attached Figure Description

[0009] Figure 1 A schematic diagram of a mobile communication system according to an embodiment of the present disclosure is shown.

[0010] Figure 2 A flowchart is shown of a method for instructing a MM process in a wireless communication network to activate an unavailable period during an enabled Non-Access Stratum (NAS) congestion, according to an embodiment of the present disclosure.

[0011] Figure 3 This describes one implementation of a user equipment (UE) according to this disclosure.

[0012] Figure 4 This describes a network node according to one implementation of this disclosure.

[0013] In the following detailed description, numerous specific details are provided for ease of explanation in order to provide a thorough understanding of the disclosed embodiments. However, it will be apparent that one or more embodiments may be practiced without these specific details. In other instances, well-known structures and devices are shown schematically for the purpose of simplifying the illustrations. Detailed Implementation

[0014] The technical terms used in this specification refer to conventional terms in the art. Where there are explanations or definitions for certain terms in this specification, those explanations or definitions shall prevail. Each embodiment of this disclosure has one or more technical features. To the extent possible, those skilled in the art may selectively implement some or all of the technical features in any embodiment, or selectively combine some or all of the technical features in these embodiments.

[0015] Please see Figure 1This illustration shows a schematic diagram of a mobile communication system 1000 according to an embodiment of the present disclosure. The mobile communication system 1000 may be a Long Term Evolution (LTE) system, a 5G new radio (NR) system, a Machine-to-Machine (M2M) system, or a future evolution of a sixth-generation communication system. The mobile communication system 1000 includes user equipment (UE) 100, network nodes 200, and a core network 300. Network nodes 200 and core network 300 may be collectively referred to as network equipment.

[0016] Network node 200 can be configured to perform the conversion between received radio frames and IP packets, and further coordinate attribute management on the air interface. For example, network node 200 can be an evolved Node B (eNB) in LTE, or a base station with a centralized-distributed architecture for 5G systems. Network node 200 can also be an access point (AP), a transport point (TRP), a central unit (CU), or other network entity, and may include some or all of the functions of the aforementioned network entities. Furthermore, network node 200 further includes a relay station. A relay station is a transmission station that receives data and / or other information from an upstream station and sends data and / or other information to a downstream station. A relay station can also be a terminal that provides relay transmission for other terminals. A relay station can also be called a repeater.

[0017] The mobile communication system 1000 may be a heterogeneous system comprising different types of base stations (e.g., macro base stations, cell base stations, femto base stations, and repeaters). These different types of base stations may have different transmit power levels, different coverage areas, and different interference effects. For example, a macro base station may have a higher transmit power level (e.g., 20 watts), while cell base stations, femto base stations, and repeaters may have a lower transmit power level (e.g., 1 watt).

[0018] Network node 200 and user equipment 100 establish a wireless connection through a wireless air interface. This wireless air interface can be based on the LTE standard or on the 5G standard. For example, the wireless air interface could be NR, or it could be a next-generation mobile communication network based on the 5G technology standard.

[0019] User equipment 100 may be a device that provides voice and / or data communication to a user. User equipment 100 may communicate with one or more core networks 300 through a radio access network (RAN) provided by network node 200. User equipment 100 may be a mobile terminal, such as a mobile phone or a computer with a mobile terminal, such as a portable, pocket-sized, handheld, built-in computer, or vehicle-mounted mobile device.

[0020] Specifically, network node 200 can be configured to operate on the network device controller (not in...) Figure 1 Under the control of the network device controller (as shown in the image), it communicates with the user equipment 100 via wireless interface 210. In some embodiments, the network device controller may be part of the core network 300 or may be integrated into the network node 200. The network node 200 may transmit information or user data to the core network 300 via interface 230 (e.g., S1 interface). The network node 200 and the core network 300 may also communicate via interface (e.g., X2 interface, not shown in the image). Figure 1 (As shown in the image) They communicate with each other.

[0021] Before an event that renders a user equipment (UE) unavailable begins, the UE includes an indication and type of unavailability, the start time of the unavailability period (if known), and the duration of the unavailability period (if known), and triggers a mobility registration update or a UE-initiated deregistration process.

[0022] However, when the UE needs to indicate the start time of the "unavailable period" and the backoff timer (e.g., T3346) is running, the behavior of the UE is undefined.

[0023] To address the current problem, this disclosure provides a method for instructing a MM procedure in a wireless communication network to activate an unavailable period during congestion in an enabled Non-Access Stratum (NAS). See also... Figure 2 The diagram illustrates a flowchart of a method for instructing a MM process to activate an unavailable cycle during an enabled Non-Access Stratum (NAS) congestion, according to an embodiment of the present disclosure. The method includes, for example, steps S110 to S160.

[0024] In step S110, it is detected whether timer T3346 is running or has been deactivated. After executing step S110, at least one of steps S120 to S160 is executed. The order of steps S120, S130, S140, S150, and S160 may be changed and is not intended to limit this disclosure.

[0025] In step S120, the user equipment (UE) 100 reports an unavailability message and indicates the start time of the unavailability period, while the timer T3346 is running or has been deactivated.

[0026] In step S130, the user device (UE) 100 is allowed to perform a registration process to indicate the start time of the unavailability period, even though timer T3346 is running. The registration process may be, for example, but is not limited to, an initial registration or a mobility registration update process.

[0027] In step S140, the control network node 200 does not reject a registration process request indicating the start time of the unavailability period, even if timer T3346 is running or non-access stratum (NAS) congestion is enabled. The network node 200 is, for example, an Access and Mobility Management Function (AMF) base station.

[0028] In step S150, the user device (UE) 100 is allowed to indicate the start time of the unavailable period after the timer T3346 expires.

[0029] In step S160, the control user equipment (UE) 100 waits for the start time of the unavailable period to be indicated until timer T3346 expires.

[0030] In one embodiment, if the start timestamp of the unavailability period can be indicated after timer T3346 expires, user equipment (UE) 100 can wait until timer T3346 expires to indicate the start time of the unavailability period. For example, if the start time of the unavailability period is displayed as 2:00 PM, and timer T3346 can expire before 2:00 PM (e.g., 1:30 PM), then user equipment (UE) 100 can perform a registration process to indicate the start time of the unavailability period after timer T3346 expires (e.g., 2:00 PM).

[0031] If the unavailable period start time is displayed as 2:00 p.m., and timer T3346 can expire after 2:00 p.m. (e.g., 2:30 p.m.), then allow user equipment (UE) 100 to perform a registration process (initial registration or mobility registration update process) to indicate the "unavailable period start time", even if timer T3346 is running.

[0032] In an embodiment of non-access stratum (NAS) level mobility management congestion control, the access and mobility management function (AMF, network node 200) can detect 5GMM signaling congestion and perform general NAS level congestion control. Under 5GMM signaling congestion conditions, the access and mobility management function (AMF, network node 200) can reject 5GMM signaling requests from user equipment (UE) 100. The access and mobility management function (AMF, network node 200) should not reject the following requests:

[0033] a) Emergency service request;

[0034] b) Emergency service rollback request;

[0035] c) A request from a user equipment (UE) 100 configured to have high-priority access in a selected public land mobile network (PLMN) or non-public network (SNPN);

[0036] d) Cancellation request message;

[0037] e) A mobile termination service request triggered by a paging or notification process;

[0038] f) Requests for initial registration or mobility and periodic registration updates when an emergency is indicated by a lower level; and

[0039] g) Mobility registration update request when user equipment (UE) 100 reports unavailable information due to coverage interruption.

[0040] If timer T3346 is running or has been disabled, and:

[0041] a) User equipment (UE) 100 is a user equipment configured to have high-priority access in a selected public land mobile network (PLMN) or non-public network (SNPN);

[0042] b) User equipment (UE) 100 requires signaling to initiate emergency service or emergency service rollback; or

[0043] c) User Equipment (UE) 100 needs to report unavailability information due to coverage interruption.

[0044] This allows the user equipment (UE) 100 to initiate the 5GMM process.

[0045] Please see Figure 3The document illustrates a user equipment (UE) 100 according to an embodiment of the present disclosure. The UE 100 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to the behavior of the UE in mobile communications, including the schemes related to the various designs, concepts, schemes, systems, and methods described above, including the network environment and the processes described below.

[0046] User equipment (UE) 100 may be part of an electronic device, which may be a network device, such as a portable or mobile device, wearable device, in-vehicle device or vehicle, wireless communication device, or computing device. For example, UE 100 may 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). The user equipment may also be part of a machine-type device, which may be an Internet of Things (IoT) device, such as a fixed or stationary device, home appliance, roadside unit (RSU), wired communication device, or computing device. For example, UE 100 may 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, UE 100 may be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G network, NR network, or IoT network.

[0047] In some implementations, User Equipment (UE) 100 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 all the above-described embodiments, User Equipment (UE) 100 may be implemented as a network device. User Equipment (UE) 100 may include... Figure 3 The components shown include at least some of the components, such as processor 110, transceiver 120, and memory 130. User equipment (UE) 100 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the scheme of this disclosure.

[0048] In one aspect, processor 110 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more Complex Instruction Set Computing (CISC) or Reduced Instruction Set Computing (RISC) processors. That is, although the singular term "processor" is used herein to refer to processor 110, processor 110 may include multiple processors in some implementations and a single processor in others, according to the present disclosure. In another aspect, processor 110 may be implemented in hardware (and optionally firmware) having electronic components including, 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 transformers, configured and arranged to achieve a specific purpose according to the present disclosure. In other words, in at least some implementations, the processor is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to service request behavior of user equipment (UE) 100 in mobile communications regarding registration failures and emergency service rollbacks, according to various implementations of the present disclosure.

[0049] Transceiver 120 is coupled to processor 110. Transceiver 120 can wirelessly transmit and receive data. In some implementations, transceiver 120 can wirelessly communicate with different types of wireless networks that have different Radio Access Technologies (RATs). In some implementations, transceiver 120 can be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 120 can be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication.

[0050] Memory 130 is coupled to processor 110 and stores data. Memory 130 may include a random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitance RAM (Z-RAM). Alternatively, memory 130 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, memory 130 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.

[0051] The processor 110 of the user equipment (UE) 100 is configured to perform the above operations (e.g., steps S110, S120, S130, S150, S160).

[0052] Please see Figure 4 The document illustrates a network node 200 according to an implementation of this disclosure. The network node 200 can perform various functions to implement schemes, techniques, processes, and methods related to the behavior of network nodes in mobile communications, including the various schemes mentioned above related to various proposed designs, concepts, schemes, systems, and methods, as well as the processes described below.

[0053] Network node 200 may include Figure 4 The network node 200 may include at least some of the components shown, such as the base station controller (BSC) 210, the base transceiver (BTS) 220, and the memory 230. The network node 200 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed scheme of this disclosure.

[0054] In one aspect, the BSC 210 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more Complex Instruction Set Computing (CISC) or Reduced Instruction Set Computing (RISC) processors. That is, although the singular term "processor" is used herein to refer to the BSC 210, according to this disclosure, the BSC 210 may include multiple processors in some implementations and a single processor in others. In another aspect, the BSC 210 may be implemented in hardware (and optionally firmware) having electronic components including, 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 transformers, configured and arranged to achieve a specific purpose according to this disclosure. In other words, in at least some implementations, the processor is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to the service request behavior of the network node 200 in mobile communications regarding registration failures and emergency service rollbacks, according to various implementations of this disclosure.

[0055] The BTS 220 is coupled to the BSC 210. The BTS 220 can wirelessly transmit and receive data. In some implementations, the BTS 220 can communicate wirelessly with different types of wireless networks that have different Radio Access Technologies (RATs). In some implementations, the BTS 220 can be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, the BTS 220 can be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication.

[0056] Memory 230 is coupled to Base Station Controller (BSC) 210 and stores data therein. Memory 230 may include a random access memory (RAM), such as Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Thyristor Random Access Memory (T-RAM), and / or Zero-Capacitor Random Access Memory (Z-RAM). Alternatively, memory 230 may include a read-only memory (ROM), such as Mask ROM, Programmable ROM (PROM), Erasable Programmable ROM (EPROM), and / or Electrically Erasable Programmable ROM (EEPROM). Alternatively, memory 230 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.

[0057] The base station controller (BSC) 210 of network node 200 is configured to perform the above operations (e.g., steps S110, S140).

[0058] Based on the above embodiments, User Equipment (UE) 100 should perform a deregistration procedure to indicate the "start time of the unavailable period"; and / or allow User Equipment (UE) 100 to perform a registration procedure (initial registration or mobility registration update procedure) to indicate the "start time of the unavailable period," even if timer T3346 is running; and Network Node 200 (Access and Mobility Management Function (AMF)) must not refuse a registration procedure request indicating the "start time of the unavailable period," even if timer T3346 is running or Non-Access Stratum (NAS) congestion is enabled. This method is used to instruct the MM procedure to activate the unavailable period during non-access stratum (NAS) congestion enabled in the wireless communication network to address the current problem.

[0059] The foregoing disclosure provides various features for implementing some embodiments or examples of this disclosure. To simplify and illustrate some embodiments of this disclosure, specific components and configurations (e.g., mentioned values ​​or names) have been described above. Furthermore, some embodiments of this disclosure may reuse reference symbols and / or letters in different instances. Such repetition is for simplicity and clarity and does not inherently represent a relationship between the various embodiments and / or configurations discussed.

[0060] Various modifications and variations of the disclosed embodiments will be apparent to those skilled in the art. The specifications and examples are for illustrative purposes only, and the true scope of this disclosure is indicated by the following claims and their equivalents.

Claims

1. A method of indicating a MM procedure to activate an unavailability period during an enabled non-access stratum (NAS) congestion in a wireless communication network, comprising: detecting that a timer T3346 is running or has been deactivated; and reporting, by a user equipment (UE), an unavailability information and indicating a start time of the unavailability period while the timer T3346 is running or has been deactivated.

2. The method of claim 1, further comprising: allowing the user equipment (UE) to perform a registration procedure to indicate the start time of the unavailability period even if the timer T3346 is running.

3. The method of claim 2, wherein the registration procedure is an initial registration or a mobility registration update procedure.

4. The method of claim 1, further comprising: controlling a network node to not reject a registration procedure request indicating the start time of the unavailability period even if the timer T3346 is running or a NAS congestion is in an enabled state.

5. The method of claim 4, wherein the registration procedure is an initial registration or a mobility registration update procedure.

6. The method of claim 4, wherein the network node is an access and mobility management function (AMF) base station.

7. The method of claim 1, further comprising: allowing the user equipment (UE) to indicate the start time of the unavailability period after the timer T3346 expires.

8. The method of claim 1, further comprising: controlling the user equipment (UE) to wait to indicate the start time of the unavailability period until the timer T3346 expires.

9. A user equipment (UE), comprising: a transceiver configured to wirelessly communicate with a network node; and a processor coupled to the transceiver and configured to perform operations comprising: detecting that a timer T3346 is running or has been deactivated; reporting an unavailability information and indicating a start time of an unavailability period while the timer T3346 is running or has been deactivated.

10. The user equipment (UE) of claim 9, wherein the operations further comprise: allowing the user equipment (UE) to perform a registration procedure to indicate the start time of the unavailability period even if the timer T3346 is running.

11. The user equipment (UE) of claim 10, wherein the registration procedure is an initial registration or a mobility registration update procedure.

12. The user equipment (UE) of claim 9, wherein the operations further comprise: allowing the user equipment (UE) to indicate the start time of the unavailability period after the timer T3346 expires.

13. The user equipment (UE) of claim 9, wherein the operations further comprise: controlling the user equipment (UE) to wait to indicate the start time of the unavailability period until the timer T3346 expires.

14. A network node, comprising: A base transceiver station (BTS) configured to wirelessly communicate with a user equipment (UE); and a base station controller (BSC) coupled to the BTS and configured to perform operations comprising: detecting that a timer T3346 is running or has been deactivated; and ​ controlling the network node to not reject a registration procedure request indicating a start time of an unavailable period even if the timer T3346 is running or a NAS congestion is in an enabled state.

15. The network node of claim 14, wherein the registration procedure is an initial registration or a mobility registration update procedure.

16. The network node of claim 15, wherein the network node is an access and mobility management function (AMF) base station.

Images