DETERMINING RELEASE INFORMATION BASED ON REGISTRATION INFORMATION

FIELD

The subject matter disclosed herein relates generally to wireless communications and more particularly relates to determining release information based on registration information.

BACKGROUND

In certain wireless communications systems, a user equipment (“UE”) parameters update (“UPU”) procedure may be performed. In such systems, the UPU procedure may have various corresponding parameters.

BRIEF SUMMARY

Methods for determining release information based on registration information are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a first network function, a registration request message from a UE. The registration request message includes: an identity; at least one information element; and at least one UE capability. In some embodiments, the method includes determining release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability. In certain embodiments, the method includes transmitting to a second network function: the identity; and the release information of the UE.

One apparatus for determining release information based on registration information includes a receiver to receive a registration request message from a UE. The registration request message includes: an identity; at least one information element; and at least one UE capability. In some embodiments, the apparatus includes a processor to determine release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability. In various embodiments, the apparatus includes a transmitter to transmit to a second network function: the identity; and the release information of the UE.

Another embodiment of a method for determining release information based on registration information includes transmitting, at a first network function, an identity request message to a UE. In some embodiments, the method includes receiving an identity response message from the UE. The identity response message includes an information element and the information element includes an identity for the UE. In certain embodiments, the method includes determining release information of the UE. In various embodiments, the method includes transmitting to a second network function: the identity; and the release information of the UE.

Another apparatus for determining release information based on registration information includes a transmitter to transmit an identity request message to a UE. In some embodiments, the apparatus includes a receiver to receive an identity response message from the UE. The identity response message includes an information element and the information element includes an identity for the UE. In various embodiments, the apparatus includes a processor to determine release information of the UE, wherein the transmitter further to transmit to a second network function: the identity; and the release information of the UE.

Another embodiment of a method for determining release information based on registration information includes receiving, at a first network function, a UE state indication UE policy section identifier (“UPSI”) list message from a UE. The UE state indication UPSI includes at least one UE policy section code (“UPSC”). In some embodiments, the method includes determining an identity and release information of the UE by analyzing the at least one UPSC. In certain embodiments, the method includes transmitting to a second network function: the identity; and the release information of the UE.

Another apparatus for determining release information based on registration information includes a receiver to receive UE state indication UPSI list message from a UE. The UE state indication UPSI includes at least one UPSC. In some embodiments, the apparatus includes a processor to determine an identity and release information of the UE by analyzing the at least one UPSC. In various embodiments, the apparatus includes a transmitter to transmit to a second network function: the identity; and the release information of the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for determining release information based on registration information;

FIG. 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for determining release information based on registration information;

FIG. 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for determining release information based on registration information;

FIG. 4 is a schematic block diagram illustrating one embodiment of a system for performing a UPU procedure;

FIG. 5 is a schematic block diagram illustrating one embodiment of a system for extension of a UPU procedure to protect a UE sending capabilities within UPU acknowledgment (“ACK”) responses;

FIG. 6 is a schematic block diagram illustrating one embodiment of a system for protection of a UE capabilities indication within a registration procedure;

FIG. 7 is a schematic block diagram illustrating one embodiment of a system for performing a home network (“HN”) parameter update procedure;

FIG. 8 is a schematic block diagram illustrating one embodiment of a system for performing a UE's UPU capability check based on its identity and/or a release identity;

FIG. 9 is a schematic block diagram illustrating another embodiment of a system for performing a UE's UPU capability check based on its identity and/or a release identity;

FIG. 10 is a schematic block diagram illustrating a further embodiment of a system for performing a UE's UPU capability check based on its identity and/or a release identity;

FIG. 11 is a flow chart diagram illustrating one embodiment of a method for determining release information based on registration information;

FIG. 12 is a flow chart diagram illustrating another embodiment of a method for determining release information based on registration information; and

FIG. 13 is a flow chart diagram illustrating a further embodiment of a method for determining release information based on registration information.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments 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 a certain embodiment, the storage devices only employ signals for accessing code.

Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module 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. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

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.

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.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” 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.

Furthermore, the described features, structures, or characteristics of the embodiments 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 embodiments. One skilled in the relevant art will recognize, however, that embodiments 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 an embodiment.

Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. 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. The 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 block or blocks.

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 block or blocks.

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 execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

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 according to various embodiments. 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).

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.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 for determining release information based on registration information. 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 FIG. 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.

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 on-board 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 smart watches, 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.

The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a 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”), 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 communicably 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.

In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an 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 orthogonal frequency division multiplexing (“OFDM”) scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802.11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfox, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

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.

In certain embodiments, a network unit 104 may receive a registration request message from a UE. The registration request message includes: an identity; at least one information element; and at least one UE capability. In some embodiments, the network unit 104 may determine release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability. In certain embodiments, the network unit 104 may transmit to a second network function: the identity; and the release information of the UE. Accordingly, the network unit 104 may be used for determining release information based on registration information.

In certain embodiments, a network unit 104 may transmit an identity request message to a UE. In some embodiments, the network unit 104 may receive an identity response message from the UE. The identity response message includes an information element and the information element includes an identity for the UE. In certain embodiments, the network unit 104 may determine release information of the UE. In various embodiments, the network unit 104 may transmit to a second network function: the identity; and the release information of the UE. Accordingly, the network unit 104 may be used for determining release information based on registration information.

In certain embodiments, a network unit 104 may receive a UE state indication UPSI list message from a UE. The UE state indication UPSI includes at least one UPSC. In some embodiments, the method includes determining an identity and release information of the UE by analyzing the at least one UPSC. In certain embodiments, the network unit 104 may transmit to a second network function: the identity; and the release information of the UE. Accordingly, the network unit 104 may be used for determining release information based on registration information.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used for determining release information based on registration information. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 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. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“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 display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 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.

In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used for determining release information based on registration information. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

In certain embodiments, the receiver 312 to receive a registration request message from a UE. The registration request message includes: an identity; at least one information element; and at least one UE capability. In some embodiments, the processor 302 to determine release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability. In various embodiments, the transmitter 310 to transmit to a second network function: the identity; and the release information of the UE.

In certain embodiments, the transmitter 310 to transmit an identity request message to a UE. In some embodiments, the receiver 312 to receive an identity response message from the UE. The identity response message includes an information element and the information element includes an identity for the UE. In various embodiments, the processor 302 to determine release information of the UE. The transmitter 310 further to transmit to a second network function: the identity; and the release information of the UE.

In some embodiments, the receiver 312 to receive UE state indication UPSI list message from a UE. The UE state indication UPSI includes at least one UPSC. In some embodiments, the processor 302 to determine an identity and release information of the UE by analyzing the at least one UPSC. In various embodiments, the transmitter 310 to transmit to a second network function: the identity; and the release information of the UE.

It should be noted that one or more embodiments described herein may be combined into a single embodiment.

In certain embodiments, a UPU procedure may be used by a UDM for provisioning a routing identifier (“ID”) and default single (“S”) network slice selection assistance information (“NSSAI”) (“S-NSSAI”) and also for updating the routing ID and default configured NSSAI with a transmission to a UE. In some embodiments, new parameters with different data set types (e.g., provisioning of network slice specific authentication and authorization (“NSSAA”) credentials, protocol data unit (“PDU”) session authentication credentials, stand-alone non-public network (“SNPN”) credentials, and so forth) may be provided to the UE by the UDM to support vertical service requirements.

In various embodiments, for a UPU, if a UE doesn't support UPU data set types provided by a UDM, then the UPU will eventually fail.

FIG. 4 is a schematic block diagram illustrating one embodiment of a system 400 for performing a UPU procedure. The system 400 includes a UE 402, an AMF 404, an AUSF 406, and a UDM 408. Each of the communications in the system 400 may include one or more messages.

The UDM 408 decides 410 to perform a UE parameter update.

In a first communication 412, the UDM 408 transmits an Nausf_UPUProtection message which may include: a subscription permanent identifier (“SUPI”), UPU data, and/or an ACK indication. In a second communication 414, the AUSF 406 transmits an Nausf_UPUProtection response message which may include: an AUSF UPU medium access control (“MAC”) integrity (“I”) (“UPU-MAC-I_AUSF”), a UE UPU expected MAC (“XMAC”) I (“UPU-XMAC-I_UE”), and/or a UPU counter (“Counter_UPU”).

In a third communication 416, the UDM 408 transmits a Nudm_SDM_Notification message that may include: UPU data, the UPU-MAC-I_AUSF, and the Counter_UPU. In a fourth communication 418, the AMF 404 transmits a DL non-access stratum (“NAS”) transport message that may include: the UPU data, the UPU-MAC-I_AUSF, and the Counter_UPU. The UE 402 verifies 420 the UPU-MAC-I_AUSF.

In an optional fifth communication 422, the UE 402 transmits an UL NAS transport message that may include UPU-MAC-I_UE. Moreover, in an optional sixth communication 424, the AMF 404 may transmit an Nudm_SDM_Info message that may include the UPU-MAC-I_UE. The UDM 408 may compare 426 the received UPU-MAC-I_UEwith a stored UPU-XMAC-I_UE.

In FIG. 4, the UPU procedure may not support UE capability based UPU data provisioning.

FIG. 5 is a schematic block diagram illustrating one embodiment of a system 500 for extension of a UPU procedure to protect a UE sending capabilities within a UPU ACK responses. The system 500 includes a UE 502, an AMF 504, an AUSF 506, and a UDM 508. Each of the communications in the system 500 may include one or more messages.

The UDM 508 decides 510 to perform a UE parameter update for additional UPU parameters.

In a first communication 512, the UDM 508 transmits an Nausf_UPUProtection_Protect request message which may include: a SUPI, UPU data (e.g., an ACK indication, a UE capability request indication, and so forth), and/or an ACK indication. In a second communication 514, the AUSF 506 transmits an Nausf_UPUProtection_Protect response message which may include: UPU-MAC-I_AUSF, UPU-XMAC-I_UE, and/or Counter_UPU.

In a third communication 516, the UDM 508 transmits a Nudm_SDM_Notification message that may include: UPU data, the UPU-MAC-I_AUSF, and the Counter_UPU. In a fourth communication 518, the AMF 504 transmits a DL NAS transport message that may include: the UPU data, the UPU-MAC-I_AUSF, and the Counter_UPU. The UE 502 verifies 520 the UPU-MAC-I_AUSF.

In a fifth communication 522, the UE 502 transmits an UL NAS transport message that may include an ACK response (e.g., including a UE capability indication) and UPU-MAC-I_UE. Moreover, in a sixth communication 524, the AMF 504 may transmit an Nudm_SDM_Info message that may include an ACK response and the UPU-MAC-I_UE. The UDM 508 may, if there is no UE capabilities indication, compare 526 the received UPU-MAC-I_UEwith a stored UPU-XMAC-I_UE; otherwise, the UDM 508 may omit the stored UPU-XMAC-I_UEand request a UPU-XMAC-I_UEfrom the AUSF 506 corresponding to the UE capabilities indication provided by the UE 502.

In a seventh communication 528, the UDM 508 transmits an Nausf_UPUProtection_ProtectACK that may include a SUPI, and an ACK response (e.g., including the UE capabilities indication). The AUSF 506 generates 530 a new UPU-XMAC-I_UE. In an eighth communication 532, the AUSF 506 transmits an Nausf_UPUProtection_ProtectACK response message that includes the new UPU-XMAC-I_UE. The UDM 508 compares 534 the received UPU-MAC-I_UEfrom the UE 502 with the new UPU-XMAC-I_UEreceived from the AUSF 506. The UDM 508 stores the supported UE parameters update data set types if the verification is successful. In a ninth communication 536, another round of steps 510 through 526 is performed for the new parameter updated according to the received UE capabilities indication.

In FIG. 5, the UPU procedure has to be run twice, such as one round of the UPU procedure to perform a UE capability check and another round of the UPU procedure to perform the actual provisioning of UPU data, which incurs more computational complexity.

In FIG. 5, the ACK and a UE capabilities request indicator are included, and a UPU data container is defined to hold only UE parameters to be provisioned by the UDM 508. Therefore, on a successful verification of UPU-MAC-I_AUSF, the UE 502 can wrongly store the ACK and the UE capabilities request indicator as UPU data, but this is not the actual UPU data by itself. The wrong storage of information as UPU data may be made in the UE 502 because the UE 502 does not analyze the UPU data if the verification of UPU-MAC-I_AUSFis successful. The UE 502 forwards secured packet to a universal subscriber identity module (“USIM”). If the verification of UPU-MAC-I_AUSFis successful and the UPU data contains any parameters that are not protected by a secure packet, the UE 502 updates its stored parameters with received parameters in UDM updated data.

FIG. 6 is a schematic block diagram illustrating one embodiment of a system 600 for protection of a UE capabilities indication within a registration procedure. The system 600 includes a UE 602, an AMF 604, an AUSF 606, and a UDM 608. Each of the communications in the system 600 may include one or more messages.

In a first optional communication 610, the UE 602 sends a registration request message that may include a UPU capability container. In a second communication 612, the AMF 604 transmits a Nudm_UECM_Registration message that may include the UPU capability container. In a third communication 614, the UDM 608 transmits a Nausf_UPUCVerfication message that may include a SUPI, supported UE parameters update data set types, a UPUC-MAC-I_UE, and/or a Counter_UPUC(e.g., ACK indication). The AUSF 606 verifies 616 the UPUC-MAC-I_UE. In a fourth communication 618, the AUSF 606 transmits an Nausf_UPUCVerification response message that may include a result and/or a UPUC-MAC-I_AUSF.

In an optional fifth communication 620, the UDM 608 transmits an Nudm_UECM_Registration response message that may include the UPUC-MAC-I_AUSF. In an optional sixth communication 622, the AMF 604 transmits a registration accept message that may include the UPUC-MAC-I_AUSF. The UE 602 compares 624 the received UPUC-MAC-I_AUSFWith a stored UPUC-XMAC-I_AUSF.

In FIG. 6, the UDM may need to perform UPU when there is a certain triggering condition (e.g., if it is required to provide NSSAA credentials/PDU session authentication credentials/optionally SNPN credentials etc.,) and a UE's UPU capability check and UPU may not be required corresponding to every registration of the UE. Therefore, forcing the UE to generate UPU capability container when it is not required to perform any UPU from the UDM side will lead to mere resource wastage.

FIG. 7 is a schematic block diagram illustrating one embodiment of a system 700 for performing a HN parameter update procedure. The system 700 includes a UE 702, an AMF 704, an AUSF 706, and a UDM 708. Each of the communications in the system 700 may include one or more messages.

In a first communication 710, the UE 702 is authenticated and registered in a fifth generation core network (“5GC”). The UE 702 and the AUSF 706 share a Kausf. The UE 702 needs 712 to update information in the HN (e.g., UE capabilities). The UE 702 generates an HN parameter update (“HoPU”)-MAC-I_UEand Counter_HoPU. In a second communication 714, the UE 702 transmits an UL NAS transport message that may include Ho PU data, the HoPU-MAC-I_UE, and the Counter_HoPU. In a third communication 716, the AMF 704 transmits a Nudm_ParameterProvision message that includes a SUPI, HoPU data, the HoPU-MAC-I_UE, and the Counter_HoPU.

In a fourth communication 718, the UDM 708 transmits a Nausf_HoPUProtection_Protect request message that may include the SUPI, the HoPU data (e.g., HoPU data, the Counter_HoPU(e.g., including an ACK indication), and/or additional information). In a fifth communication 720, the AUSF 706 transmits a Nausf_HoPUProtection_Protect response message that may include the HoPU-MAC-I_UEand/or the HoPU-MAC-I_AUSF. The UDM 708 compares 722 the HoPU-MAC-I_UEfrom the UE 702 with the HoPU-MAC-I_UEfrom the AUSF 706.

In a sixth communication 724, the UDM 708 transmits a Nudm_ParameterProvision message that may include a result, the HoPU-MAC-I_AUSF, and/or additional information. In a seventh communication 726, the AMF 704 transmits a DL NAS transport message that may include the HoPU-MAC-I_AUSFand/or additional information. The UE 702 verifies 728 the HoPU-MAC-I_AUSF. In an eighth communication 730, the UDM 708 stores the received HoPU data and uses it accordingly (e.g., to initiate a UPU procedure for UPU data types).

FIG. 7 illustrates a mechanism based on the same principles of a UPU procedure, but it operates in an opposite direction (e.g., from UE 702 to HN). A new HoPU procedure is independent of the UPU and/or registration procedure but may be triggered in relation to these.

In FIG. 7, if the UDM 708 needs to provision any UE parameters to the UE 702, then waiting for any indefinite period of time for the UE 702 to initiate the HN parameter update procedure may impact quality of service and may lead to denial of service.

In various embodiments, the UPU procedure may be enhanced to support UE's UPU capability check based on UE release information as part of the UPU procedure and may allow the UE to store new UPU data if the UE is capable to support and/or handle the corresponding UPU data types.

In a first embodiment, there may be enhancements to a UPU procedure to enable an AMF supported UE capability (e.g., UPU data set type support capability) check and usage of UPU data provided by a UDM.

The first embodiment describes enhancements to the UPU procedure to facilitate storing, supporting, and/or handling new UPU data types at a time of initial or periodic registration including communications between an AMF and a UE exposes its release or its identity to the AMF. The AMF may inform the UDM that may transmit the new UPU data set types.

FIG. 8 is a schematic block diagram illustrating one embodiment of a system 800 for performing a UE's UPU capability check based on its identity and/or a release identity. The system 800 includes a UE 802, an AMF 804, an AUSF 806, and a UDM 808. Each of the communications in the system 800 may include one or more messages.

The UDM 808 may decide to perform a UE parameter update anytime after the UE 802 has been successfully authenticated and registered to a fifth generation (“5G”) system. The security procedure enhancements for the UE parameters update shown in FIG. 8 is described herein.

In a first communication 810, the UE 802 initially registers or perform periodic registration update with a 5G core (“5GC”) network by constructing a registration request message including several information elements (“IEs”). These IEs are used for the registration due to several factors such as a UE's identity and/or a UE's capabilities and subscription information related data management and handling.

The AMF 804 analyses 812 the registration request message to find out: 1) the UE's identity which may be according to a 5G system (“5GS”) mobile identity IE with a type of identity, such as a subscription concealed identifier (“SUCI”), 5G global unique temporary ID (“GUTI”) (“5G-GUTI”), international mobile equipment identity (“IMEI”), 5GS temporary mobile subscriber identity (“TMSI”) (“5G-S-TMSI”), IMEI software version (“SV”) (“IMEISV”), medium access control (“MAC”) address, and/or extended unique identifier (“EUI”) 64 (“EUI-64”): and/or 2) the release of the UE by determining: a) the used IEs, such as UE request type IE which is to enable a UE supporting multiple universal subscriber identity modules (“MUSIM”) to request the network to perform specific requests due to activity on another USIM; and/or b) the UE capabilities in a capability IE, such as support for an extended rejected NSSAI.

In a second communication 814, the AMF 804 forward this information in a Nudm_UEContextManagement service message (e.g., including Amf3GppAccessregistration, UE ID, permanent equipment identifier (“PEI”), IMEI, IMEISV, and/or release indication).

The UDM 808 stores 816 the release information of the UE 802 received from the AMF 804 in the UDR along with the subscription permanent identifier (“SUPI”) as part of UE capability information. The UDM 808 determines the type of the UE 802 including its release by studying received information from the AMF 804 when required and decides to perform the UPU using a control plane procedure while the UE 802 is registered to the 5G system. If the final consumer of any of the UE parameters to be updated (e.g., the updated routing ID data, provisioning of network slice specific authentication and authorization (“NSSAA”) credentials, protocol data unit (“PDU”) session authentication credentials, and/or stand-alone non-public network (“SNPN”) credentials) is the USIM, the UDM 808 protects these parameters using a secured packet mechanism to update the parameters stored on the USIM. The UDM 808 then prepare the UPU data by including the parameters protected by the secured packet, if any, as well as any UE parameters for which final consumer is the mobile equipment (“ME”). Due to the release of the UE, the UDM 808 determines to provision the UE 802 with parameters with different data type(s) (e.g., UPU dataset types such as—provisioning of NSSAA credentials, PDU session authentication credentials, and/or SNPN credentials).

In some embodiments, the UDM 808 and/or UDR may request from the AMF 804 in a Nudm_SDM_ReleaseRequest and/or Notification service operation message with SUPI, a release request indication and/or a UE capability request indication. The AMF 804 may perform UE release prediction or may fetch the UE release information if available and may provide the UE release information to the UDM 808 and/or UDR as a response in a Nudm_SDM_ReleaseResponse and/or Info service operation message. If the AMF 804 provided UE release indicates that the UE 802 is a legacy UE, then the UDM 808 determines not to trigger a UPU to provision any different data set types to the UE 802 other than the routing indicator and default single (“S”) network slice selection assistance information (“NSSAI”) (“S-NSSAI”).

In a third communication 818 and a fourth communication 820, the UDM 808 may invoke a Nausf_UPUProtection service operation message by including UPU data in a transmission to the AUSF 806 to get UPU-MAC-I_AUSFand Counter_UPU. The UDM 808 selects the AUSF 806 that holds the latest K_AUSFof the UE 802. If the UDM 808 determines to provision the UE 802 with parameters of different data types, then the UDM 808 performs the following:

- 1) the UDM 808 sends the ‘UPU Priority Information’ to the AUSF 806 in the Nausf_UPUProtection service operation message (e.g., Nausf_UPUProtection_Protect request). The ‘UPU Priority Information’ may contain the ‘Required UPU data type(s) support information’. The ‘Required UPU data type(s) support information’ may include a list of one or more UPU data set type(s) information required to be supported at the UE 802 to perform a successful UPU procedure corresponding to the required parameter provisioning as determined by the UDM 808;
- 2) if the UDM 808 determines to provision the UE 802 with parameters of different data types based on the UE release information provided by the AMF 804 and if the UDM 808 determines to invoke a UPU capability check at the UE 802, then the UDM 808 decides that the UE 802 is required to acknowledge the successful security check of the UPU priority information, received UE parameters update data, and successful UPU capability check at the UE 802, then the UDM 808 sets the corresponding indication in the UE parameters update data (e.g., ACK in the UPU header) and include the ACK indication in the Nausf_UPUProtection service operation message to signal that it also needs the expected UPU-XMAC-I_UE;
- 3) the AUSF 806 and the UE 802 associate a 16-bit counter, Counter_UPU(to be used for UPU protection), with the key K_AUSF. The AUSF 806 calculates the UPU-MAC-I_AUSFusing the parameters received from the UDM 808 and delivers the UPU-MAC-I_AUSFand Counter_UPUto the UDM 808. If the ACK indication input is present, then the AUSF 806 also computes the UPU-XMAC-I_UEand returns the computed UPU-XMAC-I_UEin the response to the UDM 808. The AUSF 806 computes the UPU-MAC-I_AUSFand UPU-XMAC-I_UE. The inclusion of UPU priority information, UPU capability check required information, UE parameters update header, and/or UE parameters update data in the calculation of UPU-MAC-I_AUSFallows the UE 802 to verify that it has not been tampered by any intermediary. The expected UPU-XMAC-I_UEallows the UDM 808 to verify that the UE 802 received the UE parameters update data correctly and performed the UE UPU capability check successfully when requested by the UDM 808; and/or
- 4) instead of UPU priority information, the following information can be used by the UE 802 in the UPU procedure to perform UE's UPU capability based UPU data provisioning: UPU capability check required information (e.g., required UPU data set type(s) support, UPU capability request). Then the description related to ‘UPU Priority Information’ may be applicable to UPU capability check required information.

In a fifth communication 822, the UDM 808 invokes a Nudm_SDM_Notification service operation which contains UPU priority information, UE parameters update data, UPU-MAC-I_AUSF, and/or Counter_UPUwithin the access and mobility subscription data. If the UDM requests an acknowledgement, it temporarily store the expected UPU-XMAC-I_UEalong with the required UPU data set type(s) support information for the UE 802 corresponding to the ongoing UPU.

In a sixth communication 824, upon receiving the Nudm_SDM_Notification message, the AMF 804 sends a downlink (“DL”) NAS transport message to the served UE 802. The AMF 804 may include, in the DL NAS transport message, the transparent container received from the UDM 808 which contains the UPU priority information, UE parameters update data, UPU-MAC-I_AUSF, and Counter_UPU.

On receiving the DL NAS transport message, the UE 802 calculates 826 the UPU-MAC-I_AUSFin the same way as the AUSF 806 using the received UPU priority information, UPU parameters update header, UE parameters update data, and the Counter_UPUand verifies whether it matches the UPU-MAC-I_AUSFvalue received in the DL NAS transport message. If the verification of UPU-MAC-I_AUSFis successful, and if both the UE's UPU capability and the network provided ‘Required UPU data type(s) support’ matches successfully, the UE 802 determines to store and use the UPU data provided by the network. If the UPU data contains any parameters that are protected by secured packet, the UE 802 shall forward the secured packet to the USIM. If the verification of UPU-MAC-I_AUSFis successful and the UPU data contains any parameters that are not protected by a secure packet, the UE 802 further update its stored parameters with the received parameters in UDM update data.

In a seventh communication 828, in response to receiving the ACK required indication from the network, if the UE 802 has successfully performed the UPU priority information and the UE 802 has successfully verified and updated the UE parameters update data provided by the UDM 808, then the UE 802 generates the UPU-MAC-I_UE(e.g., in UL NAS transport message) along with its UPU capabilities. Further the UE 802 sends the UL NAS transport message to the serving AMF 804 and includes the generated acknowledgement, UE's UPU capabilities, and UPU-MAC-I_UEin a transparent container in the UL NAS transport message.

In an eighth communication 830, if a transparent container with the UPU-MAC-I_UEwas received in the UL NAS transport message, the AMF 804 can send a Nudm_SDM_Info request message with the transparent container to the UDM 808. The transparent container contains the acknowledgement, the UE's UPU capabilities, and the UPU-MAC-I_UE.

The UDM 808, on receiving the transparent container with the acknowledgement, the UE's UPU capabilities, and the UPU-MAC-I_UE, the UDM 808 first compares 832 the received UPU-MAC-I_UEwith the expected UPU-XMAC-I_UEthat the UDM 808 stored temporarily in step 816.

If the ‘Required UPU Data Set Type(s) Support’ information provided by the network is the same as the UE 802 provided ‘UE's capability of UPU Data Set Type(s) Support’, then the UE 802 provided UPU-MAC-I_UEwill be same as the UPU-XMAC-I_UEavailable in the UDM 808 or else, if the ‘UE's capability of UPU Data Set Type(s) Support’ has more information than the ‘Required UPU Data Set Type(s) Support’, then the UDM 808 requests the AUSF 806 for the new UPU-XMAC-I_UEcomputation and ACK verification. In certain embodiments, the UDM 808, on receiving the transparent container with the acknowledgement, the UE's UPU capabilities, and the UPU-MAC-I_UE, determines to request the AUSF 806 for the verification of acknowledgement response with the UE's UPU capabilities, then steps 834 through 840 may be performed.

In a ninth communication 834, the UDM 808 requests that the AUSF 806 generate a UPU-MAC-I_UEthat considers the acknowledgement, the UE capability information provided by the UE 802. The UDM 808 invokes the Nausf_UPUProtection_ACKVerification service operation by including the contents of the UPU transparent container received from the UE 802 except for the UPU-MAC-I_UEand the Counter_UPU(e.g., temporarily stored by the UDM 808).

The AUSF 806 may use 836 the received Counter_UPUwhen calculating a new UPU-MAC-I_UE. The AUSF 806 computes the new UPU-MAC-I_UE.

In an eighth communication 838, upon reception of the new UPU-XMAC-I_UEfrom the AUSF 806 in a Nausf_UPUProtection_ACKVerification response service operation, the UDM 808 may compare 840 it to the UPU-MAC-I_UEreceived in step 824. If the verification is successful, the UDM 808 stores the received UE capability information for future use (e.g., to trigger subsequent UPU procedures for UPU data).

The UDM 808 may locally store or store in the UDR the received UPU capabilities (e.g., UPU data set type(s) supported by the UE 802) for the UE 802 along with the SUPI.

It should be noted that the processing described in FIG. 8 may be adopted with any new service operation message(s) to support UPU capability check and to perform successful a UE parameter update procedure involving the UE 802, the AMF 804, the AUSF 806, and the UDM 808, respectively.

In various embodiments, if the UE 802 determines that it is not capable to support the ‘Required UPU data type(s) support’ provided by the network, then the UE 802 can send a UPU capability check failure indication. Then the UDM 808 can store the UE capability received and can record the UPU failure status corresponding to the UPU data set type in the subscription information or UE context along with the SUPI. If a legacy UE cannot understand the message received in step 818, then the UE 802 can drop the message.

In certain embodiments, there may be a UPU-MAC-I_AUSFgeneration function. In such embodiments, an AUSF may perform a UPU-MAC-I_AUSFcomputation. Moreover, the UE may compute UPU-MAC-I_AUSFsimilar to the AUSF for the UPU-MAC-I_AUSFverification as follows: 1) when deriving a UPU-MAC-I_AUSFfrom K_AUSF, the following parameters may be used to form an input S to a key derivation function (“KDF”) with the following: a) FC=0x7B; b) P0=UE parameters update data; c) L0=length of UE parameters update data; d) P1=CounterUPU; c) L1=length of CounterUPU; f) P2=UPU priority information; g) L2=length of UPU priority information; h) P3=UE parameters update header; and/or i) L3=length of UE parameters update header. In such embodiments, the input key may be K_AUSF. The UPU-MAC-I_AUSFis identified with the 128 least significant bits of the output of the KDF.

In some embodiments, there may be a UPU-XMAC-I_UEgeneration function. In such embodiments, the AUSF, with ACK, UPU priority information and/or UPU capability check required information, performs UPU-MAC-I_AUSFcomputation. Moreover, when deriving a UPU-MAC-I_UEfrom K_AUSF, the following parameters shall be used to form an input S to a KDF with the following: 1) FC=0x7C; 2) P0=0x02 (e.g., UPU acknowledgement: verified the UE parameters update data); 3) L0=length of UPU acknowledgement (e.g., 0x00 0x02): 4) P1=Counter_UPU; 5) L1=length of Counter_UPU; 6) P2=UE parameters update header; and/or 7) L2=length of UE parameters update header. In such embodiments, the input key shall be K_AUSF. The UPU-MAC-I_UEis identified with the 128 least significant bits of the output of the KDF.

In various embodiments, there may be a UPU-MAC-I_UEgeneration function. In such embodiments, the UE after a successful UPU capability check and update and/or storing of UPU data derives a UPU-MAC-I_UEfrom the K_AUSF, the following parameters ay be used to form the input S to the KDF: 1) FC=0x7C; 2) P0=0x02 (e.g., UPU acknowledgement: verified the UE parameters update data); 3) L0=length of UPU acknowledgement (e.g., 0x00 0x02); 4) P1=Counter_UPU; 5) L1=length of Counter_UPU; 6) P2=UE parameters update header; 7) L2=Length of UE parameters update header; 8) P3=UE's capability of UPU data set type(s) support; and/or 9) L3=length of UE's capability of UPU data set type(s) support. In certain embodiments, UPU-MAC-I_UEgeneration function described may be alternatively called as UPU-MAC-I_UE-Verification generation function and/or UPU-MAC-I_UE-Response.

In some embodiments, steps described in the first embodiment may be applicable to a steering of roaming (“SoR”) procedure as enhancement to SoR for performing the SoR related UE's capability check and related SoR parameters provisioning, where the only change in the description of FIG. 8 is that all ‘UPU’ related wording should be replaced with the word ‘SoR ’.

In a second embodiment, there may be an identity request and/or response procedure. In the second embodiment, an AMF request for a UE's identity and then analyzes a response to inform a UDM about obtained information. On example of the second embodiment is shown in FIG. 9.

FIG. 9 is a schematic block diagram illustrating another embodiment of a system 900 for performing a UE's UPU capability check based on its identity and/or a release identity. The system 900 includes a UE 902, an AMF 904, an AUSF 906, and a UDM 908. Each of the communications in the system 900 may include one or more messages.

In FIG. 9, the UDM 908 can decide to perform a UE parameters update anytime after the UE 902 has been successfully authenticated and registered to the 5G system. The security procedure enhancements for the UE parameters update shown in FIG. 9 are described herein.

In a first communication 910, the AMF 904 uses an identity request message with IEs to request the UE 902 to provide a specified identity. It should be noted that the UDM 908 may request that the AMF 904 to initiate this process.

In a second communication 912, the UE 902 uses an identity response message to provide the AMF 904 with the requested identity.

The AMF 904 analyses 914 the identity response message to find out: 1) the UE's identity which may be according to a 5GS mobile identity IE with a type of identity, such as SUCI, 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64; and/or 2) the release of the UE by identifying the identity.

In a third communication 916, the AMF 904 forwards this information as part of a Nudm_UEContextManagement service message (e.g., including a release indication).

It should be noted that steps 918 through 942 may be substantially similar to the steps 816 through 840 as described in relation to FIG. 8.

In a third embodiment, there may be a UE policy delivery service. In the third embodiment, the UDM and/or UDR may receive information from a policy control function (“PCF”). One example of the security procedure enhancements for the UE parameters update is shown in FIG. 10.

FIG. 10 is a schematic block diagram illustrating a further embodiment of a system 1000 for performing a UE's UPU capability check based on its identity and/or a release identity. The system 1000 includes a UE 1002, an AMF 1004, an AUSF 1006, a PCF 1008, and a UDM/UDR 1010. Each of the communications in the system 1000 may include one or more messages.

The UDM/UDR 1010 may decide to perform a UE parameter update anytime after the UE 1002 has been successfully authenticated and registered to a 5G system. The security procedure enhancements for the UE parameter update shown in FIG. 10 is described herein.

In a first communication 1012, the UE 1002 initiates a UE-initiated UE state indication procedure creating a UE state indication message including IEs such as a UPSI list. The UPSI list includes a UPSC value which may be set by the PCF 1008 and may be a unique value within a public land mobile network (“PLMN”) which is selected by the PCF 1008.

Upon receipt of the one or more UPSCs, the PCF 1008 may analyze 1014 the one or more UPSCs and may relate the UPSC value with the UE identity and the UE policy of its PLMN that it provided to the UE 1002. The PCF may determine: 1) the UE's identity which may be according to a 5GS mobile identity IE with a type of identity, such as SUCI, 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64; and/or 2) the release of the UE 1002 by identifying the identity.

The PCF 1008 may also store UPSCs and related policy sections including: 1) the UE's identity which may be according to 5GS mobile identity IE with a type of identity, such as SUCI, 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64; and/or 2) the release of the UE 1002 by identifying the identity of the UE's PLMN in the UDR/UDM 1010 by a Nudr_DataRepository service procedure in a second communication 1016.

In some embodiments, if the UDR and the UDM are not co-located, the UDM may use the procedure for the Nudr_DataRepository service to fetch information comprising: 1) the UE's identity which may be according to 5GS mobile identity IE with a type of identity, such as SUCI, 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64; and/or 2) the release of the UE 1002 by identifying the identity.

It should be noted that steps 1018 through 1042 may be substantially similar to the steps 816 through 840 as described in relation to FIG. 8.

FIG. 11 is a flow chart diagram illustrating one embodiment of a method 1100 for determining release information based on registration information. In some embodiments, the method 1100 is performed by an apparatus, such as the network unit 104. 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.

In various embodiments, the method 1100 includes receiving 1102, at a first network function, a registration request message from a UE. The registration request message includes: an identity; at least one information element; and at least one UE capability. In some embodiments, the method 1100 includes determining 1104 release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability. In certain embodiments, the method 1100 includes transmitting 1106 to a second network function: the identity; and the release information of the UE.

In certain embodiments, the second network function transmits at least one UE parameter update data set type to the UE based on the identity and the release information of the UE. In some embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof. In various embodiments, the second network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In one embodiment, the release information of the UE comprises at least one UE parameter update data set type that the UE supports. In certain embodiments, the first network function comprises an AMF.

In some embodiments, the second network function comprises a UDM. In various embodiments, the UE stores at least one UE parameter update data set type.

FIG. 12 is a flow chart diagram illustrating another embodiment of a method 1200 for determining release information based on registration information. In some embodiments, the method 1200 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 1200 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.

In various embodiments, the method 1200 includes transmitting 1202, at a first network function, an identity request message to a UE. In some embodiments, the method 1200 includes receiving 1204 an identity response message from the UE. The identity response message includes an information element and the information element includes an identity for the UE. In certain embodiments, the method 1200 includes determining 1206 release information of the UE. In various embodiments, the method 1200 includes transmitting 1208 to a second network function: the identity; and the release information of the UE.

In certain embodiments, the second network function transmits at least one UE parameter update data set types to the UE based on the identity and the release information of the UE. In some embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof. In various embodiments, the second network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In some embodiments, the second network function comprises a UDM. In various embodiments, the UE stores at least one UE parameter update data set type.

FIG. 13 is a flow chart diagram illustrating a further embodiment of a method 1300 for determining release information based on registration information. In some embodiments, the method 1300 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 1300 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.

In various embodiments, the method 1300 includes receiving 1302, at a first network function, a UE state indication UPSI list message from a UE. The UE state indication UPSI includes at least one UPSC. In some embodiments, the method 1300 includes determining 1304 an identity and release information of the UE by analyzing the at least one UPSC. In certain embodiments, the method 1300 includes transmitting 1306 to a second network function: the identity; and the release information of the UE.

In certain embodiments, a third network function obtains the identity and the release information of the UE from the second network function. In some embodiments, the third network function transmits at least one UE parameter update data set types to the UE based on the identity and the release information of the UE. In various embodiments, the third network function comprises a UDM.

In one embodiment, the third network function determines at least one UE parameter update data set type that the UE supports based on the identity. In certain embodiments, the release information of the UE comprises at least one UE parameter update data set type that the UE supports. In some embodiments, the second network function and the third network function are collocated.

In various embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof. In one embodiment, the first network function comprises a PCF.

In certain embodiments, the second network function comprises a UDR. In some embodiments, the UE stores at least one UE parameter update data set type.

In one embodiment, an apparatus comprises a first network function, the apparatus further comprising: a receiver to receive a registration request message from a UE, wherein the registration request message comprises: an identity; at least one information element; and at least one UE capability; a processor to determine release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability; and a transmitter to transmit to a second network function: the identity; and the release information of the UE.

In certain embodiments, the second network function transmits at least one UE parameter update data set type to the UE based on the identity and the release information of the UE.

In some embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G S TMSI 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof.

In various embodiments, the second network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In one embodiment, the release information of the UE comprises at least one UE parameter update data set type that the UE supports.

In certain embodiments, the first network function comprises an AMF.

In some embodiments, the second network function comprises a UDM.

In various embodiments, the UE stores at least one UE parameter update data set type.

In one embodiment, a method at a first network function, the method comprising: receiving a registration request message from a UE, wherein the registration request message comprises: an identity; at least one information element; and at least one UE capability; determining release information of the UE by analyzing the identity, the at least one information element, and the at least one UE capability; and transmitting to a second network function: the identity; and the release information of the UE.

In certain embodiments, the second network function transmits at least one UE parameter update data set type to the UE based on the identity and the release information of the UE.

In some embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof.

In various embodiments, the second network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In one embodiment, the release information of the UE comprises at least one UE parameter update data set type that the UE supports.

In certain embodiments, the first network function comprises an AMF.

In some embodiments, the second network function comprises a UDM.

In various embodiments, the UE stores at least one UE parameter update data set type.

In one embodiment, an apparatus comprises a first network function, the apparatus further comprising: a transmitter to transmit an identity request message to a UE; a receiver to receive an identity response message from the UE, wherein the identity response message comprises an information element and the information element comprises an identity for the UE; and a processor to determine release information of the UE, wherein the transmitter further to transmit to a second network function: the identity; and the release information of the UE.

In certain embodiments, the second network function transmits at least one UE parameter update data set types to the UE based on the identity and the release information of the UE.

In some embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof.

In various embodiments, the second network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In one embodiment, the release information of the UE comprises at least one UE parameter update data set type that the UE supports.

In certain embodiments, the first network function comprises an AMF.

In some embodiments, the second network function comprises a UDM.

In various embodiments, the UE stores at least one UE parameter update data set type.

In one embodiment, a method at a first network function, the method comprises: transmitting an identity request message to a UE; receiving an identity response message from the UE, wherein the identity response message comprises an information element and the information element comprises an identity for the UE; determining release information of the UE; and transmitting to a second network function: the identity; and the release information of the UE.

In certain embodiments, the second network function transmits at least one UE parameter update data set types to the UE based on the identity and the release information of the UE.

In some embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof.

In various embodiments, the second network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In one embodiment, the release information of the UE comprises at least one UE parameter update data set type that the UE supports.

In certain embodiments, the first network function comprises an AMF.

In some embodiments, the second network function comprises a UDM.

In various embodiments, the UE stores at least one UE parameter update data set type.

In one embodiment, an apparatus comprises a first network function, the apparatus further comprising: a receiver to receive UE state indication UPSI list message from a UE, wherein the UE state indication UPSI comprises at least one UPSC; a processor to determine an identity and release information of the UE by analyzing the at least one UPSC; and a transmitter to transmit to a second network function: the identity; and the release information of the UE.

In certain embodiments, a third network function obtains the identity and the release information of the UE from the second network function.

In some embodiments, the third network function transmits at least one UE parameter update data set types to the UE based on the identity and the release information of the UE.

In various embodiments, the third network function comprises a UDM.

In one embodiment, the third network function determines at least one UE parameter update data set type that the UE supports based on the identity.

In certain embodiments, the release information of the UE comprises at least one UE parameter update data set type that the UE supports.

In some embodiments, the second network function and the third network function are collocated.

In various embodiments, the identity comprises a SUCI, a 5G-GUTI, IMEI, 5G-S-TMSI, IMEISV, MAC address, EUI-64, or a combination thereof.

In one embodiment, the first network function comprises a PCF.

In certain embodiments, the second network function comprises a UDR.

In some embodiments, the UE stores at least one UE parameter update data set type.

In one embodiment, a method at a first network function, the method comprising: receiving a UE state indication UPSI list message from a UE, wherein the UE state indication UPSI comprises at least one UPSC; determining an identity and release information of the UE by analyzing the at least one UPSC; and transmitting to a second network function: the identity; and the release information of the UE.