WIRELESS COMMUNICATION NETWORKS

Field

[0001] The subject matter disclosed herein relates generally to the field of provisioning policy sections for multiple wireless communication networks. This document defines a wireless communication device, a method in a wireless communication device, a first network function, a method in a first network function, a second network function, and a method in a second network function.

Introduction

[0002] Since Release 15 onwards UE route selection policy (URSP) rules have been defined to allow a UE to determine how to route application traffic via the mobile communication network either via 3GPP access or via non-3GPP access via an untrusted or trusted WEAN access or route the traffic non-seamlessly bypassing the mobile communication network via a WEAN connection. The URSP rules contain a Traffic Descriptor that allows the UE to determine if a URSP rule matches the application traffic that the UE is currently handling in uplink and/ or downlink. Traffic Descriptors may include Application Descriptors (OSID/OSAppID) and IP flow descriptors. IP flow descriptors may be, for example, target address of application traffic, a requested DNN by the application or a connection capability requested by an application (e.g. an IMS connection).

[0003] Each URSP rule contains a Route Selection Descriptor (RSD) that defines how the UE is to route the PDU session. The RSD includes one or more of the following: SSC Mode Selection, Network Slice Selection, DNN Selection, PDU Session Type Selection, Non-Seamless Offload indication, Access Type preference. The UE routes the traffic via the PDU session that matches the RSD components. The routes may include both 3GPP access and non-3GPP access.

[0004] Currently URSP rules are only provided to a UE from the PCF of the Home PLMN (e.g. H-PCF). A UE uses the provisioned URSP rules in any PLMN that the UE may register to, for example, when the UE is roaming to a Visited PLMN, the UE will apply the same URSP rules in the Visited PLMN as where provisioned by the Home PLMN. However, conventionally a Home PLMN will issue URSP rules suitable for traffic on the Home PLMN without consideration for any Visited PLMN that the UE may use. When the UE is roaming the PCF at the V-PLMN (e.g. V-PCF) is not allowed to create/ provision URSP rules but is allowed to create/ provision ANDSP (Access Network Discovery and Selection Policy) rules.

Summary

[0005] In convention wireless communication networks, URSP rules are provided only by the H-PLMN and the UE applies the same URSP rules in any PLMN that the UE registers to. This creates issues in case, when a UE is roaming, as the V-PLMN operator may require a specific traffic routing for a specific application. In addition, there are scenarios where a V-PLMN operator cannot interface with the H-PLMN (e.g. in case a UE registers in an SNPN with credentials from the H-PLMN) .

[0006] Disclosed herein are procedures for provisioning policy sections for multiple wireless communication networks. Said procedures may be implemented by a wireless communication device, a method in a wireless communication device, a first network function, a method in a first network function, a second network function, and a method in a second network function.

[0007] Accordingly, there is provided a wireless communication device, comprising a processor; and a memory coupled with the processor. The processor is configured to cause the wireless communication device to: send a register request message to a first network function, the register request message comprising a message to initiate establishment of a policy association; and receive a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to. [0008] There is further provided a method in a wireless communication device, the method comprising: sending a register request message to a first network function, the register request message comprising a message to initiate establishment of a policy association; and receiving a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to.

[0009] There is further provided a first network function, comprising a processor and a memory coupled with the processor. The processor is configured to cause the first network function to: receive a register request message from a wireless communication device, the register request message comprising a message to initiate establishment of a policy association; and parse the register request message to obtain the message to initiate establishment of a policy association. The processor is further configured to cause the first network function to: transmit, to a second network function, an HTTP POST message comprising the message to initiate establishment of a policy association; receive, from the second network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to; and transmitting the list to the wireless communications device.

[0010] There is further provided a method in a first network function, the method comprising: receiving a register request message from a wireless communication device, the register request message comprising a message to initiate establishment of a policy association; and parsing the register request message to obtain the message to initiate establishment of a policy association. The method further comprises transmitting, to a second network function, an HTTP POST message comprising the message to initiate establishment of a policy association; receiving, from the second network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to; and transmitting the list to the wireless communications device.

[0011] There is further provided a method in a second network function, the method comprising: receiving, from a first network function, an HTTP POST message comprising a message to initiate establishment of a policy association; and sending, to the first network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to.

Brief description of the drawings

[0012] In order to describe the manner in which advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to certain apparatus and methods which are illustrated in the appended drawings. Each of these drawings depict only certain aspects of the disclosure and are not therefore to be considered to be limiting of its scope. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0013] Methods and apparatus for provisioning policy sections for multiple wireless communication networks will now be described, by way of example only, with reference to the accompanying drawings, in which:

Figure 1 depicts an embodiment of a wireless communication system for provisioning policy sections for multiple wireless communication networks;

Figure 2 depicts a user equipment apparatus that may be used for implementing the methods described herein;

Figure 3 depicts further details of the network node that may be used for implementing the methods described herein;

Figure 4 illustrates the encoding of a UE policy section management list information element;

Figure 5 illustrates the encoding of a UE policy part;

Figure 6 illustrates a new encoding for instructions;

Figure 7 illustrates a modified UE policy network classmark information element;

Figure 8 illustrates a call flow of a procedure for the initial registration of a UE to a 5GS network;

Figure 9 illustrates a method in a wireless communication device;

Figure 10 illustrates a method in a first network function; and Figure 11 illustrates a method in a second network function.

Detailed description

[0014] As will be appreciated by one skilled in the art, aspects of this disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, arrangements described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, micro-code, etc.) or a form combining software and hardware aspects.

[0015] For example, the disclosed methods and apparatus may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0016] Furthermore, the methods and apparatus 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, referred hereafter as code. The storage devices may be tangible, non-transitory, and/ or non-transmission. The storage devices may not embody signals. In certain arrangements, the storage devices only employ signals for accessing code.

[0017] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium 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, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0018] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, 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] Reference throughout this specification to an example of a particular method or apparatus, or similar language, means that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the method and apparatus described herein. Thus, reference to features of an example of a particular method or apparatus, or similar language, may, but do not necessarily, all refer to the same example, but mean “one or more but not all examples” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof, mean “including but not limited to”, unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a”, “an”, and “the” also refer to “one or more”, unless expressly specified otherwise.

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

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

[0022] Aspects of the disclosed method and apparatus are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowchart diagrams and/ or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions /acts specified in the schematic flowchart diagrams 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 devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/ act specified in the schematic flowchart diagrams and/or schematic block diagrams.

[0024] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions /acts specified in the schematic flowchart diagrams and/ or schematic block diagram.

[0025] The schematic flowchart diagrams and/ or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s). [0026] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0027] The description of elements in each figure may refer to elements of proceeding Figures. Like numbers refer to like elements in all Figures.

[0028] Figure 1 depicts an embodiment of a wireless communication system 100 for provisioning policy sections for multiple wireless communication networks. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill 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.

[0029] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle onboard computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smartwatches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0030] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an Access and Mobility Management Function (“AMF”), a Unified Data Management Function (“UDM”), a Unified Data Repository (“UDR”), a UDM/UDR, a Policy Control Function (“PCF”), a Radio Access Network (“RAN”), an Network Slice Selection Function (“NSSF”), an operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), an application function, a service enabler architecture layer (“SEAL”) function, a vertical application enabler server, an edge enabler server, an edge configuration server, a mobile edge computing platform function, a mobile edge computing application, an application data analytics enabler server, a SEAL data delivery server, a middleware entity, a network slice capability management server, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicab ly coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0031] In one implementation, the wireless communication system 100 is compliant with New Radio (NR) protocols standardized in 3GPP, wherein the network unit 104 transmits using an Orthogonal Frequency Division Multiplexing (“OFDM”) modulation scheme on the downlink (DL) and the remote units 102 transmit on the uplink (UL) using a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfox, LoraWAN among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0032] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/ or spatial domain.

[0033] Figure 2 depicts a user equipment apparatus 200 that may be used for implementing the methods described herein. The user equipment apparatus 200 is used to implement one or more of the solutions described herein. The user equipment apparatus 200 is in accordance with one or more of the user equipment apparatuses described in embodiments herein. In particular, the user equipment apparatus 200 may comprise a wireless communication device, a remote unit 102, a user equipment apparatus 200, and/ or a UE 810 as described herein. The user equipment apparatus 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225. [0034] The input device 215 and the output device 220 may be combined into a single device, such as a touchscreen. In some implementations, the user equipment apparatus 200 does not include any input device 215 and/ or output device 220. The user equipment apparatus 200 may include one or more of: the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and/ or the output device 220.

[0035] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 may communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 may be operable on unlicensed spectrum. Moreover, the transceiver 225 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 225 may support at least one network interface 240 and/ or application interface 245. The application interface(s) 245 may support one or more APIs. The network interface(s) 240 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 240 may be supported, as understood by one of ordinary skill in the art.

[0036] The processor 205 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations. For example, the processor 205 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. The processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225. [0037] The processor 205 may control the user equipment apparatus 200 to implement the user equipment apparatus behaviors described herein. The processor 205 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

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

[0039] The memory 210 may store data related to implement a traffic category field as described herein. The memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on the apparatus 200. [0040] The input device 215 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. 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 such that text may be input 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 touch panel.

[0041] The output device 220 may be designed to output visual, audible, and/ or haptic signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a 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 similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 220 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 200, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0042] The output device 220 may include one or more speakers for producing 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 vibrations, motion, or other haptic feedback. All, or portions, of the output device 220 may be integrated with the input device 215. For example, the input device 215 and output device 220 may form a touchscreen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0043] The transceiver 225 communicates with one or more network functions of a 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 also to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times in order to send and receive messages.

[0044] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The one or more transmitters 230 may be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, the 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 illustrated, the user equipment apparatus 200 may have any suitable number of transmitters 230 and receivers 235. Further, the trans mi tter(s) 230 and the receiver(s) 235 may be any suitable type of transmitters and receivers. The transceiver 225 may include a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

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

[0046] One or more transmitters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a single hardware component, such as a multitransceiver 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 integrated into a multi-chip module. Other components such as the network interface 240 or other hardware components/ circuits may be integrated with any number of transmitters 230 and/ or receivers 235 into a single chip. The transmitters 230 and receivers 235 may be logically configured as a transceiver 225 that uses one more common control signals or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or in a multi-chip module.

[0047] Figure 3 depicts further details of the network node 300 that may be used for implementing the methods described herein. The network node 300 may be one implementation of an entity in the wireless communication network, e.g. in one or more of the wireless communication networks described herein. The network node 300 may comprise a first network function, a network unit 104, and/ or an AMF 820, as described herein. The network node 300 may comprise a second network function, a network unit 104, and/ or a PCF 830, as described herein. The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0048] The input device 315 and the 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, the memory 310, and the transceiver 325, and may not include the input device 315 and/ or the output device 320.

[0049] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 may support at least one network interface 340 and/ or application interface 345. The application interface(s) 345 may support one or more APIs. The network interface(s) 340 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 340 may be supported, as understood by one of ordinary skill in the art.

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

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

[0052] The memory 310 may store data related to establishing a multipath unicast link and/ or mobile operation. For example, the memory 310 may store parameters, configurations, resource assignments, policies, and the like, as described herein. The memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network node 300.

[0053] The input device 315 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. 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 such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen. The input device 315 may include two or more different devices, such as a keyboard and a touch panel.

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

[0055] The output device 320 may include one or more speakers for producing 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 vibrations, motion, or other haptic feedback. All, or portions, of the output device 320 may be integrated with the input device 315. For example, the input device 315 and output device 320 may form a touchscreen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0056] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The one or more transmitters 330 may be used to communicate with the UE, as described herein. Similarly, the 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 illustrated, the network node 300 may have any suitable number of transmitters 330 and receivers 335. Further, the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitters and receivers.

[0057] Since Release 15 onwards UE route selection policy (URSP) rules have been defined to allow a UE to determine how to route application traffic via the mobile communication network either via 3GPP access or via non-3GPP access via an untrusted or trusted WLAN access or route the traffic non-seamlessly bypassing the mobile communication network via a WLAN connection. The URSP rules and the procedures for the UE to apply URSP rules are described in 3GPP TS 23.502 vl 8.0.0 (Dec 2022) titled “Procedures for the 5G System (5GS)” and 3GPP TS 23.503 vl8.0.0 (Dec 2022) titled “Policy and charging control framework for the 5G System (5GS); Stage 2” (URSP rules definitions and procedures are included from version 15.0.0 onwards of 23.502 and 23.503).

[0058] The URSP rules contain a Traffic Descriptor that allows the UE to determine if a URSP rule matches the application traffic that the UE is currently handling in uplink and/ or downlink. Traffic Descriptors may include Application Descriptors (OSID/OSAppID) and IP flow descriptors. IP flow descriptors may be, for example, target address of application traffic, a requested DNN by the application or a connection capability requested by an application (e.g. an IMS connection).

[0059] Each URSP rule contains a Route Selection Descriptor (RSD) that defines how the UE is to route the PDU session. The RSD includes one or more of the following: SSC Mode Selection, Network Slice Selection, DNN Selection, PDU Session Type Selection, Non-Seamless Offload indication, Access Type preference. The UE routes the traffic via the PDU session that matches the RSD components. The routes may include both 3GPP access and non-3GPP access.

[0060] Currently URSP rules are only provided to a UE from the PCF of the Home PLMN (e.g. H-PCF). A UE uses the provisioned URSP rules in any PLMN that the UE may register to, for example, when the UE is roaming to a Visited PLMN, the UE will apply the same URSP rules in the Visited PLMN as where provisioned by the Home PLMN. However, conventionally a Home PLMN will issue URSP rules suitable for traffic on the Home PLMN without consideration for any Visited PLMN that the UE may use. When the UE is roaming the PCF at the V-PLMN (e.g. V-PCF) is not allowed to create/ provision URSP rules but is allowed to create/ provision Access Network Discovery and Selection Policy (ANDSP) rules.

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

[0062] As part of Release 18 work in eUEPO work item it has been agreed to allow a solution where the network indicates to the UE which URSP rules are applicable when a UE is roaming to a V-PLMN. This is supported by the home network (e.g. H-PCF) providing a mapping of policy section identifiers to a list of one or more V-PLMN identifiers. When the UE registers to a V-PLMN the UE uses the UE policies for that V-PLMN as higher priority as compared to other URSP rules.

[0063] There is provided herein an improvement to the operation of a wireless communication network whereby:

• the PCF is made aware, on a per UE basis, the mapping of policy section identifier to a PLMN identifier; and

• the mapping of policy section identifier to PLMN identifier is encoded within provisioned UE policies.

[0064] 3GPP TS 23.503 vl8.0.0 (Dec 2022) titled “Policy and charging control framework for the 5G System (5GS); Stage 2” states that the PCF may provide a mapping of policy section identifier(s) to a PLMN ID. Such a PCF may provide to the UE the tuple (PLMN ID, list of PSIs associated with the PLMN ID) and the Policy Sections containing URSP Rules. However, the standard does not provide details on how the PCF might encode the tuple or how this tuple might be provided.

[0065] The structure of the UE policy section management list information element is specified in 3GPP TS 24.501 vl8.1.0 titled “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3” as:

• UE policy section management sublist (PLMN ID [1 ... »])

• Instruction [1 ... «] (UPSCz, UE policy parts [1 ... C]) where the PLMN ID for the UE policy section management sublist shows the PLMN where the PCF belongs to. Thus, the PLMN IDs are limited to the HPLMN and VPLMN at the time of roaming, therefore m is either 1 or 2. The UE policy section management sublist comprises one or more instructions where each instruction comprises a specific UPSCi which is assigned by the PCF and one or more UE policy parts. Dependent on the UE policy parts the content of the UE policy part can be:

• UE route selection policy (URSP);

• access network discovery and selection policy (ANDSP);

• V2X policy (V2XP); and/or

• ProSe policy (ProSeP).

[0066] Figure 4 illustrates the encoding of the UE policy section management list information element 400. The UE policy section management list information element 400 comprises a length of UE policy section management list contents 401 and a UE policy section management list contents 402. The UE policy section management list contents 402 comprises N UE policy section management sublists, including a first UE policy section management sublist 411, a second UE policy section management sublist 412. Each UE policy section management sublist (411, 412, etc.) comprises a length of UE policy section management sublist 421, a plurality of MCC and MNC digits 422, and a UE policy section management sublist contents 426. The UE policy section management sublist contents 426 comprises M instructions, including a first instruction 431 and a second instruction 432. Each instruction (431, 432, etc.) comprises an instruction contents length 441, a USPC 442, and a UE policy section contents 443. The UE policy section contents 443 comprises Q UE policy parts, including a first UE policy part 451 and a second UE policy part 452. Each UE policy part (451, 452, etc.) comprises a UE policy part contents length 461, a plurality of spare fields 462, a UE policy part type 463, and a UE policy part contents 464.

[0067] The UE policy section management list information element 400 illustrated in Figure 4 has a spare value of UE policy part, which is zero and which is not used and shall be ignored by the UE. The UE policy part type is encoded as:

Bits

4 3 2 1

0 0 0 0 Reserved 0 0 0 1 URSP 0 0 1 0 ANDSP 0 0 1 1 V2XP Table 1: Encoding example for UE policy part type [0068] There are some unique UE policy section codes (UPSC) which have the same UE policy section parts as with other one or more PLMNs. The following examples show how this new information can be encoded.

[0069] Figure 5 illustrates the encoding 500 of the UE policy part where the first octet represents the length of the UE policy part contents and 4 least significant bits of the second octet represents the UE policy part type. Therefore, the one of the remaining bits of the second octet can be used as an indicator of whether the identities of the one or more PLMNs are the same in HPLMN and VPLMN.

[0070] In Figure 5, the first spare bit is used as an indicator, indicating whether the UPSC and the UE policy parts are the same between the HPLMN or VPLMN and one or more other PLMNs:

• If Ind. has value of “0” the UPSC and the UE policy parts are not shared by any other PLMN; or

• if In. has value of “1” the UPSC and the UE policy parts are shared by other PLMN.

[0071] In case the value of Ind. is “1” then the one or more PLMNs exists and each PLMN is defined by 3 octets. Figure 5A shows the encoding of having one or more PLMNs. The encoding comprises a UE policy part contents length 561, a plurality of spare bits, a UE policy part type 563, a UE policy part contents 564, an indicator 565, a PLMN contents length 566 and one or more PLMNs 567.

[0072] Figure 5B should if the configuration should be limited to one PLMN. This encoding comprises a UE policy part contents length 561, a plurality of spare bits, a UE policy part type 563, a UE policy part contents 564, an indicator 568 and a PLMN ID 569.

[0073] Figure 5C shows the encoding 522 of PLMN identity 569. The encoding comprises three 3 digits for MCC and three digits for MNC.

[0074] A backward compatibility analysis of this new encoding 500 shows that the legacy UE only is aware of the “UE policy part contents length” ecciA ignores the “Ind.” bit, thus any possible extra octet to identity the PLMN identities after the “UE policy part contents”.

Therefore, there is no backward compatibility issue with this new modified UE policy part. The legacy UE as well as the new UE can get the information they are capable of handling. [0075] Although there is not any backward compatibility issue with the modification proposed in the encoding 500 illustrated in connection with figure 5, the PLMN(s) with the common UPSC and the UE policy parts are repeated in each UE policy part. Figure 6 illustrates a new encoding 600 for instructions wherein the encoding 600 that avoids such repetition. According to the new encoding 600 of the instructions, the first bit of the second octet (or the third octet in case the UPSC is kept as the second octet) indicates whether there UPSC and UE policy parts are the same in the HPLMN or VPLMN and one or more other PLMNs.

• If Ind. has value of “0” the UPSC and the UE policy parts are not shared by any other PLMN; or

• if Ind. has value of “1” the UPSC and the UE policy parts are shared by other PLMN.

[0076] In case when the value of Ind. is “1” then the one or more PLMNs exist and each PLMN is defined by 3 octets.

[0077] Figure 6A shows the encoding of having one or more PLMNs.The encoding comprises an instruction contents length 641, a plurality of spare fields, an indicator 644, a UPSC 642, a UE policy section contents 643, a PLMN contents length, 645 and one or more PLMNs 646.

[0078] Figure 6B shows the encoding configuration when limited to one PLMN. The encoding comprises an instruction contents length 641, a plurality of spare fields, an indicator 647 a UPSC 642, a UE policy section contents 643, and a PLMN ID 648. [0079] Figure 6C shows the encoding 622 of a PLMN identity which comprises three digits for MCC and three digits for MNC.

[0080] A backward compatibility analysis of the new encoding 600 shows that the new encoding 600 cannot be sent to both new and legacy UEs. The UE must know the new encoding to be able to decode the UE policy parts. If the new configuration is sent to a legacy UE, the legacy UE will realize that the “Instructions content length” and the UE policy parts with the “UE policy part contents length” , shown in Figure 4, are out of sync. Thus, in accordance with clause D.8.6.2 of 3GPP TS 24.501 vl8.1.0, which states:

The UE shall ignore all out of sequence IES in a message which are not encoded as "comprehension required" (see 3GPP TS 24.007 [11]).

The network should take the same approach. the UE will ignore the UE policy section management sublist. [0081] This is not an acceptable UE behavior and thus, there is a need for the PCF to know that the UE understands the new encoding 600 prior to transmitting the UE policy section management sublist with the new encoding. The UE is therefore required to include its capability for the new encoding of the instructions in UE policy classmark as defined in clause D.6.5 of 3GPP TS 24.501 vl8.1.0.

[0082] Furthermore, there is a need for the UE to determine whether the UE policy section management sublist is configured using the new encoding. In order for the network to identify whether the UE policy section management list information element is encoded as described in the new configuration in Figure 6, the PCF may use a spare bit in the UE policy network classmark information element. A UE policy network classmark information element is specified in clause D.6.7 of 3GPP TS 24.501 vl8.1.0. Figure 7 illustrates a modified UE policy network classmark information element 700. [0083] The classmark 700 comprises a first octet comprising a Policy information Information Element Identifier (IEI) and a second octet comprising the length of policy information elements. The classmark 700 comprises a third octet that includes a filed “NSSUI”. The classmark 700 as described herein is modified to include a field in the third octet “MPSMLI” highlighted with bold and italicized text. “MPSMLI” refers to modified policy section management list indicator and comprises the value of bit 2 of octet 3 of the modified UE policy network classmark information element 700 shown in Figure 7.

Bits

2

0 The encoding UE policy section management list information element is not modified

1 The encoding UE policy section management list information element is modified

Table 2: Values for modified policy section management list indicator

[0084] As such, when the UE receives the MANAGE UE POLICY COMMAND message as defined in clause D.5.1.1 of 3GPP TS 24.501 vl8.1.0, the UE is informed by this modified classmark 700 whether the UE policy section management list is encoded as described in Figure 6, or not.

[0085] Figure 8 illustrates a call flow of a procedure 800 for the initial registration of a UE to a 5GS network and a procedure at the PCF for establishing the UE policy association and thereby transmitting the UE policy section management list information element towards the UE. Note that this procedure is transparent to the mobile communications technology and is performed in a similar manner in the EPS although the EPS comprises different network entities than the 5GS. The procedure 800 is performed by a UE 810, an AMF 820, a UE-PCF 830, and a UDM/UDR 840.

[0086] The UE 810 may comprise a wireless communication device, a remote unit 102, and/ or a user equipment apparatus 200, as described herein. The AMF 820 may comprise a first network function, a network unit 104, and/ or a network node 300, as described herein. The PCF 830 may comprise a second network function, a network unit 104, and/ or a network node 300, as described herein.

[0087] The procedure 800, begins at 871, when the UE 810 constructs a REGISTRATION REQUEST message as described in 3GPP TS 24.501 vl8.1.0 and includes the UE STATE INDICATION message to perform the UE-initiated UE state indication procedure. The UE 810 may include its capability for the new encoding of the UE policy section management list information element in the UE policy classmark information element.

[0088] The AMF 820 handles the REGISTRATION REQUEST message according to the procedure described in 3GPP TS 23.502 vl8.1.0. One part of the procedure is to select the UE-PCF 830 and to pass transparently the UE STATE INDICATION message towards the UE-PCF 830.

[0089] At 872, the AMF uses the Npcf_UEPolicyControl_Create and the attribute uePolReq as described in 3GPP TS 29.525 vl8.1.0 titled “5G System; UE Policy Control Service; Stage 3” to pass the UE STATE INDICATION message to the selected PCF to request for the establishment of the UE policy association.

[0090] At 873, the UE-PCF 830 may store the UE’s capability to handle the new encoding of the UE policy section management list information element in the UDR 840.

[0091] Based on the information in the UPSI list provided by the UE 810 and the information provided by the UDR 840, the UE-PCF 830 determines if the UE 810 requires updated UE policies (e.g. compares UPSI list provided by the UE and those received from the UDR 840) .

[0092] At 874, analyzing of the UPSI list provided by the UE 810 and those received from the UDR 840 may show a need for an update of the UE policy sections due to e.g. the UE's subscription is changed.

[0093] At 875, since there is a need to update the UE policy sections, the network- requested UE policy management procedure as described in cause D.2.1.2 of 3GPP TS 24.501 vl8.1.0 is initiated by the UE-PCF 830 encoding the policy sections to be added, modified or deleted in a UE policy section management list information element as specified in subclause D.6.2 of 3GPP TS 24.501 vl8.1.0.

• If the new encoding according to the embodiment 1 is employed, the PCF may not need to consider the UE's capability of the new encoding since the legacy UE will only get the “UE policy part contents” within the UE policy part information element and will ignore the PLMN information.

• If the new encoding according to Figure 6 is employed, the UE-PCF 830 may need to consider the UE’s capability of the new encoding since the legacy UE will ignore the UE policy management sublist information element due to the Instruction information element and the UE policy part information element being out of sequence.

[0094] At 876, the UE-PCF 830 constructs the MANAGE UE POLICY COMMAND message and transmits the MANAGE UE POLICY COMMAND message to the UE via the AMF as specified in 3GPP TS 23.502 vl8.1.0.

• if the encoding 500 according to Figure 5 is employed, the UE-PCF 830 may not need to set the modified policy section management list indicator of the UE policy network classmark IE to “The encoding UE policy section management list information element is modified”; or

• if the new encoding 600 according to Figure 6 is employed, the UE-PCF 830 sets the modified policy section management list indicator of the UE policy network classmark IE to “The encoding UE policy section management list information element is modified”.

[0095] At 877, upon receipt of the MANAGE UE POLICY COMMAND message, the UE 810 checks whether the UE policy section management list information element is modified by the new encoding by checking the modified policy section management list indicator of the UE policy network classmark IE and with respect to the new encoding: a) stores the received UE policy section of the instruction, if the UE has no stored UE policy section associated with the same UPSI as the UPSI associated with the instruction; b) replaces the stored UE policy section with the received UE policy section of the instruction, if the UE has a stored UE policy section associated with the same UPSI as the UPSI associated with the instruction; or c) deletes the stored UE policy section, if the UE has a stored UE policy section associated with the same UPSI as the UPSI associated with the instruction and the UE policy section contents of the instruction is empty.

[0096] At 878, if all instructions included in the UE policy section management list IE were executed successfully by the UE, the UE: a) creates a MANAGE UE POLICY COMPLETE message including the PTI value received within the MANAGE UE POLICY COMMAND message; and b) transports the MANAGE UE POLICY COMPLETE message using the NAS transport procedure as specified in clause 5.4.5 of 3GPP TS 24.501 vl8.1.0.

[0097] Accordingly, there is provided a wireless communication device, comprising a processor; and a memory coupled with the processor. The processor is configured to cause the wireless communication device to: send a register request message to a first network function, the register request message comprising a message to initiate establishment of a policy association; and receive a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to. [0098] The plurality of wireless communication networks may comprise a plurality of PLMNs. The first network function may be an AMF. The second network function may be a PCF.

[0099] The list comprising one or more policy sections may be formatted so as to be transparent to a capability of the wireless communication device. The capability of the wireless communication device may be that the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks. [0100] The list comprising one or more policy sections may be formatted so as to be interpreted by the wireless communication device only if the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks. A list formatted in such a way may be rejected by the wireless communication device if the wireless communication device is not capable of implementing a policy section for a plurality of wireless communication networks.

[0101] The list may be received from a second network function via the first network function. [0102] The list may indicate that the one or more policy sections are valid for more than one wireless communication network, and the processor may be further configured to cause the wireless communication device to interpret the one or more policy sections.

[0103] The processor may be further configured to cause the wireless communication device to send a capability message, the capability message comprising an indication that the wireless communication device is capable to apply one or more policy sections for more than one wireless communication network.

[0104] The processor may be further configured to cause the wireless communication device to initiate establishment of a policy association is a UE STATE INDICATION message. The UE STATE INDICATION message may be as defined in 3GPP TS 24.501 vl8.1.0 titled “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0105] Figure 9 illustrates a method 900 in a wireless communication device, the method 900 comprising: sending 910 a register request message to a first network function, the register request message comprising a message to initiate establishment of a policy association; and receiving 920 a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to.

[0106] In certain embodiments, the method 900 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0107] The plurality of wireless communication networks may comprise a plurality of PLMNs. The first network function may be an AMF. The second network function may be a PCF.

[0108] The list may comprise one or more policy sections formatted so as to be transparent to a capability of the wireless communication device. The capability of the wireless communication device may be that the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks.

[0109] The list may comprise one or more policy sections formatted so as to be interpreted by the wireless communication device only if the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks. [0110] A list formatted in such a way may be rejected by the wireless communication device if the wireless communication device is not capable of implementing a policy section for a plurality of wireless communication networks.

[0111] The list may be received from a second network function via the first network function.

[0112] The list may indicate that the one or more policy sections are valid for more than one wireless communication network, the method further comprising interpreting the one or more policy sections.

[0113] The method may further comprise sending a capability message, the capability message comprising an indication that the wireless communication device is capable to apply one or more policy sections for more than one wireless communication network. [0114] The message to initiate establishment of a policy association may be a UE STATE INDICATION message. The UE STATE INDICATION message may be as defined in 3GPP TS 24.501 vl8.1.0 titled “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0115] There is further provided a first network function, comprising a processor and a memory coupled with the processor. The processor is configured to cause the first network function to: receive a register request message from a wireless communication device, the register request message comprising a message to initiate establishment of a policy association; and parse the register request message to obtain the message to initiate establishment of a policy association. The processor is further configured to cause the first network function to: transmit, to a second network function, an HTTP POST message comprising the message to initiate establishment of a policy association; receive, from the second network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to; and transmitting the list to the wireless communications device.

[0116] The plurality of wireless communication networks may comprise a plurality of PLMNs. The first network function may be an AMF. The second network function may be a PCF.

[0117] The list transmitted to the wireless communication device may be formatted so as to be transparent to a capability of the wireless communication device. The capability of the wireless communication device may be that the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks.

[0118] The list transmitted to the wireless communication device may be formatted so as to be interpreted by the wireless communication device only if the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks. A list formatted in such a way may be rejected by the wireless communication device if the wireless communication device is not capable of implementing a policy section for a plurality of wireless communication networks.

[0119] The message to initiate establishment of a policy association may be included transparently in the HTTP POST message.

[0120] The list received from the second network function may be sent to the wireless communication device transparent to the first network function.

[0121] The list may indicate that the one or more policy sections are valid for more than one wireless communication network.

[0122] The processor may be further configured to cause the first network function to receive a capability message from the wireless communications device, the capability message comprising an indication that the wireless communication device is capable to apply one or more policy sections for more than one wireless communication network. [0123] The message to initiate establishment of a policy association may be a UE STATE INDICATION message. The UE STATE INDICATION message may be as defined in 3GPP TS 24.501 vl8.1.0 titled “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0124] Figure 10 illustrates a method 1000 in a first network function, the method 1000 comprising: receiving 1010 a register request message from a wireless communication device, the register request message comprising a message to initiate establishment of a policy association; and parsing 1020 the register request message to obtain the message to initiate establishment of a policy association. The method further comprises transmitting 1030, to a second network function, an HTTP POST message comprising the message to initiate establishment of a policy association; receiving 1040, from the second network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to; and transmitting 1050 the list to the wireless communications device. [0125] In certain embodiments, the method 1000 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0126] The plurality of wireless communication networks may comprise a plurality of PLMNs. The first network function may be an AMF. The second network function may be a PCF.

[0127] The list transmitted to the wireless communication device may be formatted so as to be transparent to a capability of the wireless communication device. The capability of the wireless communication device may be that the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks.

[0128] The list transmitted to the wireless communication device may be formatted so as to be interpreted by the wireless communication device only if the wireless communication device is capable of implementing a policy section for a plurality of wireless communication networks. A list formatted in such a way may be rejected by the wireless communication device if the wireless communication device is not capable of implementing a policy section for a plurality of wireless communication networks.

[0129] The message to initiate establishment of a policy association may be included transparently in the HTTP POST message.

[0130] The list received from the second network function may be sent to the wireless communication device transparent to the first network function.

[0131] The list may indicate that the one or more policy sections are valid for more than one wireless communication network.

[0132] The method may further comprise receiving a capability message from the wireless communications device, the capability message comprising an indication that the wireless communication device is capable to apply one or more policy sections for more than one wireless communication network.

[0133] The message to initiate establishment of a policy association may be a UE STATE INDICATION message. The UE STATE INDICATION message may be as defined in 3GPP TS 24.501 vl8.1.0 titled “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0134] There is further provided a second network function, comprising a processor; and a memory coupled with the processor. The processor is configured to cause the second network function to: receive, from a first network function, an HTTP POST message comprising a message to initiate establishment of a policy association; and send, to the first network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to.

[0135] The plurality of wireless communication networks may comprise a plurality of PLMNs. The first network function may be an AMF. The second network function may be a PCF.

[0136] The message to initiate establishment of a policy association may be included transparently in the HTTP POST message.

[0137] The list may indicate that the one or more policy sections are valid for more than one wireless communication network.

[0138] The message to initiate establishment of a policy association may be a UE STATE INDICATION message. The UE STATE INDICATION message may be as defined in 3GPP TS 24.501 vl8.1.0 titled “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0139] Figure 11 illustrates a method 1100 in a second network function, the method 1100 comprising: receiving 1110, from a first network function, an HTTP POST message comprising a message to initiate establishment of a policy association; and sending 1120, to the first network function, a list comprising one or more policy sections, wherein the one more policy sections are valid for a plurality of wireless communication networks, the plurality of wireless communication networks including a wireless communication network that the wireless communication device is registered to.

[0140] In certain embodiments, the method 1100 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0141] The plurality of wireless communication networks may comprise a plurality of PLMNs. The first network function may be an AMF. The second network function may be a PCF.

[0142] The message to initiate establishment of a policy association may be included transparently in the HTTP POST message.

[0143] The list may indicate that the one or more policy sections are valid for more than one wireless communication network. The message to initiate establishment of a policy association may be a UE STATE INDICATION message. The UE STATE INDICATION message may be as defined in 3GPP TS 24.501 vl8.1.0 titled “Non- Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0144] Currently URSP rules are provided only by the HPLMN and the UE applies the same URSP rules in any PLMN that the UE registers to. This creates issues in case, when a UE is roaming, the VPLMN operator may require a specific traffic routing handling of a specific application. In addition, there are scenarios where a VPLMN operator cannot interface with the HPLMN (e.g. in case a UE registers in an SNPN with credentials from the HPLMN).

[0145] The HPLMN may indicate to the UE from which PLMNs the UE can use UE policies from the home PLMN by providing a mapping of policy sections to PLMN id (the PCF the PLMN provisions to the UE, UE policies in policy section identified by a policy section identifier where each policy section contains URSP rules.) However, currently there are no details on how the PLMN provisions such mapping information to the UE.

[0146] There are presented herein additional enhancements to solve the following issues:

• Provides a method for the PCF to be aware on per UE basis of the mapping of policy section identifier to a PLMN;

• Provides a method to encode the mapping of policy section identifier to PLMN within provisioned UE policies.

[0147] Accordingly, there is provided a new encoding of UE policy part of the Instruction information element, which does not require that: the UE exchanges capability information with the PCF; and the PCF indicates the new encoding is employed, however, the encoding causes a repetitiveness in the transmitted information. [0148] There is further provided a new encoding of the UE policy part of the Instruction information element, which requires that: the UE exchanges capability information with the PCF; and the PCF indicates the new encoding is employed, the encoding avoids any repetitiveness in the transmitted information.

[0149] There is provided herein a method comprising: constructing by a device, a message to initiate establishment of a policy association, wherein the message is included in a register request message; transmitted by the device to a first network entity the register request message, wherein the first network entity parses the register request message to obtain the message and then includes the message transparently to its contents to an HTTP POST message; transmitted by the first network entity to a second network entity, the HTTP POST message comprising the message; constructing by the second network entity a list, the list comprising one or more policy sections, wherein the one more policy sections are valid for more than one PTMN wherein the device is registered to; and transmitting by the second network entity to the device via the first network entity the list, wherein the list is transparent to the first network entity.

[0150] The second network entity may indicate to the device that the one or more policy sections are valid for more than one PTMN in order to that the device can interpret the one or more policy sections.

[0151] the device may indicate to the network its capability for getting one or more policy sections for more than one PTMN.

[0152] The first network entity may be an AMF. The second network entity may be a PCF. The message may be a UE STATE INDICATION message as defined in 3GPP TS 24.501 V18.1.0.

[0153] It should be noted that the above-mentioned methods and apparatus illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.

[0154] Further, while examples have been given in the context of particular communication standards, these examples are not intended to be the limit of the communication standards to which the disclosed method and apparatus may be applied. For example, while specific examples have been given in the context of 3GPP, the principles disclosed herein can also be applied to another wireless communication system, and indeed any communication system which uses routing rules.

[0155] The method may also be embodied in a set of instructions, stored on a computer readable medium, which when loaded into a computer processor, Digital Signal Processor (DSP) or similar, causes the processor to carry out the hereinbefore described methods.

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

[0157] The following abbreviations are relevant in the field addressed by this document: 5GCN, 5G Core Network; 5GS, 5G System; AMF, Access and Mobility Management Function; ANDSP, Access Network Discovery and Selection Policy; API, Application Programming Interface; APN, Access Point Name; BRID, Broadcast Remote Identification; BVLOS, Beyond Visual Line of Sight; C2, Command and Control; CAA, Civil Aviation Administration; DCN, Dedicated Core Network; DNN, Data Network Name; DNS, Domain Name System; ePDG, evolved Packet Data Gateway; ePCO, Extended Protocol Configuration Options; EPS, Evolved Packet System; ER-NSSAI, Extended rejected NSSAI ; E-UTRA, Evolved Universal Terrestrial Radio Access;

FQDN, Fully Qualified Domain Name; GUMMEI, Globally Unique Mobility Management Entity Identifier; GUTI, Globally Unique Temporary Identity; HPLMN, Home PLMN; HSS, Home Subscriber Server; IE, Information Element; IMSI, International Mobile Subscriber Identity; IP, Internet Protocol; LADN, Local Area Data Network; LCS, LoCation Services ; MCC, Mobile Country Code; MNC, Mobile Network Code; N3AN, Non-3GPP Access Network; N3IWF, Non-3GPP InterWorking Function; NEF, Network Exposure Function; NID, Network Identifier; OS, Operating System; OS Id, Operating System Identity; OS App Id, Operating System Application Identity; PCF, Policy Control Function; PCO, Protocol Configuration Options; PDN, Packet Data Network; PDN GW, PDN Gateway; PDU, Protocol Data Unit; PGW, PDN GW; PLMN, Public Land Mobile Network; PLMN ID, Public Land Mobile Network identity; ProSe, Proximity Services; ProSeP, ProSe Policy; PTI, Procedure Transaction Identity; MCC, Mobile Country Code; MME, Mobility Management Entity; MNC, Mobile Network Code; NF, Network Function; NID, Network Identifier; NRID, Networked Remote Identification; NSAC, Network Slice Admission Control; NSSF, Network Slice Selection Function; PTI, Procedure Transaction Identity; P-TMSI, Packet Temporary Mobile Subscriber Identity; RAI, Routing Area Identity; RID, Remote Identification; SWG, Serving Gateway; SMF, Session and Mobility Management Function; SM-PCO , Session Management PCO; SNPN, Standalone Non-Public Network; S-NSSAI, Single Network Slice Selection Assistance Information; SSC, Session and Service Continuity; SSID, Service Set Identifier; SUCI, Subscription Concealed Identifier; SUPI, Subscription Permanent Identifier; TA, Tracking Area; TAI, Tracking Area Identity; TAU, Tracking Area Update; TEID, Tunnel Endpoint Identifier; TNAN, Trusted Non-3GPP -Access-Network; TNAP, Trusted Non-3GPP Access Network;

TNGF, Trusted Non-3GPP Gateway Function; TPAE, Third Party Authorized Entity;

UAS, Uncrewed Aerial System; UAS NF, Uncrewed Aerial System Network Function; UAV, Uncrewed Aerial Vehicle; UAV-C, Uncrewed Aerial Vehicle Controller; UDM, Unified Data Management; UDR, Unified Data Repository; UE, User Equipment;

UPDS, UE policy delivery service; UPSC, UE Policy Section Code; UPSI, UE Policy

Section Identifier; URSP, UE Route Selection Policy; USIM, Universal Subscriber

Identity Module; USS, UAS Service Supplier; UTM, Uncrewed Aerial System Traffic Management; UUAA, USS UAV Authorization/ Authentication; UUID, Universal

Unique Identifier; V2X, Vehicle to Everything; V2XP, V2X Policy; and WEANSP, Wireless Location Area Network Selection Policy.