Deriving a key, sending a configuration message and processing sensing data

The method for deriving session-specific keys using a base key and parameter N through a KDF addresses the need for secure sensing data transmission in ISAC systems, ensuring privacy and integrity of sensing data.

WO2026233731A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/061699
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-06-06
Filing Date
2026-04-23
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The challenge in Integrated Sensing and Communication (ISAC) systems is the need for secure transmission of sensing data from User Equipment (UE) to a Sensing Node, protecting against privacy leakage, disclosure, and tampering threats, while ensuring session-specific key derivation and origin verification for different sensing sessions.

Method used

A method for deriving session-specific keys using a base key and a parameter N through a Key Derivation Function (KDF) to establish secure logical channels between UE and Sensing Node, with session-level access control and data origin verification.

Benefits of technology

Ensures secure and protected transmission of sensing data, preventing unauthorized access and tampering, while enabling session-specific key derivation and origin verification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026061699_12112026_PF_FP_ABST
    Figure EP2026061699_12112026_PF_FP_ABST
Patent Text Reader

Abstract

In an example, a method performed by a wireless device for deriving a key is provided The method comprises receiving a first sensing configuration message configuring a first sensing session in the wireless device, and obtaining a first parameter. The method also comprises deriving at least a first session key for the first sensing session based on a base key and the first parameter.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] DERIVING A KEY, SENDING A CONFIGURATION MESSAGE

[0002] AND PROCESSING SENSING DATA

[0003] Background

[0004] Key Management

[0005] 3GPP defines how keys are stored, updated, and exchanged between the User Equipment (UE) and the network. The authentication and security mode procedures that are performed in the Non Access Stratum (NAS) layer define the key management procedure. A one-way function called f1 is used in a challenge-response mechanism to verify the identity of the UE by the network during the authentication procedure.

[0006] NAS key derivation:

[0007] The signaling messages between UE and the network (Access and Mobility Management Function, AMF) are protected by the NAS key.

[0008] AS Key derivation:

[0009] 3GPP defines the Access Stratum (AS) key derivation process to establish secure communication between UE and the access network. The key derivation utilizes a Key Derivation Function (KDF) as specified in 3GPP TS 33.220 v18.3.0, it combines multiple input parameters to generate unique keys for encryption and integrity protection.

[0010] Key hierarchy and derivation:

[0011] The key hierarchy and derivation in 3GPP defines how the different keys are related and generated from each other. For more information, section 6.2 of 3GPP TS 33.501 v19.2.0 can be referred to.

[0012] Integrated Sensing and Communication (ISAC)

[0013] Integrated sensing and communication (ISAC) is a promising technology candidate for 6G. With ISAC, networks can perform spatial location and state observations about passive (non-connected) objects and properties within the physical environment, such as an object’s presence, size, shape, velocity, or radio propagation properties. This information can be used to offer new services beyond communication, for example Uncrewed (alternatively Unmanned) Aerial Vehicle (UAV) detection and tracking, increased situational awareness in automotive and smart factories, and improving the network performance.Figure 1 is a simplified system view of ISAC which is using UE as a sensing entity.

[0014] Sensing architecture is not standardized yet. Some of the architectural proposal can be found in the following papers:

[0015] • Architecture Proposal for 6G Systems Integrating Sensing and Communication: https: / / www.arxiv.org / pdf / 2411.10138

[0016] • Addressing Privacy Concerns in Joint Communication and Sensing for 6G Networks:

[0017] Challenges and Prospects: https: / / arxiv.org / abs / 2405.01742

[0018] This specification refers to a simplified ISAC system, as shown in Figure 1. In this system, sensing service consumer (application) 110 can request sensing data from the sensing node 120, e.g. via Network Exposure Function (NEF) or an aggregator interface.

[0019] Sensing Service Consumer 110 - can request sensing service from network sensing. The Sensing Service Consumer receives requested sensing results in return. The Sensing Service Consumer is also referred to as Sensing client in contemporary research.

[0020] Sensing Node 120 - provides sensing functionality within the mobile network. The Sensing Node receives requests from clients, orchestrates sensing sessions and returns sensing results. The Sensing Node consists of two main components - sensing control 140 and sensing processing 150. Sensing control 140 orchestrates required sensing sessions based on requests and available sensing entities (radio units with sensing capability). And sensing processing 150 orchestrates the necessary processing steps to convert collected measurements into usable data for the sensing service consumer- sensing result. The Sensing Node is also referred to as Sensing Function in 3GPP Service and System Aspects Working Group 2 (SA2) terminology.

[0021] The sensing node can be co-located with communication network entities such as the gNodeB (gNB), AMF, Authentication Server Function (ALISF) or Unified Data Management (UDM). In those embodiments some steps between the sensing node (or parts of the sensing node such as Sensing Control and Sensing processing) and the communication network entities may be skipped.

[0022] User Equipment (U E) or Sensing Entity 130 - Sensing Entity (SE) is a radio unit with sensing capabilities for sensing signal transmission, reception or both. SE can be in gNB or UE or other sensing nodes depending on deployment. In contemporary research, the Sensing Entity is also referred to as Sensing Unit (SU).Sensing control 140 - manages all required steps to fulfill sensing requests. Sensing requests are turned into internal form of sensing sessions by the Sensing control. One sensing request can be mapped to one or more sensing sessions (e.g. drone tracking might have one session, but traffic monitoring request could be split into parallel sessions for each object type - car, pedestrians, etc.) by the Sensing control.

[0023] Sensing session - is a sequence of orchestration, transmitting and receiving sensing signals and sensing processing to convert measurements into usable information.

[0024] Sensing processing 150 - is a function that manages all necessary aspects of processing sensing measurements and data into usable information. The sensing processing 150 uses processing sessions 151 components to carry out required processing steps on sensing data. There may be one or more processing sessions 151 for each sensing session in sequence or in parallel.

[0025] Processing session 151 : is the worker node or the entity set up by the sensing processing entity 150 which processes the sensing data for a session to extract useful information such as sensing measurements etc. There may be one or more processing sessions 151 for each sensing session in sequence or in parallel. The Processing Session can be orchestrated in a RAN, a core network, an edge network or a cloud network.

[0026] Figure 2 illustrates examples of various ways in which Sensing control, Sensing Processing and Processing sessions entities could be placed in the Sensing Node 120. In particular, Figure 2(a) illustrates an example where Sensing Control and Sensing Processing entity are co-located in Sensing Node; Figure 2(b) illustrates an example where Sensing Control and Sensing Processing entity are logically separated in Sensing Node; and Figure 2(c) illustrates an example where Sensing Control and Sensing Processing entity are logically separated in Sensing Node, and Sensing Processing entity orchestrates processing sessions in Radio Access Network (RAN), core, edge or cloud.

[0027] There is an ongoing discussion on what plane to use for transporting sensing data. Control plane might become too congested with the large-scale data. User plane might not be flexible enough to support the complex sensing data processing pipeline in an optimal way. Introduction of a “data plane” for ISAC and artificial intelligence (Al) purposes is being discussed in 3GPP at the moment.

[0028] There currently exist certain challenge(s). For example, sensing data may include personally identifiable information (PH) of the UE owner and / or PH of other targets in a physical environment and hence the sensing data needs to be protected from various threatssuch as privacy leakage, disclosure and tampering threats. If such channel (i.e. carrying sensing data) is unprotected, an adversary can tamper with the sensing data and badly affect the network sensing service e.g., by causing denial-of-service attacks or poisoning sensing data (i.e., corrupting the sensing data). In ISAC, there is a need to have a secure logical channel between a UE used as sensing entity (e.g. the UE 130) and a sensing node (e.g. the sensing node 120) to securely transmit the sensing data.

[0029] The sensing control entity (e.g. the sensing control entity 140 or the sensing control node 140) may configure multiple sensing sessions on the same UE which may have different access control policies, even if they originate from the same sensing request and sensing service consumer. So, there is a need to protect sensing data belonging to different sensing sessions.

[0030] In addition, the network may also require information about the origin (e.g. from the UE 130) of sensing data. The network may require this information for multiple purposes such as legal obligations, security incident investigation, determining the UE to incentivize for sensing sessions and in general for accounting purposes.

[0031] Summary

[0032] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, examples of this disclosure provide methods for protecting sensing sessions and session data between a UE Sensing Entity (e.g. the UE 130 or the UE sensing node 130) and a Sensing Node (e.g. the sensing node 120 or the sensing entity 120). This includes for example setting up the security and deriving one or more sessionspecific keys (referred to as sensing session keys) for securely transmitting sensing data from the UE to the sensing node. The one or more sensing sessions are configured by a sensing node on a UE sensing entity. Examples of this disclosure include: a method for secure transmission of sensing data; a method employing key derivation in the UE and the sensing node for deriving session-specific keys from base key for secure transmission of sensing data; a method for obtaining and using additional parameter N to derive one or more keys from sensing base key for securely transmitting sensing data between the UE and the sensing node; and a method for sensing node to provision sensing session keys to the entity authorized to process the sensing session data, enforcing sensing session level access control.

[0033] A first example aspect of this disclosure provides a method performed by a wireless device for deriving a key. The method comprises receiving a first sensing configuration messageconfiguring a first sensing session in the wireless device, and obtaining a first parameter. The method also comprises deriving at least a first session key for the first sensing session based on a base key and the first parameter.

[0034] Another example aspect of this disclosure provides a method performed by a sensing control node for sending a sensing configuration message. The method comprises sending, to a wireless device, a first sensing configuration message configuring a first sensing session in the wireless device.

[0035] A further example aspect of this disclosure provides a method performed by a sensing control node for processing sensing data. The method comprises receiving, from a wireless device, sensing data for a first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key. The method also comprises processing the sensing data for the first sensing session.

[0036] A still further example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to the method according to any of the above example aspects.

[0037] A still further example aspect of this disclosure provides apparatus in a wireless device for deriving a key. The apparatus comprises processing circuitry and a memory. The apparatus is configured to receive a first sensing configuration message configuring a first sensing session in the wireless device, and obtain a first parameter. The apparatus is also configured to derive at least a first session key for the first sensing session based on a base key and the first parameter.

[0038] Another example aspect of this disclosure provides apparatus in a sensing control node for sending a sensing configuration message. The apparatus comprises processing circuitry and a memory. The apparatus is configured to send, to a wireless device, a first sensing configuration message configuring a first sensing session in the wireless device.

[0039] An additional example aspect of this disclosure provides apparatus in a sensing control node for processing sensing data. The apparatus comprises processing circuitry and a memory. The apparatus is configured to receive, from a wireless device, sensing data for a first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key. The apparatus is also configured to process the sensing data for the first sensing session.Certain embodiments may provide one or more of the following technical advantage(s). For example, examples of this disclosure may be aligned with the standardized method of key derivation for a UE and / or a communication network. Examples may enforce a key separation principle (i.e. , do not reuse secret key material in different contexts or sessions) by deriving separate keys for separate sensing sessions. Examples may enable bootstrapping sensing data origin to the UE. When the sensing data produced by the UE Sensing Entity 130 is protected by the keys provisioned by the communication network in the UE. Alternatively or in addition, the UE Sensing Entity 130 is protected by the keys derived from a key from the 3GPP key hierarchy. Examples may indirectly provide data origin verification to the sensing data by binding it to the UE. Examples may reinforce session level access control on sensing data processing: The entity processing sensing data would require the keys (encryption and integrity protection keys) to process the sensing data. With example methods, the sensing node 120 could reinforce sensing session level authorization on sensing data and / or the sensing node 120 could provision the keys to the processing node / entity that is authorized to process the sensing data associated to a particular sensing session.

[0040] Brief Description of the Drawings

[0041] For a better understanding of the embodiments of the present disclosure, and to show how the disclosure may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0042] Figure 1 is a simplified system view of ISAC which is using UE as a sensing entity; Figure 2 illustrates examples of various ways in which Sensing control, Sensing Processing and Processing sessions entities could be placed in the Sensing Node;

[0043] Figure 3 is a flow chart illustrating a method in accordance with some embodiments; Figure 4 is a flow chart illustrating a method in accordance with some embodiments; Figure 5 is a flow chart illustrating a method performed by a core network entity according to embodiments of the disclosure;

[0044] Figure 6 illustrates an example of 3GPP Key hierarchy in 5GS;

[0045] Figure 7 illustrates example cases for key derivation and provisioning in sensing node entities;

[0046] Figure 8 is a signalling diagram illustrating a first example embodiment;

[0047] Figure 9 is a signalling diagram illustrating a second example embodiment;

[0048] Figure 10 is a signalling diagram illustrating a third example embodiment;

[0049] Figure 11 is a signalling diagram illustrating a fourth example embodiment;

[0050] Figure 12 is a signalling diagram illustrating a fifth example embodiment;Figure 13 is a signalling diagram illustrating a sixth example embodiment;

[0051] Figure 14 shows an example of a communication system in accordance with some embodiments;

[0052] Figure 15 shows an example of another communication system in accordance with some embodiments;

[0053] Figure 16 shows a wireless device in accordance with some embodiments;

[0054] Figure 17 shows a network node in accordance with some embodiments;

[0055] Figure 18 shows a core network node in accordance with some embodiments; and Figure 19 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0056] Detailed description

[0057] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0058] Figure 3 depicts a method 300 in accordance with particular embodiments, such as for example a method performed by a wireless device for deriving a key. The method 300 may be performed by a wireless device (e.g. UE 1412, station 1512 or wireless device 1600 as described later with reference to Figures 14, 15 and 16 respectively).

[0059] The method 300 begins at step 302, with receiving a first sensing configuration message configuring a first sensing session in the wireless device. Step 304 comprises obtaining a first parameter. Step 306 comprises deriving at least a first session key for the first sensing session based on a base key and the first parameter.

[0060] Figure 4 depicts a method 400 in accordance with particular embodiments, such as for example a method performed by a sensing control node for sending a sensing configuration message. The method 400 may be performed by a network node (e.g. network node 1410, access point 1510 or network node 1700 as described later with reference to Figures 14, 15 and 17 respectively) or a core network node or entity (e.g. core network node 1408, or core network node 1800 as described later with reference to Figures 14 and 18 respectively).

[0061] The method 400 begins at step 402, comprising sending, to a wireless device, a first sensing configuration message configuring a first sensing session in the wireless device.

[0062] Figure 5 depicts a method 500 in accordance with particular embodiments, such as for example a method performed by a sensing control node for processing sensing data. Themethod 500 may be performed by a network node (e.g. network node 1410, access point 1510 or network node 1700 as described later with reference to Figures 14, 15 and 17 respectively) or a core network node or entity (e.g. core network node 1408, or core network node 1800 as described later with reference to Figures 14 and 18 respectively).

[0063] The method 500 begins at step 502, comprising receiving, from a wireless device, sensing data for a first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key. Step 504 comprises processing the sensing data for the first sensing session.

[0064] Particular example embodiments are now described for illustrative purposes.

[0065] As sensing data and sensing control signalling are two different logical classes of sensing related data, it may be possible that different security contexts (keys and logical channel) are used to transport these data. The security contexts for sensing control signalling and sensing data may also terminate in different entities of a sensing node. For example, channel transporting sensing control signalling terminates in a sensing control entity of the sensing node while a channel transporting sensing data terminates in an entity that will process the sensing data, e.g. Processing Sessions.

[0066] This disclosure provides example methods / mechanisms for a UE (used herein interchangeably with wireless device) and a sensing node (e.g. sensing control node) to establish security context for sensing data transmission, for example, establishing a security context between the UE and / or the sensing node to a processing node, which may be for example a sensing processing node, a sensing processing session (e.g. a node capable of processing sessions related to sensing), or a sensing control node.

[0067] It is assumed that the UE 130 and the sensing node120 and / or the sensing control entity 140 (or the sensing control node 140) have already established a security context (e.g., keys) for sensing control signaling.

[0068] Below are provided example steps for establishing the sensing session keys in a wireless device (e.g. the UE 130) and a sensing node (e.g. the sensing node 120 or the sensing control node 140) and provisioning the sensing session keys in an entity which will be processing the sensing data (e.g. the sensing processing node 150, the sensing processing session entity 151).

[0069] Depending on the placement of various entities as shown in Figure 2, the entity processing the sensing data might be different. In Figure 2(a), corresponding to case a in Figure 7,where all sensing functionalities are co-located in the sensing node 120, the entity processing the sensing data will be sensing node. In Figure 2(b), corresponding to case b in Figure 7, entity processing the sensing data will be the sensing processing entity 150 (or the sensing processing node 150) while in Figure 2(c), corresponding to case c in Figure 7, entity processing the sensing data will be the Processing Session entity 151 (or the processing session node 151) setup to process sensing session data. In some examples, sensing data for different sessions may be sent to different entities, e.g. different sensing processing nodes or different sensing processing sessions that may reside in the same node or different nodes.

[0070] Examples for determining base key for sensing:

[0071] There are many ways the UE 130 and the sensing node 120 may decide on the base key for sensing. The base key determines the key material for sensing data protection in the UE 130 and the sensing node 120.

[0072] Example Case 1: If a network (e.g. a communication network such as a 5G network, a 6G network) has provisioned ISAC specific keys or sensing specific keys in a subscription module of the UE or to a Mobile Eguipment (ME) part of the UE for sensing purpose which the UE uses to protect the sensing data. The sensing node 120 might have these keys already provisioned or the sensing node 120 may obtain them from a communication network entity e.g. a UDM or an O&M entity of the communication network.

[0073] Example Case 2: After successful primary authentication between the UE 130 and a network, and further depending on the embodiment, the UE 130 and the sensing node 120 use one of the intermediary keys from 3GPP key hierarchy (as shown in Figure 6) to derive base key for sensing. E.g., KAUSF, KAMF, K9NB, Kakma or KSEAF can be used to derive base key for sensing.

[0074] In an example embodiment, the sensing node 120 sends the key identifier of base key (base key ID) to the UE 130 which is to be used by the UE 130 to derive sensing session keys.

[0075] Examples for Obtaining N:

[0076] The UE 130 and the sensing node 120 use a parameter N (e.g. the first parameter, the second paramter) to derive multiple keys (at least one for each sensing session) from the sensing base key or from a key derived from the sensing base key. This parameter is an input to the Key Derivation Function (KDF) with base key as the input key. For each sensingsession, the value of parameter N will be different and agreed upon between the UE 130 and the sensing node 120.

[0077] The UE 130 and the sensing node 120 can obtain parameter N for a sensing session in multiple ways.

[0078] For example, the parameter N is sent either from the sensing node 120 to the UE 130 (e.g. in a signalling message such as a security mode command (SMC) message) or from UE to the sensing node in a message over an integrity protected channel e.g., in a control plane signaling message. The requirement of sending this parameter over integrity-protected channel is to ensure that no entity or adversary can modify the value of this parameter to an old value. It is advantageous that the UE 130 and the sensing node 120 implement methods to ensure that the received value for this parameter is fresh to deter replay attacks.

[0079] The UE 130 or the sensing node 120 (whichever sends parameter N to other) can obtain the value of N in multiple ways.

[0080] Example Case 1: The value of N can be e.g., a nonce or a value generated from a random number generator, at the UE 130 or the sensing node 120.

[0081] Example Case 2: The UE 130 and the sensing node 120 have agreed to use the value of a (local) counter running at the UE 130 and the sensing node 120. The (local) counter can be incremented as a result of sending or receiving an ISAC related signaling message by the UE 130 or the sensing node 120.

[0082] Example Case 3: The UE 130 and the sensing node 120 use some (e.g. a unique) part of sensing configuration message (e.g., the value of sensing session ID) or hash of some part of the message as the value of parameter N. It is advantageous that the UE 130 and the sensing node 120 implement methods to ensure that the selected parts of sensing configuration message to obtain value for this parameter N (e.g., session ID) is different for different sessions.

[0083] Deriving sensing session keys

[0084] The UE 130 and the sensing node 120 use the sensing base key, the parameter N and, for example, agreed upon algorithm(s) or other parameters to derive an Encryption key (e.g. the first session key) for a sensing session and an Integrity protection key (e.g. the second session key) for a sensing session. For example:

[0085] Ksens_sess_enc—KDF(Kbase, N, Enc-Alg-ID...)Ksens_sess_int—KDF(Kbase, N, Int-Alg-ID...)

[0086] Where KDF is a Key Derivation Function, Enc-Alg-ID and Int-Alg-ID are the identifiers for encryption algorithm and integrity protection algorithm respectively, agreed upon by the UE 130 and the sensing node 120.

[0087] Ksens sess enc and Ksens_sessjnt are the encryption key and the integrity protection key respectively, derived by the UE 130 and the sensing node 120, which shall only be used for the protection of sensing data for a particular sensing session. It is also possible that only one sensing session key (e.g., called Ksens_sess) is derived which is then used for both encryption and integrity protection of sensing data for a particular sensing session. Such case can for example be the case when Authenticated Encryption with Associated Data (AEAD) algorithms are used. Throughout the disclosure, when Ksens_sess_enc and Ksens_sessjnt are mentioned, they may be replaced with only one key Ksens_sess.

[0088] Figure 7 illustrates example cases for key derivation and provisioning in sensing node entities.

[0089] Examples for secure logical channel for protecting sensing data in transit

[0090] The secure logical channel for sensing data is for example the channel protected by sensing session keys between a UE (e.g. the UE 130) and a sensing node (e.g. the sensing node 120 or the network node 120). This secure channel may terminate in the sensing node, in a sensing processing entity (e.g. the sensing processing entity 150) or in one or more processing sessions (e.g. the Processing sessions 151) depending on the logical separation and placement of entities in the sensing node as shown in Figure 2 and Figure 4.

[0091] Case A as depicted in Figure 7: In case A, when the Sensing Node (e.g. the sensing node 120) includes a sensing control entity (e.g. the sensing control entity 140) and the sensing processing functions (e.g. the sensing procession entity 150, the processing session entity 151) and hence represents the combined logical functionality of the sensing control entity and the sensing processing functions, this logical channel is between the UE and the Sensing Node. The UE can send the sensing data directly to the sensing node by protecting the data with the sensing session keys derived for the session.

[0092] Case B as depicted in Figure 7: In case B, the Sensing Processing entity (e.g. the sensing processing entity 150) is the entity that processes sensing session data. Therefore, the UE (e.g. the UE 130) sends the sensing session data protected by sensing session keys to theSensing Processing entity and hence, the secure logical channel is between the UE and the Sensing Processing entity.

[0093] Case C as depicted in Figure 7: In case C, the Processing Session entity (e.g. the processing session entity 151) is setup for processing the session data and the UE needs to send the sensing session data to the Processing session entity. In one embodiment, the Sensing processing entity (e.g. the sensing processing entity 150) can route the protected sensing session data to the correct Processing Session entity. In this case, the secure logical channel for sensing data is between the UE and the Processing Session entity and the channel is secured using sensing session keys.

[0094] Examples for Sensing session key provisioning in sensing node:

[0095] Example Case A: The Sensing node (e.g. the sensing node 120 or the network node 120) derives and uses the sensing session keys locally to process the sensing session data. The sensing node doesn’t need to provision the sensing session keys to any other entity in this case.

[0096] Example Case B: The Sensing control entity (e.g. the sensing control entity 140) provisions the sensing session keys in the Sensing Processing entity (e.g. the sensing processing entity 150).

[0097] Example Case C: The Sensing control entity (e.g. the sensing control entity 140) provisions the sensing session keys in the Processing Sessions (e.g. the processing sessions entity 151) set up by the sensing processing entity (e.g. the sensing processing entity 150). In some embodiment, the sensing processing entity can also provision the sensing session keys in the Processing Sessions entity after obtaining them from the sensing control entity.

[0098] The Processing sessions entity is setup to process sensing data associated with a specific sensing session. The Sensing node (e.g. the sensing node 120) should provide the sensing session keys only to the Processing session entity (e.g. the processing sessions entity 151) that was orchestrated to process the sensing data associated to that session. The Processing Sessions entity processing sensing data for a session should not be able to access sensing data belonging to other sessions - until explicitly authorized by the sensing control entity (e.g. the sensing control entity 140) or the sensing node. This setup would require a session level authorization or access control on the Processing Sessions entity.

[0099] One way of reinforcing this session level access control on the Processing Sessions entity is through the provisioning of sensing session keys. If the Processing Sessions entity doesn’thave the corresponding session keys, the Processing Sessions entity won’t be able to read / process the data. However, this does not imply that traditional access control on the Processing Sessions entity can be replaced by key provisioning mechanism.

[0100] In addition, only the UE (e.g. the UE 130) associated with the correct sensing session should be allowed to send the sensing data to a processing session (e.g. the processing session entity 151). If the integrity check of sensing session data fails, or if sensing data can’t be deciphered using the sensing session keys provisioned at the Processing session entity, the processing session entity should reject the data and stop processing it.

[0101] The sensing control entity (e.g. the sensing control entity 140) should use a secure channel (mutually authenticated, encrypted and integrity protected) to provision the sensing session keys in the Sensing processing entity case (i.e. , case B) or in the Processing Sessions entity case (i.e., case C).

[0102] Further Example Embodiments and Sequence diagrams

[0103] In a first example embodiment, Sensing Control and Sensing Processing logically are colocated in sensing node and Sensing base key is derived from a key belonging to 3GPP key hierarchy (Example case 2 of Determining base key for sensing). Sensing node derives the sensing session keys.

[0104] Figure 8 is a signalling diagram illustrating this example embodiment. The example embodiment includes the following steps, as illustrated in Figure 8:

[0105] 1) UE and Communication network perform Primary authentication.

[0106] 2) As a result of Primary Authentication and setting up of Non-Access Stratum (NAS) and Access Stratum (AS) security, UE and Communication Network obtain base keys as shown in 3GPP key hierarchy of Figure 6.

[0107] 3) Sensing node selects a UE that can perform sensing (or a part of) to satisfy a sensing service request from a sensing service consumer.

[0108] 4) Sensing Node sends a sensing session configuration request to the selected UE.

[0109] This request includes the sensing session ID.

[0110] 5) UE can accept or reject this sensing request. In case UE accepts the sensing request, in one embodiment of obtaining N parameter, the UE can send the parameter N to Sensing node in the sensing request accept message. In otherembodiment, parameter N can be sent from UE to Sensing node in some integrity protected message.

[0111] 6) In an optional step, Sensing node can request the sensing base key from a communication network entity e.g., AMF, SEAF, ALISF, gNB etc.

[0112] 7) Communication network entity derives the sensing base key from one of the agreed upon 3GPP base keys. Similarly, UE can also derive the sensing base case from agreed upon 3GPP base key.

[0113] 8) Communication network entity sends the sensing base key to the sensing node. In some embodiment, Communication network entity can also push the sensing base key of UE to sensing node in some prior communication between sensing node and Communication network entity.

[0114] 9) Optionally the sensing node can store the sensing base key for a UE to reduce the amount of signaling between sensing and communication entities in network.

[0115] 10) Sensing node performs necessary actions to arrange / setup / orchestrate processing resources to process sensing session data.

[0116] 11) Once the resources are setup, sensing node sends the sensing session configuration. The sensing session configuration includes sensing session ID, parameters for configuring UE sensing entity’s radio. In another embodiment of obtaining N parameter, sensing node can send parameter N in sensing session configuration message. In some embodiment, parameter N can be sent from Sensing node to UE in some integrity protected message.

[0117] 12) Sensing node and UE derives the sensing session keys (Ksens_sess_int, Ksens_sess_enc) from the chosen sensing base key and the parameter N to be used for a specific sensing session.

[0118] 13) In an optional step, Sensing node can provision the sensing session keys derived in step 12 to some local entity if needed.

[0119] 14) In an optional step, Sensing node sends an indication to UE to start sending the sensing session data. In some embodiment, this can act as an indication to start using the sensing session keys to protect the sensing data and send the protected data.15) UE sends sensing session data protected by sensing session keys to the sensing node.

[0120] 16) Sensing node processes this data in the local entities setup at the sensing node using the sensing session keys.

[0121] In a second example embodiment, Sensing Control and Sensing Processing logically are colocated in sensing node and Sensing base key is Preconfigured in Subscriber module by network (Example Case 1 of Determining base key for sensing). Sensing node derives the sensing session keys.

[0122] Figure 9 is a signalling diagram illustrating this example embodiment. The example embodiment includes the following steps, as illustrated in Figure 9:

[0123] 1) UE obtains the base key. The base key can be pre-configured in the subscription module of UE, the base key can be received from a network entity upon request from UE or the base key can be pushed to the UE by network entity by appropriate means available to network entity. Since this is a sensitive data, the base key should be configured securely.

[0124] 2) In one option 1a sensing base key is pre-configured, Sensing Node obtains the base key for UE as a result of a network entity pre-configuring the base key in the sensing node. In case sensing node is co-located with a communication entity e.g., gNB, the communication entity can have base key pre-configured / stored in sensing node.

[0125] 3) Sensing node selects a UE that can perform sensing (or a part of) to satisfy a sensing service request from a sensing service consumer.

[0126] 4) Sensing Node sends a sensing session configuration request to the selected UE.

[0127] This request includes the sensing session ID.

[0128] 5) UE can accept or reject this sensing request. In case UE accepts the sensing request, in one embodiment of obtaining N parameter, the UE can send the parameter N to Sensing node in the sensing request accept message. In other embodiments, parameter N can be sent from UE to Sensing node in some integrity protected message.

[0129] 6) UE derives the sensing base key from base key obtained in step 1.) In another option 1b sensing base key is obtained from communication network entity,

[0130] 7.1 Communication network entity obtains the base key. The communication network entity (e.g., AMF, SEAF, ALISF, gNB, etc.) can have the sensing specific keys for UE pre-configured or obtain them from relevant entities (e.g., O&M of network) upon request or as a result of them pushing the keys to communication network entity.

[0131] 7.2 In this option, communication network entity may receive a request from sensing node to send sensing base key for a UE

[0132] 7.3 Communication network entity derives the sensing base key from the base key obtained in step 7.1.

[0133] 7.4 The communication network entity sends the sensing base key to the sensing node. In some embodiment, communication network entity can also push this sensing base key of UE in some prior communication between sensing node and Communication network entity.

[0134] 7.5 In an optional step, Sensing Control can store this sensing base key for UE to reduce the amount of signaling between sensing and communication entities in network.

[0135] ) Sensing node performs necessary actions to arrange / setup / orchestrate processing resources to process sensing session data.

[0136] ) Once the resources are setup, sensing node sends the sensing session configuration. The sensing session configuration includes sensing session ID, parameters for configuring UE sensing entity’s radio. In another embodiment of obtaining N parameter sensing node can send parameter N in sensing session configuration message. In other embodiments, parameter N can be sent from Sensing node to UE in some integrity protected message.

[0137] 0) Sensing node and UE derives the sensing session keys (Ksens_sess_int, Ksens_sess_enc) from the chosen sensing base key and the parameter N.

[0138] 1) In an optional step, Sensing node can provision the derived sensing session keys to some local entity if needed.12) In an optional step, Sensing node send an indication to UE to start sending the sensing session data. In some embodiment, this can act as an indication to start using the derived keys to protect the sensing data and send the protected data.

[0139] 13) UE sends sensing session data protected by sensing session keys to the sensing node.

[0140] 14) Sensing node processes this data in the local entities setup at the sensing node using the sensing session keys.

[0141] In a third example embodiment, Sensing Control and Sensing Processing are logically separate entities in sensing node. Sensing Control derives the sensing session keys and provision them in Sensing Processing.

[0142] Figure 10 is a signalling diagram illustrating this example embodiment. The example embodiment includes the following steps, as illustrated in Figure 10:

[0143] 1) UE and Communication network perform Primary authentication.

[0144] 2) As a result of Primary Authentication and setting up of NAS and AS security, UE and Communication Network obtain base keys as shown in 3GPP key hierarchy of Figure 6.

[0145] 3) Sensing control selects a UE that can perform sensing (or a part of) to satisfy a sensing service request from a sensing service consumer.

[0146] 4) Sensing control sends a sensing session configuration request to the selected UE.

[0147] This request includes the sensing session ID.

[0148] 5) UE can accept or reject this sensing request. In case UE accepts the sensing request, in one embodiment of obtaining N parameter, the UE can send the parameter N to sensing control in the sensing request accept message. In other embodiments, parameter N can be sent from UE to sensing control in some integrity protected message.

[0149] 6) In an optional step, sensing control can request the sensing base key from a communication network entity e.g., AMF, SEAF, AUSF, gNB etc.

[0150] 7) Communication network entity derives the sensing base key from one of the agreed upon 3GPP base key.8) Communication network entity sends the sensing base key to the sensing control. In some embodiment, Communication network entity can also push the sensing base key of UE in Sensing Control in some prior communication between sensing control and Communication network entity.

[0151] 9) Optionally the sensing control can store the sensing base key for a UE to reduce the amount of signaling between sensing and communication entities in network.

[0152] 10) Sensing control sends a processing request to sensing processing entity. The sensing processing entity performs necessary actions to arrange / setup / orchestrate processing resources to process sensing session data. In an optional step (10.2), once the processing resources are setup successfully, Sensing Processing can send the success response to Sensing Control.

[0153] 11) Once the resources are setup, Sensing control sends the sensing session configuration. The sensing session configuration includes sensing session ID, parameters for configuring UE sensing entity’s radio. In another embodiment of obtaining N parameter, sensing control can send parameter N in sensing session configuration message. In other embodiments, parameter N can be sent from Sensing control to UE in some integrity protected message.

[0154] 12) Sensing control and UE derives the sensing session keys (Ksens_sess_int, Ksens_sess_enc) from the chosen sensing base key and the parameter N.

[0155] 13) The Sensing control provisions the sensing session keys in the Sensing Processing entity. In an optional step (13.3), once the sensing session keys are setup successfully, Sensing Processing can send the success response to Sensing Control.

[0156] 14) In an optional step, the Sensing Control indicates to UE to start sending the sensing session data. In some embodiment, this can act as an indication to start using the keys derived in step 12 to protect the sensing data and send the protected data.

[0157] 15) UE sends sensing session data protected by sensing session keys to the sensing processing entity.

[0158] 16) Sensing processing entity processes this data using the sensing session keys received in 13.Note: The above embodiment only describes the case where sensing base key is derived from the 3GPP key hierarchy base key as a result of Primary Authentication between UE and communication entity. In another example embodiment, UE and Sensing control can obtain the sensing base key, as explained above for the second example embodiment.

[0159] In a fourth example embodiment, Sensing Control and Sensing Processing logically are logically separate entities in sensing node. Sensing Processing derives the sensing session keys.

[0160] Figure 11 is a signalling diagram illustrating this example embodiment. The example embodiment includes the following steps, as illustrated in Figure 11:

[0161] 1) UE and Communication network perform Primary authentication.

[0162] 2) As a result of Primary Authentication and setting up of NAS and AS security, UE and Communication Network obtain base keys as shown in 3GPP key hierarchy of Figure 6.

[0163] 3) Sensing control selects a UE that can perform sensing (or a part of) to satisfy a sensing service request from a sensing service consumer.

[0164] 4) Sensing control sends a sensing session configuration request to the selected UE.

[0165] This request includes the sensing session ID.

[0166] 5) UE can accept or reject this sensing request. In case UE accepts the sensing request, in one embodiment (shown as Option 1) of obtaining N parameter, the UE can send the parameter N to sensing control in the sensing request accept message. In other embodiments, parameter N can be sent from UE to sensing control in some integrity protected message.

[0167] 6) Sensing Control sends a processing request to the sensing processing entity. In one embodiment (shown as Option 1) of sending N parameter from Sensing Control to Sensing Processing, sensing control can send the parameter N (obtained in step 5) to the Sensing Processing in the processing request. In other embodiments, parameter N can be sent from sensing control to Sensing Processing in some secure message.

[0168] 7) In option 1a, the Sensing Processing obtains the sensing base key from communication network entity.7.1 Sensing processing entity request the sensing base key from the communication network entity. This step is optional.

[0169] 7.2 The communication network entity derives the sensing base key from the keys obtained in step 2.

[0170] 7.4 The communication network entity sends the sensing base key to the Sensing Processing. In some embodiment, Communication network entity can also push the sensing base key of UE in Sensing Processing in some prior communication between sensing Processing and Communication network entity.

[0171] 7) In another option 1b, the sensing Processing obtains the sensing base key from Sensing Control.

[0172] 7.1 Sensing Control request the sensing base key from the communication network entity. This step is optional.

[0173] 7.2 The communication network entity derives the sensing base key from the keys obtained in step 2.

[0174] 7.3 The communication network entity sends the sensing base key to the sensing control entity. In some embodiment, Communication network entity can also push the sensing base key of UE in Sensing Control in some prior communication between Sensing Control and Communication network entity.

[0175] 7.4 In an optional step, Sensing Control can store the sensing base key for UE to reduce the amount of signaling between sensing and communication entities in network. Steps 7.1-7.4 are pre-requisite to enable 7.5-7.6. In other words, Sensing Control should first obtain the sensing base key from Communication network entity before the Sensing Control could send / provision / push the sensing base key in the Sensing Processing entity.

[0176] 7.5 In an optional step, the sensing processing entity requests the sensing base key from the sensing control.

[0177] 7.6 The sensing control entity sends the sensing base key to the sensing processing entity. In some embodiment, Sensing Control can also push the sensing base key of UE in Sensing Processing in some prior communication between Sensing Control and Sensing Processing.8) In an optional step, Sensing Processing stores the sensing base key for UE to reduce the amount of signaling between sensing and communication entities in network.

[0178] 9) Sensing Control sends a sensing session configuration request to the selected UE.

[0179] This request includes the sensing session ID. In another embodiment (shown as Option 2) of obtaining N parameter, Sensing Control can send parameter N in sensing session configuration message. In other embodiments, parameter N can be sent from Sensing control to UE in some integrity protected message.

[0180] 10) In another embodiment (shown as Option 2) of sending parameter N from Sensing Control to Sensing Processing, Sensing Control can send the parameter N obtained / decided in step 9 in a secure message to Sensing Processing.

[0181] 11) Sensing Processing and UE derives the sensing session keys (Ksens_sess_int, Ksens_sess_enc) from the obtained sensing base key and the parameter N.

[0182] 12) Sensing control indicates to the sensing processing entity to activate the security for sensing session and start using the sensing session keys derived in step 11.

[0183] 13) In this optional step the sensing control indicates to the UE to start sending data. In some embodiment, this can act as an indication to start using the keys derived in step 11 to protect the sensing data and send the protected data.

[0184] 14) The UE start sending sensing data protected by sensing session keys to the Sensing Processing entity.

[0185] 15) The Sensing Processing entity processes the sensing session data using the sensing session keys.

[0186] Note: The above embodiment only describes the case where sensing base key is derived from the 3GPP key hierarchy base key as a result of Primary Authentication between UE and communication entity. In another embodiment, UE and Sensing control can obtain the sensing base key as explained above for the second example embodiment.

[0187] Note: In embodiment corresponding to Option 1, UE decides the parameter N, sends the parameter N to Sensing control (step 5) and Sensing Control sends the parameter N to Sensing processing (step 6.1).In embodiment corresponding to Option 2, Sensing Control decides the parameter N and sends the parameter N to UE (step 9) and to Sensing processing (step 10).

[0188] In another example embodiment, Option 3, Sensing Processing can decide the parameter N and send the parameter N to Sensing Control in a secure message from Sensing Processing to Sensing Control. The Sensing control can further send this value to UE in a secure, integrity-protected message from Sensing Control to UE.

[0189] In a fifth example embodiment, Sensing Control and Sensing Processing logically are logically separate entities in sensing node, Sensing Processing set up a Processing Session Instance to process sensing session data. As mentioned in Introduction section, these instances can be setup in the UE, the Edge network, the RAN, the Core network or even in a cloud network. The example includes multiple embodiments in which sensing session keys can be derived in different entities.

[0190] Figure 12 is a signalling diagram illustrating this example embodiment. The example embodiment includes the following steps, as illustrated in Figure 12:

[0191] Steps 1-9 are similar or identical to the third example embodiment above (Figure 10), in which sensing control has selected a UE, obtained the sensing base key for the UE, have received sensing request accept from UE in response to the sensing session configuration request. This example also includes the option 1 example embodiment where parameter N is sent from UE to sensing control in an integrity protected message, e.g., Sensing request accept.

[0192] 10. Sensing control setup processing resources for a sensing session

[0193] 10.1 Sensing Control sends a processing request to sensing processing entity.

[0194] 10.2 Sensing Processing set up Processing Session instance to process sensing session data.

[0195] 10.3: Optionally, Processing session indicate that the resources are successfully setup.

[0196] 10.4: Optionally Sensing Processing indicates to Sensing Control that processing resources are successfully setup for the sensing session.

[0197] 11. Once the resources are setup, sensing control sends the sensing session configuration. The sensing session configuration includes sensing session ID, parameters for configuringUE sensing entity’s radio. In another embodiment (shown as Option 2) of obtaining N parameter, sensing control can send parameter N in sensing session configuration message. In other embodiments, parameter N can be sent from Sensing control to UE in some integrity protected message.

[0198] 12. Sensing control and UE derives the sensing session keys (Ksens_sess_int, Ksens_sess_enc) from the obtained sensing base key and the parameter N.

[0199] 13. The Sensing control provisions the sensing session keys derived in step 12 to the Processing session instance. In another embodiment the sensing control can provision these keys in the Sensing Processing entity, which in turn can provision them in the Processing session instance.

[0200] 14. Sensing control sends the security activation indication to indicate to Processing sessions instance to activate the security and start using the sensing session keys provisioned in step 13.

[0201] 15. In an optional step, the sensing control indicates to UE to start sending the sensing session data. In some embodiment, this can act as an indication to UE to start using the derived keys to protect the sensing data and send the protected data.

[0202] 16. UE sends sensing session data protected by sensing session keys to the Processing sessions instance.

[0203] 17. Processing sessions instance processes this data using the sensing session keys received in step 13.

[0204] Note: The above embodiment only describes the case where sensing base key is derived from the 3GPP key hierarchy base key as a result of Primary Authentication between UE and communication entity. In another example embodiment, UE and Sensing control can obtain the sensing base key as explained above for the third example embodiment (case of pre-configured sensing base keys obtained by Sensing Control).

[0205] Note: The above embodiment only describes the case where sensing base key is obtained in UE and Sensing Control. In another example embodiment, UE and either of the Sensing node entities (Sensing Control, Sensing Processing, Sensing Processing Instance) can obtain the sensing base key as explained above for the first example embodiment (case of sensing base key derived from any 3GPP key hierarchy) or the second example embodiment (case of pre-configured sensing base keys).Note: In another example embodiment, Processing session Instance can derive the keys for a sensing session by obtaining the sensing base key from either sensing node entities (Sensing Control or Sensing Processing) or communication network entities. In such embodiment the sequence of messages from Sensing Processing instance may be similar to message from Sensing Processing in the fourth example embodiment.

[0206] In a sixth example embodiment, UE has more than one sensing session or Sensing node has scheduled more than 1 sensing session on UE. Sensing node can have Sensing Control and Sensing Processing co-located or logically separate. In addition, Sensing Processing can setup Processing session instance corresponding to each sensing session. The Sensing session keys can be derived in any of these entities in sensing node.

[0207] Figure 13 is a signalling diagram illustrating this example embodiment. The example embodiment includes the following steps, as illustrated in Figure 13:

[0208] 1) UE and Communication network perform Primary authentication.

[0209] 2) As a result of Primary Authentication and setting up of NAS and AS security, UE and Communication Network obtain base keys as shown in 3GPP key hierarchy of Figure 6.

[0210] 3) Sensing Node selects a UE that can perform sensing (or a part of) to satisfy a sensing service request from a sensing service consumer.

[0211] 4) Sensing Node sends the sensing session 1 configuration request to the selected UE.

[0212] This request includes the sensing session 1 ID.

[0213] 5) UE can accept or reject this sensing request. In case UE accepts the sensing request, in one embodiment (referred as Option 1 ) of obtaining N1 parameter for sensing session 1, the UE can send the parameter N1 for sensing session 1 to Sensing node in the sensing request accept message. In other embodiment, parameter N1 can be sent from UE to Sensing node in some integrity protected message.

[0214] 6) In an optional step, Sensing Node can request the sensing base key from a communication network entity e.g., AMF, SEAF, AUSF, gNB etc.

[0215] 7) Communication network entity derives the sensing base key from one of the agreed upon 3GPP base keys for sensing. Similarly, UE can also derive the sensing base case from agreed upon 3GPP base key.8) Communication network entity sends the sensing base key to the Sensing Node. In some embodiment, Communication network entity can also push the sensing base key of UE to sensing node in some prior communication between sensing node and Communication network entity.

[0216] 9) Optionally the sensing node can store the sensing base key for a UE to reduce the amount of signaling between sensing and communication entities in network.

[0217] 10) Sensing Node performs necessary actions to arrange / setup / orchestrate processing resources to process sensing data for sensing session 1.

[0218] 11) Once the resources are setup, Sensing Node sends the sensing session configuration for session 1. The sensing session configuration includes sensing session 1 ID, parameters for configuring UE sensing entity’s radio. In another embodiment (referred as Option 2 ) of obtaining N1 parameter for sensing session 1, Sensing Node can send parameter N1 in sensing session configuration message. In some embodiment, parameter N1 can be sent from Sensing Node to UE in some integrity protected message.

[0219] 12) Sensing Node sends another sensing session configuration request for session 2 to the same UE. This request includes the sensing session 2 ID. NOTE: The sensing session 2 request can come from sensing node at any of the above steps.

[0220] 13) UE can accept or reject this new sensing request. In case UE accepts the sensing request, in one embodiment (referred as Option 1 ) of obtaining N2 parameter for sensing session 2, the UE can send the parameter N2 for sensing session 2 to Sensing Node in the sensing request accept message. In other embodiment, parameter N2 can be sent from UE to Sensing node in some integrity protected message.

[0221] 14) Sensing Node performs necessary actions to arrange / setup / orchestrate processing resources to process sensing session data for session 2.

[0222] 15) Once the resources are setup, Sensing Node sends the sensing session configuration for session 2. The sensing session configuration includes sensing session 2 ID, parameters for configuring UE sensing entity’s radio . In another embodiment (referred as Option 2 ) of obtaining N2 parameter for sensing session 2, sensing node can send parameter N2 in sensing session configuration message. Insome embodiment, parameter N2 can be sent from Sensing Node to UE in some integrity protected message.

[0223] 16) Sensing node and UE derives the sensing session keys K1 from the obtained sensing base key and the parameter N1 for sensing session 1.

[0224] 17) In an optional step, Sensing Node can provision the sensing session keys derived in step 16 to some local processing entity if needed.

[0225] 18) In an optional step, Sensing Node sends an indication to UE to start sending session 1 sensing data. In some embodiment, this can act as an indication to start using the sensing session keys for session 1 to protect the sensing data and send the protected data.

[0226] 19) UE sends session 1 sensing data protected by session 1 sensing keys (K1) to the sensing node.

[0227] 20) Sensing Node processes this session 1 data in the local entity setup at the sensing node using the sessionl sensing keys (K1).

[0228] 21) Sensing Node and UE derives the sensing session 2 keys, K2 from the obtained sensing base key and the parameter N2 for sensing session 2. Note: this can happen async with sensing session 1.

[0229] 22) In an optional step, Sensing Node can provision the sensing session 2 keys, K2 derived in step 21 to some local processing entity if needed.

[0230] 23) In an optional step, Sensing Node sends an indication to UE to start sending session 2 sensing data. In some embodiment, this can act as an indication to start using the sensing session keys, K2, for session 2 to protect the sensing data and send the protected data.

[0231] 24) UE sends session 2 sensing data protected by session 2 sensing keys to the sensing node.

[0232] 25) Sensing Node processes this session 2 data in the local processing entities setup at the sensing node using the session 2 sensing keys.

[0233] Note: In cases where Sensing Control and Sensing Processing entities are two separate logical entities. In one example embodiment, the key derivation can occur in either of them. In another example embodiment, where Processing Session instances are setup by SensingProcessing entity then key derivation can happen in the Processing Session instances as well.

[0234] Figure 14 shows an example of a communication system 1400 in accordance with some embodiments. In the example, the communication system 1400 includes a telecommunications network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408. The access network 1404 includes one or more access network nodes or base stations of various types, access network nodes 1410A and 1410B are depicted (which may be collectively referred to as network nodes 1410), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1404 may include more than one access network technology. The network nodes 1410 of access network 1404 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 1412A, 1412B, 1412C, and 1412D (one or more of which may be generally referred to as UEs 1412) to the core network 1406 over one or more wireless connections.

[0235] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1402 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1402, including one or more access network nodes 1410 and / or core network nodes 1408.

[0236] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node maybe implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0237] The network nodes 1410 facilitate direct or indirect connection of one or more UEs 1412 to the core network 1406 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0238] The UEs 1412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1410 and other communication devices. Similarly, the network nodes 1408, 1410 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1402) with the UEs 1412 and / or with other network nodes or equipment in the telecommunications network 1402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1402. More specifically, UEs 1412 may send messages, data, and / or other signals to network nodes 1408, 1410 or other elements of the telecommunications network 1402 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1408, 1410 may send messages, data, and other signals to UEs 14122, other network nodes 1408, 1410, and other devices in telecommunications network 1402 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1412 by transmitting the message to an access network node 1410 that will then transmit the message to the intended UE 1412. Similarly, a core networknode 108 may receive a particular message from a UE 1412 by receiving the message from an access network node 1410 that itself received the message from the UE 1412.

[0239] In the depicted example, the core network 1406 connects elements of the access network 1404 (e.g., one or more of the network nodes 1410) to one or more host computing systems, such as host 1416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1406 includes one or more core network nodes (e.g., core network node 1408) of various types, one or more of which may be generally referred to as network nodes 1408. Network nodes 1408 are structured with hardware and software components.

[0240] Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1408.

[0241] Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0242] The host 1416 may be under the ownership or control of a service provider other than an operator or provider of the access network 1404 and / or the telecommunications network 1402. The host 1416 may be operated by the service provider or on behalf of the service provider. The host 1416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0243] As a whole, the communication system 1400 of Figure 14 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1400 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any otherappropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1400 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1400 supporting different standards, protocols, or rule sets.

[0244] As one example, in certain embodiments, access network 1404 may contain some access network nodes 1410 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1410 support (or the same access network nodes 1410 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1402 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0245] Telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1402. For example, the telecommunications network 1402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0246] In some examples, one or more of the UEs 1412 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1404.

[0247] Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0248] In the example, the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412C and / or 1412D) andnetwork nodes (e.g., network node 141 OB). In some examples, the hub 1414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs. As another example, the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1410, or by executable code, script, process, or other instructions in the hub 1414.

[0249] As another example, the hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0250] The hub 1414 may have a constant / persistent or intermittent connection to the network node 141 OB. The hub 1414 may also allow for a different communication scheme and / or schedule between the hub 1414 and UEs (e.g., UE 1412C and / or 1412D), and between the hub 1414 and the core network 1406. In other examples, the hub 1414 is connected to the core network 1406 and / or one or more UEs via a wired connection. Moreover, the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection. In some embodiments, the hub 1414 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1410B. In other embodiments, the hub 1414 may be a non-dedicated hub -that is, a device which is capable of operating to route communications between the UEs and network node 1410B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0251] Figure 15 is another example of a communication system 1500 according to some embodiments. As used herein, the communication system 1500 includes multiple access points (APs) 1510 (with four exemplary APs 1510A, 1510B, 1510C, and 1510D beingdepicted) and multiple wireless devices, referred to in the context of communication system 1500 as stations (STAs) 1512 (referred to individually as STA 1512A, STA 1512B, STA 1512C, STA 1512D, and STA 1512E). STA 1512A is served by AP 1510A in a first basic service set (BSS) 1520A. STA 151 OB and STA 1510C are served by AP 151 OB in a second BSS, BSS 1520B. STA 1512D is served by AP 1510C in a third BSS, BSS 1520C. STA 1512E is served by AP 1510D in a fourth BSS, BSS 1520D. Stations 1512 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1512 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0252] Each of STAs 1512 may connect through a radio link to one of APs 1510. For example, depending on location or channel conditions experienced by a given STA 1512, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0253] Each AP 1510 may provide data connectivity to STAs 1512 connected to a particular AP 1510. As illustrated, APs 1510 may be connected to a data network 1530. In this way, APs 1510 may also provide data connectivity between STAs 1512 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1512 and its serving AP 1510 may be used for providing various kinds of services to STA 1512, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1512 and / or on a device linked to STA 1512. By way of example, Figure 15 illustrates host(s) 1532 (e.g. application service platform(s)) provided in data network 1530. The application(s) executed on STA 1512 and / or on one or more other devices linked to STA 1512 may use the radio link for data communication with one or more other STA 1512 and / or the application service platform 1532, thereby enabling utilization of the corresponding service(s) at STA 1512.

[0254] Figure 16 shows a wireless device 1600, which may be configured to operate in communication system 1400 of Figure 14 or in communication system 1500 of Figure 15. The wireless device 1600 may be alternatively referred to as a UE 1600, like a UE 1412within the context of communication system 1400, or as a station (STA) 1600 or as a non-access-point station (non-AP STA) 1600, like a STA 1512 within the context of the communication system 1500, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0255] A wireless device 1600 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle-to-everything (V2X). In other examples, wireless device 1600 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1600 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 1600 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0256] In particular embodiments, wireless device 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input / output interface 1606, a power source 1608, a memory 1610, a communication interface 1612, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1600 may include all or a subset of the components shown in Figure 16. The level of integration between the components may vary from one embodiment of wireless device 1600 to another. In general, in a particular embodiment of wireless device 1600, processing circuitry 1602, input / output interface 1606, power source 1608, memory 1610, and communication interface 1612 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1600. Further, certain embodiments ofwireless devices 1600 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0257] The processing circuitry 1602 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1610. The processing circuitry 1602 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1602 may include multiple central processing units (CPUs). The processing circuitry 1602 may be configured to cause the wireless device 1600 to perform the methods as described with reference to Figure 3.

[0258] In the example, the input / output interface 1606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 1600. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0259] In some embodiments, the power source 1608 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 1608 may further include power circuitry for delivering power from the power source 1608 itself, and / or an external power source, to the various parts of wireless device 1600 via input circuitry or an interface such as an electrical power cable. Power source 1608 may perform any formatting, converting, or other modification tomake accessible power suitable for the respective components of the wireless device 1600 to which power is supplied.

[0260] The memory 1610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1610 includes one or more programs 1614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1616. The memory 1610 may store, for use by wireless device 1600, any of a variety of various operating systems or combinations of operating systems.

[0261] The memory 1610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1610 may allow wireless device 1600 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1610, which may be or comprise a device-readable storage medium.

[0262] The processing circuitry 1602 may be configured to communicate with an access network or other network via or using the communication interface 1612. The communication interface 1612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1622. The communication interface 1612 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device ora network node in an access network). Each transceiver may include a transmitter 1618 and / or a receiver 1620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, thetransmitter 1618 and receiver 1620 may be coupled to one or more antennas (e.g., antenna 1622) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0263] In the illustrated embodiment, communication functions of the communication interface 1612 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0264] In particular embodiments, wireless device 1600 may provide an output of data captured via a sensor, through its communication interface 1612, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1600 can be communicated through a wireless connection to a network node via another wireless device 1600. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0265] As another example, wireless device 1600 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 1600 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0266] Wireless device 1600, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limitingexamples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 1600 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 1600 shown in Figure 16.

[0267] As yet another specific example, in an loT scenario, wireless device 1600 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 1600 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 1600 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 1600 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0268] In practice, any number of wireless devices 1600 may be used together with respect to a single use case. For example, a first wireless device 1600 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1600 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 1600 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 1600 can also include more than one of the functionalities described above. For example, wireless device 1600 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0269] Figure 17 shows a network node 1700 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable tocommunicate directly or indirectly with wireless devices and / or with other network nodes or equipment, in a network. In accordance with respective embodiments, network node 1700 may be configured to operate in communication system QQ100 of Figure QQ1, like network nodes QQ108 or QQ110, or in communication system QQ200 of Figure QQ2, like AP QQ210 or a STA QQ212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, NodeBs, and gNBs), and / or virtualized instances thereof.

[0270] Network node 1700 may be categorized based on the physical cell size of the area in which it provides connectivity, which is based at least in part on the transmit power level. Network node 1700 may provide for a large or small cell size. Small cell sizes include micro-, pico-, and femto-cells. Network node 1700 may be a relay node or may be a relay donor node controlling a relay. Network node 1700 may also include one or more (or all) parts of a distributed radio base station such as centralized units (CUs), distributed units ((Dlls), e.g., in an open RAN access node) and / or remote radio units (RRUs), sometimes referred to as remote radio heads (RRHs). Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0271] Other examples of network node 1700 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0272] In particular embodiments, network node 1700 includes processing circuitry 1702, memory 1704, communication interface 1706, and power system 1708. In general, processing circuitry 1702, memory 1704, communication interface 1706, and power system 1708 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1700. In virtualized embodiments, one or more of these physical components may be allocated to the network node 1700 by a hypervisor.

[0273] The network node 1700 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which thenetwork node 1700 includes multiple entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may be considered a single separate network node. In some embodiments, the network node 1700 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memories 1704 or portions of memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1712 may be shared by different RATs). The network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies / RATs integrated into network node 1700. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1700.

[0274] Network node 1700 node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. The telecommunications network QQ102 may include one or more open RAN (e.g., ORAN) network nodes 1700. An open RAN network node is a network node that supports an open RAN specification (e.g., a specification published by the O-RAN Alliance, or similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node, including one or more access network nodes QQ110 and / or core network nodes QQ108. A network node 1700 may support one or more interfaces defined by the O-RAN Alliance’s specification, such as an A1, F1, W1, E1, E2, X2, orXn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.

[0275] Examples of an open RAN network node 1700 include one or more of an open radio unit (O-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real-time control application (e.g., xApp) or a non-real-time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an open RAN specification) or the functional equivalents thereof. An open RAN network node may be a logical node in a physical node and may be implemented in a virtualization environment in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0276] The processing circuitry 1702 of network node 1700 may include a combination of one or more of a microprocessor, central processing unit, digital signal processor, ASIC, FPGA, orany other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other components, such as memory 1704, to enable network node 1700 functionality. For example, the processing circuitry 1702 may be configured to cause the network node 1700 to perform the methods and / or signalling as described with reference to Figure XX2. Like memory QQ310, memory 1704 stores executable programs and data. Memory 1704 may be used to store information generated by processing circuitry 1702 and / or any information received via the communication interface 1706.

[0277] The communication interface 1706 is used in wired and / or wireless communication of information, including control signalling and / or data, with wireless devices, other network nodes, and / or any other network equipment as described herein. In Figure 1700, communication interface 1706 includes ports / terminals to send and receive signalling and data. Communication interface 1706 includes transceiver circuitry 1710, which may include radio front-end circuitry and baseband processing circuitry. Transceiver circuitry 1710 include filters and amplifiers and may be connected to one or more antenna(s) 1712 and to processing circuitry 1702. The transceiver circuitry 1710 may be configured to condition signals communicated between antenna 1712 and processing circuitry 1702. Additionally, the transceiver circuitry 1710 may receive digital data that is to be sent out to other network nodes or wireless devices and convert the digital data into a radio signals having the appropriate channel and bandwidth parameters using a combination of filters and / or amplifiers. The radio signals may then be transmitted via the antenna 1712. Similarly, when receiving data, the antenna 1712 may collect radio signals which are then converted into digital data by the transceiver circuitry 1710. The digital data may be passed to the processing circuitry 1702. By utilization of the transceiver circuitry 1710, processing circuitry 1702 may transmit information to and receive information from one or more wireless devices or other network nodes.

[0278] In certain alternative embodiments, the processing circuitry 1702 includes or provides transceiver circuitry 1710 and is connected to the antenna 1712. In still other embodiments, the communication interface 1706 includes one or more ports or terminals and the radiofront end circuitry of the transceiver circuitry 1710 as part of a radio unit (not shown), and the communication interface 1706 communicates with the baseband processing circuitry of the transceiver circuitry 1710, which is part of a digital unit (not shown).

[0279] The antenna 1712 may include one or more antennas or antenna arrays, configured to send and / or receive wireless signals. Some embodiments of network node 1700 may be integrated with one or more antennas 1712, while others are connectable to non-integratedantennas. In certain embodiments, the antenna 1712 is separate from the network node 1700 and connectable to the network node 1700 through one or more interfaces or ports.

[0280] The antenna 1712, communication interface 1706, and / or the processing circuitry 1702 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1700 to receive information, data, and / or signals from a UE, another network node, and / or any other network equipment.

[0281] Similarly, the antenna 1712, the communication interface 1706, and / or the processing circuitry 1702 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1700 to transmit information, data and / or signals to a UE, another network node, and / or any other network equipment.

[0282] The power system 1708 provides power to the various components of network node 1700 in a form suitable for the respective components. The network node 1700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface of the power system 1708, whereby the external power source supplies power to power the components of the network node 1700. The power system 1708 may include a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.

[0283] Embodiments of the network node 1700 may include additional components beyond those shown in Figure 17 for providing certain aspects of the network node’s functionality and operations, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein.

[0284] Figure 18 shows a core network node 1800 in accordance with some embodiments. As used herein, core network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other core network nodes or equipment or RAN network nodes, in a telecommunication network. The core network node 1800 may be operable as a core network node, a core network function or, more generally, a core network entity, such as the core network node 1408 described above with respect to Figure 14). Examples of core network nodes in this context include core network entities such as one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified DataManagement (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0285] The core network node 1800 includes processing circuitry 1802, a memory 1804, a communication interface 1806, and a power source 1808, and / or any other component, or any combination thereof. The core network node 1800 may be composed of multiple physically separate components, which may each have their own respective components. In certain scenarios in which the core network node 1800 comprises multiple separate components, one or more of the separate components may be shared among several core network nodes.

[0286] The processing circuitry 1802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other core network node 1800 components, such as the memory 1804, core network node 1800 functionality. For example, the processing circuitry 1802 may be configured to cause the network node to perform the methods as described with reference to Figure 4 and / or 5.

[0287] The memory 1804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1802. The memory 1804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1802 and utilized by the core network node 1800. The memory 1804 may be used to store any calculations made by the processing circuitry 1802 and / or any data received via the communication interface 1806. In some embodiments, the processing circuitry 1802 and memory 1804 are integrated.

[0288] The communication interface 1806 is used in wired or wireless communication of signalling and / or data between a core network node, access network node(s), and / or UE.The power source 1808 provides power to the various components of core network node 1800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1808 may further comprise, or be coupled to, power management circuitry to supply the components of the core network node 1800 with power for performing the functionality described herein. For example, the core network node 1800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1808. As a further example, the power source 1808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0289] Embodiments of the core network node 1800 may include additional components beyond those shown in Figure 18 for providing certain aspects of the core network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the core network node 1800 may include user interface equipment to allow input of information into the core network node 1800 and to allow output of information from the core network node 1800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the core network node 1800.

[0290] Figure 19 is a block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.Applications 1902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0291] Hardware 1904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1908A and VM 1908B (which may be collectively referred to as VMs 1908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1908.

[0292] The VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1906. Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0293] In the context of NFV, each of the VMs 1908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1908, and that part of hardware 1904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1908 on top of the hardware 1904 and corresponds to an application 1902.

[0294] Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization. Alternatively, hardware 1904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1910, which, among others, oversees lifecycle management of applications 1902. In some embodiments, hardware 1904 is coupled to one or more radio units that eachinclude one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1912 which may alternatively be used for communication between hardware nodes and radio units.

[0295] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0296] This disclosure includes the following enumerated embodiments.

[0297] Group A Embodiments

[0298] 1. A method performed by a wireless device for deriving a key, the method comprising:

[0299] receiving a first sensing configuration message configuring a first sensing session in the wireless device;

[0300] obtaining a first parameter; and

[0301] deriving at least a first session key for the first sensing session based on a base key and the first parameter.2. The method of embodiment 1, further comprising:

[0302] transmitting, to a processing node, sensing data for the first sensing session, wherein the sensing data for the first sensing session is protected using at least the first session key.

[0303] 3. The method of embodiment 1 or 2, comprising protecting sensing data for the first sensing session using at least the first session key.

[0304] 4. The method of embodiment 3, wherein protecting the sensing data for the first sensing session comprises encrypting the sensing data and / or integrity protecting the sensing data using at least the first session key.

[0305] 5. The method of any of embodiments 1 to 4, comprising:

[0306] deriving at least a second session key for the first sensing session based on a base key and the first parameter.

[0307] 6. The method of embodiment 5, comprising:

[0308] encrypting the sensing data for the first sensing session using the first session key; and

[0309] integrity protecting the sensing data for the first sensing session using the second session key.

[0310] 7. The method of embodiment 5 or 6, wherein:

[0311] the second session key is derived based on the base key, the first parameter and a second identifier.

[0312] 8. The method of any of embodiments 1 to 7, wherein the first session key is derived based on the base key, the first parameter and a first identifier.

[0313] 9. The method of any of embodiments 1 to 9, wherein the first sensing configuration message is received from a sensing control node.

[0314] 10. The method of embodiment 9, wherein the sensing control node is the same node as the processing node or is a different node to the processing node.

[0315] 11. The method of any of embodiments 2 to 9, wherein the processing node is a sensing processing node or a first sensing processing session.12. The method of any of embodiments 1 to 11 , wherein the first parameter comprises at least one of:

[0316] a random or pseudorandom number;

[0317] a counter;

[0318] a nonce;

[0319] a parameter obtained from a sensing control node;

[0320] at least part of the first sensing configuration message; and

[0321] at least part of a first session identifier of the first sensing session.

[0322] 13. The method of any of embodiments 2 to 12, comprising:

[0323] sending the first parameter to the processing node and / or a sensing control node; and / or

[0324] receiving the first parameter from the sensing control node.

[0325] 14. The method of any of embodiments 1 to 13, comprising receiving a second sensing configuration message configuring a second sensing session in the wireless device.

[0326] 15. The method of any of embodiments 1 to 13, wherein the first sensing configuration message configures a second sensing session in the wireless device.

[0327] 16. The method of embodiment 14 or 15, comprising:

[0328] obtaining a second parameter; and

[0329] deriving at least a third session key for the second sensing session based on a base key and the second parameter.

[0330] 17. The method of embodiment 16, wherein the second parameter comprises at least one of:

[0331] a random or pseudorandom number;

[0332] a counter;

[0333] a nonce;

[0334] a parameter obtained from a sensing control node;

[0335] at least part of the first sensing configuration message or a second sensing configuration message; and

[0336] at least part of a second session identifier of the second sensing session.

[0337] 18. The method of embodiment 16 or 17, comprising:sending the second parameter to the processing node and / or a sensing control node; and / or

[0338] receiving the second parameter from the sensing control node.

[0339] 19. The method of any of embodiments 16 to 18, further comprising:

[0340] transmitting, to a further processing node, sensing data for the second sensing session, wherein the sensing data for the second sensing session is protected using at least the third session key.

[0341] 20. The method of embodiment 19, wherein the further processing node comprises the same node as the processing node, and / or comprises a sensing processing node, a sensing processing session and / or a further sensing processing session.

[0342] 21. The method of any of embodiments 16 to 20, comprising protecting sensing data for the second sensing session using at least the third session key.

[0343] 22. The method of embodiment 21 , wherein protecting the sensing data for the second sensing session comprises: i) encrypting the sensing data using at least the first session key and / or ii) integrity protecting the sensing data using at least the first session key.

[0344] 23. The method of any of embodiments 16 to 22, comprising:

[0345] deriving at least a fourth session key for the second sensing session based on a base key and the second parameter.

[0346] 24. The method of embodiment 23, comprising:

[0347] encrypting the sensing data for the second sensing session using the third session key; and

[0348] integrity protecting the sensing data for the second sensing session using the fourth session key.

[0349] 25. The method of embodiment 23 or 24, wherein:

[0350] the fourth session key is derived based on: i) the base key, ii) the second parameter and iii) a second identifier and / or fourth identifier.

[0351] 26. The method of any of embodiments 16 to 25, wherein the third session key is derived based on i) the base key, ii) the second parameter and iii) a first identifier and / or third identifier.27. The method of any of embodiments 1 to 26, wherein the base key comprises or is derived from at least one of:

[0352] a key in a subscriber module of the wireless device;

[0353] an intermediary key;

[0354] KAUSF; KAMP; KgNB; Kakma; and KsEAF.

[0355] 28. The method of embodiment 27, comprising receiving a base key identifier from a sensing control node.

[0356] 29. The method of embodiment 28, wherein:

[0357] the base key identifier identifies the base key; or

[0358] the base key is derived from a key identified by the base key identifier.

[0359] 30. The method of any of embodiments 1 to 29, comprising obtaining the sensing data for the first sensing session according to the first sensing configuration message.

[0360] Group B embodiments

[0361] 31. A method performed by a sensing control node for sending a sensing configuration message, the method comprising:

[0362] sending, to a wireless device, a first sensing configuration message configuring a first sensing session in the wireless device.

[0363] 32. The method of embodiment 31 , further comprising:

[0364] receiving, from the wireless device, sensing data for the first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key; and

[0365] processing the sensing data for the first sensing session.

[0366] 33. The method of embodiment 32, wherein processing the sensing data for the first sensing session comprises: i) decrypting the sensing data and / or ii) integrity checking the sensing data using at least the first session key.

[0367] 34. The method of embodiment 32 or 33, comprising:

[0368] obtaining a first parameter; and

[0369] deriving at least the first session key for the first sensing session based on a base key and the first parameter.35. The method of embodiment 34, comprising:

[0370] deriving at least a second session key for the first sensing session based on a base key and the first parameter.

[0371] 36. The method of embodiment 35, comprising:

[0372] decrypting the sensing data for the first sensing session using the first session key; and

[0373] integrity checking the sensing data for the first sensing session using the second session key.

[0374] 37. The method of embodiment 35 or 36, wherein:

[0375] the second session key is derived based on the base key, the first parameter and a second identifier.

[0376] 38. The method of any of embodiments 34 to 37, wherein the first session key is derived based on the base key, the first parameter and a first identifier.

[0377] 39. The method of any of embodiments 34 to 38, wherein the first parameter comprises at least one of:

[0378] a random or pseudorandom number;

[0379] a counter;

[0380] a nonce;

[0381] a parameter obtained from a sensing control node;

[0382] at least part of the first sensing configuration message; and

[0383] at least part of a first session identifier of the first sensing session.

[0384] 40. The method of any of embodiments 34 to 39, comprising:

[0385] receiving the first parameter from the wireless device; and / or

[0386] sending the first parameter to the wireless device.

[0387] 41. The method of any of embodiments 31 to 40, comprising sending, to the wireless device, a second sensing configuration message configuring a second sensing session in the wireless device.

[0388] 42. The method of any of embodiments 31 to 40, wherein the first sensing configuration message configures a second sensing session in the wireless device.43. The method of embodiment 41 or 42, further comprising:

[0389] receiving, from the wireless device, sensing data for the second sensing session, wherein the sensing data for the second sensing session is protected using at least a third session key; and

[0390] processing the sensing data for the second sensing session.

[0391] 44. The method of embodiment 43, wherein processing the sensing data for the second sensing session comprises: i) decrypting the sensing data using at least the third session key and / or ii) integrity checking the sensing data using at least the third session key.

[0392] 45. The method of embodiment 44, comprising:

[0393] obtaining a second parameter; and

[0394] deriving at least the third session key for the second sensing session based on a base key and the second parameter.

[0395] 46. The method of embodiment 45, comprising:

[0396] deriving at least a fourth session key for the second sensing session based on a base key and the second parameter.

[0397] 47. The method of embodiment 46, comprising:

[0398] decrypting the sensing data for the second sensing session using the third session key; and

[0399] integrity checking the sensing data for the second sensing session using the fourth session key.

[0400] 48. The method of embodiment 46 or 47, wherein:

[0401] the fourth session key is derived based on i) the base key, ii) the second parameter and iii) a second identifier and / or a fourth identifier.

[0402] 49. The method of any of embodiments 45 to 48, wherein the third session key is derived based on i) the base key, ii) the second parameter and iii) a first identifier and / or a third identifier.

[0403] 50. The method of any of embodiments 45 to 49, wherein the second parameter comprises at least one of:

[0404] a random or pseudorandom number;a counter;

[0405] a nonce;

[0406] a parameter obtained from a sensing control node;

[0407] at least part of the first sensing configuration message or a second sensing configuration message; and

[0408] at least part of a second session identifier of the second sensing session.

[0409] 51. The method of any of embodiments 45 to 50, comprising:

[0410] receiving the second parameter from the wireless device; and / or

[0411] sending the second parameter to the wireless device.

[0412] 52. The method of any of embodiments 34 to 40 and 45 to 51 , wherein the base key comprises or is derived from at least one of:

[0413] a key in a subscriber module of the wireless device;

[0414] an intermediary key;

[0415] KAUSF; KAMP; KgNB; Kakma; and KsEAF.

[0416] 53. The method of any of embodiments 34 to 40 and 45 to 52, comprising sending a base key identifier to the wireless device.

[0417] 54. The method of embodiment 53, wherein:

[0418] the base key identifier identifies the base key; or

[0419] the base key is derived from a key identified by the base key identifier.

[0420] 55. The method of any of embodiments 34 to 40 and 45 to 54, comprising obtaining the base key from a network node.

[0421] 56. The method of embodiment 55, wherein the network node comprises a Unified Data Management (UDM) or Operations and Maintenance (O&M) node.

[0422] 57. A method performed by a sensing control node for processing sensing data, the method comprising:

[0423] receiving, from a wireless device, sensing data for a first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key; and processing the sensing data for the first sensing session.58. The method of embodiment 57, wherein processing the sensing data for the first sensing session comprises: i) decrypting the sensing data using at least the first session key and / or ii) integrity checking the sensing data using at least the first session key.

[0424] 59. The method of embodiment 57 or 58, comprising:

[0425] obtaining a first parameter; and

[0426] deriving at least the first session key for the first sensing session based on a base key and the first parameter.

[0427] 60. The method of embodiment 59, comprising:

[0428] deriving at least a second session key for the first sensing session based on a base key and the first parameter.

[0429] 61. The method of embodiment 60, comprising:

[0430] decrypting the sensing data for the first sensing session using the first session key; and

[0431] integrity checking the sensing data for the first sensing session using the second session key.

[0432] 62. The method of embodiment 60 or 61 , wherein:

[0433] the second session key is derived based on the base key, the first parameter and a second identifier.

[0434] 63. The method of any of embodiments 59 to 62, wherein the first session key is derived based on the base key, the first parameter and a first identifier.

[0435] 64. The method of any of embodiments 59 to 63, wherein the first parameter comprises at least one of:

[0436] a random or pseudorandom number;

[0437] a counter;

[0438] a nonce;

[0439] a parameter obtained from a sensing control node;

[0440] at least part of a configuration message configuring the first sensing session; and at least part of a first session identifier of the first sensing session.

[0441] 65. The method of any of embodiments 59 to 64, comprising:receiving the first parameter from the wireless device, a sensing processing node or a sensing control node.

[0442] 66. The method of any of embodiments 57 to 65, further comprising:

[0443] receiving, from the wireless device, sensing data for the second sensing session, wherein the sensing data for the second sensing session is protected using at least a third session key; and

[0444] processing the sensing data for the second sensing session.

[0445] 67. The method of embodiment 66, wherein processing the sensing data for the second sensing session comprises: i) decrypting the sensing data using at least the third session key and / or ii) integrity checking the sensing data using at least the third session key.

[0446] 68. The method of embodiment 66 or 67, comprising:

[0447] obtaining a second parameter; and

[0448] deriving at least the third session key for the second sensing session based on a base key and the second parameter.

[0449] 69. The method of embodiment 68, comprising:

[0450] deriving at least a fourth session key for the second sensing session based on a base key and the second parameter.

[0451] 70. The method of embodiment 69, comprising:

[0452] decrypting the sensing data for the second sensing session using the third session key; and

[0453] integrity checking the sensing data for the second first sensing session using the fourth session key.

[0454] 71. The method of embodiment 69 or 70, wherein:

[0455] the fourth session key is derived based on i) the base key, ii) the second parameter and iii) a second identifier and / or fourth identifier.

[0456] 72. The method of any of embodiments 68 to 71 , wherein the third session key is derived based on i) the base key, ii) the second parameter and iii) a first identifier and / or third identifier.73. The method of any of embodiments 68 to 72, wherein the second parameter comprises at least one of:

[0457] a random or pseudorandom number;

[0458] a counter;

[0459] a nonce;

[0460] a parameter obtained from a sensing control node;

[0461] at least part of a configuration message configuring the second sensing session; and at least part of a second session identifier of the second sensing session.

[0462] 74. The method of any of embodiments 68 to 73, comprising:

[0463] receiving the second parameter from the wireless device, a sensing processing node or a sensing control node.

[0464] 75. The method of any of embodiments 59 to 74, wherein the base key comprises or is derived from at least one of:

[0465] a key in a subscriber module of the wireless device;

[0466] an intermediary key;

[0467] KAUSF; KAMP; KgNB; Kakma; and KsEAF.

[0468] 76. The method of any of embodiments 59 to 75, comprising receiving a base key identifier from the wireless device, a sensing processing node or a sensing control node.

[0469] 77. The method of embodiment 76, wherein:

[0470] the base key identifier identifies the base key; or

[0471] the base key is derived from a key identified by the base key identifier.

[0472] 78. The method of any of embodiments 59 to 77, comprising obtaining the base key from a network node.

[0473] 79. The method of embodiment 78, wherein the network node comprises a Unified Data Management (UDM) or Operations and Maintenance (O&M) node.

[0474] 80. The method of any of embodiments 57 to 79, wherein the processing node comprises a sensing processing node or a sensing processing session for the first sensing session.81. The method of any of embodiments 1 to 80, wherein the first parameter is a parameter for deriving at least the first session key.

[0475] 82. The method of any of the previous embodiments, further comprising:

[0476] providing user data; and

[0477] forwarding the user data to a host via the transmission to the network node.

[0478] Group D Embodiments

[0479] 83. A wireless device (1412, 1512, 1600) comprising:

[0480] processing circuitry (1602) configured to cause the wireless device to perform any of the operations of any of the Group A embodiments; and

[0481] a power source (1608) configured to supply power to the processing circuitry (1602).

[0482] 84. A network node (1410, 1510, 1700) comprising:

[0483] processing circuitry (1702) configured to cause the network node to perform any of the operations of any of the Group B embodiments;

[0484] a power source (1708) configured to supply power to the processing circuitry (1702).

[0485] 85. A core network node (1408, 1800) comprising:

[0486] processing circuitry (1802) configured to cause the core network node to perform any of the operations of any of the Group B embodiments;

[0487] a power source (1808) configured to supply power to the processing circuitry (1802).

[0488] 86. A wireless device comprising:

[0489] one or more antennas;

[0490] communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to cause the wireless device to perform any of the operations of any of the Group A embodiments;

[0491] an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry;

[0492] an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and

[0493] a power source connected to the processing circuitry and configured to supply power to the wireless device.87. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of the Group A embodiments and the Group B embodiments.

[0494] 88. A wireless device (1412, 1512, 1600) configured to perform the method of any of the Group A embodiments.

[0495] 89. A wireless device (1412, 1512, 1600) comprising processing circuitry (1602) and a memory (1610), said memory containing instructions executable by said processing circuitry whereby said wireless device is operative to perform the method of any of the Group A embodiments.

[0496] 90. A network node (1410, 1510, 1700), configured to perform the method of any of the Group B embodiments.

[0497] 91. A network node (1410, 1510, 1700) comprising processing circuitry (1702) and a memory (1704), said memory containing instructions executable by said processing circuitry whereby said network node is operative to perform the method of any of the Group B embodiments.

[0498] 92. A core network node (1408, 1800), configured to perform the method of any of the Group B embodiments.

[0499] 93. A core network node (1408, 1800) comprising processing circuitry (1802) and a memory (1804), said memory containing instructions executable by said processing circuitry whereby said core network node is operative to perform the method of any of the Group B embodiments.

[0500] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

Claims1. A method (300) performed by a wireless device for deriving a key, the method comprising:receiving (302) a first sensing configuration message configuring a first sensing session in the wireless device;obtaining (304) a first parameter; andderiving (306) at least a first session key for the first sensing session based on a base key and the first parameter.

2. The method of claim 1 , further comprising transmitting, to a processing node, sensing data for the first sensing session, wherein the sensing data for the first sensing session is protected using at least the first session key.

3. The method of claim 2, comprising:sending the first parameter to the processing node and / or a sensing control node; and / orreceiving the first parameter from the sensing control node.

4. The method of any of claims 1 to 3, comprising protecting, encrypting and / or integrity protecting sensing data for the first sensing session using at least the first session key.

5. The method of any of claims 1 to 4, comprising:deriving at least a second session key for the first sensing session based on a base key and the first parameter;encrypting the sensing data for the first sensing session using the first session key; andintegrity protecting the sensing data for the first sensing session using the second session key.

6. The method of claim 5, wherein:the second session key is derived based on the base key, the first parameter and / or a second identifier; and / orthe first session key is derived based on the base key, the first parameter and / or a first identifier.

597. The method of any of claims 1 to 6, wherein the first sensing configuration message is received from a sensing control node.

8. The method of any of claims 1 to 7, wherein the first parameter comprises at least one of:a random or pseudorandom number;a counter;a nonce;a parameter obtained from a sensing control node;at least part of the first sensing configuration message; andat least part of a first session identifier of the first sensing session.

9. The method of any of claims 1 to 8, comprising receiving a second sensing configuration message configuring a second sensing session in the wireless device, or the first sensing configuration message configures a second sensing session in the wireless device;and the method comprises:obtaining a second parameter; andderiving at least a third session key for the second sensing session based on a base key and the second parameter.

10. The method of claim 9, wherein the second parameter comprises at least one of: a random or pseudorandom number;a counter;a nonce;a parameter obtained from a sensing control node;at least part of the first sensing configuration message or a second sensing configuration message; andat least part of a second session identifier of the second sensing session.

11. The method of claim 10, comprising:sending the second parameter to a processing node and / or a sensing control node; and / orreceiving the second parameter from the sensing control node.

12. The method of claim 10 or 11 , further comprising:60transmitting, to a further processing node, sensing data for the second sensing session, wherein the sensing data for the second sensing session is protected using at least the third session key.

13. The method of any of claims 10 to 12, comprising protecting, encrypting and / or integrity protecting sensing data for the second sensing session using at least the third session key.

14. The method of any of claims 10 to 13, comprising:deriving at least a fourth session key for the second sensing session based on a base key and the second parameter;encrypting the sensing data for the second sensing session using the third session key; andintegrity protecting the sensing data for the second sensing session using the fourth session key.

15. The method of claim 14, wherein:the fourth session key is derived based on: i) the base key, ii) the second parameter and / or iii) a second identifier and / or fourth identifier; and / orthe third session key is derived based on i) the base key, ii) the second parameter and / or iii) a first identifier and / or third identifier.

16. The method of claim 15, comprising receiving a base key identifier from a sensing control node, wherein:the base key identifier identifies the base key; orthe base key is derived from a key identified by the base key identifier.

17. A method (400) performed by a sensing control node for sending a sensing configuration message, the method comprising:sending (402), to a wireless device, a first sensing configuration message configuring a first sensing session in the wireless device.

18. The method of claim 17, further comprising:receiving, from the wireless device, sensing data for the first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key; andprocessing the sensing data for the first sensing session, wherein processing the sensing data for the first sensing session comprises: i) decrypting the sensing data and / or ii) integrity checking the sensing data using at least the first session key.

19. The method of claim 18, comprising:obtaining a first parameter; andderiving at least the first session key for the first sensing session based on a base key and the first parameter.

20. The method of claim 19, comprising:deriving at least a second session key for the first sensing session based on a base key and the first parameter;decrypting the sensing data for the first sensing session using the first session key; andintegrity checking the sensing data for the first sensing session using the second session key.

21. The method of claim 20, wherein:the second session key is derived based on the base key, the first parameter and / or a second identifier; and / orthe first session key is derived based on the base key, the first parameter and / or a first identifier.

22. The method of any of claims 19 to 21 , wherein the first parameter comprises at least one of:a random or pseudorandom number;a counter;a nonce;a parameter obtained from a sensing control node;at least part of the first sensing configuration message; andat least part of a first session identifier of the first sensing session.

23. The method of any of claims 19 to 22, comprising:receiving the first parameter from the wireless device; and / orsending the first parameter to the wireless device.

24. The method of any of claims 17 to 23, comprising sending, to the wireless device, a second sensing configuration message configuring a second sensing session in the wireless device, or the first sensing configuration message configures a second sensing session in the wireless device.

25. The method of claim 24, further comprising:receiving, from the wireless device, sensing data for the second sensing session, wherein the sensing data for the second sensing session is protected using at least a third session key; andprocessing the sensing data for the second sensing session, wherein processing the sensing data for the second sensing session comprises: i) decrypting the sensing data using at least the third session key and / or ii) integrity checking the sensing data using at least the third session key.

26. The method of claim 25, comprising:obtaining a second parameter; andderiving at least the third session key for the second sensing session based on a base key and the second parameter;deriving at least a fourth session key for the second sensing session based on a base key and the second parameter;decrypting the sensing data for the second sensing session using the third session key; andintegrity checking the sensing data for the second sensing session using the fourth session key.

27. The method of claim 26, wherein:the fourth session key is derived based on i) the base key, ii) the second parameter and / or iii) a second identifier and / or a fourth identifier; and / orthe third session key is derived based on i) the base key, ii) the second parameter and / or iii) a first identifier and / or a third identifier.

28. The method of claim 26 or 27, wherein the second parameter comprises at least one of:a random or pseudorandom number;a counter;a nonce;a parameter obtained from a sensing control node;at least part of the first sensing configuration message or a second sensing configuration message; andat least part of a second session identifier of the second sensing session.

29. The method of any of claims 26 to 28, comprising:receiving the second parameter from the wireless device; and / orsending the second parameter to the wireless device.

30. The method of any of claims 17 to 29, comprising sending a base key identifier to the wireless device, wherein:the base key identifier identifies the base key; orthe base key is derived from a key identified by the base key identifier.

31. The method of any of claims 17 to 30, comprising obtaining the base key from a network node.

32. A method (500) performed by a sensing control node for processing sensing data, the method comprising:receiving (502), from a wireless device, sensing data for a first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key; andprocessing (504) the sensing data for the first sensing session.

33. The method of claim 32, wherein processing (504) the sensing data for the first sensing session comprises: i) decrypting the sensing data using at least the first session key and / or ii) integrity checking the sensing data using at least the first session key.

34. The method of claim 32 or 33, comprising:obtaining a first parameter; andderiving at least the first session key for the first sensing session based on a base key and the first parameter.

35. The method of claim 34, comprising:deriving at least a second session key for the first sensing session based on a base key and the first parameter;decrypting the sensing data for the first sensing session using the first session key; andintegrity checking the sensing data for the first sensing session using the second session key.

36. The method of claim 35, wherein:the second session key is derived based on the base key, the first parameter and / or a second identifier; and / orthe first session key is derived based on the base key, the first parameter and / or a first identifier.

37. The method of any of claims 34 to 36, wherein the first parameter comprises at least one of:a random or pseudorandom number;a counter;a nonce;a parameter obtained from a sensing control node;at least part of a configuration message configuring the first sensing session; and at least part of a first session identifier of the first sensing session.

38. The method of any of claims 34 to 37, comprising:receiving the first parameter from the wireless device, a sensing processing node or a sensing control node.

39. The method of any of claims 32 to 38, further comprising:receiving, from the wireless device, sensing data for the second sensing session, wherein the sensing data for the second sensing session is protected using at least a third session key; andprocessing the sensing data for the second sensing session, wherein processing the sensing data for the second sensing session comprises: i) decrypting the sensing data using at least the third session key and / or ii) integrity checking the sensing data using at least the third session key.

40. The method of claim 39, comprising:obtaining a second parameter; andderiving at least the third session key for the second sensing session based on a base key and the second parameter.

41. The method of claim 40, comprising:deriving at least a fourth session key for the second sensing session based on a base key and the second parameter;decrypting the sensing data for the second sensing session using the third session key; andintegrity checking the sensing data for the second first sensing session using the fourth session key.

42. The method of claim 41 , wherein:the fourth session key is derived based on i) the base key, ii) the second parameter and / or iii) a second identifier and / or fourth identifier; and / orthe third session key is derived based on i) the base key, ii) the second parameter and / or iii) a first identifier and / or third identifier.

43. The method of any of claims 40 to 42, wherein the second parameter comprises at least one of:a random or pseudorandom number;a counter;a nonce;a parameter obtained from a sensing control node;at least part of a configuration message configuring the second sensing session; and at least part of a second session identifier of the second sensing session.

44. The method of any of claims 40 to 43, comprising:receiving the second parameter from the wireless device, a sensing processing node or a sensing control node.

45. The method of any of claims 32 to 44, comprising receiving a base key identifier from the wireless device, a sensing processing node or a sensing control node, wherein:the base key identifier identifies the base key; orthe base key is derived from a key identified by the base key identifier.

46. The method of any of claims 32 to 45, comprising obtaining the base key from a network node.

47. The method of any of claims 32 to 46, wherein the processing node comprises a sensing processing node or a sensing processing session for the first sensing session.

48. The method of any of claims 1 to 47, wherein the first parameter is a parameter for deriving at least the first session key.

49. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (300, 400, 500) of any of claims 1 to 48.

50. A computer program, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (300, 400, 500) according to any of claims 1 to 48.

51. A carrier containing the computer program of claim 50, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

52. Apparatus in a wireless device for deriving a key, the apparatus comprising processing circuitry and a memory, the apparatus configured to:receive (302) a first sensing configuration message configuring a first sensing session in the wireless device;obtain (304) a first parameter; andderive (306) at least a first session key for the first sensing session based on a base key and the first parameter.

53. The apparatus of claim 51 , wherein the apparatus is configured to perform the method (300) of any of claims 2 to 16.

54. Apparatus in a sensing control node for sending a sensing configuration message, the apparatus comprising processing circuitry and a memory, the apparatus configured to: send (402), to a wireless device, a first sensing configuration message configuring a first sensing session in the wireless device.

55. The apparatus of claim 54, wherein the apparatus is configured to perform the method (400) of any of claims 18 to 31.

56. Apparatus in a sensing control node for processing sensing data, the apparatus comprising processing circuitry and a memory, the apparatus configured to:67receive (502), from a wireless device, sensing data for a first sensing session, wherein the sensing data for the first sensing session is protected using at least a first session key; andprocess (504) the sensing data for the first sensing session.

57. The apparatus of claim 56, wherein the apparatus is configured to perform the method (500) of any of claims 33 to 48.68