LOCATION BASED NETWORK ACCESS MANAGEMENT

Abstract

There are provided measures for location based network access management. Such measures exemplarily comprise receiving a rejection message indicative of rejection of access of said mobile terminal to a first mobile network, checking for a cause of said rejection of access of said mobile terminal to said first mobile network, and affecting, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, a selection of a second mobile network to be accessed based on a content of said rejection message.

Description

FIELD

Various example embodiments relate to location based network access management. More specifically, various example embodiments exemplarily relate to measures (including methods, apparatuses and computer program products) for realizing location based network access management.

BACKGROUND

The present specification generally relates to network selection, and thus, network access control, in cross-border scenarios.

In cross-border scenarios in which a mobile terminal located in one country may (attempt to) access mobile networks of other countries, several challenges are raised.

One example posing such cross-border scenarios is utilization of satellite access in Third Generation Partnership Project (3GPP) 5G.

FIGS. 7 and 8 show schematic diagrams of examples of a system environment utilizing satellite access, respectively.

In particular, FIG. 7 illustrates a scenario of utilizing satellite access with satellite beams overlapping several countries.

Further, FIG. 8 illustrates a scenario of utilizing a satellite backhaul with satellite beams overlapping several countries.

Telecommunication regulations of the country in which a user equipment (UE) is physically located can be expected to be applicable to that UE's telecommunications operator. Some relaxations in regulations may be unavoidable, but the fewer relaxations that need to be negotiated, the better for speedy deployment.

System complexities can be expected when a satellite's coverage crosses country borders and/or the UE's communications use terrestrial equipment (e.g. earth stations) that are in a different country to the UE, as is illustrated in FIG. 7, in which the UE itself utilizes the satellite's coverage.

A similar situation may arise with the use of satellite backhaul. A satellite transport would in this case interconnect a RAN with a SCN. The satellite's coverage could overlap more than one country, as is illustrated in FIG. 8, in which a radio access network (RAN) to which the UE is connected utilizes the satellite's coverage for backhauling.

For both satellite access and satellite backhaul situations, it is generally foreseen to address some points in relation to these challenges as follows.

These challenges are summarizes below.

Namely, on the one hand, it was to be clarified how to ensure, when required, that the UE is using a core network of the country in which the UE is physically located.

Further, on the other hand, it was to be clarified how to select a core network when the UE is in an aeronautical or maritime location. Still further, it was to be clarified how to enable per-country, UE specific prohibition of satellite access, if the satellite system is using a same mobile country code and mobile network code (MCC+MNC) in multiple countries. Still further, it was to be clarified how to route an emergency call to the correct public safety answering point (PSAP). Still further, it was to be clarified how to handle lawful interception (LI). Still further, it was to be clarified how to address a public warning system (PWS). Finally, it was to be clarified how to handle charging and tariff notifications.

As mentioned above, to address some points in relation to these challenges, it is generally foreseen that if a UE is attempting to register to a public mobile land network (PLMN) that it is not allowed to access in the present UE location (e.g. PLMN of different country than the present UE location), an access and mobility management function (AMF) responds with REGISTRATION REJECT, including a suitable cause value to tell the UE that the selected PLMN is not allowed in the present UE location. Based on the UE location, the AMF may also include a hint of a country code (MCC, mobile country code) or a list of PLMN codes (MCC+MNC) or a list of PLMN and radio access technology (RAT) codes (MCC+MNC+RAT).

When evaluating whether the UE is allowed to access the selected PLMN, the AMF may take into account that the UE is allowed to access 90× satellite MCC in multiple countries.

In order to ensure the call being routed to a PSAP of the country of the UE location, the AMF shall take the same approach if the UE is requesting emergency registration in a country that is different from the UE location.

After REGISTRATION REJECT indicating that the PLMN is not allowed in the present UE location, the UE in automatic PLMN selection mode may attempt to select another PLMN, using the hint received from the rejecting PLMN (received from the rejecting AMF regarding the not allowed PLMN), and the UE may memorize the PLMN that is not allowed in the present county for as long as the UE remains in that country. A UE in manual PLMN selection mode may behave as normal, i.e., may remain camping on cell in limited service state after REGISTRATION REJECT. If necessary, a new cause value telling the user the reason for no service might be added.

FIG. 9 shows a schematic diagram of signaling sequences.

In particular, FIG. 9 illustrates a basic call flow following the above-outlined general way foreseen to address some points in relation to the above-explained challenges.

In step 1 of FIG. 9, a UE transmits a request (e.g. registration request) towards an AMF.

In step 2 of FIG. 9, the AMF detects that the UE is not allowed to access the network (corresponding to the registration request) from the current location of the UE.

In step 3 of FIG. 9, the AMF transmits a reject message to the UE, wherein the reject message may include network selection assistance information.

In step 4 of FIG. 9, the UE performs a network selection based on the received network selection assistance information.

The network selection assistance information refers to a country code (MCC), a list of PLMN codes (MCC+MNC), or a list of PLMN+RAT codes (MCC+MNC+RAT) sent from the AMF to the UE as described e.g. in 3GPP TR 23.737.

In principle, the network selection procedure in the UE may also be steered by other information sent from the network to the UE as part of a registration reject, a deregistration request or a service reject message. In addition, the above principles are not limited to the case of satellite coverage exemplified above.

The above-outlined foreseen approaches are rather general and provide a basic framework.

However, the above-outlined foreseen approaches do not provide any implementation details of how to provide for efficient network selection and network access control in cross-border scenarios.

Hence, the problem arises that measures allowing efficient network selection and network access control in cross-border scenarios is not provided for yet. Accordingly, the above-outlined challenges entailed by such scenarios are not yet tackled.

Hence, there is a need to provide for a location based network access management tackled the above-outlined challenges entailed by such scenarios.

SUMMARY

Various example embodiments aim at addressing at least part of the above issues and/or problems and drawbacks.

Various aspects of example embodiments are set out in the appended claims.

According to an example aspect, there is provided a method of a mobile terminal, the method comprising receiving a first message indicative of rejection of access of said mobile terminal to a first mobile network, checking for a cause of said rejection of access of said mobile terminal to said first mobile network, examining, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message, and affecting, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message.

According to an example aspect, there is provided a method of an access and mobility management function entity, the method comprising determining a location of a mobile terminal, ascertaining whether said mobile terminal is allowed to access to a first mobile network from said location of said mobile terminal, and transmitting, if said mobile terminal is not allowed to access to said first mobile network from said location of said mobile terminal, a first message indicative of rejection of access of said mobile terminal to said first mobile network.

According to an example aspect, there is provided an apparatus of a mobile terminal, the apparatus comprising receiving circuitry configured to receive a first message indicative of rejection of access of said mobile terminal to a first mobile network, checking circuitry configured to check for a cause of said rejection of access of said mobile terminal to said first mobile network, examining circuitry configured to examine, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message, and affecting circuitry configured to affect, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message.

According to an example aspect, there is provided an apparatus of an access and mobility management function entity, the apparatus comprising determining circuitry configured to determine a location of a mobile terminal, ascertaining circuitry configured to ascertain whether said mobile terminal is allowed to access to a first mobile network from said location of said mobile terminal, and transmitting circuitry configured to transmit, if said mobile terminal is not allowed to access to said first mobile network from said location of said mobile terminal, a first message indicative of rejection of access of said mobile terminal to said first mobile network.

According to an example aspect, there is provided an apparatus of a mobile terminal, the apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a first message indicative of rejection of access of said mobile terminal to a first mobile network, checking for a cause of said rejection of access of said mobile terminal to said first mobile network, examining, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message, and affecting, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message.

According to an example aspect, there is provided an apparatus of an access and mobility management function entity, the apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform determining a location of a mobile terminal, ascertaining whether said mobile terminal is allowed to access to a first mobile network from said location of said mobile terminal, and transmitting, if said mobile terminal is not allowed to access to said first mobile network from said location of said mobile terminal, a first message indicative of rejection of access of said mobile terminal to said first mobile network.

According to an example aspect, there is provided a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present disclosure), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related exemplary aspects of the present disclosure.

Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computer-executable computer program code is stored, and/or the program may be directly loadable into an internal memory of the computer or a processor thereof.

Any one of the above aspects provide implementation details of how to provide for efficient network selection and network access control in cross-border scenarios to thereby solve at least part of the problems and drawbacks identified in relation to the prior art.

By way of example embodiments, there is provided location based network access management. More specifically, by way of example embodiments, there are provided measures and mechanisms for realizing location based network access management.

Thus, improvement is achieved by methods, apparatuses and computer program products enabling/realizing location based network access management.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, the present disclosure will be described in greater detail by way of non-limiting examples with reference to the accompanying drawings, in which

FIG. 1 is a block diagram illustrating an apparatus according to example embodiments,

FIG. 2 is a block diagram illustrating an apparatus according to example embodiments,

FIG. 3 is a block diagram illustrating an apparatus according to example embodiments,

FIG. 4 is a block diagram illustrating an apparatus according to example embodiments,

FIG. 5 is a schematic diagram of a procedure according to example embodiments,

FIG. 6 is a schematic diagram of a procedure according to example embodiments,

FIG. 7 shows a schematic diagram of an example of a system environment utilizing satellite access,

FIG. 8 shows a schematic diagram of an example of a system environment utilizing satellite access,

FIG. 9 shows a schematic diagram of signaling sequences,

FIG. 10 shows a schematic diagram of signaling sequences according to example embodiments,

FIG. 11 shows a schematic diagram of signaling sequences according to example embodiments,

FIG. 12 shows a schematic diagram of signaling sequences according to example embodiments,

FIG. 13 shows a schematic diagram of signaling sequences according to example embodiments,

FIG. 14 shows a schematic diagram of signaling sequences according to example embodiments,

FIG. 15 shows a schematic diagram of signaling sequences according to example embodiments,

FIG. 16 shows a schematic diagram of signaling sequences according to example embodiments, and

FIG. 17 is a block diagram alternatively illustrating apparatuses according to example embodiments.

DETAILED DESCRIPTION

The present disclosure is described herein with reference to particular non-limiting examples and to what are presently considered to be conceivable embodiments. A person skilled in the art will appreciate that the disclosure is by no means limited to these examples, and may be more broadly applied.

It is to be noted that the following description of the present disclosure and its embodiments mainly refers to specifications being used as non-limiting examples for certain exemplary network configurations and deployments. Namely, the present disclosure and its embodiments are mainly described in relation to 3GPP specifications being used as non-limiting examples for certain exemplary network configurations and deployments. As such, the description of example embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the disclosure in any way. Rather, any other communication or communication related system deployment, etc. may also be utilized as long as compliant with the features described herein.

In particular, the present disclosure and its embodiments may be applicable in any network scenario in which network elements may not be allowed to access networks for some reason (in particular the location of the respective network element).

Hereinafter, various embodiments and implementations of the present disclosure and its aspects or embodiments are described using several variants and/or alternatives. It is generally noted that, according to certain needs and constraints, all of the described variants and/or alternatives may be provided alone or in any conceivable combination (also including combinations of individual features of the various variants and/or alternatives).

According to example embodiments, in general terms, there are provided measures and mechanisms for (enabling/realizing) location based network access management.

Example embodiments provide details regarding which messages can be used to indicate that the UE is not allowed to access the PLMN from the present location.

Further, example embodiments provide details regarding UE behaviors upon receiving the message (indicating that the UE is not allowed to access the PLMN from the present location) from the network.

Still further, example embodiments provide details regarding the behavior of a UE not supporting network selection assistance information.

Furthermore, example embodiments provide details regarding keeping the network selection assistance information in the UE.

Moreover, example embodiments provide details regarding handling a message including network selection assistance information that is not integrity protected.

Finally, example embodiments provide details regarding prioritization of PLMN and RAT combinations aligned/matched with the UE's location (UE location information) during manual network selection.

Principles according to the present disclosure are explained below.

FIG. 1 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a terminal 10 such as a user equipment UE comprising a receiving circuitry 11, a checking circuitry 12, an examining circuitry 13, and an affecting circuitry 14. The receiving circuitry 11 receives a first message indicative of rejection of access of said mobile terminal to a first mobile network. The checking circuitry 12 checks for a cause of said rejection of access of said mobile terminal to said first mobile network. The examining circuitry 13 examines, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message. The affecting circuitry 14 affects, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message. FIG. 5 is a schematic diagram of a procedure according to example embodiments. The apparatus according to FIG. 1 may perform the method of FIG. 5 but is not limited to this method. The method of FIG. 5 may be performed by the apparatus of FIG. 1 but is not limited to being performed by this apparatus.

As shown in FIG. 5, a procedure according to example embodiments comprises an operation of receiving (S51) a first message indicative of rejection of access of said mobile terminal to a first mobile network, an operation of checking (S52) for a cause of said rejection of access of said mobile terminal to said first mobile network, an operation of examining (S53), if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message, and an operation of affecting (S54), if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message.

FIG. 2 is a block diagram illustrating an apparatus according to example embodiments. In particular, FIG. 2 illustrates a variation of the apparatus shown in FIG. 1. The apparatus according to FIG. 2 may thus further comprise a detecting circuitry 21, a considering circuitry 22, an ignoring circuitry 23, a performing circuitry 24, a sending circuitry 25, a deprioritizing circuitry 26, a prioritizing circuitry 27, a displaying circuitry 28, and/or a disabling circuitry 29.

In an embodiment at least some of the functionalities of the apparatus shown in FIG. 1 (or 2) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.

According to a variation of the procedure shown in FIG. 5, exemplary additional operations and exemplary details of the examining operation (S53) are given, which are inherently independent from each other as such. According to such variation, such exemplary examining operation (S53) according to example embodiments may comprise an operation of detecting whether said first message is integrity protected. Further, an exemplary method according to example embodiments may comprise, if said first message is not integrity protected, an operation of considering said first message as invalid, and an operation of ignoring said first message.

According to a variation of the procedure shown in FIG. 5, exemplary additional operations and exemplary details of the examining operation (S53) are given, which are inherently independent from each other as such. According to such variation, such exemplary examining operation (S53) according to example embodiments may comprise an operation of detecting whether said first message is received via a Third-Generation-Partnership-Project access. Further, an exemplary method according to example embodiments may comprise, if said first message is not received via a Third-Generation-Partnership-Project access, an operation of considering said first message as invalid, and an operation of performing abnormal case handling for said first message.

According to a variation of the procedure shown in FIG. 5, exemplary additional operations and exemplary details of the examining operation (S53) are given, which are inherently independent from each other as such. According to such variation, such exemplary examining operation (S53) according to example embodiments may comprise an operation of detecting whether said first message is received via standalone non-public network. Further, an exemplary method according to example embodiments may comprise, if said first message is received via a standalone non-public network, an operation of considering said first message as invalid, and an operation of performing abnormal case handling for said first message.

According to a variation of the procedure shown in FIG. 5, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of sending a second message including information implying a present location of said mobile terminal and/or an indication whether said mobile terminal supports mobile network selection based on information provided by an access and mobility management function entity. Here, said first message is a response to said second message.

According to further example embodiments, said first message is a registration reject message, a service reject message, or a deregistration request message.

According to further example embodiments, said second message is a registration request message or a service request message.

According to further example embodiments, said information implying a present location of said mobile terminal includes at least one of

• • coordinates detected utilizing a global navigation satellite system,
  • a cell identifier of a radio cell said mobile terminal is connected to, and
  • a list of received mobile network identifiers, each respective mobile network identifier being associated with an indication of a respective signal strength detected when receiving said respective received mobile network identifier.

According to a variation of the procedure shown in FIG. 5, exemplary details of the affecting operation (S54) are given, which are inherently independent from each other as such. Such exemplary affecting operation (S54) according to example embodiments may comprise an operation of deprioritizing, in candidate mobile networks, said first mobile network or a mobile network of a country to which said first mobile network belongs, and an operation of selecting said second mobile network from said candidate mobile networks.

According to a variation of the procedure shown in FIG. 5, exemplary details of the affecting operation (S54) are given, which are inherently independent from each other as such. Here, said first message includes network selection assistance information. Such exemplary affecting operation (S54) according to example embodiments may comprise an operation of considering said network selection assistance information as a basis for said selection.

According to a variation of the procedure shown in FIG. 5, exemplary details of the considering operation are given, which are inherently independent from each other as such. Here, said network selection assistance information comprises information on mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal. Such exemplary considering operation according to example embodiments may comprise an operation of deprioritizing, in candidate mobile networks, said mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal, and an operation of selecting said second mobile network from said candidate mobile networks.

According to a variation of the procedure shown in FIG. 5, exemplary details of the considering operation are given, which are inherently independent from each other as such. Here, said network selection assistance information comprises information on mobile networks to which said mobile terminal is allowed to access from said determined location of said mobile terminal. Such exemplary considering operation according to example embodiments may comprise an operation of prioritizing, in candidate mobile networks, said mobile networks to which said mobile terminal is allowed to access from said determined location of said mobile terminal, and an operation of selecting said second mobile network from said candidate mobile networks.

According to a variation of the procedure shown in FIG. 5, exemplary details of the deprioritizing operation are given, which are inherently independent from each other as such. Such exemplary deprioritizing operation according to example embodiments may comprise an operation of displaying each of said mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal associated with an indication that said mobile terminal is not allowed to access from said determined location of said mobile terminal.

According to a variation of the procedure shown in FIG. 5, exemplary details of the prioritizing operation are given, which are inherently independent from each other as such. Such exemplary prioritizing operation according to example embodiments may comprise an operation of displaying each of said mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal associated with an indication that said mobile terminal is allowed to access from said determined location of said mobile terminal.

According to a variation of the procedure shown in FIG. 5, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of disabling said network selection assistance information, if a predetermined network selection assistance information endurance condition is satisfied.

FIG. 3 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network node 30 such as an access and mobility management function entity AMF comprising a determining circuitry 31, an ascertaining circuitry 32, and a transmitting circuitry 33. The determining circuitry 31 determines a location of a mobile terminal. The ascertaining circuitry 32 ascertains whether said mobile terminal is allowed to access to a first mobile network from said location of said mobile terminal. The transmitting circuitry 33 transmits, if said mobile terminal is not allowed to access to said first mobile network from said location of said mobile terminal, a first message indicative of rejection of access of said mobile terminal to said first mobile network. FIG. 6 is a schematic diagram of a procedure according to example embodiments. The apparatus according to FIG. 3 may perform the method of FIG. 6 but is not limited to this method. The method of FIG. 6 may be performed by the apparatus of FIG. 3 but is not limited to being performed by this apparatus.

As shown in FIG. 6, a procedure according to example embodiments comprises an operation of determining (S61) a location of a mobile terminal, an operation of ascertaining (S62) whether said mobile terminal is allowed to access to a first mobile network from said location of said mobile terminal, and an operation of transmitting (S63), if said mobile terminal is not allowed to access to said first mobile network from said location of said mobile terminal, a first message indicative of rejection of access of said mobile terminal to said first mobile network.

FIG. 4 is a block diagram illustrating an apparatus according to example embodiments. In particular, FIG. 4 illustrates a variation of the apparatus shown in FIG. 3. The apparatus according to FIG. 4 may thus further comprise a receiving circuitry 41, a generating circuitry 42, an including circuitry 43, and/or a checking circuitry 44.

In an embodiment at least some of the functionalities of the apparatus shown in FIG. 3 (or 4) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.

According to a variation of the procedure shown in FIG. 6, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of receiving, from said mobile terminal, a second message including information implying a present location of said mobile terminal, and an operation of determining said location based on said information implying said present location of said mobile terminal. Here, said first message is a response to said second message.

According to further example embodiments, said information implying a present location of said mobile terminal includes at least one of

• • coordinates detected utilizing a global navigation satellite system,
  • a cell identifier of a radio cell said mobile terminal is connected to, and
  • a list of mobile network identifiers received by said mobile terminal, each respective mobile network identifier being associated with an indication of a respective signal strength detected when receiving said respective received mobile network identifier.

According to a variation of the procedure shown in FIG. 6, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of generating network selection assistance information based on said information implying a present location of said mobile terminal, and an operation of including said selection assistance information into said first message.

According to further example embodiments, said network selection assistance information comprises information on mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal.

Alternatively, according to further example embodiments, said network selection assistance information comprises information on mobile networks to which said mobile terminal is allowed to access from said determined location of said mobile terminal.

According to a variation of the procedure shown in FIG. 6, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of checking whether said second message includes an indication that said mobile terminal supports mobile network selection based on information provided by said access and mobility management function entity, an operation of including, if said second message includes said indication that said mobile terminal supports mobile network selection based on information provided by an access and mobility management function entity, a cause of said rejection of access of said mobile terminal to said first mobile network to said first message, wherein said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from said determined location of said mobile terminal, and an operation of including, if said first message does not include said indication that said mobile terminal supports mobile network selection based on information provided by an access and mobility management function entity, said cause of said rejection of access of said mobile terminal to said first mobile network to said first message, wherein said cause of said rejection of access of said mobile terminal to said first mobile network is not indicative of that said mobile terminal is not allowed to access to said first mobile network from said determined location of said mobile terminal.

According to further example embodiments, said second message is a registration request message or a service request message.

According to further example embodiments, said first message is a registration reject message, a service reject message, or a deregistration request message.

Example embodiments are explained below in more specific terms. In detail, according to example embodiments, in addition to the REGISTRATION REJECT message, the SERVICE REJECT message and the DEREGISTRATION REQUEST message are enhanced so that they can be used to indicate that the UE is not allowed to access a certain PLMN from the present UE location. In other words, according to example embodiments, a cause value indicating that the UE is not allowed to access a certain PLMN from the present UE location is added to the REGISTRATION REJECT message, the SERVICE REJECT message, and the DEREGISTRATION REQUEST message.

Namely, during the idle mode, a UE could have crossed the border while still being registered to the same PLMN. In this case, when the UE sends a SERVICE REQUEST message to transition to the connected mode, according to example embodiments, the service request is rejected with an indication that the UE is not allowed to access the PLMN at the present location.

FIG. 10 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 10, the UE transmits a SERVICE REQUEST message to the AMF. In the present example embodiment, the message contains a list of PLMNs in the vicinity of the UE, each of which is optionally associated with a signal strength.

According to example embodiments, the UE provides its location as coordinates using GNSS to the network, or the network fetches the UE location if possible. According to further example embodiments, the UE scans for PLMN IDs that are broadcasted from base stations in its vicinity, optionally together with the signal strength or other information the UE has available, and sends a corresponding list to the network (AMF).

In step 2 of FIG. 10, the AMF detects that the UE is not allowed to access the network from the current (UE's) location.

In step 3 of FIG. 10, the AMF transmits a SERVICE REJECT message.

The SERVICE REJECT message includes network selection assistance information.

In step 4 of FIG. 10, the UE performs a network selection based on the network selection assistance information.

It may take some time for the network to fetch the location of the UE or, for signaling load management, the network can delay some location procedures. As such, the network would not be able to immediately respond to the request received from the UE and to at the same time react to the lack of allowance of the UE to connect to a specific PLMN.

In view thereof, according to example embodiments, the network is able to trigger de-registration of the UE with the indication that the UE is not allowed to access the PLMN at the present location (e.g. as soon as such mismatch was detected).

FIG. 11 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 11 the AMF detects that the UE is not allowed to access the network from the current (UE's) location.

In step 2 of FIG. 11, the AMF transmits a DEREGISTRATION REQUEST (DEREGISTRATION REJECT) message.

The DEREGISTRATION REQUEST (DEREGISTRATION REJECT) message includes network selection assistance information.

In step 3 of FIG. 11, the UE performs a network selection based on the network selection assistance information.

According to example embodiments in relation to detailed UE behaviors upon receiving the message (indicating that the UE is not allowed to access the PLMN from the present location) from the network, the UE performs abnormal case handling when a message as described above is e.g. received via non-3GPP access, via a standalone non-public network (SNPN), or via a closed access group cell. These cases do not limit example embodiments. Rather, such behavior may be applied also in other abnormal cases.

According to example embodiments, the UE sets the 5G system (5GS) update status to 5U3 ROAMING NOT ALLOWED.

According to example embodiments, the UE enters the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally 5GMM-(DE)REGISTERED.PLMN-SEARCH.

According to example embodiments, the UE can then select a new PLMN based on the received network selection assistance information, e.g. a PLMN where the PLMN ID contains a certain MCC.

FIG. 12 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 12, the AMF transmits a REGISTRATION REJECT message or SERVICE REJECT message or DEREGISTRATION REQUEST message as explained above.

The message includes network selection assistance information.

In step 2 of FIG. 12, the UE performs an abnormal case handling when the message is e.g. received via non-3GPP access, via an SNPN, or view a closed access group cell. The UE sets the 5GS update status to 5U3 ROAMING NOT

ALLOWED. The UE may enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally 5GMM-(DE)REGISTERED.PLMN-SEARCH.

According to example embodiments in relation to the behavior of a UE not supporting network selection assistance information, the UE indicates whether it supports network selection assistance information. If the UE indicates that it does not support network selection assistance information, the network uses another existing 5GMM cause value (e.g. cause value “#13, roaming not allowed in this tracking area”) instead of the cause value according to example embodiments as explained above to indicate that the UE is not allowed to access the PLMN from the current location.

According to example embodiments, the UE then behaves as defined for this cause value (e.g. for cause value “#13, roaming not allowed in this tracking area”), e.g. scans for a new PLMN or de-registers from the network.

FIG. 13 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 13, the UE transmits a REGISTRATION REQUEST message (or SERVICE REQUEST message) to the AMF.

The message includes an indication whether the UE supports network selection assistance information.

In step 2 of FIG. 13, the AMF, if the UE has indicated that it does not support network selection assistance information (i.e., if the UE has not indicated that it supports network selection assistance information), the network uses another existing 5GMM cause value (e.g. cause value “#13, roaming not allowed in this tracking area”) instead of the cause value according to example embodiments as explained above to indicate that the UE is not allowed to access the PLMN from the current location.

In step 3 of FIG. 13, the AMF transmits a REGISTRATION REJECT message or a SERVICE REJECT message or a DEREGISTRATION REQUEST message indicative of the another existing 5GMM cause value (e.g. cause value “#13, roaming not allowed in this tracking area”).

According to example embodiments in relation to keeping the network selection assistance information in the UE, the current PLMN and PLMN(s) corresponding to the network selection assistance information is avoided during the next PLMN selection process only under the assumption that the network selection assistance information is blacklist-based. If the network selection assistance information is whitelist-based, according to example embodiments, only PLMN(s) corresponding to the network selection assistance information are allowed during the next PLMN selection process. According to further example embodiments, the UE has an implementation-specific timer to manage how long such information (the current PLMN and network selection assistance information) can be kept in the UE. In this case the information can be used for multiple PLMN selection processes.

FIG. 14 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 14, the AMF transmits a REGISTRATION REJECT message or SERVICE REJECT message or DEREGISTRATION REQUEST message as explained above.

The message includes network selection assistance information.

In step 2 of FIG. 14, the UE performs network selection based on the network selection assistance information. Here, the current PLMN and PLMN(s) corresponding to the network selection assistance information is avoided during the next PLMN selection process only under the assumption that the network selection assistance information is blacklist-based. If the network selection assistance information is whitelist-based, only PLMN(s) corresponding to the network selection assistance information are allowed during the next PLMN selection process. The UE can have an implementation-specific timer to manage how long such information (the current PLMN and network selection assistance information) can be kept in the UE.

According to example embodiments in relation to handling a message including network selection assistance information that is not integrity protected, non-integrity protected messages indicating that the UE is not allowed to access the PLMN from the present location are ignored by the UE.

FIG. 15 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 15, the AMF transmits a REGISTRATION REJECT message or SERVICE REJECT message or DEREGISTRATION REQUEST message as explained above.

The message includes network selection assistance information.

In step 2 of FIG. 15, the UE ignores the message (REGISTRATION REJECT message or SERVICE REJECT message or DEREGISTRATION REQUEST message) indicating that the UE is not allowed to access the PLMN from the present location, if the message (REGISTRATION REJECT message or SERVICE REJECT message or DEREGISTRATION REQUEST message) is a non-integrity protected message.

According to example embodiments in relation to prioritization of PLMN and RAT combinations aligned/matched with the UE's location (UE location information) during manual network selection, the UE displays an indication to the user whether the available PLMNs are aligned/matching with the network selection assistance information using free text.

According to further example embodiments, the UE displays the country name together with the available and allowed PLMN(s). The country name displayed to the user is set based on the MCC of the PLMN and the configured information in the UE (information available in the mobile equipment (ME) which could be obtained via the network identity and time zone (NITZ) mechanism or be configured on the universal subscriber identity module (USIM)).

FIG. 16 shows a schematic diagram of signaling sequences according to example embodiments considering the above.

In step 1 of FIG. 16, the AMF transmits a REGISTRATION REJECT message or SERVICE REJECT message or DEREGISTRATION REQUEST message as explained above.

The message includes network selection assistance information.

In step 2 of FIG. 16, the UE performs network selection based on the network selection assistance information. Here, the UE displays an indication to the user whether the available PLMNs are aligned/matching with the network selection assistance information using free text. Alternatively, the UE displays the country name together with the available and allowed PLMN(s). The country name displayed to the user is set based on the MCC of the PLMN and the configured information in the UE.

Example embodiments are specified below in other words.

These example embodiments substantially related to UE and network behavior are specified below exemplarily with the existing specifications (in particular 3GPP TS 24.501, 3GPP TS 23.122) as baseline, but are not to be understood as limiting.

Initial Registration not Accepted by the Network

Network Behavior

According to example embodiments, if the registration is rejected because the UE attempted to register to the PLMN which the UE is not allowed to access in the present location and the UE indicated that it supports network selection assistance information, if such an indication mechanism (i.e. the UE indicates whether it supports network selection assistance information during the registration procedure) is made available, the AMF sets the 5GMM cause value in the REGISTRATION REJECT message to a value indicating that the reason for the rejection is due to UE location (e.g. the cause value could be “#xx (PLMN not allowed in the present location)”) and may include information that can be used for network selection, called “network selection assistance information”, in the REGISTRATION REJECT message.

According to further example embodiments, if the UE can indicate whether it supports network selection assistance information, if the registration is rejected by the network because the UE attempted to register to a PLMN which the UE is not allowed to access in the present location and the UE did not indicate that it supports network selection assistance information, the network rejects the registration with a 5GMM cause value other than the above-mentioned 5GMM cause indicating that the reason for the rejection is due to UE location, e.g. with cause value “#13 (Roaming not allowed in this tracking area)”. According to example embodiments, the exact cause value to be used can be defined by the operator.

Initial Registration not Accepted by the Network

UE Behavior

According to example embodiments, the UE takes the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message. In particular, according to example embodiments, the UE takes the following actions if the 5GMM cause value received in the REGISTRATION REJECT message is the 5GMM cause indicating that the reason for the rejection is due to UE location (e.g. “#xx (PLMN not allowed in the present location)”):

If the REGISTRATION REJECT message with this cause value is received without integrity protection, then the UE discards the message.

If this cause value is received via non-3GPP access, an SNPN, or a closed access group cell (or in other abnormal cases), this is considered as an abnormal case and the behavior of the UE is specified in bullet c) of subclause 5.5.1.2.7 in 3GPP TS 24.501.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2 of 3GPP TS 24.501) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall delete the list of equivalent PLMNs (if available) and reset the registration attempt counter.

The UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally 5GMM-DEREGISTERED.PLMN-SEARCH. The UE can then select a new PLMN based on the received network selection assistance information, e.g. a PLMN where the PLMN ID contains a certain MCC.

According to example embodiments, if the UE is registered in S1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in subclause 4.8.3 of 3GPP TS 24.501. Otherwise, the UE performs a PLMN selection according to 3GPP TS 23.122. The UE shall not consider the current PLMN as an available PLMN during the PLMN selection (or more specifically when estimating PLMNs applicable for bullets i), ii), iii) of clause 4.4.3.1.1 in 3GPP TS 23.122). In addition, if the REGISTRATION REQUEST message includes network selection assistance information and the network selection assistance information contains one or more PLMNs, then the UE shall not consider the PLMN(s) as available PLMN(s) during the PLMN selection (or more specifically when estimating PLMNs applicable for bullets i), ii), iii) of clause 4.4.3.1.1 in 3GPP TS 23.122). Alternatively, if the REGISTRATION REQUEST message includes network selection assistance information and the network selection assistance information contains one or more MCCs, then the UE shall not consider PLMN(s) including the MCC(s) as available PLMN(s) during the PLMN selection (or more specifically when estimating PLMNs applicable for bullets i), ii), iii) of clause 4.4.3.1.1 in 3GPP TS 23.122).

According to example embodiments, if the UE needs to perform manual PLMN selection, the UE indicates to the user whether the available PLMNs are aligned with the network selection assistance information.

According to example embodiments, the UE remembers the current PLMN and the network selection assistance information for implementation-specific time for PLMN selections.

Mobility and Periodic Registration Update not Accepted by the Network

According to example embodiments, the network and the UE show almost the same network and UE behavior compared to the initial registration explained above (“Initial registration not accepted by the network”).

Two key differences according to example embodiments are that the UE needs to enter 5GMM-REGISTERED.PLMN-SEARCH state, and that the abnormal case handling is specified in bullet c) of subclause 5.5.1.3.7 in 3GPP TS 24.501.

Network-Initiated De-Registration Procedure Completed by the UE

Network Behavior

According to example embodiments, if the UE needs to be de-registered because the UE is registered to the PLMN which the UE is not allowed to access in the present location and the UE indicated that it supports network selection assistance information, if such an indication mechanism (i.e. the UE indicates whether it supports network selection assistance information during the registration procedure) is made available, the AMF sets the 5GMM cause value in the DEREGISTRATION REQUEST message to a value indicating that the reason for the de-registration is due to UE location (e.g. “#xx (PLMN not allowed in the present location)”) and may include information that can be used for network selection in the DEREGISTRATION REQUEST message.

According to further example embodiments, if the UE can indicate whether it supports network selection assistance information, the network behaves as follows. Based on operator policy, if the UE needs to be de-registered because the UE is registered to the PLMN which the UE is not allowed to access in the present location and the UE indicated that it does not support network selection assistance information (did not indicate that it supports network selection assistance information), the network sends a de-registration request with a 5GMM cause value other than the above-mentioned 5GMM cause indicating that the reason for the rejection is due to UE location, e.g. with cause value “#13 (Roaming not allowed in this tracking area)”.

Network-Initiated De-Registration Procedure Completed by the UE

UE Behavior

According to example embodiments, the UEs show almost the same UE behavior compared to the initial registration explained above (“Initial registration not accepted by the network”).

Two key differences according to example embodiments are that the UE needs to enter 5GMM-DEREGISTERED.PLMN-SEARCH state, and that the abnormal case handling is specified in bullet b) of subclause 5.5.2.3.4 in 3GPP TS 24.501.

Service Request Procedure not Accepted by the Network

According to example embodiments, the network and the UE show almost the same network and UE behavior compared to the initial registration explained above (“Initial registration not accepted by the network”).

Four key differences according to example embodiments are that the request is not a registration request but a service request, that the reject message is the SERVICE REJECT message not the REGISTRATION REJECT message, that the UE needs to enter 5GMM-REGISTERED.PLMN-SEARCH state, and that the abnormal case handling is specified in bullet i) of subclause 5.6.1.7 in 3GPP TS 24.501.

The above-described procedures and functions may be implemented by respective functional elements, processors, or the like, as described below.

In the foregoing exemplary description of the network entity, only the units that are relevant for understanding the principles of the disclosure have been described using functional blocks. The network entity may comprise further units that are necessary for its respective operation. However, a description of these units is omitted in this specification. The arrangement of the functional blocks of the devices is not construed to limit the disclosure, and the functions may be performed by one block or further split into sub-blocks.

When in the foregoing description it is stated that the apparatus, i.e. network entity (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression “unit configured to” is construed to be equivalent to an expression such as “means for”).

In FIG. 17, an alternative illustration of apparatuses according to example embodiments is depicted. As indicated in FIG. 17, according to example embodiments, the apparatus (terminal) 10′ (corresponding to the terminal comprises a processor 171, a memory 172 and an interface 173, which are connected by a bus 174 or the like. Further, according to example embodiments, the apparatus (network node) 30′ (corresponding to the network node 30) comprises a processor 175, a memory 176 and an interface 177, which are connected by a bus 178 or the like, and the apparatuses may be connected via link 179, respectively.

The processor 171/175 and/or the interface 173/177 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively. The interface 173/177 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively. The interface 173/177 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.

The memory 172/176 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the example embodiments.

In general terms, the respective devices/apparatuses (and/or parts thereof) may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.

When in the subsequent description it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression “processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as “means for xxx-ing”).

According to example embodiments, an apparatus representing the terminal 10 comprises at least one processor 171, at least one memory 172 including computer program code, and at least one interface 173 configured for communication with at least another apparatus. The processor (i.e. the at least one processor 171, with the at least one memory 172 and the computer program code) is configured to perform receiving a rejection message indicative of rejection of access of said mobile terminal to a first mobile network (thus the apparatus comprising corresponding means for receiving), to perform prohibiting modification of an information tag included in a second system information block to be broadcasted, said information tag being indicative of a change of said list (thus the apparatus comprising corresponding means for prohibiting), and to perform affecting, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, a selection of a second mobile network to be accessed based on a content of said rejection message (thus the apparatus comprising corresponding means for affecting).

According to example embodiments, an apparatus representing the network node 30 comprises at least one processor 175, at least one memory 176 including computer program code, and at least one interface 177 configured for communication with at least another apparatus. The processor (i.e. the at least one processor 175, with the at least one memory 176 and the computer program code) is configured to perform ascertaining whether a mobile terminal is allowed to access to a first mobile network from a determined location of said mobile terminal (thus the apparatus comprising corresponding means for ascertaining), and to perform transmitting, if said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, a rejection message indicative of rejection of access of said mobile terminal to said first mobile network (thus the apparatus comprising corresponding means for transmitting).

For further details regarding the operability/functionality of the individual apparatuses, reference is made to the above description in connection with any one of FIGS. 1 to 17, respectively.

For the purpose of the present disclosure as described herein above, it should be noted that

• • method steps likely to be implemented as software code portions and being run using a processor at a network server or network entity (as examples of devices, apparatuses and/or modules thereof, or as examples of entities including apparatuses and/or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;
  • generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;
  • method steps and/or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;
  • devices, units or means (e.g. the above-defined network entity or network register, or any one of their respective units/means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus like the user equipment and the network entity/network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.

In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.

Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure. Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.

Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.

The present disclosure also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.

In view of the above, there are provided measures for location based network access management. Such measures exemplarily comprise receiving a rejection message indicative of rejection of access of said mobile terminal to a first mobile network, checking for a cause of said rejection of access of said mobile terminal to said first mobile network, and affecting, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, a selection of a second mobile network to be accessed based on a content of said rejection message.

Even though the disclosure is described above with reference to the examples according to the accompanying drawings, it is to be understood that the disclosure is not restricted thereto. Rather, it is apparent to those skilled in the art that the present disclosure can be modified in many ways without departing from the scope of the inventive idea as disclosed herein.

LIST OF ACRONYMS AND ABBREVIATIONS

• 3GPP Third Generation Partnership Project
• 5GMM 5GS mobility management
• 5G system
• AMF access and mobility management function
• CR change request
• GNSS global navigation satellite system
• GUTI globally unique temporary identity
• LI lawful interception
• MCC mobile country code
• MCC+MNC mobile country code and mobile network code
• ME mobile equipment
• MNC mobile network code
• ngKSI next generation key set identifier
• NITZ network identity and time zone
• PDU protocol data unit
• PLMN public mobile land network
• PLMN ID PLMN identity
• PSAP public safety answering point
• PWS public warning system
• RAN radio access network
• RAT radio access technology
• SNPN standalone non-public network
• TAI tracking area identity
• TR technical report
• TS technical specification
• UE user equipment
• USIM universal subscriber identity module

Claims

1-49. (canceled)

50. An apparatus of a mobile terminal, the apparatus comprising: at least one processor,at least one memory including computer program code, andthe at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus at least to: receive a first message comprising an indication of rejection of access of said mobile terminal to a first mobile network;check the indication for a cause of said rejection of access of said mobile terminal to said first mobile network;examine, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message, andaffect, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message.

51. The apparatus according to claim 50, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to: examine, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message by: detecting whether said first message is integrity protected;if said first message is not integrity protected: considering said first message as invalid; andignoring said first message.

52. The apparatus according to claim 50, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to: examine, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message by: detecting whether said first message is received via a Third-Generation-Partnership-Project access; if said first message is not received via a Third-Generation-Partnership-Project access:considering said first message as invalid; andperforming abnormal case handling for said first message.

53. The apparatus according to claim 50, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to: examine, if said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from a determined location of said mobile terminal, validity of said first message by: detecting whether said first message is received via standalone non-public network; andif said first message is received via a standalone non-public network: considering said first message as invalid, andperforming abnormal case handling for said first message.

54. The apparatus according to claim 50, wherein sending a second message including information implying a present location of said mobile terminal and/or an indication whether said mobile terminal supports mobile network selection based on information provided by an access and mobility management function entity, whereinsaid first message is a response to said second message.

55. The apparatus according to claim 50, wherein said first message is a registration reject message, a service reject message, or a deregistration request message.

56. The apparatus according to claim 55, wherein said second message is a registration request message or a service request message.

57. The method according to claim 54, wherein said information implying a present location of said mobile terminal includes at least one of: coordinates detected utilizing a global navigation satellite system;a cell identifier of a radio cell said mobile terminal is connected to; anda list of received mobile network identifiers, each respective mobile network identifier being associated with an indication of a respective signal strength detected when receiving said respective received mobile network identifier.

58. The apparatus according to claim 50, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to affect, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message by: deprioritizing, in candidate mobile networks, said first mobile network or a mobile network of a country to which said first mobile network belongs, andselecting said second mobile network from said candidate mobile networks.

59. The apparatus according to claim 50, wherein said first message includes network selection assistance information, and wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to affect, if said first message is considered valid, a selection of a second mobile network to be accessed based on a content of said first message by: considering said network selection assistance information as a basis for said selection.

60. The apparatus according to claim 59, wherein said network selection assistance information comprises information on mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal, wherein said considering comprises: deprioritizing, in candidate mobile networks, said mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal, andselecting said second mobile network from said candidate mobile networks.

61. The apparatus according to claim 59, wherein said network selection assistance information comprises information on mobile networks to which said mobile terminal is allowed to access from said determined location of said mobile terminal, wherein said considering comprises: prioritizing, in candidate mobile networks, said mobile networks to which said mobile terminal is allowed to access from said determined location of said mobile terminal; andselecting said second mobile network from said candidate mobile networks.

62. The apparatus according to claim 60, wherein said deprioritizing comprises: displaying each of said mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal associated with an indication that said mobile terminal is not allowed to access from said determined location of said mobile terminal.

63. The apparatus according to claim 61, wherein said prioritizing comprises displaying each of said mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal associated with an indication that said mobile terminal is allowed to access from said determined location of said mobile terminal.

64. The apparatus according to claim 59, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to disable said network selection assistance information, if a predetermined network selection assistance information endurance condition is satisfied.

65. An access and mobility management function entity, the access and mobility management function entity comprising: at least one processor;at least one memory;wherein the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to at least: determine a location of a mobile terminal,ascertain whether said mobile terminal is allowed to access to a first mobile network from said location of said mobile terminal, andtransmit, if said mobile terminal is not allowed to access to said first mobile network from said location of said mobile terminal, a first message indicative of rejection of access of said mobile terminal to said first mobile network.

66. The access and mobility management function entity according to claim 65, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus to at least: receive, from said mobile terminal, a second message including information implying a present location of said mobile terminal, wherein said first message is a response to said second message, and the method further comprisesdetermine said location based on said information implying said present location of said mobile terminal.

67. The access and mobility management function entity according to claim 66, wherein said information implying a present location of said mobile terminal includes at least one of: coordinates detected utilizing a global navigation satellite system;a cell identifier of a radio cell said mobile terminal is connected to; ora list of mobile network identifiers received by said mobile terminal, each respective mobile network identifier being associated with an indication of a respective signal strength detected when receiving said respective received mobile network identifier.

68. The access and mobility management function entity according to claim 66, further comprising: generating network selection assistance information based on said information implying a present location of said mobile terminal, andincluding said selection assistance information into said first message.

69. The access and mobility management function entity according claim 68, wherein said network selection assistance information comprises at least one of: information on mobile networks to which said mobile terminal is not allowed to access from said determined location of said mobile terminal or information on mobile networks to which said mobile terminal is allowed to access from said determined location of said mobile terminal.

70. The access and mobility management function entity according to claim 66, wherein the at least one processor, with the at least one memory and the computer program code, are further configured to cause the apparatus at least to: check whether said second message includes an indication that said mobile terminal supports mobile network selection based on information provided by said access and mobility management function entity,include, if said second message includes said indication that said mobile terminal supports mobile network selection based on information provided by an access and mobility management function entity, a cause of said rejection of access of said mobile terminal to said first mobile network to said first message, wherein said cause of said rejection of access of said mobile terminal to said first mobile network is indicative of that said mobile terminal is not allowed to access to said first mobile network from said determined location of said mobile terminal, andinclude, if said first message does not include said indication that said mobile terminal supports mobile network selection based on information provided by an access and mobility management function entity, said cause of said rejection of access of said mobile terminal to said first mobile network to said first message, wherein said cause of said rejection of access of said mobile terminal to said first mobile network is not indicative of that said mobile terminal is not allowed to access to said first mobile network from said determined location of said mobile terminal.

71. The access and mobility management function entity according to claim 66, wherein said second message is a registration request message or a service request message.

72. The access and mobility management function entity according to claim 65, wherein said first message is a registration reject message, a service reject message, or a deregistration request message.