Mobility in wireless communication networks

Abstract

A method is provided in a first network function, comprising the step of sending a request to a second network function, wherein the request requests the deletion of a first policy association, the first policy association being established for at least one PDU session, the at least one PDU session being established by a wireless communication device in a first mobile communication technology, and the at least one PDU session being forwarded to a second mobile communication technology. The method further comprises the step of receiving a processing response from a second network function, the processing response indicating that the wireless communication device supports a second policy association, the second policy association being for a second mobile communication technology.

Description

Technical Field

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

Background Art

[0002] A wireless communication device such as a UE may be connected to both a 5th generation system (5GS) and an evolved packet system (EPS) and communicate through both. Such a UE can register with 5GS and attach to EPS either through single registration or dual registration, and may be able to receive UE policy sections in both EPS and 5GS. In the case of single registration to 5GS, when the UE supports a UE policy section including URSP in EPS and the PDU session is handed over from 5GS to EPS, the SM-PCF needs to establish a UE policy association with the UE-PCF in order to assign an appropriate policy to the PDU session after the handover. When the PDU session is handed over from 5GS to EPS, it is not clear how the UE-PCF should indicate to the AMF that the UE can handle the UE policy section management list in EPS.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

[0004] Disclosed herein are procedures for providing mobility in a wireless communication network. These procedures may be implemented by a first network function, a method in the first network function, a second network function, and a method in the second network function.

[0005] A new dialogue between UE-PCF and AMF for PDU session handover from 5GS to EPS, in which the N26 reference point is implemented, is presented herein.

[0006] Accordingly, a first network function is provided, comprising a processor and memory coupled to the processor. The processor is configured to cause the first network function to send a request to a second network function, the request requesting the deletion of a first policy association, the first policy association being established for at least one PDU session, the at least one PDU session being established by a wireless communication device in a first mobile communication technology, and the at least one PDU session being transferred to a second mobile communication technology. The processor is further configured to cause the first network function to receive a processing response from the second network function, the processing response indicating that a wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology.

[0007] A method in a first network function is further provided, comprising the step of sending a request to a second network function, wherein the request requests the deletion of a first policy association, the first policy association being established for at least one PDU session, the at least one PDU session being established by a wireless communication device in a first mobile communication technology, and the at least one PDU session being forwarded to a second mobile communication technology. The method further comprises the step of receiving a processing response from a second network function, the processing response indicating that the wireless communication device supports a second policy association, the second policy association being for a second mobile communication technology.

[0008] A second network function is further provided, comprising a processor and memory coupled to the processor. The processor is configured to receive a request from the first network function requesting the deletion of a first policy association, wherein the first policy association is established for at least one PDU session, at least one PDU session is established by a wireless communication device in a first mobile communication technology, and at least one PDU session is transferred to a second mobile communication technology, and to send a processing response to the first network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology.

[0009] A method in a second network function is further provided, comprising the steps of: receiving a request from a first network function to delete a first policy association, wherein the first policy association is established for at least one PDU session, at least one PDU session is established by a wireless communication device in a first mobile communication technology, and at least one PDU session is forwarded to a second mobile communication technology; and sending a processing response to the first network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology.

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

[0011] Next, methods and apparatus for providing mobility in a wireless communication network will be described, simply as examples, with reference to the attached drawings. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows one embodiment of a wireless communication system for providing mobility between wireless communication networks. [Figure 2] This figure shows a user device that may be used to implement the method described herein. [Figure 3] This figure shows further details of the network nodes that may be used to implement the methods described herein. [Figure 4]This diagram shows a network architecture capable of sending policy sections to the UE. [Figure 5] This diagram shows the process for UE mobility from 5GS to EPS when the N26 interface is supported by AMF and MME. [Figure 6] This figure shows the method in the first network function. [Figure 7] This figure shows the method in the second network function. [Modes for carrying out the invention]

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

[0014] For example, the disclosed methods and apparatus may be implemented as custom very large-scale integrated ("VLSI") circuits or as hardware circuits comprising off-the-shelf semiconductors such as gate arrays, logic chips, transistors, or other individual components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, or programmable logic devices. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code that can be organized as objects, procedures, or functions, for example.

[0015] Furthermore, the method and apparatus may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmission. The storage device may not embody a signal. In certain configurations, the storage device merely employs a signal for accessing the code.

[0016] Any combination of one or more computer-readable media may be utilized. The computer-readable media may be a computer-readable storage media. The computer-readable storage media may be a storage device that stores the code. The storage device may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing, but is not limited thereto.

[0017] More specific examples (non-exhaustive list) of the storage device include, hereinafter, 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 media may be any tangible media that can include or store a program for use by or in relation to an instruction execution system, apparatus, or device.

[0018] Throughout this specification, any reference to a particular method or apparatus, or to an example of similar wording, means that the particular features, structure, or characteristics described in relation to that example are included in at least one implementation of the methods and apparatus described herein. Thus, all references to a particular method or apparatus, or to an example of similar wording, mean "one or more examples, but not all," although they may, not necessarily, refer to the same example. The terms "including," "comprising," and "having," and their variations, mean "including, but not limited to," unless otherwise specified. The enumeration of items does not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also mean "one or more," unless otherwise specified.

[0019] As used herein, a list accompanied by the conjunction "and / or" includes any single item in the list or any combination of items in the list. For example, a list of A, B and / or C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B and C. As used herein, a list using the term "one or more of" includes any single item in the list or any combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B and C. As used herein, a list using the term "one of" includes only one of any single item in the list. For example, "one of A, B and C" includes only A, only B, or only C, and excludes the combination of A, B and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only one of A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C and combinations thereof" includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B and C.

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

[0021] The embodiments of the disclosed methods and apparatus are described below with reference to schematic flowcharts and / or schematic block diagrams of the methods, apparatus, systems, and program products. It should be understood that each block in the schematic flowcharts and / or schematic block diagrams, as well as any combination of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, a dedicated computer, or other programmable data processing device to create a machine, and as a result, instructions executed via the computer or other programmable data processing device processor create means for implementing the functions / actions specified in the schematic flowcharts and / or schematic block diagrams.

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

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

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

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

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

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

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

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

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

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

[0032] Figure 2 illustrates a user device 200 that may be used to implement the methods described herein. The user device 200 is used to implement one or more of the solutions described herein. The user device 200 conforms to one or more of the user devices described in the embodiments described herein. Specifically, the user device 200 may comprise a wireless communication device, a remote unit 102, a UE 410, 411, or 510 as described herein. The user device 200 includes a processor 205, memory 210, an input device 215, an output device 220, and a transceiver 225.

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

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

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

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

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

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

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

[0040] The output device 220 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to the user. For example, the output device 220 may include, but is not limited to, a liquid crystal display ("LCD"), a light-emitting diode ("LED") display, an organic LED ("OLED") display, a projector, or a similar display device capable of outputting images, text, etc., to the user. As another non-limiting example, the output device 220 may include a wearable display, such as a smartwatch, smart glasses, or a head-up display, that is detached from the rest of the user equipment device 200 but communicatively coupled to it. Furthermore, the output device 220 may be a component of a smartphone, personal digital assistant, television, tablet computer, notebook (laptop) computer, personal computer, or vehicle dashboard.

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

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

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

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

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

[0046] Figure 3 illustrates further details of a network node 300 that may be used to implement the method described herein. The network node 300 may be an implementation of one entity in a wireless communication network, for example, in one or more of the wireless communication networks described herein. The network node 300 may comprise a first network function, network unit 104, and / or AMF422, 522, as described herein. The network node 300 may comprise a second network function, network unit 104, and / or UE-PCF431, 532, as described herein. The network node 300 includes a processor 305, memory 310, input device 315, output device 320, and transceiver 325.

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

[0048] As illustrated, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335, where the transceiver 325 communicates with one or more remote units 200. In addition, the transceiver 325 may support at least one network interface 340 and / or application interface 345. The application interface 345 may support one or more APIs. The network interface 340 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 340 may be supported, as will be understood by those skilled in the art.

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

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

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

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

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

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

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

[0056] Wireless communication devices such as UEs may be able to connect to and communicate through both fifth-generation systems (5GS) and advanced packet systems (EPS). Such UEs can register with 5GS and attach to EPS via single or dual registration, and may be able to receive UE policy sections in both EPS and 5GS. In the case of single registration to 5GS, if the UE supports UE policy sections including URSP in EPS and a PDU session is handed over from 5GS to EPS, the SM-PCF needs to establish a UE policy association with the UE-PCF in order to assign the appropriate policy to the PDU session after the handover. It is unclear how the UE-PCF should indicate to the AMF that the UE is able to handle the UE policy section management list in EPS when a PDU session is handed over from 5GS to EPS.

[0057] A new dialogue between UE-PCF and AMF for PDU session handover from 5GS to EPS, in which the N26 reference point is implemented, is presented herein.

[0058] N26 is an inter-core network interface, for example, between the AMF and MME, and can be used to enable interworking between the 5G core and the EPC. However, support for the N26 interface in the network is optional. Interworking procedures using the N26 interface enable the exchange of MM and SM states between the source and target networks, and therefore, handover procedures can be supported through the N26 interface.

[0059] The N26 interface between the AMF in 5GC and the MME in EPC can be used to enable seamless session continuity during inter-system handovers, which can be particularly useful for delivering voice services. Using N26 can result in reduced voice interruption time, for example, when performing a handover from 5G (VoNR) to 4G (VoLTE).

[0060] 3GPP TS 24.501 v18.1.0, titled "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18)," describes the UE-initiated UE status indication procedure in section D.2.2, which is performed during initial registration to 5GS. Section D.2.2.1 of 3GPP TS 24.501 v18.1.0 states that the purpose of the UE-initiated UE status indication procedure is as follows: The purpose of the UE-start type UE status indication procedure is to provide the PCF with: a) Delivering the UPSI of the UE policy section, where the UE policy section is - Identified by a UPSI that has a PLMN ID portion indicating the HPLMN or selected PLMN, and stored in the UE if any, or - It has a PLMN ID portion that indicates the PLMN ID portion of the selected SNPN's SNPN identity, is identified by the UPSI associated with the selected SNPN's NID, and is stored in the UE, if any. To broadcast, b) Indicate whether the UE supports ANDSP, and c) Distributing one or more OS IDs for the UE. That is the case.

[0061] Section D.2.2.2 of 3GPP TS 24.501 v18.1.0 describes the initiation of a UE-initiated UE state indication procedure as follows: To initiate a UE-initiated UE state indication procedure, the UE shall create a UE STATE INDICATION message. a) Allocate an unused PTI value and set the PTI IE to that allocated PTI value. b) If not operating in SNPN access mode, the UPSI in the UE policy section that is identified by a UPSI having a PLMN ID portion indicating an available HPLMN or selected PLMN in the UE shall be included in the UPSI list IE. c) When operating in SNMP access mode, - The selected SNPN has a PLMN ID portion that indicates the MCC and MNC, - Associated with the NID of the selected SNPN, The UPSIs identified by the available UPSIs in the UE policy section shall be included in the UPSI list IE. d) The UE policy class mark IE shall specify whether the UE supports ANDSP. e) One or more OS IDs of the UE may be included in the UE OS ID IE. The UE shall send a UE STATE INDICATION message (see example in Figure D.2.2.2.1). The UE shall transport the created UE STATE INDICATION message using the registration procedure (see sub-section 5.5.1).

[0062] Section D.2.2.3 of 3GPP TS 24.501 v18.1.0 describes the UE-initiated UE state indication procedure accepted by the network. It explains that upon receiving the UE STATE INDICATION message, the PCF should behave as described in 3GPP TS 23.502 v18.1.0, titled "Procedures for the 5G System (5GS)", and 3GPP TS 29.525 v18.1.0, titled "5G System; UE Policy Control Service; Stage 3".

[0063] The 3GPP work item for Extended UE Policy (eUEPO) enables UEs to receive UE policy sections when they register with the EPS network. Figure 4 shows a network architecture 400 that has the ability to send policy sections to UEs.

[0064] The network architecture 400 includes a UE 410 that communicates via the E-UTRAN 412 and the Mobility Management Entity (MME) 424. The network architecture 400 further includes a UE 411 that communicates with the Next Generation Radio Access Network (NG-RAN) 413 and the Access and Mobility Management Function (AMF) 422. The MME 424 and E-UTRAN 412 communicate with the Serving Gateway (SGW) 426, which in turn communicates with the Session Management Function (SMF) + Packet Data Network Gateway-Control (PGW-C) 428 and the User Plane Function (UPF) + Packet Data Network Gateway-User (PGW-U) 427. The AMF 422 and NG-RAN 413 also communicate with the SMF + PGW-C 428 and the User Plane Function (UPF) + Packet Data Network Gateway-User (PGW-U) 427. The network architecture 400 further includes a session management policy control function (SM-PCF) 430, a home subscriber server (HSS) + integrated data management (UDM) 436, and a user device policy control function (UE-PCF) 431. Interfaces between various network functions are also shown in Figure 4.

[0065] UE410 and 411 may each comprise a wireless communication device, a remote unit 102, a user equipment device 200, and / or UE510, as described herein. AMF422 may comprise a first network function, a network unit 104, a network node 300, and / or AMF522, as described herein. UE-PCF431 may comprise a second network function, a network unit 104, a network node 300, and / or UE-PCF532, as described herein.

[0066] The UE410 requests the establishment of PDN connectivity when attaching to the EPS (in this case, E-UTRAN412). Furthermore, by using the Extended Protocol Configuration Option (ePCO), the UE410 sends a UE STATE INDICATION message to the SMF+PGW-C428, which is later forwarded to the SM-PCF430 to provide the UE policy section and establish a UE policy association with the UE-PCF431.

[0067] The SM-PCF430 does not support N15 reference points, while the UE-PCF431 does not support N7 reference points. In this configuration, UE policy association establishment between the SM-PCF430 and UE-PCF431 is provided for URSP distribution from UE-PCF431 in 5GC to UE410 in EPS. URSP can be distributed transparently to UE410 via the SM-PCF430, SMF+PGW-C428, SGW426, and MME424. As illustrated in Figure 4, an interface (Nx) between the SM-PCF430 and UE-PCF431 must be specified to establish the UE policy association. The N15 interface can be reused as Nx. When UE410 sends an attach request in EPS (e.g., initial attach procedure, 5GS-EPS mobility procedure without N26), UE410 sends a UE policy container containing a list of PSIs and instructions for URSP delivery via EPS to UE-PCF431 in the PCO. When the UE policy is updated in UE-PCF431 while UE410 is in EPS, UE-PCF431 sends the UE policy container to SMF+PGW-C428. SMF+PGW-C428 sends the PCO containing the UE policy container to UE410. Furthermore, when UE411 sends a registration request in 5GS, UE411 sends a UE policy container containing a list of PSIs and instructions for URSP delivery via EPS to UE-PCF431. In 5GS-EPS handover / idle mode mobility using N26, UE policy associations established in 5GS may be maintained in EPS.

[0068] Figure 5 shows process 500 for UE mobility from 5GS to EPS when the N26 interface is supported by AMF and MME. Process 500 is carried out by UE510, gNB and / or eNB520, AMF522, MME524, SGW526, SMF+PGW-C528, SM-PCF530, and UE-PCF532.

[0069] UE510 may include a wireless communication device, a remote unit 102, a user equipment device 200, and / or UE410, 411 as described herein. AMF522 may include a first network function, a network unit 104, a network node 300, and / or AMF422 as described herein. UE-PCF532 may include a second network function, a network unit 104, a network node 300, and / or UE-PCF431 as described herein.

[0070] The assumed prerequisites for process 500 are as follows: • The UE is initially registered in 5GS using a PDU session, and the UE operates in single registration mode. • When a UE registers with 5GS, it already includes a UE status indication message, and includes the ability to support URSP provisioning in EPS. • The ability to support URSP provisioning in EPS is stored in the UDR for the UE. • N26 interface is supported.

[0071] Process 500 is initiated at 571, and this step includes steps 1 through 18, as shown in Figure 4.11.1.2.1-1 of 3GPP TS 23.502 v18.1.0 titled “Procedures for the 5G System (5GS)”, and will be explained with reference to this figure. By the time of the tracking area update, it is assumed that the PDU session has been transferred to the EPS and that the EPS bearer has been established for both UL and DL. AMF522 releases the PDU SM context.

[0072] In 572, AMF522 uses the Npcf_UEPolicyControl_Delete service operation described in 3GPP TS 29.525 v18.1.0, titled "5G System; UE Policy Control Service; Stage 3," to delete UE policy associations. The Npcf_UEPolicyControl_Delete message may contain a UE policy association identity (UePolAssoId).

[0073] In 573, UE-PCF532 evaluates whether UE510 is capable of handling the UE policy section managed list in the EPS. UE-PCF532 may respond with "102 Processing" 573a, which includes an indication of UE capability regarding the UE policy section managed list in the EPS. Alternatively, UE-PCF532 may reject the Npcf_UEPolicyControl_Delete service operation by responding with "400 Bad Request" 573b, which includes an indication of UE capability regarding the UE policy section managed list in the EPS. The "400 Bad Request" message is an example of a "4XX reject" message, and UE-PCF532 may respond with any such "4XX reject" message. New information elements may be added to the data structure supported by the DELETE response body, as described in Table 5.3.3.3.2 of 3GPP TS 29.525 v18.1.0 titled "5G System; UE Policy Control Service; Stage 3" and replicated below as Table 1. Note that this table refers to Table 5.2.7.1-1 of 3GPP TS 29.500 v18.1.0 titled "5G System; Technical Realization of Service Based Architecture; Stage 3".

[0074] [Table 1]

[0075] Therefore, a new data type, "ProcessingResponse," is defined herein, as shown in Table 2 below.

[0076] [Table 2]

[0077] In step 574, AMF522 sends the UE-PCF ID, UE policy association ID, and reason for the request within the Nsmf_PDUSession_UpdateSMContext request to SMF+PGW-C528. This may require additional attributes for the SmContextUpdateData type beyond those defined in 3GPP TS 29.502 v18.1.0 titled "Procedures for the 5G System (5GS)". For example, the Nsmf_PDUSession_UpdateSMContext request may include the UE-PCF ID and UE policy association ID.

[0078] In step 575, the SMF+PGW-C528 passes information to the SM-PCF530. This can be done by sending an Npcf_SMPolicyControl_Update request message to the SM-PCF530. The Npcf_SMPolicyControl_Update request message may include the UE-PCF ID and the UE policy association ID.

[0079] In 576, SM-PCF530 may determine whether UE510 supports URSP delivery in EPC by checking UE context policy control subscription information in UDR (not shown) based on information provided by SMF+PGW-C528, and based on that, decide to establish a UE policy association toward UE-PCF532.

[0080] In step 577, the UE policy association is still maintained by either step 573a or step 573b, where UE-PCF532 indicates to AMF522 that the removal of the UE policy association is being processed or rejected, respectively, because the UE supports the UE policy section management list in EPS.

[0081] In step 578, SM-PCF530 uses the UE policy association ID received from SMF+PGW-C528 to locate UE-PCF532 using the UE-PCF ID, and establishes a UE policy association with the selected UE-PCF532. SM-PCF530 contains the policy container received from SMF+PGW-C528.

[0082] In step 579, the UE policy association between SM-PCF530 and UE-PCF532 is established, and the usual procedure then follows to determine the UE policy section.

[0083] In port 580, UE-PCF532 sends Npcf_UEPolicyControl_Create.

[0084] In step 581, UE-PCF532 removes the initial UE policy association created when UE510 was registered with 5GS.

[0085] In step 582, if UE-PCF532 responded to AMF522 with "102 Processing" in step 573a, UE-PCF532 sends "204 No Contents" to confirm the deletion of the original UE policy association established during 5GS registration.

[0086] In step 583, the SMF+PGW-C528 receives a new UE policy association and updates the UE policy association it had stored for UE510 accordingly.

[0087] As an alternative to 582 and 583, if UE-PCF532 responds to AMF522 with a "400 Bad Request" message in step 573b, then in 584, SMF+PGW-C528 sends an Nsmf_PDUSession_UpdateSMContext response to AMF522, and AMF522 is therefore aware that a new UE policy association has been established at the request of SM-PCF. If UE-PCF532 responds with "102 Processing" in 573a, step 584 is not necessary.

[0088] In step 585, AMF522 unregisters UE510 from 5GS and deletes the UE policy association created when UE510 was registered with 5GS.

[0089] In 586, SM-PCF530 and UE-PCF532 may send the UE policy section management list described in 3GPP TS 24.501 v18.1.0 titled "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".

[0090] Accordingly, a first network function is provided, comprising a processor and memory coupled to the processor. The processor is configured to cause the first network function to send a request to a second network function, the request requesting the deletion of a first policy association, the first policy association being established for at least one PDU session, the at least one PDU session being established by a wireless communication device in a first mobile communication technology, and the at least one PDU session being transferred to a second mobile communication technology. The processor is further configured to cause the first network function to receive a processing response from the second network function, the processing response indicating that a wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology.

[0091] The first network function may be AMF. The second network function may be UE-PCF. The first mobile communication technology may be 5GS. The second mobile communication technology may be EPS.

[0092] A processing response may include a cause. The cause can define the reason for the processing response.

[0093] The processing response may include an instruction that the requested removal of the first policy association is being processed. The processing response may include a reason for the processing.

[0094] The processing response may include an instruction that the requested removal of the first policy association was denied. The processing response may include the reason for the denial.

[0095] The processor may be further configured to provide the fourth network function with the identity of the second network function and the identity of at least one PDU session. The fourth network function may comprise an SMF+PGW-C. The first network function may be an AMF.

[0096] Figure 6 shows a method 600 in a first network function, which includes the step 610 of sending a request to a second network function, wherein the request requests the deletion of a first policy association, the first policy association being established for at least one PDU session, the at least one PDU session being established by a wireless communication device in a first mobile communication technology, and the at least one PDU session being forwarded to a second mobile communication technology. The method 600 further includes the step 620 of receiving a processing response from the second network function, the processing response indicating that the wireless communication device supports a second policy association, the second policy association being for a second mobile communication technology.

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

[0098] The first network function may be AMF. The second network function may be UE-PCF. The first mobile communication technology may be 5GS. The second mobile communication technology may be EPS.

[0099] A processing response may include a cause. The cause can define the reason for the processing response.

[0100] The processing response may include an instruction that the requested removal of the first policy association is being processed. The processing response may include a reason for the processing.

[0101] The processing response may include an instruction that the requested removal of the first policy association was denied. The processing response may include the reason for the denial.

[0102] The method may further include the step of providing the fourth network function with the identity of the second network function and the identity of at least one PDU session. The fourth network function may comprise an SMF+PGW-C.

[0103] The first network function could be AMF.

[0104] A second network function is further provided, comprising a processor and memory coupled to the processor. The processor is configured to receive a request from the first network function requesting the deletion of a first policy association, wherein the first policy association is established for at least one PDU session, at least one PDU session is established by a wireless communication device in a first mobile communication technology, and at least one PDU session is transferred to a second mobile communication technology, and to send a processing response to the first network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology.

[0105] The first network function may be AMF. The second network function may be UE-PCF. The first mobile communication technology may be 5GS. The second mobile communication technology may be EPS.

[0106] A processing response may include a cause. The cause can define the reason for the processing response.

[0107] The processing response may include an instruction that the requested removal of the first policy association is being processed. The processing response may include a reason for the processing.

[0108] The processing response may include an instruction that the requested removal of the first policy association was denied. The processing response may include the reason for the denial.

[0109] The processor may be further configured to cause a second network function to receive a request from a third network function to establish a second policy association, and to establish the second policy association. The third network function may be an SM-PCF. The third network function may be configured to send a policy section management list to the device.

[0110] The processor may be further configured to cause a second network function to delete the first policy association and to notify the first network function that the first policy association has been deleted.

[0111] The second network function could be UE-PCF.

[0112] Figure 7 shows a method 700 in a second network function, comprising the steps of: receiving a request from a first network function to delete a first policy association, wherein the first policy association is established for at least one PDU session, at least one PDU session is established by a wireless communication device in a first mobile communication technology, and at least one PDU session is forwarded to a second mobile communication technology; and sending a processing response to the first network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology.

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

[0114] The first network function may be AMF. The second network function may be UE-PCF. The first mobile communication technology may be 5GS. The second mobile communication technology may be EPS.

[0115] A processing response may include a cause. The cause can define the reason for the processing response.

[0116] The processing response may include an instruction that the requested removal of the first policy association is being processed. The processing response may include a reason for the processing.

[0117] The processing response may include an instruction that the requested removal of the first policy association was denied. The processing response may include the reason for the denial.

[0118] The method may further include the steps of receiving a request from a third network function to establish a second policy association, and establishing the second policy association. The third network function may be an SM-PCF. The third network function may be configured to send a policy section management list to the device.

[0119] The method may further include the steps of deleting the first policy association and notifying the first network function that the first policy association has been deleted. The second network function may be a UE-PCF.

[0120] During a handover from 5GS to EPS, if there are any PDU sessions to be transferred from 5GS to EPS and the UE supports UE policy section management lists, the UE-PCF sends a "102 processing" message when the AMF requests the removal of the UE policy association for the transferred PDU sessions. The "102 processing" message includes a machine-readable message indicating that the UE supports UE policy section management lists in the EPS. If the UE policy association for the EPS is changed, the UE-PCF may send a further "204 no contents" message.

[0121] During a handover from 5GS to EPS, if there are any PDU sessions to be transferred from 5GS to EPS, and the UE supports the UE policy section management list in EPS, a new UE policy association must be established, and the old UE policy association (established during 5GS registration) must be removed.

[0122] After the transfer of the PDU session from 5GS to EPS, AMF requests that UE-PCF remove the old UE policy association established during 5GS registration. UE-PCF recognizes that a UE can have a UE policy association in EPS and therefore processes the request after establishing a new UE policy association in EPS. The new cause is also exchanged between UE-PCF and AMF.

[0123] As described herein, upon receiving a request from the AMF to remove the UE policy association created during 5GS registration, the UE-PCF recognizes that the UE is capable of addressing the UE policy association in the EPS, and therefore the UE-PCF, • Responds with a "102 Processing" message indicating that the UE is capable of handling UE policy associations in the EPS. • AMF triggers the provision of information about the UE-PCF identity and UE policy association identity to SMF+PGW-C. The information is passed to SM-PCF, which then requests UE-PCF to establish UE policy associations for UEs in EPS. Next, UE-PCF removes the old UE policy association and sends a "204 No Contents" message to AMF.

[0124] In the alternative configuration, the first UE-PCF response listed above is instead a "400 Bad Request" message with the same cause, indicating that the UE is capable of addressing the UE policy association in the EPS. Therefore, SMF+PWG-C then notifies AMF about removing the old UE policy association.

[0125] Accordingly, a method is provided comprising the steps of: a first network entity requesting a second network entity to delete a first policy association, wherein the first policy association is established for one or more PDU sessions, established by a device in a first mobile communication technology but transferred to a second mobile communication technology; a second network entity responding to the first network entity with a processing response, wherein the processing response includes the device supporting a second policy association, and the second policy association is for a second mobile communication technology; a first network entity providing a fourth network entity with the identity of the second network entity and the identity of one or more PDU sessions; a third network entity requesting the second network entity to establish a second policy association; a second network entity establishing the second policy association; and a second network entity deleting the first policy association and notifying the first network entity.

[0126] A third network entity may send a policy section management list to the device.

[0127] The first network entity may be AMF. The second network entity may be UE-PCF. The third network entity may be SM-PCF. The first mobile communication technology may be 5GS. The second mobile communication technology may be EPS.

[0128] It should be noted that the methods and apparatus described above are illustrative of the invention, not limiting it, and that many alternative configurations can be designed by those skilled in the art without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in the claims, and “a” or “an” does not exclude plurals; a single processor or other unit may perform the functions of several units enumerated in the claims. No reference numerals in the claims should be construed to limit their scope.

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

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

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

[0132] The following abbreviations are relevant to the fields covered in this document: 5GCN, 5G Core Network; 5GS, 5G System; AMF, Access and Mobility Management Function; ANDSP, Access Network Discovery and Selection Policy; API, Application Programming Interface; APN, Access Point Name; BRID, Broadcast Remote Identification; BVLOS, Beyond Visual Line of Sight; C2, Command and Control; CAA, Civil Aviation Authority; DCN, Dedicated Core Network; DNN, Data Network Name; DNS, Domain Name System; ePDG, Advanced Packet Data Gateway; ePCO, Extended Protocol Configuration Option; EPS, Advanced Packet System; ER-NSSAI, Extended Denial NSSAI; E-UTRA, Advanced Universal -Sal Terrestrial Radio Access; FQDN, Fully Qualified Domain Name; GUMMEI, Globally Unique Mobility Management Entity Identifier; GUTI, Globally Unique Temporary Identity; HPLMN, Home PLMN; HSS, Home Subscriber Server; IE, Information Element; IMSI, International Mobile Subscriber Identity; IP, Internet Protocol; LADN, Local Area Data Network; LCS, Location Services; MCC, Mobile Country Code; MNC, Mobile Network Code; N3AN, Non-3GPP Access Network; N3IWF, Non-3GPP Interworking Function; NEF, Network Exposure Function; NID, Network Identifier; OS, Operating System; OS Id, Operating System Identity; OS App Id, Operating System Application Identity; PCF, Policy Control Function; PCO, Protocol Configuration Option; 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, Procedural Transaction Identity; MCC, Mobile Country Code; MME, Mobility Management Entity; MNC, Mobile Network Code; NF, Network Function; NID, Network Identifier;NRID, Network Remote Identification; NSAC, Network Slice Admission Control; NSSF, Network Slice Selection Function; PTI, Procedural Transactional Identity; P-TMSI, Packet Temporary Mobile Subscriber Identity; RAI, Routing Area Identity; RID, Remote Identification; SGW, Serving Gateway; SMF, Session and Mobility Management Function; SM-PCO, Session Management PCO; SNPN, Standalone Non-Public Network; S-NSSAI, Single Network Slice Selection Support Information; SSC, Session and Service Continuity; SSID, Service Set Identifier; SUCI, Subscription Confidentiality Identifier; SUPI, Subscription Permanent Identifier; TA, Tracking Area; TAI, Tracking Area Identity; TAU, Tracking Area Refresh; TEID, Tunnel Endpoint Identifier; TNAN, Trusted Non-3GPP Access Network; TNAP, Trusted Non-3GPP Access Point; TNGF, Trusted Non-3GPP Gateway Function; TPAE, Third-Party Authorized Entity; UAS, Unmanned Aerial System; UAS NF, Unmanned Aerial System Network Function; UAV, Unmanned Aerial Vehicle; UAV-C, Unmanned Aerial Vehicle Controller; UDM, Integrated Data Management; UDR, Integrated Data Repository; UE, User Equipment; UPDS, UE Policy Distribution 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, Unmanned Aerial System Traffic Management; UUAA, USS UAV Authorization / Authorization; UUID, Universal Unique Identifier; WLANSP, Wireless Local Area Network Selection Policy; [Explanation of Symbols]

[0133] 100 Wireless Communication Systems 102 Remote Unit 104 Network Units 200 User equipment, devices 205 Processor 210 memory 215 Input Devices 220 Output Devices 225 Transceiver 230 Transmitter 235 Receiver 240 network interfaces 245 Application Interfaces 300 network nodes 305 Processor 310 memory 315 Input Devices 320 Output Devices 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interfaces 345 Application Interfaces 400 Network Architectures 410 UE 411 UE 412 E-UTRAN 413 Next-Generation Wireless Access Network (NG-RAN) 422 Access and Mobility Management Function (AMF), AMF 424 Mobility Management Entity (MME), MME 426 Serving Gateway (SGW) 427 User Plane Function (UPF) + Packet Data Network Gateway-User (PGW-U) 428 Session Management Function (SMF) + Packet Data Network Gateway-Control (PGW-C), SMF + PGW-C 430 Session Management Policy Control Function (SM-PCF), SM-PCF 431 User Device Policy Control Function (UE-PCF), UE-PCF 436 Home Subscriber Server (HSS) + Unified Data Management (UDM) 500 processes 510 UE 520 gNB and / or eNB 522 AMF 524 MME 526 SGW 528 SMF+PGW-C 530 SM-PCF 532 UE-PCF 600 ways 700 methods

Claims

1. The first network function is, Processor and The system comprises a memory coupled with the processor, and the processor performs the first network function, Sending a request to a second network function, wherein the request requests the deletion of a first policy association, the first policy association has been established for at least one PDU session, the at least one PDU session has been established by a wireless communication device in a first mobile communication technology, and the at least one PDU session is forwarded to a second mobile communication technology. Receiving a processing response from the second network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for the second mobile communication technology, and receiving A first network function configured to perform the following actions.

2. The first network function according to claim 1, wherein the processing response includes a cause.

3. The first network function according to claim 1 or 2, wherein the processing response includes an instruction that the requested deletion of the first policy association is being processed.

4. The first network function according to claim 1 or 2, wherein the processing response includes an instruction that the requested removal of the first policy association was denied.

5. The first network function according to any one of claims 1 to 4, wherein the processor is further configured to provide the fourth network function with the identity of the second network function and the identity of the at least one PDU session.

6. The first network function according to any one of claims 1 to 5, wherein the first network function is an AMF.

7. A method in the first network function, A step of sending a request to a second network function, wherein the request requests the deletion of a first policy association, the first policy association has been established for at least one PDU session, the at least one PDU session has been established by a wireless communication device in a first mobile communication technology, and the at least one PDU session has been transferred to a second mobile communication technology. A step of receiving a processing response from the second network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology. Methods that include...

8. The method according to claim 7, wherein the processing response includes a cause.

9. The method according to claim 7 or 8, wherein the processing response includes an instruction that the requested deletion of the first policy association is being processed.

10. The method according to claim 7 or 8, wherein the processing response includes an instruction that the requested deletion of the first policy association was refused.

11. The method according to any one of claims 7 to 10, further comprising the step of providing a fourth network function with the identity of the second network function and the identity of the at least one PDU session.

12. The method according to any one of claims 7 to 11, wherein the first network function is AMF.

13. The second network function is, Processor and The system comprises a memory coupled with the processor, and the processor is configured for the second network function, Receiving a request from a first network function to delete a first policy association, wherein the first policy association has been established for at least one PDU session, the at least one PDU session has been established by a wireless communication device in a first mobile communication technology, and the at least one PDU session is forwarded to a second mobile communication technology. Sending a processing response to the first network function, wherein the processing response indicates that the wireless communication device supports a second policy association, and the second policy association is for a second mobile communication technology, and A second network function configured to perform the following actions.

14. The second network function according to claim 13, wherein the processing response includes a cause.

15. The second network function according to claim 13 or 14, wherein the processing response includes an instruction that the requested deletion of the first policy association is being processed.

16. The second network function according to claim 13 or 14, wherein the processing response includes an instruction that the requested removal of the first policy association was denied.

17. The processor provides the second network function, Receiving a request from the third network function to establish the aforementioned second policy association, To establish the second policy association mentioned above A second network function according to any one of claims 13 to 16, further configured to perform the following:

18. The processor provides the second network function, Deleting the first policy association, To notify the first network function that the first policy association has been removed. A second network function according to any one of claims 13 to 17, further configured to perform the following:

19. The second network function according to any one of claims 13 to 18, wherein the second network function is a UE-PCF.

Images