Methods and apparatuses for network-initiated mobility in a network

Abstract

A method implemented by a user equipment (UE), comprising: the UE receiving a first message from a home service provider (SP) of the UE, the first message including information associated with one or more target networks, the first message initiating a network handover that changes the UE's serving network from a current network to one of the one or more target networks; the UE selecting the one of the one or more target networks; and the UE accessing the one target network.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 021,460, filed on May 7, 2020, entitled “Methods and Apparatus for Network Initiated Continuity of SNPN Deployments,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to methods and apparatus for digital communications, and in particular embodiments, to methods and apparatus for network-initiated mobility within a network. Background Art

[0004] Mobility management generally refers to the functionality of a communication network that is intended to support the mobility of subscribers (e.g., user equipment (UE)) by allowing the continuous provision of services such as calls, content, data, and messages to subscribers as they move within the communication system. As the services provided by communication networks become increasingly complex and their requirements become more stringent, the tasks involved in mobility management become more difficult to implement.

[0005] A stand-alone non-public network (SNPN) is a network operated by a non-public network (NPN) operator that does not rely on the network functions provided by a public-line mobile network (PLMN). In other words, an SNPN is able to deploy fifth-generation (5G) networks for private use without relying on public 5G networks.

[0006] However, as the UE keeps moving, it is possible for the UE to exit the coverage of the first SNPN and enter the coverage of the second SNPN.Therefore, there is a need for methods and apparatus for network-initiated mobility in non-public networks such as SNPNs. Summary of the Invention

[0007] According to a first aspect, a method implemented by a user equipment (UE) is provided. The method includes: the UE receiving a first message including information associated with one or more target networks from a home service provider (SP) of the UE, the first message initiating a network handover to change the UE's serving network from a current network to one of the one or more target networks; the UE selecting the one of the one or more target networks; and the UE accessing the one target network.

[0008] In a first implementation of the method according to the first aspect, the home SP owns the service subscription of the UE to the service or application that the UE is accessing through the serving network.

[0009] In a second implementation of the method according to the first aspect or any preceding implementation of the first aspect, the one or more target networks include private networks belonging to a SP different from the home SP.

[0010] In a third implementation of the method according to the first aspect or any preceding implementation of the first aspect, the first message includes a network switching indication or a network boot indication.

[0011] In a fourth embodiment of the method according to the first aspect or any preceding embodiment of the first aspect, it further includes: the UE receives a second message from the home SP including network information associated with one or more candidate networks involving network switching of the UE, and the second message is received before receiving the first message; the UE measures the one or more candidate networks based on the network information; and the UE reports the measurement information associated with the one or more candidate networks to the home SP.

[0012] In a fifth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the first message or the second message is received during one of a UE configuration procedure or a parameter update procedure.

[0013] In a sixth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the first message is received in a dedicated network control message that directs the UE from the current network to the one target network.

[0014] In a seventh implementation of the method according to the first aspect or any preceding implementation of the first aspect, the first message is received in a policy configuration message for directing the UE from the current network to the one target network based on a service connection policy.

[0015] In an eighth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the first message further includes a time window duration for completing or starting the network switching process.

[0016] In a ninth implementation of the method according to the first aspect or any preceding implementation of the first aspect, when the time window duration is equal to 0, the UE initiates the network switching process as soon as possible.

[0017] In a tenth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the second message includes a UE network switching policy.

[0018] In an eleventh implementation of the method according to the first aspect or any preceding implementation of the first aspect, the first message includes a network handover policy to assist the UE in making a handover decision.

[0019] In a twelfth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the network handover policy includes a performance threshold or a location trigger for causing the UE to initiate handover.

[0020] In a thirteenth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the performance threshold comprises application-level performance.

[0021] In a fourteenth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the network information includes: identifications of one or more candidate networks; and identifications of one or more SPs of the one or more candidate networks.

[0022] In a fifteenth implementation of the method according to the first aspect or any preceding implementation of the first aspect, the measurement information includes: an indicator indicating whether the signal strength of each candidate network among the one or more candidate networks is suitable for the UE.

[0023] According to a second aspect, a method implemented by a home service provider (SP) is provided. The method includes: the home SP receiving a report including information associated with a location of a user equipment (UE) from the home SP; the home SP selecting one or more target networks based on the information; and the home SP sending a first message including information associated with the one or more target networks to the UE, the first message initiating a network handover to change the UE's serving network from a current network to one of the one or more target networks.

[0024] In a first implementation manner of the method according to the second aspect, the method further includes: the home SP sending a second message including a measurement request for one or more candidate networks to the UE.

[0025] In a second implementation of the method according to the second aspect or any preceding implementation of the second aspect, the home SP owns the service subscription of the UE to the service or application that the UE is accessing through the serving network.

[0026] In a third implementation of the method according to the second aspect or any preceding implementation of the second aspect, the one or more target networks include a private network belonging to an SP different from the home SP.

[0027] In a fourth implementation of the method according to the second aspect or any preceding implementation of the second aspect, the first message is sent in one of a UE configuration procedure or a parameter update procedure.

[0028] In a fifth implementation of the method according to the second aspect or any preceding implementation of the second aspect, the first message is sent in a dedicated network control message that directs the UE from the current network to the one target network.

[0029] In a sixth implementation of the method according to the second aspect or any preceding implementation of the second aspect, the first message is sent in a policy configuration message for directing the UE from the current network to the one target network based on a service connection policy.

[0030] In a seventh implementation of the method according to the second aspect or any preceding implementation of the second aspect, the information includes location information of the UE.

[0031] In an eighth embodiment of the method according to the second aspect or any preceding embodiment of the second aspect, further comprising:

[0032] The SP determines one or more candidate networks based on the UE's location information and a distance threshold; and

[0033] The SP queries the one or more candidate networks to obtain performance information associated with the one or more candidate networks.

[0034] In a ninth implementation of the method according to the second aspect or any preceding implementation of the second aspect, the information includes performance information associated with one or more candidate networks determined by the UE.

[0035] In a tenth implementation of the method according to the second aspect or any preceding implementation of the second aspect, the one or more target networks are selected from the one or more candidate networks based on performance information.

[0036] In an eleventh implementation of the method according to the second aspect or any preceding implementation of the second aspect, the performance information includes an indicator indicating whether the signal strength of each candidate network of the at least one candidate network is suitable for the UE.

[0037] According to a third aspect, a UE is provided. The UE includes: one or more processors; and a non-transitory memory including instructions that, when executed by the one or more processors, cause the UE to: receive a first message including information associated with one or more target networks from a home service provider (SP) of the UE, the first message initiating a network handover that changes a serving network of the UE from a current network to one of the one or more target networks; select the one of the one or more target networks; and access the one target network.

[0038] In a first implementation of the method according to the third aspect, the home SP owns the service subscription of the UE to the service or application that the UE is accessing through the serving network.

[0039] In a second implementation of the method according to the third aspect or any preceding implementation of the third aspect, the one or more target networks include a private network belonging to an SP different from the home SP.

[0040] In a third implementation of the method according to the third aspect or any preceding implementation of the third aspect, the first message includes a network switching indication or a network boot indication.

[0041] In a fourth embodiment of the method according to the third aspect or any preceding embodiment of the third aspect, the above-mentioned instructions cause the UE to: receive from the home SP a second message including network information associated with one or more candidate networks involving network switching of the UE, the second message being received before receiving the first message; measure the one or more candidate networks based on the network information; and report the measurement information associated with the one or more candidate networks to the home SP.

[0042] In a fifth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the first message or the second message is received during one of a UE configuration procedure or a parameter update procedure.

[0043] In a sixth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the first message is received in a dedicated network control message that directs the UE from the current network to the one target network.

[0044] In a seventh implementation of the method according to the third aspect or any preceding implementation of the third aspect, the first message is received in a policy configuration message for directing the UE from the current network to the one target network based on a service connection policy.

[0045] In an eighth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the first message further includes a time window duration for completing or starting the network switching process.

[0046] In a ninth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the second message includes a UE network switching policy.

[0047] In a tenth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the first message includes a network handover policy to assist the UE in making a handover decision.

[0048] In an eleventh implementation of the method according to the third aspect or any preceding implementation of the third aspect, the network handover policy includes a performance threshold or a location trigger for causing the UE to initiate handover.

[0049] In a twelfth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the performance threshold comprises application-level performance.

[0050] In a thirteenth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the network information includes: identifications of the one or more candidate networks; and identifications of one or more SPs of the one or more candidate networks.

[0051] In a fourteenth implementation of the method according to the third aspect or any preceding implementation of the third aspect, the measurement information includes: an indicator indicating whether the signal strength of each candidate network among the one or more candidate networks is suitable for the UE.

[0052] An advantage of the exemplary embodiments is that network-initiated mobility in non-public networks is supported. Mobility is initiated and assisted by information provided by the network to improve mobility performance.

[0053] Yet another advantage of exemplary embodiments is that the information provided by the network assists the UE in gathering information associated with potential target networks, which helps improve mobility performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0055] Figure 1 A first exemplary communication system is shown;

[0056] Figure 2 A communication system highlighting network switching is shown;

[0057] Figure 3AShown is a communication system highlighting that a UE obtains services from a service provider (SP) via a standalone non-dedicated network (SNPN) #1;

[0058] Figure 3B Shown is a communication system highlighting that UE 305 obtains services from an SP (SP#1) through an NPN (including its own radio access network (RAN) and 5G core (5GC));

[0059] FIG4 shows a communication system highlighting the prior art support for UE mobility;

[0060] FIG5 shows a diagram of communications exchanged and processes performed by entities involved in supporting UE mobility in the prior art;

[0061] Figure 6 shows a high-level view of a communication system supporting network-initiated mobility in an NPN according to exemplary embodiments presented herein;

[0062] Figure 7 illustrates an architecture of a first exemplary communication system highlighting entities having enhanced operations to support network-initiated mobility according to exemplary embodiments presented herein;

[0063] Figure 8 illustrates an architecture of a second exemplary communication system highlighting entities having enhanced operations to support network-initiated mobility according to exemplary embodiments presented herein;

[0064] Figure 9 A diagram illustrating communications exchanged and processing performed by entities participating in a UE reporting potential target network procedure according to an exemplary embodiment presented herein;

[0065] Figure 10 A diagram illustrating communications exchanged and processes performed by entities participating in a first exemplary network-triggered network handover according to exemplary embodiments presented herein;

[0066] Figure 11 A diagram illustrating messages exchanged and processes performed by entities participating in a second exemplary network-triggered network handover according to exemplary embodiments presented herein;

[0067] Figure 12 A flowchart illustrating exemplary operations performed in a UE participating in network-initiated mobility according to exemplary embodiments presented herein;

[0068] Figure 13 A flowchart illustrating exemplary operations performed in an SP participating in network-initiated mobility according to exemplary embodiments presented herein;

[0069] Figure 14 A flowchart illustrating exemplary operations performed in an SP initiating network-initiated mobility according to exemplary embodiments presented herein;

[0070] Figure 15 An exemplary communication system according to exemplary embodiments presented herein is shown;

[0071] Figure 16A and Figure 16B shows an exemplary apparatus in which the methods and teachings according to the present disclosure may be implemented; and

[0072] Figure 17 is a block diagram of a computing system that can be used to implement the various apparatus and methods disclosed herein. DETAILED DESCRIPTION

[0073] The structure and use of the disclosed embodiments are discussed in detail below. However, it should be understood that the present disclosure provides many applicable concepts that can be embodied in a variety of specific contexts. The specific embodiments discussed are merely illustrative of the specific structure and use of the embodiments and do not limit the scope of the present disclosure.

[0074] Figure 1 A first exemplary communication system 100 is shown. The communication system 100 includes an access node 110 having a coverage area 101, serving user equipment (UE) such as UE 120. The access node 110 is connected to a backhaul network 115, which provides connectivity to services and the internet. In a first mode of operation, communications to and from the UE traverse the access node 110. In a second mode of operation, communications to and from the UE do not traverse the access node 110, however, the access node 110 typically allocates resources for the UE to use for communication when specific conditions are met. In the second mode of operation, communications between a pair of UEs occur over sidelinks 125, which include unidirectional communication links. Communications between a pair of UEs and an access node also occur over unidirectional communication links, where the communication link between the UE and the access node is referred to as an uplink 130 and the communication link between the access node and the UE is referred to as a downlink 135.

[0075] Access nodes can also be generally referred to as Node B, evolved Node B (eNB), next generation (NG) Node B (gNB), master eNB (MeNB), secondary eNB (SeNB), master gNB (MgNB), secondary gNB (SgNB), network controller, control node, base station, access point, transmission point (TP), transmission-reception point (TRP), cell, carrier, macro cell, femto cell, pico cell, etc., and UE can also be generally referred to as mobile station, mobile phone, terminal, user, subscriber, site, etc. The access node may provide wireless access according to one or more wireless communication protocols, such as 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), 5G, 5G LTE, 5G NR, sixth generation (6G), high speed packet access (HSPA), IEEE 802.11 series standards such as 802.11a / b / g / n / ac / ad / ax / ay / be, etc. Although it is understood that the communication system may employ multiple access nodes capable of communicating with multiple UEs, for simplicity, only one access node and two UEs are shown.

[0076] Due to the mobile nature of UEs, they often exit the coverage area of a first network entity or access network (AN) and enter the coverage area of a second network entity or AN. In this case, a network handover is performed to move the UE from the coverage area of the first network entity or AN to the coverage area of the second network entity or AN. A special case of network handover is handover (HO). In HO, the UE typically moves relative to a serving entity (e.g., an access node of a single network). Figure 2 A communication system 200 is shown highlighting a network handover. The communication system 200 includes a first AN (AN#1) 205 and a second AN (AN#2) 207. A UE 210 receives services from a service provider (SP) 215 via a connection with a gNB 220.

[0077] However, since UE 210 is mobile, it moves toward the periphery of AN#1 205, and the quality of the connection with gNB 220 degrades. However, the deployment of communication system 200 causes the coverage of AN#2 207 to overlap with that of AN#1 205, and when UE 210 exits the coverage of AN#1 205, UE 205 also enters the coverage of AN#2 207. Therefore, to continue receiving services from SP 215, UE 210 participates in a network handover to establish a new connection with SP 215 through gNB 222 of AN#2 207, while disconnecting from gNB 220.

[0078] AN#1 205 and AN#2 207 of the communication system 200 can be any of various access networks, including public networks (PN) (such as public line mobile networks (PLMN)), non-public networks (NPN), independent NPNs (SNPN), etc.

[0079] One area of research regarding network enhancements for private networks relates to enhancements to support mobility in SNPNs, with a particular focus on credentials held by entities separate from the SNPN.

[0080] Figure 3A The communication system 300 is shown highlighting that UE 305 obtains services from SP (SP#3) 310 through SNPN#1 312. Figure 3A As shown, UE 305 is served by SP 310 via gNB 314 of SNPN #1 312. However, when UE 305 moves, UE 305 has to continue to serve SP 310 via gNB 316 of SNPN #2 318. In other words, UE 305 moves from gNB 314 of SNPN #1 312 to gNB 316 of SNPN #2 318 to continue to serve SP 310, and thus UE 305 participates in a network handover from SNPN #1 312 to SNPN #2 318.

[0081] Figure 3B The diagram shows a communication system 350 highlighting that UE 305 obtains services from SP (SP#1) 355 via NPN 367 (which includes its own radio access network (RAN) 369 and 5G core network (5GC) 371). The services 373 provided by SP 355 may include, for example, services provided by the Internet Protocol (IP) multimedia subsystem (IMS). Figure 3BAs shown, UE 305 is served by SP 355 via a connection to NPN 367 and PN 375 (which includes its own RAN 377 and 5GC 379). However, when UE 305 moves, UE 305 must continue to receive service from SP 355, but has moved away from NPN 367. In this case, UE 305 continues to receive service from SP 355 via PN 375. In other words, UE 305 participates in a network handover from NPN 367 to PN 375.

[0082] Existing techniques for supporting UE mobility require a UE-initiated protocol data unit (PDU) session establishment procedure involving the UE and a first SNPN, where the first SNPN is a voyaging visitor network (V-SNPN), and the UE's data anchor is located in the home SP. The data anchor utilizes home routing. When the UE moves from the first SNPN to the second SNPN, the existing techniques operate as if the UE has moved from one V-SNPN to another.

[0083] Figure 4 shows a communication system 400 highlighting the prior art of supporting UE mobility. The communication system 400 includes a UE 305 and a V-SNPN 405 participating in a UE-initiated PDU session establishment procedure, and the UE 305 obtains services using a Home SP 407. For example, the Home SP 407 may be a PLMN or a SNPN.

[0084] The V-SNPN 405 includes: a RAN (or AN) 409 that provides connectivity between the UE 305 and the V-SNPN 405; an access and mobility management function (AMF) 411 that handles connectivity and mobility management tasks; a visitor session management function (V-SMF) 413 that interacts with the decoupled data plane (including managing PDU sessions); and a visitor user plane function (V-UPF) 415 that provides interconnection between the RAN 409 and the data network of the V-SNPN 405.

[0085] The home SP 407 includes: a home UPF (H-UPF) 417 that provides interconnection between the mobile infrastructure of the home SP 407 and the data network 419; a home policy charging function (H-PCF) 421 that manages control plane functions; a home SMF (H-SMF) 423 that interacts with the decoupled data plane of the home SP 407; and a unified data management (UDM) 425 that integrates different data sources.

[0086] Figure 5 shows a diagram 500 of the communications exchanged and the processing performed by entities involved in supporting UE mobility in the prior art. The participating entities include UE 305, RAN 409, AMF 411, V-UPF 415, V-SMF 413, H-UPF 417, H-SMF 423, H-PCF 421, and UDM 425.

[0087] The prior art includes: UE 305 sending a PDU session establishment request (event 505); SMF selection by V-SNPN 405 (event 507); UPF selection by V-SNPN 405 (event 509); PDU session authentication and authorization (event 511); and UPF selection by Home SP 407 (event 513). The selection of entities and the communications exchanged between the entities establish the PDU session requested by UE 305.

[0088] However, existing technologies only initiate network handovers from the UE 305. Therefore, there is no solution in which the network (or its entities) can trigger and control network handovers between NPNs (or SNPNs) or between an NPN and a PLMN. For example, for load balancing purposes, the network can trigger a network handover from a first SNPN to a second SNPN. Existing network-initiated mobility support only occurs within the same network.

[0089] Since Home SP 407 may have service level agreements (SLAs) with different network providers (NPN, SNPN, PLMN, etc.), Home SP 407 may steer UE 305 to different networks supported by different network providers, wherein the network to which UE 305 is steered may be based on business needs or applications. For example, if the hotspot provided by the SNPN is overloaded or there are some other conditions that restrict new UEs, Home SP 407 may steer low-priority UEs to a PLMN that has coverage for low-priority UEs and has an SLA with Home SP 407, while reserving the SNPN for high-priority UEs.

[0090] Therefore, there is a need for methods and apparatus for supporting network-initiated mobility in NPNs (or SNPNs). The methods and apparatus can provide support for network-initiated mobility when a UE moves between NPNs (or SNPNs) or between an NPN and a PLMN.

[0091] According to exemplary embodiments, methods and apparatus are provided for supporting network-initiated mobility in an NPN. The methods and apparatus provided herein support network-initiated mobility of a UE between NPNs or between an NPN and a PLMN. In one embodiment, the network triggers UE mobility, such as a network handover, to trigger the UE to perform a mobility procedure to a target network (which may be, for example, an NPN, SNPN, PN, or PLMN).

[0092] In one embodiment, in the above-described method and apparatus, the network uses enhanced UE provisioning or configuration capabilities to send information to the UE, where the information includes target network information. After selecting the target network, the network instructs the UE to switch to the target network. For example, the network sends a message to the UE including information associated with the target network. This information may be in the form of an identifier of the target network, such as a SNPN ID, PLMN ID, NPN ID, etc. This information may be sent in the form of an indicator, such as a network handover indicator. For example, this information may be sent during a UE configuration update procedure.

[0093] The indicator may include a trigger to cause the UE to scan for potential target networks and report the scan results to the network. The indicator may also include a network handover policy to assist the UE in making a network handover decision. For example, the indicator may include a performance threshold (such as an application-level performance threshold) or a location trigger for causing the UE to initiate a network handover.

[0094] This information may also include a time or duration. The time may specify when the UE should initiate (or complete, depending on the implementation) a mobility procedure to switch to the target network. The duration may specify a time window within which the UE should complete (or initiate, depending on the implementation) a mobility procedure to switch to the target network. If the duration is set to 0, the UE immediately (or as soon as possible) initiates a mobility procedure to switch to the target network.

[0095] In one embodiment, in the above-mentioned method and apparatus, the network uses enhanced application functionality to influence traffic routing capabilities by introducing new information about network switching instructions. The new information prepares and triggers the UE to switch to the target network. The network can also prepare the target network for network switching. For example, the network uses information associated with the target network to update UE policy information and provides the UE policy information to the UE. The information associated with the target network includes, for example, NPN ID, SNPN ID, PLMNID, etc. The network can provide UE policy information to the UE through a UE configuration update procedure or a UE parameter update procedure, for example. However, the information associated with the target network may be included in a UE route selection policy (URSP) or in a new UE policy containing a new UE routing rule, which includes a traffic descriptor.

[0096] In one embodiment, an application function (AF) may use a new message to provide a request to the network to instruct the UE to perform an activity, including network handover to a target network, deregistration, etc. In one embodiment, an existing message may be enhanced to provide a request to the network to instruct the UE to perform an activity. An example of such an enhanced message is a UE policy / configuration update message.

[0097] In one embodiment, the network uses information provided by the UE to select a target network for network handover. For example, the network selects the target network based on the UE's measurements of potential target networks. The potential target networks may be network-configured and provided to the UE in the form of a preferred network list. The UE may use its location to determine the potential target networks and determine the signaling status of the potential target networks. The signaling status may be an indication of whether the signal strength of the potential target network meets a signal strength threshold. The UE may use its location to determine the potential target networks and measure transmissions performed by the potential target networks. For example, the potential target networks include networks in the preferred network list that are within a distance threshold of the UE. As another example, the potential target networks include networks in the preferred network list whose transmission measurements exceed a signal strength threshold. The UE reports the transmission measurements or signaling status to the network.

[0098] In one embodiment, the update of the preferred network list triggers the UE to perform repeated measurements on potential target networks, which may result in reselection of the target network. For example, the update of the preferred network list may result in the selection of a target network with a potentially higher priority.

[0099] As another example, the network selects a target network based on measurements of potential target networks performed by the network based on the UE's location. The UE may report its location to the network, or the network may perform measurements to determine the UE's location (e.g., location service (LCS)). Based on the UE's location, the network may then query a preferred network list for potential target networks that meet a distance threshold or provide coverage for the UE, for network coverage or status information. For example, the network may query the potential target network for performance information about the potential target network.

[0100] Figure 6 A high-level view of a communication system 600 supporting network-initiated mobility in an NPN is shown. Communication system 600 includes a UE 305 with connectivity provided by a serving network 605. Serving network 605 is operated by operator A and includes network functions NF1 607 and NF2 609. Serving network 605 can be, for example, an NPN or a SNPN. UE 305 is utilizing services provided by SP C 611. UE 305 is also within the coverage of a target network 613, which can be, for example, an NPN, a SNPN, or a PLMN. Target network 613 includes network functions NF3 615 and NF4 617.

[0101] When UE 305 is within overlapping coverage of serving network 605 and target network 613, SP C 611 plans to move UE 305 from serving network 605 to target network 613. Using information including a preferred network list provided by SP C 611 to UE 305, SP C 611 instructs UE 305 to collect and report transmission measurements of potential target networks, which in this example include target network 613.

[0102] SP C 611 selects a target network 613 based on the transmission measurement values reported by UE 305 and instructs UE 305 to switch to target network 613. SP C 611 interacts with serving network 605 and target network 613 to prepare for the handover between serving network 605 and target network 613. UE 305 performs the network handover and is able to connect to target network 613 without service interruption.

[0103] SP C 611 may also be a network operator that also provides network connection services to UE 305 .

[0104] The deployment is considered to present a prior art solution initiated by the UE: a UE 305 belonging to a company is located in an area covered by two SNPN networks, namely a first SNPN provided by provider_1 and a second SNPN provided by provider_2. Using the prior art solution, the UE 305 will use the stored preferred roaming list associated with the company to select the first SNPN (provider_1) or the second SNPN (provider_2). For example, the UE 305 will select and use the second SNPN (provider_2). If the prior art solution is being used and the UE 305 is not moving, if the UE 305 does not lose the signal from the second SNPN (provider_2), the UE 305 cannot move seamlessly to the first SNPN (provider_1). In addition, the company cannot guide the UE 305 moving from the second SNPN (provider_2) to the first SNPN (provider_1). In other words, UE 305 must manually disconnect from the second SNPN (Provider_2) and select the first SNPN (Provider_1) to which it wants to connect; or if UE 305 is moving out of the coverage of the second SNPN (Provider_2), UE 305 performs a network scan and selects the first SNPN (Provider_1).

[0105] In contrast, the exemplary embodiments presented herein will allow the company to direct the UE 305 to switch from the second SNPN (Provider_2) to the first SNPN (Provider_1) without interrupting service when the UE 305 is not moving and is in the overlapping coverage area of the second SNPN (Provider_2) and the first SNPN (Provider_1).

[0106] Figure 7The architecture of a first exemplary communication system 700 is shown, highlighting enhanced operations to support network-initiated mobility. Communication system 700 includes a UE 305, SNPN #1 312, SNPN #2 318, and an SP 310. Communication system 700 includes entities enhanced to support network-initiated mobility. These entities include the UE 305, AMFs 705 and 707, UDMs 709 and 711, NEFs 713 and 715, and AF 717. Enhancements to the AMFs 705 and 707 include enhancements to the control plane interactions between the AMFs 705 and 707 and the UE 305 to support network-triggered UE mobility handovers between different networks belonging to different operators. Enhancements to the NEFs 713 and 715 include enhancements to the control interface and the addition of new information elements for exchanging mobility messages between the UE 305 and the SP 310, and between the SP 310 and the underlying network. Enhancements to the UE 305 include support for new control plane interactions between the AMFs 705 and 707 and the UE 305 to support network-triggered UE mobility handover between different networks belonging to different operators, as well as support for new interactions (including new interfaces) between the UE 305 and the SP 310 for mobility management. Enhancements to the UDMs 709 and 711 include support for storing potential target networks, preferred network lists, bootstrapping, and connection policies. Enhancements to the AF 717 include bootstrapping information from the application side.

[0107] Figure 8The architecture of a second exemplary communication system 800 is shown, highlighting enhanced operations to support network-initiated mobility. Communication system 800 includes UE 305, PLMN#1 375, SNPN#2 367, and SP 310. Communication system 800 includes entities enhanced to support network-initiated mobility. These entities include UE 305, AMFs 705 and 707, UDMs 709 and 711, NEFs 713 and 715, and AF 717. Enhancements to AMFs 705 and 707 include enhancements to the control plane interactions between AMFs 705 and 707 and UE 305 to support network-triggered UE mobility handovers between different networks belonging to different operators. Enhancements to NEFs 713 and 715 include enhancements to the control interface and the addition of new information elements for exchanging mobility messages between UE 305 and SP 310, and between SP 310 and the underlying network. Enhancements to the UE 305 include support for new control plane interactions between the AMFs 705 and 707 and the UE 305 to support network-triggered UE mobility handover between networks belonging to different operators, as well as support for new interactions (including new interfaces) between the UE 305 and the SP 310 for mobility management. Enhancements to the UDMs 709 and 711 include support for storage of potential target networks, preferred network lists, bootstrapping, and connection policies. Enhancements to the AF 717 include bootstrapping information from the application side.

[0108] Related to SP-triggered mobility: These embodiments are used for the case when the UE 305 is located in overlapping coverage areas from 2 different networks (SNPN#1 312 or SNPN#2 318 or PLMN) belonging to different operators and can easily be handed over between the RANs of the two different networks or between different core networks with a shared RAN.

[0109] The exemplary embodiments provide a new mechanism that allows the SP 310 to know which networks have coverage for the UE 305 before network switching. This will help the SP 310 make decisions about the mobility of the UE 305. There are several ways to achieve this:

[0110] Option 1: Send an indication message to allow UE 305 to report potential target networks in UE 305's current location and their signaling status to SP 310. This indication message can be delivered from AF 717 to UE 305 via enhanced NEF 713 or 715, or can be transmitted via an application-level protocol. UE 305 can scan as instructed and report the scan results to AF 717. This report can provide potential SNPN IDs of potential target networks in UE 305's preferred network list.

[0111] The preferred network list may be pre-configured in the UE 305 or sent by the AF 717 as part of the report indication information. The latter may be sent from the AF 717 to the UE 305 via the NEF / AMF by enhancing the provisioning capability of the UE 305 or the network monitoring capability of the UE 305. If the AF 717 provides the UE 305 with an updated preferred network list via the serving network, the UE 305 may replace its pre-configured or existing preferred network list with the updated preferred network list.

[0112] In addition to network switching, the preferred network list provided by SP 310 can also be used by UE 305 for network selection for initial network access.

[0113] - Option 2: Based on the location of UE 305, SP 310 queries network coverage and status information from potential target networks (i.e., target networks that have network coverage for UE 305). This option does not require changes to the UE, but enhances the interaction between SP 310 and the network service provider.

[0114] - Option 3: Use the mobility container in the NAS messages between the UE 305 and the AF 717 to carry common mobility management protocols, such as 802.21 that rely on the underlying radio access technology, in order to support multi-radio access technology network handover between different networks belonging to different operators.

[0115] -Since PLMN and NPN have differences in network selection and network authentication and authorization, AF 717 can provide UE 305 with different target network information to be used for PLMN and SNPN, such as different IDs, different credentials (3GPP or non-3GPP credentials), etc.

[0116] After SP 310 obtains information about potential target networks that have coverage for UE 305, SP 310 may make a decision to handover UE 305 between networks where UE 305 has coverage.

[0117] In another embodiment, the SP 310 may be allowed to provide the preferred network list to the UE 305 by providing a selection policy to the UE 305 from a network management function such as an access network discovery and selection function (ANDSF), so as to provide a network selection policy to the UE 305. The network selection function (e.g., ANDSF) may be located in the SP 310 or in a serving network to which the UE 305 is connected. If the network selection function is located in the serving network, the SP 310 may provide the preferred network list to the serving network provider through its interaction interface with the serving network provider, such as an NEF / AF interface.

[0118] To move a UE from one network to another, several options are provided:

[0119] - Option 1: SP 310 can use the enhanced UE provisioning / configuration capabilities provided by the serving network to send an indication with target network information to UE 305. After UE 305 receives the indication, UE 305 can use existing procedures to move to the target network. Detailed procedure examples are discussed herein.

[0120] The indication may also include a network switching window (time or duration) during which the UE may perform network switching. In the case where the network switching window is set to 0, the UE immediately (or as soon as possible) initiates a mobility procedure to switch to the target network.

[0121] The indication may include a trigger that causes the UE 305 to scan all available networks and report the results to the SP 310 .

[0122] The indication may also include a network handover policy for assisting the UE 305 in making a network handover decision, for example, a performance threshold or location trigger for the UE to initiate a network handover, wherein the performance threshold includes application-level performance.

[0123] Option 2: Enhanced application functionality impacts traffic routing capabilities by introducing new information for network handover instructions from the SP 310 to the serving SNPN (e.g., SNPN #1 312) to prepare and trigger the UE 305 to move to another network (i.e., the target network), and also providing additional information or instructions to allow the SP 310 to prepare the target network and thus prepare for network handover. Detailed process examples are discussed herein.

[0124] For the above two options, a common container can be introduced in the existing control messages between UE 305 and the network to carry mobility commands from SP 310 to UE 305. These mobility commands can use other industry standards or protocols, such as 802.21. 3GPP is used as a carrier for these command messages.

[0125] An embodiment provides a UE capability indication indicating whether the UE 305 can support network-initiated mobility between different networks belonging to different operators, which is sent by the UE 305 to the network or can be set as part of the UE subscription information.

[0126] The procedure examples shown below may also be applied to UE mobility between a SNPN and a PLMN or between PLMNs.

[0127] Figure 9 Diagram 900 illustrates communications exchanged and processing performed by entities involved in the UE Report Potential Target Networks procedure. The communications and processing described above, for example, reuse existing 3GPP functions and procedures, but with information elements (IEs) of an embodiment. The participating entities include UE 305, RAN 409, AMF 705, UDM 709, Network Data Analytics Function (NWDAF) 905, NEF 713, and SP 310 (via AF 717). RAN 409, AMF 705, UDM 709, NWDAF 905, and NEF 713 are NFs of serving network 605.

[0128] SP 310 requests UE 305 to report potential target networks by sending a UE Provisioning Update message to NEF 713 (Event 910). The UE Provisioning Update message includes an indicator instructing UE 305 to report potential target networks. The UE Provisioning Update message may optionally include a new or updated preferred network list. NEF 713 sends the UE Provisioning Update message to UDM 709, which sends the UE Provisioning Update message to AMF 705 (Event 912). The UE Provisioning Update message may be sent to UDM 709 (and then AMF 705) using a UE Configuration Update procedure. Existing UE Configuration Update procedures may be used. The UE Provisioning Update message includes an indicator instructing UE 305 to report potential target networks. The UE Provisioning Update message may optionally include a new or updated preferred network list.

[0129] AMF 705 sends a UE provision update message to UE 305 (event 914). The UE provision update message may be sent to UE 305, for example, via RAN 409. The UE provision update message includes an indicator instructing UE 305 to report potential target networks. The UE provision update message may optionally include a new or updated preferred network list. UE 305 identifies the potential target network (block 916). UE 305 may identify the potential target network by scanning available networks for access, and may identify the potential target network based on the preferred network list and the scan results from SP 310. For example, UE 305 scans available networks and compares the scan results with the preferred network list, where the potential target network includes a network that is both in the scan results and in the preferred network list and that meets any requirements or restrictions associated with the networks found in the scan.

[0130] SP 310 subscribes to UE status reports (Event 918). Subscribing to UE status reports involves exchanging messages with NEF 713 and NWDAF 905. Subscribing to UE status reports enables SP 310 to be notified of changes in the status of UE 305. For example, if NWDAF 905 detects a change in the status of UE 305, NWDAF 905 sends updates to SP 310 and other network entities that subscribe to UE status reports for UE 305.

[0131] UE 305 sends a network access stratum (NAS) message to AMF 705 to report potential target networks (event 920). The NAS message includes the potential target networks (e.g., identification of the potential target networks) and optionally includes measurements of the potential target networks (e.g., signal strength measurements). UE 305 sends a UE status update notification to NWDAF 905 to report the potential target networks (event 922). The UE status update notification, for example, includes the potential target networks (e.g., identification of the potential target networks). NWDAF 905 sends an event notification to NEF 713, which forwards the event notification to SP 310 to report the potential target networks (event 924). The event notification includes a report of the potential target networks (and optionally, the measurements of the potential status reports).

[0132] In one embodiment, the reporting of potential target networks (and optionally, the measurements of potential target methods) is not visible to the serving network 605, meaning that the reporting is encrypted or encapsulated in control messages transmitted over the serving network 605. The control messages include the messages transmitted in events 920, 922, and 924.

[0133] Figure 10Diagram 1000 illustrates communications exchanged and processes performed by entities participating in a first exemplary network-triggered network handover. The first exemplary network-triggered network handover is triggered by sending an indication instructing a network handover. The communications and processes described above, for example, reuse existing 3GPP functions and procedures, but with information elements (IEs) of an exemplary embodiment. The participating entities include UE 305, RAN 1005 (of SNPN#1 312), AMF 707 (of SNPN#1 312), UPF 1007 (of SNPN#1 312), NEF 715 (of SNPN#1 312), RAN 1009 (of SNPN#2 318), NEF 713 (of SNPN#2 318), AMF 705 (of SNPN#2 318), SMF 1011 (of SNPN#2 318), AF 717 (of SP 310) and UPF 1013 (of SP 310).

[0134] SP 310 transmits the UE configuration update to NEF 715 via AF 717 (event 1020). The UE configuration update includes an indicator that instructs UE 305 to switch from SNPN #1 312 to SNPN #2 318. The UE configuration update may optionally include a time or duration associated with the network switch. For example, the time specifies a time before which UE 305 should start or complete the network switch. For another example, the duration specifies a time window during which UE 305 should start or complete the network switch. If the duration is set to 0, the UE immediately (or as soon as possible) initiates a mobility procedure to switch to the target network.

[0135] NEF 715, AMF 707, and UE 305 participate in the UE Configuration Update procedure (Event 1022). The participant in the UE Configuration Update procedure transmits an indicator to UE 305 indicating that UE 305 should switch to SNPN #2 318. UE 305 triggers a network handover to SNPN #2 318 (Block 1024). The existing UE-initiated PDU Session Establishment procedure is performed (Block 1032). The UE-initiated PDU Session Establishment procedure is used to switch UE 305 from SNPN #1 312 to SNPN #2 318.

[0136] As an option, AF 717 and NEF 713 share a UE parameter provision message for the expected UE behavior of UE 305 (event 1026). The UE parameter provision message allows SP 310 to notify SNPN#2 318 (target network) to prepare for UE 305 (incoming UE), for example, for fast network handover. This enhances the existing network notification of expected UE behavior by NEF 713. The UE parameter provision message includes the identity of UE 305 (incoming UE) and the expected behavior of UE 305. NEF 713 provides the expected UE behavior of UE 305 to AMF 705 (event 1028) and provides the expected UE behavior of UE 305 to RAN 1009 (event 1030).

[0137] As an option, if UE 305 does not switch to SNPN#2 318 before the specified time or duration, SP 310 sends a cancel or notify message to SNPN#2 318 to cancel the network switch (event 1034). SNPN#2 318 also releases any resources allocated to UE 305 and the network switch.

[0138] Figure 11 Diagram 1100 illustrates communications exchanged and processes performed by entities participating in a second exemplary network-triggered network handover. The second exemplary network-triggered network handover is triggered by updating UE policy information. The communications and processes described above, for example, reuse existing 3GPP functions and procedures, but with information elements (IEs) of an exemplary embodiment. The participating entities include UE 305 (incoming UE), RAN 1005 (of SNPN#1 312), AMF 707 (of SNPN#1 312), SMF+UPF 1105 (of SNPN#1 312), NEF 715 (of SNPN#1 312), RAN 1009 (of SNPN#2 318), NEF 713 (of SNPN#2318), AMF 705 (of SNPN#2 318), SMF+UPF 1107 (of SNPN#2 318), AF 717 (of SP 310) and UPF 1013 (of SP310).

[0139] SP 310 updates the expected UE behavior by transmitting a UE parameter provision message for the expected UE behavior to NEF 713 via AF 717 (Event 1120). The UE parameter provision message for the expected UE behavior includes the identity of the incoming UE (i.e., UE 305) and the expected behavior of UE 305. NEF 713 provides the expected incoming UE behavior to prepare for UE 305 by transmitting the expected incoming UE behavior to AMF 705 (Event 1122). AMF 705 provides the expected incoming UE behavior in response to NEF 713 (Event 1124).

[0140] AMF 705 selects an SMF (e.g., SMF+UPF 1107), which in turn selects a UPF for UE 305 (Event 1126). SMF+UPF 1107 and UPF 1013 (of SP 310) participate in the PDU establishment process (Event 1128).

[0141] AF 717 transmits a UE deregistration message to NEF 715 (event 1130). The UE deregistration message includes the network identifier of the target network (SNPN#2 318) to which UE 305 is to be handed over. NEF 715 sends a network-initiated deregistration request to UE 305 (event 1132). The network-initiated deregistration request may be sent using existing procedures, except for the following:

[0142] (1) NEF 715 provides a deregistration request to the UDM of SNPN#1 312, which then triggers the process; and

[0143] (2) The network-initiated deregistration request message from the AMF 707 to the UE 305 includes the cause of the deregistration and the identifier of the target network, e.g., SNPN#2 318.

[0144] UE 305 switches to SNPN #2 318 (block 1134). As an option, if UE 305 does not switch to SNPN #2 318 before a specified time or duration, SP 310 sends a cancel or notify message to SNPN #2 318 to cancel the network switch (event 1136). SNPN #2 318 also releases any resources allocated to UE 305 and the network switch.

[0145] UE 305 initiates a PDU session establishment procedure with SNPN#2 318 (Event 1138). The PDU session establishment procedure, for example, establishes a data connection between UE 305 and SNPN#2 318. UE 305 communicates with SP 310 through SNPN#2 318 (Event 1140).

[0146] In one embodiment, event 1120 between AF 717 and NEF 713 allows SP 310 to notify the target network (SNPN #2 318) to prepare for a fast network handover for UE 305, which enhances the existing network notification of expected UE behavior by NEF 713. Alternatively, new messages between AF 717 and NEF 713 can be used to deliver information related to UE 305 to the target network.

[0147] Figure 12 A flow diagram illustrating example operations 1200 performed in a UE participating in network-initiated mobility is shown. Operations 1200 may be indicative of operations performed in a UE (e.g., UE 305) that is a UE participating in network-initiated mobility.

[0148] Operations 1200 begin with the UE receiving a candidate network report request (block 1205). The candidate network report request may be received, for example, from a service provider (SP) serving the UE. The candidate network report request may be received, for example, via a NAS message from the AMF of the SP. The UE scans for networks (block 1207). The UE scans for networks near its location and collects network identities and signal measurements (e.g., signal strength measurements) for the networks.

[0149] The UE uses the preferred network list to identify potential target networks (block 1209). The UE uses the results of the scan (block 1207) and the preferred network list to identify potential target networks that it can access. For example, there may be some networks that the UE is able to scan, but these networks do not grant the UE access. Access to these networks may be limited due to subscription type, UE priority, network load, etc.

[0150] The UE reports potential target networks (block 1211). For example, the UE reports a list of potential target networks to the SP. The list may include identifiers of the potential target networks. The list may also include information related to signal measurements of the potential target networks. The report may be sent to the SP, for example, via a NAS message. Alternatively, the report may be sent to the SP using any other network protocol.

[0151] The UE checks to determine whether it has received a network handover instruction (block 1213). The UE may check to determine whether it has received a network handover instruction instructing the UE to handover to a target network, such as SNPN#2 as specified in the network handover instruction. This network may be one of the potential target networks previously reported by the UE.

[0152] If the UE has received the network switching instruction, the UE initiates a PDU session establishment procedure to switch from its serving network (eg, SNPN#1) to the target network (eg, SNPN#2) (block 1215). The PDU session establishment procedure performed by the UE may be as described above.

[0153] If the UE has not received a network handover instruction, the UE receives a deregistration request (block 1217). The deregistration request may be received, for example, from the SP's AMF and include a reason code for handover to the target network. The deregistration request may also include the identity of the target network (e.g., SNPN #2). The UE deregisters from its serving network (e.g., SNPN #1) and accesses and registers with the target network (e.g., SNPN #2) (block 1219). Registration with the target network utilizes, for example, the identity of the target network provided in the deregistration request.

[0154] Figure 13 A flow diagram illustrating example operations 1300 performed in an SP participating in network-initiated mobility is shown. Operations 1300 may be indicative of operations performed in an SP (eg, SP 310) as an SP participating in network-initiated mobility.

[0155] Operations 1300 begin with the SP sending a candidate network report request (block 1305). The candidate network report request may, for example, be sent to a UE served by the SP. The candidate network report request may be sent using a NAS message. The SP receives a report of potential target networks (block 1307). The report of potential target networks may be in the form of a list including identifiers of potential target networks. The list may also include information related to signal measurements of the potential target networks.

[0156] The SP selects a target network (block 1309). The SP selects the target network based on, for example, a report received from the UE. The target network selection may be based on selection criteria, which may include network load, UE subscription level, UE priority, etc.

[0157] The SP sends a network switching instruction (block 1311). The network switching instruction can be sent to the UE, for example. The network switching instruction instructs the UE to switch to the target network, such as SNPN#2. The network switching instruction includes the identifier of the target network and can optionally include a time or duration for the UE to start or complete the network switching. In one embodiment, if the SP does not send a network switching instruction, the SP can alternatively send a deregistration request. The deregistration request includes a reason code for the network switching to the target network. The deregistration request can also include the identifier of the target network, such as SNPN#2. The SP participates in the network switching process (block 1313).

[0158] Figure 14A flow diagram illustrates example operations 1400 performed in an SP initiating network-initiated mobility. Operations 1400 may be indicative of operations performed in an SP (eg, SP 310) acting as an SP initiating network-initiated mobility.

[0159] Operations 1400 begin with the SP receiving a report having information related to the location of the UE (block 1405). The report may be received from the UE. For example, the report may include information related to potential target networks that are in close proximity to the UE. For example, the potential target network may meet a distance threshold relative to the UE, or the signal strength of the potential target network's transmission may meet a signal strength threshold. As another example, the report may include information related to the location of the UE.

[0160] Optionally, the SP measures potential target networks (block 1407). For example, where the report includes information related to the UE's location, the SP identifies potential target networks that meet a distance threshold relative to the UE, or measures the signal strength of transmissions of potential target networks that may meet a signal strength threshold.

[0161] The SP selects a target network (block 1409). The SP selects a target network from potential target networks based on, for example, selection criteria. Examples of selection criteria may include network load, UE subscription level, UE priority, etc. The SP sends a message with information related to the target network (block 1411). This message may, for example, be sent to the UE. The message may include an identifier of the target network and, optionally, a time or duration for the UE to initiate or complete network handover. The SP participates in the network handover process (block 1413).

[0162] Figure 15 An exemplary communication system 1500 is shown. Generally, system 1500 enables multiple wireless or wired users to transmit and receive data and other content. System 1500 can implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0163] In this example, the communication system 1500 includes electronic devices (EDs) 1510a to 1510c, radio access networks (RANs) 1520a to 1520b, a core network 1530, a public switched telephone network (PSTN) 1540, the Internet 1550, and other networks 1560. Figure 15 A certain number of these components or elements are shown in FIG, but any number of these components or elements may be included in system 1500.

[0164] EDs 1510a to 1510c are configured to operate or communicate in system 1500. For example, EDs 1510a to 1510c are configured to transmit or receive via a wireless or wired communication channel. Each ED 1510a to 1510c represents any suitable end-user device and may include (or may be referred to as) user equipment (UE), a wireless transmit / receive unit (WTRU), a mobile station, a fixed or mobile subscriber unit, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a computer, a touchpad, a wireless sensor, or a consumer electronic device.

[0165] RANs 1520a and 1520b herein include base stations 1570a and 1570b, respectively. Each base station 1570a and 1570b is configured to wirelessly connect to one or more EDs 1510a through 1510c to provide access to a core network 1530, the PSTN 1540, the Internet 1550, and / or other networks 1560. For example, base stations 1570a and 1570b may include or be one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNodeB), a next-generation NodeB (gNB), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. EDs 1510a through 1510c are configured to connect to and communicate with the Internet 1550 and provide access to the core network 1530, the PSTN 1540, or other networks 1560.

[0166] exist Figure 15In the illustrated embodiment, base station 1570a forms part of RAN 1520a, which may include other base stations, components, and / or devices. Furthermore, base station 1570b forms part of RAN 1520b, which may include other base stations, components, or devices. Base stations 1570a and 1570b each operate to transmit or receive wireless signals within a specific geographic area (sometimes referred to as a "cell"). In some embodiments, multiple-input multiple-output (MIMO) technology may be employed, with each cell having multiple transceivers.

[0167] Base stations 1570a through 1570b communicate with one or more EDs 1510a through 1510c using wireless communication links over one or more air interfaces 1590. The air interface 1590 may utilize any suitable radio access technology.

[0168] It is contemplated that system 1500 may utilize multi-channel access capabilities, including the schemes described above. In certain embodiments, the base station and ED implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may also be used.

[0169] RANs 1520a and 1520b communicate with core network 1530 to provide voice, data, application, Voice over Internet Protocol (VoIP), or other services to EDs 1510a through 1510c. It should be understood that RANs 1520a and 1520b or core network 1530 may communicate directly or indirectly with one or more other RANs (not shown). Core network 1530 may also serve as a gateway to other networks, such as PSTN 1540, Internet 1550, and other networks 1560. Furthermore, some or all of EDs 1510a through 1510c may include functionality for communicating with different wireless networks using different wireless technologies or protocols over different wireless links. Instead of (or in addition to) wireless communication, EDs may communicate with service providers or switches (not shown) and Internet 1550 via wired communication channels.

[0170] Although Figure 15 An example of a communication system is shown, but Figure 15 For example, communication system 1500 may include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0171] Figure 16A and Figure 16BExemplary devices are shown that can implement the methods and teachings according to the present disclosure. In particular, Figure 16A An exemplary ED 1610 is shown, Figure 16B Shown is an exemplary base station 1670. These components may be used in system 1500 or any other suitable system.

[0172] like Figure 16A As shown, ED 1610 includes at least one processing unit 1600. Processing unit 1600 implements various processing operations of ED 1610. For example, processing unit 1600 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 1610 to operate in system 1500. Processing unit 1600 also supports the methods and teachings described in more detail above. Each processing unit 1600 includes any suitable processing or computing device for performing one or more operations. For example, each processing unit 1600 may include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application-specific integrated circuit.

[0173] ED 1610 also includes at least one transceiver 1602. Transceiver 1602 is used to modulate data or other content for transmission via at least one antenna or network interface controller (NIC) 1604. Transceiver 1602 is also used to demodulate data or other content received by at least one antenna 1604. Each transceiver 1602 includes any suitable structure for generating signals for wireless or wired transmission, or for processing signals received via wireless or wired means. Each antenna 1604 includes any suitable structure for transmitting or receiving wireless or wired signals. One or more transceivers 1602 can be used in ED 1610, and one or more antennas 1604 can be used in ED 1610. Although shown as a single functional unit, transceiver 1602 can also be implemented using at least one transmitter and at least one separate receiver.

[0174] ED 1610 also includes one or more input / output devices 1606 or interfaces (e.g., a wired interface to the Internet 1550). Input / output devices 1606 facilitate interaction with a user or other devices on a network (network communications). Each input / output device 1606 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0175] In addition, ED 1610 includes at least one memory 1608. Memory 1608 stores instructions and data used, generated, or collected by ED 1610. For example, memory 1608 may store software instructions or firmware instructions executed by processing unit 1600, as well as data used to reduce or eliminate interference in incoming signals. Each memory 1608 includes any suitable volatile or non-volatile storage and retrieval device. Any suitable type of memory may be used, such as random access memory (RAM), read-only memory (ROM), a hard disk, an optical disk, a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.

[0176] like Figure 16B As shown, base station 1670 includes the functionality of at least one processing unit 1650, at least one transceiver 1652, including a transmitter and a receiver, one or more antennas 1656, at least one memory 1658, and one or more input / output devices or interfaces 1666. A scheduler, as will be understood by those skilled in the art, is coupled to processing unit 1650. The scheduler may be included within base station 1670 or operate separately from base station 1670. Processing unit 1650 implements various processing operations of base station 1670, such as signal encoding, data processing, power control, input / output processing, or any other functions. Processing unit 1650 may also support the methods and teachings described in more detail above. Each processing unit 1650 comprises any suitable processing or computing device for performing one or more operations. Each processing unit 1650 may comprise, for example, a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application-specific integrated circuit.

[0177] Each transceiver 1652 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1652 also includes any suitable structure for processing signals received wirelessly or wired from one or more EDs or other devices. Although the transmitter and receiver are shown as a combined unit in transceiver 1652, the transmitter and receiver can be separate components. Each antenna 1656 includes any suitable structure for transmitting or receiving wireless or wired signals. Although a common antenna 1656 is shown coupled to transceiver 1652, one or more antennas 1656 can be coupled to transceiver 1652, allowing separate antennas 1656 to be coupled to the transmitter and receiver when configured as separate components. Each memory 1658 includes any suitable volatile or non-volatile storage and retrieval device. Each input / output device 1666 facilitates interaction with a user or other devices in a network (network communications). Each input / output device 1666 includes any suitable structure for providing information to a user or receiving / providing information from a user, including network interface communications.

[0178] Figure 17 17 is a block diagram of a computing system 1700 that can be used to implement the devices and methods disclosed herein. For example, the computing system can be any entity in a UE, an access network (AN), a mobility management (MM), a session management (SM), a user plane gateway (UPGW), or an access stratum (AS). A particular device may utilize all or only a subset of the components shown, and the degree of integration between devices may vary. In addition, a device may include multiple component instances, such as multiple processing units, processors, memories, transmitters, and receivers. Computing system 1700 includes a processing unit 1702. The processing unit includes a central processing unit (CPU) 1714, a memory 1708, and may also include a mass storage device 1704 connected to a bus 1720, a video adapter 1710, and an I / O interface 1712.

[0179] Bus 1720 may be one or more of any type of bus architecture, including a memory bus or storage controller, a peripheral bus, or a video bus. CPU 1714 may include any type of electronic data processor. Memory 1708 may include any type of non-transient system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In one embodiment, memory 1708 may include ROM for use at startup and DRAM for program and data storage used during program execution.

[0180] The mass storage device 1704 may include any type of non-transitory storage device for storing data, programs, and other information and making such data, programs, and other information accessible via the bus 1720. The mass storage device 1704 may include, for example, one or more of a solid-state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive.

[0181] The video adapter 1710 and the I / O interface 1712 provide interfaces for coupling external input and output devices to the processing unit 1702. As shown, examples of input and output devices include a display 1718 coupled to the video adapter 1710 and a mouse, keyboard, and printer 1716 coupled to the I / O interface 1712. Other devices can be coupled to the processing unit 1702, and additional or fewer interface cards can be used. For example, a serial interface such as a Universal Serial Bus (USB) (not shown) can be used to provide an interface for external devices.

[0182] Processing unit 1702 also includes one or more network interfaces 1706, which may include wired links, such as Ethernet cables, or wireless links for accessing nodes or different networks. Network interfaces 1706 allow processing unit 1702 to communicate with remote units via a network. For example, network interface 1706 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In one embodiment, processing unit 1702 is coupled to a local area network 1722 or a wide area network for processing data and communicating with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0183] It should be understood that one or more steps of the embodiment method provided herein can be performed by corresponding units or modules. For example, a signal can be transmitted by a transmitting unit or a transmitting module. A signal can be received by a receiving unit or a receiving module. A signal can be processed by a processing unit or a processing module. Other steps can be performed by a measuring unit or a module, a selecting unit or a module, a determining unit or a module, an inquiry unit or a module, a reporting unit or a module. Each unit or module can be hardware, software or a combination thereof. For example, one or more of these units or modules can be an integrated circuit, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).

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

Claims

1. A method implemented by a user equipment UE, characterized in that: The method comprises: The UE sends a report including information associated with the location of the UE to a home service provider (SP) of the UE; The UE receives a first message from the home SP, the first message including information associated with one or more target networks, the first message initiating a network handover to change a serving network of the UE from a current network to one of the one or more target networks, wherein the one or more target networks are selected by the home SP based on the information associated with the location of the UE, and the one or more target networks include a private network belonging to an SP different from the home SP; The UE selects the one target network among the one or more target networks; and The UE accesses the target network.

2. The method according to claim 1, characterized in that The home SP owns the UE's service subscription for the service or application that the UE is accessing through the serving network.

3. The method according to claim 1, characterized in that The first message includes a network switching instruction or a network boot instruction.

4. The method according to claim 1 or 2, characterized in that Also includes: receiving, by the UE, a second message from the home SP, the second message including network information associated with one or more candidate networks involved in network handover of the UE, the second message being received before receiving the first message; The UE measures the one or more candidate networks according to the network information; as well as The UE reports measurement information associated with the one or more candidate networks to the home SP.

5. The method according to claim 4, characterized in that The first message or the second message is received in one of a UE configuration procedure or a parameter update procedure.

6. The method according to claim 4, characterized in that The first message is received in a dedicated network control message that directs the UE from the current network to the one target network.

7. The method according to claim 1, characterized in that The first message is received in a policy configuration message for directing the UE from the current network to the one target network based on a service connection policy.

8. The method according to claim 4, characterized in that The first message also includes a time window duration for completing or initiating a network handover procedure.

9. The method according to claim 8, characterized in that When the time window duration is equal to 0, the UE starts the network switching process as soon as possible.

10. The method according to claim 4, characterized in that The second message includes a UE network switching policy.

11. The method according to claim 10, characterized in that The first message includes a network handover policy to assist the UE in making a handover decision.

12. The method according to claim 11, characterized in that The network handover policy includes a performance threshold or a location trigger for the UE to initiate the handover.

13. The method according to claim 12, characterized in that The performance threshold includes application-level performance.

14. The method according to claim 4, characterized in that The network information includes: identifiers of the one or more candidate networks; and identifiers of one or more SPs of the one or more candidate networks.

15. The method according to claim 4, characterized in that The measurement information includes an indicator indicating whether the signal strength of each of the one or more candidate networks is suitable for the UE.

16. A method implemented by a home service provider (SP), characterized in that: The method comprises: receiving, by the home SP, a report from a user equipment UE including information associated with the location of the UE; The home SP selects one or more target networks based on the information; and The home SP sends a first message to the UE, the first message including information associated with the one or more target networks, the first message initiating a network handover to change the UE's serving network from a current network to one of the one or more target networks, the one or more target networks including a private network belonging to an SP different from the home SP.

17. The method according to claim 16, characterized in that Also includes: The home SP sends a second message including a measurement request for one or more candidate networks to the UE.

18. The method according to claim 16 or 17, characterized in that The home SP owns the UE's service subscription for the service or application that the UE is accessing through the serving network.

19. The method according to claim 16 or 17, characterized in that The first message is sent during one of a UE configuration process and a parameter update process.

20. The method according to claim 16, wherein The first message is sent in a dedicated network control message that directs the UE from the current network to the one target network.

21. The method according to claim 16, wherein The first message is sent in a policy configuration message for directing the UE from the current network to the one target network based on a service connection policy.

22. The method according to claim 16 or 17, characterized in that The information includes location information of the UE.

23. The method according to claim 22, characterized in that Also includes: The SP determines one or more candidate networks according to the location information of the UE and a distance threshold; as well as The SP queries the one or more candidate networks to obtain performance information associated with the one or more candidate networks.

24. The method according to claim 16 or 17, characterized in that The information includes performance information associated with one or more candidate networks determined by the UE.

25. The method according to claim 23, characterized in that The one or more target networks are selected from the one or more candidate networks based on the performance information.

26. The method according to claim 25, characterized in that The performance information includes an indicator indicating whether a signal strength of each of the one or more candidate networks is suitable for the UE.

27. A user equipment UE, characterized in that include: one or more processors; as well as a non-transitory memory comprising instructions that, when executed by the one or more processors, cause the UE to: sending a report including information associated with the location of the UE to a home service provider (SP) of the UE; receiving a first message from the home SP, the first message including information associated with one or more target networks, the first message initiating a network handover to change a serving network of the UE from a current network to one of the one or more target networks, wherein the one or more target networks are selected by the home SP based on the information associated with the location of the UE, and the one or more target networks include a private network belonging to an SP different from the home SP; selecting the one of the one or more target networks; and Access the one target network.

28. The UE according to claim 27, wherein: The home SP owns the UE's service subscription for the service or application that the UE is accessing through the serving network.

29. The UE according to claim 27, wherein: The first message includes a network switching instruction or a network boot instruction.

30. The UE according to claim 27 or 28, wherein: The instructions further cause the UE to: receiving a second message from the home SP, the second message including network information associated with one or more candidate networks involved in network handover of the UE, the second message being received before receiving the first message; measuring the one or more candidate networks according to the network information; as well as Measurement information associated with the one or more candidate networks is reported to the home SP.

31. The UE according to claim 30, wherein: The first message or the second message is received in one of a UE configuration procedure or a parameter update procedure.

32. The UE according to claim 30, wherein: The first message is received in a dedicated network control message that directs the UE from the current network to the one target network.

33. The UE according to claim 27, wherein: The first message is received in a policy configuration message for directing the UE from the current network to the one target network based on a service connection policy.

34. The UE according to claim 30, wherein: The first message also includes a time window duration for completing or initiating a network handover procedure.

35. The UE according to claim 30, wherein: The second message includes a UE network switching policy.

36. The UE according to claim 35, wherein: The first message includes a network handover policy to assist the UE in making a handover decision.

37. The UE according to claim 36, wherein: The network handover policy includes a performance threshold or a location trigger for the UE to initiate the handover.

38. The UE according to claim 37, wherein: The performance threshold includes application-level performance.

39. The UE according to claim 30, wherein: The network information includes: identifiers of the one or more candidate networks; and identifiers of one or more SPs of the one or more candidate networks.

40. The UE according to claim 30, wherein: The measurement information includes an indicator indicating whether the signal strength of each of the one or more candidate networks is suitable for the UE.

Images