Redirecting user equipment to non-public mobile network

Abstract

A first system may be provided in a public mobile network, and a second system may be provided in a non-public mobile network, which may cooperate to selectively redirect user equipment from the public mobile network to the non-public mobile network. This redirection may be accomplished by the first system commanding the base station (s) within or near the coverage area of the non-public mobile network in turn commanding the user equipment to perform measurements on radio frequencies used by the non-public mobile network. In this way, the user equipment may be commanded to listen on the radio frequency used by the non-public mobile network, and if the user equipment is in the coverage area of the non-public mobile network, the user equipment may switch and connect to the non-public mobile network and thereby benefit from enhanced service and / or additional coverage. Advantageously, a user may not need to manually search for a non-public mobile network, or may not need to have pre-configured user equipment for a non-public mobile network.

Description

Technical Field

[0001] The present invention relates to a system for redirecting a user equipment from a public mobile network to a non-public mobile network. The present invention further relates to a computer-implemented method performed on a corresponding system, to an apparatus representing a user equipment, and to a computer-implemented method performed on the apparatus. The present invention further relates to a computer-readable medium comprising data for causing a processor system to perform the computer-implemented method. Background Art

[0002] Recent telecommunications standards provide support for non-public networks (NPNs), a typical example of which is a private network. Such non-public networks can take various forms, for example, as standalone non-public mobile networks (SNPNs), which refer to non-public networks operated by an NPN operator and do not rely on the network functionality provided by a public land mobile network (PLMN), or as public network integrated non-public networks (PNI-NPNs), which refer to non-public networks that can be deployed with the support of a public network. It is desirable for user equipment (UE) to be able to dynamically switch between public and non-public networks, where both types of networks are referred to elsewhere as 'mobile' networks. For example, non-public mobile networks can be deployed in venues such as museums, stadiums, conference centers, or any other cultural, sporting, or commercial venues to provide enhanced services or additional coverage to their visitors. Non-limiting examples of enhanced services include locally enhancing high-demand services, such as by providing support for "Video, Imaging, and Audio for Professional Applications" (VIAPA), as described in 3GPP TR 23.700-07.

[0003] However, in order to be able to use enhanced services or additional coverage, the UE may need to switch to a non-public mobile network when the UE is near a venue or attending an event. However, the non-public mobile network may not know the identity of the UE because the UE may not have subscribed to the non-public mobile network. There are several reasons behind this. First, it may be difficult to predict that the user will visit a specific venue or attend a specific event or it may be difficult to predict the time when the user will be at the venue or event. Therefore, it is difficult to pre-provision the user's UE in advance. Second, even if the UE is ensured to subscribe to the non-public mobile network, this is unlikely to scale well because the same operator of the non-public mobile network is unlikely to organize many (or all) events that the user wishes to attend. Third, operators of non-public mobile networks should not rely on users to search for non-public mobile networks on their UEs and manually switch themselves to the non-public mobile network because (1) many users may not be aware of the existence of non-public mobile networks, or (2) users may not be technically savvy enough to search for and switch to non-public mobile networks. Summary of the Invention

[0004] It is desirable to be able to redirect a user device from a public mobile network to a non-public mobile network without requiring the user to manually search for and switch to the non-public mobile network.

[0005] In a first aspect of the present invention, a system for redirecting a user equipment from a public mobile network to a non-public mobile network is provided, wherein the system is part of the public mobile network. The system may include:

[0006] - Network interface;

[0007] a processor subsystem configurable to perform the following operations via the network interface:

[0008] - receiving a request to redirect a user equipment from the public mobile network to the non-public mobile network, wherein the request may identify the non-public mobile network;

[0009] - receiving location information, wherein the location information may indicate a coverage area of the non-public mobile network;

[0010] - receiving frequency information, wherein the frequency information may indicate the frequency of the non-public mobile network

[0011] One or more radio frequencies used by the network;

[0012] - Identify the range of the coverage area that may be located within the non-public mobile network

[0013] at least one base station of the public mobile network in or within; and

[0014] - using the at least one base station of the public mobile network to command a user equipment connectable to the at least one base station to perform measurements on the one or more radio frequencies in order to: enable the user equipment to connect to the non-public mobile network if the measurements indicate that connection to the non-public mobile network is possible.

[0015] In another aspect of the present invention, a system for redirecting a user equipment from a public mobile network to a non-public mobile network is provided, wherein the system is part of the non-public mobile network. The system may include:

[0016] - Network interface;

[0017] a processor subsystem configurable to perform the following operations via the network interface:

[0018] - sending a request to the public mobile network to redirect the user equipment from the public mobile network to the non-public mobile network, wherein the request may identify the

[0019] non-public mobile networks;

[0020] - sending location information to the public mobile network, wherein the location information may indicate the coverage area of the non-public mobile network; and

[0021] - sending frequency information to the public mobile network, wherein the frequency information may indicate one or more radio frequencies used by the non-public mobile network.

[0022] In another aspect of the present invention, an apparatus is provided for representing a user equipment of a mobile network. The apparatus may include:

[0023] - Radio access network interface;

[0024] - a processor subsystem configurable to, when connected to a public mobile network, perform the following operations:

[0025] - receiving a request to perform measurements on one or more radio frequencies usable by a non-public mobile network, wherein the one or more radio frequencies may be indicated by frequency information, wherein the frequency information may be received as part of the request or separately;

[0026] - performing said measurements in response to said request; and

[0027] - if the measurements indicate that connection to the non-public mobile network is possible,

[0028] Then connect to the non-public mobile.

[0029] In another aspect of the present invention, a computer-implemented method for redirecting a user device from a public mobile network to a non-public mobile network is provided. The method may include performing the following operations on the public mobile network:

[0030] - receiving a request to redirect a user equipment from the public mobile network to the non-public mobile network, wherein the request may identify the non-public mobile network;

[0031] - receiving location information, wherein the location information may indicate a coverage area of the non-public mobile network;

[0032] - receiving frequency information, the frequency information being indicative of one or more radio frequencies used by the non-public mobile network;

[0033] - identifying at least one base station of the public mobile network that may be located within or within the coverage area of the non-public mobile network; and

[0034] - using the at least one base station of the public mobile network to command a user equipment connectable to the at least one base station to perform measurements on the one or more radio frequencies in order to: enable the device to connect to the non-public mobile network if the measurements indicate that connection to the non-public mobile network is possible.

[0035] In another aspect of the present invention, a computer-implemented method for redirecting a user device from a public mobile network to a non-public mobile network is provided. The method may include performing the following operations on the non-public mobile network:

[0036] - sending a request to the public mobile network to redirect the user equipment from the public mobile network to the non-public mobile network, wherein the request may identify the non-public mobile network;

[0037] - sending location information to the public mobile network, wherein the location information may indicate the coverage area of the non-public mobile network; and

[0038] - sending frequency information to the public mobile network, wherein the frequency information may indicate one or more radio frequencies used by the non-public mobile network.

[0039] In yet another aspect of the present invention, a computer-implemented method performed by an apparatus, the apparatus representing a user equipment of a public mobile network, may be provided. The method may include performing the following operations by the apparatus:

[0040] - receiving a request to perform measurements on one or more radio frequencies used by a non-public mobile network, wherein the one or more radio frequencies may be indicated by frequency information, wherein the frequency information may be provided as part of the request or separately;

[0041] - performing said measurements in response to said request; and

[0042] - If the measurements indicate that connection to the non-public mobile network is possible, connecting to the non-public mobile network.

[0043] In yet another aspect of the present invention, a transient or non-transitory computer-readable medium may be provided, wherein the data represents a computer program, the computer program comprising instructions for causing a processor system to perform any of the computer-implemented methods described in this specification.

[0044] According to the above measures, a first system may be provided in a public mobile network and a second system may be provided in a non-public mobile network, which systems may cooperate to redirect a user equipment (UE) from a public mobile network to a non-public mobile network. The first system may be referred to as the 'public network system' below, and the second system may be referred to as the 'non-public network system' below. The UE (meaning one or each of a plurality of UEs) may be a subscriber to a public mobile network or otherwise allowed to roam via a public mobile network, and may be connected to the public mobile network before redirection, but may not typically be pre-configured (provisioned) to utilize the non-public mobile network, for example, because the non-public mobile network is not subscribed. In order to enable the UE to remain connected to the non-public mobile network, the UE may be commanded to perform measurements on the radio frequencies used by the non-public mobile network for reasons explained elsewhere in this specification.

[0045] These instructions may be sent by the public network system, for example, upon request by the non-public network system, and may be generated based on information characterizing the non-public mobile network. Furthermore, the non-public network system may make this information available to the public network system, and the information may include an identifier of the non-public mobile network, a location of the non-public mobile network (e.g., in the form of a geographic location or coverage area), and may indicate one or more radio frequencies on which the base station(s) of the non-public mobile network operate. Based on the provided information, the public network system may selectively redirect the UE to the non-public mobile network, as only UEs that can connect to a base station of the public mobile network located in or near the coverage area of the non-public mobile network may be redirected.

[0046] More specifically, selective redirection can be achieved by the following operations: the public network system identifies which of the base stations of the public network are within the coverage area of the non-public mobile network or at least in the vicinity of the non-public mobile network, and provides instructions only to those UEs connected to these base stations and, in some embodiments, only to a subset of those UEs. Therefore, the location of the base station of the public mobile network can be used as an indication of the location of the UE connected to the base station. In this way, it is possible to avoid UEs that are (far) outside the coverage area of the non-public mobile network from being redirected, which otherwise may result in unnecessary measurements being performed by the UE and / or unnecessary internal data communications within the public mobile network. In addition, by using the location of the base station to which the UE is connected as an indication of the UE's location, there is no need to determine the UE's (precise) location in other ways, which can address privacy issues and reduce unnecessary data communications.

[0047] The redirection itself can be achieved by the public network system instructing (one or more) base stations within or near the coverage area of the non-public mobile network, and in turn instructing the user equipment to perform measurements on one or more radio frequencies used by the base stations of the non-public mobile network. In this way, the UE can be instructed to listen on the radio frequencies used by the non-public mobile network, which it might not otherwise do. Such measurements may represent a prerequisite for the UE to actually be able to switch to the non-public mobile network. That is, based on the measurements, it can be determined whether the UE is within range of the non-public mobile network, and if it is within range, the UE can do so, for example, after receiving an instruction to switch and connect to the non-public mobile network or based on internal decision logic to implement such a switch.

[0048] Since UEs within the coverage area of a non-public mobile network can be automatically commanded to perform measurements, there may be no need for the user to manually search for non-public mobile networks. This can greatly increase the potential use of non-public mobile networks for which UEs may not have been pre-configured. In practice, it is possible that UEs may not be pre-configured to utilize many instances of non-public mobile networks because they may only have limited coverage areas and / or are only temporary, which may make it difficult to predict which UEs will be within the coverage area of a non-public mobile network and, therefore, may make it difficult to predict which UEs need to be pre-configured in advance. Therefore, based on the above measures, if a UE is within the coverage area of a non-public mobile network, it can still connect to the non-public mobile network to benefit from enhanced services and / or additional coverage areas.

[0049] The following embodiments may relate to a system that is part of a public mobile network and a computer-implemented method executed on the public mobile network, but may also represent a system that is part of a non-public mobile network and a computer-implemented method executed on the non-public mobile network, as well as corresponding limitations of an apparatus representing a user equipment and a computer-implemented method executed on the apparatus.

[0050] In an embodiment, the processor subsystem may be configured to use at least one base station to perform the following operations:

[0051] - receiving measurement data from the user equipment, wherein the measurement data comprises measurements performed by the user equipment;

[0052] - Analysing the measurements to determine whether connection to the non-public mobile network is possible and, if so, commanding the user equipment to connect to the non-public mobile network.

[0053] The public network system may obtain measurement data from the user equipment and may analyze the measurement data to determine whether the UE is capable of connecting to the non-public mobile network, for example with sufficient connection quality. If the UE is capable of this, the public network system may instruct the UE via its base station to connect to the non-public mobile network. In such an embodiment, the UE may not need to decide whether to connect to the non-public mobile network on its own, but may instead perform and report measurements (which is itself functionality of the prior art) and then execute an instruction to connect to the non-public mobile network. Therefore, there may be no need to modify the prior art UE to be able to decide whether to connect to the non-public mobile network on its own. In addition, by making such a decision within the network, more control over the UE's handover to the non-public mobile network may be retained.

[0054] In an embodiment, the processor subsystem may be configured to, if measurements indicate that connection to a non-public mobile network is possible, command the user equipment to switch to an access mode for connecting to the non-public mobile network using at least one base station. Some types of non-public mobile networks, such as standalone non-public mobile networks, may require a switch in access mode to enable connection to the non-public mobile network. Based on the above measures, if the network decides that the UE will be redirected to a non-public mobile network, the UE may be commanded to switch its access mode to, for example, a non-public mobile network access mode. Therefore, there may be no need to modify the prior art UE to be able to switch its access mode to connect to the non-public mobile network. In addition, by making such a decision within the network, more control over the UE's handover to the non-public mobile network may be retained.

[0055] In an embodiment, the processor subsystem may be configured to receive time information indicating a start time at which the user equipment will be redirected to the non-public mobile network and to instruct the user equipment at the start time or at a time selected based on the start time. The non-public mobile network may be temporary or only semi-permanent and therefore may not be operational at all times, or it may not be generally desirable to redirect the UE to the non-public mobile network at all times. With this in mind, the UE may only be redirected to the non-public mobile network starting at a specified time, which may be, for example, the time when the non-public mobile network becomes operational or when a specific activity begins. In some embodiments, the redirection may only be active during a time window, which may be defined by a start time and a stop time to, for example, take into account the non-public mobile network ceasing its operation or the cessation of a specific activity.

[0056] In an embodiment, the processor subsystem may be configured to use at least one base station to command the user equipment by preconfiguring at least one base station to send corresponding instructions to the user equipment. Thus, the instructions provided to the UE may be sent via (one or more) base stations of the public mobile network, which may be preconfigured to do so. In other words, the public network system may preconfigure its (one or more) base stations to send redirection-related instructions to the UE. This may be advantageous because the base station is able to communicate directly with the connected UE and is therefore able to directly command a UE that is in or near the coverage area of a non-public mobile network. Advantageously, there may be no need to generate instructions for a separate UE in the public mobile network upstream of (one or more) base stations, which reduces the amount of internal data communication within the public mobile network.

[0057] In an embodiment, pre-configuration may include sending at least frequency information to at least one base station to enable the at least one base station to command the user equipment to perform measurements on one or more radio frequencies. As part of pre-configuration of its base station(s) in or near the coverage area of the non-public mobile network, the public network system may provide its base station(s) with the necessary information, such as the one or more radio frequencies on which the UE will perform measurements, to enable commanding the UE.

[0058] In an embodiment, the processor subsystem may be configured to, in response to a request to stop redirecting the user equipment to a non-public mobile network, preconfigure at least one base station to stop sending instructions to the user equipment. The non-public mobile network may be temporary or only semi-permanent and therefore may not always be operational, or it may generally not be desirable to always redirect the UE to the non-public mobile network. In view of this, redirection of the UE to the non-public mobile network may be stopped, for example, to allow for the non-public mobile network to cease its operation or a specific activity to cease.

[0059] In an embodiment, the processor subsystem may be configured to send a report to the non-public mobile network, wherein the report includes at least one of the following:

[0060] -The number of user devices redirected to non-public mobile networks;

[0061] - an identifier of the user equipment being redirected to the non-public mobile network;

[0062] - the duration of the user equipment's connection to the non-public mobile network; and

[0063] -Billing information associated with the redirection of the user equipment to a non-public mobile network.

[0064] Such reports may be used, for example, for billing purposes.

[0065] In an embodiment, the request may be received from the non-public mobile network, or the request may be an internal request from the public mobile network. The request to redirect the UE may originate from the non-public mobile network itself, such as from the non-public network system or another entity within the non-public mobile network, but may also be an internal request from the public mobile network, for example, if it is desired to offload some UEs to the non-public mobile network for capacity reasons or to expand the coverage of the public mobile network.

[0066] The following embodiments may relate to a system as part of a non-public mobile network and a computer-implemented method executed on the non-public mobile network, but may also represent a system as part of a public mobile network and a computer-implemented method executed on the public mobile network, as well as corresponding limitations of an apparatus representing a user equipment and a computer-implemented method executed on the apparatus.

[0067] In an embodiment, the processor subsystem may be configured to send a set of one or more of the following items to the public mobile network:

[0068] - a start time at which the user equipment will be redirected to the non-public mobile network,

[0069] - a stop time after which the user equipment will not be redirected to the non-public mobile network,

[0070] - reporting interval, indicating at which interval the public mobile network will report the redirection of the user device,

[0071] -report type, indicating the type of report,

[0072] - Identification information identifying a group of user devices to be redirected to the non-public mobile network.

[0073] The start time and the stop time may together define a time window or time interval during which the UE will be redirected. Alternatively, the start time or the stop time may be sent. In the latter case, the redirection may start immediately and may stop at the indicated stop time, while in the former case, the redirection may start at the indicated start time and continue, for example until a request to stop the redirection is received. The report type may indicate the type of report, for example periodic, none, unidirectional, directional or on request, while the reporting interval may be another optional parameter indicating how often reporting will be performed for some types of reports, for example periodic. Another aspect is that the UEs to be redirected may not only be selective in terms of location, but may also be restricted to a specific set of UEs in other ways. For example, a non-public network system may obtain a list of UEs that it wishes to allow access to a non-public mobile network. The list may, for example, consist of identifiers of UEs (e.g., in the form of telephone numbers) and may enable the public network system to redirect only those UEs that are in or near the coverage area of the non-public mobile network (e.g., by having only base stations in or near that coverage area pre-configured to redirect UEs), but in addition, to redirect only those UEs that are included in the list or are generally part of the group. This may allow the non-public mobile network to restrict access to its network to only selected UEs, for example, UEs that have tickets to an event or venue and have registered their telephone numbers in advance.

[0074] In another aspect of the present invention, a mobile network is provided, comprising a system for redirecting a user device as described herein. For example, a public mobile network may be provided, comprising a public network system, or a non-public mobile network may be provided, comprising a non-public network system.

[0075] The following embodiments may relate to an apparatus representing a user equipment and a computer-implemented method executed on the apparatus, but may also represent corresponding limitations of a system that is part of a public mobile network and a computer-implemented method executed on the public mobile network, and a system that is part of a non-public mobile network and a computer-implemented method executed on the non-public mobile network.

[0076] In an embodiment, the processor subsystem may be configured to, before connecting to the non-public mobile network, switch to an access mode for connecting to the non-public mobile network, for example, in response to an instruction received from a public mobile network. Some types of non-public mobile networks, such as independent non-public mobile networks, may require a switch in access mode by the UE in order to be able to connect to the non-public mobile network. According to the above measures, the UE may, for example, switch the access mode to, for example, a non-public mobile network access mode in response to an instruction from a public mobile network. In this way, the UE is enabled to connect to the non-public mobile network. In particular, if the UE is configured to switch the access mode in response to an instruction sent by a public mobile network, the public operator can control which non-public mobile network the UE connects to, which may provide a security advantage because the UE may be prevented from connecting to a "malicious" non-public mobile network.

[0077] In an embodiment, the processor subsystem may be configured to switch to an access mode for connecting to a public mobile network after disconnecting from a non-public mobile network. If a switch in access mode is required to connect to the non-public mobile network, another switch in access mode may be required to reconnect to the public mobile network. The device may be configured to perform this switch back to the public mobile network access mode, for example, upon disconnecting from or being disconnected from a non-public mobile network, to enable reconnection to the public mobile network. This ensures that the device can reconnect to the public mobile network after, for example, being only temporarily connected to the non-public mobile network. This is advantageous because many types of non-public mobile networks may have limited coverage and / or be only temporary. Therefore, it is desirable for the device to be able to switch back to the public mobile network. It also prevents the UE from connecting to a "rogue" non-public mobile network upon disconnecting from an earlier non-public mobile network, which could otherwise occur if the UE remained in the non-public mobile network access mode and continued searching for a non-public mobile network.

[0078] In an embodiment, the processor subsystem may be configured to:

[0079] - Sending measurements to the public mobile network; and

[0080] - Connecting to the non-public mobile network in response to a request from the public mobile network to connect to the non-public mobile network.

[0081] According to this embodiment, the public network system can decide whether the UE will be handed over to the non-public mobile network. By making such a decision within the network, more control over the UE's handover can be retained.

[0082] In an embodiment, the processor subsystem may be configured to analyze the measurements to determine whether connection to a non-public mobile network is possible, and if so, to connect to the non-public mobile network. By making this determination within the device, the device may autonomously decide to switch to the non-public mobile network, avoiding the need for external data communication. Additionally, in its decision, the device may utilize data that may not be directly accessible to the network but may be accessible to the device, such as the device's exact location or user preferences (e.g., stored in the device or on a SIM card), or the like.

[0083] It will be appreciated by those skilled in the art that two or more of the above-mentioned embodiments, implementations, and / or aspects of the invention may be combined in any way deemed useful.

[0084] Modifications and variations of any one of the systems or devices, computer-implemented methods and / or computer programs may be performed by a person skilled in the art based on the present description, and the modifications and variations correspond to modifications and variations of the description of another of these systems or devices, computer-implemented methods and / or computer programs, or vice versa. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter.

[0086] Figure 1 Shown is a user equipment (UE) that is a subscriber of a public land mobile network (PLMN) in a coverage area of a non-public network (NPN);

[0087] Figure 2 Shows the UE of the PLMN switching from the PLMN to the SNPN;

[0088] Figure 3 shows the redirection of UE to SNPN, which involves the pre-configuration phase, the activity phase, the reporting phase and the cleanup phrase;

[0089] Figure 4 shows the message exchange during the pre-configuration phase;

[0090] Figure 5 shows the message exchange during the activity phase;

[0091] Figure 6 shows the message exchange during the reporting phase;

[0092] Figure 7 shows the message exchange during the cleanup phase;

[0093] Figure 8A processor system is shown, which may be exemplary for a system or UE as described in this specification;

[0094] Figure 7 A non-transitory computer-readable medium comprising data is shown;

[0095] Figure 8 An exemplary data processing system is shown.

[0096] It should be noted that items with the same reference numerals in different drawings have the same structural features and the same functions, or are the same signals. Where the function and / or structure of such items have been described, there is no need to repeat the description thereof in the detailed description.

[0097] Reference Mark List

[0098] The following list of references and abbreviations is provided to facilitate interpretation of the drawings and should not be construed as limiting the claims.

[0099] 5GC 5G Core

[0100] NPN Non-Public Mobile Network

[0101] SNPN Standalone Non-Public Mobile Network

[0102] PLMN Public Land Mobile Network

[0103] UE User Equipment

[0104] 1-43 Message / Step 100 Public Land Mobile Network 5G Core

[0105] 110 Public Land Mobile Network Base Stations

[0106] 200 Non-public network 5G core

[0107] 210 Non-public network base stations

[0108] 220 Non-public network coverage area

[0109] 300 user devices

[0110] 400 system

[0111] 410 Network Interface

[0112] 420 processor subsystem

[0113] 430 Data Storage Device

[0114] 500 Non-transitory computer readable medium

[0115] 510 Stored Data

[0116] 1000 Exemplary Data Processing System

[0117] 1002 processor

[0118] 1004 memory element

[0119] 1006 system bus

[0120] 1008 local storage

[0121] 1010 Mass Storage Device

[0122] 1012 Input Device

[0123] 1014 output device

[0124] 1016 Network Adapter

[0125] 1018 Application DETAILED DESCRIPTION

[0126] The following embodiments are described in the context of a 5G telecommunications network that complies with one or more ETSI NFV and related standards. However, the concepts described in the following embodiments are equally applicable, mutatis mutandis, to any other type of telecommunications standard that provides public and non-public mobile networks for user equipment.

[0127] For the sake of simplicity, the public mobile network may be referred to below as simply a public network or by the acronym PLMN, and the non-public mobile network may be referred to as a non-public network or private network or by the acronym SNPN, which refers to a specific example of a stand-alone non-public network. However, this is not a limitation, as the claimed measures are equally applicable to other types of non-public networks, such as a public network integrated non-public network (PNI-NPN).

[0128] Figure 1 A user equipment UE 300 is shown, which is located in the coverage area 220 of a separate non-public mobile network SNPN. Figure 1 2 is shown in the form of a network core 200 and one or more base stations 210. The network core 200 may be a 5G network core ('5GC'), but may also be a subsequent generation network core, for example, sixth generation or subsequent generations. Figure 1 Further shown is a Public Land Mobile Network PLMN, which is also shown in the form of a 5G network core 100 and one or more base stations 110. Figure 1In the example, the coverage area 220 of the non-public network SNPN at least partially overlaps with the coverage area of the public network, for example because the PLMN may have a base station 110 in the coverage area 220 of the SNPN. The UE 300 may be a subscriber or at least able to roam via the PLMN, but may not typically be a subscriber of the SNPN.

[0129] Figure 1 , UE 300 is shown as being connected to the PLMN via base station 110 while being in the coverage area 220 of the SNPN. However, it may be desirable for UE 300 to, for example, temporarily connect to the SNPN while remaining in the coverage area 220 of the SNPN, for example to take advantage of enhanced services and / or additional coverage that may be provided to UE 300 by the SNPN.

[0130] Figure 2 The diagram shows the result of UE 300 switching from a PLMN to an SNPN, as UE 300 is now connected to the base station 210 of the SNPN. Methods for switching a UE from a PLMN to an SNPN may be known per se. That is, the user of the UE may use the user interface of the UE, for example, by requesting the UE to display all available mobile networks, to search for the SNPN, and may manually instruct the UE to connect to the SNPN, for example, by selecting the SNPN from a list of found mobile networks.

[0131] However, it would be desirable to enable a UE at a specific location to be redirected to a SNPN without manual involvement of the user. The following technical measures may redirect the UE to a SNPN using a PLMN, and in particular the PLMN to which the UE is connected. It will be understood that this may involve that a commercial agreement between the operators of the PLMN and the SNPN is in force, for example to incentivize the operator of the PLMN to redirect its subscribers to the SNPN. However, such a commercial agreement is not technically required to perform the redirection, and is therefore not a (necessary) feature of the present invention. Note that the need for a commercial agreement may also reduce the likelihood that the UE will be redirected to a malicious SNPN network, as the PLMN may not be incentivized to do so.

[0132] Figure 3 The following diagram illustrates several phases of UE to SNPN redirection, which may include a pre-configuration phase 1, an activity phase 2, a reporting phase 3, and a cleanup phase 3. For each of these phases, Figure 3 The entities involved as indicated by the arrows are the SNPN (shown only through its 5G core for simplicity), the PLMN (also shown only through its 5G core) and the UE to be redirected.

[0133] 1. Pre-configuration phase. The pre-configuration phase can be used to exchange information between the PLMN and the SNPN, for example, to inform the PLMN about the location and capabilities of the SNPN. Based on the exchanged information, the PLMN can pre-configure its base stations, such as its gNodeB in the example of a 5G PLMN, to redirect UEs to the SNPN.

[0134] 2. Active phase: The active phase may involve redirection of the UE to the SNPN via a base station of the PLMN.

[0135] 3. Reporting Phase. The reporting phase may involve reporting from the PLMN to the SNPN, or from the SNPN to the PLMN, or in both directions. Through such reporting, the PLMN and / or SNPN may better understand the redirection process and the costs, e.g., technical and / or financial, incurred by redirecting the UE to the SNPN. Note that this phase may be performed concurrently with the activity phase, but may also be performed additionally or alternatively after the activity phase has completed.

[0136] 4. Cleanup phase. During the cleanup phase, the PLMN may be informed that the SNPN is no longer active. In addition, charging records may be exchanged between the SNPN and the PLMN, for example detailing the number of redirected PDU sessions.

[0137] Reference Figure 4-7 These phases are described in more detail, with each figure illustrating the exchange of information for the corresponding phase. In these examples, the base stations of the SNPN and PLMN are shown as gNodeBs (gNBs). However, it is noted that the steps of redirecting the UE may also be divided into other phases or may not be explicitly or implicitly divided into phases at all. It will be further appreciated that, in this description, simply referring to certain steps or phases as 'optional' does not imply that other steps or phases not explicitly marked as optional are also optional from a technical perspective and are therefore required.

[0138] Figure 4 The message exchange in the pre-configuration phase is shown.In this figure and the following figures, the messages in the figures may be numbered, wherein the same numbers are used in the accompanying description of the message exchange.

[0139] Figure 4 The message exchange in may involve the following steps:

[0140] 11. The SNPN's 5GC may send a RedirectionRequest message to the PLMN 5GC. The RedirectionRequest may carry information including, but not limited to, one or more of the following: an identifier of the SNPN (which may take the form of a PLMN ID and an additional network identifier (NID)), the SNPN's capacity, capabilities, location, an indication of the start time and / or stop time of redirection, the requested reporting type (e.g., periodic, none, unidirectional, directional, or on request), and the reporting interval.

[0141] Through this request, the SNPN may request the PLMN to redirect the UE to the SNPN in a specific location and, in some examples, for a specific time frame (eg, defined with start time and stop time parameters).

[0142] Optionally, the request may specify the quality of service (QoS) or network slice that the SNPN will or can provide for the UE's PDU session.

[0143] 12. If the PLMN decides to complete the request, the PLMN 5GC may respond to the request with a 200 Success (Request Accepted) message. If the PLMN returns an error, the redirection process may stop at this step and not proceed to any of the subsequent stages.

[0144] 13. The SNPN's 5GC may send a message to the PLMN containing information about the SNPN's gNBs, for example by providing frequency information specifying the frequencies used by the SNPN's gNBs. This step may be performed only after the PLMN accepts the redirection request to ensure that internal SNPN information (e.g., used frequencies) is not shared with non-cooperating PLMNs. Optionally, in addition to frequency information, other information may be provided to the PLMN by the SNPN's 5GC, such as location information indicating the geographic location of each gNB.

[0145] 14. The PLMN's 5GC may send a message to at least some of its gNBs 110. The message may take the form of a Preconfigured RwR (frequency, start time, stop time, etc.), where 'RwR' stands for 'Release with Redirection'. Through this message, the PLMN may preconfigure its gNBs to redirect UEs at the location of the SNPN to the SNPN. This preconfiguration of gNBs may be selective, as only gNBs at or near the location specified in the redirection request may be preconfigured, thereby minimizing the number of preconfiguration messages in the PLMN. Furthermore, if a start time (start_time) is specified, the preconfigured information may not be applied until that point in time and, therefore, may not be actively used.

[0146] 15. The PLMN's gNB 110 may respond with a 200 Success (Confirmation) message to notify the PLMN's 5GC.

[0147] 16. The PLMN's 5GC may send a 200 Success (Confirmation) message to the SNPN's 5GC. That is, after the PLMN's gNB is provisioned, the PLMN's 5GC may notify the SNPN's 5GC that the PLMN is ready to enter the next phase, e.g., the Active phase, as described below.

[0148] Continuing with reference to step 11, it is noted that the location of the SNPN may be indicated to the PLMN in various ways, for example, as a geographic location defined by latitude and longitude, as a geographic area defined by latitude, longitude, and a radius, as a geographic area defined by multiple geographic locations, or by identifying a base station of the PLMN at the location of the SNPN. Generally speaking, the location identified to the PLMN may indicate the coverage area of the SNPN.

[0149] Figure 5 Shows the message exchange in the activity phase. Figure 5 The message exchange in may involve the following steps, which are described for one gNB 110 of a PLMN but are equally applicable to a group of gNBs:

[0150] 21. The PLMN's gNB 110 may send an RRC Connection Reconfiguration message containing a measurement object to the UE. This involves the following: At the start time of redirecting the UE (e.g., as defined in step 21 of the preconfiguration phase, or immediately if no such parameter is specified), information preconfigured in the PLMN's gNB (e.g., the frequencies used by the SNPN's gNB) may be sent to UEs within the gNB's range. This RRC Connection Reconfiguration message may instruct the UE to measure the specified frequencies of the active cell. Furthermore, the gNB may specify the measurement object type as an SNPN cell. After receiving the measurement object, the UE may consider the discovered SNPN as a candidate for future use (rather than as an unsuitable cell, as may be the default in the PLMN access mode, see 3GPP TS 38.304 clause 4.5).

[0151] 22. The UE may perform the specified measurements as well as any other measurements specified in the previous RRC connection reconfiguration message (eg, of other neighboring cells around the current serving cell).

[0152] 23. The UE may send a measurement report to the PLMN's gNB 110. The report may, for example, include measurements related to the SNPN's current serving cell(s) and other neighboring cells measured by the UE.

[0153] 24. The PLMN gNB 110 may decide to handover the UE to an SNPN. To that end, the PLMN gNB 110 may first determine whether the UE should be handed over to an SNPN upon receiving a measurement report of the SNPN cell(s). There are a number of parameters that the gNB may use to make this decision, such as the difference in signal strength between the served cell and the neighboring (SNPN) cell(s), the signal strength of the SNPN cell(s), the number of UEs that the gNB has already handed over to an SNPN, the UE's location, and / or the UE's subscription preferences.

[0154] 25. If the PLMN decides to handover the UE to an SNPN, the PLMN gNB 110 may send an RRC Release message to the UE. The RRC Release message may include a redirection configuration specifying that the new cell to which the UE should connect belongs to an SNPN.

[0155] 26. The UE may switch the access mode from the PLMN access mode to the SNPN access mode in response to the RRC release message.

[0156] 27. The UE may register with the SNPN.

[0157] After the UE is out of range of the SNPN, the UE may again switch the access mode to the PLMN access mode and reconnect to the PLMN. Alternatively, another RRC release message may be used to redirect the UE back to the PLMN, for example, in the same manner as when the UE was redirected to the SNPN. Generally speaking, a temporary or semi-permanent SNPN ensures that all UEs are properly released (and optionally redirected to the PLMN) before deciding to enter the cleanup phase.

[0158] Figure 6 Message exchanges in the reporting phase are shown. The reporting phase can be used to send periodic summaries from the PLMN to the SNPN and / or from the SNPN to the PLMN. This phase may be optional, and whether reporting can be performed and, if so, which type of reporting and frequency can be agreed upon in the pre-configuration phase. Figure 6 The message exchange in shows reporting from the core of the PLMN to the core of the SNPN, but is applicable mutatis mutandis to reporting from the core of the SNPN to the core of the PLMN. The steps involved may be:

[0159] 31. The 5GC of the PLMN may send a RedirectionSummary to the 5GC of the SNPN. The summary may include, for example, the number of redirected UEs, the duration of the redirection, and the billing information associated with the redirection of the UEs by the PLMN.

[0160] 32. The 5GC of the SNPN may respond to the RedirectionSummary of the PLMN with a 200 Success (Confirmation) message.

[0161] Figure 6 An alternative to steps 31 and 32 is that in step 31, the 5GC of the SNPN may send a request for a report to the 5GC of the PLMN, and in step 32, the 5GC of the PLMN may respond to the request of the SNPN with a 200 Success (Summary of Redirection) message, where the 200 Success message includes a report, for example, a summary of the redirection.

[0162] Figure 7 Message exchanges in the cleanup phase are shown. The cleanup phase may be applicable only or primarily to temporary and semi-permanent SNPNs, such as SNPNs established at specific locations or for specific events. Permanent SNPNs, such as SNPNs in museums or businesses, may not typically require a cleanup phase. Figure 7 The message exchange in may involve the following steps:

[0163] 41. The 5GC of the SNPN may send a RedirectionStopRequest message to the 5GC of the PLMN. By means of this message, the SNPN may inform the PLMN that the SNPN will stop its operation. This may be due, for example, to the end of an activity provided to it by the SNPN. Alternatively, the 5GC of the PLMN may decide to stop redirection without a request by the 5GC of the SNPN to stop redirection, for example when the PLMN temporarily offloads its UEs (some of them) using the SNPN and such offloading is no longer required. In this case, the 5GC of the PLMN may send a message to the 5GC of the SNPN to inform the SNPN that the PLMN will stop redirecting its UEs to the SNPN.

[0164] 42. The 5GC of the PLMN may send an instruction to the gNB 110 of the PLMN to delete the release with redirection (RwR) configuration deployed to the gNB 110 of the PLMN in step 23 of the pre-configuration phase.

[0165] 43. When the deletion request is completed, the PLMN's gNB 110 may send a 200 Success (Confirmation) message to the PLMN's 5GC.

[0166] 44. After all delete requests are completed, the PLMN's 5GC may send a 200 Success (Redirection Summary) message to the SNPN's 5GC. The summary may include, for example, the number of redirected UEs, the duration of the redirection, or billing information associated with the redirection.

[0167] In addition, after the SNPN stops its operation, the UE that is still attached to the gNB of the SNPN can switch the access mode to the PLMN access mode and can reconnect to the PLMN.

[0168] Continue to refer to the following Figure 3 However, the various steps are described from the perspective of the corresponding entities (e.g., UE, SNPN, PLMN, etc.) while referring to the corresponding stages. Note that the numbering of the steps here is independent of the numbering used in the figures.

[0169] User Equipment: The UE may perform one or more of the following steps:

[0170] 1. (Active phase) Connect to the PLMN.

[0171] 2. (Active Phase) Receive and process the RRC reconfiguration message (step 1 of the active phase). In contrast to a typical measurement configuration message, this message may specify that the new cell is an SNPN cell. The UE may be configured to process this information and, if the cell is within range of the UE, classify the cell as suitable and as a candidate for future use.

[0172] 3. (Active phase) Perform measurements.

[0173] a. If the UE measures the SNPN cell received in step 2, the UE may regard the cell as a valid candidate.

[0174] 4. (Active phase) Upon detecting that the signal strength of an SNPN is above a certain threshold, such as the threshold received in the previous step or otherwise known to the UE, the UE may send a measurement report to the gNB of the PLMN.

[0175] 5. (Active Phase) Upon receiving an RRC Release message with a redirection configuration having an SNPN indicator and referring to the SNPN cells referenced in the measurement report, the UE may be configured to process the information and may:

[0176] a. Save the PLMNID of the PLMN to which the UE is currently connected.

[0177] b. Change its access mode to SNPN access mode.

[0178] c. Connect to SNPN.

[0179] d. Consumer services.

[0180] e. If the SNPN has more than one active cell, the UE (because it is operating in SNPN access mode) may consider these other SNPN cells as valid candidates to hand over to, and / or the SNPN may perform a handover of the UE to another of its active cells.

[0181] Note that alternatively, the decision to switch to SNPN access mode and / or the decision to connect to SNPN may be offloaded to the UE rather than commanding it to do so via the RRC release message. That is, after performing the measurements in step 3, the UE may already know that the cell on the specified frequency is an SNPN cell because it has measured the cell and is able to read a broadcast message about the cell containing information identifying the cell as an SNPN cell.

[0182] 6. (Active Phase) If the SNPN stops its operation (e.g. in case of temporary activity) or the UE goes out of the coverage of the SNPN (e.g. the user leaves the premises), the UE may:

[0183] a. Disconnect from SNPN.

[0184] b. Change its access mode to PLMN access mode. For that purpose, the UE can be configured so that the RRC release configuration with SNPN redirection is only temporarily valid and only for the connection to a specific SNPN. Thus, when disconnected from the SNPN, the UE can restore its connection to the PLMN and can only be redirected to a new SNPN when the UE receives a new redirection instruction from the PLMN.

[0185] c. Connect to the PLMN whose ID was saved in step 5.

[0186] SNPN: SNPN may perform one or more of the following steps:

[0187] 1. (Pre-configuration phase) The SNPN may inform one or more PLMNs of its PLMNID+NID, capabilities, location, time span (e.g., start time and stop time), and potential QoS and / or network slices that the SNPN can provide to the UE.

[0188] 2. (Pre-configuration phase) Upon receiving a response from (one or more) PLMNs, the SNPN may perform one of the following operations:

[0189] a. If the PLMN's response is that it wishes to satisfy the request from the SNPN, meaning that the PLMN may have returned a 200 Success message to the SNPN, the SNPN may proceed to step 3.

[0190] b. If the response of the PLMN is that it does not wish to fulfill the request from the SNPN, meaning that the PLMN may have informed the SNPN that it does not wish to fulfill the request from the SNPN, the SNPN may stop the process.

[0191] 3. (Pre-configuration phase) The SNPN may send information related to its gNB configuration to the PLMN, for example in the form of frequency information and optionally also location information indicating the location of the gNB.

[0192] 4. (Pre-configuration phase) Upon receiving confirmation that the gNB is pre-configured, the SNPN can be ready to start serving the UE.

[0193] 5. (Active phase) The UE can connect to the SNPN, and the SNPN can serve the connected UE.

[0194] 6. [Optional] (Reporting phase) The SNPN may receive a redirection summary from the PLMN, for example in response to a request sent from the SNPN to the PLMN. The SNPN may optionally send its own redirection summary to the PLMN.

[0195] 7. (Cleanup phase) The SNPN may stop its operation, for example after the activity is completed. The UE may be disconnected.

[0196] 8. [Optional] (Cleanup phase) The SNPN may inform the PLMN that it is no longer operational. This may also be indicated in advance in the form of a stop time parameter sent in step 1.

[0197] 9. [Optional] (Clean-up phase) The SNPN may receive a summary of the redirection from the PLMN. This step may depend on the commercial agreement between the SNPN and the PLMN.

[0198] PLMN: The PLMN may perform one or more of the following steps:

[0199] 1. (Pre-configuration phase) Upon receiving a request from an SNPN to redirect a number of its UEs to the SNPN at a given location and optionally for a given time period, the PLMN may check whether the PLMN is able and willing (e.g. subject to the commercial agreement existing between the operators of the PLMN and the NPN) to satisfy the request. Two options are possible:

[0200] a. The PLMN wishes to fulfill the request and returns a 200 Success message to the SNPN.

[0201] The process continues with step 2.

[0202] b. If the PLMN does not wish to fulfill the request from the SNPN, the PLMN will inform the SNPN. This action can stop the process.

[0203] 2. (Pre-configuration phase) Upon receiving the list of gNB configurations (e.g., frequencies used) for the SNPN, the PLMN may:

[0204] a. Identify the gNB of the PLMN that is at or near the location where the SNPN wishes to provide service to the UE.

[0205] b. For each of the identified gNBs, the PLMN may preconfigure the frequencies to be used during the measurement and Release with Redirection (RwR) steps in the active phase. Additionally, the PLMN may specify the time period during which the configuration should apply, for example using start time and stop time parameters. If no time period is preconfigured, and in particular if no start time is provided, the configuration may be applied immediately.

[0206] c. Upon provisioning the gNB, the PLMN may return a confirmation message to the SNPN, which informs the SNPN that it is ready to start redirecting the UE.

[0207] 3. (Active Phase) At a specified time (e.g., as specified by a start time), the SNPN may begin its operation and the PLMN may send an RRC reconfiguration message to all UEs in its area. The message may update the UE's measurement configuration with the new SNPN cell(s).

[0208] 4. (Active phase) Upon receiving the measurement report from the UE, the PLMN may send an RRC release message with the SNPN redirection configuration to the UE. Thus, the UE may switch to the SNPN.

[0209] 5. [Optional] (Reporting phase) The PLMN may, for example, periodically send a redirection summary to the SNPN, for example in response to a request received from the SNPN. In some examples, the redirection summary may include information that can be used by the SNPN to estimate, for example, technical and / or financial costs of the redirection.

[0210] 6. (Cleanup Phase) After the SNPN stops the operation of its network, for example, after the activity is completed, the UEs redirected to the SNPN can connect to the PLMN. The PLMN can continue to provide services to these UEs.

[0211] 7. [Optional] (Cleanup phase) After the SNPN notifies the PLMN that it is no longer operational, the PLMN may send a summary of the redirection from the PLMN to the SNPN. This step may depend on the commercial agreement that exists between the SNPN and the PLMN.

[0212] It will be appreciated that redirection of the UE from the PLMN to the SNPN may also take various other forms.

[0213] For example, instead of the SNPN requesting the PLMN to redirect the UE, the PLMN may also request the SNPN to take over (a part of) its UE, for example to obtain additional coverage in times of very busy activity. In this case, messages 11 and 12 in the pre-configuration phase may be used in conjunction with Figure 4 is sent in the opposite direction compared to the direction shown in . More specifically, the PLMN may send a RedirectRequest to the SNPN, and the SNPN may confirm the request. The SNPN may then send gNB information to the PLMN to ensure that the UE can be redirected to its gNB. Furthermore, in this case, during the cleanup phase, an additional redirectionSummary may be sent from the SNPN to the PLMN, highlighting the resources consumed by its UE while connected to the SNPN; this information may be used, for example, for billing.

[0214] In general, the RRC Release message sent during the active phase may not need to include (all) the information the UE needs to connect to the SNPN network. That is, the UE may already be able to obtain this information from the measurement configuration sent by the gNB and the broadcast messages received.

[0215] Note further that during the pre-configuration phase, the SNPN may request that only a certain set of UEs be redirected, for example, UEs with active reservations (e.g., museum reservations, sports reservations). The SNPN may also request that only certain UEs be redirected to the SNPN. This may be applicable, for example, to a scenario where a user needs to make a reservation in advance for, for example, an event, venue, seminar, or conference, and enter their phone number or provide another form of identification. In this way, the PLMN can redirect only selected UEs to the SNPN.

[0216] Generally speaking, the functionality attributed to a system described in this specification may refer to the functionality of one or more network functions implemented in a mobile network, for example, by a network node or a system of network nodes. The network function(s) may be made available within the corresponding mobile network in order to establish the corresponding functionality in the mobile network.

[0217] It will be appreciated that, according to the standards of the prior art (3GPP TS23.501 clause 5.30.2.4.1, 3GPP TS23.122 clause 4.4.1), the SNPN and PLMN access modes in the UE may be mutually exclusive. Therefore, a UE operating in SNPN access mode may select an independent non-public network (SNPN) via the Uu interface and may not perform the PLMN selection process. Similarly, if the UE is not set to operate in SNPN access mode, the UE may not select an SNPN and register with it even if it is SNPN enabled. The same reasoning may apply to PLMN access mode, for example, a UE operating in PLMN access mode may not select an SNPN and register with it, but may only register with an available PLMN. Therefore, although the prior art UE (operating in SNPN mode and registered to SNPN) can register with the PLMN via SNPN (where SNPN is acting as an untrusted non-3GPP access, 3GPP TS 23.501 clause 5.30.2.7), the UE may not be handed over to the PLMN NG-RAN if it is out of range of the SNPN because the UE may be operating in SNPN access mode. In order to solve this defect, the UE may, for example, Figure 5 The message 25 and step 26 described are commanded to switch the access mode, or if the measurement (e.g. Figure 5 If step 22 in step 22) indicates that switching to SNPN is possible, it may be configured to switch the access mode autonomously. In the latter case, if the measurements are satisfactory, specifying a measurement object of type SNPN may enable the UE to switch to SNPN access mode later. In particular, in the message containing the measurement object, one or more signal strength thresholds may be included, for example, as part of a reporting object such as reportConfigToAddModList. Signal strength thresholds may conventionally be used to define the conditions for when the UE will send measurement reports to the network. However, in some embodiments, these signal strength thresholds may be used by the UE for different purposes, namely, to determine when to switch to SNPN access mode and subsequently connect to the SNPN. This may involve the UE comparing the measured signal strength with a signal strength threshold and continuing to switch to SNPN access mode if the measured signal strength exceeds the threshold.

[0218] Figure 8A processor system 400 is shown, which may represent a system for redirecting a user device from a public mobile network to a non-public mobile network as described in this specification, meaning that the processor system 400 may implement such a system. The processor system 400 may include a network interface 410 for network data communication. The network interface 410 may, for example, be a wired communication interface to a fixed (e.g., non-mobile) portion of a mobile telecommunications network, such as an Ethernet or fiber-optic based interface. Alternatively, the network interface 410 may be a wireless communication interface. In still other examples, the processor system 400 may be a subsystem of a larger system, such as a supersystem that implements several network functions. In this case, the network interface 410 may be an internal interface of the supersystem, for example, a virtual, software-based network interface.

[0219] The processor system 400 may further include a processor subsystem 420, which may be configured, for example, by hardware design or software, to perform the operations described in this specification with respect to aspects related to the entity that the processor system is implementing (for example, a system for redirecting a user device from a public mobile network to a non-public mobile network). Generally speaking, the processor subsystem 420 may be implemented by a single central processing unit (CPU) such as an x86 or ARM-based CPU, but may also be implemented by a combination or system of such CPUs and / or other types of processing units. In embodiments in which the processor system 400 is distributed across different entities, for example across different servers, the processor subsystem 420 may also be distributed, for example, across the CPUs of such different servers. For example Figure 8 As shown in , the processor system 400 may include a data storage device 430, such as a hard disk drive, a solid state drive, or an array of such hard disks and / or solid state drives, which may be used to store data. In some examples, the processor system 400 may be implemented by a network node or by a system of network nodes that jointly provide network functions.

[0220] exist Figure 8 In an alternative embodiment of the processor system 400, the processor system 400 may represent a user equipment or a device representing a user equipment, as described in this specification. Examples of such devices include, but are not limited to, mobile phones, tablet devices, computers, smart glasses, robotic systems, connectivity-enabled vehicles, etc. In this case, the network interface 410 may represent a radio access network interface to a mobile network, and the processor subsystem 420 may be configured, for example, by hardware design or software, to perform the operations described in this specification with respect to the entity (e.g., user equipment or device) being implemented by the processor system.

[0221] In general, each entity described in this specification may be implemented as a device or equipment or may be implemented in a device or equipment. The device or equipment may include one or more (micro) processors that execute appropriate software. The (one or more) processors of the corresponding entity may be implemented by one or more of these (micro) processors. The software that implements the functionality of the corresponding entity may have been downloaded and / or stored in a corresponding memory or multiple memories, for example, it may have been stored in a volatile memory such as RAM or in a non-volatile memory such as flash memory. Alternatively, the (one or more) processors of the corresponding entity may be implemented in the form of programmable logic in the device or equipment, for example, it may be implemented as a field programmable gate array (FPGA). Any input and / or output interface may be implemented by the corresponding interface of the device or equipment. In general, each functional unit of the corresponding entity may be implemented in the form of a circuit or circuit system (circuitry). The corresponding entity may also be implemented in a distributed manner, for example, involving different devices or equipment.

[0222] Note that any of the methods described in this specification (e.g., any of the claims) may be implemented on a computer as a computer-implemented method, as dedicated hardware, or as a combination of both. Instructions (e.g., executable code) for a computer may be stored in, for example, a computer program. Figure 9 , for example, in the form of a series of machine-readable physical indicia 510 and / or as a series of elements having different electrical (e.g., magnetic) or optical properties or values. The executable code may be stored in a transient or non-transient manner. Examples of computer-readable media include memory devices, optical storage devices, integrated circuits, servers, online software, etc. Figure 9 A memory card 500 is shown as an example.

[0223] Figure 101 is a block diagram illustrating an exemplary data processing system 1000 that can be used in the embodiments described in this specification. This data processing system includes the data processing entities described in this specification, including but not limited to a system for redirecting user devices and a device for representing user devices. The data processing system 1000 may include at least one processor 1002, which is coupled to a memory element 1004 via a system bus 1006. Therefore, the data processing system can store program code in the memory element 1004. In addition, the processor 1002 can execute program code accessed from the memory element 1004 via the system bus 1006. In one aspect, the data processing system can be implemented as a computer that is suitable for storing and / or executing program code. However, it should be understood that the data processing system 1000 can be implemented in the form of any system that can perform the functions described in this specification, including a processor and a memory. The memory element 1004 may include one or more physical memory devices, such as, for example, a local memory 1008 and one or more mass storage devices 1010. Local memory may refer to random access memory or other non-persistent memory devices typically used during the actual execution of program code. Mass storage may be implemented as a hard drive, solid-state drive, or other persistent data storage device. Data processing system 1000 may also include one or more cache memories (not shown) that provide temporary storage of at least some program code in order to reduce the number of times program code would otherwise be retrieved from mass storage 1010 during execution.

[0224] Input / output (I / O) devices, shown as input device 1012 and output device 1014, can optionally be coupled to the data processing system. Examples of input devices may include, but are not limited to, a microphone, a keyboard, a pointing device such as a mouse, a game controller, a Bluetooth controller, a VR controller, and gesture-based input devices, or the like. Examples of output devices may include, but are not limited to, a monitor or display, speakers, or the like. Input devices and / or output devices may be coupled to the data processing system directly or through an intervening I / O controller. A network adapter 1016 may also be coupled to the data processing system to enable it to be coupled to other systems, computer systems, remote network devices, and / or remote storage devices via an intervening non-public or public network. The network adapter may include: a data receiver for receiving data transmitted to the data system by the system, device, and / or network; and a data transmitter for transmitting data to the system, device, and / or network. Radios, modems, cable modems, and Ethernet cards are examples of different types of network adapters that can be used with data processing system 1000.

[0225] like Figure 10 As shown in FIG, memory element 1004 can store application 1018. It should be appreciated that data processing system 1000 can further execute an operating system (not shown) that can facilitate the execution of applications. Applications implemented in the form of executable program code can be executed by data processing system 1000, for example, by processor 1002. In response to executing the applications, the data processing system can be configured to perform one or more operations that will be described in more detail herein.

[0226] For example, data processing system 1000 may represent a system for redirecting a user device as described herein. In that case, application 1018 may represent an application that, when executed, configures data processing system 1000 to perform the functions described with reference to the system for redirecting a user device. In another example, data processing system 1000 may represent an embodiment of a user device or an apparatus representing a user device as described herein. In that case, application 1018 may represent an application that, when executed, configures data processing system 1000 to perform the functions described with reference to the user device and / or apparatus.

[0227] The abstract of the specification may be stated as follows: A first system may be provided in a public mobile network, and a second system may be provided in a non-public mobile network, the systems cooperating to selectively redirect a user equipment from the public mobile network to the non-public mobile network. Such redirection may be achieved by the first system commanding (one or more) base stations within or near the coverage area of the non-public mobile network, and thereby commanding the user equipment to perform measurements on radio frequencies used by the non-public mobile network. In this way, the user equipment may be commanded to listen to the radio frequencies used by the non-public mobile network, and if the user equipment is within the coverage area of the non-public mobile network, the user equipment may be handed over and connected to the non-public mobile network and thereby benefit from enhanced services and / or additional coverage. Advantageously, there may be no need for the user to manually search for the non-public mobile network, nor may the user equipment be pre-configured for the non-public mobile network.

[0228] It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims.

[0229] In the claims, any reference signs placed between parentheses should not be construed as limiting the claim. The use of the verb "comprise" and its conjugations does not exclude the presence of elements or stages other than those stated in the claim. The article "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. Expressions such as "at least one of...", when preceding a list or group of elements, indicate a selection of all elements or any subset of elements from the list or group. For example, the expression "at least one of A, B, and C" should be understood to include only A, only B, only C, A and B, A and C, B and C, or all of A, B, and C. The present invention can be implemented by hardware comprising several different elements and by a suitably programmed computer. In a device claim enumerating several components, several of these components may be implemented by the same piece of hardware. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims

1. A system for redirecting a user equipment from a public mobile network to a non-public mobile network, wherein the system is part of the public mobile network, wherein the system comprises: - Network interface; a processor subsystem configured to perform the following operations via the network interface: - receiving a request to redirect a user equipment from the public mobile network to the non-public mobile network, wherein the request identifies the non-public mobile network; - receiving location information, the location information indicating a coverage area of the non-public mobile network; - receiving frequency information indicating one or more radio frequencies used by the non-public mobile network; - identifying at least one base station of the public mobile network located within or within the coverage area of the non-public mobile network; as well as - using the at least one base station of the public mobile network to command a user equipment connected to the at least one base station to perform measurements on the one or more radio frequencies in order to: enable the user equipment to connect to the non-public mobile network if the measurements indicate that connection to the non-public mobile network is possible.

2. The system according to claim 1, wherein: The processor subsystem is configured to use the at least one base station to perform the following operations: - receiving measurement data from the user equipment, wherein the measurement data comprises the measurements performed by the user equipment; - analyzing the measurements to determine whether the connection to the non-public mobile network is possible, and if so, commanding the user equipment to connect to the non-public mobile network.

3. The system according to claim 1 or 2, wherein: The processor subsystem is configured to command the user equipment to switch to an access mode for connecting to the non-public mobile network using the at least one base station if the measurements indicate that the connection to the non-public mobile network is possible.

4. The system according to any one of claims 1 to 3, wherein: The processor subsystem is configured to receive time information indicating a start time at which the user equipment is to be redirected to the non-public mobile network, and to command the user equipment at the start time or at a time selected based on the start time.

5. The system according to any one of claims 1 to 4, wherein: The processor subsystem is configured to command the user equipment using the at least one base station by preconfiguring the at least one base station to send corresponding instructions to the user equipment.

6. The system according to claim 5, wherein: The pre-configuration comprises sending at least the frequency information to the at least one base station to enable the at least one base station to command the user equipment to perform the measurements on the one or more radio frequencies.

7. A system according to claim 5 or 6, wherein: The processor subsystem is configured to preconfigure the at least one base station to stop sending instructions to the user equipment in response to a request to stop redirecting the user equipment to the non-public mobile network.

8. A system for redirecting a user equipment from a public mobile network to a non-public mobile network, wherein the system is part of the non-public mobile network, wherein the system comprises: - Network interface; a processor subsystem configured to perform the following operations via the network interface: - sending a request to the public mobile network to redirect the user equipment from the public mobile network to the non-public mobile network, wherein the request identifies the non-public mobile network; - sending location information to the public mobile network, wherein the location information indicates the coverage area of the non-public mobile network; and - sending frequency information to the public mobile network, wherein the frequency information indicates one or more radio frequencies used by the non-public mobile network.

9. The system, wherein: The processor subsystem is configured to send to the public mobile network a set of one or more of the following: - a start time at which the user equipment will be redirected to the non-public mobile network, a stop time after which the user equipment will not be redirected to the non-public mobile network, - a reporting interval, indicating at which interval the public mobile network will report the redirection of the user equipment, - Report Type, indicating the type of report, - Identification information identifying a group of user equipment to be redirected to the non-public mobile network.

10. A mobile network comprising a system according to any one of claims 1 to 9.

11. An apparatus representing user equipment of a mobile network, wherein the apparatus comprises: - Radio access network interface; - a processor subsystem configured to, when connected to a public mobile network, perform the following operations: - receiving a request to perform measurements on one or more radio frequencies used by a non-public mobile network, wherein the one or more radio frequencies are indicated by frequency information, wherein the frequency information is received; - performing said measurements in response to said request; as well as - If the measurements indicate that connection to the non-public mobile network is possible, connecting to the non-public mobile network.

12. The device according to claim 11, wherein The processor subsystem is configured to, before connecting to the non-public mobile network, switch to an access mode for connecting to the non-public mobile network, for example in response to an instruction received from the public mobile network.

13. The device according to claim 12, wherein The processor subsystem is configured to, after disconnecting from the non-public mobile network, switch to an access mode for connecting to the public mobile network.

14. The device according to any one of claims 11 to 13, wherein The processor subsystem is configured to: - sending said measurements to said public mobile network; and - connecting to the non-public mobile network in response to a request from the public mobile network to connect to the non-public mobile network.

15. The device according to any one of claims 11 to 13, wherein The processor subsystem is configured to analyze the measurements to determine whether the connection to the non-public mobile network is possible, and if so, to connect to the non-public mobile network.

16. A computer-implemented method for redirecting a user device from a public mobile network to a non-public mobile network, wherein the method comprises performing the following operations at the public mobile network: - receiving a request to redirect a user equipment from the public mobile network to the non-public mobile network, wherein the request identifies the non-public mobile network; - receiving location information, the location information indicating a coverage area of the non-public mobile network; - receiving frequency information indicating one or more radio frequencies used by the non-public mobile network; - identifying at least one base station of the public mobile network that is located within or within the coverage area of the non-public mobile network; and - using the at least one base station of the public mobile network to command a user equipment connected to the at least one base station to perform measurements on the one or more radio frequencies in order to: enable the device to connect to the non-public mobile network if the measurements indicate that connection to the non-public mobile network is possible.

17. A computer-implemented method for redirecting a user device from a public mobile network to a non-public mobile network, wherein the method comprises performing the following operations on the non-public mobile network: - sending a request to the public mobile network to redirect the user equipment from the public mobile network to the non-public mobile network, wherein the request identifies the non-public mobile network; - sending location information to the public mobile network, wherein the location information indicates the coverage area of the non-public mobile network; and - sending frequency information to the public mobile network, wherein the frequency information indicates one or more radio frequencies used by the non-public mobile network.

18. A computer-implemented method performed by an apparatus, the apparatus representing user equipment of a public mobile network, wherein the method comprises performing, by the apparatus: - receiving a request to perform measurements on one or more radio frequencies used by a non-public mobile network, wherein the one or more radio frequencies are indicated by frequency information, wherein the frequency information is provided as part of the request or separately; - performing said measurements in response to said request; as well as - If the measurements indicate that connection to the non-public mobile network is possible, connecting to the non-public mobile network.

19. A transitory or non-transitory computer-readable medium comprising data, the data representing a computer program comprising instructions for causing a processor system to perform the method according to any one of claims 16 to 18.

Images