Patent Application
20250081257
The present application relates generally to device-to-network relaying and relates more particularly to relaying for an emergency service.
Proximity services (ProSe) in a communication network enable communication devices that are in proximity of one another to communicate directly, via a path not traversing any network node. Proximity services relaying exploits ProSe so that one communication device can relay traffic for another communication device in proximity. For example, a so-called ProSe device-to-network relay is a communication device that relays unicast traffic between a remote communication device and the communication network. Via a Pro-Se device-to-network relay, then, the remote communication device can communicate with the network even if the remote communication device is outside of the network's coverage.
To support traffic relaying, the relay communication device reports an identifier for the remote communication device to the communication network, e.g., so that the communication network can track which sessions are for relaying traffic for the remote communication device. The reported identifier can be a subscription identifier stored on an integrated circuit card of the communication device, e.g., a subscription concealed identifier (SUCI) stored on a Universal Subscriber Identity Module (USIM). Or, the reported identifier can be a proximity services relay user key (PRUK) identity bound to a proximity services relay user key that is generated during authentication of the remote communication device, for protecting an interface between the relay and remote communication devices.
Challenges exist, though, in enabling support for relaying traffic for an emergency service, e.g., 112 or 911 calls. Indeed, given the emergency nature of an emergency service, the traffic should be relayed even if the remote communication device lacks an integrated circuit card (e.g., USIM) and/or even if authentication of the remote communication device fails. Yet if the remote communication device lacks an integrated circuit card and authentication can't be completed, then the relay communication device heretofore has no identifier to report to the communication network for use by the communication network in identifying the remote communication device. Existing approaches therefore fail to adequately support emergency service relaying under some circumstances.
Some embodiments herein exploit an equipment identifier associated with a remote communication device for identifying the remote communication device in a context where a relay communication device relays traffic for the remote communication device. The equipment identifier may for instance be an International Mobile Equipment Identity (IMEI). By exploiting such an equipment identifier, some embodiments advantageously provide more robust support for emergency service traffic relaying. Indeed, because the equipment identifier is available even if the remote communication device lacks an integrated circuit card and even if the remote communication device cannot be authenticated, some embodiments support emergency service traffic relaying even in this case.
More particularly, embodiments herein include a method performed by a relay communication device configured to relay traffic for a remote communication device. The method comprises receiving, from the remote communication device, an equipment identifier associated with the remote communication device. In this case, the method alternatively or additionally comprises transmitting, to a network node in a communication network, a report that reports an equipment identifier associated with the remote communication device as identifying the remote communication device for which the relay communication device is to relay traffic.
In some embodiments, the method also comprises relaying traffic between the remote communication device and the communication network.
In some embodiments, the method comprises receiving the equipment identifier. In some embodiments, the equipment identifier is received in a request for the relay communication device to relay traffic for the remote communication device. In some embodiments, the request is a Direct Communication Request, DCR. In some embodiments, the request requests the relay communication device to relay traffic for the remote communication device for an emergency service. In some embodiments, the request includes an emergency relay service code. In some embodiments, the method further comprises receiving, from the remote communication device, a request for the relay communication device to relay traffic for the remote communication device. In this case, the method further comprises making a decision to transmit the identity request to the remote communication device, based on the received request lacking the equipment identifier. In some embodiments, the identity request is transmitted according to the decision. In some embodiments, the identity request is a Remote Identity Request or is included in a Direct Security Mode Command message.
In some embodiments, the method comprises transmitting the report. In some embodiments, the report is a Remote User Equipment Report. In some embodiments, the network node implements a Session Management Function, SMF.
In some embodiments, the equipment identifier is a Permanent Equipment Identifier, PEI.
In some embodiments, the equipment identifier is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
In some embodiments, the relay communication device is to relay traffic for the remote communication device for an emergency service.
In some embodiments, the method further comprises receiving the equipment identifier and/or transmitting the report reporting the equipment identifier, based on the traffic being for an emergency service and/or based on receiving an emergency service relay code.
In some embodiments, the remote communication device lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the communication device.
In some embodiments, the method further comprises making a decision to skip a security procedure with the remote communication device, based on the relay communication device receiving the equipment identifier and/or an emergency relay service code. In this case, the method further comprises, in accordance with the decision, skipping the security procedure with the remote communication device.
In some embodiments, the method further comprises, based on failure of or skipping of a security procedure with the remote communication device, performing a direct security mode command procedure with null ciphering and integrity protection. In some embodiments, performing the direct security mode command procedure includes transmitting a message of the direct security mode command procedure with a flag indicating an algorithm chosen for the null ciphering and integrity protection. In some embodiments, performing the direct security mode command procedure includes setting a root key to a value specific for null ciphering and integrity protection and/or setting each of one or more session keys to a value specific for null ciphering and integrity protection.
In some embodiments, the relay communication device is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
In some embodiments, the remote communication device is a 5G ProSe Remote User Equipment.
Other embodiments herein include a method performed by a remote communication device. The method comprises transmitting, to a relay communication device configured to relay traffic for the remote communication device, an equipment identifier associated with the remote communication device.
In some embodiments, the method further comprises transmitting traffic to a communication network via the relay communication device, with the equipment identifier identifying the remote communication device to the communication network.
In some embodiments, the equipment identifier is transmitted in a request for the relay communication device to relay traffic for the remote communication device. In some embodiments, the request is a Direct Communication Request, DCR. In some embodiments, the request requests the relay communication device to relay traffic for the remote communication device for an emergency service. In some embodiments, the request includes an emergency relay service code.
In some embodiments, the method further comprises receiving, from the relay communication device, an identity request requesting information identifying the remote communication device. In some embodiments, the equipment identifier is transmitted in response to the identity request. In some embodiments, the method further comprises transmitting, to the relay communication device, a request for the relay communication device to relay traffic for the remote communication device, wherein the request lacks the equipment identifier. In some embodiments, the identity request is received after transmitting the request. In some embodiments, the identity request is a Remote Identity Request or is included in a Direct Security Mode Command message.
In some embodiments, the equipment identifier is a Permanent Equipment Identifier, PEI.
In some embodiments, the equipment identifier is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
In some embodiments, the relay communication device is to relay traffic for the remote communication device for an emergency service.
In some embodiments, the method further comprises transmitting the equipment identifier, based on the traffic being for an emergency service and/or based on transmitting an emergency service relay code.
In some embodiments, the remote communication device lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the communication device.
In some embodiments, the method further comprises, based on failure of or skipping of a security procedure with the relay communication device, performing a direct security mode command procedure with null ciphering and integrity protection. In some embodiments, performing the direct security mode command procedure includes receiving a message of the direct security mode command procedure with a flag indicating an algorithm chosen for the null ciphering and integrity protection. In some embodiments, performing the direct security mode command procedure includes setting a root key to a value specific for null ciphering and integrity protection and/or setting each of one or more session keys to a value specific for null ciphering and integrity protection.
In some embodiments, the relay communication device is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
In some embodiments, the remote communication device is a 5G ProSe Remote User Equipment.
Other embodiments herein include a method performed by a network node in a communication network. The method comprises receiving, from a relay communication device configured to relay traffic for the remote communication device, a report that reports an equipment identifier associated with the remote communication device as identifying the remote communication device for which the relay communication device is to relay traffic.
In some embodiments, the method further comprises using the equipment identifier to identify the remote communication device and/or to determine that the remote communication device has an ongoing session.
In some embodiments, the report is a Remote User Equipment Report.
In some embodiments, the network node implements a Session Management Function, SMF.
In some embodiments, the equipment identifier is a Permanent Equipment Identifier, PEI.
In some embodiments, the equipment identifier is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
In some embodiments, the relay communication device is to relay traffic for the remote communication device for an emergency service.
In some embodiments, the remote communication device lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the remote communication device.
In some embodiments, the relay communication device is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
In some embodiments, the remote communication device is a 5G ProSe Remote User Equipment.
Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.
Of course, the present disclosure is not limited to the above features and advantages. Indeed, those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.
Some embodiments herein exploit an equipment identifier 20 associated with the remote communication device 14 for identifying the remote communication device 14 in this context. The equipment identifier 20 may identify the remote communication device 14 separate and apart from a subscription to receive communication services. The equipment identifier 20 may for instance be a Permanent Equipment Identifier (PEI), e.g., in the form of an International Mobile Equipment Identity (IMEI) or an IMEI Software Version (IMEISV).
As shown in this regard, the remote communication device 14 transmits the equipment identifier 20 to the relay communication device 12. In some embodiments, the remote communication device 14 transmits the equipment identifier 20 in a request (e.g., a Direct Communication Request, DCR) for the relay communication device 12 to relay traffic for the remote communication device 14. In other embodiments, the remote communication device 14 transmits the equipment identifier 20 in a response to an identity request 26 from the relay communication device 12 requesting information identifying the remote communication device 14, e.g., where the identity request 26 may be a Remote Identity Request or may be included in a Direct Security Mode Command message. In one such embodiment, the relay communication device 12 makes a decision to transmit the identity request 26 to the remote communication device 14 if the relay communication device 12 receives a request to relay traffic but the request lacks the equipment identifier 20.
Regardless, in receipt of such an equipment identifier 20, the relay communication device 12 may report the equipment identifier 20 to a network node 22 in the communication network 10, e.g., a network node implementing a Session Management Function (SMF).
By exploiting such an equipment identifier 20, some embodiments advantageously provide more robust support for emergency service traffic relaying. Indeed, in some embodiments, the equipment identifier 20 herein is available even if the remote communication device 14 lacks an integrated circuit card, or subscriber identity module, for storing a subscription identity (e.g., an International Mobile Subscription Identity, IMSI) identifying a subscription associated with the remote communication device 14. And the equipment identifier 20 is moreover available even if the remote communication device 14 cannot be authenticated. Accordingly, even if the remote communication device 14 lacks an integrated circuit card or subscriber identity module, and even if the remote communication device 14 cannot be authenticated, some embodiments still enable identification of the remote communication device 14 so as to still support emergency service traffic relaying in this case.
Some embodiments herein then are implemented as part of, in order for, or conditional upon the relay communication device 12 relaying traffic for the remote communication device 14 for an emergency service. For example, in some embodiments, the remote communication device 14 transmits the equipment identifier 20 to the relay communication device 12 based on the traffic 18 being for an emergency service and/or based on transmitting an emergency relay service code (RSC). The remote communication device 14 may for example transmit the equipment identifier 20 in a request (e.g., a Direct Communication Request, DCR) for the relay communication device 12 to relay traffic for the remote communication device 14 for an emergency service, e.g., in which case the request may include an emergency relay service code (RSC). In one such embodiment, though, the remote communication device 14 transmits the equipment identifier 20 to the relay communication device 12 in this case only if the remote communication device 14 lacks an integrated circuit card or subscriber identity module, and/or if the remote communication device 14 cannot be authenticated, i.e., if the remote communication device 14 is unable to provide a proximity services relay user key (PRUK) identity or subscription identity.
Consider now an example of some embodiments herein where the relay communication device 12 is a 5G ProSe UE-to-Network Relay and the remote communication device 14 is a 5G ProSe Remote User Equipment (UE).
A 5G ProSe UE-to-Network Relay is a (5G ProSe-enabled) UE that provides functionality to support connectivity to the network for 5G ProSe Remote UE(s).
Some embodiments herein are applicable to the procedure of Security for 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay, as otherwise specified by TS 33.503 V17.1.0. Embodiments herein are applicable to either or both methods i.e., user-plane (UP) based and control-plane (CP) based procedures. Both can be used for 5G ProSe UE-to-Network Relay authorization and security establishment in PC5 interface. The UP based procedure as shown in
Some embodiments herein may be incorporated into the high-level flows of security for UE-to-Network Relays as shown in
Some embodiments herein in this regard support emergency service over UE-to-Network Relay, e.g., per TS23.700-33 V1.0.0,
According to TS 22.101, emergency service is defined as citizen to authority services, and it is left to the national authorities to decide whether the network accepts emergency calls e.g. for valid UE only, or for UEs without the SIM/USIM/ISIM. Here, ISIM stands for Internet Protocol (IP) Multimedia Services Identity Module.
In the 5G ProSe UE-to-Network relaying, if there is an emergency request from the remote UE, it implies that the Relay UE needs to be responsible for remote UE's emergency service. It is required that the Relay UE has a valid SIM/USIM/ISIM.
In some embodiments, the Relay UE shall support to establish PC5 communication for emergency service, for either an authenticated Remote UE (e.g. Remote UE with USIM and properly being authenticated by PC5 communication security procedure) or an unauthenticated Remote UE (e.g. Remote UE without USIM or authentication can't complete for any reason).
Some embodiments herein specify a procedure to setup the emergency session and the security thereof.
In particular, some embodiments herein propose that a normal PC5 communication security procedure for emergency service is performed for a valid Remote User ID. By contrast, in some embodiments, a PC5 communication security with null ciphering and integrity is performed for an unauthenticated Remote UE.
With regard to reporting for an emergency service, in some embodiments, an authenticated Remote User ID, i.e. (UP-/CP-) PRUK ID or SUbscription Concealed Identifier (SUCI), is used as UE ID for an authenticated remote UE. By contrast, in case of an unauthenticated Remote UE, a PEI in some embodiments is used to identify the UE in a Remote UE Report. Some embodiments herein therefore include one or more methods to retrieve the PEI of the remote UE over the PC5 link.
Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments allow PC5 communication establishment and reporting for unauthenticated UEs.
Step 0a. The 5G ProSe UE-to-Network relay 12 is provisioned with the discovery security materials as described in TS 33.503 V17.1.0. Based on the local regulation and the operator policy, there may or may not be discovery security materials provisioned for Emergency Relay Service Code (RSC).
Step 0b. The 5G ProSe Remote UE 14 is provisioned with the discovery security materials and retrieves the UP-PRUK and UP-PRUK ID for UP based security method from the network as described in TS 33.503 V17.1.0. Based on the local regulation and the operator policy, there may be or may be no discovery security materials provisioned for Emergency RSC.
If the 5G ProSe Remote UE is USIM-less, this step is skipped. The Emergency RSC and the discovery security materials (if exist) are locally configured in the 5G ProSe Remote UE 14.
Step 1. The discovery procedure for the Emergency RSC is performed between the 5G ProSe Remote UE 14 and the 5G ProSe UE-to-Network Relay 12 using the discovery parameters and discovery security material as described in TS 33.503 V17.1.0.
Based on the local regulation and the operator policy, the announcement and discovery of Emergency RSC may be performed without security protection.
Step 2. If the 5G ProSe Remote UE 14 has USIM, the 5G ProSe Remote UE 14 sends a Direct Communication Request (DCR) that contains (UP-/CP-) PRUK ID or SUCI, Emergency RSC and KNRP freshness parameter 1 to the 5G ProSe UE-to-Network Relay 12. The message may additionally include the PEI of the 5G ProSe Remote UE 14.
If the 5G ProSe Remote UE 14 is USIM-less, the 5G ProSe Remote UE 14 sends a Direct Communication Request that contains PEI and Emergency RSC to the 5G ProSe UE-to-Network Relay 12. In this way, the 5G ProSe Remote UE 14 may send the 5G ProSe UE-to-Network Relay 12 its equipment identifier 20 as shown in
Step 3, composed of Steps 3a and 3b. If (UP-/CP-) PRUK ID or SUCI is received, the 5G ProSe UE-to-Network Relay 12 performs UP or CP based security procedure as described in TS33.503 V17.1.0. This includes the 5G ProSe UE-to-Network Relay 12 transmitting a key request to the 5GC (Step 3a) and receiving a key response from the 5GC, including the requested key (Step 3b).
If only PEI and Emergency RSC are received, the 5G ProSe UE-to-Network Relay 12 skips this step if the local regulation and the operator policy allow.
Step 4, composed of Steps 4a and 4b. If step 3 is successfully performed, the 5G ProSe UE-to-Network Relay 12 performs Direct Security Mode Command procedure towards the 5G ProSe Remote UE 13 as described in TS33.503 V17.1.0. This includes the 5G ProSe UE-to-Network Relay 12 transmitting a Direct Security Mode Command towards the 5G ProSe Remote UE 13 (Step 4a) and receiving a Direct Security Mode Complete from the 5G ProSe Remote UE 13 (Step 4b).
If step 3 is failed or skipped, e.g., the 5G ProSe Remote UE 13 is USIM-less, the 5G ProSe UE-to-Network Relay 12 performs Direct Security Mode Command procedure with Null ciphering and integrity protection if the local regulation and the operator policy allow.
In the message, there may be included a flag to indicate the chosen algorithm for Null ciphering and integrity protection. Null ciphering and integrity protection may be achieved by setting PC5 link root key or session keys to a specific value e.g., all zeros.
In the message, there may be included an indicator e.g., “PEI request” to request PEI (e.g., IMEI) from the remote UE 14.
Step 5, composed of Steps 5a and 5b. If the 5G ProSe Remote UE 14 is not authenticated successfully via UP or CP based security procedure (step 3 fails or skipped) or Direct Security Mode Command procedure (step 4) failed or skipped, and PEI is not received from Direct Communication Request, the 5G ProSe UE-to-Network Relay 12 sends Remote Identity Request to the 5G ProSe Remote UE 14 (Step 5a) to retrieve the PEI based on the local regulation and the operator policy. Here, the Remote Identity Request exemplifies the identity request 26 in
Step 6. The 5G ProSe UE-to-Network Relay 12 sends a Direct Communication Accept message to the 5G ProSe Remote UE 14 to finish the PC5 connection establishment procedures for the emergency service.
Step 7. When the 5G ProSe Layer-3 UE-to-Network Relay 12 sends a Remote UE Report to the SMF for the Emergency RSC, the 5G ProSe Layer-3 UE-to-Network Relay 12 includes Remote User ID i.e. (UP-/CP-) PRUK ID if UP or CP based security procedure is successfully performed. Otherwise, the 5G ProSe Layer-3 UE-to-Network Relay 12 includes the PEI of the 5G ProSe Remote UE 14 in the Remote UE Report. Here, the Remote UE Report exemplifies the report 24 in
In some embodiments herein, a Permanent Equipment Identifier (PEI) is defined for the 3GPP UE accessing the 5G System. The PEI can assume different formats for different UE types and use cases. The UE shall present the PEI to the network together with an indication of the PEI format being used. If the UE supports at least one 3GPP access technology (i.e. NG-RAN, E-UTRAN, UTRAN or GERAN), the UE must be allocated a PEI in the IMEI or IMEISV format. If a UE has registered with a network by using a network subscription and a PEI of the UE, then the UE shall keep the PEI to be used with the network subscription and shall not use that PEI with another network subscription while the UE is in registered state in the network.
In some embodiments, the PEI may be one of the following: (i) for UEs that support at least one 3GPP access technology, an IMEI or IMEISV, as defined in TS 23.003 v17.6.0; (ii) PEI used in the case of W-5GAN access as further specified in TS 23.316 v17.3.0; (iii) for UEs not supporting any 3GPP access technologies, the IEEE Extended Unique Identifier EUI-64 of the access technology the UE uses to connect to the 5GC.
In some embodiments, the Relay Service Code (RSC) is used in the 5G ProSe UE-to-Network Relay discovery, to indicate the connectivity service the 5G ProSe UE-to-Network Relay 12 provides to the 5G ProSe Remote UE 14. The RSCs are configured on the 5G ProSe UE-to-Network Relay 12 and the 5G ProSe Remote UE 14.
In some embodiments, an ‘Emergency call’ refers to speech calls, and Global Traffic Technologies (GTT) Emergency calls if applicable. Emergency calls will be routed to the emergency services in accordance with national regulations for where the subscriber is located. This may be based upon one or more default emergency call numbers stored in the mobile equipment (ME). It shall be allowed to establish an emergency call without the need to dial a dedicated number to avoid the mis-connection in roaming case, such as menu, by use of a ‘red button’, or a linkage to a car air bag control. Emergency calls shall be supported by the UE without a SIM/USIM/ISIM being present.
Emergency calls shall be supported by UEs that are subject to service restrictions, e.g. for UEs camping on a cell in a forbidden PLMN or in a forbidden Location Area (LA) (see 3GPP TS 22.011 v18.3.0), or on a Closed Subscriber Group (CSG) cell without the subscriber being a member of that CSG (see 3GPP TS 22.220 v17.0.0). Such emergency calls shall be accepted by the network if required by local regulation.
It shall be possible to initiate emergency calls to different emergency call centres, depending on the type of emergency. Some embodiments herein are applicable for one or more of following types of emergency calls: Police, Ambulance, Fire Brigade, Marine Guard, Mountain Rescue, Manually Initiated eCall (MleC), Automatically Initiated eCall (AleC)
The Home Environment operator shall specify preferred emergency call numbers (e.g. 999 for United Kingdom (UK) citizens or 110, 118 and 119 for Japanese citizens). These emergency call numbers shall be stored in the SIM/USIM and the ME shall read this and use any entry of these digits to set up an emergency call. It shall be possible to store more than one instance of this field.
It shall be possible to tie any emergency call number to any single emergency call type or to any combination of emergency call types. The association between emergency call numbers and emergency call type shall be able to be programmed by the Home Environment operator into the SIM/USIM.
The ME shall identify an emergency number dialled by the end user as a valid emergency number and initiate emergency call establishment if it occurs under one or more of the following conditions. If it occurs outside of the following conditions, the ME should not initiate emergency call establishment but normal call establishment. Emergency number identification takes place before and takes precedence over any other (e.g. supplementary service related) number analysis.
In view of the modifications and variations herein,
Regardless, the method in some embodiments includes receiving, from the remote communication device 14, an equipment identifier 20 associated with the remote communication device 14, e.g., a Permanent Equipment Identifier, PEI. (Block 630).
The method alternatively or additionally includes transmitting, to a network node 22 in a communication network 10, a report 24 that reports an equipment identifier 20 associated with the remote communication device 14 as identifying the remote communication device 14 for which the relay communication device 12 is to relay traffic 18 (Block 670). In some embodiments, the report is a Remote User Equipment Report. In some embodiments, the network node implements a Session Management Function, SMF.
In some embodiments, the method also comprises relaying traffic 18 between the remote communication device 12 and the communication network 10 (Block 680).
In some embodiments, the method comprises receiving the equipment identifier 20 and/or transmitting the report 24 reporting the equipment identifier 20, based on the traffic 18 being for an emergency service and/or based on receiving an emergency service relay code.
In some embodiments where the method comprises receiving the equipment identifier 20, the equipment identifier 20 may be received in a request for the relay communication device 12 to relay traffic 18 for the remote communication device 14. In some embodiments, the request is a Direct Communication Request, DCR. In some embodiments, the request requests the relay communication device 12 to relay traffic for the remote communication device 14 for an emergency service. In some embodiments, the request includes an emergency relay service code.
In other embodiments, though, if the request for the relay communication device 12 to relay traffic 18 for the remote communication device 14 lacks the equipment identifier 20 (Block 600), the method further comprises making a decision to transmit an identity request 26 to the remote communication device 14, based on the received request lacking the equipment identifier 20 (Block 610). According to this decision, then, the method further comprises transmitting, to the remote communication device 14, an identity request 26 requesting information identifying the remote communication device 14 (Block 620). In some embodiments, the identity request is a Remote Identity Request or is included in a Direct Security Mode Command message.
In some embodiments, the method further comprises making a decision to skip a security procedure with the remote communication device 14, based on the relay communication device 12 receiving the equipment identifier 20 and/or an emergency relay service code (Block 640). In one such embodiment, the method further comprises, in accordance with the decision, skipping the security procedure with the remote communication device 14 (Block 650). In some embodiments, the method further comprises, based on failure of or skipping of a security procedure with the remote communication device 14, performing a direct security mode command procedure with null ciphering and integrity protection (Block 660). In some embodiments, performing the direct security mode command procedure includes transmitting a message of the direct security mode command procedure with a flag indicating an algorithm chosen for the null ciphering and integrity protection. In some embodiments, performing the direct security mode command procedure includes setting a root key to a value specific for null ciphering and integrity protection and/or setting each of one or more session keys to a value specific for null ciphering and integrity protection.
In some embodiments, the equipment identifier is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
In some embodiments, the relay communication device 12 is to relay traffic for the remote communication device for an emergency service.
In some embodiments, the remote communication device 14 lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the remote communication device 14.
In some embodiments, the relay communication device 12 is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
In some embodiments, the remote communication device 14 is a 5G ProSe Remote User Equipment.
In some embodiments, the method further comprises transmitting traffic 18 to a communication network 10 via the relay communication device 12, with the equipment identifier 20 identifying the remote communication device 14 to the communication network 10 (Block 740).
In some embodiments, the equipment identifier 20 is transmitted in a request for the relay communication device 12 to relay traffic for the remote communication device 14. In some embodiments, the request is a Direct Communication Request, DCR. In some embodiments, the request requests the relay communication device 12 to relay traffic for the remote communication device 14 for an emergency service. In some embodiments, the request includes an emergency relay service code.
In other embodiments, the method further comprises transmitting, to the relay communication device 12, a request for the relay communication device 12 to relay traffic 18 for the remote communication device 14, wherein the request lacks the equipment identifier 20 (Block 700). In one such embodiment, the method further comprises receiving, from the relay communication device 12, an identity request 26 requesting information identifying the remote communication device 14 (Block 710). In some embodiments, the identity request is a Remote Identity Request or is included in a Direct Security Mode Command message. In some embodiments, the equipment identifier is transmitted in response to the identity request.
In some embodiments, the equipment identifier 20 is a Permanent Equipment Identifier, PEI.
In some embodiments, the equipment identifier 20 is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
In some embodiments, the relay communication device 12 is to relay traffic for the remote communication device 14 for an emergency service.
In some embodiments, the method further comprises transmitting the equipment identifier 20, based on the traffic 18 being for an emergency service and/or based on transmitting an emergency service relay code.
In some embodiments, the remote communication device 14 lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the remote communication device 14.
In some embodiments, the method further comprises, based on failure of or skipping of a security procedure with the relay communication device 12, performing a direct security mode command procedure with null ciphering and integrity protection (Block 730). In some embodiments, performing the direct security mode command procedure includes receiving a message of the direct security mode command procedure with a flag indicating an algorithm chosen for the null ciphering and integrity protection. In some embodiments, performing the direct security mode command procedure includes setting a root key to a value specific for null ciphering and integrity protection and/or setting each of one or more session keys to a value specific for null ciphering and integrity protection.
In some embodiments, the relay communication device 12 is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
In some embodiments, the remote communication device 14 is a 5G ProSe Remote User Equipment.
In some embodiments, the method further comprises using the equipment identifier 20 to identify the remote communication device 14 and/or to determine that the remote communication device 14 has an ongoing session (Block 810).
In some embodiments, the report 24 is a Remote User Equipment Report.
In some embodiments, the network node 22 implements a Session Management Function, SMF.
In some embodiments, the equipment identifier 20 is a Permanent Equipment Identifier, PEI.
In some embodiments, the equipment identifier 20 is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
In some embodiments, the relay communication device 12 is to relay traffic for the remote communication device 14 for an emergency service.
In some embodiments, the remote communication device 14 lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the remote communication device 14.
In some embodiments, the relay communication device 12 is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
In some embodiments, the remote communication device 14 is a 5G ProSe Remote User Equipment.
Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device configured to perform any of the steps of any of the embodiments described above for the relay communication device 12 or the remote communication device 14.
Embodiments also include a communication device comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device. The power supply circuitry is configured to supply power to the relay communication device 12 or the remote communication device 14.
Embodiments further include a communication device comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the relay communication device 12 or the remote communication device 14. In some embodiments, the communication device further comprises communication circuitry.
Embodiments further include a communication device comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device is configured to perform any of the steps of any of the embodiments described above for the relay communication device 12 or the remote communication device 14.
Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the relay communication device 12 or the remote communication device 14. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.
Embodiments herein also include a network node 22 configured to perform any of the steps of any of the embodiments described above for the network node 22.
Embodiments also include a network node 22 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 22. The power supply circuitry is configured to supply power to the network node 22.
Embodiments further include a network node 22 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 22. In some embodiments, the network node 22 further comprises communication circuitry.
Embodiments further include a network node 22 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node 22 is configured to perform any of the steps of any of the embodiments described above for the network node 22.
More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.
Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.
A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.
Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.
Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.
In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 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 1100 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 1100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
The UEs 1112 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 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1112 and/or with other network nodes or equipment in the telecommunication network 1102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1102.
In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. 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 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include 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).
The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and/or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 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.
As a whole, the communication system 1100 of
In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 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 IoT services to yet further UEs.
In some examples, the UEs 1112 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 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. 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).
In the example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and/or 1112d) and network nodes (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 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 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 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 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
The hub 1114 may have a constant/persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow for a different communication scheme and/or schedule between the hub 1114 and UEs (e.g., UE 1112c and/or 1112d), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and/or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 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 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub—that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
The host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and a memory 1212. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as
The memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g., data generated by a UE for the host 1200 or data generated by the host 1200 for a UE. Embodiments of the host 1200 may utilize only a subset or all of the components shown. The host application programs 1214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1200 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
Like host 1200, embodiments of host 1302 include hardware, such as a communication interface, processing circuitry, and memory. The host 1302 also includes software, which is stored in or accessible by the host 1302 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1306 connecting via an over-the-top (OTT) connection 1350 extending between the UE 1306 and host 1302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1350.
The network node 1304 includes hardware enabling it to communicate with the host 1302 and UE 1306. The connection 1360 may be direct or pass through a core network (like core network 1106 of
The UE 1306 includes hardware and software, which is stored in or accessible by UE 1306 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1306 with the support of the host 1302. In the host 1302, an executing host application may communicate with the executing client application via the OTT connection 1350 terminating at the UE 1306 and host 1302. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1350 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1350.
The OTT connection 1350 may extend via a connection 1360 between the host 1302 and the network node 1304 and via a wireless connection 1370 between the network node 1304 and the UE 1306 to provide the connection between the host 1302 and the UE 1306. The connection 1360 and wireless connection 1370, over which the OTT connection 1350 may be provided, have been drawn abstractly to illustrate the communication between the host 1302 and the UE 1306 via the network node 1304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
As an example of transmitting data via the OTT connection 1350, in step 1308, the host 1302 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1306. In other embodiments, the user data is associated with a UE 1306 that shares data with the host 1302 without explicit human interaction. In step 1310, the host 1302 initiates a transmission carrying the user data towards the UE 1306. The host 1302 may initiate the transmission responsive to a request transmitted by the UE 1306. The request may be caused by human interaction with the UE 1306 or by operation of the client application executing on the UE 1306. The transmission may pass via the network node 1304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1312, the network node 1304 transmits to the UE 1306 the user data that was carried in the transmission that the host 1302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1314, the UE 1306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1306 associated with the host application executed by the host 1302.
In some examples, the UE 1306 executes a client application which provides user data to the host 1302. The user data may be provided in reaction or response to the data received from the host 1302. Accordingly, in step 1316, the UE 1306 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1306. Regardless of the specific manner in which the user data was provided, the UE 1306 initiates, in step 1318, transmission of the user data towards the host 1302 via the network node 1304. In step 1320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1304 receives user data from the UE 1306 and initiates transmission of the received user data towards the host 1302. In step 1322, the host 1302 receives the user data carried in the transmission initiated by the UE 1306.
One or more of the various embodiments improve the performance of OTT services provided to the UE 1306 using the OTT connection 1350, in which the wireless connection 1370 forms the last segment.
In an example scenario, factory status information may be collected and analyzed by the host 1302. As another example, the host 1302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1302 may store surveillance video uploaded by a UE. As another example, the host 1302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1350 between the host 1302 and UE 1306, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1302 and/or UE 1306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1304. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1350 while monitoring propagation times, errors, etc.
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.
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.
Notably, modifications and other embodiments of the present disclosure will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the present disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples:
A1. A method performed by a relay communication device configured to relay traffic for a remote communication device, the method comprising:
A12. The method of any of embodiments A10-A11, wherein the network node implements a Session Management Function, SMF.
A13. The method of any of embodiments A1-A12, wherein the equipment identifier is a Permanent Equipment Identifier, PEI.
A14. The method of any of embodiments A1-A13, wherein the equipment identifier is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
A15. The method of any of embodiments A1-A14, wherein the relay communication device is to relay traffic for the remote communication device for an emergency service.
A16. The method of any of embodiments A1-A15, further comprising receiving the equipment identifier and/or transmitting the report reporting the equipment identifier, based on the traffic being for an emergency service and/or based on receiving an emergency service relay code.
A17. The method of any of embodiments A1-A16, wherein the remote communication device lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the communication device.
A18. The method of any of embodiments A1-A17, further comprising:
AA3. The method of embodiment AA1, wherein the equipment identifier is transmitted in a request for the relay communication device to relay traffic for the remote communication device.
AA4. The method of embodiment AA3, wherein the request is a Direct Communication Request, DCR.
AA5. The method of any of embodiments AA3-AA4, wherein the request requests the relay communication device to relay traffic for the remote communication device for an emergency service.
AA6. The method of any of embodiments AA3-AA5, wherein the request includes an emergency relay service code.
AA7. The method of embodiment AA, further comprising receiving, from the relay communication device, an identity request requesting information identifying the remote communication device, wherein the equipment identifier is transmitted in response to the identity request.
AA8. The method of embodiment AA7, further comprising transmitting, to the relay communication device, a request for the relay communication device to relay traffic for the remote communication device, wherein the request lacks the equipment identifier, wherein the identity request is received after transmitting the request.
AA9. The method of embodiment AA8, wherein the identity request is a Remote Identity Request or is included in a Direct Security Mode Command message.
AA10. The method of any of embodiments AA1-AA9, wherein the equipment identifier is a Permanent Equipment Identifier, PEI.
AA11. The method of any of embodiments AA1-AA13, wherein the equipment identifier is an International Mobile Equipment Identity, IMEI, or an IMEI Software Version, IMEISV.
AA12. The method of any of embodiments AA1-AA11, wherein the relay communication device is to relay traffic for the remote communication device for an emergency service.
AA13. The method of any of embodiments AA1-AA12, further comprising transmitting the equipment identifier, based on the traffic being for an emergency service and/or based on transmitting an emergency service relay code.
AA14. The method of any of embodiments AA1-AA13, wherein the remote communication device lacks a universal integrated circuit card, or subscriber identity module, for storing a subscription identity associated with the communication device.
AA15. The method of any of embodiments AA1-AA14, further comprising, based on failure of or skipping of a security procedure with the relay communication device, performing a direct security mode command procedure with null ciphering and integrity protection.
AA16. The method of embodiment AA15, wherein performing the direct security mode command procedure includes receiving a message of the direct security mode command procedure with a flag indicating an algorithm chosen for the null ciphering and integrity protection.
AA17. The method of any of embodiments AA15-AA16, wherein performing the direct security mode command procedure includes setting a root key to a value specific for null ciphering and integrity protection and/or setting each of one or more session keys to a value specific for null ciphering and integrity protection.
AA18. The method of any of embodiments AA1-AA17, wherein the relay communication device is a Layer-3 UE-to-Network Relay or a 5G Proximity Services, ProSe, UE-to-Network Relay.
AA19. The method of any of embodiments AA1-AA18, wherein the remote communication device is a 5G ProSe Remote User Equipment.
AA. The method of any of the previous embodiments, further comprising:
B1. A method performed by a network node in a communication network, the method comprising:
C1. A communication device configured to perform the method of any of the Group A embodiments.
C2. A communication device comprising processing circuitry configured to perform the method of any of the Group A embodiments.
C3. A communication device comprising:
D1. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/CN2022/123440 | Sep 2022 | WO | international |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2023/077113 | 9/29/2023 | WO |
