Timing and synchronization techniques for secure networks

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can monitor a set of time-frequency resources for one or more cell detection signals (CDSs) associated with a pseudorandom sequence, wherein the pseudorandom sequence and the set of time-frequency resources are indicated by an output of a pseudorandom function (PRF) based on a timing parameter, a cell identifier (ID), and a shared key. Thus, the UE can communicate with a network entity via a cell associated with the cell ID based on receiving the one or more CDSs. The UE can also exchange one or more messages with the network entity and can perform a time calibration procedure based on the one or more messages and a delay threshold of the UE. The one or more messages can indicate an ID of the UE, a cryptographic number, a time interval, or a combination thereof.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 948,706, filed by Bai et al. on September 20, 2022, entitled “TIMING AND SYNCHRONIZATION TECHNIQUES FOR SECURE NETWORKS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including timing and synchronization techniques for secure networks. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE).

[0005] Some wireless communication systems, such as military or tactical networks, may be vulnerable to attack from external threats. Conventional mechanisms for improving the overall security of such systems may be associated with higher costs and hardware requirements, which may not be suitable for some deployments. Summary of the invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses that support timing and synchronization techniques for secure networks.For example, the described techniques may improve the security of communications between user equipment (UE) and network entities in a wireless communication system.

[0007] According to various aspects of the present disclosure, a UE may monitor a set of time-frequency resources to find one or more cell detection signals (CDS) associated with a pseudo-random sequence. The set of time-frequency resources and the pseudo-random sequence may be indicated by an output of a pseudo-random function (PRF) based on a timing parameter, a cell identifier (ID), and a shared key. The UE may communicate with a network entity via a cell associated with a cell ID based on monitoring the set of time-frequency resources to find one or more CDS.

[0008] Additionally or alternatively, the UE may send a first message indicating the UE's ID and the first encrypted number. The UE may receive a second message in response to the first message, wherein the second message indicates the UE's ID, the first time interval, and the second encrypted number. The UE may perform a time calibration procedure based on the second message, the second time interval between the reception of the second message and the transmission of the first message, and the UE's delay threshold.

[0009] A method for wireless communication at a UE is described. The method may include monitoring a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The method may also include communicating with a network entity via a cell associated with the cell ID based on monitoring the set of time-frequency resources to find the one or more CDSs.

[0010] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to enable the device to monitor a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The instructions may also be executable by the processor to enable the device to communicate with a network entity via a cell associated with the cell ID based on monitoring the set of time-frequency resources to find the one or more CDSs.

[0011] Another apparatus for wireless communication at a UE is described. The apparatus may include a component for monitoring a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The apparatus may also include a component for communicating with a network entity via a cell associated with the cell ID based on monitoring the set of time-frequency resources to find the one or more CDSs.

[0012] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: monitor a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The instructions can also be executed by the processor to communicate with a network entity via a cell associated with the cell ID based on monitoring the set of time-frequency resources to find the one or more CDSs.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining two or more bit sequences based on making two or more calls to the PRF.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: generating the pseudo-random sequence and resource location information by aggregating the two or more bit sequences, wherein the resource location information indicates the time-frequency resource set.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a first pseudo-random sequence and a first frequency position at a first time.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a second pseudo-random sequence and second frequency position information at a second time, wherein the duration between the first time and the second time corresponds to the periodicity of the one or more CDSs.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a plurality of bits indicating one or more symbol positions and physical resource block (PRB) positions to monitor for the one or more CDSs.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, monitoring the time-frequency resource set may include operations, features, components, or instructions for performing the following operations: performing frequency-domain correlation analysis on multiple resource elements (REs) in the time-frequency resource set.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a plurality of cell groups associated with a corresponding plurality of cell group IDs.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: generating a pseudo-random output for each of the multiple cell groups based on the corresponding multiple cell group IDs, wherein the pseudo-random output includes a pseudo-random sequence and a set of time-frequency resource locations associated with one of the multiple cell groups.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: selecting a subset of the multiple cell groups based on monitoring the set of time-frequency resource locations associated with each of the multiple cell groups.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: generating a pseudo-random output for each cell in the subset of the multiple cell groups, wherein the pseudo-random output includes a pseudo-random sequence and a set of time-frequency resource locations associated with the cells in the subset of the multiple cell groups.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more CDSs include a primary CDS (P-CDS) time division multiplexed (TDM) with a secondary CDS (S-CDS).

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a pseudo-random cell ID that is a function of the shared key, a physical cell identifier (PCID) associated with the cell of the network entity, and a timestamp associated with the generation of the pseudo-random cell ID, wherein the output of the pseudo-random function is based on the pseudo-random cell ID.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timestamp indicates a time slot, a system frame number (SFN), or a coordinated universal time (UTC) associated with generation of the pseudo-random cell ID.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing a Boolean operation on one or more least significant bits (LSBs) of the pseudo-random output and the PCID associated with the cell of the network entity, wherein generating the pseudo-random cell ID is based on a result of the Boolean operation.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating the output of the PRF based on a time drift threshold of the UE, wherein the output indicates a pseudo-random bit sequence and a set of time-frequency resource locations.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for monitoring the set of time-frequency resource locations for one or more timing synchronization signals (TSS) indicative of the pseudo-random bit sequence.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining absolute timing information based on measuring the one or more TSSs, wherein the timing parameter is based on the absolute timing information.

[0030] A method for wireless communication at a network entity is described. The method may include sending one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The method may also include communicating with a UE via a cell associated with the cell ID based on sending the one or more CDSs via the set of time-frequency resources.

[0031] A device for wireless communication at a network entity is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to send one or more CDSs associated with a pseudo-random sequence via a time-frequency resource set, wherein the pseudo-random sequence and the time-frequency resource set are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The instructions may also be executable by the processor to cause the device to communicate with a UE via a cell associated with the cell ID based on sending the one or more CDSs via the time-frequency resource set.

[0032] Another apparatus for wireless communication at a network entity is described. The apparatus may include means for sending one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The apparatus may also include means for communicating with a UE via a cell associated with the cell ID based on sending the one or more CDSs via the set of time-frequency resources.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to: send one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The instructions can also be executed by the processor to communicate with a UE via a cell associated with the cell ID based on sending the one or more CDSs via the set of time-frequency resources.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for acquiring absolute timing information via a global navigation satellite system (GNSS), wherein the timing parameters are based on the absolute timing information.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the one or more CDSs may include operations, features, components, or instructions for performing the following operations: sending the one or more CDSs via two or more carrier frequencies according to a frequency hopping communication scheme.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each cell of the network entity may be associated with a different pseudo-random cell ID.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: inputting the shared key and seed parameters into the pseudo-random function, the seed parameters comprising an absolute time bit sequence, a frequency bit sequence, a PCID bit sequence, a time-specific parameterized bit sequence, or a combination thereof, wherein the output of the PRF indicates the pseudo-random sequence and the time-frequency resource set.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a pseudo-random cell ID for the cell based on the shared key, the PCID of the cell of the network entity, and a timestamp associated with the generation of the pseudo-random cell ID, wherein the output of the PRF is based on the pseudo-random cell ID.

[0039] A method for wireless communication at a UE is described. The method may include sending a first message indicating an ID of the UE and a first encryption number. The method may also include receiving a second message indicating the ID of the UE, a first time interval, and a second encryption number in response to the first message. The method may also include performing a time calibration procedure based on the second message, a second time interval between the receipt of the second message and the transmission of the first message, and a delay threshold of the UE.

[0040] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to send a first message indicating an ID of the UE and a first encryption number. The instructions may also be executable by the processor to cause the device to receive a second message indicating the ID of the UE, a first time interval, and a second encryption number in response to the first message. The instructions may also be executable by the processor to cause the device to perform a time calibration procedure based on the second message, a second time interval between the reception of the second message and the transmission of the first message, and a delay threshold of the UE.

[0041] Another apparatus for wireless communication at an IE is described. The apparatus may include means for sending a first message indicating an ID of the UE and a first encryption number. The apparatus may also include means for receiving a second message indicating the ID of the UE, a first time interval, and a second encryption number in response to the first message. The apparatus may also include means for performing a time calibration procedure based on the second message, a second time interval between the receipt of the second message and the transmission of the first message, and a delay threshold of the UE.

[0042] A non-transitory computer-readable medium storing code for wireless communication at an IE is described. The code may include instructions that can be executed by a processor to: send a first message indicating an ID of the IE and a first encryption number. The instructions can also be executed by the processor to receive a second message indicating the ID of the UE, a first time interval, and a second encryption number in response to the first message. The instructions can also be executed by the processor to perform a time calibration procedure based on the second message, a second time interval between the reception of the second message and the transmission of the first message, and a delay threshold of the IE.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the time calibration procedure may include operations, features, components, or instructions for performing the following operations: determining that the duration of the second time interval is less than the sum of the delay threshold and the duration of the first time interval.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the time calibration procedure may include operations, features, components, or instructions for performing the following operations: updating one or more time settings of the UE based on a timestamp associated with sending the second message and a timestamp associated with receiving the second message.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the time calibration procedure may include operations, features, components, or instructions for performing the following operations: suppressing performance of a timing adjustment based on determining that the duration of the second time interval is greater than the sum of the delay threshold and the duration of the first time interval, wherein the first time interval corresponds to the duration between sending the second message and receiving the first message.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the second message may include operations, features, components, or instructions for performing the following operations: receiving an indication of an absolute time associated with the transmission of the second message, a subframe associated with the transmission of the second message, or both, wherein performing the time calibration procedure is based on the indication.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message includes a physical uplink shared channel (PUSCH) transmission encrypted using a first pseudo-random sequence, and the second message includes a physical downlink shared channel (PDSCH) transmission encrypted using a second pseudo-random sequence.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the time calibration procedure may include operations, features, components, or instructions for performing the following operations: determining that the product of a scaling factor and the duration of the first time interval is less than the delay threshold, wherein the scaling factor is based on an error rate associated with a local oscillator of the IE.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the time calibration procedure may include operations, features, components, or instructions for performing the following operations: performing a time adjustment based on a timestamp associated with sending the second message and a timestamp associated with receiving the second message.

[0050] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: transitioning from a non-synchronized timing (NT) state to a synchronized timing (T) state after executing the time calibration procedure, wherein the UE initiates the time calibration procedure in response to entering the NT state.

[0051] A method for wireless communication at a network entity is described. The method may include receiving a first message indicating an ID of a UE and a first encryption number. The method may also include performing an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The method may also include sending a second message indicating the ID of the UE, a time interval, and a second encryption number in response to the first message and based on a result of the authentication procedure.

[0052] A device for wireless communication at a network entity is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to receive a first message indicating an ID of a UE and a first encrypted number. The instructions may also be executable by the processor to cause the device to perform an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The instructions may also be executable by the processor to cause the device to send a second message indicating the ID of the IE, a time interval, and a second encrypted number in response to the first message and based on the result of the authentication procedure.

[0053] Another apparatus for wireless communication at a network entity is described. The apparatus may include a component for receiving a first message indicating an ID of an IE and a first encryption number. The apparatus may also include a component for performing an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The apparatus may also include a component for sending a second message indicating the ID of the UE, a time interval, and a second encryption number in response to the first message and based on the result of the authentication procedure.

[0054] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to: receive a first message indicating an ID of a UE and a first encrypted number. The instructions can also be executed by the processor to perform an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The instructions can also be executed by the processor to send a second message indicating the ID of the UE, a time interval, and a second encrypted number in response to the first message and based on a result of the authentication procedure.

[0055] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second message may include operations, features, components, or instructions for performing the following operations: sending an indication of a pseudo-random key to be used to encrypt subsequent messages between the UE and the network entity.

[0056] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the authentication procedure may include operations, features, components, or instructions for obtaining a shared key based on the credential information associated with the UE.

[0057] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the authentication procedure may include operations, features, components, or instructions for verifying a cryptographic signature of the first message based on the shared key.

[0058] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for exchanging one or more messages with the UE to obtain a shared key before receiving the first message. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] Figure 1 and Figure 2 An example of a wireless communication system supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is illustrated.

[0060] Figure 3 An example of a system diagram supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is illustrated.

[0061] Figure 4 An example of a resource graph supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is illustrated.

[0062] Figures 5 to 7 An example of a communication timeline supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is illustrated.

[0063] Figure 8 and Fig. 9 An example of a process flow supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is illustrated.

[0064] Fig.10 and Fig.11 A block diagram of a device supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is shown.

[0065] Fig.12 A block diagram of a communications manager supporting timing and synchronization techniques for a secure network is shown in accordance with one or more aspects of the present disclosure.

[0066] Fig.13 A diagram of a system including devices supporting timing and synchronization techniques for a secure network is shown in accordance with one or more aspects of the present disclosure.

[0067] Fig.14 and Fig.15 A block diagram of a device supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is shown.

[0068] Fig.16 A block diagram of a communications manager supporting timing and synchronization techniques for a secure network is shown in accordance with one or more aspects of the present disclosure.

[0069] Fig.17 A diagram of a system including devices supporting timing and synchronization techniques for a secure network is shown in accordance with one or more aspects of the present disclosure.

[0070] Figures 18 to 21 A flow chart illustrating a method of supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0071] Wireless communications can be used in a variety of secure networks, such as military systems, law enforcement systems, critical industrial applications, and other tactical networks with relatively high security requirements. The synchronization and timing mechanisms used in some wireless communication systems may not be suitable for tactical networks (also known as secure networks) because these networks may be more susceptible to external threats (e.g., denial of service (DoS) attacks, eavesdropping attacks, replay attacks, etc.). For example, an attacking device may attempt to interfere with the communication between a user equipment (IE) in a secure network and a network entity by injecting noise into a target frequency range, thereby reducing the possibility that the IE can successfully communicate with the network entity within the target frequency range.

[0072] An attacking device (equivalently referred to as an attacker, threat agent, or threat actor) may also attempt to impersonate a network entity so that the UE connects to the attacking device (and shares data with the attacking device). Additionally or alternatively, the attacking device may use radio equipment to observe signals and extract information (such as device location or general activity level) from the observed signals. Some attacking devices may also use replay attacks to disrupt the timing of communications between two devices. For example, an attacking device may receive a signal from a UE at a first time and then resend the signal to a network entity at a later time to introduce a delay between the UE and the network entity. Secure networks may have stricter security regulations to prevent or otherwise mitigate such attacks. However, existing synchronization and cell acquisition procedures may not comply with these regulations.

[0073] Various aspects of the present disclosure support techniques for acquiring timing information and cell information in a secure network. For timing acquisition, the UE may use a bootstrap process that is not susceptible to replay attacks. In order to initiate the bootstrap process, the UE may send a first message (e.g., an encrypted challenge) to a network entity. The first message may indicate an identifier (ID) of the UE, a first time interval, and a first encrypted number (e.g., a random number). In response to the first message, the network entity may obtain credentials for the UE (e.g., from a core network) and respond with a second message (e.g., an encrypted response). The second message may indicate the UE's ID, the first time interval, and the second encrypted number. The UE may determine whether the second message has been tampered with (e.g., by an attacking device) based on information in the second message, a second time interval between the sending of the first message and the receiving of the second message, and a delay threshold of the UE.

[0074] After successfully acquiring the timing information, the UE may initiate a secure cell acquisition procedure by making one or more calls to a pseudo-random function (PRF) that depends on the timing input (the previously acquired timing information), the cell ID, and the shared key. The output of the PRF may indicate a pseudo-random sequence and the location of one or more time-frequency resources (e.g., symbol position and physical resource block (PRB) position). Thus, the UE may monitor the one or more time-frequency resources for a cell detection signal (CDS) indicating a pseudo-random sequence. Upon detecting the CDS, the UE may connect to the cell associated with the cell ID, thereby enabling the UE to perform cell acquisition in a secure manner.

[0075] Various aspects of the present disclosure may be implemented to achieve one or more of the following advantages. The described techniques may improve the reliability, security, and efficiency of timing and synchronization procedures between UEs and network entities in a secure network. More specifically, the described techniques may reduce the risk of replay attacks, impersonation attacks, and jamming attacks that disrupt communications between UEs and network entities, which may achieve greater communications reliability. In addition, various aspects of the present disclosure may enable UEs to perform cell acquisition and timing calibration without compromising the integrity of the secure network.

[0076] Various aspects of the present disclosure are first described in the context of wireless communication systems, system diagrams, resource diagrams, communication timelines, and process flows. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to timing and synchronization techniques for secure networks.

[0077] Figure 1 An example of a wireless communication system 100 supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0078] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0079] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0080] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. For another example, the node may be a network entity 105. For another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115.

[0081] In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different with respect to these examples. Similarly, references to UE 115, network entity 105, devices, equipment, computing systems, etc. may include disclosures of UE 115, network entity 105, devices, equipment, computing systems, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0082] In some examples, the network entities 105 may communicate with the core network 130 or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0083] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a giga-Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0084] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (Cv) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0085] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functions, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160.

[0086] Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170 such that DU 165 may support one or more layers of the protocol stack and RU 170 may support one or more different layers of the protocol stack. DU 165 may support one or more different cells (e.g., via one or more RU 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer may be performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interfaces). In some examples, midhaul communication links 162 or fronthaul communication links 168 may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by respective network entities 105 communicating via these communication links.

[0087] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) that is controlled (eg, scheduled) by a coupled IAB donor's DU 165 .

[0088] The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0089] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support timing and synchronization techniques for a secure network as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0090] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0091] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0092] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate carrier operation, user data, or other signaling.

[0093] The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive" or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0094] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element (RE) may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits indicated by each RE may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of REs (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0095] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each of which may have a specific duration, such as 10 milliseconds (ms). Each radio frame may be identified by a system frame number (SFN) that may range from 0 to 1023.

[0096] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0097] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0098] Physical channels may be multiplexed according to various techniques for communicating using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115.

[0099] For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of the control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for the control information format with a given payload size. The search space set may include: a common search space set configured for transmitting control information to multiple UEs 115, and a UE-specific search space set for transmitting control information to a specific UE 115.

[0100] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0101] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0102] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0103] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0104] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 kilohertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using the lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0105] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0106] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0107] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0108] According to various aspects of the present disclosure, the UE 115 may monitor a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence. The set of time-frequency resources and the pseudo-random sequence may be indicated by an output of a PRF based on timing parameters, a cell ID, and a shared key. The UE 115 may communicate with the network entity 105 via a cell associated with the cell ID based on monitoring the set of time-frequency resources to find one or more CDSs.

[0109] Additionally or alternatively, UE 115 may send a first message indicating an ID of UE 115 and a first encryption number. In response to the first message, UE 115 may receive a second message indicating an ID of UE 115, a first time interval, and a second encryption number. UE 115 may perform a time calibration procedure based on the second message, a second time interval between receipt of the second message and transmission of the first message, and a delay threshold of UE 115.

[0110] Various aspects of the wireless communication system 100 may be implemented to achieve one or more of the following advantages. Figure 1 The described techniques may enable UE 115 and network entity 105 to communicate with greater security, reduced interference, and improved reliability, among other benefits. For example, the timing and synchronization procedures described herein may enable one or both of UE 115 and network entity 105 to mitigate interference attacks, impersonation attacks, replay attacks, and eavesdropping attacks from external devices, which may increase the likelihood of successful communication between UE 115 and network entity 105.

[0111] Figure 2An example of a wireless communication system 200 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100 or be implemented by them. For example, the wireless communication system 200 may include UE 115-a, UE 115-b, UE 115-c, and network entity 105-a, which may be reference Figure 1 Examples of corresponding devices described. The wireless communication system 200 (a tactical or high-security network) may also include an attack device 205 (equivalently referred to as a jamming or eavesdropping device) that attempts to monitor or disrupt communications between the network entity 105-a and the UE 115.

[0112] The wireless communication system 200 may be an example of a secure or tactical network deployed in a hostile area, such as a base or conflict zone, with a buffer zone between the secure network and other networks. Figure 2 The secure network depicted in the example of may be used by a military organization in a hostile environment where hostile forces attempt to disrupt the network or observe network behavior to extract relevant information. The wireless communication system 200 may include various devices commissioned or deployed by a military organization, such as UE 115 and network entity 105-a.

[0113] In some cases, the attack device 205 may impersonate the network entity 105-a by replaying (retransmitting) a signal from the network entity 105-a. The communication between the network entity 105-a and the UE 115 may also be susceptible to sequence-specific interference. To mitigate such interference, the network entity 105-a may use a wider bandwidth or a different frequency (e.g., according to a frequency hopping scheme) to send a signal to the UE 115. Using a wider bandwidth and a frequency hopping scheme may reduce the likelihood of interference and signal detection. Additionally or alternatively, the network entity 105-a may use a cryptographically secure spreading sequence (e.g., a scrambling sequence, a spreading sequence, or a frequency hopping sequence) to send a signal.

[0114] In a replay attack, attacking device 205 may receive signal 230 from network entity 105-a at a first time and send signal 235 (a replay of signal 230) to UE 115-a at a later time, thereby disrupting the timing of communications between UE 115-a and network entity 105-a. In other words, signal 235 from attacking device 205 may introduce a timing error between UE 115-a and network entity 105-a. In some examples, UE 115 and network entity 105-a may communicate with each other by performing (as described in reference to FIG. 2 ). Figure 8 and Fig. 9 The initial handshake procedure described in is used to prevent or mitigate replay attacks to ensure that the two devices are synchronized in time.

[0115] For example, UE 115-b may send an indication of an encrypted challenge 220 to network entity 105-a. Upon receiving the encrypted challenge 220 from UE 115-b, network entity 105-a may retrieve credentials for UE 115-b (via the core network) and obtain a shared key to be used to encrypt subsequent messages between network entity 105-a and UE 115-b. Network entity 105-a may then send an encrypted response 225 to UE 115-b. UE 115-b may determine whether the encrypted response 225 is valid (e.g., whether the message has been tampered with) based on an error tolerance, a duration between the sending of the encrypted challenge 220 and the receiving of the encrypted response 225, and timing information in the encrypted response 225. If UE 115-b determines that the encrypted response 225 is valid, UE 115-b may obtain absolute timing based on the timing information in the encrypted response 225.

[0116] The UE 115 may also acquire absolute timing information by receiving a timing synchronization signal (TSS) 215 from the network entity 105-a and measuring the timing synchronization signal (TSS). When the UE 115 has acquired approximate timing information (e.g., with an error of less than 100ms), the TSS 215 may help reduce the timing uncertainty of the UE 115. Additionally or alternatively, the UE 115 may acquire absolute timing information via time domain synchronization or a global navigation satellite system (GNSS). Once the UE 115 has acquired this information, the UE 115 may perform a synchronization procedure to identify the cell of the network entity 105-a. More specifically, the UE 115 may identify the cell ID associated with the network entity 105-a by monitoring one or more pseudo-random time-frequency resources (e.g., symbols and PRBs) to find the CDS 210.

[0117] In some examples, the wireless communication system 200 may be associated with a high signal-to-noise ratio (SNR). To reduce the adverse effects of interference in such scenarios, the UE 115 and the network entity 105-a may use frequency hopping and randomization. In other examples, the UE 115 may use (see Figure 8 and Fig. 9 The UE 115 may use the bootstrapping mechanism described above to acquire timing information and encryption keys via interference-resistant communications associated with relatively low data rates. The UE 115 may use the bootstrapping mechanism when there are interfering or attacking devices in the wireless communication system 200.

[0118] When the attack device 205 is able to determine or identify the time-frequency resources for communication between the UE 115 and the network entity 105-a, the UE 115 can use steering. The steering subsystem described herein can use low data rate communication to reduce the impact of interference. The UE 115 can access the steering subsystem (without previous timing information) using UE-specific credentials provided via a universal subscriber identity module (SIM) or other means. Once the UE 115 has obtained the timing information and encryption keys, the UE 115 can communicate securely with the network entity 105-a.

[0119] The operating mode of UE 115 may change based on whether UE 115 has successfully completed the bootstrap process. For example, when UE 115-c does not have timing information (e.g., when UE 115-c is in a no timing (NT) state), UE 115-c may acquire timing information before accessing the network. UE 115-c may acquire timing via different mechanisms (e.g., bootstrap, TSS, GNSS). However, if the UE has acquired timing (e.g., if the UE is in a timing (T) state), UE 115-c may search for the cell ID of network entity 105-a and initiate a user plane connection with network entity 105-a by monitoring to find CDS210. In some cases, UE 115-c may transition between NT state (unsynchronized state) and T state (synchronized state).

[0120] For example, if UE 115-c cannot find a cell within a certain period of time (resulting in loss of synchronization), UE 115-c may revert to the NT state. UE 115-c may transition to the NT state based on other conditions or triggers (e.g., radio link failure). The complexity of the guidance subsystem may be based on various operating conditions. In some deployments, the guidance subsystem may be available only in a specified area. In such cases, UE 115-c may move to the specified area to obtain timing information (thereby reducing the complexity of the guidance subsystem). In other cases, if UE 115-c enters the NT state in a venue (e.g., relatively far away from a specified area), a more complex guidance subsystem may be used for implementation.

[0121] Figure 3 An example of a system diagram 300 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The system diagram 300 may implement or be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. For example, the system diagram 300 may be implemented by reference to Figure 1 and Figure 2 The described UE 115 implements. The system diagram 300 may include a CDS, which may be a reference Figure 2An example of CDS 210 is described. In system diagram 300, a UE may monitor a set of time-frequency resources based on the output of PRF 305 to look for a pseudo-random sequence.

[0122] exist Figure 3 In an example of FIG. 3 , a UE in a secure (tactical) network may input a cell ID 310, a timing parameter 315, and a shared key 320 into a PRF 305. The UE may monitor symbols 330 and PRBs 335 based on an output 325 of the PRF 305 to find a CDS. The UE may have access to the shared key 320, which is used to derive common randomness via the PRF 305. The shared key 320 may be unknown to an attacker and may be refreshed periodically. Devices in a secure network may be synchronized in time (e.g., using GNSS, TSS, a bootstrap subsystem, or some other mechanism). The UE may be configured with a set of channels (e.g., frequencies) on which cells may be found.

[0123] In some examples, the UE may obtain synchronization by measuring one or more synchronization signals (CDS and TSS). These synchronization signals may have characteristics that prevent or reduce the possibility of attacks from other devices. In order to mitigate replay attacks and DoS attacks, the pseudo-random sequence indicated by the synchronization signal may change over time. The synchronization signal may be sent at a pseudo-random time-frequency moment to mitigate burst interference. The synchronization signal may be sent using a relatively large bandwidth or frequency hopping to reduce the impact of narrowband interference.

[0124] In some examples, the two network entities may be configured to use different pseudo-random sequences. If the UE does not have accurate timing information, the UE may use the configured sequence to perform a time domain search. In some examples, the synchronization signal may have a periodicity of 20ms. In such examples, if the timing uncertainty of the UE is approximately 1 second (+ / -), the UE may test (use) one hundred different sequences. In some examples, if the UE is using narrowband radio frequency for time domain search, the UE may not be able to use frequency hopping (because the UE and the network may be using different frequency hopping configurations). Using fixed frequency locations may increase the adverse effects of narrowband interference.

[0125] The UE may use the CDS to find the cell ID (when timing and frequency are known). When this information is known, the CDS may not be limited to the narrowband search process for primary synchronization signal (PSS) and secondary synchronization signal (SSS) acquisition. The UE may be preconfigured with a CDS periodicity (e.g., every 10 ms). The UE may calculate a pseudo-random sequence for the corresponding time interval 360 based on the cell ID 310 and other input parameters. If the UE performs an exclusive OR (XOR) Boolean operation on the cell ID 310 and the pseudo-random sequence, an attacker can recover the cell ID 310 by XORing multiple cells together. The pseudo-random sequence may be used to determine the sequence (e.g., using orthogonal phase shift keying). Additionally or alternatively, the pseudo-random sequence may be used to determine the time domain and frequency domain position within the time interval 360 (e.g., 10 ms). The UE may determine such a position based on one or more constraints (e.g., TDM configuration). If frequency hopping is used, multiple time or frequency starting points may be obtained from the PRF 305.

[0126] In some cases, the subcarrier spacing of the CDS may be 15kHz. The CDS may span 14 PRBs (336 bits). There may be 140 possible symbol positions (7.13 bits). The starting PRB may range from PRB 0 to PRB 35 (5.12 bits). Therefore, the UE may call PRF 305 three times to obtain 384 bits. In some cases, more bits may be used (e.g., for repetition and cross-repetition frequency hopping). If the CDS is a one-step or one-time detection signal, the UE may test up to 1005 cell ID hypotheses to find the CDS. The UE may perform three PRF calls for each cell ID. The UE may perform frequency domain correlation analysis on 168 REs. In some examples, the UE may search within a limited time domain window (to take into account propagation delay). In some cases, the UE may reduce the number of hypotheses by using an approximate positioning position, preconfiguration, or some combination thereof. Similar to PSS and SSS, the overall complexity of CDS detection can be reduced by splitting the CDS into a primary CDS (P-CDS) and a secondary CDS (S-CDS).

[0127] Additionally or alternatively, the number of cell IDs may be reduced. Using fewer cell groups (e.g., 15 cell groups identified by cell ID mod15) may be unsafe because the same set of cells may send the same signal with a periodicity corresponding to the subcarrier spacing of the CDS. The safety of such a process may be improved by randomizing the cell groups over time. Subsequently, the UE may calculate the output of PRF 305. For example, the UE may obtain time, frequency, and sequence position based on time or cell groups. After calculating the output of the PRF, the UE may search for the corresponding signal (e.g., 15 signals for 15 cell groups) and select a certain number of cell groups (e.g., 2 cell groups) with the highest detection signal correlation. After this selection, the UE may calculate the PRF output for each cell in the selected group. In some examples, there may be a total of 67 cell IDs per cell group. TDM may be performed on the P-CDS and S-CDS CDS to avoid buffering (e.g., the P-CDS and S-CDS may be separated by at least 1ms). For example, the UE may divide the CDS periodicity (eg, 20 ms) into 2 segments (eg, 10 ms segments) and refrain from using the center 1 ms.

[0128] In some examples, the network entity may randomize the cell group (e.g., to improve security). When randomizing the cell group, the network entity may create a reversible randomized cell ID that depends on the current time. For example, the randomized cell ID at a given time may be a cell ID that depends on the actual cell ID and the parameter rN. ID =f(N ID , t; k), where t represents a time slot, SFN, Coordinated Universal Time (UTC) or any other timing parameter 315, k represents a shared key 320, and rN ID Refers to the current time. In some cases, the UE may obtain a pseudo-random sequence by invoking PRF 305 and XORing a certain number of least significant bits (LSBs) in the binary output with the cell ID 310. In some cases, if nearby cells are configured with different randomized cell IDs, the network entity may generate a pseudo-random permutation accordingly.

[0129] In some examples, the three sectors of the same network entity may use different cell IDs. The network entity may use equation N ID,1 =N ID mod 3, N ID,2 =N ID div 3, rN ID =3f(N ID，1 , t; k)+N ID，2 Different sectors (cells) of the same network entity may have the same N ID，2 and different NID，1 This mechanism can be extended to any number of cells (e.g., to prevent collisions between neighboring cells, the network may increase the value 3 to a different value).

[0130] In some examples, the network entity may generate a seed (or counter), which may be denoted as c. The seed may be based on the cell ID 310 and the timing parameters 315. The PRF 305 may take a shared key 320 (e.g., a key of any length) and a seed (e.g., a 128-bit seed or counter) as inputs. In some examples, the PRF 305 may take other inputs specified by the Advanced Encryption Standard (AES) or other encryption mechanisms. The PRF 305 may produce a bit sequence (e.g., 128 bits) in an output 325. A different seed may be used for each channel or signal generated. If the seed is reused, the PRF output may be the same, which may compromise the security of the system. Therefore, a seed may be calculated for each channel or signal.

[0131] In some examples, a 128-bit seed may be divided into multiple parts. For example, a 128-bit seed may be divided into a specified number of bits (represented by T) for absolute time 340 (e.g., a 1000 ms division) and a specified number of bits (M) for time-specific parameterization 355 (e.g., a 1000 ms specific parameterization). For the M bits, the device may generate randomness at different scales. Common randomness across 1000 ms (e.g., for a timing recovery signal) may produce one option (e.g., hypothesis, path, bucket). Common randomness across 10 ms (e.g., for the location of a CDS) may produce 100 options. There may be no common randomness per subframe. Common randomness per time slot (e.g., for subcarrier spacing up to 120 kHz) may produce 8000 options. When the total number of options is less than 8192 (13 bits), a mapping may be used to configure the device.

[0132] The UE may determine the number of blocks per option so that the number is less than 2 per option. 20 Blocks (2 per option 27 bits or 134Mb per option). Further partitioning may also be supported (e.g., blocks for demodulation reference signal (DMRS), physical downlink shared channel (PDSCH), synchronization). The partitioning of the 128-bit seed may include 27 bits per block in a given option, 13 bits per option, and 88 bits for the absolute time 340 in seconds (which may be in 10 18 The number of bits for absolute time 340 may be modified to support additional options or blocks per option. In some cases, cell ID 310 may be embedded in each option. Alternatively, cell ID 310 may be a separate field.

[0133] The shared key 320 (which may be pre-programmed) may be used for broadcast services and signals. However, the shared key 320 may also be modified to support unicast services and signals. In some cases, the shared key 320 may be used for broadcast services or signals to prevent (e.g., when the same CORESET is used for unicast and broadcast) physical downlink control channel (PDCCH) scrambling or frequency hopping. In some cases, the shared key 320 may support multiple frequencies (carrier aggregation). In such cases, the PRF seed may include frequency information 345. In some examples, the UE may be configured with multiple different frequencies (e.g., 10 frequencies). In such examples, the PRF seed may include a physical cell ID (PCID) 350.

[0134] Figure 4 An example of a resource graph 400 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The resource graph 400 may implement reference Figures 1 to 3 Aspects of any of the wireless communication systems or system diagrams described herein may be implemented by or in accordance with the present invention. For example, resource diagram 400 may be provided by reference to Figure 1 and Figure 2 The resource map 400 may include a CDS 405, which may be a reference Figure 2 The resource map 400 may also include a TSS 410, which may be a reference Figure 2 An example of a TSS 215 is described.

[0135] exist Figure 4 In the example of , the UE may perform timing and synchronization procedures based on the CDS 405 and the TSS 410. The network entity may send the CDS 405 using pseudo-random time-frequency resources (symbols and PRBs). The CDS 405 may include or otherwise indicate a pseudo-random sequence. The network entity may send the CDS 405 in a time interval 415 (e.g., 10 ms). Similarly, the network entity may send the TSS 410 in a time interval 420 (e.g., 1 s).

[0136] The UE may use TSS 410 to acquire more accurate timing (e.g., after being disconnected from GNSS for a relatively long time). The configuration of TSS 410 may be based on the maximum (threshold) time drift of the UE and the maximum complexity of the UE (in terms of simultaneous searches). For example, if the maximum drift of the UE is + / - 500ms, the UE may generate a random value associated with a current time window of 1s.

[0137] The random value may indicate a center frequency (e.g., a PRB), a time, and a pseudo-random sequence. The UE may search the identified time-frequency resources for a pseudo-random sequence, and may obtain timing information based on the identified pseudo-random sequence (in CDS 405). In some cases, all cells may use the same time and frequency resources to send the same TSS 410, which may introduce ambiguity and interference. To address these issues, the UE may be configured to monitor multiple TSSs (e.g., 3 TSSs) that may be in the same frequency range. In some examples, TSS 410 may be designed for 1 detection.

[0138] Figure 5 An example of a communication timeline 500 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The communication timeline 500 may be implemented with reference to Figures 1 to 4 Aspects of any of the described wireless communication systems, system diagrams, or resource diagrams may be implemented by or in accordance with one or more embodiments of the present invention. For example, the communication timeline 500 may include a UE 115-d and a network entity 105-b, which may be referenced to Figure 1 and Figure 2 The communication timeline 500 may also include an attack device 505, which may be a reference Figure 2 An example of an attack device 205 is described. Communications timeline 500 illustrates an example of a replay attack.

[0139] exist Figure 5 In the example of FIG. 1 , the network entity 105 - b may be configured to execute the following operations at time t 0 Signal 510 is sent to UE 115-d. Signal 510 may include timing information (e.g., the subframe at t 0 Attack device 505 may capture the waveform of signal 510 from network entity 105-b. 1 (t 0 +t 攻击 ), the attack device 505 may send a replayed signal 515 to the UE 115-d.

[0140] The attacking device 505 may delay 525 (t 攻击 ). The time delay 525 may include the time required for the attack device 505 to decode and re-encode the signal 510. The time delay 525 may also include any internal delays between components of the attack device 505. The replayed signal 515 may include timing information from the signal 510 (e.g., the subframe at t 0 start).

[0141] At time t 2 (t 0 +t 攻击+t 传播 ), UE 115-d may receive replayed signal 515. Replayed signal 515 may be a signal 510 with a propagation delay (t 传播 ). The timing information in the replayed signal 515 (e.g., the subframe at t 0 The timing error may be introduced at UE 115-d. For example, UE 115-d may determine that the subframe is at t 2 Instead of 0 begins, thereby disrupting the timing of communications between UE 115-d and network entity 105-b.

[0142] refer to Figure 5 The described techniques and operations may enable UE 115-d and network entity 105-b to detect and mitigate replay attacks performed by attack device 505. For example, UE 115-d and network entity 105-b may perform (see Figure 8 and Fig. 9 The UE 115-d and the network entity 105-b may perform a handshake procedure (described above) to confirm that the UE 115-d and the network entity 105-b are aligned in time. If a delay (caused by the attacking device 505) is detected during the handshake procedure, the UE 115-d may enter the NT state and attempt to reacquire accurate timing information via GNSS or TSS reception.

[0143] Figure 6 An example of a communication timeline 600 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The communication timeline 600 may be implemented with reference to Figures 1 to 5 Aspects of any of the described wireless communication systems, system diagrams, or resource diagrams may be implemented by or in accordance with one or more embodiments of the present invention. For example, the communication timeline 600 may include a UE 115-e and a network entity 105-c, which may be referenced by Figures 1 to 5 The communication timeline 600 may also include an attack device 605, which may be a reference Figure 2 Described example of attack device 205. Attack device 605-a and attack device 605-b may be connected via one or more wired or wireless links.

[0144] If the transmission from network entity 105-c has a relatively long duration (e.g., for communications with a relatively low data rate), attack device 605-a may perform early decoding of the transmission and perform a non-causal replayed transmission by re-encoding the decoded transmission. In some examples, attack device 605 may introduce non-causality into the transmission from network entity 105-c.

[0145] For example, UE 115-e may receive a message that appears to be from network entity 105-c before network entity 105-c sends the message. In other examples, attack device 605 may introduce non-causality into transmissions from UE 115-e to network entity 105-c. For example, network entity 105-c may receive a message that appears to be from UE 115-e before UE 115-e sends the message.

[0146] exist Figure 6 In the example of FIG. 1 , the network entity 105 - c may perform the following operations at time t 0 Signal 610 is sent to UE 115-e. Attacker device 605-a may intercept signal 610 and perform early decoding on signal 610. As a result, attacker device 605 may re-encode a portion 620 of the intercepted signal (e.g., the last few symbols of signal 610). Attacker device 605-b may send a signal including filler waveform 615 and intercepted and re-encoded portion 620 of signal 610.

[0147] Attacking device 605-b may perform an early termination of fill waveform 615 and thereafter initiate a non-causal retransmission of signal 610. 1 Initially, UE 115-e may receive filler waveform 615 and re-encoded portion 620 of signal 610 from attacking device 605. Therefore, due to the delay caused by attacking device 605, UE 115-e may obtain incorrect timing information. The maximum timing error in such a scenario may be given by T 最大 +(t 0 +t 1 )express.

[0148] Additionally or alternatively, UE 115-e may, at time t 2 105 - c may transmit signal 625. Attacker device 605 - b may intercept signal 625 from UE 115 - e, perform early decoding on signal 625, and re-encode the decoded portion of signal 625. Thus, attacker device 605 - a may transmit signal 630 including the decoded (and subsequently re-encoded) portion of signal 625. Network entity 105 - c may transmit signal 630 at time t 3 Reception of signal 630 begins, thereby introducing further delay between UE 115 - e and network entity 105 - c .

[0149] The techniques described herein may enable UE 115-e and network entity 105-c to detect and mitigate replay attacks performed by attack device 605. For example, UE 115-e and network entity 105-c may perform (see Figure 8 and Fig. 9The UE 115-e and the network entity 105-c may perform a handshake procedure (described in detail) to confirm that the UE 115-e and the network entity 105-c are aligned in time. If a delay (caused by the attacking device 605) is detected during the handshake procedure, the UE 115-e may enter the NT state and attempt to reacquire accurate timing information via GNSS or TSS reception.

[0150] Figure 7 An example of a communication timeline 700 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The communication timeline 700 may be implemented with reference to Figures 1 to 6 Aspects of any of the described wireless communication systems, system diagrams, resource diagrams, or communication timelines may be implemented by or may be implemented by the communication timeline 700. The communication timeline 700 may include a network entity 105-d, which may be a reference Figure 6 The communication timeline 700 may also include an attack device 705, which may be a reference Figures 2 to 6 Examples of corresponding devices described.

[0151] exist Figure 7 In the example of FIG. 1 , the network entity 105 - d may be configured to execute the following operations at time t 2 The signal (also referred to as a message or transmission) may span a duration 710. In some cases, the attacking device 705 may introduce a timing error by retransmitting the signal for a duration 715 that is longer than the duration 710. The duration 720 illustrates the accumulated error between the original transmission from the network entity 105-d and the subsequent retransmissions from the attacking device 705.

[0152] If the UE's local oscillator has an error of approximately + / - parts per million (PPM) Z, there may be an initial timing error of up to (1+2X) between the UE and the network entity 105-d. If X is relatively small, the UE may be able to acquire timing information with sufficient accuracy. If the UE detects a timing or frequency error greater than 2X, the UE may determine that the attack device 705 is tampering with communications between the UE and the network entity 105-d.

[0153] In order to mitigate the replay attack from the attacking device 705, t 1 (the time associated with the receipt of the encrypted challenge) and t 2 The maximum time between (the time associated with the sending of the encrypted response) imposes a limit because this duration can be scaled by the attacking device 705 up to (1+2X).

[0154] However, in some cases, the attacking device 705 may introduce a continuous drift that accumulates over time (e.g., duration 720), which may cause the UE to drift away from the timing of the network entity 105-d. The UE may repeatedly refer to Figure 8 and Fig. 9 The described techniques and operations to periodically confirm (re-establish) timing to the network entity 105 - d may reduce the likelihood of timing misalignment between the UE and the network entity 105 - d .

[0155] Figure 8 An example of a process flow 800 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The process flow 800 may be implemented with reference to Figures 1 to 7 Aspects of any of the described wireless communication systems, system diagrams, resource diagrams, or communication timelines may be implemented by or in any manner. For example, process flow 800 may include UE 115-f, network entity 105-e, and core network 805, which may be reference Figures 1 to 7 Examples of corresponding devices described. In the following description of process flow 800, operations between UE 115-f, network entity 105-e, and core network 805 may be added, omitted, or performed in a different order (relative to the exemplary order shown).

[0156] The UE 115-f may implement the process flow 800 to confirm or establish the accuracy of timing information at the UE 115-f. For example, the UE 115-f may determine that the UE 115-f is aligned in time with the network entity 105-e by performing a handshake procedure with the network entity 105-e.

[0157] At 810 (at time t 0 ), UE 115-f may send a first message to network entity 105-b. The first message may include a challenge indicating an encrypted number (e.g., a random number), an ID of UE 115-f (e.g., a temporary mobile subscriber identity (TMSI) or some other form of UE identification), and an encrypted signature. Network entity 105-e may send a first message to network entity 105-b at time t 1 Receive inquiries.

[0158] At 815, the network entity 105-e may request credential information associated with the UE 115-f from the core network 805 (using the ID of the UE 115-f). At 820, the core network 805 may provide the requested credential information to the network entity 105-e.

[0159] At 825 (t 2 ), the network entity 105-e may send a second message including a response to the challenge. The UE 115-f may 3The response from the network entity 105 - e may indicate the second encrypted number (random number), the ID of the UE 115 - f (e.g., UE_ID), the time interval between the reception of the first message and the sending of the second message (e.g., τ=(t 2 -t 1 )), encryption keys, encryption signatures, or a combination thereof.

[0160] The time interval (e.g., τ) between the receipt of the first message and the transmission of the second message may include RRH latency (if the RRH line is secure). The response (which may be a signed or encrypted response) may further indicate an absolute transmission time associated with the response (e.g., t 2 ), a subframe in which the network entity 105-e sends a response, a key for common randomness (to complete the bootstrapping process), or other information.

[0161] At 830, UE 115-f may examine the response and based on the second message, receipt of the second message (t 3 ) and the sending of the first message (t 0 ), a delay threshold of UE 115-f, or some combination thereof to determine whether to adjust one or more timing parameters. For example, UE 115-f may check the response and calculate Δt=t 3 -t 0 If the calculated delay is less than or equal to the delay threshold (Tmax), UE 115-f may set t 3 The actual timing is set to t 2 .

[0162] Therefore, UE 115-f may obtain a timing with an error between [0, Δt]. Depending on the delay threshold (error tolerance) of UE 115-f (which may be provided to UE 115-f), UE 115-f may determine that the response is valid and transition from the NT state to the T state (as shown in FIG. Figure 2 described).

[0163] Fig. 9 An example of a process flow 900 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is illustrated. The process flow 900 may be implemented with reference to Figures 1 to 8 Aspects of any of the described wireless communication systems, system diagrams, resource diagrams, communication timelines, or process flows may be implemented by or as described herein. For example, process flow 900 may include UE 115-g and network entity 105-f, which may be reference Figures 1 to 8Examples of corresponding devices described. In the following description of process flow 900, operations between the UE 115-g and the network entity 105-f may be added, omitted, or performed in a different order (relative to the exemplary order shown).

[0164] At 905, the UE 115-g and the network entity 105-f may perform an initial key exchange to obtain a common key. The UE 115-g and the network entity 105-f may omit or ignore any timing parameters signaled during the initial key exchange (since the timing cannot be trusted at this time). The network entity may obtain the common key from the core network or via any suitable key exchange mechanism.

[0165] The cryptographic signature can be used to verify that both devices have access to the public key. After the initial key exchange, the UE 115-g and the network entity 105-f may know each other, and additional steps may be implemented to prevent an attacking device from performing an early termination of the decoding (see reference Figure 6 described).

[0166] At 910 (t 0 ), UE 115-g may send a physical uplink shared channel (PUSCH) transmission (with rate matched or coded bits) scrambled using a sequence generated by the first PRF. Network entity 105-f may transmit at t 1 Receive the scrambled PUSCH transmission. At 915 (t 2 ), the network entity 105 - f may send a PDSCH transmission (with rate matched or decoded bits) scrambled using a sequence generated by a second PRF.

[0167] At 920, UE 115-g may transmit the scrambled PDSCH, receive the second message (t 3 ) and the sending of the first message (t 0 ) and the delay threshold of UE 115-g to determine whether to adjust one or more timing parameters. For example, UE 115-g may calculate Δt=t 3 -t 0 -τ and determine whether the time interval meets the delay threshold (T 最大 ).

[0168] Thus, the UE 115-g may obtain a timing with an error between [0, Δt]. Depending on a delay threshold or error tolerance of the UE 115-g (which may be provided to the UE 115-g), the UE 115-g may (e.g., by setting t 3 The actual timing is set to t 2 ) adjusts one or more timing parameters and transitions from the NT state to the T state (as referenced Figure 2 described).

[0169] Fig.10 A block diagram 1000 of a device 1005 supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The device 1005 can be an example of aspects of a UE 115 as described herein. The device 1005 can include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0170] Receiver 1010 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to timing and synchronization techniques for secure networks). The information may be communicated to other components of device 1005. Receiver 1010 may utilize a single antenna or multiple antennas.

[0171] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to timing and synchronization techniques for secure networks), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or multiple antennas.

[0172] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the timing and synchronization techniques for secure networks as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0173] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0174] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0175] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0176] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE (device 1005). For example, the communication manager 1020 may be configured to or otherwise support a component for monitoring a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The communication manager 1020 may be configured to or otherwise support a component for communicating with a network entity via a cell associated with a cell ID based on monitoring the set of time-frequency resources to find one or more CDSs.

[0177] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE (device 1005). For example, the communication manager 1020 may be configured to or otherwise support a component for sending a first message indicating the ID of the UE and the first encrypted number. The communication manager 1020 may be configured to or otherwise support a component for receiving a second message indicating the ID of the UE, the first time interval, and the second encrypted number in response to the first message. The communication manager 1020 may be configured to or otherwise support a component for performing a time calibration procedure based on the second message, the second time interval between the reception of the second message and the transmission of the first message, and the delay threshold of the UE.

[0178] By including or configuring a communication manager 1020 according to examples as described herein, a device 1005 (e.g., a processor controlling or otherwise coupled to a receiver 1010, a transmitter 1015, a communication manager 1020, or a combination thereof) may support techniques for reducing power consumption by reducing the number of retransmissions performed or requested by the device 1005. For example, the techniques described herein may reduce the likelihood that a replay attack will adversely affect communications between the device 1005 and other devices in a secure network, thereby increasing the likelihood that the device 1005 will successfully receive transmissions from those devices. As a result, the device 1005 may request fewer retransmissions, which may result in reduced power consumption at the device 1005 (e.g., by enabling the device 1005 to remain in a sleep mode for a longer duration).

[0179] Fig.11 A block diagram 1100 of a device 1105 supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or IE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0180] The receiver 1110 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to timing and synchronization techniques for secure networks). The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or multiple antennas.

[0181] The transmitter 1115 may provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to timing and synchronization techniques for secure networks), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or multiple antennas.

[0182] Device 1105 or its various components may be examples of components for performing various aspects of timing and synchronization techniques for secure networks as described herein. For example, communication manager 1120 may include resource monitoring component 1125, communication component 1130, message sending component 1135, message receiving component 1140, time calibration component 1145, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0183] According to the examples disclosed herein, the communication manager 1120 can support wireless communication at the UE (device 1105). The resource monitoring component 1125 can be configured to or otherwise support a component for monitoring a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of the PRF based on a timing parameter, a cell ID, and a shared key. The communication component 1130 can be configured to or otherwise support a component for communicating with a network entity via a cell associated with a cell ID based on monitoring the set of time-frequency resources to find one or more CDSs.

[0184] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE (device 1105). The message sending component 1135 may be configured to or otherwise support a component for sending a first message indicating the ID of the UE and the first encrypted number. The message receiving component 1140 may be configured to or otherwise support a component for receiving a second message indicating the ID of the UE, the first time interval, and the second encrypted number in response to the first message. The time calibration component 1145 may be configured to or otherwise support a component for performing a time calibration procedure based on the second message, the second time interval between the reception of the second message and the transmission of the first message, and the delay threshold of the UE.

[0185] Fig.12 A block diagram 1200 of a communication manager 1220 supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of the timing and synchronization techniques for a secure network as described herein. For example, the communication manager 1220 may include a resource monitoring component 1225, a communication component 1230, a message sending component 1235, a message receiving component 1240, a time calibration component 1245, a sequence generation component 1250, a frequency correlation component 1255, a cell identification component 1260, a duration determination component 1265, a state transition component 1270, a Boolean execution component 1275, an absolute timing component 1280, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0186] According to examples disclosed herein, the communication manager 1220 can support wireless communication at the UE. The resource monitoring component 1225 can be configured to or otherwise support components for monitoring a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of the PRF based on a timing parameter, a cell ID, and a shared key. The communication component 1230 can be configured to or otherwise support components for communicating with a network entity via a cell associated with a cell ID based on monitoring the set of time-frequency resources to find one or more CDSs.

[0187] In some examples, the sequence generation component 1250 may be configured or otherwise support components for obtaining two or more bit sequences based on two or more calls to the PRF. In some examples, the sequence generation component 1250 may be configured or otherwise support components for generating a pseudo-random sequence and resource location information by aggregating two or more bit sequences, wherein the resource location information indicates a set of time-frequency resources.

[0188] In some examples, the sequence generation component 1250 may be configured or otherwise support components for generating a first pseudo-random sequence and first frequency position information at a first time. In some examples, the sequence generation component 1250 may be configured or otherwise support components for generating a second pseudo-random sequence and second frequency position information at a second time, wherein the duration between the first time and the second time corresponds to the periodicity of one or more CDSs.

[0189] In some examples, sequence generation component 1250 may be configured or otherwise support means for generating a plurality of bits indicating one or more symbol positions and PRB positions to monitor for one or more CDSs.

[0190] In some examples, to support monitoring of a set of time-frequency resources, frequency correlation component 1255 may be configured as or otherwise support components for performing frequency domain correlation analysis on multiple REs in the set of time-frequency resources.

[0191] In some examples, the cell identification component 1260 may be configured or otherwise support components for identifying a plurality of cell groups associated with respective cell group IDs. In some examples, the sequence generation component 1250 may be configured or otherwise support components for generating a pseudo-random output for each of the plurality of cell groups based on the respective plurality of cell group IDs, wherein the pseudo-random output includes a pseudo-random sequence and a set of time-frequency resource locations associated with a cell group in the plurality of cell groups.

[0192] In some examples, the cell identification component 1260 may be configured to or otherwise support components for selecting a subset of the plurality of cell groups based on monitoring a set of time-frequency resource locations associated with each of the plurality of cell groups. In some examples, the sequence generation component 1250 may be configured to or otherwise support components for generating a pseudo-random output for each cell in the subset of the plurality of cell groups, wherein the pseudo-random output includes a pseudo-random sequence and a set of time-frequency resource locations associated with the cells in the subset of the plurality of cell groups. In some examples, the one or more CDSs include a P-CDS that is TDMed with an S-CDS.

[0193] In some examples, sequence generation component 1250 can be configured to or otherwise support components for generating a pseudo-random cell ID that is a function of a shared key, a PCID associated with a cell of a network entity, and a timestamp associated with the generation of the pseudo-random cell ID, wherein an output of the pseudo-random function is based on the pseudo-random cell ID. In some examples, the timestamp indicates a time slot, SFN, or UTC associated with the generation of the pseudo-random cell ID.

[0194] In some examples, Boolean execution component 1275 may be configured as or otherwise support means for performing a Boolean operation on one or more LSBs of the pseudo-random output and a PCID associated with a cell of the network entity, wherein generating the pseudo-random cell ID is based on a result of the Boolean operation.

[0195] In some examples, sequence generation component 1250 may be configured or otherwise support means for generating an output of a PRF based on a time drift threshold of the UE, wherein the output indicates a pseudo-random bit sequence and a set of time-frequency resource locations. In some examples, resource monitoring component 1225 may be configured or otherwise support means for monitoring a set of time-frequency resource locations to find one or more TSSs indicating a pseudo-random bit sequence.

[0196] In some examples, absolute timing component 1280 can be configured or otherwise support means for acquiring absolute timing information based on measuring one or more TSSs, wherein the timing parameters are based on the absolute timing information.

[0197] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. The message sending component 1235 may be configured to or otherwise support a component for sending a first message indicating the ID of the UE and the first encrypted number. The message receiving component 1240 may be configured to or otherwise support a component for receiving a second message indicating the ID of the UE, the first time interval, and the second encrypted number in response to the first message. The time calibration component 1245 may be configured to or otherwise support a component for performing a time calibration procedure based on the second message, the second time interval between the reception of the second message and the transmission of the first message, and the delay threshold of the UE.

[0198] In some examples, to support performing a time alignment procedure, duration determination component 1265 may be configured or otherwise support means for determining that the duration of the second time interval is less than the sum of the delay threshold and the duration of the first time interval. In some examples, to support performing a time alignment procedure, time alignment component 1245 may be configured or otherwise support means for updating one or more time settings of the UE based on a timestamp associated with the sending of the second message and a timestamp associated with the receiving of the second message.

[0199] In some examples, to support execution of a time calibration procedure, time calibration component 1245 may be configured as or otherwise support components for suppressing execution of a timing adjustment based on determining that the duration of a second time interval is greater than the sum of a delay threshold and the duration of a first time interval, where the first time interval corresponds to the duration between sending the second message and receiving the first message.

[0200] In some examples, to support receiving a second message, time calibration component 1245 may be configured as or otherwise support components for receiving an indication of an absolute time associated with sending the second message, a subframe associated with sending the second message, or both, wherein execution of the time calibration procedure is based on the indication.

[0201] In some examples, the first message includes a PUSCH transmission scrambled using a first pseudo-random sequence. In some examples, the second message includes a PDSCH transmission scrambled using a second pseudo-random sequence.

[0202] In some examples, to support performing a time alignment procedure, duration determination component 1265 may be configured to or otherwise support means for determining that a product of a scaling factor and a duration of the first time interval is less than a delay threshold, wherein the scaling factor is based on an error rate associated with a local oscillator of the UE. In some examples, to support performing a time alignment procedure, time alignment component 1245 may be configured to or otherwise support means for performing a time adjustment based on a timestamp associated with the transmission of the second message and a timestamp associated with the reception of the second message.

[0203] In some examples, state transition component 1270 may be configured or otherwise support components for transitioning from an unsynchronized timing state to a synchronized timing state after performing a time calibration procedure, wherein the UE initiates the time calibration procedure in response to entering the unsynchronized timing state.

[0204] Fig.13A diagram of a system 1300 including a device 1305 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein, or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1345).

[0205] I / O controller 1310 can manage input signals and output signals of device 1305. I / O controller 1310 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize an operating system, such as MS- or another known operating system. Additionally or alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor, such as processor 1340. In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.

[0206] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, a wired link, or a wireless link as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1325 for transmission; and demodulating packets received from one or more antennas 1325. The transceiver 1315 or the transceiver 1315 and one or more antennas 1325 may be examples of transmitters 1015, transmitters 1115, receivers 1010, receivers 1110, or any combination thereof or components thereof as described herein.

[0207] Memory 1330 may include random access memory (RAM) and read-only memory (ROM). Memory 1330 may store computer-readable, computer-executable code 1335 including instructions that, when executed by processor 1340, cause device 1305 to perform various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1335 may not be directly executable by processor 1340, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1330 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0208] Processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks that support timing and synchronization technology for a secure network). For example, device 1305 or a component of device 1305 may include processor 1340 and memory 1330 coupled to or coupled to processor 1340, and processor 1340 and memory 1330 are configured to perform various functions described herein.

[0209] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at the UE (device 1305). For example, the communication manager 1320 may be configured to or otherwise support a component for monitoring a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of the PRF based on a timing parameter, a cell ID, and a shared key. The communication manager 1320 may be configured to or otherwise support a component for communicating with a network entity via a cell associated with a cell ID based on monitoring the set of time-frequency resources to find one or more CDSs.

[0210] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1320 may support wireless communication at the UE. For example, the communication manager 1320 may be configured to or otherwise support a component for sending a first message indicating the ID of the UE and the first encrypted number. The communication manager 1320 may be configured to or otherwise support a component for receiving a second message indicating the ID of the UE, the first time interval, and the second encrypted number in response to the first message. The communication manager 1320 may be configured to or otherwise support a component for performing a time calibration procedure based on the second message, the second time interval between the reception of the second message and the transmission of the first message, and the delay threshold of the UE.

[0211] By including or configuring a communication manager 1320 according to the examples described herein, the device 1305 can support techniques for improving security, reducing interference, and increasing reliability, among other benefits. For example, the timing and synchronization procedures described herein can enable one or both of the device 1305 or the network entity to mitigate interference attacks, impersonation attacks, replay attacks, and eavesdropping attacks from external threats, which can increase the likelihood of successful communication between the device 1305 and the network entity.

[0212] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions that are executable by the processor 1340 to cause the device 1305 to perform various aspects of the timing and synchronization techniques for secure networks as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0213] Fig.14 A block diagram 1400 of a device 1405 supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0214] Receiver 1410 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0215] The transmitter 1415 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1405. For example, the transmitter 1415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0216] The communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the timing and synchronization techniques for secure networks as described herein. For example, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0217] In some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0218] Additionally or alternatively, in some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0219] In some examples, communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1410, transmitter 1415, or both. For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated with receiver 1410, transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0220] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at a network entity (device 1405). For example, the communication manager 1420 may be configured to or otherwise support a component for sending one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The communication manager 1420 may be configured to or otherwise support a component for communicating with a UE via a cell associated with a cell ID based on sending one or more CDSs via a set of time-frequency resources.

[0221] Additionally or alternatively, according to examples disclosed herein, the communication manager 1420 may support wireless communication at a network entity (e.g., device 1405). For example, the communication manager 1420 may be configured to or otherwise support a component for receiving a first message indicating an ID of the UE and a first encrypted number. The communication manager 1420 may be configured to or otherwise support a component for performing an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The communication manager 1420 may be configured to or otherwise support a component for sending a second message indicating the ID of the UE, a time interval, and a second encrypted number in response to the first message and based on the result of the authentication procedure.

[0222] By including or configuring the communication manager 1420 according to the examples as described herein, the device 1405 (e.g., a processor that controls or otherwise couples with the receiver 1410, the transmitter 1415, the communication manager 1420, or a combination thereof) can support techniques for reducing power consumption by reducing the number of retransmissions performed or requested by the device 1405. For example, the techniques described herein can reduce the likelihood that a replay attack will adversely affect communications between the device 1405 and a UE in a secure network, thereby increasing the likelihood that the device 1405 will successfully communicate with the IE. As a result, the device 1405 can perform fewer retransmissions, which can achieve reduced power consumption at the device 1405.

[0223] Fig.15 A block diagram 1500 of a device 1505 supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of aspects of the device 1405 or the network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0224] Receiver 1510 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1505. In some examples, receiver 1510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0225] The transmitter 1515 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1505. For example, the transmitter 1515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1515 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1515 and the receiver 1510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0226] Device 1505 or its various components may be examples of components for performing various aspects of timing and synchronization techniques for secure networks as described herein. For example, communication manager 1520 may include CDS sending component 1525, communication component 1530, message receiving component 1535, authentication component 1540, message sending component 1545, or any combination thereof. Communication manager 1520 may be an example of various aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1510, transmitter 1515, or both. For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or be integrated with receiver 1510, transmitter 1515, or both to obtain information, output information, or perform various other operations as described herein.

[0227] According to examples disclosed herein, the communication manager 1520 may support wireless communications at a network entity (e.g., device 1505). The CDS sending component 1525 may be configured to or otherwise support components for sending one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of the PRF based on a timing parameter, a cell ID, and a shared key. The communication component 1530 may be configured to or otherwise support components for communicating with a UE via a cell associated with a cell ID based on sending one or more CDSs via the set of time-frequency resources.

[0228] Additionally or alternatively, according to examples disclosed herein, the communication manager 1520 may support wireless communications at a network entity (e.g., device 1505). The message receiving component 1535 may be configured to or otherwise support a component for receiving a first message indicating an ID of the UE and a first encrypted number. The authentication component 1540 may be configured to or otherwise support a component for performing an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The message sending component 1545 may be configured to or otherwise support a component for sending a second message indicating the ID of the UE, a time interval, and a second encrypted number in response to the first message and based on the result of the authentication procedure.

[0229] Fig.16 A block diagram 1600 of a communication manager 1620 supporting timing and synchronization techniques for a secure network in accordance with one or more aspects of the present disclosure is shown. The communication manager 1620 may be an example of aspects of the communication manager 1420, the communication manager 1520, or both as described herein. The communication manager 1620 or its various components may be examples of components for performing various aspects of the timing and synchronization techniques for a secure network as described herein. For example, the communication manager 1620 may include a CDS sending component 1625, a communication component 1630, a message receiving component 1635, an authentication component 1640, a message sending component 1645, a timing information component 1650, a PRF component 1655, or any combination thereof.

[0230] Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0231] According to examples disclosed herein, the communication manager 1620 may support wireless communications at a network entity. The CDS sending component 1625 may be configured to or otherwise support components for sending one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of the PRF based on a timing parameter, a cell ID, and a shared key. The communication component 1630 may be configured to or otherwise support components for communicating with a UE via a cell associated with a cell ID based on sending one or more CDSs via the set of time-frequency resources.

[0232] In some examples, timing information component 1650 may be configured or otherwise support components for acquiring absolute timing information via GNSS, wherein the timing parameters are based on the absolute timing information.

[0233] In some examples, to support sending one or more CDSs, CDS sending component 1625 may be configured to or otherwise support means for sending one or more CDSs via two or more carrier frequencies according to a frequency hopping communication scheme. In some examples, each cell of the network entity is associated with a different pseudo-random cell ID.

[0234] In some examples, the PRF component 1655 may be configured as or otherwise support components for inputting a shared key and seed parameters into a pseudo-random function, the seed parameters comprising an absolute time bit sequence, a frequency bit sequence, a PCID bit sequence, a time-specific parameterized bit sequence, or a combination thereof, wherein an output of the PRF indicates a pseudo-random sequence and a set of time-frequency resources.

[0235] In some examples, the PRF component 1655 may be configured to or otherwise support components for generating a pseudo-random cell ID for a cell based on a shared key, a PCID of the cell of the network entity, and a timestamp associated with the generation of the pseudo-random cell ID, wherein the output of the PRF is based on the pseudo-random cell ID.

[0236] Additionally or alternatively, according to examples disclosed herein, the communication manager 1620 may support wireless communications at a network entity. The message receiving component 1635 may be configured to or otherwise support a component for receiving a first message indicating an ID of the UE and a first encrypted number. The authentication component 1640 may be configured to or otherwise support a component for performing an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The message sending component 1645 may be configured to or otherwise support a component for sending a second message indicating the ID of the UE, a time interval, and a second encrypted number in response to the first message and based on the result of the authentication procedure.

[0237] In some examples, to support sending the second message, message sending component 1645 may be configured or otherwise support means for sending an indication of a pseudo-random key to be used to encrypt subsequent messages between the UE and the network entity.

[0238] In some examples, to support performing the authentication procedure, the authentication component 1640 may be configured to or otherwise support a component for obtaining a shared key based on credential information associated with the UE. In some examples, to support performing the authentication procedure, the authentication component 1640 may be configured to or otherwise support a component for verifying an encrypted signature of the first message based on the shared key.

[0239] In some examples, the message sending component 1645 may be configured or otherwise support components for exchanging one or more messages with the UE to obtain a shared key prior to receiving the first message.

[0240] Fig.17 A diagram of a system 1700 including a device 1705 that supports timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The device 1705 may be an example of a device 1405, a device 1505, or a network entity 105 as described herein, or include components thereof. The device 1705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1705 may include components that support output and acquisition of communications, such as a communication manager 1720, a transceiver 1710, an antenna 1715, a memory 1725, a code 1730, and a processor 1735. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1740).

[0241] The transceiver 1710 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1710 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1710 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1705 may include one or more antennas 1715, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1710 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1715, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1715, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1710 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1715 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1715 configured to support various transmit or output operations, or a combination thereof.

[0242] In some implementations, the transceiver 1710 may include or be configured to be coupled to one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1710, or the transceiver 1710 and one or more antennas 1715, or the transceiver 1710 and one or more antennas 1715 and one or more processors or memory components (e.g., processor 1735 or memory 1725 or both) may be included in a chip or chip assembly installed in the device 1705. In some examples, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0243] Memory 1725 may include RAM and ROM. Memory 1725 may store computer-readable, computer-executable code 1730 including instructions that, when executed by processor 1735, cause device 1705 to perform various functions described herein. Code 1730 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1730 may not be directly executable by processor 1735, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1725 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0244] Processor 1735 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1735 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1735. Processor 1735 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1725) to cause device 1705 to perform various functions (e.g., functions or tasks that support timing and synchronization techniques for a secure network).

[0245] For example, the device 1705 or a component of the device 1705 may include a processor 1735 and a memory 1725 coupled to the processor 1735, the processor 1735 and the memory 1725 being configured to perform the various functions described herein. The processor 1735 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, a virtual machine, or a container instance)) that may host (e.g., by executing code 1730) functions for performing the functions of the device 1705. The processor 1735 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1705 (such as within the memory 1725). In some implementations, the processor 1735 may be a component of a processing system.

[0246] A processing system may generally refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs that may be delivered to, for example, other systems or components of the device 1705. For example, the processing system of the device 1705 may refer to a system that includes various other components or subcomponents of the device 1705, such as the processor 1735, or the transceiver 1710, or the communication manager 1720, or other components or combinations of components of the device 1705. The processing system of the device 1705 may interface with other components of the device 1705 and may process information (such as inputs or signals) received from the other components or output information to the other components.

[0247] For example, the chip or modem of device 1705 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1705 can transmit information output from the chip or modem.

[0248] Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1705 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0249] In some examples, bus 1740 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1740 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1705, or communications performed between different components of device 1705 that may be co-located or may be located in different locations (e.g., where device 1705 may refer to a system in which one or more of communication manager 1720, transceiver 1710, memory 1725, code 1730, and processor 1735 may be located in one of the different components or divided between the different components).

[0250] In some examples, communication manager 1720 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1720 may manage the transfer of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1720 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1720 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0251] According to examples disclosed herein, the communication manager 1720 may support wireless communications at a network entity, e.g., device 1705. For example, the communication manager 1720 may be configured to or otherwise support components for sending one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The communication manager 1720 may be configured to or otherwise support components for communicating with a UE via a cell associated with a cell ID based on sending one or more CDSs via the set of time-frequency resources.

[0252] Additionally or alternatively, according to examples disclosed herein, the communication manager 1720 may support wireless communication at a network entity (e.g., device 1705). For example, the communication manager 1720 may be configured to or otherwise support a component for receiving a first message indicating an ID of the UE and a first encrypted number. The communication manager 1720 may be configured to or otherwise support a component for performing an authentication procedure based on retrieving credential information associated with the UE using the ID of the UE. The communication manager 1720 may be configured to or otherwise support a component for sending a second message indicating the ID of the UE, a time interval, and a second encrypted number in response to the first message and based on the result of the authentication procedure.

[0253] By including or configuring a communication manager 1720 according to examples as described herein, the device 1705 can support techniques for improving security, reducing interference, and increasing reliability, among other benefits. For example, the timing and synchronization procedures described herein can enable one or both of the device 1705 or the UE to mitigate interference attacks, impersonation attacks, replay attacks, and eavesdropping attacks from other devices, which can increase the likelihood of successful communication between the device 1705 and the UE.

[0254] In some examples, the communication manager 1720 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1710, one or more antennas 1715 (e.g., where applicable), or any combination thereof. Although the communication manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported or performed by the transceiver 1710, the processor 1735, the memory 1725, the code 1730, or any combination thereof. For example, the code 1730 may include instructions that are executable by the processor 1735 to cause the device 1705 to perform various aspects of the timing and synchronization techniques for the secure network as described herein, or the processor 1735 and the memory 1725 may be otherwise configured to perform or support such operations.

[0255] Fig.18 A flowchart illustrating a method 1800 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or a component thereof. For example, the operations of the method 1800 may be implemented by a UE or a component thereof. Figures 1 to 13 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0256] At 1805, the UE may monitor a set of time-frequency resources to find one or more CDSs associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of the PRF based on a timing parameter, a cell ID, and a shared key. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The resource monitoring component 1225 described executes.

[0257] At 1810, the UE may communicate with a network entity via a cell associated with a cell ID based on monitoring a set of time-frequency resources to find one or more CDSs. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The communication component 1230 described performs.

[0258] Fig.19 A flowchart illustrating a method 1900 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof. Figures 1 to 9 as well as Figures 14 to 17 The described network entity 105 performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0259] At 1905, the network entity may send one or more CDSs associated with a pseudo-random sequence via a set of time-frequency resources, where the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a PRF based on a timing parameter, a cell ID, and a shared key. The operations of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.16 The described CDS sending component 1625 executes.

[0260] At 1910, the network entity may communicate with the UE via a cell associated with the cell ID based on sending one or more CDSs via a set of time-frequency resources. The operations of 1910 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1910 may be described with reference to Fig.16 The communication component 1630 described performs.

[0261] Fig. 20A flowchart illustrating a method 2000 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a UE or a component thereof. For example, the operations of the method 2000 may be implemented by a UE as described in reference to Figures 1 to 13 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0262] At 2005, the UE may send a first message indicating the UE's ID and a first encrypted number. The operations of 2005 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.12 The described message sending component 1235 executes.

[0263] At 2010, the UE may receive a second message indicating the UE's ID, the first time interval, and the second encryption number in response to the first message. The operations of 2010 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.12 The described message receiving component 1240 executes.

[0264] At 2015, the UE may perform a time calibration procedure based on the second message, a second time interval between the reception of the second message and the transmission of the first message, and a delay threshold of the UE. The operations of 2015 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.12 The described time alignment component 1245 performs.

[0265] Fig.21 A flowchart illustrating a method 2100 for supporting timing and synchronization techniques for a secure network according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a network entity or a component thereof. For example, the operations of the method 2100 may be implemented by a network entity or a component thereof. Figures 1 to 9 as well as Figures 14 to 17 The described network entity 105 performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0266] At 2105, the network entity may receive a first message indicating an ID of the UE and a first encryption number. The operations of 2105 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.16 The described message receiving component 1635 executes.

[0267] At 2110, the network entity may perform an authentication procedure based on retrieving credential information associated with the UE using the UE's ID. The operations of 2110 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.16 The authentication component 1640 described performs.

[0268] At 2115, the network entity may send a second message indicating the ID of the UE, the time interval, and the second encryption number in response to the first message and based on the result of the authentication procedure. The operations of 2115 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.16 The described message sending component 1645 executes.

[0269] The following provides an overview of various aspects of the disclosure:

[0270] Aspect 1: A method for wireless communication at an IE, the method comprising: monitoring a time-frequency resource set to search for one or more cell detection signals associated with a pseudo-random sequence, wherein the pseudo-random sequence and the time-frequency resource set are indicated by an output of a pseudo-random function based at least in part on a timing parameter, a cell identifier, and a shared key; and communicating with a network entity via a cell associated with the cell identifier based at least in part on monitoring the time-frequency resource set to search for the one or more cell detection signals.

[0271] Aspect 2: According to the method described in Aspect 1, the method also includes: obtaining two or more bit sequences based at least in part on two or more calls to the pseudo-random function; and generating the pseudo-random sequence and resource location information by aggregating the two or more bit sequences, wherein the resource location information indicates the time-frequency resource set.

[0272] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: generating a first pseudo-random sequence and a first frequency position at a first time; and generating a second pseudo-random sequence and second frequency position information at a second time, wherein the duration between the first time and the second time corresponds to the periodicity of the one or more cell detection signals.

[0273] Aspect 4: According to the method according to any one of aspects 1 to 3, the method further comprises: generating a plurality of bits indicating one or more symbol positions and physical resource block positions to be monitored to find the one or more cell detection signals.

[0274] Aspect 5: According to the method according to any one of aspects 1 to 4, monitoring the time-frequency resource set includes: performing frequency domain correlation analysis on multiple resource elements in the time-frequency resource set.

[0275] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: identifying multiple cell groups associated with corresponding multiple cell group identifiers; and generating a pseudo-random output for each of the multiple cell groups based at least in part on the corresponding multiple cell group identifiers, wherein the pseudo-random output includes a pseudo-random sequence and a set of time-frequency resource locations associated with one of the multiple cell groups.

[0276] Aspect 7: According to the method described in Aspect 6, the method also includes: selecting a subset of the multiple cell groups based at least in part on monitoring the time-frequency resource location set associated with each cell group in the multiple cell groups; and generating a pseudo-random output for each cell in the subset of the multiple cell groups, wherein the pseudo-random output includes a pseudo-random sequence and a time-frequency resource location set associated with the cell in the subset of the multiple cell groups.

[0277] Aspect 8: The method according to any one of aspects 1 to 7, wherein the one or more cell detection signals include a primary cell detection signal time-division multiplexed with a secondary cell detection signal.

[0278] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: generating a pseudo-random cell identifier, wherein the pseudo-random cell identifier is a function of the shared key, a physical cell identifier associated with the cell of the network entity, and a timestamp associated with the generation of the pseudo-random cell identifier, wherein the output of the pseudo-random function is at least partially based on the pseudo-random cell identifier.

[0279] Aspect 10: The method according to aspect 9, wherein the timestamp indicates a time slot, a system frame number or a coordinated universal time associated with the generation of the pseudo-random cell identifier.

[0280] Aspect 11: According to the method described in any one of Aspects 9 to 10, the method also includes: performing a Boolean operation on one or more least significant bits of the pseudo-random output and the physical cell identifier associated with the cell of the network entity, wherein the generation of the pseudo-random cell identifier is at least partially based on the result of the Boolean operation.

[0281] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: generating the output of the pseudo-random function based at least in part on a time drift threshold of the IE, wherein the output indicates a pseudo-random bit sequence and a time-frequency resource position set; and monitoring the time-frequency resource position set to search for one or more timing synchronization signals indicating the pseudo-random bit sequence.

[0282] Aspect 13: The method according to aspect 12, further comprising: obtaining absolute timing information based at least in part on measuring the one or more timing synchronization signals, wherein the timing parameters are based at least in part on the absolute timing information.

[0283] Aspect 14: A method for performing wireless communications at a network entity, the method comprising: sending one or more cell detection signals associated with a pseudo-random sequence via a time-frequency resource set, wherein the pseudo-random sequence and the time-frequency resource set are indicated by an output of a pseudo-random function based at least in part on a timing parameter, a cell identifier, and a shared key; and communicating with an IE via a cell associated with the cell identifier based at least in part on sending the one or more cell detection signals via the time-frequency resource set.

[0284] Aspect 15: The method according to aspect 14, the method further comprising: acquiring absolute timing information via a global navigation satellite system, wherein the timing parameter is at least partially based on the absolute timing information.

[0285] Aspect 16: The method according to any one of aspects 14 to 15, wherein sending the one or more cell detection signals comprises: sending the one or more cell detection signals via two or more carrier frequencies according to a frequency hopping communication scheme.

[0286] Aspect 17: The method according to any one of aspects 14 to 16, wherein each cell of the network entity is associated with a different pseudo-random cell identifier.

[0287] Aspect 18: According to the method described in any one of Aspects 14 to 17, the method further includes: inputting the shared key and seed parameters into the pseudo-random function, the seed parameters comprising an absolute time bit sequence, a frequency bit sequence, a physical cell identifier bit sequence, a time-specific parameterized bit sequence, or a combination thereof, wherein the output of the pseudo-random function indicates the pseudo-random sequence and the time-frequency resource set.

[0288] Aspect 19: According to the method described in any one of Aspects 14 to 18, the method also includes: generating the pseudo-random cell identifier for the cell based at least in part on the shared key, the physical cell identifier of the cell of the network entity, and a timestamp associated with the generation of the pseudo-random cell identifier, wherein the output of the pseudo-random function is at least in part based on the pseudo-random cell identifier.

[0289] Aspect 20: A method for performing wireless communications at a UE, the method comprising: sending a first message indicating an identifier of the UE and a first encryption number; receiving a second message indicating the identifier of the UE, a first time interval, and a second encryption number in response to the first message; and performing a time calibration procedure based at least in part on the second message, a second time interval between the reception of the second message and the sending of the first message, and a delay threshold of the UE.

[0290] Aspect 21: A method according to Aspect 20, wherein performing the time calibration procedure includes: determining that the duration of the second time interval is less than the sum of the delay threshold and the duration of the first time interval; and updating one or more time settings of the UE based at least in part on a timestamp associated with the sending of the second message and a timestamp associated with the receiving of the second message.

[0291] Aspect 22: A method according to Aspect 20, wherein executing the time calibration procedure includes: suppressing execution of a timing adjustment based at least in part on determining that the duration of the second time interval is greater than the sum of the delay threshold and the duration of the first time interval, wherein the first time interval corresponds to the duration between sending the second message and receiving the first message.

[0292] Aspect 23: A method according to any one of Aspects 20 to 22, wherein receiving the second message includes: receiving an indication of an absolute time associated with the sending of the second message, a subframe associated with the sending of the second message, or both, wherein performing the time calibration procedure is at least partially based on the indication.

[0293] Aspect 24: A method according to any one of Aspects 20 to 23, wherein: the first message includes a physical uplink shared channel transmission encrypted using a first pseudo-random sequence; and the second message includes a physical downlink shared channel transmission encrypted using a second pseudo-random sequence.

[0294] Aspect 25: A method according to any one of Aspects 20 to 21, wherein performing the time calibration procedure includes: determining that the product of a scaling factor and the duration of the first time interval is less than the delay threshold, wherein the scaling factor is based at least in part on an error rate associated with a local oscillator of the UE; and performing a time adjustment based at least in part on a timestamp associated with the sending of the second message and a timestamp associated with the receiving of the second message.

[0295] Aspect 26: According to any one of Aspects 20 to 25, the method also includes: transitioning from an unsynchronized timing state to a synchronized timing state after performing the time calibration procedure, wherein the UE initiates the time calibration procedure in response to entering the unsynchronized timing state.

[0296] Aspect 27: A method for wireless communication at a network entity, the method comprising: receiving a first message indicating an identifier of a UE and a first encryption number; performing an authentication procedure based at least in part on retrieving credential information associated with the UE using the identifier of the UE; and sending a second message indicating the identifier of the UE, a time interval, and a second encryption number in response to the first message and based at least in part on a result of the authentication procedure.

[0297] Aspect 28: The method according to aspect 27, wherein sending the second message includes: sending an indication of a pseudo-random key to be used for encrypting subsequent messages between the UE and the network entity.

[0298] Aspect 29: A method according to any one of Aspects 27 to 28, wherein performing the authentication procedure includes: obtaining a shared key based at least in part on the credential information associated with the UE; and verifying the encrypted signature of the first message based at least in part on the shared key.

[0299] Aspect 30: According to any one of aspects 27 to 29, the method further comprises: exchanging one or more messages with the UE to obtain a shared key before receiving the first message.

[0300] Aspect 31: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 13.

[0301] Aspect 32: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 13.

[0302] Aspect 33: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 13.

[0303] Aspect 34: An apparatus for performing wireless communications at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method according to any one of Aspects 14 to 19.

[0304] Aspect 35: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 14 to 19.

[0305] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 14 to 19.

[0306] Aspect 37: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method according to any one of Aspects 20 to 26.

[0307] Aspect 38: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 20 to 26.

[0308] Aspect 39: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 20 to 26.

[0309] Aspect 40: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method according to any one of Aspects 27 to 30.

[0310] Aspect 41: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 27 to 30.

[0311] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 27 to 30.

[0312] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0313] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0314] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0315] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0316] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0317] Computer readable media include both non-transient computer storage media and communication media, and the communication media include any medium that facilitates the transfer of a computer program from one location to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. By way of example and not limitation, non-transient computer readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special-purpose computer or a general or special-purpose processor.

[0318] Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of computer-readable media. As used herein, disks and optical disks include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0319] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0320] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0321] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0322] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0323] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: monitoring a set of time-frequency resources for one or more cell detection signals associated with a pseudo-random sequence, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a pseudo-random function based at least in part on a timing parameter, a cell identifier, and a shared key; as well as Based at least in part on monitoring the set of time-frequency resources for the one or more cell detection signals, communicating with a network entity via a cell associated with the cell identifier.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: obtaining two or more bit sequences based at least in part on making two or more calls to the pseudorandom function; and The pseudo-random sequence and resource location information are generated by aggregating the two or more bit sequences, wherein the resource location information indicates the set of time-frequency resources.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: A first pseudo-random sequence and first frequency position information are generated at a first time; and a second pseudo-random sequence and second frequency position information are generated at a second time, wherein the duration between the first time and the second time corresponds to the periodicity of the one or more cell detection signals.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A plurality of bits are generated indicating one or more symbol locations and physical resource block locations to monitor for the one or more cell detection signals.

5. The apparatus of claim 1 , wherein to monitor the set of time-frequency resources, the instructions are executable by the processor to cause the apparatus to: A frequency domain correlation analysis is performed on a plurality of resource elements in the time-frequency resource set.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a plurality of cell groups associated with a corresponding plurality of cell group identifiers; and A pseudo-random output is generated for each of the plurality of cell groups based at least in part on the respective plurality of cell group identifiers, wherein the pseudo-random output comprises a pseudo-random sequence and a set of time-frequency resource locations associated with a cell group in the plurality of cell groups.

7. The apparatus of claim 6, wherein the instructions are further executable by the processor to cause the apparatus to: selecting a subset of the plurality of cell groups based at least in part on monitoring the set of time-frequency resource locations associated with each of the plurality of cell groups; and generating a pseudo-random output for each cell in the subset of the plurality of cell groups, wherein the pseudo-random output comprises a pseudo-random sequence and a set of time-frequency resource locations associated with a cell in the subset of the plurality of cell groups. 8 . The apparatus according to claim 1 , wherein the one or more cell detection signals include a primary cell detection signal time-division multiplexed with a secondary cell detection signal.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: generating a pseudo-random cell identifier that is a function of the shared key, a physical cell identifier associated with the cell of the network entity, and a timestamp associated with generation of the pseudo-random cell identifier, wherein the output of the pseudo-random function is based at least in part on the pseudo-random cell identifier.

10. The apparatus of claim 9, wherein the timestamp indicates a time slot, a system frame number, or a coordinated universal time associated with generation of the pseudo-random cell identifier.

11. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: A Boolean operation is performed on one or more least significant bits of the pseudo-random output and the physical cell identifier associated with the cell of the network entity, wherein generating the pseudo-random cell identifier is based at least in part on a result of the Boolean operation.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: generating the output of the pseudorandom function based at least in part on a time drift threshold of the UE, wherein the output indicates a pseudorandom bit sequence and a set of time-frequency resource locations; and The set of time-frequency resource locations is monitored for one or more timing synchronization signals indicative of the pseudo-random bit sequence.

13. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: Absolute timing information is acquired based at least in part on measuring the one or more timing synchronization signals, wherein the timing parameters are based at least in part on the absolute timing information.

14. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting one or more cell detection signals associated with a pseudo-random sequence via a set of time-frequency resources, wherein the pseudo-random sequence and the set of time-frequency resources are indicated by an output of a pseudo-random function based at least in part on a timing parameter, a cell identifier, and a shared key; and Based at least in part on transmitting the one or more cell detection signals via the set of time-frequency resources, communicating with a user equipment (IE) via a cell associated with the cell identifier.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Absolute timing information is acquired via a global navigation satellite system, wherein the timing parameters are based at least in part on the absolute timing information.

16. The apparatus of claim 14, wherein to transmit the one or more cell detection signals, the instructions are executable by the processor to cause the apparatus to: The one or more cell detection signals are transmitted via two or more carrier frequencies according to a frequency hopping communication scheme.

17. The apparatus of claim 14, wherein each cell of the network entity is associated with a different pseudo-random cell identifier.

18. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: The shared key and a seed parameter are input to the pseudo-random function, the seed parameter comprising an absolute time bit sequence, a frequency bit sequence, a physical cell identifier bit sequence, a time-specific parameterized bit sequence, or a combination thereof, wherein the output of the pseudo-random function indicates the pseudo-random sequence and the set of time-frequency resources.

19. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: The pseudo-random cell identifier for the cell is generated based at least in part on the shared key, a physical cell identifier of the cell of the network entity, and a timestamp associated with generation of the pseudo-random cell identifier, wherein the output of the pseudo-random function is based at least in part on the pseudo-random cell identifier.

20. An apparatus for wireless communication at a user equipment (IE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a first message indicating an identifier of the IE and a first encryption number; receiving, in response to the first message, a second message indicating the identifier of the IE, a first time interval, and a second encryption number; as well as A time alignment procedure is performed based at least in part on the second message, a second time interval between receipt of the second message and transmission of the first message, and a delay threshold of the IE.

21. The apparatus of claim 20, wherein to perform the time alignment procedure, the instructions are executable by the processor to cause the apparatus to: determining that the duration of the second time interval is less than the sum of the delay threshold and the duration of the first time interval; and One or more time settings of the UE are updated based at least in part on a timestamp associated with the transmission of the second message and a timestamp associated with the receipt of the second message.

22. The apparatus of claim 20, wherein to perform the time alignment procedure, the instructions are executable by the processor to cause the apparatus to: Refraining from performing a timing adjustment based at least in part on determining that the duration of the second time interval is greater than the sum of the delay threshold and the duration of the first time interval, wherein the first time interval corresponds to a duration between sending the second message and receiving the first message.

23. The apparatus of claim 20, wherein to receive the second message, the instructions are executable by the processor to cause the apparatus to: An indication of an absolute time associated with transmission of the second message, a subframe associated with transmission of the second message, or both is received, wherein performing the time alignment procedure is based at least in part on the indication.

24. The apparatus of claim 20, wherein: The first message comprises a physical uplink shared channel transmission scrambled using a first pseudo-random sequence; and The second message includes a physical downlink shared channel transmission scrambled using a second pseudo-random sequence.

25. The apparatus of claim 20, wherein to perform the time alignment procedure, the instructions are executable by the processor to cause the apparatus to: determining that a product of a scaling factor and a duration of the first time interval is less than the delay threshold, wherein the scaling factor is based at least in part on an error rate associated with a local oscillator of the IE; and The time adjustment is performed based at least in part on a timestamp associated with the transmission of the second message and a timestamp associated with the receipt of the second message.

26. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: and transitioning from an unsynchronized timing state to a synchronized timing state after performing the time alignment procedure, wherein the UE initiates the time alignment procedure in response to entering the unsynchronized timing state.

27. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a first message indicating an identifier of a user equipment (UE) and a first encrypted number; performing an authentication procedure based at least in part on retrieving credential information associated with the IE using the identifier of the IE; as well as In response to the first message and based at least in part on a result of the authentication procedure, a second message is sent indicating the identifier of the UE, a time interval, and a second encrypted number.

28. The apparatus of claim 27, wherein to send the second message, the instructions are executable by the processor to cause the apparatus to: An indication of a pseudo-random key to be used to encrypt subsequent messages between the IE and the network entity is sent.

29. The apparatus of claim 27, wherein to perform the authentication procedure, the instructions are executable by the processor to cause the apparatus to: obtaining a shared key based at least in part on the credential information associated with the UE; and The cryptographic signature of the first message is verified based at least in part on the shared key.

30. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: One or more messages are exchanged with the UE to obtain a shared key before receiving the first message.

Images