US-12628107-B2 - Network identification collision detection for private networks

Abstract

Techniques are directed toward network identification collision detection. An example method includes selecting a first subscriber identity module (SIM) associated with a public land mobile network identifier (PLMN ID) and a network identifier (NID) of a private network. The method can further include generating a first non-access stratum (NAS) registration request to establish a connection with the private network using the first SIM. The method can further include processing a NAS registration request reject message received from the private network. The method can further include selecting a second SIM associated with the PLMN ID and the NID. The method can further include generating a second NAS registration request to establish a connection with the private network using the second SIM. The method can further include processing a NAS registration request success message received from the private network. The method can further include logging NID collision information.

Inventors

• Alexander Sirotkin
• Daniel M. Valins
• Nai Tao Cui
• Raj S. Chaugule
• Sudeep Manithara Vamanan
• Tao Tao

Assignees

• APPLE INC.

Dates

Publication Date

20260512

Application Date

20240103

Claims (20)

1. 1 . A method, comprising: selecting a first subscriber identity module (SIM) associated with a public land mobile network identifier (PLMN ID) and a network identifier (NID) of a private network; generating a first non-access stratum (NAS) registration request to be transmitted to the private network to establish a connection with the private network using the first SIM; processing a NAS registration request reject message received from the private network; selecting a second SIM based the second SIM being associated with the PLMN ID and the NID; generating a second NAS registration request to be transmitted to the private network to establish a connection with the private network using the second SIM; processing a NAS registration request success message received from the private network; and logging NID collision information based on the NAS registration request reject message, the NAS registration request success message, the first SIM being associated with the PLMN ID and NID, and the second SIM being associated with the PLMN ID and NID.
2. 2 . The method of claim 1 , wherein the method further includes: generating a first radio resource control (RRC) message including an indicator of an availability of NID collision information, wherein the first RRC message is to be transmitted to a base station; processing a request for the NID collision information received in a second RRC message from the base station; and generating a third RRC message with the NID collision information, the third RRC message to be transmitted to the base station.
3. 3 . The method of claim 1 wherein the NID collision information includes an indication that an NID collision has occurred, a time the NID collision occurred, or the PLMN ID and NID of the private network.
4. 4 . The method of claim 3 , wherein the NID collision information further includes a global navigation satellite system (GNSS) location, a cell identifier, or a number of highest bits of the GNSS location.
5. 5 . The method of claim 1 , wherein the method further includes: determining expiration criteria has been fulfilled, the expiration criteria being a time-based expiration criteria or a location-based expiration criteria; and discarding the logged NID collision information based on determining the expiration criteria has been fulfilled.
6. 6 . The method of claim 5 , wherein: the expiration criteria is a time-based expiration criteria that includes an expiration of a time interval; or the expiration criteria is a location-based expiration criteria that includes a change in location coordinates, a number of cell re-selections or handovers exceeding a threshold number, or moving out of a coverage of the private network.
7. 7 . The method of claim 1 , wherein the method further includes: connecting with a public network prior to the second NAS registration request being transmitted; and generating a message including an indicator of an availability of NID collision information, the message to be transmitted to the private network based on establishing a connection with the private network.
8. 8 . The method of claim 1 , wherein the NID collision information is a first NID collision information instance associated with a first NID collision, wherein a second NID collision information instance associated with a second NID collision is logged, wherein the second NID collision occurs after the first NID collision, and wherein the method further comprises discarding the first NID collision information instance.
9. 9 . The method of claim 1 , wherein the NID collision information is a first NID collision information instance associated with a first NID collision, wherein a plurality of NID collision information instances are logged, including the first NID collision information instance, and wherein logging NID collision information instances is discontinued upon reaching a threshold number of logged NID collision information instances.
10. 10 . The method of claim 1 , wherein the NAS registration request reject message includes cause code #11 or cause code #13, wherein NID collision information further includes a tracking area identity (TAI), and wherein the NID collision information further includes a new radio cell global identifier (NCGI) of a cell where the NAS registration request reject message was received.
11. 11 . The method of claim 1 , wherein the NID is self-selected by the private network, and wherein a cause code included in the NAS registration request reject message is selected based on the NID being self-selected.
12. 12 . The method of claim 1 , wherein the method further comprises: generating a first message including an indicator of an availability of NID collision information, and wherein the first message is to be transmitted to an application server; processing a second message including an indicator of a request for the NID collision information, the second message received from the application server; and generating a third message including the NID collision information, the third message to be transmitted to the application server.
13. 13 . An apparatus comprising: memory having instructions; processing circuitry coupled with the memory to execute the instructions to: select a subscriber identity module (SIM) associated with a public land mobile network identifier (PLMN ID) and a network identifier (NID) of a first private network; generate a first non-access stratum (NAS) registration request to establish a connection with the first private network using the SIM, the first NAS registration request to be transmitted to the first private network; process a NAS registration request reject message received from the first private network; generate a second NAS registration request to establish a connection with a second private network using the SIM, the second private network associated with the PLMN ID and NID, and the second NAS registration request to be transmitted to the second private network; process a NAS registration request success message received from the second private network; and log NID collision information based on the NAS registration request reject message, the NAS registration request success message, and the first private network and the second private network being associated with the PLMN ID and NID.
14. 14 . The apparatus of claim 13 , wherein the SIM is selected based on a system information block one (SIB1) broadcast that includes the PLMN ID and the NID.
15. 15 . The apparatus of claim 13 , wherein the processing circuitry is to further execute the instructions to determine an expiration criteria has not been fulfilled.
16. 16 . The apparatus of claim 13 , wherein the first NAS registration request is generated while the apparatus transitions from a radio resource control (RRC) idle state to an RRC connected state, or while the apparatus transitions from an RRC inactive state to an RRC connected state.
17. 17 . The apparatus of claim 13 , wherein the apparatus is to be coupled with a single SIM or a single private SIM of a computing platform that incorporates the apparatus.
18. 18 . One or more non-transitory, computer-readable media including instructions that, when executed, cause an apparatus to: process a first non-access stratum (NAS) registration request to establish a connection with a private network using a first subscriber identity module (SIM) associated with a first public land mobile network identifier (PLMN ID) and a network identifier (NID); determine to reject the first NAS registration request based on the first SIM; process a second NAS registration request to establish a connection with the private network using a second SIM associated with the PLMN ID and the NID; and generate a NAS registration success message based on the second NAS registration request and the second SIM.
19. 19 . The one or more non-transitory, computer-readable media of claim 18 , wherein the instructions, when executed, further cause the apparatus to determine to reject the first NAS registration request based on an access stratum (AS) security activation failure.
20. 20 . The one or more non-transitory, computer-readable media of claim 18 , wherein the first SIM is an embedded SIM (eSIM).

Description

CROSS-REFERENCES TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 63/443,107, filed on Feb. 3, 2023, which is incorporated by reference herein in its entirety for all purposes. BACKGROUND Cellular communications can be defined in various standards to enable communications between a user equipment and a cellular network. For example, long-term evolution (LTE) and Fifth generation (5G) networks are defined by wireless standards that aim to improve upon data transmission speed, reliability, availability, and more. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an illustration of a system for connecting to a private network, according to one or more embodiments. FIG. 2 is a signaling diagram for network identifier (NID) collision detection and notification, according to one or more embodiments. FIG. 3 is a signaling diagram for detecting an NID collision, according to one or more embodiments. FIG. 4 is an illustration of example abstract syntax notation one (ASN.1) language for indicating the availability of NID collision information, according to one or more embodiments. FIG. 5 is an illustration of example ASN.1 language for requesting NID collision information, according to one or more embodiments. FIG. 6 is an illustration of example ASN.1 language for reporting an NID collision, according to one or more embodiments. FIG. 7 is a process flow for detecting an NID collision by a multi-SIM device, according to one or more embodiments. FIG. 8 is a process flow for detecting an NID collision by a single-private SIM device, according to one or more embodiments. FIG. 9 illustrates an example of receive components, according to one or more embodiments. FIG. 10 illustrates an example of a UE, according to one or more embodiments. FIG. 11 illustrates an example of a base station, according to one or more embodiments. DETAILED DESCRIPTION The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B); and the phrase “based on A” means “based at least in part on A,” for example, it could be “based solely on A” or it could be “based in part on A.” The following is a glossary of terms that may be used in this disclosure. The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer to an application processor, baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes. The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two