RU2783383C1 - Systems and method for safe updates of configuration parameters provided in user equipment - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: method includes: reception to user equipment (hereinafter – UE) from an element of an access and mobility management function (hereinafter – AMF) of the first non-access stratum (hereinafter – NAS) message containing a container, which contains update of a configuration parameter of UE, wherein the specified update of the configuration parameter of UE contains UE parameter incapsulated into a protected package; the first safety checking for checking the specified update of the configuration parameter of UE; and direction of the specified protected package to a universal subscriber identification module (hereinafter – USIM) made with the possibility of communication with the specified UE, if the specified first safety checking is successful, while the specified USIM is made with the possibility of the second safety checking for checking the specified protected package, and, if the specified second safety checking is successful, update of one or more of the specified configuration parameters of UE in the specified USIM based on the specified UE parameter incapsulated in the specified protected package.

EFFECT: provision of safe update of configuration parameters of UE, using NAS messages.

65 cl, 18 dwg, 9 tbl

Description

Related Applications

This ordinary patent application claims priority to U.S. Provisional Application No. 62/742,341, filed October 06, 2018, which is incorporated herein by reference in its entirety.

Technical field

This disclosure relates to the field of communication systems and, in particular, to updating mobile devices.

State of the art

Service providers or service providers implement mobile networks to offer multiple voice and data services to end users of mobile phones or other mobile devices/terminals commonly referred to as User Equipment (UE). Some examples of voice services are voice calls, call forwarding, call waiting, and so on. Some examples of data services are Internet access, audio streaming, video streaming, online games, Internet Protocol television (IP-TV), etc. A mobile network is a type of network in which the last link to the end user is wireless. The mobile network typically comprises a core network and one or more Radio Access Networks (RANs) that exchange signaling and data with the UE via an air interface.

The UE is typically provided with an International Mobile Subscriber Identity (IMSI), security authentication, encryption information, and other configuration parameters. There may be cases where the UE's home network needs to update one or more of the configuration parameters in the UE. For example, the UE's home network may update configuration parameters when there is a subscription change, when there is a new service assignment, when mobile networks migrate from Long-Term Evolution (LTE) networks to next generation networks, and so on. Therefore, it is advantageous to identify extended procedures for updating configuration parameters at the UE.

The essence of the invention

The embodiments described herein provide UE configuration parameter updates using Non-Access Stratum (NAS) messages. In general, mobile networks transitioning to next generation networks may include Unified Data Management (UDM) and Access and Mobility Management Function (AMF). The UDM, which resides in the UE's home network, is configured to assemble the UE configuration parameter update for the UE with security protection (eg, secure packet, integrity protection, etc.). The UDM sends an update of the security protected UE configuration parameter to the AMF. The AMF, in turn, is configured to transparently send a UE configuration parameter update to the UE using a NAS message. Again, the UE configuration parameter update is securely protected in the NAS message. The UE is configured to update its UE configuration parameters when receiving the NAS message based on the update provided in the NAS message. One of the technical advantages of this procedure is that end-to-end security is provided for updating the UE configuration parameters. Another technical advantage is that native control plane functionality can be used to update the UE configuration parameters. Thus, it is not necessary to deploy a dedicated network element to provide updates to the UE.

One embodiment comprises a mobile network AMF element. The AMF element contains a processor(s) and a storage device containing computer program code executable by the processor. The processor is configured to cause the AMF element to receive a control plane message from the UDM element containing an update of the UE configuration parameter for the UE. The specified UE configuration parameter update is securely protected according to the protection mechanism. The processor is further configured to cause the AMF element to insert the UE configuration parameter update that is securely protected into the first NAS message container, the container for updating the UE configuration parameter. The processor is further configured to cause the AMF element to send a first NAS message to the UE with a container containing the UE configuration parameter update that is securely protected.

In another embodiment, the UE configuration parameter update is encapsulated in a secure packet according to a security mechanism.

In another embodiment, the UE configuration parameter update is integrally secured using the UE's NAS security context in accordance with the security mechanism.

In another embodiment, the UE configuration parameter update is encapsulated in a secure packet, and the secure packet is integrally secured using the UE's NAS security context according to the security mechanism.

In another embodiment, the first NAS message contains a NAS registration confirmation message sent to the UE during the NAS registration procedure. The processor is further configured to cause the AMF element to receive a second NAS message from the UE during the NAS registration procedure with the container containing the UE confirmation that the UE configuration parameter update has been received and send another control plane message to the UDM element with the UE confirmation. The second NAS message received from the UE may contain an NAS registration in progress message or an uplink NAS transport message.

In another embodiment, the first NAS message contains a downlink NAS transport message of the NAS transport procedure performed after the NAS registration procedure. The processor is further configured to cause the AMF element to receive a second NAS message from the UE with a container containing a UE confirmation from the UE that the UE configuration parameter update has been received and send another control plane message to the UDM element with the UE confirmation. The second NAS message contains an uplink NAS transport message.

Another embodiment comprises a method for performing an update procedure to update the UE configuration parameters provided in the UE. Said method includes receiving a control plane message in an AMF element from a UDM element that contains an update of a UE configuration parameter for the UE. The specified UE configuration parameter update is securely protected according to the protection mechanism. The method further includes inserting, in the AMF element, a UE configuration parameter update that is securely protected into a container of the first NAS message, wherein the container is for updating the UE configuration parameter. The method further includes sending a first NAS message from the AMF element to the UE with a container containing the UE configuration parameter update that is securely protected.

In another embodiment, the UE configuration parameter update is encapsulated in a secure packet according to a security mechanism.

In another embodiment, the UE configuration parameter update is integrally secured using the UE's NAS security context in accordance with the security mechanism.

In another embodiment, the UE configuration parameter update is encapsulated in a secure packet, and the secure packet is integrally secured using the UE's NAS security context according to the security mechanism.

In another embodiment, the first NAS message contains the NAS registration confirmation message sent from the AMF element to the UE during the NAS registration procedure.

In another embodiment, the method further includes receiving a second NAS message in the AMF element from the UE during the NAS registration procedure with the container containing the UE confirmation that the UE configuration parameter update has been received and sending another control plane message from the AMF element to the element UDM with UE confirmation. The second NAS message may comprise an NAS registration in progress message or an uplink NAS transport message.

In another embodiment, the first NAS message contains a downlink NAS transport message of the NAS transport procedure performed after the NAS registration procedure.

In another embodiment, the method further includes receiving a second NAS message in the AMF element from the UE with a container containing a UE acknowledgment from the UE that the UE configuration parameter update has been received, and sending another control plane message from the AMF element to the UDM element with the acknowledgment U.E. The second NAS message contains an uplink NAS transport message.

In another embodiment, the method further includes receiving a first NAS message to the UE from an AMF element containing a container that contains a UE configuration parameter update for the UE that is securely protected, performing a security check at the UE to verify the UE configuration parameter update, and updating one or more of the UE configuration parameters based on the UE configuration parameter update when the UE configuration parameter update is verified.

In another embodiment, when the first NAS message contains a re-registration indicator, the method further includes initiating a NAS registration procedure at the UE to re-register using the updated UE configuration parameters.

Another embodiment comprises a UE that includes a Universal Integrated Circuit Card (UICC) that houses a Universal Subscriber Identity Module (USIM), a processor, and a memory containing computer program code executable by the processor. . One or both of the UICC and said storage device store UE configuration parameters for the UE. The processor is configured to cause the UE to receive a first NAS message from an AMF element containing a container that contains a UE configuration parameter update for the UE that is securely protected according to the protection mechanism. The UICC and/or the processor is configured to cause the UE to perform a security check to check for a UE configuration parameter update and update one or more of the UE configuration parameters based on the UE configuration parameter update when the UE configuration parameter update is verified.

In another embodiment, the UE configuration parameter update is encapsulated in a secure packet in the container of the first NAS message.

In another embodiment, the UE configuration parameter update is holistically secured using the UE's NAS security context.

In another embodiment, the UE configuration parameter update is encapsulated in a secure packet in the first NAS message container, and the secure packet is securely secured using the UE's NAS security context.

In another embodiment, the first NAS message contains a NAS registration confirmation message sent to the UE during the NAS registration procedure.

In another embodiment, when the NAS registration confirmation message contains a UE confirmation indicator, the processor is further configured to cause the UE to send a second NAS message to the AMF element with a container containing a UE confirmation from the UE that the UE configuration parameter update has been received. The second NAS message may comprise an NAS registration in progress message or an uplink NAS transport message.

In another embodiment, the first NAS message contains a downlink NAS transport message of the NAS transport procedure performed after the NAS registration procedure.

In another embodiment, when the downlink NAS transport message contains a UE confirmation indicator, the processor is further configured to cause the UE to send an uplink NAS transport message to the AMF element with a container containing a UE confirmation from the UE that the UE configuration parameter update was received.

In another embodiment, when the first NAS message contains a re-registration indicator, the processor is further configured to direct the UE to initiate a NAS registration procedure to re-register using the updated UE configuration parameters.

Another embodiment comprises an AMF element that contains means for receiving a control plane message from a UDM element containing an update of a UE configuration parameter for the UE. The specified update of the UE configuration parameter is securely protected according to the protection mechanism. The AMF element further comprises means for inserting the UE configuration parameter update that is securely protected into the first NAS message container, and means for sending the first NAS message to the UE with the container containing the UE configuration parameter update that is securely protected.

Another embodiment includes a UE that contains means for storing UE configuration parameters for the UE. The UE further comprises means for receiving a first NAS message from an AMF element containing a container that contains a UE configuration parameter update for the UE that is securely protected according to the protection mechanism, means for performing a security check for checking the update of the UE configuration parameter, and means for updating one or more of the UE configuration parameters based on the UE configuration parameter update when the UE configuration parameter update is verified.

The above summary of the invention gives an overview of some aspects of this description of the invention. This summary of the invention is not a detailed overview of the description of the invention. It is intended neither to identify key or critical elements of the specification nor to delineate any scope of specific embodiments of the specification or any scope of the claims. Its sole purpose is to present some of the concepts of the description of the invention in a simplified form as an introduction to the more detailed description below.

Brief description of graphic materials

Some embodiments of the present invention will now be described solely by way of example with reference to the accompanying drawings. The same reference number represents the same element or the same type of element in all drawings.

Fig. 1 illustrates a mobile network in an exemplary embodiment.

Fig. 2 illustrates an Evolved Packet Core (EPC) network.

Fig. 3 illustrates a non-roaming next generation network architecture.

Fig. 4 illustrates the next generation network roaming architecture.

Fig. 5 illustrates the radio protocol stack.

Fig. 6 is a block diagram of a UE in an exemplary embodiment.

Fig. 7 is a functional model for a UE in an exemplary embodiment.

Fig. 8 is a block diagram of an AMF element in an exemplary embodiment.

Fig. 9 is a block diagram of a UDM element in an exemplary embodiment.

Fig. 10 is a flowchart illustrating a method for performing an update procedure on a UDM element in an exemplary embodiment.

Fig. 11 is a flowchart illustrating a method for performing an update procedure in an AMF element in an exemplary embodiment.

Fig. 12 is a flowchart illustrating a method for performing an update procedure in a UE in an exemplary embodiment.

Fig. 13 is a message diagram illustrating an update procedure during registration in an exemplary embodiment.

Fig. 14 is a message diagram illustrating an update procedure after registration in an exemplary embodiment.

Fig. 15 is a message diagram illustrating an update procedure during registration in an exemplary embodiment.

Fig. 16 is a message diagram illustrating an update procedure after registration in an exemplary embodiment.

Fig. 17 is a message diagram illustrating an update procedure during registration in an exemplary embodiment.

Fig. 18 is a message diagram illustrating the update procedure after registration in the exemplary embodiment.

Description of Embodiments

These figures and the following description illustrate specific exemplary embodiments. Thus, it will be appreciated that those skilled in the art will be able to develop various devices that, although not expressly described or shown herein, embody the principles of the embodiments and are included within the scope of the embodiments. In addition, any examples described herein are intended to assist in understanding the principles of the embodiments and should be construed as not limiting such specifically listed examples and conditions. As a result, the concept (ideas) of the invention is not limited to the specific embodiments or examples described below, but by the claims and their equivalents.

Fig. 1 illustrates a mobile network 100 in an exemplary embodiment. The mobile network 100 (also referred to as a cellular network) is a type of network in which the last link is wireless and provides voice and/or data services to a plurality of devices. Mobile network 100 may be a third generation network (Third Generation - 3G), fourth generation (Fourth Generation - 4G) and/or a next generation network (eg, fifth generation (5G)).

Mobile network 100 is illustrated as providing communications services to UE 110 (along with other UEs not shown). UE 110 may be used for voice services, data services, Machine-to-Machine (M2M) or Machine Type Communication (MTC) services, Internet of Things (IoT) services, and/or other services. UE 110 may be an end user device such as a mobile phone (eg, smartphone), a tablet or PDA, a computer with a mobile broadband adapter, and so on.

Mobile network 100 comprises one or more radio access networks (RANs) 120 that communicate with UE 110 via air interface 122. RAN 120 may support access to an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) , access to a wireless local area network (Wireless Local Area Network - WLAN), fixed access, satellite radio access, new radio access technologies (Radio Access Technologies - RAT), etc. By way of example, RAN 120 may comprise an E-UTRAN or a Next Generation RAN (NG-RAN) that contains one or more base stations 124 dispersed over a geographic area. Base station 124 may include an entity that uses radio technology to communicate with UEs in the licensed spectrum and interface the UE with a core network. Base stations 124 in E-UTRAN are referred to as evolved Node Bs (Evolved-NodeBs - eNodeB). Base stations 124 in NG-RAN are referred to as gNodeB (NR base stations) and/or ng-eNodeB (LTE base stations supporting 5G core network). As another example, RAN 120 may contain a WLAN that contains one or more points 125 wireless access (Wireless Access Points - WAP). WLAN is a network in which a UE can connect to a Local Area Network (LAN) via a wireless (radio) connection. The WAP 125 is a node that uses a radio technology to communicate with a UE in the unlicensed spectrum and provides the UE with access to the core network. One example of a WAP 125 is a Wi-Fi access point that operates on the 2.4 GHz or 5 GHz radio bands. As used herein, the term "base station" may refer to eNodeB, gNodeB, ng-eNodeB, WAP, etc.

UE 110 have the ability to connect to cell 126 of RAN 120 to access core network 130. Thus, RAN 120 is the air interface between UE 110 and core network 130. Core network 130 is the central part of mobile network 100, which provides various services to clients connected with RAN 120. One example of core network 130 is the Evolved Packet Core (EPC) network proposed by 3GPP for LTE. Another example of a core network 130 is a 5G core network proposed by 3GPP. The core network 130 includes network elements 132, which may include servers, devices, apparatuses, or equipment (including hardware) that provide services to UE 110. The network elements 132 in the EPC network may contain a Mobility Management Entity (MME) Gateway - S-GW), Packet Data Network Gateway - P-GW, etc. The network elements 132 in a 5G network may comprise an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), an Application Function (AF), a Plane user (User Plane Function - UPF), etc.

Fig. 2 illustrates an Evolved Packet Core (EPC) network 200, which is the core network for LTE. The EPC network 200 includes a mobility management entity (MME) 214, a serving gateway (S-GW) 215, a packet data network (P-GW) gateway 216, a Home Subscriber Server (HSS) 217, and a policy function 218 and charging rules (Policy and Charging Rules Function - PCRF), but may contain other elements not shown, such as IP Multimedia Subsystem (IMS) application servers. In the EPC network 200, user data (also referred to as "user plane") and signaling (also referred to as "control plane") are separated. The MME 214 handles the control plane in the EPC network 200. For example, MME 214 handles signaling related to mobility and security for E-UTRAN access. MME 214 is responsible for tracking and paging UE 110 in idle mode. S-GW 215 and P-GW 216 handle the user plane. S-GW 215 and P-GW 216 transport data traffic between UE 110 and external data networks 240 (DN or Packet Data Network (PDN)). The S-GW 215 is the interconnection point between the radio side and the EPC network 200 and serves the UE 110 by routing incoming and outgoing IP packets. S-GW 215 is also the anchor point for intra-LTE mobility (ie in case of handover between eNodeB) and between LTE and other accesses from 3GPP. The P-GW 216 is the interconnection point between the EPC network 200 and the external data networks 240 (ie, the entry or exit point for the data network 240) and routes packets to and from the data network 240 . HSS 217 is a database that stores information related to users and related to subscribers. The PCRF 218 provides a Policy and Charging Control (PCC) solution in the EPC 200 network and is a node or entity in the EPC network 200 that formulates PCC rules for services requested by an end user.

MME 214 is connected to RAN 120 (ie eNodeB) via S1-MME interface, and S-GW 215 is connected to RAN 120 via S1-U interface. MME 214 connects to S-GW 215 via S11 interface, and connects to HSS 217 via S6a interface. The PCRF 218 is connected to the P-GW 216 via a Gx interface, which allows the transfer of policy and charging rules from the PCRF 218 to the Policy and Charging Enforcement Function (PCEF) in the P-GW 216. The PCRF 218 is connected to the S- GW 215 via Gxx interface and S-GW 215 is connected to P-GW 216 via S5 interface.

Fig. 3 illustrates a non-roaming next generation network architecture 300. The architecture in Fig. 3 is a reference point representation as further described in 3GPP TS 23.501 (v15.3.0), which is incorporated herein by reference in its entirety. Architecture 300 consists of network functions (Network Function - NF) for the core network, and the network functions for the control plane are separated from the user plane. The backbone control plane contains an Authentication Server Function (AUSF) function 310, a single data management (UDM) 312, a Network Slice Selection Function (NSSF) 313, an access and mobility management (AMF) function 314, a 316 session management (Session Management Function - SMF), function 318 policy management (PCF) and function 320 applications (AF). The backbone user plane contains one or more user plane functions (UPFs) 324 that communicate with the data network 240 . UE 110 may access the control plane and user plane of the core network via the (R)AN 120.

AUSF 310 is configured to support authentication of UE 110. UDM 312 is configured to store subscription data/information for UE 110. UDM 312 may store three types of user data: subscription, policy, and session-related context (eg, UE location). AMF 314 is configured to provide UE-based authentication, authorization, mobility management, and so on. The SMF 316 is configured to provide the following functions: session management (SM), UE Internet Protocol (IP) address allocation and management, UPF selection and management, termination of interfaces to the PCF 318, policy enforcement and quality control part Quality of Service (QoS), police interception, SM termination of NAS message parts, Downlink Data Notification (DNN), roaming function, local enforcement processing for applying QoS for Service Level Agreements Agreement - SLA), billing data collection and billing interface, etc. If UE 110 has multiple sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionality for each session. The PCF 318 is configured to support a unified policy framework for managing network behavior and providing policy rules for control plane functions for QoS enforcement, billing, access control, traffic routing, and so on. AF 320 provides packet flow information to PCF 318. PCF 318 is configured to determine mobility and session control policy rules based on said information so that AMF 314 and SMF 316 work properly.

UPF 324 supports various user plane operations and functions such as packet routing and forwarding, traffic processing (e.g., QoS enforcement), Intra-RAT/Inter-RAT mobility anchor point (if applicable), packet inspection, and policy enforcement. , police interception (UP collection), traffic accounting and reporting, etc. The data network 240 is not part of the core network and provides Internet access, operator services, third party services, and so on. For example, the International Telecommunication Union (ITU) has classified 5G mobile network services into three categories: Enhanced Mobile Broadband (eMBB), Ultra-reliable and Low-Latency Communications (uRLLC) and Massive Machine Type Communications (mMTC) or Massive Internet of Things (MIoT). eMBB focuses on high bandwidth services such as HD video, Virtual Reality (VR) and Augmented Reality (AR). uRLLC focuses on delay-sensitive services such as automated driving and remote control. mMTC and MIoT focus on services that have high connectivity requirements such as smart city and smart agriculture. Communication network 240 may be configured to provide these and other services.

Architecture 300 contains the following reference points. The N1 reference point is implemented between UE 110 and AMF 314. The N2 reference point is implemented between (R)AN 120 and AMF 314. The N3 reference point is implemented between (R)AN 120 and UPF 324. The N4 reference point is implemented between SMF 316 and UPF 324. Reference point N5 is implemented between PCF 318 and AF 320. Reference point N6 is implemented between UPF 324 and data network 240. Reference point N7 implemented between SMF 316 and PCF 318. Reference point N8 implemented between UDM 312 and AMF 314. Reference point N9 implemented between two UPF 324. Reference point N10 implemented between UDM 312 and SMF 316. Reference point N11 implemented between AMF 314 and SMF 316. Reference point N12 is implemented between AMF 314 and AUSF 310. Reference point N13 is implemented between UDM 312 and AUSF 310. Reference point N14 is implemented between two AMFs. Reference point N15 is implemented between PCF 318 and AMF 314 in case of non-roaming scenario. Reference point N22 implemented between NSSF 313 and AMF 314.

Fig. 4 illustrates a next generation network roaming architecture 400. The architecture in Fig. 4 is a local breakout scenario in the reference point representation, as further described in 3GPP TS 23.501 (v15.3.0). The roaming scenario shows a Visited Public Land Mobile Network (VPLMN) 402 and a Home PLMN (HPLMN) 404. The HPLMN 404 identifies the PLMN that stores the mobile subscriber profile. The VPLMN is the PLMN on which the mobile subscriber roamed when leaving his HPLMN. Users roaming to other networks will receive subscription information from HPLMN 404. In a local breakthrough scenario, PCF 318 (hPCF), UDM 312 and AUSF 310 are in HPLMN 404 for UE 110. Other network functions containing visited PCF (visited PCF - vPCF) 418 are in VPLMN 402.

Fig. 5 illustrates a radio protocol stack 500, for example, for air interface 122. As described herein, user plane 512 contains a set of protocols used to transfer actual user data over a network, and control plane 514 contains protocols used to manage and establish user connections and channels on the network. For the user plane 512 and the control plane 514, the radio protocol stack 500 comprises a physical (PHY) layer 501, a Medium Access Control (MAC) layer 502, a Radio Link Control (RLC) layer 503, and a layer 504 Packet Data Convergence Protocol (PDCP). The control plane 514 further comprises a Radio Resource Control (RRC) layer 505 and a Non-Access Layer (NAS) layer 506.

The physical layer 501 carries all information from the MAC transport channels over the air interface. Data and signaling messages are carried over physical channels between different layers of the physical layer 501. Physical channels are divided into physical data channels and physical control channels. The physical data channels may include a Physical Downlink Shared Channel (PDSCH), a Physical Broadcast Channel (PBCH), a Physical Multicast Channel (PMCH), a Physical Uplink Shared Channel ( Physical Uplink Shared Channel - PUSCH) and physical random access channel (Physical Random Access Channel - PRACH). The physical control channels may include a Physical Control Format Indicator Channel (PCFICH), a Physical Hybrid ARQ Indicator Channel (PHICH), a Physical Downlink Control Channel (PDCCH), and a Physical Uplink Control Channel. communication line (Physical Uplink Control Channel - PUCCH).

MAC layer 502 is responsible for mapping between logical channels and transport channels, multiplexing MAC service data units (SDU) from one or different logical channels into transport blocks (transport block - TB) that will be delivered to the physical layer over transport channels , demultiplexing MAC SDUs from one or different logical channels from transport blocks delivered from the physical layer over transport channels, reporting scheduling information, error correction with Hybrid Automatic Repeat Request (HARQ), processing priorities between UEs by dynamic scheduling, priority processing between logical channels of the same UE, and logical channel prioritization. Layer 503 RLC is responsible for the transmission of blocks of protocol data (Protocol Data Unit - PDU) of the upper layer, error correction through ARQ and concatenation, segmentation and reassembly of the RLC SDU. The RLC layer 503 is also responsible for RLC PDU data resegmentation, RLC PDU data reordering, duplication detection, RLC SDU reset, RLC reestablishment, and protocol error detection. PDCP layer 504 is responsible for header compression and IP data decompression, data transfer (user plane or control plane), maintenance of PDCP sequence numbers (Sequence Number - SN), sequential delivery of upper layer PDUs during lower layer re-establishment, redundant elimination of lower layer SDUs when restoring lower levels for radio bearers mapped in RLC Acknowledged Mode (AM), encryption and decryption of user plane data and control plane data, integrity protection and control plane data integrity checking, timer-based drop, drop duplicate, etc. d. The RRC layer 505 is responsible for broadcasting NAS-related system information, broadcasting access layer (AS)-related system information, paging, establishing, maintaining, and releasing an RRC connection between UE and RAN, security functions including key management, establishing , configuration, maintenance and release of point-to-point radio channels (Radio Bearer - RB). The NAS layer 506 represents the highest layer of the control plane 514 between the UE and the core network (eg, MME/AMF) and supports UE mobility and session management procedures for establishing and maintaining an IP connection between the UE and the core network.

Each UE 110 receiving services from a mobile network is provided with configuration parameters. The home network (ie HPLMN) may want to update one or more of the configuration parameters at the UE. In previous mobile networks, configuration parameter updates were performed using an over-the-air (OTA) mechanism. The OTA mechanism required the deployment of a specialized network element called an OTA gateway. When the configuration parameter update was completed, the network operator's internal system sent service requests to the OTA gateway. Different OTA "channels" have been specified for sending the service request to the UE, such as Short Message Services (SMS), Unstructured Supplementary Service Data (USSD), HyperText Transfer Protocol (HTTP). ) etc. The OTA gateway mapped said service requests to OTA "channels" for service requests to be sent to the UE. For example, when an SMS channel was used, the OTA gateway encapsulated the updated configuration settings in one or more SMS messages. The OTA gateway then sent the SMS messages to the SMS Center (SMSC), which forwarded the SMS messages to the UE. It is desirable to provide a native control plane solution that a network operator can use to update UE configuration parameters without the need to deploy a dedicated network element such as an OTA gateway. It is also desirable to provide a solution in which the configuration parameters of the UE are securely protected.

In the embodiments described herein, the network transparently sends a securely secure UE configuration parameter update to the UE via a control plane NAS message. For example, an update of a UE configuration parameter may be securely protected using a secure packet, using a NAS security context integrity protection key, or both. Upon receiving the UE configuration parameter update in the NAS message, the UE may update its UE configuration parameters. The solution proposed in this document is described in relation to a next generation network (eg, 5G), but similar solutions can be provided in networks of earlier or later generations. More detailed information about the embodiments is provided below.

Fig. 6 is a block diagram of UE 110 in an exemplary embodiment. UE 110 includes an air interface component 602, one or more processors 604, a memory 606, a user interface component 608, and a battery 610. Air interface component 602 is a hardware component that represents the local radio resources of UE 110, such as an RF unit 620 (e.g., transceiver) and one or more antennas 622 used for wireless communication with a base station (eg, base station 124) via radio or "over the air" signals. Processor 604 is the internal circuitry, logic, hardware, software, etc. that provides the functions of UE 110. Processor 604 may be configured to execute software instructions 640 that are loaded into memory 606. Processor 604 may contain a set of one or more processors, or may contain a multiprocessor core, depending on the specific implementation. Processor 604 may implement one or more applications 630. These applications 630 may access downlink (DL) data via RAN 120 and core network 130, and may also generate uplink (UL) data for transmission. to the destination via RAN 120 and backbone 130. Memory 606 is a computer-readable medium for storing data, instructions 640, applications, and so on. and is available to processor 604. Memory 606 is a hardware storage device capable of storing information on a temporary and/or permanent basis. The storage device 606 may include random-access memory (RAM) or any other volatile or non-volatile storage device. Component 608 user interface is a hardware component for interaction with the end user. For example, the user interface component 608 may include a display 650, a screen, a touch screen, and the like. (for example, liquid crystal display (Liquid Crystal Display - LCD), LED (Light Emitting Diode - LED) display, etc.). The user interface component 608 may include a keyboard or keypad 652, a tracking device (eg, a trackball or trackpad), a speaker, a microphone, and so on.

UE 110 also includes a Universal Integrated Circuit Card (UICC) 660, which is a hardware device that provides security and integrity functions to UE 110. Although not shown in FIG. 6, the UICC 660 may include a processor (i.e., a Central Processing Unit (CPU)), a storage device (i.e., Read-Only Memory (ROM), RAM, an Electrically Erasable Programmable Read-Only Memory - EEPROM)) and input / output circuits (Input / Output - I / O). The UICC 660 may contain or store a Universal Subscriber Identity Module (USIM) 662 that stores information such as International Mobile Subscriber Identity (IMSI), authentication and encryption security information, and other home operator configuration information.

UICC 660 and/or memory 606 may store home operator information that is used to configure UE 110, referred to herein as UE configuration parameters 664. One or more of the UE configuration parameters 664 may be used exclusively by the UICC 660, and one or more of the UE configuration parameters 664 may be used by the processor 604. The UE configuration parameters 664 may include a routing indicator, a home network identifier (eg, a PLMN identifier, and MCC/MNC information), home network security scheme ID, home network public key ID, home network public certificates, network selection information (eg, operator controlled PLMN selector with access technology list) and/or other information. The UE configuration parameters 664 may represent data previously provided by the network operator or data provided by the network, for example, through an update procedure as described below. UE 110 may include various other components not specifically illustrated in FIG. 6.

Fig. 7 is a functional model for UE 110 in an exemplary embodiment. UE 110 may be subdivided into domains such as Mobile Equipment (ME) 702 and USIM 662. As described above, functions for USIM 662 may be performed by a processor and storage device at UICC 660. Functions for ME 702 may be performed by processor 604 and storage device 606. ME 702 performs radio transmission and contains applications. USIM 662 contains data and procedures that uniquely and securely identify themselves. These functions are typically built into a stand-alone smart card such as a UICC 660. As noted above, one or more of the UE configuration parameters 664 may be stored exclusively in the USIM 662 for use or processing by the UICC 660, and one or more of the UE configuration parameters 664 UE configurations may be stored exclusively in the ME 702 for use or processing in the ME 702.

Fig. 8 is a block diagram of an AMF element 314 in an exemplary embodiment. As described above, the AMF element 314 is configured to provide authentication, authorization, mobility management, and so on. based on UE. In this embodiment, the AMF element 314 contains the following subsystems: a network interface component 802 and an update manager 804 that run on one or more platforms. Network interface component 802 may include circuitry, logic, hardware, facility, etc., configured to exchange control plane messages or signaling with other network elements and/or UEs (eg, via RAN 120). The network interface component 802 may operate using a variety of protocols (including the NAS protocol) or reference points. The update manager 804 may contain circuitry, logic, hardware, means, etc., configured to handle updates to UE configuration parameters on the UE. One or more of the subsystems of AMF element 314 may be implemented on a hardware platform consisting of analog and/or digital circuitry. One or more of the subsystems of AMF element 314 may be implemented in a processor 830 that executes instructions stored in memory 832. Processor 830 includes an integrated hardware circuit configured to execute the instructions, and memory 832 is a machine-readable, non-volatile storage medium for data, instructions, applications, etc. and available to processor 830. AMF element 314 may include various other components not specifically illustrated in FIG. eight.

Fig. 9 is a block diagram of a UDM element 312 in an exemplary embodiment. As described above, UDM element 312 is configured to store access and mobility subscription data for the UE. In this embodiment, the UDM element 312 contains the following subsystems: a network interface component 902, a subscriber data repository 904, and an update manager 906 that run on one or more platforms. The network interface component 902 may include circuitry, logic, hardware, facility, etc. configured to exchange control plane messages or signaling with other network elements. The network interface component 902 may operate using multiple protocols or reference points. Subscriber data repository 904 may contain circuitry, logic, hardware, facility, etc. configured to store access and mobility subscription data. The update manager 906 may include circuitry, logic, hardware, means, etc., configured to handle updates to UE configuration parameters on the UE. One or more of the subsystems of UDM element 312 may be implemented on a hardware platform consisting of analog and/or digital circuitry. One or more of the subsystems of UDM element 312 may be implemented in a processor 930 that executes instructions stored in memory 932. UDM element 312 may include various other components not specifically illustrated in FIG. 9.

The update procedure may be performed or called when the UE registers with the network or after the UE registers with the network. Fig. 10-12 illustrate the general update procedure performed by UDM element 312, AMF element 314, and UE 110. Additional details of the update procedure are described in the message map examples below. Therefore, the flowcharts provided herein may be supplemented by the update procedures described in connection with the message schemas.

Fig. 10 is a flowchart illustrating a method 1000 for performing an update procedure in UDM element 312 in an exemplary embodiment. The steps of method 1000 will be described with reference to UDM element 312 in FIG. 9, but those skilled in the art will appreciate that method 1000 may be performed in other network elements or devices. In addition, the steps of the flow charts described herein are not exhaustive and may include other steps not shown, and the steps may be performed in an alternative order.

For this embodiment, it can be assumed that the UE 110 registers with the network through the NAS registration procedure or is already registered with the network. Update manager 906 of UDM element 312 initiates an update procedure to update one or more of the UE configuration parameters 664 at UE 110 (block 1002). For example, the update manager 906 may process the UE configuration information stored in the subscriber data repository 904 and determine whether an update of the UE configuration parameters 664 is required or desirable. The update manager 906 collects the UE configuration parameter update for UE 110 (block 1004). A UE configuration parameter update contains information, a command, an instruction, etc. used to perform a UE configuration parameter update 664 at UE 110. For example, a UE configuration parameter update may contain one or more updated UE configuration parameters for UE 110 as part of the data. access and mobility subscriptions.

The update manager 906 applies security protection to the UE configuration parameter update (block 1006) in accordance with one or more protection mechanisms. In one embodiment, the protection mechanism may be a protected packet. Thus, the update manager 906 may customize or encapsulate the UE configuration parameter update in a secure package to apply security protection (optional step 1008). Typically, a protected packet contains application messages to which certain mechanisms have been applied. Application messages are commands or data exchanged between the network element and the UICC. The sender adds a security header (command header) to the application message and then applies the requested security to the command header part and the entire application message. The resulting structure is called a (protected) command packet, which contains the protected data as payload. The update manager 906 can access a local secure package library or a remote secure package library to configure or encapsulate a UE configuration parameter update in a secure package. In another embodiment, the protection mechanism may be an integrity protection. Thus, update manager 906 may apply integrity protection in updating a UE configuration parameter using the NAS security context for UE 110 (optional step 1010). NAS security is used to securely deliver NAS signaling messages between UE 110 and AMF element 314 in the control plane using NAS security keys. The NAS security context is a set of NAS security keys and settings used to secure NAS messages. NAS security keys are generated when UE 110 authenticates to the network. Thus, after authentication, the update manager 906 can apply integrity protection in updating the UE configuration parameter using the integrity protection key of the NAS security context. In yet another embodiment, the update manager 906 may use both a secure packet and a NAS security context to secure an update of a UE configuration parameter (optional step 1012). The update manager 906 may then insert or otherwise include the securely protected update of the UE configuration parameter in the control plane message (block 1014).

The update manager 906 may also embed or otherwise include a UE acknowledgment indicator in the control plane message (optional step 1016). The UE confirmation indicator may be turned on when the home network requires confirmation from the UE 110 that the UE configuration parameter update security check was successful. The update manager 906 may also embed or otherwise include a re-registration indicator in the control plane message (optional step 1016). The re-registration indicator may be turned on when the home network wants UE 110 to re-register with the network with updated UE configuration parameters. The update manager 906 then sends a control plane message to the AMF element 314 that contains the securely secure update of the UE configuration parameter (block 1018) and the UE confirmation indicator and/or re-registration indicator (if requested) via the network interface component 902.

Fig. 11 is a flowchart illustrating a method 1100 for performing an update procedure in AMF element 314 in an exemplary embodiment. The steps of method 1100 will be described with reference to AMF element 314 in FIG. 8, but those skilled in the art will appreciate that method 1100 may be performed in other network elements or devices.

Update manager 804 of AMF element 314 receives a control plane message from UDM element 312 that contains a securely secure update of the UE configuration parameter (block 1102) via network interface component 802. The update manager 804 inserts the securely protected UE configuration parameter update into the NAS message container (block 1104). The transmission of a securely secure UE configuration parameter update is considered "transparent" to AMF element 314. Thus, the update manager 804 is programmed to send a securely protected update of the configuration parameter to the UE without modifying or changing the update of the configuration parameter of the UE. The update manager 804 may therefore insert the securely secure UE configuration parameter update received in the control plane message from UDM element 312 into a "transparent" container that is dedicated to updating the UE configuration parameter. One example of such a transparent container is described in more detail below.

The type of NAS message used by AMF element 314 to transport a securely protected update of a UE configuration parameter may depend on the NAS procedure being performed. For example, when the NAS registration procedure is performed, the NAS message may contain a NAS registration confirmation message. When the NAS transport procedure is performed, the NAS message may contain a DL NAS transport message. The update manager 804 then sends a NAS message to the UE 110 (step 1106) via the network interface component 802.

Fig. 12 is a flowchart illustrating a method 1200 for performing an update procedure at UE 110 in an exemplary embodiment. The steps of method 1200 will be described with reference to UE 110 in FIG. 6-7, but those skilled in the art will appreciate that method 1200 may be performed in other devices.

UE 110 (eg, via ME 702) receives a NAS message from AMF element 314 (block 1202). The ME 702 or USIM 662 performs a security check to ensure that the securely secure UE configuration parameter update included in the NAS message container is provided by the home network (ie HPLMN) to the UE 110 (block 1204). For example, ME 702 or USIM 662 may compute a checksum to determine if the received securely secure UE configuration parameter update matches the securely secure UE configuration parameter update sent by UDM element 312. When the security check is not successful, the ME 702 or USIM 662 discards the securely secure UE configuration parameter update (block 1206). When the security check is successful, ME 702 or USIM 662 updates one or more UE configuration parameters 664 provided to UE 110 based on the UE configuration parameter update (block 1208). As described above, the UE configuration parameter update may be encapsulated in a secure packet. In this scenario, the USIM 662 is configured to decode or decompress the UE configuration parameter update from the secure package using the secure package library. The USIM 662 then updates one or more of the UE configuration parameters 664 locally to the USIM 662 based on the UE configuration parameter update.

When the NAS message contains a UE acknowledgment indicator, ME 702 or USIM 662 sends a NAS message to AMF element 314 with a container containing the UE acknowledgment (optional step 1210). The transmission of the UE acknowledgment is considered "transparent" to AMF element 314. Thus, the ME 702 or USIM 662 is programmed to insert the UE acknowledgment into a "transparent" container that is intended for the UE acknowledgment. One example of such a transparent container is described in more detail below.

The type of NAS message may depend on the NAS procedure being executed. For example, when the NAS registration procedure is performed, the NAS message may contain a NAS registration confirmation message or a NAS UL transport message. When the NAS transport procedure is performed, the NAS message may contain a NAS UL transport message.

In FIG. 11, update manager 804 of AMF element 314 receives a NAS message from UE 110 with a container containing a UE acknowledgment (optional step 1108) via network interface component 802. The update manager 804 then sends a control plane message to the UDM element 312 with an acknowledgment to the UE (optional step 1110) via the network interface component 802. In FIG. 10, update manager 906 of UDM element 312 receives a UE acknowledgment control plane message from AMF element 314 (optional step 1020) via network interface component 902. The update manager 906 then checks that the UE acknowledgment has been provided by the UE 110 (optional step 1022).

In FIG. 12, when the NAS message from AMF element 314 contains a re-registration indicator, UE 110 (eg, via ME 702) initiates a NAS registration procedure to re-register using the updated UE configuration parameters (optional step 1212). After that, the update procedure may be completed.

The following are examples of performing the update procedure in additional embodiments.

Example 1: Update procedure during registration using secure package

Fig. 13 is a message diagram illustrating an update procedure during registration in an exemplary embodiment. In this embodiment, UE 110 is in an idle mode (eg, RRC_IDLE). UE 110 initiates the NAS registration procedure by sending a NAS registration request to AMF element 314 (S1). In response to a NAS registration request (of type "initial"), AMF element 314 may initiate an authentication procedure (S2) to authenticate UE 110. For the authentication procedure, AMF element 314 may interact with AUSF element 310 and UDM element 312. For example, AMF element 314 may send an authentication request (ie, Nausf_UEAuthentication_Authenticate Request) to AUSF element 310. In response to receiving the authentication request, the AUSF element 310 may send an authentication request (ie, a Nudm_UEAuthentication_Get Request) to the UDM element 312. Element 312 UDM contains functions associated with the function of the repository and processing authentication credentials (Authentication Credential Repository and Processing Function - ARPF), which selects an authentication method and calculates authentication data and key materials (for example, tokens) for element 310 AUSF (if necessary) . UDM element 312 may send an authentication response (ie Nudm_UEAuthentication_Get Response) to AUSF element 310 that contains an authentication vector (AV) and other information. The AUSF element 310 may then send an authentication response (ie Nuasf_UEAuthentication_Authenticate Response) to the AMF element 314 which contains the AV and other information. The AMF element 314 is configured to perform an authentication procedure with the UE 110 using the information provided by the UDM/AUSF. For example, AMF element 314 may send an authentication request to UE 110 along with an authentication token from the AV, and UE 110 tries to verify the authentication token. If successful, UE 110 computes a response token and sends an authentication response with a response token, which is received by AMF element 314. AMF element 314 may format or generate another authentication request (ie, Nausf_UEAuthentication_Authenticate Request) and insert a response token from UE 110 into the authentication request along with other information. The AMF element 314 may then send an authentication request to the AUSF element 310. AUSF element 310 may check if the response token from UE 110 matches the expected response token and send an authentication response (ie, Nausf_UEAuthentication_Authenticate Response) to AMF element 314 indicating authentication success/failure.

Upon authentication, AMF element 314 may initiate a NAS security procedure to establish a NAS security context (S3). As part of the NAS security procedure, AMF element 314 selects the NAS security algorithm (or multiple algorithms) for encryption and integrity protection. AMF element 314 then sends a security mode command message to UE 110 that indicates the NAS security algorithm(s), ngKSI, and other information. UE 110 uses ngKSI and the NAS security algorithm to determine the appropriate keys to secure subsequent NAS messages. Thus, a NAS security context is established between UE 110 and AMF element 314 . UE 110 then sends a security mode completion message to AMF element 314 .

As an additional part of the NAS registration procedure, AMF element 314 sends a subscription data request (eg, Nudm_SDM_Get message) to HPLMN UDM element 312 to obtain access and mobility subscription data for UE 110, among other information (S4). When the user's subscription information indicates the initiation of a UE configuration parameter update (eg, a routing ID update), the UDM element 312 initiates an update procedure. UDM element 312 collects a UE configuration parameter update that contains one or more updated UE configuration parameters. UDM element 312 then applies security protection to the UE configuration parameter update by referring to the secure package library to encapsulate the UE configuration parameter update in a secure package. An example of secure packets and the structure of secure packets is disclosed in 3GPP TS 131.115 (v.9.0.0), which is incorporated by reference as if it were incorporated herein in its entirety. UDM element 312 then sends a subscription data response (eg, Nudm_SDM_Get response) to AMF element 314 (S5) that contains the secure packet. UDM element 312 may also include a UE confirmation indicator and/or a re-registration indicator in the subscription data response.

As another part of the registration procedure, AMF element 314 may also send a subscribe message (eg, Nudm_SDM_Subscribe) to UDM element 312 to subscribe to a change notification for UE configuration parameters (not shown in FIG. 13).

The AMF element 314 is configured to transparently send a secure packet to UE 110 as part of the update procedure. Thus, the AMF element 314 formats or generates the NAS Registration Confirmation message and inserts the secure packet into the container of the NAS Registration Confirmation message. AMF element 314 may also insert a UE acknowledgment indicator and/or a re-registration indicator (if applicable) into the container of the NAS registration acknowledgment message. Then, AMF element 314 sends a NAS registration confirmation message to UE 110 (S6).

In this embodiment, the NAS registration confirmation message container is for updating the configuration parameter of the UE. Table 1 illustrates an example message content for a NAS registration confirmation message.

Table 1:

IEI Information element Type/Reference Presence Format Length Extended protocol discriminator Extended protocol discriminator M V one Security header type Security header type M V 1/2 Reserved semi-octet Reserved semi-octet M V 1/2 Registration confirmation message identification Message type M V one … xx UE Configuration Parameter Update Container UE Configuration Parameter Update Container O TLV-E 20-2048 …

In this example, the NAS registration confirmation message contains a newly defined information element (IE) of the UE configuration parameter update container. Additional description of the NAS protocol can be found in 3GPP TS 24.301 (v15.4.0), which is incorporated herein by reference in its entirety. Table 2 is an example of a UE configuration parameter update container IE. This container is considered transparent because the AMF element 314 inserts the secure package into the container without modifying the secure package.

Table 2:

8 7 6 5 4 3 2 1 UE Configuration Parameter Update Container IEI octet 1 UE Configuration Parameter Update Container Content Length octet 2 octet 3 UE configuration parameter update header octet 4 Secure Packet [UE Configuration Parameter Update] octet 5-2048*

Table 3 illustrates an example of a UE configuration setting update header for a UE configuration setting update container IE.

Table 3:

In the header, the RRR bit may be used as a re-registration indicator. The UE ACK bit may be used as a UE acknowledgment indicator. The data type bit may be used to indicate whether the container is used in a NAS message sent from the network to the UE (eg, value = 0) or in a NAS message sent from the UE to the network (eg, value = 1).

When receiving a NAS registration confirmation message, the ME 702 may behave as if an SMS message is received with the protocol identifier set to "download SIM data", the data encoding scheme set to "message class 2", and the SMS payload in as a secure package. ME 702 routes or downloads the secure packet to USIM 662 (S7). The USIM 662 performs a security check to verify that the secure packet was sent by the UDM element 312 of the home network. If the security check is not successful, the USIM 662 discards the UE configuration parameter update and continues with the registration procedure. If the security check is successful, the USIM 662 unpacks the UE configuration parameter update from the secure package using the secure package library. After checking the integrity of the secure packet/replay protection, the USIM 662 updates one or more of the UE configuration parameters 664 based on the update of the UE configuration parameter.

If the network has requested an acknowledgment from UE 110 and the security check is successful, USIM 662 may send a acknowledgment to the UE to ME 702 (S8). ME 702 formats or generates another NAS message to send a UE acknowledgment to AMF element 314 . In the example shown in FIG. 13, the ME 702 formats the NAS registration progress message and inserts the UE confirmation into the NAS registration progress message container. The NAS registration progress message container is for acknowledgment by the UE. Table 4 illustrates an example message content for a NAS registration progress message.

Table 4:

IEI Information element Type/Reference Presence Format Length Extended protocol discriminator Extended protocol discriminator M V one Security header type Security header type M V 1/2 Reserved semi-octet Reserved semi-octet M V 1/2 Registration confirmation message identification Message type M V one … xx UE Acknowledgment Container UE Acknowledgment Container O TLV-E 20-2048

In this example, the NAS registration progress message contains a newly defined UE confirmation container IE. Table 5 is an example of a UE acknowledgment container IE.

Table 5:

8 7 6 5 4 3 2 1 UE Acknowledgment Container IEI octet 1 UE Acknowledgment Container Content Length octet 2 octet 3 UE Acknowledgment Header octet 4 UE confirmation octet 5-20

Table 6 illustrates an example UE acknowledgment header.

Table 6:

In another example, USIM 662 may apply security protection to the UE's assertion by accessing a secure packet library to encapsulate the UE's assertion in a secure packet. Therefore, the ME 702 may insert the secure packet into the UE's acknowledgment container IE.

The ME 702 then sends a NAS registration done message to the AMF element 314 with a container containing the UE confirmation (S9). The AMF element 314 sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with an acknowledgment to the UE (S10). UDM element 312 may then check that the UE acknowledgment has been provided by UE 110.

In an alternative embodiment, shown in FIG. 13, ME 702 may use another type of NAS message to send a UE acknowledgment to AMF element 314. In this alternative, the ME 702 formats the NAS UL transport message and inserts the UE acknowledgment into the NAS UL transport message container. The value of the payload container type may be for acknowledging the UE in the payload container IE of the NAS UL transport message. The ME 702 then sends the NAS UL transport message to the AMF element 314 with a container containing the UE acknowledgment (S9a). The AMF element 314 in turn sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with a UE confirmation (S10a).

If the network has indicated that UE 110 needs re-registration and the security check is successful, then UE 110 de-registers and re-initiates a new NAS registration procedure (S11) using the updated UE configuration parameters.

Example 2: Post-registration update procedure using secure package

Fig. 14 is a message diagram illustrating an update procedure after registration in an exemplary embodiment. In this embodiment, UE 110 is already registered with the network and is in connected mode (ie, RRC-CONNECTED). At some point after registration, UDM element 312 may receive an instruction or process local policies to determine that the UE configuration settings at UE 110 need to be updated. Thus, the UDM element 312 initiates the update procedure and collects the UE configuration parameter update. UDM element 312 then applies security protection to the UE configuration parameter update by referring to the secure package library to encapsulate the UE configuration parameter update in a secure package. UDM element 312 then sends an update notification (eg, Nudm_SDM_UpdateNotification) to AMF (S1) element 314 that contains the secure packet. UDM element 312 may also include a UE confirmation indicator and/or a re-registration indicator in the update notification.

The AMF element 314 is configured to transparently send a secure packet to UE 110 as part of the update procedure. Thus, AMF element 314 formats or generates a downlink (DL) NAS transport message and inserts a secure packet into a DL NAS transport message container. AMF element 314 may also insert a UE acknowledgment indicator and/or a re-registration indicator (if applicable) into the NAS DL transport message container. In this embodiment, the NAS DL transport message container is for updating the configuration parameter of the UE. The AMF element 314 may set the payload container type IE to the "UE Configuration Settings Container" and set the payload container IE to the secure packet. Then, AMF element 314 sends a NAS DL transport message to UE 110 (S2).

When receiving a NAS DL transport message, the ME 702 may behave as if an SMS message is received with the protocol identifier set to "download SIM data", the data encoding scheme set to "message class 2", and the SMS payload as protected package. ME 702 routes or downloads the secure packet to USIM 662 (S3). The USIM 662 performs a security check to verify that the secure packet was sent by the UDM element 312 of the home network. If the security check is not successful, the USIM 662 discards the UE configuration parameter update. If the security check is successful, the USIM 662 unpacks the UE configuration parameter update from the secure package using the secure package library. After checking the integrity of the secure packet/replay protection, the USIM 662 updates one or more of the UE configuration parameters 664 based on the update of the UE configuration parameter.

If the network has requested an acknowledgment from UE 110 and the security check is successful, USIM 662 may send a UE acknowledgment to ME 702 (S4). The ME 702 formats or generates the NAS UL transport message and inserts the UE acknowledgment into the NAS UL transport message container. The NAS UL transport message container is for acknowledgment by the UE. The ME 702 then sends the NAS UL transport message to the AMF element 314 with a container containing the UE acknowledgment (S5). The AMF element 314 sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with an acknowledgment to the UE (S6). UDM element 312 may then check that the UE acknowledgment has been provided by UE 110.

If the network has indicated that UE 110 needs re-registration and the security check is successful, then UE 110 de-registers and re-initiates a new NAS registration procedure using the updated UE configuration parameters (not shown).

Example 3: Update procedure during registration using a security key

Fig. 15 is a message diagram illustrating an update procedure during registration in an exemplary embodiment. In this embodiment, UE 110 initiates a NAS registration procedure by sending a NAS registration request to AMF element 314 (S1). In response to a NAS registration request (of type "initial"), AMF element 314 may initiate an authentication procedure (S2) to authenticate UE 110. When UE 110 authenticates to the network, AMF element 314 may initiate a NAS security procedure to establish a NAS security context (S3 ). When UE 110 is authenticated and a NAS security context is established, AMF element 314 sends a subscription data request (eg, Nudm_SDM_Get message) to HPLMN UDM element 312 to obtain access and mobility subscription data for UE 110, among other information (S4). When the user's subscription information indicates the initiation of a UE configuration parameter update (eg, a routing ID update), the UDM element 312 initiates an update procedure. UDM element 312 collects the UE configuration parameter update and applies integrity protection to the UE configuration parameter update using the NAS security context for UE 110. To do this, UDM element 312 sends a protection request (e.g., Nausf_ParameterProtectionRequest) to AUSF element 310 with update UE configuration parameter (S5) . The AUSF element 310 identifies the NAS counter (composed of the NAS sequence number) and calculates integrity protection information based on the NAS security context for the UE 110, such as the AUSF Message Authentication Code (MAC) to update the UE configuration parameter and the NAS counter. AUSF element 310 may also calculate an expected MAC from UE 110 (X-UE-MAC). AUSF element 310 then sends a protection response (eg, Nausf_ParameterProtectionResponse) with integrity protection information (ie, AUSF-MAC, NAS counter, and X-UE-MAC) to UDM element 312 (S6). UDM element 312 then sends a subscription data response (eg, Nudm_SDM_Get response) to AMF element 314 (S7), which contains the UE configuration parameter update and integrity protection information (i.e., AUSF-MAC and NAS counter). UDM element 312 may also include a UE confirmation indicator and/or a re-registration indicator in the subscription data response.

The AMF element 314 is configured to transparently send a UE configuration parameter update to the UE 110 as part of the update procedure. Thus, the AMF element 314 formats or generates the NAS Registration Confirm message and inserts the UE configuration parameter update into the NAS Registration Confirm message container along with integrity protection information (eg, AUSF-MAC and NAS counter). AMF element 314 may also insert a UE acknowledgment indicator and/or a re-registration indicator (if applicable) into the container of the NAS registration acknowledgment message. Then, AMF element 314 sends a NAS registration confirmation message to UE 110 (S8).

In this example, the NAS registration confirmation message contains a newly defined UE configuration parameter update container IE. Table 7 is an example of a UE configuration parameter update container IE.

Table 7:

8 7 6 5 4 3 2 1 UE Configuration Parameter Update Container IEI octet 1 UE Configuration Parameter Update Container Content Length octet 2 octet 3 UE configuration parameter update header octet 4 AUSF-MAC octet 5-20 NAS counter octet 21-22 UE configuration parameter update octet 23*-2048*

This container is considered transparent because the AMF element 314 inserts the UE configuration parameter update into the container without changing the UE configuration parameter update. As described in Example 1, the UE ACK bit of the UE Configuration Parameter Update header may be used to indicate that the network has requested an acknowledgment from the UE, and the RRR bit may be used to indicate that the network has requested re-registration.

In response to receiving the NAS registration confirmation message, the ME 702 of the UE 110 performs a security check to verify that the UE configuration parameter update has been sent by the home network UDM element 312 . For example, ME 702 calculates the UE-MAC to update the UE configuration parameter and the NAS counter and compares the UE-MAC with the AUSF-MAC. If the indicated MACs match, then it is checked that the UE configuration parameter update will be from the home network, and the security check is successful. If the security check is not successful, the ME 702 discards the UE configuration parameter update and continues with the registration procedure. If the security check is successful, then the ME 702 and/or USIM 662 update one or more of the UE configuration parameters 664 based on the UE configuration parameter update.

If the network has requested confirmation from the UE 110 and the security check is successful, then the ME 702 formats the NAS registration done message and inserts the UE-MAC into the NAS registration done message container. The NAS registration progress message container is for acknowledgment by the UE. In this example, the NAS registration progress message contains a newly defined UE confirmation container IE. Table 8 is an example of a UE acknowledgment container IE.

Table 8:

8 7 6 5 4 3 2 1 UE Configuration Parameter Update Container IEI octet 1 UE Configuration Parameter Update Container Content Length octet 2 octet 3 UE configuration parameter update header octet 4 UE MAC octet 5-20

The ME 702 then sends a NAS registration done message to the AMF element 314 with the container containing the UE-MAC (S9). The AMF element 314 sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with the UE-MAC (S10). UDM element 312 may then compare the UE-MAC calculated by UE 110 with the X-UE-MAC calculated by AUSF element 310 to verify that the UE acknowledgment has been provided by UE 110.

If the network has indicated that UE 110 needs re-registration and the security check is successful, then UE 110 de-registers and re-initiates a new NAS registration procedure using the updated UE configuration parameters (not shown).

Example 4: Update procedure after registration using a security key

Fig. 16 is a message diagram illustrating the update procedure after registration in the exemplary embodiment. In this embodiment, UE 110 is already registered with the network and is in connected mode. At some point after registration, UDM element 312 may receive an instruction or process local policies to determine that the UE configuration settings at UE 110 need to be updated. Thus, the UDM element 312 initiates the update procedure and collects the UE configuration parameter update. UDM element 312 also applies integrity protection to the UE configuration parameter update using the NAS security context for UE 110. To do this, UDM element 312 sends a protection request (eg, Nausf_ParameterProtectionRequest) to AUSF element 310 with the UE configuration parameter update (S1). The AUSF element 310 identifies the NAS counter and calculates integrity protection information based on the NAS security context for the UE 110, such as AUSF-MAC to update the UE configuration parameter and the NAS counter. AUSF element 310 may also calculate an expected MAC from UE 110 (X-UE-MAC). AUSF element 310 then sends a protection response (eg, Nausf_ParameterProtectionResponse) with integrity protection information (ie, AUSF-MAC, NAS counter, and X-UE-MAC) to UDM element 312 (S2). UDM element 312 then sends an update notification (eg, Nudm_SDM_UpdateNotification) to AMF (S3) element 314, which contains the UE configuration parameter update and integrity protection information (ie, AUSF-MAC and NAS counter). UDM element 312 may also include a UE confirmation indicator and/or a re-registration indicator in the update notification.

The AMF element 314 is configured to transparently send a UE configuration parameter update to the UE 110 as part of the update procedure. Thus, AMF element 314 formats or generates the NAS DL transport message and inserts the UE configuration parameter update into the NAS DL transport message container along with integrity information (eg, AUSF-MAC and NAS counter). AMF element 314 may also insert a UE acknowledgment indicator and/or a re-registration indicator (if applicable) into the NAS DL transport message container. In this embodiment, the NAS DL transport message container is for updating the configuration parameter of the UE. Then, AMF element 314 sends a NAS DL transport message to UE 110 (S4).

In response to receiving the NAS DL transport message, the UE 110 ME 702 performs a security check to verify that the UE configuration parameter update has been sent by the home network UDM element 312 . If the security check is not successful, the ME 702 discards the UE configuration parameter update. If the security check is successful, then the ME 702 and/or USIM 662 update one or more of the UE configuration parameters 664 based on the UE configuration parameter update.

If the network has requested confirmation from UE 110 and the security check is successful, then ME 702 formats the NAS UL transport message and inserts the UE-MAC into the NAS UL transport message container. The NAS UL transport message container is for acknowledgment by the UE. The ME 702 then sends the NAS UL transport message to the AMF element 314 with the container containing the UE-MAC (S5). The AMF element 314 sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with the UE-MAC (S6). UDM element 312 may then compare the UE-MAC calculated by UE 110 with the X-UE-MAC calculated by AUSF element 310 to verify that the UE acknowledgment has been provided by UE 110.

If the network has indicated that UE 110 needs re-registration and the security check is successful, then UE 110 de-registers and re-initiates a new NAS registration procedure using the updated UE configuration parameters (not shown).

Example 5: Update procedure during registration using secure package and security key

Fig. 17 is a message diagram illustrating an update procedure during registration in an exemplary embodiment. In this embodiment, UE 110 initiates a NAS registration procedure by sending a NAS registration request to AMF element 314 (S1). In response to a NAS registration request (of type "initial"), AMF element 314 may initiate an authentication procedure (S2) to authenticate UE 110. After UE 110 is authenticated, AMF element 314 may initiate a NAS security procedure to establish a NAS security context (S3). When UE 110 is authenticated and a NAS security context is established, AMF element 314 sends a subscription data request (eg, Nudm_SDM_Get message) to HPLMN UDM element 312 to obtain access and mobility subscription data for UE 110, among other information (S4). When the user's subscription information indicates the initiation of a UE configuration parameter update (eg, a routing ID update), the UDM element 312 initiates an update procedure. UDM element 312 collects a UE configuration parameter update that contains one or more updated UE configuration parameters. UDM element 312 then applies security protection to the UE configuration parameter update by referring to the secure package library to encapsulate the UE configuration parameter update in a secure package.

UDM element 312 also applies integrity protection to the secure packet using the NAS security context for UE 110. To do this, UDM element 312 sends a protection request (eg, Nausf_ParameterProtectionRequest) to AUSF element 310 with secure packet (S5). The AUSF element 310 identifies the NAS counter and calculates integrity protection information based on the NAS security context for UE 110, such as the AUSF-MAC for the secure packet and the NAS counter. AUSF element 310 may also calculate an expected MAC from UE 110 (X-UE-MAC). AUSF element 310 then sends a protection response (eg, Nausf_ParameterProtectionResponse) with integrity protection information (ie, AUSF-MAC, NAS counter, and X-UE-MAC) to UDM element 312 (S6). UDM element 312 then sends a subscription data response (eg, Nudm_SDM_Get response) to AMF element 314 (S7) that contains the secure packet and integrity protection information (ie, AUSF-MAC and NAS counter). UDM element 312 may also include a UE confirmation indicator and/or a re-registration request in the subscription data response.

The AMF element 314 is configured to transparently send a secure packet to UE 110 as part of the update procedure. Thus, the AMF element 314 formats or generates the NAS Registration Confirmation message and inserts the secure packet into the container of the NAS Registration Confirmation message. AMF element 314 may also insert a UE confirmation indicator and/or a re-registration request (if applicable) in a NAS registration confirmation message container along with the AUSF-MAC and the NAS counter. In this example, the NAS registration confirmation message contains a newly defined UE configuration parameter update container IE. Table 9 is an example of a UE configuration parameter update container IE.

Table 9:

8 7 6 5 4 3 2 1 UE Configuration Parameter Update Container IEI octet 1 UE Configuration Parameter Update Container Content Length octet 2 octet 3 UE configuration parameter update header octet 4 AUSF-MAC octet 5-20 NAS counter octet 21-22 Secure Packet [UE Configuration Parameter Update] octet 23*-2048*

This container is considered transparent because the AMF element 314 inserts the secure package into the container without modifying the secure package. Then, AMF element 314 sends a NAS registration confirmation message to UE 110 (S8). In response to receiving the NAS registration confirmation message, the UE 110 ME 702 performs a security check to verify that the secure packet was sent by the home network UDM element 312 . If the security check fails, the ME 702 discards the secure packet and continues with the registration procedure. If the security check is successful, then the ME 702 routes or downloads the secure packet to the USIM 662 (S9). The USIM 662 also performs a security check to verify that the secure packet was sent by the UDM element 312 of the home network. If the security check is not successful, the USIM 662 discards the UE configuration parameter update. If the security check is successful, the USIM 662 unpacks the UE configuration parameter update from the secure package using the secure package library. The USIM 662 then updates one or more of the UE configuration parameters 664 based on the UE configuration parameter update.

If the network has requested confirmation from the UE 110 and the security check is successful, then the ME 702 formats the NAS registration done message and inserts the UE-MAC into the NAS registration done message container. The ME 702 then sends a NAS registration done message to the AMF element 314 (S11). The AMF element 314 sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with the UE-MAC (S10). UDM element 312 may then compare the UE-MAC calculated by UE 110 with the X-UE-MAC calculated by AUSF element 310 to verify that the UE acknowledgment has been provided by UE 110.

If the network has indicated that UE 110 needs re-registration and the security check is successful, then UE 110 de-registers and re-initiates a new NAS registration procedure using the updated UE configuration parameters (not shown).

Example 6: Update procedure after registration using a secure package and a security key

Fig. 18 is a message diagram illustrating an update procedure after registration in an exemplary embodiment. In this embodiment, UE 110 is already registered with the network and is in connected mode. At some point after registration, UDM element 312 may receive an instruction or process local policies to determine that the UE configuration settings at UE 110 need to be updated. Thus, the UDM element 312 initiates the update procedure and collects the UE configuration parameter update. UDM element 312 then applies security protection to the UE configuration parameter update by referring to the secure package library to encapsulate the UE configuration parameter update in a secure package.

UDM element 312 also applies integrity protection to the secure packet using the NAS security context for UE 110. To do this, UDM element 312 sends a protection request (eg, Nausf_ParameterProtectionRequest) to AUSF element 310 with secure packet (S1). The AUSF element 310 identifies the NAS counter and calculates integrity protection information based on the NAS security context for UE 110, such as the AUSF-MAC for the secure packet and the NAS counter. AUSF element 310 may also calculate an expected MAC from UE 110 (X-UE-MAC). AUSF element 310 then sends a protection response (eg, Nausf_ParameterProtectionResponse) with integrity protection information (ie, AUSF-MAC, NAS counter, and X-UE-MAC) to UDM element 312 (S2). UDM element 312 then sends an update notification (eg, Nudm_SDM_UpdateNotification) to AMF (S3) element 314 that contains the secure packet and integrity protection information (ie, AUSF-MAC and NAS counter). UDM element 312 may also include a UE confirmation indicator and/or a re-registration request in the update notification.

The AMF element 314 is configured to transparently send a secure packet to UE 110 as part of the update procedure. Thus, the AMF element 314 formats or generates the NAS DL transport message and inserts the secure packet into the NAS DL transport message container. AMF element 314 may also insert a UE acknowledgment indicator and/or a re-registration indicator (if applicable) into the DL NAS transport message container along with the AUSF-MAC and the NAS counter. Then, AMF element 314 sends a NAS DL transport message to UE 110 (S4).

In response to receiving the NAS DL transport message, the UE 110 ME 702 performs a security check to verify that the secure packet was sent by the home network UDM element 312 . If the security check fails, the ME 702 discards the secure packet. If the security check is successful, then the ME 702 routes or downloads the secure packet to the USIM 662 (S5). The USIM 662 also performs a security check to verify that the secure packet was sent by the UDM element 312 of the home network. If the security check is not successful, the USIM 662 discards the UE configuration parameter update. If the security check is successful, the USIM 662 unpacks the UE configuration parameter update from the secure package using the secure package library. The USIM 662 then updates one or more of the UE configuration parameters 664 based on the UE configuration parameter update. USIM 662 also sends a UE acknowledgment to ME 702 (S6).

If the network has requested confirmation from UE 110 and the security check is successful, then ME 702 formats the NAS UL transport message and inserts the UE-MAC into the NAS UL transport message container. The ME 702 then sends the NAS UL transport message to the AMF element 314 (S7). The AMF element 314 sends an information message (eg, Nudm_SDM_Info message) to the UDM element 312 with the UE-MAC (S8). UDM element 312 may then compare the UE-MAC calculated by UE 110 with the X-UE-MAC calculated by AUSF element 310 to verify that the UE acknowledgment has been provided by UE 110.

If the network has indicated that UE 110 needs re-registration and the security check is successful, then UE 110 de-registers and re-initiates a new NAS registration procedure using the updated UE configuration parameters (not shown).

Any of the various elements or modules shown in the figures or described herein may be implemented as hardware, software, firmware, or some combination thereof. For example, the element may be implemented as dedicated hardware. Specialized hardware elements may be called "processors", "controllers", or some similar terminology. When provided by a processor, the functions may be provided by a single dedicated processor, a single shared processor, or a collection of individual processors, some of which may be shared. Moreover, the explicit use of the term "processor" or "controller" shall not be construed as referring solely to hardware capable of executing the software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC) or other circuit, field programmable gate array (FPGA), read-only memory (ROM) for software storage, random access memory (RAM), non-volatile storage device, logic, or some other physical hardware component or module.

In addition, an element may be implemented as instructions executable by a processor or computer to perform the functions of the element. Some examples of instructions are software, program code, and firmware. Instructions are operable when they are executed by the processor to instruct the processor to perform the functions of an element. The instructions may be stored on data storage devices that can be read by the processor. Some examples of storage devices are digital or solid state storage devices, magnetic storage media such as magnetic disks and magnetic tapes, hard drives or optically readable digital storage media.

As used in this application, the term "scheme" may refer to one or more or all of the following:

(a) implementations of circuits only in hardware (eg, implementations only in analog and/or digital circuits);

(b) combinations of hardware circuits and software, such as (if applicable):

(i) a combination of analog and/or digital hardware circuit(s) with software/firmware; and

(ii) any parts of a hardware processor(s) with software (including digital signal processor(s), software, and storage device(s) that work together to cause a device, such as a mobile phone or a server, to perform various functions ; and

(c) hardware(s) circuit(s) and/or processor(s), such as a microprocessor(s) or part of a microprocessor(s), that require software (such as firmware) to operate, but said software may be absent when it is not needed for work.

This definition of "scheme" applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuit" also encompasses the implementation of simply a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) associated software and/or firmware. The term "circuitry" also encompasses, for example, and when applicable to a particular claim element, a baseband or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device.

While specific embodiments have been described herein, the scope of the disclosure is not limited to those specific embodiments. The scope of the present disclosure is defined by the following claims and any equivalents thereof.

Claims (139)

1. User Equipment (UE), comprising: universal subscriber identification module (USIM); at least one processor; and at least one storage device containing computer program code; wherein the USIM stores UE configuration parameters for said UE, wherein said at least one storage device and said computer program code are configured, by means of said at least one processor, to instruct said UE at least: receive from an access and mobility management function (AMF) element a first non-access layer (NAS) message containing a container that contains a UE configuration parameter update for said UE, said UE configuration parameter update containing a UE parameter encapsulated in a secure packet; perform a first security check to verify said UE configuration parameter update; and forward the specified secure packet to the specified USIM if the specified first security check is successful, wherein the specified USIM is configured to perform a second security check to verify the specified secure packet, and if the specified second security check is successful, update one or more of the specified configuration parameters UE in the specified USIM based on the specified UE parameter encapsulated in the specified secure packet. 2. The UE of claim 1, wherein said UE parameter encapsulated in said secure packet is a routing indicator parameter. 3. The UE of claim 1, wherein said first security check verifies the integrity of said UE configuration parameter update using said UE's NAS security context. 4. The UE of claim 1, wherein said USIM is stored on a universal integrated circuit card (UICC) within said UE. 5. The UE of claim 1, wherein said first NAS message contains a NAS registration confirmation message sent to said UE during the NAS registration procedure. 6. UE according to claim 5, characterized in that: when said NAS registration confirmation message contains a UE confirmation indicator, said processor is further configured to cause said UE to send a second NAS message to said AMF element with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received, wherein said second NAS message contains an NAS registration in progress message or an uplink NAS transport message. 7. The UE of claim 1, wherein said first NAS message contains a downlink NAS transport message of the NAS transport procedure. 8. The UE of claim 7, wherein when said downlink NAS transport message contains a UE acknowledgment indicator, said processor is further configured to: causing said UE to send an uplink NAS transport message to said AMF element with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received. 9. The UE of claim 1, wherein when said first NAS message contains a re-registration indicator, said processor is further configured to: causing said UE to initiate a NAS registration procedure to re-register using said updated UE configuration parameters. 10. A method for securely updating configuration parameters provided in a user equipment (UE), including: receiving at said UE, from an Access Mobility Management Function (AMF) element, a first non-access stratum (NAS) message containing a container that contains a UE configuration parameter update for a specified UE, said UE configuration parameter update containing a UE parameter encapsulated in a secure packet ; performing a first security check to verify said UE configuration parameter update; and forwarding said secure packet to a universal subscriber identity module (USIM) capable of communicating with said UE if said first security check is successful, wherein said USIM is configured to perform a second security check to verify said secure packet, and if said second security check is successful, update one or more of the specified UE configuration parameters in the specified USIM based on the specified UE parameter encapsulated in the specified secure packet. 11. The method of claim 10, wherein said UE parameter encapsulated in said secure packet is a routing indicator parameter. 12. The method of claim 10, wherein said first security check verifies the integrity of said UE configuration parameter update using said UE's NAS security context. 13. The method of claim 10, wherein said USIM is stored on a universal integrated circuit card (UICC) within said UE. 14. The method of claim 10, wherein said first NAS message comprises a NAS registration confirmation message sent to said UE during the NAS registration procedure. 15. The method of claim 14, wherein when said NAS registration confirmation message contains a UE confirmation indicator, said method further includes: causing said UE to send a second NAS message to said AMF element with a container containing a UE acknowledgment from said UE that said UE configuration parameter update has been received, said second NAS message containing a NAS Registration Progress Message or an uplink NAS Transport Message . 16. The method of claim 10, wherein said first NAS message comprises a downlink NAS transport message of the NAS transport procedure. 17. The method of claim 16, wherein when said downlink NAS transport message contains a UE acknowledgment indicator, said method further includes: causing said UE to send an uplink NAS transport message to said AMF element with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received. 18. The method of claim 10, wherein when said first NAS message contains a re-registration indicator, said method further includes: causing said UE to initiate a NAS registration procedure to re-register using said updated UE configuration parameters. 19. Access and mobility management function (AMF) element, containing: at least one processor; and at least one storage device containing computer program code, wherein said at least one storage device and said computer program code are configured, using said at least one processor, to prescribe to said AMF element at least: generating a first Non-Access Layer (NAS) message containing a container that contains a user equipment (UE) configuration parameter update for said UE, said UE configuration parameter update containing a UE parameter encapsulated in a secure packet; and transmit said first NAS message to the UE, wherein said first NAS message is configured to (i) cause said UE to perform a first security check to verify said UE configuration parameter update, (ii) cause said UE to forward said secure packet to the universal subscriber identity module (USIM) configured to communicate with said UE if said first security check is successful, (iii) causing said USIM to perform a second security check to verify said secure packet, and (iv) updating one or more of said UE configuration parameters in the specified USIM based on the specified UE parameter encapsulated in the specified secure packet, if the specified second security check is successful. 20. The AMF element of claim 19, wherein said UE parameter encapsulated in said secure packet is a routing indicator parameter. 21. The AMF element of claim 19, wherein said first security check is configured to check the integrity of said UE configuration parameter update using said UE's NAS security context. 22. The AMF element of claim 19, wherein said first NAS message contains the NAS registration confirmation message sent to the designated UE during the NAS registration procedure. 23. The AMF element of claim 22, wherein when said NAS registration confirmation message contains a UE confirmation indicator, said NAS registration confirmation message is further configured to cause said UE to send a second NAS message to said AMF element with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received, wherein said second NAS message contains an NAS registration in progress message or an uplink NAS transport message. 24. The AMF element of claim 19, wherein said first NAS message contains an NAS transport procedure downlink transport message of the NAS transport procedure. 25. The AMF element of claim 24, wherein when said downlink NAS transport message contains a UE acknowledgment indicator, said first NAS message is further configured to cause said UE to send an uplink NAS transport message to said containerized AMF element. containing a UE confirmation from said UE that said UE configuration parameter update has been received. 26. The AMF element of claim 19, wherein when said first NAS message contains a re-registration indicator, said first NAS message is further configured to cause said UE to initiate a NAS registration procedure to re-register using said updated UE configuration parameters. 27. The AMF element according to claim 19, characterized in that said at least one storage device and said computer program code are configured, using said at least one processor, to prescribe to said AMF element at least: receive a control plane message from a unified data control (UDM) containing a specified update of the UE configuration parameter for the specified UE; and insert the specified UE configuration parameter update into the specified container of the specified first NAS message. 28. The AMF element according to claim 27, characterized in that said at least one storage device and said computer program code are configured, using said at least one processor, to prescribe to said AMF element at least: receive said second NAS message from said UE during said NAS registration procedure with a container containing a UE confirmation that said UE configuration parameter update has been received; and send another control plane message to the specified UDM element with the specified acknowledgment by the UE, wherein the specified second NAS message received from the specified UE contains an NAS registration progress message or an uplink NAS transport message. 29. A method for securely updating configuration parameters provided in a user equipment (UE), including: generating a first Non-Access Layer (NAS) message containing a container that contains a UE configuration parameter update for said UE, said UE configuration parameter update containing a UE parameter encapsulated in a secure packet; and transmitting said first NAS message to the UE, said first NAS message being configured to (i) cause said UE to perform a first security check to verify said UE configuration parameter update, (ii) cause said UE to forward said secure packet to the universal subscriber identity module (USIM) configured to communicate with said UE if said first security check is successful, (iii) causing said USIM to perform a second security check to verify said secure packet, and (iv) updating one or more of said UE configuration parameters in the specified USIM based on the specified UE parameter encapsulated in the specified secure packet, if the specified second security check is successful. 30. The method of claim 29, wherein said UE parameter encapsulated in said secure packet is a routing indicator parameter. 31. The method of claim 29, wherein said first security check verifies the integrity of said UE configuration parameter update using said UE's NAS security context. 32. The method of claim 29, wherein said first NAS message comprises a NAS registration confirmation message sent to said UE during the NAS registration procedure. 33. The method of claim 32, wherein when said NAS registration confirmation message contains a UE confirmation indicator, said method further includes: causing said UE to send a second NAS message to said AMF element with a container containing a UE acknowledgment from said UE that said UE configuration parameter update has been received, said second NAS message containing a NAS Registration Progress Message or an uplink NAS Transport Message . 34. The method of claim 29, wherein said first NAS message comprises a downlink NAS transport message of the NAS transport procedure. 35. The method of claim 34, wherein when said downlink NAS transport message comprises a UE acknowledgment indicator, said method further includes: causing said UE to send an uplink NAS transport message to said AMF element with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received. 36. The method of claim 29, wherein when said first NAS message contains a re-registration indicator, said method further includes: causing said UE to initiate a NAS registration procedure to re-register using said updated UE configuration parameters. 37. The method of claim 29, further comprising: receiving a control plane message from a unified data control (UDM) containing said update of a UE configuration parameter for said UE; and inserting said UE configuration parameter update into said container of said first NAS message. 38. The method of claim 37, further comprising: receiving said second NAS message from said UE during said NAS registration procedure with a container containing a UE confirmation that said UE configuration parameter update has been received; and sending another control plane message to said UDM with said UE acknowledgment, said second NAS message received from said UE containing an NAS Registration Progress Message or an uplink NAS Transport Message. 39. Element of the access and mobility management function (AMF) of the mobile network, containing: at least one processor; and at least one storage device containing computer program code executable by said processor, said processor being configured to assign to said AMF element: receive a control plane message from a unified data control (UDM) containing a user equipment (UE) configuration parameter update for said UE, said UE configuration parameter update being securely protected by a security mechanism; insert said UE configuration parameter update, which is securely protected, into a Non-Access Layer (NAS) first message container, said container for updating the UE configuration parameter; and send said first NAS message to said UE with a container containing said UE configuration parameter update that is securely protected, said UE configuration parameter update containing the UE parameter encapsulated in a secure packet, wherein said first NAS message is configured to instruct said UE: perform a first security check to verify said UE configuration parameter update; forward the specified secure packet to the universal subscriber identity module (USIM) of the specified UE if the specified first security check is successful, and upon receiving said secure packet at the USIM of said UE, cause said USIM to perform a second security check to verify said secure packet, and if said second security check is successful, cause said USIM to update one or more of said UE configuration parameters in said USIM based on said parameter of the UE encapsulated in the specified secure packet. 40. The AMF element of claim 39, wherein said UE configuration parameter update is encapsulated in a secure packet in accordance with a security mechanism. 41. The AMF element of claim 39, wherein said UE configuration parameter update is integrally secured using said UE's NAS security context in accordance with the security mechanism. 42. The AMF element of claim 39, wherein said UE configuration parameter update is encapsulated in a secure packet, and said secure packet is integrally secured using said UE's NAS security context according to the security mechanism. 43. The AMF element of claim 39, wherein said first NAS message contains the NAS registration confirmation message sent to the designated UE during the NAS registration procedure. 44. The AMF element according to claim 43, characterized in that said processor is further configured to prescribe to said AMF element: receive a second NAS message from said UE during a NAS registration procedure with a container containing a UE confirmation that said UE configuration parameter update has been received; and send another control plane message to said UDM with an acknowledgment by the UE, wherein said second NAS message received from said UE contains an NAS registration progress message or an uplink NAS transport message. 45. The AMF element of claim 39, wherein said first NAS message contains a downlink NAS transport message of the NAS transport procedure performed after the NAS registration procedure. 46. The AMF element according to claim 45, characterized in that said processor is further configured to prescribe to said AMF element: receive a second NAS message from said UE with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received; and send another control plane message to said UDM with UE acknowledgment, said second NAS message containing an uplink NAS transport message. 47. A method for performing an update procedure for updating user equipment (UE) configuration parameters provided in a UE, including: receiving a control plane message in an access and mobility control function (AMF) element from a unified data control (UDM) element that contains a UE configuration parameter update for said UE, said UE configuration parameter update being securely protected by a security mechanism; inserting, in said AMF element, said UE configuration parameter update that is securely protected into a Non-Access Layer (NAS) first message container, said container for said UE configuration parameter update; and sending said first NAS message from said AMF element to said UE with a container containing said UE configuration parameter update that is securely protected, said UE configuration parameter update containing the UE parameter encapsulated in a secure packet, wherein said first NAS message is configured to instruct said UE: perform a first security check to verify said UE configuration parameter update; forward the specified secure packet to the universal subscriber identity module (USIM) of the specified UE if the specified first security check is successful, and upon receiving said secure packet at the USIM of said UE, cause said USIM to perform a second security check to verify said secure packet, and if said second security check is successful, cause said USIM to update one or more of said UE configuration parameters in said USIM based on said parameter of the UE encapsulated in the specified secure packet. 48. The method of claim 47, wherein said UE configuration parameter update is encapsulated in a secure packet in accordance with a security mechanism. 49. The method of claim 47, wherein said UE configuration parameter update is integrally secured using said UE's NAS security context in accordance with the security mechanism. 50. The method of claim 47, wherein said UE configuration parameter update is encapsulated in a secure packet, and said secure packet is integrally secured using said UE's NAS security context in accordance with the security mechanism. 51. The method of claim 47, wherein said first NAS message comprises an NAS registration confirmation message sent from said AMF element to said UE during a NAS registration procedure. 52. The method of claim 51, further comprising: receiving a second NAS message in said AMF element from said UE during a NAS registration procedure with a container containing a confirmation to the UE that said UE configuration parameter update has been received; and sending another control plane message from said AMF element to said UDM with UE acknowledgment, said second NAS message containing an NAS Registration Progress Message or an uplink NAS Transport Message. 53. The method of claim 47, wherein said first NAS message comprises a downlink NAS transport message of the NAS transport procedure performed after the NAS registration procedure. 54. The method of claim 53, further comprising: receiving a second NAS message in said AMF element from said UE with a container containing a UE confirmation from said UE that said UE configuration parameter update has been received; and sending another control plane message from said AMF element to said UDM with UE acknowledgment, said second NAS message comprising an uplink NAS transport message. 55. The method of claim 47, further comprising: receiving said first NAS message at said UE from said AMF element containing said container that contains a UE configuration parameter update for said UE that is securely protected; performing a security check on said UE to check said UE configuration parameter update; and updating at said UE one or more UE configuration parameters based on said UE configuration parameter update when said UE configuration parameter update is verified. 56. The method of claim 55, further comprising: initiating a NAS registration procedure at said UE to re-register using said updated UE configuration parameters when said first NAS message contains a re-registration indicator. 57. User equipment (UE), containing: a universal integrated circuit card (UICC) that houses a universal subscriber identity module (USIM); at least one processor; and at least one storage device containing computer program code executable by the processor, wherein at least one of said UICC and said storage device stores UE configuration parameters for said UE, said processor being configured to instruct said UE: receive a first Non-Access Layer (NAS) message from an Access Mobility Function (AMF) element containing a container that contains a UE configuration parameter update for a specified UE that is securely protected according to a security mechanism, said container being for a specified parameter update UE configurations; wherein said processor is configured to instruct said UE: perform a first security check to verify said UE configuration parameter update; and forward the specified container to the specified UICC if the specified first security check is successful, wherein said UICC is configured to prescribe to said USIM: after receiving said secure packet at said UICC of said UE, perform a second security check to check said container, and if said second security check is successful, update one or more UE configuration parameters based on said UE configuration parameter update. 58. The UE of claim 57, wherein said UE configuration parameter update is encapsulated in a secure packet in said container of said first NAS message. 59. The UE of claim 57, wherein said UE configuration parameter update is integrally secured using said UE's NAS security context. 60. The UE of claim 57, wherein said UE configuration parameter update is encapsulated in a secure packet in said container of said first NAS message, and said secure packet is integrally secured using said UE's NAS security context. 61. The UE of claim 57, wherein said first NAS message contains a NAS registration confirmation message sent to said UE during the NAS registration procedure. 62. The UE of claim 61, wherein when said NAS registration confirmation message contains a UE confirmation indicator, said processor is further configured to cause said UE to send a second NAS message to said AMF element with a container containing a UE confirmation from said UE. that said UE configuration parameter update has been received; wherein said second NAS message contains an NAS registration in progress message or an uplink NAS transport message. 63. The UE of claim 57, wherein said first NAS message contains a downlink NAS transport message of the NAS transport procedure performed after the NAS registration procedure. 64. UE according to claim 63, characterized in that: when said downlink NAS transport message contains a UE confirmation indicator, said processor is further configured to cause said UE to send an uplink NAS transport message to said AMF element with a container containing a UE confirmation from said UE that said UE configuration parameter update was taken. 65. The UE of claim 57, wherein when said first NAS message contains a re-registration indicator, said processor is further configured to cause said UE to initiate a NAS registration procedure to re-register using said updated UE configuration parameters.

Images