CN112073176A

CN112073176A - Key updating method and device

Info

Publication number: CN112073176A
Application number: CN201910503450.5A
Authority: CN
Inventors: 毕晓宇; 侯云静
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-06-11
Filing date: 2019-06-11
Publication date: 2020-12-11
Anticipated expiration: 2039-06-11
Also published as: WO2020248749A1; CN112073176B

Abstract

The application discloses a key updating method and a key updating device, which are used for providing a solution for updating a key for decrypting positioning auxiliary data when an LMF entity serving a terminal is changed. The key updating method provided by the embodiment of the application comprises the following steps: determining a corresponding updated key when a Location Management Function (LMF) entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data; and sending the key to the terminal.

Description

Key updating method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for updating a key.

Background

A network architecture supporting location services is shown in fig. 1, and the main network functions in the diagram are described as follows:

GMLC: the functional entity receives a positioning request of an LCS (LoCation Services) client, triggers a positioning process and returns the position of User Equipment (UE) to the LCS client.

UDM: the functional entity storing the information of the UE, for example, subscription information, has established information of a Protocol Data Unit (PDU) session.

An AMF entity: and the mobility management functional entity accesses authentication and tracks the position of the UE.

LMF entity: and the position management functional entity acquires the position of the UE.

The issuing of the positioning auxiliary data and the encryption key mainly relates to entities such as an LMF entity, a UDM entity, an AMF entity and the like. Wherein the LMF entity is responsible for formulating the encryption key and the positioning assistance data. The UDM entity stores an assistance data type to which a User Equipment (UE) subscribes. The AMF entity receives auxiliary data and a secret key issued by the LMF entity, wherein the auxiliary data is broadcasted through a Radio Access Network (RAN), and the AMF entity sends the secret key to the UE through a registration process. When the UE receives the key, the key may be used to decrypt the received broadcasted assistance data.

The specific process of broadcasting the network assistance data is shown in fig. 2 and described as follows:

step 201, the LMF entity transmits a message (Namf _ Communication _ N1N2MessageTransfer) through the AMF Communication N1N2, and sends Network Assistance Data (Network Assistance Data) to the AMF entity.

Step 202, the AMF entity sends the network assistance data to the 5G radio access network (NG-RAN) through N2 Transport.

Step 203, the NG-RAN sends the network assistance data to the UE via a Broadcast Message (Broadcast Message).

Currently, the LMF entity change procedure supports a service LMF entity to change in a 5GC-MT-LR (Mobile terminal Location Request) procedure. The mobility of the target UE may result in a change of the serving AMF entity that the original serving LMF entity does not fit. For example, the serving LMF entity may be remote from the new serving AMF entity, resulting in higher resource utilization of the AMF entity to LMF entity signaling, or the LMF entity may not configure information (e.g., cell database) for the UE's current access network. In this case, the serving LMF entity may need to change.

Disclosure of Invention

The embodiment of the application provides a key updating method and a key updating device, which are used for providing a solution for updating a key for decrypting positioning auxiliary data when an LMF entity serving a terminal is changed.

On a network side, for example, on an LMF entity side, a key update method provided in an embodiment of the present application includes:

determining a corresponding updated key when a Location Management Function (LMF) entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data;

and sending the key to the terminal.

By the method, a corresponding updated key is determined when an LMF entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data; sending the key to the terminal provides a solution for how to update the key for decrypting the positioning assistance data when the LMF entity serving the terminal changes, so that the updated key can be sent to the terminal.

Optionally, the key is sent to the terminal through a non-access stratum NAS message or a long term evolution positioning protocol LPP message.

Optionally, the key is sent to a mobility management function, AMF, entity through an updated target LMF entity, and the key is sent to the terminal through the AMF entity.

Optionally, when receiving a new key request sent by an AMF entity, sending the key to the AMF entity, and sending the key to the terminal through the AMF entity.

Optionally, the key is sent to the terminal when a location request of the terminal is received.

Optionally, when receiving an instant location request of a new service, sending the key to the terminal through a downlink location message.

On a network side, for example, on an AMF entity side, an embodiment of the present application provides a key updating method, including:

receiving a corresponding updated key when a Location Management Function (LMF) entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data;

and sending the key to the terminal.

By the method, a corresponding updated key is received when a Location Management Function (LMF) entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data; the key is sent to the terminal, thus providing a solution for how to update the key for decrypting the positioning assistance data when the LMF entity serving the terminal changes, so that the updated key can be sent to the terminal.

Optionally, after sending a new key request to the updated target LMF entity, receiving the key sent by the target LMF entity.

Optionally, when the key is received through a non-access stratum NAS message, the method further includes managing and saving the key.

On a terminal side, a key updating method provided in an embodiment of the present application includes:

the key is saved.

By the method, a corresponding updated key is received when a Location Management Function (LMF) entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data; the key is stored so that the terminal can obtain the updated key of the LMF entity, i.e. the key for decrypting the positioning assistance data generated by the latest LMF entity currently serving the terminal.

Optionally, the key is received through a non-access stratum NAS message or a long term evolution positioning protocol LPP message.

Optionally, after sending a service request message to the network side, the key is received, and the service request message includes a key request and key type information.

Optionally, the service request message is a non-access stratum NAS message or an event report message.

On the network side, for example, on the LMF entity side, an embodiment of the present application provides a key updating apparatus, including:

a memory for storing program instructions;

a processor for calling the program instructions stored in the memory and executing according to the obtained program:

and sending the key to the terminal.

On the network side, for example, on the AMF entity side, an embodiment of the present application provides a key updating apparatus, including:

a memory for storing program instructions;

and sending the key to the terminal.

Optionally, when the key is received through a non-access stratum NAS message, the processor is further configured to call the program instruction stored in the memory, and execute, according to the obtained program: and managing and storing the key.

On a terminal side, a key updating apparatus provided in an embodiment of the present application includes:

a memory for storing program instructions;

the key is saved.

On the network side, for example, on the LMF entity side, another key update apparatus provided in this embodiment of the present application includes:

the system comprises a determining unit, a judging unit and a processing unit, wherein the determining unit is used for determining a corresponding updated key when a Location Management Function (LMF) entity serving a terminal is updated, and the key is used for decrypting positioning auxiliary data;

and the sending unit is used for sending the key to the terminal.

On the network side, for example, on the AMF entity side, another key update apparatus provided in the embodiments of the present application includes:

the terminal comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a corresponding updated key when a Location Management Function (LMF) entity serving the terminal is updated, and the key is used for decrypting positioning auxiliary data;

and the sending unit is used for sending the key to the terminal.

On the terminal side, another key updating apparatus provided in the embodiment of the present application includes:

and the storage unit is used for storing the key.

Another embodiment of the present application provides a computing device, which includes a memory and a processor, wherein the memory is used for storing program instructions, and the processor is used for calling the program instructions stored in the memory and executing any one of the above methods according to the obtained program.

Another embodiment of the present application provides a computer storage medium having stored thereon computer-executable instructions for causing a computer to perform any one of the methods described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic diagram of a network architecture supporting location services in the prior art;

fig. 2 is a diagram illustrating a detailed process of broadcasting network assistance data in the prior art;

fig. 3 is a schematic view of an LMF modification flow provided in an embodiment of the present application;

fig. 4 is a schematic view of an LMF modification flow provided in an embodiment of the present application;

fig. 5 is a schematic view of an LMF modification flow provided in an embodiment of the present application;

fig. 6 is a schematic view of an LMF modification flow provided in an embodiment of the present application;

fig. 7 is a schematic view of an LMF modification flow provided in an embodiment of the present application;

fig. 8 is a schematic flowchart of a key updating method at the LMF entity side according to an embodiment of the present disclosure;

fig. 9 is a schematic flowchart of a key update method at the AMF entity side according to an embodiment of the present application;

fig. 10 is a flowchart illustrating a key updating method at a terminal side according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a key update apparatus on an LMF entity side according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a key update apparatus on the AMF entity side according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a key updating apparatus at a terminal side according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another key update apparatus on the LMF entity side according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of another key update apparatus on the AMF entity side according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another key updating apparatus at a terminal side according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the 5G system, when a preferred 5GC-MT-LR positioning method is adopted, the UE does not report the position information immediately, when positioning is triggered (possibly event-triggered positioning or possibly periodic triggered positioning), an external client initiates a positioning request for a target user to the GMLC, privacy verification is performed between the GMLC and the UDM, and if the UE allows positioning, the GMLC sends the positioning request to the AMF entity. The AMF entity selects an LMF entity, and a positioning process is executed between the UE and the LMF entity, wherein the UE may need to acquire positioning auxiliary information sent by the LMF entity from a network. At this time, due to the movement of the UE, the AMF entity selects a new LMF entity for the UE, which specifically includes the following steps, referring to fig. 3:

the UE triggers a Service Request (UE Triggered Service Request).

The UE sends a Non-access stratum (NAS) transport message containing the event report message to the serving AMF entity. The NAS transport message includes an Identifier (ID) indicating LMF 1 (the original LMF entity before update) and an Event Report (Event Report).

303. Based on operator configuration and policies, the AMF entity may evaluate and determine that LMF 1 is not suitable or capable of supporting the location of the current UE access network or serving cell, and determine that LMF2 (the updated target LMF entity) is the more suitable LMF entity.

The AMF entity invokes an AMF Communication N1message notification message (Namf _ Communication _ N1MessageNotify) service operation to LMF 1. The service operation includes the event report received in step 302. If the AMF entity determines in step 303 that a new LMF2 should be used, it also indicates to LMF 1.

305. If the AMF entity does not indicate a new LMF entity in step 304, LMF 1 may evaluate and determine that it is not suitable or capable of supporting the location of the current UE access network or serving cell and LMF2 is a more suitable LMF entity based on operator configuration and policy.

LMF 1 calls an LMF location context transfer (Nlmf _ location context transfer) request service operation to LMF2 to provide the current location context of the UE and includes the event report message received in step 304. The service operation includes the AMF entity identification and the information or all the information that LMF 1 initially receives periodically. The location request is triggered from either the AMF entity or from an early serving LMF entity according to this procedure. The service operation may also include a current status of the event report (e.g., a number of event reports received from the UE so far and/or a duration of the event reports so far) and may include location related information of the UE, such as a previous location estimate.

And 307, the LMF2 informs the LMF 1 of the position context transmission operation result (Nlmf _ LocatContextTransfer Response). LMF 1 then releases all resources of the process.

LMF2 invokes an AMF Communication N1N2message transfer (Namf _ Communication _ N1N2MessageTransfer) service operation to the AMF entity to request the transfer of an Event Report acknowledgement (Event Report acknowledgement) message to the UE. The event report acknowledgement indicates a change of the LMF entity and includes an identifier indicating LMF 2.

The AMF entity forwards the event report acknowledgement to the UE in a NAS transport message. The AMF entity also notifies the LMF2 of the delivery result of the event report confirmation.

310. If the event report requires a location estimate, LMF2 may perform a UE Positioning Procedure (UE Positioning Procedure) to determine the UE location.

Unlike the 5G and 4G, in the preferred 5GC-MT-LR procedure of the 5G system, the located context is stored in the LMF entity, and if the LMF entity is responsible for generating the key for the auxiliary data broadcast, the auxiliary data will change when the location of the UE changes (the auxiliary data includes the location information of the UE, the ID of the cell, and the timing sequence).

The LMF entity is responsible for selecting a positioning mode, and the LMF 1 selects several positioning modes according to a Public Land Mobile Network (PLMN) and quality of service (QoS), and generates a key corresponding to the positioning modes for positioning the assistance data. LMF 1 may pass the previous key to LMF2 for subsequent ciphering in sending assistance data to the UE. However, there are problems in that:

when the AMF entity reselects the LMF entity, the use of the previous key for encryption may cause a security risk due to the change of the assistance data, and the UE may need to establish a new key synchronization relationship with the new LMF entity before. Otherwise, the UE is in the range of the LMF2, and the information auxiliary information sent by the LMF entity cannot be obtained and is used for the positioning calculation of the UE.

After selecting the LMF2, other services request the positioning of the UE, and the LMF 1 selects different positioning modes according to the QoS of the service and the PLMN, which are different from the positioning modes selected by the LMF 1 before, and the UE cannot acquire the auxiliary data without a new key to perform the positioning of the UE.

In summary, in the 5G system, the NG-RAN transmits the encrypted network assistance data in a broadcast manner, and the UE decrypts the data based on the encryption key received from the network. The problem of LMF change may be involved in the procedure of the transferred 5GC-MT-LR, and there is no processing description of the key and the security context in this scenario at present, so the embodiments of the present application provide a key updating method and apparatus for providing a key updating solution for decrypting the positioning assistance data when the LMF entity serving the terminal is changed.

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a universal microwave Access (WiMAX) system, a 5G NR system, and the like. These various systems include terminal devices and network devices.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or other processing device connected to a wireless modem. The names of the terminal devices may also be different in different systems, for example, in a 5G system, the terminal devices may be referred to as User Equipments (UEs). Wireless terminal devices, which may be mobile terminal devices such as mobile telephones (or "cellular" telephones) and computers with mobile terminal devices, e.g., mobile devices that may be portable, pocket, hand-held, computer-included, or vehicle-mounted, communicate with one or more core networks via the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The network device according to the embodiment of the present application may be a core network device, such as an LMF entity and an AMF entity.

Various embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the display sequence of the embodiment of the present application only represents the sequence of the embodiment, and does not represent the merits of the technical solutions provided by the embodiments.

It should be noted that, in the embodiment of the present application, the key set information may be updated in the process of updating the key (that is, not only the updated key may be issued, but also information related to the updated key may be issued, and the key set information may include information such as a key type, a key, a validity period, and a key identifier. In the embodiment of the application, the key and the related information content can be carried in the NAS message, and the AMF entity is visible at the moment; or may be carried in a Long Term Evolution Positioning Protocol (LPP) message, for example, carried in an event report (event report) message, the AMF entity is invisible.

The first embodiment,

Referring to fig. 4, when the LMF entity needs to be changed, the network directly issues an updated key to the UE through the LMF entity change process, and indicates the UE to change, which specifically includes:

step 401 to step 406 are the same as the description of step 301 to step 306 in the LMF entity change flow shown in fig. 3, and are not described herein again.

After receiving the NLMF _ LocationContextTransfer request service operation, lmf2 generates a new Key (Key generation).

Step 407, same as step 307 in the LMF entity change flow shown in fig. 3.

And step 408, the LMF2 sends the updated key to the AMF entity through NAS information, wherein the NAS information carries a key update indication and/or a new key set.

Step 409, the AMF entity sends a key update indication and/or a new key set to the UE through the NAS message; or step 410, the LMF2 transmits the key update indication and/or the new key set (key update indication and/or new key set) to the AMF entity through the event report message, and the AMF entity forwards the key update indication and/or the new key set (key update indication and/or new key set) to the UE through the NAS message.

Example II,

Referring to fig. 5, when the LMG is changed, the AMF entity selects a new LMF entity, and the AMF entity requests a key from the LMF2 through the LMF 1 as a party for applying the key. The specific process is as follows:

steps 501 to 503 are the same as steps 301 to 303 in the LMF entity change flow shown in fig. 3, and are not described again here.

After selecting a new LMF entity, the AMF entity forwards the key request (which may also include the type of the key) to the source LMF entity, step 504.

Step 505 is the same as step 305 in the LMF entity change flow shown in fig. 3.

The source LMF entity forwards the key request (which may also include the type of key) to the target LMF entity, step 506.

Step 5x. the target LMF entity generates a new key.

Step 507 to step 510 are the same as step 407 to step 410 in the first embodiment, and are not described herein again.

Example III,

The UE carries the key request in the event report, and the specific flow is as shown in fig. 6, which includes:

step 601 is the same as step 301 of the LMF entity change flow shown in fig. 3.

Step 602, the UE carries the key request in the event report, and may also carry the key type of the request;

step 603 to step 610, which is the same as step 503 to step 510 in the embodiment, are not described herein again.

Example four,

The AMF entity transparently transmits (similar to 2G/3G method), and when the AMF entity just selects a new LMF entity and a new service initiates positioning, a key needs to be transmitted based on LPP protocol. Referring to fig. 7, the specific process includes:

steps 701 to 705 are the same as steps 301 to 305 described in the LMF entity change flow shown in fig. 3.

Step 706 comprises step 706a and step 706b, that is, LMF2 issues a key through a downlink positioning message, where the downlink positioning message carries a key update indication and/or a new key set.

Step 707 to step 710 are the same as the steps 306 to 309 described in the LMF entity change procedure shown in fig. 3.

It should be noted that, in step 707, the source LMF may request a key from the target LMF, and if the target LMF has sent an updated key through the downlink location message, the key information will be carried in the response message step 708 and 710, and if the requested key type is the same as that in step 706, the same key identifier is returned.

In summary, on the network side, for example, on the LMF entity side, referring to fig. 8, a key updating method provided in the embodiment of the present application includes:

s801, determining a corresponding updated key when an LMF entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data;

s802, the secret key is sent to the terminal.

By the method, a solution of how to update the key for decrypting the positioning assistance data when the LMF entity serving the terminal is changed is provided, so that the updated key can be sent to the terminal.

On the network side, for example, on the AMF entity side, referring to fig. 9, an embodiment of the present application provides a key updating method, including:

s901, receiving a corresponding updated key when a location management function LMF entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data;

s902, the secret key is sent to the terminal.

On the terminal side, referring to fig. 10, a key updating method provided in an embodiment of the present application includes:

s101, receiving a corresponding updated key when a Location Management Function (LMF) entity serving a terminal is updated, wherein the key is used for decrypting positioning auxiliary data;

and S102, storing the key.

On a network side, for example, on a core network device LMF entity side, referring to fig. 11, an apparatus for updating a key provided in an embodiment of the present application includes:

a memory 141 for storing program instructions;

a processor 140, configured to call the program instructions stored in the memory 141, and execute, according to the obtained program:

and sending the key to the terminal.

A transceiver 142 for receiving and transmitting data under the control of the processor 140.

Wherein in fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 140, and various circuits of memory, represented by memory 141, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 142 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 141 may store data used by the processor 140 in performing operations.

The processor 140 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD).

On a network side, for example, on an AMF entity side of a core network device, referring to fig. 12, an apparatus for updating a key provided in an embodiment of the present application includes:

a memory 155 for storing program instructions;

a processor 154 for calling the program instructions stored in said memory 155, and executing, according to the obtained program:

and sending the key to the terminal.

Optionally, when the key is received via a non-access stratum NAS message, the processor 154 is further configured to call the program instructions stored in the memory 155, and execute, according to the obtained program: and managing and storing the key.

A transceiver 151 for receiving and transmitting data under the control of the processor 154.

In FIG. 12, a bus architecture (represented by bus 156), bus 156 may include any number of interconnected buses and bridges, bus 156 linking together various circuits including one or more processors, represented by processor 154, and memory, represented by memory 155. The bus 150 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. Bus interface 153 provides an interface between bus 156 and transceiver 151. The transceiver 151 may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 154 is transmitted over a wireless medium via the antenna 152, and further, the antenna 152 receives the data and transmits the data to the processor 154.

The processor 154 is responsible for managing the bus 156 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 155 may be used to store data used by processor 154 in performing operations.

Alternatively, the processor 154 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

On the terminal side, referring to fig. 13, a key updating apparatus provided in an embodiment of the present application includes:

a memory 160 for storing program instructions;

a processor 161, configured to call the program instructions stored in the memory 160, and execute, according to the obtained program:

the key is saved.

A transceiver 162 for receiving and transmitting data under the control of the processor 161.

In fig. 13, among other things, the bus architecture may include any number of interconnected buses and bridges with various circuits of one or more processors, represented by processor 161, and memory, represented by memory 160, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 162 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 163 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 161 is responsible for managing the bus architecture and general processing, and the memory 160 may store data used by the processor 161 in performing operations.

Alternatively, the processor 161 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

On the network side, for example, on the LMF entity side, referring to fig. 14, another key updating apparatus provided in the embodiment of the present application includes:

a determining unit 11, configured to determine an updated key corresponding to an updated location management function LMF entity serving a terminal when the LMF entity is updated, where the key is used to decrypt positioning assistance data;

a sending unit 12, configured to send the key to the terminal.

On the network side, for example, on the AMF entity side, referring to fig. 15, another key update apparatus provided in the embodiment of the present application includes:

a receiving unit 21, configured to receive an updated key corresponding to an updated location management function LMF entity serving a terminal when the LMF entity is updated, where the key is used to decrypt positioning assistance data;

a sending unit 22, configured to send the key to the terminal.

Optionally, when receiving the key through a non-access stratum NAS message, the sending unit 22 is further configured to: and managing and storing the key.

On the terminal side, referring to fig. 16, another key updating apparatus provided in the embodiment of the present application includes:

a receiving unit 31, configured to receive an updated key corresponding to an updated location management function LMF entity serving a terminal when the LMF entity is updated, where the key is used to decrypt positioning assistance data;

a holding unit 32 for holding the key.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The embodiment of the present application provides a computing device, which may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a Personal Digital Assistant (PDA), and the like. The computing device may include a Central Processing Unit (CPU), memory, input/output devices, etc., the input devices may include a keyboard, mouse, touch screen, etc., and the output devices may include a Display device, such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), etc.

The memory may include Read Only Memory (ROM) and Random Access Memory (RAM), and provides the processor with program instructions and data stored in the memory. In the embodiments of the present application, the memory may be used for storing a program of any one of the methods provided by the embodiments of the present application.

The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained program instructions by calling the program instructions stored in the memory.

Embodiments of the present application provide a computer storage medium for storing computer program instructions for an apparatus provided in the embodiments of the present application, which includes a program for executing any one of the methods provided in the embodiments of the present application.

The computer storage media may be any available media or data storage device that can be accessed by a computer, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

The method provided by the embodiment of the application can be applied to terminal equipment and also can be applied to network equipment.

The Terminal device may also be referred to as a User Equipment (User Equipment, abbreviated as "UE"), a Mobile Station (Mobile Station, abbreviated as "MS"), a Mobile Terminal (Mobile Terminal), or the like, and optionally, the Terminal may have a capability of communicating with one or more core networks through a Radio Access Network (RAN), for example, the Terminal may be a Mobile phone (or referred to as a "cellular" phone), a computer with Mobile property, or the like, and for example, the Terminal may also be a portable, pocket, hand-held, computer-built-in, or vehicle-mounted Mobile device.

The network device may be a core network device.

The above method process flow may be implemented by a software program, which may be stored in a storage medium, and when the stored software program is called, the above method steps are performed.

To sum up, in the technical solution provided in the embodiment of the present application, the updated key may be issued by expanding NAS messages, or may be issued by expanding LPP messages. In particular, the amount of the solvent to be used,

1. when the LMF entity is changed, the target LMF entity sends a key to the AMF entity, and the AMF entity sends a new key to the UE through the NAS/LPP message. When the NAS message is issued, the AMF entity manages and stores the key; when the LPP message is issued, the LPP manages and stores the key.

2. When the LMF entity is changed, the AMF entity sends a key application, requests a new key from the updated target LMF entity, and the target LMF entity sends the new key to the UE through the AMF entity by NAS information.

3. When reporting an event, the UE carries a key request. When the LMF entity is changed, the UE initiates a service request to the network, the service request carries the key request and the key type, the target LMF entity receives the positioning request of the target UE, and the updated key is directly issued through the NAS or LPP message. If the UE carries the key request through the NAS message, the AMF entity is visible, and when the key is returned, the key is returned through the NAS message; if the UE carries the key request in the event report message, the AMF entity is invisible, only transparent transmission is carried out, and the key is returned through the LPP message.

4. When the LMF entity is changed, the target LMF entity receives the instant positioning request of new service at the same time, and sends the updated key to the UE through the downlink positioning message. When the NAS message is issued, the AMF entity can see the key; when the LPP message is issued, the AMF entity can not see the key.

Therefore, the technical scheme provided by the embodiment of the application solves the relevant problem of key updating when the LMF entity is changed.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for updating a key, the method comprising:

and sending the key to the terminal.

2. The method according to claim 1, characterized in that the key is sent to the terminal by means of a non-access stratum, NAS, message or a long term evolution positioning protocol, LPP, message.

3. Method according to claim 1 or 2, characterized in that the key is sent to a mobility management function, AMF, entity via an updated target LMF entity, and the key is sent to the terminal via the AMF entity.

4. Method according to claim 1 or 2, characterized in that, when receiving a new key request sent by a mobility management function, AMF, entity, the key is sent to the AMF entity, through which the key is sent to the terminal.

5. Method according to claim 1 or 2, characterized in that the key is sent to the terminal when a positioning request of the terminal is received.

6. A method according to claim 1 or 2, characterized in that said key is sent to said terminal by means of a downlink positioning message when an immediate positioning request for a new service is received.

7. A method for updating a key, the method comprising:

and sending the key to the terminal.

8. The method according to claim 7, characterized in that the key is sent to the terminal by means of a non-access stratum, NAS, message or a long term evolution positioning protocol, LPP, message.

9. The method as claimed in claim 7 or 8, wherein the key sent by the target LMF entity is received after sending a new key request to the updated target LMF entity.

10. The method of claim 7, wherein when the key is received via a non-access stratum (NAS) message, the method further comprises managing and maintaining the key.

11. A method for updating a key, the method comprising:

the key is saved.

12. The method according to claim 11, wherein the key is received via a non-access stratum, NAS, message or a long term evolution positioning protocol, LPP, message.

13. The method according to claim 11 or 12, wherein the key is received after a service request message is sent to a network side, and the service request message includes a key request and key type information.

14. The method of claim 13, wherein the service request message is a non-access stratum (NAS) message or an event report message.

15. A key update apparatus, characterized in that the apparatus comprises:

a memory for storing program instructions;

and sending the key to the terminal.

16. The apparatus of claim 15, wherein the key is sent to the terminal via a non-access stratum (NAS) message or a Long term evolution positioning protocol (LPP) message.

17. An arrangement according to claim 15 or 16, characterized in that said key is sent to a mobility management function, AMF, entity via an updated target LMF entity, said key being sent to said terminal via said AMF entity.

18. The arrangement according to claim 15 or 16, characterized in that, when receiving a new key request sent by a mobility management function, AMF, entity, the key is sent to the AMF entity, through which the key is sent to the terminal.

19. The apparatus according to claim 15 or 16, wherein the key is sent to the terminal when a positioning request of the terminal is received.

20. The arrangement according to claim 15 or 16, characterized in that said key is sent to said terminal by means of a downlink positioning message when an immediate positioning request for a new service is received.

21. A key update apparatus, characterized in that the apparatus comprises:

a memory for storing program instructions;

and sending the key to the terminal.

22. The apparatus of claim 21, wherein the key is sent to the terminal via a non-access stratum (NAS) message or a Long term evolution positioning protocol (LPP) message.

23. The apparatus as claimed in claim 21 or 22, wherein the key sent by the target LMF entity is received after sending a new key request to the updated target LMF entity.

24. The apparatus of claim 21, wherein when the key is received via a non-access stratum (NAS) message, the processor is further configured to invoke the program instructions stored in the memory to perform, in accordance with the obtained program: and managing and storing the key.

25. A key update apparatus, characterized in that the apparatus comprises:

a memory for storing program instructions;

the key is saved.

26. The apparatus of claim 25, wherein the key is received via a non-access stratum (NAS) message or a Long term evolution positioning protocol (LPP) message.

27. The apparatus according to claim 25 or 26, wherein the key is received after a service request message is sent to a network side, and the service request message includes a key request and key type information.

28. The apparatus of claim 27, wherein the service request message is a non-access stratum (NAS) message or an event report message.

29. A key update apparatus, characterized in that the apparatus comprises:

and the sending unit is used for sending the key to the terminal.

30. A key update apparatus, characterized in that the apparatus comprises:

and the sending unit is used for sending the key to the terminal.

31. A key update apparatus, characterized in that the apparatus comprises:

and the storage unit is used for storing the key.

32. A computer storage medium having stored thereon computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 14.