Device, method and apparatus for communication, and computer readable medium
By using the key generated based on paging keys and NAS algorithm information during the voice rollback process to protect the integrity and confidentiality of the voice rollback information, the problem of voice rollback security vulnerability in the prior art is solved, ensuring that Security and integrity of terminal devices.
Patent Information
- Application Number
- CN202380037054.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-29
- Filing Date
- 2023-03-17
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art has security vulnerabilities in the voice back-up process. Attackers can imitate paging messages and redirect terminal devices to pseudo-base stations, resulting in calls being hijacked and lacking effective security protection.
By generating integrity protection keys and cryptographic keys based on paging keys and non-access layer (NAS) algorithm information between the first device and the second device, the integrity and confidentiality of the voice backoff information is ensured, using Password key decryption and integrity protect the key to verify message integrity, discarding any messages that fail to completeness verification.
有效增强了语音回退信息的安全性,防止攻击者通过模仿寻呼消息劫持呼叫,确保终端设备在语音回退过程中的安全性和完整性。
Smart Images

Figure CN119096571A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular, to devices, methods, apparatuses, and computer-readable media for communications. Background Art
[0002] The terminal device may perform a handover or redirection from the first cell to the second cell. If the first cell does not support the voice service of the terminal device and the first cell adopts a higher-level radio access technology (RAT) than the second cell, the handover or redirection may be referred to as a handover or redirection triggered by voice fallback.
[0003] To improve voice fallback performance, network devices may include voice fallback information in messages associated with handover or redirection, which may cause security issues. Summary of the invention
[0004] In general, example implementations of the present disclosure provide devices, methods, apparatus, and computer-readable media for communications.
[0005] In a first aspect, a first device is provided. The first device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, enable the first device to: generate an integrity protection key and a cryptographic key based on a paging key and non-access stratum (NAS) algorithm information; receive a message from a second device, the message including voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; decrypt the voice fallback information using the cryptographic key; and in response to a failure to verify the integrity of the voice fallback information using the integrity protection key certificate, discard the message.
[0006] In a second aspect, a second device is provided. The second device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, enable the second device to: receive a paging request from a third device, the paging request including a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; generate voice fallback information based on the voice service type indication; generate an integrity protection key and a cryptographic key based on the paging key and the NAS algorithm information; generate encrypted and integrity-protected voice fallback information by using the integrity protection key to integrity-protect the voice fallback information, and by using the cryptographic key to encrypt the voice fallback information; and send a message to the first device, the message including the encrypted and integrity-protected voice fallback information.
[0007] In a third aspect, a method implemented at a first device is provided. The method includes: generating, at the first device, an integrity protection key and a cryptographic key based on a paging key and non-access stratum (NAS) algorithm information; receiving, in idle mode, a message from a second device, the message including voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; decrypting the voice fallback information using the cryptographic key; and in response to a failure to verify the integrity of the voice fallback information using the integrity protection key, discarding the message.
[0008] In a fourth aspect, a method implemented at a second device is provided. The method includes: receiving a paging request at the second device from a third device, the paging request including a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; generating voice fallback information based on the voice service type indication; generating an integrity protection key and a cryptographic key based on the paging key and the NAS algorithm information; generating encrypted and integrity-protected voice fallback information by integrity-protecting the voice fallback information using the integrity protection key and encrypting the voice fallback information using the cryptographic key; and sending a message to a first device, the message including the encrypted and integrity-protected voice fallback information.
[0009] In a fifth aspect, a first device is provided. The first device includes: a component for generating an integrity protection key and a cryptographic key based on a paging key and non-access stratum (NAS) algorithm information at the first device; a component for receiving a message from a second device in an idle mode, the message including voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; a component for decrypting the voice fallback information using the cryptographic key; and a component for discarding the message in response to a failure to verify the integrity of the voice fallback information using the integrity protection key.
[0010] In a sixth aspect, a second apparatus is provided. The second apparatus includes: a component for receiving a paging request from a third device, the paging request including a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; a component for generating voice fallback information based on the voice service type indication; a component for generating an integrity protection key and a cryptographic key based on the paging key and the NAS algorithm information; a component for generating encrypted and integrity-protected voice fallback information by integrity-protecting the voice fallback information using the integrity protection key and encrypting the voice fallback information using the cryptographic key; and a component for sending a message to the first apparatus, the message including the encrypted and integrity-protected voice fallback information.
[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, wherein the non-transitory computer-readable medium comprises program instructions, and the program instructions are used to cause an apparatus to execute the method according to the third aspect.
[0012] In an eighth aspect, a non-transitory computer-readable medium is provided, wherein the non-transitory computer-readable medium comprises program instructions, and the program instructions are used to cause an apparatus to execute the method according to the fourth aspect.
[0013] It should be understood that the abstract is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some implementations of the present disclosure in the accompanying drawings, in which:
[0015] Figure 1 An example communication environment is shown in which implementations of the present disclosure may be implemented;
[0016] Figure 2 A signaling diagram illustrating a process for voice fallback security enhancement according to some example implementations of the present disclosure is shown;
[0017] Figure 3 An example of key derivation for paging according to some implementations of the present disclosure is shown;
[0018] Figure 4 An example of MAC-I generation for paging according to some implementations of the present disclosure is shown;
[0019] Figure 5 An example of a process for encrypting voice fallback information according to some implementations of the present disclosure is shown;
[0020] Figure 6 A flowchart illustrating an example method according to some implementations of the present disclosure;
[0021] Figure 7 A flowchart illustrating another example method according to some implementations of the present disclosure is shown;
[0022] Figure 8 shows a simplified block diagram of an apparatus suitable for implementing an embodiment of the present disclosure; and
[0023] Fig. 9 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.
[0024] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0025] The principles of the present disclosure will now be described with reference to some example implementations. It should be understood that these implementations are described only for illustrative purposes, and help those skilled in the art to understand and implement the present disclosure, without proposing any limitation to the scope of the present disclosure. The present disclosure described herein can be implemented in various ways except the following manner.
[0026] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0027] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, those skilled in the art recognize that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.
[0028] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the example implementation, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any term and all combinations of one or more of the listed terms.
[0029] The terms used herein are only used to describe specific implementations and are not intended to limit example implementations. As used herein, the singular forms "a", "an", and "the" also include the plural forms, unless the context clearly indicates otherwise. It is further understood that the terms "comprises", "includes", "has", "has", "includes", and / or "comprising" when used herein specify the presence of the features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0030] As used in this application, the term "circuitry" may refer to one or more or all of the following:
[0031] (a) a hardware circuit implementation only (such as an implementation using only analog and / or digital circuitry), and
[0032] (b) a combination of hardware circuitry and software such as (where applicable):
[0033] (i) a combination of analog and / or digital hardware circuits and software / firmware, and
[0034] (ii) any portion of a hardware processor(s) with software (including digital signal processor(s), software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions), and
[0035] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) to operate, but which may not be present when the software is not required for operation.
[0036] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.
[0037] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation of communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocol, and / or any other protocol currently known or to be developed in the future. The implementation of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can be used to implement the present disclosure. The scope of the present disclosure should not be limited to the above-mentioned system.
[0038] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from the network. A network device may refer to a base station (BS) or an access point (AP), for example, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR next generation NodeB (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated and access backhaul (IAB) node, a relay, a low power node (such as a femto, pico), etc., depending on the terminology and technology applied. A network device is allowed to be defined as part of a gNB, for example in a CU / DU split, in which case the network device is defined as a gNB-CU or a gNB-DU.
[0039] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a user equipment (UE), a user station (SS), a portable user station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and playback appliance, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a notebook embedded device (LEE), a notebook mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), consumer electronic devices, equipment operating in a commercial and / or industrial wireless network, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.
[0040] Figure 1 1 is a schematic diagram of an example communication environment 100 in which implementations of the present disclosure may be implemented. Figure 1 As shown, the communication environment 100 may include a first device 110, a second device 120, a third device 130, a fourth device 140 and a fifth device 150, which may communicate with each other.
[0041] In this example, the first device 110 is shown as a terminal device, and the second device 120 and the fourth device 140 are shown as access network devices serving the terminal device. Therefore, the service areas of the second device 120 and the fourth device 140 are respectively referred to as cells 122 and 142.
[0042] It should be understood that the number of network devices and terminal devices is only for illustrative purposes, without any limitation. Communication environment 100 may include any number of network devices and terminal devices suitable for implementing the disclosed embodiment. Although not shown, it should be understood that one or more terminal devices may be provided with services by the second device 120 and the fourth device 140.
[0043] The communication in the communication environment 100 can be implemented according to any suitable (multiple) communication protocols, including but not limited to cellular communication protocols such as the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G) and the fifth generation (5G), wireless local area network communication protocols (such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), and / or any other currently known or future developed protocols. In addition, the communication can utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other currently known or future developed technology.
[0044] In some implementations, the second device 120 may use a first radio access technology (RAT) and the fourth device 140 may use a second RAT different from the first RAT. In some embodiments, the first RAT may be a 5G RAT and the second RAT may be one of a 2G, 3G, and 4G RAT.
[0045] In this implementation, the second device 120 and the third device 130 may be implemented in a next generation (NG) or 5G communication system. For example, the second device 120 may be implemented as an access network device in a next generation radio access network (NG-RAN), and the third device 130 may be implemented as a core network device in a 5G core (5GC) network. For example, the second device 120 may be implemented as a gNB, and the third device 130 may be implemented as an access and mobility management function (AMF) device.
[0046] In such an implementation, the fourth device 140 and the fifth device 150 may be implemented in an evolved packet system (EPS). For example, the fourth device 140 may be implemented as an access network device in an evolved universal terrestrial radio access network (EUTRAN), and the fifth device 150 may be implemented as a core network device in an evolved packet core (EPC).
[0047] Although the possible implementation of the present disclosure will be described below with the first RAT being a 5G RAT and the second RAT being a 4G RAT as an example, in other possible implementations, the first RAT and the second RAT may also be other RATs as long as they are different from each other. For example, in another possible embodiment, the first RAT may be a 5G RAT, and the second RAT may be 2G or 3G.
[0048] In some implementations, the first device 110 may perform a handover or redirection of the first device 110 from the cell 122 to the cell 142 for voice service. If the cell 122 does not support the voice service of the first device 110, and the cell 122 adopts a higher-level RAT than the cell 142, the handover or redirection may be referred to as voice fallback. In an implementation where the cell 142 is a cell in the EPS, the handover or redirection is also referred to as EPS fallback. Hereinafter, the voice fallback will be described with the EPS fallback as an example. However, other types of voice fallbacks other than the EPS fallback may also be used in the present disclosure.
[0049] In Release 16, to improve EPS fallback performance, the network device can include voiceFallbackIndication in the MobilityFromNRCommand or RRCRelease message to indicate that the handover or redirection is triggered by EPS fallback. Specifically, the usage of voiceFallbackIndication is as follows:
[0050] In the case of NR to EUTRA handover, upon handover failure, the terminal device may first try to select an E-UTRA cell instead of initiating RRC re-establishment as in the traditional way;
[0051] In case of redirection, the terminal device can set the establishmentCause to mo-VoiceCall.
[0052] The above enhancements can reduce voice call establishment delays when handover fails and eliminate handover / E-UTRA RRC establishment failures due to target admission control on non-voice services.
[0053] Release 17 supports voice service indication in paging messages. As part of the Multi-User Subscriber Identity Module (MUSIM) topic, it was agreed to add a voice service indication in the paging message from 5GC to gNB so that the gNB can include the voice service indication in the access stratum (AS) paging message. A similar mechanism also applies to inactive (INACTIVE) terminal devices. A potential use of the indication is to let the terminal device prioritize voice services.
[0054] Release 17 also supports fast EPS fallback triggered by paging. Assuming that the gNB will eventually trigger EPS fallback for MT-Calls for idle / inactive terminal devices by paging the terminal device to CONNECTED mode and performing subsequent handover / redirection, if it finds that paging is for voice services, it may have considered the network configuration (N26 availability, whether VoNR is preferred, NR / E-UTRA coverage) and UE (paging) capabilities to make the decision of EPS fallback, so the EPS fallback indication can be included in the paging message.
[0055] The 3rd Generation Partnership Project (3GPP) Radio Access Network Group 2 (RAN2) is discussing solutions to reduce the EPS fallback delay for IDLE / INACTIVE UEs. The motivation is that some operators and vendors believe that the current EPS fallback process is relatively long, which has a negative impact on the UE experience of voice services, so they prefer to reduce the delay.
[0056] However, considering that the traditional EPS fallback process involves both the core network and the RAN, there are some concerns that the candidate solutions discussed in RAN2 may have an impact on upper layer signaling or core network procedures, which is not the intention of RAN2 in the current version.
[0057] The solution includes two aspects, namely, enhancements for mobile terminated (MT) cases and enhancements for mobile originated (MO) cases. The following is a brief introduction.
[0058] For the MT case, when the network equipment indicates EPS fallback for voice services, the idle / inactive UE directly enters E-UTRA via paging in NR for connection establishment. There are two candidate alternatives for EPS fallback indication.
[0059] In alternative 1, the EPS fallback indication is included in the paging message. Upon receipt of a paging from the core network indicating the voice service type (same as agreed for MUSIM) by the gNB, the gNB may decide to perform EPS fallback for the UE and indicate EPS fallback in the Uu paging message.
[0060] In alternative 2, the EPS fallback indication is included in the system information block (SIB). The specific indication can be a new radio voice (VoNR) support indication or E-UTRA frequency information. When EPS fallback is indicated in the SIB and the voice service type is indicated in the Uu paging message, the idle / inactive UE can assume that the network triggers EPS fallback for it.
[0061] For the MO case, the EPS fallback indication in the SIB proposed in the above alternative 2 can be applied to the MO case. That is, when an idle / inactive UE initiates a MO call, if EPS fallback is indicated in the SIB, the UE directly enters E-UTRA for connection establishment.
[0062] However, the solutions proposed in Alternative 1 and Alternative 2 have security issues. Since the UE is in idle mode, there is no security protection for the paging message sent to the base station traditionally. Therefore, the fake base station established by the attacker can imitate the paging message and use the solution in Alternative 1 or Alternative 2 to redirect the UE to the fake base station or the desired base station and hijack the call. This is a serious security vulnerability for the solutions in Alternative 1 and Alternative 2 that needs to be resolved.
[0063] Example embodiments of the present disclosure provide a solution for voice fallback security enhancement to solve the above-mentioned problems and one or more potential problems among other potential problems. According to the solution, the first device generates an integrity protection key and a cryptographic key based on a paging key and non-access stratum (NAS) algorithm information. The first device uses the cryptographic key to decrypt the voice fallback information in the message received from the second device, and uses the integrity protection key to verify the integrity of the voice fallback information. If the verification of the integrity of the voice fallback information fails, the first device discards the message. In this way, the security of the voice fallback information is guaranteed. In the following, the principles of the present disclosure will refer to Figures 2 to 9 is described.
[0064] Figure 2 FIG. 200 is a signaling diagram of a process for voice fallback security enhancement according to some example implementations of the present disclosure. The process 200 may involve: Figure 1 The first device 110, the second device 120 and the third device 130 are shown. Although the process 200 has been Figure 1 The process is described in the communication environment 100, but the process is also applicable to other communication scenarios.
[0065] like Figure 2 As shown, the first device 110 generates 215 an integrity protection key and a cipher key based on a paging key and non-access stratum (NAS) algorithm information. In the following, the integrity protection key may be represented by K PCHintIndicates that the cryptographic key can be represented by K PCHenc Indicated by, and the paging key can be represented by K PCH express.
[0066] In some implementations, the first device 110 may generate integrity protection keys and cryptographic keys during NAS security context establishment.
[0067] In some implementations, after the primary authentication 210 of the first device 110 with the third device 130 is deemed successful, the NAS security context establishment may be performed. For the primary authentication of the first device 110, the first device 110 may send a registration request to the third device 130. The registration request may include capability information about the first device 110. The capability information may indicate whether the first device 110 supports paging key derivation in the first device 110. The third device 130 may use the proposed procedure for the first device 110 that supports paging key derivation. For older versions of terminal devices (such as Release 15 or Release 16) in which such paging key derivation is not supported, the third device 130 will not send a paging message in a secure manner.
[0068] Similarly, the third device 130 generates 220 an integrity protection key and a cryptographic key based on the paging key and the NAS algorithm information.
[0069] In some implementations, the first device 110 or the third device 130 may generate a paging key based on a first key for access and mobility management (AMF) and at least one of the following:
[0070] a first predetermined value,
[0071] · The string associated with the paging channel,
[0072] The length of the string, or
[0073] An identification of the first device 110 .
[0074] Figure 3 An example of key derivation for paging according to some implementations of the present disclosure is shown. Figure 3 As shown, the first key (K AMF The first predetermined value, the string "PCH" associated with the paging channel, the length of the string (0x000x03), and the 5G-temporary mobile subscriber identity (TMSI) of the first device 110 are used as inputs to a key derivation function (KDF) to generate a paging key K. PCH .
[0075] In some implementations, the first predetermined value can be in the range of 0x69-0x79, 0x7B-0x7D, and 0x83-0x84.
[0076] The paging key K is generated PCH , the first device 110 or the third device 130 based on the paging key K PCH and NAS algorithm information to generate integrity protection keys and cryptographic keys.
[0077] In some implementations, the NAS algorithm information may include at least one of the following:
[0078] A second predetermined value,
[0079] The algorithm type specifier,
[0080] The length of the algorithm type specifier,
[0081] NAS algorithm identifier, or
[0082] The length of the NAS algorithm identifier (ID).
[0083] In some implementations, the second predetermined value can be in the range of 0x69-0x79, 0x7B-0x7D, and 0x83-0x84.
[0084] By way of example only, and not to limit the scope of the present disclosure, the algorithm type specifier may be N-NAS-enc-alg, the length of the algorithm type specifier may be 0x000x01, and the length of the NAS algorithm may be 0x00 0x01.
[0085] It should be noted that since the 5G-TMSI changes frequently (i.e., after each successful paging process), the paging key K PCH , the integrity protection key K PCHint and the cryptographic key K PCHenc It will be very fresh every time.
[0086] In some implementations, the first device 110 may receive the NAS algorithm information from the second device 120. In some implementations, the first device 110 may receive the NAS algorithm information from the second device 120 in a security mode command procedure. For example, the first device 110 may receive the NAS algorithm information from the second device 120 in a paging message or a system information block (SIB) message.
[0087] In some implementations, the NAS algorithm information may be predefined at the first device 110 .
[0088] Reference Figure 2After generating the paging key, the third device 130 sends 225 a paging request to the second device 120. The paging request includes the paging key, the NAS algorithm information, and the voice service type indication. Accordingly, the second device 120 receives the paging request from the third device 130.
[0089] In some implementations, the second device 120 may determine whether the first NAS algorithm indicated by the NAS algorithm identifier is not available for the second device 120. If the first NAS algorithm indicated by the NAS algorithm identifier is not available for the second device 120, the second device 120 may send an indication of a second NAS algorithm available to the second device 120 to the third device 130. In other words, the second device 120 may not support the NAS algorithm identifier indicated by the third device 130. In this case, the second device 120 may reject the paging request, and the third device 130 may select another NAS algorithm supported by the first device 110 (received in the initial capability information about the first device 110) for the second device 120.
[0090] In some implementations, the first device 110, the second device 120, and the third device 130 may be expected to support all algorithms or a minimum set of algorithms anyway. This will optimize delays in the delivery of paging messages.
[0091] Upon receiving the paging request, the second device 120 may decide to perform voice fallback for the first device 110. Accordingly, the second device 120 generates 230 voice fallback information based on the voice service type indication in the paging request.
[0092] In turn, the second device 120 generates 235 an integrity protection key and a cipher key based on the paging key and the NAS algorithm information.
[0093] Furthermore, the second device 120 generates 240 the encrypted and integrity-protected voice fallback information by integrity-protecting the voice fallback information using the integrity protection key and by encrypting the voice fallback information using the cryptographic key.
[0094] In some implementations, the encrypted and integrity-protected voice fallback information may include integrity-protected voice fallback information and encrypted voice fallback information.
[0095] In some implementations, the second device 120 may generate a message authentication code for integrity (MAC-I) based on at least one of the following:
[0096] Integrity protection keys,
[0097] The first count value,
[0098] Voice fallback information,
[0099] The direction of transmission of voice fallback information, or
[0100] ·Bearer identity assigned to the paging channel.
[0101] In such an implementation, the second device 120 may determine the MAC-I as integrity-protected voice fallback information.
[0102] Figure 4 An example of MAC-I generation for paging according to some implementations of the present disclosure is shown. Figure 4 As shown, the integrity protection key K PCHint , a first count value (represented by COUNT), voice fallback information (represented by MESSAGE), the direction of transmission of the voice fallback information (represented by DIRECTION), and a bearer identifier allocated for the paging channel (represented by BEARER) are used as inputs to the integrity NAS algorithm (NIA).
[0103] As an example only and not intended to limit the scope of the present disclosure, the integrity protection key K PCHint It may have 128 bits, the first count value "COUNT" may be equal to 1, the direction of transmission of the voice fallback information "DIRECTION" may be 1 for the downlink (DL) and 0 for the uplink (UL), and the bearer identifier "BEARER" may have 5 bits.
[0104] In some implementations, the second device 120 may generate the keystream block based on at least one of the following:
[0105] Cryptographic keys,
[0106] The second count value,
[0107] · Bearer identifier assigned to the paging channel,
[0108] The direction of transmission of voice fallback information, or
[0109] The required length of the keystream block.
[0110] In such an implementation, the second device 120 may generate a paging block based on the voice back-off information, and generate encrypted voice back-off information based on the keystream block and the paging block.
[0111] Figure 5 An example of a process for encrypting voice fallback information according to some implementations of the present disclosure is shown. Figure 5 As shown, the second device 120 uses the cryptographic key K PCHenc, a second count value (represented by COUNT), a bearer identifier allocated for the paging channel (represented by BEARER), the direction of transmission of the voice fallback information (represented by DIRECTION), and the required length of the key stream block (represented by LENGTH) are used as inputs to the cryptographic NAS algorithm (NEA) to generate a key stream block 510.
[0112] As an example only and not intended to limit the scope of the present disclosure, the cryptographic key K PCHenc It may have 128 bits, the second count value "COUNT" may be equal to 1, the direction of transmission of the voice fallback information "DIRECTION" may be 1 for the downlink (DL) and may be 0 for the uplink (UL), and the bearer identifier "BEARER" may have 5 bits.
[0113] Additionally, the second device 120 may generate a paging block 520 in plain text based on the voice fallback information.
[0114] In turn, the second device 120 may generate a ciphertext block 530 based on the keystream block 510 and the paging block 520 in plain text. For example, the second device 120 may generate the ciphertext block 530 using a bit-by-bit binary addition of the keystream block 510 and the paging block 520 in plain text. The second device 120 may then determine the ciphertext block 530 as encrypted voice fallback information.
[0115] In the same way, the first device 110 can use the cryptographic key K PCHenc , a second count value (represented by COUNT), a bearer identifier allocated for the paging channel (represented by BEARER), the direction of transmission of the voice fallback information (represented by DIRECTION), and the required length of the key stream block (represented by LENGTH) are used as inputs of the NEA to generate a key stream block 540.
[0116] In addition, the first device 110 may restore the plaintext paging block 520 based on the ciphertext block 530 and the keystream block 540. For example, the first device 110 may restore the paging block 520 using bit-by-bit binary addition of the ciphertext block 530 and the keystream block 540.
[0117] Reference Figure 2 , after generating the encrypted and integrity-protected voice fallback information, the second device 120 sends 245 a message to the first device 110 in idle mode, the message including the encrypted and integrity-protected voice fallback information.
[0118] In some implementations, the encrypted and integrity-protected voice back-off information may include a MAC-I and a ciphertext block 530 .
[0119] In some implementations, the second device 120 may send a paging indication in a paging indication channel (PICH) and send the encrypted voice fallback information in a Uu paging message in the paging channel. For example, the second device 120 may include the encrypted voice fallback information in the Uu paging message as a paging payload.
[0120] Alternatively, the second device 120 may send the encrypted voice fallback information in a SIB message and send the voice service type in a Uu paging message.
[0121] Accordingly, the first device 110 receives a message from the second device 120 , the message including the encrypted and integrity-protected voice fallback information.
[0122] Upon receiving the message, the first device 110 decrypts 250 the voice fallback information using the cryptographic key.
[0123] In addition, the first device 110 verifies 255 the integrity of the voice fallback information using the integrity protection key.
[0124] In some implementations, to verify the integrity of the voice fallback information, the first device 110 may generate an X-MAC based at least on the integrity protection key. Figure 4 The X-MAC is generated in a similar manner to the example of . If the X-MAC does not correspond to the MAC-I received from the second device 120, the verification of the integrity protection fails. In this case, the first device 110 discards 260 the message. As a result, the first device 110 abandons the redirection for the voice call and continues to remain in idle mode.
[0125] On the other hand, if the X-MAC corresponds to the received MAC-I, the integrity protection is verified successfully. In this case, the first device 110 may select a cell for the voice call based on the voice fallback information.
[0126] In some implementations, the voice fallback information may include parameters required to select a target cell in which the first device 110 is redirected to connect for the voice call. In an implementation where the voice fallback information is EPS fallback information, the first device 110 may select a target cell in E-UTRAN. For example, the first device 110 may select a target cell provided by the fourth device 140. The first device 110 may then perform an RRC connection establishment with the fourth device 140. In turn, the first device 110 may perform a tracking area update (TAU) and a voice call establishment with the fifth device 150.
[0127] Figure 6FIG. 6 is a flowchart of an example method 600 implemented at a first device according to some example embodiments of the present disclosure. For discussion purposes, the method 600 will refer to Figure 1 It is described from the perspective of the first device 110 .
[0128] At block 610, the first device 110 generates an integrity protection key and a cryptographic key based on the paging key and the NAS algorithm information.
[0129] At block 620, the first device 110 receives a message from the second device in idle mode, the message including voice fallback information. The voice fallback information is integrity protected by an integrity protection key and encrypted by a cryptographic key.
[0130] At block 630 , the first device 110 decrypts the voice fallback information using the cryptographic key.
[0131] At block 640 , the first device 110 , in response to a failure to verify the integrity of the voice fallback information using the integrity protection key, discards the message.
[0132] In some implementations, the method 600 further includes generating a paging key based on the first key for access and mobility management and at least one of: a first predetermined value, a string associated with a paging channel, a length of the string, or an identification of the first device.
[0133] In some implementations, the NAS algorithm information includes at least one of the following: a second predetermined value, an algorithm type specifier, a length of the algorithm type specifier, a NAS algorithm identifier, or a length of the NAS algorithm identifier.
[0134] In some implementations, method 600 further includes receiving NAS algorithm information from the second device.
[0135] In some implementations, the method 600 further includes, in response to successfully verifying the integrity of the voice fallback information using the integrity protection key, selecting a target cell for the voice call based on the voice fallback information.
[0136] Figure 7 FIG. 7 is a flowchart of an example method 700 implemented at a second device according to some example embodiments of the present disclosure. For discussion purposes, the method 700 will refer to Figure 1 It is described from the perspective of the second device 120 .
[0137] At block 710, the second device 120 receives a paging request from a third device, the paging request including a paging key, NAS algorithm information, and a voice service type indication.
[0138] At block 720 , the second device 120 generates voice fallback information based on the voice service type indication.
[0139] At block 730, the second device 120 generates an integrity protection key and a cipher key based on the paging key and the NAS algorithm information.
[0140] At block 740 , the second device 120 generates encrypted and integrity-protected voice back-off information by integrity-protecting the voice back-off information using the integrity protection key and by encrypting the voice back-off information with the cryptographic key.
[0141] At block 750 , the second device 120 sends a message to the first device, the message including the encrypted and integrity-protected voice fallback information.
[0142] In some implementations, the NAS algorithm information includes at least one of the following: a second predetermined value, an algorithm type specifier, a length of the algorithm type specifier, a NAS algorithm identifier, or a length of the NAS algorithm identifier.
[0143] In some implementations, method 700 further includes: based on determining that the first NAS algorithm indicated by the NAS algorithm identifier is not available for the second device, sending an indication of a second NAS algorithm available for the second device to the third device.
[0144] In some implementations, method 700 further includes sending NAS algorithm information to the first device.
[0145] In some implementations, generating encrypted and integrity-protected voice fallback information includes: generating a message authentication code for integrity (MAC-I) based on at least one of the following items: an integrity protection key, a first count value, voice fallback information, a direction of transmission of the voice fallback information, or a bearer identifier allocated for a paging channel; and determining the MAC-I as integrity-protected voice fallback information.
[0146] In some implementations, generating encrypted and integrity-protected voice fallback information includes: generating a keystream block based on at least one of: a cryptographic key, a second count value, a bearer identifier assigned to a paging channel, a direction of transmission of the voice fallback information, or a required length of the keystream block; generating a paging block based on the voice fallback information; and generating encrypted voice fallback information based on the keystream block and the paging block.
[0147] refer to Figures 1 to 5 The described example implementation of the present disclosure may also be applied to methods 600 and 700. Therefore, details of the example implementation are omitted.
[0148] In some example embodiments, a device capable of performing any of the methods 600 (e.g., a first device) may include a component for performing the corresponding steps of the method 600. The component may be implemented in any suitable form. For example, the component may be implemented in the form of a circuit system or a software module.
[0149] In some example embodiments, the first device includes: a component for generating an integrity protection key and a cryptographic key based on a paging key and NAS algorithm information at the first device; a component for receiving a message from a second device in an idle mode, the message including voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; a component for decrypting the voice fallback information using the cryptographic key; and a component for discarding the message in response to a failure to verify the integrity of the voice fallback information using the integrity protection key.
[0150] In some implementations, the first apparatus further includes: means for generating a paging key based on the first key for access and mobility management and at least one of: a first predetermined value, a string associated with a paging channel, a length of the string, or an identification of the first device.
[0151] In some implementations, the NAS algorithm information includes at least one of the following: a second predetermined value, an algorithm type specifier, a length of the algorithm type specifier, a NAS algorithm identifier, or a length of the NAS algorithm identifier.
[0152] In some implementations, the first apparatus further includes means for receiving NAS algorithm information from the second device.
[0153] In some implementations, the first apparatus further includes means for selecting a target cell for the voice call based on the voice fallback information in response to success of verifying the integrity of the voice fallback information using the integrity protection key.
[0154] In some example embodiments, a device capable of performing any of the methods 700 (e.g., a second device) may include a component for performing the corresponding steps of the method 700. The component may be implemented in any suitable form. For example, the component may be implemented in the form of a circuit system or a software module.
[0155] In some example embodiments, the second device includes: a component for receiving a paging request from a third device, the paging request including a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; a component for generating voice fallback information based on the voice service type indication; a component for generating an integrity protection key and a cryptographic key based on the paging key and the NAS algorithm information; a component for generating encrypted and integrity-protected voice fallback information by integrity-protecting the voice fallback information using the integrity protection key and by encrypting the voice fallback information using the cryptographic key; and a component for sending a message to the first device, the message including the encrypted and integrity-protected voice fallback information.
[0156] In some implementations, the NAS algorithm information includes at least one of the following: a second predetermined value, an algorithm type specifier, a length of the algorithm type specifier, a NAS algorithm identifier, or a length of the NAS algorithm identifier.
[0157] In some implementations, the second apparatus further includes means for sending, to a third device, an indication of a second NAS algorithm available to the second device based on determining that the first NAS algorithm indicated by the NAS algorithm identification is not available to the second device.
[0158] In some implementations, the second apparatus further includes: a component for sending NAS algorithm information to the first device.
[0159] In some implementations, a component for generating encrypted and integrity-protected voice fallback information includes: a component for generating a message authentication code for integrity (MAC-I) based on at least one of the following items: an integrity protection key, a first count value, voice fallback information, a direction of transmission of the voice fallback information, or a bearer identifier allocated for a paging channel; and determining the MAC-I as integrity-protected voice fallback information.
[0160] In some implementations, the components for generating encrypted and integrity-protected voice fallback information include: components for generating a keystream block based on at least one of the following items: a cryptographic key, a second count value, a bearer identifier assigned to a paging channel, a direction of transmission of the voice fallback information, or a required length of the keystream block; components for generating a paging block based on the voice fallback information; and components for generating encrypted voice fallback information based on the keystream block and the paging block.
[0161] Figure 8 800 is a simplified block diagram of a device 800 suitable for implementing an embodiment of the present disclosure. The device 800 may be provided to implement a communication device, such as Figure 1The first device 110 or the second device 120 is shown. As shown in the figure, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.
[0162] The communication module 840 is used for two-way communication. The communication module 840 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary for communication with other network elements.
[0163] Processor 810 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 800 may have multiple processors, such as application specific integrated circuit chips, which are time-slaved to a clock synchronized with a main processor.
[0164] The memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 824, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that do not persist during power outages.
[0165] The computer program 830 includes computer executable instructions executed by the associated processor 810. The program 830 may be stored in the ROM 824. The processor 810 may perform any suitable actions and processes by loading the program 830 into the RAM 822.
[0166] The embodiments of the present disclosure may be implemented by a program 830, so that the apparatus 800 may execute the following steps: Figures 1 to 7 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.
[0167] In some example embodiments, the program 830 may be explicitly contained in a computer-readable medium, which may be included in the device 800 (e.g., in the memory 820) or in other storage devices accessible to the device 800. The device 800 may load the program 830 from the computer-readable medium to the RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig. 9An example of a computer readable medium 900 in the form of a CD or DVD is shown. The computer readable medium has a program 830 stored thereon.
[0168] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.
[0169] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target physical or virtual processor to perform the above referenced Figure 6 and 7 Methods 600 and 700 of the present invention. Typically, a program module includes a routine, program, library, object, class, component, data structure, etc. that performs a specific task or implements a specific abstract data type. In various embodiments, the functions of the program modules can be combined or split between program modules as needed. The machine executable instructions of the program modules can be executed in a local or distributed device. In a distributed device, the program modules can be located in both local and remote storage media.
[0170] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code is implemented when executed by the processor or controller in the flow chart and / or the block diagram. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.
[0171] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.
[0172] The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. A more specific example of a computer readable storage medium will include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0173] In addition, although the operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in order or performing all the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0174] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Instead, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1. A first device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to: generating an integrity protection key and a cipher key based on a paging key and non-access stratum (NAS) algorithm information; receiving a message from a second device, the message comprising voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; decrypting the voice fallback information using the cryptographic key; as well as In response to a failure to verify the integrity of the voice fallback information using the integrity protection key, discarding the message.
2. The first device according to claim 1, wherein the first device is further configured to: The paging key is generated based on a first key for access and mobility management and at least one of: A first predetermined value, The string associated with the paging channel, the length of the string, or The identifier of the first device.
3. The first device according to claim 1, wherein the NAS algorithm information comprises at least one of the following items: The second predetermined value, The algorithm type specifier, The length of the algorithm type specifier, NAS algorithm identifier, or The length of the NAS algorithm identifier.
4. The first device according to claim 1, wherein the first device is further configured to: The NAS algorithm information is received from the second device.
5. The first device according to claim 1, wherein the first device is further configured to: In response to success in verifying the integrity of the voice fallback information using the integrity protection key, a target cell for a voice call is selected based on the voice fallback information.
6. A second device, comprising: at least one processor; as well as at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device to: receiving a paging request from a third device, the paging request including a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; generating voice fallback information based on the voice service type indication; Generate an integrity protection key and a cipher key based on the paging key and the NAS algorithm information; Generating encrypted and integrity-protected voice fallback information by integrity protecting the voice fallback information using the integrity protection key and encrypting the voice fallback information using the cryptographic key; as well as A message is sent to the first device, the message including the encrypted and integrity-protected voice fallback information.
7. The second device according to claim 6, wherein the NAS algorithm information comprises at least one of the following items: The second predetermined value, The algorithm type specifier, The length of the algorithm type specifier, NAS algorithm identifier, or The length of the NAS algorithm identifier.
8. The second device according to claim 7, wherein the second device is further configured to: Based on determining that the first NAS algorithm indicated by the NAS algorithm identifier is not available for the second device, an indication of a second NAS algorithm available for the second device is sent to the third device.
9. The second device according to claim 6, wherein the second device is further configured to: Send the NAS algorithm information to the first device.
10. The second device of claim 6, wherein the second device is caused to generate the encrypted and integrity-protected voice fallback information by: Generate a message authentication code for integrity (MAC-I) based on at least one of the following: the integrity protection key, The first count value, The voice fallback information, the direction of transmission of the voice fallback information, or a bearer identifier assigned to a paging channel; and The MAC-I is determined as integrity-protected voice fallback information.
11. The second device of claim 6, wherein the second device is caused to generate the encrypted and integrity-protected voice fallback information by: Generate a keystream block based on at least one of the following: the cryptographic key, The second count value, Bearer identifier assigned to the paging channel, the direction of transmission of the voice fallback information, or the desired length of the keystream block; generating a paging block based on the voice fallback information; and Encrypted voice fallback information is generated based on the keystream block and the paging block.
12. A method comprising: At the first device, generating an integrity protection key and a cipher key based on a paging key and non-access stratum (NAS) algorithm information; In idle mode, receiving a message from a second device, the message including voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; decrypting the voice fallback information using the cryptographic key; as well as In response to a failure to verify the integrity of the voice fallback information using the integrity protection key, discarding the message.
13. The method according to claim 12, further comprising: The paging key is generated based on a first key for access and mobility management and at least one of: A first predetermined value, The string associated with the paging channel, the length of the string, or The identifier of the first device.
14. The method according to claim 12, wherein the NAS algorithm information comprises at least one of the following items: The second predetermined value, The algorithm type specifier, The length of the algorithm type specifier, NAS algorithm identifier, or The length of the NAS algorithm identifier.
15. The method according to claim 12, further comprising: The NAS algorithm information is received from the second device.
16. The method according to claim 12, further comprising: In response to success in verifying the integrity of the voice fallback information using the integrity protection key, a target cell for a voice call is selected based on the voice fallback information.
17. A method comprising: At the second device, receiving a paging request from a third device, the paging request including a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; generating voice fallback information based on the voice service type indication; Generate an integrity protection key and a cipher key based on the paging key and the NAS algorithm information; Generating encrypted and integrity-protected voice fallback information by integrity-protecting the voice fallback information using the integrity protection key and encrypting the voice fallback information using the cryptographic key; as well as A message is sent to the first device, the message including the encrypted and integrity-protected voice fallback information.
18. The method according to claim 17, wherein the NAS algorithm information comprises at least one of the following items: The second predetermined value, The algorithm type specifier, The length of the algorithm type specifier, NAS algorithm identifier, or The length of the NAS algorithm identifier.
19. The method according to claim 18, further comprising: Based on determining that the first NAS algorithm indicated by the NAS algorithm identifier is not available for the second device, an indication of a second NAS algorithm available for the second device is sent to the third device.
20. The method of claim 17, further comprising: Send the NAS algorithm information to the first device.
21. The method of claim 17, wherein generating the encrypted and integrity-protected voice fallback information comprises: Generate a message authentication code for integrity (MAC-I) based on at least one of the following: the integrity protection key, The first count value, The voice fallback information, the direction of transmission of the voice fallback information, or a bearer identifier assigned to a paging channel; and The MAC-I is determined as integrity-protected voice fallback information.
22. The method of claim 17, wherein generating the encrypted and integrity-protected voice fallback information comprises: Generate a keystream block based on at least one of the following: the cryptographic key, The second count value, Bearer identifier assigned to the paging channel, the direction of transmission of the voice fallback information, or the desired length of the keystream block; generating a paging block based on the voice fallback information; and Encrypted voice fallback information is generated based on the keystream block and the paging block.
23. A first device, comprising: means for generating, at the first device, an integrity protection key and a cipher key based on a paging key and non-access stratum (NAS) algorithm information; means for receiving, in idle mode, a message from a second device, the message comprising voice fallback information, the voice fallback information being integrity protected by the integrity protection key and encrypted by the cryptographic key; A component for decrypting the voice fallback information using the cryptographic key; as well as Means for discarding the message in response to a failure to verify the integrity of the voice fallback information using the integrity protection key.
24. A second device, comprising: means for receiving a paging request from a third device, the paging request comprising a paging key, non-access stratum (NAS) algorithm information, and a voice service type indication; A component for generating voice fallback information based on the voice service type indication; A component for generating an integrity protection key and a cipher key based on the paging key and the NAS algorithm information; A component for generating encrypted and integrity-protected voice fallback information by integrity protecting the voice fallback information using the integrity protection key and encrypting the voice fallback information using the cryptographic key; as well as Means for sending a message to a first device, the message including the encrypted and integrity-protected voice fallback information.
25. A computer-readable medium comprising program instructions, wherein the program instructions are used to cause an apparatus to at least perform the method according to any one of claims 12 to 16.
26. A computer-readable medium comprising program instructions, wherein the program instructions are used to cause an apparatus to at least perform the method according to any one of claims 17 to 22.
