Network mapping of policy sections in wireless communication networks

Abstract

A method is provided for a first network function of a first wireless communication network, comprising the steps of determining a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and the policy configuration is placed in a separate policy section identified by a unique policy section identifier; and transmitting the policy configuration to a second network function of the first wireless communication network.

Description

Technical Field

[0001] The subject matter disclosed in this specification generally relates to the field of implementing network mapping of policy sections in wireless communication networks. This document defines a first network function, a method in the first network function, a wireless communication device, and a method in the wireless communication device.

Background Art

[0002] Since Release 15, UE Route Selection Policy (URSP) rules have been defined to enable a UE to determine how to route application traffic over a mobile communication network either via 3GPP access (where "3GPP" is a registered trademark) via untrusted WLAN access or trusted WLAN access or via non-3GPP access or how to route traffic that non-seamlessly bypasses the mobile communication network via a WLAN connection. The URSP rules include traffic descriptors that enable the UE to determine whether the URSP rules match the application traffic that the UE is currently handling in the uplink and / or downlink. The traffic descriptors can include application descriptors (OSID / OSAppID) and IP flow descriptors. The IP flow descriptor can be, for example, the target address of the application traffic, the DNN requested by the application, or the connection capabilities requested by the application (e.g., IMS connection).

[0003] Each URSP rule includes a Route Selection Descriptor (RSD) that defines how the UE should route PDU sessions. The RSD includes one or more of the following: SSC mode selection, network slice selection, DNN selection, PDU session type selection, non-seamless offload instruction, and access type preference. The UE routes traffic through PDU sessions that conform to the RSD components. Routes can include both 3GPP and non-3GPP access.

[0004] Currently, URSP rules are only provided to the UE from the home PLMN's PCF (i.e., H-PCF). The UE uses the provisioned URSP rules in any PLMN it may register in, and for example, when the UE is roaming to a visited PLMN, the UE applies the same URSP rules in the visited PLMN as they would be provisioned by the home PLMN. However, traditionally, the home PLMN issues URSP rules appropriate for the traffic on the home PLMN, without considering any visited PLMNs the UE may use. When the UE is roaming, the PCF in the V-PLMN (i.e., V-PCF) is not allowed to create / provision URSP rules, but it is allowed to create / provision ANDSP (Access Network Discovery and Selection Policy) rules. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 23.502 v18.0.0 [Non-Patent Document 2] 3GPP TS 23.503 v18.0.0 [Non-Patent Document 3] 3GPP TS 24.501 v18.1.0 [Overview of the project] [Means for solving the problem]

[0006] In traditional wireless communication networks, URSP rules are provided only by the H-PLMN, and the UE applies the same URSP rules in any PLMN the UE registers with. This creates problems when the UE is roaming, as the V-PLMN operator may require specific traffic routing for specific applications. In addition, there are scenarios where the V-PLMN operator cannot interface with the H-PLMN (for example, when the UE registers in the SNPN using credentials from the H-PLMN).

[0007] Disclosed herein is a procedure for network mapping of policy sections in a wireless communication network. The procedure may be implemented by a first network function, a method in the first network function, a wireless communication device, and a method in the wireless communication device.

[0008] Accordingly, a first network function of a first wireless communication network is provided, comprising a processor and memory coupled to the processor. The processor is configured to cause the first network function to determine a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and to include the policy configuration in a separate policy section identified by a unique policy section identifier, and to transmit the policy configuration to the second network function of the first wireless communication network.

[0009] Therefore, the first wireless communication network can indicate to wireless communication devices which wireless communication devices can use policies issued from the first wireless communication network. This can be facilitated by providing a mapping of policy sections to wireless communication network identities.

[0010] A method in a first network function of a first wireless communication network is further provided, comprising the steps of determining a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and the policy configuration is placed in a separate policy section identified by a unique policy section identifier; and transmitting the policy configuration to a second network function of the first wireless communication network.

[0011] A wireless communication device is further provided, comprising a processor and memory coupled to the processor. The processor is configured to cause the wireless communication device to send a registration request to a wireless communication network, the registration request comprising a policy container which includes instructions that the wireless communication device may apply different policies in different wireless communication networks.

[0012] A method in a wireless communication device is further provided, comprising the step of sending a registration request to a wireless communication network, wherein the registration request includes a policy container that includes instructions indicating that the wireless communication device may apply different policies in different wireless communication networks.

[0013] To illustrate how the advantages and features of this disclosure can be obtained, the description of this disclosure is made by reference to the specific apparatus and methods shown in the accompanying drawings. Each of these drawings illustrates only a particular aspect of this disclosure and should not be considered to limit its scope. The drawings may be simplified for clarity and are not necessarily drawn to scale.

[0014] Next, a method and apparatus for network mapping of policy sections in a wireless communication network will be described, simply as an example, with reference to the attached drawings. [Brief explanation of the drawing]

[0015] [Figure 1] This figure illustrates one embodiment of a wireless communication system for network mapping of policy sections in a wireless communication network. [Figure 2] This figure illustrates user equipment that may be used to implement the methods described herein. [Figure 3] This figure illustrates further details of network nodes that may be used to implement the methods described herein. [Figure 4] This figure shows a revised version of the class mark. [Figure 5] This diagram shows the method for delivering the policy section - PLMN configuration mapping to the UE. [Figure 6] This figure shows a method in the first network function of the first wireless communication network. [Figure 7] This diagram shows a method in a wireless communication device. [Modes for carrying out the invention]

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

[0017] For example, the disclosed methods and apparatuses may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, logic chips, off-the-shelf semiconductors such as transistors, or other discrete components. The disclosed methods and apparatuses 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 apparatuses may include one or more physical or logical blocks of executable code that may be compiled, for example, as objects, procedures, or functions.

[0018] Furthermore, the methods and apparatuses may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain configurations, the storage device may merely employ a signal for accessing the code.

[0019] Any combination of one or more computer-readable media may be utilized. The computer-readable media may be a computer-readable storage media. The computer-readable storage media may be a storage device storing 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 foregoing.

[0020] More specific examples (a non-exhaustive list) of a memory device include, for example, 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), portable compact disk 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 document, a computer-readable storage medium can 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.

[0021] Throughout this specification, reference to a particular method or apparatus, or an example of similar wording, means 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 in this specification. Accordingly, all references to features of a particular method or apparatus, or an example of similar wording, while not necessarily all referring to the same example, may, but not necessarily, refer to the same example, and mean, unless otherwise specified, “one or more, but not all, examples”. The terms “including”, “comprising”, “having” and their variants mean, unless otherwise specified, “including but not limited to”. An enumerated list of items does not imply that any or all of the items are mutually exclusive, unless otherwise specified. Unless otherwise specified, the terms “a”, “an”, and “the” also refer to “one or more”.

[0022] As used herein, a list with the conjunction "and / or" includes any single item in the list or any combination of items in the 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 the list or any combination of items in the 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 exactly one of any single items in the list. For example, "one of A, B and C" includes A only, B only, or C only, and excludes the combination of A, B and C. As used herein, “members selected from the group consisting of A, B, and C” includes only one of A, B, or C, and excludes any combination of A, B, and C. As used herein, “members selected from the group consisting of A, B, and C and any combination 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.

[0023] Furthermore, the features, structures, or properties described herein can be combined in any suitable manner. The following description provides numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, in order to give a full understanding of the disclosure. However, those skilled in the art will recognize that the disclosed methods and apparatus can be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

[0024] The embodiments of the disclosed methods and apparatus are described below with reference to schematic flowcharts and / or schematic block diagrams of the methods, apparatus, systems, and program products. It should be understood that each block in the schematic flowcharts and / or schematic block diagrams, as well as any combination 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 dedicated computer, or other programmable data processing device to create a machine, and as a result, instructions executed via the computer or other programmable data processing device processor create means for implementing the functions / actions specified in the schematic flowcharts and / or schematic block diagrams.

[0025] Code that can instruct a computer, other programmable data processing device, or other device to function in a particular way may also be stored in a storage device, and as a result, the instructions stored in the storage device produce a product containing instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0026] The code can also be loaded onto a computer, other programmable data processing device, or other device to perform a series of operational steps on the computer, other programmable device, or other device to create a process executed by the computer, and as a result, the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0027] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, a segment, or a portion of code containing one or more executable instructions for implementing a specified logical function.

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

[0029] The descriptions of elements in each figure may refer to elements in preceding figures. Similar numbers refer to the same elements in all figures.

[0030] Figure 1 illustrates one embodiment of a wireless communication system 100 for network mapping of policy sections in a wireless communication network. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Although a specific number of remote units 102 and network units 104 are illustrated in Figure 1, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100. The wireless communication system may comprise a wireless communication network and at least one wireless communication device. The wireless communication device is typically a 3GPP user equipment (UE). The wireless communication network may comprise at least one network node. The network node may be a network unit.

[0031] In one embodiment, the remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., Internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, and drones. In some embodiments, the remote unit 102 includes wearable devices such as smartwatches, fitness bands, and optical head-mounted displays. Furthermore, the remote unit 102 may be referred to as a subscriber unit, mobile, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote unit 102 may communicate directly with other remote units 102 via side-link communication.

[0032] The network unit 104 may be distributed across geographical areas. In certain embodiments, the network unit 104 may include access points, access terminals, bases, base stations, node B, eNB, gNB, home node B, relay nodes, devices, core network, airborne servers, radio access nodes, APs, NRs, network entities, access and mobility management functions ("AMF"), integrated data management functions ("UDM"), integrated data repository ("UDR"), UDM / UDR, policy management functions ("PCF"), radio access network ("RAN"), network slice selection functions ("NSSF"), operation, administration and management ("OAM"), session management functions ("SMF"), and user plane functions ("UPF"). These may be referred to as application functions, authentication server functions ("AUSF"), security anchor functions ("SEAF"), trusted non-3GPP gateway functions ("TNGF"), application functions, service enabler architecture layer ("SEAL") functions, vertical application enabler server, edge enabler server, edge configuration server, mobile edge computing platform functions, mobile edge computing applications, application data analysis enabler server, SEAL data distribution server, middleware entities, network slice capability management server, or by any other terminology used in the art. Network unit 104 is generally part of a radio access network that includes one or more controllers commutably coupled to one or more corresponding network units 104. A radio access network is generally commutably coupled to one or more core networks, and one or more core networks may be coupled to other networks, among many others, such as the Internet and public switched telephone networks. These and other elements of radio access networks and core networks are not shown but are generally well known to those skilled in the art.

[0033] In one implementation, the wireless communication system 100 conforms to the New Radio (NR) protocol standardized by 3GPP, with the network unit 104 transmitting on the downlink (DL) using orthogonal frequency division multiplexing ("OFDM") modulation, and the remote unit 102 transmitting on the uplink (UL) using either single-carrier frequency division multiple access ("SC-FDMA") or OFDM. However, more generally, the wireless communication system 100 may implement any other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variant, GSM, GPRS, UMTS, LTE variant, CDMA2000, Bluetooth®, ZigBee, Sigfox, or LoraWAN. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0034] The network unit 104 can serve several remote units 102 within a serving area, for example, a cell or cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, frequency domain, and / or spatial domain.

[0035] Figure 2 illustrates a user device 200 that may be used to implement the methods described herein. The user device 200 is used to implement one or more of the solutions described herein. The user device 200 conforms to one or more of the user devices described in the embodiments described herein. Specifically, the user device 200 may include a wireless communication device as described herein. The user device 200 may include a UE510 as described herein. The user device 200 includes a processor 205, memory 210, input device 215, output device 220, and transceiver 225.

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

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

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

[0039] The processor 205 can control the user device 200 to implement the behavior of the user device described herein. The processor 205 may include an application processor (also known as the “main processor”) that manages application domain and operating system (“OS”) functions, and a baseband processor (also known as the “baseband radio processor”) that manages radio functions.

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

[0041] Memory 210 may store data related to implementing traffic category fields, as described herein. Memory 210 may also store program code and related data, such as an operating system or other controller algorithms running on device 200.

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

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

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

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

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

[0047] A first transmitter / receiver pair used to communicate with a mobile communication network via a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network via an unlicensed radio spectrum may be combined into a single transceiver unit, for example, a single chip that performs functions for use with both licensed and unlicensed radio spectra. The first and second transmitter / receiver pairs may share one or more hardware components. For example, a particular transceiver 225, transmitter 230, and receiver 235 may be implemented as physically separate components that access shared hardware and / or software resources, such as a network interface 240.

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

[0049] Figure 3 illustrates further details of a network node 300 that may be used to implement the method described herein. The network node 300 may be an implementation of one entity in a wireless communication network, for example, in one or more of the wireless communication networks described herein. The network node 300 may have a first network function as described herein. The network node 300 may have a policy control function 530 as described herein. The network node 300 includes a processor 305, memory 310, input device 315, output device 320, and transceiver 325.

[0050] The input device 315 and output device 320 may be combined into a single device such as a touchscreen. In some implementations, the network node 300 does not include any input device 315 and / or output device 320. The network node 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.

[0051] As illustrated, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335, where the transceiver 325 communicates with one or more remote units 200. 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, N2, and N3. Other network interfaces 340 may be supported, as will be understood by those skilled in the art.

[0052] The processor 305 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 305 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. The processor 305 may execute instructions stored in 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.

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

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

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

[0056] 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 capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD, LED display, OLED display, projector, or similar display device capable of outputting images, text, etc., to a user. As another non-limiting example, the output device 320 may include a wearable display, such as a smartwatch, smart glasses, or head-up display, that is detached from the rest of the network node 300 but communicatively coupled to it. Furthermore, the output device 320 may be a component of a smartphone, personal digital assistant, television, tablet computer, notebook (laptop) computer, personal computer, or vehicle dashboard.

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

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

[0059] Since Release 15, UE Route Selection Policy (URSP) rules have been defined to allow UEs to decide how to route application traffic through the mobile communications network via untrusted WLAN access, trusted WLAN access via 3GPP access, or non-3GPP access, or how to route traffic that non-seamlessly bypasses the mobile communications network via WLAN connections. URSP rules and procedures for UEs to apply URSP rules are described in 3GPP TS 23.502 v18.0.0 (December 2022), titled "Procedures for the 5G System (5GS)," and 3GPP TS 23.503 v18.0.0 (December 2022), titled "Policy and charging control framework for the 5G System (5GS); Stage 2" (the definition and procedures for URSP rules are included in versions 15.0.0 and later of 23.502 and 23.503).

[0060] A URSP rule includes a traffic descriptor that allows the UE to determine whether the URSP rule is suitable for the application traffic currently being handled by the UE on the uplink and / or downlink. The traffic descriptor may include an application descriptor (OSID / OSAppID) and an IP flow descriptor. The IP flow descriptor may be, for example, the target address of the application traffic, the DNN requested by the application, or the connectivity capability requested by the application (e.g., IMS connectivity).

[0061] Each URSP rule includes a route selection descriptor that defines how the UE should route PDU sessions. The RSD includes one or more of the following: SSC mode selection, network slice selection, DNN selection, PDU session type selection, non-seamless offload instruction, and access type preference. The UE routes traffic through PDU sessions that conform to the RSD components. Routes can include both 3GPP and non-3GPP access.

[0062] Currently, URSP rules are only provided to the UE from the home PLMN's PCF (i.e., H-PCF). The UE uses the provisioned URSP rules in any PLMN it may register in, and for example, when the UE is roaming to a visited PLMN, the UE applies the same URSP rules in the visited PLMN as they would be provisioned by the home PLMN. However, traditionally, the home PLMN issues URSP rules appropriate for the traffic on the home PLMN, without considering any visited PLMNs the UE may use. When the UE is roaming, the PCF in the V-PLMN (i.e., V-PCF) is not allowed to create / provision URSP rules, but it is allowed to create / provision ANDSP (Access Network Discovery and Selection Policy) rules.

[0063] H-PCF provisions URSP and / or ANDSP policies to the UE within the UE policy information provided to the UE via NAS signaling. H-PCF allocates URSP and ANDSP rules within policy sections in the UE policy information, and each policy section is identified by a specific policy section identifier. H-PCF stores the policy sections and policy section identifiers in a database used as a means for H-PCF to determine whether the UE requires the updated policy. When a UE registers with PLMN, the UE includes in the registration request the policy section identifier associated with the policy section stored in the UE, which enables PCF (in both VPLMN and HPLMN) to determine whether the updated policy is required in the UE.

[0064] As part of the Release 18 work in the eUEPO work item, it has been agreed to enable a solution that allows the network to tell the UE which URSP rules are applicable when the UE is roaming to a V-PLMN. This is supported by a home network (i.e., H-PCF) that provides a mapping of policy section identifiers to a list of one or more V-PLMN identifiers. When a UE registers with a V-PLMN, the UE uses its policies for that V-PLMN with higher priority than other URSP rules.

[0065] Improvements to the operation of wireless communication networks are provided herein, thereby, • PCF knows the mapping of policy section identifiers to PLMN identifiers for each UE. • The mapping of policy section identifiers to PLMN identifiers is encoded within the provisioned UE policy.

[0066] 3GPP TS 23.503 v18.0.0 (December 2022), titled "Policy and charging control framework for the 5G System (5GS); Stage 2," states that a PCF may provide a mapping of policy section identifiers to PLMN IDs. Such a PCF may provide the UE with a tuple (PLMN ID, a list of PSIs associated with the PLMN ID) and a policy section containing URSP rules. However, the standard does not provide details on how a PCF may encode the tuple or how this tuple may be provided.

[0067] Tuples are provided herein, contained within separate, independent policy sections. Each tuple includes a PLMN ID and a list of PSIs associated with that PLMN ID.

[0068] The solutions presented herein involve mapping policy section identifiers (or PSIs) to V-PLMNs within policy sections in policies provisioned to the UE. For simplicity, such policies may be defined herein as "Policy Section Configuration by PLMN" policies.

[0069] Such a policy section is configured to indicate that its content includes a PLMN-specific policy section configuration policy. The policy section may identify the route selection policy and the wireless communication network to which the policy section should apply. The UE policy section type, defined in Table D.6.2.7 of 3GPP TS 24.501 v18.1.0 (January 2023) titled "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3", defines the policy type. Such a UE policy section is shown in Table 1 below and is modified to include a new binary encoding for identifying the "PLMN-specific policy section configuration" rule (PPPSC rule), highlighted in bold and italicized text.

[0070] [Table 1]

[0071] The policy sections described herein include the following information, namely: • UE Route Selection Policy (URSP) rules, • Access Network Discovery and Selection Policy (ANDSP) rules (including SSIDs applicable to each PLMN), • V2X policy (V2XP) rules, • ProSe policy (ProSeP) rules, and / or • A "Policy Section Configuration by PLMN" that includes mapping policy section identifiers to PLMN identifiers (as described herein). It may include one or more of these.

[0072] PCF can ensure that each policy section contains one type of rule, namely URSP rules, ANDSP, V2X, ProSe policies, or PLMN-specific policy section configurations.

[0073] The Policy Section Configuration by Policy Section MN (PPPSC) contains a list of PLMNs to which the UE should apply rules within the policy section, for each policy section identifier (PSI). The PCF ensures that the policy section identifiers (PSIs) in that list are part of the policy section identifiers associated with the policy section provisioned to the UE.

[0074] When a PCF provides a PLMN-specific policy section configuration (PPPSC), the PCF includes such policies in the policy section identified by a specific PSI. The PCF may store the PSI in the UDR within the policy set entry data identified by the UE's SUPI, ensuring that each time the UE registers in the PLMN, this UE always has a consistent PLMN-specific policy section configuration (PPPSC). For example, if all stored UE policies are deleted in the UE (e.g., due to the UE being switched on / off), during initial registration to the PLMN, the UE will not include in its registration request any PSI that would allow the PCF to determine, based on the registration request and the information stored in the UDR that the UE needs to be provisioned with its UE policies (including the PPPSC). The policies provisioned to the UE are based on the information stored in the UDR.

[0075] When a UE receives a PLMN-specific policy section configuration (PPPSC) as part of a UE policy sent to the UE by a PCF, the UE constrains the priority list of policy sections for each PLMN based on the policy section identifiers in the PLMN-specific policy section configuration. When a UE registers with a particular PLMN, route selection policy rules identified as specific to that particular PLMN are applied by the UE with higher priority than route selection policy rules not identified as such.

[0076] To facilitate the implementation of PLMN-specific policy section configuration rules, the UE may be configured to support receiving and applying such rules as indicated in the PCF. When the UE registers with a 5G network, the UE may indicate support for receiving PLMN-specific policy section configurations (PPSCs). For example, the UE may include the ability to configure PLMN-specific policy section configurations within the policy container in its initial registration request.

[0077] When a UE sends a UE status instruction message in a registration request, the UE may include an instruction within the UE policy class mark information element indicating that it supports PPPSC rules during initial registration. The traditional UE policy class mark is described in clause D.6.5.1 of 3GPP TS 24.501. A modified version of this class mark 400 is shown in Figure 4.

[0078] Class mark 400 includes a first octet containing a policy information element identifier (IEI) and a second octet containing the length of the policy information element. Class mark 400 also includes a third octet containing the field "SupportANDSP". Class mark 400 as described herein is modified to include the field "SupportPPPSC", highlighted in bold and italic text, in the third octet.

[0079] Figure 5 shows a method 500 for delivering a policy section-PLMN configuration mapping to the UE. Method 500 is implemented by UE510, AMF520, PCF530, and UDR540. UE510 may comprise a wireless communication device as described herein. UE510 may comprise a user equipment device 200 as described herein. PCF530 may comprise a first network function as described herein. PCF530 may comprise a network node 300 as described herein.

[0080] Method 500 is initiated at 571, and it is decided that UE510 will register with the 5G network. UE510 is configured to support PPPSC rules.

[0081] In 572, since the UE510 is configured to support PPPSC rules (or the ability to support applying URSP rules in V-PLMN), the UE510 includes a policy container in the registration request that contains a policy section identifier and an instruction that PPPSC rules are supported. The UE510 also includes a list of policy section identifiers in the registration request if the UE510 remembers the policy.

[0082] As described in 573, in 3GPP TS 23.502 v18.0.0 (December 2022) titled "Procedures for the 5G System (5GS)", the AMF520 performs the registration procedure.

[0083] In 574, as described in 3GPP TS 23.502 v18.0.0, at one point in the registration procedure, AMF520 selects PCF530 (for UE510 policy).

[0084] In step 575, the AMF520 establishes a UE510 policy association with the selected PCF530 by sending an Npcf_UEPolicyAssociation_Create request. The AMF520 then contains the policy container received by the UE510.

[0085] In step 576, PCF530 confirms the establishment of a UE510 policy association.

[0086] In 577, the procedure for registering the UE510 continues as described in 3GPP TS 23.502 v18.0.0.

[0087] In 578, PCF530 may store in UDR540 the ability of UE510 to support PPPSC rules (or the ability to support applying URSP rules in a particular V-PLMN).

[0088] In 579, PCF530 may query UDR540 for the current UE510 policy / policy section stored in UE510 (based on the policy section identifier).

[0089] In step 580, PCF530 determines whether UE510 requires an updated UE510 policy based on the information provided by UE510 (PSI identifier) ​​and UDR540 (i.e., it compares the PSI sent by UE510 with the PSI retrieved by UDR540).

[0090] In 581, if PCF530 determines that an updated UE510 policy is required (for example, based on UDR540 information indicating that some policy sections are not stored in UE510, or based on updated subscription information), PCF530 sends the updated UE510 policy by triggering a UE510 configuration update for transparent policy delivery, as described in section 4.2.4.3 of 3GPP TS 23.502 v18.0.0. The UE510 policy may include policy sections identified by PSI identifiers, which include PPPSC rules. PCF530 may decide to create PPPSC rules based on PPPSC capabilities reported by UE510 or based on PPPSC capabilities retrieved from UDR540.

[0091] In 582a, UDR540 may notify PCF530 of VPLMN-specific URSP rules for one or more VPLMNs identified by a VPLMN identifier (as described in 3GPP TS 23.502 v18.0.0).

[0092] In 582b, PCF530 may receive a request from PCF530 in V-PLMN for V-PLMN-specific URSP rules.

[0093] In step 583, PCF530 determines V-PLMN-specific URSP rules and includes them in a policy section (containing only URSP rules) associated with a policy section identifier. PCF530 assigns the policy section identifier.

[0094] In step 584, PCF530 includes a mapping of policy section identifiers (for policy sections containing VPLMN-specific rules) to a list of VPLMN identifiers based on the information provided in steps 582a / 582b, and includes them within the PPPSC rules. PCF530 includes the PPPSC rules in a separate policy section (containing only the PPPSC rules) associated with the policy section identifier. PCF530 assigns the policy section identifier. If an existing policy section containing PPPSC rules exists (i.e., UE510 has already provisioned such rules), PCF530 may update the PPPSC rules with the updated information and include the updated rules in the existing policy section containing the PPPSC rules.

[0095] In 585, the PCF530 sends the updated UE510 policy by triggering a UE510 configuration update for transparent policy delivery as described in section 4.2.4.3 of 3GPP TS 23.502 v18.0.0. The UE510 policy includes a policy section identified by a PSI identifier, which contains the PPPSC rule.

[0096] In 586, when UE510 extracts the mapping of PSI to PLMN identifiers from PPPSC rules and registers them in PLMN according to the mapping information, it prioritizes the URSP rules of the policy section identified by the PSI.

[0097] Accordingly, a first network function of a first wireless communication network is provided, comprising a processor and memory coupled to the processor. The processor is configured to cause the first network function to determine a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and to include the policy configuration in a separate policy section identified by a unique policy section identifier, and to transmit the policy configuration to the second network function of the first wireless communication network.

[0098] Therefore, the first wireless communication network can indicate to wireless communication devices which wireless communication devices can use policies issued from the first wireless communication network. This can be facilitated by providing a mapping of policy sections to wireless communication network identities.

[0099] The first network function may include a policy control function (PCF). The second network function may include an access and mobility management function (AMF).

[0100] Policies applied by wireless communication devices can be UE policies. Policies applied by wireless communication devices can be route selection policy rules. Route selection policies can be UE routing selection policy (URSP) rules.

[0101] Wireless communication devices may have a UE. A UE can be defined according to 3GPP.

[0102] Wireless communication networks can be identified by a Public Land Mobile Network (PLMN) identifier. The first wireless communication network may be a home wireless communication network. The second wireless communication network may be a visited wireless communication network.

[0103] The processor may be further configured to receive instructions for a list of route selection policies for wireless communication devices, the list of route selection policies including instructions for the identity of the wireless communication network to which each route selection policy should apply.

[0104] Each policy configuration may contain a tuple that includes a policy section identifier and a wireless communication network identifier. The policy section identifier may be associated with the wireless communication network identifier. Each policy configuration may be defined as a new rule within a policy section.

[0105] The policy configuration for a wireless communication device may be determined based on stored policies identified by policy section identifiers received by the wireless communication device during the registration procedure. The configuration may be specific to one wireless communication network. The configuration may be specific to two or more wireless communication networks. For example, the wireless communication device may send a list of policy section identifiers (corresponding to stored policies), and based on that list, a first network function may determine that the wireless communication device does not have a policy section containing wireless communication network-specific configurations.

[0106] The processor may be further configured to determine a policy configuration indicating one or more policies based on receiving information indicating that a wireless communication device can apply different policies in different wireless communication networks. This information may be received from an integrated data repository (UDR).

[0107] Figure 6 shows a method 600 in a first network function of a first wireless communication network, the method comprising: step 610 determining a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and the policy configuration is placed in a separate policy section identified by a unique policy section identifier; and step 620 transmitting the policy configuration to a second network function of the first wireless communication network.

[0108] Therefore, the first wireless communication network can indicate to wireless communication devices which wireless communication devices can use policies issued from the first wireless communication network. This can be facilitated by providing a mapping of policy sections to wireless communication network identities.

[0109] In certain embodiments, method 600 may be implemented by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0110] The first network function may include a policy control function (PCF). The second network function may include an access and mobility management function (AMF).

[0111] Policies applied by wireless communication devices can be UE policies. Policies applied by wireless communication devices can be route selection policy rules. Route selection policies can be UE routing selection policy (URSP) rules.

[0112] Wireless communication devices may have a UE. A UE can be defined according to 3GPP.

[0113] Wireless communication networks can be identified by a Public Land Mobile Network (PLMN) identifier. The first wireless communication network may be a home wireless communication network. The second wireless communication network may be a visited wireless communication network.

[0114] The method includes the step of receiving instructions for a list of route selection policies for a wireless communication device, the further step of which the list of route selection policies includes instructions for the identity of the wireless communication network to which each route selection policy should apply.

[0115] Each policy configuration may contain a tuple that includes a policy section identifier and a wireless communication network identifier. The policy section identifier may be associated with the wireless communication network identifier. The wireless communication network identifier may be associated with the policy section identifier.

[0116] Each policy configuration can be defined as a new rule within a policy section.

[0117] The policy configuration for a wireless communication device may be determined based on a stored policy identified by a policy section identifier received by the wireless communication device during the registration procedure.

[0118] The configuration may be specific to one wireless communication network. The configuration may be specific to two or more wireless communication networks. For example, a wireless communication device may send a list of policy section identifiers (corresponding to stored policies), and based on that list, a first network function may determine that the wireless communication device does not have a policy section containing a wireless communication network-specific configuration.

[0119] The method may further include the step of determining a policy configuration that represents one or more policies, based on receiving information indicating that a wireless communication device can apply different policies in different wireless communication networks. The information indicating that a wireless communication device can apply different policies in different wireless communication networks may be received from an integrated data repository (UDR).

[0120] A wireless communication device is further provided, comprising a processor and memory coupled to the processor. The processor is configured to cause the wireless communication device to send a registration request to a wireless communication network, the registration request comprising a policy container which includes instructions that the wireless communication device may apply different policies in different wireless communication networks.

[0121] Therefore, a wireless communication device can receive instructions from a first wireless communication network regarding which wireless communication network the wireless communication device can use policies issued from the first wireless communication network. This can be facilitated by provisioning a mapping of policy sections to wireless communication network identities.

[0122] Policies applied by wireless communication devices can be UE policies. Policies applied by wireless communication devices can be route selection policy rules. Route selection policies can be UE routing selection policy (URSP) rules.

[0123] The processor may be further configured to store within the Wireless Communication Device Policy Class Mark Information element instructions that a wireless communication device may apply different policies in different wireless communication networks.

[0124] A registration request may be sent to the first network function. An instruction that a wireless communication device may apply different route selection policy rules in different wireless communication networks may be received by the PCF and stored in the UDR by the PCF.

[0125] Figure 7 shows a method 700 in a wireless communication device, the method 700 comprising step 710 of sending a registration request to a wireless communication network, wherein the registration request includes a policy container that includes instructions that the wireless communication device may apply different policies in different wireless communication networks.

[0126] Therefore, a wireless communication device can receive instructions from a first wireless communication network regarding which wireless communication network the wireless communication device can use policies issued from the first wireless communication network. This can be facilitated by provisioning a mapping of policy sections to wireless communication network identities.

[0127] In certain embodiments, method 700 may be implemented by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0128] Policies applied by wireless communication devices can be UE policies. Policies applied by wireless communication devices can be route selection policy rules. Route selection policies can be UE routing selection policy (URSP) rules.

[0129] The method may further include the step of storing in a wireless communication device policy class mark information element an instruction that a wireless communication device may apply different policies in different wireless communication networks. A registration request may be sent to a first network function.

[0130] An instruction that a wireless communication device can apply different route selection policy rules in different wireless communication networks may be received by the PCF and stored in the UDR by the PCF.

[0131] In traditional wireless communication networks, URSP rules are provided only by the H-PLMN, and the UE applies the same URSP rules in any PLMN the UE registers with. This creates problems when the UE is roaming, as a V-PLMN operator may require specific traffic routing for specific applications. In addition, there are scenarios where the V-PLMN operator cannot interface with the H-PLMN (for example, when the UE registers in the SNPN using credentials from the H-PLMN). Currently, there are no details on how a PLMN can provision URSP-PLMN mapping information to the UE.

[0132] This specification provides a method for PCF to recognize the mapping of policy section identifiers to PLMNs for each UE. Further, a method for encoding the mapping of policy section identifiers to PLMNs within a provisioned UE policy is provided.

[0133] Therefore, the PCF of H-PLMN (H-PCF) includes a tuple (PLMN ID, policy section identifier) ​​in a separate policy section identified by the policy section identifier.

[0134] Accordingly, a PCF in a first mobile communication network is provided, configured to receive instructions for a list of URSP policies for a UE applicable to a second mobile communication network identified by a PLMN identifier; determine a PLMN-specific policy configuration for a UE, which includes such a PLMN configuration in a policy section identified by a policy section identifier; and send a first message to a first network function (AMF), which sends a policy section containing the PLMN policy configuration and the associated policy section identifier.

[0135] A PLMN-specific policy configuration may include a tuple containing a policy section identifier and an associated PLMN identifier (or vice versa, a PLMN identifier and an associated policy section identifier).

[0136] PLMN-specific policy configurations can be defined as new rules within the policy section.

[0137] The PCF may determine policy-specific configuration information based on the PLMN-specific policy configuration received by the UE during the registration request.

[0138] The PCF may determine policy-specific configuration information based on receiving information from the UDR indicating that the UE can apply URSP rules in a particular PLMN.

[0139] Further provided is a UE in a first mobile communications network, configured to decide to register with a 5G mobile communications network and to send a registration request that includes in the request a policy container that has the capability to support PLMN-specific policy configuration.

[0140] The capabilities can be stored within the UE policy class mark information element.

[0141] A policy container, including PLMN-specific policy configuration capabilities, can be received by PCF.

[0142] The ability to support separate policy configurations for each PLMN can be stored in the UDR by the PCF.

[0143] It should be noted that the methods and apparatus described above are illustrative of the invention, not limiting it, 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 “comprising” does not exclude the presence of elements or steps other than those listed in the claims, and “a” or “an” does not exclude plurals; a single processor or other unit may perform the functions of several units enumerated in the claims. No reference numerals in the claims should be construed to limit their scope.

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

[0145] The method can also be embodied in a set of instructions that, when stored on a computer-readable medium and loaded into a computer processor, digital signal processor (DSP), or similar processor, cause the processor to perform the method described above.

[0146] The methods and apparatus described may be practiced in other specific forms. The methods and apparatus described should be considered in all respects as illustrative and not limiting. Accordingly, the scope of the invention is indicated not by the above description but by the appended claims. All modifications that fall within the meaning and scope of the equivalent claims should be encompassed within their scope.

[0147] The following abbreviations are relevant to the areas covered in this document: URSP, UE Routing Selection Policy; PCF, Policy and Billing Function; UE, User Equipment; NEF, Network Exposure Function; UDR, Integrated Data Repository; PSI, Policy Section Identifier; RSD, Route Selection Descriptor [Explanation of symbols]

[0148] 100 Wireless Communication Systems 102 Remote Unit 104 Network Units 200 User equipment, devices 205 Processor 210 memory 215 Input Devices 220 Output Devices 225 Transceiver 230 Transmitter 235 Receiver 240 network interfaces 245 Application Interfaces 300 network nodes 305 Processor 310 memory 315 Input Devices 320 Output Devices 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interfaces 345 Application Interfaces 400 Class Mark 450 LMF 500 ways 510 UE 520 AMF 530 Policy control function, PCF 540 UDR 600 ways 700 methods

Claims

1. A first network function of a first wireless communication network, wherein the first network function is Processor and The system comprises a memory coupled with the processor, and the processor performs the first network function, Determining a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and the policy configuration is placed in a separate policy section identified by a unique policy section identifier. The policy configuration is transmitted to the second network function of the first wireless communication network. A first network function configured to perform the following actions.

2. The first network function according to claim 1, wherein the processor is further configured to receive instructions for a list of route selection policies for the wireless communication device, the list of route selection policies including instructions for the identity of a wireless communication network to which each route selection policy should be applied.

3. The first network function according to claim 1, wherein each policy configuration includes a tuple containing a policy section identifier and a wireless communication network identifier.

4. The first network function according to claim 1, 2, or 3, wherein each policy configuration is defined as a new rule within a policy section.

5. The first network function according to any one of claims 1 to 4, wherein the policy configuration for the wireless communication device is determined based on the stored policy identified by a policy section identifier received by the wireless communication device during a registration procedure.

6. The first network function according to any one of claims 1 to 5, wherein the processor is further configured to determine the policy configuration, which represents one or more policies, based on receiving information indicating that the wireless communication device can apply different policies in different wireless communication networks.

7. A method in the first network function of a first wireless communication network, A step of determining a policy configuration for a wireless communication device, wherein the policy configuration indicates one or more policies to be applied by the wireless communication device in a second wireless communication network, and the policy configuration is placed in a separate policy section identified by a unique policy section identifier. The steps include transmitting the policy configuration to the second network function of the first wireless communication network, and Methods that include...

8. The method according to claim 7, further comprising the step of receiving instructions for a list of route selection policies for the wireless communication device, wherein the list of route selection policies includes instructions for the identity of a wireless communication network to which each route selection policy should apply.

9. The method according to claim 7, wherein each policy configuration includes a tuple containing a policy section identifier and a wireless communication network identifier.

10. The method according to claim 7, 8, or 9, wherein each policy configuration is defined as a new rule within a policy section.

11. The method according to any one of claims 7 to 10, wherein the policy configuration for the wireless communication device is determined based on the stored policy identified by a policy section identifier received by the wireless communication device during a registration procedure.

12. The method according to any one of claims 7 to 11, further comprising the step of determining the policy configuration which represents one or more policies, based on receiving information indicating that the wireless communication device can apply different policies in different wireless communication networks.

13. A wireless communication device, Processor and The device comprises a processor and a memory coupled thereto, and the processor provides the wireless communication device, Sending a registration request to a wireless communication network, wherein the registration request includes a policy container that includes instructions that the wireless communication device may apply different policies in different wireless communication networks. A wireless communication device configured to perform the following actions.

14. The wireless communication device according to claim 13, further configured to store in a wireless communication device policy class mark information element the instruction that the wireless communication device can apply different policies in different wireless communication networks.

15. The wireless communication device according to claim 13 or 14, wherein the registration request is sent to a first network function.

16. A method in a wireless communication device, A step of sending a registration request to a wireless communication network, wherein the registration request includes a policy container that includes instructions that the wireless communication device may apply different policies in different wireless communication networks. Methods that include...

17. The method according to claim 16, further comprising the step of storing in a wireless communication device policy class mark information element the instruction that the wireless communication device can apply different policies in different wireless communication networks.

18. The method according to claim 16 or 17, wherein the registration request is sent to the first network function.

Images