WO2025066165A1 - Communication method and apparatus - Google Patents

Abstract

Provided in the present application are a communication method and apparatus. The method comprises: a terminal device sending first information to a first network element, wherein the first information is used for requesting a first key, and the first key is used for encrypting assistance data; receiving a first message from the first network element, wherein the first message comprises first indication information, and the first indication information is used for indicating that the first key does not exist; if a first time or a time counter or a timer expires, sending second information to the first network element, wherein the second information is used for requesting the first key; or waiting for the first network element to send the first key. When a first key does not exist on or is not available to a network side (e.g., a first network element), by means of sending indication information for indicating that the first key does not exist or is not available, a terminal device is notified, in a timely manner, of a situation wherein there is no first key on the network side at present, such that the terminal device can be prevented from blindly and frequently attempting to initiate a request for acquiring the first key, and the energy consumption and network signaling overheads generated due to the terminal device blindly and frequently attempting to request the first key can be reduced.

Description

A communication method and device

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 28, 2023, with application number 202311294451.6 and application name “A Communication Method and Device”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a communication method and device.

Background Art

Real-time kinematic (RTK) positioning technology is a differential positioning technology, also known as carrier phase differential technology. In RTK positioning technology, the base station data center obtains auxiliary data (such as RTK auxiliary data) based on the global navigation satellite system (GNSS) positioning measurement results reported by the base station and the difference between the GNSS positioning data calculated based on the actual position of the base station. After that, the base station data center encrypts the auxiliary data and sends it to the base station through the location management function (LMF) network element and the mobility management (AMF) network element. Then, the base station broadcasts the encrypted auxiliary data, so that the positioning subjects such as terminal devices within the base station range can calibrate the positioning results (or correct them) according to the auxiliary data to improve the positioning accuracy.

Exemplarily, take the example of a terminal device obtaining RTK auxiliary data broadcast by a base station for positioning calibration. In order to successfully parse (or decrypt) the encrypted RTK auxiliary data broadcast by the base station, the terminal device must first obtain the RTK key corresponding to the encrypted RTK auxiliary data by accessing the AMF network element. Among them, the PTK key has a validity period and cannot be used after the validity period expires. However, in the process of the terminal device obtaining the RTK key, when the terminal device requests the RTK key from the AMF network element, the AMF network element temporarily does not have the RTK key, then there will be a problem of energy loss caused by the terminal device blindly trying to send the RTK key acquisition request; or when the AMF network element does not send the RTK key to the terminal device in time after updating the RTK key, the terminal device will be unable to parse the encrypted RTK auxiliary data due to the expiration of the RTK key. Therefore, the current solution for terminal devices to obtain RTK keys needs further study.

Summary of the invention

The present application provides a communication method and apparatus for enabling a terminal device to effectively obtain a key and successfully parse encrypted auxiliary data.

In a first aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, etc.). Optionally, the first communication device can be a terminal device or a component (such as a chip, a chip system or a circuit, etc.) that can support the terminal device to implement the functions required by the method, and the second communication device can be a first network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the first network element to implement the functions required by the method. Exemplarily, taking the data interaction between the terminal device and the first network element to implement the communication method as an example, in the method, the terminal device can send a first message to the first network element, the first message is used to request a first key, and the first key is used to encrypt auxiliary data. After that, the terminal device receives a first message from the first network element, the first message includes a first indication information, and the first indication information is used to indicate that the first key does not exist (Not exist) or is not available (Not available) or is not configured or stored. Then, if the first time or timer or timer (timer) expires, the terminal device sends a second message to the first network element, and the second information is used to request the first key, or the terminal device waits for the first network element to send the first key.

It should be understood that the present application does not limit the terminal device to sending the second information until the first time or the timer or the timer expires. The terminal device may also send the second information after randomly waiting for a period of time without limitation.

It should be understood that the assistance data in the present application can be understood as positioning assistance data, high-precision positioning assistance data, RTK data, GNSS assistance data, positioning data, differential positioning data, high-precision positioning data, GNSS positioning data, outdoor positioning data, satellite positioning data, positioning service data, high-precision positioning service data, differential positioning service data, GNSS positioning service data, satellite positioning service data, or RTK positioning service data. When a UE that has signed a high-precision service performs RTK positioning, it is necessary to calibrate its own positioning result according to the RTK calibration data broadcast by the network device (such as a base station) through the air interface to improve the positioning accuracy. It should be understood that the first information or the second information in the present application can be a key indication (for example, a cipher key or a ciphering key).

In the present method, during the process of the terminal device requesting to obtain the first key, the network side (such as the first network element) temporarily does not have the first key. By sending an indication message to the terminal device indicating that the first key does not exist or is unavailable, it is possible to promptly notify the terminal device when the network side temporarily does not have the first key requested by the terminal device. This helps to avoid the terminal device from blindly and frequently attempting to initiate a request to obtain the first key, and can reduce the energy consumption of the terminal device due to blindly and frequently attempting to request the first key. It can also help the terminal device to effectively obtain the latest key to parse encrypted auxiliary data, and can also reduce the signaling overhead of the network, especially in scenarios with a large number of terminals.

In one possible design, the terminal device sends first information to the first network element, including: if the auxiliary data is converted/switched from being received through the user plane of the terminal device to being received through the control plane, the terminal device sends the first information to the first network element, wherein the user plane reception may include reception through a session, for example, reception through a PDU session of the terminal device; the control plane reception may include reception through control plane signaling, for example, reception of a system message sent by an access network device, and the system message may include reception of a system message block (SIB).

In one possible design, when a terminal device receives an indication from a control plane to receive auxiliary data through a user plane (e.g., a PDU session) (e.g., from a third-party application or application function (Application Function, AF) or an application server (Application Server, AS), where the third-party application or AF or AS may be an auxiliary data center), the terminal device sends a first message to a first network element. It should be understood that in this design, since the third-party application or AF or AS can count the number of terminal devices from which auxiliary data is obtained (e.g., it can sense which terminal devices obtain auxiliary data from it through a PDU session), when the third-party application or AF or AS senses/determines that auxiliary data needs to be sent through the control plane (e.g., the user plane connection load is high or the outlet traffic pressure is high, etc.), an indication for notifying the control plane to receive auxiliary data is sent to these terminal devices through a PDU session.

In one possible design, the terminal device receives a notification message from the core network or base station, notifying it to receive auxiliary data through the control plane. This scenario can be that when a third-party application or AF or AS perceives/determines that auxiliary data needs to be sent through the control plane (for example, the user plane connection load is high or the export traffic pressure is high, etc.), the core network or base station is first notified, and then the core network or base station notifies the terminal device to switch/convert to receiving auxiliary data through the control plane.

In the above design, whether the receiving method of the auxiliary data has changed can be determined/perceived/known as a trigger condition for sending the first information, thereby ensuring that the sending of the first information is more in line with the actual needs of the terminal device.

In one possible design, the first message may also include second indication information, which may be used to indicate a first time or a timer or a timer, and the first time or a timer or a timer may be used to indicate a next request time for the first key, or to indicate a sending time for the next request information for the first key, or to indicate a start time for the next request information for the first key.

In the above design, during the process of the terminal device requesting to obtain the first key, the network side (such as the first network element) does not have the first key temporarily. By selectively generating the second indication information and carrying it in the first message and sending it to the terminal device, the terminal device can effectively request the first key according to the second indication information, thereby further avoiding the terminal device from blindly and frequently attempting to initiate a request to obtain the first key, helping to reduce the energy consumption caused by the terminal device's blindly and frequently attempting to request the first key, and can also reduce the signaling overhead of the network, especially in scenarios with a large number of terminals.

In a possible design, the first message may also include third indication information, where the third indication information is used to instruct the terminal device to wait for the first network element to send the first key.

In the above design, during the process of the terminal device requesting to obtain the first key, the network side (such as the first network element) temporarily does not have the first key. By selectively generating a third indication information and carrying it in the first message and sending it to the terminal device, the terminal device can wait for the first key to be issued according to the third indication information, thereby further avoiding the terminal device from blindly and frequently attempting to initiate a request to obtain the first key, which helps to reduce the energy consumption caused by the terminal device's blindly and frequently attempting to request the first key.

In one possible design, the auxiliary data is converted from being received through the user plane of the terminal device to being received through the control plane, including: receiving a system message block sent by the access network device to determine (or perceive) that the auxiliary data is converted from being received through the user plane of the terminal device to being received through the control plane; or not receiving a system message block sent by the access network device to determine that the auxiliary data is converted from being received through the control plane to being received through the user plane of the terminal device.

In the above design, the implementation methods for determining whether the receiving method of the auxiliary data has changed are flexible and diverse, which can ensure that the sending of the first information is more accurate and more in line with the actual sending situation.

In one possible design, a timer or timer is used to indicate a first duration, where the first duration is the time interval between two consecutive requests for the first key by the terminal device, and the first time is the sum of the time when the terminal device sends the first message and the first duration.

In a possible design, the first time is the sum of the time when the terminal device sends the first message and a second time length set by the terminal device.

In the above design, after the terminal device fails to request the first key according to the first information, it sends the information requesting the first key again after a period of time set by the terminal device, which helps to reduce the energy consumption caused by the terminal device's blind attempts to continuously request the first key.

In a second aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, etc.). Optionally, the first communication device can be a terminal device or a component (such as a chip, a chip system or a circuit, etc.) that can support the terminal device to implement the functions required by the method, and the second communication device can be a first network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the first network element to implement the functions required by the method. Exemplarily, taking the data interaction between the terminal device and the first network element to implement the communication method as an example, in the method, the first network element receives first information from the terminal device, wherein the first information is used to request a first key, and the first key is used to encrypt auxiliary data. Afterwards, if the first key does not exist or is not available, the first network element can send a first message to the terminal device, wherein the first message can include first indication information, and the first indication information can be used to indicate that the first key does not exist or is not available. Then, the first network element receives second information from the terminal device, or if the first key is obtained, sends the first key to the terminal device, wherein the second information is used to request the first key.

For the technical effects that can be achieved in the second aspect, please refer to the technical effects that can be achieved in the first aspect mentioned above, and no further details will be given here.

In one possible design, the first key does not exist or is unavailable, including: the first network element does not store the first key, for example, the local or remote distributed database does not store the first key; or if the first network element does not store the first key locally, a second message is sent to a second network element, wherein the second message is used to request the first key, and then the first network element receives a third message from the second network element, the third message may include fourth indication information, and the fourth indication information may be used to indicate that the first key does not exist or is unavailable.

In the above design, if the first network element does not store the first key locally (or does not exist or is not configured or is unavailable), the first network element requests the first key from the second network element, and further determines whether it is necessary to send an indication information to the terminal device to indicate that the first key does not exist or is unavailable based on the third message from the second network element, so that the terminal device can accurately know the request status of the first key.

In one possible design, the first network element obtains the first key, including: the first network element receives a fifth message from the second network element, and the fifth message may include the first key.

In the above design, after the second network element obtains the first key, it will send the first key to the first network element in a timely manner.

In one possible design, the first message may also include second indication information, which may be used to indicate a first time or a timer or a timer, and the first time or a timer or a timer may be used to indicate a next request time for the first key, or to indicate a sending time for the next request information for the first key, or to indicate a start time for the next request information for the first key.

For the beneficial effects of the above design, please refer to the relevant description of the first aspect, which will not be repeated here.

In a possible design, the first message may also include third indication information, and the third indication information may be used to instruct the terminal device to wait for the first network element to send the first key.

For the beneficial effects of the above design, please refer to the relevant description of the first aspect, which will not be repeated here.

In a third aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a second communication device, a third communication device, etc.). Optionally, the second communication device may be a first network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the first network element to implement the functions required by the method, and the third communication device may be a second network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the second network element to implement the functions required by the method. Exemplarily, taking the data interaction between the first network element and the second network element to implement the communication method as an example, in this method, after receiving the second message from the first network element, the second network element may send a third message to the first network element, the second message is used to request the first key, and the third message may include fourth indication information, and the fourth indication information may be used to indicate that the first key does not exist or is not available.

For the technical effects that can be achieved in the third aspect, please refer to the relevant description of the first aspect above, which will not be repeated here.

In one possible design, the method also includes: the second network element may send a fifth message to the first network element, and the fifth message may include the first key.

In a fourth aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, etc.). Optionally, the first communication device can be a first terminal device or a component (such as a chip, a chip system or a circuit, etc.) that can support the first terminal device to implement the functions required by the method, and the second communication device can be a first network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the first network element to implement the functions required by the method. Exemplarily, taking the communication method implemented by data interaction between the first terminal device and the first network element as an example, in this method, if the first terminal device is in a connection management connected state, the first network element can send a sixth message to the first terminal device, and the sixth message can be used to update NAS parameters or to notify the first terminal device that the key has been updated, and the sixth message may include the second key; or if the first terminal device is in a connection management idle state, the first network element can send a paging message to the first terminal device, and the paging message is used to page the first terminal device; thereafter, if the first network element receives a seventh message from the first terminal device, it can send an eighth message to the first terminal device, and the seventh message can be used to activate a user plane session, and the eighth message may include the second key. The user associated with the first terminal device is a user who has signed a contract for a first service, the first service may include a high-precision positioning service, and the second key is a new key for encrypting auxiliary data corresponding to the high-precision positioning service.

It should be understood that the high-precision positioning service in the present application can also be replaced by the following descriptions: RTK service, outdoor satellite positioning service, outdoor positioning service, differential service, etc., and the present application does not limit this.

It should be understood that the first terminal device associated user can be understood as the user of the first terminal device; or can be understood as the user holding the first terminal device; or can be understood as the user owning the first terminal device; or can be understood as the first terminal itself referring to the first user, that is, the first users can be replaced with each other, and this application is not limited.

It should be understood that the auxiliary data corresponding to the encrypted high-precision positioning service can be understood as the auxiliary data of the encrypted high-precision positioning service; and the new key can be understood as the updated key.

In this method, after obtaining the latest key (such as the second key), the first network element promptly pushes the second key to the terminal device associated with the user who has signed up for the first service (such as a high-precision positioning service). This allows the network side to promptly notify the relevant terminal devices after obtaining the latest key, so that the relevant terminal devices can use the latest key to successfully decrypt the encrypted auxiliary data, which helps to improve the positioning accuracy of the terminal devices.

In one possible design, the sixth message, the seventh message, or the eighth message is a non-access stratum NAS message.

In a possible design, the sixth message is a configuration update message (configuration update); the seventh message is a service request message (service request); and the eighth message is a service acceptance message (service accept).

In a fifth aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, etc.). Optionally, the first communication device may be a first terminal device or a component (such as a chip, a chip system or a circuit, etc.) that can support the first terminal device to implement the functions required for the method, and the second communication device may be a first network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the first network element to implement the functions required for the method. Exemplarily, taking the example of implementing a communication method by data interaction between a first terminal device and a first network element, in this method,

For the technical effects that can be achieved in the fifth aspect, please refer to the technical effects that can be achieved in the fourth aspect mentioned above, and no further details will be given here.

In one possible design, the sixth message, the seventh message, or the eighth message is a non-access stratum NAS message.

In one possible design, the sixth message is a configuration update message; the seventh message is a service request message; and the eighth message is a service reception message.

In a sixth aspect, the present application provides a possible communication device. Optionally, the communication device may be a communication device (such as a first communication device or a second communication device or a third communication device) or a component (such as a chip, a chip system or a circuit, etc.) that can support the communication device to implement the functions required for the communication method. Exemplarily, the first communication device may be a terminal device or a first terminal device (such as a UE), the second communication device may be a first network element (such as an AMF network element or an MME), and the third communication device may be a second network element (such as an LMF network element or an E-SMLC). When the communication device is a chip arranged in the first communication device (or the second communication device or the third communication device), the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to implement the transceiver of the communication device. The input and output interface may include an input interface and/or an output interface, the input interface can implement the reception of the communication device, and the output interface can be used to implement the sending of the communication device. The processor is used to read and execute corresponding computer programs or instructions so that the corresponding functions of the first communication device (or the second communication device or the third communication device) are implemented. Optionally, when the chip implements the corresponding functions of the first communication device (or the second communication device or the third communication device) in the communication method embodiment provided by the present application, the input and output interface can implement the sending and receiving operations performed by the first communication device (or the second communication device or the third communication device) in the communication method embodiment provided by the present application; the processor can implement other operations other than the sending and receiving operations performed by the first communication device (or the second communication device or the third communication device) in the above-mentioned communication method embodiment provided by the present application.

In one example, when the communication device is used to implement the function of the terminal device in the method embodiment shown in the first aspect or the second aspect, the beneficial effects can be referred to the description of the terminal device in the first aspect or the second aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the terminal device in the method embodiment shown in the first aspect or the second aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module (or a communication unit, a transceiver module or a transceiver unit, used to send and receive data) and a processing module (or a processing unit). The communication module is used to send a first message to a first network element. The first information is used to request a first key, and the first key is used to encrypt auxiliary data. The communication module is also used to receive a first message from the first network element. The first message includes a first indication information, and the first indication information is used to indicate that the first key does not exist or is not available. The processing module is used to send a second message to the first network element if the first time or timer or timer expires, or wait for the first network element to send the first key. The second information is used to request the first key. These modules can execute the corresponding functions of the terminal device in the method embodiments shown in the first aspect or the second aspect above. Please refer to the detailed description of the corresponding functions of the terminal device in the method examples, which will not be repeated here.

In another example, when the communication device is used to implement the method embodiment shown in the first aspect, the second aspect, or the third aspect, When the function of a network element is realized, the beneficial effects can refer to the description of the first network element in the first aspect, the second aspect or the third aspect, which will not be repeated here. The communication device has the function of realizing the behavior of the first network element in the method embodiment shown in the first aspect, the second aspect or the third aspect. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module and a processing module. The communication module is used to receive first information from a terminal device. The first information is used to request a first key, and the first key is used to encrypt auxiliary data. The processing module is used to send a first message to the terminal device if the first key does not exist or is not available. The first message includes first indication information, and the first indication information is used to indicate that the first key does not exist or is not available. The communication module is also used to receive second information from the terminal device, or if the first key is obtained, send the first key to the terminal device. The second information is used to request the first key. These modules can perform the corresponding functions of the first network element in the method embodiment shown in the first aspect, the second aspect or the third aspect, and specifically refer to the detailed description of the corresponding functions of the first network element in the method example, which will not be repeated here.

In another example, when the communication device is used to implement the function of the second network element in the method embodiment shown in the second aspect or the third aspect, the beneficial effects can refer to the description of the second network element in the second aspect or the third aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the second network element in the method embodiment shown in the second aspect or the third aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module and a processing module. The communication module is used to receive a second message from the first network element. The second message is used to request a first key. The processing module is used to send a third message to the first network element if the first key does not exist or is not available locally. The third message includes fourth indication information, and the fourth indication information is used to indicate that the first key does not exist or is not available. These modules can perform the corresponding functions of the second network element in the method embodiment shown in the second aspect or the third aspect, and specifically refer to the detailed description of the corresponding functions of the second network element in the method example, which will not be repeated here.

In another example, when the communication device is used to implement the function of the first network element in the method embodiment shown in the fourth aspect or the fifth aspect, the beneficial effects can be referred to the description of the first network element in the fourth aspect or the fifth aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the first network element in the method embodiment shown in the fourth aspect or the fifth aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module and a processing module. The communication module is used for the first terminal device to be in a connection management connection state, and send a sixth message to the first terminal device. The sixth message is used to update NAS parameters or to notify the first terminal device that the key has been updated; the sixth message includes a second key; the user associated with the first terminal device is a user who has signed a first service, and the first service includes a high-precision positioning service; the second key is a new key for encrypting auxiliary data corresponding to the high-precision positioning service. The communication module is also used to send a paging message to the first terminal device if the first terminal device is in a connection management idle state. The paging message is used to page the first terminal device. The communication module is also used to receive a seventh message from the first terminal device. Among them, the seventh message is used to activate the user plane session. The communication module is also used to send an eighth message to the first terminal device. Among them, the eighth message includes a second key. Optionally, the processing module is used to save (or store) the second key. The processing module is also used to determine the contracted user to whom the second key needs to be pushed. These modules can execute the corresponding functions of the first network element in the method embodiment shown in the fourth aspect or the fifth aspect above. Please refer to the detailed description of the corresponding functions of the first network element in the method example, which will not be repeated here.

In another example, when the communication device is used to implement the function of the first terminal device in the method embodiment shown in the fourth aspect or the fifth aspect, the beneficial effect can refer to the description of the first terminal device in the fourth aspect or the fifth aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the first terminal device in the method embodiment shown in the fourth aspect or the fifth aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes a communication module. The communication module is used to receive a sixth message from the first network element if the first terminal device is in a connection management connection state. The sixth message is used to update NAS parameters or to notify the first terminal device that the key has been updated; the sixth message includes a second key; the user associated with the first terminal device is a user who has signed a first service, and the first service includes a high-precision positioning service; the second key is a new key for encrypting auxiliary data corresponding to the high-precision positioning service. The communication module is also used to receive a paging message from the first network element if the first terminal device is in a connection management idle state. The paging message is used to page the first terminal device. The communication module is also used to send a seventh message to the first network element. The seventh message is used to activate the user plane session. The communication module is further used to receive an eighth message from the first network element. The eighth message includes the second key. These modules can execute the corresponding functions of the first terminal device in the method embodiment shown in the fourth aspect or the fifth aspect above. For details, please refer to the detailed description of the corresponding functions of the first terminal device in the method example, which will not be repeated here.

In another example, when the communication device is used to implement the function of the second network element in the method embodiment shown in the fourth aspect or the fifth aspect, the beneficial effects can be referred to the description of the second network element in the fourth aspect or the fifth aspect, which will not be repeated here. Implement the function of the behavior of the second network element in the method embodiment shown in the fourth aspect or the fifth aspect above. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes a communication module. The communication module is used to send a broadcast key data notification message to the first network element. Among them, the broadcast key data notification message includes a second key. These modules can execute the corresponding functions of the second network element in the method embodiment shown in the fourth aspect or the fifth aspect above. Please refer to the detailed description of the corresponding functions of the second network element in the method example, which will not be repeated here.

In the seventh aspect, the present application provides a possible communication device, which may be a communication device (such as a first communication device or a second communication device or a third communication device) required for executing the communication method provided in the present application, or may be a device including a communication device required for executing the communication method provided in the present application, or may be a device having the functions required to implement the communication method. Among them, the communication device may include a transceiver and a processor. Optionally, the communication device may also include a memory. Among them, the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the transceiver. When the processor executes the computer program or instruction, the communication device executes any possible design method of the first aspect above, any possible design method of the second aspect above, any possible design method of the third aspect above, any possible design method of the fourth aspect above, or any possible design method of the fifth aspect above.

In an eighth aspect, the present application provides a possible communication system, which may include the first communication device, the second communication device, and the third communication device mentioned in the first aspect, the second aspect, the third aspect, the fourth aspect, or the fifth aspect. The relevant functional implementation of the first communication device, the second communication device, or the third communication device can refer to the relevant description mentioned in the first aspect, the second aspect, the third aspect, the fourth aspect, or the fifth aspect, which will not be repeated here.

Exemplarily, the communication system may include one or more first communication devices, one or more second communication devices, and one or more third communication devices.

In the ninth aspect, the present application provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run on a computer, the computer executes any possible method in the design of the first aspect or any possible method in the design of the second aspect or any possible method in the design of the third aspect or any possible method in the design of the fourth aspect or any possible method in the design of the fifth aspect.

In the tenth aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a computer, the computer executes any possible design method of the first aspect or any possible design method of the second aspect or any possible design method of the third aspect or any possible design method of the fourth aspect or any possible design method of the fifth aspect.

In an eleventh aspect, the present application provides a chip, which may include a processor and a memory (or the chip is coupled to the memory), and the chip executes program instructions in the memory to execute the method in any possible design of the first aspect or the method in any possible design of the second aspect or the method in any possible design of the third aspect or the method in any possible design of the fourth aspect or the method in any possible design of the fifth aspect. Wherein, "coupling" refers to the direct or indirect combination of two components with each other, such as coupling can refer to an electrical connection between two components.

In a twelfth aspect, the present application further provides a chip system, which includes a processor for supporting a computer device to implement any possible method in the design of the first aspect or any possible method in the design of the second aspect or any possible method in the design of the third aspect or any possible method in the design of the fourth aspect or any possible method in the design of the fifth aspect. In one possible design, the chip system also includes a memory, which is used to store the necessary programs and data of the computer device. The chip system can be composed of chips, or it can include chips and other discrete devices.

Based on the implementations provided in the above aspects, this application can also be further combined to provide more implementations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1a exemplarily shows a possible communication system architecture diagram provided by an embodiment of the present application;

FIG. 1b exemplarily shows another possible communication system architecture diagram provided in an embodiment of the present application;

FIG2 exemplarily shows a schematic diagram of another possible communication system architecture provided in an embodiment of the present application;

FIG3 exemplarily shows a flow chart of a communication method provided in Embodiment 1 of the present application;

FIG4 exemplarily shows a flow chart of another communication method provided in Embodiment 1 of the present application;

FIG5 exemplarily shows a flow chart of another communication method provided in Embodiment 1 of the present application;

FIG6 exemplarily shows a flow chart of a communication method provided in Embodiment 2 of the present application;

FIG7 exemplarily shows a flow chart of another communication method provided in Embodiment 2 of the present application;

FIG8 exemplarily shows a flow chart of another communication method provided in Embodiment 2 of the present application;

FIG9 exemplarily shows a schematic structural diagram of a possible communication device provided in an embodiment of the present application;

FIG10 exemplarily shows a schematic structural diagram of another possible communication device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

The following is an introduction to possible communication system architectures applicable to the communication method provided in this application. It should be noted that these introductions are for the convenience of understanding by those skilled in the art and do not limit the scope of protection claimed in this application.

FIG. 1a exemplarily shows a possible communication system architecture diagram applicable to the embodiment of the present application. Among them, the communication system architecture shown in FIG. 1a is the fifth-generation (5th-generation, 5G) communication system architecture formulated by the third generation partnership project (3GPP) standard, and the communication system architecture includes terminal equipment, access network (such as (R)AN), core network (CN) and data network (DN). Optionally, the terminal equipment can be connected to the access network equipment (such as (R)AN equipment) in a wireless manner, and the access network equipment can be connected to the core network in a wireless or wired manner. The core network equipment and the wireless access network equipment can be independent and different physical devices, or the functions of the core network equipment and the logical functions of the wireless access network equipment can be integrated on the same physical device, or the functions of some core network equipment and some wireless access network equipment can be integrated on one physical device. Terminal equipment and terminal equipment and access network equipment and access network equipment can be connected to each other in a wired or wireless manner. Exemplarily, the communication system architecture may also include other network devices (such as wireless relay devices or wireless backhaul devices, etc.).

The following is a brief introduction to the functions of some devices included in the communication system architecture.

Terminal equipment: It is an entity on the user side that has the function of sending and receiving signals, and can provide users with service functions such as video, voice, and data connectivity. For example, the terminal equipment is the entrance for mobile users to interact with the network, and can provide basic computing and storage capabilities, display service windows to users, and receive user operation input. The next generation of terminal equipment (NextGen UE) can use new air interface technology to establish signal connections and data connections with (R)AN equipment, thereby transmitting control signals and service data to the mobile network.

Optionally, the terminal device may also be referred to as a terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent or UE device, etc. In the embodiment of the present application, the terminal device may be fixed or mobile, and the implementation of the present application does not limit this. Exemplarily, the terminal device may be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted, or may be deployed on the water (such as a ship, etc.), or may be deployed in the air (such as an airplane, a balloon or a satellite, etc.).

Exemplarily, the terminal device may be a mobile phone, a tablet computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA), a computer, a wireless modem, a handheld device (handset), a laptop computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, Wireless terminals in industrial control, vehicle-mounted terminal equipment, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, wearable terminal equipment, vehicles, drones, helicopters, airplanes, factory machines/equipment, machine type communication (MTC) terminals, ships or robots, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal equipment.

(R)AN equipment: is a device that connects terminal devices to wireless networks. For example, (R)AN equipment can provide network access functions for authorized users in a specific area, and can determine transmission tunnels of different qualities to transmit user data based on user levels, business requirements, etc. (R)AN equipment can manage its own resources, use them reasonably, provide access services to terminal devices on demand, and is responsible for forwarding control signals and user data between terminal devices and the core network.

Exemplarily, (R)AN equipment may include, but is not limited to: a next generation base station (next generation NodeB, gNB) in a fifth generation (5G) communication system, a next generation base station in a sixth generation (6G) communication system, a base station in a future communication system, a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (base station controller, BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc.

Optionally, in a network structure, the (R)AN device may also include a centralized unit (CU) or a distributed unit (DU). This structure can split the protocol layers of the network device, with the functions of some protocol layers being centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers being distributed in the DU, which is centrally controlled by the CU. For example, the functions of the packet data convergence protocol (PDCP) layer and above can be set in the CU, and the functions of the protocol layers below the PDCP (such as the RLC layer and the medium access control (MAC) layer, etc.) are set in the DU. It should be noted that this division of the protocol layers is only an example, and it can also be divided in other protocol layers. The radio frequency device can be remote and not placed in the DU, or it can be integrated in the DU, or part of it can be remote and part of it can be integrated in the DU, and the embodiments of the present application do not impose any restrictions. In addition, in some embodiments, the control plane (CP) and user plane (UP) of the CU can be separated and implemented by different entities, namely, the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity).

For example, taking the network device as a base station, the base station can communicate with the terminal device, or communicate with the terminal device through a relay station. The terminal device can communicate with multiple base stations in different access technologies.

In the embodiment of the present application, the (R)AN device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. The embodiment of the present application does not limit the specific technology and specific device form used by the wireless access network device.

Data network: A data network that provides business services to users. Generally, the client is located in the terminal device and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet. It can also be a proprietary network jointly deployed by operators, such as a network that provides IP multimedia core network subsystem (IMS) services.

Core network: responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for terminal devices. When the terminal device is attached, it provides network access authentication for the terminal device; when the terminal device has a service request, it allocates network resources for the terminal device; when the terminal device moves, it updates network resources for the terminal device; when the terminal device is idle, it provides a fast recovery mechanism for the terminal device; when the terminal device is detached, it releases network resources for the terminal device; when the terminal device has service data, it provides data routing functions for the terminal device, such as forwarding uplink data to the data network; or receiving downlink data of the terminal device from the data network and forwarding it to the (R)AN device, so that the (R)AN device sends it to the terminal device. Optionally, in terms of functional logic, the network elements of the core network can be divided into two parts: user plane network elements and control plane network elements. Among them, the user plane network elements are responsible for the transmission of service data. For example, the user plane network elements can include but are not limited to user plane function (UPF) network elements. The control plane network elements are responsible for the management of the mobile network. For example, the control plane may include but is not limited to access and mobility management function (AMF) network elements, session management function (SMF) network elements, unified data management (UDM) network elements, policy control function (PCF) network elements, application function (AF) network elements, authentication server function (AUSF) network elements, and network slice selection function (NSSF) network elements. Of course, the core network can also include other network elements (such as network exposure function (NEF) network elements, network storage function (NRF) network elements, unified data repository (UDR) network elements, network slice-specific authentication and authorization function (NSSAAF) network elements, etc.), which are not listed here one by one.

Optionally, the core network control plane adopts a service-oriented architecture, and the interaction between control plane network elements adopts the service call method to replace the point-to-point communication method in the traditional architecture. In the service-oriented architecture, the control plane network elements will open services to other control plane network elements for other control plane network elements to call; in point-to-point communication, the communication interface between control plane network elements will store a set of specific messages, which can only be used by the control plane network elements at both ends of the interface when communicating.

The following is a brief introduction to the functions of some network elements included in the core network:

(1) SMF network element: mainly used for session management, IP address allocation and management of terminal devices, selection of endpoints for manageable user equipment plane functions, policy control, or charging function interfaces, and downlink data notification, etc. For example, it can complete the establishment, release, and update processes related to protocol data unit (PDU) sessions. In 5G communication systems, session management network elements can be SMF network elements. In future communications such as the sixth-generation (6G) communication system, session management function network elements can still be SMF network elements, or have other names, which are not limited in this application. Nsmf is a service-based interface provided by SMF network elements. SMF network elements can communicate with other network functions through Nsmf.

(2) AMF network element: Mainly used for mobility management and access management, etc. For example, it can receive non-access stratum (NAS) signaling (including mobility management (MM) signaling and session management (SM) signaling) of terminal devices and related signaling of access network devices (such as N2 signaling at the base station granularity that interacts with AMF network elements), complete the user registration process and forwarding of SM signaling and mobility management. For example, it can be the mobility management entity (MME) in the fourth-generation (6G) communication system or the AMF network element in the 5G communication system. In future communication systems such as 6G communication systems, the access management network element can still be the AMF network element, or have other names, which is not limited in this application. Namf is a service-based interface provided by the AMF network element. The AMF network element can communicate with other network functions through Namf.

(3) UDM network element: used to process user identification, contract signing, access authentication, registration, or mobility management. In a 5G communication system, the data management network element may be a UDM network element. In future communication systems such as a 6G communication system, the data management network element may still be a UDM network element, or may have other names, which are not limited in this application. Nudm is a service-based interface provided by the UDM network element, and the UDM network element can communicate with other network functions through Nudm.

(4) PCF network element: a unified policy framework for guiding network behavior, providing policy rule information (such as mobility-related policies or PDU session-related policies (such as quality of service (QoS) policies, billing policies, etc.)) to control plane functional network elements (such as AMF, SMF, etc.). In a 5G communication system, the policy control network element may be a PCF network element. In future communication systems such as a 6G communication system, the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application. Npcf is a service-based interface provided by the PCF network element, and the PCF network element can communicate with other network functions through Npcf.

(5) AF network element: used for data routing affected by applications, access to network open functions, or interacting with the policy framework for policy control, etc. In a 5G communication system, an application network element may be an AF network element. In future communication systems such as a 6G communication system, an application network element may still be an AF network element, or have other names, which are not limited in this application. Naf is a service-based interface provided by AF, and an AF network element can communicate with other network functions through Naf.

(6) UPF network element: used for packet routing and forwarding, or QoS processing of user plane data, etc. In a 5G communication system, the user plane network element may be a UPF network element. In future communication systems such as a 6G communication system, the user plane network element may still be a UPF network element, or have other names, which are not limited in this application.

(7) AUSF network element: mainly used for user authentication, etc. In the 5G communication system, the authentication service network element can be the AUSF network element. In future communication systems such as the 6G communication system, the authentication service network element can still be the AUSF network element, or have other names, which are not limited in this application. Nausf is a service-based interface provided by the AUSF network element. The AUSF network element can communicate with other network functions through Nausf.

(8) NSSF network element: used to select a network slice for a terminal device. In a 5G communication system, the network slice selection function network element may be a NSSF network element. In future communication systems such as a 6G communication system, the network slice selection function network element may still be a NSSF network element, or may have other names, which is not limited in this application.

(9) NEF network element: used to securely open services and capabilities provided by 3GPP network functions to the outside. In a 5G communication system, a network open network element may be a NEF network element. In future communication systems such as a 6G communication system, a network open function network element may still be a NEF network element, or have other names, which are not limited in this application. Nnef is a service-based interface provided by the NEF network element, and the NEF network element can communicate with other network functions through Nnef.

(10) NRF network element: used to provide service registration, discovery and authorization, and maintain available network function (NF) instance information, which can realize on-demand configuration of network functions and services and interconnection between NFs. In the 5G communication system, the network storage network element can be an NRF network element. In future communication systems such as the 6G communication system, the network storage function network element can still be an NRF network element, or have other names, which is not limited in this application. Nnrf is a service-based interface provided by the NRF network element. The NRF network element can communicate with other network functions through Nnrf.

(11) NSSAAF network element: It is mainly responsible for the authentication and authorization of network slices and can interact with the authentication, authorization, and accounting server (AAA-S) through the authentication, authorization, and accounting proxy (AAA-P).

(12) UDR network element: used by UDM network elements to store subscription data or read subscription data and PCF network elements to store policy data or read policy data.

It is understandable that the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above network element or function can be implemented by one device, or by multiple devices, or a functional module in one device, which is not specifically limited in the embodiments of the present application.

As shown in Figure 1a, the terminal device can access the 5G communication system through access network devices such as (R)AN devices. The terminal device can communicate with the AMF network element through the next generation network (Next generation, NG) 1 interface (referred to as N1), the access network device communicates with the AMF network element through the N2 interface (referred to as N2), the access network device communicates with the UPF network element through the N3 interface (referred to as N3), the AMF network element communicates with the SMF network element through the N11 interface (referred to as N11), and the AMF network element communicates with the SMF network element through the N8 interface (referred to as N8). ) communicates with UDM network elements, AMF network elements communicate with AUSF network elements through N12 interface (N12 for short), AMF network elements communicate with PCF network elements through N15 interface (N15 for short), SMF network elements communicate with PCF network elements through N7 interface (N7 for short), SMF network elements communicate with UPF network elements through N4 interface (N4 for short), NEF network elements communicate with SMF network elements through N29 interface (N29 for short), and UPF network elements access the data network (DN) through N6 interface (N6 for short).

It should be noted that the names of the network elements and the interfaces between the network elements in Figure 1a are only used as an example. During the specific implementation process, the names of the network elements and the interfaces between the network elements may be other names, and the embodiments of the present application do not limit this.

FIG1b is a schematic diagram of another possible communication system architecture provided by the current technical specification (e.g., a schematic diagram of a network architecture for supporting positioning). This network architecture is an expansion of the communication system architecture shown in FIG1a. For example, multiple functional entities such as a gateway mobile location center (GMLC) network element, a location retrieval function (LRF) network element, a location service (LCS) client, and a location management function (LMF) network element are added to support positioning service functions.

The following is a brief introduction to the functions of the newly added functional entities in the network architecture shown in Figure 1b.

(1) GMLC network element: responsible for processing positioning requests for positioning services and selecting appropriate AMF network elements for positioning services.

(2) LRF network element: It can be configured with the GMLC network element or independently, and is responsible for retrieving or verifying the location information of the terminal device and providing routing and related information for the terminal device that has initiated the IMS emergency session.

(3) Location service client (LCS client): A positioning request can be sent to the GMLC network element through the Le interface between the GMLC network element and the LCS client to initiate positioning services for the UE.

(4)LMF network element: Mainly responsible for managing positioning requests, allocating positioning resources, and determining the location of terminal devices during positioning services.

For example, as shown in Figure 1b, NL1 is the interface between the AMF network element and the LMF network element. NL7 is the interface between the LMF network element and the LMF network element. N52 is the interface between the UDM network element and the NEF network element. NL2 is the interface between the AMF network element and the GMLC network element. NL5 is the interface between the NEF network element and the GMLC network element. N33 is the interface between the NEF network element and the AF network element. N51 is the interface between the AMF network element and the NEF network element. NL6 is the interface between the UDM network element and the GMLC network element. One Le is the interface between the LCS client and the GMLC network element; one Le is the interface between the LCS client and the LRF network element.

It should be understood that the introduction of the application architecture of the above-mentioned RTK positioning technology is based on the 5G communication system architecture as an example, while in the 4G communication system architecture, the AMF network element can be replaced by MME, and the LMF network element can be replaced by the evolved serving mobile location center (E-SMLC). Figure 2 is a schematic diagram of another possible communication system architecture (such as the positioning architecture of the 4G communication system) provided in an embodiment of the present application. As shown in Figure 2, the E-SMLC is similar to the role of the LMF network element, and the MME is similar to the role of the AMF network element. The MME can be connected to the access network device (such as the Evolved Universal Terrestrial Radio Access Network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN)) through the S1 application protocol (S1 application protocol, S1-AP) interface. In the embodiment of the present application, the LMF network element and the E-SMLC can be referred to as location management network elements. For example, as shown in Figure 2, LTE-Uu is the interface between UE and E-UTRAN; SLs is the interface between E-SMLC and MME; SLg is the interface between MME and GMLC network element; SLm is the interface between location measurement unit (LMU) and E-SMLC.

The specific implementation of the communication method in the embodiment of the present application is described in detail below based on the communication system architecture shown in Figure 1a, Figure 1b or Figure 2.

[Example 1]

Figure 3 exemplarily shows a flow chart of a communication method provided in Example 1 of the present application. The method is applicable to the communication system architecture illustrated in Figure 1a or Figure 1b or Figure 2. The method flow can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device and a third communication device). Optionally, the first communication device can be a terminal device or a component (such as a chip, a chip system or a circuit, etc.) that can support the terminal device to implement the functions required by the method, the second communication device can be a first network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the first network element to implement the functions required by the method, and the third communication device can be a second network element or a component (such as a chip, a chip system or a circuit, etc.) that can support the second network element to implement the functions required by the method. Exemplarily, when the communication method illustrated in Figure 3 is applicable to the communication system architecture illustrated in Figure 1a or Figure 1b, the terminal device can be the UE illustrated in Figure 1a or Figure 1b, the first network element can be the AMF network element illustrated in Figure 1a or Figure 1b, and the second network element can be the AMF network element illustrated in Figure 1a or Figure 1b. 1b. When the communication method illustrated in FIG. 3 is applicable to the communication system architecture illustrated in FIG. 2, the terminal device may be the UE illustrated in FIG. 2, the first network element may be the MME illustrated in FIG. 2, and the second network element may be the E-SMLC illustrated in FIG. 2. In order to facilitate the introduction of the technical solution provided in Example 1 of the present application, the following takes the first communication device as the terminal device, the second communication device as the first network element, and the third communication device as the second network element as an example to introduce the process of implementing the communication method by data interaction between the first communication device, the second communication device, and the third communication device. As shown in FIG. 3, the method includes:

Step 301: A terminal device sends first information to a first network element, and the first network element receives the first information.

Among them, the first information is used to request the first key, and the first key is used to encrypt the assistance data. For example, the first key requested by the terminal device may be one or more. Optionally, the first key can also be used to decrypt (or parse) the encrypted assistance data. For example, the first key can be an RTK key or a key of GNSS assistance data (GNSS assistance data) sent through posSIB or a key of assistance data. Exemplarily, the assistance data may refer to data used to assist the terminal device in achieving precise positioning, such as positioning assistance data. For example, the positioning assistance data may be RTK positioning assistance data.

For example, when the first network element is an AMF network element, the first information may be carried in a registration request message (Registration Request) message or other messages. When the first network element is an MME, the first information may be carried in a tracking area update request (Tracing Area Update Request, TAU Request) message or other messages.

Optionally, the first information may pass through one or more access network devices (such as base stations) during the process of being sent by the terminal device to the first network element. For example, when the diagram shown in FIG3 is applicable to the communication system architecture shown in FIG1a or FIG1b, the access network device may be a next-generation base station (such as gNB) in a 5G communication system, and when the diagram shown in FIG3 is applicable to the communication system architecture shown in FIG2, the access network device may be a base station (such as eNB) in a 4G communication system.

Exemplarily, the implementation process of a terminal device sending the first information to a first network element is introduced below through the following possible implementation methods.

Method 1: If the auxiliary data is converted from (or received from) a user plane (e.g., a PDU session) of the terminal device to a control plane, the terminal device may send the first information to the first network element. For example, the control plane reception may include receiving a system information block (SIB) sent by the access network device.

Exemplarily, in the following possible situations, the auxiliary data is converted from being received through a user plane of the terminal device to being received through a control plane.

Scenario 1: The terminal device receives (or obtains) a system message block (or may be referred to as a system information block) sent by the access network device and determines (or senses) that the auxiliary data (or the first key) is converted from being received by the user plane of the terminal device to being received by the control plane. For example, the terminal device discovers (or determines) that the auxiliary data is converted from being received by the user plane of the terminal device to being received by the SIB sent by the access network device (such as the positioning SIB of the air interface).

Scenario 2: The terminal device does not receive (or does not obtain) the system message block sent by the access network device to determine that the auxiliary data is converted from being received through the control plane to being received through the user plane of the terminal device.

Method 2: If the terminal device determines that the first key is invalid (for example, the first key is not available in the area where the terminal device is located or the available time of the first key is lower than the preset threshold T3512 or the usage period of the first key exceeds the validity period, etc.), the terminal device sends the first information to the first network element.

Step 302: The first network element does not have the first key locally, and sends a second message to the second network element. The second network element receives the second message.

In one example, if the first network element determines that the first key requested by the terminal device does not exist locally (or is not configured or is not available or stored), the first network element may send a first request message (such as a second message) to the second network element. Exemplarily, the first request message may carry (or include or contain) an identifier or name or type of the first key.

In another example, if the first network element determines that the RTK key requested by the UE exists locally (or is configured or can be obtained or stored), the first network element can send a NAS message to the terminal device. The NAS message can carry the first key requested by the terminal device. The NAS message can be a Registration Accept (or Registration Accept) message.

Step 303: The second network element does not have the first key locally, and sends a third message to the first network element. The first network element receives the third message.

For example, the third message may be a response message of the second message.

In one example, if the second network element determines that the first key requested by the terminal device does not exist locally (or is not configured or is not available or is not stored), the second network element may send a third message to the first network element. The third message may be a response message to the second message. Exemplarily, the third message may include fourth indication information, and the fourth indication information is used to indicate that the first key does not exist (or is not configured or is not available or is not stored).

In another example, if the second network element determines that the first key requested by the terminal device exists locally (or is configured or can be obtained or stored), the second network element may send a response message to the first network element. Exemplarily, the response message may carry the first key.

In another example, if the second network element determines that the first key requested by the terminal device does not exist locally, but after a period of time, ... The second network element obtains the first key requested by the terminal device, and at this time the second network element may send a fifth message to the first network element. Exemplarily, the fifth message may carry the first key.

The above steps 302 to 303 are optional steps, that is, they do not need to be performed in some application scenarios, but need to be performed in some application scenarios.

Step 304: The first network element sends a first message to the terminal device. The terminal device receives the first message.

In one possible implementation, if the first network element does not have the first key requested by the terminal device locally (for example, the first network element directly feeds back the first message when the first key requested by the terminal device does not exist locally, i.e., does not execute the above steps 302 to 303) or the first network element learns that the first key requested by the terminal device does not exist locally in the second network element, then the first network element can send the first message to the terminal device. In this way, this implementation can timely notify the terminal device that the network side (such as the first network element or the second network element) does not have the first key temporarily, thereby avoiding the terminal device from blindly attempting to initiate a request to obtain the first key, which helps to reduce the energy consumption of the terminal device (such as resource consumption, power consumption, or signaling overhead, etc.).

Exemplarily, the first message may include first indication information, and the first indication information is used to indicate that the first key does not exist (or is not configured or is not available or is not stored). For example, the first indication information may be a reason value/cause (cause) used to indicate that the first key does not exist (or is not configured or is not available or is not stored), such as a reason value of 1 is used to indicate that the first key exists, and a reason value of 0 is used to indicate that the first key does not exist; or, a reason value of 0 is used to indicate that the first key exists, and a reason value of 1 is used to indicate that the first key does not exist; or, carrying a reason value indicates that the first key does not exist, and not carrying a reason value indicates that the first key exists. The reason/cause value may be a Boolean type or an enumeration type or a character type or an integer type, which is not limited in the embodiments of the present application.

In one example, the first message may also include second indication information, and the second indication information is used to indicate a first time or a timer or a timer. Optionally, the first time or a timer (Timer) or a timer (Timer) is used to indicate the next request time of the first key, or to indicate the sending time of the next request information of the first key, or to indicate the start time of the next request information of the first key, or to indicate the start time of the next request information of the first key. For example, the timer or timer can also be used to indicate the first duration, in which case the first time may refer to the sum of the time when the terminal device sends the first information and the first duration. Among them, the first duration is the time interval between two adjacent requests for the first key by the terminal device.

In addition, when the first message does not carry the second indication information, the first time may refer to the sum of the time when the terminal device sends the first information and the second time length set by the terminal device.

In another example, the first message may further include third indication information, and the third indication information is used to indicate that the terminal device is waiting for the first network element to send the first key. Optionally, after generating the third indication information, the first network element may mark the user associated with the terminal device as waiting for the first key to be sent. Afterwards, after obtaining the first key sent by the second network element, the first network element may promptly send the first key to the terminal device, thereby avoiding the terminal device from blindly attempting to initiate a request to obtain the first key, which helps to reduce the energy consumption of the terminal device.

For example, after acquiring the first key sent by the second network element, the first network element may send the first key to the terminal device. Exemplarily, the first key may be carried in an information or may also be carried in a message.

In another possible implementation, if the first network element locally stores the first key requested by the terminal device or the first network element learns that the second network element locally stores the first key requested by the terminal device, the first network element may send a response message to the terminal device. Exemplarily, the response message may carry the first key.

Step 305: When the first time or the timer or the timer expires, the terminal device sends the second information to the first network element, or waits for the first network element to send the first key. Optionally, the first network element receives the second information.

Exemplarily, the second information may be used to request the first key again, or to initiate a request to obtain the first key again.

In a possible implementation, when the first message includes the first indication information but does not include the second indication information and the third indication information, the first time may refer to the sum of the time when the terminal device sends the first information and the second time period set by the terminal device. The terminal device may send the second information to the first network element when the first time expires.

In another possible implementation, when the first message includes the first indication information and the second indication information, the terminal device may send the second information to the first network element at the first time or when the timer or timer expires. For example, when the timer or timer is used to indicate the first duration, the first time may refer to the sum of the time when the terminal device sends the first information and the first duration.

In another possible implementation, when the first message includes the first indication information and the third indication information, the terminal device may temporarily not send information for requesting the first key to the first network element, but wait for the first network element to send the first key. In this way, the implementation can avoid the terminal device from blindly attempting to initiate a request to obtain the first key, which helps to reduce the energy consumption of the terminal device.

It can be seen from the above steps 301 to 305 that in the process of the terminal device requesting to obtain the first key, the network side (such as the first network element or the second network element) does not have the first key, and sends an indication message indicating that the first key does not exist or is unavailable to the terminal device. The device can promptly notify the terminal device when the network side temporarily does not have the first key requested by the terminal device, which helps to avoid the terminal device from blindly and frequently trying to initiate a request for the first key, and can reduce the energy consumption caused by the terminal device blindly and frequently trying to request the first key. It can also help the terminal device effectively obtain the key for parsing encrypted auxiliary data.

Based on the technical solution of the communication method shown in FIG. 3 above, the following specific examples shown in FIG. 4 to FIG. 5 respectively introduce the implementation process of the communication method provided in the embodiment of the present application under the 5G communication system architecture and the 4G communication system architecture. In the specific example shown in FIG. 4, the terminal device is UE, the (R) AN device is gNB (or can be called NG-(R) AN device), the first key is RTK key, the first network element is AMF network element, the second network element is LMF network element, and the auxiliary data is RTK positioning auxiliary data; in the specific example shown in FIG. 5, the terminal device is UE, the (R) AN device is eNB (or can be called eNodeB), the first key is RTK key, the first network element is MME, the second network element is E-SMLC, and the auxiliary data is RTK positioning auxiliary data. It can be understood that in the embodiment of the present application, the action performed by a network element can also be replaced by the action performed by the functional component in the network element. In the embodiment of the present application, the functional component may, for example, include at least one of a chip, a chip system, a processor, and a processing unit.

FIG4 is a flow chart of another communication method provided in Embodiment 1 of the present application. The communication method shown in FIG4 is applicable to a 5G communication system architecture (or can be understood as a 5G core network (Core) architecture). As shown in FIG4 , the specific flow of the method may include:

Step 401: The UE sends a registration request message to the AMF network element. The AMF network element receives the registration request message.

For example, the registration request message may be a NAS message. Exemplarily, the registration request message may carry information or indication information requesting an RTK key (such as an indication requesting a Cipher Key) for requesting an RTK key (Cipher Key). Optionally, the registration request message may also carry an identifier, name, or type of the RTK key requested by the UE. Optionally, the RTK key requested by the UE may be one or more.

Optionally, the registration request message may pass through one or more gNBs during the process of being sent from the UE to the AMF network element. For example, taking one gNB as an example, the UE may first send the registration request message to the gNB in its area, and the gNB may send the registration request message to the AMF network element.

Exemplarily, the implementation process of the UE sending a registration request message to the AMF network element is introduced below through the following possible implementation methods.

Method 1: The UE receives RTK positioning assistance data (or RTK key) through the user plane of the UE (e.g., PDU session) at the beginning. When the UE needs to convert the RTK positioning assistance data received by the user plane of the UE to the RTK positioning assistance data received by the control plane (e.g., the UE discovers/determines that the RTK positioning assistance data is converted from being received through the user plane of the UE to being received through the positioning SIB message of the air interface), the UE sends a registration request message to the AMF network element. For example, the registration request message may carry an indication of requesting an RTK key (Cipher Key), or may also carry an identifier, name, or type of the RTK key.

Method 2: When the UE determines that the RTK key is invalid (for example, it is not available in the area where the UE is located or the RTK key availability time is lower than the preset threshold T3512 or the RTK key usage period exceeds the validity period, etc.), the UE sends a registration request message to the AMF network element.

Step 402: If the RTK key requested by the UE is not stored locally, the AMF network element sends a first request message to the LMF network element. The LMF network element receives the first request message.

Optionally, if the AMF network element determines that the RTK key requested by the UE is stored locally, the AMF network element may send a Registration Accept message (or Registration Accept) to the UE. Exemplarily, the Registration Accept message may carry the RTK key requested by the UE. For example, the Registration Accept message may be a NAS message.

The first request message is used to request an RTK key. Exemplarily, the first request message may carry an identifier or name of the RTK key requested by the UE.

Step 403: The LMF network element sends a request response message to the AMF network element. The AMF network element receives the request response message.

Exemplarily, the LMF network element may carry indication information (such as data availability (DataAvailability)) in the request response message. Optionally, the indication information may be used to indicate whether the LMF network element locally stores the RTK key requested by the UE, or may be used to indicate whether the LMF network element is locally configured with the RTK key requested by the UE, or may be used to indicate whether the LMF network element locally can obtain the RTK key requested by the UE. For example, DataAvailability may be a cause value used to indicate the presence or absence of an RTK key, such as a cause value of 1 used to indicate that the RTK key exists, and a cause value of 0 used to indicate that the RTK key does not exist.

In one possible implementation, when the LMF network element determines that the RTK key requested by the UE is not stored locally, it can carry the indication information DataAvailability = "CIPHERING_KEY_DATA_NOT_AVAILABLE" in the request response message. The indication information is used to indicate that the RTK key requested by the UE is not available (or used to indicate that the RTK key requested by the UE has not been queried).

In another possible implementation, when the LMF network element determines that the RTK key requested by the UE is stored locally, the indication information DataAvailability = "CIPHERING_KEY_DATA_AVAILABLE" can be carried in the request response message, and the indication information is used to indicate that the RTK key requested by the UE is available (or used to indicate that the RTK key requested by the UE can be queried), and the request response message is also It can carry the RTK key requested by the UE.

Step 404: The AMF network element sends a registration reception message to the UE. The UE receives the registration reception message.

In a possible implementation, when the AMF network element determines that the request response message carries the indication information DataAvailability = "CIPHERING_KEY_DATA_NOT_AVAILABLE", the AMF network element may carry the indication information DataAvailability = "CIPHERING_KEY_DATA_NOT_AVAILABLE" in the registration reception message. Optionally, the AMF network element may also carry the first information in the registration reception message. In one example, the first information may be information indicating a timer, where the timer is used to indicate the time when the UE attempts to request the RTK key next time, or the first information may indicate the time when the UE attempts to request the RTK key next time. In another example, the first information may indicate a first duration, where the first duration is the time interval between two consecutive acquisitions of the RTK key by the UE. In yet another example, the first information may indicate that the UE is waiting for the AMF network element to send the RTK key. In addition, in this example, the AMF network element may mark that the UE-associated user is waiting for the RTK key to be sent, and after obtaining the RTK key sent by the LMF network element, the AMF network element may send the RTK key to the UE.

In another possible implementation, when the AMF network element determines that the request response message carries DataAvailability = "CIPHERING_KEY_DATA_AVAILABLE", it can obtain the RTK key requested by the UE from the request response message, and can carry the RTK key requested by the UE in the registration reception message.

Optionally, the registration reception message may pass through one or more gNBs during the process of being sent from the AMF network element to the UE. For example, taking one gNB as an example, the AMF network element may first send the registration reception message to the gNB, and the gNB may send the registration reception message to the UE.

Step 405: If the indication information included in the registration reception message indicates that the RTK key is not available, the UE sends a second request message to the AMF network element or waits for the AMF network element to send the RTK key.

Exemplarily, the second request message may carry information or indication information for requesting the RTK key again (such as an indication for requesting the Cipher Key again) for requesting the RTK key again. Optionally, the second request message may also carry an identifier or name of the RTK key requested by the UE. For example, the second request message may be a new registration request message, or may be a message for requesting the RTK key again.

Optionally, the second request message may pass through one or more gNBs during the process of being sent by the UE to the AMF network element. For example, taking one gNB as an example, the UE may first send the second request message to the gNB in its area, and the gNB may send the second request message to the AMF network element.

Exemplarily, the implementation process of the UE sending a second request message to the AMF network element is introduced below through the following possible implementation methods.

Method 1: When the indication information included (or carried) in the registration reception message indicates that the RTK key is not available and the first information included in the registration reception message indicates the time when the UE will attempt to request the RTK key next time, the UE can send a second request message to the AMF network element when the time for the next attempt to request the RTK key arrives.

Method 2: When the indication information included in the registration reception message indicates that the RTK key is not available and the first information included in the registration reception message indicates a first duration, the UE can send a second request message to the AMF network element after the first duration has passed since the last time the RTK key was requested. Method 3: When the indication information included in the registration reception message indicates that the RTK key is not available, the UE can send a second request message to the AMF network element after the second duration set by the UE has passed since the last time the RTK key was requested.

In addition, if the indication information included in the registration reception message indicates that the RTK key is not available and the first information included in the registration reception message indicates that the UE is waiting for the AMF network element to send the RTK key, the UE may not send a second request message to the AMF network element, but wait for the AMF network element to send the RTK key.

It can be seen from the above steps 401 to 405 that for the 5GC communication scenario, when the UE requests to obtain the RTK key, the network side (such as the LMF network element or the AMF network element) does not have the RTK key temporarily, and selectively generates indication information (such as indication information or second information for indicating that the RTK key requested by the UE is not available) and carries it in the registration reception message and sends it to the UE. In this way, the method can timely notify the UE when the network side temporarily does not have the RTK key requested by the UE, which helps to reduce the energy consumption caused by the UE blindly trying to request the RTK key, thereby effectively avoiding the problem that the UE generates certain energy consumption losses (such as signaling overhead or power loss or communication resource consumption, etc.) due to the UE blindly trying to request the RTK key.

FIG5 is a flow chart of another communication method provided in Embodiment 1 of the present application. The communication method shown in FIG5 is applicable to a 4G communication system architecture (or can be understood as a 4G core network (Evolved Packet Core, EPC) or an Evolved Packet System (Evolved Packet System, EPS)). As shown in FIG5, the specific flow of the method may include:

Step 501: UE sends a tracking area update request message to MME. MME receives the tracking area update request message.

For example, the tracking area update request message may pass through one or more eNodeBs during the process of being sent from the UE to the MME. For example, taking one eNodeB as an example, the UE may first send the tracking area update request message to the eNodeB in its area, and the eNodeB The tracking area update request message is sent to the MME.

Optionally, the implementation method of the UE sending the tracking area update request message to the MME in step 501 can refer to the implementation method of the UE sending the registration request message to the AMF network element in the above step 401, which will not be repeated here.

Step 502: If the RTK key requested by the UE is not stored locally, the MME sends a third request message to the E-SMLC. The E-SMLC receives the third request message.

Optionally, if the MME determines that the RTK key requested by the UE is stored locally, the MME may send a Tracking Area Update Accept (or Tracking Area Update Accept) (TAU Accept) message to the UE. Exemplarily, the Tracking Area Update Accept message may carry the RTK key requested by the UE.

The third request message is used to request the RTK key. Exemplarily, the third request message may carry an identifier or name of the RTK key requested by the UE. For example, the third request message may be an interface message.

Step 503: The E-SMLC sends a request response message to the MME. The MME receives the request response message.

Exemplarily, the E-SMLC may carry indication information in the request response message. Optionally, the indication information may be used to indicate whether the E-SMLC locally stores the RTK key requested by the UE, or may be used to indicate whether the E-SMLC locally is configured with the RTK key requested by the UE, or may be used to indicate whether the E-SMLC locally can obtain the RTK key requested by the UE. For example, the indication information may be an indication of DataAvailability, or may be information used to indicate the presence or absence of the RTK key, for example, it may be a cause/cause value, such as a cause/cause value of 1 is used to indicate that the RTK key exists, and a cause/cause value of 0 is used to indicate that the RTK key does not exist. For another example, a cause/cause value of 0 indicates that the RTK key does not exist, and a cause/cause value of 1 is used to indicate that the RTK key exists. For another example, a cause/cause value carries an indication that the key does not exist, and a cause/cause value does not carry an indication that the key exists.

In one possible implementation, when the E-SMLC determines that the RTK key requested by the UE is stored locally, the E-SMLC may carry indication information in the request response message, where the indication information is used to indicate that the RTK key requested by the UE is available (or used to indicate that the RTK key requested by the UE can be queried), and the request response message may also carry the RTK key requested by the UE.

In another possible implementation, when the E-SMLC determines that the RTK key requested by the UE is not stored locally, the E-SMLC may carry indication information in the request response message, where the indication information is used to indicate that the RTK key requested by the UE is not available (or used to indicate that the RTK key requested by the UE is not queried).

Step 504: The MME sends a tracking area update reception message to the UE. The UE receives the tracking area update reception message.

In one possible implementation, if the MME determines that the indication information included in the request response message indicates that the RTK key requested by the UE is available, the MME can obtain the RTK key requested by the UE from the request response message and can carry the RTK key requested by the UE in the tracking area update reception message.

In another possible implementation, if the indication information included in the determination request response message by the MME indicates that the RTK key requested by the UE is not available, the MME may carry the indication information for indicating that the RTK key requested by the UE is not available in the tracking area update reception message. Optionally, the MME may also carry the second information in the tracking area update reception message. In one example, the second information may be information indicating a timer, the timer being used to indicate the time when the UE attempts to request the RTK key next time, or the second information may indicate the time when the UE attempts to request the RTK key next time. In another example, the second information may indicate a first duration, the first duration being the time interval between two consecutive acquisitions of the RTK key by the UE. In yet another example, the second information may indicate that the UE is waiting for the MME to send the RTK key. In addition, in this example, the MME may mark the UE-associated user as waiting for the RTK key to be sent, and after obtaining the RTK key sent by the E-SMLC, the MME may send the RTK key to the UE.

Step 505: If the indication information included in the tracking area update reception message indicates that the RTK key is unavailable, the UE sends a fourth request message to the MME or waits for the MME to send the RTK key.

Exemplarily, the fourth request message may carry information or indication information for requesting the RTK key again (such as an indication for requesting the Cipher Key again) for requesting the RTK key again. Optionally, the fourth request message may also carry an identifier or name of the RTK key requested by the UE. For example, the fourth request message may be a new tracking area update request message, or may be a message for requesting the RTK key again.

For example, the fourth request message may pass through one or more eNodeBs during the process of being sent from the UE to the MME. For example, taking one eNodeB as an example, the UE may first send the fourth request message to the eNodeB in its area, and the eNodeB may send the second request message to the MME.

Optionally, the implementation method of the UE sending the fourth request message to the MME in step 505 can refer to the implementation method of the UE sending the second request message to the AMF network element in the above step 405, which will not be repeated here.

In addition, if the indication information included in the tracking area update reception message indicates that the RTK key is not available and the tracking area update reception message If the second information included in the message indicates that the UE waits for the MME to send the RTK key, the UE may not send the fourth request message to the MME, but wait for the MME to send the RTK key.

It can be seen from the above steps 501 to 505 that for the EPC communication scenario, when the UE requests to obtain the RTK key, the network side (such as E-SMLC or MME) does not have the RTK key temporarily, and selectively generates indication information (such as indication information or second information for indicating that the RTK key requested by the UE is not available) and carries it in the tracking area update reception message and sends it to the UE. In this way, the method can timely notify the UE when the network side temporarily does not have the RTK key requested by the UE, which helps to reduce the energy consumption caused by the UE blindly trying to request the RTK key, thereby effectively avoiding the problem that the UE generates certain energy consumption losses (such as signaling overhead or power loss or communication resource consumption, etc.) due to the UE blindly trying to request the RTK key.

[Example 2]

FIG6 exemplarily shows a flow chart of a communication method provided in Embodiment 2 of the present application. The method is applicable to the communication system architecture illustrated in FIG2. The method flow may be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, and a third communication device). Optionally, the first communication device may be a first terminal device or a component (such as a chip, a chip system, or a circuit, etc.) that can support the first terminal device to implement the functions required by the method, the second communication device may be a first network element or a component (such as a chip, a chip system, or a circuit, etc.) that can support the first network element to implement the functions required by the method, and the third communication device may be a second network element or a component (such as a chip, a chip system, or a circuit, etc.) that can support the second network element to implement the functions required by the method. Exemplarily, when the communication method illustrated in FIG6 is applicable to the communication system architecture illustrated in FIG1a or FIG1b, the terminal device may be the UE illustrated in FIG1a or FIG1b, the first network element may be the AMF network element illustrated in FIG1a or FIG1b, and the second network element may be the LMF network element illustrated in FIG1a or FIG1b. When the communication method illustrated in FIG6 is applicable to the communication system architecture illustrated in FIG2, the terminal device may be the UE illustrated in FIG2, the first network element may be the MME illustrated in FIG2, and the second network element may be the E-SMLC illustrated in FIG2. In order to facilitate the introduction of the technical solution provided in the first embodiment of the present application, the following takes the first communication device as the terminal device, the second communication device as the first network element, and the third communication device as the second network element as an example to introduce the process of implementing the communication method by data interaction between the first communication device, the second communication device, and the third communication device. As shown in FIG6, the method includes:

Step 601: A first network element obtains a second key from a second network element and stores the second key.

Optionally, the first network element may obtain the second key from the second network element, and save (or store) the obtained second key. Exemplarily, the second key may be a new key for encrypting the auxiliary data corresponding to the high-precision positioning service included in the first service. It should be understood that the second key may also be used to decrypt (or parse) the encrypted auxiliary data. For example, the second key may be a new/updated RTK key.

When the communication method illustrated in FIG6 is applicable to the communication system architecture illustrated in FIG1a or FIG1b, the second network element may be the LMF network element illustrated in FIG1a or FIG1b. When the communication method illustrated in FIG6 is applicable to the communication system architecture illustrated in FIG2, the second network element may be the E-SMLC illustrated in FIG2.

For example, the second network element may send the latest key (such as the second key) used to encrypt the auxiliary data corresponding to the high-precision positioning service to the first network element through a broadcast key data notification (Nlmf_Broadcast_CipheringKeyDataNotify) message.

After obtaining the second key, the first network element can determine which users need to push/send the second key according to whether the users have signed up for the first service. The first network element will push the second key only to users who have signed up for the first service. Afterwards, the first network element can select a corresponding push method to push the second key according to the connection management state of the terminal device used by the contracted user (such as the connection management connected state or the connection management idle state). For example, the second key pushed by the first network element can be one or more.

In one example, when the terminal device (such as the first terminal device) used by the subscriber is in the connection management connected state, the first network element performs the following step 602. In another example, when the terminal device (such as the first terminal device) used by the subscriber is in the connection management idle state, the first network element performs the following steps 603 and 605.

Step 602: If the first terminal device is in the connection management connection state, the first network element sends a sixth message to the first terminal device. The first terminal device receives the sixth message.

Optionally, the sixth message may be used to update NAS parameters or may be used to notify the first terminal device that the key has been updated. Exemplarily, the sixth message may carry the second key.

For example, when the communication method illustrated in FIG. 6 is applicable to the communication system architecture illustrated in FIG. 1a or FIG. 1b, the sixth message may be a NAS message. For example, the NAS message may be a configuration update message. For example, the configuration update message may be a configuration update command message or a configuration update complete message. When the communication method illustrated in FIG. 6 is applicable to the communication system architecture illustrated in FIG. 2, the sixth message may also be a NAS message. The NAS message may be a message such as updating a terminal device parameter configuration.

Step 603: If the first terminal device is in the connection management idle state, the first network element sends a paging message to the first terminal device. The end device receives the paging message.

Among them, the paging message is used to page the first terminal device to trigger the service request process, which helps to page the first terminal device from the connection management idle state back to the connection management connected state, so that the second key can be pushed to the first terminal device in a timely manner.

Step 604: The first terminal device sends a seventh message to the first network element according to the paging message. The first terminal device receives the seventh message.

Exemplarily, the seventh message may be used to activate a user plane session (such as a PDU session). For example, the seventh message may be a NAS message, such as a service request message.

After receiving the paging message, the first terminal device can start the service request process according to the paging message, for example, it can send the seventh message to the first network element to activate the corresponding PDU session.

Step 605: The first network element sends an eighth message to the first terminal device. The first terminal device receives the eighth message.

Exemplarily, the eighth message may carry the second key.For example, the eighth message may be a response message to the seventh message.

After the user plane session of the first terminal device is activated, the first terminal device may receive a corresponding service message (such as a NAS message) from the first network element through the user plane connection. Accordingly, after the user plane session of the first terminal device is activated, the first network element may send the second key to the first terminal device by sending a corresponding service response message (such as the eighth message) to the first terminal device. Exemplarily, the sixth message may be a NAS message, for example, a NAS message may be a service reception message (or may be referred to as a service acceptance message).

It can be seen from the above steps 601 to 605 that after obtaining the latest key (such as the second key), the first network element promptly pushes the second key to the terminal device associated with the user who has signed up for the first service (such as the high-precision positioning service). This enables the network side to promptly notify the relevant terminal devices after obtaining the latest key, so that the relevant terminal devices can use the latest key to successfully decrypt the encrypted auxiliary data, which helps to improve the positioning accuracy of the terminal devices.

Based on the technical solution of the communication method shown in FIG. 6 above, the following specific examples shown in FIG. 7 and FIG. 8 respectively introduce the implementation process of the communication method provided in the embodiment of the present application under the 5G communication system architecture and the 4G communication system architecture. In the specific example shown in FIG. 7, the terminal device is a UE, the (R) AN device is a gNB (or may be referred to as an NG-(R) AN device), the first key is an RTK key, the first network element is an AMF network element, the second network element is an LMF network element, and the auxiliary data is RTK positioning auxiliary data; in the specific example shown in FIG. 8, the terminal device is a UE, the (R) AN device is an eNB (or may be referred to as an eNodeB), the first key is an RTK key, the first network element is an MME, the second network element is an E-SMLC, and the auxiliary data is RTK positioning auxiliary data. It can be understood that in the embodiment of the present application, the action performed by a network element can also be replaced by the action performed by the functional component in the network element. In the embodiment of the present application, the functional component may, for example, include at least one of a chip, a chip system, a processor, and a processing unit.

FIG7 is a flow chart of another communication method provided in Embodiment 2 of the present application. The communication method shown in FIG7 is applicable to a 5G communication system architecture. As shown in FIG7 , the specific flow of the method may include:

Step 701: The LMF network element sends a broadcast key data notification message to the AMF network element. The AMF network element receives the broadcast key data notification message.

For example, the broadcast key data notification message may include the latest RTK key corresponding to the RTK positioning assistance data (or may be understood as the updated RTK key). The RTK key may be understood as the key of the assistance data or the key of the GNSS assistance data.

After receiving the broadcast key data notification message, the AMF network element obtains the latest RTK key from the broadcast key data notification message and stores (or saves) the latest RTK key.

Step 702: The AMF network element determines the target UE to which the latest RTK key needs to be pushed.

Among them, the target UE-associated user to which the latest RTK key needs to be pushed is the user who has signed up for the high-precision positioning service (hereinafter referred to as the "signed user").

For example, the AMF network element can determine which users have signed up for high-precision positioning services based on the bitmap of the location service (LCS)-broadcast assistance (BCA). After that, the AMF network element can promptly and accurately push the latest RTK key to the UEs corresponding to these users, so that the UEs corresponding to these users can promptly use the latest RTK key to successfully parse (or successfully decrypt) the encrypted RTK positioning assistance data broadcast by the base station, thereby effectively improving the UE positioning accuracy and effectively avoiding the problem that the encrypted RTK positioning assistance data cannot be successfully parsed due to the expiration of the RTK key of the UE corresponding to the contracted user, thereby causing inaccurate UE positioning accuracy.

Step 703: When it is determined that the target UE is in the connection management connection state, the AMF network element sends a NAS message to the target UE. The target UE receives the NAS message.

Exemplarily, the NAS message may be a configuration update message. For example, the configuration update message may be a configuration update command message or a configuration update complete message.

Optionally, the NAS message may carry the latest RTK key.

For example, for a first user whose UE is in a connection management (CM) connected state among the contracted users, the AMF network element may send a NAS message to the first user. The NAS message carries the latest RTK key. Exemplarily, the number of first users may be one or more, which is not limited in the embodiments of the present application.

Optionally, the NAS message may pass through one or more gNBs during the process of being sent by the AMF network element to the target UE. For example, taking one gNB as an example, the AMF network element may first send the NAS message to the gNB, and the gNB may send the NAS message to the target UE.

Step 704: When it is determined that the target UE is in the connection management idle state, the AMF network element sends a paging message to the target UE. The target UE receives the paging message.

The paging message is used to page the target UE, so as to page the target UE back from the CM idle state to the CM_connected state, thereby enabling the latest RTK key to be pushed to the target UE in a timely manner.

For example, for the second user whose UE is in CM_idle among the contracted users, the AMF network element needs to first send a paging message to the UE corresponding to the second user. After receiving the paging message, the UE corresponding to the second user initiates a service request process. Exemplarily, the number of second users can be one or more, and the embodiments of the present application do not limit this.

Optionally, the paging message may pass through one or more gNBs during the process of being sent by the AMF network element to the target UE. For example, taking one gNB as an example, the AMF network element may first send the paging message to the gNB, and the gNB may send the paging message to the target UE.

Step 705: The target UE sends a service request message to the AMF network element according to the paging message. The AMF network element receives the service request message.

For example, after receiving the paging message, the target UE can initiate a service request process according to the paging message. For example, the target UE can send a service request message to the AMF network element. Exemplarily, the service request message can be a NAS message.

Optionally, the service request message may pass through one or more gNBs during the process of being sent from the target UE to the AMF network element. For example, taking one gNB as an example, the target UE may first send the service request message to the gNB in its area, and the gNB may send the service request message to the AMF network element.

Step 706: The AMF network element sends a service reception message to the target UE. The target UE receives the service reception message.

Exemplarily, the service receive (or may be referred to as service accept) message may be a NAS message.

For example, after receiving the service request message, the AMF network element can push the latest RTK key to the target UE through the service reception message.

Optionally, the service reception message may pass through one or more gNBs during the process of being sent by the AMF network element to the target UE. For example, taking one gNB as an example, the AMF network element may first send the service reception message to the gNB, and the gNB may send the service reception message to the target UE.

It can be seen from the above steps 701 to 706 that for the 5GC communication scenario, after the LMF network element generates the latest RTK key (or updates the RTK key), it can push the latest RTK key (or updated RTK key) to the AMF network element. After that, the AMF network element can promptly push the latest RTK key (or updated RTK key) to the corresponding target UE (i.e., the UE used by the contracted user). In this way, the method can enable the network side to promptly notify the corresponding target UE after generating the latest RTK key (or updating the RTK key), so that the target UE can use the latest RTK key (or updated RTK key) to successfully parse the encrypted RTK positioning assistance data, thereby effectively improving the positioning accuracy of the UE, and effectively avoiding the problem that the target UE cannot parse the encrypted RTK positioning assistance data due to the expiration of the RTK key, resulting in inaccurate UE positioning accuracy.

FIG8 is a flow chart of another communication method provided in Embodiment 2 of the present application. The communication method shown in FIG8 is applicable to a 4G communication system architecture. As shown in FIG8 , the specific flow of the method may include:

Step 801: E-SMLC sends a broadcast key data notification message to MME. MME receives the broadcast key data notification message.

Optionally, the implementation of step 801 may refer to the implementation of step 701 described above, which will not be repeated here.

Step 802: The MME determines the target UE to which the latest RTK key needs to be pushed.

Optionally, the implementation of step 802 may refer to the implementation of step 702 described above, which will not be repeated here.

Step 803: When the target UE is in the connection management connected state, the MME sends a NAS message to the target UE. The target UE receives the NAS message.

Optionally, the implementation of step 803 may refer to the implementation of step 703 described above, which will not be repeated here.

In addition, since there is no configuration update process initiated by the network side in EPS, the NAS message may be a message (such as a configuration message) for updating UE parameter configuration in step 803. For example, the configuration message may be a configuration update command message (or a configuration update complete message).

Step 804: When the target UE is in the connection management idle state, the MME sends a paging message to the target UE. The target UE receives the paging message.

Optionally, the implementation of step 804 may refer to the implementation of step 704 described above, which will not be described in detail here.

Step 805: The target UE sends a service request message to the MME according to the paging message. The MME receives the service request message.

Optionally, the implementation of step 805 may refer to the implementation of step 705 described above, which will not be repeated here.

Step 806: The MME sends a service receiving message to the target UE. The target UE receives the service receiving message.

Optionally, the implementation of step 806 may refer to the implementation of step 706 described above, which will not be described in detail here.

It can be seen from the above steps 801 to 806 that for the EPC communication scenario, after the E-SMLC generates the latest RTK key (or updates the RTK key), it can push the latest RTK key (or the updated RTK key) to the MME. After that, the MME can promptly push the latest RTK key (or the updated RTK key) to the corresponding target UE (i.e., the UE used by the contracted user). In this way, the method can realize that after the network side generates the latest RTK key (or updates the RTK key), it can promptly notify the corresponding target UE, so that the target UE can use the latest RTK key (or the updated RTK key) to successfully parse the encrypted RTK positioning assistance data, thereby effectively improving the positioning accuracy of the UE, and effectively avoiding the problem that the target UE cannot parse the encrypted RTK positioning assistance data due to the expiration of the RTK key, resulting in inaccurate UE positioning accuracy.

It should be noted that in the description of the present application, "at least one" refers to one or more, and "multiple" refers to two or more. "And/or" describes the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which can represent: the situation where A exists alone, A and B exist at the same time, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the associated objects before and after are an "or" relationship. "At least one of the following (individuals)" or its similar expression refers to any combination of these items, including any combination of single items (individuals) or plural items (individuals). For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first", "second", and "third" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or importance of multiple objects. In addition, the terms "including", "comprising", "having" and their variations appearing in the present application all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

In addition, it should be noted that each step involved in the above embodiments can be performed by a corresponding device, or by a chip, processor, or chip system in the device, and the embodiments of the present application do not limit them. The above embodiments are only described by taking the corresponding device as an example.

It should be noted that in the above embodiments, some steps can be selected for implementation, and the order of the steps in the diagram can be adjusted for implementation, and this application does not limit this. It should be understood that executing some steps in the diagram, adjusting the order of the steps, or combining them for specific implementation all fall within the scope of protection of this application.

It is understandable that, in order to implement the functions in the above embodiments, the various devices involved in the above embodiments include hardware structures and/or software modules corresponding to the execution of the various functions. It should be easily appreciated by those skilled in the art that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

It should be understood that the "steps" in the embodiments of the present application are only for illustration, and are a method of expression used to better understand the embodiments, and do not constitute a substantial limitation on the execution of the scheme of the present application. For example, the "steps" can also be understood as "features". In addition, the steps do not constitute any limitation on the execution order of the scheme of the present application. Any changes in the order of steps, step merging, or step splitting made on this basis that do not affect the implementation of the overall scheme, and the resulting new technical solutions are also within the scope of the disclosure of the present application.

Based on the same concept, the embodiment of the present application also provides a possible communication device, which is applicable to the communication system architecture shown in Figure 1a or Figure 1b or Figure 2. Optionally, the communication device can be a communication device (such as a terminal device (such as a first terminal device or other terminal device), a first network element or a second network element) or a device that can support the communication device to implement the functions required by the communication method. In an example, when the communication device is a terminal device (or a first terminal device) (such as a UE), the communication device is used to implement the technical solutions involved in the terminal device (or the first terminal device) in the above embodiment, or the module (such as a chip) of the communication device is used to implement the technical solutions involved in the terminal device (or the first terminal device) in the above embodiment, so the beneficial effects possessed by the terminal device (or the first terminal device) in the above embodiment can also be achieved. Exemplarily, when the communication device is a chip set in the terminal device (or the first terminal device), the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to implement the transceiver of the communication device (or the first terminal device). The input/output interface may include an input interface and/or an output interface. The input interface may implement the reception of the terminal device (or the first terminal device), and the output interface may be used to implement the transmission of the terminal device (or the first terminal device). The processor is used to read and execute the corresponding computer program or instruction so that the corresponding function of the terminal device (or the first terminal device) is implemented. Optionally, when the chip implements the corresponding function of the terminal device (or the first terminal device) in the above embodiment, the input/output interface The port can implement the transceiver operation performed by the terminal device (or the first terminal device) in the above embodiment; the processor can implement other operations except the transceiver operation performed by the terminal device (or the first terminal device) in the above embodiment. For specific related descriptions, please refer to the related descriptions of the terminal device (or the first terminal device) in the above embodiment, which will not be described in detail here.

In another example, when the communication device is a first network element (such as an AMF network element or an MME), the communication device is used to implement the technical solution involved in the first network element in the above embodiment, or the module (such as a chip) of the communication device is used to implement the technical solution involved in the first network element in the above embodiment, so the beneficial effects of the first network element in the above embodiment can also be achieved. Exemplarily, when the communication device is a chip set in the first network element, the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to implement the transceiver of the communication device. The input and output interface may include an input interface and/or an output interface, the input interface can implement the reception of the first network element, and the output interface can be used to implement the transmission of the first network element. The processor is used to read and execute the corresponding computer program or instruction so that the corresponding function of the first network element is implemented. Optionally, when the chip implements the corresponding function of the first network element in the above embodiment, the input and output interface can implement the transceiver operation performed by the first network element in the above embodiment; the processor can implement other operations except the transceiver operation performed by the first network element in the above embodiment. For specific related descriptions, please refer to the related descriptions of the first network element in the above embodiment, which will not be described in detail here.

In another example, when the communication device is a second network element (such as an LMF network element or an E-SMLC), the communication device is used to implement the technical solution involved in the second network element in the above embodiment, or the module (such as a chip) of the communication device is used to implement the technical solution involved in the second network element in the above embodiment, so the beneficial effects of the second network element in the above embodiment can also be achieved. Exemplarily, when the communication device is a chip set in the second network element, the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to implement the transceiver of the communication device. The input and output interface may include an input interface and/or an output interface, the input interface can implement the reception of the second network element, and the output interface can be used to implement the transmission of the second network element. The processor is used to read and execute the corresponding computer program or instruction so that the corresponding function of the second network element is implemented. Optionally, when the chip implements the corresponding function of the second network element in the above embodiment, the input and output interface can implement the transceiver operation performed by the second network element in the above embodiment; the processor can implement other operations except the transceiver operation performed by the second network element in the above embodiment. For specific related descriptions, please refer to the related descriptions of the second network element in the above embodiment, which will not be described in detail here.

9, the communication device 900 includes a communication module 901 (or may be referred to as a transceiver module, for sending and receiving data) and a processing module 902. The communication device 900 is used to implement the functions of the first communication device (such as a terminal device) or the second communication device (such as a first network element) or the third communication device (such as a second network element) in the method embodiments shown in the above-mentioned FIGS. 3 to 8.

Optionally, the communication module 901 may include a receiving module and/or a sending module. The receiving module may be used for the communication device 900 to receive signals (information or data, etc.); the sending module may be used for the communication device 900 to send signals (information or data, etc.). The sending module may send signals (information or data, etc.) under the control of the processing module 902, and the receiving module may receive signals (information or data, etc.) under the control of the processing module 902.

When the communication device 900 is used to implement the functions of the terminal device in the method embodiments shown in Figures 3 to 5 above: the communication module 901 is used to send a first message to the first network element. The first information is used to request a first key, and the first key is used to encrypt auxiliary data. The communication module 901 is also used to receive a first message from the first network element. The first message includes first indication information, and the first indication information is used to indicate that the first key does not exist or is not available. The processing module 902 is used to send a second message to the first network element, or wait for the first network element to send a first key if the first time or timer or timer expires. The second information is used to request the first key.

When the communication device 900 is used to implement the function of the first network element in the method embodiment shown in Figures 3 to 5 above: the communication module 901 is used to receive the first information from the terminal device. The first information is used to request the first key, and the first key is used to encrypt auxiliary data. The processing module 902 is used to send a first message to the terminal device if the first key does not exist or is not available. The first message includes first indication information, and the first indication information is used to indicate that the first key does not exist or is not available. The communication module 901 is also used to receive the second information from the terminal device, or if the first key is obtained, send the first key to the terminal device. The second information is used to request the first key.

When the communication device 900 is used to implement the function of the second network element in the method embodiments shown in Figures 3 to 5 above: the communication module 901 is used to receive a second message from the first network element. The second message is used to request the first key. The processing module 902 is used to send a third message to the first network element if the first key does not exist or is not available locally. The third message includes fourth indication information, and the fourth indication information is used to indicate that the first key does not exist or is not available.

When the communication device 900 is used to implement the function of the first network element in the method embodiment shown in Figures 6 to 8 above: the communication module 901 is used for the first terminal device to be in the connection management connection state, and send the sixth message to the first terminal device. The sixth message is used to update the NAS parameters or to notify the first terminal device that the key has been updated; the sixth message includes the second key; the first terminal device is associated with the user who signed the first The user of the service, the first service includes a high-precision positioning service; the second key is a new key for encrypting the auxiliary data corresponding to the high-precision positioning service. The communication module 901 is also used to send a paging message to the first terminal device if the first terminal device is in a connection management idle state. The paging message is used to page the first terminal device. The communication module 901 is also used to receive the seventh message from the first terminal device. The seventh message is used to activate the user plane session. The communication module 901 is also used to send an eighth message to the first terminal device. The eighth message includes the second key. Optionally, the processing module 902 is used to save (or store) the second key. The processing module 902 is also used to determine the signed user to whom the second key needs to be pushed.

When the communication device 900 is used to implement the function of the first terminal device in the method embodiment shown in Figures 6 to 8 above: the communication module 901 is used to receive the sixth message from the first network element if the first terminal device is in the connection management connection state. The sixth message is used to update the NAS parameters or to notify the first terminal device that the key has been updated; the sixth message includes the second key; the user associated with the first terminal device is a user who has signed a contract for the first service, and the first service includes a high-precision positioning service; the second key is a new key for encrypting the auxiliary data corresponding to the high-precision positioning service. The communication module 901 is also used to receive a paging message from the first network element if the first terminal device is in the connection management idle state. The paging message is used to page the first terminal device. The communication module 901 is also used to send a seventh message to the first network element. The seventh message is used to activate the user plane session. The communication module 901 is also used to receive an eighth message from the first network element. The eighth message includes the second key.

When the communication device 900 is used to implement the function of the second network element in the method embodiments shown in Figures 6 to 8 above: the communication module 901 is used to send a broadcast key data notification message to the first network element, wherein the broadcast key data notification message includes the second key.

Among them, when the communication device 900 is used to implement the function of the first communication device or the second communication device or the third communication device in the method embodiments shown in Figures 3 to 8, for a more detailed description of the communication module 901 and the processing module 902, refer to the relevant description of the first communication device or the second communication device or the third communication device in the method embodiments shown in Figures 3 to 8 above, and will not be repeated here.

It should be understood that the communication module 901 in the embodiment of the present application can be implemented by a transceiver or a transceiver-related circuit component, and the processing module 902 can be implemented by a processor or a processor-related circuit component.

It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, or a server, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program codes.

Based on the same concept, the embodiment of the present application also provides a possible communication device, which is applicable to the communication system architecture shown in Figure 1a or Figure 1b or Figure 2. Exemplarily, the communication device may be a device (such as a first communication device or a second communication device or a third communication device) required for executing the communication method provided in the embodiment of the present application, or may be a device including a device required for executing the communication method provided in the embodiment of the present application. Optionally, the communication device may also be arranged in a chip in the first communication device (or the second communication device or the third communication device). When the communication device is a chip arranged in the first communication device (or the second communication device or the third communication device), the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to realize the transceiver of the communication device. The input and output interface may include an input interface and/or an output interface, and the input interface can realize the reception of the communication device, and the output interface can be used to realize the sending of the communication device. The processor is used to read and execute corresponding computer programs or instructions so that the corresponding functions of the first communication device (or the second communication device or the third communication device) are realized. Optionally, when the chip implements the corresponding functions of the first communication device (or the second communication device or the third communication device) in the above embodiment, the input and output interface can implement the transceiver operation performed by the first communication device (or the second communication device or the third communication device) in the above embodiment; the processor can implement other operations except the transceiver operation performed by the first communication device (or the second communication device or the third communication device) in the above embodiment. For specific related descriptions, please refer to the relevant descriptions in the above embodiments, which will not be described in detail here. By way of example, it is taken that the communication device is a first communication device (such as a terminal device or a first terminal device) or a second communication device (such as a first network element) or a third communication device (such as a second network element). When the communication device is used to implement the technical solutions involved in the first communication device in the above embodiment, the beneficial effects possessed by the first communication device in the above method embodiment can also be achieved. When the communication device is used to implement the above implementation The technical solution involved in the second communication device in the embodiment can also achieve the beneficial effects of the second communication device in the above method embodiment. When the communication device is used to implement the technical solution involved in the third communication device in the above embodiment, the beneficial effects of the third communication device in the above method embodiment can also be achieved.

Referring to FIG. 10 , the communication device 1000 includes: a transceiver 1001 and a processor 1002. Optionally, the communication device 1000 further includes a memory 1003. The transceiver 1001, the processor 1002 and the memory 1003 are interconnected. When the communication device 1000 is used to implement the technical solution involved in the first communication device provided in the above embodiment, the transceiver 1001 can be used to implement the function of the above communication module 901 when executing the technical solution involved in the first communication device, and the processor 1002 is used to implement the function of the above processing module 902 when executing the technical solution involved in the first communication device. When the communication device 1000 is used to implement the technical solution involved in the second communication device provided in the above embodiment, the transceiver 1001 can be used to implement the function of the above communication module 901 when executing the technical solution involved in the second communication device, and the processor 1002 is used to implement the function of the above processing module 902 when executing the technical solution involved in the second communication device. When the communication device 1000 is used to implement the technical solution involved in the third communication device provided in the above embodiment, the transceiver 1001 can be used to implement the function of the above communication module 901 when executing the technical solution involved in the third communication device, and the processor 1002 is used to implement the function of the above processing module 902 when executing the technical solution involved in the third communication device.

Optionally, the transceiver 1001, the processor 1002 and the memory 1003 are interconnected via a bus 1004. The bus 1004 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG10 is represented by only one thick line, but it does not mean that there is only one bus or one type of bus.

The transceiver 1001 is used to receive and send data. For example, when the communication device 1000 is a UE as shown in FIG. 1a, FIG. 1b or FIG. 2, the transceiver 1001 implements communication with the RAN device as shown in FIG. 1a, FIG. 1b or FIG. 2, or can also implement communication with other devices (such as vehicle-mounted devices or servers) outside the communication system architecture shown in FIG. 1a, FIG. 1b or FIG. 2. In one example, the transceiver can be a transceiver device with integrated data transceiver function. In another example, the transceiver can also be composed of a transmitter and a receiver, wherein the transmitter is used to send data and the receiver is used to receive data.

Optionally, the transceiver 1001 may include a transmitter and/or a receiver. The transmitter is used to send signals, messages, information, or data, etc. The receiver is used to receive signals, messages, information, or data, etc. Exemplarily, the transmitter sends signals, messages, information, or data, etc. under the control of the processor 1002. The receiver receives signals, messages, information, or data, etc. under the control of the processor 1002.

The functions of the processor 1002 can refer to the description of the corresponding functions involved in the first communication device or the second communication device or the third communication device in the above embodiments, and will not be repeated here. Among them, the processor 1002 can be a central processing unit (CPU), a network processor (NP) or a combination of CPU and NP, etc. The processor 1002 can further include a hardware chip. The above-mentioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. When the processor 1002 implements the above-mentioned functions, it can be implemented by hardware, and of course, it can also be implemented by executing the corresponding software through hardware.

The memory 1003 is used to store program instructions, etc. Specifically, the program instructions may include program codes, and the program codes include computer operation instructions. The memory 1003 may include random access memory (RAM), and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 1002 executes the program instructions stored in the memory 1003 to implement the above functions, thereby implementing the method steps required to be executed by the first communication device, the second communication device, or the third communication device in the above embodiments.

Based on the same concept, the embodiment of the present application also provides a possible communication system, which includes a first communication device (such as a terminal device or a first terminal device), a second communication device (such as a first network element) and a third communication device (such as a second network element). Among them, the first communication device can be used to implement the technical solution involved in the first communication device in the above embodiment, the second communication device can be used to implement the technical solution involved in the second communication device in the above embodiment, and the third communication device can be used to implement the technical solution involved in the third communication device in the above embodiment.

Based on the same concept, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed on a computer, the computer executes the method provided in the above embodiment.

Based on the same concept, an embodiment of the present application also provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, the computer executes the method provided in the above embodiment.

The storage medium may be any available medium that can be accessed by a computer. For example, but not limited to, a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.

Based on the same concept, an embodiment of the present application further provides a chip, which is coupled to a memory and is used to read a computer program stored in the memory to implement the method provided in the above embodiment.

Based on the same concept, an embodiment of the present application also provides a chip system, which includes a processor for supporting a computer device to implement the functions involved in the first communication device (such as a terminal device) or the second communication device (such as a first network element) or the third communication device (such as a second network element) in the above embodiments. In one possible design, the chip system also includes a memory, which is used to store the necessary programs and data for the computer device. The chip system can be composed of chips, or it can include chips and other discrete devices.

In the method provided in the embodiment of the present application, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

The steps of the method described in the embodiments of the present application can be directly embedded in the hardware, the software unit executed by the processor, or the combination of the two. The software unit can be stored in RAM, ROM, EEPROM, register, hard disk, removable disk, CD-ROM or other storage media of any form in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and the storage medium can be arranged in an ASIC.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these 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 also intended to include these modifications and variations.

Claims (24)

A communication method, characterized in that it is applied to a terminal device, the method comprising: Sending first information to a first network element, where the first information is used to request a first key, where the first key is used to encrypt auxiliary data; receiving a first message from the first network element, where the first message includes first indication information, where the first indication information is used to indicate that the first key does not exist or is unavailable; When a first time or a timer or a timer expires, second information is sent to the first network element, where the second information is used to request the first key; or Wait for the first network element to send the first key. The method according to claim 1, wherein sending the first information to the first network element comprises: The auxiliary data is converted from being received through the user plane of the terminal device to being received through the control plane, and the first information is sent to the first network element. The control plane reception includes receiving a system message sent through an access network device. The method as claimed in claim 1 or 2 is characterized in that the first message also includes second indication information, and the second indication information is used to indicate the first time or the timer or the timer, and the first time or the timer or the timer is used to indicate the next request time of the first key, or to indicate the sending time of the next request information of the first key, or to indicate the start time of the next request information of the first key. The method as claimed in claim 1 or 2 is characterized in that the first message also includes third indication information, and the third indication information is used to instruct the terminal device to wait for the first network element to send the first key. The method according to claim 2, wherein the auxiliary data is converted from being received through a user plane of the terminal device to being received through a control plane, comprising: Receiving a system message sent by the access network device to determine that the auxiliary data is converted from being received from the user plane of the terminal device to being received through the control plane; or Failure to receive the system message sent by the access network device determines that the auxiliary data is converted from being received through the control plane to being received through the user plane of the terminal device. A communication method, characterized in that it is applied to a first network element, and the method comprises: receiving first information from a terminal device, wherein the first information is used to request a first key, and the first key is used to encrypt auxiliary data; The first key does not exist or is unavailable, sending a first message to the terminal device, where the first message includes first indication information, and the first indication information is used to indicate that the first key does not exist or is unavailable; receiving second information from the terminal device, where the second information is used to request the first key; or If the first key is obtained, the first key is sent to the terminal device. The method according to claim 6, wherein the first key does not exist or is unavailable, comprising: the first key is not stored; or The first key is not stored, and a second message is sent to a second network element, where the second message is used to request the first key; a third message is received from the second network element, where the third message includes fourth indication information, and the fourth indication information is used to indicate that the first key does not exist or is unavailable. The method according to claim 6, wherein obtaining the first key comprises: A fifth message is received from the second network element, where the fifth message includes the first key. The method as claimed in claim 6 or 7 is characterized in that the first message also includes second indication information, and the second indication information is used to indicate a first time or a timer or a timer, and the first time or the timer or the timer is used to indicate the next request time of the first key, or to indicate the sending time of the next request information of the first key, or to indicate the start time of the next request information of the first key. The method as claimed in claim 6 or 7 is characterized in that the first message also includes third indication information, and the third indication information is used to instruct the terminal device to wait for the first network element to send the first key. A communication method, characterized in that it is applied to a second network element, the method comprising: receiving a second message from a first network element, where the second message is used to request the first key; A third message is sent to the first network element, where the third message includes fourth indication information, and the fourth indication information is used to indicate that the first key does not exist or is unavailable. The method according to claim 11, characterized in that the method further comprises: A fifth message is sent to the first network element, where the fifth message includes the first key. A communication method, characterized in that it is applied to a first network element, and the method comprises: The first terminal device is in a connection management connection state, and sends a sixth message to the first terminal device, where the sixth message is used to update a non-access layer NAS parameter or to notify the first terminal device that a key has been updated, and the sixth message includes a second key; or The first terminal device is in a connection management idle state, sending a paging message to the first terminal device, where the paging message is used to page the first terminal device; receiving a seventh message from the first terminal device, sending an eighth message to the first terminal device, where the seventh message is used to activate a user plane session, and the eighth message includes a second key; The user associated with the first terminal device is a user who has signed up for a first service, and the first service includes a high-precision positioning service; the second key is a new key for encrypting auxiliary data corresponding to the high-precision positioning service. The method as claimed in claim 13 is characterized in that the sixth message or the seventh message or the eighth message is a non-access layer NAS message. The method as claimed in claim 14 is characterized in that the sixth message is a configuration update message; the seventh message is a service request message; and the eighth message is a service reception message. A communication method, characterized in that it is applied to a first terminal device, and the method comprises: The first terminal device is in a connection management connection state, and receives a sixth message from the first network element, where the sixth message is used to update a non-access layer NAS parameter or to notify the first terminal device that a key has been updated, and the sixth message includes a second key; or The first terminal device is in a connection management idle state, and receives a paging message from the first network element, where the paging message is used to page the first terminal device; sends a seventh message to the first network element, and receives an eighth message from the first network element, where the seventh message is used to activate a user plane session, and the eighth message includes a second key; The user associated with the first terminal device is a user who has signed up for a first service, and the first service includes a high-precision positioning service; the second key is a new key for encrypting auxiliary data corresponding to the high-precision positioning service. The method as claimed in claim 16 is characterized in that the sixth message or the seventh message or the eighth message is a non-access layer NAS message. The method as claimed in claim 17 is characterized in that the sixth message is a configuration update message; the seventh message is a service request message; and the eighth message is a service reception message. A communication device, characterized in that it includes a module or unit for executing the method as described in any one of claims 1 to 5, or includes a module or unit for executing the method as described in any one of claims 6 to 10, or includes a module or unit for executing the method as described in any one of claims 11 to 12, or includes a module or unit for executing the method as described in any one of claims 13 to 15, or includes a module or unit for executing the method as described in any one of claims 16 to 18. A communication device, comprising: transceiver, used to receive and send data; Memory for storing computer program instructions and data; A processor, configured to execute and call computer program instructions and data in the memory so that the communication device performs the method as described in any one of claims 1-5, or the method as described in any one of claims 6-10, or the method as described in any one of claims 11-12, or the method as described in any one of claims 13-15, or the method as described in any one of claims 16-18. A communication system, characterized in that it includes a terminal device for executing the method as described in any one of claims 1-5, a first network element for executing the method as described in any one of claims 6-10 or the method as described in any one of claims 13-15, a second network element for executing the method as described in any one of claims 11-12, and a first terminal device for executing the method as described in any one of claims 16-18. A computer-readable storage medium, characterized in that a computer program or instruction is stored in the computer-readable storage medium, and when the computer program or instruction is executed by a computer, the computer executes the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 10, or the method as described in any one of claims 11 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 18. A computer program product, characterized in that the computer program product comprises a computer program or instructions, which, when executed on a computer, causes the computer to execute the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 10, or the method as described in any one of claims 11 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 18. A chip, characterized in that the chip includes a processor, and the chip is used to execute program instructions in a storage to perform the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 10, or the method as described in any one of claims 11 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 18.