Destination 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 destination network identification information. This specification defines network nodes in a first wireless communication network, methods of network nodes in a first wireless communication network, network nodes in a second wireless communication network, and methods of network nodes in a second wireless communication network.

Background Art

[0002] User Equipment (UE) Route Selection Policy (URSP) rules and procedures for a UE to apply URSP rules are described in 3GPP (registered trademark) TS23.502 v17.3.0 and 3GPP TS23.503 v17.3.0. A URSP rule includes a traffic descriptor that enables a UE to determine whether the URSP rule matches application traffic. The traffic descriptor includes an application descriptor that may define operating system identity (OSID) and operating system application identity (OSAppID). The traffic descriptor also includes an IP flow descriptor 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 identifier may roam away from its home public land mobile network (PLMN) and access services within the roaming area by using the visited PLMN. In principle, once a communication is established, the UE is uninterrupted within its PLMN area. [Overview of the project] [Problems that the invention aims to solve]

[0004] The problem with existing UE route selection policy rules is that they can only be set by the home PLMN. Furthermore, such rules are universally applied by UEs, regardless of which PLMN the UE is registered with.

[0005] Procedures for implementing destination network guidance for route selection policy rules are disclosed herein. These procedures may be performed by user equipment and at least one node of at least one wireless communication network. [Means for solving the problem]

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

[0007] A method for a network node in a first wireless communication network is further provided. The method comprises the step of receiving application guidance in route selection policy rule determination from an application function in a second wireless communication network. The method further comprises the step of constructing a route selection policy rule using the application guidance. The route selection policy rule includes an application descriptor and a route selection descriptor having network identification information, the network identification information identifies the second wireless communication network, and the route selection policy rule defines the route for application traffic when a user device is registered in the second wireless communication network. The method further comprises the step of transmitting the route selection policy rule to the user device.

[0008] Further network nodes are provided within a second wireless communication network. Each network node includes a transmitter configured to send application guidance in route selection policy rule determination to a policy control function within the first wireless communication network.

[0009] A method for a network node in a second wireless communication network is further provided. The method comprises the step of sending application guidance in route selection policy rule determination to a policy control function in the first wireless communication network.

[0010] Further, network nodes are provided within the first wireless communication network. Each network node comprises a receiver and a processor. The receiver is configured to receive requests from application functions (AF) within the second wireless communication network, the requests comprising service parameters that identify 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) within the first wireless communication network. The network node may also be a Network Exposure Function (NEF).

[0011] To illustrate the manner in which the advantages and features of this disclosure can be obtained, the description of this disclosure is expressed by reference to several apparatuses and methods illustrated in the accompanying drawings. Each of these drawings illustrates only a few aspects of this disclosure and should therefore not be considered to limit its scope. The drawings may be simplified for clarity and are not necessarily drawn to a specific scale.

[0012] A method and apparatus for implementing destination network guidance for route selection policy rules is described below as an example, with reference to the attached drawings. [Brief explanation of the drawing]

[0013] [Figure 1] This diagram shows the UE, home PLMN, and visited PLMN. [Figure 2]This diagram shows the procedure for provisioning service-specific parameters in Home PLMN. [Figure 3] This is a diagram showing user equipment. [Figure 4] This diagram shows network nodes. [Figure 5] This diagram shows the method for user equipment. [Figure 6] This diagram shows the method of a network node in the first wireless communication network. [Figure 7] This diagram shows another method for network nodes in a first wireless communication network. [Figure 8] This diagram shows the method of a network node in a second wireless communication network. [Figure 9] This is a signaling diagram illustrating the procedure for VPLMN to act on URSP rules for UEs roaming from different PLMNs. [Modes for carrying out the invention]

[0014] As will be understood by those skilled in the art, aspects of this disclosure may be embodied as systems, apparatus, methods, or program products. Accordingly, the configurations described herein may be implemented in hardware form as a whole, in software form as a whole (including firmware, resident software, microcode, etc.), or in a combination of software and hardware forms.

[0015] For example, the disclosed methods and apparatus may be implemented as hardware circuits comprising custom very-large-scale integration ("VLSI") circuits or off-the-shelf semiconductors such as gate arrays, logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented as programmable hardware devices such as field-programmable gate arrays, programmable array logic, or programmable logic devices. 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 objects, procedures, or functions, for example.

[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, which are referred to below as code. The storage devices may be tangible, non-temporary, and / or non-transmitting. The storage devices may not embody signals. In certain configurations, the storage devices employ only signals for accessing the code.

[0017] Any combination of one or more computer-readable media may be used. The computer-readable media may be computer-readable storage media. The computer-readable storage media may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination thereof.

[0018] More specific examples (non-exhaustive list) of a memory device would include the following, namely, an electrical connection having one or more wires, a portable computer diskette, a hard disk, random-access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM") or flash memory, a portable compact disc read-only memory ("CD-ROM"), an optical memory device, a magnetic memory device, or any suitable combination of the foregoing. 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 in connection with that example is included in at least one implementation of the methods and apparatuses described herein. Thus, references to features of an example of a particular method or apparatus, or similar language, may, but not necessarily, refer to the same example, and may, unless otherwise specified, mean "one or more, but not all, examples". The terms "including", "comprising", "having", and variations thereof mean "including, without limitation", unless otherwise specified. An enumerated listing of items does 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 that list, or any combination of items in that list. For example, the list 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 any 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 any single item in that list, or a unique one. 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. When used herein, “members selected from the group consisting of A, B, and C” includes one unique individual of A, B, or C, but excludes combinations of A, B, and C. When used herein, “members selected from the group consisting of A, B, and C, and their combinations” 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 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, one of ordinary skill in the art will recognize that the disclosed methods and apparatuses may 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 illustrated or described in detail to avoid obscuring aspects of the present disclosure.

[0022] Aspects of the disclosed methods and apparatuses are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus, such that the instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / acts specified in the schematic flowcharts 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 include instructions for generating a manufacture including instructions for implementing the functions / acts specified in the schematic flowcharts and / or schematic block diagrams.

[0024] The code may also be loaded onto a computer, another programmable device, or another device to cause it to execute a series of operational steps on the computer, another programmable device, or another device in order to generate a computer-executed process, and as a result, the code executed on the computer or other programmable device provides a process for performing functions / actions specified in schematic flowcharts and / or schematic block diagrams.

[0025] The schematic flowcharts and / or schematic block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of the device, system, method, and program product. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code containing one or more executable instructions of code for performing a specified logical function.

[0026] It should also be noted that in some alternative implementations, the functions mentioned within a block may be performed in a different order than those mentioned in the diagram. For example, two blocks shown consecutively may actually be executed substantially in parallel, or blocks may sometimes be executed in reverse order depending on the functionality involved. Other steps and methods may be conceivable that are equivalent in function, logic, or effect to one or more blocks or parts thereof in the illustrated diagram.

[0027] The descriptions of elements within each drawing may refer to elements in preceding drawings. Similar numbers refer to the same elements across all drawings.

[0028] The URSP rules, available from Release 15 onwards, enable UEs to determine how application traffic should be routed through mobile communications networks via untrusted or trusted Wireless Local Area Network (WLAN) access, via either 3GPP or non-3GPP access, or how traffic should be routed non-seamlessly by bypassing the mobile communications network via WLAN connections. The URSP rules and procedures for UEs to apply them are described in 3GPP TS23.502 v17.3.0 and 3GPP TS23.503 v17.3.0 (the URSP rules and procedures are included in versions 15.0.0 and later of 23.502 and 23.503).

[0029] A URSP rule includes a traffic descriptor that allows the UE to determine whether the URSP rule is consistent with application traffic. The traffic descriptor may include an application descriptor (OSID / OSAppID), an IP flow descriptor (e.g., the target address of the application traffic), a data network name (DNN) requested by the application, or connectivity required by the application (e.g., IMS connectivity).

[0030] Each URSP rule includes a Route Selection Descriptor (RSD) that tells the UE how to route Packet Data Unit (PDU) sessions for consistent 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 representation, and access type preference. The UE routes application traffic through PDU sessions that are consistent with the RSD components via 3GPP or non-3GPP access as defined by the URSP rule.

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

[0032] In addition, as part of the Release 17 work, application functions can instruct the HPLMN to create URSP rules for application traffic. This is stated in Chapter 4.15.6.10 of 3GPP TS23.502 v17.3.0, which states that the AF is permitted 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 the case of roaming, the URSP rules are provided by the H-PCF, and the ANDSP rules may be provided by the V-PCF, the H-PCF, or both.

[0033] This specification provides solutions for HPLMNs to identify when specific URSP rules are required within a VPLMN. This specification also provides solutions on how URSP rules should be structured to enable UEs to determine when URSP rules should be applied within a particular VPLMN.

[0034] Figure 1 shows UE110, HPLMN120, and VPLMN140. UE110 may establish a connection to the Internet 190 via HPLMN120, or via VPLMN140 when roaming. HPLMN120 includes 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, VPLMN140 includes a RAN 142, an AMF 144, a PCF 146, a UDM 148, a UDR 150, a NEF 152, and an AF 154.

[0035] Figure 2 shows the procedure for service-specific parameter provisioning in HPLMN. Section 4.15.6.7 of 3GPP TS23.502 v17.3.0 describes service-specific parameter provisioning. AF234 uses the Nnef_ServiceParameter service to provide service-specific parameters to HPLMN220 and UE210.

[0036] In step 271, AF234 invokes the Nnef_ServiceParameter_Create service operation. The request may include subscription information for reporting the results of UE210 policy distribution. To update or delete an existing request, AF234 invokes the Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation, along with the corresponding transaction reference ID provided to AF234 in the Nnef_ServiceParameter_Create response message. AF234 sends the request to NEF232. NEF232 authorizes the AF request.

[0037] In step 272, NEF232 sends a Nudm_ServiceSpecificAuthorisation_Create Request message to UDM228.

[0038] In step 273, UDM228 authorizes the AF request. The requested service-specific parameters may be DNN, S-NSSAI, or machine-type communication provider identification information.

[0039] In step 274, UDM228 responds to AF234 with the Nudm_ServiceSpecificAuthorisation_Create_Response message.

[0040] In step 275, PCF226 initiates UE policy distribution as specified in Chapter 4.2.4.3 of 3GPP TS23.502 v17.3.0. Furthermore, if AF234 is subscribed to notifications about the results of UE policy distribution due to service-specific parameter provisioning targeting a single UE, and the UE policy container is notified to PCF from AMF, PCF notifies NEF of the UE policy distribution results contained within the UE policy container as a result of that procedure by sending Npcf_EventExposure_Notify.

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

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

[0043] As shown in the figure, 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 unlicensed spectrum. Furthermore, the transceiver 325 may include multiple UE panels supporting one or more beams. In addition, 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 understood by those skilled in the art.

[0044] The processor 305 may include any known controller capable of executing computer-readable instructions and / or logical operations. For example, the processor 305 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 305 may execute instructions stored in memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to memory 310, input device 315, output device 320, and transceiver 325.

[0045] The processor 305 may control the user equipment 300 to perform the UE behavior described above. The processor 305 may include an application processor (also called the "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also called the "baseband radio processor") that manages wireless functions.

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

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

[0048] The input device 315 may include any known computer input device, including touch panels, buttons, keyboards, styluses, microphones, etc. The input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display. The input device 315 may include a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. The input device 315 may include two or more different devices, such as a keyboard and a touchscreen.

[0049] The output device 320 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 320 may include an electronically controllable display or display device that can output visual data to the user. For example, the 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 a similar display device that can output images, text, etc., to the user. As another non-limiting example, the output device 320 may include a wearable display that is separate from the rest of the user equipment device 300 but communicatively coupled to it, such as a smartwatch, smart glasses, or a head-up display. Furthermore, the output device 320 may be a component of a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, or vehicle dashboard.

[0050] The output device 320 may include one or more speakers for generating sound. For example, the output device 320 may generate an audible alarm or notification (e.g., a beep or chime). The output device 320 may include one or more haptic devices for generating vibration, motion, or other tactile 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.

[0051] The transceiver 325 communicates with one or more network functions of a mobile communication 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, and similarly to receive messages, data, and other signals. For example, the processor 305 may selectively activate the transceiver 325 (or a portion thereof) at certain times to send and receive messages.

[0052] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. One or more transmitters 330 may be used to provide UL communication signals to a base unit of a wireless communication network. Similarly, 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 illustrated, the user equipment 300 may have any preferred number of transmitters 330 and receivers 335. Furthermore, the transmitters 330 and receivers 335 may be any preferred 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 licensed radio spectrum, and a second transmitter / receiver pair used to communicate with a mobile communications network over unlicensed radio spectrum may be combined with a single transceiver unit, for example, a single chip that performs functions for use with both licensed and unlicensed radio spectrum. The first and second transmitter / receiver pairs may share one or more hardware components. For example, several transceivers 325, transmitters 330, and receivers 335 may be implemented as physically separate components that access shared hardware and / or software resources, such as a network interface 340.

[0054] One or more transmitters 330 and / or 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-a-chip, an Application-Specific Integrated Circuit ("ASIC"), or other types of hardware components. One or more transmitters 330 and / or 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 along with any number of transmitters 330 and / or receivers 335. 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] Figure 4 shows further details of a network node 400 that may be used to implement the method 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, memory 410, input device 415, output device 420, and transceiver 425.

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

[0057] As shown in the figure, 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. In addition, the transceiver 425 may support at least one network interface 440 and / or 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 understood by those skilled in the art.

[0058] The processor 405 may include any known controller capable of executing computer-readable instructions and / or 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 memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to memory 410, input device 415, output device 420, and transceiver 425.

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

[0060] Memory 410 may store data related to establishing a multipath unicast link and / or mobile operation. For example, memory 410 may store parameters, configurations, resource allocations, policies, etc., as described above. 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 device 415 may include any known computer input device, including touch panels, buttons, keyboards, styluses, microphones, etc. The input device 415 may be integrated with the output device 420, for example, as a touchscreen or similar touch-sensitive display. The input device 415 may include a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. The input device 415 may include two or more different devices, such as a keyboard and a touchscreen.

[0062] The output device 420 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 420 may include an electronically controllable display or display device that can output 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 that can output images, text, etc., 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 smartwatch, smart glasses, or a head-up display. Furthermore, the output device 420 may be a component of a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, vehicle dashboard, etc.

[0063] The output device 420 may include one or more speakers for generating sound. For example, the output device 420 may generate an audible alarm or notification (e.g., a beep or chime). The output device 420 may include one or more haptic devices for generating vibration, motion, or other haptic feedback. All or part 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 touchscreen 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. One or more transmitters 430 may be used to communicate with a UE, as described herein. Similarly, one or more receivers 435 may be used to communicate with network functions in the PLMN and / or RAN, as described herein. Although only one transmitter 430 and one receiver 435 are illustrated, a network node 400 may have any preferred number of transmitters 430 and receivers 435. Furthermore, the transmitters 430 and receivers 435 may be any preferred type of transmitter and receiver.

[0065] A user device is provided that is registered with a first wireless communication network, and the first wireless communication network is identified by first network identification information. The user device may include UE110, 210, 510, and / or 910 as described herein. The user device includes a receiver and a processor. The user device may be user device 300 as described with reference to Figure 3, and comprising a processor 305, a receiver 335, and a transmitter 330. The receiver is configured to receive route selection policy rules, which include an application descriptor and a route selection descriptor, the route selection descriptor comprising network identification information. The processor is configured to detect application traffic that matches the application descriptor and to determine that the network identification information of the route selection descriptor matches the identification information of the first wireless communication network. Once the processor has determined that the network identification information of the route selection descriptor matches the identification information of the first wireless communication network, it is further configured to apply the route selection descriptor to the detected application traffic.

[0066] By applying rules that include network identification information, i.e., the network identification information described above, user devices can adapt route selection according to the identification information of the network to which the user device is registered. In the example above, the network identification information of the route selection descriptor matches the first network identification information, and therefore the route selection policy rule is applied to application traffic. However, if the user device roams to a different network, for example, a second wireless communication network, and registers with it, the route selection policy rule with the network identification information, which is the first network identification information, will not be applied to application traffic.

[0067] The first wireless communication network may be the user's home network. The second wireless communication network may be the user's destination network. The user's device 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 communication network may be a destination network for the user's device. The second wireless communication network may be the user's home network. Route selection policy rules may be received from the second wireless communication network.

[0069] Route selection policy rules may include route selection components. Route selection components may provide various characteristics of the route to be selected for application traffic. Route selection components may include at least one of the following: SSC mode selection, network slice selection, DNN selection, PDU session type selection, non-seamless offload indication, proximity-based service (ProSe) Layer 3 UE to network relay offload indication, access type preference, PDU session pair ID, and retransmission sequence number (RSN).

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

[0071] Route selection policy rules may include route selection validation criteria, which include at least one of network identification information, a time window, and a location criterion. The route selection validation criteria define the environment in which the route selection policy rules must be applied. These are optional and allow, for example, that the route selection policy rules be applied only within a specific network, only within a specific geographical area, or only during a specific time window.

[0072] Figure 5 shows Method 500 for a user device, where the user device is registered with a first wireless communication network, and the first wireless communication network is identified by first network identification information. The user device may include UE110, 210, 300, 510, and / or 910 as described herein. Method 500 comprises the step of receiving a route selection policy rule (510), the route selection policy rule including an application descriptor and a route selection descriptor, the route selection descriptor comprising network identification information. Method 500 further comprises the step of detecting application traffic that matches the application descriptor (520), and the step of determining whether the network identification information of the route selection descriptor matches the identification information of the first wireless communication network (530). If Method 500 determines that the network identification information of the route selection descriptor matches the identification information of the first wireless communication network, it further comprises the step of applying the route selection descriptor to the detected application traffic (540).

[0073] By applying rules that include network identification information, i.e., the network identification information described above, user devices can adapt route selection according to the identification information of the network to which the user device is registered. In the example above, the network identification information of the route selection descriptor matches the first network identification information, and therefore the route selection policy rule is applied to application traffic. However, if the user device roams to a different network, for example, a second wireless communication network, and registers with it, the route selection policy rule with the network identification information, which is the first network identification information, will not be applied to application traffic.

[0074] Further network nodes are provided in the first wireless communication network, each comprising a processor and a transmitter. The network nodes may be PCF126, 146, 226, and / or 926 as described herein. The network nodes may also include network node 400, as described with reference to Figure 4, and comprising a processor 405, a receiver 435, and a transmitter 430. The processor is configured to construct route selection policy rules including an application descriptor and a route selection descriptor, the route selection descriptor comprising network identification information. The network identification information identifies a second wireless communication network, and the route selection policy rules define the routes for application traffic when a user device registers in the second wireless communication network. The transmitter is configured to transmit the route selection policy rules to the user device.

[0075] By providing user devices with rules that include network identification information, the first wireless communication network can configure route selection according to the identification information of the network to which the user devices register. In the example above, the network identification information of the route selection descriptor matches the first network identification information, and therefore the route selection policy rules are applied to application traffic. However, if the user devices roam to a different network, for example, a second wireless communication network, and register with it, the route selection policy rules that include the network identification information of the first network identification information will not be applied to application traffic.

[0076] The first wireless communication network is the user's home network, and the second wireless communication network is the user's destination network. Accordingly, the first wireless communication network can set route selection policy rules that the user's device should apply when roaming to the second wireless communication network.

[0077] The network node may have a policy control function. The network node may further include a receiver configured to receive notifications of updated service parameters from a UDR in a first wireless communication network. The UDR in the first wireless communication network may receive updated SSIs from an application function in a second wireless communication network. The service parameters may be service-specific information.

[0078] The processor may be further configured to determine routes for application traffic in a second wireless communication network from updated service parameters. The processor may construct route selection policy rules from the updated service parameters according to the determined routes for application traffic in the second wireless communication network. The updated service parameters may be for UEs, for groups of UEs, or for S-NSSAI / DNAI combinations. S-NSSAI refers to network slice selection assistance information used to uniquely identify network slices. DNAI refers to a data network access identifier that identifies user plane access to one or more data networks where a particular application may find.

[0079] Figure 6 shows Method 600 for a network node in a first wireless communication network. The network node may be a PCF126, 146, 226, 400, and / or 926 as described herein. Method 600 comprises the step (610) of constructing a route selection policy rule including an application descriptor and a route selection descriptor, the route selection descriptor comprising network identification information. The network identification information identifies a second wireless communication network, and the route selection policy rule defines the route for application traffic when a user device is registered in the second wireless communication network. Method 600 further comprises the step (620) of transmitting the route selection policy rule to the user device.

[0080] Further network nodes are provided in the first wireless communication network. The network nodes may be NEF132, 152, 232, and 932. The network nodes may include network node 400, as described with reference to Figure 4, and comprising a processor 405, a receiver 435, and a transmitter 430. The network node includes a receiver configured to receive requests from application functions (AFs) in the second wireless communication network, the requests comprising service parameters that identify both the first application and the second wireless communication network. The network node further includes a processor configured to store the service parameters in an integrated data repository (UDR) of the first wireless communication network.

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

[0082] A method is further provided for a network node in a first wireless communication network. The network nodes may be NEF132, 152, 232, and 932. The network nodes may include network node 400 as described with reference to Figure 4. The method comprises the step of receiving a request from an application function (AF) in a second wireless communication network, the request comprising service parameters that identify both the first application and the second wireless communication network. The method further comprises the step of storing the service parameters in an integrated data repository (UDR) of the first wireless communication network.

[0083] Further network nodes in the first wireless communication network are provided. The network nodes may be PCF126, 146, 226, and / or 926 as described herein. The network nodes may include network node 400 as described with reference to Figure 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 route selection policy rule determination from application functions in the second wireless communication network. The processor is configured to construct route selection policy rules using the application guidance, the route selection policy rules comprising an application descriptor and a route selection descriptor comprising network identification information, the network identification information identifying the second wireless communication network, and the route selection policy rules defining the route for application traffic when a user device is registered in the second wireless communication network. The transmitter is configured to transmit the route selection policy rules to the user device.

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

[0085] By receiving application guidance in route selection policy rule determination from application functions within the second wireless communication network, a network node can create a route selection policy rule having a route selection descriptor containing the network identification information of the second wireless communication network. Such a route selection policy rule is then transmitted to the user device, and as a result, the first wireless communication network can configure route selection according to the identification information of the network to which the user device will register. For example, if the network identification information of the route selection descriptor matches the network identification information of the wireless communication network to which the user device will register, the route selection policy rule will be applied to the application traffic. In the above example, the rule is set for the second wireless communication network to which the user device may roam. If the user device roams to and registers with the second wireless communication network, the route selection policy rule containing the network identification information of the second network will be applied to the application traffic that matches the route selection policy rule.

[0086] The application guide may include validity conditions. The validity conditions may comprise at least one of the following: identification information for a second wireless communication network, multiple identification information for wireless communication networks, or identification information for an application.

[0087] Route selection policy rules may define the route for application traffic when a user device is registered in any wireless communication network that has identification information consistent with one of several identification information for the wireless communication network.

[0088] The transmitter may be further configured to send route selection policy rules to the user device. The route selection policy rules may be sent to the user device when the user device registers with the first wireless communication network.

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

[0090] The processor may be further configured to determine routes for application traffic within a second wireless communication network from service parameters. The processor may construct route selection policy rules from the service parameters according to the determined routes. The updated service parameters may be for UEs, for groups of UEs, or for S-NSSAI / DNAI combinations.

[0091] Figure 7 shows Method 700 for a network node in a first wireless communication network. The network node may be PCF126, 146, 226, 400, and / or 926 as described herein. Method 700 comprises the step (710) of receiving application guidance in route selection policy rule determination from an application function in a second wireless communication network. Method 700 further comprises the step (720) of constructing a route selection policy rule using the application guidance. The route selection policy rule includes an application descriptor and a route selection descriptor having network identification information, the network identification information identifying the second wireless communication network, and the route selection policy rule defines a route for application traffic when a user device is registered in the second wireless communication network. Method further comprises the step (730) of transmitting the route selection policy rule to the user device.

[0092] By receiving application guidance in route selection policy rule determination from application functions within a second wireless communication network, a network node can create a route selection policy rule having a route selection descriptor containing the network identification information of the second wireless communication network. Such a route selection policy rule is then transmitted to the user device, and as a result, the first wireless communication network can configure route selection according to the identification information of the network to which the user device will register. For example, if the network identification information of the route selection descriptor matches the network identification information of the wireless communication network to which the user device will register, the route selection policy rule will be applied to the application traffic. In the above example, the rule is set for the second wireless communication network to which the user device may roam. If the user device roams to and registers with the second wireless communication network, the route selection policy rule with the network identification information of the second network will be applied to the application traffic that matches the route selection policy rule.

[0093] Further network nodes in a second wireless communication network are provided. The network nodes may comprise AF134, 154, 234, and / or 954 as described herein. The network nodes may comprise network node 400 as described with reference to Figure 4, and comprising a processor 405, a receiver 435, and a transmitter 430. The network node comprises a transmitter configured to send application guidance in route selection policy rule determination to a policy control function in the first wireless communication network.

[0094] Network nodes in the second wireless communication network may be configured to send application guidance for route selection policy rule determination to the policy control function in the first wireless communication network via the network exposure function (NEF) in the first wireless communication network.

[0095] By sending application guidance in route selection policy rule determination from an application function in the second wireless communication network, a network node can inform a policy control function in the first wireless communication network that when a user device roams to the second wireless communication network, that policy control function should create a route selection policy rule for specific application traffic. After creation, such a route selection policy rule may then be sent to the user device, and as a result, the first wireless communication network can configure route selection according to the identification information of the network to which the user device is registered. For example, if the network identification information of the route selection descriptor matches the network identification information of the wireless communication network to which the user device is registered, the route selection policy rule will be applied to the application traffic. In the above example, the rule is set for the second wireless communication network to which the user device may roam. If the user device roams to and registers with the second wireless communication network, the route selection policy rule with the network identification information of the second network will be applied to application traffic that matches the route selection policy rule, according to the application guidance sent in route selection policy rule determination.

[0096] The application guide may include validity conditions. The validity conditions comprise at least one of the following: identification information for a second wireless communication network, multiple identification information for wireless communication networks, and / or identification information for an application.

[0097] Route selection policy rules may define the route for application traffic when a user device is registered in any wireless communication network that has identification information consistent with one of several identification information for the wireless communication network.

[0098] When a network node determines that it wants to route traffic to a second wireless communication network, it may be triggered to send application guidance in route selection policy rule determination. Such a decision may be made when a particular class of application traffic exceeds a certain threshold.

[0099] A network node may also be an application function. An application function may be an application function within a PLMN other than the user's home PLMN.

[0100] Figure 8 shows method 800 of a network node in a second wireless communication network. The network node may include AF134, 154, 234, 400, and / or 954 as described herein. Method 800 includes the step (810) of sending application guidance in route selection policy rule determination to a policy control function in the first wireless communication network.

[0101] By sending application guidance in route selection policy rule determination from an application function in the second wireless communication network, a network node can inform a policy control function in the first wireless communication network that when a user device roams to the second wireless communication network, that policy control function should create a route selection policy rule for specific application traffic. After creation, such a route selection policy rule may then be sent to the user device, and as a result, the first wireless communication network can configure route selection according to the identification information of the network to which the user device is registered. For example, if the network identification information of the route selection descriptor matches the network identification information of the wireless communication network to which the user device is registered, the route selection policy rule will be applied to the application traffic. In the above example, the rule is set for the second wireless communication network to which the user device may roam. If the user device roams to and registers with the second wireless communication network, the route selection policy rule with the network identification information of the second network will be applied to application traffic that matches the route selection policy rule, according to the application guidance sent in route selection policy rule determination.

[0102] Further network nodes are provided within the first wireless communication network. The network nodes may be NEF132, 152, 232, and 932. The network nodes may include network node 400, as described with reference to Figure 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 requests from application functions (AFs) within the second wireless communication network, the requests comprising service parameters that identify both the first application and the second wireless communication network. The processor is configured to store the service parameters in an integrated data repository (UDR) of the first wireless communication network.

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

[0104] A method for a network node in a first wireless communication network is further provided. The method comprises the step of receiving a request from an application function (AF) in a second wireless communication network, the request comprising service parameters that identify both the first application and the second wireless communication network. The processor is configured to store the service parameters in an integrated data repository (UDR) of the first wireless communication network. The network node may also 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 a VPLMN requires specific processing of UE application traffic. The AF in the visited PLMN (or a different PLMN) provides service information by reusing the service-specific information provisioning procedure described in 3GPP TS23.502 v17.3.0, with the difference that the AF includes indications for applying this rule only to UEs targeted within that particular PLMN.

[0106] The trigger for an AF request may stem from the VPLMN's AF service provider wanting to use specific DNN / S-NSSAI processing for a roaming UE. Additionally or alternatively, the trigger may be provided by a network slice capability enabler server as defined in 3GPP TS25.434 v16.0.0. The NSCE server may be located in the AF. The NSCE server may receive network / slice notification remappings for applications from NSCE clients (located in the UE) based on the configuration provided by the NSCE server to the NSCE clients within the UE.

[0107] NEF stores the AF request information in the UDR within the "Application Data" field in the service-specific information data subset, along with the assigned transaction reference ID (provided by AF).

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

[0109] [Table 1A]

[0110] [Table 1B]

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

[0112] Figure 9 is a signaling diagram showing the procedure for a VPLMN to act on URSP rules for a UE roaming from a different PLMN. UE910 communicates with home PLMN920. Home PLMN920 comprises PCF926, UDM928, UDR930, and NEF932. Visited PLMN (VPLMN) comprises Visited AF (V-AF)954 and Visited PCF (V-PCF)946.

[0113] In 971, an AF within the VPLMN is triggered to request the UE's home PLMN to perform a specific action of routing traffic to the VPLMN.

[0114] In 972, the NEF includes the updated service information in the request, and the AF invokes the service operation. The updated information includes validity conditions for applying the URSP rule within a specific 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 is applicable to any UE, or the AF may include the UE's domain information and / or external identifiers.

[0115] In step 973, NEF932 sends an authorization request to UDM928 via the Nudm_ServiceSpecificAuthorization_Create Request message. In step 974, UDM928 authorizes the request. In step 975, the UDM sends the authorization to NEF932 via the Nudm_ServeSpecificAuthorization_Create Response message. Steps 973-975 may be performed in accordance with 3GPP TS23.502 v17.3.0.

[0116] In 976, in response to successful authorization, NEF932 updates the data in UDR930 by including the updated service information within the application data. NEF932 invokes a Nudr_DM_Create (or Update) service request, which requests UDR930 to store the service information in the “Application Data” dataset within the service-specific information data subset identifier. NEF932 may also include a data key indicating the target UE or group of UEs. In one embodiment, the service information is stored within an existing service information parameter, including the S-NSSAI or DNN of the service information as a data key (if the request is for any UE).

[0117] In 977, UDR930 acknowledges the NEF request.

[0118] In step 978, NEF932 acknowledges the AF request.

[0119] In 979, if PCF926 is subscribed to service-specific information, UDR930 notifies PCF926 of the updated service information.

[0120] In 980, when UE910 registers with HPLMN920 (or VPLMN), UE910 may include a list of Public Service Identities (PSIs). PCF926 includes the list of PSIs related to HPLMN920 in its request, and AMF (in HPLMN) or V-PCF946 (in VPLMN) (as illustrated in Figure 9) initiates a UE910 policy association creation request.

[0121] In 981, PCF926 retrieves application data subscription information from UDR930.

[0122] In 982, PCF926 creates updated URSP rules, including URSP rules with validity conditions for each PLMN, according to the information stored in UDR930.

[0123] In 983, PCF926 delivers the updated URSP rules to UE910 by initiating a UE configuration update for transparent policy delivery (via V-PCF946 if the UE is roaming) in order to deliver the updated URSP rules to UE910.

[0124] In 984, UE910 acknowledges the successful implementation of the rule.

[0125] In 985, if V-AF954 is subscribed to the notification of successful policy delivery, PCF926 notifies UDM928.

[0126] In step 986, UDM928 notifies NEF932 of the successful policy delivery. In step 987, NEF932 acknowledges this.

[0127] In step 988, NEF932 notifies V-AF954 of the successful policy distribution. In step 989, V-AF954 responds with an acknowledgment.

[0128] Upon receiving a URSP rule that includes PLMN validity conditions, UE910 enforces the URSP rule as follows: When the UE finds that application traffic matches a traffic descriptor in a URSP rule, the UE checks the list of route selection descriptors for the matched URSP rule. If an RSD in the list of RSDs includes a PLMN validity condition, the UE checks whether the PLMN identification information within the validity condition matches the PLMN identification information of the registered PLMN or a PLMN equivalent to the registered PLMN. If consistent, the UE considers the RSD valid and routes application traffic according to the contents of the route selection descriptor. If there is no alignment, the UE considers the RSD invalid and proceeds to process a second RSD from the list of aligned URSP rule RSDs, if available. If other RSDs are inconsistent, the UE will consider the URSP rules to be inconsistent and will process different URSP rules.

[0129] Currently, URSP rules are provided only by HPLMNs, and UEs apply the same URSP rules in any PLMN to which they register. This creates problems when a UE is roaming and a VPLMN operator may require specific traffic routing processing for specific applications that are different from those required by the HPLMN.

[0130] As part of the Release 18 work, 3GPP SA2 identifies how V-PLMNs can act on H-PLMNs to create and provision URSP rules. This specification provides solutions that help enable HPLMNs to identify when specific URSP rules are required within a VPLMN. This specification also provides solutions that help specify how URSP rules are structured to enable UEs to decide when URSP rules should be applied within a particular VPLMN.

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

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

[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] Further provided is a Network Exposure Function (NEF) in the first mobile communication network, which receives a request from an Application Function (AF) that provides service parameters for a first application, the service parameters comprising a first indication that the service parameters will be applied in a second mobile communication network, and stores the service parameters in an Integrated Data Repository (UDR) in the first mobile communication network, the stored service parameters being applied by a Policy Control Function (PCF) in the first mobile communication network to create URSP rules, the URSP rules indicating how the traffic of the first application will be routed by the remote unit once the remote unit is registered in the second mobile communication network. The first indication may be a VPLMN-ID.

[0135] A policy control function (PCF) is further provided within the first mobile communication network, which is configured to receive notifications from the UDR of updated service-specific information for UEs, groups of UEs, or S-NSSAI / DNAI combinations, determine specific processing of application traffic routing within the second mobile communication network from the service-specific information, and construct URSP rules containing validity conditions within the route selection descriptor to apply the contents of the route selection descriptor when a device is registered in the second mobile communication network.

[0136] A UE in a first mobile communication network is further provided, configured to receive URSP rules from a second mobile communication network, detect application traffic that matches the application descriptor in the URSP rule, determine that the route selection descriptor in the matched URSP rule includes a validity condition for a PLMN, and determine that the PLMN identifier in the validity condition matches the PLMN identification information of the first mobile communication network, and then apply the route selection descriptor components of the matched URSP rule.

[0137] It should be noted that the methods and apparatus described above are illustrative rather than limiting to the present invention, and that many alternative configurations can be designed by those skilled in the art without departing from the scope of the appended claims. The word “equipped with” does not exclude the presence of elements or steps other than those enumerated in the claims, and “a” or “an” does not exclude plural, and a single processor or other unit may implement the functions of several units described in the claims. Any reference numerals in the claims shall not be construed as limiting their scope.

[0138] Furthermore, although examples are given in the context of specific communication standards, these examples are not intended to limit the communication standards to which the disclosed methods and apparatus may be applied. For example, while 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 method 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 similar, causes the processor to execute the method described above.

[0140] The methods and apparatus described may be practiced in other specific forms. The methods and apparatus described should be considered illustrative and not restrictive in all respects. Therefore, the scope of the invention is indicated not by the above description but by the appended claims. All modifications that fall within the equivalent meaning and scope of the claims should be encompassed within those scopes. [Explanation of symbols]

[0141] 110 User Equipment (UE) 120 HPLMN 122 Wireless Access Network (RAN) 124 Application Management Function (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 154 AF 190 Internet 200 Remote Units 210 UE 220 HPLMN 226 PCF 228 UDM 232 NEF 234 AF 300 User Equipment 305 Processor 310 memory 315 Input Devices 320 Output Devices 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interfaces 345 Application Interfaces 400 network nodes 405 Processor 410 memory 415 Input Devices 420 Output Devices 425 Transceiver 430 Transmitter 435 Receiver 440 Network Interfaces 445 Application Interfaces 510 UE 910 UE 920 Home PLMN 926 PCF 928 UDM 930 UDR 932 NEF 946 Visited PCF (V-PCF) 954 Destination AF (V-AF)

Claims

1. A network node in a first wireless communication network having a network exposure function (NEF), At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor is connected to the network node. Receiving application guidance in route selection policy rule determination from an application function in the second wireless communication network via the NEF, Constructing a route selection policy rule using the aforementioned application guidance, wherein the route selection policy rule includes an application descriptor and a route selection descriptor having network identification information that identifies the second wireless communication network, and the route selection policy rule defines a route for application data traffic when user equipment (UE) is registered in the second wireless communication network. Sending the aforementioned route selection policy rules to the aforementioned UE, It is configured to perform the following: The aforementioned application guidance includes validity conditions that at least include application identification information. Network node.

2. The validity condition comprises at least one of the identification information of the second wireless communication network, or a plurality of identification information of the wireless communication network. The network node according to claim 1.

3. The aforementioned network node is a policy control function. The network node according to claim 1.

4. The at least one processor is configured to cause the network node to receive notifications of service parameters from the Unified Data Repository (UDR) in the first wireless communication network. The network node according to claim 1.

5. The at least one processor is configured to cause the network node to determine the route for the application data traffic in the second wireless communication network from the service parameters. The network node according to claim 4.

6. The at least one processor is configured to cause the network node to construct the route selection policy rules from the service parameters according to the determined route. The network node according to claim 5.

7. A network node in a second wireless communication network, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor is connected to the network node. The system is configured to transmit application guidance for route selection policy rule determination to a policy control function within the first wireless communication network via a network exposure function (NEF) within the first wireless communication network. The aforementioned application guidance includes validity conditions that at least include application identification information. Network node.

8. The aforementioned effectiveness conditions are, Identification information of the second wireless communication network, or Multiple identification information for wireless communication networks It comprises at least one of the following: The network node according to claim 7.

9. When a user device-specific process is determined for routing traffic to the second wireless communication network, it is triggered to send application guidance in route selection policy rule determination. The network node according to claim 6.

10. The aforementioned network node is an application function. The network node according to claim 9.

11. A method performed by a network node in a second wireless communication network, The process includes the step of transmitting application guidance in route selection policy rule determination to a policy control function in the first wireless communication network via a network exposure function (NEF) in the first wireless communication network, The aforementioned application guidance includes validity conditions that at least include application identification information. method.

12. The validity condition comprises at least one of the identification information of the second wireless communication network, or a plurality of identification information of the wireless communication network. The method according to claim 11.

13. When the network node determines user device-specific processing for routing traffic to the second wireless communication network, it is triggered to send application guidance in route selection policy rule determination. The method according to claim 11.

14. The aforementioned network node is an application function. The method according to claim 11.

15. A processor for wireless communication, It comprises at least one controller coupled to at least one memory, and the at least one controller provides the processor with The system is configured to transmit application guidance for route selection policy rule determination to a policy control function within the first wireless communication network via a network exposure function (NEF) within the first wireless communication network. The aforementioned application guidance includes validity conditions that at least include application identification information. Processor.

16. The aforementioned effectiveness conditions are, The system comprises identification information for a second wireless communication network, or at least one of a plurality of identification information for wireless communication networks. The processor according to claim 15.

17. When a user device determines how to route traffic to a second wireless communication network, it triggers the sending of application guidance in route selection policy rule determination. The processor according to claim 15.

18. The network node is equipped with the processor, and the network node is an application function. The processor according to claim 15.

Images