User equipment behavior when non-satellite access is not allowed in mobile communications

Abstract

Related techniques are described for user equipment (UE) behavior when non-satellite access is not allowed in mobile communications. An apparatus (e.g., UE) sends a request to access a network over a non-satellite access to the network without allowing use of the non-satellite access. In response, the apparatus receives a rejection message with a new rejection cause from the network. The new rejection reason comprises one or both of the following: (a) a public land mobile network, PLMN, is specific and indicates that the UE is not allowed to access the PLMN or an equivalent PLMN through non-satellite access; and (b) encompassing all subscription-based PLMNs and indicating that the UE is not allowed to access any network through non-satellite access.

Description

[0001] Cross-referencing

[0002] This disclosure claims priority to Indian Patent Applications Nos. 202321061303, 202321061304, 202321061305, 202321061306 and 202321061307, filed on September 12, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically to the behavior of a user equipment (UE) when non-satellite access is not permitted in mobile communications. Background Technology

[0004] In the current third-generation partnership program (The 3) rd In wireless communications (such as mobile communications) under the Generation Partnership Project (3GPP) specification, when a User Equipment (UE) requests registration via non-satellite access, but the UE is not permitted to use non-satellite access due to its subscription or in a public land mobile network (PLMN), the network may refuse the UE. When the network (e.g., the PLMN) cannot allow the UE to use non-satellite access, the UE's behavior is not yet defined. Therefore, solutions targeting UE behavior are needed when non-satellite access is not permitted in mobile communications. Summary of the Invention

[0005] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Detailed descriptions will follow in the following description section. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0006] One objective of this disclosure is to propose solutions or strategies for addressing the problems described herein. More specifically, the various solutions proposed in this disclosure are believed to provide solutions for user equipment (UE) behavior when non-satellite access is not permitted in mobile communications. It is believed that implementations of one or more of the solutions proposed herein can solve or mitigate the aforementioned problems.

[0007] In one aspect, a method may involve a network receiving a request from a user equipment (UE) to access a network via non-satellite access, where the UE is not permitted to use non-satellite access. The method may also involve the network rejecting the request by sending a rejection message to the UE with a new rejection reason. This new rejection reason may include one or both of the following: (a) specific to a Public Land Mobile Network (PLMN) and indicating that the UE is not permitted to access the PLMN or an equivalent PLMN via non-satellite access; and (b) covering all subscription-based PLMNs and indicating that the UE is not permitted to access any network via non-satellite access.

[0008] In another aspect, a method may involve a UE sending a request to the network to access the network via non-satellite access, where the UE is not permitted to use non-satellite access. The method may also involve the UE receiving a rejection message from the network with a new rejection reason. This new rejection reason may include one or both of the following: (a) specific to a Public Land Mobile Network (PLMN) and indicating that the UE is not permitted to access the PLMN or an equivalent PLMN via non-satellite access; and (b) covering all subscription-based PLMNs and indicating that the UE is not permitted to access any network via non-satellite access.

[0009] It is worth noting that although the content described herein may be within the context of certain wireless access technologies, networks, and network topologies, such as fifth-generation (5G) / New Radio (NR) / B5G (B5G) mobile communications, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of wireless access technologies, networks, and network topologies, such as, but not limited to, fourth-generation (4G) / Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), vehicle-to-everything (V2X), and non-terrestrial network (NTN) communications. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0010] The accompanying drawings are included in this specification to further understand this disclosure and form part of this disclosure. The drawings illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions for clarity in illustrating the concepts of this disclosure.

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

[0012] Figure 2 This is a block diagram of an example communication system, which is consistent with an implementation of the present disclosure.

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

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

[0015] Detailed embodiments and implementations of the subject matter of the claims are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are for illustrative purposes only and may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to fully communicate the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0016] Overview

[0017] According to the implementation of this disclosure, various techniques, methods, schemes, and / or solutions relate to the behavior of user equipment (UE) in mobile communications when non-satellite access is not permitted. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in combination.

[0018] Figure 1 An example network environment 100 is shown in which various solutions and schemes of this disclosure can be implemented. Figures 2-4Examples of implementing various proposed solutions according to this disclosure are shown in network environment 100. The following description of the various proposed solutions is in conjunction with… Figures 1-4 It was carried out.

[0019] See Figure 1 Network environment 100 may involve a UE 110, such as a mobile device or smartphone, wirelessly communicating with wireless network 120 as part of a communication network. Wireless network 120 may be a Public Land Mobile Network (PLMN) encompassing 5G / NR and 4G / LTE domains. UE 110 may initially communicate wirelessly with wireless network 120 via a base station or network node 125 (e.g., eNB, gNB, or Transceiver Point (TRP)). In network environment 100, UE 110 and wireless network 120 may implement various schemes regarding UE behavior when non-satellite access is not permitted in mobile communications, as described herein.

[0020] It is worth noting that although the various proposed schemes may be described separately or individually below, in actual implementation, some or all of the proposed schemes may be used in combination or implemented together. Of course, each proposed scheme may also be used or implemented individually or separately. In addition, as used in this article, "lower layer" may refer to the layers below the Radio Resource Control (RRC) layer in the 5GMM protocol stack, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, Physical (PHY) layer, etc.

[0021] According to various proposed schemes in this disclosure, a request from UE 110 to access network 120 via non-satellite access may be rejected by network 120 for a new rejection reason, indicating that UE 110 is not permitted to access network 120 via non-satellite access. This new rejection reason may be: (1) PLMN-specific, indicating that UE 110 is not permitted to access that PLMN (and / or its equivalent PLMN) via non-satellite access; and / or (2) all PLMNs (based on subscription), indicating that UE 110 is not permitted to access any network via non-satellite access.

[0022] According to one approach proposed in this disclosure, regarding a new PLMN-specific denial reason for restricting non-satellite access in a PLMN, if UE 110 is denied service requesting a new PLMN-specific denial reason, or if network 120 initiates a separation or deregistration procedure and indicates the reason after UE 110 has successfully registered for non-satellite access, then UE 110 may perform one, several, or all of the following operations after receiving a denial from network 120 (e.g., a fifth-generation system (5GS) network).

[0023] For example, User Equipment (UE) 110 can set its 5G System (5GS) update status to 5U3 roaming not allowed. Alternatively, UE 110 can delete the last accessed Registration Tracking Area Identifier (TAI). Alternatively, UE 110 can delete the TAI list. Alternatively, UE 110 can delete the 5G Globally Unique Temporary Identifier (5G-GUTI) if UE 110 is not registered or not registered to the same Public Land Mobile Network (PLMN) through other access. Alternatively, UE 10 can delete the ngKSI (ngKSI consists of a value and a security context parameter type indicating whether the 5G non-access stratum (NAS) security context is a native 5G NAS security context or a mapped 5G NAS security context) if UE 110 is not registered or not registered to the same PLMN through other access. Alternatively, UE 110 can enter the PLMN-SEARCH state. Alternatively, UE 110 can enter the LIMITED-SERVICE state. Alternatively, UE 110 may treat the PLMN as prohibited and store "(N1 mode) non-satellite access prohibited PLMN", or disable the PLMN's non-satellite access N1 mode capability. Alternatively, if UE 110 treats the PLMN as prohibited, UE 110 may store the PLMN identifier in a new prohibited list (e.g., "5GCN non-satellite access prohibited PLMN" or "non-satellite access prohibited PLMN"). Alternatively, if UE 110 disables the PLMN's non-satellite access N1 mode capability, UE 110 may start a timer and enable the PLMN's non-satellite access N1 mode capability upon timer expiration, removal of the universal subscriber identity module (USIM), or UE power-on and power-off. Alternatively, UE 110 may start the T3245 timer if configured to use the T3245 timer. Alternatively, UE 110 may perform a PLMN selection procedure. Alternatively, UE 110 may maintain a new non-integrity protection counter (e.g., a non-satellite access PLMN-specific attempt counter). Alternatively, UE 110 can set a new counter for the PLMN (a PLMN-specific attempt counter for non-satellite access) to a value specific to the UE if the rejection message has been successfully integrity checked by the Non-Access Stratum (NAS). Alternatively, UE 110 can start a T3540 timer for NAS signaling connection release.Alternatively, UE 110 can process Evolved Packet System (EPS) Mobility Management (EMM) parameters such as EMM status and / or EPS update status and / or 4G-GUTI and / or last accessed registration TAI and / or TAI list and / or eKSI and / or EMM attach attempt counter and / or tracking area update attempt counter, similar to 5GMM with the same reason value. Alternatively, UE 110 can clear the new banned PLMN list when the T3245 timer expires. Alternatively, UE 110 can remove the selected PLMN from the new banned list when UE 110 registers to the selected PLMN on a non-satellite cell. Alternatively, UE 110 can start the T3247 timer when a new rejection reason value is received for non-integrity protection. Alternatively, UE 110 can increment a new counter (non-satellite access PLMN-specific attempt counter) for the PLMN to a UE-specific maximum value if the message has been checked for NAS non-integrity. Alternatively, for each new counter (a PLMN-specific attempt counter for non-satellite access) whose value is greater than zero and less than a UE-specific maximum value, UE 110 may remove the corresponding PLMN from the new prohibited PLMN list (prohibited PLMNs for non-satellite access) when the T3247 timer expires and / or UE 110 is turned off and / or the USIM is removed. Alternatively, UE 110 may, if stored, remove the PLMN identified by the list in the REFRESH command from the new prohibited PLMN list and enable the PLMN's non-satellite access N1 mode capability if disabled. Alternatively, UE 110 may, if stored, remove the PLMN identified by the preferred PLMN / access technology combination list provided in the steering of roaming (SOR) from the new prohibited PLMN list and enable the PLMN's non-satellite access N1 mode capability if disabled. Alternatively, UE 110 may, if stored, ignore the contents of the new prohibited PLMN list and enable the PLMN's non-satellite access N1 mode capability when the user manually selects a PLMN for registration if disabled.

[0024] According to one proposed scheme of this disclosure, for a specific denial reason for non-satellite access (access restricted by subscription), when UE 110 requests service, it is denied non-satellite access due to a new denial reason, or when network 120 initiates a separation or deregistration procedure and indicates the reason after UE 110 has successfully registered for non-satellite access, UE 110 may perform one, several, or all of the following operations after receiving the denial from network 120 (e.g., a 5GS network).

[0025] For example, UE 110 can set the 5GS update status to 5U3 roaming not allowed. Alternatively, UE 110 can delete the last accessed registered TAI. Alternatively, UE 110 can delete the TAI list. Alternatively, UE 110 can delete the 5G-GUTI if UE 110 is not registered or not registered to the same PLMN through other access. Alternatively, UE 110 can delete the ngKSI if UE 110 is not registered or not registered to the same PLMN through other access. Alternatively, UE 110 can enter the PLMN-SEARCH state. Alternatively, UE 110 can enter the LIMITED-SERVICE state. Alternatively, UE 110 can disable the N1 mode capability for non-satellite access. Alternatively, UE 110 can start a timer for disabling and enabling the N1 mode capability for non-satellite access for the PLMN when the timer expires, the USIM is removed, or the UE powers on / off. Alternatively, UE 110 can start the T3245 timer if configured to use the T3245 timer. Alternatively, UE 110 can perform a PLMN selection procedure. Alternatively, UE 110 can maintain a new non-integrity protection counter, for example, if the USIM / Subscriber Identity Module (SIM) is deemed invalid for non-satellite access (all modes or N1 mode only). Alternatively, UE 110 can set a new counter to a UE-specific maximum value if the message has been successfully integrity checked by NAS. Alternatively, UE 110 can start a T3540 timer for NAS signaling connection release. Alternatively, UE 110 can process EMM parameters EMM status and / or EPS update status and / or 4G-GUTI and / or last accessed registered TAI and / or TAI list and / or eKSI and / or EMM attach attempt counter and / or tracking area update attempt counter, similar to 5GMM with the same reason value. Alternatively, UE 110 can clear a new banned PLMN list when the T3245 timer expires. Alternatively, UE 110 can start a T3247 timer when a new rejection reason value is non-integrity protection. Alternatively, UE 110 can increment a new counter when the message is non-integrity protection. Alternatively, UE 110 may set SIM / USIM to be valid for non-satellite services when the T3247 timer expires and / or UE 110 is turned off and / or USIM is removed, under the following conditions: (a) UE 110 does not maintain a counter for the "SIM / USIM is deemed invalid for non-satellite services" event; or (b) UE 110 maintains a counter for the "SIM / USIM is deemed invalid for non-satellite services" event and the value of the counter is less than a specific maximum value implemented by the UE.

[0026] In one proposed solution of this disclosure, for applicability to other systems such as General Packet Radio Service (GPRS), Evolved Packet System (EPS), and 6G, the proposed solution may also be applied to other systems such as GPRS, EPS, 6G, WiMax, WiFi (or Wi-Fi), and non-3GPP access to meet the corresponding requirements of restricting user equipment (UE) 110 from using non-satellite access. Implementation of the proposed solution may include certain methods, functions, and / or parameters (excluding other items mentioned above), such as: (a) new rejection reasons received from network 120; and (b) the UE's behavior upon receiving a rejection reason, such as: (i) maintaining new timers and other timers, i.e., timer start-up, stop-up, and timer expiration behavior; (ii) maintaining different lists (e.g., new prohibited lists); and (iii) disabling / enabling N1, S1, or other modes.

[0027] Exemplary Implementation

[0028] Figure 2 An example communication system 200 is shown, having at least one example device 210 and one example device 220, conforming to one implementation of this disclosure. Each of devices 210 and 220 is capable of performing various functions to implement the schemes, techniques, processes, and methods described herein, relating to UE behavior when non-satellite access is not permitted in mobile communications, encompassing the various schemes described above regarding various proposed designs, concepts, schemes, systems, and methods, including network environment 100, and the processes described below.

[0029] Each of devices 210 and 220 can be part of an electronic device, which can be a network device or UE (e.g., UE110), such as a portable or mobile device, a wearable device, an in-vehicle device or vehicle, a wireless communication device, or a computing device. For example, each of devices 210 and 220 can be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet, laptop, or mobile phone. Each of devices 210 and 220 can also be part of a machine-type device, which can be an Internet of Things (IoT) device, such as a non-mobile or fixed device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, each of devices 210 and 220 can be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented as a network device, device 210 and / or device 220 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, NR, or IoT network.

[0030] In some implementations, each of devices 210 and 220 can 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, each of devices 210 and 220 can be implemented as a network device or a UE. Each of devices 210 and 220 can contain... Figure 2 At least some components are shown, such as processor 212 and processor 222. Each of devices 210 and 220 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solutions of this disclosure; therefore, for the sake of brevity, Figure 2 These components are not shown and are not described below.

[0031] In one aspect, each of processors 212 and 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. Even though the singular term "a processor" is used herein to refer to processors 212 and 222, in some implementations each of processors 212 and 222 may comprise multiple processors, and in other implementations a single processor, consistent with this disclosure. In another aspect, each of processors 212 and 222 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, these electronic components being configured and arranged to achieve the specific purposes of this disclosure. In other words, in at least some implementations, each of processors 212 and 222 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to UE behavior when non-satellite access is not permitted in mobile communications, consistent with various implementations of this disclosure.

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

[0033] In some implementations, device 210 may further include a memory 214 coupled to processor 212, which can access and store data therein. In some implementations, device 220 may further include a memory 224 coupled to processor 222, which can access and store data therein. Each of memory 214 and memory 224 may include a random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitance RAM (Z-RAM). Alternatively, or additionally, each of memory 214 and memory 224 may include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of memories 214 and 224 may contain 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.

[0034] Each of devices 210 and 220 can be a communication entity capable of communicating with each other using various schemes proposed in this disclosure. For illustrative purposes and without limitation, the following describes the capabilities of device 210 as a UE (e.g., UE 110) and device 220 as a network node (e.g., network node 125) in a network (e.g., a wireless network 120 as a 5G / NR mobile network) within the context of example flows 300 and 400.

[0035] Exemplary process

[0036] Figure 3 An example flow 300 according to an embodiment of the present disclosure is illustrated. Flow 300 may represent one aspect of implementing the various designs, concepts, schemes, systems, and methods proposed above. More specifically, flow 300 may represent one aspect of the related concepts and schemes proposed in this disclosure concerning the behavior of a user equipment (UE) when non-satellite access is not permitted in mobile communications. Flow 300 may include one or more operations, actions, or functions as shown in blocks 310 and 320. Although shown in discrete block form, the individual blocks of flow 300 may be divided into more blocks, merged into fewer blocks, or omitted depending on the desired implementation. Furthermore, the blocks / sub-blocks of flow 300 may be arranged according to... Figure 3The process can be executed in the order shown, or in a different order. Furthermore, one or more blocks / subblocks of process 300 may be repeated or iteratively executed. Process 300 may be implemented by or in devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 300 is described below with device 210 as a user equipment (e.g., UE 110) and device 220 as a communication entity of a network (e.g., a network node or base station, such as network node 125, or a network such as wireless network 120). Process 300 may begin at block 310.

[0037] At 310, process 300 may involve the processor 222 of device 220 receiving, via transceiver 226, a request for access to a network via a non-satellite access from a user equipment (e.g., device 210), which is not permitted to use the non-satellite access. Process 300 may continue from 310 to 320.

[0038] At 320, process 300 may involve processor 222 sending a rejection message with a new rejection reason to user equipment via transceiver 226 to reject the request. The new rejection reason may include one or both of the following: (a) specific to a Public Land Mobile Network (PLMN) and indicating that the user equipment is not permitted to access the PLMN or equivalent via non-satellite access; and (b) covering all subscription-based PLMNs and indicating that the user equipment is not permitted to access any network via non-satellite access.

[0039] In some embodiments, upon rejection, process 300 may involve processor 222 rejecting a service request from a user equipment with a new rejection reason specific to the PLMN.

[0040] In some embodiments, upon rejection, process 300 may involve processor 222 rejecting the network when initiating a disconnect or deregistration procedure and indicating a new reason for rejection, even though the user equipment has successfully registered via non-satellite access.

[0041] In some embodiments, upon rejection, process 300 may involve processor 222 rejecting a user equipment request for service with a new rejection reason, thereby restricting the use of non-satellite access.

[0042] Figure 4An example flow 400 according to an embodiment of this disclosure is illustrated. Flow 400 may represent one aspect of implementing the various designs, concepts, schemes, systems, and methods proposed above. More specifically, flow 400 may represent one aspect of the related concepts and schemes proposed in this disclosure concerning the behavior of a user equipment (UE) when non-satellite access is not permitted in mobile communications. Flow 400 may include one or more operations, actions, or functions as shown in blocks 410 and 420. Although shown in discrete block form, the individual blocks of flow 400 may be divided into more blocks, merged into fewer blocks, or omitted depending on the desired implementation. Furthermore, the blocks / sub-blocks of flow 400 may be arranged according to... Figure 4 The process can be executed in the order shown, or in a different order. Furthermore, one or more blocks / subblocks of process 400 may be repeated or iteratively executed. Process 400 may be implemented by or in devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 400 is described below with device 210 as a user equipment (e.g., UE 110) and device 220 as a communication entity of a network (e.g., a network node or base station, such as network node 125, or a network such as wireless network 120). Process 400 may begin at block 410.

[0043] At 410, process 400 may involve the processor 212 of device 210 acting as a user equipment, sending a request via transceiver 216 to a network (e.g., via wireless network 120, where device 220 acts as network node 125) to access the network via a non-satellite access, whereby the user equipment is not permitted to use the non-satellite access. Process 400 may continue from 410 to 420.

[0044] At 420, process 400 may involve processor 212 receiving a rejection message with a new rejection reason from the network via transceiver 216. The new rejection reason may include one or both of the following: (a) specific to a Public Land Mobile Network (PLMN) and indicating that the user equipment is not permitted to access the PLMN or equivalent via non-satellite access; and (b) covering all subscription-based PLMNs and indicating that the user equipment is not permitted to access any network via non-satellite access.

[0045] In some embodiments, in response to a new rejection reason that restricts the use of non-satellite access in the PLMN as a new PLMN-specific rejection reason, process 400 may involve processor 212 performing at least one of the following operations: (1) setting the 5GS update status to 5U3 roaming not allowed; (2) deleting the last accessed registered TAI; (3) deleting the TAI list; (4) deleting the 5G-GUTI if the user equipment is not registered or not registered to the same PLMN through other access; (5) deleting the ngKSI if the user equipment is not registered or not registered to the same PLMN through other access; (6) entering the PLMN-SEARCH state; (7) entering the LIMITED-SERVIC state. E state; (8) deem the PLMN prohibited and store the PLMN's identity in a new prohibited list; (9) disable the PLMN's N1 mode capability for non-satellite access and start a timer to enable the N1 mode capability for non-satellite access in the following situations: (a) the timer expires, or (b) the USIM is removed, or (c) the user equipment is powered on or off; (10) if the user equipment is configured to use the T3245 timer, start the T3245 timer; (11) perform the PLMN selection procedure; (12) maintain a new non-integrity protection counter as a PLMN-specific attempt counter for non-satellite access; (13) if the rejection message has been successfully integrity checked by the non-access stratum (NAS), Set the PLMN-specific attempt counter for non-satellite access of the PLMN to the maximum value for the user equipment; (14) Start the T3540 timer to release the NAS signaling connection; (15) Process the EMM parameters EMM status or EPS update status or 4G-GUTI or last access registration TAI or TAI list or eKSI or EMM attachment attempt counter or tracking area update attempt counter, similar to 5GMM with the same reason value; (16) Clear the new prohibited PLMN list when the T3245 timer expires; (17) Remove the selected PLMN from the new prohibited list when the user equipment registers on a non-satellite cell on the selected PLMN; (18) When the new rejection reason When received as non-integrity protection, start the T3247 timer; (19) if the rejection message has been checked for non-integrity by the NAS, increment the PLMN-specific attempt counter for non-satellite access of the PLMN to the maximum value implemented by the user equipment; (20) for each new counter whose value is greater than zero and less than the maximum value implemented by the user equipment, remove the corresponding PLMN from the new prohibited PLMN list when the T3247 timer expires, or when the user equipment is shut down, or when the USIM is removed; (21) if stored, delete the PLMN identified by the list in the refresh command from the new prohibited PLMN list, and enable the N1 mode capability for non-satellite access of the PLMN, if it has been disabled.(22) If stored, remove the PLMN identified by the preferred PLMN / access technology combination list provided in the Roaming Guide (SOR) from the new prohibited PLMN list and enable the PLMN's N1 mode non-satellite access capability if disabled; (23) If stored, ignore the contents of the new prohibited PLMN list and enable the PLMN's N1 mode non-satellite access capability if disabled when the user manually selects a PLMN for registration.

[0046] In some implementations, in response to a new rejection reason being a non-satellite access-specific rejection reason for subscription restrictions, process 400 may involve processor 212 performing at least one of the following operations: (1) setting the 5GS update state to 5U3 roaming not allowed; (2) deleting the last accessed Registration Tracking Area Identifier (TAI); (3) deleting the TAI list; (4) deleting the 5G Globally Unique Temporary Identifier (5G-GUTI) if the user equipment (UE) is not registered or not registered to the same public terrestrial mobile network (PLMN) through other access; (5) deleting the ngKSI if the user equipment (UE) is not registered or not registered to the same public terrestrial mobile network (PLMN) through other access; (6) entering the PLMN-SEARCH state; (7) entering the LIMITED-SERVICE state; (8) disabling the N1 mode capability for non-satellite access; (9) starting a timer for disabling and enabling the N1 mode capability for non-satellite access for the public terrestrial mobile network (PLMN) if: (a) the timer expires, or (b) Remove the Universal Subscriber Identity Module (USIM), or (c) switch the on / off state of the User Equipment (UE); (10) if the User Equipment (UE) is configured to use the T3245 timer, start the T3245 timer; (11) perform the Public Land Mobile Network (PLMN) selection procedure; (12) maintain a new non-integrity protection counter; (13) if the rejection message has successfully passed the integrity check through the Non-Access Stratum (NAS), set the new counter to the specific maximum value achieved by the User Equipment (UE); (14) start the T3540 timer to release the NAS signaling connection; (15) process the Evolved Packet System (EPS) Mobility Management (EMM) parameters EMM state or EPS update state or 4G-GUTI or Last Accessed Register Tracking Area Identifier (TAI) or TAI list or eKSI or EMM Attachment Attempt Counter or Tracking Area Update Attempt Counter, similar to 5GMM with the same cause value; (16) When the T3245 timer expires, clear the new list of prohibited Public Land Mobile Networks (PLMNs); (17) when a new rejection reason is received for non-integrity protection, start the T3247 timer; (18) if the rejection message is for non-integrity protection, increment the new counter; (19) when the T3247 timer expires, or when the user equipment (UE) is turned off, or when the USIM is removed, set the Subscriber Identity Module (SIM) or USIM to be valid for non-satellite services in the following events: (a) the user equipment (UE) does not maintain a counter for the "SIM / USIM is deemed invalid for non-satellite services" event;Or (b) The User Equipment (UE) maintains a counter for the "SIM / USIM is deemed invalid for non-satellite services" event, and the value of the counter is less than a specific maximum value implemented by the UE.

[0047] Additional notes

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

[0049] Furthermore, regarding the use of almost all plural and / or singular terms in this document, those skilled in the art can appropriately convert plural to singular and / or singular to plural depending on the context and / or application. Various singular / plural permutations are explicitly listed herein for ease of understanding.

[0050] Furthermore, those skilled in the art will understand that terms commonly used herein, particularly in appended claims, such as the body of an appended claim, are generally considered "open" terms. For example, "comprising" should be interpreted as "comprising but not limited to," "having" should be interpreted as "having at least," and "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also understand that if a specific number of claims is explicitly expressed in the claims, then that intention is explicitly expressed in the claims; if no such expression is made, then that intention does not exist. For example, for ease of understanding, the following appended claims may contain the use of the introductory phrases "at least one" and "one or more" to introduce the claims. However, the use of such phrases should not be construed as limiting any particular claim containing such introduced claims to containing only one such claim, even if the same claim contains the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to definite articles used to introduce claims. Furthermore, even when a specific number of claims is explicitly stated, those skilled in the art will recognize that such claims should be interpreted as at least the stated number. For example, simply stating "two claims" without any other modifiers implies at least two claims, or two or more claims. Additionally, when using conventions such as "at least one of A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems where A, B, and C are present simultaneously. Similarly, when using conventions such as "at least one of A, B, or C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one of A, B, or C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems where A, B, and C are present simultaneously. Those skilled in the art will also understand that almost all extractives and / or phrases presenting two or more alternative terms in the specification, claims, or drawings should be understood to include one of the terms, any two terms, or both terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

[0051] As can be seen from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: A network node's processor receives a request from a user equipment (UE) to access the network via a non-satellite access method, where the UE is not permitted to use that non-satellite access; and The processor rejects the request by sending a rejection message with a new rejection reason to the UE. The new reason for rejection includes one or both of the following: Specific to Public Land Mobile Network (PLMN) and instructs the user equipment not to access the PLMN or equivalent via this non-satellite access; as well as This covers all subscription-based PLMNs and instructs the user equipment not to access any network through this non-satellite access.

2. The method of claim 1, wherein the rejection comprises: When the user equipment requests service, it is rejected with this new PLMN-specific rejection reason.

3. The method of claim 1, wherein the rejection comprises: When the network initiates a separation or deregistration procedure, a rejection is made, and a new reason for rejection is indicated, wherein the user equipment has successfully completed registration through the non-satellite access.

4. The method of claim 1, wherein the rejection includes rejecting the user equipment request for service with the new rejection reason, thereby restricting the use of the non-satellite access.

5. A method comprising: A user equipment (UE) processor sends a request to the network to access the network via a non-satellite access, where the UE is not permitted to use that non-satellite access; and The processor receives a rejection message from the network with a new rejection reason. The new reason for rejection includes one or both of the following: Specific to Public Land Mobile Network (PLMN) and instructs the user equipment not to access the PLMN or equivalent via this non-satellite access; as well as This covers all subscription-based PLMNs and instructs the user equipment not to access any network through this non-satellite access.

6. The method of claim 5, wherein, In response to this new rejection reason, which restricts the use of non-satellite access in the PLMN to a new PLMN-specific rejection reason, the action further includes performing at least one of the following: Set the 5th generation system (5GS) update status to 5U3 roaming not allowed; Delete the last accessed Register Tracking Area Identifier (TAI); Delete a TAI from the list; If the user equipment has not registered with other access points or has not registered with the same PLMN, delete a fifth-generation globally unique temporary identifier (5G-GUTI). If the user equipment has not registered through other access points or has not registered to the same PLMN, delete an ngKSI; Entering a PLMN-SEARCH state; Enter a LIMITED-SERVICE state; The PLMN is deemed prohibited, and its identifier is stored in a new prohibited list; Disable the non-satellite access N1 mode capability of the PLMN and start a timer to enable the non-satellite access N1 mode capability of the PLMN under the following conditions: The timer expired, or Remove a Universal User Identification Module (USIM), or Toggle the on or off status of the user's device; If the user equipment is configured to use a T3245 timer, the T3245 timer is started; Perform a PLMN selection process; Maintain a new non-integrity protection counter as a PLMN-specific non-satellite access attempt counter; If the rejection message has been successfully verified for integrity by the Non-Access Stratum (NAS), set the PLMN-specific attempt counter for non-satellite access of the PLMN to a specific maximum value implemented by a user equipment. Start a T3540 timer for NAS signaling connection release; Process Evolved Packet System (EPS) Mobility Management (EMM) parameters: EMM status or EPS update status or a fourth-generation globally unique temporary identifier (4G-GUTI) or a last access registration TAI or TAI list or eKSI or EMM attachment attempt counter or tracking area update attempt counter, similar to fifth-generation mobility management (5GMM) with the same cause value. Clear the list of disabled PLMNs when the T3245 timer expires; When the user equipment registers to the selected PLMN on a non-satellite cell, the selected PLMN is removed from the new prohibited list; When the new rejection reason is non-integrity protection, the T3247 timer is started; If a rejection message has been checked for incompleteness by the NAS, the PLMN-specific attempt counter for non-satellite access of the PLMN will be incremented to a specific maximum value for that user equipment. For each new counter whose value is greater than zero and less than the specific maximum value achieved by the user equipment, the corresponding PLMN is removed from the new list of prohibited PLMNs when the T3247 timer expires, when the user equipment is shut down, or when the USIM is removed. If stored, remove the PLMN identified by the list in the refresh command from the new prohibited PLMN list, and enable the non-satellite access N1 mode capability of the PLMN if the non-satellite access N1 mode capability of the PLMN has been disabled. If stored, remove the PLMN identified by the preferred PLMN / access technology combination list provided in the Roaming Guide (SOR) from the new prohibited PLMN list and enable the PLMN's N1 mode non-satellite access capability if it is disabled; If stored, ignore the contents of the new prohibited PLMN list, and if the non-satellite access N1 mode capability of the PLMN is already disabled, enable the non-satellite access N1 mode capability of the PLMN when the user manually selects the PLMN for registration.

7. The method of claim 5, wherein, In response to this new rejection reason, which is a non-satellite access-specific rejection reason used for subscription restrictions, the action further includes performing at least one of the following: Set the 5th generation system (5GS) update status to 5U3 roaming not allowed; Delete the last accessed Registered Tracking Region Identifier (TAI); Delete a TAI from the list; If the user equipment is not registered or not registered to the same PLMN through other access, delete a fifth-generation globally unique temporary identifier (5G-GUTI); If the user equipment is not registered or has not registered to the same PLMN through other access, delete one ngKSI; Entering a PLMN-SEARCH state; Enter a LIMITED-SERVICE state; Disable non-satellite access 1N1 mode capability; A timer is started for the PLMN to disable and enable the N1 mode capability for non-satellite access in the following circumstances: The timer expired, or Remove a Universal User Identification Module (USIM), or The power on and off of the user equipment; If the user equipment is configured to use the T3245 timer, the T3245 timer is started; Perform a PLMN selection process; Maintain a new non-integrity protection counter; If the rejection message has successfully passed the integrity check through the Non-Access Stratum (NAS), then the new counter is set to a specific maximum value implemented by a user equipment. To release the NAS signaling connection, start a T3540 timer; Process Evolved Packet System (EPS) Mobility Management (EMM) parameters: EMM status or EPS update status or a fourth-generation globally unique temporary identifier (4G-GUTI) or the last accessed registered TAI or TAI list or eKSI or EMM appended attempt counter or tracking area update attempt counter, similar to fifth-generation mobility management (5GMM) with the same cause value. Clear the new list of disabled PLMNs when the T3245 timer expires; When the new rejection reason is non-integrity protection, start a T3247 timer; If the rejection message is non-integrity protected, increment a new counter; The Subscriber Identity Module (SIM) or USIM is set to be valid for non-satellite services on the following events: when the T3247 timer expires, when the user equipment is turned off, or when the USIM is removed: The user equipment does not maintain a counter for "SIM / USIM deemed invalid for non-satellite services" events; or The user equipment (UE) maintains a counter for the "SIM / USIM is deemed invalid for non-satellite services" event, and the value of the counter is less than a specific maximum value implemented by the user equipment (UE).

8. An apparatus that can be implemented in a user equipment, comprising: A transceiver configured for wireless communication; as well as A processor coupled to a transceiver is configured to perform operations including: The transceiver sends a request to the network to access the network via non-satellite access, while the user equipment (UE) is not permitted to use non-satellite access; and Receive a rejection message with a new rejection reason from the network via a transceiver. The new reason for rejection includes one or both of the following: Specific to Public Land Mobile Networks (PLMNs) and instructing user equipment not to access the PLMN or equivalent via non-satellite access; as well as Cover all subscription-based PLMNs and instruct user equipment not to access any network via non-satellite access.

9. The device as claimed in claim 8, wherein, When the new rejection reason is a new PLMN-specific rejection reason that restricts the use of non-satellite access in the PLMN, the processor is further configured to perform at least one of the following operations: Set the 5GS update status to 5U3 roaming not allowed; Delete the last accessed Register Tracking Area Identifier (TAI); Delete TAI from the list; If the user equipment is not registered or not registered to the same PLMN through other access, delete a fifth-generation globally unique temporary identifier (5G-GUTI); Delete ngKSI if the user equipment is not registered or has not registered to the same PLMN through other access methods; Enter PLMN-SEARCH state; Enter LIMITED-SERVICE status; Treat PLMNs as prohibited and store their identities in a new prohibited list; Disable the PLMN's non-satellite access N1 mode capability and start the timer to enable the non-satellite access N1 mode capability under the following conditions: The timer expired, or Remove the Universal User Identity Module (USIM), or The power on and off of the user equipment; Start the T3245 timer when the user equipment is configured to use the T3245 timer. Perform the PLMN selection process; Maintain a new non-integrity protection counter as a PLMN-specific attempt counter for non-satellite access; If the rejection message has been successfully verified for integrity by the Non-Access Stratum (NAS), set the PLMN-specific attempt counter for non-satellite access of the PLMN to a specific maximum value for the user equipment. Start the T3540 timer to release the NAS signaling connection; Processing Evolved Packet System (EPS) Mobility Management (EMM) parameters: EMM status, EPS update status, or 4G-GUTI (4th Generation Globally Unique Temporary Identifier), or last accessed registered TAI or TAI list, or eKSI, or EMM attachment attempt counter or tracking area update attempt counter, similar to 5GMM with the same cause value. Clear the list of disabled PLMNs when the T3245 timer expires; When a user equipment registers on a non-satellite cell on a selected PLMN, the selected PLMN is removed from the new prohibited list; When the new rejection reason is received as non-integrity protection, start the T3247 timer; If the rejection message has been checked for incompleteness by the NAS, the PLMN-specific attempt counter for non-satellite access of the PLMN will be incremented to a specific maximum value implemented by the user equipment. For each new counter whose value is greater than zero and less than a user equipment that achieves a specific maximum value, the corresponding PLMN is removed from the new list of prohibited PLMNs when the T3247 timer expires, when the user equipment is turned off, or when the USIM is removed. If stored, remove the PLMN identified by the list in the refresh command from the new list of prohibited PLMNs, and enable the PLMN's N1 mode capability for non-satellite access if it is disabled; If stored, remove the PLMN identified by the preferred PLMN / access technology combination list provided in the Roaming Guide (SOR) from the new list of prohibited PLMNs, and enable the PLMN's N1 mode non-satellite access capability if disabled; If stored, ignore the contents of the new prohibited PLMN list and enable the PLMN's non-satellite access N1 mode capability when the user manually selects a PLMN for registration, if it is disabled.

10. The device as claimed in claim 8, wherein, When the new rejection reason is a non-satellite access-specific rejection reason used for a subscription restriction, the processor is further configured to perform at least one of the following operations: Set the 5GS update status to 5U3 roaming not allowed; Delete the last accessed Registered Tracking Region Identifier (TAI); Delete a TAI from the list; If the user equipment is not registered through other access or not registered to the same public terrestrial mobile network (PLMN), delete the fifth-generation globally unique temporary identifier (5G-GUTI); Delete ngKSI if the user equipment has not registered through other access points or has not registered to the same PLMN; Enter PLMN-SEARCH state; Enter LIMITED-SERVICE status; Disable the N1 mode capability for non-satellite access; In the following situations, a disable and enable timer for the PLMN will be started: The timer expired, or Remove a Universal User Identification Module (USIM), or The power on and off of the user equipment; If the user equipment is configured to use the T3245 timer, start the T3245 timer; Execute the PLMN selection procedure; Maintain a new non-integrity protection counter; If the rejection message has been successfully integrity checked by the Non-Access Stratum (NAS), then the new counter is set to the maximum value that the user equipment implements. Release the start timer for the T3540 for NAS signaling connection; Process Evolved Packet System (EPS) Mobility Management (EMM) parameters: EMM status or EPS update status or 4G-GUTI or last accessed registered TAI or TAI list or eKSI or EMM appended attempt counter or tracking area update attempt counter, similar to 5GMM with the same cause value. Clear the list of disabled PLMNs when the T3245 timer expires; When the new rejection reason is received as non-integrity protection, start the T3247 timer; If the rejection message is non-integrity protected, increment the counter. When the T3247 timer expires, the user equipment is turned off, or the USIM is removed, a Subscriber Identity Module (SIM) or a USIM will be set to be valid for non-satellite services under the following conditions: The user equipment does not maintain a counter for an event where "SIM / USIM is deemed invalid for non-satellite services"; or The user equipment maintains a counter for the "SIM / USIM is deemed invalid for non-satellite services" event, and the value of this counter is less than a specific maximum value implemented by the user equipment.

Images