Communication method and device

Abstract

The present application relates to a communication method and a device. The method comprises: receiving first information, wherein the first information is used for determining a mode of obtaining, on the basis of a shared key, a sequence generation parameter corresponding to a downlink sensing signal, and the shared key is shared by a first device and a second device.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] In related technologies, 3GPP has initiated research on converged perception communication services. These perception services, provided by this integrated scenario, can track and potentially identify any target (perception target) in the environment by transmitting perception signals via terminals and / or base stations, and measuring the echo signals of these perception signals via the perception terminals and / or access network equipment. However, in these perception scenarios, ensuring the security of the perception signals themselves, and thus the security of the entire perception scenario, has become a challenge.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method and device.

[0005] An embodiment of the present application provides a communication method performed by a first device, including:

[0006] Receive first information, where the first information is used to determine a method for obtaining a sequence generation parameter corresponding to a downlink perception signal based on a shared key, where the shared key is shared by the first device and the second device.

[0007] An embodiment of the present application provides a first device, including:

[0008] A communication unit is configured to receive first information, wherein the first information is used to determine a method for obtaining a sequence generation parameter corresponding to a downlink perception signal based on a shared key, where the shared key is shared by the first device and the second device.

[0009] By adopting the above solution, first information can be configured for the first device. This first information enables the first device to determine how to generate sequence generation parameters for the downlink perception signal using a key shared by the first and second devices. This allows the parameter range of the sequence generation parameters for the downlink perception signal to be changed. Furthermore, only the first and second devices can access the specific contents of the sequence generation parameters; other devices cannot obtain these parameters. Furthermore, only the receiving end in the first and second devices can correctly receive and measure the downlink perception signal generated based on the sequence generation parameters, thereby improving the security of the downlink perception signal itself and ensuring the security of the perception scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0011] FIG2 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0012] FIG3 is a schematic diagram of a modulation scenario according to an embodiment of the present application.

[0013] FIG4 is a schematic flowchart of a communication method in which the first device is a UE according to an embodiment of the present application.

[0014] FIG5 is a schematic flowchart of a communication method in which the first device is a base station according to an embodiment of the present application.

[0015] FIG6 is another schematic flowchart of a communication method in which the first device is a UE according to an embodiment of the present application.

[0016] FIG7 is another schematic flowchart of a communication method in which the first device is a base station according to an embodiment of the present application.

[0017] FIG8 is a schematic block diagram of a first device according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as LTE, LTE-A, NR, NR evolution, WLAN, WiFi, or other communication systems.

[0019] The embodiments of the present application describe various embodiments in conjunction with network devices and terminals. The terminals can be mobile or fixed, and can also be referred to as mobile stations, user units, etc. The terminal can be a site in a WLAN, and can be a smart terminal, wireless modem, laptop computer, tablet computer, or other terminal. In the embodiments of the present application, the terminal can be a VR terminal / AR terminal, an industrial control terminal, an unmanned driving terminal, a telemedicine terminal, a smart grid terminal, a transportation safety terminal, a smart city terminal, or a wireless terminal for a smart home, etc. As an example and not a limitation, in the embodiments of the present application, the terminal can also be a wearable device.

[0020] In the embodiment of the present application, the network device may be a device for communicating with a terminal, an access point in a WLAN, an evolved base station in LTE, or a relay station, or a network device (gNB) in an in-vehicle device, a wearable device, and an NR network, or a network device in a future evolved PLMN network or a network device in a non-terrestrial network. As an example and not a limitation, in the embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device.

[0021] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0022] Figure 1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminals 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminals 120 within its coverage area, although this embodiment of the present application does not limit this. In one possible implementation, the communication system 100 may also include a mobility management entity, access and mobility management functions, and other network entities, although this embodiment of the present application does not limit this. The network devices may include access network devices and core network devices. That is, the communication system may also include multiple core networks for communicating with the access network devices. The access network devices may be base stations of LTE, LTE-A, or NR systems. Taking the communication system shown in Figure 1 as an example, the communication devices may include network devices and terminals with communication functions. The communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities, although this embodiment of the present application does not limit this.

[0023] Figure 2 is a schematic flow chart of a communication method performed by a first device according to an embodiment of the present application. The method includes at least part of the following contents.

[0024] S210. Receive first information, where the first information is used to determine a method for obtaining a sequence generation parameter corresponding to a downlink perception signal based on a shared key, where the shared key is shared by the first device and the second device.

[0025] Optionally, the first device is an access network device that sends the downlink perception signal, and the second device is a terminal that receives an echo signal of the downlink perception signal.

[0026] Optionally, the first device is a terminal that receives an echo signal of the downlink perception signal, and the second device is an access network device that sends the downlink perception signal.

[0027] The access network equipment may include at least one of the following: a base station, a gNB, an eNB, a network device in a future evolved PLMN network, a network device in an NTN network, a satellite, and the like.

[0028] The downlink sensing signal may also be referred to as a downlink sensing reference signal, or as any one of the sensing reference signals. For example, the downlink sensing reference signal may be a PRS (Positioning Reference Signal), a DM-RS (Demodulation Reference Signal), a CSI-RS (Channel State Information Reference Signal), and the like. The specific types of all possible downlink sensing reference signals are not limited or exhaustive here.

[0029] The echo signal of the downlink sensing signal may refer to a signal resulting from the downlink sensing signal being reflected by a sensing target. In some possible examples, the echo signal of the downlink sensing signal may also be referred to as a reflected signal of the downlink sensing signal, or simply as an echo signal, or simply as a reflected signal. This does not limit or exhaustively list all possible names for the echo signal of the downlink sensing signal. In some possible examples, the sensing target may also be simply referred to as a target.

[0030] The shared key may also be alternatively called a perception key, a key for calculating generation parameters of a perception signal, a key for calculating parameters, etc. Possible names of the shared key are not limited or exhaustive here.

[0031] The sequence generation parameter corresponding to the downlink perception signal may include a downlink PRS sequence ID (dl-PRS-SequenceID), or simply referred to as a sequence ID (Sequence ID), which may be expressed as

[0032] In some possible implementations, when the first device is a terminal and the second device is an access network device, the terminal receiving the first information may refer to receiving the first information from a sensing function (SF). When the first device is an access network device and the second device is a terminal, the access network device receiving the first information may refer to receiving the first information from the SF.

[0033] The first information may also be referred to as one of the following: perception assistance data, perception-related data, perception-related assistance data, perception configuration data, perception-related configuration information, etc. The perception function may also be referred to as a perception server.

[0034] It should be understood that although this embodiment primarily describes the first device obtaining the first information, in a downlink sensing scenario, the first device and the second device, which are both transceivers, i.e., the terminal and the access network device, will receive the same first information. In other words, the second device will also perform the processing of receiving the first information. Therefore, in the following description of this embodiment, the first device and the second device are no longer distinguished, and the description will be based on the transceiver and the terminal and the access network device in the downlink sensing scenario.

[0035] In one embodiment, the terminal receiving the first information from the SF may be one of the following: the terminal directly receiving the first information from the SF; the terminal receiving the first information from the SF through a core network device; the terminal receiving the first information from the SF through an access network device.

[0036] Exemplarily, the terminal may not send the first request message before receiving the first information. In this case, the terminal may directly receive the first information.

[0037] For example, the first information can be sent directly to the terminal by the access network device. For example, the access network device sends a second request message to the SF (or to the SF through the core network device), and the second request message can be used to request the first information, that is, the second request message is also used to request the relevant auxiliary data required for subsequent transmission or generation of downlink perception signals. After the access network device receives the first information sent by the SF (or receives the SF through the core network device), the first information is saved locally and sent directly to the terminal. In this case, the first information sent by the access network device to the terminal can be carried by any downlink AS message.

[0038] For example, the SF and / or the core network device may send the first information to the terminal (or the SF sends the first information to the terminal via the core network device). This embodiment does not limit the reason why the SF triggers sending the first information to the terminal.

[0039] On the terminal side, the first information can be used by the terminal to obtain sequence generation parameters for the downlink perception signal, and then calculate the perception sequence based on the sequence generation parameters, and demodulate the echo signal of the downlink perception signal based on the perception sequence. In other words, the first information is used to enable the terminal to obtain relevant auxiliary data required for the subsequent demodulation of the echo signal of the downlink perception signal; the relevant auxiliary data may include at least one of the following: auxiliary data related to the echo signal of the demodulated downlink perception signal, auxiliary data related to the generation of the downlink perception signal, auxiliary data related to the transmission of the downlink perception signal, etc. The relevant auxiliary data can be expressed as NR-DL-PRS-AssistanceData (NR downlink PRS assistance data).

[0040] Exemplarily, before receiving the first information, the terminal may further include: sending a first request message, where the first request message may be used to request obtaining the first information, that is, to request obtaining relevant auxiliary data required for subsequent transmission or generation of a downlink perception signal.

[0041] The sending of the first request message may include one of the following: the terminal directly sends the first request message to the SF; the terminal sends the first request message to the SF through the core network device; the terminal sends the first request message to the access network device.

[0042] Optionally, in a case where the terminal directly sends the first request message to the SF, the terminal may directly receive the first information from the SF.

[0043] Optionally, when the terminal sends a first request message to the SF through the core network device, the terminal can receive the first information from the SF through the core network device. In this case, the first request message can be carried by any NAS (Non-Access Network) message (uplink NAS message); the first information can be carried by any NAS message (downlink NAS message).

[0044] Optionally, when the terminal sends a first request message to the access network device, the access network device may forward the first request message to the SF. Accordingly, the access network device receives the first information from the SF and sends the first information to the terminal. Alternatively, the access network device forwards the first request message to the SF via the core network device. Accordingly, the access network device receives the first information from the SF via the core network device and sends the first information to the terminal.

[0045] In this case, the first request message sent by the terminal to the access network device can be carried by any uplink AS (access layer) message; the first information sent by the access network device to the terminal can be carried by any downlink AS message.

[0046] In one embodiment, the access network device receives the first information from the SF in one of the following ways: the access network device directly receives the first information from the SF; the access network device receives the first information from the SF through the core network device.

[0047] Exemplarily, before the access network device receives the first information from the SF, the access network device may perform the following processing: sending a second request message to the SF, where the second request message may be used to request the first information, that is, the second request message is also used to request the relevant auxiliary data required for subsequent transmission or generation of a downlink perception signal.

[0048] The access network device sending the second request message may include one of the following: the access network device directly sending the second request message to the SF; the access network device sending the second request message to the SF through the core network device.

[0049] In this case, if the access network device and the terminal separately request the first information from the SF, the access network device will store the first information locally after receiving it and perform subsequent processing without sending it to the terminal. If the access network device independently requests the first information from the SF, the access network device will store the first information locally after receiving it and send it to the terminal.

[0050] Optionally, before the access network device receives the first information from the SF, the access network device may perform the following processing: receiving a first request message from the first device (terminal), forwarding the first request message to the SF, or forwarding the first request message to the SF through the core network device. Accordingly, the access network device receives the first information from the SF, stores the first information locally, and sends the first information to the terminal; or, the second device receives the first information from the SF through the core network device, stores the first information locally, and sends the first information to the terminal. In this case, the first request message sent by the terminal to the access network device can be carried by any uplink AS message; the first information sent by the access network device to the terminal can be carried by any downlink AS message.

[0051] Exemplarily, the access network device may not send the second request message before receiving the first information. In this case, the access network device can directly receive the first information from the SF (or receive the first information from the SF through the core network device). This embodiment does not limit the reason why the SF side triggers the sending of the first information to the access network device.

[0052] On the access network device side, the first information can be used by the access network device to obtain sequence generation parameters for the downlink perception signal, further calculate the perception sequence based on the sequence generation parameters, and generate and transmit the downlink perception signal based on the perception sequence. In other words, the first information is used by the access network device to obtain relevant auxiliary data required for the subsequent generation or transmission of an echo signal for the downlink perception signal. This relevant auxiliary data may include at least one of the following: auxiliary data related to the generation of the downlink perception signal, auxiliary data related to the transmission of the downlink perception signal, auxiliary data related to the demodulation of the echo signal of the downlink perception signal, and so on.

[0053] In some possible implementations, the shared key is one of the following: a first key shared by the first device and the second device, wherein the first key includes one of the following: an access layer key, an access layer security base key, a next hop key (NH), a physical layer key; calculated based on the first key.

[0054] The access layer key may include at least one of the following: UP (User Plane) integrity protection (or verification) key KUpint , UP confidentiality key K UPenc , control plane integrity protection (or verification) key K RRCint , control plane confidentiality key K RRCenc This embodiment does not limit the derivation method of each access layer key.

[0055] The access layer (AS) security base key can be K gNB . Exemplarily, where K gNB It can be the initial K specified in the relevant protocol. gNB , or K NG-RAN Here, K NG-RAN It can also be expressed alternatively as K NG-RAN *, or, alternatively, the non-initial key K gNB This embodiment does not limit the derivation method of the access layer security basic key.

[0056] The physical layer key may be generated based on characteristics of the physical layer channel between the first device and the second device. This embodiment does not limit the specific method of generating the physical layer key. Exemplarily, the physical layer key may be represented as Kphy.

[0057] It should be understood that the above is only an exemplary description of the first key. In actual processing, the first key may also be a key generated or shared in other ways. All key types that may be used as the first key are not limited or enumerated here.

[0058] Optionally, the first key used by the first device and the second device may be a default key between the two parties or a key specified in an agreement. NG-RAN as the first key.

[0059] Optionally, the first device may determine the first key. The processing of the first device may further include: the first device sending an identifier of the first key to the second device. The processing of the second device may further include: receiving the identifier of the first key from the first device; and determining the first key based on the identifier of the first key. For example, the identifier of the first key may be K Upint The identification of K Upint as the first key.

[0060] Optionally, the second device may determine the first key. The processing by the second device may further include: sending an identifier of the first key to the first device. The processing by the first device may further include: receiving the identifier of the first key from the second device, and determining the first key based on the identifier of the first key.

[0061] In one embodiment, the first device and the second device directly use the first key as a shared key.

[0062] In one embodiment, the shared key is calculated based on the first key. In this embodiment, the shared key is calculated by the first device and the second device respectively.

[0063] It should be noted that the timing when the first device and the second device calculate the shared key is within the protection scope of this embodiment as long as it is before the sequence generation parameter corresponding to the downlink perception signal is obtained based on the shared key. The following description no longer limits the processing timing for calculating the shared key and / or the processing timing when the first device and the second device obtain the relevant parameters for calculating the shared key.

[0064] In this embodiment, the first device and the second device both calculate the shared key based on the first key. The first device and the second device calculate the shared key in the same way, use the same parameters, and the shared key ultimately obtained is theoretically the same. Therefore, the relevant instructions for calculating the shared key based on the first key involved below can be applied to the first device and the second device, and the processing performed by different devices will no longer be distinguished below.

[0065] The key algorithm used to calculate the shared key may be a default one or a protocol-specified one. For example, the key algorithm may include at least one of the following: a key derivation function (KDF), a first authentication function, a second authentication function, a third key generation function (e.g., f3), a fourth key generation function (e.g., f4), a fifth key generation function (e.g., f5), a hash algorithm, an Advanced Encryption Standard (AES), SNOW 3G (Snow Third Generation), ZUC (ZUChongzhi), an exclusive OR calculation, and a direct connection calculation. The hash algorithm may include HMAC-SHA-256 (Hash based Message Authentication Code-Secure Hash Algorithm-256, a secure hash algorithm based on a hashed message authentication code 256, which may be expressed as SHA-256), or other hash algorithms or hash functions may be used, which are not exhaustive in this embodiment.

[0066] Taking the first key KgNB as an example, the calculation of the shared key K can be expressed by the following formula: K=KDF(KgNB). The shared key can also be expressed as Ksf, which will not be repeated below.

[0067] Optionally, the shared key is calculated based on the first key and at least one of the following parameters: an identifier of the first device, an identifier of the second device, a random number, and an identifier of a perception service.

[0068] The identifier of the perception service may also be replaced by the perception service type, and the identifier of the perception service may be represented as a perception service ID. The identifier of the perception service may be configured by the SF to the first device and the second device, for example, when the SF sends a first message to the first device and / or the second device respectively, the first message carries the identifier of the perception service.

[0069] The random number may be generated by the first device, and then the random number may be sent by the first device to the second device. Alternatively, the random number may be generated by the second device, and then the random number may be sent by the second device to the first device. Alternatively, the random number may be carried in the first information, that is, it may be configured by the network side (such as SF) to the first device and the second device. It should be understood that this is only an exemplary description. In actual processing, as long as the first device and the second device can obtain the same random number, it is within the scope of protection of this embodiment.

[0070] It should be understood that the above is only an exemplary description of the parameters used to calculate the shared key. In actual processing, other parameters may be added, such as an indicator of the perception service to indicate the execution of the perception service. All parameters that may be used to calculate the shared key are not enumerated here.

[0071] Still taking the first key as KgNB as an example, the calculation of the shared key can be expressed by the following formula: The calculation of the shared key can be expressed by the following formula: K = KDF(KgNB, "Sensing", sensing service ID, UE ID, gNB ID, Nonce), the meanings of the remaining parameters in the formula are the same as those defined in the previous embodiment; except for the first key KgNB in ​​the formula, the remaining parameters are optional parameters, where K represents the shared key, "Sensing" represents the indicator of the sensing service, the sensing service ID is the ID of the sensing service, the UE ID and the gNB ID are the identifier of the first device and the identifier of the second device, respectively. For example, if the first device is a terminal and the second device is a merged access network, the UE ID is the identifier of the first device, and the gNB ID is the identifier of the second device; except for KgNB in ​​the formula, the remaining parameters are optional parameters.

[0072] In some possible implementations, the shared key is calculated based on a second key shared by the first device and the core network device. The shared key is calculated by the first device and the core network device respectively, and the shared key is configured on the second device side.

[0073] In this embodiment, the first device is a terminal, and the second device is an access network device. This embodiment will not be described using the first and second devices, but will instead use the terminal and access network device as examples. It should be noted that as long as the terminal and access network device obtain or calculate the shared key before obtaining the sequence generation parameters corresponding to the downlink perception signal based on the shared key, this is within the scope of this embodiment. The following description does not limit the timing of calculating the shared key and / or obtaining the parameters related to calculating the shared key.

[0074] On the terminal side, the shared key is calculated based on the second key. On the access network device side, the shared key is configured, and the processing on the access network device further includes: receiving the shared key from the core network device.

[0075] On the core network device side, the shared key is calculated based on the second key. The processing of the core network device may include: calculating the shared key based on the second key; and sending the shared key to the access network device.

[0076] This embodiment does not limit the specific triggering method for the core network device to calculate the shared key. For example, when the terminal sends a first request message to the SF through the core network device, the core network device calculates the shared key and configures it to the access network device. For another example, when the access network device sends a second request message to the SF through the core network device, the core network device calculates the shared key and configures it to the access network device. In this case, the shared key can also be sent to the access network device at the same time as the first information. For example, the first information and the shared key can be carried by the same message, etc., and no limitation or exhaustive list is made here.

[0077] Among them, the core network device may include at least one of the following: AMF (Access and Mobility Management Function), AUSF (Authentication Server Function), SEAF (Security Anchor Function), AKMA server (AAnF, AKMA Anchor Function), GBA server BSF (Bootstrapping Server Function), AF (Application Function), SF, etc.; AMF and SEAF may also be set up together. Accordingly, the second key shared by the terminal and the core network device can be one of the following: K shared between the terminal and AMF AMF , K shared between the terminal and AUSF (AMF) SEAF, K shared between the terminal and AKMA AKMA , K shared by the terminal and AF AF , GBA key shared between the terminal and GBA server such as K sNAF It should be understood that this is merely an example and does not limit or exhaustively list all possible key types of the second key.

[0078] The terminal may determine the type of the second key in the following ways:

[0079] In one approach, the type of the second key used by the terminal may be a default one or a protocol-specified one. In this approach, the type of the second key used by the terminal is irrelevant to how the terminal receives the first information.

[0080] In one embodiment, the type of the second key used by the terminal may be related to the first information received by the terminal.

[0081] In one case, the terminal receives the first information by: receiving the first information from the SF through the core network device. In this case, the core network device from which the terminal receives the first information can also be used to determine the type of the second key used by the terminal. For example, if the terminal receives the first information from the AMF, it determines that the second key is K AMF For example, the terminal receives the first information from AUSF, and determines that the second key is K SEAF For example, the terminal receives the first information from AAnF and determines that the second key is K AKMA or K AF For example, the terminal receives the first information from the NAF and determines that the second key is K sNAF .

[0082] In one scenario, the terminal receiving the first information may include: the terminal receiving the first information from the SF via an access network device. In this case, the access network device may receive the first information from the SF via a core network device and send the first information to the terminal. Furthermore, the access network device may send an identifier of the core network device (e.g., at least one of an ID, name, and number) to the terminal. Accordingly, the terminal may determine the type of the second key based on the identifier of the core network device.

[0083] It should be understood that since the terminal and the core network device essentially calculate the shared key based on the second key, and the terminal and the core network device should use the same key algorithm and other identical parameters to calculate the shared key, the shared keys obtained by the two should theoretically be the same. This embodiment no longer distinguishes between the different names of the shared keys calculated by different devices.

[0084] The description of the key algorithm used to calculate the shared key is the same as that in the above embodiment and will not be repeated here.

[0085] The second key is K AMF For example, the terminal and the core network device can use the following formula to calculate the shared key K based on the second key: K = KDF (K AMF ).

[0086] Optionally, on the terminal and core network device side, the shared key is calculated based on the second key and at least one of the following parameters: an identifier of the access network device, a random number, an identifier of the terminal, and an identifier of the perception service.

[0087] The second key is K AMF For example, on the terminal and core network device (AMF) side, the following formula can be used to calculate the shared key: K = KDF (K AMF , "Sensing", sensing service ID, UE ID, gNB ID, Nonce), where K represents the shared key, "Sensing" represents the indicator of the sensing service, sensing service ID is the ID of the sensing service, UE ID is the identifier of the terminal, and gNB ID is the identifier of the access network device; in addition to the second key K AMF , the remaining parameters are optional.

[0088] The second key is K SEAF For example, on the terminal and core network device (AUSF) side, the following formula can be used to calculate the shared key: Ksf = KDF (K SEAF , “Sensing”, sensing service ID, UE ID, gNB ID, Nonce), the meaning of each parameter in the formula is the same as in the previous example and is not repeated here. SEAF , the remaining parameters are optional.

[0089] It should be noted that the above is only an exemplary description. In actual processing, the second key can also be replaced by K AKMA , K AF , K sNAF And so on, any one of them, I will not go into details one by one.

[0090] Furthermore, the random number may be generated by a core network device. The identifier of the perception service on the terminal side and / or the second random number may be configurable.

[0091] Specifically, on the terminal side, the method further includes: receiving at least one of the following from the core network device: an identifier of the perception service, and a random number. The timing at which the terminal receives the identifier and / or random number of the perception service is within the protection scope of this embodiment as long as it occurs before obtaining the sequence generation parameter corresponding to the downlink perception signal based on the shared key. For example, it may be before receiving the reflected signal of the downlink perception signal. For example, when the terminal sends a first request message to the SF via the core network device, the core network device sends the random number to the terminal while forwarding the first information sent by the SF to the terminal. For example, when the access network device sends a second request message to the SF via the core network device, the core network device sends the random number to the terminal while forwarding the first information sent by the SF to the access network device. This embodiment does not limit the timing at which the terminal receives the identifier and / or random number of the perception service, or the related process for the terminal to receive the identifier and / or random number of the perception service.

[0092] In some possible implementations, the first device may receive the shared key.

[0093] In one embodiment, when the first device is an access network device and the second device is a terminal, the access network device can receive a shared key from the core network device; in this case, the core network device and the terminal calculate the shared key based on the second key shared by both parties. The specific processing method is similar to the aforementioned embodiment and will not be repeated.

[0094] In one embodiment, the first device is a terminal and the second device is an access network device, or the first device is an access network device and the second device is a terminal, and the first device can receive the shared key.

[0095] In this embodiment, the shared key can be generated by SF and configured to the first device and the second device respectively. In this embodiment, the shared key can be K sf This embodiment does not limit the manner in which the SF calculates the shared key. As long as the first device and the second device ultimately obtain the same shared key, they are protected by this embodiment. This embodiment also does not limit the timing at which the SF configures the shared key for the first device and the second device. As long as it is before the sequence generation parameters corresponding to the downlink perception signal are obtained based on the shared key, they are protected by this embodiment.

[0096] In some possible implementations, the first information may further include an identifier of the shared key.

[0097] In this embodiment, the SF can directly instruct the first device and the second device to use the same key as the shared key by carrying the identifier of the shared key in the first information. The shared key can be any one of multiple possible types of keys that the first device and the second device have pre-generated and shared.

[0098] For example, the first device and the second device have already obtained at least one of the access layer key, access layer security basic key, next hop key (NH), physical layer key, etc. shared by both parties through other protocols or processes in advance. The relevant descriptions of the above-mentioned various types of keys are the same as those in the previous embodiment and are not repeated here. For example, SF can include or carry the ID of Kphy in the first information, so that the first device and the second device can both know to use Kphy as the shared key used this time, and use the shared key to obtain the sequence generation parameter corresponding to the downlink perception signal. For example, SF can include or carry Kphy in the first information. UPenc ID, so that the first device and the second device can know the use of K UPenc The shared key is used as the shared key for this time, and the sequence generation parameter corresponding to the downlink perception signal is obtained using the shared key.

[0099] In some possible implementations, the first information is used by the first device to determine a sequence generation parameter corresponding to generating the downlink perception signal based on a plurality of bits intercepted from the shared key.

[0100] Specifically, after the first device receives the first information, the method further includes: intercepting multiple bits from the shared key based on the first information, and generating a sequence generation parameter corresponding to the downlink perception signal based on the multiple bits.

[0101] The extracting a plurality of bits from the shared key based on the first information may refer to: determining an extracting position based on the first information, and extracting a plurality of bits from the shared key based on the extracting position.

[0102] Generating the sequence generation parameter corresponding to the downlink perception signal based on the multiple bits may refer to using the multiple bits as the sequence generation parameter corresponding to the downlink perception signal. That is, maintaining the order of the multiple bits unchanged and the value of each bit in the multiple bits unchanged, and directly using the multiple bits as the sequence generation parameter for the downlink perception signal. Maintaining the order of the multiple bits unchanged may refer to maintaining the order of the multiple bits identical to the order of the multiple bits in the shared key.

[0103] In a preferred example, the number of the multiple bits intercepted from the shared key may be 32 bits or 32 bits.

[0104] In the process of PRS signal generation, the main variables come from cinit. The main core variables in cinit are In the relevant agreements Parameter range: 0~4095=0~2 12-1, this example increases The value range of this parameter is changed from 2 12 Expanded to 0-2 31 -1. By increasing The range of the parameter is increased by 2 19 The possibility space of the attacker guesses the PRS possibility space from the original protocol 2 93 Increased to 2 112 , close to 2 128 The size of the possibility space.

[0105] It should be understood that this is only an exemplary explanation. In actual processing, the number of multiple bits intercepted from the shared key may not be limited to 32 bits or 32 bits. For example, in some possible examples, the number of multiple bits intercepted from the shared key may also be greater than 32 bits, such as 47 bits, etc.

[0106] Alternatively, in some other examples, the number of the multiple bits intercepted from the shared key may be less than 32 bits and greater than or equal to 12 bits, etc., which are not exhaustively listed here.

[0107] For example, the sequence generation parameters corresponding to the downlink perception signal are: For example, the first device intercepts multiple bits from the shared key based on the first information, and generates a sequence generation parameter corresponding to the downlink perception signal based on the multiple bits, which can be expressed as follows: Wherein, K is a shared key, Truncate[] represents a truncation calculation or truncation calculation or truncation function, and "32" represents the number of truncation bits. The shared key can be any one of the ones mentioned in the above embodiments, and will not be repeated here.

[0108] The first information is used to indicate at least one of the following: a start bit of the shared key to be intercepted; an end bit of the shared key to be intercepted; a number of bits of the shared key to be intercepted; or an interception rule of the shared key.

[0109] In one embodiment, the first information is used to indicate a start bit of interception of the shared key and an end bit of interception of the shared key.

[0110] The interception start bit of the shared key can be indicated by the position information of the interception start bit of the shared key. The interception end bit of the shared key can be indicated by the position information of the interception end bit of the shared key. That is, the first information may include: the position information of the interception start bit of the shared key and the position information of the interception end bit of the shared key.

[0111] The position information may be indicated by numbering or sorting. It should be noted that numbering is merely an exemplary description method. In some other examples, the numbering may alternatively be represented by an index, a sequence number, or the like. This does not limit or exhaustively list all possible names for numbering. Sorting is also merely an exemplary description method. In some other examples, the sorting may alternatively be represented by an arrangement order, an arrangement position, a ranking, or a rank, or the like. This does not limit or exhaustively list all possible names for sorting.

[0112] In terms of the composition of the shared key, different bits within the shared key can be numbered differently. That is, each bit in the shared key is numbered, and the numbers corresponding to two adjacent bits are consecutive, with the number corresponding to the latter bit being greater than the number corresponding to the former bit. For example, the numbering can be incremented starting from the lowest bit of the shared key, which is numbered 0. Similarly, the highest bit of the shared key is numbered N, where N is equal to the length of the shared key minus one. Alternatively, different bits within the shared key can be distinguished by different orderings. For example, the lowest bit of the shared key is numbered 1, while the highest bit of the shared key is numbered M, where M is equal to the length of the shared key. Therefore, in the first information, the number or sequence number of the truncated start bit in the shared key can be used to indicate the truncated start bit in the shared key, and the number or sequence number of the truncated end bit in the shared key can be used to indicate the truncated end bit in the shared key.

[0113] Optionally, the type of the location information, whether it is a number or a sequence, may be a default or protocol-specified type. For example, if the number is used as the location information by default, the first information includes at least one of the following: the number of the intercepted start bit in the shared key, and the number of the intercepted end bit in the shared key.

[0114] Optionally, whether the type of the position information is specifically a number or a sort may be indicated in the first information. For example, in addition to including at least one of the position information of the intercepted start bit in the shared key and the position information of the intercepted end bit in the shared key, the first information may also include an indication of the type of position information. The indication of the type of position information is used to indicate whether numbering or sorting is used as the position information. For example, if the indication of the type of position information includes index, it indicates that numbering is used as the position information. If the indication of the type of position information includes order (arrangement order), it indicates that sorting is used as the position information.

[0115] Extracting multiple bits from the shared key based on the first information may include: determining the starting bit in the shared key based on the position information of the extracted starting bit of the shared key contained in the first information, and determining the ending bit of the shared key based on the position information of the extracted ending bit in the shared key contained in the first information; and extracting the starting bit, the ending bit, and all bits between the starting bit and the ending bit in the shared key as the extracted multiple bits.

[0116] For example, the first information can be expressed as {i-start, i-stop}, where i-start represents the position information of the interception start bit corresponding to the shared key, and i-stop represents the position information of the interception end bit corresponding to the shared key.

[0117] Exemplarily, the first information includes: the serial number of the intercepted start bit corresponding to the shared key, and the serial number of the intercepted end bit corresponding to the shared key. For example, the first information may include {0,31}, that is, i-start is equal to 0, indicating that the serial number of the intercepted start bit is 0, and i-stop is 31, indicating that the serial number of the intercepted end bit is 31; then the first device can determine that the serial number of the start bit in the shared key is 0, and the serial number of the end bit in the shared key is 31 based on the first information; and intercept all 32 bits in the shared key with serial numbers 0 to 31 and therebetween as the intercepted 32 bits.

[0118] For example, the first information includes: the order of the intercepted start bit corresponding to the shared key, and the order of the intercepted end bit corresponding to the shared key. For example, the first information may include {97, 128}, that is, i-start is equal to 97, indicating that the order of the intercepted start bit is 97, and i-stop is 128, indicating that the order of the intercepted end bit is 128; then the first device can determine that the order of the start bit in the shared key is 97, and the order of the end bit in the shared key is 128 based on the first information; all 32 bits in the shared key that are ordered between 97 and 128 are intercepted as the intercepted 32 bits.

[0119] In one embodiment, the first information is used to indicate the start bit of the shared key to be intercepted and the number of bits of the shared key to be intercepted. Alternatively, the first information is used to indicate the end bit of the shared key to be intercepted and the number of bits of the shared key to be intercepted.

[0120] The number of bits intercepted from the shared key refers to the total number of bits intercepted from the shared key. The number of bits intercepted from the shared key can also be replaced by the interception length of the shared key, which also refers to the total number of bits intercepted.

[0121] Optionally, the number of truncated bits of the shared key may be represented by a value directly indicating the number of truncated bits of the shared key, or a value of the number of truncated bits of the shared key. For example, the number of truncated bits of the shared key may be represented by a value of 32 indicating the number of truncated bits of the shared key to indicate that the number of truncated bits of the shared key is 32 bits.

[0122] Exemplarily, the first information may include: the order of the intercepted start bits corresponding to the shared key, and the number of intercepted bits of the shared key.

[0123] The first device intercepts multiple bits from the shared key based on the first information, which may include: determining the starting bit position in the shared key based on the position information of the interception starting bit of the shared key contained in the first information, and taking the starting bit position in the shared key as the current bit; judging whether the number of extracted bits reaches the interception bit number value of the shared key contained in the first information; if the number of extracted bits does not reach the interception bit number value of the shared key contained in the first information, continuing to extract the next bit of the current bit, and returning to execute the process of judging whether the number of extracted bits reaches the interception bit number value of the shared key contained in the first information; if the number of extracted bits reaches the interception bit number value of the shared key contained in the first information, ending the extraction process, and taking all the currently extracted bits as multiple bits intercepted from the shared key.

[0124] Alternatively, the first device intercepts multiple bits from the shared key based on the first information, which may include: calculating the position information of the intercepted end bit of the shared key based on the position information of the intercepted start bit of the shared key contained in the first information and the number of intercepted bits of the shared key contained in the first information; determining the start bit position in the shared key based on the position information of the intercepted start bit, and determining the end bit position of the shared key based on the position information of the intercepted end bit; intercepting the start bit position, the end bit position, and all bits between the start bit position and the end bit position in the shared key as the intercepted multiple bits.

[0125] Among them, calculating the position information of the intercepted end bit of the shared key based on the position information of the intercepted start bit of the shared key contained in the first information and the number of intercepted bits of the shared key contained in the first information can refer to: adding the position information of the intercepted start bit of the shared key contained in the first information and the number of intercepted bits of the shared key contained in the first information to obtain the position information of the intercepted end bit of the shared key.

[0126] Exemplarily, the first information may include: the order of the intercepted end bits corresponding to the shared key and the number of intercepted bits of the shared key.

[0127] The first device intercepts multiple bits from the shared key based on the first information, which may include: determining the end bit position in the shared key based on the position information of the intercepted end bit of the shared key contained in the first information, and taking the end bit position in the shared key as the current bit; judging whether the number of extracted bits reaches the intercepted bit number value of the shared key contained in the first information; if the number of extracted bits does not reach the intercepted bit number value of the shared key contained in the first information, continuing to extract the previous bit of the current bit, and returning to execute the process of judging whether the number of extracted bits reaches the intercepted bit number value of the shared key contained in the first information; if the number of extracted bits reaches the intercepted bit number value of the shared key contained in the first information, ending the extraction process, and taking all the currently extracted bits as multiple bits intercepted from the shared key.

[0128] Alternatively, the first device intercepts multiple bits from the shared key based on the first information, which may include: calculating the position information of the intercepted start bit of the shared key based on the position information of the intercepted end bit of the shared key contained in the first information and the number of intercepted bits of the shared key contained in the first information; determining the start bit position in the shared key based on the position information of the intercepted start bit, and determining the end bit position of the shared key based on the position information of the intercepted end bit; intercepting the start bit position, the end bit position, and all bits between the start bit position and the end bit position in the shared key as the intercepted multiple bits.

[0129] Among them, calculating the position information of the intercepted end bit of the shared key based on the position information of the intercepted end bit of the shared key contained in the first information and the number of intercepted bits of the shared key contained in the first information can refer to: subtracting the number of intercepted bits of the shared key contained in the first information from the position information of the intercepted end bit of the shared key contained in the first information to obtain the position information of the intercepted end bit of the shared key.

[0130] Optionally, the number of truncated bits of the shared key may be represented by a quantity indicator.

[0131] Exemplarily, the first device side may pre-configure or save at least one of the following: multiple optional quantity indicators, multiple optional truncated bit quantities, and a correspondence between each optional quantity indicator and the optional truncated bit quantity, wherein different optional quantity indicators correspond to different optional truncated bit quantities.

[0132] For example, the first device may pre-configure or save two optional quantity indicators, namely a first optional quantity indicator and a second optional quantity indicator. The first optional quantity indicator is used to indicate that the number of truncated bits is 12, and the second optional quantity indicator is used to indicate that the number of truncated bits is 32. As long as the first optional quantity indicator and the second optional quantity indicator are different, they are within the protection scope of this embodiment, such as the first optional quantity indicator is "00" and the second optional quantity indicator is "01", or the first optional quantity indicator is "10" and the second optional quantity indicator is "01", etc., which are not limited or exhaustive here.

[0133] Exemplarily, the first information may include: the order of the intercepted start bits corresponding to the shared key, and a quantity indicator of the number of intercepted bits of the shared key. Alternatively, the first information may include: the number of intercepted end bits corresponding to the shared key, and a quantity indicator of the number of intercepted bits of the shared key. In this example, the process of the first device intercepting multiple bits from the shared key based on the first information is similar to the aforementioned embodiment, differing only in that the corresponding number of intercepted bits needs to be determined based on the quantity indicator of the number of intercepted bits of the shared key contained in the first information, and therefore, a repeated explanation is not provided.

[0134] In some possible examples, the number of bits intercepted from the shared key may be a default number set by the first device or specified by a protocol. In such an example, the first information may be used only to indicate the start bit of the shared key to be intercepted; or the first information may be used only to indicate the end bit of the shared key to be intercepted.

[0135] Since the number of bits intercepted from the shared key is specified by default or by the protocol, after receiving any of the above-mentioned first information, the first device can determine the number of bits to be intercepted based on the number of bits intercepted from the shared key it already has and the interception start bit of the shared key; or determine the number of bits to be intercepted based on the number of bits intercepted from the shared key it already has and the interception end bit of the shared key. The specific method for determining the number of bits to be intercepted is similar to that in the previous embodiment and will not be repeated here.

[0136] In one embodiment, the first information is used to indicate an interception rule of the shared key.

[0137] Optionally, the shared key interception rule may be indicated using specific rule description information. For example, the rule description information may include at least one of intercepting odd bits, intercepting even bits, intercepting a specified number of bits, intercepting a number of bits, etc. Intercepting a specified number of bits may include intercepting bits at a specified number of positions.

[0138] For example, the first information includes a truncation rule for a shared key, and the truncation rule includes truncation of odd bits and the number of truncation bits. In this case, the first device can extract the odd bits to be truncation as indicated by the truncation rule in the first information, starting from the lowest odd bit, until the number of all bits currently extracted reaches the number of truncation bits indicated by the truncation rule in the first information. Specifically, the first device can extract the lowest odd bit as the current bit based on the truncation of odd bits indicated by the truncation rule in the first information; determine whether the number of extracted bits has reached the number of truncation bits indicated by the truncation rule in the first information; if the number of extracted bits has not reached the number of truncation bits indicated by the truncation rule in the first information, continue to extract the next odd bit after the current bit, and return to the process of determining whether the number of extracted bits has reached the number of truncation bits indicated by the truncation rule in the first information; if the number of extracted bits has reached the number of truncation bits indicated by the truncation rule in the first information, terminate the extraction process, and use all the currently extracted bits as the multiple bits truncation from the shared key.

[0139] For example, the first information includes a shared key interception rule, where the interception rule includes intercepting a specified number of bits. In this case, the first device may extract the multiple bits from the position corresponding to the shared key based on the interception rule in the first information indicating the interception of the specified number of bits. It should be understood that the specified positions of the multiple bits may also be numbers or sequence numbers. The relevant description is the same as in the previous embodiment and is not repeated here.

[0140] Optionally, the interception rule of the shared key may be indicated by a rule indicator.

[0141] Exemplarily, the first device may pre-save or configure at least one of the following: a plurality of optional rule indicators, a plurality of optional rules, a correspondence between each optional rule indicator and an optional rule, wherein different optional rule indicators correspond to different rules. For example, the first optional rule indicator among the plurality of optional rule indicators corresponds to truncating odd bits, the second optional rule indicator corresponds to truncating even bits, the third optional rule indicator corresponds to at least one of truncating the number of bits, and so on. Among them, as long as the three optional rule indicators are different from each other, they are within the protection scope of this embodiment, such as the first optional rule indicator is "001", the second optional rule indicator is "010", and the third optional rule indicator is "011", or the first optional rule indicator is "100", the second optional rule indicator is "200", and the third optional rule indicator is "300", and so on, which are not limited or exhaustive here.

[0142] Exemplarily, the first information may include one or more rule indicators; the processing of the first device determining multiple bits is similar to the aforementioned example, with the only difference being that the first device first determines the corresponding specific rules based on one or more rule indicators, and then performs the processing of intercepting multiple bits, so no repeated explanation is given.

[0143] In some possible implementations, the first information is used by the first device to determine, based on the shared key and the calculation parameters, a sequence generation parameter corresponding to the downlink perception signal. Specifically, after the first device receives the first information, the method further includes: determining the calculation parameters based on the first information, and calculating the sequence generation parameters corresponding to the downlink perception signal based on the shared key and the calculation parameters.

[0144] The calculation parameter may be a specific value, and the calculation parameter may be a positive integer.

[0145] Calculating the sequence generation parameter corresponding to the downlink perception signal based on the shared key and the calculation parameter may refer to: calculating the calculation parameter based on the first calculation method to obtain a first value, and calculating the shared key and the first value based on the second calculation method to obtain the sequence generation parameter corresponding to the downlink perception signal.

[0146] The first calculation method and the second calculation method can both be pre-configured, defaulted, or specified by a protocol.

[0147] Exemplarily, the first calculation method may be a power of 2 calculation; the second calculation method may be a modulo calculation (mod) or a remainder calculation, that is, calculating the remainder of a division. Specifically, calculating the sequence generation parameter corresponding to the downlink perception signal based on the shared key and the calculation parameter may be: calculating 2 to the power of L to obtain a first value, where the value of L is equal to the calculation parameter; calculating the remainder after dividing the shared key by the first value, and using the remainder as the sequence generation parameter corresponding to the downlink perception signal, wherein calculating the remainder after dividing the shared key by the first value is performing a modulo calculation or a remainder calculation.

[0148] For example, the sequence generation parameters corresponding to the downlink perception signal are For example, the sequence generation parameter corresponding to the downlink perception signal is calculated and can be expressed as: Where K is the shared key, mod represents the modulo calculation or modulo function, and "L" represents the calculation parameter.

[0149] In the process of generating the PRS signal (i.e., the downlink perception signal), the main variable comes from cinit. In the solution provided in this embodiment, the principle for selecting the calculation parameter L is to ensure that the sequence generated by cinit is an m-sequence, so that two m-sequences generate a perception sequence.

[0150] In a preferred example, the calculation parameter may be 31. The sequence generation parameter corresponding to the downlink perception signal obtained by the above calculation may be expressed as:

[0151] The above embodiment has explained that in the process of generating the PRS signal (ie, the downlink perception signal), the main variables come from cinit. The main core variables in cinit are In the relevant agreements Parameter range: 0~4095=0~2 12 -1, this example passes The calculation method makes The value range is: {0,1,...,2 31 -1}, thus The range of parameters is from {0,1,...,2 12 -1} is expanded to {0,1,...,2 31 -1}. By increasing The range of the parameter is increased by 2 19 The possibility space of the attacker guesses the PRS possibility space from the original protocol 2 93 Increased to 2 112 , close to 2 128 The size of the possibility space.

[0152] In some possible examples, the calculation parameter may also be 47. For example, the sequence generation parameter corresponding to the downlink perception signal is calculated and obtained, which can be expressed as:

[0153] This example passes The calculation method makes The value range is increased to: {0,1,...,2 47 -1}, thus The range of parameters is from {0,1,...,2 12 -1} is expanded to {0,1,...,2 47 -1}. By increasing The range of the parameter is increased by 2 35 The possibility space of the attacker guesses the PRS possibility space from the original protocol 2 93 Increased to 2 128 The size of the possibility space.

[0154] The above are only some exemplary descriptions of possible values ​​of the calculation parameters. In practice, the calculation parameters may be larger or smaller, and all possible values ​​of the calculation parameters are not exhaustively listed here.

[0155] The method for determining the calculation parameters may vary with the content of the first information. The following is an illustrative description of the method for determining the calculation parameters in combination with multiple possible embodiments.

[0156] The first information includes one of the following: the calculation parameter; and range-related information corresponding to the sequence generation parameter, where the range-related information corresponding to the sequence generation parameter is used to determine the calculation parameter.

[0157] In one embodiment, the first information may include a calculation parameter. That is, the first information may directly include a specific value of the calculation parameter, and the first device may determine the calculation parameter based on the first information by extracting the calculation parameter from the first information.

[0158] In one embodiment, the first information may include range-related information corresponding to the sequence generation parameter.

[0159] The range-related information corresponding to the sequence generation parameter includes one of the following: a value range corresponding to the sequence generation parameter, and a value range indicator corresponding to the sequence generation parameter.

[0160] Optionally, the range-related information corresponding to the sequence generation parameter may include a value range corresponding to the sequence generation parameter.

[0161] In one example, the value range corresponding to the sequence generation parameter may refer to the range of the sequence generation parameter identifier (referred to as Sequence ID), for example, the value range corresponding to the sequence generation parameter may be {0...A}, or {0...2 A-1}, where A is a positive integer.

[0162] In this case, the first device may determine the calculation parameter based on the first information by: determining the calculation parameter based on a value range corresponding to the sequence generation parameter.

[0163] For example, the calculation parameter can be determined by using a logarithmic function with a base of 2 to calculate the maximum value in the value range corresponding to the sequence generation parameter. For example, the value range corresponding to the sequence generation parameter is {0...2 32-1}; Accordingly, the maximum value 2 in the value range corresponding to the sequence generation parameter is 32-1 , using the logarithmic function with base 2 to calculate the maximum value in the range of values ​​corresponding to the sequence generation parameter, the result is 31.

[0164] In one example, the value range corresponding to the sequence generation parameter may also indicate the maximum value corresponding to the sequence generation parameter, such as 2 32-1Accordingly, the first device may determine the calculation parameter based on the first information by using a logarithmic function with base 2 to calculate the maximum value corresponding to the sequence generation parameter included in the first information to obtain a second value, and adding one to the second value to obtain the calculation parameter.

[0165] Optionally, the range-related information corresponding to the sequence generation parameter may include a value range indicator corresponding to the sequence generation parameter.

[0166] Exemplarily, the first device may pre-save or configure at least one of the following: multiple selectable value range indicators, multiple optional calculation parameters, a correspondence between each selectable value range indicator and an optional calculation parameter, and a correspondence between each selectable value range indicator and an selectable value range corresponding to a sequence generation parameter, wherein different selectable value range indicators correspond to different optional calculation parameters and / or different selectable value ranges.

[0167] For example, the first device pre-stores two selectable value range indicators and their corresponding selectable calculation parameters and / or selectable value ranges, the first selectable value range indicator corresponds to the first selectable calculation parameter and / or the first selectable value range, the second selectable value range indicator corresponds to the second selectable calculation parameter and / or the second selectable value range, etc. As long as the first selectable value range indicator and the second selectable value range indicator are different, they are within the protection scope of this embodiment, for example, the first selectable value range indicator is "0" and the second selectable value range indicator is "1", or the first selectable value range indicator is "1" and the second selectable value range indicator is "2", etc., and no limitation or exhaustive enumeration is made here.

[0168] For example, the first selectable value range indicator "0" corresponds to the first selectable calculation parameter, namely 32, and the second selectable value range indicator "1" corresponds to the second selectable calculation parameter, namely 12. It should be understood that this is merely an example, and in actual processing, the selectable ranges of calculation parameters include but are not limited to the several possibilities in the above examples, and the selectable value range indicators are also not limited to the several possibilities in the above examples, but are not intended to be exhaustive.

[0169] Exemplarily, the first information may include a value range indicator corresponding to the sequence generation parameter. The first device determining the calculation parameter based on the first information may include: determining the calculation parameter corresponding to the value range indicator based on a value range indicator corresponding to the sequence generation parameter.

[0170] In some possible implementations, the first device is an access network device. After obtaining a sequence generation parameter corresponding to a downlink perception signal, the access network device may generate and transmit the downlink perception signal, including: calculating a perception sequence based on the sequence generation parameter corresponding to the downlink perception signal; sequentially extracting multiple bits from the perception sequence, calculating modulation symbols for the multiple bits based on a first modulation scheme, mapping the modulation symbols to corresponding perception signal time-frequency resources, and obtaining and transmitting the downlink perception signal. The number of modulation symbols is multiple and is not limited herein.

[0171] The perception sequence may also be referred to as any one of a gold sequence, a bitstream, a perception bitstream, and the like, and all possible names are not limited or exhaustive herein. The perception sequence may be a gold sequence, and calculating the perception sequence based on the sequence generation parameter corresponding to the downlink perception signal may refer to calculating the perception sequence based on the sequence generation parameter corresponding to the downlink perception signal using a gold sequence calculation method.

[0172] For example, assuming that the perception sequence is represented as c(n), where n = 0, 1, ..., MPN-1, the calculation method of c(n) is as follows: c(n) = (x1(n+N c )+x2(n+N c ))mod2 x1(n+31)=(x1(n+3)+x1(n))mod2 x2(n+31)=(x2(n+3)+x2(n+2)+x2(n+1)+x2(n))mod2

[0173] Among them, NC = 1600;

[0174] The first m-sequence is initialized to x1(0)=1,...,x1(n)=0,n=1,...,30;

[0175] Initialization of the second m-sequence:

[0176] The length of the Gold sequence c(n) is: 2 31 -1; The sequence generation parameter corresponding to the downlink perception signal is calculated based on the solution provided in the embodiment of the present application. The specific generation method has been described in detail in the previous embodiment and will not be repeated here. The number of symbols in a slot; is the time slot number; l is the OFDM symbol mapped to the time slot.

[0177] The processing of extracting multiple bits and the processing of calculating modulation symbols can be performed alternately. For example, after extracting multiple bits for the first time, the multiple bits are processed and mapped to the corresponding time-frequency resources based on the first modulation method, and then multiple bits are extracted for the second time, and then the multiple bits are processed and mapped to the corresponding time-frequency resources based on the first modulation method, and so on, until the time-frequency resources of the perception signal are fully mapped.

[0178] The first modulation mode may be Quadrature Phase Shift Keying (QPSK). In this case, the number of multiple bits extracted each time may be 2 bits. The related processing of QPSK modulation and mapping PRS resources is the same as that described in the previous embodiment and will not be described in detail. The modulation symbol obtained by calculating the multiple bits based on QPSK can be expressed as: Wherein, c(2m) and c(2m+1) are specific values ​​of 2 bits respectively, and r(m) represents the mth modulation symbol.

[0179] As shown in Figure 3, after generating the c(n) bit stream (perception sequence, simply represented as c(n)), c(n) is modulated into symbols by QPSK in sequence starting from c(0) and mapped to the subcarriers of the corresponding symbol. Assuming that the number of PRS subcarriers on the corresponding symbol of the corresponding time slot is N, then in the original protocol, it is necessary to take c(0), c(1), ..., c(2N-1) bits from c(n), and take 2 bits in sequence to map them to the corresponding subcarriers to generate QPSK symbols. As shown in Figure 3, taking the first symbol of the first resource as an example, {c(0), c(1)}, {c(2), c(3)}, {c(4), c(5)}, {c(6), c(7)}, {c(2N-2), c(2N-1)} are taken in sequence to obtain symbols modulated by QPSK and mapped to the subcarriers of the first symbol of the first resource (PRS resource).

[0180] In some possible implementations, the first device is a terminal. After obtaining the sequence generation parameters corresponding to the downlink perception signal and receiving the echo signal of the downlink perception signal, the processing of the terminal may include: calculating a perception sequence based on the sequence generation parameters corresponding to the downlink perception signal; extracting multiple bits from the perception sequence in sequence; calculating the modulation symbols for the multiple bits using a first modulation method; and demodulating the echo signal of the downlink perception signal based on the modulation symbols to obtain the perception result.

[0181] The method for calculating the perception sequence based on the sequence generation parameters corresponding to the downlink perception signal is the same as in the aforementioned embodiment and is not described in detail here. The relevant description of the first modulation method is the same as in the aforementioned embodiment and is not described in detail here. The specific processing of the terminal using the first modulation method to calculate the modulation symbols for the multiple bits should also be the same as the specific processing of the access network device side to calculate the modulation symbols for the multiple bits based on the first modulation method, and is therefore not described in detail here.

[0182] Demodulating the echo signal of the downlink sensing signal based on the modulation symbol to obtain the sensing result may include: calculating a channel estimation value based on the modulation symbol corresponding to the first resource and the echo signal of the downlink sensing signal received on the first resource; and obtaining the sensing result based on the channel estimation value. Relevant parameters in the channel estimation value include at least one of the following: amplitude, frequency, and phase.

[0183] The sensing result calculated based on the channel estimation value may refer to the sensing result being calculated using one or more algorithms according to different sensing requirements (such as different sensing types and / or different sensing services, etc.) and / or a default method. This embodiment does not limit the various possible algorithms.

[0184] The first resource may include a first time domain resource and a first frequency domain resource. The first time domain resource may be any one of a specified moment, a period of time, or a time domain range where a specified moment t is located, etc.; the first frequency domain resource may be any one of a specified subcarrier, or a subcarrier on a specified frequency f, etc. For example, assuming that the first resource is a subcarrier at moment t and frequency f, the downlink perception signal transmitted by the access network device on the first resource is expressed as: x(t,f); the reflected signal obtained after the downlink perception signal passes through the perception target is expressed as: y(t,f). Since the terminal side calculates the modulation symbol based on the same perception sequence and the same calculation method as the access network device, in theory the modulation symbol on the first resource should be the same as the downlink perception signal transmitted by the access network device on the first resource, so the modulation symbol on the first resource is also expressed as: x(t,f); on the first resource, that is, at moment t and on the subcarrier with a frequency of f, the terminal can calculate the CSI as Here, H() represents the channel estimate, which can be included in the CSI. For example, CSI amplitude can be used to estimate respiratory rate, while CSI phase can be used to estimate respiratory rate; CSI Doppler information can be used to infer indoor human motion trajectories; CSI dynamic phase changes can be used for gesture recognition; and human behavior detection can be performed by combining CSI amplitude and phase.

[0185] After completing the above processing, the terminal may also perform the following processing: reporting the perception result. The terminal reporting the perception result may include one of the following: the terminal reporting the perception result to the core network device; the terminal reporting the perception result to the access network device; the terminal reporting the perception result to the SF. The relevant processing of the terminal is not limited here.

[0186] The solution provided in the embodiment of this application is described in conjunction with relevant technologies:

[0187] Related technologies do not address the security of PRS signal transmission from the perspective of its inherent security. The security of the PRS signal itself is crucial when performing operations such as sensing services. Improving the security of the PRS signal itself is a key consideration in protecting PRS signal perception results. After the PRS sequence is generated, it is mapped onto a time-frequency grid to generate PRS resources. These resources are repeated according to specific rules, and a PRS resource set is generated and distributed. An attacker performs blind detection on the PRS signal. The following section analyzes the possible space for an attacker to guess the PRS signal.

[0188] The parameters for configuring the PRS sequence and resources are as follows, and the corresponding specific configurations are as follows:

[0189] PRS Point A: This field specifies the absolute frequency of the DL-PRS reference resource block. Its lowest subcarrier is also called DL-PRS Point A. Value range: 0 to 3278165.

[0190] StartPRB: This field specifies the starting PRB index, which is defined relative to the reference DL-PRS Point A of the positioning frequency layer. Value range: 0 to 2176.

[0191] Bandwidth: This field specifies the number of PRBs allocated for DL-PRS resources (allocated DL-PRS bandwidth), which is a multiple of 4 PRBs. Values ​​range from 1 to 63.

[0192] PRS sequence: PRS sequence, sequence ID value: 0~4095=0~2 12 -1.

[0193] Symbol offset: The starting symbol of the DL-PRS resource in a time slot. Value range: 0 to 12.

[0194] NumSymbol (Number of symbols): The number of symbols for each DL-PRS resource in a time slot: 2, 4, 6, 12.

[0195] Comb size: This field specifies the spacing of resource elements in each symbol of the DL-PRS resource. Values: 2, 4, 6, 12.

[0196] Starting offset: The frequency domain resource element (RE) offset of the first symbol in the DL-PRS resource. Value range: 0 to CombSize-1.

[0197] The above parameters symbol offset, NumSymbol, comb size, and starting offset constrain each other. These parameters are configured differently according to different usage scenarios. Under different configurations, the possibility of PRS resource space is different. Under the existing protocol, the size of the PRS resource possibility space is 2.653E+17. Furthermore, the PRS resource set includes multiple repeated instances, so the size of the PRS possibility space can be increased to 9.537E+27≈2 93 .

[0198] The solution provided in this embodiment changes the parameter range and method of generating the PRS sequence, thereby achieving the purpose of improving the security of the PRS signal. In the perception service involving user privacy, it provides higher security than the positioning service. In the process of PRS signal generation, the main variables come from cinit. In cinit, the main core variables are The parameters selected in this example are c for calculating the PRS sequence init in Parameters, in the relevant protocols Parameter range: 0~4095=0~2 12 -1, this example increases The value range of this parameter is changed from 2 12 Expanded to 0-2 31 -1. By increasing The range of the parameter is increased by 2 19 The possibility space of the attacker guesses the PRS possibility space from the original protocol 2 93 Increased to 2 112 , close to 2 128 The size of the possibility space.

[0199] The following examples are used to further illustrate the solution provided in this application:

[0200] In the first embodiment, the first device is a UE, and with reference to FIG4 :

[0201] Step 401: The UE sends a first request message to the perception server (SF), where the first request message is used to request first information, i.e., perception-related auxiliary data or configuration data, which is mainly used for the auxiliary data (NR-DL-PRS-AssistanceData) required for the subsequent UE to receive downlink PRS signaling.

[0202] It should be noted that this step may be optional, that is, step 402 may be directly executed without executing step 401 .

[0203] Step 402: The SF returns the sensing assistance data (ie, the first information) to the UE. The sensing assistance data includes intercepting relevant information to increase the Sequence ID (sequence ID) in the range of {0...2^32-1}.

[0204] The interception related information can be used to indicate at least one of the following: the interception start bit of the shared key; the interception end bit of the shared key; the number of intercepted bits of the shared key; the interception rule of the shared key. The interception related information can be used to determine the 32 bits of the interception key KeNB, such as {0..31} bits, or {97..128}, or any 32 bits; for example, it can be expressed as KeNB can be replaced by the existing key shared between the base station and the UE, such as NH, K RRCINT ,K RRCENC ,K UP INT ,K UPENC Or, KeNB can be replaced with a key shared by UE and core network equipment, such as K AMF , K SEAF , K AKMA , K AF , K sNAF , K SF And so on, any one of them, which will not be exhaustive or repeated here. Thus, the range of SequenceID is {0...2^32-1}.

[0205] Among them, SF is the perception server, and the messages transmitted between UE and SF may be forwarded through the physical interface between AMF and base station shown in Figure 4.

[0206] In the second embodiment, the first device is a base station, as shown in FIG5 :

[0207] Step 501: The base station sends a second request message to the SF. The second request message is used to request first information, i.e., perception-related auxiliary data or configuration data, which is mainly used for the auxiliary data (NR-DL-PRS-AssistanceData) required for the subsequent base station to generate and send downlink PRS. This step may be optional, that is, step 501 may not be performed and step 502 may be performed directly.

[0208] Step 502: SF returns the sensing assistance data (i.e., the first information) to the base station. The sensing assistance data includes the interception related information, which is used to increase the range of SequenceID (sequence ID) to {0...2^32-1}. The detailed description of this step is similar to that of the aforementioned step 402, except that the UE in step 402 is replaced by the base station in this embodiment, so it is not repeated here. It should be noted that in this step, if KeNB is replaced by a key shared by the UE and the core network device, such as K AMF , K SEAF , K AKMA , K AF , K sNAF , K SF If any one of the above is true, the base station can also obtain the corresponding key in advance. There is no limitation on the way the base station obtains the key.

[0209] Among them, the messages between the base station and the SF may be forwarded through the physical interface of the AMF.

[0210] Based on the first and second embodiments, the sensing process between the UE and the base station may include: the base station modulating the sensing signaling using the previously obtained random sequence ID number, the modulation process being consistent with the prior art; the base station transmitting a downlink PRS sensing signal; sensing the target's reflected sensing signal; and the UE demodulating the sensing signaling using the previously obtained random sequence ID number, the demodulation process being consistent with the prior art. The UE returns the sensing data to the AMF, which may be forwarded by the base station.

[0211] In the third embodiment, the first device is a UE, and a key derivation method is used to generate a sequence ID parameter. For example, referring to FIG6 :

[0212] Step 601 is the same as step 401 and will not be described in detail. This step may be optional, that is, step 602 may be directly executed without executing step 601.

[0213] Step 602: SF returns the sensing assistance data (i.e., first information) to the UE. The sensing assistance data is used by the UE to determine the calculation parameters, which are used to calculate the sequence generation parameters (sequence ID) in combination with the shared key. In this embodiment, The range of SequenceID is {0...2^32-1}. Ksf can also be replaced by any type of key mentioned in the above embodiment, for example, it can be replaced by KeNB, NH, K RRCINT ,K RRCENC ,K UP INT ,K UPENC Any one of the above, or, can be replaced by K AMF , K SEAF , K AKMA , K AF , K sNAF , K SF And so on, any one of them, no exhaustive or repeated explanation is given here.

[0214] In the fourth embodiment, the first device is a base station, and a key derivation method is used to generate a sequence ID parameter. For example, referring to FIG. 7 :

[0215] Step 701 is the same as step 501 and will not be described in detail. This step may be optional, that is, step 701 may not be performed and step 702 may be performed directly.

[0216] Step 702: The SF returns the sensing assistance data (i.e., the first information) to the base station. The sensing assistance data is used by the base station to determine the calculation parameters, which are used to calculate the sequence generation parameters (sequence ID) in combination with the shared key. In this embodiment, The range of SequenceID is {0...2^32-1}. Ksf can also be replaced by any type of key mentioned in the above embodiment, for example, it can be replaced by KeNB, NH, K RRCINT ,K RRCENC ,K UP INT ,K UPENC Any one of the above, or, can be replaced by K AMF , K SEAF , K AKMA , K AF , K sNAF , K SF It should be noted that in this step, if Ksf is replaced with the key shared by the UE and the core network device, such as K AMF , K SEAF , K AKMA , K AF , K sNAF , K SF If any one of the above is true, the base station can also obtain the corresponding key in advance. There is no limitation on the way the base station obtains the key.

[0217] The solution provided in this embodiment can send configuration information to the first device, enabling the first device to determine how to generate sequence generation parameters for downlink perception signals using a key shared by the first and second devices. This allows the parameter range of the sequence generation parameters for the downlink perception signals to be changed. Furthermore, only the first and second devices can access the specific contents of the sequence generation parameters; other devices cannot obtain these parameters. Furthermore, only the receiving end in the first and second devices can correctly receive and measure the downlink perception signals generated based on these sequence generation parameters, thereby improving the security of the downlink perception signals themselves and ensuring the security of the perception scenario.

[0218] Furthermore, the solution provided in this embodiment increases the range of optional parameters for generating the PRS sequence without changing the sequence generation method, ensuring high compatibility with existing protocols. By increasing the range of optional parameters for generating the PRS sequence, the overall confidentiality space of the PRS signal is increased, reaching 128 bits. Using a key derivation approach to generate the Sequence ID parameter, compared to using a random number, eliminates the need to transmit the random number in high-level PRS configuration messages, directly utilizing existing keys for greater efficiency.

[0219] FIG8 is a schematic diagram of the composition structure of a first device according to an embodiment of the present application, including:

[0220] The communication unit 801 is configured to receive first information, where the first information is used to determine a method for obtaining a sequence generation parameter corresponding to a downlink perception signal based on a shared key, where the shared key is shared by the first device and the second device.

[0221] As shown in FIG8 , the first device further includes:

[0222] The processing unit 802 is configured to extract a plurality of bits from the shared key based on the first information, and generate a sequence generation parameter corresponding to the downlink perception signal based on the plurality of bits.

[0223] The first information is used to indicate at least one of the following: a start bit of the shared key to be intercepted; an end bit of the shared key to be intercepted; a number of bits of the shared key to be intercepted; or an interception rule of the shared key.

[0224] The processing unit is configured to determine a calculation parameter based on the first information, and calculate a sequence generation parameter corresponding to the downlink perception signal based on the shared key and the calculation parameter.

[0225] The first information includes one of the following: the calculation parameter; and range-related information corresponding to the sequence generation parameter, where the range-related information corresponding to the sequence generation parameter is used to determine the calculation parameter.

[0226] The range-related information corresponding to the sequence generation parameter includes one of the following: a value range corresponding to the sequence generation parameter, and a value range indicator corresponding to the sequence generation parameter.

[0227] The first information also includes an identifier of the shared key.

[0228] The shared key is one of the following: a first key shared by the first device and the second device, wherein the first key includes one of the following: an access layer key, an access layer security basic key, a next hop key NH, a physical layer key; and is calculated based on the first key.

[0229] The communication unit is configured to receive the shared key.

[0230] The shared key is calculated based on a second key shared by the first device and the core network device.

[0231] The first device is an access network device that sends the downlink perception signal, and the second device is a terminal that receives an echo signal of the downlink perception signal.

[0232] The first device is a terminal that receives an echo signal of the downlink perception signal, and the second device is an access network device that sends the downlink perception signal.

[0233] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned communication method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the device can be found in the corresponding description in the above-mentioned method embodiment, which will not be repeated here. It should be noted that the functions described by each module (sub-module, unit or component, etc.) in the device of the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).

[0234] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0235] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0236] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method performed by a first device, comprising: Receiving first information, where the first information is used to determine a manner of obtaining sequence generation parameters corresponding to a downlink sensing signal based on a shared key, and the shared key is shared by the first device and a second device.

2. The method according to claim 1, wherein, The method further comprises: Intercepting a plurality of bits from the shared key based on the first information, and generating sequence generation parameters corresponding to the downlink sensing signal based on the plurality of bits.

3. The method according to claim 2, wherein, The first information is used to indicate at least one of the following: The starting bit of the interception of the shared key; The ending bit of the interception of the shared key; The number of bits intercepted from the shared key; The interception rule of the shared key.

4. The method according to claim 1, wherein, The method further comprises: Determining calculation parameters based on the first information, and calculating sequence generation parameters corresponding to the downlink sensing signal based on the shared key and the calculation parameters.

5. The method according to claim 4, wherein The first information includes one of the following: The calculation parameters; Range-related information corresponding to the sequence generation parameters, where the range-related information corresponding to the sequence generation parameters is used to determine the calculation parameters.

6. The method according to claim 5, wherein, The range-related information corresponding to the sequence generation parameters includes one of the following: the value range corresponding to the sequence generation parameters, the value range indicator corresponding to the sequence generation parameters.

7. The method according to any one of claims 1-6, wherein, The first information further includes an identifier of the shared key.

8. The method according to any one of claims 1-7, wherein, The shared key is one of the following: A first key shared by the first device and the second device, where the first key includes one of the following: an access stratum key, an access stratum security base key, a next-hop key NH, a physical layer key; Calculated based on the first key.

9. The method according to any one of claims 1-7, wherein, The method further comprises: Receiving the shared key.

10. The method according to any one of claims 1-7, wherein, The shared key is calculated based on a second key shared by the first device and a core network device.

11. The method according to any one of claims 1-9, wherein, The first device is an access network device that sends the downlink sensing signal, and the second device is a terminal that receives an echo signal of the downlink sensing signal.

12. The method according to any one of claims 1-10, wherein, The first device is a terminal that receives an echo signal of the downlink sensing signal, and the second device is an access network device that sends the downlink sensing signal.

13. A first device, comprising: A communication unit, configured to receive first information, where the first information is used to determine a manner of obtaining sequence generation parameters corresponding to a downlink sensing signal based on a shared key, and the shared key is shared by the first device and a second device.

14. The first device according to claim 13, wherein, The first device further comprises: a processing unit, configured to intercept a plurality of bits from the shared key based on the first information, and generate sequence generation parameters corresponding to the downlink sensing signal based on the plurality of bits.

15. The first device according to claim 14, wherein, The first information is used to indicate at least one of the following: the starting bit of the interception of the shared key; the ending bit of the interception of the shared key; the number of bits intercepted from the shared key; the interception rule of the shared key.

16. The first device according to claim 13, wherein, The first device further comprises: a processing unit, configured to determine calculation parameters based on the first information, and calculate sequence generation parameters corresponding to the downlink sensing signal based on the shared key and the calculation parameters.

17. The first device according to claim 16, wherein, The first information includes one of the following: the calculation parameter; range-related information corresponding to the sequence generation parameter, where the range-related information corresponding to the sequence generation parameter is used to determine the calculation parameter.

18. The first device according to claim 17, wherein, The range-related information corresponding to the sequence generation parameter includes one of the following: the value range corresponding to the sequence generation parameter, the value range indicator corresponding to the sequence generation parameter.

19. The first device according to any one of claims 13-18, wherein, The first information further includes an identifier of the shared key.

20. The first device according to any one of claims 13-19, wherein, The shared key is one of the following: a first key shared by the first device and the second device, where the first key includes one of the following: an access stratum key, an access stratum security fundamental key, a next-hop key NH, a physical layer key; calculated based on the first key.

21. The first device according to any one of claims 13-19, wherein, The communication unit is configured to receive the shared key.

22. The first device according to any one of claims 13-19, wherein, The shared key is calculated based on a second key shared by the first device and a core network device.

23. The first device according to any one of claims 13-21, wherein The first device is an access network device that sends the downlink sensing signal, and the second device is a terminal that receives an echo signal of the downlink sensing signal.

24. The first device according to any one of claims 13-22, wherein, The first device is a terminal that receives an echo signal of the downlink sensing signal, and the second device is an access network device that sends the downlink sensing signal.

Images