IP Library Granted Patent US 12,587,924
Granted Patent B2
US 12,587,924 · App. 17/916,304 · Granted Mar 24, 2026

Methods, apparatuses and systems directed to a change of WTRU to WTRU relay

Inventors: Michelle Perras (Montréal, CA); Samir Ferdi (Kirkland, CA); Alec Brusilovsky (Downingtown, PA); Xiaoyan Shi (Westmount, CA); Saad Ahmad (Montreal, CA)
Assignee: INTERDIGITAL PATENT HOLDINGS, INC.
H04W36/08H04W36/0038H04W36/00835H04W36/00837H04W36/037
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,587,924
App. No.
17/916,304
Granted
Mar 24, 2026
Kind
B2
Abstract

Methods, apparatuses, systems, etc., directed to performing a change of relay are disclosed herein. In an embodiment, a WTRU may transmit a link modification request message to a target WTRU via a first relay WTRU for requesting a change of relay. The WTRU may receive a link modification accept message from the target WTRU via the first relay WTRU, indicating a (e.g., proposed) second relay WTRU (e.g., identifier). The WTRU may transmit a direct communication request message including the second relay WTRU identifier for indicating to the target WTRU acceptance of the proposed second relay WTRU. The WTRU may a receiving a direct communication accept message from the target WTRU via the second relay WTRU, indicating the traffic may be relayed via the second relay WTRU.

Claims (30)

1 . A method implemented in a source wireless transmit/receive unit (WTRU), wherein a first link has been established between the source WTRU and a first relay WTRU and wherein a second link has been established between the source WTRU and a second relay WTRU, the method comprising:

transmitting a link modification request message on the first link to the first relay WTRU to be used by the first relay WTRU to transmit a corresponding link modification request message to a target WTRU, wherein the link modification request message is a request for a change of relay for the target WTRU, and wherein the link modification request message comprises a relay reselection indication, a list of candidate relay identifiers and a first Internet Protocol address of the target WTRU;

receiving a link modification accept message on the first link from the first relay WTRU that is based on a corresponding link modification accept message originating from the target WTRU, wherein the link modification accept message indicates that the target WTRU accepts the request for the change of relay, and wherein the link modification accept message comprises the relay reselection indication, an identifier of the second relay WTRU and a second Internet Protocol address of the target WTRU to be used for communication via the second relay WTRU;

transmitting a link modification acknowledge message on the first link to the first relay WTRU to be used by the first relay WTRU to transmit a corresponding link modification acknowledge message to the target WTRU, wherein the link modification acknowledge message acknowledges a target WTRU's acceptance of the request for the change of relay, and wherein the link modification acknowledge message comprises a second Internet Protocol address of the source WTRU to be used for communication via the second relay WTRU; and

switching Internet Protocol traffic directed to the target WTRU from the first link to the second link via the second relay WTRU.

2 . The method according to claim 1 , wherein said transmitting the link modification request message is based on detecting a condition for the change of relay.

3 . The method according to claim 1 , wherein said transmitting the link modification request message is based on receiving, from the first relay WTRU, a trigger for the change of relay.

4 . The method of claim 3 , wherein receiving said trigger for the change of relay comprises receiving an initial link modification request message received from the first relay WTRU.

5 . The method of claim 1 , wherein when the source WTRU is communicating with multiple target WTRUs via the first relay WTRU, the source WTRU transmits a single link modification request message that includes in a same message, a respective IP address of each of the multiple target WTRUs.

6 . The method of claim 1 , wherein the link modification request message further indicates a first IP address of the source WTRU.

7 . The method of claim 6 , wherein the first IP address of the source WTRU and the second IP address of the source WTRU are a same IP address.

8 . The method of claim 6 , wherein the first IP address of the source WTRU is different from the second IP address of the source WTRU.

9 . The method of claim 1 , wherein the first IP address of the target WTRU and the second IP address of the target WTRU are a same IP address.

10 . The method of claim 1 , wherein the first IP address of the target WTRU is different from the second IP address of the target WTRU.

11 . A source wireless transmit/receive unit (WTRU), wherein a first link has been established between the source WTRU and a first relay WTRU and wherein a second link has been established between the source WTRU and a second relay WTRU, the source WTRU comprising:

a processor; and

a transceiver operatively coupled to the processor, the processor being configured to:

transmit a link modification request message on the first link to the first relay WTRU to be used by the first relay WTRU to transmit a corresponding link modification request message to a target WTRU, wherein the link modification request message is a request for a change of relay for the target WTRU, and wherein the link modification request message comprises a relay reselection indication, a list of candidate relay identifiers and a first Internet Protocol address of the target WTRU;

receive a link modification accept message on the first link from the first relay WTRU that is based on a corresponding link modification accept message originating from the target WTRU, wherein the link modification accept message indicates that the target WTRU accepts the request for the change of relay, and wherein the link modification accept message comprises the relay reselection indication, an identifier of the second relay WTRU and a second Internet Protocol address of a target WTRU to be used for communication via the second relay WTRU;

transmit a link modification acknowledge message on the first link to the first relay WTRU to be used by the first relay WTRU to transmit a corresponding link modification acknowledge message to the target WTRU, wherein the link modification acknowledge message acknowledges a target WTRU's acceptance of the request for the change of relay, and wherein the link modification acknowledge message comprises a second Internet Protocol address of the source WTRU to be used for communication via the second relay WTRU; and

switch Internet Protocol traffic directed to the target WTRU from the first link to the second link via the second relay WTRU.

12 . The source WTRU according to claim 11 , wherein being configured to transmit the link modification request message comprises being configured to transmit the link modification request message based on detecting a condition for the change of relay.

13 . The source WTRU according to claim 11 , wherein being configured to transmit the link modification request message comprises being configured to transmit the link modification request message based on receiving a trigger for the change of relay from the first relay WTRU.

14 . The source WTRU of claim 13 , wherein being configured to receive said trigger for the change of relay comprises being configured to receive an initial link modification request message from the first relay WTRU.

15 . The source WTRU of claim 11 , wherein when the source WTRU is communicating with multiple target WTRUs via the first relay WTRU, the source WTRU transmits a single link modification request message that includes in a same message a respective IP address of each of the multiple target WTRUs.

16 . The source WTRU of claim 11 , wherein the link modification request message further indicates a first IP address of the source WTRU via the first relay WTRU.

17 . The source WTRU of claim 16 , wherein the first IP address of the source WTRU and the second IP address of the source WTRU are a same IP address.

18 . The source WTRU of claim 16 , wherein the first IP address of the source WTRU is different from the second IP address of the source WTRU.

19 . The source WTRU of claim 11 , wherein the first IP address of the target WTRU and the second IP address of the target WTRU are a same IP address.

20 . The source WTRU of claim 11 , wherein the first IP address of the target WTRU is different from the second IP address of the target WTRU.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 5, 2023
From: IDAC HOLDINGS, INC.
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 062308/0215 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2022
From: PERRAS, MICHELLE
To: IDAC HOLDINGS, INC.
Reel/Frame 061338/0784 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2022
From: FERDI, SAMIR; BRUSILOVSKY, ALEC; SHI, XIAOYAN; AHMAD, SAAD
To: IDAC HOLDINGS, INC.
Reel/Frame 061338/0880 →
Continuity (2)
Provisional Application 63007008 · Apr 8, 2020
Related Publication 20230224778A1 · Jul 13, 2023
References Cited (64)
US 9155002B2 · Jang · 2015 [cited by examiner]
US 10326516B2 · Zhao · 2019 [cited by examiner]
US 10492120B2 · Yasukawa · 2019 [cited by examiner]
US 11239898B1 · Chandra et al. · 2022 [cited by applicant]
US 11638132B2 · Perras et al. · 2023 [cited by applicant]
US 20050135305A1 · Wentink · 2005 [cited by examiner]
US 20060105709A1 · Oh et al. · 2006 [cited by applicant]
US 20070297367A1 · Wang et al. · 2007 [cited by applicant]
US 20110238997A1 · Bellur et al. · 2011 [cited by applicant]
US 20140032905A1 · Long et al. · 2014 [cited by applicant]
US 20140119544A1 · Lee · 2014 [cited by applicant]
US 20140135019A1 · Jang et al. · 2014 [cited by applicant]
US 20140215135A1 · Park et al. · 2014 [cited by applicant]
US 20160100353A1 · Gleixner · 2016 [cited by examiner]
US 20170202038A1 · Ahmad · 2017 [cited by applicant]
US 20170245245A1 · Kim et al. · 2017 [cited by applicant]
US 20170289098A1 · Chun et al. · 2017 [cited by applicant]
US 20180077241A1 · Byun et al. · 2018 [cited by applicant]
US 20180084481A1 · Wang · 2018 [cited by examiner]
US 20180152234A1 · Huang et al. · 2018 [cited by applicant]
US 20180159935A1 · Cavalcanti et al. · 2018 [cited by applicant]
US 20180254820A1 · Chae et al. · 2018 [cited by applicant]
US 20190053251A1 · Loehr et al. · 2019 [cited by applicant]
US 20190089547A1 · Simplicio, Jr. et al. · 2019 [cited by applicant]
US 20190223008A1 · Vanderveen et al. · 2019 [cited by applicant]
US 20190254103A1 · Nord · 2019 [cited by examiner]
US 20200100088A1 · Kim et al. · 2020 [cited by applicant]
US 20200145798A1 · Kim et al. · 2020 [cited by applicant]
US 20200178048A1 · Kim et al. · 2020 [cited by applicant]
US 20200336258A1 · Zhu et al. · 2020 [cited by applicant]
US 20210144781A1 · Xu et al. · 2021 [cited by applicant]
US 20210153063A1 · Zhang · 2021 [cited by examiner]
US 20210211870A1 · Perras et al. · 2021 [cited by applicant]
US 20210336967A1 · Yasukawa · 2021 [cited by examiner]
US 20220007445A1 · Pan et al. · 2022 [cited by applicant]
US 20220369215A1 · Dees · 2022 [cited by examiner]
US 20220377524A1 · Ferdi et al. · 2022 [cited by applicant]
US 20230032220A1 · Guo et al. · 2023 [cited by applicant]
US 20230269573A1 · Orsino · 2023 [cited by examiner]
CN 112839374A · 2021 [cited by applicant]
CN 114846841A · 2022 [cited by applicant]
CN 113011765B · 2022 [cited by applicant]
EP 2733988A2 · 2014 [cited by applicant]
EP 3185612A1 · 2017 [cited by applicant]
EP 3280209A1 · 2018 [cited by applicant]
JP 2021027585A · 2021 [cited by applicant]
RU 2400942C1 · 2010 [cited by applicant]
WO 2016122533A1 · 2016 [cited by applicant]
WO 2017027355A1 · 2017 [cited by applicant]
WO 2017173072A1 · 2017 [cited by applicant]
WO 2018066876A1 · 2018 [cited by applicant]
WO 2018128505A1 · 2018 [cited by applicant]
WO 2018208061A1 · 2018 [cited by applicant]
WO 2021201857A1 · 2021 [cited by applicant]
WO 2022150538A1 · 2022 [cited by applicant]
Anonymous, “Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services”, 3rd Generation Partnership Project (3GPP), Technical Specification Group Services and System Aspects, Document:… [cited by applicant]
Anonymous, Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS), 3rd Generation Partnership Project (3GPP), Technical Specification Group Services and System Aspects, Document: TR 23.7… [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Study on architecture enhancements for the Evolved Packet System (EPS) and the 5G System (5GS) to support advanced V2X se… [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Study on security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services (Release 16),” 3GPP TR 33.836… [cited by applicant]
Qualcomm Inc., et al. “V2X privacy over PC5,” 3GPP TSG-CT WG1 Meeting #101bis, C1-170340, Spokane, USA (Jan. 16-20, 2017). [cited by applicant]
Qualcomm Inc.: “Security establishment procedures for Prose one-to-one communication”, 3GPP Tdoc C1-161418 3GPP TSG-CT WG1 Meeting #96, Jeju (Korea), Feb. 15-19, 2016, 37 pages. [cited by applicant]
Interdigital: “TR 33.836 solution #4 update”, 3GPP Draft; S3-193307—TR 33.836 Solution 4 Update, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis C… [cited by applicant]
LG Electronics, “Clarification of ID change for V2X PC5 conmunication” 3GPP TSG SA WG3 (Security) Meeting #87, S3-171109, Ljubljana, Slovenia (May 15-19, 2017). [cited by applicant]
Anonymous, “New SID: Study on architecture enhancements for 3GPP support of advanced V2X services—Phase 2”, 3rd Generation Partnership Project (3GPP), Document: SP-190631, 3GPP SA2 Meeting #134, Sapporo, Japan, Jun. 24,… [cited by applicant]