Network selection in non-terrestrial networks

Abstract

The present disclosure relates to network selection in a non-terrestrial network. A user equipment (UE) is configured to: receive broadcast information from a public land-based mobile network (PLMN) including at least a PLMN identifier (ID); attempt to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station deployed in a non-terrestrial network (NTN) arrangement operated by the PLMN, the NTN arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receive a message including a cause code indicating that the PLMN is not allowed to operate at the current UE location and also including a set of attributes indicating additional conditions under which registration with the PLMN is not allowed; and refrain from making additional registration attempts with the PLMN when the additional conditions are met.

Description

[0001] Priority Claim / Incorporation by Reference

[0002] This patent application claims priority to U.S. Provisional Application Serial No. 63 / 201,763, filed on May 12, 2021, and entitled “Network Selection in a Non-Terrestrial Network,” which is incorporated herein by reference in its entirety. Background Art

[0003] A user equipment (UE) can establish a connection with at least one of multiple different networks or network types. Signaling between the UE and the network can be achieved via beamforming. Beamforming is an antenna technique used to transmit a directional signal, which can be called a beam.

[0004] A non-terrestrial network (NTN) is a network that utilizes non-terrestrial components (e.g., one or more satellites) to provide UEs with access to a public land-based mobile network (PLMN) (e.g., a PLMN operating a 5G New Radio (NR) radio access network (RAN)). Satellite-based NTNs can provide extensive network coverage across diverse regions. For example, the beams used by satellites can have large coverage areas that span regional boundaries. Due to legal or regulatory reasons, PLMNs may be restricted from providing network access in specific areas. Summary of the Invention

[0005] Some example embodiments relate to a processor of a user equipment (UE) configured to perform operations including: receiving broadcast information from a public land-based mobile network (PLMN) including at least a PLMN identifier (ID); attempting to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station deployed in a non-terrestrial network (NTN) arrangement operated by the PLMN, the NTN arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receiving a message including a cause code indicating that the PLMN is not allowed to operate at a current UE location and also including a set of attributes indicating additional conditions under which registration with the PLMN is not allowed; and refraining from making additional registration attempts with the PLMN when the additional conditions are met.

[0006] Other exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations including: receiving broadcast information from a public land-based mobile network (PLMN) including at least a PLMN identifier (ID); attempting to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station deployed in a non-terrestrial network (NTN) arrangement operated by the PLMN, the NTN arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receiving a registration rejection including a cause code indicating that the PLMN is not allowed to operate at the current UE location; determining additional conditions under which registration with the PLMN is not allowed, wherein the additional conditions are determined based on default geographic information defining an area within which the UE should not attempt the additional registration attempts; and refraining from making additional registration attempts with the PLMN when the additional conditions are met.

[0007] Additional exemplary embodiments relate to a processor of a base station configured to perform operations including: broadcasting information including at least a public land-based mobile network (PLMN) identifier (ID) from a PLMN, wherein the base station is deployed in a non-terrestrial network (NTN) arrangement including a non-terrestrial component configured to provide service to a user equipment (UE) via a serving link; receiving a registration request for the PLMN from the UE; determining a current UE location; determining that the PLMN is not permitted to operate at the current UE location; and transmitting a message to the UE including a cause code indicating that the PLMN is not permitted to operate at the current UE location. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0009] Figure 2 An exemplary non-terrestrial network (NTN) architecture is shown in accordance with various exemplary embodiments.

[0010] Figure 3 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0011] Figure 4 An exemplary base station is shown in accordance with various exemplary embodiments.

[0012] Figure 5 An exemplary beam coverage scenario is shown where the coverage provided by the satellite crosses the borders of a country where PLMN operation is permitted.

[0013] Figure 6 Methods for network selection according to various exemplary embodiments described herein are shown. DETAILED DESCRIPTION

[0014] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which similar elements have the same reference numerals. The exemplary embodiments are described with reference to user equipment (UE). However, reference to the UE is provided for illustrative purposes only. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component. The exemplary embodiments are also described with reference to a 5G New Air (NR) network. However, reference to the 5G NR network is provided for illustrative purposes only. The exemplary embodiments may be utilized with any network that can establish a connection with the UE and exchange information and data with the UE.

[0015] Example embodiments are described with reference to a 5G NR network integrated with a non-terrestrial network (NTN) that utilizes one or more satellites to provide UEs with access to the 5G NR radio access network (RAN). Satellite-based NTNs can provide broad network coverage across diverse regions where network providers (e.g., public land mobile networks (PLMNs)) may be restricted from providing network access in specific areas due to legal or regulatory reasons. According to some aspects described herein, the network can provide a geographical indication to the UE so that the UE will avoid attempting to access the PLMN. This indication can be provided to the UE in a registration rejection transmitted via satellite when the UE attempts to access the PLMN. This indication can also be provided in a service rejection or deregistration request transmitted from the PLMN.

[0016] In one aspect, the network transmission may indicate that the UE should not attempt to access the geographic area of ​​a particular PLMN. In another aspect, the UE may be provided with a list of unique beam or cell identifiers on which the UE should avoid attempting access. In this way, the UE can reduce unnecessary network access attempts that will continue to be rejected until the UE changes its location to an area where network access on the PLMN is allowed.

[0017] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. It should also be understood that an actual network arrangement can include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.

[0018] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 can also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), long term evolution RAN, traditional cellular network, WLAN, etc.), and UE 110 can also communicate with the network via a wired connection. With respect to the exemplary embodiment, UE 110 can establish a connection with 5G NR RAN 120. Therefore, UE 110 can have a 5G NR chipset to communicate with NR RAN 120.

[0019] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, cells or base stations (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0020] In the network arrangement 100, the 5G NR RAN 120 includes a base station (e.g., gNB 120A) representing a gNB in ​​a non-terrestrial network (NTN) deployment. For example, a satellite-based system can be integrated with the 5G NR RAN 120 to provide network access to the UE 110.

[0021] Figure 2 An exemplary non-terrestrial network (NTN) architecture 200 is shown in accordance with various exemplary embodiments. NTN may refer to any network that uses non-terrestrial components, such as satellites, aircraft, unmanned aerial vehicles (UAVs), etc., to provide network services to user terminals.

[0022] The NTN architecture 200 represents a network arrangement that includes one or more satellites 215 integrated with a data network 205. The data network 205 may be, for example, a satellite or a network device as described above with respect to a satellite or a network device. Figure 1 The 5G NR RAN 120 is depicted. The NTN architecture 200 includes a gateway 210 that connects the terrestrial data network 205 with the NTN components. Figure 2 In the NTN architecture 200, gateways 210 and satellites 215 communicate via feeder links 225. However, any number of satellites 215 may communicate with any number of gateways 210 via any number of corresponding feeder links 225. For example, in some NTN deployments, some satellites may be served by several gateways simultaneously.

[0023] Satellite 215 provides network services to UE 220 via service link 230. Satellite 215 can implement either a transparent payload or a regenerative payload. A transparent payload refers to an arrangement in which satellite 215 receives a signal and transmits an amplified version of that signal using frequency conversion. For example, satellite 215 may receive uplink communications from a UE on the service link 230 frequency and transmit an amplified version of the signal to network 205 on the feeder link 225 frequency, or it may receive downlink communications from network 205 on the feeder link 235 frequency and transmit an amplified version of the signal to UE 215 on the service link 230 frequency. A regenerative payload refers to an arrangement in which satellite 215 acts as a distributed unit (DU) or base station (e.g., gNB), where the received signal is regenerated using signal processing techniques (e.g., demodulation, decoding, switching, encoding, modulation, etc.) before retransmission. Satellite 215 generates one or more beams within its service area defined by its field of view, depending on the satellite's 215 antenna pattern and minimum elevation angle. The beam's footprint 235 is typically elliptical.

[0024] refer to Figure 1 In a regenerative payload arrangement, the gNB 120A may be located on an aerial component (e.g., Figure 2 In a transparent payload arrangement, gNB 120A may be located on the ground, and satellite 215 is used to mirror signals between gNB 120 and UE 110, as described above.

[0025] Figure 2 The examples shown are not intended to limit the exemplary embodiments in any way. Those skilled in the art will understand that the NTN can be integrated with the 5G NR RAN and / or other networks in any of a variety of ways. For example, a typical satellite-based NTN may include a low earth orbit (LEO) constellation that includes a series of satellites and gateways with extensive interconnectivity via ground-to-ground station (G2G) links, satellite-to-satellite (S2S) links, ground-to-satellite (G2S) links, and satellite-to-ground (S2G) links. Other types of satellite-based NTNs include geostationary earth orbit (GEO) satellites or medium earth orbit (MEO) satellites. Different types of NTNs each have corresponding advantages and disadvantages and can be deployed in a variety of scenarios, depending on the goals to be achieved, for example, wide coverage across large areas, concentrated coverage in urban environments, or along routes with high passenger traffic. Therefore, Figure 2 The NTN architecture 200 described in FIG. 2 is provided for illustration purposes only.

[0026] return Figure 1In the network arrangement 100, the gNB 120A may include one or more communication interfaces to exchange data and / or information with the UE 110, the corresponding RAN, the cellular core network 130, the Internet 140, etc.

[0027] UE 110 may connect to 5G NR-RAN 120 via gNB 120A. Those skilled in the art will appreciate that any relevant procedures may be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 may be associated with a particular cellular provider, where UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 may transmit corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 may associate with a particular cell (e.g., gNB 120A). However, as described above, reference to 5G NR-RAN 120 is for illustrative purposes only, and any suitable type of RAN may be used.

[0028] In addition to the 5G NR RAN 120, 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 can be considered an interconnected collection of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0029] Figure 3 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 110. The UE 110 may include a processor 305, a memory arrangement 310, a display device 315, an input / output (I / O) device 320, a transceiver 325, and other components 330. The other components 330 may include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, and the like.

[0030] The processor 305 may be configured to execute a number of engines of the UE 110. For example, these engines may include a network access restriction engine 335 configured to perform operations including determining whether the UE should attempt to access the network based on information provided by the network. For example, based on geographic information or beam / cell information, the UE may avoid attempting to register with the network until the UE is located in an area where access to the network is permitted, as will be described in further detail below.

[0031] The engine described above as an application (e.g., a program) executed by the processor 305 is merely exemplary. The functionality associated with the engine may also be represented as a separate, integrated component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 305 is shared between two or more processors, such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0032] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 315 may be a hardware component configured to display data to a user, and the I / O device 320 may be a hardware component that enables user input. The display device 315 and the I / O device 320 may be separate components or may be integrated together (such as a touch screen). The transceiver 325 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN (not shown in the figure), traditional RAN (not shown in the figure), WLAN (not shown in the figure), etc. Therefore, the transceiver 325 can operate on a plurality of different frequencies or channels (e.g., a continuous frequency group).

[0033] Figure 4 An exemplary base station, e.g., gNB 120A, is shown in accordance with various exemplary embodiments. gNB 120A may represent any access node through which UE 110 may establish a connection and manage network operations.

[0034] The gNB 120A may include a processor 405, a memory arrangement 410, an input / output (I / O) device 415, a transceiver 420, and other components 425. Other components 425 may include, for example, a battery, data acquisition devices, ports for electrically connecting the base station to other electronic devices, and the like.

[0035] Processor 405 may be configured to execute multiple engines of gNB 120A. For example, processor 405 of gNB 120A may execute network access engine 430, which may cause gNB 120A to perform operations including rejecting a network access attempt when the UE is located in an area where the network cannot provide network service. Network access engine 430 may further be configured to provide the UE with additional information regarding the geographic area and / or cell / beam in which the UE should avoid further access attempts, as described in further detail below. However, reference to processor 405 is merely exemplary. Functionality associated with the engines may also be represented as standalone, integrated components of gNB 120A or as modular components coupled to gNB 120A, such as integrated circuits with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some base stations, the functionality described for processor 405 is split across multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of a base station.

[0036] Memory 410 may be a hardware component configured to store data related to operations performed by gNB 120A. I / O device 415 may be a hardware component or port that enables a user to interact with gNB 120A. Transceiver 420 may be a hardware component configured to exchange data with UE 110 and any other UEs in system 100. Transceiver 420 may operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies). Thus, transceiver 420 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0037] When a UE detects information broadcast from the network (including, for example, a PLMN ID including a Mobile Country Code (MCC) and a Mobile Network Code (MNC)), the UE may attempt to access a public land-based mobile network (PLMN), e.g., register with the network. The UE may then initiate registration by transmitting a registration request to the PLMN. In some scenarios, the NTN deployed by the PLMN may provide beam coverage, where the beams span regional boundaries. Figure 5 An exemplary beam coverage scenario is shown in which the coverage provided by the satellite crosses the border of a country where PLMN operation is permitted. This scenario may be referred to as cross-border leakage. However, due to regulatory or legal restrictions, other scenarios may arise in which PLMN beams may cross the border of an area where PLMN operation is permitted. Therefore, those skilled in the art will appreciate that the exemplary embodiments are not limited to cross-border leakage scenarios.

[0038] The PLMN may reject a registration attempt from a UE when the UE is located in a geographic location where the network is not permitted to provide services due to regulatory or legal restrictions. When the PLMN is not permitted to provide any services to the UE, a reason code may be included in the Registration Rejection, such as Reason Code #78, meaning "PLMN is not permitted to operate at the current UE location." A Registration Rejection may be in response to an Initial Registration Request or a Mobility Registration Request.

[0039] A PLMN may be allowed to operate only within the geographical boundaries of the country for the PLMN's MCC. The International Telecommunication Union (ITU) Telecommunication Standardization Sector (ITU-T) has allowed some exceptions to this general rule, such as in areas adjacent to borders, and in some cases, may allow a PLMN to operate in a foreign country (i.e., a country where the MCC assigned to it by the ITU-T is different from the MCC broadcast by the PLMN). However, this type of access is generally restricted.

[0040] To assist the UE in selecting a PLMN permitted to operate at the current UE location, the UE may utilize a map providing the boundaries between countries to which the ITU assigns MCCs, in conjunction with a database storing which PLMNs (defined by the combination of the network-broadcast MCC and Mobile Network Code (MNC)) are permitted to operate in which countries. However, as discussed above, these boundaries may not be rigid. It may be assumed that there are certain areas / strips on each side of the boundary where PLMNs in one country are permitted to operate in adjacent countries.

[0041] Even when such maps and databases are available to the UE, the UE may attempt to register to a PLMN outside its legal coverage, for example if the UE has an outdated map or database, or if the UE's location determined by the network is different from the location estimated by the UE itself.

[0042] Regardless of the reason why a UE may attempt PLMN access outside the legal operating area of ​​a PLMN, it is the operator's responsibility to ensure that service is not provided outside the country / area where the network is permitted to operate. Therefore, the network should reject the registration request accordingly.

[0043] If the network rejects the UE with a new cause #78, "PLMN not allowed to operate at the current UE location," it would be useful to provide the UE with some criteria regarding the area (near the current UE location) where UE registration attempts will continue to be rejected. In this way, the UE will be prevented from making further registration attempts, which will again be rejected by the network. Without such criteria, the UE may continue to attempt to register with the PLMN, wasting UE processing power and / or battery life. This information may also provide the UE with some guidance as to where new registration attempts are likely to succeed. Thus, when the UE has moved to a new location where PLMN operation is allowed, the UE can again attempt to access the PLMN.

[0044] According to various exemplary embodiments described herein, the network may provide the UE with a set of attributes for a new rejection cause #78, "PLMN not allowed to operate at current UE location," that indicate when and where restrictions on re-registration attempts apply. The cause code and associated attributes may also be indicated in a service rejection or deregistration request from the PLMN.

[0045] In some exemplary embodiments, the network may provide the UE with geographical information defining an area within which the UE will consider that the PLMN is not allowed to operate. This geographical information may be provided along with the rejection reason code as described above. The geographical information may be provided in one of the following forms, although this list should not be considered exhaustive. For example, the geographical information may include 1) a circle defined by a specific midpoint (latitude / longitude) and a radius; 2) a circle defined by a midpoint and a radius, where the midpoint is determined to be the current UE location that the UE will estimate / obtain; 3) an ellipse defined by the major axis, minor axis, and the latitude / longitude positions of the two foci of the ellipse; or 4) a polygon with n corners, each corner defined by a latitude / longitude position. When the UE is located in a geographical area for which the network has indicated "PLMN is not allowed to operate at the current UE location" in a registration reject, the UE should not attempt to register to that PLMN.

[0046] After receiving the geographic information, the UE will check its current location against the stored information before initiating another registration attempt on the PLMN-ID. For example, the UE may use its current Global Positioning Satellite (GPS) location, such as its latitude / longitude position, and check whether the current location falls within the restricted area. If the current UE location falls within the indicated geographic area, the UE will not attempt to register with the PLMN. If the current UE location falls outside the indicated geographic area, the UE may attempt to access the PLMN again.

[0047] The indicated geographic information may not fully capture the areas where the PLMN is not permitted to operate. For example, the indicated information may only cover a subset of the regions / countries where the PLMN is not permitted to operate. Therefore, if the UE leaves the covered area and attempts to access the PLMN again, if the new UE location is also a restricted area, the PLMN may again reject the registration attempt and send a new geographic indication for another area that the UE cannot attempt to access. Once the UE has left the legally restricted area, if the UE attempts to access the PLMN again, the registration request may be accepted.

[0048] According to other exemplary embodiments, under certain deployment conditions, geographic information may be provided as a list of globally unique beam IDs or globally unique cell IDs. For example, if the deployment is such that 1) satellite cell coverage is provided by small cells or by downlink transmit beams within a cell, where the UE will receive broadcast system information from these cells in order to detect the cell and determine which operator (i.e., PLMN) is operating the cell, and 2) the coverage area of ​​these beams is small enough to define the area where the PLMN is allowed to operate (including areas / strips beyond the borders where the PLMN is allowed to operate in neighboring countries), then geographic information may be provided in this manner. Geographic information may be provided in the following manner.

[0049] In the first option, a list of globally unique beam IDs (i.e. PLMN ID (MCC+MNC), Tracking Area ID, Cell-ID, Beam-ID) is indicated which the UE should consider as not allowing PLMN operation, i.e. the UE is not allowed to trigger a new registration attempt on this list.

[0050] In the second option, a list of globally unique cell IDs (i.e. PLMN ID (MCC+MNC), Tracking Area ID, Cell-ID) is indicated which the UE shall consider as not allowing PLMN operation, i.e. the UE is not allowed to trigger a new registration attempt on this list.

[0051] Although the UE has selected a cell or a beam of a cell for which the network has indicated in a Registration Reject that "PLMN is not allowed to operate at the current UE location", the UE should not attempt to register with that PLMN. Therefore, similar to the first exemplary embodiment, before attempting to register on a PLMN ID, the UE will check the indicated information against the PLMN information (i.e., globally unique beam ID or globally unique cell ID) and determine whether the access attempt should be restricted.

[0052] According to one variation, with respect to the first and second exemplary embodiments discussed above, the network may configure the retry restriction to apply only for a limited time period, "T_cause_78." In other words, the network may indicate a timer value, i.e., the period of T_cause_78, during which, after receiving a rejection cause, the UE considers all attributes of the received rejection to be valid. When the timer expires, the indicated attributes are considered invalid.

[0053] According to another variation, with respect to the first exemplary embodiment discussed above, some default geographic information may be provided to the UE, such as a circle with a certain radius and a midpoint defined by the current UE location (as discussed with respect to the second geographic information option discussed above). If the PLMN sending the rejection cause does not signal geographic information applicable to that particular rejection message, the UE may use the default geographic information. In a similar manner, if the UE is not provided with a T_cause_78 value applicable to a particular rejection message, a default value for T_cause_78 may also be provided to the UE.

[0054] If the UE uses / maintains a pre-existing map with the boundaries of the countries to which the ITU assigns MCCs, and has a database defining which PLMNs are allowed to operate in which countries, the UE can combine this map with the received geographical applicability with the new rejection cause "PLMN not allowed to operate at the current UE location." In this case, if there is any conflict, the information received in the rejection should take precedence over the stored map and MCC database. For example, if an area is indicated as restricted by the provided information, but not by the stored information, then the area will be considered restricted based on the provided information.

[0055] As discussed above, embodiments of the present invention provide various UE and network advantages. A UE will not attempt to register with a PLMN when located in a geographic area where the network has indicated in a registration reject that "PLMN operation is not permitted at the current UE location," thus avoiding unnecessary network load and UE power consumption. This also ensures that the UE will search for other suitable cells of the same or different PLMN, regardless of radio access technology, in order to register and regain service. Furthermore, if no other PLMN is available, exemplary embodiments help the UE avoid remaining in an out-of-service state, even if it has moved to a new location where PLMN operation is permitted.

[0056] Figure 6 A method 600 for network selection is shown according to various exemplary embodiments described herein.

[0057] In 605, a user equipment (UE) receives broadcast information from a public land-based mobile network (PLMN) including at least a PLMN identifier (ID). The PLMN ID may include a mobile country code (MCC) combined with a mobile network code (MNC). This information may be broadcast via a non-terrestrial network (NTN) beam deployed by the PLMN via satellite. The base station transmitting the broadcast information may be located on a satellite, or may be located on the ground, with the satellite acting as a relay for the base station signal.

[0058] In 610, the UE attempts to register with the PLMN by sending a registration request to the PLMN. The registration request may be an initial registration request or a mobility registration request.

[0059] In 615, the PLMN determines the current UE location and whether the PLMN is allowed to operate at the current UE location. The PLMN may restrict providing service at the current UE location for legal or regulatory reasons, eg, the PLMN is not allowed to provide service in the country where the UE is located.

[0060] At 620, the PLMN transmits a message to the UE including a cause code indicating that the PLMN is not permitted to operate at the current UE location. This message may be a registration reject message. The message may also include a set of attributes indicating additional conditions under which registration with the PLMN is not permitted. For example, geographic information defining an area in which the UE should avoid further registration attempts may be transmitted. This information may also include a list of global cell IDs or global beam IDs that the UE should avoid attempting to access. In other embodiments, the cause code and the set of attributes may be transmitted in a service reject or deregistration request from the PLMN.

[0061] When the additional conditions are met, the UE refrains from making additional registration attempts with the PLMN in 625. When the UE moves to a location where the other conditions are not met, the UE may again attempt to access the PLMN.

[0062] Example

[0063] In a first embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving broadcast information from a public land-based mobile network (PLMN) including at least a PLMN identifier (ID); attempting registration with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station deployed in a non-terrestrial network (NTN) arrangement operated by the PLMN, the NTN arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receiving a message including a cause code indicating that the PLMN is not allowed to operate at a current UE location and also including a set of attributes indicating additional conditions under which registration with the PLMN is not allowed; and refraining from making additional registration attempts with the PLMN when the additional conditions are met.

[0064] In a second embodiment, the processor according to the first embodiment, wherein the set of attributes indicates a list of globally unique beam IDs on which the UE should not attempt these additional registration attempts.

[0065] In a third embodiment, the processor according to the second embodiment, wherein each globally unique beam ID is defined by the PLMN ID, the tracking area ID, the local cell ID, and the local beam ID.

[0066] In a fourth embodiment, the processor according to the second embodiment, wherein the set of attributes indicates a list of globally unique cell IDs on which the UE should not attempt the additional registration attempts.

[0067] In a fifth embodiment, the processor according to the fourth embodiment, wherein each globally unique cell ID is defined by the PLMN ID, the tracking area ID, and the local cell ID.

[0068] In a sixth embodiment, the processor according to the first embodiment, wherein the set of attributes indicates geographical information defining an area within which the UE should not attempt the additional registration attempts.

[0069] In a seventh embodiment, the processor of the sixth embodiment wherein the geographic information comprises a circle defined by the indicated midpoint and a radius.

[0070] In an eighth embodiment, the processor of the sixth embodiment, wherein the geographic information comprises an ellipse defined by a major axis, a minor axis, and two focal positions.

[0071] In a ninth embodiment, the processor of the sixth embodiment, wherein the geographic information comprises a polygon defined by N corners, wherein each corner is defined by the indicated location.

[0072] In a tenth embodiment, the processor according to the first embodiment, wherein the non-terrestrial component comprises a satellite that provides beam coverage in areas where PLMN operation is not permitted.

[0073] In an eleventh embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a public land-based mobile network (PLMN); and a processor communicatively coupled to the transceiver and configured to perform operations including: receiving broadcast information including at least a PLMN identifier (ID) from the PLMN; attempting to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station operated by the PLMN deployed in a non-terrestrial network (NTN) arrangement, the NTN arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receiving a message including a cause code indicating that the PLMN is not allowed to operate at a current UE location and also including a set of attributes indicating additional conditions under which registration with the PLMN is not allowed; and refraining from making additional registration attempts with the PLMN when the additional conditions are met.

[0074] In a twelfth embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a public land-based mobile network (PLMN); and a processor communicatively coupled to the transceiver and configured to perform operations including: receiving broadcast information including at least a PLMN identifier (ID) from the PLMN; attempting to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station deployed in a non-terrestrial network (NTN) arrangement operated by the PLMN, the NTN arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receiving a registration reject including a cause code indicating that the PLMN is not allowed to operate at a current UE location; determining additional conditions in which registration with the PLMN is not allowed, wherein the additional conditions are determined based on default geographical information defining an area within which the UE should not attempt the additional registration attempts; and refraining from making additional registration attempts with the PLMN when the additional conditions are met.

[0075] In a thirteenth embodiment, a processor of a base station configured to perform operations comprising: broadcasting information including at least a public land-based mobile network (PLMN) identifier (ID) from a PLMN, wherein the base station is deployed in a non-terrestrial network (NTN) arrangement, the NTN arrangement including a non-terrestrial component configured to provide service to a user equipment (UE) via a serving link; receiving a registration request for the PLMN from the UE; determining a current UE location; determining that the PLMN is not permitted to operate at the current UE location; and transmitting a message to the UE, the message including a cause code indicating that the PLMN is not permitted to operate at the current UE location and also including a set of attributes indicating additional conditions under which registration with the PLMN is not permitted.

[0076] In a fourteenth embodiment, the processor according to the thirteenth embodiment, wherein the set of attributes indicates a list of globally unique beam IDs on which the UE should not attempt these additional registration attempts.

[0077] In a fifteenth embodiment, the processor according to the fourteenth embodiment, wherein each globally unique beam ID is defined by the PLMN ID, tracking area ID, local cell ID, and local beam ID.

[0078] In a sixteenth embodiment, the processor according to the thirteenth embodiment, wherein the set of attributes indicates a list of globally unique cell IDs on which the UE should not attempt the additional registration attempts.

[0079] In a seventeenth embodiment, the processor of the sixteenth embodiment, wherein each globally unique cell ID is defined by the PLMN ID, the tracking area ID, and the local cell ID.

[0080] In an eighteenth embodiment, the processor of the seventeenth embodiment wherein the geographic information comprises a circle defined by the indicated midpoint and a radius.

[0081] In a nineteenth embodiment, the processor of the seventeenth embodiment, wherein the geographic information comprises an ellipse defined by a major axis, a minor axis, and two focal positions.

[0082] In a twentieth embodiment, the processor of the seventeenth embodiment, wherein the geographic information comprises a polygon defined by N corners, wherein each corner is defined by the indicated location.

[0083] In a twenty-first embodiment, a base station includes: a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver and configured to perform operations including: broadcasting information including at least a public land-based mobile network (PLMN) identifier (ID) from a PLMN, wherein the base station is deployed in a non-terrestrial network (NTN) arrangement including a non-terrestrial component configured to provide service to the UE via a serving link; receiving a registration request for the PLMN from the UE; determining a current UE location; determining that the PLMN is not permitted to operate at the current UE location; and transmitting a message to the UE, the message including a cause code indicating that the PLMN is not permitted to operate at the current UE location and also including a set of attributes indicating additional conditions under which registration with the PLMN is not permitted.

[0084] In a twenty-second embodiment, the base station of the twenty-first embodiment, wherein the message further includes a set of attributes indicating additional conditions under which registration with the PLMN is not permitted.

[0085] In a twenty-third embodiment, the base station according to the twenty-second embodiment, wherein the set of attributes indicates geographical information defining an area within which the UE should not attempt the additional registration attempts.

[0086] In a twenty-fourth embodiment, the base station according to the twenty-third embodiment, wherein the geographic information includes a circle defined by a radius, wherein the UE determines a midpoint based on the current UE position.

[0087] In a twenty-fifth embodiment, the base station according to the twenty-third embodiment, wherein the geographical information includes default geographical information defining an area within which the UE should not attempt the additional registration attempts.

[0088] In a twenty-sixth embodiment, according to the base station of the twenty-fifth embodiment, the default geographic information includes a circle with a default radius.

[0089] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0090] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of one embodiment may be combined with features of other embodiments in any manner not publicly denied, or with features that are not functionally or logically inconsistent with the operation or described function of the device of the embodiments disclosed herein.

[0091] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0092] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A computer-readable storage medium having instructions stored thereon that, when executed by a processor of a user equipment (UE), cause the processor to perform operations comprising: receiving broadcast information from a public land mobile network (PLMN) including at least a PLMN identifier (ID); attempting to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station operated by the PLMN deployed in a non-terrestrial network (NTN) arrangement, the NTN arrangement utilizing non-terrestrial components and configured to provide service to the UE via a serving link; receiving a message including a cause code indicating that the PLMN is not allowed to operate at a current UE location; storing the PLMN ID of the PLMN together with a set of attributes indicating further conditions under which registration with the PLMN is not permitted, the set of attributes including geographical information defining an area within which the UE should not attempt further registration attempts with the PLMN; as well as When the further condition is met, further registration attempts to the PLMN are avoided, wherein determining whether the further condition is met comprises at least comparing a UE location with the geographical information. 2 . The computer-readable storage medium of claim 1 , wherein the geographic information comprises a circle defined by a radius, wherein the UE determines a midpoint based on the current UE location.

3. The computer-readable storage medium of claim 1 , wherein the operations further comprise: Determine updated UE location; checking the updated UE location against the geographic information; as well as When the updated UE location falls within the defined area, further registration attempts are avoided.

4. The computer-readable storage medium of claim 1 , wherein the operations further comprise: Determine updated UE location; checking the updated UE location against the geographic information; as well as When the updated UE location falls outside the defined area, attempting to register with the PLMN by sending the registration request to the PLMN.

5. The computer-readable storage medium of claim 1, wherein the message further comprises a timer value indicating a duration for which the UE should refrain from making the additional registration attempts with the PLMN when the additional condition is met.

6. The computer-readable storage medium of claim 1 , wherein the UE uses pre-existing geographic information defining an area within which the UE should not attempt the additional registration attempt, wherein the set of attributes indicates geographic information defining an additional area within which the UE should not attempt the additional registration attempt, wherein the operations further comprise: When the indicated geographic information conflicts with the previously existing geographic information, the indicated geographic information is used.

7. The computer-readable storage medium of claim 1, wherein the message is a registration rejection, a service rejection, or a deregistration request.

8. A user equipment (UE), comprising: a transceiver configured to communicate with a network; as well as a processor communicatively coupled to the transceiver, wherein the processor is configured to perform operations comprising: receiving broadcast information from a public land mobile network (PLMN) including at least a PLMN identifier (ID); attempting to register with the PLMN by sending a registration request to the PLMN, wherein the UE attempts the registration via a base station operated by the PLMN deployed in a non-terrestrial network (NTN) arrangement, the NTN arrangement utilizing non-terrestrial components and configured to provide service to the UE via a serving link; receiving a message including a cause code indicating that the PLMN is not allowed to operate at a current UE location; storing the PLMN ID of the PLMN together with a set of attributes indicating further conditions under which registration with the PLMN is not permitted, the set of attributes including geographical information defining an area within which the UE should not attempt further registration attempts with the PLMN; as well as When the further condition is met, further registration attempts to the PLMN are avoided, wherein determining whether the further condition is met comprises at least comparing a UE location with the geographical information.

9. The UE of claim 8, wherein the geographic information comprises a circle defined by a radius, wherein the UE determines a midpoint based on the current UE location.

10. The UE according to claim 8, wherein the operations further comprise: Determine updated UE location; checking the updated UE location against the geographic information; as well as When the updated UE location falls within the defined area, further registration attempts are avoided.

11. The UE according to claim 8, wherein the operations further comprise: Determine updated UE location; checking the updated UE location against the geographic information; as well as When the updated UE location falls outside the defined area, attempting to register with the PLMN by sending the registration request to the PLMN.

12. The UE of claim 8, wherein the message further comprises a timer value indicating a duration for which the UE should refrain from making the further registration attempt with the PLMN when the further condition is met.

13. The UE of claim 8 , wherein the UE uses pre-existing geographic information defining an area within which the UE should not attempt the additional registration attempt, wherein the set of attributes indicates geographic information defining an additional area within which the UE should not attempt the additional registration attempt, wherein the operations further comprise: When the indicated geographic information conflicts with the previously existing geographic information, the indicated geographic information is used. The UE according to claim 8 , wherein the message is a registration reject, a service reject, or a deregistration request.

Images