Starting non-integrity timer in localized service in mobile communications

Abstract

Technical schemes for starting a non-integrity timer in a localized service in mobile communications are described. In one context, a device (e.g., a user equipment (UE)) receives a rejection message that is not integrity protected and has a particular cause value. In response to the reception, the device starts a timer T3247 from a random value that is uniformly randomly drawn within a range for a localized service in a standalone-public network (SNPN). In another context, the device adds the SNPN to the prohibited SNPN list. Then, if the timer T3245 is not running, the device starts the timer T3245.

Description

[0001] Cross-referencing

[0002] This disclosure claims priority interest in Indian Patent Application No. 202321064280, filed on September 25, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically, to initiating a non-integrity timer in a localized service within mobile communications. Background Technology

[0004] In wireless communications (e.g., mobile communications) under the current Generation Partnership Project (3GPP) specifications, if a User Equipment (UE) receives a Registration Reject message or Service Reject message with Generation Mobility Management (5GMM) cause values ​​#3, #6, #7, #12, #13, #15, #27, #72, #74, or #75 without integrity protection before the network has established a secure exchange of non-access-stratum (NAS) messages for an N1 non-access-stratum signaling connection, the UE should stop timer T3510 or T3517 (if it is running). In addition, the user equipment should start timer T3247 (e.g., according to 3GPP Technical Specification (TS) 24.008) and uniformly randomly select a random value from the following range: 15 to 30 minutes for 5GMM cause value #74; and 30 to 60 minutes for other 5GMM cause values.

[0005] User equipment (UE) starts a T3247 timer, and upon receiving a rejection message for no integrity protection for some reason, the UE can clear the non-integrity attempt counter, remove the standalone non-public network (SNPN) from the blocked list, or set each item in the "Subscriber Data List" after a specific duration (e.g., T3247 expires). However, starting T3247 will have no effect if a random value is calculated and T3247 expires after the end of the current localized service validity period, because the UE cannot periodically attempt on the same SNPN after a rejection message for no integrity protection. Therefore, a solution involving starting a non-integrity timer in localized services within mobile communications is necessary. Summary of the Invention

[0006] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further elaborated in the detailed description below. 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.

[0007] The objective of this disclosure is to propose solutions or strategies to address the problems described herein. More specifically, the various solutions proposed in this disclosure are believed to provide solutions regarding the initiation of non-integrity timers in localized services within mobile communications. It is believed that implementations of one or more of the solutions proposed herein can solve or mitigate the aforementioned problems.

[0008] In one aspect, a method may involve a user equipment (UE) receiving a rejection message with no integrity protection and a specific cause value. The method may also involve the UE, upon receiving the message, starting a timer T3247 for a localized service in a standalone non-public network (SNPN) with a random value uniformly drawn from a range.

[0009] In another aspect, one method may involve a user equipment adding a standalone non-public network to a list of prohibited standalone non-public networks. The method may also involve, after such addition, the user equipment starting timer T3245 even if timer T3245 is not running.

[0010] 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 5G / New Radio / Beyond Fifth-Generation (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, 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

[0011] The accompanying drawings are included in this specification to provide a further understanding of the present disclosure and are incorporated into and constitute a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the specification, serve to explain the principles of the present disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concepts of the present disclosure.

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

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

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

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

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

[0017] Overview

[0018] According to the implementation of this disclosure, various techniques, methods, schemes, and / or solutions are involved in initiating a non-integrity timer in a localized service in mobile communications. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in some combination.

[0019] Figure 1 Example network environment 100 is shown, illustrating various solutions and schemes for implementing the contents of this disclosure. Figures 2-4 Examples of implementations of various proposed schemes in network environment 100, based on this disclosure, are shown. The following descriptions of the various proposed schemes are in conjunction with... Figures 1-4 It was carried out.

[0020] See Figure 1 Network environment 100 may involve a user equipment (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 the 5G / NR domain and the 4G / LTE domain. UE 110 may initially communicate wirelessly with wireless network 120 via a base station or network node 125 (e.g., an evolved Node B (eNB), a next-generation Node B (gNB), or a transceiver point (TRP)). In network environment 100, UE 110 and wireless network 120 may implement various schemes related to initiating non-integrity timers in localized services in mobile communications, as described herein, in accordance with this disclosure.

[0021] It is worth noting that although the various proposed schemes may be described individually or separately below, in actual implementation, some or all of the proposed schemes may be used or implemented in combination. 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 layer below the radio resource control (RRC) layer in the 5GMM protocol stack, such as the packet data convergence protocol (PDCP) layer, radio control link (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.

[0022] In the Automatic Standalone Non-Public Network (SNPN) selection procedure, UE 110 may select an SNPN in the following order (if available and permitted). First, if UE 110 supports access to an SNPN that provides localized services, and access to localized services within that SNPN is enabled, UE 110 may use SNPN selection parameters to select an SNPN to access localized services within that SNPN, either based on the selected entry in the "User Data List" or in relation to the selected Public Land Mobile Network (PLMN) subscription. First, UE 110 may consider an SNPN previously selected for each of the following SNPN list entries, and the SNPN to which UE 110 was last registered, provided the entry's validity information is still satisfied. Second, UE 110 may consider the SNPN list, each SNPN broadcasting an indication that access is supported using credential holder credentials, and identified by the SNPN identifier (in priority order) contained in the "Certificate Holder-Controlled Localized Service Priority SNPN List" entry, provided the entry's validity information is satisfied. Third, UE 110 may consider a list of SNPNs, each broadcasting an indication that access is supported using credential holder credentials, and broadcasting a group identifier (ID) for network selection (GIN), which is included in the "List of Localized Service Priority GINs Controlled by Credential Holder" (in order of priority), provided the validity information of the entry is satisfied. If multiple SNPNs broadcast the same GIN, the order in which UE 110 attempts to register on these SNPNs can be determined by the UE implementation.

[0023] According to the first proposed scheme of this disclosure, when UE 110 receives a registration rejection message or service rejection message without integrity protection, and UE 110 starts timer T3247, if SNPN is not selected for the specific access type for receiving the message in accordance with Section 4.9.3.1.1(a0) of 3GPP TS 23.122, or if there is no next valid time period for SNPN, then the time period of T3247 may be randomly selected from the following ranges: (1) for fifth-generation mobility management reason value #74, from 15 minutes to 30 minutes; and / or (2) for other fifth-generation mobility management reason values, from 30 minutes to 60 minutes.

[0024] According to the proposed scheme, if the SNPN is selected for the specific access type receiving the message in accordance with Clause 4.9.3.1.1(a0) of 3GPP TS 23.122, then the time period of T3247 can be randomly selected from the following ranges: (1) for the fifth-generation mobility management reason value #74, from 15 minutes to the end time of the current localized service effective time period minus the current time of UE 110; and / or (2) for the fifth-generation mobility management reason value #75, from 30 minutes to the end time of the current localized service effective time period minus the current time of UE 110; and / or (3) for the period between the start and end time of the next effective time period of the localized service in the SNPN, applicable to the fifth-generation mobility management reason value #74 and / or #75 and / or other fifth-generation mobility management reason values; and / or (4) for the fifth-generation mobility management reason value #74, from 15 minutes to the end time of the current localized service effective time period minus the current time of UE 110. 110 current time point; and / or (5) for other fifth-generation mobility management reason values, from 30 minutes to the end time point of the current localized service valid time period minus the UE 110 current time point; and / or (6) between the UE 110 current time point and the end time point of the current valid time period of the localized service in SNPN, applicable to fifth-generation mobility management reason values ​​#74 and / or #75 and / or other fifth-generation mobility management reasons; and / or (7) between the start time point and the end time point of the current valid time period of the localized service in SNPN, applicable to fifth-generation mobility management reason values ​​#74 and / or #75 and / or other fifth-generation mobility management reasons; and / or (8) between the start time point and the end time point of the next valid time period of the localized service in SNPN, applicable to fifth-generation mobility management reason values ​​#74 and / or #75 and / or other fifth-generation mobility management reasons.

[0025] As an example, before the wireless network 120 has established a secure exchange of NAS messages for the N1 non-access stratum signaling connection, if the user equipment (UE) 110 receives a registration rejection message or service rejection message without integrity protection and with a fifth-generation mobility management value (5GMM) cause value #3, #6, #7, #12, #13, #15, #27, #72, #74, or #75, the UE 110 may stop timer T3510 or T3517 (if it is running). If the standalone non-public network (SNPN) sending the message is selected according to section 4.9.3.1.1 a0) or section 4.9.3.2.1 a0) of 3GPP TS 23.122, and the SNPN has a next valid time period, then UE 110 may, for the localized service in the SNPN, start timer T3247 (e.g., 3GPP TS 24.008) with a uniformly randomly drawn random value from the start time of the next valid time period to one of the following, depending on the circumstances: For 5GMM cause value #74, if the next valid time period exceeds 30 minutes, then the range may be between the start time of the next valid time period of the localized service in the SNPN and 30 minutes after that start time. Alternatively, for 5GMM cause value #74, if the next valid time period does not exceed 30 minutes, then the range may be between the start time of the next valid time period of the localized service in the SNPN and the end time of that next valid time period. For other 5GMM cause values, if the next valid time period exceeds 60 minutes, the range may be between the start time of the next valid time period for the localized service in SNPN and 60 minutes after that start time. Alternatively, for other 5GMM cause values, if the next valid time period does not exceed 60 minutes, the range may be between the start time of the next valid time period for the localized service in SNPN and the end time of that next valid time period. Otherwise, the range may be between the start time of the next valid time period for the localized service in SNPN and: (a) for 5GMM cause value #74, between 15 minutes and 30 minutes; or (b) for other 5GMM cause values, between 30 minutes and 60 minutes.

[0026] According to the second proposed scheme of this disclosure, when UE 110 adds SNPN to a "Permanently Banned SNPN List for Localized Services in SNPN" or a "Temporarily Banned SNPN List for Localized Services in SNPN," which is associated with a selected entry in the "User Data List" or a selected PLMN subscription for 3GPP access or non-3GPP access, and timer T3245 is not running, UE 110 may start timer T3245. If there is no next valid time period for SNPN, UE 110 may start timer T3245 with a random value uniformly randomly drawn from a range of 12 hours (12h) to 24 hours (24h). Alternatively, or additionally, if there is a next valid time period for SNPN, UE 110 may start timer T3245 with a random value uniformly randomly drawn from a range between the start and end times of the next valid time period for localized services in SNPN.

[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 embodiments of this disclosure. Both device 210 and device 220 can perform various functions to implement the schemes, techniques, processes, and methods described herein, involving initiating a non-integrity timer in a localized service in mobile communications, including the schemes described above for various proposed designs, concepts, schemes, systems, and methods, including network environment 100, and the processes described below.

[0029] Both devices 210 and 220 can be part of an electronic device, which may be a network device or a UE (e.g., UE 110), 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, devices 210 and 220 can both be implemented in smartphones, smartwatches, personal digital assistants, electronic control units (ECUs) in vehicles, digital cameras, or computing devices such as tablets, laptops, or handheld computers. Devices 210 and 220 can also be part of a machine-type device, which may be an Internet of Things (IoT) device, such as a non-mobile or fixed device, a home appliance, a roadside unit (RSU), a wired communication device, or a computing device. For example, devices 210 and 220 can both 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 as an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or as a gNB or TRP in a 5G, NR, or IoT network.

[0030] In some implementations, both device 210 and device 220 may take the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more complex instruction-set computing (CISC) processors, or one or more reduced instruction-set computing (RISC) processors. In all the above embodiments, both device 210 and device 220 may be implemented as network devices or UEs. Both device 210 and device 220 may contain... Figure 2 The components shown include at least some of the components, such as processor 212 and processor 222, respectively. Devices 210 and 220 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity, Figure 2 Such components of devices 210 and 220 are not shown and are not described below.

[0031] In one aspect, both processor 212 and processor 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "processor" is used herein to refer to processor 212 and processor 222, according to certain embodiments of this disclosure, processor 212 and processor 222 may comprise multiple processors, or in other embodiments may be a single processor. In another aspect, both processor 212 and processor 222 may be implemented in hardware (and optionally firmware) and include, 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 varactors, these electronic components being configured and arranged according to this disclosure to achieve a particular purpose. In other words, in at least some embodiments, processor 212 and processor 222 are dedicated machines specifically designed, arranged, and configured to perform specific tasks, including tasks related to initiating non-integrity timers in localized services in mobile communications according to various embodiments of this disclosure.

[0032] In some embodiments, device 210 may further include a transceiver 216 connected to processor 212. Transceiver 216 enables wireless data transmission and reception. In some embodiments, transceiver 216 can wirelessly communicate with different types of wireless networks and different radio access technologies (RATs). In some embodiments, 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 to enable multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 220 may further include a transceiver 226 connected to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 226 can wirelessly communicate with different types of UE / wireless networks and different RATs. In some embodiments, transceiver 226 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas to enable MIMO wireless communication.

[0033] In some embodiments, device 210 may further include a memory 214 coupled to and accessible by processor 212 for storing data. In some embodiments, device 220 may further include a memory 224 coupled to and accessible by processor 222 for storing data. Each of memory 214 and memory 224 may include a random-access memory (RAM), such as dynamic random-access memory (DRAM), static random-access memory (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, each of memories 214 and 224 may include a read-only memory (ROM), such as a mask ROM, a programmable ROM (PROM), an erasable programmable ROM (EPROM), and / or an electrically erasable programmable ROM (EEPROM). Alternatively, each of memories 214 and 224 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0034] Each of devices 210 and 220 can be a communication entity capable of communicating according to various proposed schemes of this disclosure. For the purpose of illustration and without limitation, the following describes, in the context of example flows 300 and 400, the capabilities of device 210 as user equipment (UE, e.g., UE 110) and device 220 as a network node (e.g., network node 125) belonging to a network (e.g., wireless network 120 as a fifth-generation / new radio (5G / NR) mobile network).

[0035] Example Process

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

[0037] At 310, process 300 may involve the processor 212 of device 210 receiving, via transceiver 216, a rejection message with a specific cause value that has no integrity protection (e.g., from wireless network 120, via device 220 as network node 125). Process 300 may continue from 310 to 320.

[0038] At 320, process 300 may involve the processor 212 of device 210, upon receiving the data, starting timer T3247 for a random value uniformly randomly drawn from a range for localized services in an independent non-public network.

[0039] In some implementations, the range may include the interval between the start and end times of the next valid time period for localized services in the independent, non-public network. In some implementations, the specific reason may include 5th Generation Mobility Management (5GMM) reason value #74 or 5GMM reason value #75.

[0040] In some implementations, the range may be the range between the start time and the end time of the next valid time period for the localized service in the independent non-public network, provided that the next valid time period does not exceed 30 minutes. Alternatively, the range may be the range between the start time and the end time of the next valid time period for the localized service in the independent non-public network, provided that the next valid time period does not exceed 60 minutes.

[0041] In some implementations, the rejection message may include a registration rejection message or a service rejection message.

[0042] In some implementations, the independent, non-public network may be selected for the specific access type that receives the rejection message.

[0043] Figure 4 An example flow 400 according to an embodiment of this disclosure is illustrated. Flow 400 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 400 may represent one aspect of proposed concepts and schemes related to initiating a non-integrity timer in a localized service in mobile communications. Flow 400 may include one or more operations, actions, or functions as shown in flow blocks 410 and 420. Although shown as discrete flow blocks, the individual flow blocks of flow 400 may be divided into more flow blocks, merged into fewer flow blocks, or omitted according to desired implementation methods. Furthermore, the flow blocks / sub-flow 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 process blocks / sub-process blocks of process 400 can be executed repeatedly or iteratively. Process 400 can be implemented by devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 400 is described below in the context of device 210 as a user equipment (e.g., UE 110) and device 220 as a communication entity such as a network node or base station (e.g., network node 125) belonging to a network (e.g., wireless network 120). Process 400 may begin with process block 410.

[0044] At 410, process 400 may involve the processor 212 of device 210 adding a standalone non-public network to the list of prohibited standalone non-public networks. Process 400 can continue from 410 to 420.

[0045] At 420, process 400 may involve the processor 212 of device 210 starting timer T3245 if timer T3245 is not running after this addition.

[0046] In some implementations, when starting timer T3245, process 400 may involve the processor 212 of device 210 starting timer T3245 with a random value uniformly randomly drawn from a range of 12 hours to 24 hours when there is no next valid time period.

[0047] In some implementations, when starting timer T3245, process 400 may involve the processor 212 of device 210 starting timer T3245 with a random value uniformly randomly drawn from the range between the start and end times of the next valid time period for localized services in the independent non-public network, provided that the independent non-public network has a next valid time period.

[0048] In some implementations, when adding a standalone non-public network to the list of prohibited standalone non-public networks, processor 212 starts timer T3245 to add the standalone non-public network to either a "permanent list of prohibited standalone non-public networks for localized services in standalone non-public networks" or a "temporary list of prohibited standalone non-public networks for localized services in standalone non-public networks," which are associated with selected entries in the "User Data List" or selected PLMN subscriptions for 3GPP access or non-3GPP access.

[0049] Additional Notes

[0050] The topics described herein sometimes demonstrate different components contained within or connected to different other components. It should be understood that these 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” 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 and / or logically interactive and / or logically interactive components.

[0051] 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. For clarity, various singular / plural arrangements are explicitly listed herein.

[0052] Furthermore, those skilled in the art will understand that terms commonly used in this specification, particularly in appended claims, such as the body portion of appended claims, are generally considered "open-ended" 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 further understand that if a specific quantity is introduced in a claim intentionally, that intention will be explicitly stated in the claim; if no such statement is made, then that intention does not exist. For example, for ease of understanding, the appended claims below may contain the use of the introductory phrases "at least one" and "one or more" to introduce the content of the claim. However, the use of such phrases should not be interpreted as meaning that when the content of a claim is introduced by the indefinite article "a" or "an," any specific claim containing that content is limited to containing only one instance of that content, 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 the use of definite articles to introduce the content of a claim. Furthermore, even if a specific number of the introduced content is explicitly stated in the claims, those skilled in the art will recognize that such a statement should be interpreted as at least the number stated. For example, stating "two contents" alone, without further modification, means at least two contents, or two or more contents. Additionally, when using conventions such as "at least one A, B, and C, etc.", such structures should generally be interpreted in the way that those skilled in the art understand the convention. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C, etc. Similarly, when using conventions such as "at least one A, B, or C, etc.", such structures should generally be interpreted in the way that those skilled in the art understand the convention. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C, etc. Those skilled in the art will further understand that virtually any disjunctive words and / or phrases appearing in the description, claims, or drawings, when presenting two or more alternative terms, should be understood to include one, any, or both terms. For example, the phrase “A or B” should be understood to include the possibility of “A”, or “B”, or “A and B”.

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

Claims

1. A method comprising: A processor of a user equipment receives a rejection message that has no integrity protection and has a specific cause value. as well as Upon receiving the data, the processor starts a timer T3247 for a localized service in an independent, non-public network, by uniformly and randomly selecting a random value from a range.

2. The method of claim 1, wherein the range includes a range between a start time point of the next valid time period and an end time point of the next valid time period for the localized service in the independent non-public network.

3. The method of claim 2, wherein the specific reason includes a fifth-generation mobility management reason #74.

4. The method of claim 2, wherein the specific reason includes a fifth-generation mobility management reason #75.

5. The method of claim 2, wherein the range includes the range between the start time and the end time of the next valid time period for the localized service in the independent non-public network, provided that the next valid time period does not exceed 30 minutes.

6. The method of claim 2, wherein the range includes the range between the start time and the end time of the next valid time period for the localized service in the independent non-public network, provided that the next valid time period does not exceed 60 minutes.

7. The method of claim 1, wherein the rejection message includes a registration rejection message or a service rejection message.

8. The method of claim 1, wherein the independent non-public network is selected for a specific access type to receive the rejection message.

9. A method comprising: A processor of a user device adds a standalone, non-public network to a list of prohibited standalone, non-public networks. as well as After the independent non-public network is added to the list of prohibited independent non-public networks, the processor starts the timer T3245 if the timer T3245 is not running.

10. The method of claim 9, wherein starting the timer T3245 comprises starting the timer T3245 by uniformly and randomly selecting a random value within a range of 12 hours to 24 hours when there is no next valid time period.

11. The method of claim 9, wherein starting the timer T3245 comprises, if there is a next valid time period in the independent non-public network, starting the timer T3245 with a random value uniformly randomly drawn from a range between a start time point and an end time point of the next valid time period for the localized service in the independent non-public network.

12. The method of claim 9, wherein adding the independent non-public network to the list of prohibited independent non-public networks includes adding the independent non-public network to a "permanent list of prohibited independent non-public networks for localized service access in independent non-public networks" or a "temporary list of prohibited independent non-public networks for localized service access in independent non-public networks", which are associated with selected entries of a "user data list" or a selected public land mobile network subscription for access under the 3G Partner Program or not under the 3G Partner Program.

Images