Seamless user equipment (UE) context recovery
By coordinating the unavailability period and backoff timer of the UE in the wireless communication system, the network disposal and context recovery problems of the UE during the unavailability period are solved, and the efficiency of seamless recovery and resource management is achieved.
Patent Information
- Application Number
- CN202280094264.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-29
- Publication Date
- 2024-11-12
AI Technical Summary
In wireless communication systems, user equipment (UE) has challenges with seamless context recovery with 3GPP networks during unavailability periods, especially when UE fails to know the unavailability periods in advance, which may affect the execution of critical operations and networking. Disposal.
By determining and coordinating unavailability periods between UE and 3GPP networks, using non-access layer message exchange and backoff timer mechanisms, ensure that the UE performs unavailability period operations with network support and seamlessly recovers after the period ends Context.
Moderate network disposal and context recovery during UE unavailability periods are realized, ensuring the smooth completion of critical operations and effective management of network resources, and reducing the risk of signal storms and congestion caused by simultaneous updates of multiple UEs.
Smart Images

Figure CN118947175A_ABST
Abstract
Description
Technical Field
[0001] The present application relates generally to wireless communication systems, including systems, methods, and apparatus for assigning wireless communication devices (eg, user equipment (UE)) to paging subgroups. Background Art
[0002] Wireless mobile communication technologies use various standards and protocols to send data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs) (commonly referred to within industry organizations as WLANs). ).
[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between base stations of the RAN (which may also sometimes be referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices referred to as user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).
[0004] Each RAN may use one or more radio access technologies (RATs) for communication between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.
[0005] The base stations used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (also sometimes referred to as a gNodeB or gNB).
[0006] The RAN provides its communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core (EPC) while NG-RAN may utilize the 5G Core Network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS
[0007] To easily identify the discussion of any particular element or action, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.
[0008] Figure 1 An example flow diagram for seamless UE context recovery following a period of unavailability of the UE is illustrated.
[0009] Figures 2 to 4 Illustrated Figure 1 The illustrated flow chart is directed to a first set of example implementations for a UE deregistering from a 3GPP network during a period of unavailability.
[0010] Figures 5 to 7 Illustrated Figure 1 The flowchart shown is for a second set of example implementations of a UE that does not deregister from the 3GPP network during a period of unavailability.
[0011] Figure 8 An example flow chart for seamless UE context recovery when the 3GPP network initiates deregistration of the UE is illustrated.
[0012] Fig.9A and Fig. 9B An example flow chart of seamless UE context recovery for multiple UEs is illustrated.
[0013] Fig.10 An example method of wireless communications by a UE is shown that may be used to preserve context of the UE during periods of unavailability of the UE.
[0014] Fig.11 An example method of communicating by a network server that may be used to preserve a context of a UE during a period of unavailability of the UE is shown.
[0015] Fig.12 Another example method of wireless communications by a UE is shown that may be used to preserve context of the UE during periods of unavailability of the UE.
[0016] Fig.13 An example architecture of a wireless communication system according to embodiments disclosed herein is illustrated.
[0017] Fig.14A system for performing signaling between a wireless device and one or more network devices according to embodiments disclosed herein is illustrated. DETAILED DESCRIPTION
[0018] Various embodiments are described with reference to UE. However, reference to UE is provided for illustrative purposes only. The example embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for information and data interaction with the network. Therefore, the UE described herein is used to represent any suitable electronic device.
[0019] Sometimes, the UE may need to perform operations that make the UE unavailable to some or all aspects of the 3GPP network (e.g., unavailable to the CN or Application Function (AF)). Operations that may make the UE unavailable to some or all aspects of the 3GPP network include applications such as security patches, software upgrades, silent resets, and device restarts. The UE may sometimes perform these operations in response to user input, but the initiation of some or all of these operations is typically left to the UE implementation.
[0020] The duration of the UE's unavailability period (i.e., the time that the UE is unavailable to some or all aspects of the 3GPP network) may range from several seconds to several minutes. When the UE becomes unavailable without a priori knowledge of the CN or AF, the unavailability may impact critical operations that may need to be performed on or by an application server. For example, the CN or AF may require input from an Internet of Things (IoT) device, or ultra-reliable low-latency communication (URLLC) between the AF and a device (e.g., industrial, factory, or medical equipment) that may require an immediate response from the device. Therefore, it would be useful for the UE and the CN or AF to coordinate the timing of the UE's unavailability period so that critical operations can be handled appropriately and / or so that the network can gracefully handle the UE's unavailability.
[0021] In some cases, the CN or AF may be aware of events that will require a period of unavailability of the UE. For example, the UE may download a software update that the CN or AF knows the UE needs to install. However, even in these cases, the timing of the installation may be left to the UE implementation, and the UE may delay installation for various reasons, such as low storage capacity or low battery power.
[0022] The present disclosure describes systems, methods, apparatus, and devices that enable a network (e.g., a 5G system (5GS)) to determine the timing of a UE's unavailability period.
[0023] Figure 1 An example flow diagram 100 for seamless UE context recovery following a period of unavailability of the UE is illustrated. Figure 1The message shown may be sent between the UE 102 and the 3GPP network 104. In some cases, the message may be a non-access stratum (NAS) message sent between the UE 102 and a network server 106 (e.g., a network server hosting an access and mobility management function (AMF) of the CN) via a base station 108 (e.g., an eNB or gNB). The operations performed by the UE 102 may be performed by a processor of the UE 102, and the transmission and reception of the UE 102 may be performed via a transceiver of the UE 102. The operations performed by the 3GPP network 104 may be performed by a processor of the network server 106, and the transmission and reception of the network server 106 may be performed via a communication interface of the network server 106.
[0024] At 110, UE 102 may optionally send capability information to 3GPP network 104 (eg, to network server 106). The capability information may include information regarding the UE's capabilities for determining (eg, scheduling) periods of unavailability of UE 102.
[0025] At 112, the 3GPP network 104 (e.g., the network server 106) may optionally send support (or non-support) information to the UE 102. The support information may indicate whether the 3GPP network 104 supports the UE's capability for determining periods of unavailability of the UE 102. If the 3GPP network 104 supports the UE's capability for determining periods of unavailability, the 3GPP network 104 may be able to retain the context of the UE 102 during the period when the UE 102 is unavailable to the 3GPP network 104. If the 3GPP network 104 does not support the UE's capability for determining periods of unavailability, the 3GPP network 104 may not be able to retain the context of the UE 102 during the period when the UE 102 is unavailable to the 3GPP network 104.
[0026] At 114, UE 102 may determine to perform an operation during the period of unavailability of UE 102. The operation may include, for example, one or more of: a silent reset of the modem, a security patch update, an OS upgrade, a modem software update, a device restart when modem settings are changed (e.g., via OMA-DM), another type of firmware, software or binary update, etc.
[0027] At 116, UE 102 may send a first message to 3GPP network 104 (e.g., to network server 106) requesting acceptance of the unavailability period in response to determining to perform the operation at 114. The first message may include an estimated duration of the unavailability period (e.g., the duration in seconds or some other time unit). When capability information is exchanged at 110 and 112, the first message may be sent only if 3GPP network 104 indicates that it supports the UE's capability for determining the unavailability period.
[0028] At 118, the 3GPP network 104 (e.g., the network server 106) may send a second message indicating acceptance of the unavailability period or rejection of the unavailability period to the UE 102 in response to receiving the first message at 116. When the 3GPP network 104 accepts the unavailability period, the UE 102 may continue its preparation for the unavailability period and start the unavailability period. Alternatively, the second message may reference a backoff timer, in which case the UE 102 may not start the unavailability period until the backoff timer has been applied. The length of the backoff timer may be included in the second message in some cases. In other cases, the second message may indicate that a backoff timer with a predetermined duration should be applied. While the backoff timer is running, the UE 102 may function normally and may communicate with the 3GPP network 104.
[0029] At 120, and in response to receiving the acceptance of the unavailability period at 116, the UE 102 may start the unavailability period and perform the operations that the UE previously determined to perform at 114. However, if the acceptance of the unavailability period referenced a backoff timer, the UE may first apply the backoff timer and then start the unavailability period and perform the operations. If the UE 102 instead receives a rejection of the unavailability period at 118, the UE 102 may not start the unavailability period and may send a new request for acceptance of the unavailability period at a later time. In some cases, the rejection of the unavailability period sent at 118 may reference a backoff timer indicating how long the UE 102 must wait before sending a new request for acceptance of the unavailability period.
[0030] At 122, and concurrently with the operations performed at 120, the 3GPP network 104 (e.g., network server 106) may apply a back-off timer and / or apply a timer within the estimated duration of the unavailability period (i.e., assuming that the 3GPP network 104 sends an acceptance of the unavailability period to the UE 102). While applying one or both of these timers, the 3GPP network 104 may preserve the context of the UE 102. For example, the 3GPP network 104 (e.g., network server 106) may buffer or save incoming requests (e.g., pages) for the UE 202, etc. After application of one or both of the timers (or within application of one or both of the timers), the 3GPP network 104 may anticipate that the UE 102 sends (and may monitor at 124) a message (e.g., a registration request message or a service request message) indicating that the UE 102 has concluded the operations that the UE intended to perform during the unavailability period. If such a message is received by the 3GPP network 104 (e.g., by the network server 106) within the unavailability period or within a predetermined time period after the unavailability period, the UE 102 may seamlessly restore the UE's context with the 3GPP network 104. If such a message is not received by the 3GPP network 104 within the unavailability period or within a predetermined time period after the unavailability period, the 3GPP network 104 may discard the UE's context.
[0031] Other signaling or operations may also be performed at or after 124. When a backoff timer (if any) is applied at 120, other signaling or operations may also be performed.
[0032] Figures 2 to 4 Illustrated Figure 1 The illustrated flow diagrams are directed to a first set of example implementations for a UE 202 deregistering from a 3GPP network 204 during a period of unavailability. Figures 2 to 4 The message shown may be sent as a NAS message in some cases, and may be sent between the UE 202 and the network server 206 (e.g., the network server hosting the AMF of the CN) of the 3GPP network 204. The message may be sent between the UE 202 and the network server 206 via the base station 208 (e.g., eNB or gNB). The operations performed by the UE 202 may be performed by a processor of the UE 202, and the transmission and reception of the UE 202 may be performed via a transceiver of the UE 202. The operations performed by the 3GPP network 204 may be performed by a processor of the network server 206, and the transmission and reception of the network server 206 may be performed via a communication interface of the network server 206.
[0033] Figure 2An example flow diagram 200 is illustrated for a UE 202 deregistering from a 3GPP network 204 after a period of unavailability of the UE is accepted by the 3GPP network 204 .
[0034] At 210, UE 202 may optionally send capability information to 3GPP network 204 (e.g., to network server 206). The capability information may be sent in a 5G Mobility Management (5GMM) Capability Information Element (IE) of a Registration Request message. The capability information may include an indication of a capability for determining a period of unavailability of UE 202.
[0035] At 212, the 3GPP network 204 (e.g., the network server 206) may optionally send support (or non-support) information to the UE 202. The support information may be sent in a 5GS Network Feature Support IE of the Registration Accept message. The support information may include an indication of support for a capability for determining a period of unavailability of the UE 202. If the 3GPP network 204 supports the UE's capability for determining a period of unavailability, the 3GPP network 204 may be able to retain the context of the UE 202 during the period in which the UE 202 is unavailable to the 3GPP network 204. If the 3GPP network 204 does not support the UE's capability for determining a period of unavailability, the 3GPP network 204 may not be able to retain the context of the UE 202 during the period in which the UE 202 is unavailable to the 3GPP network 204.
[0036] At 214, UE 202 may determine to perform an operation during the period of unavailability of UE 202. The operation may include, for example, referring to Figure 1 Any of the operations described.
[0037] At 216, UE 202 may send a first message to 3GPP network 204 (e.g., to network server 206) requesting acceptance of the unavailability period in response to determining to perform the operation at 214. The first message may be a registration request message, such as a registration request message for mobility and periodic registration updates. The first message may include an estimated duration of the unavailability period (e.g., a duration in seconds or some other time unit). The estimated duration of the unavailability period may be sent in the unavailable time IE of the registration request message. When capability information is exchanged at 210 and 212, the first message may be sent only if 3GPP network 204 indicates that it supports the UE's capability for determining the unavailability period.
[0038] At 218, the 3GPP network 204 (e.g., the network server 206) may send a second message indicating acceptance of the unavailability period to the UE 202 in response to receiving the first message at 214. The second message may be a registration accept message and may include a 5GS attach request result IE indicating acceptance of the unavailability period (e.g., an "unavailable time accepted" indication).
[0039] At 220 , and in response to receiving the registration accept message, UE 202 may send a registration complete message to 3GPP network 204 (eg, to network server 206 ).
[0040] At 222, and in response to the unavailability period being accepted, UE 202 may deregister from 3GPP network 204. The deregistration may be initiated by sending a deregistration request message to 3GPP network 204 (e.g., to network server 206). In some embodiments, the deregistration request message may include a reason or type for the deregistration. For example, UE 202 may indicate that the reason for the deregistration is "software update" (i.e., type: software update). At 224, 3GPP network 204 may confirm the deregistration request message by sending a deregistration accept message.
[0041] After receiving the deregistration accept message, UE 202 may start an unavailability period at 226 and perform the operations that the UE previously determined to perform at 214 .
[0042] At 228, and concurrently with the operations performed at 226, the 3GPP network 204 (e.g., the network server 206) may apply a timer for the estimated duration of the unavailability period. While applying the timer, the 3GPP network 204 may preserve the context of the UE 202 (e.g., stop sending data to the UE 502, discard pending data, maintain paging, etc.). After (or within) the application of the timer, the 3GPP network 204 may anticipate that the UE 202 sends (and may monitor at 230) a registration request message indicating that the UE 202 has ended the operations that the UE intended to perform during the unavailability period. If such a message is received by the 3GPP network 204 (e.g., by the network server 206) during the unavailability period or within a predetermined time period after the unavailability period, the UE 202 may seamlessly resume the context of the UE with the 3GPP network 204. If such a message is not received by the 3GPP network 204 within the unavailability period or within a predetermined time period after the unavailability period, the 3GPP network 204 may discard the context of the UE.
[0043] Other signaling or operations may also be performed after 230. The other signaling may include, for example, a registration accept message sent by the 3GPP network 204 in response to the registration request message sent at 230.
[0044] although Figure 2 Flowchart 200 is illustrated in which the UE's unavailability period is accepted by the 3GPP network 204, but the UE's unavailability period may alternatively be rejected by the 3GPP network 204. In this alternative scenario, and at 218, the 3GPP network 204 (e.g., the network server 206) may send a second message indicating the rejection of the unavailability period to the UE 202 in response to receiving the first message at 216. The second message may be a registration acceptance message and may include a 5GS additional request result IE indicating the rejection of the unavailability period (e.g., an "unavailable time rejected" indication). In this scenario, the UE 202 may send a third message (i.e., a repeated request) to the 3GPP network 204 (e.g., to the network server 206) requesting acceptance of the unavailability period. Then, the 3GPP network 204 may send a fourth message indicating whether the unavailability period is accepted or rejected. In some cases, the second message (ie, the message including the rejection of the unavailability period) may reference a backoff timer indicating how long the UE 202 must wait before again requesting acceptance of the unavailability period.
[0045] Figure 3 An example flow diagram 300 is illustrated for a UE 202 deregistering from a 3GPP network 204 after a period of unavailability of the UE is accepted by the 3GPP network 204 and after the UE 202 applies a back-off timer.
[0046] The operations at 210 to 220 may be similar to those of reference Figure 2 However, at 218, the 3GPP network 204 may send a second message including acceptance of the unavailability period and also referencing a backoff timer. The length of the backoff timer may be included in the second message in some cases. In other cases, the second message may indicate that a backoff timer with a predetermined duration should be applied.
[0047] At 302 and 304, and in response to the unavailability period being accepted, the UE 202 and the 3GPP network 204 (e.g., the network server 206) may start a back-off timer. While the back-off timer is running, and at 306, the UE 202 may optionally participate in other signaling or operations (e.g., downloads, paging, configuration updates, etc.) with the 3GPP network 204, either initiated by the UE 202 or in response to messages received from the 3GPP network 204 (e.g., from the base station 208 or the network server 206).
[0048] At 308 and 310, UE 202 and 3GPP network 204 may end the back-off timer. Subsequently, and at 222, UE 202 may deregister from 3GPP network 204. The deregistration may be initiated by sending a deregistration request message to 3GPP network 204 (e.g., to network server 206). UE 202 and 3GPP network 204 may then continue operations 224, 226, 228, and 230, as described with reference to FIG. Figure 2 Descriptive.
[0049] Figure 4 An example flow diagram 400 is illustrated for a UE 202 deregistering from a 3GPP network 204 after a period of unavailability of the UE is accepted by the 3GPP network 204 and while the UE 202 is applying a back-off timer.
[0050] The operations at 210 to 220 may be similar to those of reference Figure 2 However, at 218, the 3GPP network 204 may send a second message including acceptance of the unavailability period and also referencing a backoff timer. The length of the backoff timer may be included in the second message in some cases. In other cases, the second message may indicate that a backoff timer with a predetermined duration should be applied.
[0051] At 402 and 404, and in response to the unavailability period being accepted, the UE 202 and the 3GPP network 204 (e.g., the network server 206) may start a back-off timer. While the back-off timer is running, the UE 202 may optionally participate in other signaling or operations (e.g., downloads, paging, configuration updates, etc.) with the 3GPP network 204, either initiated by the UE 202 or in response to messages received from the 3GPP network 204 (e.g., from the base station 208 or the network server 206).
[0052] At 406, and in the process of engaging in other signaling or operations with the 3GPP network 204 while the back-off timer is applied (e.g., in response to paging), the UE 202 may send a third message (e.g., a service request message) to the 3GPP network 204 (e.g., to the network server 206). If the conditions of the 3GPP network 204 have changed since the registration accept message was sent 218, and it is now able to accept the UE 202 to start the unavailability period of the UE, the 3GPP network 204 (e.g., the network server 206) may include acceptance of the unavailability period in a response to the third message sent at 408 (e.g., in a fourth message such as a service accept message). In some cases, the fourth message may be a registration accept message including a 5GS attach request result IE, which may indicate acceptance of the unavailability period (e.g., an "unavailable time accepted" indication).
[0053] At 222, UE 202 may deregister from 3GPP network 204 without terminating the backoff timer. The deregistration may be initiated by sending a deregistration request message to 3GPP network 204 (e.g., to network server 206). UE 202 and 3GPP network 204 may then continue operations 224, 226, 228, and 230 as described with reference to Figure 2 Alternatively, the operations at 406 and / or 222 may be replaced by a network-initiated sending of a deregistration request message, wherein the 3GPP network 204 requests the UE 202 to deregister and begin an unavailability period.
[0054] Figures 5 to 7 Illustrated Figure 1 The flowchart shown is directed to a second set of example implementations for a UE 502 that does not deregister from a 3GPP network 504 during a period of unavailability. Figures 5 to 7 The message shown may be sent as a NAS message in some cases, and may be sent between the UE 502 and a network server 506 (e.g., a network server hosting an AMF of the CN) of the 3GPP network 504. The message may be sent between the UE 502 and the network server 506 via a base station 508 (e.g., an eNB or a gNB). The operations performed by the UE 502 may be performed by a processor of the UE 502, and the transmission and reception of the UE 502 may be performed via a transceiver of the UE 502. The operations performed by the 3GPP network 504 may be performed by a processor of the network server 506, and the transmission and reception of the network server 506 may be performed via a communication interface of the network server 506.
[0055] refer to Figures 5 to 7 The described embodiments reuse the Multi-Universal Subscriber Identity Module (MUSIM) features to indicate the unavailability period of the UE to the 3GPP network. The reused MUSIM features may include, for example, the connection release feature described in 3GPP Technical Specification (TS) 23.501 clause 5.38.2 and / or the paging restriction described in 3GPP TS 23.501 clause 5.38.5. Reference Figures 5 to 7 The described embodiments may also introduce a new feature, the expected remaining duration feature, which may be used to indicate the estimated duration of the unavailability period. The expected remaining duration feature may only be used in combination with the connection release feature.
[0056] Figure 5An example flow chart 500 is illustrated. At 510, the UE 502 may optionally send capability information to the 3GPP network 504 (e.g., to the network server 506). For a particular Universal Subscriber Identity Module (USIM) of the UE 502 and for a particular Public Land Mobile Network (PLMN), the capability information may be sent in a 5GMM Core Network Capability IE of the Registration Request message. The capability information may include an indication of support for MUSIM connection release, MUSIM paging restriction, and expected remaining duration.
[0057] At 512, the 3GPP network 504 (e.g., the network server 506) may optionally send support (or non-support) information to the UE 502. The support information may be sent in a 5GS network feature support IE of the registration accept message. The support information may include an indication of support for MUSIM connection release, MUSIM paging restriction, and expected remaining duration (i.e., an estimated duration of the unavailability period), and may be based on network capabilities and network preferences (e.g., based on local area network policies). An indication of support for paging restriction may be provided only if connection release is supported. Similarly, an indication of support for expected remaining duration may be provided only if connection release is supported. If the 3GPP network 504 supports at least MUSIM connection release and expected remaining duration (and preferably supports MUSIM paging restriction), the 3GPP network 504 may be able to retain the context of the UE 502 during the period when the UE 502 is unavailable to the 3GPP network 504. If the 3GPP network 504 does not support MUSIM connection release or expected remaining duration, the 3GPP network 504 may not be able to retain the context of the UE 502 during the period when the UE 502 is unavailable to the 3GPP network 504.
[0058] At 514, UE 502 may determine to perform an operation during the period of unavailability of UE 502. The operation may include, for example, referring to Figure 1 Any of the operations described.
[0059] At 516, the UE 502 may send a first message including a release request indication, a paging restriction indication (indicating that all paging is restricted), and an expected remaining duration to the 3GPP network 504 (e.g., to the network server 506) in response to determining to perform the operation at 514. The first message may be a registration request message (such as a registration request message for mobility and periodic registration updates) or a service request message. The expected remaining duration may indicate an estimated duration of the unavailability period (e.g., a duration in seconds or some other time unit). When capability information is exchanged at 510 and 512, the first message may be sent only if the 3GPP network 504 indicates that it supports at least MUSIM connection requests and the expected remaining duration.
[0060] At 518, the 3GPP network 504 (e.g., the network server 506) may send a second message indicating acceptance of the unavailability period to the UE 502 in response to receiving the first message at 514. The second message may be a registration accept message or a service accept message including a release request indication, paging restriction information, and an acceptance value of the expected remaining duration.
[0061] At 520 , and in response to receiving the registration accept message or the service accept message, the UE 502 may begin an unavailability period and perform the operations that the UE previously determined to perform at 514 .
[0062] At 522, and concurrently with the operations performed at 520, the 3GPP network 504 (e.g., the network server 506) may apply a timer for the expected remaining duration. While applying the timer, the 3GPP network 504 may preserve the context of the UE 502 (e.g., stop sending data to the UE 502, discard pending data, maintain paging, etc.). After (or within) the application of the timer, the 3GPP network 504 may expect the UE 502 to send (and may monitor at 524) a registration request message or a service request message indicating that the UE 502 has ended the operations that the UE intended to perform during the unavailability period. If such a message is received by the 3GPP network 504 (e.g., by the network server 506) during the unavailability period or within a predetermined time period after the unavailability period, the UE 502 may seamlessly restore the context of the UE with the 3GPP network 504. If such a message is not received by the 3GPP network 504 within the unavailability period or within a predetermined time period after the unavailability period, the 3GPP network 504 may discard the context of the UE. Alternatively, the 3GPP network 504 may automatically attempt to resume communication with the UE 502 after the unavailability period, regardless of whether the UE 502 sent a message during or after the unavailability period (e.g., NAS signaling may be automatically resumed).
[0063] Other signaling or operations may also be performed after 524. Other signaling may include, for example, a registration accept message or a service accept message sent in response to the registration request message or the service request message sent at 524.
[0064] although Figure 5Flowchart 500 is illustrated in which the UE's unavailability period is accepted by the 3GPP network 504, but the UE's unavailability period may alternatively be rejected by the 3GPP network 504. In this alternative scenario, and at 518, the 3GPP network 504 (e.g., the network server 506) may send a second message indicating the rejection of the unavailability period to the UE 502 in response to receiving the first message at 516. The second message may be a registration acceptance message or a service acceptance message indicating the rejection of the unavailability period. In this scenario, the UE 502 may send a third message (i.e., a repeated request) requesting acceptance of the unavailability period to the 3GPP network 504 (e.g., to the network server 506). The 3GPP network 504 may then send a fourth message indicating whether the unavailability period is accepted or rejected. In some cases, the second message (i.e., the message including the rejection of the unavailability period) may reference a backoff timer indicating how long the UE 502 must wait before requesting acceptance of the unavailability period again.
[0065] Figure 6 An example flow diagram 600 is illustrated for a UE 502 receiving acceptance of a period of unavailability of the UE but also receiving a back-off timer.
[0066] The operations at 510 to 518 may be similar to those of reference Figure 5 However, at 518, the 3GPP network 504 may send a second message including acceptance of the unavailability period and also referencing a backoff timer. The length of the backoff timer may be included in the second message in some cases. In other cases, the second message may indicate that a backoff timer with a predetermined duration should be applied.
[0067] At 602 and 604, and in response to the unavailability period being accepted, the UE 502 and the 3GPP network 504 (e.g., the network server 506) may start a back-off timer. While the back-off timer is running, and at 606, the UE 502 may optionally participate in other signaling or operations (e.g., downloads, paging, configuration updates, etc.) with the 3GPP network 504, either initiated by the UE 502 or in response to messages received from the 3GPP network 504 (e.g., from the base station 508 or the network server 506).
[0068] At 608 and 610, the UE 502 and the 3GPP network 504 may end the back-off timer. Subsequently, and at 612, the UE 502 may begin an unavailability period and perform the operations that the UE previously determined to perform at 514. At the same time, and at 614, the 3GPP network 504 (e.g., the network server 506) may apply the timer for the expected remaining duration. The UE 502 and the 3GPP network 504 may then continue operations 524 and 526, as described with reference to Figure 5 Descriptive.
[0069] Figure 7 Another example flow diagram 700 is illustrated for a UE 502 that receives acceptance of a period of unavailability of the UE but also receives a back-off timer.
[0070] The operations at 510 to 518 may be similar to those of reference Figure 5 However, at 518, the 3GPP network 504 may send a second message including acceptance of the unavailability period and also referencing a backoff timer. The length of the backoff timer may be included in the second message in some cases. In other cases, the second message may indicate that a backoff timer with a predetermined duration should be applied.
[0071] At 702 and 704, and in response to the unavailability period being accepted, the UE 502 and the 3GPP network 504 (e.g., the network server 506) may start a back-off timer. While the back-off timer is running, the UE 502 may optionally participate in other signaling or operations (e.g., downloads, paging, configuration updates, etc.) with the 3GPP network 504, either initiated by the UE 502 or in response to messages received from the 3GPP network 504 (e.g., from the base station 508 or the network server 506).
[0072] At 706, and in the process of engaging in other signaling or operations with the 3GPP network 504 while the back-off timer is applied (e.g., in response to paging), the UE 502 may send a third message (e.g., a service request message) to the 3GPP network 504 (e.g., to the network server 506). If the conditions of the 3GPP network 504 have changed since the registration accept message was sent 518, and it is now acceptable for the UE 502 to start the unavailability period of the UE, the 3GPP network 504 (e.g., the network server 506) may include acceptance of the unavailability period in a response to the third message sent at 708 (e.g., in a fourth message such as a service accept message). The fourth message may include, for example, a release request indication, a paging restriction indication (indicating that all paging is restricted), and an expected remaining duration.
[0073] At 710, and without ending the backoff timer, the UE 502 may begin an unavailability period and perform the operations that the UE previously determined to perform at 514. At the same time, and at 712, the 3GPP network 504 (e.g., the network server 506) may apply the timer for the expected remaining duration. The UE 502 and the 3GPP network 504 may then continue operations 524 and 526, as described with reference to Figure 5 Descriptive.
[0074] Figure 8 An example flow diagram 800 for seamless UE context recovery when a 3GPP network 804 initiates deregistration of a UE 802 is illustrated. Figure 8 The message shown may be sent as a NAS message in some cases, and may be sent between the UE 802 and a network server 806 (e.g., a network server hosting an AMF of the CN) of the 3GPP network 804. The message may be sent between the UE 802 and the network server 806 via a base station 808 (e.g., an eNB or a gNB). The operations performed by the UE 802 may be performed by a processor of the UE 802, and the transmission and reception of the UE 802 may be performed via a transceiver of the UE 802. The operations performed by the 3GPP network 804 may be performed by a processor of the network server 806, and the transmission and reception of the network server 806 may be performed via a communication interface of the network server 806.
[0075] The operations at 210 and 212 may be similar to those of reference Figure 2 Describe the operations.
[0076] At 810, UE 802 may download at least one of a firmware update or a software update. The update may be downloaded from 3GPP network 804 or over another wireless or wired network. 3GPP network 804 may coordinate the download, be aware of the download, or may be informed of the download.
[0077] At 812, the 3GPP network 804 (e.g., network server 806) may send a deregistration request message to the UE 802. The deregistration request message may indicate that the UE 802 is to deregister from the 3GPP network 804 and install a firmware update or software update during the period of unavailability of the UE 802. In some cases, the deregistration request message may include an indication that reregistration is required. In some cases, the deregistration request message may indicate a reason for the deregistration (e.g., to perform a firmware or software update).
[0078] At 814, UE 802 may begin the unavailability period and install the update.
[0079] At 816, and concurrently with the operations performed at 814, the 3GPP network 804 (e.g., the network server 806) may apply a timer for the estimated duration of the unavailability period. While applying the timer, the 3GPP network 804 may retain the context of the UE 802 (e.g., stop sending data to the UE 802, discard pending data, maintain paging, etc.). After (or within) the application of the timer, the 3GPP network 804 may expect the UE 802 to send (and may monitor at 818) a registration request message indicating that the UE 802 has finished installing the update. If such a message is received by the 3GPP network 804 (e.g., by the network server 806) within the unavailability period or within a predetermined time period after the unavailability period, the UE 802 may seamlessly restore the context of the UE with the 3GPP network 804. If such a message is not received by the 3GPP network 804 within the unavailability period or within a predetermined time period after the unavailability period, the 3GPP network 804 may discard the context of the UE.
[0080] Fig.9A and Fig. 9B An example flow diagram 900 is illustrated for seamless UE context recovery for multiple UEs. Fig.9A and Fig. 9B The message shown may be sent as a NAS message in some cases, and may be sent between a group of UEs (including UE 902) and a network server 906 (e.g., a network server hosting an AMF of a CN) of a 3GPP network 904. The message may be sent between the UE and the network server 906 via a base station (e.g., an eNB or a gNB). The operations performed by the UE may be performed by a corresponding processor of the UE, and the transmission and reception of the UE may be performed via a corresponding transceiver of the UE. The operations performed by the 3GPP network 904 may be performed by a processor of the network server 906, and the transmission and reception of the network server 906 may be performed via a communication interface of the network server 906.
[0081] The operations at 510 and 512 may be similar to those of reference Figure 5 The operations described may be performed for UE 902 and other UEs in the group of UEs.
[0082] The operations at 914 to 934 assume that the UE has downloaded at least one of a firmware update or a software update. The update may be downloaded from the 3GPP network 904 or over another wireless or wired network. The 3GPP network 904 may coordinate the download, be aware of the download, or be informed of the download.
[0083] At 914, the AF 910 may inform a policy control function (PCF) 912 of the 3GPP network 904 of the identities of the UEs and the times at which different UEs are scheduled to install the firmware or software update (e.g., via a network exposure function (NEF) of the 3GPP network 904). Different UEs may be scheduled to install the update at different times, but some UEs (e.g., a subset of UEs) may be scheduled to install the update at the same time.
[0084] At 916, the PCF 912 may notify the network server 906 (eg, AMF) of the set of UEs and their installation time.
[0085] At each of 918, 920, 922, etc., the network server 906 may send a configuration update command to a corresponding one of the UEs. For example, at 922, the network server 906 may send a configuration update command to the UE 902. Different configuration update commands may be sent at different times. Sending the configuration update command at different times may prevent a "signal storm," in which multiple UEs may perform updates at the same time and attempt to re-register with the 3GPP network 904 at or about the same time. Sending the configuration update command at different times may also reduce the chance that all (or a large number of) UEs become unavailable to the 3GPP network 904 at or about the same time. After sending the configuration update command to the UE, the network server 906 may retain the context of the UE for the expected duration of the UE's unavailability period.
[0086] At 924, 926, 928, etc., each of the UEs will install the update while the 3GPP network 904 (eg, network server 906) retains the context of the UEs.
[0087] At each of 930, 932, 934, etc., the respective UE may send a registration request message to the 3GPP network (e.g., to the network server 906) after completing the installation of the firmware update or software update. Since the timing of the configuration update commands sent at 918, 920, and 922 is staggered, the reception of the registration request messages by the 3GPP network at 930, 932, and 934 will likely be staggered. At 936, 938, 940, etc., the 3GPP network 904 (e.g., the network server 906) may respond to each registration request message with a registration accept message.
[0088] The process of flowchart 900 may be particularly applicable to IoT devices that may not have any kind of intelligent processing capabilities. The process may help save power for IoT or other power-constrained devices because it may reduce the chance of UEs experiencing random access channel (RACH) failures due to congestion caused by signal storms when many UEs complete firmware or software updates at the same time and simultaneously send registration request messages to the 3GPP network 904.
[0089] Fig.10 An example method 1000 for wireless communications by a UE is shown that may be used to preserve context of the UE during periods of unavailability of the UE.
[0090] At 1002, method 1000 can comprise determining to perform an operation during a period of unavailability of a UE.
[0091] At 1004, method 1000 may include, in response to determining to perform the operation, sending a first message to the 3GPP network requesting acceptance of the unavailability period. The first message may include an estimated duration of the unavailability period, such as, for example, reference Figures 1 to 7 described.
[0092] At 1006, method 1000 can comprise receiving a second message from the 3GPP network indicating acceptance of the unavailability period or rejection of the unavailability period.
[0093] Fig.11 An example method 1100 of communicating by a network server is shown that may be used to preserve the context of a UE during a period of unavailability of the UE.
[0094] At 1102, method 1100 may include receiving a first message from a UE requesting acceptance of an unavailability period of the UE. The first message may include an estimated duration of the unavailability period, such as, for example, reference Figures 1 to 7 described.
[0095] At 1104, method 1100 can include sending a second message to the UE indicating acceptance of the unavailability period or rejection of the unavailability period.
[0096] Fig.12
[0063] Another example method 1200 for wireless communications by a UE is shown that may be used to preserve context of the UE during periods of unavailability of the UE.
[0097] At 1202, method 1200 can include downloading at least one of a firmware update or a software update.
[0098] At 1204, method 1200 can include receiving a deregistration request message from the 3GPP network after downloading the software update indicating that the UE is to deregister from the 3GPP network and install the firmware update or software update during a period of unavailability of the UE.
[0099] At 1206, method 1200 can include starting an unavailability period after receiving the message indicating that the UE is to deregister from the 3GPP network.
[0100] At 1208, method 1200 may include installing the software update during the unavailability period.
[0101] At 1210, method 1200 can include sending a registration request message to a 3GPP network after installing the software update.
[0102] Embodiments contemplated herein include an apparatus having means for performing one or more elements of flowcharts 100, 200, 300, 400, 500, 600, 700, 800, or 900 or methods 1000, 1100, or 1200. Such an apparatus may be, for example, an apparatus of a UE (such as a wireless device as a UE, as described herein). Alternatively, such an apparatus may be, for example, an apparatus of a CN (such as a network device of a CN (e.g., AMF), as described herein).
[0103] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of flowcharts 100, 200, 300, 400, 500, 600, 700, 800, or 900 or methods 1000, 1100, or 1200. Such non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory of a wireless device that is a UE, as described herein). Alternatively, such non-transitory computer-readable media may be, for example, a memory of a CN (such as a memory of a network device (e.g., AMF) of the CN, as described herein).
[0104] Embodiments contemplated herein include an apparatus having logical components, modules, or circuits for performing one or more elements of flowcharts 100, 200, 300, 400, 500, 600, 700, 800, or 900 or methods 1000, 1100, or 1200. Such an apparatus may be, for example, an apparatus of a UE (such as a wireless device as a UE, as described herein). Alternatively, such an apparatus may be, for example, an apparatus of a CN (such as a network device of a CN (e.g., AMF), as described herein).
[0105] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of flowcharts 100, 200, 300, 400, 500, 600, 700, 800, or 900 or methods 1000, 1100, or 1200. Such an apparatus may be, for example, an apparatus of a UE (such as a wireless device that is a UE, as described herein). Alternatively, such an apparatus may be, for example, an apparatus of a CN (such as a network device of a CN (e.g., an AMF), as described herein).
[0106] Embodiments contemplated herein include a signal as described in or associated with one or more elements of flowcharts 100 , 200 , 300 , 400 , 500 , 600 , 700 , 800 , or 900 , or methods 1000 , 1100 , or 1200 .
[0107] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein the program is executed by a processor to cause the processor to perform one or more elements of flowchart 100, 200, 300, 400, 500, 600, 700, 800 or 900 or method 1000, 1100 or 1200. The processor may be a processor of a UE (such as a processor of a wireless device as a UE, as described herein), and the instructions may be located, for example, in the processor and / or on a memory of the UE (such as a memory of a wireless device as a UE, as described herein). Alternatively, the processor may be a processor of a CN (such as a processor of a network device (e.g., AMF) of the CN, as described herein), and the instructions may be located, for example, in the processor and / or on a memory of the CN (such as a memory of a network device (e.g., AMF) of the CN, as described herein).
[0108] Fig.13 An example architecture of a wireless communication system 1300 according to an embodiment disclosed herein is illustrated. The following description is provided for an example wireless communication system 1300 operating in conjunction with 4G or LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.
[0109] like Fig.13 As shown, the wireless communication system 1300 includes UE 1302 and UE 1304 (although any number of UEs may be used). In this example, UE 1302 and UE 1304 are illustrated as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.
[0110] UE 1302 and UE 1304 may be configured to be communicatively coupled to RAN 1306. In an embodiment, RAN 1306 may be NG-RAN, E-UTRAN, etc. UE 1302 and UE 1304 utilize connections (or channels) (shown as connection 1308 and connection 1310, respectively) with RAN 1306, where each connection (or channel) includes a physical communication interface. RAN 1306 may include one or more base stations, such as base station 1312 and base station 1314, to implement connection 1308 and connection 1310.
[0111] In this example, connection 1308 and connection 1310 are air interfaces that enable such communicative coupling and may conform to the RAT used by RAN 1306, such as, for example, LTE and / or NR.
[0112] In some embodiments, UE 1302 and UE 1304 may also directly exchange communication data via side link interface 1316. UE 1304 is shown as being configured to access an access point (shown as AP 1318) via connection 1320. By way of example, connection 1320 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 1318 may include In this example, AP 1318 can connect to another network (eg, the Internet) without going through CN 1324.
[0113] In an embodiment, UE 1302 and UE 1304 may be configured to communicate with each other or with base station 1312 and / or base station 1314 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.
[0114] In some embodiments, all or part of base station 1312 or base station 1314 may be implemented as one or more software entities running on a server computer as part of a virtual network. In addition, or in other embodiments, base station 1312 or base station 1314 may be configured to communicate with each other via interface 1322. In an embodiment where wireless communication system 1300 is an LTE system (e.g., when CN 1324 is an EPC), interface 1322 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In an embodiment where wireless communication system 1300 is an NR system (e.g., when CN 1324 is a 5GC), interface 1322 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to a 5GC, between a base station 1312 (e.g., a gNB) and an eNB connected to a 5GC, and / or between two eNBs connected to a 5GC (e.g., CN 1324).
[0115] RAN 1306 is shown as being communicatively coupled to CN 1324. CN 1324 may include one or more network elements 1326, including one or more AMFs, configured to provide various data and communication services to customers / subscribers (e.g., UE 1302 and users of UE 1304) connected to CN 1324 via RAN 1306. The components of CN 1324 may be implemented in one physical device or separate physical devices including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).
[0116] In an embodiment, CN 1324 may be an EPC, and RAN 1306 may be connected to CN 1324 via an S1 interface 1328. In an embodiment, S1 interface 1328 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between base station 1312 or base station 1314 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between base station 1312 or base station 1314 and a mobility management entity (MME).
[0117] In an embodiment, CN 1324 may be a 5GC, and RAN 1306 may be connected to CN 1324 via an NG interface 1328. In an embodiment, NG interface 1328 may be divided into two parts: an NG user plane (NG-U) interface, which carries service data between base station 1312 or base station 1314 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between base station 1312 or base station 1314 and AMF.
[0118] In general, the application server 1330 may be an element that provides applications (e.g., packet-switched data services) that use Internet Protocol (IP) bearer resources with the CN 1324. The application server 1330 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 1302 and the UE 1304 via the CN 1324. The application server 1330 may communicate with the CN 1324 via the IP communication interface 1332.
[0119] Fig.14 A system 1400 for performing signaling 1436, 1438 between a wireless device 1402 and one or more network devices 1418, 1424 according to embodiments disclosed herein is illustrated. The system 1400 may be part of a wireless communication system as described herein. The wireless device 1402 may be, for example, a UE of a wireless communication system. The network devices 1418, 1424 may include, for example, a base station (e.g., gNB) and an AMF of the wireless communication system.
[0120] The wireless device 1402 may include one or more processors 1404. The processor 1404 may execute instructions to cause various operations of the wireless device 1402 to be performed, as described herein. The processor 1404 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0121] The wireless device 1402 may include a memory 1406. The memory 1406 may be a non-transitory computer-readable storage medium that stores instructions 1408 (which may include, for example, instructions executed by the processor 1404). The instructions 1408 may also be referred to as program code or a computer program. The memory 1406 may also store data used by the processor 1404 and results computed by the processor.
[0122] The wireless device 1402 may include one or more transceivers 1410, which may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 1412 of the wireless device 1402 to facilitate signaling (e.g., signaling 1436) sent or received by the wireless device 1402 with other devices (e.g., network device 1418) according to a corresponding RAT.
[0123] The wireless device 1402 may include one or more antennas 1412 (e.g., one, two, four, or more). For embodiments with multiple antennas 1412, the wireless device 1402 may exploit the spatial diversity of such multiple antennas 1412 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmission by the wireless device 1402 may be implemented based on precoding (or digital beamforming) applied at the wireless device 1402, which multiplexes the data streams across the antennas 1412 based on known or assumed channel characteristics, so that each data stream is received with appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with the data stream). Certain embodiments may use a single-user MIMO (SU-MIMO) approach (where data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).
[0124] In certain embodiments with multiple antennas, the wireless device 1402 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 1412 are relatively adjusted so that the (joint) transmissions of the antennas 1412 can be directed (this is sometimes referred to as beam steering).
[0125] The wireless device 1402 may include one or more interfaces 1414. The interfaces 1414 may be used to provide input to or output from the wireless device 1402. For example, a wireless device 1402 that is a UE may include an interface 1414, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to provide input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits (e.g., in addition to the transceiver 1410 / antenna 1412 described above), which allow the UE to communicate with other devices and may communicate according to known protocols (e.g., etc.) to perform the operation.
[0126] The wireless device 1402 may include an unavailability period management module 1416. The unavailability period management module 1416 may be implemented via hardware, software, or a combination thereof. For example, the unavailability period management module 1416 may be implemented as a processor, circuit, and / or instructions 1408 stored in the memory 1406 and executed by the processor 1404. In some examples, the unavailability period management module 1416 may be integrated within the processor 1404 and / or the transceiver 1410. For example, the unavailability period management module 1416 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 1404 or the transceiver 1410.
[0127] The unavailability period management module 1416 may be used in various aspects of the present disclosure, for example, Figures 1 to 12 The unavailability period management module 1416 may be configured, for example, to determine or manage unavailability periods of the wireless device 1402, as described herein.
[0128] The network device 1418 may also include one or more processors. The processor may execute instructions so that various operations of the network device 1418 are performed as described herein. The processor may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0129] The network device 1418 may include a memory. The memory may be a non-transitory computer-readable storage medium that stores instructions (which may include, for example, instructions executed by a processor). Instructions may also be referred to as program code or a computer program. The memory may also store data used by the processor and results calculated by the processor.
[0130] The network device 1418 may include one or more transceivers, which may include RF transmitter and / or receiver circuits that use the antenna 1420 of the network device 1418 to facilitate signaling (e.g., signaling 1436) sent or received by the network device 1418 with other devices (e.g., wireless device 1402) according to the corresponding RAT.
[0131] The network device 1418 may include one or more antennas 1420 (e.g., one, two, four, or more). In embodiments with multiple antennas 1420, the network device 1418 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described.
[0132] The network device 1418 may include one or more interfaces. The interface may be used to provide input to or output from the network device 1418. For example, the network device 1418 as a base station may include an interface consisting of a transmitter, a receiver, and other circuits (e.g., in addition to the transceiver / antenna 1420 already described), which enables the base station to communicate with other equipment in the core network (e.g., network device 1424) and / or enables the base station to communicate with an external network, computer, database, etc., in order to achieve the purpose of performing operations, management, and maintenance of the base station or other equipment operably connected to the base station.
[0133] The network device 1418 may include an unavailability period management module 1422. The unavailability period management module 1422 may be implemented via hardware, software, or a combination thereof. For example, the unavailability period management module 1422 may be implemented as a processor, a circuit, and / or instructions stored in a memory and executed by a processor. In some examples, the unavailability period management module 1422 may be integrated within a processor and / or a transceiver. For example, the unavailability period management module 1422 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuits) within a processor or a transceiver.
[0134] The unavailability period management module 1422 may be used in various aspects of the present disclosure, for example, Figures 1 to 12 The unavailability period management module 1422 may be configured, for example, to determine or manage unavailability periods of the wireless device 1402, as described herein.
[0135] The network device 1424 may also include one or more processors 1426. The processor 1426 may execute instructions 1430 so that various operations of the network device 1424 are performed as described herein. The processor 1426 may include one or more processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0136] The network device 1424 may include a memory 1428. The memory 1428 may be a non-transitory computer-readable storage medium that stores instructions 1430 (which may include, for example, instructions executed by the processor 1426). The instructions 1430 may also be referred to as program code or a computer program. The memory 1428 may also store data used by the processor 1426 and results calculated by the processor.
[0137] The network device 1424 may include one or more interfaces 1432. The interface 1432 may be used to provide input to or output from the network device 1418. For example, the network device 1424 of the AMF as the core network may include an interface consisting of a transmitter, a receiver and other circuits, which enables the AMF to communicate with other equipment (e.g., with the network device 1418 via signaling 1438, or with the wireless device 1402 via signaling 1438, and with the network device 1418), and / or enables the AMF to communicate with external networks, computers, databases, etc., in order to achieve the purpose of performing operations, management and maintenance of the AMF or other equipment operably connected to the AMF.
[0138] The network device 1424 may include an unavailability period management module 1434. The unavailability period management module 1434 may be implemented via hardware, software, or a combination thereof. For example, the unavailability period management module 1434 may be implemented as a processor, circuit, and / or instructions 1430 stored in the memory 1428 and executed by the processor 1426. In some examples, the unavailability period management module 1434 may be integrated within the processor 1426. For example, the unavailability period management module 1434 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 1426.
[0139] The unavailability period management module 1434 may be used in various aspects of the present disclosure, for example, Figures 1 to 12 The unavailability period management module 1434 may be configured, for example, to determine or manage unavailability periods of the wireless device 1402, as described herein.
[0140] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. For another example, circuits associated with a UE, a base station, a network element, etc. as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.
[0141] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.
[0142] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations; or may include a combination of hardware, software, and / or firmware.
[0143] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of another embodiment may be used in one embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless expressly stated herein.
[0144] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.
[0145] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1. A user equipment (UE), the UE comprising: Transceiver; and A processor, the processor being configured to: determining to perform an operation during a period of unavailability of the UE; in response to determining to perform the operations and sending, via the transceiver, a first message to a 3rd Generation Partnership Project (3GPP) network requesting acceptance of the unavailability period, the first message including an estimated duration of the unavailability period; as well as A second message indicating the acceptance of the unavailability period or a rejection of the unavailability period is received from the 3GPP network via the transceiver.
2. The UE according to claim 1, wherein: The processor is configured to: before sending the first message, sending, in a 5G Mobility Management (5GMM) Capability Information Element (IE) of a Registration Request message and via the transceiver to the 3GPP network, an indication of a capability for determining the unavailability period; and An indication of support for the capability for determining the unavailability period is received in a 5G System (5GS) Network Feature Support IE of a Registration Accept message and via the transceiver from the 3GPP network.
3. The UE according to claim 1, wherein: The first message is a registration request message, and the estimated duration of the unavailability period is included in a first information element (IE) of the registration request message; and The second message is a registration accept message including a second IE indicating the acceptance or the rejection of the unavailability period.
4. The UE according to claim 1, wherein: The second message indicates that the unavailability period is accepted; and The processor is configured to: in response to the unavailability period being accepted, starting the unavailability period; as well as The operation is performed during the unavailability period.
5. The UE according to claim 4, wherein: The processor is configured to: in response to the unavailability period being accepted, before starting the unavailability period, sending, via the transceiver, a deregistration request message to the 3GPP network; as well as After performing the operation, a registration request message is sent to the 3GPP network via the transceiver. The UE according to claim 5 , wherein the deregistration request message includes a reason or type of deregistration.
7. The UE according to claim 4, wherein: The processor is configured to: After performing the operation, a registration request message or a service request message is sent to the 3GPP network via the transceiver.
8. The UE according to claim 1, wherein: The second message references a backoff timer; and The processor is configured to: Starting the backoff timer; and After the backoff timer ends, sending a deregistration request message to the 3GPP network via the transceiver; receiving a deregistration accept message from the 3GPP network in response to sending the deregistration request message; starting the unavailability period after receiving the deregistration accept message; performing the operation during the unavailability period; as well as After performing the operation, a registration request message is sent to the 3GPP network via the transceiver.
9. The UE according to claim 1, wherein: The second message references a backoff timer; and The processor is configured to: Starting the backoff timer; sending a third message to the 3GPP network via the transceiver after starting the back-off timer and before ending the back-off timer; receiving, in response to the third message and via the transceiver, from the 3GPP network a fourth message including the acceptance of the unavailability period; as well as In response to the unavailability period being accepted, starting the unavailability period; as well as The operation is performed during the unavailability period.
10. The UE according to claim 1, wherein: The second message indicates that the unavailability period is rejected; and The processor is configured to: sending, after receiving the second message and via the transceiver, to the 3GPP network a third message requesting the acceptance of the unavailability period, the third message comprising the estimated duration of the unavailability period; as well as A fourth message including the acceptance or the rejection of the unavailability period is received from the 3GPP network via the transceiver.
11. The UE according to claim 1, wherein: The processor is configured to: before sending the first message, sending, in a 5G Mobility Management (5GMM) core network capabilities information element (IE) of a registration request message and via the transceiver to the 3GPP network, an indication of a capability to support Multiple Universal Subscriber Identity Module (MUSIM) connection release, MUSIM paging restriction, and the estimated duration of the unavailability period; as well as An indication of the estimated duration to support the MUSIM connection release, the MUSIM paging restriction, and the unavailability period is received from the 3GPP network via the transceiver in a REGISTER ACCEPT message.
12. The UE according to claim 1, wherein: The first message is a registration request message or a service request message, and the first message further includes a release request indication and a paging restriction indication; and The second message is a registration accept message or a service accept message including the acceptance or the rejection of the unavailability period.
13. The UE according to claim 1, wherein: The second message references a backoff timer; and The processor is configured to: Starting the backoff timer; After the backoff timer ends, starting the unavailability period; performing the operations during the unavailability period; and After performing the operation, a registration request message or a service request message is sent to the 3GPP network via the transceiver.
14. The UE of claim 1, wherein the operation comprises at least one of a firmware update or a software update.
15. A user equipment (UE), the UE comprising: Transceiver; and A processor, the processor being configured to: downloading at least one of a firmware update or a software update; receiving, after downloading the software update, a deregistration request message from a 3rd Generation Partnership Project (3GPP) network via the transceiver indicating that the UE is to deregister from the 3GPP network and install the firmware update or the software update during a period of unavailability of the UE; starting the unavailability period after receiving the message indicating that the UE is to deregister from the 3GPP network; installing the software update during the unavailability period; as well as A registration request message is sent via the transceiver to the 3GPP network after installing the software update.
16. A network server, comprising: Communication interface; and A processor, the processor being configured to: receiving, via the communication interface, from a user equipment (UE) a first message requesting acceptance of an unavailability period for the UE, the first message comprising an estimated duration of the unavailability period; as well as A second message indicating the acceptance of the unavailability period or the rejection of the unavailability period is sent to the UE via the communication interface.
17. The network server according to claim 16, wherein: The processor is configured to: before receiving the first message, receiving, from the UE via the communications interface and in a 5G Mobility Management (5GMM) Capability Information Element (IE) of a Registration Request message, an indication of a capability for determining the unavailability period; and An indication of support for the capability for determining the unavailability period is sent in a 5G System (5GS) Network Feature Support IE of a Registration Accept message and to the UE via the communication interface.
18. The network server according to claim 16, wherein: The second message references a backoff timer; and The processor is configured to: Starting the backoff timer; After the back-off timer ends, receiving a deregistration request message from the UE via the communication interface; as well as After receiving the deregistration request message, starting a timer for the estimated duration of the unavailability period; as well as retaining the context of the UE; as well as Monitoring for a registration request message from the UE after ending the timer for the estimated duration of the unavailability period.
19. The network server according to claim 16, wherein: The second message references a backoff timer; and The processor is configured to: Starting the backoff timer; After the backoff timer ends, starting a timer for the estimated duration of the unavailability period; as well as retaining the context of the UE and limiting paging of the UE; as well as A registration request message or a service request message from the UE is monitored after ending the timer for the estimated duration of the unavailability period.
20. The network server according to claim 19, wherein: The processor is configured to: The context of the UE is restored when the registration request message or the service request message is received; otherwise, the context of the UE is deleted.
