Limiting route selection policy rules to a few networks

Abstract

A user equipment device is further provided, comprising a receiver, a transmitter, and a processor. The receiver is configured to receive at least one route selection policy rule together with a policy delivery request from a first wireless communications network, the policy delivery request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The transmitter is configured to send a registration request to a second wireless communications network, the network identity of the second wireless communications network is not listed in the list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The processor is configured to not apply the route selection policy rule provisioned from the first wireless communications network.

Description

[Technical Field]

[0001] The subject matter disclosed herein generally relates to the field of enforcing route selection policy rule restrictions on some networks. This specification defines a network node, a method in the network node, a user equipment device, and a method in the user equipment device. [Background technology]

[0002] User Equipment (UE) Route Selection Policy (URSP) rules and procedures for a UE to apply the URSP rules are described in 3GPP TS23.502 v17.3.0 and 3GPP TS23.503 v17.3.0. URSP rules include traffic descriptors that enable a UE to determine whether the URSP rules apply to application traffic. The traffic descriptors include application descriptors that may specify an operating system identity (OSID) and an application identity (OSAppID). The traffic descriptors also include IP flow descriptors, such as the target address of the application traffic, the name of the data network requested by the application, and / or the connection capabilities requested by the application (e.g., IP Multimedia Subsystem (IMS) connection).

[0003] A UE with a valid international mobile subscriber identity may roam from its home public land mobile network (H-PLMN) and access services in the roamed area by using a visited PLMN (V-PLMN). If communication is established, the UE is, in principle, unhindered within the PLMN area.

[0004] S2-2200401 is a change request for TS23.503 v17.3.0 submitted by MediaTek Inc. at TSG-SA WG2 Electronic Meeting #149E on February 14, 2022. It proposes that the UE use only the URSP rules signaled by the PCF of the SNPN access without any means for the HPLMN to indicate to the UE whether the UE can use the URSP rules from the HPLMN. The drawback of this approach is that the UE cannot use operator services when accessing this SNPN. For example, an operator may want to route IMS traffic to the HPLMN through the SNPN network via non-3GPP access or via connectivity to the SNPN through an N3IWF.

[0005] S2-2200640, a 3GPP consultation document titled "Reply LS on PCF in case of SNPN with CH using AUSF / UDM for primary auth" submitted by Huawei at TSG-SA WG2 Telemeeting #149E on February 14, 2022, proposes that for a UE that can access both a PLMN (when not operating in SNPN access mode) and an SNPN using a PLMN subscription (when operating in SNPN access mode), and for a common URSP, the UE is expected to be (pre-)configured with one URSP that is applicable regardless of whether the UE accesses a PLMN or an SNPN. On the other hand, for two URSPs, the UE is expected to be (pre-)configured with one URSP that is applicable when the UE accesses an SNPN and another URSP that is applicable when the UE accesses a PLMN. Such configuration can cause complications when there is a conflict between the URSP rules. It is not clear from the document which URSP rule has priority.

[0006] A Stand-alone Non-Public Network (SNPN) is a wireless communications network that operates without relying on network functions provided by a PLMN, where PCF is a policy control function, CH is a credential holder, and AUSF / UDM refers to an authentication server function and / or unified data manager. The credential holder may be an H-PLMN. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] “Reply LS on PCF in case of SNPN with CH using AUSF / UDM for primary auth”, Huawei, TSG-SA WG2 electronic meeting #149E, February 14, 2022 Summary of the Invention [Problem to be solved by the invention]

[0008] A problem with existing UE route selection policy rules is that they can only be configured by the home PLMN. Furthermore, such rules are universally applied by the UE, regardless of which PLMN the UE is registered in. Different PLMNs may have different traffic profiles, and USRP rules useful for a first PLMN may not be useful for a second PLMN. Typically, a UE roaming from a first PLMN to a second PLMN will have the USRP rules from the first PLMN applied in the second PLMN. This can be disadvantageous.

[0009] Disclosed herein are procedures for restricting route selection policy rules to certain networks, which may be implemented by network nodes within a wireless communications network and by user equipment devices within the wireless communications network. [Means for solving the problem]

[0010] A user equipment device is provided, comprising: a receiver, a transmitter, and a processor. The receiver is configured to receive at least one route selection policy rule together with a policy distribution request from a first wireless communications network. The policy distribution request includes a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The transmitter is configured to send a registration request to a second wireless communications network, wherein a network identity of the second wireless communications network is not listed in the list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The processor is configured to not apply the route selection policy rule provisioned from the first wireless communications network.

[0011] A method in a user equipment device is also provided. The method includes receiving at least one route selection policy rule together with a policy distribution request from a first wireless communications network, the policy distribution request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The method further includes sending a registration request to a second wireless communications network, the network identities of the second wireless communications network not listed in the list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The method further includes not applying the route selection policy rule provisioned from the first wireless communications network.

[0012] A network node in a second wireless communications network is also provided, the network node comprising: a receiver and a processor; the receiver is configured to receive a registration request from a user equipment device, wherein a network identity of the second wireless communications network is not listed in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply; and the processor is configured to register the user equipment device with the second wireless communications network.

[0013] A method in a network node in a second wireless communications network is provided, the method including receiving a registration request from a user equipment device, wherein a network identity of the second wireless communications network is not listed in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply, the method further comprising registering the user equipment device with the second wireless communications network.

[0014] A network node in a third wireless communications network is also provided, the network node comprising: a receiver and a processor. The receiver is configured to receive a registration request from a user equipment device, wherein a network identity of the third wireless communications network is listed in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply. The processor is configured to register the user equipment device with the third wireless communications network.

[0015] To explain how the advantages and features of the present disclosure may be obtained, the description of the disclosure will be expressed by reference to several apparatus and methods that are illustrated in the accompanying drawings. Each of these drawings illustrates only some aspects of the present disclosure and therefore should not be considered limiting of its scope. The drawings may be simplified for clarity and are not necessarily drawn to scale.

[0016] A method and apparatus for restricting route selection policy rules to a number of networks will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief explanation of the drawings]

[0017] [Figure 1A] FIG. 1 illustrates a known system of a wireless communication network including an SNPN. [Figure 1B] 1 illustrates a known system of a wireless communication network including a V-PLMN. [Figure 2] FIG. 1 illustrates a user equipment device. [Figure 3] FIG. 2 illustrates further details of a network node. [Figure 4] FIG. 1 illustrates a method in a network node in a first wireless communications network. [Figure 5] FIG. 1 illustrates a method in a user equipment device. [Figure 6] FIG. 1 illustrates a method in a user equipment device. [Figure 7] FIG. 1 illustrates a method in a network node in a second wireless communications network. [Figure 8] 1 is a message sequence chart illustrating the methods presented herein. DETAILED DESCRIPTION OF THE INVENTION

[0018] As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, the configurations described herein may be implemented entirely in hardware, entirely in software (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects.

[0019] For example, the disclosed methods and apparatus may be implemented as hardware circuitry comprising custom very-large-scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code, which may be organized as, for example, objects, procedures, or functions.

[0020] Furthermore, the methods and apparatus may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmittable. The storage devices may not embody signals. In some configurations, the storage devices employ only signals to access the code.

[0021] Any combination of one or more computer-readable mediums may be utilized. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the above.

[0022] More specific examples (non-exhaustive list) of storage devices would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this specification, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0023] References throughout this specification to a particular example of a method or apparatus, or similar language, mean that a particular feature, structure, or characteristic described with respect to that example is included in at least one implementation of the methods and apparatus described herein. Thus, all references to features of a particular example of a method or apparatus, or similar language, may, but do not necessarily, refer to the same example and may mean "one or more, but not all, examples" unless otherwise specified. The terms "including," "comprising," and "having," and variations thereof, mean "including but not limited to," unless otherwise specified. Enumerated listings of items do not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also refer to "one or more," unless otherwise specified.

[0024] As used herein, a list with the conjunction "and / or" includes any single item in that list or combination of items in that list. For example, a list of A, B, and / or C includes A only, B only, C only, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of" includes any single item in that list or combination of items in that list. For example, one or more of A, B, and C includes A only, B only, C only, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of" includes one and only one of any single item in that list. For example, "one of A, B, and C" includes A only, B only, or C only, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes one and only one of A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C, and combinations thereof" includes A alone, B alone, C alone, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C.

[0025] Furthermore, the described features, structures, or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the present disclosure. However, those skilled in the art will recognize that the disclosed methods and apparatuses can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the present disclosure.

[0026] Aspects of the disclosed methods and apparatus are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, may be implemented by code. This code may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executing via the processor of the computer or other programmable data processing apparatus, create means for performing the functions / acts specified in the schematic flowchart illustrations and / or schematic block diagrams.

[0027] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture that includes instructions that implement the functions / acts specified in the schematic flowchart diagrams and / or schematic block diagrams.

[0028] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to create a computer-implemented process, such that the code running on the computer or other programmable apparatus provides a process for performing the functions / acts specified in the schematic flowchart diagrams and / or schematic block diagrams.

[0029] The schematic flowchart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products. In this regard, each block in the schematic flowchart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of code for implementing the specified logical function(s).

[0030] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially in parallel, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figures.

[0031] The description of an element in each drawing may refer to the element in the preceding drawing, and like numbers refer to like elements in all drawings.

[0032] URSP rules have been specified in Release 15 and later of the 3GPP standards to enable a UE to determine how application traffic should be routed through the mobile communications network, either via untrusted or trusted WLAN access, via 3GPP or non-3GPP access, or non-seamlessly bypassing the mobile communications network via a WLAN connection. The URSP rules and procedures for a UE to apply the URSP rules are described in 3GPP TS 23.502 v17.3.0 and 3GPP TS 23.503 v17.3.0 (URSP rule specifications and procedures are included in versions 15.0.0 and later of 23.502 and 23.503). The URSP rules are an example of route selection policy rules.

[0033] The URSP rule includes a traffic descriptor that enables the UE to determine whether the URSP rule matches the application traffic. The traffic descriptor includes an application descriptor (OSID / OSAppID), an IP flow descriptor (e.g., a target address of the application traffic), a data network name required by the application, or a connection capability required by the application (e.g., an IMS connection).

[0034] Each URSP rule includes a Route Selection Descriptor (RSD) that indicates to the UE how a Packet Data Unit (PDU) session should be routed. The RSD includes one or more of the following: session and service continuity mode selection, network slice selection, data network name selection, PDU session type selection, non-seamless offload indication, and access type preference.

[0035] A UE receiving the URSP rule routes traffic identified by the URSP rule via a PDU session matching the RSD component identified in the URSP rule over 3GPP or non-3GPP access.

[0036] Currently, URSP rules are provided to a UE only from the PCF of the H-PLMN (i.e., the H-PCF). The UE uses the URSP rules provisioned by the H-PLMN among any PLMNs to which the UE may register. When a UE is roaming, the PCF in the V-PLMN (i.e., the V-PCF) cannot create URSP rules for or provision URSP rules to a visiting UE. However, ANDSP (Access Network Discovery and Selection Policy) rules may be created by the V-PCF for or provisioned to a visiting UE by the V-PCF. The PCF provisions URSP and / or ANDSP policies to a UE within UE policy information provided to the UE via NAS signaling. The PCF allocates URSP and ANDSP rules within policy sections within the UE policy information, with each policy section identified by a specific policy section identifier. The PCF stores the policy sections and policy section identifiers in a database, which are used by the PCF to determine whether the UE requires an updated policy. When a UE registers with a PLMN, the UE includes in its registration request to the PLMN a policy section identifier associated with a policy section stored in the UE that allows the PLMN's PCF (in either the home network or the visited network) to identify whether an updated policy is required at the UE.

[0037] Additionally, in some private network deployments, a UE may register with a standalone non-public network (SNPN) using credentials from a different PLMN. In such a scenario, the UE uses the URSP rules from the credential holder, but the PCF in the credential holder PLMN cannot provide the URSP rules to the UE. In such a scenario, there are questions about how the UE applies the URSP rules and whether the SNPN network can provide the URSP rules to the UE.

[0038] 1A shows a known system 100 of a wireless communication network including an SNPN. The system 100 comprises a user equipment (UE) 101, a credential holder 110, and an SNPN 120. The credential holder 110 comprises a unified data management (UDM) 112, a network repository function (NRF) 114, an authentication server function (AUSF) 116, and a security edge protection proxy (SEPP) 118. The SNPN 120 comprises a Radio Access Network (RAN) 130, a User Plane Function (UPF) 132, a data network (DN) 134, an Access and Mobility management Function (AMF) 136, a Session Management Function (SMF) 138, a Network Slice Selection Function (NSSF) 140, a Network Exposure Function (NEF) 142, a Network Repository Function (NRF) 144, a Policy Control Function (PCF) 146, an Application Function (AF) 148, and a Security Edge Protection Proxy (SEPP) 150.

[0039] The functions of the RAN 130 may be performed by some other access network, which may not use radio. The UE 101 communicates with the AMF 136 using the N1 interface. The RAN 130 communicates with the AMF 136 using the N2 interface. The RAN 130 communicates with the UPF 132 using the N3 interface. The N9 interface allows communication between UPFs 132. The DN 134 communicates with the UPF 132 using the N6 interface. The UPF 132 communicates with the SMF 138 using the N4 interface. The SEPP of each network communicates using the N32 interface. Each of the UDM 112, NRF 114, AUSF 116, AMF 136, SMF 138, NSSF 140, NEF 142, NRF 144, PCF 146, and AF 148 communicates with the network using a respective interface.

[0040] 1B shows a known system 105 of a wireless communication network including a V-PLMN. The system includes a user equipment (UE) 101, a V-PLMN 125, and an H-PLMN 160. The H-PLMN 160 includes a unified data manager (UDM) 162, a network repository function (NRF) 164, a network slice-specific authentication and authorization function (NSSAAF) 166, an authentication server function (AUSF) 168, a policy control function (PCF) 170, a network exposure function (NEF) 172, a network slice access control function (NSACF) 174, and a home security edge protection proxy (hSEPP) 180. The V-PLMN 125 comprises a Radio Access Network (RAN) 130, a User Plane Function (UPF) 132, a Data Network (DN) 134, an Access and Mobility Management Function (AMF) 136, a Session Management Function (SMF) 138, a Network Slice Selection Function (NSSF) 140, a Network Exposure Function (NEF) 142, a Network Repository Function (NRF) 144, a Policy Control Function (PCF) 146, an Application Function (AF) 148, and a Visited Security Edge Protection Proxy (SEPP) 150.

[0041] The functions of the RAN 130 may be performed by some other access network, which may not use radio. The UE 101 communicates with the AMF 136 using the N1 interface. The RAN 130 communicates with the AMF 136 using the N2 interface. The RAN 130 communicates with the UPF 132 using the N3 interface. The N9 interface allows communication between UPFs 132. The DN 134 communicates with the UPF 132 using the N6 interface. The UPF 132 communicates with the SMF 138 using the N4 interface. The SEPP of each network communicates using the N32 interface. The UDM 162, NRF 164, NSSAAF 166, AUSF 168, PCF 170, NEF 172, and NSACF 174 each communicate with the network using a respective interface.

[0042] As part of the Release 18 work, there are also scenarios where a VPLMN may require specific route selection policies for roaming UEs.

[0043] This application presents several solutions to this problem. The solutions presented herein help to enable the VPLMN to be aware that URSP rules can be provided to the UE. Furthermore, the solutions presented herein help to enable the HPLMN to control with which PLMNs the UE can use the rules provided by the HPLMN and how the HPLMN indicates to the UE with which PLMNs the UE can use the rules provided by the HPLMN.

[0044] To address the above issue, the HPLMN may indicate to the UE with which PLMNs the UE can use UE policies from the HPLMN. Such an indication may be delivered by providing a list of PLMNs for each provisioned UE policy. When the UE registers with a PLMN that is not in the list of PLMNs, the UE does not use policies provided by the HPLMN, but instead uses only policies provided by the VPLMN.

[0045] 2 shows a user equipment device 200 that can be used to implement the methods described herein. The user equipment device 200 is used to implement one or more of the solutions described above. The user equipment device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0046] The input device(s) 215 and the output device(s) 220 may be combined into a single device, such as a touchscreen. In some implementations, the user equipment device 200 does not include any input device(s) 215 and / or output device(s) 220. The user equipment device 200 may include one or more of the processor 205, the memory 210, and the transceiver 225, and may not include the input device(s) 215 and / or the output device(s) 220.

[0047] As shown, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 may communicate with one or more cells (i.e., wireless coverage areas) supported by one or more base units. The transceiver 225 may be capable of operating on an unlicensed spectrum. Moreover, the transceiver 225 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 225 may support at least one network interface 240 and / or application interface 245. The application interface 245 may support one or more APIs. The network interface 240 may support 3GPP reference points such as Uu, N1, PC5, etc. As will be appreciated by those skilled in the art, other network interfaces 240 may be supported.

[0048] The processor 205 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 205 may be a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), auxiliary processing unit, field programmable gate array (FPGA), or similar programmable controller. The processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225.

[0049] The processor 205 may control the user equipment device 200 to implement the UE behaviors described above. The processor 205 may include an application processor (also known as a “main processor”) that manages application domain and operating system (“OS”) functions, and a baseband processor (also known as a “baseband radio processor”) that manages radio functions.

[0050] Memory 210 may be a computer-readable storage medium. Memory 210 may include volatile computer storage media. For example, memory 210 may include RAM, including dynamic RAM (“dynamic RAM” or “DRAM”), synchronous dynamic RAM (“synchronous dynamic RAM” or “SDRAM”), and / or static RAM (“static RAM” or “SRAM”). Memory 210 may include non-volatile computer storage media. For example, memory 210 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 210 may include both volatile and non-volatile computer storage media.

[0051] Memory 210 may store data related to implementing the traffic category fields as described above. Memory 210 may also store program code and related data, such as operating systems or other controller algorithms running on device 200.

[0052] The input device 215 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. The input device 215 may be integrated with the output device 220, for example, as a touch screen or similar touch-sensitive display. The input device 215 may include a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. The input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0053] Output device 220 may be designed to output visual, audible, and / or tactile signals. Output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 220 may include, without limitation, a liquid crystal display ("LCD"), a light-emitting diode ("LED") display, an organic LED ("OLED") display, a projector, or similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 220 may include a wearable display that is separate from but communicatively coupled to the rest of user equipment device 200, such as a smartwatch, smart glasses, or a head-up display. Furthermore, output device 220 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0054] The output device 220 may include one or more speakers for generating sound. For example, the output device 220 may generate an acoustic alert or notification (e.g., a beep or chime). The output device 220 may include one or more haptic devices for generating vibration, movement, or other haptic feedback. All or part of the output device 220 may be integrated with the input device 215. For example, the input device 215 and the output device 220 may form a touchscreen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0055] The transceiver 225 communicates with one or more network functions of a mobile communications network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals, as well as to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times to send and receive messages.

[0056] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The one or more transmitters 230 may be used to provide UL communication signals to a base unit of a wireless communication network. Similarly, the one or more receivers 235 may be used to receive DL communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are shown, the user equipment device 200 may have any suitable number of transmitters 230 and receivers 235. Furthermore, the transmitters 230 and receivers 235 may be any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair used to communicate with a mobile communication network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over an unlicensed radio spectrum.

[0057] A first transmitter / receiver pair may be used to communicate with a mobile communications network over a licensed radio spectrum, and a second transmitter / receiver pair may be used to communicate with a mobile communications network over an unlicensed radio spectrum, and may be combined into a single transceiver unit, e.g., a single chip that performs functions for use with both licensed and unlicensed radio spectrum. The first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, network interface 240.

[0058] One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated within a single hardware component, such as a multi-transceiver chip, a system-on-chip, an application-specific integrated circuit (ASIC), or other type of hardware component. One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated within a multi-chip module. Other components, such as a network interface 240 or other hardware components / circuits, may be integrated within a single chip with any number of transmitters 230 and / or receivers 235. The transmitters 230 and receivers 235 may be logically configured as a transceiver 225 using another common control signal, or as modular transmitters 230 and receivers 235 implemented within the same hardware chip or multi-chip module.

[0059] 3 shows further details of a network node 300 that may be used to implement the methods described herein. The network node 300 may be one implementation of an entity in a wireless communication network. The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0060] The input device(s) 315 and the output device(s) 320 may be combined into a single device, such as a touchscreen. In some implementations, the network node 300 does not include any input device(s) 315 and / or output device(s) 320. The network node 300 may include one or more of the processor 305, the memory 310, and the transceiver 325, and may not include the input device(s) 315 and / or the output device(s) 320.

[0061] As shown, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 may support at least one network interface 340 and / or application interface 345. The application interface 345 may support one or more APIs. The network interface 340 may support 3GPP reference points, such as Uu, N1, N2, and N3. As will be appreciated by those skilled in the art, other network interfaces 340 may be supported.

[0062] The processor 305 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 305 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0063] Memory 310 may be a computer-readable storage medium. Memory 310 may include volatile computer storage media. For example, memory 310 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). Memory 310 may include non-volatile computer storage media. For example, memory 310 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 310 may include both volatile and non-volatile computer storage media.

[0064] The memory 310 may store data related to establishing multipath unicast links and / or mobile operations. For example, the memory 310 may store parameters, configurations, resource allocations, policies, etc., as described above. The memory 310 may also store program code and related data, such as operating systems or other controller algorithms running on the network node 300.

[0065] The input device 315 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. The input device 315 may be integrated with the output device 320, for example, as a touch screen or similar touch-sensitive display. The input device 315 may include a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. The input device 315 may include two or more different devices, such as a keyboard and a touch panel.

[0066] The output device 320 may be designed to output visual, audible, and / or tactile signals. The output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 320 may include a wearable display that is separate from but communicatively coupled to the rest of the network node 300, such as a smartwatch, smart glasses, a head-up display, etc. Furthermore, the output device 320 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0067] The output device 320 may include one or more speakers for generating sound. For example, the output device 320 may generate an acoustic alert or notification (e.g., a beep or chime). The output device 320 may include one or more haptic devices for generating vibration, movement, or other haptic feedback. All or part of the output device 320 may be integrated with the input device 315. For example, the input device 315 and the output device 320 may form a touchscreen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0068] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The one or more transmitters 330 may be used to communicate with a UE, as described herein. Similarly, the one or more receivers 335 may be used to communicate with network functions in a PLMN and / or RAN, as described herein. Although only one transmitter 330 and one receiver 335 are shown, the network node 300 may have any suitable number of transmitters 330 and receivers 335. Furthermore, the transmitters 330 and receivers 335 may be any suitable types of transmitters and receivers.

[0069] A network node in the first wireless communications network is also provided, the network node comprising a receiver, a processor, and a transmitter. The network node may be the network node 300 comprising the processor 305, the transmitter 330, and the receiver 335. The network node may be a PCF. The network node may be a Home PCF 170, 816. The receiver is configured to receive an indication from the user equipment device that the user equipment device requires a route selection policy rule, the user equipment device being a subscriber to the first wireless communications network. The processor is configured to determine a list of network identities, each network identity identifying a wireless communications network for which the network node is authorized to configure a route selection policy rule that the user equipment device should apply when connected to the wireless communications network. The transmitter is configured to send at least one route selection policy rule together with a policy distribution request to the user equipment device, the policy distribution request including the list of network identities to which the route selection policy rule provisioned from the network node should apply.

[0070] The first wireless communications network is a home network of the user equipment device. The policy delivery request may comprise, for each route selection policy rule sent to the user equipment device, a list of network identification information that identifies in which networks the route selection policy rule should apply.

[0071] The indication that the user equipment device needs route selection policy rules may be a registration request. The registration request may be received from the user equipment device. The indication that the user equipment device needs route selection policy rules may be a route selection policy rule update request. The route selection policy rule update request may be received from the user equipment device. The indication may comprise a list of policy section identifiers. The network node may determine from the received policy section identifiers that the user equipment device needs updated URSP rules.

[0072] The route selection policy rules may be provided using a UE configuration update, and the updated UE configuration may be for transparent policy distribution.

[0073] 4 shows a method 400 in a network node in a first wireless communications network. The network node may be the network node 300. The network node may be a PCF. The network node may be a home PCF 170, 816. The method 400 comprises receiving (410) an indication from a user equipment device that the user equipment device requires a route selection policy rule, the user equipment device being a subscriber to the first wireless communications network. The method further comprises determining (420) a list of network identities, each network identity identifying a wireless communications network for which the network node is authorized to configure route selection policy rules that the user equipment device should apply when connected to the wireless communications network. The method further comprises sending (430) at least one route selection policy rule with a policy distribution request to the user equipment device, the policy distribution request including the list of network identities to which the route selection policy rule provisioned from the network node should apply.

[0074] The first wireless communications network is a home network of the user equipment device. The policy delivery request may comprise, for each route selection policy rule sent to the user equipment device, a list of network identification information that identifies in which networks the route selection policy rule should apply.

[0075] The indication that the user equipment device needs route selection policy rules may be a registration request. The registration request may be received from the user equipment device. The indication that the user equipment device needs route selection policy rules may be a route selection policy rule update request. The route selection policy rule update request may be received from the user equipment device. The indication may comprise a list of policy section identifiers. The network node may determine from the received policy section identifiers that the user equipment device needs updated URSP rules.

[0076] The network node may be a Policy Control Function (PCF). The PCF may be a home PCF. The route selection policy rules may be provided using a UE configuration update. The updated UE configuration may be for transparent policy distribution.

[0077] Further provided is a user equipment device comprising a transmitter and a receiver. The user equipment device may be a UE 101, 200, and / or 812 as described herein. The user equipment device may comprise a processor 205, a transmitter 230, and a receiver 235. The transmitter is configured to send an indication to a first wireless communications network that the user equipment device requires a route selection policy rule, the user equipment device being a subscriber to the first wireless communications network. The receiver is configured to receive at least one route selection policy rule together with a policy delivery request from the first wireless communications network, the policy delivery request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network should apply.

[0078] The indication that the user equipment device needs route selection policy rules may be a registration request. The registration request may be received from the user equipment device. The indication that the user equipment device needs route selection policy rules may be a route selection policy rule update request. The route selection policy rule update request may be received from the user equipment device.

[0079] The network node may be a Policy Control Function (PCF). The PCF may be a home PCF. The route selection policy rules and the list of network identities may be provided using a UE configuration update. The updated UE configuration may be for transparent policy distribution.

[0080] The transmitter may be further configured to transmit a subsequent registration to a second wireless communications network, the second wireless communications network having a network identity that is not listed in a list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply. The user equipment device may further comprise a processor configured to not apply the route selection policy rules provisioned from the first wireless communications network when the user equipment device registers with the second wireless communications network.

[0081] The processor may be configured to determine that the second wireless communications network is not identified in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply.

[0082] The transmitter may be further configured to request route selection policy rules from the second wireless communications network, and the processor may be further configured to apply any route selection policy rules received from the second wireless communications network when the user equipment device is registered with the second wireless communications network.

[0083] The processor may be further configured to apply any rules received from an access network discovery and selection function (ANDSF) of the second wireless communications network, where the rules from the ANDSF are not route selection policy rules as described herein.

[0084] The transmitter may be further configured to transmit a subsequent registration to a third wireless communications network, the third wireless communications network having a network identity listed in the list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply. The user equipment device may further comprise a processor configured to apply the route selection policy rules provisioned from the first wireless communications network when the user equipment device registers with the third wireless communications network.

[0085] The processor may be configured to determine that the third wireless communications network is identified in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply.

[0086] The processor may be further configured to ignore any route selection policy rules received from the third wireless communications network when the user equipment device is registered with the third wireless communications network. The processor may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the third wireless communications network.

[0087] 5 illustrates a method 500 in a user equipment device. The user equipment device may be a UE 101, 200, and / or 812, as described herein. The method 500 comprises sending (510) an indication to a first wireless communications network that the user equipment device requires a route selection policy rule, the user equipment device being a subscriber to the first wireless communications network. The method further comprises receiving (520) at least one route selection policy rule with a policy delivery request from the first wireless communications network, the policy delivery request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network should apply.

[0088] The indication that the user equipment device needs route selection policy rules may be a registration request. The registration request may be received from the user equipment device. The indication that the user equipment device needs route selection policy rules may be a route selection policy rule update request. The route selection policy rule update request may be received from the user equipment device.

[0089] The network node may be a Policy Control Function (PCF). The PCF may be a home PCF. The route selection policy rules and the list of network identities may be provided using a UE configuration update. The updated UE configuration may be for transparent policy distribution.

[0090] The method may further include transmitting a subsequent registration to a second wireless communications network, the second wireless communications network having a network identity that is not listed in a list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply. The method may further include not applying the route selection policy rules provisioned from the first wireless communications network when the user equipment device registers with the second wireless communications network.

[0091] The method may further include determining that the second wireless communications network is not identified in a list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply.

[0092] The method may further include requesting route selection policy rules from the second wireless communications network.

[0093] The method may further include applying any route selection policy rules received from the second wireless communications network when the user equipment device is registered with the second wireless communications network. The method may further include applying any rules received from an Access Network Discovery and Selection Function (ANDSF) of the second wireless communications network.

[0094] The method may further include transmitting a subsequent registration to a third wireless communications network, the third wireless communications network having a network identity listed in a list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply. The method may further include applying the route selection policy rules provisioned from the first wireless communications network when the user equipment device registers with the third wireless communications network. The method may further include determining that the third wireless communications network is identified in the list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply.

[0095] The method may further include, when the user equipment device is registered with the third wireless communications network, ignoring any route selection policy rules received from the third wireless communications network. The method may further include applying any rules received from an Access Network Discovery and Selection Function (ANDSF) of the third wireless communications network.

[0096] Further provided is a user equipment device comprising a receiver, a transmitter, and a processor. The user equipment device may be a UE 101, 200, and / or 812 as described herein. The user equipment device may comprise a processor 205, a transmitter 230, and a receiver 235. The receiver is configured to receive at least one route selection policy rule together with a policy distribution request from a first wireless communications network, the policy distribution request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The transmitter is configured to send a registration request to a second wireless communications network, the network identities of the second wireless communications network not listed in the list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The processor is configured to not apply the route selection policy rule provisioned from the first wireless communications network.

[0097] The first wireless communications network is a home network of the user equipment device.

[0098] The policy delivery request may comprise, for each route selection policy rule sent to the user equipment device, a list of network identification information that identifies in which networks the route selection policy rule should apply. The second wireless communications network is a visited wireless communications network.

[0099] Configuring the processor to not apply the route selection policy rule provisioned from the first wireless communications network may include configuring the processor to deactivate the route selection policy rule provisioned from the first wireless communications network. If the user equipment device later registers with the first wireless communications network, the deactivated rule may be reactivated.

[0100] Not applying the route selection policy rule provisioned from the first wireless communications network may include disabling the route selection policy rule provisioned from the first wireless communications network. When the user equipment device later re-registers with the first wireless communications network, the disabled rule may be enabled.

[0101] Not applying the route selection policy rule provisioned from the first wireless communications network may include discarding the route selection policy rule provisioned from the first wireless communications network. Upon re-registering with the first wireless communications network, the user equipment device may request an alternative rule from the first wireless communications network.

[0102] The transmitter may be further configured to request the local route selection policy rule from the second wireless communications network. Following the transmitter sending the request for the local route selection policy rule, the receiver of the user equipment device may be configured to receive the local route selection policy rule received from the second wireless communications network.

[0103] The processor may be further configured to apply any local route selection policy rules received from the second wireless communications network. The processor may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the second wireless communications network. When the user equipment device deregisters from the second wireless communications network, any rules received from the second wireless communications network may be deleted.

[0104] The transmitter may be further configured to transmit a subsequent registration to a third wireless communications network, the third wireless communications network having a network identity listed in the list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply. The user equipment device may further comprise a processor configured to apply the route selection policy rules provisioned from the first wireless communications network when the user equipment device registers with the third wireless communications network.

[0105] The processor may be further configured to ignore any route selection policy rules received from the third wireless communications network. The processor may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the third wireless communications network.

[0106] Alternatively, when sending a subsequent registration to the third wireless communications network, the transmitter may indicate that local route selection policy rules are required. The processor may be further configured to give priority to any local route selection policy received from the third wireless communications network, but to also apply route selection policy rules provisioned from the first wireless communications network.

[0107] The transmitter may be further configured to send an indication that the user equipment device requires the route selection policy rule to the first wireless communications network. In response to the indication that the user equipment device requires the route selection policy rule being a registration request, the at least one route selection policy rule may be received along with a policy delivery request. The indication may comprise a registration request. The indication may be a route selection policy rule update request.

[0108] The route selection policy rules may be received using a UE configuration update, and the updated UE configuration may be for transparent policy distribution.

[0109] 6 shows a method 600 in a user equipment device. The user equipment device may be a UE 101, 200, and / or 812 as described herein. The user equipment device may include a processor 205, a transmitter 230, and a receiver 235. The method 600 comprises receiving (610) at least one route selection policy rule along with a policy distribution request from a first wireless communications network, the policy distribution request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The method 600 further comprises sending (620) a registration request to a second wireless communications network, the network identities of the second wireless communications network not listed in the list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The method 600 further comprises not applying (630) the route selection policy rule provisioned from the first wireless communications network.

[0110] The first wireless communications network is a home network of the user equipment device. The policy delivery request may comprise, for each route selection policy rule sent to the user equipment device, a list of network identification information that identifies within which networks the route selection policy rule should apply. The second wireless communications network is a visited wireless communications network.

[0111] Not applying the route selection policy rule provisioned from the first wireless communications network includes deactivating the route selection policy rule provisioned from the first wireless communications network. If the user equipment device later registers with the first wireless communications network, the deactivated rule may be reactivated.

[0112] Not applying the route selection policy rule provisioned from the first wireless communications network may include disabling the route selection policy rule provisioned from the first wireless communications network. When the user equipment device later re-registers with the first wireless communications network, the disabled rule may be enabled.

[0113] Not applying the route selection policy rule provisioned from the first wireless communications network may include discarding the route selection policy rule provisioned from the first wireless communications network. Upon re-registering with the first wireless communications network, the user equipment device may request an alternative rule from the first wireless communications network.

[0114] The method may further include requesting the local route selection policy rules from the second wireless communications network. Following the transmitter sending the request for the local route selection policy rules, the receiver of the user equipment device may be configured to receive the local route selection policy rules received from the second wireless communications network.

[0115] The method may further include applying any local route selection policy rules received from the second wireless communications network. The processor may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the second wireless communications network. When the user equipment device deregisters from the second wireless communications network, any rules received from the second wireless communications network may be deleted.

[0116] The method may further include transmitting a subsequent registration to a third wireless communications network, the third wireless communications network having a network identity listed in the list of network identities to which the route selection policy rules provisioned from the first wireless communications network must apply. The method may further include applying the route selection policy rules provisioned from the first wireless communications network when the user equipment device registers with the third wireless communications network.

[0117] The method may further include ignoring any route selection policy rules received from the third wireless communications network. The method may further include applying any rules received from an Access Network Discovery and Selection Function (ANDSF) of the third wireless communications network.

[0118] Alternatively, when a subsequent registration is sent to the third wireless communications network, the transmission may indicate that local route selection policy rules are required, and the route selection policy rules provisioned from the first wireless communications network may be given priority and applied over any local route selection policy received from the third wireless communications network.

[0119] The method may further include sending an indication to the first wireless communications network that the user equipment device requires the route selection policy rule.

[0120] At least one route selection policy rule may be received with a policy delivery request in response to the indication that the user equipment device requires a route selection policy rule being a registration request. The indication may comprise a registration request. The indication may be a route selection policy rule update request.

[0121] The route selection policy rules may be received using a UE configuration update, and the updated UE configuration may be for transparent policy distribution.

[0122] A network node in a second wireless communications network is also provided. The network node may be the network node 300 comprising a processor 305, a transmitter 330, and a receiver 335. The network node may be a visited PCF 146, 826. The network node comprises a receiver and a processor. The receiver is configured to receive a registration request from a user equipment device, wherein a network identity of the second wireless communications network is not listed in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply. The processor is configured to register the user equipment device with the second wireless communications network.

[0123] The user equipment device is configured to receive at least one route selection policy rule from a first wireless communications network along with a policy delivery request, the policy delivery request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The first wireless communications network is a home network of the user equipment device. The policy delivery request may comprise, for each route selection policy rule sent to the user equipment device, a list of network identities identifying in which networks the route selection policy rule must apply. The second wireless communications network is a visited wireless communications network.

[0124] The receiver may be further configured to receive a request for the local route selection policy rule from the user equipment device, whereupon the transmitter of the network node is configured to send the local route selection policy rule to the user equipment device.

[0125] The local route selection policy rules may be pre-configured at the network node, the user equipment device may be an inward roaming device, and the local route selection policy rules may be configured per network, for example, based on a service level agreement.

[0126] The user equipment device may be configured to apply any local route selection policy rules received from the second wireless communications network. The user equipment device may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the second wireless communications network. When the user equipment device deregisters from the second wireless communications network, any rules received from the second wireless communications network may be deleted.

[0127] The network node may send a request to the first wireless communications network for authorization to provide the local route selection policy rule to the user equipment device. The network node may be configured to send the local route selection policy rule to the user equipment device in response to receiving authorization from the first wireless communications network.

[0128] The user equipment device may be configured to apply route selection policy rules received from the network node that have a higher priority than route selection policy rules provisioned from the first wireless communications network.

[0129] The local route selection policy rules are sent using UE configuration updates. The updated UE configuration may be for transparent policy distribution.

[0130] 7 shows a method 700 in a network node in a second wireless communications network. The network node may be network node 300. The network node may be a visited PCF 146, 826. The method 700 comprises receiving (710) a registration request from a user equipment device, wherein a network identity of the second wireless communications network is not listed in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply. The method 700 further comprises registering (720) the user equipment device with the second wireless communications network.

[0131] The method may further include receiving a request for a local route selection policy rule from the user equipment device, and in response, sending the local route selection policy rule to the user equipment device.

[0132] The user equipment device may be configured to receive at least one route selection policy rule from a first wireless communications network along with a policy delivery request, the policy delivery request including a list of network identities to which the route selection policy rule provisioned from the first wireless communications network must apply. The first wireless communications network is a home network of the user equipment device. The policy delivery request may comprise, for each route selection policy rule sent to the user equipment device, a list of network identities identifying in which networks the route selection policy rule must apply. The second wireless communications network is a visited wireless communications network.

[0133] The method may further include receiving a request for local route selection policy rules from a user equipment device and, in response, sending the local route selection policy rules to the user equipment device. The local route selection policy rules may be pre-configured at a network node. The user equipment device may be an inward roaming device. The local route selection policy rules may be configured per network, for example, based on a service level agreement.

[0134] The user equipment device may be configured to apply any local route selection policy rules received from the second wireless communications network. The user equipment device may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the second wireless communications network. When the user equipment device deregisters from the second wireless communications network, any rules received from the second wireless communications network may be deleted.

[0135] The method may further include sending a request to the first wireless communications network for authorization to provide the local route selection policy rule to the user equipment device. The method may further include sending the local route selection policy rule to the user equipment device in response to receiving authorization from the first wireless communications network.

[0136] The user equipment device may be configured to apply route selection policy rules received from the network node that have a higher priority than route selection policy rules provisioned from the first wireless communications network.

[0137] The local route selection policy rules may be sent using a UE configuration update. The updated UE configuration may be for transparent policy distribution.

[0138] Provisions for V-PCF in third wireless communications networks A network node in a third wireless communications network is further provided, the network node comprising: a receiver configured to receive a registration request from a user equipment device, wherein a network identification of the third wireless communications network is listed in a list of network identities to which route selection policy rules provisioned from the first wireless communications network must apply; and a processor configured to register the user equipment device with the third wireless communications network.

[0139] The user equipment device may be configured to ignore any route selection policy rules received from the third wireless communications network. The processor may be further configured to apply any rules received from an Access Network Discovery and Selection Function (ANDSF) of the third wireless communications network.

[0140] Alternatively, when sending a subsequent registration to the third wireless communications network, the transmitter may indicate that local route selection policy rules are required. The processor may be further configured to give priority to any local route selection policy received from the third wireless communications network, but to also apply route selection policy rules provisioned from the first wireless communications network.

[0141] A network node in the third wireless communications network may send service-specific information to the first wireless communications network, where the service-specific information may enable the first wireless communications network to generate route selection policy rules appropriate for the third wireless communications network.

[0142] The network node may be configured to receive an indication from the user equipment device that the user equipment device requires a route selection policy rule.

[0143] At least one route selection policy rule may be received with a policy delivery request in response to the indication that the user equipment device requires a route selection policy rule being a registration request. The indication may comprise a registration request. The indication may be a route selection policy rule update request.

[0144] According to some configurations presented herein, the H-PLMN may provide configuration information specifying PLMNs from which the UE can request URSP rules. For example, when a PCF (H-PCF) in the H-PLMN provides a UE with a UE policy including URSP rules, the H-PCF includes information about which PLMNs the UE should apply the URSP rules received from the H-PCF. This supports filtering by URSP rule and / or indicating a list of PLMNs for which the URSP rules provisioned by the H-PLMN can be used. Additionally or alternatively, this supports filtering by policy section identifier and / or UE policy, where a list of PLMNs associated with each policy section identifier of the UE policy is included in the UE policy provisioned to the UE. The list of PLMNs may include PLMN and / or SNPN identification information.

[0145] The UE may store a UE policy that includes multiple policy sections, each identified by a policy section identifier, and each policy section identifier includes a PLMN identifier that indicates the PLMN that provisioned the UE with the UE policy.

[0146] When per URSP rule filtering is performed, indicating the list of PLMNs for which the URSP rule provisioned by the H-PLMN may be used, the following may apply:

[0147] When the UE is registered / is in the process of registering with a PLMN that is in the list of PLMNs for which the URSP rules provisioned by the H-PLMN may be used, the UE applies the URSP rules provided by the H-PLMN.

[0148] If the UE is registered with a V-PLMN / SNPN and receives a UE policy that includes URSP rules from a listed V-PLMN / SNPN in the "List of PLMNs for which URSP rules provisioned by the HPLMN may be used", the UE ignores the URSP rules from the listed V-PLMN / SNPN. The UE may include an indication in the response as to why the rules should be ignored. If the UE receives a UE policy that includes ANDSP rules from a listed V-PLMN / SNPN, the UE applies the ANDSP rules as usual.

[0149] When the UE is registering with a non-listed V-PLMN / SNPN that is not in the "PLMN list for which URSP rules provisioned by the H-PLMN may be used," the UE determines that the UE must use the URSP policy from this non-listed PLMN and must not use the URSP policy provided by the home PLMN. In such a scenario, the UE may include an indication / request for URSP rules from the non-listed PLMN / SNPN on which the UE is registering. This may be supported by: Including an indication in the UE policy container in the registration request that the UE requests new URSP rules / temporary URSP rules; and / or · Include an indication and generic NAS message requesting new / temporary URSP rules (include UE policy container).

[0150] When a PCF in an unenumerated V-PLMN or SNPN receives an indication / request from the UE, it provides the local URSP rules to the UE. It assigns a policy section identifier that includes the SNPN or PLMN identifier and provides the policy to the UE using the UE configuration update procedure for transparent policy delivery.

[0151] When a UE is registered with a V-PLMN / SNPN and receives local URSP rules from an unlisted V-PLMN / SNPN that is not in the list of PLMNs, the UE applies only the V-PLMN / SNPN URSP rules and does not apply any URSP rules or policies provided by the H-PLMN. When the UE deregisters from the V-PLMN / SNPN, the UE does not need to store the local URSP rules.

[0152] If filtering is performed by policy section identifier and / or UE policy, the UE policy provisioned to the UE includes a list of PLMNs associated with each policy section identifier of the UE policy. In this situation, the following may apply:

[0153] When the UE is registered or is in the process of registering with a PLMN that is in the list of PLMNs associated with a PSI identifier, the UE applies the UE policies provided by the H-PLMN. The PSI identifier is a Public Service Identity (PSI) used to identify services hosted by an AS (Application Server).

[0154] If the UE is registered with a V-PLMN / SNPN and receives a UE policy from the V-PLMN / SNPN in its list of PLMNs, the UE will give priority to the V-PLMN / SNPN policy but will also apply the UE policy of the home PLMN. Note that in such a scenario, the V-PLMN / SNPN may not provide any local URSP rules.

[0155] When the UE is registering with a PLMN that is not in the PLMN list (i.e., a V-PLMN or an SNPN), the UE determines that it must use the UE policy from this PLMN and must not use the UE policy provided by the home PLMN. In such a scenario, the UE may include an indication / request for the UE policy from the PLMN / SNPN to which the UE is registering. This may be supported by including an indication in the UE policy container in the registration request that the UE requests a new policy / temporary policy.

[0156] When a PCF in a V-PLMN or SNPN receives an indication / request from a UE, the PCF provides local UE policies, including URSP rules, to the UE. These local UE policies may be pre-configured in the PCF of the inbound roamer. The PCF assigns a policy section identifier, including the SNPN or PLMN identifier, and provides the policy to the UE using the UE configuration update procedure for transparent policy delivery.

[0157] When a UE is registered with a V-PLMN / SNPN and receives a UE policy from a V-PLMN / SNPN that is not in the list of PLMNs, the UE applies only the V-PLMN / SNPN policy and does not apply any policy provided by the H-PLMN. When the UE deregisters from the V-PLMN / SNPN, the UE does not need to store the policy.

[0158] Figure 8 is a message sequence chart 800 illustrating the method presented herein. Figure 8 shows a UE 812, an H-PLMN 810, and a V-PLMN 820. The V-PLMN 820 may be an SNPN. The H-PLMN 810 comprises a Radio Access Network (RAN) 814, an Access and Mobility Management Function (AMF) 815, a Home Policy Control Function (H-PCF) 816, and a Unified Data Manager / Unified Data Repository (UDM / UDR) 817. The Visited PLMN (V-PLMN) 820 comprises a Radio Access Network (RAN) 822, an Access and Mobility Management Function (AMF) 824, and a Visited Policy Control Function (V-PCF) 826.

[0159] At 870, the UE 812 registers in the Home PLMN 810 per section 4.2.2.2 of 3GPP TS23.502 v17.3.0. The UE 812 includes a list of PSI identifiers associated with the Home PLMN 810.

[0160] At 871, the H-PCF 816 determines whether new or updated URSP rules are needed. The H-PCF 816 determines, based on operator policy, to include information about which PLMNs the UE policy provisioned by the H-PCF 816 may apply to.

[0161] At 872, the H-PCF 816 provides the URSP rules using a UE configuration update for transparent policy delivery. The H-PCF 816 includes information to assist the UE 812 in determining in which PLMN or SNPN the URSP rules provided by the home PLMN 810 should apply.

[0162] At 873, the UE 812 may be roaming or may determine that a V-PLMN 820, which may be an SNPN, is nearby. The UE 812 selects a V-PLMN 820 to register with.

[0163] At 874, the UE 812 checks whether the selected V-PLMN 820 is included in the list of PLMNs provided by the H-PCF 816.

[0164] At 875, if the selected V-PLMN 820 is not in the list of PLMNs, the UE 812 determines that the URSP rules provided by the H-PLMN 810 are not applicable to this PLMN.

[0165] At 876, the UE 812 registers with this V-PLMN 820 without including the policy section identifier associated with the home PLMN 810. The UE 812 may also include an indication or request to include new / temporary URSP rules.

[0166] At 877, based on the lack of PSI received at the V-PCF 826 and / or based on an indication / request provided by the UE 812, the V-PCF 826 determines to provide local / temporary URSP rules to the UE 812 even if the UE 812 is from a different PLMN. These local / temporary URSP rules may be pre-configured in the V-PCF 826 and may be configured for each H-PLMN of the visiting UE. The local / temporary URSP rules may be based on a service level agreement.

[0167] At 878, the V-PCF 826 provides temporary URSP rules using UE configuration updates for transparent policy delivery.

[0168] At 879, the UE 812 applies the URSP rules only within the selected PLMN, i.e., V-PLMN 820. When the UE 812 deregisters from the selected PLMN, the UE 812 does not need to store the local / temporary URSP rules.

[0169] After step 879, if the UE 812 registers with a different PLMN that is part of the list of PLMNs provided by the H-PCF 816, the UE registers with the new PLMN using the PSI associated with the home PLMN 810 and visited PLMN 820 (if available) as per the procedures in 23.502 v17.3.0.

[0170] In step 875 of FIG. 8, if the selected PLMN 820 is in the list of PLMNs, the UE 812 may determine that the URSP rules provided by the H-PLMN 810 may be used, providing a list of PSIs associated with the home PLMN 810.

[0171] In an alternative embodiment when the UE 812 registers with the V-PLMN 820, when the V-PCF 826 receives a UE policy association request from the AMF 824 in the V-PLMN 820 and the V-PCF 826 can communicate with a PCF in the H-PLMN 810 over the roaming interface, the V-PCF 826 may request from the H-PCF 816 whether the H-PCF 816 can provide temporary URSP rules to the UE 812. If the H-PCF 816 approves the request, the H-PCF 816 may not include the UE policy to the UE 812 or may provide an indication to the UE 812 that the URSP rules received from the V-PCF 826 can be accepted. If the V-PCF 826 receives an acknowledgement response to the H-PCF 816, the V-PCF 826 provides the URSP rules to the UE 812. The UE 812 first prioritizes the URSP rules received from the V-PCF 826, and then applies the URSP rules from the H-PLMN 810, if they are available. USRP rules are an example of route selection policy rules.

[0172] In the alternative, the V-PCF 826 may include the service-specific information to the H-PCF 816 to build the URSP rules. The H-PCF 816 updates the URSP rules and provisions the updated rules to the UE 812 using the UE configuration update for transparent UE policy delivery procedure.

[0173] According to known solutions, URSP rules are provided only by the H-PLMN, and the UE applies the same URSP rules in any PLMN where the UE registers. This can cause problems when the UE is roaming, when the V-PLMN operator may require specific traffic routing treatment for specific applications. In addition, there are scenarios where the V-PLMN operator cannot interface with the H-PLMN (e.g., when the UE registers in an SNPN using credentials from the H-PLMN).

[0174] The solution presented herein helps to enable the V-PLMN to be aware that URSP rules can be provided to the UE.

[0175] The solution presented herein helps enable an H-PLMN to control with which PLMNs the UE can use the rules provided by the H-PLMN and how the H-PLMN indicates to the UE with which PLMNs the UE can use the rules provided by the H-PLMN.

[0176] To address the above issue, the H-PLMN may indicate to the UE with which PLMNs the UE can use UE policies from the H-PLMN. Such an indication may be delivered by providing a list of PLMNs for each provisioned UE policy. When the UE registers with a PLMN that is not in the list of PLMNs, the UE does not use policies provided by the H-PLMN and instead uses only policies provided by the V-PLMN.

[0177] According to one configuration described herein, the H-PLMN provides configuration information about PLMNs that allows the UE to request URSP rules from different PLMNs.

[0178] According to one configuration described herein, the H-PLMN provides configuration information about PLMNs to which the UE can apply policy sections from the home PLMN.

[0179] Accordingly, there is provided a policy control function in the first mobile communications network configured to determine PLMNs for which the UE is allowed to use URSP rules provisioned from the first mobile communications network and to send a first policy distribution request, the request including a list of PLMN identities for which the URSP rules provisioned from the first mobile communications network may be used.

[0180] There is further provided a UE configured to register in a first mobile communications network associated with a first PLMN identity, and further configured to determine whether the first PLMN identity is in a list of PLMN identities provisioned from a second PLMN, and to apply URSP rules provisioned from the second PLMN in response to a determination that the first PLMN identity is in the list of PLMNs provisioned from the second PLMN.

[0181] It should be noted that the above-described methods and apparatus illustrate rather than limit the present invention, and that those skilled in the art can design many alternative configurations without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps other than those listed in a claim, and "a" or "an" does not exclude a plurality; a single processor or other unit may fulfill the functions of several units recited in a claim. Any reference signs in the claims shall not be construed as limiting their scope.

[0182] Furthermore, while examples are given in the context of particular communication standards, these examples are not intended to be a limitation on the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples are given in the context of 3GPP, the principles disclosed herein may also be applied to other wireless communication systems, and indeed to any communication system that uses routing rules.

[0183] The methods may also be embodied in a set of instructions stored on a computer-readable medium that, when loaded into a computer processor, a digital signal processor (DSP), or the like, causes the processor to perform the methods described above.

[0184] The described method and apparatus may be embodied in other specific forms. The described method and apparatus are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0185] 100 systems 101 User Equipment (UE) 105 System 110 Credential Holders 112 Unified Data Manager (UDM) 114 Network Repository Facility (NRF) 116 Authentication Server Function (AUSF) 118 Security Edge Protection Proxy (SEPP) 120 Standalone Non-Public Network (SNPN) 125 V-PLMN 130 Radio Access Network (RAN) 132 User Plane Function (UPF) 134 Data Network (DN) 136 Access and Mobility Management Function (AMF) 138 Session Management Facility (SMF) 140 Network Slice Selection Function (NSSF) 142 Network Exposure Function (NEF) 144 Network Repository Facility (NRF) 146 Policy Control Function (PCF) 148 Application Functions (AF) 150 Security Edge Protection Proxy (SEPP) 160 H-PLMN 162 Unified Data Manager (UDM) 164 Network Repository Facility (NRF) 166 Network Slice Specific Authentication and Authorization Function (NSSAAF) 168 Authentication Server Function (AUSF) 170 Policy Control Function (PCF) 172 Network Exposure Function (NEF) 174 Network Slice Access Control Function (NSACF) 180 Home Security Edge Protection Proxy (hSEPP) 200 User Equipment Device 205 processors 210 memory 215 Input Devices 220 output devices 225 Transceiver 230 Transmitter 235 receiver 240 network interfaces 245 Application Interface 300 network nodes 305 processor 310 memory 315 Input Devices 320 output device 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interface 345 Application Interface 810 H-PLMN 812 User Equipment (UE) 814 Radio Access Network (RAN) 815 Access and Mobility Management Function (AMF) 816 Home Policy Control Function (H-PCF) 817 Unified Data Manager / Unified Data Repository (UDM / UDR) 820 V-PLMN 822 Radio Access Network (RAN) 824 Access and Mobility Management Function (AMF) 826 Visited Policy Control Function (V-PCF)

Claims

1. A user equipment (UE) for wireless communications, comprising: At least one memory; and at least one processor coupled to the at least one memory, the at least one processor configured to: receiving at least one route selection policy rule together with a policy delivery request from a first wireless communications network, the policy delivery request including a list of network identities to which a route selection policy rule provisioned from the first wireless communications network should be applied; sending a registration request to a second wireless communications network, wherein a network identity of the second wireless communications network is not listed in the list of network identities to which route selection policy rules provisioned from the first wireless communications network should apply; not applying route selection policy rules provisioned from the first wireless communications network; configured to cause U.E. To not apply a route selection policy rule provisioned from the first wireless communications network, the at least one processor is configured to cause the UE to deactivate the route selection policy rule provisioned from the first wireless communications network. The UE of claim 1.

3. The at least one processor is configured to cause the UE to request local route selection policy rules from the second wireless communications network. The UE of claim 1.

4. The at least one processor is configured to cause the UE to apply any local route selection policy rules received from the second wireless communications network. The UE of claim 3.

5. The at least one processor may further include a processor for transmitting a plurality of packets to the UE. sending a subsequent registration to a third wireless communications network, the third wireless communications network having a network identification listed in the list of network identifications to which route selection policy rules provisioned from the first wireless communications network should apply; applying route selection policy rules provisioned from the first wireless communications network when the UE is registered in the third wireless communications network; configured to cause The UE of claim 1.

6. The at least one processor is configured to cause the UE to ignore route selection policy rules received from the third wireless communications network. The UE of claim 5.

7. The at least one processor is configured to cause the UE to send an indication that the UE requires a route selection policy rule to the first wireless communications network. The UE of claim 1.

8. The at least one processor is configured to cause the UE to receive the route selection policy rules using a UE configuration update. The UE of claim 1.

9. 1. A method performed by a user equipment (UE), comprising: receiving at least one route selection policy rule together with a policy delivery request from a first wireless communications network, the policy delivery request including a list of network identities to which a route selection policy rule provisioned from the first wireless communications network should be applied; sending a registration request to a second wireless communications network, a network identity of the second wireless communications network being not listed in the list of network identities to which route selection policy rules provisioned from the first wireless communications network should apply; not applying route selection policy rules provisioned from the first wireless communications network; A method comprising:

10. A network node in a second wireless communications network, At least one memory; and at least one processor coupled to the at least one memory, the at least one processor configuring the network node to: receiving a registration request from a user equipment (UE), wherein a network identity of the second wireless communications network is not listed in a list of network identities to which route selection policy rules provisioned from a first wireless communications network should apply; and registering the UE with the second wireless communications network. Network node.

11. The at least one processor may include a processor for controlling the network node. receiving, from the UE, a request for local route selection policy rules; and in response thereto, sending local route selection policy rules to the UE; 11. The network node of claim 10, configured to:

12. The at least one processor is configured to cause the network node to send a request to the first wireless communications network for authorization to provide local route selection policy rules to the UE. A network node according to claim 10.

13. The at least one processor is configured to cause the network node to send the local route selection policy rule with a UE configuration update. A network node as claimed in claim 12.

14. A processor for wireless communications, comprising: at least one controller coupled to at least one memory, the at least one controller configured to cause the processor to: receiving at least one route selection policy rule together with a policy delivery request from a first wireless communications network, the policy delivery request including a list of network identities to which a route selection policy rule provisioned from the first wireless communications network should be applied; sending a registration request to a second wireless communications network, wherein a network identity of the second wireless communications network is not listed in the list of network identities to which route selection policy rules provisioned from the first wireless communications network should apply; not applying route selection policy rules provisioned from the first wireless communications network; configured to cause Processor.

15. The method of claim 14, wherein the at least one controller is configured to cause the processor to deactivate the route selection policy rule provisioned from the first wireless communications network, so as to not apply the route selection policy rule provisioned from the first wireless communications network.

15. The processor of claim 14.

16. The at least one controller is configured to cause the processor to request local route selection policy rules from the second wireless communications network.

15. The processor of claim 14.

17. The at least one controller configured to cause the processor to apply any local route selection policy rules received from the second wireless communications network.

17. The processor of claim 16.

18. The at least one controller, in turn, instructing the processor to: sending a subsequent registration to a third wireless communications network, the third wireless communications network having a network identification listed in the list of network identifications to which route selection policy rules provisioned from the first wireless communications network should apply; applying a route selection policy rule provisioned from the first wireless communication network when a first user equipment (UE) is registered in the third wireless communication network; configured to cause 20. The processor of claim 17.

19. The at least one controller is configured to cause the processor to ignore route selection policy rules received from the third wireless communications network.

20. The processor of claim 18.

20. The at least one controller is configured to cause the processor to send an indication that a user equipment (UE) requires a route selection policy rule to the first wireless communications network.

15. The processor of claim 14.

Images