US-12621744-B2 - Change of PC5 link identifiers between the WTRU and the layer-2 WTRU to WTRU relay
Abstract
In examples, the E2E link IDs may be isolated per-hop, so that changes of link IDs may not impact other E2E/per-hop links (e.g., a LIU procedure may only run between a WTRU and the relay). A relay may allocate R-specific security IDs/session key identifiers (e.g., MSBs/LSBs of Knrp-sess ID). The relay (e.g., relay WTRU) may replace the security IDs/session key identifiers received from peer WTRUs with R-specific security IDs/session key identifiers, for example, if forwarding a message. In examples, per-hop IDs and E2E IDs may be added to link identifier update messages. In examples, the support application layer ID and IP address/prefix may be changed using a link modification procedure (e.g., between E2E peer WTRUs), which may be executed during the LIU procedure run between a WTRU and a WTRU-to-WTRU relay.
Inventors
- Michelle Perras
- Samir Ferdi
- XiaoYan Shi
- Taimoor ABBAS
Assignees
- INTERDIGITAL PATENT HOLDINGS, INC.
Dates
- Publication Date
- 20260505
- Application Date
- 20220107
Claims (20)
- 1 . A relay wireless transmit/receive unit (WTRU) for establishing an end-to-end (E2E) link, comprising: a processor configured to: receive a first message from a first WTRU, wherein the first message comprises an adaptation header that indicates a first set of most significant bits (MSBs) for the first WTRU that are associated with a first session key identifier; generate a second session key identifier; generate a second set of MSBs based on the second session key identifier, wherein the second set of MSBs have a mapping to the first set of MSBs; send a second message to a second WTRU, wherein the second message indicates the second set of MSBs; generate a first set of least significant bits (LSBs) based on the second session key identifier, wherein the first set of LSBs have a mapping to a second set of LSBs that are associated with the second WTRU; and send a third message to the first WTRU, wherein the third message indicates the first set of LSBs.
- 2 . The relay WTRU of claim 1 , wherein the processor is further configured to: receive a fourth message from the first WTRU, wherein the fourth message comprises a first data, the first set of LSBs, and the first set of MSBs for the first WTRU.
- 3 . The relay WTRU of claim 2 , wherein the processor is further configured to: generate a fifth message to the second WTRU based on the first set of LSBs and the first set of MSBs, wherein the fifth message comprises the first data, the second set of MSBs, and the second set of LSBs; and send the fifth message to the second WTRU.
- 4 . The relay WTRU of claim 2 , wherein the processor is further configured to: receive a sixth message from the second WTRU, wherein the sixth message comprises a second data, the second set of MSBs, and the second set of LSBs for the second WTRU.
- 5 . The relay WTRU of claim 4 , wherein the processor is further configured to: generate a seventh message to the first WTRU based on the second set of MSBs and the second set of LSBs, wherein the seventh message comprises the second data, the first set of LSBs, and the first set of MSBs; and send the seventh message to the first WTRU.
- 6 . The relay WTRU of claim 1 , wherein the processor is further configured to: receive a fourth message from the first WTRU, wherein the fourth message indicates E2E link information including the first session key identifier, indicates a request to update E2E link information associated with the E2E link and with the first session key identifier, and indicates a third set of MSBs for the first WTRU.
- 7 . The relay WTRU of claim 6 , wherein the processor is further configured to: determine a third set of LSBs, wherein the third set of LSBs and the third set of MSBs for the first WTRU are associated with the first session key identifier; and send a fifth message to the first WTRU, wherein the fifth message indicates the third set of LSBs.
- 8 . The relay WTRU of claim 7 , wherein the processor is further configured to: receive a sixth message from the first WTRU, wherein the sixth message indicates that the first WTRU received the indication of the third set of LSBs.
- 9 . The relay WTRU of claim 1 , wherein the first session key identifier and the second session key identifier are associated with a same session.
- 10 . The relay WTRU of claim 1 , wherein the adaptation header comprises the second message and the third message.
- 11 . A method for establishing an end-to-end (E2E) link, comprising: receiving a first message from a first WTRU, wherein the first message comprises an adaptation header that indicates a first set of most significant bits (MSBs) for the first WTRU that are associated with a first session key identifier; generating a second session key identifier; generating a second set of MSBs based on the second session key identifier, wherein the second set of MSBs have a mapping to the first set of MSBs; sending a second message to a second WTRU, wherein the second message indicates the second set of MSBs; generating a first set of least significant bits (LSBs) based on the second session key identifier, wherein the first set of LSBs have a mapping to a second set of LSBs that are associated with the second WTRU; and sending a third message to the first WTRU, wherein the third message indicates the first set of LSBs.
- 12 . The method of claim 11 , further comprising: receiving a fourth message from the first WTRU, wherein the fourth message comprises a first data, the first set of LSBs, and the first set of MSBs for the first WTRU.
- 13 . The method of claim 12 , further comprising: generating a fifth message to the second WTRU based on the first set of LSBs and the first set of MSBs, wherein the fifth message comprises the first data, the second set of MSBs, and the second set of LSBs; and sending the fifth message to the second WTRU.
- 14 . The method of claim 13 , further comprising: receiving a sixth message from the second WTRU, wherein the sixth message comprises a second data, the second set of MSBs, and the second set of LSBs for the second WTRU.
- 15 . The method of claim 14 , further comprising: generating a seventh message to the first WTRU based on the second set of MSBs and the second set of LSBs, wherein the seventh message comprises the second data, the first set of LSBs, and the first set of MSBs; and sending the seventh message to the first WTRU.
- 16 . The method of claim 11 , further comprising: receiving a fourth message from the first WTRU, wherein the fourth message indicates E2E link information including the first session key identifier, indicates a request to update E2E link information associated with the E2E link and with the first session key identifier, and indicates a third set of MSBs for the first WTRU.
- 17 . The method of claim 16 , further comprising: determining a third set of LSBs, wherein the third set of LSBs and the third set of MSBs for the first WTRU are associated with the first session key identifier; and sending a fifth message to the first WTRU, wherein the fifth message indicates the third set of LSBs.
- 18 . The method of claim 17 , further comprising: receiving a sixth message from the first WTRU, wherein the sixth message indicates that the first WTRU received the indication of the third set of LSBs.
- 19 . The method of claim 11 , wherein the first session key identifier and the second session key identifier are associated with a same session.
- 20 . The method of claim 11 , wherein the adaptation header comprises the second message and the third message.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS This application is the National Stage Entry under 35 U.S.C. § 371 of Patent Cooperation Treaty Application No. PCT/US2022/011541, filed Jan. 7, 2022, which claims the benefit of Provisional U.S. Patent Application No. 63/134,838, filed Jan. 7, 2021, and Provisional U.S. Patent Application No. 63/170,888, filed Apr. 5, 2021, the disclosures of which are incorporated herein by reference in their entireties. BACKGROUND Mobile communications using wireless communication continue to evolve. A fifth generation of mobile communication radio access technology (RAT) may be referred to as 5G new radio (NR). A previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long term evolution (LTE). SUMMARY In examples, the end-to-end (E2E) link identifications (IDs) may be isolated per-hop, so that changes of link IDs may not impact other E2E/per-hop links (e.g., a Linked Identifier Update (LIU) procedure may run between a WTRU and the relay). A relay (e.g., a relay WTRU) may allocate R-specific security IDs/session key identifiers (e.g., most significant bits (MSBs)/least significant bits (LSBs) of Knrp-sess ID). The relay (e.g., relay WTRU) may replace the security IDs/session key identifiers received from peer WTRUs with R-specific security IDs/session key identifiers, for example, if forwarding a message. In examples, per-hop IDs and E2E IDs may be added to link identifier update messages. In examples, the support application layer ID and IP address/prefix may be changed using a link modification procedure (e.g., between E2E peer WTRUs), which may be executed during the LIU procedure run between a WTRU and a WTRU-to-WTRU relay. In examples, a WTRU may send a Direct Communication Request (DCR) message. The DCR message may not include an adaptation header. The DCR message may be sent for a discovery and link establishment request (e.g., integrated discovery). A relay (e.g., relay WTRU) may receive the DCR message. The relay (e.g., relay WTRU) may add an adaptation header to the DCR message before forwarding it. In examples, for standalone discovery, announcement and solicitation messages may be sent without an adaptation header. A relay (e.g., relay WTRU) may add an adaptation header before forwarding the messages. The response message may be sent with the adaptation header from the responding WTRU. In examples, no adaptation header may be used, and the E2E ID may be added to the message payload. In examples, a relay (e.g., a relay WTRU) for establishing an E2E link may be provided. The relay WTRU may include a processor The processor may be configured to receive a first message from a first WTRU. The first message may indicate MSBs for the first WTRU that may be associated with a session key identifier. The processor may be configured to send a second message to a second WTRU. The second message may indicate relay MSBs. The relay MSBs may be associated with the MSBs for the first WTRU and may be associated with the session key identifier. The processor may be configured to send a third message to the first WTRU. The third message may indicate relay LSBs. The relay LSBs may be associated with LSBs for the second WTRU and may be associated with the session key identifier. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented. FIG. 1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment. FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment. FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment. FIG. 2 illustrates an example of a Layer 2 (L2) WTRU-to-WTRU relay. FIG. 3 shows an example of an end-to-end (E2E) link establishment. FIG. 4 shows an example of a Linked Identifier Update (LIU) procedure isolated on a per-hop link basis. FIG. 5 illustrates an example procedure if the application layer ID and Internet Protocol (IP) address/prefix are changed on the source WTRU. FIG. 6 illustrates an example compatible direct/indirect PC5 unicast link establishment procedure. FIG. 7 illustrates an example of a discovery procedure when an adaptation header is included. FIG. 8 illustrates another example of a discovery procedure when an adaptation header is included. DETAILED DESCRIPTION FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, vi