[go: up one dir, main page]

WO2025071922A1 - Gestion d'id court à l'aide de pc5-rrc pour un protocole d'adaptation de relais de liaison latérale u2u (srap) - Google Patents

Gestion d'id court à l'aide de pc5-rrc pour un protocole d'adaptation de relais de liaison latérale u2u (srap) Download PDF

Info

Publication number
WO2025071922A1
WO2025071922A1 PCT/US2024/046089 US2024046089W WO2025071922A1 WO 2025071922 A1 WO2025071922 A1 WO 2025071922A1 US 2024046089 W US2024046089 W US 2024046089W WO 2025071922 A1 WO2025071922 A1 WO 2025071922A1
Authority
WO
WIPO (PCT)
Prior art keywords
short
terminal
remote
destination
source
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/046089
Other languages
English (en)
Inventor
Henry Chang
Masato Fujishiro
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kyocera Corp
Original Assignee
Kyocera Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kyocera Corp filed Critical Kyocera Corp
Publication of WO2025071922A1 publication Critical patent/WO2025071922A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • This invention generally relates to wireless communications and more particularly to Short ID management for U2U Sidelink Relay Adaptation Protocol (SRAP).
  • SRAP Short ID management for U2U Sidelink Relay Adaptation Protocol
  • U2N UE-to-Network
  • the U2N link includes a PC5 link between the relay device and the remote UE and Uu link between the relay device and a base station in the network.
  • the U2N communication links use a Sidelink Relay Adaptation Protocol (SRAP) defined by one or more revisions of the 3 rd Generation Partnership Project (3GPP) standards to transmit control and data signals over the PC5 link and the Uu link.
  • SRAP is used to perform bearer mapping (signaling radio bearers (SRBs) and data radio bearers (DRBs)) between the two links.
  • SRBs signal radio bearers
  • DRBs data radio bearers
  • a local Remote UE ID is included in both the PC5 SRAP header and the Uu SRAP header.
  • the Layer 2 (L2) U2N Relay UE is configured by the gNB with the local Remote UE ID to be used in SRAP headers.
  • FIG. 5 is a flow chart of an example of a method of managing Short IDs for an E2E PC5 communication link performed at a relay terminal.
  • SRAP is applied to the adaptation layer 106 for RBs mapping where a SRAP entity is implemented at each device for each link hop.
  • Each SRAP entity has transmitting and receiving portions.
  • the transmitting portion of the SRAP entity 120 at the remote source UE has a corresponding receiving portion of the SRAP entity 122 at the LI2U relay UE (relay terminal)
  • the transmitting portion of the SRAP entity 122 at the U2U relay UE (relay terminal) has a corresponding receiving portion of the SRAP entity 120 at the source remote UE (remote source terminal).
  • the 1X1:1 mapping is supported by the first hop PC5 adaptation layer 120, 122 between the remote UE sidelink (SL) RBs and first hop PC5-RLC channels for relaying.
  • the first hop adaptation layer over the first PC5 hop 118 between the source remote UE and the relay UE supports identification of traffic destined to different remote destination UEs.
  • the second hop PC5 adaptation layer 126, 128 supports bearer mapping between the ingress RLC channels over the first PC5 hop and egress RLC channels over the second PC5 hop 124 at the L1 U2U relay UE.
  • the adaptation layer 106 is supported over the second PC5 link for the L2 U2U relay.
  • the adaptation layer 106 is laid over the RLC sublayer for both the control plane and the user plane over the second PC5 link 124.
  • SDAP sidelink Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • FIG. 2A is a block diagram of a system 200 for an example of Short ID (Local ID) selection for PC5 SRAP for an E2E PC5 communication link 202 with at least one relay terminal 204, 206.
  • a remote source terminal 210 establishes an E2E PC5 communication link 202 between the remote source terminal 210 and a remote destination terminal 212 through the at least one relay terminal 204, 206.
  • the first relay terminal 206 is the relay terminal connected to the remote source terminal 210 through a PC5-RRC link and the last relay terminal 210 is the relay terminal connected to the remote destination terminal 212 through a PC5-RRC link.
  • the first relay terminal 206 is represented with dashed lines in FIG.
  • the remote and relay terminals use ProSe UE IDs to establish the E2E PC5 link 202 in accordance with known techniques.
  • ProSe UE IDs include Application Layer IDs and L2IDs.
  • a User Info ID is an Application layer ID.
  • the E2E PC5 link 202 includes a PC5 first hop 218 between the source remote terminal 210 and the first relay terminal 206, a PC5 second hop 214 between the first relay terminal 206 and the second relay terminal 204, and a PC5 third hop 216 between the second relay terminal 204 and the destination remote terminal 212.
  • E2E PC5-RRC messages are encapsulated in the hop-by-hop PC5-RRC messages.
  • the relay terminal selects Local IDs sequentially such that the currently selected Local ID is the next highest Local ID that is not in use. With such a technique, therefore, the relay terminal may first assign a Local ID of “0” where the next selected Local ID is “1” if not in use. In other situations, the Local ID may be based on a ProSe UE ID of a terminal. The ProSe UE IDs may be L2IDs in some circumstances. In other circumstances, the ProSe UE IDs are the User Info IDs. In some examples, the last relay terminal 204 selects both portions 222, 224 to generate the Short ID 220.
  • the source portion 224 is selected by the remote source terminal 210 and is forwarded to the last relay terminal 204 where the last relay terminal 204 selects the destination portion 222 that is combined with the source portion 224 to generate the Short ID 220.
  • the relay terminal 204 provides information identifying the Short ID 220 to the remote destination terminal 212 and to the PC5-connected relay terminal 206.
  • Each relay terminal facilitating the E2E PC5 link 202 receives and forwards the information to the next relay terminal such that the information is eventually received by the remote source terminal 210.
  • the remote terminals 210, 212 include the Short ID in headers of messages transmitted over the E2E PC5 link 202 and the relay terminals 204, 206 apply the Short ID 220 to the SRAP to facilitate SRB and DRB mapping.
  • the Short ID 220 includes two portions 222, 224.
  • the two portions 222, 224 can be interpreted as two separate Local IDs of the remote terminals 210, 214.
  • the source portion 224 therefore, can be a source Local ID of the remote source terminal 210 and the destination portion 222 can be a destination Local ID of the remote destination terminal 212.
  • the Short ID 220 is applied to the SRAP at each relay terminal and is included in the header of messages transmitted by the remote terminals.
  • the Short ID in the headers may depend on the direction of the E2E transmission, however.
  • the Short ID is composed of the source Local ID and destination Local ID, the order of the Local IDs within in the Short ID may be reversed when the packet is transmitted from the destination remote UE to the source remote UE.
  • Such a technique may be advantageous when the relay terminal cannot determine which direction the packet is directed. This may be more of a consideration when there are many relay terminals involved in the E2E path. Therefore, the Short ID in a header in message transmitted from the remote source terminal to the remote destination terminal over the E2E PC5 link 202 may include the source portion prior to the destination portion.
  • the Short ID in a header in message transmitted from the remote destination terminal to the remote source terminal over the E2E PC5 link 202 may include the destination portion prior to the source portion.
  • the remote and relay terminals use ProSe UE IDs to establish the E2E PC5 link 202 in accordance with known techniques.
  • ProSe UE IDs include Application Layer IDs and L2IDs.
  • a User Info ID is an Application layer ID.
  • the E2E PC5 link 202 includes the PC5 first hop 218 between the source remote terminal 210 and the first relay terminal 206, a PC5 second hop 214 between the first relay terminal 206 and the second relay terminal 204, and a PC5 third hop (last hop) 216 between the second relay terminal 204 and the destination remote terminal 212.
  • the E2E PC5-RRC link is established before the Short ID selection process.
  • the Short ID assignment procedure is executed while the PC5-RRC connection for each of the hops 214, 216, 218 is established.
  • the example of FIG. 2B can be modified such that transmissions of the Short ID assignment procedure are included within the hop-by-hop (HbH) PC5-RRC connection establishment procedure.
  • the remote source terminal and the remote destination terminal may each transmit information over the established E2E link.
  • the remote source terminal may be a transmitting terminal or a receiving terminal and the remote destination terminal may be transmitting terminal or a receiving terminal.
  • transmissions to a relay terminal from the remote terminals 210, 212 include the ProSe UE ID such as the User Info ID in a header of the transmissions.
  • the relay terminal at the other endpoint of the hop recognizes the ProSe UE ID of the transmitting remote terminal.
  • the User Info of a terminal UE is essentially a unique permanent identifier of the terminal.
  • the remote source terminal 210 sends a Short ID request message 226 to the first relay terminal 206 for a Short ID (Local ID) for use in the SRAP layer of the protocol stack by both relay terminals 204, 206.
  • the Short ID request message 226 includes at least an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212.
  • the destination ProSe UE ID is the L2ID of the remote destination terminal 212 and the Short ID request message 226 is a RRCReconfigurationSidelink message.
  • the last relay terminal 204 determines whether the relay terminal 204 is the last relay terminal connected through the last hop to the remote destination terminal. In response to determining that the next hop is the last hop 216 to the remote destination terminal, the last relay terminal generates the Short ID 220 for the remote source terminal. For the example, therefore, the last relay terminal selects the destination portion 222 and selects the source portion 224. In one example, each portion 222, 224 includes four bits such that the Short ID 220 is eight bits long.
  • the first relay terminal 206 sends a Short ID message 234 to the remote source terminal 210.
  • the Short ID message 234 includes at least the Short ID and the destination ProSe UE ID, such as the L2ID of the remote destination terminal 212.
  • the Short ID message 234 is an RRCReconfigurationSidelink message in the example.
  • the Short ID is applied to the SRAP layer by each relay terminal 204, 206 and each remote terminal 210, 212 includes the Short ID in the SRAP header for E2E transmissions.
  • FIG. 2B includes two relay terminals supporting the E2E link 202
  • the principles described above can be applied to E2E links including any number of relay terminals.
  • the SRAP Short ID management technique may be applied to an E2E link including only a single relay terminal.
  • the Short ID assignment procedure is executed while the PC5-RRC connection for each of the hops 214, 216, 218 is established.
  • the example of FIG. 2C can be modified such that transmissions of the Short ID assignment procedure are included within the hop-by-hop (HbH) PC5-RRC connection establishment procedure.
  • the remote source terminal and the remote destination terminal may each transmit information over the established E2E link.
  • the remote source terminal may be a transmitting terminal or a receiving terminal and the remote destination terminal may be transmitting terminal or a receiving terminal.
  • transmissions to a relay terminal from the remote terminals 210, 212 include the ProSe UE ID such as the User Info ID in a header of the transmissions.
  • the relay terminal at the other endpoint of the hop recognizes the ProSe UE ID of the transmitting remote terminal.
  • the User Info of a terminal UE is essentially a unique permanent identifier of the terminal.
  • the remote source terminal 210 sends a Short ID request message 226 to the first relay terminal 206 for a Short ID (Local ID) for use in the SRAP layer of the protocol stack by both relay terminals 204, 206.
  • the Short ID request message 226 includes at least an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212.
  • the destination ProSe UE ID is the L2ID of the remote destination terminal 212 and the Short ID request message 226 is a RRCReconfigurationSidelink message.
  • the Short ID request message 226 is transmitted after the PC5-RRC connection between remote source terminal 210 and the first relay 206 is established, but before the other PC5-RRC connections are established for the remaining hops 214, 216.
  • the first relay terminal 206 selects a source portion 224 of the Short ID 220 and sends a Short ID portion message 236 to the remote source terminal 210.
  • the Short ID portion message 236 includes at least the selected source portion 224 of the Short ID 220.
  • the first relay terminal 206 selects a portion of the L2ID of the remote source terminal 210 as the source portion 224.
  • the Short ID portion message 236 is a RRCReconfigurationCompleteSidelink message in the example.
  • the first relay terminal 206 determines whether the first relay terminal 206 is the last relay terminal connected through the last hop to the remote destination terminal. The first relay terminal 206, therefore, determines if the egress hop of the first relay terminal 206 is to the remote destination terminal 212. In response to determining that the next hop is not to the remote destination terminal, the first relay terminal sends, a Short ID assignment request message 238 to the next relay terminal (last relay terminal 204).
  • the Short ID assignment request message 238 at least includes an indication that the Short ID should be assigned, the source portion 224, and the destination ProSe LIE ID of the remote destination terminal 212, such as the L2ID of the remote destination terminal 212.
  • the Short ID assignment request message 228 is a PC5-RRC message for the example.
  • the last relay terminal 204 determines whether the relay terminal 204 is the last relay terminal connected through the last hop to the remote destination terminal. In response to determining that the next hop is the last hop 216 to the remote destination terminal 212, the last relay terminal 204 selects a destination portion 222 of the Short ID for the destination terminal and combines the source portion 224 and the destination portion 222 to generate the Short ID 220. In one example, each portion 222, 224 includes four bits such that the Short ID 220 is eight bits long. In some situations, the last relay terminal 212 evaluates the source portion 224 of the Short ID 220 to determine if there is conflict with using the source Local ID selected by the first relay terminal.
  • the last relay terminal 212 determines if the source Local ID is in use for another communication link. If the source Local ID (source portion 224) is in use, the last relay terminal sends a Short ID rejection message to the first relay terminal indicating the source portion of the Short ID is not acceptable.
  • the last relay terminal 204 sends the Short ID 220 to the remote destination terminal 212 in a Short ID message 230 that at least includes the Short ID 220 and the source ProSe UE ID, such as the L2ID of the remote source terminal 210.
  • the Short ID message 230 is an RRCReconfigurationSidelink message in the example.
  • the Short ID 220 may include a source Local ID and destination Local ID.
  • the last relay terminal 204 also sends information related to the Short ID 220 to the first relay terminal 206 in a Short ID message 240 that at least includes the destination portion 222 of the Short ID 220 and the destination ProSe UE ID, such as the L2ID of the remote destination terminal 212.
  • the Short ID message 240 therefore, includes the destination Local ID and the L2ID of the remote destination terminal 212.
  • the Short ID message 240 is a PC5-RRC message in the example.
  • the first relay terminal 206 sends a Short ID message 242 to the remote source terminal 210.
  • the Short ID message 240 includes at least the destination portion 222 of the Short ID 220 and the destination ProSe UE ID, such as the L2ID of the remote destination terminal 212.
  • the Short ID message 240 is an RRCReconfigurationSidelink message in the example.
  • FIG. 20 includes two relay terminals supporting the E2E link 202
  • the principles described above can be applied to E2E links including any number of relay terminals.
  • the SRAP Short ID management technique may be applied to an E2E link including only a single relay terminal.
  • FIG. 2D is a block diagram of the system 200 for an example of Short ID (Local ID) selection for PC5 SRAP for an E2E PC5 communication link 202 provided by a single relay terminal 204.
  • the source remote terminal 210 establishes an E2E PC5 communication link 202 between the source remote terminal 210 and a destination remote terminal 212 through the relay terminal 204.
  • the E2E PC5-S link is established before the Short ID selection process and the Short ID assignment procedure is executed while the PC5-RRC connection for each of the hops 216, 218 is established. In some situations, however, the Short ID selection process is performed after the E2E PC5 RRC connection is established.
  • the remote source terminal and the remote destination terminal may each transmit information over the established E2E link.
  • the remote source terminal may be a transmitting terminal or a receiving terminal and the remote destination terminal may be transmitting terminal or a receiving terminal.
  • transmissions to a relay terminal from the remote terminals 210, 212 include the ProSe UE ID such as the User Info ID in a header of the transmissions.
  • the relay terminal at the other endpoint of the hop recognizes the ProSe UE ID of the transmitting remote terminal.
  • the User Info of a terminal UE is essentially a unique permanent identifier of the terminal.
  • the PC5-RRC connection between the remote source terminal 210 and the relay terminal 204 is established in accordance with known techniques.
  • the remote source terminal 210 sends a Short ID request message 250 to the relay terminal 204 for a Short ID (Local ID) for use in the SRAP layer of the protocol stack by the relay terminal 204.
  • the Short ID request message 250 includes at least an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212.
  • the destination ProSe UE ID is the L2ID of the remote destination terminal 212 and the Short ID request message 250 is a RRCReconfigurationSidelink message.
  • the Short ID request message 250 is transmitted after the PC5-RRC connection between remote source terminal 210 and the relay terminal 204 is established, but before the other PC5-RRC connection is established for the last hop [0051]
  • the relay terminal 204 determines whether the relay terminal 204 is the last relay terminal connected through the last hop to the remote destination terminal. The relay terminal 204, therefore, determines if the egress hop of the relay terminal 204 is to the remote destination terminal 212.
  • the relay terminal 204 selects the source portion 224 and the destination portion 222 of the Short ID 220 and sends a Short ID message 252 to the remote source terminal 210.
  • the Short ID message 252 includes the Short ID 220 with the source portion 224 and the destination portion 222. As discussed above, each portion can be considered to be a Local ID of the respective remote terminal. Although other messages can be used, an example of a suitable Short ID message 252 is a RRCReconfigurationCompleteSidelink message.
  • the relay terminal 204 After the PC5-RRC connection of the last hop 216 is established, the relay terminal 204 also transmits a Short ID message 254 to the remote destination terminal 212 that includes the Short ID 220.
  • the Short ID message is an PC5-RRC message that includes at least the source portion 224, the destination portion 222 and the source ProSe UE ID of the remote source terminal 210.
  • the source ProSe UE ID is the L2ID of the remote source terminal 210 and the Short ID message 254 is a RRCReconfigurationSidelink message.
  • the Short ID is applied to the SRAP layer by the relay terminal 204 and each remote terminal 210, 212 includes the Short ID in the SRAP header for E2E transmissions.
  • FIG. 3 is a block diagram of an example of a UE device 300 suitable for use as each of the terminal devices 204, 206, 210, 212.
  • the UE device 300 is any wireless communication device such as a mobile phone, a transceiver modem, a personal digital assistant (PDA), a tablet, or a smartphone.
  • the UE device 300 is a machine type communication (MTC) communication device or Internet-of-Things (IOT) device.
  • MTC machine type communication
  • IOT Internet-of-Things
  • the UE device 300 therefore is any fixed, mobile, or portable equipment that performs the functions described herein.
  • the various functions and operations of the blocks described with reference to UE device 300 may be implemented in any number of devices, circuits, or elements. Two or more of the functional blocks may be integrated in a single device, and the functions described as performed in any single device may be implemented over several devices.
  • the UE device 300 includes at least electronics 302, a transmitter 304 and a receiver 306.
  • the electronics 302 include any combination of hardware, software, and/or firmware for communicating with and controlling other UE device components to execute the functions described herein as well as facilitating the overall functionality of a communication device.
  • An example of suitable electronics 302 includes code running on a microprocessor or processor arrangement connected to memory 310.
  • the transmitter 304 includes electronics configured to transmit wireless signals. In some situations, the transmitter 304 may include multiple transmitters.
  • the receiver 306 includes electronics configured to receive wireless signals. In some situations, the receiver 306 may include multiple receivers.
  • the receiver 306 and transmitter 304 receive and transmit signals, respectively, through antenna 308.
  • the antenna 308 may include separate transmit and receive antennas. In some circumstances, the antenna 308 may include multiple transmit and receive antennas.
  • the transmitter 304 and receiver 306 in the example of FIG. 3 perform radio frequency (RF) processing including modulation and demodulation.
  • the receiver 306, therefore, may include components such as low noise amplifiers (LNAs) and filters.
  • the transmitter 304 may include filters and amplifiers.
  • Other components may include isolators, matching circuits, and other RF components. These components in combination or cooperation with other components perform the communication device functions. The required components may depend on the particular functionality required by the communication device.
  • the transmitter 304 includes a modulator (not shown), and the receiver 306 includes a demodulator (not shown).
  • the modulator can apply any one of a plurality of modulation orders to modulate the signals to be transmitted as part of the uplink signals.
  • the demodulator demodulates the downlink signals in accordance with one of a plurality of modulation orders.
  • the UE device 300 is capable of transmitting and receiving sidelink signals to and from other UE devices as well as communicating with base stations.
  • the electronics 302, in conjunction with the receiver 306, measure an evaluate signals transmitted by other devices, such as base stations and UE devices.
  • the electronics 302 and the receiver 306, therefore, can receive, measure, and evaluate downlink reference signals transmitted by a base station.
  • Signal measurements and evaluations can be stored in the memory 310.
  • the electronics 302 and receiver 306 can also receive, measure and evaluate discovery signals transmitted by nearby UE devices to generate a neighbor list that includes neighbor UE devices within the maximum distance.
  • the neighbor list is stored in the memory 310 and may be transmitted to a base station.
  • FIG. 4 is a flow chart of an example of method of managing Short IDs for an E2E PC5 communication link performed at a relay terminal.
  • the method may be performed in a system such the system 200 discussed herein.
  • the method is performed by a relay terminal such as the relay terminal 204.
  • the method may be performed using any of several techniques involving any combination of software, hardware, and firmware.
  • software code running on electronics including a processor, computer or other processor arrangement within the remote terminal device may facilitate the reception of signals, measurements, and transmissions.
  • One or more of the steps may be omitted, combined, performed in parallel, or performed in a different order than that described herein or shown in FIG. 4.
  • additional steps may be added that are not explicitly described in connection with the example discussed with reference to FIG. 4.
  • the relay terminal provides relay service to the establish and maintain an E2E PC5 communication link between the remote source terminal and the remote destination terminal.
  • a Short ID assignment request message is received from a previous relay terminal.
  • a previous relay terminal is a relay terminal facilitating the E2E PC5 link 202 that is closer to the remote source terminal 210 than the relay terminal receiving the Short ID assignment request message. Therefore, for examples that include two relay terminals such as described in reference to FIG. 2B and FIG. 2C, the first relay terminal 206 is a previous relay terminal from the perspective of the last relay terminal 204. The last relay terminal 204 is a next relay terminal from the perspective of the first relay terminal 206.
  • the Short ID assignment request message at least includes an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212, such as the L2ID of the remote destination terminal 212.
  • the Short ID assignment request message is a PC5-RRC message for the example.
  • the relay terminal determines whether the egress hop is to the remote destination terminal 212. Therefore, the relay terminal determines if the relay terminal is the last relay terminal to the remote destination terminal in the link 202 or if the egress hop is to another relay terminal. If the egress hop is directly to the remote destination terminal 212, the method proceeds to step 408. Otherwise, the method continues at step 410.
  • the relay terminal sends a Short ID assignment request message to the next relay terminal.
  • the Short ID assignment request message at least includes an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212, such as the L2ID of the remote destination terminal 212.
  • the Short ID assignment request message is a PC5-RRC message for the example.
  • a Short ID message is received from the next relay terminal where the Short ID message includes the Short ID that has been assigned by the last relay terminal.
  • the Short ID message is a PC5-RRC message that includes at least the source ProSe UE ID (e.g., L2ID of remote source terminal) and both portions 222, 224 of the Short ID 220.
  • the relay terminal transmits a Short ID message including the Short ID to the previous relay terminal.
  • the Short ID message is a PC5-RRC message that includes at least the destination ProSe UE ID (e.g., L2ID of remote destination terminal) and both portions 222, 224 of the Short ID 220 in the example.
  • the relay terminal applies the Short ID to the SRAP for the E2E PC5 communication link.
  • the relay terminal selects the destination portion 222 and the source portion 224 of the Short ID 220.
  • the relay terminal may select the destination portion 222 and the source portion 224 by sequentially selecting unused Local IDs.
  • the relay terminal transmits a Short ID message including the Short ID to the remote destination terminal 212.
  • the Short ID message is an RRCReconfigurationSidelink message that includes at least both portions 222, 224 of the Short ID and source ProSe UE ID, such as the L2ID of the remote source terminal 210.
  • the method continues at step 416 where the relay terminal applies the Short ID to the SRAP.
  • FIG. 5 is a flow chart of an example of a method of managing Short IDs for an E2E PC5 communication link performed at a relay terminal.
  • the method may be performed in a system such the system 200 discussed herein.
  • the method is performed by a first relay terminal 206 connected to the remote source terminal over a PC5 first hop 218.
  • the method may be performed using any of several techniques involving any combination of software, hardware, and firmware.
  • software code running on electronics including a processor, computer or other processor arrangement within the remote terminal device may facilitate the reception of signals, measurements, and transmissions.
  • One or more of the steps may be omitted, combined, performed in parallel, or performed in a different order than that described herein or shown in FIG. 5.
  • additional steps may be added that are not explicitly described in connection with the example discussed with reference to FIG. 5.
  • the relay terminal provides relay service to the establish and maintain an E2E PC5 communication link between the remote source terminal and the remote destination terminal.
  • a Short ID request message is received from the remote source terminal.
  • the Short ID request message at least includes an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212, such as the L2ID of the remote destination terminal 212.
  • the Short ID assignment request message is an RRCReconfigurationSidelink message for the example.
  • the relay terminal selects source portion 224 of the Short ID 220.
  • the relay terminal selects a source portion 224 of the Short ID for the remote source terminal by identifying the next unused Local ID of a sequence of Local IDs.
  • the source portion therefore, can be viewed as a Local ID of the remote source terminal.
  • the relay terminal transmits a Short ID message including the source portion 224 of the Short ID 220 to the remote source terminal 210.
  • the relay terminal transmits an RRCReconfigurationCompleteSidelink message including the source portion 224 (source Local ID) to the remote source terminal 210.
  • the relay terminal determines whether the egress hop is to the remote destination terminal 212. Therefore, the relay terminal determines if the relay terminal is the last relay terminal to the remote destination terminal in the link 202 or if the egress hop is to another relay terminal. If the egress hop is directly to the remote destination terminal 212, the method proceeds to step 512. Otherwise, the method continues at step 514.
  • the relay terminal sends a Short ID assignment request message to the next relay terminal.
  • the Short ID assignment request message at least includes an indication that a Short ID should be assigned and the destination ProSe UE ID of the remote destination terminal 212, such as the L2ID of the remote destination terminal 212.
  • the Short ID assignment request message is a PC5-RRC message for the example.
  • a Short ID message is received from the next relay terminal where the Short ID message includes the destination portion 222 (destination Local ID) that has been assigned by the last relay terminal.
  • the Short ID message is a PC5-RRC message that includes at least the destination ProSe UE ID (e.g., L2ID of remote destination terminal) and the destination portion 222 of the Short
  • the relay terminal transmits a Short ID message including the Short ID to the remote source terminal 210.
  • the Short ID message is an RRCReconfigurationCompleteSidelink message that includes at least the destination ProSe UE ID (e.g., L2ID of remote destination terminal) and the destination Local ID (destination portion 222 of the Short ID 220) in the example.
  • the destination ProSe UE ID e.g., L2ID of remote destination terminal
  • the destination Local ID destination portion 222 of the Short ID 220
  • the relay terminal applies the Short ID to the SRAP for the E2E PC5 communication link.
  • the relay terminal selects the destination portion 222 of the Short ID 220 and generates the Short ID 220 by combing the source portion 224 selected by the remote source terminal 210 with the destination portion 222.
  • the relay terminal transmits a Short ID message including the Short ID to the remote destination terminal 212.
  • the Short ID message is an RRCReconfigurationSidelink message that includes at least both portions 222, 224 of the Short ID and source ProSe UE ID, such as the L2ID of the remote source terminal 210.
  • the method continues at step 520 where the relay terminal applies the Short ID to the SRAP.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, electronics, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
  • Computer readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the methods and apparatus of this invention may take the form, at least partially, of program logic or program code (i.e., instructions) embodied in tangible media, such as a machine-readable storage medium.
  • program code When the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
  • the methods and apparatus of the present invention may also be embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission.
  • the program code When the program code is received and loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
  • the program code When implemented on a general-purpose processor, the program code combines with the processor to provide a unique apparatus that operates analogously to specific logic circuits.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller. Therefore, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un terminal relais fournit au moins une partie d'une liaison de communication PCS de bout en bout (E2E) entre un terminal source distant et un terminal de destination distant, le terminal relais comprenant une connexion PC5-RRC au terminal de destination distant. Le terminal relais sélectionne au moins une partie d'un ID court pour un protocole d'adaptation de relais de liaison latérale (SRAP) pour une communication sur la liaison de communication PCS E2E, l'ID court étant plus court qu'un ID d'UE ProSe source du terminal source distant et étant plus court que l'ID d'UE ProSe de destination du terminal de destination distant. Le terminal relais transmet un message de notification d'ID court identifiant l'ID court au terminal de destination distant et applique l'ID court au SRAP pour une communication sur la liaison de communication PCS E2E.
PCT/US2024/046089 2023-09-28 2024-09-11 Gestion d'id court à l'aide de pc5-rrc pour un protocole d'adaptation de relais de liaison latérale u2u (srap) Pending WO2025071922A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363541204P 2023-09-28 2023-09-28
US63/541,204 2023-09-28

Publications (1)

Publication Number Publication Date
WO2025071922A1 true WO2025071922A1 (fr) 2025-04-03

Family

ID=95202167

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/046089 Pending WO2025071922A1 (fr) 2023-09-28 2024-09-11 Gestion d'id court à l'aide de pc5-rrc pour un protocole d'adaptation de relais de liaison latérale u2u (srap)

Country Status (1)

Country Link
WO (1) WO2025071922A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200337096A1 (en) * 2018-08-03 2020-10-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods, User Equipment and Base Station for Sidelink Identification

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200337096A1 (en) * 2018-08-03 2020-10-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods, User Equipment and Base Station for Sidelink Identification

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HAO XU, CATT: "Discussion on U2U Relay", 3GPP DRAFT; R2-2307551; TYPE DISCUSSION; NR_SL_RELAY_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Toulouse, FR; 20230821 - 20230825, 11 August 2023 (2023-08-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052443262 *
JIANHUA LIU, QUALCOMM INCORPORATED: "Common part and Layer-2 specific part on U2U Relay", 3GPP DRAFT; R2-2307742; TYPE DISCUSSION; NR_SL_RELAY_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Toulouse, FR; 20230821 - 20230825, 11 August 2023 (2023-08-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052443453 *
NAVEEN PALLE, APPLE: "Discussion on remaining issues on UE-to-UE Relay", 3GPP DRAFT; R2-2307855; TYPE DISCUSSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Toulouse, FR; 20230821 - 20230825, 11 August 2023 (2023-08-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052443566 *
SUNGCHEOL CHANG, ETRI: "Discussion on Adaptation Layer for L2 U2U Relay", 3GPP DRAFT; R2-2308611; TYPE DISCUSSION; NR_SL_RELAY_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Toulouse, FR; 20230821 - 20230825, 11 August 2023 (2023-08-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052444305 *

Similar Documents

Publication Publication Date Title
US12328779B2 (en) Methods and apparatus for sidelink relay channel establishment
WO2021139771A1 (fr) Configuration de liaison latérale et transfert de trafic pour relais de couche 2 ue à ue
US9124510B2 (en) Configuring relay cell identities in cellular networks
US9510372B2 (en) Method and apparatus for establishing device-to-device connection in wireless communication system
US20240306229A1 (en) Transmission of coverage indicator with relay capability by relay user equipment (ue) devices
US20160302181A1 (en) Mobile communication system, radio communication apparatus, network apparatus, and radio terminal
CN111567127A (zh) 终端设备、基站设备和方法
US20240284545A1 (en) Path switch to indirect communication through relay ue device in rrc connection state other than rrc connected
US20170332417A1 (en) Random Access Procedure and Burst Transmission in a High Frequency System
US20140140286A1 (en) Method of direct communication by terminal
US20240064588A1 (en) Base station, and communication control method
WO2025042620A1 (fr) Gestion d'id court sélectionné par un relais pour un protocole d'adaptation de relais de liaison latérale (srap) u2u
WO2021136379A1 (fr) Filtrage de paquets précoce pour découverte d'ue de liaison latérale
EP4171163A1 (fr) Procédés et appareil d'acquisition de si pour une opération de relais de liaison latérale
US20240259864A1 (en) Hybrid quality of service flow
WO2025071922A1 (fr) Gestion d'id court à l'aide de pc5-rrc pour un protocole d'adaptation de relais de liaison latérale u2u (srap)
WO2025042619A1 (fr) Gestion d'id court pour protocole d'adaptation de relais de liaison latérale (srap) u2u
CN120435907A (zh) 无线通信系统中人工智能网络管理模型的传输
CN115996445A (zh) 系统信息的获取方法和用户设备
CN120835347A (zh) 终端连接方法及装置
US20240171959A1 (en) Restricted relay selection procedure based on communication link quality thresholds
WO2025034550A1 (fr) Rapport de défaillance de liaison u2n à trajets multiples
US20240147506A1 (en) Dynamic sl resource allocation
US20250254599A1 (en) Systems and methods for device-to-device communications
WO2025137827A1 (fr) Systèmes et procédés de transfert d'informations pour systèmes de relais

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24873305

Country of ref document: EP

Kind code of ref document: A1