METHOD AND APPARATUS FOR COMMUNICATION SYSTEMS INVOLVING INCORPORATING USER EQUIPMENT IDENTIFIERS INTO CONTROL CHANNEL TRANSMISSIONS
20230007642 · 2023-01-05
Assignee
Inventors
Cpc classification
H04L5/0053
ELECTRICITY
H04W72/20
ELECTRICITY
H04W92/10
ELECTRICITY
International classification
Abstract
The apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to duplicate base station computation of an identifier value for a user equipment, and search for one or more control channel transmissions incorporating an identifier value matching the identifier value.
Claims
1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: base station computation of an identifier value for a user equipment; and for one or more control channel transmissions incorporating an identifier value matching the identifier value.
2. The apparatus according to claim 1, wherein the duplicating base station computation of an identifier value for the user equipment comprises computing an identifier value based on one or more input parameter values and one or more mathematical functions used at the base station to compute an identifier value for the user equipment.
3. The apparatus according to claim 2, wherein an identifier value is based at least partly on a value of a time-related parameter; and wherein the computed identifier value is effective for a time period related to the value of the time-related parameter.
4. The apparatus according to claim 3, wherein athe at least one memory and the instructions are further configured to , with the at least on processor, cause the apparatus to: base station computation of a further identifier value; and after expiry of the time period, for one or more control channel transmissions incorporating an identifier value matching the further identifier value.
5. The apparatus according to claim 3, wherein the time-related parameter is a system frame number.
6. The apparatus according to claim 2, wherein the an identifier value is at least partly based on a security key value derived at least partly from a secret key shared between the base station and the user equipment.
7. The apparatus according to claim 2, wherein the computing an identifier value is at least partly based on a start value included in a random access reply message.
8. The apparatus according to claim 1, wherein the one or more control channel transmissions indicate radio resources allocated to the user equipment for downlink and/or uplink transmissions.
9. An apparatus comprising: at least one processor: and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: incorporate the identifier value into one or more control channel transmissions specific to the user equipment.
10. The apparatus according to claim 9, wherein the duplicating user equipment computation of an identifier value for the user equipment comprises computing an identifier value based on one or more input parameter values and one or more mathematical functions used at the user equipment to compute an identifier value for the user equipment.
11. The apparatus according to claim 9, wherein the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus: to the user equipment a base value for computation of an identifier value; and in response to thereafter determining that computation based on the base value generates an identifier value that clashes with one or more identifier values for one or more other user equipment sharing radio resources for control channel transmissions with the user equipment send a new base value to the user equipment.
12-15. (canceled)
16. A method comprising: duplicating base station computation of an identifier value for a user equipment; and searching for one or more control channel transmissions incorporating an identifier value matching the identifier value.
17. The method according to claim 16, wherein the duplicating base station computation of an identifier value for the user equipment comprises computing an identifier value based on one or more input parameter values and one or more mathematical functions used at the base station to compute an identifier value for the user equipment.
18. The method according to claim 17, wherein the computing an identifier value is based at least partly on a value of a time-related parameter; and wherein the computed identifier value is effective for a time period related to the value of the time-related parameter.
19. The method according to claim 18, further comprising: duplicating base station computation of a further identifier value; and after expiry of the time period, searching for one or more control channel transmissions incorporating an identifier value matching the further identifier value.
20. The method according to claim 18, wherein the time-related parameter is a system frame number.
21. The method according to claim 17, wherein the computation of an identifier value is at least partly based on a security key value derived at least partly from a secret key shared between the base station and the user equipment.
22. The method according to claim 17, wherein the computation of an identifier value is at least partly based on a start value included in a random access reply message.
23. The method according to claim 16, wherein the one or more control channel transmissions indicate radio resources allocated to the user equipment for downlink and/or uplink transmissions.
Description
BRIEF DESCRIPTION OF THE FIGURES
[0066] Some example embodiments will now be described in further detail, by way of example only, with reference to the following examples and accompanying drawings, in which:
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
DETAILED DESCRIPTION
[0076] In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G), without restricting the embodiments to such an architecture, however. The embodiments may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system (UMTS) radio access network (UTRAN), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof.
[0077]
[0078] The embodiments are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties.
[0079] The example of
[0080]
[0081] A communications system typically comprises more than one (e/g)NodeB in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signalling purposes. The (e/g)NodeB is a computing device configured to control the radio resources of communication system it is coupled to. The NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment. The (e/g)NodeB includes or is coupled to transceivers. From the transceivers of the (e/g)NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to devices. The antenna unit may comprise a plurality of antennas or antenna elements. The (e/g)NodeB is further connected to the core network 106 (CN or next generation core NGC). Depending on the deployed technology, the (e/g)NodeB is connected to a serving and packet data network gateway (S-GW+P-GW) or user plane function (UPF), for routing and forwarding user data packets and for providing connectivity of devices to one or more external packet data networks, and to a mobile management entity (MME) or access mobility management function (AMF), for controlling access and mobility of the devices.
[0082] Exemplary embodiments of a device are a subscriber unit, a user device, a user equipment (UE), a user terminal, a terminal device, a mobile station, a mobile device, etc
[0083] The device typically refers to a mobile or static device (e.g. a portable or non-portable computing device) that includes wireless mobile communication devices operating with or without an universal subscriber identification module (USIM), including, but not limited to, the following types of devices: mobile phone, smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction, e.g. to be used in smart power grids and connected vehicles. The device may also utilise cloud. In some applications, a device may comprise a user portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation is carried out in the cloud.
[0084] The device illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station. The device (or in some embodiments a layer 3 relay node) is configured to perform one or more of user equipment functionalities.
[0085] Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected information and communications technology, ICT, devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.
[0086] Additionally, although the apparatuses have been depicted as single entities, different units, processors and/or memory units (not all shown in
[0087] The current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network. The low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).
[0088] The communication system is also able to communicate with other networks 112, such as a public switched telephone network, or a VoIP network, or the Internet, or a private network, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in
[0089] The technology of Edge cloud may be brought into a radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN). Using the technology of edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. Application of cloud RAN architecture enables RAN real time functions being carried out at or close to a remote antenna site (in a distributed unit, DU 108) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 110).
[0090] It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio, NR) networks are being designed to support multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well.
[0091] 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, Mobile Broadband, (MBB) or ensuring service availability for critical communications, and future railway/maritime/aeronautical communications. Satellite communication may utilise geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node or by a gNB located on-ground or in a satellite.
[0092] It is clear to a person skilled in the art that the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the device may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g)NodeBs or may be a Home(e/g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The (e/g)NodeBs of
[0093] For fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs has been introduced. Typically, a network which is able to use “plug-and-play” (e/g)Node Bs, includes, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in
[0094]
[0095] Later, both UE 100 and BS 104 separately perform the same pre-determined computation of an identifier value (hereafter referred to as dynamic C-RNTI or DC-RNTI value) for the UE 100, using the base C-RNTI value as one input (OPERATIONS 206a and 206b of
[0096] In this example, K.sub.RNTI is derived from existing keys K.sub.eNB or K.sub.gNB, using the key derivation function (KDF) as mentioned in 3GPP TS 33.501, Annex A, with a further input comprising a FC-value from the FC number space controlled by TS 33.220, as mentioned at TS 33.501 A.1.2.
[0097] In this example, the DC-RNTI value is computed from the base C-RNTI value, the SFN/HFN and KRNTI using a one-way mathematical function, such as the ones specified in the Milenage and Tuak algorithm sets identified in TS35.205 and TS35.231.
[0098] The SFN (used in this example as one of the inputs to compute the DC-RNTI value for UE 100) is broadcast by the cell, and has a value shared by all UEs served by the cell. An incremented SFN value is broadcast every 10 ms (in the physical broadcast channel (PBCH) for the cell). The SFN is 10 bits in length, and may therefore have 1024 different values. The SFN cycle (the time period over which the SFN value repeats) is 1024*10 ms=10.24 seconds.
[0099] In another example, a hyper frame number (HFN) of the kind implemented in LTE is used instead of SFN as an input for computation of the DC-RNTI value. The HFN value increments when the SFN value is equal to 0. The HFN is also 10 bits in length. The HFN cycle (the time period over which the HFN value repeats) is 1024*1024*10 ms=10485.76 second (about 7 days).
[0100] In another example, the timing reference broadcast in 5G NR as part of the 9th System Information Block (SIB9) is used instead of SFN or HFN as one input for computation of the DC-RNTI value.
[0101] BS 104 incorporates the DC-RNTI value computed at BS 104 for UE 100 into one or more control downlink channel transmissions (e.g. PDCCH transmissions) specific to UE 100 (OPERATION 208 of
[0102] The computed DC-RNTI value is thus used by UE 100 and BS 104 to distinguish control channel transmissions specific to the UE 100 from control channel transmissions specific to other UEs searching the same search space for DCI messages specific thereto. A control channel transmission (e.g. PDCCH transmission) incorporating the computed DC-RNTI value for UE 100 indicates data channel radio resources allocated to uplink transmissions by UE 100 and/or downlink transmissions specific to UE 100.
[0103] UE 100 is representative of a plurality of UEs searching the same search space for PDCCH transmissions incorporating a DC-RNTI value matching a DC-RNTI value computed at the respective UE based on a respective base C-RNTI value and a respective security key (KRNTI).
[0104] According to one example whose representation is shown in
[0105] With reference to
[0106] As mentioned above, one of the input parameters is the SFN value for the cell at the time of DC-RNTI computation, which is different to the SFN value used for the previous DC-RNTI computation and is also different to the SFN value that will be used for the subsequent DC-RNTI computation. In this way, control channel transmissions specific to UE 100 incorporate changing identifier values over time.
[0107] As mentioned above, UE 100 is representative of a plurality of UEs searching the same search space for control channel transmissions incorporating a DC-RNTI value matching the DC-RNTI value computed at UE 100 (based on the respective base C-RNTI value and respective security key value). According to this example embodiment, other UEs (or all UEs) of the plurality of UEs searching the same search space for PDCCH transmissions compute respective fresh DC-RNTI values at the same time. For example, the SFN/HFN values at which DC-RNTI computation is performed is the same for other UEs (e.g. all UEs searching the search space for control channel transmissions).
[0108] According to another example, BS 104 triggers the computation of a fresh DC-RNTI value. For example, the trigger may take the form of an encrypted RRC message.
[0109]
[0110] BS 104 precomputes a sequence of DC-RNTI values for UE 100 based respectively on the predetermined SFN values at which UE 100 is configured to perform DC-RNTI computation (OPERATION 300 of
[0111] Another example technique for avoiding DC-RNTI clashes is as follows. Instead of precomputing a future sequence of DC-RNTI values for UE 100 (and respective future sequences of DC-RNTI values for other UEs sharing the same PDCCH search space with UE 100), BS 104 checks for DC-RNTI clashes each time DC-RNTI values are about to be recomputed at UEs including UE 100. If the precomputation at BS 104 of the next round of DC-RNTIs for the UEs predicts a DC-RNTI clash for UE 100, BS 104 tries one or more new base C-RNTI values for UE 100 until BS 104 finds a new base C-RNTI value for which pre-computation of DC-RNTI values predicts no DC-RNTI clashes; and BS 104 sends the new base C-RNTI value to UE 100.
[0112] The implementation described so far has the advantage that no new information has to be passed between UE 100 and BS 104 for the generation of DC-RNTI values, except when an individual configuration for changing the DC-RNTI value is required, and/or unless a precomputation of DC-RNTI values at BS 104 predicts a DC-RNTI clash. The inputs for computing DC-RNTI values for UE are already available to UE 100. The base C-RNTI value is the C-RNTI value already included in the RAR message; the security key K.sub.RNTI derived from a key already used at UE for other existing purposes at UE 100; and SFN values are already broadcast by the cell.
[0113] According to one example variation, BS 104 sends all parameters for computing the DC-RNTIs to UE 100 in an encrypted RRC message, such as, for example, the RRC reconfiguration message sent by BS 104 following the RRC security command procedure. For example, computation at the UE 100 may be based on: a K.sub.RNTI value included in the encrypted RRC message; a starting value (instead of the C-RNTI value included in the RAR message); and the SFN value.
[0114] According to another example embodiment, UE 100 does not duplicate the BS computation of DC-RNTI values, but instead receives from BS 104 a sequence of DC-RNTI values to use over a period of time.
[0115]
[0116] For all techniques described above, either (i) the information necessary for duplicating base station computation of DC-RNTI at UE 100 or (ii) a set of DC-RNTI values for UE 100, may be included in a RRC reconfiguration message sent to command or trigger a handover of UE 100 from a source cell to a target cell.
[0117] Sending such an encrypted RRC reconfiguration message also in the event of an intra-cell handover (for which the source cell and the target cell are the same and only the used channel is changed) provides an opportunity to securely re-set the computation of DC-RNTI at UE 100 or provide UE 100 with a new sequence of DC-RNTI values.
[0118] Also in the event of restoring a RRC connection via a serving cell (for example, in the event of Beam Failure Recovery), UE may use a DC-RNTI value computed at UE 100 (or one of a sequence of DC-RNTI values received previously in an encrypted message via the serving cell). For the example of computing a DC-RNTI value at UE 100, the UE 100 reads the current SFN value from the master information block (MIB) broadcast by the serving cell.
[0119] The example embodiments described above can reduce the risk of a malicious third party being able to track the PDCCH transmissions specific to UE 100, and thus can increase security against PDCCH-tracking based attacks, and against man-in-the-middle (MITM) attacks by fake base stations (FBSs).
[0120] For example, the example embodiments can reduce the effectiveness of attacks in which the attacker relies on being able to identify PDCCH transmissions related to a GUTI (Globally Unique Temporary Identifier) or SUCI (Subscription Concealed Identifier) included in a register request via data channel resources scheduled by a PDCCH transmission.
[0121] For example, the example embodiments can thus reduce the risk of a malicious third party (with the extra assistance of additional intelligence (like physical observation)) being able to identify the human subscriber using the UE that sent the register request including the GUTI or SUCI.
[0122] For example, the example embodiments can reduce the effectiveness of attacks involving a malicious attacker sending traffic (e.g. a series of silent short messages, or a series of messenger messages) to a public address of a human victim known by the attacker to have a UE served by a particular cell, and then exploiting the characteristics of the traffic resulting from the traffic originated by the malicious attacker (like number and length of messages, timing).
[0123] For example, the example embodiments can increase security in networks where the GUTI is not changed frequently, by increasing the difficulty of determining which PDCCH transmissions are related to a GUTI (i.e. specific to a UE having the GUTI).
[0124] For example, the example embodiments can reduce the effectiveness of malicious attacks involving the attacker finding (by monitoring both source and target cells for a handover of UE 100 (and having possibly also other intelligence)) the C-RNTI value used in a random access (RA) procedure for the UE.
[0125] For example, the example embodiments can increase security against IMP4GT (IMPersonation Attacks in 4G NeTworks) involving an attacker relying on being able to map PDCCH transmissions to a GUTI. IMP4GT is described in a paper entitled “IMP4GT: IMPersonation Attacks in 4G NeTworks by David Rupprecht et al (DO 1:10.14722/ndss.2020.24283).
[0126] For example, the example embodiments can reduce the effectiveness of attacks involving exploitation of unencrypted MAC control elements sent to a certain UE.
[0127]
[0128]
[0129] It is to be noted that embodiments of the present invention may be implemented as circuitry, in software, hardware, application logic or a combination of software, hardware and application logic. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as the base stations or user equipment of the above-described embodiments.
[0130] As used in this application, the term “circuitry” refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the user equipment or base stations of the above-described embodiments, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term “circuitry” would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term “circuitry” would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.
[0131] The described features, advantages, and characteristics of the invention can be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages can be recognized in certain embodiments that may not be present in all embodiments of the invention. One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention.