IP Library Granted Patent US 12,445,833
Granted Patent B2
US 12,445,833 · App. 18/018,590 · Granted Oct 14, 2025

Privacy of relay selection in cellular sliced networks

Inventor: Walter Dees (Eindhoven, NL)
Assignee: Koninklijke Philips N.V.
H04W12/03H04W8/005H04W12/06H04W76/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,445,833
App. No.
18/018,590
Granted
Oct 14, 2025
Kind
B2
Abstract

A cellular communication system supports a Network Relay Function ( 140 ) for managing the indirect connections. A mobile device ( 110 ) may send a request message to a relay device ( 120 ), the request message including a relay service code (associated with a set of privacy sensitive PDU session parameters). The relay device receives the request message and sends a transfer request message to the cellular communication system indicating a request to transfer data via an indirect connection and including the requested relay service code. The Network Relay Function receives the transfer request message, determines a different relay service code to be used instead of the requested relay service code; and sends a transfer response message including the different relay service code in an encrypted manner that allows it to be decrypted by the mobile device, but not the relay device; and forwarding by the relay device the encrypted different relay service code to the mobile device in a response to the request message.

Claims (111)

1. A cellular communication system (CCS) comprising a radio access network (RAN), multiple cellular base stations (BS) and a core network (CN),

the cellular communication system providing a cellular network that supports indirect connections,

each indirect connection providing data transfer between a mobile device and the cellular communication system via at least one relay device being a mobile device arranged for communication with the radio access network and capable of supporting the indirect connection,

the cellular communication system further comprising at least one network relay entity arranged to provide a Network Relay Function (NRF) for managing the indirect connections,

the mobile device comprising:

a connection processor arranged for managing connections to the cellular network, the connection processor providing a relay function for managing at least one indirect connection,

the relay function being arranged to at least

send, as part of a setup procedure, a request message (M) to at least one relay device (UEx), the request message including a Relay Service Code (RSC1) and an encrypted identifier of the at least one relay device (UEx), and further containing an encrypted identifier of the mobile device;

receive a response message (M′) from the at least one relay device (UEx), the response message including an encrypted Relay Service Code (RSC2);

decrypt the encrypted Relay Service Code (RSC2) and insert the decrypted Relay Service Code (RSC2′) instead of RSC1 in subsequent discovery and connection setup messages, whereby RSC2′ is associated with the same set of PDU session attributes as RSC1;

the relay device comprising:

a communication unit arranged for communication in the cellular network, and,

a relay processor arranged for managing the communication in the cellular network and for managing an indirect connection between the mobile device and the cellular network, the relay processor being arranged:

to receive the request message (M) from the mobile device;

after receiving request message (M), to send a transfer request message (N) to the cellular communication system in dependence of the request message (M), the transfer request message (M′) including the Relay Service Code RSC1 and at least one of the encrypted identifiers received from the mobile device in request message (M);

to receive a transfer response message (N′) from the cellular communication system, the transfer response message (N′) containing an encrypted Relay Service Code (RSC2);

after receiving the transfer response message (N′), to send a response message (M) to the mobile device in dependence of the transfer response message and containing the encrypted Relay Service Code (RSC2);

the Network Relay Function being arranged:

to receive at least one transfer request message (N) from the relay device, the transfer request message (N) including a Relay Service Code (RSC1) and at least one of the encrypted identifiers of the mobile device and the encrypted identifier of the relay device;

to determine a different Relay Service Code (RSC2′) to be used instead of the Relay Service Code (RSC1) received in the transfer request message (N); to encrypt the different Relay Service Code (RSC2′) using a key that allows it to be decrypted by the mobile device but not the relay device, resulting in an encrypted Relay Service Code (RSC2);

to send a transfer response message (N′) including the encrypted Relay Service Code (RSC2) to the relay device.

2. The cellular communication system of claim 1 , wherein the Network Relay Function is arranged to encrypt the identifier of the mobile device and/or the identifier of the relay device using a key that allows them to be decrypted by a Network Relay Function (NRF) in the cellular network and not by the relay device.

3. The cellular communication system (CCS) of claim 1 , wherein the relay processor is arranged to store a set of spare Relay Service Codes and wherein the Network Relay Function is arranged to select the different Relay Service Code (RSC2′) from the set of spare Relay Service Codes available in the relay device or a fresh Relay Service Code.

4. The cellular communication system of claim 1 , wherein the mobile device is arranged to send a freshness parameter in the request message, the freshness parameter indicating that keys used to encrypt elements of the request message have not been updated for more than a predetermined time or indicating a time when the keys were last updated.

5. The cellular communication system of claim 1 , wherein the Network Relay Function is arranged to add a decrypted Relay Service Code to the transfer response message (N′) and the relay device is arranged to use the decrypted Relay Service Code to fetch a PDU session attribute.

6. The cellular communication system of claim 1 , wherein the request message (M) and response message (N) include a Global Unique Temporary Identifier (GUTI) or Temporary Mobile Subscriber Identity (TMSI) or Subscription Concealed Identifier (SUCI).

7. The cellular communication system (CCS) of claim 1 , wherein the request message (M) includes a Relay Service Code (RSC1) associated with a set of PDU session attributes.

8. The cellular communication system (CCS) of claim 1 , wherein the mobile device is arranged to include in the request message (M), a nonce and wherein the relay device is arranged to keep track of the used nonces and discard any request messages containing a previously used nonce or abort the setup procedure.

9. The cellular communication system (CCS) of claim 1 , wherein the mobile device is arranged to include in the request message (M), a nonce and wherein relay device is arranged to forward the nonce in the transfer request message (N) and the relay function is arranged to keep track of the used nonces and discard any transfer request messages containing a previously used nonce or abort the setup procedure.

10. The cellular communication system of claim 1 , wherein the mobile device comprises a non-volatile storage unit arranged for storing a set of Relay Service Codes that are supported by the mobile device that may each be associated with a set of PDU session attributes and the mobile device being further arranged to store a set of Relay Service Codes that are supported by the mobile device that may each be associated with a set of PDU session attributes, and the relay device comprises a non-volatile storage unit arranged for storing a set of Relay Service Codes that are supported by the relay device, including the set of spare Relay Service Codes and the relay processor of the relay device being further arranged to store a set of spare Relay Service Codes, and wherein the Network Relay Function being further arranged to determine a different Relay Service Code (RSC2′) to be used instead of the Relay Service Code (RSC1) received in the transfer request message (M′), where the different Relay Service Code (RSC2′) is selected from the set of spare Relay Service Codes available in the relay device.

11. A mobile device arranged to be used in the cellular communication system as defined in claim 1 comprising:

a transceiver arranged for wireless communication in the cellular network, and

being arranged to store a set of Relay Service Codes that are supported by the mobile device that may each be associated with a set of PDU session attributes, and

a connection processor arranged for managing connections to the cellular network, the connection processor providing a relay function for managing at least one indirect connection,

the relay function being arranged to at least:

send, as part of a setup procedure, a request message (M) to at least one relay device (UEx), the request message including a Relay Service Code (RSC1) associated with a set of PDU session attributes and also includes an encrypted identifier of the at least one relay device (UEx), and further containing an encrypted identifier of the mobile device, the identifiers encrypted using a key that allows it to be decrypted by a Network Relay Function (NRF) in the cellular network;

receive a response message (M′) from the at least one relay device (UEx), the response message including an encrypted Relay Service Code (RSC2), the encrypted Relay Service Code (RSC2) encrypted by a Network Relay Function (NRF) in the cellular network using a key that allows it to be decrypted by the mobile device but not the relay device;

decrypt the encrypted Relay Service Code (RSC2) and insert the decrypted Relay Service Code (RSC2′) instead of RSC1 in subsequent discovery and connection setup messages, whereby RSC2′ is associated with the same set of PDU session attributes as RSC1.

12. The mobile device of claim 11 , wherein the mobile device selects a different layer-2 identification for the request message (M) from at least the most recently used layer-2 identifications used in a previous message sent from the mobile device to the relay device.

13. The mobile device of claim 11 , wherein the mobile device is arranged to send a freshness parameter in the request message, the freshness parameter indicating that keys used to encrypt elements of the request message have not been updated for more than a predetermined time or indicating a time when the keys were last updated.

14. The mobile device of claim 11 , wherein the mobile device is arranged to include a Global Unique Temporary Identifier (GUTI) or Temporary Mobile Subscriber Identity (TMSI) or Subscription Concealed Identifier (SUCI) in request message (M).

15. The mobile device of any of claim 11 , wherein the mobile device is arranged to include a nonce in the request message (M).

16. The mobile device of any of claim 11 , wherein the mobile device is arranged to send a freshness parameter in the request message (M), the freshness parameter indicating that keys used to encrypt elements of the request message have not been updated for more than a predetermined time or indicating a time when the keys were last updated.

17. A network relay entity providing a Network Relay Function (NRF) for use in the cellular communication system as defined in claim 1 , the network relay entity being arranged:

to receive at least one transfer request message (N) from a relay device, the transfer request message (M′) including a Relay Service Code (RSC1) and an encrypted identifier of a mobile device that has sent the Relay Service Code (RSC1) to the relay device;

to determine a different Relay Service Code (RSC2′) to be used instead of the Relay Service Code (RSC1) received in the transfer request message (N);

to encrypt the different Relay Service Code (RSC2′) using a key that allows it to be decrypted by the mobile device but not the relay device, resulting in an encrypted Relay Service Code (RSC2), and

to send a transfer response message (N′) including the encrypted Relay Service Code (RSC2) to the relay device.

18. The network relay entity of claim 17 whereby the different Relay Service Code (RSC2′) to be used instead of the Relay Service Code (RSC1) is selected from a set of spare Relay Service Codes available in the relay device.

19. The network relay entity of claim 17 , wherein the Network Relay Function is arranged to add a decrypted Relay Service Code to the transfer response message (N′) and the relay device is arranged to use the decrypted Relay Service Code to fetch a PDU session attribute.

20. The network relay entity of claim 17 , wherein the Network Relay Function is arranged to include a new encrypted Global Unique Temporary Identifier (GUTI) or Temporary Mobile Subscriber Identity (TMSI) or Subscription Concealed Identifier (SUCI) in transfer response message (N′).

21. A relay device arranged for communication in the cellular network of claim 1 and comprising:

a relay processor arranged for managing the communication in the cellular network and for managing an indirect connection between the mobile device and the cellular network,

the relay processor being arranged:

to receive, as part of a setup procedure, the request message (M) from the mobile device;

after receiving request message (M), to send a transfer request message (N) to the cellular communication system in dependence of the request message (M), the transfer request message (N) including the Relay Service Code RSC1 and at least one of the encrypted identifiers received from the mobile device in request message (M);

to receive a transfer response message (N′) from the cellular communication system, the transfer response message (N′) containing an encrypted Relay Service Code (RSC2);

after receiving the transfer response message (N′), to send a response message (M′) to the mobile device in dependence of the transfer response message and containing the encrypted Relay Service Code (RSC2).

22. The relay device of claim 21 , wherein the relay device is arranged to forward, in the transfer request message (N), any nonce or freshness parameter received in the request message (M).

23. The relay device of claim 21 , wherein the relay device is arranged to keep track of the used nonces and discard any request messages containing a previously used nonce or abort the setup procedure.

24. A cellular communication system (CCS) comprising a radio access network (RAN), multiple cellular base stations (BS) and a core network (CN),

the cellular communication system providing a cellular network that supports indirect connections,

each indirect connection providing data transfer between a mobile device and the cellular communication system via at least one relay device being a mobile device arranged for communication with the radio access network and capable of supporting the indirect connection,

the cellular communication system comprising at least one network relay entity arranged to provide a Network Relay Function (NRF) for managing the indirect connections,

the mobile device comprising:

a connection processor arranged for managing connections to the cellular network, the connection processor providing a relay function for managing at least one indirect connection,

the relay function being arranged to at least:

send, as part of a setup procedure, a request message (M) to at least one relay device (UEx), the request message including a Relay Service Code (RSC1) and also includes an identifier of the at least one relay device (Uex), and further containing an identifier of the mobile device and a message authentication code;

receive a response message (M′) from the at least one relay device (Uex), the response message including an encrypted Relay Service Code (RSC2);

decrypt the encrypted Relay Service Code (RSC2) and insert the decrypted Relay Service Code (RSC2′) instead of RSC1 in subsequent discovery and connection setup messages, whereby RSC2′ is associated with the same set of PDU session attributes as RSC1;

the relay device comprising:

a communication unit arranged for communication in the cellular network, and,

a relay processor arranged for managing the communication in the cellular network and for managing an indirect connection between the mobile device and the cellular network,

the relay processor being arranged:

to receive the request message (M) from the mobile device;

after receiving request message (M), to send a transfer request message (N) to the cellular communication system in dependence of the request message (M), the transfer request message (N) including the Relay Service Code RSC1, the message authentication code and the identifier of the mobile device received from the mobile device in request message (M);

to receive a transfer response message (N′) from the cellular communication system, the transfer response message (N′) containing an encrypted Relay Service Code (RSC2);

after receiving the transfer response message (N′), to send a response message (M′) to the mobile device in dependence of the transfer response message and containing the encrypted Relay Service Code (RSC2);

the Network Relay Function being arranged:

to receive at least one transfer request message (N) from the relay device, the transfer request message (N) including a Relay Service Code (RSC1) and an identifier of the mobile device and the message authentication code;

to determine a different Relay Service Code (RSC2′) to be used instead of the Relay Service Code (RSC1) received in the transfer request message (N);

to encrypt the different Relay Service Code (RSC2′) using a key that allows it to be decrypted by the mobile device but not the relay device, resulting in an encrypted Relay Service Code (RSC2);

to send a transfer response message (N′) including the encrypted Relay Service Code (RSC2) to the relay device.

25. The cellular communication system of claim 24 wherein at least one of the Relay Service Code (RSC1), the identifier of the mobile device, and the identifier of the at least one relay device (UEx) in the request message (M) and the transfer request message (N) are encrypted by the mobile device or are integrity protected by the message authentication code, in order to represent a protected indicator indicative that the mobile device has selected the at least one relay device (UEx).

26. The cellular communication system of claim 25 wherein the relay device includes in transfer request message (N) the identifier of the at least one relay device received from the mobile device in the request message (M).

27. The cellular communication system of claim 25 , wherein the key used by the mobile device to encrypt the at least one of the Relay Service Code, the identifier of the mobile and the identifier of the at least one relay device, or the key used to determine the message authentication code allows decryption by the Network Relay Function (NRF) in the cellular network and not by the relay devices (UEx).

28. The cellular communication system of claim 25 , wherein the Network Relay Function (NRF) only sends a transfer response message (N′) containing an encrypted Relay Service Code RSC2 or PDU session information related to RSC1 to the at least one relay device (UEx) if the output of decrypting the received encrypted identifiers reveals an identifier of the at least one relay device or if the Message Authentication Code as forwarded by the at least one relay device and originating from the mobile device reveals that the identifiers have not been manipulated, using the information received in the transfer request message (N).

29. The cellular communication system of claim 28 , wherein the information provided by the encrypted identifiers or message payload with respective Message Authentication Code in the transfer request message (N) is used by the cellular communication system (CCS) to perform an additional verification whether the at least one relay device (UEx) is allowed/authorized to act as relay UE for the respective remote UE.

30. A mobile device arranged to be used in the cellular communication system as defined in claim 24 comprising:

a transceiver arranged for wireless communication in the cellular network, and

being arranged to store a set of Relay Service Codes that are supported by the mobile device that may each be associated with a set of PDU session attributes, and

a connection processor arranged for managing connections to the cellular network, the connection processor providing a relay function for managing at least one indirect connection,

the relay function being arranged to at least:

send a request message (M) to at least one relay device (UEx), the request message including a Relay Service Code (RSC1) and also includes an identifier of the at least one relay device (UEx), and further containing an identifier of the mobile device, and a message authentication code;

receive a response message (M′) from the at least one relay device (UEx), the response message including an encrypted Relay Service Code (RSC2), the encrypted Relay Service Code (RSC2) encrypted by a Network Relay Function (NRF) in the cellular network using a key that allows it to be decrypted by the mobile device but not the relay device;

decrypt the encrypted Relay Service Code (RSC2) and insert the decrypted Relay Service Code (RSC2′) instead of RSC1 in subsequent discovery and connection setup messages, whereby RSC2′ is associated with the same set of PDU session attributes as RSC1.

31. The mobile device of claim 30 whereby a key is used to encrypt at least one of the Relay Service Code, the identifier of the mobile and the identifier of the at least one relay device, or a key is used to determine the message authentication code that allows decryption by the Network Relay Function (NRF) in the cellular network and not by the relay devices (UEx).

32. A network relay entity providing a Network Relay Function (NRF) for use in the cellular communication system as defined in claim 24 , the network relay entity being arranged:

to receive at least one transfer request message (M′) from a relay device, the transfer request message (N) including a Relay Service Code (RSC1) and an identifier of a mobile device that has sent the Relay Service Code (RSC1) to the relay device and a message authentication code;

check the message authentication code to verify that the Relay Service Code and the identifier of the mobile device have not been manipulated

to determine a different Relay Service Code (RSC2′) to be used instead of the Relay Service Code (RSC1) received in the transfer request message (N), whereby the different Relay Service Code (RSC2′) is selected from a set of spare Relay Service Codes available in the relay device or a fresh Relay Service Code;

to encrypt the different Relay Service Code (RSC2′) using a key that allows it to be decrypted by the mobile device but not the relay device, resulting in an encrypted Relay Service Code (RSC2);

to send a transfer response message (N′) including the encrypted Relay Service Code (RSC2) to the relay device.

33. A relay device arranged for communication in the cellular network of claim 24 and comprising:

a relay processor arranged for managing the communication in the cellular network and for managing an indirect connection between the mobile device and the cellular network,

The relay processor being arranged:

to store a set of spare Relay Service Codes;

to receive, as part of a setup procedure, the request message (M) from the mobile device;

after receiving request message (M), to send a transfer request message (N) to the cellular communication system in dependence of the request message (M), the transfer request message (N) including the Relay Service Code RSC1, the message authentication code and the identifier of the mobile device received from the mobile device in request message (M);

to receive a transfer response message (N′) from the cellular communication system, the transfer response message (N′) containing an encrypted Relay Service Code (RSC2);

after receiving the transfer response message (N′), to send a response message (M′) to the mobile device in dependence of the transfer response message and containing the encrypted Relay Service Code (RSC2).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2023
From: DEES, WALTER
To: KONINKLIJKE PHILIPS N.V.
Reel/Frame 062540/0156 →
Priority Claims (6)
EP 20192144 · Aug 21, 2020 · regional
EP 20192352 · Aug 24, 2020 · regional
EP 21152328 · Jan 19, 2021 · regional
EP 21158292 · Feb 19, 2021 · regional
EP 21190309 · Aug 9, 2021 · regional
EP 21191932 · Aug 18, 2021 · regional
Continuity (1)
Related Publication 20230319549A1 · Oct 5, 2023
References Cited (28)
US 9445352B2 · Wu et al. · 2016 [cited by applicant]
US 9565573B2 · Mukherjee et al. · 2017 [cited by applicant]
US 9826460B2 · Patil et al. · 2017 [cited by applicant]
US 10177834B2 · Basu Mallick et al. · 2019 [cited by applicant]
US 10212651B2 · Gulati et al. · 2019 [cited by applicant]
US 10313867B2 · Kuge · 2019 [cited by examiner]
US 20150341794A1 · Vanderveen · 2015 [cited by examiner]
US 20160212721A1 · Sheng et al. · 2016 [cited by applicant]
US 20160227518A1 · Li et al. · 2016 [cited by applicant]
US 20160285539A1 · Sadiq et al. · 2016 [cited by applicant]
US 20180035448A1 · Gupta et al. · 2018 [cited by applicant]
US 20180092017A1 · Freda et al. · 2018 [cited by applicant]
US 20180192280A1 · Kuge · 2018 [cited by applicant]
US 20190335332A1 · Ying · 2019 [cited by examiner]
US 20220330361A1 · Ding · 2022 [cited by examiner]
WO WO2017002855A1 · 2017 [cited by examiner]
WO 2018083381A1 · 2018 [cited by applicant]
WO 2018129543A1 · 2018 [cited by applicant]
WO 2021001086A1 · 2021 [cited by applicant]
International Search Report and Written Opinion from PCT/EP2021/073230 mailed Nov. 22, 2021. [cited by applicant]
Philips International B V: UE-to-Network Relay discovery and handling of POU session parameters with Remote UE based relay selection11,3GPP Draft; S2-2004202, 3rd Generation Partnership Project. (3GPP), Mobile Competenc… [cited by applicant]
Philips International B V: “LIE-to-Network Relay discovery and handling of POU session parameters with CN based relay selection”, 3GPP Draft; S2-2004201, 3rd Generation Partnership Project (3GPP), Mobile Competence Cent… [cited by applicant]
Huawei et al: “Authorization checking on per MCPTT group basis”,3GPP Draft; S6-150732 WAS S6-150693 Authorization Checking on Per MCPTT Group, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Ro… [cited by applicant]
ZTE et al: “Security for Relay Service Code”,3GPP Draft; S3-152275-CR0090—Security for Relay Service Code, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles ; F-06921 Sophia-An… [cited by applicant]
Intel: “Security for Remote UE to UE-Network Relay Proximity-based Services (ProSe) Direct Communication for Public Safety Use”,3GPP Draft; S3-151809, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre;… [cited by applicant]
Philips International B V: “Solution to mitigate privacy issues of relay service codes and POU parameters for L3 UE-to-NW relays”,3GPP Draft; S3-210543, 3rd Generation Partnership Project (3GPP), Mobile Competence Centr… [cited by applicant]
Philips International B V: “Update to solution #32”,3GPP Draft; S3-212147, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France vol. SA W… [cited by applicant]
Samsung , Solution for key management in 5G ProSerelay communication[online] , 3GPP TSG SA WG3 #100e S3-201961 , Internet<URL:https://www.3gpp.org/ftp/tsg_sa/WG3_Security/TSGS3_100e/Docs/S3-201961.zip> , 2020 Apr. 15, … [cited by applicant]
Cited By (1)
US 12,648,030