WO2024088586A1

WO2024088586A1 - Policy section requests in a wireless communication network

Info

Publication number: WO2024088586A1
Application number: PCT/EP2023/057705
Authority: WO
Inventors: Roozbeh Atarius; Dimitrios Karampatsis
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2023-02-06
Filing date: 2023-03-24
Publication date: 2024-05-02
Anticipated expiration: 2025-08-06

Abstract

There is provided herein a method in a first network node, the method comprising: receiving a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determining, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmitting to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

Description

POLICY SECTION REQUESTS IN A

WIRELESS COMMUNICATION NETWORK

Field

[0001] The subject matter disclosed herein relates generally to the field of implementing policy section requests in a wireless communication network. This document defines a first network node for wireless communication, a method in a first network node, a wireless communication device, and a method in a wireless communication device.

Introduction

[0002] At the time of 5GS registration, a UE receives UE policy sections by performing a UE-initiated UE state indication procedure according to 3GPP TS 24.501 vl8.1.0: “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”.

[0003] 3GPP TS 24.501 vl8.1.0 specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for both: mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.

[0004] The 5GS session management (5GSM) protocol defined in to 3GPP TS 24.501 vl8.1.0 provides procedures for the handling of 5GS PDU sessions. Together with the bearer control provided by the access stratum, this protocol is used for the control of user-plane resources. Further, procedures in the 5GS are specified for UE policy delivery service between the UE and the policy control function (PCF) for both 3GPP access and non-3GPP access.

Summary

[0005] During a UE-initiated UE state indication procedure, the UE is meant to send some information elements towards the PCF, but the UE may not have any knowledge about some of those information elements. The above-described procedure for the UE- initiated UE state indication can be modified by making transmitting those information elements optional. However, such a modification creates a problem that this is then not backward compatible with legacy systems. [0006] Disclosed herein are procedures for policy section requests in a wireless communication network. Said procedures may be implemented by a first network node for wireless communication, a method in a first network node, a wireless communication device, and a method in a wireless communication device.

[0007] There is provided herein a first network node for wireless communication, the first network node comprising a processor and a memory coupled with the processor, the processor configured to cause the first network node to: receive a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determine, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmit to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0008] Where a wireless communication device registers to a wireless communication system upon selection of a wireless communication network, the wireless communication device uses a specific value for the mandatory information element, wherein that value has not been assigned by the first network node to the wireless communication device. This is the first value, and is a value selected by the wireless communication device node. In certain implementations the wireless communication device may use a “dummy” value or “zero” value, such that the binary encoding is a dummy value.

[0009] There is further provided a method in a first network node, the method comprising: receiving a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determining, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmitting to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0010] There is further provided a wireless communication device comprising a processor, and a memory coupled with the processor, the processor configured to cause the wireless communication device to: transmit to a first network node a first message to establish a policy association for the wireless communication device, wherein the first message comprises: a first identity; and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device node. The processor is further configured to cause the wireless communication device to receive from the first network node a second message, wherein the second message comprises a second identity, at least one policy section and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0011] There is further provided a method in a wireless communication device, the method comprising transmitting to a first network node a first message to establish a policy association for the wireless communication device, wherein the first message comprises: a first identity; and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device node. The method further comprises receiving from the first network node a second message, wherein the second message comprises a second identity, at least one policy section and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

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 policy section requests in a wireless communication network will now be described, byway of example only, with reference to the accompanying drawings, in which:

Figure 1 depicts an embodiment of a wireless communication system for policy section requests in a wireless communication network;

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

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

Figure 4 is a messaging diagram illustrating a method presented herein;

Figure 5 illustrates a UE policy section management list information element for a PLMN;

Figure 6 illustrates a process by which a UE may register to the 5GS on a selected SNPN by using a non-3GPP access network;

Figure 7 illustrates a UE policy section management list information element for SNPN;

Figure 8 illustrates a further example of UE registration;

Figure 9 illustrates a method in a first network node;

Figure 10 illustrates a method where the first policy section code is associated with one or more policy sections;

Figure 11 illustrates a method in a wireless communication device; and

Figure 12 illustrates a method in a wireless communication device where the first policy section code may be one of one or more policy section codes which are associated with one or more policy sections.

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 policy section requests in a wireless communication network. 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.

[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, Sigfoxx, 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 remote unit 102 and/ or a UE 410, 610, 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 base unit 104 and/ or a PCF 460, 630, 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] At the time 5GS registration, the UE gets the UE policy sections by performing the UE-initiated UE state indication procedure according to 3GPP TS 24.501 vl8.1.0. During the UE-initiated UE state indication procedure, the UE must send some information elements towards the PCF, however the UE may not have any knowledge about some of those information elements. The procedure for the UE-initiated UE state indication can be modified by making transmitting those information elements optionally and when the UE has knowledge for them. However, this method is not backward compatible with legacy systems. There is presented herein a revised procedure for policy section requests in a wireless communication network that addresses this problem.

[0058] The UE-initiated UE state indication procedure is, in general, used for the purpose of: delivering to the PCF the UPSI(s) of the UE policy section(s); indicating to the PCF whether the UE supports ANDSP; and delivering to the PCF the UE's one or more OS Ids.

[0059] The UE policy section(s) which are: identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN, and stored in the UE, if any; or identified by a UPSI with the PLMN ID part indicating the PLMN ID part of the SNPN identity of the selected SNPN and associated with the NID of the selected SNPN, and stored in the UE, if any.

[0060] The UE creates a UE STATE INDICATION message as defined in 3GPP TS 24.501 vl8.1.0, where the UE:

• shall allocate a PTI value currently not used and set the PTI IE to the allocated PTI value;

• if not operating in SNPN access operation mode, shall include the UPSI(s) of the UE policy section(s) which are identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN available in the UE in the UPSI list IE;

• if operating in SNPN access operation mode, shall include UPSI(s) of the UE policy section(s) which are identified by a UPSI;

• shall specify whether the UE supports ANDSP in the UE policy classmark IE; and

• may include the UE's one or more OS IDs in the UE OS Id IE. [0061] The UE policy section(s) are identified by a UPSI: with the PLMN ID part indicating the MCC and MNC of the selected SNPN; associated with the NID of the selected SNPN; and available in the UE in the UPSI list IE.

[0062] The UE shall send the UE STATE INDICATION message to the PCF (see example in figure D.2.2.2.1 in 3GPP TS 24.501 vl8.1.0). It should further be noted that the UE shall transport the created UE STATE INDICATION message using the registration procedure described in subclause 5.5.1 of 3GPP TS 24.501 vl8.1.0.

[0063] The UE STATE INDICATION message is defined according to table D.5.4.1.1 in 3GPP TS 24.501 vl8.1.0 reproduced as table 1 below.

Table 1: UE STATE INDICATION message content

[0064] The contents of the UE STATE INDICATION message contain:

• The mandatory UPSI list information element comprises a set of UPSI sublists; each for a PLMN with related one or more UPSCs.

• The mandatory UE policy classmark information element provides the network with information about the policy aspects of the UE and is currently only the support of ANDSP by the UE.

• The optional UE OS Id information element provides the network with information about the one or more OSs of the UE.

[0065] Although the UPSI list information element is mandatory, the UE may not be able to include it in the UE STATE INDICATION message for examples in the cases when the UE is within a PLMN and is not aware of the assigned one or more UPSCc which are related to that PLMN. [0066] If the UE does not have any UPSI list to report, there have been two solutions to resolve what the UE should do:

[0067] Solution 1 is based on limiting the UPSI list information element to 3 octets by indicating that the length of this information is zero. Thus, the UE constructs the UE STATE INDICATION message with the UPSI list IE containing zero UPSI sublist. Since this shall be considered by the PCF a synthetic error, as the result the PCF either ignores the UE STATE INDICATION message or attempts to resolve the UE STATE INDICATION message. This is due to the following procedure quoted from clause D.8.5.1 in 3GPP TS 24.501 vl8.1.0, which specifies how the network shall proceed in the event that a message is received containing a syntactically incorrect mandatory information element (IE). However, it has been noted that this is a stretch of the term syntactically error. In addition, even if the PCF considers this as a synthetic error and does not take action in respect of it, the UE will not receive any UE policy section(s) even if the UE is due for that information.

Excerpt from clause D.8.5.1 of 3GPP TS 24.501 vl8.1.0

[0068] Solution 2 is based on creating a new message which does not include UPSI list information element. The message is called the SHORT UE STATE INDICATION message and is defined as the following table in CR#4693 against 3GPP TS 24.501 vl8.0.1.

Table 2: SHORT UE STATE INDICATION message content

[0069] Legacy PCF ignores the new SHORT UE STATE INDICATON message due to the rule stated in clause D.8.4 in 3GPP TS 24.501 vl8.1.0, reproduced below and which specifies that UPDS messages shall be ignored if they have either a message type not defined for the UPDS or are not implemented by the receiver. However, this solution 2 is considered too complex for practical implementation. In addition, if the UE is within a PLMN/SNPN with legacy PCF, the UE will not receive any UE policy section(s) even if the UE requires, and/ or is due to receive that information.

Excerpt from clause D.8.4 of 3GPP TS 24.501 v!8.1.0 [0070] Figure 4 is a messaging diagram illustrating a first example presented herein. Figure 4 shows a method 400 being performed by a User Equipment (UE) 410, an Access and Mobility Management Function (AMF) 420, a Policy Control Function (PCF) 430 and a Unified Data Repository (UDR) 440. In this first example, the UE registers to the 5GS on a selected PLMN which may be HPLMN. The UE may have been assigned UPSCs for one or more PLMNs (including HPLMN) by the PCF. However, if the UE is assigned any UPSC, the UE may not know the value for that UPSC, but the value is known the PCF locally or stored in the UDR which the PCF can have access to. As such the UE, which is not aware of the values of one or more UPSCs may operate as follows. [0071] The process 400 begins at 471, where the UE 410, during registration to 5GS on the selected PLMN which may be HPLMN, performs the UE initiated state indication procedure by including the UE STATE INDICATION message. For the UPSI list, the UE includes PLMN ID for the selected PLMN. The UE has currently registered to the 5GS in the selected PLMN which may be HPLMN, and the UE does not have the information for the one or more UPSCs for that PLMN which was selected for the 5GS registration and any other PLMN. Therefore, the UE uses:

• a value which may be zero;

• a value which may have been assigned by the UE's operator subscriber that the UE may be able to use when/if the UE is not aware of the one or more UPCSs of any PLMN including the selected PLMN for registration; or

• any value.

[0072] The reason for being able to use any value is that the PCF 430 will check any value for the one or more UPSCs and if they are not associated with the UE policy sections, then they are replaced by the new values for UPSCs which are associated with the UE policy sections which will be provided to the UE 410 as described below in step 474. The PCF will also transmit the one or more UPSCs to the UE with associated “empty” UE policy sections to indicate to the UE that the one or more UPSCs are not valid and should be deleted from the UE.

[0073] At 472, the AMF 420 requests the PCF 430 to establish the UE policy association as described in 3GPP TS 29.525 vl 8.0.0 “5G System; UE Policy Control Service; Stage 3”, where the PCF 430 uses the received information comprised within the UE STATE INDICATION message to establish the UE policy association. The PCF 430 matches the received UPSCs in the UE STATE INDICATION message to the related UE policy sections corresponding to the PLMN or HPLMN. The PCF 430 may realize that the received UPSCs need to be updated by transmitting new UE policy sections and the related UPSCs due to:

• the UE’s subscription;

• the assigned values by the UE; or

• both of the above.

[0074] At 473, the UE policy sections and the related UPSCs may have been previously stored in the UDR 430 and not available locally. The PCF 420 may therefore retrieve UE policy sections from UDR 430 the previously stored information in UDR 430 as specified in 3GPP TS 29.519 vl8.0.0 “5G System; Usage of the Unified Data Repository service for Policy Data, Application Data and Structured Data for Exposure; Stage 3”. [0075] At 474, the PCF 430 uses Namf_Communication_NlN2MessageTransfer service operation defined in clause 5.2.2.3.1 of 3GPP TS 29.518 vl8.0.0: “5G System; Access and Mobility Management Services; Stage 3” to send the MANAGE UE POLICY COMMAND message, defined in clause D.5.1.1 of 3GPP TS 24.501 vl8.1.0, comprising the UE policy sections and the related UPSCs for one or more PLMNs including HPLMN to the UE 410. If the chosen values for the one or UPSCs which the UE 410 used in step 471, are not associated with any UE policy sections, the UE policy sections associated with those one or more UPSCs are set to empty to indicate to the UE that it should eliminate the UE policy sections associated with those one or more UPSCs.

[0076] Figure 5 illustrates a UE policy section management list information element 500 for a PLMN. Specifically, figure 5 illustrates a UE policy section management list information element which is contained by the “MANAGE UE POLICY COMMAND” message and which is used for transmitting the UE policy sections and the related UPSCs for the one or more PLMNs.

[0077] The UE policy section management list information element 500 comprises a length of UE policy section management list contents 501 and a UE policy section management list contents 502. The UE policy section management list contents 502 comprises N UE policy section management sublists, including a first UE policy section management sublist 511, a second UE policy section management sublist 512. Each UE policy section management sublist (511, 512, etc.) comprises a length of UE policy section management sub list 521, a plurality of MCC and MNC digits 522, and a UE policy section management sublist contents 526. The UE policy section management sublist contents 526 comprises M instructions, including a first instruction 531 and a second instruction 532. Each instruction (531, 532, etc.) comprises an instruction contents length 541, a USPC 542, and a UE policy section contents 543. The UE policy section contents 543 comprises Q UE policy sections, including a first UE policy section 551 and a second UE policy section 552. Each UE policy section (551, 552, etc.) comprises a UE policy section contents length 561, a spare field 562, a UE policy section type 563, and a UE policy section contents 564. It should be noted that in some documents a UE policy section is referred to as a UE policy part.

[0078] Example 1 illustrated in figure 4 concerns a UE registering to the 5GS on a selected PLMN. For completeness, figure 6 illustrates a process 600 by which a UE may register to the 5GS on a selected SNPN by using a non-3GPP access network. The procedure for the registration to 5GS is similar to the illustration in Figure 4 with the difference that the PCF now of the SNPN instead of the PLMN or HPLMN. Figure 6 shows the method 600 being performed by a User Equipment (UE) 610, an Access and Mobility Management Function (AMF) 620, a Policy Control Function (PCF) 630 and a Unified Data Repository (UDR) 640.

[0079] At 671, the UE 610 during the registration to 5GS on the selected SNPN, performs the UE-requested UE initiated state indication procedure by including the UE STATE INDICATION message. For the UPSI list, the UE 610 includes PLMN ID and NID for the selected SNPN. Since the UE 610 has currently to the 5GS in the selected an SNPN and the UE 610 does not have the information for the one or more UPSCs for that SNPN which was selected for the 5GS registration or any other SNPN/PLMN. Therefore, the UE 610 uses: a value which may be zero; a value which may have been assigned by the UE's operator subscriber that the UE 610 may be able to use when/if the UE 610 is not aware of the one or more UPCSs of any SNPN/PLMN including the selected SNPN for registration; or any value. The value may be randomly selected. The value may be determined by the UE, or predetermined.

[0080] The reason for being able to use any value is that the PCF 630 will check any value for the one or more UPSCs and if they are not associated with the UE policy sections, then they are replaced by the new values for UPSCs which are associated with the UE policy sections which will be provided to the UE as described in step 674.

[0081] At 672, the AMF 620 sends a request to the PCF 630, the request asking to establish the UE policy association as described in 3GPP TS 29.525 vl8.0.0, where the PCF 630 uses the received information comprised within the UE STATE INDICATION message to establish the UE policy association. The PCF 630 matches the received UPSCs in the UE STATE INDICATION message to the related UE policy sections corresponding to the SNPN. The PCF 630 may determine that the received UPSCs need to be updated by transmitting new UE policy sections and the related UPSCs. The PCF 630 may make such a determination based on the UE’s subscription; the values assigned by the UE; or both.

[0082] At 673, the UE policy sections and the related UPSCs may have been previously stored in the UDR 640 and not available locally. The PCF 630 may therefore retrieve UE policy sections from UDR 640 the previously stored information in UDR 640 as specified in 3GPP TS 29.519 vl8.0.0.

[0083] At 674, the PCF 630 uses Namf_Communication_NlN2MessageTransfer service operation defined in clause 5.2.2.3.1 of 3GPP TS 29.518 vl8.0.0 to send the MANAGE UE POLICY COMMAND message, defined in clause D.5.1.1 of 3GPP TS 24.501 vl8.1.0, comprising the UE policy sections and the related UPSCs for one or more SNPNs to the UE. If the chosen values for the one or UPSCs which the UE used in step 671, are not associated with any UE policy sections, the UE policy sections associated with those one or more UPSCs are set to empty to indicate to the UE that those one or more UPSCs need to be eliminated.

[0084] Figure 7 illustrates a UE policy section management list information element for SNPN. Specifically, figure 7 illustrates UE policy section management list information element which is contained by the MANAGE UE POLICY COMMAND" message and that is used for transmitting the UE policy sections and the related UPSCs for the one or more SNPNs.

[0085] The UE policy section management list information element 700 comprises a length of UE policy section management list contents 701 and a UE policy section management list contents 702. The UE policy section management list contents 702 comprises N UE policy section management sublists, including a first UE policy section management sublist 711, a second UE policy section management sublist 712. Each UE policy section management sublist (711, 712, etc.) comprises a length of UE policy section management sublist 721, a plurality of MCC and MNC digits 722, and a UE policy section management sublist contents 726. The UE policy section management sublist contents 726 comprises M instructions, including a first instruction 731 and a second instruction 732. Each instruction (731, 732, etc.) comprises an instruction contents length 741, a USPC 742, and a UE policy section contents 743. The UE policy section contents 743 comprises Q UE policy sections, including a first UE policy section 751 and a second UE policy section 752. Each UE policy section (751, 752, etc.) comprises a UE policy section contents length 761, a spare field 762, a UE policy section type 763, and a UE policy section contents 764. It should be noted that in some documents a UE policy section is referred to as a UE policy part.

[0086] A third example of UE registration is illustrated in Figure 8. Figure 8 shows the method 800 being performed by a User Equipment (UE) 810, an Access and Mobility Management Function (AMF) 820, a Policy Control Function (PCF) 830 and a Unified Data Repository (UDR) 8640. Figure 8 illustrates a process 800 that is implemented when the selected values for the one or more UPSCs used by the UE when performing the UE-requested UE initiated state indication procedure happen to be associated with one or more UE policy sections attributed to the UE. Although unlikely, it is possible that the ‘dummy’ value sent by the UE corresponds to a policy section attributed to the UE. Therefore, in reply from the PCF the UE does not receive an empty UE policy section for the one or more UPSCs of the dummy value. The UE therefore realizes that there are UE policy sections associated with those selected values for the one or more UPSCs and that the UE does not have those. In order to obtain those UE policy sections, the UE re-performs the UE-requested UE initiated state indication procedure by initiating the mobility and periodic registration procedure described in

3GPP TS 24.501 vl8.1.0 and including the UE STATE INDICATION message as shown in Figure 8.

[0087] Steps 871 to 874 correspond to steps 471 to 474 as described above with reference to figure 4 and also steps 671 to 674 as described above with reference to figure 6.

[0088] At 875, the UE 810 attempts to get the UE policy sections associated with the selected values for the one or more UPSCs used by initiating the UE mobility and periodic registration and including the UE STATE INDICATION message. The UPSI list IE comprises PLMN ID or SNPN ID depending on if the UE is registered to 5GS via selected PLMN or SNPN, respectively and:

• received associated UPSCs for the PLMN or SNPN during the registration described in connection with figures 4 and 6; but

• NOT the selected values for the one or more UPCSs used by the UE-requested UE initiated state indication procedure (as illustrated in connection with figures 4 and 6).

[0089] At 876, upon establishment of the UE policy association, the PCF 830 retrieves locally or from UDR 840 as the previously stored information in UDR 840 as specified in 3GPP TS 29.519 vl 8.0.0, the UE policy sections associated with the one or more UPSCs used by the UE-requested UE 810 initiated state indication procedure as explained in connection with figures 4 and 6 above. The PCF 830 uses Namf_Communication_NlN2MessageTransfer service operation defined in clause 5.2.2.3.1 of 3GPP TS 29.518 vl8.0.0 to send the MANAGE UE POLICY COMMAND message, defined in clause D.5.1.1 of 3GPP TS 24.501 vl8.1.0, comprising the UE policy sections and the one or more UPSCs used by the UE-requested UE initiated state indication procedure described above in connection with figures 4 and 6. [0090] In the case when the UE 810 has UE policy section associated with only one UPSC which happens to be the selected value for the UPCS used by the UE-requested UE initiated state indication procedure described above in connection with figures 4 and 6, the PCF 830 may not transmit any UE policy section associated with that selected value for the UPSC. In this case the UE 810 may proceed with step 875 by using another arbitrary value to associate with the UE policy sections. In an alternative the UE may use the received UPSCs which associate with the received UE policy sections as the outcome of the first UE-requested UE initiated state indication procedure.

[0091] The PCF 830 will then, at step 876, transmit the UE policy sections and the associated value for the UPSC which was the selected value (selected by the UE) for the UPCS used by the UE-requested UE initiated state indication procedure described above in connection with figures 4 and 6.

[0092] There is provided herein a first network node for wireless communication, the first network node comprising a processor and a memory coupled with the processor, the processor configured to cause the first network node to: receive a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determine, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmit to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0093] Transmitting the second message to the wireless communication device may comprise the first network node sending the second message via the second network node. The wireless communication device may send the first message to a second network node, and the second network node may forward the first message to the first network node. The first network node may comprise a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). The first policy section code may comprise a first binary code. The first policy section code may comprise a UE Policy Section Code (UPSC). The policies available for the wireless communication device may be determined from a from a third network node or based on subscription information for the wireless communication device. The policy may be a policy for the wireless communication device. Where the wireless communication device is a UE the policy may be a UE policy. The policy may comprise a UE route selection policy (URSP). The policy may comprise an Access Network Discovery and Selection Policy (ANDSP).

[0094] Where a wireless communication device registers to a wireless communication system upon selection of a wireless communication network, the wireless communication device uses a specific value for the mandatory information element, wherein that value has not been assigned by the first network node to the wireless communication device. This is the first value, and is a value selected by the wireless communication device node. In certain implementations the wireless communication device may use a “dummy” value or “zero” value, such that the binary encoding is a dummy value.

[0095] The value selected by the wireless communication device may be a dummy value. The value selected by the wireless communication device is provided so as to comply with the message format that the wireless communication device is expected to send. The value selected by the wireless communication device is likely to be a value not adopted by the network node. However, there is a slim chance that the selected value, the dummy value, has been adopted by the network node. The selected value may be randomly selected. The random selection may be performed every time a selected value is needed. The random selection may be performed in advance and the selected value preset. The selected value may be predefined. The selected value may be zero.

[0096] In the specific example of a UE registering with a 5GS: upon selection of a PLMN, the UE uses a specific value for the mandatory IE, wherein that value has not been assigned by the PCF to the UE. This is the first value, and is a value selected by the wireless communication device node. In certain implementations the UE may use a “dummy” value or “zero” value, such that both the PLMN ID and the UPSC are dummy values. Similarly, where a UE registers to the 5GS upon selection of an SNPN, the UE uses a specific value for the mandatory IE, wherein that value has not been assigned by the PCF to the UE. Again, this is the first value, and is a value selected by the wireless communication device node. In certain implementations the UE may use a “dummy” value or “zero” value, such that the UPSC are dummy values.

[0097] The respective policy section code(s) in the second message are different to the first policy section code carried in the first message.

[0098] The first policy section code may not be associated with one or more policy sections. The first value may be predefined.

[0099] However, the first policy section code may be associated with one or more policy sections, and the processor may be further configured to cause the first network node to: receive a third message from the wireless communication device, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node; determine that the wireless communication device requires additional policy section codes associated with the first identity; and transmit a fourth message to the wireless communication device, wherein the fourth message comprises at least the first identity and at least one policy section, and a policy section code for each of the at least one policy section, wherein one or more policy sections of the at least one policy section transmitted in the fourth message are associated with the first identity.

[0100] If the chosen value (the ‘dummy’ or the first value which is a value selected by the wireless communication device node) is not actually assigned to the wireless communication device by the first network node, the first network node, upon establishment of the wireless communication device policy association, transmits wireless communication device policy sections wherein, one of them comprises the policy selection code set to that value (dummy) in addition to empty policy section to indicate to the wireless communication device that that policy selection code (dummy) should not be considered as an assigned policy selection code and related wireless communication device policy section should be eliminated by the wireless communication device. This is what the wireless communication device excepts to receive. [0101] However, the wireless communication device selects the first value without knowing what values are adopted by the network node. Accordingly, there is a slight chance that the first value of the policy selection code selected as a dummy by the wireless communication device happens to be in fact a policy section code assigned to the wireless communication device by the first network node. In that case the wireless communication device will NOT receive any wireless communication device policy section associating with that policy selection code. Therefore, not receiving that policy selection code (dummy) should be considered by the wireless communication device as an indication that there is an associated wireless communication device policy section associated with that policy selection code (dummy) which the wireless communication device does not have. In order for the wireless communication device to get the associated wireless communication device policy section, the wireless communication device needs to yet again send the message (UE STATE INDICATION message) as a third message by performing the periodic registration to the network, but this time, the wireless communication device includes all the received policy selection codes that it received in the first registration. In this case the wireless communication device will only receive the associated policy section associated with the dummy policy selection code, where the dummy policy selection code selected by the wireless communication device happens to have been one that was assigned to the wireless communication device by the first network node. Such a mechanism saves bandwidth by eliminating repetitive information yet still ensuring the missing wireless communication device policy section is delivered to the wireless communication device.

[0102] In the specific example of a UE registering with a PCF: if the chosen value (the ‘dummy’ or the first value which is a value selected by the wireless communication device node) is not actually assigned to the UE by the PCF, the PCF, upon establishment of the UE policy association, transmits UE policy sections, wherein one of them is an empty UE policy section and is associated with the UPSC set to that value (dummy). Including the dummy USPC value indicates to the UE that the UPSC (dummy) should not be considered an assigned UPSC and that any related UE policy section should be eliminated by the UE. This is what the UE excepts to receive.

[0103] However, the UE selects the first value without knowing what values are adopted by the network node. Accordingly, there is a slight chance that the first value of the UPSC selected as a dummy by the UE happens to be in fact a UPSC assigned to the UE by the PCF. In that case the UE will NOT receive any UE policy section which is associated with that UPSC. Therefore, not receiving that UPSC (dummy) is considered by the UE to indicate that there is at least one associated UE policy section associated with that UPSC (dummy) which the UE did not receive in the second message and therefore the UE does not have it. In order for the UE to get the associated UE policy section, the UE needs to again send the message (UE STATE INDICATION message) as a third message by performing the periodic registration to the network, but this time, the UE includes all the received UPSCs that it received in the second message during the first registration. Transmitting all the received UPSCs received in the second message means that the UE will only receive the associated policy section with the dummy UPSC, rather than receiving again any of those received UPSCs and the associated policy section (thus avoiding transmission of information which already was received in the second message). Such a mechanism saves bandwidth by eliminating repetitive information yet still ensuring the missing UE policy section associated with the dummy UPSC is delivered to the UE.

[0104] Determining that the wireless communication device requires additional policy section codes associated with the first identity comprises the first network node determining that the wireless communication device requires updated policies. Each policy section contains one or more policies.

[0105] The policy section code transmitted in the second message may be associated with a policy section transmitted by the first network node to the wireless communication device. The policy section codes may comprise UE Policy Section Codes (UPSC).

[0106] The first identity may be an identity of a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN).

[0107] The second identity may be an identity of a PLMN or an SNPN, and wherein the one or more policy sections in the second message may each be associated with a policy section code, and wherein the policy section transmitted in the second message may be associated with one or more policy section codes transmitted by the first network node to the wireless communication device.

[0108] The first network node may be a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). There may also be a third network node. The third network node may comprise a Unified Data Repository (UDR). [0109] The first value may be: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

[0110] Figure 9 illustrates a method 900 in a first network node. 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. The method 900 comprises: receiving 910 a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determining 920, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmitting 930 to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0111] Transmitting the second message to the wireless communication device may comprise the first network node sending the second message via the second network node. The wireless communication device may send the first message to a second network node, and the second network node may forward the first message to the first network node. The first network node may comprise a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). The first policy section code may comprise a first binary code. The first policy section code may comprise a UE Policy Section Code (UPSC). The policies available for the wireless communication device may be determined from a from a third network node or based on subscription information for the wireless communication device. The policy may be a policy for the wireless communication device. Where the wireless communication device is a UE the policy may be a UE policy. The policy may comprise a UE route selection policy (URSP). The policy may comprise an Access Network Discovery and Selection Policy (ANDSP). [0112] Where a wireless communication device registers to a wireless communication system upon selection of a wireless communication network, the wireless communication device uses a specific value for the mandatory information element, wherein that value has not been assigned by the first network node to the wireless communication device. This is the first value, and is a value selected by the wireless communication device node. In certain implementations the wireless communication device may use a “dummy” value or “zero” value, such that the binary encoding is a dummy value.

[0113] The value selected by the wireless communication device may be a dummy value. The value selected by the wireless communication device is provided so as to comply with the message format that the wireless communication device is expected to send. The value selected by the wireless communication device is likely to be a value not adopted by the network node. However, there is a slim chance that the selected value, the dummy value, has been adopted by the network node. The selected value may be randomly selected. The random selection may be performed every time a selected value is needed. The random selection may be performed in advance and the selected value preset. The selected value may be predefined. The selected value may be zero.

[0114] In the specific example of a UE registering with a 5GS: upon selection of a PLMN, the UE uses a specific value for the mandatory IE, wherein that value has not been assigned by the PCF to the UE. This is the first value, and is a value selected by the wireless communication device node. In certain implementations the UE may use a “dummy” value or “zero” value, such that both the PLMN ID and the UPSC are dummy values. Similarly, where a UE registers to the 5GS upon selection of an SNPN, the UE uses a specific value for the mandatory IE, wherein that value has not been assigned by the PCF to the UE. Again, this is the first value, and is a value selected by the wireless communication device node. In certain implementations the UE may use a “dummy” value or “zero” value, such that the UPSC are dummy values.

[0115] The respective policy section code(s) in the second message are different to the first policy section code carried in the first message.

[0116] The first policy section code may not be associated with one or more policy sections. The first value may be predefined.

[0117] Figure 10 illustrates a method 1000 where the first policy section code is associated with one or more policy sections. 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. The method 1000 comprises steps 1010, 1020 and 1030 corresponding to steps 910, 920 and 930 above. The method 1000 further comprises receiving 1040 a third message from the wireless communication device, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node; determining 1050 that the wireless communication device requires additional policy section codes associated with the first identity; and transmitting 1060 a fourth message to the wireless communication device, wherein the fourth message comprises at least the first identity and at least one policy section, and a policy section code for each of the at least one policy section, wherein one or more policy sections of the at least one policy section transmitted in the fourth message are associated with the first identity.

[0118] If the chosen value (the ‘dummy’ or the first value which is a value selected by the wireless communication device node) is not actually assigned to the wireless communication device by the first network node, the first network node, upon establishment of the wireless communication device policy association, transmits wireless communication device policy sections wherein, one of them comprises the policy selection code set to that value (dummy) in addition to empty policy section to indicate to the wireless communication device that that policy selection code (dummy) should not be considered as an assigned policy selection code and related wireless communication device policy section should be eliminated by the wireless communication device. This is what the wireless communication device excepts to receive.

[0119] However, the wireless communication device selects the first value without knowing what values are adopted by the network node. Accordingly, there is a slight chance that the first value of the policy selection code selected as a dummy by the wireless communication device happens to be in fact a policy section code assigned to the wireless communication device by the first network node. In that case the wireless communication device will NOT receive any wireless communication device policy section associating with that policy selection code. Therefore, not receiving that policy selection code (dummy) should be considered by the wireless communication device as an indication that there is an associated wireless communication device policy section associated with that policy selection code (dummy) which the wireless communication device does not have. In order for the wireless communication device to get the associated wireless communication device policy section, the wireless communication device needs to yet again send the message (UE STATE INDICATION message) as a third message by performing the periodic registration to the network, but this time, the wireless communication device includes all the received policy selection codes that it received in the first registration. In this case the wireless communication device will only receive the associated policy section associated with the dummy policy selection code, where the dummy policy selection code selected by the wireless communication device happens to have been one that was assigned to the wireless communication device by the first network node. Such a mechanism saves bandwidth by eliminating repetitive information yet still ensuring the missing wireless communication device policy section is delivered to the wireless communication device.

[0120] In the specific example of a UE registering with a PCF: if the chosen value (the ‘dummy’ or the first value which is a value selected by the wireless communication device node) is not actually assigned to the UE by the PCF, the PCF, upon establishment of the UE policy association, transmits UE policy sections, wherein one of them is an empty UE policy section and is associated with the UPSC set to that value (dummy). Including the dummy USPC value indicates to the UE that the UPSC (dummy) should not be considered an assigned UPSC and that any related UE policy section should be eliminated by the UE. This is what the UE excepts to receive.

[0121] However, the UE selects the first value without knowing what values are adopted by the network node. Accordingly, there is a slight chance that the first value of the UPSC selected as a dummy by the UE happens to be in fact a UPSC assigned to the UE by the PCF. In that case the UE will NOT receive any UE policy section which is associated with that UPSC. Therefore, not receiving that UPSC (dummy) is considered by the UE to indicate that there is at least one associated UE policy section associated with that UPSC (dummy) which the UE did not receive in the second message and therefore the UE does not have it. In order for the UE to get the associated UE policy section, the UE needs to again send the message (UE STATE INDICATION message) as a third message by performing the periodic registration to the network, but this time, the UE includes all the received UPSCs that it received in the second message during the first registration. Transmitting all the received UPSCs received in the second message means that the UE will only receive the associated policy section with the dummy UPSC, rather than receiving again any of those received UPSCs and the associated policy section (thus avoiding transmission of information which already was received in the second message). Such a mechanism saves bandwidth by eliminating repetitive information yet still ensuring the missing UE policy section associated with the dummy UPSC is delivered to the UE.

[0122] There is a slight chance that the UE has only one assigned UPSC in the registered PLMN and that the UE, which does not know the assigned UPSC, has selected a value for the UPSC (a dummy value) which happens to be the assigned UPSC. In this case, the UE does not receive any policy section. The UE may in this case, send the message (UE STATE INDICATION message) as a third message by performing the periodic registration to the network, but this time, the UE includes another chosen value than the first chosen value for UPSC (a second dummy value which is different from the first dummy value) used during the first registration.

[0123] Generally, for the UE to minimize the chance that the chosen “dummy” value for the UPSC to be the same as a value assigned by the PLMN’s PCF, the UE may use several chosen values (dummy values) for UPSC and use them when performing the UE- initiated UE state indication procedure.

[0124] Determining that the wireless communication device requires additional policy section codes associated with the first identity comprises the first network node determining that the wireless communication device requires updated policies. Each policy section contains one or more policies.

[0125] The policy section code transmitted in the second message may be associated with a policy section transmitted by the first network node to the wireless communication device. The policy section codes may comprise UE Policy Section Codes (UPSC).

[0126] The first identity may be an identity of a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN).

[0127] The second identity may be an identity of a PLMN or an SNPN, and wherein the one or more policy sections in the second message are each associated with a policy section code, and wherein the policy section transmitted in the second message may be associated with one or more policy section codes transmitted by the first network node to the wireless communication device.

[0128] The first network node may be a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). There may also be a third network node. The third network node may comprise a Unified Data Repository (UDR). [0129] The first value may be: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

[0130] There is further provided a wireless communication device comprising a processor, and a memory coupled with the processor, the processor configured to cause the wireless communication device to: transmit to a first network node a first message to establish a policy association for the wireless communication device, wherein the first message comprises: a first identity; and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device node. The processor is further configured to cause the wireless communication device to receive from the first network node a second message, wherein the second message comprises a second identity, at least one policy section and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0131] Receiving the second message from the first network node may comprise the first network node sending the second message via a second network node. The wireless communication device may send the first message to the second network node, and the second network node may forward transparently the first message to the first network node. The first network node may comprise a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). [0132] It should be noted that the second message received from the first network node may comprise a plurality of policy sections, each policy section associated with a policy section code. The received policy section codes may each be different from the first policy section code. The value selected by the wireless communication device may be a value not set by a first network node.

[0133] The first policy section code may not be associated with any policy section associated with wireless communication device.

[0134] However, the first policy section code may be one of one or more policy section codes which are associated with one or more policy sections, the processor further configured to cause the wireless communication device to: transmit a third message to the first network node, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node; and receive a fourth message from the first network node, wherein the fourth message comprises at least the first identity, at least one policy section associated with the first identity, and a respective policy section code for each policy section associated with the first identity. Each policy section contains one or more policies.

[0135] The one or more policy sections transmitted in the second message may be associated with one or more policy sections transmitted by the first network node to the wireless communication device.

[0136] The first identity may be an identity of a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN).

[0137] The second identity may be an identity of a PLMN or an SNPN, and wherein the one or more policy section codes transmitted in the second message may be associated with one or more policy sections transmitted by the first network node to the device. [0138] The first network node may be a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). There may also be a third network node. The third network node may comprise a Unified Data Repository (UDR).

[0139] The first value may be: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

[0140] Figure 11 illustrates a method 1100 in a wireless communication device. 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. The method 1100 comprises transmitting 1110 to a first network node a first message to establish a policy association for the wireless communication device, wherein the first message comprises: a first identity; and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device node. The method further comprises receiving 1120 from the first network node a second message, wherein the second message comprises a second identity, at least one policy section and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

[0141] Receiving the second message from the first network node may comprise the first network node sending the second message via a second network node. The wireless communication device may send the first message to the second network node, and the second network node may forward transparently the first message to the first network node. The first network node may comprise a Policy Control Function (PCF). The second network node may be an Access and Mobility Management Function (AMF). [0142] It should be noted that the second message received from the first network node may comprise a plurality of policy sections, each policy section associated with a policy section code. The received policy section codes may each be different from the first policy section code.

[0143] The value selected by the wireless communication device node may be a value not set by a first network node. The first policy section code may not be associated with any policy section associated with wireless communication device.

[0144] Figure 12 illustrates a method 1200 n a wireless communication device where the first policy section code may be one of one or more policy section codes which are associated with one or more policy sections. The method 1200 comprises steps 1210 and 1220 corresponding to steps 1110 and 1120 of figure 11 described above. The method 1200 further comprises, transmitting 1230 a third message to the first network node, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node. The method 1200 further comprises, receiving 1240 a fourth message from the first network node, wherein the fourth message comprises at least the first identity, at least one policy section associated with the first identity, and a respective policy section code for each policy section associated with the first identity. Each policy section contains one or more policies.

[0145] The one or more policy sections transmitted in the second message may be associated with one or more policy sections transmitted by the first network node to the wireless communication device.

[0146] The first identity may be an identity of a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN). The second identity may be an identity of a PLMN or an SNPN, and wherein the one or more policy section codes transmitted in the second message may be associated with one or more policy sections transmitted by the first network node to the device.

[0147] The first network node may be a Policy Control Function (PCF); and the second network node may be an Access and Mobility Management Function (AMF). There may also be a third network node. The third network node may comprise a Unified Data Repository (UDR).

[0148] The first value may be: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

[0149] As described herein, if the UE is not aware of the UPSC associated with the UE policy section in a PLMN or an SNPN at the time of requesting the associated policy sections, the UE assigns a value to the UPSC. The received UE policy sections have associated UPSCs and the UE policy section associated with the assigned value must be empty, showing that the assigned value is not valid anymore. If this is not the case, then the assigned value happens to be associated with UE policy sections that have not been transmitted to the UE. The UE therefore requests once again UE policy sections but this time with only those UPSCs that the UE has received.

[0150] Advantageously, this means that the PCF transmits to the UE the UE policy sections which were associated with the assigned UPSCs. Further, the PCF does not retransmit the already transmitted UE policy sections associated with the received UPSCs, unless there has been a change in those UE policy sections from the previous transmission.

[0151] It should also be noted that if the PCF of an SNPN transmits the MANAGE UE POLICY COMMAND message comprising the UE policy section management list information element with the UE policy sections and the related UPSCs, the UE policy sections comprise the SNPN identity which the PLMN ID plus NID.

[0152] Accordingly, there is provided herein a method comprising: transmitting by a device to a second network entity transparently to a first network entity a first message type to establish a policy association for the device, wherein the first message type comprising a first list comprising: a first identity; and a first binary encoding, the first binary encoding is set to a first value wherein the first value is not set by the second network entity. The method further comprises establishing by the second network entity the policy association for the device; and transmitting by the second network entity to the device transparently to the first network entity, a second message type, wherein the second message type comprises a second list comprising at least: a second identity; and a second binary encoding, the second binary encoding is set to a second value, wherein the second value is set by the second network entity. [0153] The first value may be predefined and the first binary encoding may not be associated with one or more UE policy sections.

[0154] The method may further comprise transmitting by the device to the second network entity transparently to the first network entity, a second instance of the first message type to establish the policy association for the device, wherein the second instance of the first message type comprises the second list comprising: the second identity; and the second binary encoding. The method further comprises establishing by the second network entity the policy association for the device; and transmitting by the second network entity to the device transparently to the first network entity, a second instance of the second message type, wherein the second instance of the second message type comprises a second list comprising at least: the first identity; and one or more UE policy sections and the first binary encoding set to a first value.

[0155] The second value may be associated with one or more UE policy sections transmitted by the second network entity to the device.

[0156] The first identity may be the identity of a PLMN or an SNPN.

[0157] The second identity may be the identity of a PLMN or an SNPN, wherein the second binary encoding set to the second value, is associated with one or more UE policy sections transmitted by the second network entity to the device.

[0158] The first network entity may be an AMF. The second network entity may be a PCF. The third network entity may be a UDR.

[0159] The first value may be: zero; a non-zero value assigned by the operator that the device uses if the device is not aware any value for the first binary encoding; or any nonzero value.

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

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

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

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

[0164] 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; BVTOS, 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; ePCO, Extended Protocol Configuration Options; ePDG, evolved Packet Data Gateway; 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; MME, Mobility Management Entity; MNC, Mobile Network Code; N3AN, Non-3GPP Access Network; N3IWF, Non-3GPP InterWorking Function; NEF, Network Exposure Function; NF, Network Function; NID, Network Identifier; NRID, Networked Remote Identification; NSAC, Network Slice Admission Control; NSSF, Network Slice Selection Function; OS, Operating System; OS App Id, Operating System Application Identity; OS Id, Operating System 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; PTI, Procedure Transaction Identity; P-TMSI, Packet Temporary Mobile Subscriber Identity; RAI, Routing Area Identity; RID, Remote Identification; 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; SWG, Serving Gateway; TA, Tracking Area; TAI, Tracking Area Identity; 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; and WEANSP, Wireless Location Area Network Selection Policy.

Claims

1. A first network node for wireless communication, the first network node comprising: a processor; and a memory coupled with the processor, the processor configured to cause the first network node to: receive a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determine, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmit to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

2. The first network node of claim 1, the first policy section code is not associated with one or more policy sections.

The first value may be predefined.

3. The first network node of claim 1, wherein the first policy section code is associated with one or more policy sections, and wherein the processor is further configured to cause the first network node to: receive a third message from the wireless communication device, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node; determine that the wireless communication device requires additional policy section codes associated with the first identity; and transmit a fourth message to the wireless communication device, wherein the fourth message comprises at least the first identity and at least one policy section, and a policy section code for each of the at least one policy section, wherein one or more policy sections of the at least one policy section transmitted in the fourth message are associated with the first identity.

4. The first network node of any preceding claim, wherein the policy section code transmitted in the second message is associated with a policy section transmitted by the first network node to the wireless communication device.

5. The first network node of any preceding claim, wherein the first identity is an identity of a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN).

6. The first network node of any preceding claim, wherein the second identity is an identity of a PLMN or an SNPN, and wherein the one or more policy sections in the second message are each associated with a policy section code, and wherein the policy section transmitted in the second message is associated with one or more policy section codes transmitted by the first network node to the wireless communication device.

7. The first network node of any preceding claim, wherein: the first network node is a Policy Control Function (PCF); and the second network node is an Access and Mobility Management Function (AMF).

8. The first network node of any preceding claim, wherein the first value is: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

9. A method in a first network node, the method comprising: receiving a first message from a wireless communication device, the first message including a request to establish a policy association for the wireless communication device, wherein the first message comprises a first identity and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device; determining, from the first value, that the wireless communication device requires an update of all available policies for the wireless communication device, and determining the available policies for the wireless communication device; and transmitting to the wireless communication device a second message, wherein the second message comprises a second identity, at least one policy section, and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

10. The method of claim 9, the first policy section code is not associated with one or more policy sections.

11. The method of claim 9, wherein the first policy section code is associated with one or more policy sections; receiving a third message from the wireless communication device, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node; determining that the wireless communication device requires additional policy section codes associated with the first identity; and transmitting a fourth message to the wireless communication device, wherein the fourth message comprises at least the first identity and at least one policy section, and a policy section code for each of the at least one policy section, wherein one or more policy sections of the at least one policy section transmitted in the fourth message are associated with the first identity.

12. The method of any of claims 9 to 11, wherein the policy section code transmitted in the second message is associated with a policy section transmitted by the first network node to the wireless communication device.

13. The method of any of claims 9 to 12, wherein the first identity is an identity of a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN).

14. The method of any of claims 9 to 13, wherein the second identity is an identity of a PLMN or an SNPN, and wherein the one or more policy sections in the second message are each associated with a policy section code, and wherein the policy section transmitted in the second message is associated with one or more policy section codes transmitted by the first network node to the wireless communication device.

15. The method of any of claims 9 to 14, wherein: the first network node is a Policy Control Function (PCF); and the second network node is an Access and Mobility Management Function (AMF).

16. The method of any of claims 9 to 15, wherein the first value is: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

17. A wireless communication device comprising: a processor; and a memory coupled with the processor, the processor configured to cause the wireless communication device to: transmit to a first network node a first message to establish a policy association for the wireless communication device, wherein the first message comprises: a first identity; and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device node; receive from the first network node a second message, wherein the second message comprises a second identity, at least one policy section and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.

18. The wireless communication device of claim 17, wherein the value selected by the wireless communication device node is a value not set by a first network node.

19. The wireless communication device of claim 17 or 18, wherein the first policy section code is not associated with any policy section associated with wireless communication device.

20. The wireless communication device of claim 17, wherein the first policy section code is one of one or more policy section codes which are associated with one or more policy sections, the processor further configured to cause the wireless communication device to: transmit a third message to the first network node, the third message including a request to establish the policy association for the wireless communication device, wherein the third message comprises the first identity and the first policy section code set by the first network node; receive a fourth message from the first network node, wherein the fourth message comprises at least the first identity, at least one policy section associated with the first identity, and a respective policy section code for each policy section associated with the first identity.

21. The wireless communication device of any of claims 17 to 20, wherein the one or more policy sections transmitted in the second message are associated with one or more policy sections transmitted by the first network node to the wireless communication device.

22. The wireless communication device of any of claims 17 to 21, wherein the first identity is an identity of a Public Land Mobile Network (PLMN) or a Standalone Non- Public Network (SNPN).

23. The wireless communication device of any of claims 17 to 22, wherein the second identity is an identity of a PLMN or an SNPN, and wherein the one or more policy section codes transmitted in the second message are associated with one or more policy sections transmitted by the first network node to the device.

24. The wireless communication device of any of claims 17 to 23, wherein: the first network node is a Policy Control Function (PCF); and the second network node is an Access and Mobility Management Function (AMF).

25. The wireless communication device of any of claims 17 to 24, wherein the first value is: zero; a non-zero value; or a non-zero assigned by operator subscriber that the device uses if the device is not aware any value for the first policy section code.

26. A method in a wireless communication device, the method comprising: transmitting to a first network node a first message to establish a policy association for the wireless communication device, wherein the first message comprises: a first identity; and a first policy section code, wherein the first policy section code is set to a first value wherein the first value is a value selected by the wireless communication device node; receiving from the first network node a second message, wherein the second message comprises a second identity, at least one policy section and a respective policy section code for each policy section, wherein the at least one policy section code received in the second message is set by the first network node, wherein each policy section contains one or more policies.