CN113455027B

CN113455027B - Method and apparatus for mobile roaming service

Info

Publication number: CN113455027B
Application number: CN202080015033.7A
Authority: CN
Inventors: 相治咸; 刘建宁; 李岩
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-04-30
Filing date: 2020-03-12
Publication date: 2023-03-17
Anticipated expiration: 2040-03-12
Also published as: CN113455027A; WO2020102831A1

Abstract

A method, comprising: receiving one or more Service Change Network Selection Lists (SCNSL) from a home network of a user equipment; detecting that a service change occurrence indicator associated with the home network is set to a first specified value, and based thereon: switching from using the network selection list to using the SCNSL according to the selection policy of the user equipment; scanning for an appropriate network in the SCNSL; receiving identifiers from one or more networks in the SCNSL; determining network selection priority according to the SCNSL; one of the one or more networks in the SCNSL is selected according to the network selection priority.

Description

Method and apparatus for mobile roaming service

The present application claims priority from U.S. provisional application No. 62/840,922, entitled "system and method for mobile roaming service disruption minimization" filed on 2019, 30/4, and incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates generally to methods and apparatus for digital communications, and in particular embodiments, to methods and apparatus for mobile roaming services.

Background

Regional regulatory authorities strive to take measures to minimize the impact of communication interruptions, regardless of cause, on people's daily life. For example, recently, the korean government announced measures to enhance the resilience of communication services in a catastrophic situation. One of the measures is to provide access to communication services in an emergency situation through cooperation between regional operators. As social ties become increasingly tighter, these types of regulatory requirements should be supported effectively.

When a network is unable to provide communication services to network users due to certain events (e.g., disasters (e.g., fire, earthquake, bad weather, etc.), oversubscription of services due to oversubscription (e.g., concerts, special events, etc.), the time that user communication services are interrupted and the additional impact on other networks should be minimized. To better address these aspects, methods and apparatus for mobile roaming services are needed.

Disclosure of Invention

According to a first aspect, a method implemented by a User Equipment (UE) is provided. The method comprises the following steps: the UE receives one or more Service Change Network Selection Lists (SCNSL) from a home network of the UE; the UE detects that a service change occurrence indicator associated with the home network is set to a first specified value and, based thereon: the UE switches from using the network selection list to using the SCNSL according to the selection strategy of the UE; the UE scans for a suitable network in the SCNSL; the UE receives identifiers from one or more networks in the SCNSL; the UE determines the network selection priority according to the SCNSL; the UE selects one of the one or more networks in SCNSL according to the network selection priority.

In a first embodiment of the method according to the first aspect, the one or more SCNSLs are different from the network selection list.

In a second embodiment of the method according to the first aspect or any previous embodiment thereof, the network selection priority comprises at least one of: a service of the UE, a subscription level of the UE, a current time of day, a time and period of expected service, a trigger event limit, or a service provided by one or more networks.

In a third implementation of the method according to the first aspect or any previous implementation thereof, the network selection priority further comprises a location of the UE and a time and period of service expected to be received by the UE.

In a fourth embodiment of the method according to the first aspect or any previous embodiment thereof, further comprising: the UE determines the location of the UE and the time and period of the service the UE is expected to receive.

In a fifth embodiment of the method according to the first aspect or any previous embodiment thereof, further comprising: the UE accesses one of the one or more networks.

In a sixth implementation of the method according to the first aspect or any previous implementation thereof, further comprising the UE detecting that a service change occurrence indicator associated with the home network is set to a second specified value, and based thereon: UE switches to a network selection list; the UE scans a suitable second network in the network selection list; the UE receiving identifiers from one or more second networks in the network selection list; the UE selects one of the one or more second networks according to the network selection list.

In a seventh implementation form of the method according to the first aspect as such or any previous implementation form thereof, the above-mentioned service change occurrence indicator is received from a network covering the UE.

In an eighth implementation of the method according to the first aspect as such or any previous implementation thereof, the UE is capable of receiving information from the network as described above.

In a ninth embodiment of the method according to the first aspect or any previous embodiment thereof, further comprising: the UE accesses one of the one or more second networks.

In a tenth embodiment of the method according to the first aspect or any previous embodiment thereof, further comprising: the UE receives an identifier of a home network; the UE accesses a home network.

In an eleventh implementation of the method according to the first aspect as such or any previous implementation thereof, the service change occurrence indicator is set to a first specified value indicating that a service change event has occurred in the home network.

According to a second aspect, a method implemented by a network entity is provided. The method comprises the following steps: a network entity detecting that a service change event has occurred on a network; the network entity transmits a service change occurrence indicator associated with the network, the service change occurrence indicator being set to a first specified value.

In a first embodiment of the method according to the second aspect, the network entity receives a service change event from a centralized management entity.

In a second embodiment of the method according to the second aspect or any previous embodiment thereof, the service change event comprises at least one of: an emergency event occurring in the network, or a special event occurring in the network.

In a third embodiment of the method according to the second aspect or any previous embodiment thereof, the service change occurrence indicator is sent in a broadcast message or a unicast message in response to the query.

In a fourth embodiment of the method according to the second aspect or any previous embodiment thereof, further comprising: the network entity detects that the service change event is resolved and, based thereon, the network entity sends a service change occurrence indicator set to a second specified value.

In a fifth embodiment of the method according to the second aspect or any previous embodiment thereof, the second specified value indicates that the service change event has been resolved.

In a sixth embodiment of the method according to the second aspect or any previous embodiment thereof, the first specified value indicates that a service change event occurred.

According to a third aspect, a UE is provided. The UE comprises: a non-transitory memory comprising instructions; one or more processors in communication with the memory, wherein the one or more processors execute the instructions to: receiving one or more SCNSLs from a home network of the UE; detecting that a service change occurrence indicator associated with the home network is set to a first specified value, and based thereon: switching from using the network selection list to using the SCNSL according to the selection strategy of the UE; scanning for an appropriate network in the SCNSL; receiving identifiers from one or more networks in the SCNSL; determining the network selection priority according to the SCNSL; one of the one or more networks in the SCNSL is selected according to a network selection priority.

In a first embodiment of the UE according to the third aspect, the network selection priority comprises at least one of: a service of the UE, a subscription level of the UE, a current time of day, a time and period of expected service, a trigger event limit, or a service provided by one or more networks.

In a second embodiment of the UE according to the third aspect or any previous embodiment thereof, the network selection priority further comprises a location of the UE and a time and period of service expected to be received by the UE.

In a third embodiment of the UE according to the third aspect or any previous embodiment thereof, the one or more processors further execute the instructions to determine a location of the UE and a time and period of service expected to be received by the UE.

In a fourth embodiment of the UE according to the third aspect or any previous embodiment thereof, the one or more processors further execute the instructions to access one of the one or more networks.

In a fifth embodiment of the UE according to the third aspect or any previous embodiment thereof, the one or more processors further execute the instructions to: detecting that a service change occurrence indicator associated with the home network is set to a second specified value, and based thereon: switching to using the network selection list; scanning a suitable second network in the network selection list; receiving identifiers from one or more second networks in the network selection list; one of the one or more second networks is selected according to the network selection list.

In a sixth embodiment of the UE according to the third aspect or any previous embodiment thereof, the one or more processors further execute the instructions to: receiving an identifier of a home network; and accessing the home network.

According to a fourth aspect, a network entity is provided. The network entity includes: a non-transitory memory comprising instructions; one or more processors in communication with the memory, wherein the one or more processors execute instructions to: detecting that a service change event has occurred on the network; a service change occurrence indicator associated with the network is sent, the service change occurrence indicator being set to a first specified value.

In a first embodiment of the network entity according to the fourth aspect, the one or more processors further execute the instructions to receive a service change event from the centralized management entity.

In a second embodiment of the network entity according to the fourth aspect or any previous embodiment thereof, the service change event comprises at least one of: an emergency event occurring in the network, or a special event occurring in the network.

In a third embodiment of the network entity according to the fourth aspect or any previous embodiment thereof, the one or more processors further execute instructions to: it is detected that the service change event is resolved and, based thereon, a service change occurrence indicator set to a second specified value is transmitted.

The advantages of the preferred embodiment are: users affected by service change conditions may obtain service in networks that are not normally available to them. Accordingly, the user can receive important information in an emergency or maintain user satisfaction in a non-emergency.

Another advantage of the preferred embodiment is: once the service change condition clears, the user may return to their normal network even if the user misses an indication that the service change condition has cleared.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

fig. 1 illustrates an example communication system 100 for communicating data;

fig. 2A shows a communication system with three Public Land Mobile Networks (PLMNs).

Fig. 2B illustrates a communication system highlighting a situation where an emergency event causes a Home PLMN (HPLMN) to be disabled;

FIG. 2C illustrates a communication system highlighting the case where a particular event causes a service disruption;

fig. 3A illustrates a first example service change PLMN selection list in accordance with example embodiments presented herein;

fig. 3B illustrates a second example service change PLMN selection list in accordance with an example embodiment presented herein;

FIG. 4 shows a diagram of messages exchanged and processing that occurs at a device or network participating in example operations that occur in response to the occurrence of a service change event, according to an example embodiment presented herein;

fig. 5 illustrates a flowchart of example operations occurring in a UE in response to an occurrence of a service change event according to example embodiments presented herein;

fig. 6 illustrates a flowchart of example operations occurring in a network entity in response to an occurrence of a service change event according to example embodiments presented herein;

fig. 7 illustrates a flowchart of example operations occurring in a UE that recovers upon resolving a service change event, according to example embodiments presented herein;

fig. 8 illustrates a detailed view of a communication system highlighting a configuration of a service change PLMN list according to an example embodiment presented herein;

fig. 9 illustrates an example communication system according to example embodiments presented herein;

10A and 10B illustrate example devices that may implement methods and teachings in accordance with this disclosure; and

FIG. 11 is a block diagram of a computing system that may be used to implement the apparatus and methods disclosed herein.

Detailed Description

The construction and use of the disclosed embodiments are discussed in detail below. It should be appreciated, however, that the present disclosure provides many applicable concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific structures and uses of the embodiments and do not limit the scope of the disclosure.

Fig. 1 illustrates an example communication system 100 for communicating data. Communication system 100 includes an access point (access point) 110 having a coverage area 111, a plurality of mobile devices (e.g., mobile device 120 and mobile device 122), and a backhaul network 130.AP 110 may include any component capable of providing wireless access by establishing uplink (dashed lines) and/or downlink (solid lines) connections with mobile devices. In the first mode of operation, communication with the mobile device is through the AP 110. In the second mode of operation, communication with the mobile device does not pass through the AP 110, however, when certain conditions are met, the AP 110 typically allocates resources for communication by the mobile device.

An AP may also generally refer to a Node B (Node B), an evolved Node B (eNB), a Next Generation (NG) Node B (gNB), a master eNB (MeNB), a secondary eNB (SeNB), a master gNB (MgNB), a secondary gNB (SgNB), a network controller, a control Node, a base station, an access Node, a Transmission Point (TP), a transmission-reception point (TRP), a cell, a carrier, a macro cell, a femto cell, a pico cell, and the like, while a mobile device may also generally refer to a mobile station, a mobile apparatus, a mobile station, a terminal, a user, a subscriber, a station, a User Equipment (UE), and the like. The AP may provide wireless access according to one or more wireless communication protocols, such as third generation partnership project (3 GPP) Long Term Evolution (LTE), LTE advanced (LTE-a), 5G LTE, 5G NR, high Speed Packet Access (HSPA), IEEE 802.11 family of standards (e.g., 802.11 a/b/G/n/ac/ad/ax/ay/be), and so on. For simplicity, only one AP and two mobile devices are shown, although it is understood that the communication system may use multiple APs capable of communicating with multiple mobile devices.

Backhaul network 130 may be any component or collection of components that allow an AP and a remote end to exchange data. In some embodiments, backhaul network 130 may include various other wireless devices, such as relays, low power nodes, and the like. A public land network (PLMN) is a mobile radio network that provides a combination of radio services in a particular area. PLMNs are typically operated by a single operator. There may be multiple PLMNs in an area with overlapping coverage. A Home Public Land Mobile Network (HPLMN) and an access public land mobile network (VPLMN) in communication system 100 may have the same overlapping coverage area or different coverage areas from each other.

The 3GPP technical specification group regards service and system aspects: service (SA 1) has created a new project to investigate how to enhance roaming between operators to provide services in catastrophic situations. Potential aspects that need to be addressed in order to obtain relevant potential service requirements include, for example:

-the scenario, scale, or cause of the communication service interruption;

-allowing affected users to override restrictions, e.g. PLMNs that were barred due to previous access before a disaster occurred;

-allowing affected users to obtain warning information missed during service interruptions; and

-giving the disaster-stricken user a different treatment (e.g. differentiated treatment of access control) than the local home user, and applying the differentiated treatment to which types of services (e.g. voice, data, etc.).

In case of disasters, problems associated with enhanced inter-operational roaming include:

UE selection during a disaster situation, e.g. to allow affected users to override restrictions, e.g. PLMNs that were barred due to previous access before the disaster occurred; and

-preventing VPLMN flooding by UEs from PLMN experiencing disaster.

Fig. 2A shows a communication system 200 with three PLMNs. The communication system 200 includes three PLMNs: HPLMN205, PLMN _1210, and PLMN _2 212. Operating within HPLMN205 are UE 220 and UE 225.HPLMN205 is the home PLMN for UE 220 and UE 225. The UE 220 operates within the coverage areas of the HPLMN205 and PLMN _1210, while the UE 225 operates within the coverage areas of the HPLMN205, PLMN _1210, and PLMN _2 212. Thus, the UE 220 may be connected to the HPLMN205 or PLMN _1210, and the UE 225 may be connected to the HPLMN205, PLMN _1210, or PLMN _2 212.

Fig. 2B illustrates communication system 200 highlighting the case where an emergency event causes HPLMN205 to be disabled. Because the HPLMN205 is disabled, the UE 220 and the UE 225 cannot obtain service through the HPLMN 205. However, if there is a service agreement between the HPLMN205 and the PLMN _1210 or PLMN _2 212, the UE 220 or UE 225 may obtain service through the PLMN _1210 or PLMN _2 212. If the HPLMN205 does not have a service agreement with PLMN _1 or PLMN _2 212, the UE 220 or UE 225 may be out of service.

Fig. 2C illustrates communication system 200 highlighting the case where a particular event results in a service disruption. As shown in fig. 2C, UE 225 is located in region 250, and region 250 may correspond to the location of a particular event (e.g., a concert, a conference, a sporting event, etc.). In general, a special event may be an event or occurrence that causes the HPLMN to suspend its user service for a period of time. Thus, for the duration of a particular event, the HPLMN expects the user to move to another network during this time. For purposes of discussion, consider the case where there are so many users in region 250 that it is not possible for HPLMN205 to provide service to all of its users. In this case, the UE 225 may be out of service.

Accordingly, there is a need for methods and apparatus for mobile roaming services in scenarios resulting from service change situations. As described above, in a catastrophic or emergency situation, or upon the occurrence of a special event, it may be necessary to move the UE from one PLMN to another PLMN to enable the UE to continue receiving service. In these service change situations, the existing service agreements between PLMNs may not ensure that the UE continues to receive service. For example, in an emergency situation, the only available PLMN may not have a service agreement with the HPLMN of the UE, and thus the UE will not be able to obtain service through the only available PLMN. As another example, in a conference, the conference organizer has a service agreement with the PLMN, which does not have a service agreement with the HPLMN of the UE. The UE will not have access to services that help ensure the conference is successful, e.g., services that enhance the experience of the conferee.

According to an example embodiment, a network selection mechanism for selecting a VPLMN in a service change event is provided. The network selection mechanism enables the UE to obtain service through a PLMN whose HPLMN of the UE does not typically have a service agreement or whose HPLMN of the UE does not typically have a service agreement at the subscription level of the UE. Thus, without a network selection mechanism, the UE may not be able to obtain service upon the occurrence of a service change event. As previously mentioned, service change events (including emergency events, catastrophic events, special events, etc.) are non-routine events that typically do not occur on a daily basis and are not within the scope of the general PLMN selection list. The generic PLMN selection list may provide a list of PLMNs that have service agreements with the HPLMN of the UE, as well as services that the UE may obtain through the PLMNs if the UE roams outside the HPLMN coverage. The normal PLMN selection list typically does not include information on how to handle the occurrence of a service change event, which may include a loss of connection with the HPLMN.

According to an example embodiment, a multi-policy based network selection mechanism is provided for accessing a VPLMN when the HPLMN of a UE is unavailable. In the event that the HPLMN is not available, for example due to a catastrophic event or emergency, or due to the presence of a special agreement between the HPLMN and one or more other PLMNs for providing service in a special event, the network selection mechanism may effect selection of the LPMN based on one or more policies. Examples of policies include, but are not limited to: time of day, location, type of service, type of subscription, service change event limit, UE subscription level, PLMN selection criteria, time and period of expected service, or a combination thereof.

While the discussion presented herein focuses primarily on disasters or emergencies, the example embodiments presented herein are operable in other situations as well. For example, during a particular event (e.g., a concert, a conference, a sporting event, etc.), the number of users operating within a particular area may exceed the capabilities of a single PLMN (e.g., HPLMN). In this case, the HPLMN may be arranged with one or more other PLMNs to allow at least some users to migrate to the one or more other PLMNs to alleviate congestion caused by a large number of users during the duration of a particular event. In other words, there is a cooperative arrangement between the HPLMN and one or more other PLMNs to establish roaming operations between operators in addition to the normal roaming relationships that normally exist. This arrangement will replace existing roaming relationships between various PLMNs that may or may not exist. Thus, discussion of disaster or emergency events should not be construed as limiting the scope of the example embodiments.

According to an example embodiment, a service change event PLMN selection mechanism is provided for UEs whose HPLMN cannot provide service. When the HPLMN of the UE is unable to provide service to the UE, for example, after a service change event occurs, the UE needs to obtain service from other PLMNs. Due to typical non-expectations of service change events, the normal PLMN selection list does not include information about where the UE will get service from when the service change event occurs.

In an embodiment, a service change PLMN selection list is provided. The service change PLMN selection list may be separate from the normal PLMN selection list. In an embodiment, the service change PLMN selection list is provided by the HPLMN and provided to the UE. As an example, when the UE attaches to the HPLMN, the UE is provided with a service change PLMN selection list. In an embodiment, the UE is provided with a plurality of service change PLMN selection lists, for example, adapted for different service change events, different UE locations, different subscription levels, service times and periods, etc.

Further, the serving change PLMN selection list may be provided to the UE when the serving change PLMN selection list changes. For example, when the HPLMN establishes an agreement with a PLMN, affecting the service change PLMN selection list, an updated version of the service change PLMN selection list is generated and provided to the UE. As another example, when the agreement between the HPLMN and any PLMN it has service agreements changes, the HPLMN updates the service change PLMN selection list and provides the updated service change PLMN selection list to the UE. As another example, when the subscription level of the UE changes, and if a different version of the service change PLMN selection list is approved, the HPLMN provides the UE with a different version of the service change PLMN selection list.

An example service change PLMN selection list may include a priority list for the VPLMN that lists candidate VPLMNs or disaster alliance Identifiers (IDs) for access by the UE and lists time, location, service type, roaming trigger event restrictions, subscription type or level (e.g., gold (gold), silver (silver), bronze (bronze), etc., where gold is higher than silver, silver is higher than bronze, for example), and other PLMN selection policies, which the UE uses to select a VPLMN for service. The UE uses the information in the service change PLMN selection list to generate policies or restrictions according to which a VPLMN is selected for service.

The entry of the example service change PLMN selection list may specify that when the UE is located at the third location, the UE searching for voice service is allowed access to the third VPLMN because the service change event is a fire emergency. Another example service change PLMN selection list may specify that a UE searching for video service is allowed to access a second VPLMN when the UE is located at a second location. Another example service change PLMN selection list entry may specify that a first UE with a high level of subscription type (e.g., subscription level gold) is allowed to access a second VPLMN while located at a particular location, and a second UE with a low level of subscription type (e.g., subscription level bronze) is allowed to access a third VPLMN while located at a particular location, where the second VPLMN provides greater bandwidth, less latency, higher quality of service (QoS) requirements, fewer number of UEs, etc. than the third VPLMN (in other words, the second VPLMN is an advanced VPLMN and the third VPLMN is not an advanced VPLMN). Additional examples of service change PLMN selection lists and associated entries are provided below.

Fig. 3A illustrates a first example service change PLMN selection list 300. As shown in fig. 3A, the service change PLMN selection list 300 includes entries for multiple PLMNs. By way of example, entry 306 is associated with HPLMN 305, entry 311 is associated with VPLMN _1 310, entry 316 is associated with VPLMN _2 315, and so on. The entries in the service change PLMN selection list 300 may be prioritized. As an example, a UE using the service change PLMN selection list 300 may select the highest entry in the service change PLMN selection list that meets the requirements of the UE (e.g., service, time, location, subscription level, service change event restrictions, service time and period, etc.).

Entry 306 includes two entries: entry 307, which indicates that HPLMN 305 provides video services at

locations

1, 2, 3 24 hours a day, and entry 308, which indicates that HPLMN 305 provides audio services at all locations 24 hours a day. The entry 311 includes three entries: entry 312, indicating that VPLMN _1 310 provides video service at location 1 between 8 am and 7 pm; an entry 313 indicating that VPLMN _1 310 provides audio service at location 2 24 hours a day; entry 314, indicating that VPLMN _1 310 provides E911 service at all locations 24 hours a day. The entries 316 include three entries: entry 317, indicating that VPLMN _2 315 provides video service at location 2 between 7 pm and 5 am; entry 318, indicating that VPLMN _2 315 provides audio service at location 1 24 hours a day; entry 319, indicating that VPLMN _2 315 provides E911 service at all locations 24 hours per day.

Fig. 3B illustrates a second example service change PLMN selection list 350. As shown in fig. 3B, the service change PLMN selection list 350 includes entries grouped based on selection priority. By way of example, entry 356 is associated with location criteria 355, entry 361 is associated with service criteria 360, and so on. The entries in the service change PLMN selection list 350 may be prioritized. As an example, a UE using the serving change PLMN selection list 350 may select an entry based on a selection criterion matching the requirements of the UE. As an example, a UE using the service change PLMN selection list 350 may select the highest priority entry matching the location of the UE and the next highest priority entry matching the service requirements of the UE.

The entry 356 includes two entries: entry 357 indicating that the ordered list of plmns for location 1 includes HPLMN, VPLMN _2, and VPLMN _1; entry 358, indicates that the ordered list of plmns includes HPLMN, VPLMN _1, and VPLMN _3 for location 2. Entry 361 includes two entries: entry 362, indicating that the ordered list for location 1, plmn includes HPLMN, VPLMN _2, and VPLMN _1, and entry 363, indicating that the ordered list for location 2, plmn includes HPLMN, VPLMN _1, and VPLMN _3.

The entries shown in fig. 3A and 3B are for illustration and are not intended to show all information that may be included in the service change PLMN selection list. For example, fig. 3A and 3B do not illustrate service change event restrictions and subscription types. Thus, the information shown in fig. 3A and 3B should not be construed as limiting the scope of example embodiments.

In an embodiment, the UE activates and uses the service change PLMN selection list when a service change event occurs. In normal operation, the UE uses the normal PLMN selection list when no service change event has occurred. However, when a service change event occurs, the UE switches to the service change PLMN selection list and selects a PLMN to obtain service using the service change PLMN selection list.

In an embodiment, the service change PLMN selection list is deactivated when the service change event is completed. When the service change event is completed (e.g., when recovering from a catastrophic event or emergency or when a special event ends), the UE switches to the normal PLMN selection list and resumes normal operation.

In an embodiment, the service change occurrence indicator indicates that a service change event has occurred. As an example, the service change occurrence indicator includes an indicator of one bit or more and an identifier field, and indicates that a service change event has occurred in the PLMN by an identifier transmitted in the identifier field when the indicator is set to a first value. Further, when the indicator is set to the second value, the service change occurrence indicator (via the identifier conveyed in the identifier field) indicates that the PLMN has resumed from the service change event or ended the service change event. As another example, the service change occurrence indicator may be an identifier field, which when set to an identifier of a PLMN, implicitly indicates that a service change event has occurred in the PLMN through the identifier transmitted in the identifier field. When the PLMN has recovered from the service change event or the service change event ends, another service change occurrence indicator may be sent, implicitly indicating that a service change event has recovered or ended.

FIG. 4 illustrates processing of messages and occurrences exchanged at a device or network participating in an example operation occurring in response to an occurrence of a service change event. Fig. 4 shows messages exchanged and processing occurring at PLMN _1 405, network entity 407, PLMN _2409, first UE (UE _ 1) 411, second UE (UE _ 2) 413, and PLMN _3 415.

At PLMN _1 405, the service change condition is satisfied (block 420). If an emergency or catastrophic event occurs, a failure may be detected at one or more network entities of PLMN _1 405, for example. As an example, an earthquake may have disabled one or more access nodes of PLMN _1 405. As another example, where the network change event is a special event, the special event may be detected based on a time and location associated with the special event. Network entity 407 sends a service change notification (event 422). The service change notification may be a network level message for PLMNs operating near PLMN _1 405 to notify those PLMNs that a service change event occurred in PLMN _1 405. For example, the service change notification may be a message with an identifier of PLMN _1 405. The network entity 407 may be a network entity of PLMN _1 405. Alternatively, the network 407 may be a network entity of any other PLMN that is capable of detecting that a service change event has occurred in PLMN _1 405.

PLMNs receiving the service change notification (e.g., PLMN _2409 and PLMN _3 415) transmit service change occurrence indicators (events 424 and 426). As an example, the service change occurrence indicator includes a one-bit or longer indicator set to a value indicating that a service change event has occurred and an identifier field set to an identifier of the PLMN _1 405. As another example, the service change occurrence indicator includes an identifier field set to an identifier of PLMN _1 405. The service change occurrence indicator may be broadcast so that any UE can receive the service change occurrence indicator. The service change occurrence indicator may also be multicast or unicast. As an example, the service change occurrence indicator may be multicast (to the group of UEs) or unicast (to the UEs) in response to a query from a member of the group of UEs or the UEs. The query may be, for example, a network status query. As an alternative to sending the service change occurrence indicator to the UE in an over-the-air (over-the-air) broadcast, multicast, or unicast message, the service change occurrence indicator may be sent to the UE in other manners, such as through the internet or a wired network.

As shown in fig. 4, the first UE 411 and the second UE 413 receive a service change occurrence indicator. The first UE 411 and the second UE 413 switch to their respective service change PLMN selection lists (which may be different), initiate service change selection, and select PLMNs that meet their respective selection priorities (block 428 and block 430). For purposes of discussion, the first UE 411 selects PLMN _2409 and the second UE 413 selects PLMN _3 415. However, the UE selects a PLMN according to its requirements (e.g., service, time, location, subscription level, service change event limits, service time and period, etc.). The first UE 411 accesses PLMN _2409 (event 432) and the second UE 413 accesses PLMN _3 415 (event 434). Accessing the PLMN may include sending one or more messages to attach to the PLMN. The UE may also receive one or more messages from the PLMN.

In case of a service change event in PLMN _1 405, once the service change event has been resolved or ended, the message exchange and processing as shown in fig. 4 also applies to the restoration of normal activity of PLMN _1 405 and the UEs served by PLMN _1 405. As an example, once the service change event has been resolved or ended, network entity 407 sends a service change notification indicating that the service change event has been resolved or ended. PLMN _2409 and PLMN _3 415 may send service change occurrence indicators indicating that the service change event has been resolved or ended. The first UE 411 and the second UE 413 may then switch back to their respective general PLMN selection lists and select a PLMN according to the general PLMN selection lists. Alternatively, PLMN _1 405 may resume operation, and upon detection of such a transmission, the UE served by PLMN _1 405 may switch back to PLMN _1 405 and resume normal operation. The handoff based on HPLMN transmission will be discussed in detail below.

Fig. 5 illustrates a flow diagram of example operations 500 that occur in a UE in response to an occurrence of a service change event. The operations 500 may indicate operations that occur in the UE when the UE responds to the occurrence of a service change event. The service change event may be a catastrophic event or an emergency event, as well as a special event.

The operations 500 begin with the UE receiving a service change occurrence indicator (block 505). The service change occurrence indicator may indicate that a service change event has occurred in the PLMN through an identifier included in the service change occurrence indicator. As an example, a service change event occurs in the HPLMN of the UE. The service change occurrence indicator may be received in a broadcast message, a message sent to a UE group including the UE, or a message specifically addressed to the UE. The service change occurrence indicator may also be received in a message sent over the internet or a wired network. The UE switches to the service change PLMN selection list (block 507). Switching from the normal PLMN selection list to the service change PLMN selection list after the UE receives a service change occurrence indicator indicating that a service change event has occurred.

Optionally, the UE determines its current location (block 509). As an example, a UE may measure position reference signals transmitted by access nodes located in the vicinity of the UE and determine its current position based on the measurements. As another example, the UE transmits location reference signals, and an access node located near the UE measures the location reference signals to determine the current location of the UE. The current location of the UE may be helpful in selecting a PLMN, but it may not be necessary to update the current location of the UE. The previously determined UE location may be used instead of the current location. In addition to determining the current location of the UE, the UE may also determine the time and period of the service it desires to receive. Additional knowledge of the time and period of service that the UE desires to receive may further assist the UE in considering PLMNs. As an example, if the UE desires to use a video service, the UE will not consider PLMNs that do not provide the video service.

The UE scans for a suitable PLMN (block 511). The UE scans for signals transmitted by access nodes of PLMNs located in the vicinity of the UE. For example, signals received by the UE may be used to identify a PLMN, and potentially the relative signal strength and quality of the PLMN.

The UE determines a network selection priority (block 513). The network selection priority may be determined based on the service change PLMN selection list and information included therein. Further, the network selection priority may be determined according to the service the UE intends to use and the location of the UE, the subscription level of the UE, the time of day, the service time and period, and the like. One example network selection priority may be as follows: PLMN 3, voice, access time is 4 pm to 10 pm; PLMN 4, video, and access time from 12 pm to 10 pm; PLMN2, voice, access time 4 pm to 10 pm.

The UE selects a PLMN (block 515). The UE selects a PLMN from the PLMNs that can be detected in the scanning performed in block 511. The selection of the PLMN may change the PLMN selection list according to network selection priority and service. For example, in the case where there are more than one possible PLMNs to choose from, the UE may select the PLMN that is more signaled (or better performance guarantee, better performance history, lower error rate, etc.). The UE accesses the selected PLMN (block 517). Accessing the selected PLMN may include sending one or more messages to attach to the selected PLMN. The UE may also receive one or more messages from the selected PLMN.

Fig. 6 illustrates a flow diagram of example operations 600 that occur in a network entity in response to the occurrence of a service change event. Operation 600 may indicate an operation that occurs in a network entity when the network entity responds to the occurrence of a service change event. The service change event may be a catastrophic event or an emergency event, as well as a special event. The network entity may be in a PLMN experiencing a service change event or in a PLMN in the vicinity of the PLMN experiencing a service change event. The network entity may be an access node or any other entity in the PLMN capable of detecting a service change event and communicating with other network entities.

The operations 600 begin by detecting an occurrence of a network change event from a network entity (block 605). As an example, the network entity may detect a failure in one or more network entities of the PLMN where the service change event occurred. As another example, where the network change event is a special event, the network entity may detect the occurrence of a service change event based on a time and location associated with the special event. The network entity sends a service change notification (block 607). The service change notification may be a network level message for PLMNs operating in the vicinity of the PLMN where the service change event occurred to notify those nearby PLMNs that the service change event occurred in the PLMN. For example, the service change notification may be a message with an identifier of the PLMN where the service change event occurred.

According to an example embodiment, the network selection mechanism for selecting a VPLMN upon the occurrence of a service change event is also operable when recovering from the service change event or the service change event ends. In other words, when the service change event is resolved, the network selection mechanism for selecting a VPLMN when the service change event occurs is also operable.

In an embodiment, when a service change event has been resolved or the service change event ends, the network entity sends a service change notification (upon detecting a recovery from or end of the service change event) indicating that the PLMN has resumed normal operation. The service change notification may follow, for example, a format of the service change notification indicating that a service change event occurred.

In an embodiment, the PLMN sends a service change occurrence indicator indicating that a service change event has been resolved (e.g., service change event ends) in the PLMN identified in the identifier field after receiving a service change notification indicating that the PLMN has resumed normal operation. For example, the service change occurrence indicator may follow a format of the service change occurrence indicator indicating that a service change event occurs.

In an embodiment, the UEs switch back to normal operation using their respective service change PLMN selection lists, receiving a service change notification indicating that the PLMN has resumed normal operation. For example, the UE may resume normal operation by switching back to the normal PLMN selection list.

According to an example embodiment, by organizing the service change PLMN selection list, the UE is enabled to switch back to normal operation even if the UE does not receive a service change notification indicating that the PLMN has resumed normal operation. In an embodiment, the organization service changes the PLMN selection list such that information related to the HPLMN of the UE (including services provided by the HPLMN, location of the HPLMN, subscription type, etc.) is assigned the highest priority. In case of assigning the highest priority to the HPLMN, the UE will select the HPLMN whenever the UE can detect the HPLMN.

Fig. 7 illustrates a flow diagram of example operations 700 occurring in a UE that resumes after a service change event is resolved. Operation 700 may indicate operations that occur in a UE when the UE resumes due to a service change event being resolved.

The operations 700 begin with the UE performing a check to determine whether it has received a service change occurrence indicator indicating that a service change event has been resolved (block 705). The format of the service change occurrence indicator indicating that the service change event has been resolved may be similar to the service change occurrence indicator indicating that the service change event has occurred, but the indicator is set to, for example, a different value. If the UE has received such a service change occurrence indicator, the UE resumes normal operation by deactivating service change PLMN selection (block 707) and switching back to the normal PLMN selection list (block 709).

However, even if the UE does not receive a service change occurrence indicator indicating that the service change event has been resolved, the UE may still switch back to normal operation when the UE detects transmission of the HPLMN for the UE (block 711). Since the service change PLMN selection list is organized such that the HPLMN of the UE is given the highest priority, if the UE detects a transmission from its HPLMN, the UE determines that the service change event has been resolved and the UE resumes normal operation by deactivating the service change PLMN selection (block 707) and switching back to the normal PLMN selection list (block 709).

Fig. 8 illustrates a detailed view of a communication system 800 that highlights configurations of service change PLMN lists. The communication system 800 includes a UE 805 connected to a network function 810 through a network-side interface 815. The network function 810 may be implemented in one or more network entities, either separate or collocated. The network function 810 configures the UE 805 with a normal PLMN selection list and a service change PLMN selection list. The UE 805 may store the normal PLMN selection list and the service change PLMN selection list in the memory 807. As an example, the above-mentioned normal PLMN selection list is stored in the memory 807 as a normal PLMN selection list 808, and the above-mentioned service change PLMN selection list is stored in the memory as a service change PLMN selection list 809. In the case where multiple service change PLMN selection lists are configured for the UE 805, the multiple service change PLMN selection lists may be stored in the memory 807.

Fig. 9 illustrates an example communication system 900. In general, the system 900 enables multiple wireless or wired users to send and receive data and other content. System 900 may implement one or more channel access methods such as Code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

In this example, communication system 900 includes Electronic Devices (EDs) 910a through ED910c, radio Access Networks (RANs) 920a through RAN 920b, a core network 930, a Public Switched Telephone Network (PSTN) 940, the internet 950, and other networks 960. Although a particular number of these components or elements are shown in fig. 9, any number of these components or elements may be included in system 900.

The EDs 910a through 910c are configured to operate or communicate in the system 900. For example, the EDs 910a to 910c are used for transmission or reception via a wireless communication channel or a wired communication channel. Each ED910 a to ED910c represents any suitable end user device and may include (or may be referred to as) for example the following: a user equipment or device (UE), a wireless transmit or receive unit (WTRU), a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a Personal Digital Assistant (PDA), a smart phone, a laptop computer, a tablet, a wireless sensor, or a consumer electronic device.

RAN 920a through RAN 920b herein include base stations 970a through 970b, respectively. Base stations 970 a-970 b are each configured to wirelessly connect with one or more of EDs 910 a-910 c to enable access to core network 930, PSTN 940, internet 950, or other network 960. For example, base stations 970 a-970B may include (or be) one or more of several well-known devices, such as a Base Transceiver Station (BTS), a node B (NodeB), an evolved node B (eNodeB), a Next Generation (NG) node B (gNB), a home node B, a home eNodeB, a site controller, an Access Point (AP), or a wireless router. The EDs 910a through 910c are used to connect and communicate with the internet 950 and may access a core network 930, PTSN 940, or other network 960.

In the embodiment illustrated in fig. 9, base station 970a forms a portion of RAN 920a, and RAN 920a may include other base stations, network elements, and/or devices. Base station 970b forms a portion of RAN 920b, and RAN 920b may include other base stations, network elements, and/or devices. Each base station 170 a-170 b transmits or receives wireless signals within a particular geographic area or region, sometimes referred to as a "cell. In some embodiments, each cell may have multiple transceivers, such that multiple-input multiple-output (MIMO) techniques may be used.

Base stations 970 a-970 b communicate with one or more of EDs 910 a-910 c over one or more air interfaces 990 using wireless communication links. Air interface 990 may use any suitable radio access technology.

It is contemplated that system 900 may utilize multi-channel access functionality, including such schemes as described above. In particular embodiments, the base station and the ED implement a 5G New Radio (NR), LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be used.

RANs 920 a-920 b communicate with a core network 930 to provide voice, data, applications, voice over internet protocol (VoIP), or other services to EDs 910 a-910 c. It is to be appreciated that the RAN 920 a-920 b or the core network 930 may communicate directly or indirectly with one or more other RANs (not shown). The core network 930 may also serve as a gateway access for other networks, such as PTSN 940, the internet 950, and other networks 960. Further, some or all of the EDs 910 a-910 c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of (or in addition to) wireless communication, the ED may communicate with a service provider, or a switch (not shown), and the internet 950 via a wired communication channel.

Although fig. 9 shows one example of a communication system, various changes may be made to fig. 9. For example, communication system 900 may include any number of EDs, base stations, networks, or other components in any suitable configuration.

Fig. 10A and 10B illustrate example devices that may implement methods and teachings in accordance with this disclosure. In particular, fig. 10A shows an example ED 1010 and fig. 10B shows an example base station 1070. These components may be used in system 900 or any other suitable system.

As shown in fig. 10A, ED 1010 includes at least one processing unit 1000. Processing unit 1000 implements various processing operations of ED 1010. For example, processing unit 1000 may perform signal coding, data processing, power control, input/output processing, or any other function that enables ED 1010 to operate in system 900. The processing unit 1000 also supports the methods and teachings described in detail above. Each processing unit 1000 includes any suitable processing or computing device for performing one or more operations. Each processing unit 1000 may, for example, comprise a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

The ED 1010 also includes at least one transceiver 1002. The transceiver 1002 is used to modulate data or other content for transmission over at least one antenna or Network Interface Controller (NIC) 1004. The transceiver 1002 is also used to demodulate data or other content received by the at least one antenna 1004. Each transceiver 1002 includes any suitable structure for generating wireless or wired transmitted signals or processing wireless or wired received signals. Each antenna 1004 includes any suitable structure for transmitting or receiving wireless or wired signals. One or more transceivers 1002 may be used in the ED 1010 and one or more antennas 1004 may be used in the ED 1010. Although the transceiver 1002 is shown as a single functional unit, it may be implemented using at least one transmitter and at least one separate receiver.

The ED 1010 also includes one or more input/output devices 1006 or interfaces (e.g., wired interfaces to the internet 950). The input/output devices 1006 facilitate interaction with users or other devices in the network (network communications). Each input/output device 1006 includes any suitable structure for providing information to or receiving information from a user, including network interface communications, such as a speaker, microphone, keypad, keyboard, display, or touch screen.

In addition, the ED 1010 includes at least one memory 1008. The memory 1008 stores instructions and data used, generated, or collected by the ED 1010. For example, the memory 1008 may store software or firmware instructions that are executed by the processing unit 1000 as well as data for reducing or eliminating interference in the input signal. Each memory 1008 includes any suitable volatile or non-volatile storage and retrieval device. Any suitable type of memory may be used, such as Random Access Memory (RAM), read Only Memory (ROM), hard disk, optical disk, subscriber Identity Module (SIM) card, memory stick, secure Digital (SD) memory card, and so forth.

As shown in fig. 10B, the base station 1070 includes at least one processing unit 1050, at least one transceiver 1052 (including the functionality of a transmitter and receiver), one or more antennas 1056, at least one memory 1058, and one or more input/output devices or interfaces 1066. As will be appreciated by those skilled in the art, a scheduler is coupled to the processing unit 1050. The scheduler may be included within the base station 1070 or operate separately from the base station 1070. The processing unit 1050 performs various processing operations for the base station 1070, such as signal coding, data processing, power control, input/output processing, or any other function. The processing unit 1050 may also support the methods and teachings described in detail above. Each processing unit 1050 includes any suitable processing or computing device for performing one or more operations. Each processing unit 1050 may comprise, for example, a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

Each transceiver 1052 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1052 also includes any suitable structure for processing signals received wirelessly or wiredly from one or more EDs or other devices. Although shown as combined into a transceiver 1052, the transmitter and receiver may be separate components. Each antenna 1056 includes any suitable structure for transmitting or receiving wireless or wired signals. Although one common antenna 1056 is shown herein as coupled to the transceiver 1052, one or more antennas 1056 may be coupled to the transceiver 1052, allowing separate antennas 1056 to be coupled to the transmitter and receiver if provided as separate components. Each memory 1058 includes any suitable volatile or non-volatile storage and retrieval device. Each input/output device 1066 facilitates interaction with a user or other device in the network (network communication). Each input/output device 1066 includes any suitable structure for providing information to a user or receiving/providing information from a user, including network interface communications.

FIG. 11 is a block diagram of a computing system 1100 that may be used to implement the apparatus and methods disclosed herein. For example, the computing system may be any of the following entities: UE, access Network (AN), mobility Management (MM), session Management (SM), user Plane Gateway (UPGW), or Access Stratum (AS). A particular device may use all or only a subset of the components shown, and the level of integration may vary from device to device. Moreover, an apparatus may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1100 includes a processing unit 1102. The processing unit includes a Central Processing Unit (CPU) 1114 connected to bus 1120, memory 1108, and may also include mass storage device 1104, video adapter 1110, and I/O interface 1112.

The bus 1120 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 1114 may include any type of electronic data processor. The memory 1108 may include any type of non-transitory system memory, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous DRAM (SDRAM), read Only Memory (ROM), or a combination thereof. In an embodiment, memory 1108 may include ROM for use at startup, and DRAM for program and data storage for use when executing programs.

Mass memory 1104 may include any type of non-transitory storage device for storing data, programs, and other information and enabling access to the data, programs, and other information via bus 1120. Mass storage 1104 may include, for example, one or more of the following: a solid state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive.

The video adapter 1110 and the I/O interface 1112 provide interfaces for coupling external input and output devices to the processing unit 1102. As shown, examples of input and output devices include a display 1118 coupled to the video adapter 1110 and a mouse, keyboard, or printer 1116 coupled to the I/O interface 1112. Other devices may be coupled to the processing unit 1102 and additional or fewer interface cards may be used. For example, a serial interface, such as a Universal Serial Bus (USB) (not shown), may be used to provide an interface for external devices.

The processing unit 1102 also includes one or more network interfaces 1106, which network interfaces 1106 may include wired (e.g., ethernet cables) or wireless links for access nodes or different networks. The network interface 1106 allows the processing unit 1102 to communicate with remote units via a network. For example, network interface 1106 may provide wireless communication via one or more transmitters/transmit antennas and one or more receivers/receive antennas. In an embodiment, the processing unit 1102 is coupled to a local area network 1122 or a wide area network for data processing and communication with remote devices (e.g., other processing units, the internet, or remote storage facilities).

It should be understood that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, the signal may be transmitted by a transmitting unit or a transmitting module. The signal may be received by a receiving unit or a receiving module. The signals may be processed by a processing unit or processing module. Further steps may be performed by a detecting unit or module, a switching unit or module, a scanning unit or module, a determining unit or module, an accessing unit or module, or a selecting unit or module. The individual units or modules may be hardware, software, or a combination thereof. For example, one or more of the above units or modules may be an integrated circuit, such as a Field Programmable Gate Array (FPGA) or an application-specific integrated circuit (ASIC).

Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the scope of the disclosure as defined by the appended claims.

Claims

1. A method implemented by a User Equipment (UE), the method comprising:

receiving, by the UE, one or more Service Change Network Selection Lists (SCNSLs) from a home network of the UE;

the UE detects that a service change occurrence indicator associated with the home network is set to a first specified value and, based thereon:

the UE switches from using a network selection list to using SCNSL according to the selection strategy of the UE;

the UE scans for a suitable network in the SCNSL;

the UE receiving identifiers from one or more networks in the SCNSL;

the UE determines the network selection priority according to the SCNSL; and

the UE selecting one of the one or more networks in the SCNSL according to the network selection priority;

wherein the UE detects that the service change occurrence indicator associated with the home network is set to a second specified value and, based thereon:

the UE switches to use the network selection list;

the UE scans a suitable second network in the network selection list;

receiving, by the UE, identifiers from one or more second networks in the network selection list; and

the UE selects one of the one or more second networks according to the network selection list.

2. The method of claim 1, the one or more SCNSLs being different from the network selection list.

3. The method of claim 1, the network selection priority comprising at least one of: a service of the UE, a subscription level of the UE, a current time of day, a time and period of expected service, a trigger event limit, or a service provided by the one or more networks.

4. The method of claim 3, the network selection priority further comprising a location of the UE and a time and period of service the UE is expected to receive.

5. The method of claim 4, further comprising:

the UE determines the location of the UE and a time and period of service the UE is expected to receive.

6. The method of any of claims 1-5, further comprising:

the UE accesses the one of the one or more networks.

7. The method of any of claims 1-5, the service change occurrence indicator is received from a network overlaying the UE.

8. The method of claim 7, the UE capable of receiving information from the network.

9. The method of claim 1, further comprising:

the UE accesses the one of the one or more second networks.

10. The method according to any one of claims 1-5, further comprising:

the UE receiving an identifier of the home network; and

and the UE accesses the home network.

11. The method of any of claims 1-5, the service change occurrence indicator being set to the first specified value indicating that a service change event has occurred in the home network.

12. A method implemented by a network entity, the method comprising:

the network entity detecting that a service change event has occurred on the network; and

the network entity transmitting a service change occurrence indicator associated with the network, the service change occurrence indicator set to a first specified value;

the network entity detecting that the service change event is resolved and based thereon sending the service change occurrence indicator set to a second specified value, the service change occurrence indicator set to the second specified value for causing the UE to, based thereon:

switching to using the network selection list;

scanning for a suitable second network in the network selection list;

receiving identifiers from one or more second networks in the network selection list; and

selecting one of the one or more second networks according to the network selection list.

13. The method of claim 12, the network entity receiving the service change event from a centralized management entity.

14. The method of claim 12, the service change event comprising at least one of: an emergency event occurring in the network, or a special event occurring in the network.

15. The method of any of claims 12-14, the service change occurrence indicator is sent in a broadcast message or a unicast message in response to a query.

16. The method of claim 12, the second specified value indicates that the service change event has been resolved.

17. The method of any of claims 12-14, the first specified value indicating that the service change event occurred.

18. A User Equipment (UE), comprising:

a non-transitory memory comprising instructions; and

one or more processors in communication with the memory, wherein the one or more processors execute the instructions to:

receiving one or more Service Change Network Selection Lists (SCNSLs) from a home network of the UE;

detecting that a service change occurrence indicator associated with the home network is set to a first specified value, and based thereon:

switching from using a network selection list to using SCNSL according to the selection strategy of the UE;

scanning for a suitable network in the SCNSL;

receiving identifiers from one or more networks in the SCNSL;

determining a network selection priority according to the SCNSL; and

selecting one of the one or more networks in the SCNSL according to the network selection priority;

wherein the one or more processors are further to execute the instructions to:

detecting that the service change occurrence indicator associated with the home network is set to a second specified value, and based thereon:

switching to using the network selection list;

scanning for a suitable second network in the network selection list;

19. The UE of claim 18, the network selection priority comprising at least one of: a service of the UE, a subscription level of the UE, a current time of day, a time and period of expected service, a trigger event limit, or a service provided by the one or more networks.

20. The UE of claim 19, the network selection priority further comprising a location of the UE and a time and period of service the UE is expected to receive.

21. The UE of claim 20, the one or more processors to further execute the instructions to:

determining the location of the UE and a time and period of service the UE is expected to receive.

22. The UE of any of claims 18-21, the one or more processors to further execute the instructions to:

accessing the one of the one or more networks.

23. The UE of any one of claims 18-21, the one or more processors to further execute the instructions to:

receiving an identifier of the home network; and

and accessing the home network.

24. A network entity, comprising:

a non-transitory memory comprising instructions; and

detecting that a service change event has occurred on the network; and

sending a service change occurrence indicator associated with the network, the service change occurrence indicator set to a first specified value;

wherein the one or more processors are further to execute the instructions to:

detecting that the service change event is resolved, and based thereon sending the service change occurrence indicator set to a second specified value, the service change occurrence indicator set to the second specified value for causing the UE to, based thereon:

switching to using the network selection list;

scanning for a suitable second network in the network selection list;

25. The network entity of claim 24, the one or more processors further execute the instructions to:

receiving the service change event from a centralized management entity.

26. The network entity of claim 24, the service change event comprising at least one of: an emergency event occurring in the network, or a special event occurring in the network.