Visited network guidance for route selection policy rules

Abstract

A network node in a first wireless communications network is provided. The network node comprises a receiver, a processor, and a transmitter. The receiver is configured to receive application guidance in a route selection policy rule determination from an application function in a second wireless communications network. The processor is configured to construct a route selection policy rule using the application guidance, the route selection policy rule including an application descriptor and a route selection descriptor comprising network identification information, the network identification information identifying the second wireless communications network, and the route selection policy rule defining a route for application traffic when the user equipment device is registered in the second wireless communications network. The transmitter is configured to transmit the route selection policy rule to the user equipment device.

Description

[Technical field]

[0001] The subject matter disclosed herein generally relates to the field of implementing route selection policy rules and visited network identity information. This specification provides a network node in a first wireless communication network, a method of the network node in the first wireless communication network, a network node in a second wireless communication network, and a method of the network node in the second wireless communication network. [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. The URSP rules include traffic descriptors that allow 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 data network name 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 (PLMN) and access services in the roamed area by using a visited PLMN. If communication is established, the UE is in principle unhindered in that PLMN area. Summary of the Invention [Problem to be solved by the invention]

[0004] A problem with existing UE route selection policy rules is that they can only be configured by the home PLMN, and such rules are applied universally by the UE without regard to which PLMN the UE is registered in.

[0005] Disclosed herein are procedures for implementing visited network guidance for route selection policy rules, the procedures may be implemented by user equipment and at least one node of at least one wireless communication network. [Means for solving the problem]

[0006] A network node in a first wireless communications network is provided. The network node comprises a receiver, a processor, and a transmitter. The receiver is configured to receive application guidance in a route selection policy rule determination from an application function in a second wireless communications network. The processor is configured to construct a route selection policy rule using the application guidance, the route selection policy rule including an application descriptor and a route selection descriptor comprising network identification information, the network identification information identifying the second wireless communications network, and the route selection policy rule defining a route for application traffic when the user equipment device is registered in the second wireless communications network. The transmitter is configured to transmit the route selection policy rule to the user equipment device.

[0007] A method of a network node in a first wireless communications network is further provided. The method comprises receiving application guidance in a route selection policy rule decision from an application function in a second wireless communications network. The method further comprises constructing a route selection policy rule using the application guidance. The route selection policy rule includes an application descriptor and a route selection descriptor comprising network identification information, the network identification information identifying the second wireless communications network, and the route selection policy rule prescribes a route for application traffic when the user equipment device is registered in the second wireless communications network. The method further comprises transmitting the route selection policy rule to the user equipment device.

[0008] A network node in the second wireless communications network is further provided, the network node comprising a transmitter configured to send application guidance in the route selection policy rule decision to a policy control function in the first wireless communications network.

[0009] There is further provided a method in a network node in a second wireless communications network, the method comprising sending application guidance in a route selection policy rule decision to a policy control function in the first wireless communications network.

[0010] A network node in the first wireless communications network is further provided. The network node comprises a receiver and a processor. The receiver is configured to receive a request from an application function (AF) in the second wireless communications network, the request comprising service parameters identifying both the first application and the second wireless communications network. The processor is configured to store the service parameters in a Unified Data Repository (UDR) of the first wireless communications network. The network node may be a Network Exposure Function (NEF).

[0011] To explain the manner in which 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 illustrated in the accompanying drawings. Each of these drawings illustrates only some aspects of the present disclosure and therefore should not be considered as limiting its scope. The drawings may be simplified for clarity and are not necessarily drawn to scale.

[0012] A method and apparatus for implementing visited network guidance for route selection policy rules will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief description of the drawings]

[0013] [Figure 1] A diagram showing a UE, a home PLMN, and a visited PLMN. [Diagram 2]A diagram showing a procedure for service specific parameter provisioning in a home PLMN. [Diagram 3] FIG. 2 illustrates a user equipment device. [Figure 4] FIG. 2 illustrates a network node. [Diagram 5] FIG. 2 illustrates a method for a user equipment device. [Figure 6] A diagram showing a method of a network node in a first wireless communications network. [Figure 7] FIG. 1 illustrates another method of a network node in a first wireless communications network. [Figure 8] A diagram showing a method of a network node in a second wireless communications network. [Figure 9] A signaling diagram showing a procedure for a VPLMN to act on URSP rules for a UE roaming from a different PLMN. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] 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. Thus, the configurations described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, microcode, etc.), or a form combining software and hardware aspects.

[0015] 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, for example, as objects, procedures, or functions.

[0016] 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 certain configurations, the storage devices employ only signals to access the code.

[0017] Any combination of one or more computer readable media 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.

[0018] 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.

[0019] References throughout this specification to an example of a particular 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 an example of a particular 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," "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.

[0020] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, 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 the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, 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 the list. For example, "one of A, B, and C" includes only A, only B, or only 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" 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 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.

[0021] 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, and the like, 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, and the like. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the present disclosure.

[0022] Aspects of the disclosed methods and apparatus are described below with reference to schematic flow chart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products. It will be understood that each block of the schematic flow chart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flow chart 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 producing 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 flow chart illustrations and / or schematic block diagrams.

[0023] 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 flow chart diagrams and / or schematic block diagrams.

[0024] 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 generate a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for performing the functions / acts specified in the schematic flow chart illustrations and / or schematic block diagrams.

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

[0026] 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 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.

[0027] 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.

[0028] URSP rules in Release 15 and later are specified to enable a UE to determine how application traffic should be routed through the mobile communications network, either via untrusted or trusted Wireless Local Area Network (WLAN) access, via either 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 provisions and procedures are included in versions 15.0.0 and later of 23.502 and 23.503).

[0029] The URSP rule includes a traffic descriptor that allows the UE to determine whether the URSP rule matches the application traffic. The traffic descriptor includes the application descriptor (OSID / OSAppID), the IP flow descriptor (e.g., the target address of the application traffic), the Data Network Name (DNN) required by the application, or the connection capability required by the application (e.g., IMS connection).

[0030] Each URSP rule includes a Route Selection Descriptor (RSD) that indicates to the UE how a Packet Data Unit (PDU) session should be routed for the matching application traffic. The RSD includes one or more of the following: Session and Service Continuity (SSC) mode selection, network slice selection, Data Network Name (DNN) selection, Packet Data Unit (PDU) session type selection, non-seamless offload indication, and access type preference. The UE routes application traffic over PDU sessions that match the RSD elements over 3GPP or non-3GPP accesses as specified by the URSP rule.

[0031] Currently, URSP rules are only provided to the UE from the Policy Control Function (PCF) of the HPLMN (i.e., H-PCF). The UE uses the provisioned URSP rules in any PLMN to which the UE may register. When the UE is roaming, the PCF in the V-PLMN (i.e., V-PCF) is not allowed to create or provision URSP rules, but is allowed to create and provision Access Network Discovery and Selection Policy (ANDSP) rules. The PCF provisions the URSP and / or ANDSP policies to the UE in the UE policy information. The UE policy information is provided to the UE via Non-Access Stratum (NAS) signaling. The PCF allocates the URSP and ANDSP rules in policy sections in the UE policy information. Each policy section is identified by a specific policy section identifier. The PCF stores the policy sections and policy section identifiers in a database that is used as a means for the PCF to determine whether the UE needs an updated policy. When the UE registers, it includes in the registration request a policy section identifier that corresponds to a policy section stored in the UE, which allows the PCF (in both the VPLMN and the HPLMN) to identify whether an updated policy is required at the UE.

[0032] In addition, as part of the Release 17 work, it is possible for the application function to indicate to the HPLMN to create URSP rules for application traffic. This is described in Chapter 4.15.6.10 of 3GPP TS23.502 v17.3.0, which states that the AF is allowed to provide guidance for URSP determination to the 5G system via the NEF, and the home PCF determines the URSP for the UE. Section 5.2.5.6.1 of 3GPP TS23.502 v17.3.0 states that in case of roaming, the URSP rules are provided by the H-PCF, and the ANDSP rules can be provided by the V-PCF or the H-PCF or both.

[0033] This specification provides a solution for the HPLMN to identify that a specific URSP rule is required in a VPLMN. This specification also provides a solution on how the URSP rule is configured to allow the UE to determine that the URSP rule should be applied in a specific VPLMN.

[0034] 1 shows a UE 110, an HPLMN 120, and a VPLMN 140. The UE 110 may establish a connection with the Internet 190 through the HPLMN 120, or through the VPLMN 140 when roaming. The HPLMN 120 comprises a Radio Access Network (RAN) 122, an Application Management Function (AMF) 124, a Policy Control Function (PCF) 126, a User Data Management (UDM) 128, a User Data Repository (UDR) 130, a Network Exposure Function (NEF) 132, and an Application Function (AF) 134. Similarly, the VPLMN 140 comprises a RAN 142, an AMF 144, a PCF 146, a UDM 148, a UDR 150, a NEF 152, and an AF 154.

[0035] 2 shows a procedure for service-specific parameter provisioning in the HPLMN. Section 4.15.6.7 of 3GPP TS23.502 v17.3.0 describes the service-specific parameter provisioning. The AF 234 uses the Nnef_ServiceParameter service to provide the service-specific parameters to the HPLMN 220 and the UE 210.

[0036] At 271, the AF 234 invokes the Nnef_ServiceParameter_Create service operation. The request may include subscription information to the reporting of the results of the UE 210 policy delivery. To update or remove an existing request, the AF 234 invokes the Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation with the corresponding transaction reference ID provided to the AF 234 in the Nnef_ServiceParameter_Create response message. The AF 234 sends the request to the NEF 232. The NEF 232 authorizes the AF request.

[0037] At 272, the NEF 232 sends a Nudm_ServiceSpecificAuthorisation_Create Request message to the UDM 228.

[0038] At 273, the UDM 228 authorizes the AF request. The requested service-specific parameters may be the DNN, the S-NSSAI, or the machine type telecommunications provider identity.

[0039] At 274, the UDM 228 responds to the AF 234 with a Nudm_ServiceSpecificAuthorisation_Create_Response message.

[0040] At 275, the PCF 226 initiates UE policy delivery as specified in chapter 4.2.4.3 of 3GPP TS 23.502 v17.3.0. Furthermore, if the AF 234 subscribes to notifications about the result of the UE policy delivery due to the service specific parameter provisioning targeting a single UE and a UE policy container is notified to the PCF from the AMF, the PCF notifies the NEF of the UE policy delivery result contained in the UE policy container as a result of the procedure by sending an Npcf_EventExposure_Notify.

[0041] 3 illustrates a user equipment device 300 that may be used to implement the methods described herein. The user equipment device 300 is used to implement one or more of the solutions described above. The user equipment device 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0042] The input devices 315 and the output devices 320 may be combined into a single device, such as a touch screen. In some implementations, the user equipment device 300 does not include any input devices 315 and / or output devices 320. The user equipment device 300 may include one or more of the processor 305, the memory 310, and the transceiver 325, and may not include the input devices 315 and / or the output devices 320.

[0043] As shown, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The transceiver 325 may communicate with one or more cells (i.e., wireless coverage areas) supported by one or more base units. The transceiver 325 may be capable of operating on an unlicensed spectrum. Moreover, the transceiver 325 may include multiple UE panels supporting one or more beams. 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, PC5, etc. Other network interfaces 340 may be supported, as will be appreciated by those skilled in the art.

[0044] 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, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field programmable gate array ("FPGA"), or a 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.

[0045] The processor 305 may control the user equipment device 300 to implement the UE behaviors described above. The processor 305 may include an application processor (also called a “main processor”) that manages application domains and operating system (“OS”) functions, as well as a baseband processor (also called a “baseband radio processor”) that manages radio functions.

[0046] 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, a flash memory, or any other suitable non-volatile computer storage device. Memory 310 may include both volatile and non-volatile computer storage media.

[0047] The memory 310 may store data related to implementing the traffic category field as described below. The memory 310 may also store program code and related data, such as an operating system or other controller algorithms running on the device 300.

[0048] 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.

[0049] Output device 320 may be designed to output visual, audible, and / or tactile signals. Output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 320 may include, but is not limited to, 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, and the like to a user. As another non-limiting example, output device 320 may include a wearable display that is separate from but communicatively coupled to the rest of user equipment device 300, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, 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, and the like.

[0050] 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 a portion 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 touch screen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

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

[0052] 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 provide UL communication signals to a base unit of a wireless communication network. Similarly, the one or more receivers 335 may be used to receive DL communication signals from the base unit. Although only one transmitter 330 and one receiver 335 are shown, the user equipment device 300 may have any suitable number of transmitters 330 and receivers 335. Furthermore, the transmitters 330 and receivers 335 may be any suitable type of transmitter and receiver. The transceiver 325 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.

[0053] 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 used to communicate with a mobile communications network over an unlicensed radio spectrum 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 325, transmitters 330, and receivers 335 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 340.

[0054] The one or more transmitters 330 and / or the one or more receivers 335 may be implemented and / or integrated into 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. The one or more transmitters 330 and / or the one or more receivers 335 may be implemented and / or integrated into a multi-chip module. Other components, such as a network interface 340 or other hardware components / circuits, may be integrated into a single chip with any number of transmitters 330 and / or receivers 335. The transmitters 330 and receivers 335 may be logically configured as a transceiver 325 using another common control signal, or as modular transmitters 330 and receivers 335 implemented in the same hardware chip or in a multi-chip module.

[0055] 4 shows further details of a network node 400 that may be used to implement the methods described herein. The network node 400 may be one implementation of an entity in a wireless communication network. The network node 400 includes a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425.

[0056] The input devices 415 and the output devices 420 may be combined into a single device, such as a touch screen. In some implementations, the network node 400 does not include any input devices 415 and / or output devices 420. The network node 400 may include one or more of the processor 405, the memory 410, and the transceiver 425, and may not include the input devices 415 and / or the output devices 420.

[0057] As shown, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435, where the transceiver 425 communicates with one or more remote units 200. Additionally, the transceiver 425 may support at least one network interface 440 and / or an application interface 445. The application interface 445 may support one or more APIs. The network interface 440 may support 3GPP reference points, such as Uu, N1, N2, and N3. Other network interfaces 440 may be supported, as will be appreciated by those skilled in the art.

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

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

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

[0061] The input devices 415 may include any known computer input devices, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. The input devices 415 may be integrated with the output devices 420, for example, as a touch screen or similar touch-sensitive display. The input devices 415 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 devices 415 may include two or more different devices, such as a keyboard and a touch panel.

[0062] The output device 420 may be designed to output visual, audible, and / or tactile signals. The output device 420 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 420 may include a wearable display that is separate from but communicatively coupled to the rest of the network node 400, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, the output device 420 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, and the like.

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

[0064] The transceiver 425 includes at least one transmitter 430 and at least one receiver 435. The one or more transmitters 430 may be used to communicate with a UE, as described herein. Similarly, the one or more receivers 435 may be used to communicate with a network function in a PLMN and / or a RAN, as described herein. Although only one transmitter 430 and one receiver 435 are illustrated, the network node 400 may have any suitable number of transmitters 430 and receivers 435. Furthermore, the transmitters 430 and receivers 435 may be any suitable type of transmitter and receiver.

[0065] A user equipment device is provided that is registered with a first wireless communication network, the first wireless communication network being identified by a first network identification. The user equipment device may comprise a UE 110, 210, 510, and / or 910 as described herein. The user equipment device comprises a receiver and a processor. The user equipment device may be a user equipment device 300 as described with reference to FIG. 3 and comprising a processor 305, a receiver 335, and a transmitter 330. The receiver is configured to receive a route selection policy rule, the route selection policy rule including an application descriptor and a route selection descriptor, the route selection descriptor comprising a network identification. The processor is configured to detect application traffic that matches the application descriptor and determine that the network identification of the route selection descriptor matches the identification of the first wireless communication network. The processor is further configured to apply the route selection descriptor to the detected application traffic upon determining that the network identification of the route selection descriptor matches the identification of the first wireless communication network.

[0066] By applying the rules including the network identity, i.e. the network identity as described above, the user equipment can adapt the route selection according to the identity of the network to which the user equipment is registered. In the above example, the network identity of the route selection descriptor matches the first network identity, and therefore the route selection policy rule is applied to the application traffic. However, if the user equipment is to roam and register to a different network, e.g., a second wireless communication network, the route selection policy rule comprising the network identity that is the first network identity will not be applied to the application traffic.

[0067] The first wireless communication network may be a home network for the user equipment. The second wireless communication network may be a visited network for the user equipment. The user equipment may connect to the second wireless communication network while roaming. Route selection policy rules may be received from the first wireless communication network.

[0068] The first wireless communications network may be a visited network for the user equipment. The second wireless communications network may be a home network for the user equipment. Route selection policy rules may be received from the second wireless communications network.

[0069] The route selection policy rule may comprise a route selection component. The route selection component may provide various characteristics of the route to be selected for the application traffic. The route selection component may comprise at least one of an SSC mode selection, a network slice selection, a DNN selection, a PDU session type selection, a non-seamless offload indication, a Proximity-based Service (ProSe) Layer 3 UE-to-network relay offload indication, an access type preference, a PDU session pair ID, and a retransmission sequence number (RSN).

[0070] Any number of route selection components may be configured in a route selection policy rule. The number of route selection components configured in a route selection policy rule depends on the requirements of the wireless communication network.

[0071] The route selection policy rule may comprise route selection validation criteria, which comprise at least one of a network identification, a time window, and a location criterion. The route selection validation criteria define the circumstances under which the route selection policy rule must be applied. These are optional, allowing, for example, the route selection policy rule to be applied only in a particular network, only in a particular geographic area, or only during a particular time window.

[0072] 5 illustrates a method 500 of a user equipment device, where the user equipment device is registered with a first wireless communication network, the first wireless communication network being identified by a first network identification. The user equipment device may comprise a UE 110, 210, 300, 510, and / or 910 as described herein. The method 500 comprises receiving a route selection policy rule (510), where the route selection policy rule includes an application descriptor and a route selection descriptor, where the route selection descriptor comprises a network identification. The method 500 further comprises detecting application traffic matching the application descriptor (520) and determining whether the network identification of the route selection descriptor matches the identification of the first wireless communication network (530). The method 500 further comprises applying the route selection descriptor to the detected application traffic upon determining that the network identification of the route selection descriptor matches the identification of the first wireless communication network (540).

[0073] By applying the rules including the network identity, i.e. the network identity as described above, the user equipment can adapt the route selection according to the identity of the network to which the user equipment is registered. In the above example, the network identity of the route selection descriptor matches the first network identity, and therefore the route selection policy rule is applied to the application traffic. However, if the user equipment is to roam and register to a different network, e.g., a second wireless communication network, the route selection policy rule comprising the network identity that is the first network identity will not be applied to the application traffic.

[0074] A network node in the first wireless communications network is further provided, the network node comprising a processor and a transmitter. The network node may be a PCF 126, 146, 226, and / or 926 as described herein. The network node may comprise a network node 400 as described with reference to FIG. 4 and comprising a processor 405, a receiver 435, and a transmitter 430. The processor is configured to construct a route selection policy rule including an application descriptor and a route selection descriptor, the route selection descriptor comprising a network identification. The network identification identifies a second wireless communications network, and the route selection policy rule specifies a route for application traffic when the user equipment device is registered in the second wireless communications network. The transmitter is configured to transmit the route selection policy rule to the user equipment device.

[0075] By providing the user equipment with the rule including the network identity, the first wireless communication network can configure the route selection according to the identity of the network to which the user equipment is registered. In the above example, the network identity of the route selection descriptor matches the first network identity, and therefore the route selection policy rule is applied to the application traffic. However, if the user equipment is to roam and register to a different network, for example, a second wireless communication network, the route selection policy rule with the network identity that is the first network identity will not be applied to the application traffic.

[0076] The first wireless communication network is a home network for the user equipment, and the second wireless communication network is a visited network for the user equipment. Accordingly, the first wireless communication network can set a route selection policy rule that the user equipment should apply when the user equipment roams to the second wireless communication network.

[0077] The network node may comprise a policy control function. The network node may further comprise a receiver configured to receive notification of updated service parameters from a UDR in the first wireless communications network. The UDR in the first wireless communications network may receive updated SSI from an application function in the second wireless communications network. The service parameters may be service specific information.

[0078] The processor may be further configured to determine a route for application traffic in the second wireless communication network from the updated service parameters. The processor may build a route selection policy rule from the updated service parameters according to the determined route for application traffic in the second wireless communication network. The updated service parameters may be for a UE, for a group of UEs, or for an S-NSSAI / DNAI combination. S-NSSAI refers to network slice selection assistance information used to uniquely identify a network slice. DNAI refers to a data network access identifier that identifies a user plane access to one or more data networks on which a particular application may be found.

[0079] 6 illustrates a method 600 of a network node in a first wireless communications network. The network node may be a PCF 126, 146, 226, 400, and / or 926 as described herein. The method 600 comprises building (610) a route selection policy rule including an application descriptor and a route selection descriptor, the route selection descriptor comprising a network identification. The network identification identifies a second wireless communications network, and the route selection policy rule specifies a route for application traffic when the user equipment device is registered in the second wireless communications network. The method 600 further comprises transmitting (620) the route selection policy rule to the user equipment device.

[0080] A network node in the first wireless communication network is further provided. The network node may be a NEF 132, 152, 232, 932. The network node may comprise a network node 400 as described with reference to FIG. 4 and comprising a processor 405, a receiver 435, and a transmitter 430. The network node comprises a receiver configured to receive a request from an application function (AF) in the second wireless communication network, the request comprising service parameters identifying both the first application and the second wireless communication network. The network node further comprises a processor configured to store the service parameters in a Unified Data Repository (UDR) of the first wireless communication network.

[0081] The network node may be a Network Exposure Function (NEF). The stored service parameters are applied by a Policy Control Function (PCF) in the first wireless communications network to create route selection policy rules. The route selection policy rules indicate how traffic of the first application will be routed by the remote unit when the remote unit registers with the second wireless communications network. The service parameters may be service specific information.

[0082] A method in a network node in a first wireless communication network is further provided. The network node may be a NEF 132, 152, 232, 932. The network node may comprise a network node 400 as described with reference to Fig. 4. The method comprises receiving a request from an Application Function (AF) in a second wireless communication network, the request comprising service parameters identifying both the first application and the second wireless communication network. The method further comprises storing the service parameters in a Unified Data Repository (UDR) of the first wireless communication network.

[0083] A network node in the first wireless communications network is further provided. The network node may be a PCF 126, 146, 226, and / or 926 as described herein. The network node may comprise a network node 400 as described with reference to FIG. 4 and comprising a processor 405, a receiver 435, and a transmitter 430. The network node comprises a receiver, a processor, and a transmitter. The receiver is configured to receive application guidance in a route selection policy rule determination from an application function in the second wireless communications network. The processor is configured to construct a route selection policy rule using the application guidance, the route selection policy rule including an application descriptor and a route selection descriptor comprising a network identification information, the network identification information identifying the second wireless communications network, and the route selection policy rule defining a route for application traffic when the user equipment device is registered in the second wireless communications network. The transmitter is configured to transmit the route selection policy rule to the user equipment device.

[0084] A network node in the first wireless communications network may receive application guidance in route selection policy rule determination from an application function in the second wireless communications network via a network exposure function (NEF) in the first wireless communications network.

[0085] By receiving the application guidance in the route selection policy rule determination from the application function in the second wireless communication network, the network node can create a route selection policy rule having a route selection descriptor including a network identity of the second wireless communication network. Such a route selection policy rule is then sent to the user equipment, so that the first wireless communication network can set the route selection according to the identity of the network to which the user equipment is registered. For example, if the network identity of the route selection descriptor matches the network identity of the wireless communication network to which the user equipment is registered, the route selection policy rule is applied to the application traffic. In the above case, the rule is set for the second wireless communication network to which the user equipment may roam. If the user equipment is to roam and register to the second wireless communication network, the route selection policy rule with the network identity, which is the second network identity, will be applied to the application traffic that matches the route selection policy rule.

[0086] The application guidance may include a validity condition. The validity condition may comprise at least one of an identity of the second wireless communications network, a plurality of identities of the wireless communications network, or an identity of the application.

[0087] The route selection policy rules may specify a route for application traffic when a user equipment device is registered in any wireless communications network having an identity matching one of a plurality of identities of the wireless communications network.

[0088] The transmitter may be further configured to transmit the route selection policy rule to the user equipment device upon registration of the user equipment device with the first wireless communications network.

[0089] The network node may be a policy control function. The receiver may be further configured to receive notification of updated service parameters from a UDR in the first wireless communications network. The service parameters may be service specific information.

[0090] The processor may be further configured to determine a route for the application traffic in the second wireless communication network from the service parameters. The processor may build a route selection policy rule from the service parameters according to the determined route. The updated service parameters may be for a UE, for a group of UEs, or for an S-NSSAI / DNAI combination.

[0091] 7 illustrates a method 700 of a network node in a first wireless communications network. The network node may be a PCF 126, 146, 226, 400, and / or 926 as described herein. The method 700 comprises receiving (710) an application guidance in a route selection policy rule decision from an application function in a second wireless communications network. The method 700 further comprises constructing (720) a route selection policy rule using the application guidance. The route selection policy rule includes a route selection descriptor comprising an application descriptor and a network identification information, the network identification information identifying the second wireless communications network, and the route selection policy rule prescribes a route for application traffic when the user equipment device is registered in the second wireless communications network. The method further comprises transmitting (730) the route selection policy rule to the user equipment device.

[0092] By receiving the application guidance in the route selection policy rule decision from the application function in the second wireless communication network, the network node can create a route selection policy rule having a route selection descriptor including a network identity of the second wireless communication network. Such a route selection policy rule is then sent to the user equipment, so that the first wireless communication network can set the route selection according to the identity of the network to which the user equipment is registered. For example, if the network identity of the route selection descriptor matches the network identity of the wireless communication network to which the user equipment is registered, the route selection policy rule is applied to the application traffic. In the above case, the rule is set for the second wireless communication network to which the user equipment may roam. If the user equipment is to roam and register to the second wireless communication network, the route selection policy rule with the network identity, which is the second network identity, will be applied to the application traffic that matches the route selection policy rule.

[0093] There is further provided a network node in the second wireless communications network. The network node may comprise an AF 134, 154, 234, and / or 954 as described herein. The network node may comprise a network node 400 as described with reference to FIG. 4 and comprising a processor 405, a receiver 435, and a transmitter 430. The network node comprises the transmitter configured to send application guidance in the route selection policy rule decision to a policy control function in the first wireless communications network.

[0094] A network node in the second wireless communications network may be configured to send application guidance in the route selection policy rule decision to a policy control function in the first wireless communications network via a network exposure function (NEF) in the first wireless communications network.

[0095] By sending the application guidance in the route selection policy rule decision from the application function in the second wireless communication network, the network node can inform the policy control function in the first wireless communication network that such policy control function should create a route selection policy rule for a particular application traffic when the user equipment roams to the second wireless communication network. After creation, such route selection policy rule may then be sent to the user equipment, so that the first wireless communication network can set the route selection according to the identity of the network to which the user equipment is registered. For example, if the network identity of the route selection descriptor matches the network identity of the wireless communication network to which the user equipment is registered, the route selection policy rule is applied to the application traffic. In the above case, the rule is set for the second wireless communication network to which the user equipment may roam. If the user equipment is to roam and register to the second wireless communication network, the route selection policy rule with the network identity, which is the second network identity, will be applied to the application traffic that matches the route selection policy rule according to the application guidance sent in the route selection policy rule decision.

[0096] The application guidance may include a validity condition, the validity condition comprising at least one of an identity of the second wireless communications network, a plurality of identities of the wireless communications network, and / or an identity of the application.

[0097] The route selection policy rules may specify a route for application traffic when a user equipment device is registered in any wireless communications network having an identity matching one of a plurality of identities of the wireless communications network.

[0098] The network node may be triggered to send application guidance in route selection policy rule decisions upon determining a desired user equipment specific disposition of routing traffic to the second wireless communications network. Such a decision may be made when a particular class of application traffic exceeds some threshold.

[0099] The network node may be an application function. The application function may be an application function in a PLMN other than the home PLMN of the user equipment. The application function may be an application function in a PLMN other than the home PLMN of the user equipment.

[0100] 8 shows a method 800 of a network node in a second wireless communications network. The network node may comprise an AF 134, 154, 234, 400, and / or 954 as described herein. The method 800 comprises sending (810) application guidance in a route selection policy rule decision to a policy control function in the first wireless communications network.

[0101] By sending the application guidance in the route selection policy rule decision from the application function in the second wireless communication network, the network node can inform the policy control function in the first wireless communication network that such policy control function should create a route selection policy rule for a particular application traffic when the user equipment roams to the second wireless communication network. After creation, such route selection policy rule may then be sent to the user equipment, so that the first wireless communication network can set the route selection according to the identity of the network to which the user equipment is registered. For example, if the network identity of the route selection descriptor matches the network identity of the wireless communication network to which the user equipment is registered, the route selection policy rule is applied to the application traffic. In the above case, the rule is set for the second wireless communication network to which the user equipment may roam. If the user equipment is to roam and register to the second wireless communication network, the route selection policy rule with the network identity, which is the second network identity, will be applied to the application traffic that matches the route selection policy rule according to the application guidance sent in the route selection policy rule decision.

[0102] A network node in the first wireless communication network is further provided. The network node may be a NEF 132, 152, 232, 932. The network node may comprise a network node 400 as described with reference to FIG. 4 and comprising a processor 405, a receiver 435, and a transmitter 430. The network node comprises a receiver and a processor. The receiver is configured to receive a request from an application function (AF) in the second wireless communication network, the request comprising service parameters identifying both the first application and the second wireless communication network. The processor is configured to store the service parameters in a Unified Data Repository (UDR) of the first wireless communication network.

[0103] The network node may be a Network Exposure Function (NEF). The stored service parameters are applied by a Policy Control Function (PCF) in the first wireless communications network to create a route selection policy rule. The route selection policy rule indicates how traffic of the first application will be routed by the remote unit when the remote unit registers with the second wireless communications network.

[0104] A method of a network node in a first wireless communication network is further provided. The method comprises receiving a request from an Application Function (AF) in a second wireless communication network, the request comprising service parameters identifying both the first application and the second wireless communication network. The processor is configured to store the service parameters in a Unified Data Repository (UDR) of the first wireless communication network. The network node may be a Network Exposure Function (NEF).

[0105] According to the methods and apparatus described herein, an AF in a VPLMN may provide guidance for creating URSP rules in a PLMN different from the HPLMN. In one use case, an application function in the VPLMN requires specific processing of UE application traffic. The AF in the visited PLMN (or different PLMN) provides the service information reusing the service specific information provisioning procedure described in 3GPP TS 23.502 v17.3.0 with the difference that the AF includes an indication to apply this rule only to UEs targeted in the specific PLMN.

[0106] The trigger for the AF request may result from the desire of the AF service provider in the VPLMN to use a specific DNN / S-NSSAI procedure for the roaming UE. Additionally or alternatively, the trigger may be provided by a network slice capability enablement server as specified in 3GPP TS25.434 v16.0.0. The NSCE server may be located in the AF. The NSCE server may receive from the NSCE client (located in the UE) a network / slice notification re-mapping for the application based on the configuration provided by the NSCE server to the NSCE client in the UE.

[0107] The NEF stores the AF request information together with the assigned transaction reference ID (provided by the AF) in a UDR in the "application data" field in the service specific information data subset.

[0108] When the PCF receives the updated subscription information from the UDR, the PCF derives the updated URSP rule for the UE (or any UE) with information in the URSP rule indicating to the UE that this URSP rule applies only when registering to a specific PLMN. In one embodiment, the PLMN information may be included as a separate validity condition in the route selection descriptor. An example is shown in the table below.

[0109] [Table 1A]

[0110] [Table 1B]

[0111] In an alternative embodiment, the PLMN validity conditions may be included in the UE location validity information.

[0112] 9 is a signaling diagram illustrating a procedure for a VPLMN to act on URSP rules for a UE roaming from a different PLMN. A UE 910 communicates with a Home PLMN 920. The Home PLMN 920 comprises a PCF 926, a UDM 928, a UDR 930, and a NEF 932. A Visited PLMN (VPLMN) comprises a Visited AF (V-AF) 954 and a Visited PCF (V-PCF) 946.

[0113] At 971, the AF in the VPLMN is triggered to request the UE's home PLMN for specific processing of routing traffic to the VPLMN.

[0114] At 972, the NEF includes the updated service information in a request to the AF to invoke the service operation. The updated information includes the validity conditions for applying the URSP rules in a particular PLMN. The validity information may also include a list of VPLMNs. This procedure is described in 3GPP TS23.502 v17.3.0, chapter 4.15.6.10. The request may be applicable for any UE or the AF may include the domain information and / or external identifier of the UE.

[0115] At 973, the NEF 932 sends an authorization request via a Nudm_ServiceSpecificAuthorization_Create Request message to the UDM 928. At 974, the UDM 928 authorizes the request. At 975, the UDM sends the authorization via a Nudm_ServceSpecificAuthorization_Create Response message to the NEF 932. Steps 973-975 may be performed in accordance with 3GPP TS 23.502 v17.3.0.

[0116] At 976, in response to successful authorization, the NEF 932 updates the data in the UDR 930 with the updated service information in the application data. The NEF 932 invokes a Nudr_DM_Create (or Update) service request requesting that the UDR 930 store the service information in the "application data" data set in the service specific information data subset identifier. The NEF 932 may also include a data key indicating the target UE or group of UEs. In one embodiment, the service information is stored in the existing service information parameters with the S-NSSAI or DNN of the service information as the data key (if the request is for any UE).

[0117] At 977, the UDR 930 acknowledges the NEF request.

[0118] At 978, the NEF 932 acknowledges the AF request.

[0119] At 979, if the PCF 926 subscribes to the service specific information, the UDR 930 notifies the PCF 926 of the updated service information.

[0120] At 980, when the UE 910 registers with the HPLMN 920 (or VPLMN), the UE 910 may include a list of Public Service Identities (PSI). The AMF (in the HPLMN) or the V-PCF 946 (in the VPLMN) (as shown in FIG. 9 ) initiates a UE 910 policy association creation request, with the PCF 926 including the list of PSI associated with the HPLMN 920 in the request.

[0121] At 981 , the PCF 926 retrieves the application data subscription information from the UDR 930 .

[0122] At 982, the PCF 926 creates updated URSP rules according to the information stored in the UDR 930, including URSP rules with validity conditions for each PLMN.

[0123] At 983, the PCF 926 provides the updated URSP rules to the UE 910 by initiating a UE configuration update for transparent policy delivery (via the V-PCF 946 if the UE is roaming) to deliver the updated URSP rules to the UE 910.

[0124] At 984, the UE 910 acknowledges the successful implementation of the rule.

[0125] At 985, if the V-AF 954 has subscribed to notifications of successful policy distribution, the PCF 926 notifies the UDM 928.

[0126] At 986, the UDM 928 informs the NEF 932 of the successful policy distribution, which at 987 the NEF 932 acknowledges.

[0127] At 988, the NEF 932 informs the V-AF 954 of the successful policy distribution. At 989, the V-AF 954 acknowledges this.

[0128] Upon receiving the URSP rules including the PLMN validity conditions, the UE 910 enforces the URSP rules as follows. · When the UE finds that the application traffic matches the traffic descriptor of a URSP rule, the UE checks the list of route selection descriptors of the matched URSP rule. If an RSD in the list of RSDs contains a PLMN validity condition, the UE checks whether the PLMN identity in the validity condition matches the PLMN identity of the registered PLMN or a PLMN equivalent to the registered PLMN. If there is a match, the UE considers the RSD valid and routes the application traffic according to the contents of the route selection descriptor. If there is no match, the UE considers the RSD invalid and proceeds to process the second RSD in the list of RSDs of the matched URSP rule, if available. If the other RSDs are not consistent, the UE will regard the URSP rule as inconsistent and process the different URSP rule.

[0129] Currently, URSP rules are provided only by the HPLMN, and the UE applies the same URSP rules in any PLMN that the UE registers in. This creates a problem when the UE is roaming, where the VPLMN operator may require specific traffic routing treatment for certain applications that differs from the applications required by the HPLMN.

[0130] As part of the Release 18 work, 3GPP SA2 will identify how a V-PLMN can act on an H-PLMN to create and provision URSP rules. This specification provides a solution that helps enable an HPLMN to identify that a specific URSP rule is required in a VPLMN. This specification additionally provides a solution that helps specify how the URSP rule is configured to enable a UE to determine that a URSP rule should be applied in a specific VPLMN.

[0131] According to the solution provided herein, an AF in a different PLMN (i.e., a visited PLMN for the UE) provides HPLMN information to assist the HPLMN in creating URSP rules that the UE can use when registered in that VPLMN. A new configuration of URSP rules is provided to include a validity condition in the route selection descriptor of the URSP rule to enable the UE to determine that the route selection descriptor is valid only when the UE is registered in a particular VPLMN.

[0132] It is known that the AF may provide guidance to PLMNs for creating URSP rules. According to the solution provided herein, URSP rules for different PLMNs may be created.

[0133] Accordingly, a PCF is provided that is configured to construct URSP rules for different VPLMNs by including validity conditions in the route selection descriptor of the URSP rule.

[0134] There is further provided a Network Exposure Function (NEF) in the first mobile communications network configured to receive a request from an Application Function (AF) providing service parameters for a first application, the request comprising a first indication that the service parameters are to be applied in the second mobile communications network, and to store the service parameters in a Unified Data Repository (UDR) in the first mobile communications network, the stored service parameters being applied by a Policy Control Function (PCF) in the first mobile communications network to create URSP rules, the URSP rules indicating how traffic of the first application is to be routed by the remote unit upon registration of the remote unit in the second mobile communications network. The first indication may be a VPLMN-ID.

[0135] A Policy Control Function (PCF) in the first mobile communications network is further provided, where the PCF is configured to receive a notification from the UDR of updated service-specific information for a UE, for a group of UEs, or for an S-NSSAI / DNAI combination, determine a specific treatment of application traffic routing in the second mobile communications network from the service-specific information, and construct a URSP rule including a validity condition in the route selection descriptor to apply the contents of the route selection descriptor when a device is registered in the second mobile communications network.

[0136] Further provided is a UE in the first mobile communications network configured to receive a URSP rule from the second mobile communications network, detect application traffic matching an application descriptor in the URSP rule, determine that a route selection descriptor in the matched URSP rule includes a validity condition for a PLMN, and apply the route selection descriptor component of the matched URSP rule upon determining that a PLMN identifier in the validity condition matches a PLMN identity of the first mobile communications network.

[0137] It should be noted that the above-described methods and apparatus illustrate rather than limit the 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 recited in a claim, and "a" or "an" does not exclude a plurality, and 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.

[0138] Furthermore, while examples are given in the context of particular communication standards, these examples are not intended to be a limitation of the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples are given in the given 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.

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

[0140] The described method and apparatus may be embodied in other specific forms. The described method and apparatus should be considered in all respects as illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the above 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]

[0141] 110 User Equipment (UE) 120 HPLMN 122 Radio Access Network (RAN) 124 Application Management Facility (AMF) 126 Policy Control Function (PCF) 128 User Data Management (UDM) 130 User Data Repository (UDR) 132 Network Exposure Function (NEF) 134 Application Functions (AF) 140 VPLMN 142 RAN 144 AMF 146 PCF 148 UDM 150 UDR 152 NEF 154AF 190 Internet 200 Remote Unit 210UE 220 HPLMN 226 PCF 228 UDM 232 NEF 234AF 300 User equipment device 305 Processor 310 Memory 315 Input Devices 320 Output Device 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interface 345 Application Interface 400 network nodes 405 Processor 410 Memory 415 Input Devices 420 output device 425 Transceiver 430 Transmitter 435 Receiver 440 Network Interface 445 Application Interface 510UE 910UE 920 Home PLMN 926 PCF 928 UDM 930 UDR 932 NEF 946 Visited PCF (V-PCF) 954 Visiting AF (V-AF)

Claims

1. A network node in a first wireless communications network, comprising: a receiver configured to receive application guidance in route selection policy rule determination from an application function in the second wireless communications network; a processor configured to construct route selection policy rules using the application guidance, the route selection policy rules including an application descriptor and a route selection descriptor comprising a network identification information, the network identification information identifying the second wireless communications network, the route selection policy rules defining a route for application traffic when a user equipment device is registered in the second wireless communications network; and a transmitter configured to transmit the route selection policy rules to the user equipment device; A network node comprising:

2. The network node of claim 1 , wherein the application guide includes a validity condition.

3. The validity condition is: an identity of the second wireless communications network; A plurality of identities of wireless communications networks; or Application Identity The network node of claim 2, comprising at least one of:

4. 4. The network node of claim 1, wherein the transmitter is further configured to transmit the route selection policy rules to the user equipment device.

5. 5. A network node according to claim 1, wherein the network node is a policy control function.

6. The network node of claim 1 , wherein the receiver is further configured to receive notification of updated service parameters from a UDR in the first wireless communications network.

7. The network node of claim 6, wherein the processor is further configured to determine a route for application traffic in a second wireless communications network from the service parameters.

8. The network node according to claim 6 or 7, wherein the processor is further configured to construct the route selection policy rules from the service parameters according to the determined route.

9. 1. A method in a network node in a first wireless communications network, comprising: receiving application guidance in route selection policy rule determination from an application function in the second wireless communications network; constructing a route selection policy rule using the application guidance, the route selection policy rule including a route selection descriptor comprising an application descriptor and a network identification information, the network identification information identifying the second wireless communications network, the route selection policy rule defining a route for application traffic when a user equipment device is registered in the second wireless communications network; transmitting the route selection policy rules to the user equipment device; A method comprising:

10. a network node in a second wireless communications network, a transmitter configured to send application guidance in route selection policy rule determination to a policy control function in the first wireless communications network; A network node comprising:

11. The network node of claim 10, wherein the application guide includes a validity condition.

12. The validity condition is: an identity of the second wireless communications network; A plurality of identities of wireless communications networks; or Application Identity The network node of claim 11, comprising at least one of:

13. 13. The network node of claim 10, 11 or 12, wherein upon determining a desired user equipment specific disposition of routing traffic to the second wireless communications network, the network node is triggered to send application guidance in a route selection policy rule determination.

14. 14. A network node according to any one of claims 10 to 13, wherein the network node is an application function.

15. A method in a network node in a second wireless communications network, comprising: Sending application guidance in the route selection policy rule determination to a policy control function in the first wireless communications network. A method comprising:

Images