US20240023049A1

US20240023049A1 - Handling PLMN Prioritization

Info

Publication number: US20240023049A1
Application number: US18/475,759
Authority: US
Inventors: Roland Gruber; Deepak Dash; Nitin Kuppelur
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2020-11-04
Filing date: 2023-09-27
Publication date: 2024-01-18
Also published as: CN117354895A; US20230422197A1; WO2022099281A1; CN116472729A

Abstract

A user equipment (UE) transmits a registration request message to a first public land mobile network (PLMN), wherein the first PLMN is a roaming PLMN, receives a registration accept message from the first PLMN, determines that the registration accept message includes a manipulated steering of roaming (SoR) container or does not include a SoR container, wherein the SoR container is configured by a home PLMN (HPLMN) of the UE and transmitted to the first PLMN from the HPLMN, determines that the registration accept message includes an indication that the first PLMN does not support voice over packet switching (VoPS) and adds the first PLMN to a first list of PLMNs in which voice service is not possible in an N1 mode.

Description

BACKGROUND

5G new radio (NR) wireless communications support updates to user equipment (UE) parameters by a home PLMN (HPLMN) while the UE is roaming. The HPLMN update of parameters are based on the policies of the network provider. For example, according to current 3GPP standards, parameters such as the steering of roaming (SoR) list may be updated on the UE by the HPLMN. However, there are scenarios where the UE parameters may not be updated in the correct manner.

SUMMARY

Some exemplary embodiments are related to a user equipment (UE) having a transceiver configured to connect to a plurality of networks and a processor communicatively coupled to the transceiver and configured to perform operations. The operations include transmitting a registration request message to a first public land mobile network (PLMN), wherein the first PLMN is a roaming PLMN, receiving a registration accept message from the first PLMN, determining that the registration accept message includes a manipulated steering of roaming (SoR) container or does not include a SoR container, wherein the SoR container is configured by a home PLMN (HPLMN) of the UE and transmitted to the first PLMN from the HPLMN, determining that the registration accept message includes an indication that the first PLMN does not support voice over packet switching (VoPS) and adding the first PLMN to a first list of PLMNs in which voice service is not possible in an N1 mode.
Other exemplary embodiments include a processor of a user equipment (UE) configured to perform operations. The operations include transmitting a registration request message to a first public land mobile network (PLMN), wherein the first PLMN is a roaming PLMN, receiving a registration accept message from the first PLMN, determining that the registration accept message includes a manipulated steering of roaming (SoR) container or does not include a SoR container, wherein the SoR container is configured by a home PLMN (HPLMN) of the UE and transmitted to the first PLMN from the HPLMN, determining that the registration accept message includes an indication that the first PLMN does not support voice over packet switching (VoPS) and adding the first PLMN to a first list of PLMNs in which voice service is not possible in an N1 mode.
Still further exemplary embodiments are related to a method performed by a user equipment (UE). The method includes transmitting a registration request message to a first public land mobile network (PLMN), wherein the first PLMN is a roaming PLMN, receiving a registration accept message from the first PLMN, determining that the registration accept message includes a manipulated steering of roaming (SoR) container or does not include a SoR container, wherein the SoR container is configured by a home PLMN (HPLMN) of the UE and transmitted to the first PLMN from the HPLMN, determining that the registration accept message includes an indication that the first PLMN does not support voice over packet switching (VoPS) and adding the first PLMN to a first list of PLMNs in which voice service is not possible in an N1 mode.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary network arrangement according to various exemplary embodiments.

FIG. 2 shows an exemplary UE according to various exemplary embodiments.

FIG. 3 shows a method of selecting a radio access technology (RAT)/public land mobile network (PLMN) combination according to various exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The exemplary embodiments describe manners for a user equipment (UE) to select a radio access technology (RAT)/public land mobile network (PLMN) combination while roaming.
The exemplary embodiments are described with regard to a network that includes 5G (new radio) NR RAT. However, the exemplary embodiments may be implemented in other types of networks using the principles described herein.
The exemplary embodiments are also described with regard to a UE. However, the use of a UE is merely for illustrative purposes. The exemplary embodiments may be utilized with any electronic component that may establish a connection with a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any electronic component.
Based on current Third Generation Partnership Project (3GPP) standards TS 24.501 and 23.122, a UE, which registers on a roaming PLMN without a voice over packet switch (VoPS) indication from the network and whose usage setting is voice centric, is to disable its 5G NR RAT services on the current PLMN and search for other RATS (e.g., legacy RATS such as Long Term Evolution (LTE)) on the same PLMN.
In addition, in some cases, the subscriber identity module (SIM) of a UE may be configured with an indication that the UE is to receive the steering of roaming (SoR) transparent container information element (IE). When a home PLMN (HPLMN) sends the SoR container including a preferred PLMN list to the UE via a roaming PLMN, the HPLMN adds a unique signature to encrypt the container. If the roaming PLMN attempts to manipulate the SoR container or fails to forward the container to the UE altogether, the UE will designate the roaming PLMN as a lowest priority PLMN and proceed to search for a higher priority PLMN that may support a 5G RAT.
An issue that arises is when both of these scenarios arise simultaneously. The current 3GPP standards do not address a scenario where both (1) the roaming PLMN indicates that the network does not support VoPS and (2) the SoR container is not received in the Registration Accept message received from the roaming PLMN.
According to some exemplary embodiments, when both scenarios (1 and 2) described above occur simultaneously, the UE adds the current PLMN to a list of PLMNs on which voice services (e.g., VoPS) on 5G RAT (e.g., N1 mode) are temporarily not supported and to a list of PLMNs where registration was aborted due to SoR failure. As a result, the UE does not immediately disable its 5G RAT services and instead begins to search for 5G RATS on higher priority PLMNs. If no higher priority PLMNs with RAT are found, the UE will then disable its 5G RAT services and camp on a legacy RAT of the current PLMN.
FIG. 1 shows an exemplary network arrangement 100 according to various exemplary embodiments. The exemplary network arrangement 100 includes a UE 110. It should be noted that any number of UEs may be used in the network arrangement 100. Those skilled in the art will understand that the UE 110 may alternatively be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (IoT) devices, etc. It should also be understood that an actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of a single UE 110 is merely provided for illustrative purposes.
The UE 110 may be configured to communicate with one or more networks. In the example of the network configuration 100, the networks with which the UE 110 may wirelessly communicate are a 5G New Radio (NR) radio access network (5G NR-RAN) 120, an LTE radio access network (LTE-RAN) 122 and a wireless local access network (WLAN) 124. However, it should be understood that the UE 110 may also communicate with other types of networks and the UE 110 may also communicate with networks over a wired connection. Therefore, the UE 110 may include a 5G NR chipset to communicate with the 5G NR-RAN 120, an LTE chipset to communicate with the LTE-RAN 122 and an ISM chipset to communicate with the WLAN 124.
The 5G NR-RAN 120 and the LTE-RAN 122 may be portions of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, I-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.) that are configured to send and receive traffic from UE that are equipped with the appropriate cellular chip set. The WLAN 124 may include any type of wireless local area network (WiFi, Hot Spot, IEEE 802.11x networks, etc.).
The UE 110 may connect to the 5G NR-RAN 120 via the gNB 120A and/or the gNB 120B. During operation, the UE 110 may be within range of a plurality of gNBs. Thus, either simultaneously or alternatively, the UE 110 may connect to the 5G NR-RAN 120 via the gNBs 120A and 120B. Further, the UE 110 may communicate with the eNB 122A of the LTE-RAN 122 to transmit and receive control information used for downlink and/or uplink synchronization with respect to the 5G NR-RAN 120 connection.
Those skilled in the art will understand that any association procedure may be performed for the UE 110 to connect to the 5G NR-RAN 120. For example, as discussed above, the 5G NR-RAN 120 may be associated with a particular cellular provider where the UE 110 and/or the user thereof has a contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit the corresponding credential information to associate with the 5G NR-RAN 120. More specifically, the UE 110 may associate with a specific base station (e.g., the gNB 120A of the 5G NR-RAN 120).
In addition to the networks 120, 122 and 124 the network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 also manages the traffic that flows between the cellular network and the Internet 140. The cellular core network 130 may be considered to be the interconnected set of components that manages the operation and traffic of the cellular network. The cellular core network may include various other components performing any of a variety of different functions.
FIG. 2 shows an exemplary UE 110 according to various exemplary embodiments. The UE 110 will be described with regard to the network arrangement 100 of FIG. 1 . It should be noted that the UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input/output (I/O) device 220, a transceiver 225 and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, one or more antenna panels, etc. For example, the UE 110 may be coupled to an industrial device via one or more ports.
The processor 205 may be configured to execute a plurality of engines of the UE 110. For example, the engines may include an PLMN management engine 235. As will be described in more detail below, the PLMN management engine 235 may perform various operations related to camping on a PLMN based on, for example, a stored PLMN list.
The above referenced engine being an application (e.g., a program) executed by the processor 205 is only exemplary. The functionality associated with the engine may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UE, the functionality described for the processor 205 is split among two or more processors such as a baseband processor and an applications processor. The exemplary embodiments may be implemented in any of these or other configurations of a UE.
The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to show data to a user while the I/O device 220 may be a hardware component that enables the user to enter inputs. The display device 215 and the I/O device 220 may be separate components or integrated together such as a touchscreen. The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, the LTE-RAN 122, the WLAN 124, etc. Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies).
FIG. 3 shows a method 300 of selecting a radio access technology (RAT)/public land mobile network (PLMN) combination according to various exemplary embodiments. In the example of FIG. 3 , it may be considered that a usage setting of the UE 110 is voice centric and that a SIM of the UE 110 is configured with an indication that the UE is to receive the SoR transparent container IE.
At 305, the UE 110 sends a registration request to a first PLMN (e.g., a gNB of the first PLMN) while roaming. Although not shown in FIG. 3 , the first PLMN transmits an Nudm_SDM_Get request message to the HPLMN to obtain an SoR container from the HPLMN. At 310, the UE 110 receives a registration accept transmission from the first PLMN. In some embodiments, the registration accept transmission includes the SoR container and an indication of whether the first PLMN supports VoPS services. At 315, the UE 110 may transmit a Registration Complete message to the first PLMN. In some embodiments, the UE may alternatively not transmit the Registration Complete message if it determines that it will not ultimate camp on this PLMN.
At 320, the UE 110 determines if the first PLMN supports VoPS and if an unmanipulated SoR container was received in the registration accept transmission. It should be noted that the answer to the latter (the unmanipulated SoR container) will be negative if the SoR container was entirely not received or if the SoR container was received but the UE 110 determines that the first PLMN tried to manipulate the SoR container.
Although the following description addresses the scenarios in which both parameters are answered in either the affirmative or the negative, it should be noted that if the answer to one is affirmative and the other is negative (e.g., VoPS is supported, but SoR not received, or vice versa), then the UE 110 will act according to the standards defined in 3GPP 24.501 and 23.122.
If the UE 110 determines that VoPS is supported by the first PLMN and that an unmanipulated SoR has been received, then at 325, the UE 110 camps on the 5G RAT of the first PLMN. However, if the UE 110 determines VoPS is not supported by the first PLMN and that an unmanipulated SoR has not been received, then, at 325, the UE 110 releases the connection to the first PLMN. Subsequently, at 335, the UE 110 adds the first PLMN to a list of PLMNs on which voice services (e.g., VoPS) on 5G RAT (e.g., N1 mode) are temporarily not supported and also to a list of PLMNs where registration was aborted due to failure to receive an unmanipulated SoR container. As a result, the first PLMN is assigned a lowest priority. However, the UE 110 does not immediately disable its 5G RAT services
At 340, the UE 110 searches for higher priority PLMNs with a 5G RAT and other available RATS supported by the UE 110. In some embodiments, this search may be based on a PLMN priority list stored on the UE 110 (e.g., locally, on the SIM). At 345, the UE 110 determines if a higher priority PLMN has been found. If so, then, at 350, the UE 110 camps on the higher priority PLMN. If, however, a higher priority PLMN has not been found, then the UE 110 disables its 5G RAT services and camps on a legacy RAT (e.g., LTE, 3G, etc.) of the first PLMN. As a result of the method 300, the probability that the UE 110 will camp on a low priority PLMN is advantageously minimized, thus improving user experience and minimizing roaming charges.
Those skilled in the art will understand that the above-described exemplary embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An exemplary hardware platform for implementing the exemplary embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc. In a further example, the exemplary embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.
Although this application described various aspects each having different features in various combinations, those skilled in the art will understand that any of the features of one aspect may be combined with the features of the other aspects in any manner not specifically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed aspects.
It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
It will be apparent to those skilled in the art that various modifications may be made in the present disclosure, without departing from the spirit or the scope of the disclosure. Thus, it is intended that the present disclosure cover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent.

Claims

1-21. (canceled)

22. A base station, comprising:

a transceiver configured to communicate with a user equipment (UE); and

a processor communicatively coupled to the transceiver and configured to perform operations comprising:

receiving, from the UE, a registration request message for a first public land mobile network (PLMN), wherein the first PLMN is a roaming PLMN; and

transmitting, to the UE, a registration accept message comprising a steering of roaming (SoR) container, wherein the SoR container is configured by a home PLMN (HPLMN) of the UE and transmitted to the first PLMN from the HPLMN, wherein the registration accept message further comprises an indication of whether the first PLMN supports voice over packet switching (VoPS).

23. The base station of claim 22, wherein the operations further comprise:

receiving, from the UE, a registration complete message.

24. The base station of claim 22, wherein the SoR container is a manipulated SoR container.

25. The base station of claim 22, wherein the SoR container is an unmanipulated SoR container.

26. The base station of claim 25, wherein the first PLMN supports VoPS.

27. The base station of claim 26, wherein based on the unmanipulated SoR container and the first PLMN support of the VoPS, the UE camps on the base station.

28. The base station of claim 22, wherein the first PLMN does not support VoPS.

29. A processor of a base station configured to perform operations comprising:

receiving, from a user equipment (UE), a registration request message for a first public land mobile network (PLMN), wherein the first PLMN is a roaming PLMN; and

30. The processor of claim 29, wherein the operations further comprise:

receiving, from the UE, a registration complete message.

31. The processor of claim 29, wherein the SoR container is a manipulated SoR container.

32. The processor of claim 29, wherein the SoR container is an unmanipulated SoR container.

33. The processor of claim 32, wherein the first PLMN supports VoPS.

34. The processor of claim 33, wherein based on the unmanipulated SoR container and the first PLMN support of the VoPS, the UE camps on the base station.

35. The processor of claim 29, wherein the first PLMN does not support VoPS.

36. A method performed by a base station, comprising:

37. The method of claim 36, further comprising:

receiving, from the UE, a registration complete message.

38. The method of claim 36, wherein the SoR container is a manipulated SoR container.

39. The method of claim 36, wherein the SoR container is an unmanipulated SoR container.

40. The method of claim 39, wherein the first PLMN supports VoPS.

41. The method of claim 40, wherein based on the unmanipulated SoR container and the first PLMN support of the VoPS, the UE camps on the base station.