METHOD AND APPARATUS FOR T3502 TREATMENT OF INTEGRATION SERVICES IN WIRELESS COMMUNICATIONS
Patent Information
- Application Number
- BR112025021546
- Authority / Receiving Office
- BR · BR
- Patent Type
- Applications
- Publication Date
- 2026-09-08
Smart Images

Figure 00000000_0000_ABST
Description
1 / 20 METHOD AND APPARATUS FOR T3502 TREATMENT OF INTEGRATION SERVICES IN WIRELESS COMMUNICATIONS CROSS-REFERENCE TO RELATED PATENT APPLICATION(S)
[0001] This disclosure is part of a non-provisional application claiming the benefit of priority of Indian Patent Application No. 202321033076, filed on May 10, 2023, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD
[0002] This disclosure relates generally to mobile communications and, more particularly, to techniques for handling T3502 timer services for integration in wireless communications. BACKGROUND
[0003] According to the current specification of the 3rd Generation Partnership Project (3GPP), integration services on a standalone non-public network (SNPN) allow a mobile station (MS) to access an SNPN indicating that integration is permitted, using standard user equipment (UE) credentials for primary authentication so that the MS is configured with one or more entries from the subscriber data list. When an initial registration or mobility registration update procedure for integration services fails due to an abnormal situation, such as timer T3510 expiration, lower layer failure, or similar, while the UE registration attempt counter reaches 5, the UE must start its timer T3502.For example, when a UE is performing an initial registration for integration services in an SNPN, or when the UE is registered for integration services in the SNPN and is performing a mobility registration update procedure in the SNPN, when the initial registration or the mobility registration update procedure for integration services fails due to a... Petition 870250101166, dated 05 / 11 / 2025, page 9 / 32 2 / 20 An abnormal situation occurs when the UE registration attempt counter reaches 5. The UE may enter the 5GMMDEREGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.PLMN-SEARCH state and may also perform an SNPN selection or an SNPN selection for integration services. Additionally, the UE must start its T3502 timer.
[0004] If the UE changes its state to PLMN-SEARCH, it may camp on the same SNPN where the T3502 timer is running or on a different SNPN. If the UE camps on a different SNPN, the T3502 will be interrupted. If the UE's initial registration or mobility registration update procedure fails due to abnormal situations such as T3510 expiration, lower layer failure, or other reason, while the UE's registration attempt counter reaches 5 on the different SNPN, the UE will change its state to PLMN-SEARCH and may camp on the same SNPN where the T3502 is running or on a different SNPN, resulting in the UE being stuck in a loop from which the UE cannot escape. Currently, there is no mechanism to avoid this loop. Therefore, there is a need for a solution for handling the T3502 timer for integration services in wireless communications. SUMMARY
[0005] The following summary is merely illustrative and is not intended to be limiting in any way. That is, the following summary is provided to present concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described in this document. Selected implementations are described in more detail below in the detailed description. Therefore, the following summary is not intended to identify essential features of the claimed object, nor is it intended to be used to determine the scope of the claimed object.
[0006] One objective of this disclosure is to propose solutions or schemes that address the problem(s) described in this document(s). More specifically, it is believed that several Petition 870250101166, dated 05 / 11 / 2025, page 10 / 32 3 / 20 of the schemes proposed in this disclosure provide solutions relating to the handling of the T3502 timer for integration services in wireless communications.
[0007] In one aspect, a method may include a UE, responsive to an existing predefined condition, performing operations that include: (1) disabling a specific capability for network access; (2) storing an identity of a public terrestrial mobile network (PLMN) or standalone non-public network (SNPN) where the specific capability for network access has been disabled; and (3) starting a timer with respect to re-enabling the specific capability for network access. The method may also involve the UE removing the PLMN or SNPN identity from the stored identities of PLMNs or SNPNs where the specific capability for network access has been disabled upon timer expiration.
[0008] In another aspect, a method may include a UE, responsive to an existing predefined condition, performing operations that include: (1) disabling a specific capability for network access; (2) storing an identity of a public terrestrial mobile network (PLMN) or standalone non-public network (SNPN) where the specific capability for network access has been disabled; and (3) initiating a timer with respect to re-enabling the specific capability for network access. The method may also involve the UE triggering a PLMN selection, an SNPN selection, or an SNPN selection for integration services. The method may further involve the UE keeping the specific capability disabled while performing the PLMN selection, the SNPN selection, or the SNPN selection for integration services.
[0009] It is worth noting that, although the description presented in this document may be in the context of certain radio access technologies, networks and network topologies, such as 5th Generation (5G), New Radio (NR) or Beyond 5th Generation (B5G) mobile communications, the concepts, proposed schemes and any Petition 870250101166, dated 05 / 11 / 2025, p. 11 / 32 4 / 20 variations / derivatives thereof can be implemented in, for, and by other types of radio access technologies, networks, and network topologies, such as, for example and without limitation, Long Term Evolution (LTE), Advanced LTE, Advanced LTE Pro, Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), vehicle-to-everything (V2X) communications, and non-terrestrial networks (NTN). Therefore, the scope of this disclosure is not limited to the examples described in this document. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The accompanying drawings are included to provide a better understanding of the disclosure and are incorporated into and form part of this disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It should be understood that the drawings are not necessarily to scale, as some components may be shown disproportionately to the size of the actual implementation in order to clearly illustrate the concept of this disclosure.
[0011] Figure 1 is a diagram of an example network environment in which various solutions and schemes according to the present disclosure can be implemented.
[0012] Figure 2 is a block diagram of an example communication system according to an implementation of the present disclosure.
[0013] Figure 3 is a flowchart of a first example process according to an implementation of the present disclosure.
[0014] Figure 4 is a flowchart of a second example process according to an implementation of the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS
[0015] Detailed embodiments and implementations of the matters claimed are disclosed in this document. However, it should be understood that the embodiments and implementations disclosed are Petition 870250101166, dated 05 / 11 / 2025, page 12 / 32 5 / 20 are merely illustrative of the claimed subjects, which may be incorporated in various forms. This disclosure may, however, be incorporated in various forms and should not be interpreted as limited to the exemplary embodiments and implementations presented herein. Instead, these exemplary embodiments and implementations are provided so that the description of this disclosure is complete and comprehensive, fully conveying the scope of this disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the embodiments and implementations presented. Overview
[0016] The implementations according to this disclosure refer to various techniques, methods, schemes and / or solutions relevant to the handling of T3502 timer integration services in wireless communications. According to this disclosure, various possible solutions can be implemented separately or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one or another combination.
[0017] Figure 1 illustrates an example of a 100 network environment in which various solutions and schemes, according to this disclosure, can be implemented. Figures 2 to 4 illustrate examples of the implementation of various schemes proposed in the 100 network environment, according to this disclosure. The following description of the various proposed schemes is provided with reference to Figures 1 to 4.
[0018] Referring to Figure 1, network environment 100 may involve a UE 110 in wireless communication with a wireless network 120 (e.g., a 5G NR mobile network) as part of a communication network. The wireless network 120 may include a first SNPN. Petition 870250101166, dated 05 / 11 / 2025, p. 13 / 32 6 / 20 and a second SNPN (referred to interchangeably in this document as SNPN A and SNPN B, respectively). The UE 110 may initially communicate wirelessly with the wireless network 120 via a base station or network node 125 (e.g., an eNB, gNB, or transmit / receive point (TRP)). In the network environment 100, the UE 110 and the wireless network 120 may implement various schemes relating to the T3502 timer handling of integration services in wireless communications, in accordance with this disclosure, as described in this document.
[0019] As used in this document, a lower layer may refer to a layer in the 5th Generation Mobility Management (5GMM) protocol stack that is below the RRC layer, such as a packet data convergence protocol (PDCP) layer, a radio control link (RLC) layer, a medium access control (MAC) layer, a physical layer (PHY), and so on. It is worth noting that unequal modulation (UEQM) in the various proposed schemes may be in the frequency domain and / or the spatial domain. It is also worth noting that, although the various proposed schemes may be described individually or separately below, in real implementations, some or all of the proposed schemes may be used or implemented together. Of course, each of the proposed schemes may be used or implemented individually or separately.
[0020] When UE 110 performs an initial registration for integration services on SNPN A and the registration fails due to an abnormal situation (e.g., T3510 expiration, lower layer failure, or other reason) and the UE 110 registration attempt counter reaches 5 on SNPN A, a first T3502 (if running) may be interrupted by UE 110 after an SNPN change. UE 110 may start a second T3502 and perform an SNPN selection procedure for integration services. When UE 110 encounters SNPN B and initiates an initial registration Petition 870250101166, dated 05 / 11 / 2025, page 14 / 32 7 / 20 for integration services on SNPN B, the second T3502 (if running) may be interrupted after an SNPN change. If the initial registration for integration services fails due to an abnormal situation (e.g., T3510 expiration, lower layer failure, or other reason), while the UE 110 registration attempt counter reaches 5 on SNPN B, UE 110 may initiate a third T3502 and perform another SNPN selection procedure for integration services. The aforementioned operations may be repeated in a loop, and UE 110 may become stuck in the registration loop, thus overloading the signaling on wireless network 120, since T3502 is applicable to the selected SNPN.
[0021] According to a proposed scheme, as per this disclosure, the UE 110 may disable an N1 mode capability for an SNPN in which the UE 110 is currently hosted on a 3GPP access if an initial registration or mobility registration update procedure for integration services fails due to an abnormal situation (e.g., T3510 expiration, lower layer failure, or other reason) and the UE 110 registration attempt counter reaches 5. The UE 110 may memorize (e.g., store in a list) the identities of one or more SNPNs in which the N1 mode capability for 3GPP access has been / is disabled. As defined in 3GPP, N1 mode refers to a mode in which a UE (e.g., UE 110) is allowed access to a 5G core network via a 5G radio access network (RAN).
[0022] As an implementation option, the UE 110 can start a timer to enable the N1 mode capability for 3GPP access. That is, at the end of this timer, the UE 110 can enable the N1 mode capability for 3GPP access. It may be recommended that the value of this timer to re-enable the N1 mode capability be the same as the value of T3502. If the value of T3502 is indicated as zero or disabled by the network Petition 870250101166, dated 05 / 11 / 2025, page 15 / 32 8 / 20 wireless 120, a non-zero implementation-specific value can be used by UE 110 for such a timer to re-enable the N1 mode capability.
[0023] In another proposed scheme, according to this disclosure, when an initial registration or mobility registration update procedure for integration services fails due to an abnormal situation (e.g., T3510 expiration, lower layer failure, or other reason), while the UE 110 registration attempt counter reaches 5 for a first SNPN (e.g., SNPN A) plus one or more conditions from a plurality of conditions, UE 110 may keep a first T3502 running and optionally associate the first T3502 with the first SNPN. Optionally, UE 110 may not consider the first SNPN while the first T3502 is running in an SNPN selection procedure for integration services.The plurality of conditions may include, for example, but not limited to: (1) UE 110 carrying out an SNPN selection mode for integration services; (2) UE 110 initiating the first T3502; (3) UE 110 carrying out the SNPN selection procedure for integration services; (4) UE 110 selecting a second SNPN (e.g., SNPN B) for integration services; and (5) UE 110 initiating a registration procedure to register with the second SNPN.
[0024] In view of the foregoing, certain features of the various schemes proposed in accordance with this disclosure may be summarized below.
[0025] In one aspect, UE 110 may, in response to the existence of a predefined condition, perform certain operations, including: (1) disabling a specific capability for network access; (2) storing in a list the identity of a public terrestrial mobile network (PLMN) or SNPN, with the list containing the identities of PLMNs or SNPNs where the specific capability for network access has been disabled; and (3) initiating a Petition 870250101166, dated 05 / 11 / 2025, page 16 / 32 9 / 20 timer to re-enable specific network access capability. Additionally, UE 110 can remove the PLMN or SNPN identity from the list upon timer expiration.
[0026] In some implementations, the predefined condition may include a failure of a registration procedure for an initial registration for integration services while a UE registration attempt counter reaches 5.
[0027] In some implementations, the predefined condition may include a failure of a mobility registration update procedure for integration services while a UE registration attempt counter reaches 5.
[0028] In some implementations, the specific capability may include an N1 mode capability for 3GPP access.
[0029] In another aspect, the UE 110 may, in response to the existence of a predefined condition, perform certain operations, including: (1) disabling a specific capability for network access; (2) storing in a list the identity of a PLMN or SNPN, with the list containing the identities of the PLMNs or SNPNs where the specific capability for network access has been disabled; and (3) starting a timer to re-enable the specific capability for network access. The UE 110 may trigger a PLMN selection, an SNPN selection, or an SNPN selection for integration services. Furthermore, the UE 110 may keep the specific capability disabled while performing PLMN selection, SNPN selection, or SNPN selection for integration services.
[0030] In some implementations, on trigger, UE 110 may enter a 5GMM-DEREGISTERED.PLMN-SEARCH or 5GMMREGISTERED.PLMN-SEARCH state to trigger PLMN selection, SNPN selection, or SNPN selection for integration services.
[0031] In some implementations, the predefined condition may include a failure of a registration procedure for an initial registration for integration services while a counter of Petition 870250101166, dated 05 / 11 / 2025, page 17 / 32 10 / 20 attempts to register with the EU reach 5.
[0032] In some implementations, the predefined condition may include a failure of a mobility registration update procedure for integration services while a UE registration attempt counter reaches 5.
[0033] In some implementations, the specific capability may include an N1 mode capability for 3GPP access. Illustrative implementations
[0034] Figure 2 illustrates an example communication system 200, with at least one example device 210 and one example device 220, according to an implementation of the present disclosure. Each of device 210 and device 220 can perform various functions to implement schemes, techniques, processes and methods described in this document, relating to the handling of T3502 timer integration services in wireless communications, including the various schemes described above in relation to the various proposed designs, concepts, schemes, systems and methods, including the network environment 100, as well as the processes described below.
[0035] Each of device 210 and device 220 may be part of an electronic device, which may be a network device or an UE (e.g., UE 110), such as a portable or mobile device, a wearable device, a vehicle device or vehicle, a wireless communication device, or a computing device. For example, each of device 210 and device 220 may be implemented in a smartphone, a smartwatch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or computing equipment such as a tablet computer, a laptop computer, or a notebook computer. Each of device 210 and device 220 may also be part of a machine-type device, which may be an IoT device, such as a stationary or fixed device, a residential device, a Petition 870250101166, dated 05 / 11 / 2025, page 18 / 32 11 / 20 roadside unit (RSU), a wired communication device, or a computing device. For example, each of device 210 and device 220 can be implemented in a smart thermostat, a smart refrigerator, a smart lock, a wireless speaker, or a home control hub. When implemented in or as a network device, devices 210 and / or 220 can be implemented in an eNodeB on an LTE, LTE Advanced, or LTE Advanced Pro network, or in a gNB or TRP on a 5G network, an NR network, or an IoT network.
[0036] In some implementations, each of device 210 and device 220 may be implemented in the form of one or more integrated circuit (IC) chips, such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex instruction set computing (CISC) processors, or one or more reduced instruction set computing (RISC) processors. In the various schemes described above, each of device 210 and device 220 may be implemented in either a network device or a UE. Each of device 210 and device 220 may include at least some of the components shown in Figure 2, such as a processor 212 and a processor 222, respectively, for example.Each of apparatus 210 and apparatus 220 may also include one or more other components not relevant to the proposed scheme of this disclosure (for example, internal power supply, display device and / or user interface device) and, therefore, such components of apparatus 210 and 220 are not shown in Figure 2 nor described below in the interest of simplicity and brevity.
[0037] In one respect, each of processor 212 and processor 222 can be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term “a processor” is used in this document to refer to Petition 870250101166, dated 05 / 11 / 2025, page 19 / 32 12 / 20 refers to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations, according to this disclosure. In another aspect, each of processor 212 and processor 222 may be implemented in the form of hardware (and optionally firmware) with electronic components including, for example and without limitation, 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 varactors that are configured and arranged to achieve specific uses, according to this disclosure.In other words, in at least some implementations, each of processor 212 and processor 222 is a special-purpose machine specifically designed, organized, and configured to perform specific tasks, including those pertaining to the T3502 timer handling of integration services in wireless communications, according to various implementations of this disclosure.
[0038] In some implementations, device 210 may also include a transceiver 216 coupled to processor 212. Transceiver 216 may be capable of wirelessly transmitting and receiving data. In some implementations, transceiver 216 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs). In some implementations, transceiver 216 may be equipped with a plurality of 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 multi-input multiple-output (MIMO) wireless communications. In some implementations, device 220 may also include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of transmitting and receiving data. Petition 870250101166, dated 05 / 11 / 2025, p. 20 / 32 13 / 20 wirelessly. In some implementations, the 226 transceiver may be able to communicate wirelessly with different types of UEs / wireless networks from different RATs. In some implementations, the 226 transceiver may be equipped with a plurality of antenna ports (not shown), such as four antenna ports. That is, the 226 transceiver may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.
[0039] In some implementations, device 210 may also include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein. In some implementations, device 220 may also include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Each of memory 214 and memory 224 may include a type of random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and / or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory 214 and memory 224 may include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM).Alternatively, or additionally, each of memory 214 and memory 224 may include a type of non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.
[0040] Each of device 210 and device 220 may be a communication entity capable of communicating with each other using various schemes proposed in accordance with this disclosure. For illustrative purposes and without limitation, a description of the capabilities of device 210, as a UE (e.g., UE 110), and of device 220, as a network node (e.g., network node 125) of a network (e.g., wireless network 120 as a network) Petition 870250101166, dated 05 / 11 / 2025, p. 21 / 32 14 / 20 mobile 5G / NR), is provided below in the context of example processes 300 and 400. Illustrative Processes
[0041] Figure 3 illustrates an example process 300, according to an implementation of the present disclosure. Process 300 may represent an aspect of the implementation of several proposed designs, concepts, schemes, systems, and methods described above, in whole or in part, including those belonging to those described above. More specifically, process 300 may represent an aspect of the proposed concepts and schemes relating to the handling of the T3502 timer for integration services in wireless communications. Process 300 may include one or more operations, actions, or functions, as illustrated by one or more of blocks 310 and 320. Although illustrated as discrete blocks, several blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 300 may be performed in the order shown in Figure 3 or, alternatively, in a different order.Furthermore, one or more blocks / sub-blocks of process 300 can be executed iteratively. Process 300 can be implemented by or on device 210 and device 220, as well as any variations thereof. For illustrative purposes only and without limiting the scope, process 300 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity, such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120). Process 300 can start on block 310.
[0042] In 310, process 300 may involve processor 212 of device 210, in response to an existing predefined condition, performing operations that include: (1) disabling a specific capability for network access; (2) storing (for example, in Petition 870250101166, dated 05 / 11 / 2025, page 22 / 32 15 / 20 memory 214) an identity of a PLMN or SNPN, in which the specific capability for network access has been disabled; and (3) start a timer with respect to re-enabling the specific capability for network access. Process 300 can proceed from 310 to 320.
[0043] In 320, process 300 may involve processor 212 removing the PLMN or SNPN identity from the stored identities of PLMNs or SNPNs where the specific capability for network access has been disabled after the timer expires.
[0044] In some implementations, the predefined condition may include a failure of a registration procedure for an initial registration for integration services while a UE registration attempt counter reaches 5.
[0045] In some implementations, the predefined condition may include a failure of a mobility registration update procedure for integration services while a UE registration attempt counter reaches 5.
[0046] In some implementations, the specific capability may include an N1 mode capability for 3GPP access.
[0047] Figure 4 illustrates an example 400 process, according to an implementation of the present disclosure. The 400 process may represent an aspect of the implementation of several proposed designs, concepts, schemes, systems, and methods described above, in whole or in part, including those belonging to those described above. More specifically, the 400 process may represent an aspect of the proposed concepts and schemes relating to the handling of the T3502 timer for integration services in wireless communications. The 400 process may include one or more operations, actions, or functions, as illustrated by one or more of the 410, 420, and 430 blocks. Although illustrated as discrete blocks, several blocks of the 400 process may be divided into additional blocks, combined into fewer Petition 870250101166, dated 05 / 11 / 2025, page 23 / 32 16 / 20 blocks or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 400 can be executed in the order shown in Figure 4 or, alternatively, in a different order. Additionally, one or more blocks / sub-blocks of process 400 can be executed iteratively. Process 400 can be implemented by or on device 210 and device 220, as well as any variations thereof. For illustrative purposes only and without limiting the scope, process 400 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity, such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120). Process 400 can start in block 410.
[0048] In 410, process 400 may involve processor 212 of device 210, in response to an existing predefined condition, performing operations that include: (1) disabling a specific capability for network access; (2) storing (for example, in memory 214) an identity of a PLMN or SNPN, where the specific capability for network access has been disabled; and (3) starting a timer with respect to re-enabling the specific capability for network access. Process 400 may proceed from 410 to 420.
[0049] In 420, process 400 may involve processor 212 firing a PLMN selection, an SNPN selection, or an SNPN selection for integration services. Process 400 may proceed from 420 to 430.
[0050] In 430, process 400 may involve processor 212 keeping the specific capability disabled when performing PLMN selection, SNPN selection, or SNPN selection for integration services.
[0051] In some implementations, upon firing, process 400 may involve processor 212 entering a PLMNSEARCH state or an ATTEMPTING-REGISTRATION state to fire the Petition 870250101166, dated 05 / 11 / 2025, page 24 / 32 17 / 20 selection of PLMN, selection of SNPN, or selection of SNPN for integration services.
[0052] In some implementations, the predefined condition may include a failure of a registration procedure for an initial registration for integration services while a UE registration attempt counter reaches 5.
[0053] In some implementations, the predefined condition may include a failure of a mobility registration update procedure for integration services while a UE registration attempt counter reaches 5.
[0054] In some implementations, the specific capability may include an N1 mode capability for 3GPP access. Additional notes
[0055] The subject described in this document sometimes illustrates different components contained within, or connected to, different other components. It should be understood that such represented architectures are merely examples and that, in fact, many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively associated in such a way that the desired functionality is achieved. Therefore, any two components combined in this document to achieve a specific functionality can be seen as associated with each other in such a way that the desired functionality is achieved, regardless of architectures or intermediate components.Similarly, any two components thus associated can also be seen as operationally connected or operationally coupled to each other to achieve the desired functionality, and any two components capable of being thus associated can also be seen as operationally coupleable to each other to achieve the desired functionality. Specific examples of operationally coupleable components include... Petition 870250101166, dated 05 / 11 / 2025, page 25 / 32 18 / 20 but are not limited to physically attachable and / or physically interactive components and / or wireless interactive components and / or wireless interactive components and / or logically interactive components.
[0056] Furthermore, with regard to the use of substantially any plural and / or singular terms described in this document, those skilled in the art may translate from plural to singular and / or from singular to plural as appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth in this document for the sake of clarity.
[0057] Furthermore, it will be understood by those skilled in the art that, in general, the terms used in this document, and especially in the appended claims, for example, the bodies of the appended claims, are generally conceived as open terms, for example, the term including should be interpreted as including, but not limited to, the term having should be interpreted as having at least, the term includes should be interpreted as includes, but not limited to, etc. It will further be understood by those skilled in the art that, if a specific number of an introduced claim recitation is intended, such intention will be explicitly recited in the claim and, in the absence of such recitation, such intention will not be present. For example, as an aid to understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim recitations.However, the use of such phrases should not be interpreted as implying that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any specific claim containing such introduced claim recitation to implementations containing only one of these recitations, even when the same claim includes the phrases. Petition 870250101166, dated 05 / 11 / 2025, p. 26 / 32 19 / 20 introductory 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 meaning at least one or one or more; the same applies to the use of definite articles used to introduce claim recitations. Furthermore, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the subject will recognize that such recitation should be interpreted as meaning at least the number recited, for example, the mere recitation of two recitations, without other modifiers, means at least two recitations, or two or more recitations. Additionally, in cases where a convention analogous to “at least one of A, B, and C, etc.” is used, the interpretation should be that the same applies to the use of definite articles used to introduce claim recitations.In general, the construction "at least one of A, B, or C" is intended to be understood by someone skilled in the technique; for example, "a system having at least one of A, B, and C" would include, but not be limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In cases where a convention analogous to "at least one of A, B, or C, etc." is used, the construction is generally intended to be understood by someone skilled in the technique; for example, "a system having at least one of A, B, or C" would include, but not be limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.It will also be understood by those skilled in the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood as encompassing the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood as including the possibilities of “A” or “B” or “A and B”.
[0058] In view of the above, it is clear that several Petition 870250101166, dated 05 / 11 / 2025, p. 27 / 32 20 / 20 implementations of this disclosure have been described in this document for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Consequently, the various implementations disclosed in this document are not intended to be limiting, the true scope and spirit being indicated by the following claims. Petition 870250101166, dated 05 / 11 / 2025, p. 28 / 32
Claims
1 / 4 CLAIMS 1. A method, characterized in that it comprises: performing, by a processor of a user equipment (UE), operations responsive to an existing predefined condition, the operations comprising: disabling a specific capability for network access; storing an identity of a public terrestrial mobile network (PLMN) or a non-public standalone network (SNPN), in which the specific capability for network access has been disabled; and initiating a timer with respect to the reactivation of the specific capability for network access; and removing, by the processor, the identity of the PLMN or SNPN from the stored identities of PLMNs or SNPNs in which the specific capability for network access has been disabled upon expiration of the timer.
2. Method, according to claim 1, characterized in that the predefined condition comprises a failure of a registration procedure for an initial registration for integration services while a UE registration attempt counter reaches 5.
3. Method, according to claim 1, characterized in that the predefined condition comprises a failure of a mobility registration update procedure for integration services while a UE registration attempt counter reaches 5.
4. Method, according to claim 1, characterized in that the specific capacity comprises an N1 mode capacity for a 3rd Generation Partnership Project (3GPP) access.
5. Method, characterized by the fact that it comprises: performing, by a processor of a user equipment (UE), operations responsive to an existing predefined condition, the operations comprising: Petition 870250090725, dated 06 / 10 / 2025, page 14 / 18 2 / 4 disabling a specific capability for network access; storing an identity of a public terrestrial mobile network (PLMN) or a non-public standalone network (SNPN), in which the specific capability for network access has been disabled; and initiating a timer with respect to the reactivation of the specific capability for network access; triggering, by the processor, a PLMN selection, an SNPN selection or an SNPN selection for integration services; and maintaining, by the processor, the specific capability disabled when performing the PLMN selection, the SNPN selection or the SNPN selection for integration services.
6. Method, according to claim 5, characterized in that the triggering comprises entering a PLMN-SEARCH state or an ATTEMPTING-REGISTRATION state to trigger PLMN selection, SNPN selection, or SNPN selection for integration services.
7. Method, according to claim 5, characterized in that the predefined condition comprises a failure of a registration procedure for an initial registration for integration services while a UE registration attempt counter reaches 5.
8. Method, according to claim 5, characterized in that the predefined condition comprises a failure of a mobility registration update procedure for integration services while a UE registration attempt counter reaches 5.
9. Method, according to claim 5, characterized in that the specific capacity comprises an N1 mode capacity for a 3rd Generation Partnership Project (3GPP) access.
10. Device deployable in a user equipment (UE), characterized in that it comprises: a transceiver configured to communicate wirelessly; and a processor coupled to the transceiver and configured to perform operations comprising: performing, through the transceiver, operations responsive to a predefined existing condition, the operations comprising: disabling a specific capability for network access; storing an identity of a public terrestrial mobile network (PLMN) or a non-public standalone network (SNPN), in which the specific capability for network access has been disabled; and initiating a timer with respect to the reactivation of the specific capability for network access.
11. Device according to claim 10, characterized in that the processor is further configured to perform operations comprising: removing the identity of the PLMN or SNPN from the stored identities of PLMNs or SNPNs in which the specific capability for network access has been disabled upon timer expiration.
12. Device according to claim 10, characterized in that the processor is further configured to perform operations comprising: triggering a PLMN selection, an SNPN selection or an SNPN selection for integration services; and keeping the specific network access capability disabled when performing the PLMN selection, the SNPN selection or the SNPN selection for integration services.
13. Device according to claim 12, characterized in that the drive comprises entering an ATTEMPTING-REGISTRATION state or a PLMN-SEARCH state to trigger PLMN selection, SNPN selection, or SNPN selection for integration services.
14. Device, according to claim 10, characterized in that the predefined condition comprises a failure of Petition 870250090725, dated 06 / 10 / 2025, page 16 / 18 4 / 4 a registration procedure for an initial registration for integration services while a counter of EU registration attempts reaches 5.
15. Device, according to claim 10, characterized in that the predefined condition comprises a failure of a mobility registration update procedure for integration services while a counter of EU registration attempts reaches 5.
16. Device according to claim 10, characterized in that the specific network access capability comprises an N1 mode capability for 3GPP access. Petition 870250090725, dated 06 / 10 / 2025, pp. 17 / 18