WO2024210552A2 - Procédé et dispositif de gestion de connexion de bout en bout configurée par l'intermédiaire d'un relais de terminal dans un système de communication sans fil - Google Patents

Procédé et dispositif de gestion de connexion de bout en bout configurée par l'intermédiaire d'un relais de terminal dans un système de communication sans fil Download PDF

Info

Publication number
WO2024210552A2
WO2024210552A2 PCT/KR2024/004398 KR2024004398W WO2024210552A2 WO 2024210552 A2 WO2024210552 A2 WO 2024210552A2 KR 2024004398 W KR2024004398 W KR 2024004398W WO 2024210552 A2 WO2024210552 A2 WO 2024210552A2
Authority
WO
WIPO (PCT)
Prior art keywords
relay
connection
sidelink
terminal
srb
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.)
Ceased
Application number
PCT/KR2024/004398
Other languages
English (en)
Korean (ko)
Other versions
WO2024210552A3 (fr
Inventor
강현정
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.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to CN202480035824.4A priority Critical patent/CN121220178A/zh
Publication of WO2024210552A2 publication Critical patent/WO2024210552A2/fr
Publication of WO2024210552A3 publication Critical patent/WO2024210552A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • 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

  • the present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for establishing an end-to-end connection with another terminal based on a sidelink with a relay terminal in a wireless communication system and managing the end-to-end connection.
  • 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave), such as 28GHz and 39GHz ('Above 6GHz').
  • mmWave millimeter wave
  • mmWave millimeter wave
  • 28GHz and 39GHz 'Above 6GHz'
  • 6G mobile communication technology which is called the system after 5G communication (Beyond 5G)
  • implementation in the terahertz band for example, the 3 terahertz (3THz) band at 95GHz
  • 3THz the 3 terahertz
  • eMBB enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low-Latency Communications
  • mMTC massive Machine-Type Communications
  • beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves
  • numerologies such as operation of multiple subcarrier intervals
  • dynamic operation of slot formats for efficient use of ultra-high frequency resources
  • initial access technology to support multi-beam transmission and wideband
  • definition and operation of BWP Bitth Part
  • new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information
  • L2 pre-processing L2 Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
  • V2X Vehicle-to-Everything
  • NR-U New Radio Unlicensed
  • UE Power Saving NR terminal low power consumption technology
  • NTN Non-Terrestrial Network
  • Standardization of wireless interface architecture/protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) to provide nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step RACH for NR to simplify random access procedures is also in progress, and standardization of system architecture/services for 5G baseline architecture (e.g. Service based Architecture, Service based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.
  • 5G baseline architecture e.g. Service based Architecture, Service based Interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • An embodiment of the present disclosure seeks to provide a device and method capable of effectively providing a service in a wireless communication system.
  • a method performed by a first UE in a wireless communication system may include the steps of identifying an expiration of a timer associated with an end-to-end (E2E) connection for sidelink communication with a second UE via a relay UE, or a failure of an integrity check of a sidelink (SL) signaling radio bearer (SRB) for the E2E connection, and discarding a sidelink relay adaption protocol (SRAP) configuration for the E2E connection.
  • E2E end-to-end
  • SRB sidelink signaling radio bearer
  • a device and method can be provided that can effectively provide a service and expand service coverage in a wireless communication system.
  • FIG. 1a is a diagram illustrating a wireless communication system according to one embodiment of the present disclosure.
  • FIG. 1b is a diagram illustrating a wireless communication system according to one embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating a configuration of a base station in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating a configuration of a terminal in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating the configuration of a communication unit in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 5 is a diagram illustrating a structure of time-frequency resources of a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 6 is a diagram illustrating a signal flow for managing a terminal connection between remote terminals in a wireless communication system that performs communication via a terminal relay according to one embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating a signal flow for managing a terminal connection between remote terminals in a wireless communication system that performs communication via a terminal relay according to one embodiment of the present disclosure.
  • FIG. 8 is a diagram illustrating a signal flow between a remote terminal and a terminal relay that manages a terminal-to-terminal connection in a wireless communication system that performs communication through a terminal relay according to one embodiment of the present disclosure.
  • each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. Since these computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement the function in a specific manner, the instructions stored in the computer-available or computer-readable memory can also produce a manufactured article including an instruction means for performing the functions described in the flow diagram block(s).
  • the computer program instructions may also be installed on a computer or other programmable data processing apparatus, a series of operational steps may be performed on the computer or other programmable data processing apparatus to produce a computer-executable process, so that the instructions executing the computer or other programmable data processing apparatus may also provide steps for executing the functions described in the flowchart block(s).
  • each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a particular logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending on the functionality they perform.
  • the term ' ⁇ part' used in the present embodiment means a software or hardware component such as an FPGA or ASIC, and the ' ⁇ part' performs certain roles.
  • the ' ⁇ part' is not limited to software or hardware.
  • the ' ⁇ part' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors.
  • the ' ⁇ part' includes components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.
  • the functions provided in the components and ' ⁇ parts' may be combined into a smaller number of components and ' ⁇ parts' or further separated into additional components and ' ⁇ parts'. Additionally, the components and ' ⁇ parts' may be implemented to regenerate one or more CPUs within the device or secure multimedia card.
  • the main targets are the New RAN (NR) radio access network and the packet core (5G system, or 5G core network, or NG Core: next generation core) core network on the 5G mobile communication standard specified by the 3GPP, a mobile communication standard standardization organization.
  • NR New RAN
  • 5G system or 5G core network, or NG Core: next generation core
  • 5G mobile communication standard specified by the 3GPP, a mobile communication standard standardization organization.
  • the main gist of the present disclosure can be applied to other communication systems having a similar technical background with slight modifications without significantly departing from the scope of the present disclosure, and this will be possible at the discretion of a person having technical knowledge skilled in the technical field of the present disclosure.
  • a network data collection and analysis function which is a network function that provides a function for analyzing and providing data collected from a 5G network to support network automation
  • NWDAF may collect, store, and/or analyze information from a 5G network and provide the results to an unspecified network function (NF).
  • the analysis results may be independently utilized by each NF.
  • 3GPP 3rd generation partnership project long term evolution
  • 5G Fifth Generation Partnership Project
  • NR Long Term Evolution
  • LTE Long Term Evolution
  • present disclosure is not limited to the terms and names and may be equally applied to systems that comply with other standards.
  • the present disclosure relates to a method and device for managing a PC5 termination connection established between two remote terminals when a terminal is connected to another terminal through a sidelink relay in a wireless communication system.
  • Embodiments of the present disclosure can expand service coverage, increase reliability of data transmission and reception, and minimize or reduce battery usage of a terminal by allowing a terminal to transmit and receive data/signaling with another terminal through a sidelink relay.
  • the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (base station), a wireless access unit, a base station controller, or a node on a network.
  • the terminal may include a UE (user equipment), an MS (mobile station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function.
  • eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as an eNB may represent a gNB.
  • the term terminal may represent various wireless communication devices as well as mobile phones, NB-IoT (internet of things) devices, and sensors.
  • PDSCH physical downlink shared channel
  • PDSCH physical downlink shared channel
  • PDSCH may also be used to refer to data. That is, in the present disclosure, the expression 'transmitting a physical channel' may be interpreted equivalently to the expression 'transmitting data or a signal through a physical channel'.
  • upper signaling means a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer.
  • Upper signaling can be understood as RRC (radio resource control) signaling or MAC (media access control) control element (CE).
  • the present disclosure states that in a wireless communication system, when a terminal is connected to another terminal through a sidelink relay, the terminal, the other terminal, and the sidelink relay may be in an RRC_CONNECTED state, an RRC_INACTIVE state, an RRC_IDLE state, and an OUT-OF-COVERAGE state from a network perspective, and the states of each terminal including the sidelink relay may be operated independently.
  • the terminal, the other terminal, and the sidelink relay may be connected to the same cell, different cells, the same base station, or different base stations, respectively.
  • V2X vehicle-to-everything
  • the present disclosure for solving the above-mentioned problem relates to a method and device for handling a problem situation of a terminal connection established by two remote terminals in a system for relaying and transmitting data or signaling between terminals (i.e., two remote terminals) based on a sidelink with a relay terminal in a wireless communication system.
  • the problem situation of the terminal connection established by two remote terminals may include at least one of a case in which a transmitting terminal transmits a PC5 RRC message (RRCReconfigurationSidelink message) for configuration and establishment of the terminal connection and does not receive a PC5 RRC response message (RRCReconfigurationCompleteSidelink message) from a receiving terminal for a set time (e.g., T400 timer), and a case in which integrity protection of a PDCP (packet data convergence protocol) PDU (protocol data unit) corresponding to data or signaling transmitted by the transmitting terminal to the receiving terminal fails to be protected.
  • PDCP packet data convergence protocol
  • PDU protocol data unit
  • FIG. 1A of the present disclosure illustrates only one base station
  • the wireless communication system may further include other base stations that are identical or similar to the base station (110), and may further include more relays (or relay UEs). That is, the configuration of the wireless communication system of FIG. 1A is exemplary, and may further include other components (e.g., base stations, UEs, servers) that are not illustrated in FIG. 1A.
  • each of the terminal (130) and the terminal (140) may be referred to or referred to by other terms other than the term 'terminal', such as 'user equipment (UE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' or 'user device,' or other terms having equivalent technical meanings thereto.
  • UE 'user equipment
  • UE mobile station
  • 'subscriber station ' remote terminal
  • ' 'wireless terminal ' or 'user device
  • FIG. 1b is a diagram illustrating a wireless communication system according to one embodiment of the present disclosure.
  • FIG. 1b illustrates a wireless communication system (or mobile communication system) that includes terminals (150, 170) and a sidelink relay (160) that can relay data transmission and reception between terminals as part of nodes using a wireless channel.
  • the sidelink relay (160) may be a U2U (UE to UE) relay.
  • the wireless communication system is not limited to the above-described example. That is, the configuration of the wireless communication system of FIG. 1b is an example, and may further include other components not illustrated in FIG. 1b.
  • each of the terminal (150) and the terminal (170) is a device or apparatus used by a user, which may perform direct communication via a wireless channel or may perform communication with an opposing terminal via a wireless channel with the relay (160).
  • a link between the terminal (150) and the terminal (170), a link between the terminal (150) and the relay (160), and a link between the terminal (170) and the relay (160) may be referred to as a side link, and the side link may also be referred to as a PC5 interface.
  • the Uu interface may be referred to as an interface between a UE and a base station (e.g., an eNoB or gNB), and PC-5 may be referred to as a communication technology for vehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X) and/or device-to-device (D2D) data transmission.
  • V2V vehicle-to-vehicle
  • V2X vehicle-to-everything
  • D2D device-to-device
  • the first antenna port and the second antenna port may be in a QCL relationship or may be evaluated to be in a QCL relationship if large-scale characteristics of a channel carrying symbols on the first antenna port can be inferred from a channel carrying symbols on the second antenna port (in case that).
  • the large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, or a spatial receiver parameter.
  • the terminal (130), the terminal (140), the terminal (150), and/or the terminal (170) illustrated in FIG. 1a and/or FIG. 1b may support vehicular communication.
  • vehicular communication in the LTE system, standardization work on V2X (vehicle to everything) technology based on a device-to-device (D2D) architecture was completed in 3GPP Release 14 and Release 15, and standardization work on V2X technology based on 5G NR was completed in 3GPP Release 16.
  • NR V2X may support unicast communication, groupcast (or multicast) communication, and/or broadcast communication between terminals.
  • NR V2X aims to provide more advanced services such as platooning, advanced driving, extended sensor, and remote driving.
  • V2X services can be divided into basic safety services and advanced services.
  • the basic safety services may include detailed services of vehicle notification (cooperative awareness messages (CAM) or basic safety message (BSM)) services, left turn notification services, forward collision warning services, emergency vehicle approach notification services, forward obstacle warning services, and/or intersection signal information services.
  • V2X information may be transmitted and received using broadcast, unicast, or groupcast transmission methods.
  • Advanced services not only have stronger quality of service (QoS) requirements than the basic safety services, but also require a method for transmitting and receiving V2X information using unicast and groupcast transmission methods in addition to broadcast so that V2X information can be transmitted and received within a specific vehicle group or between two vehicles.
  • Advanced services may include detailed services of platooning services, autonomous driving services, remote driving services, and/or extended sensor-based V2X services.
  • NR V2X can provide public safety services by supporting direct communication services between terminals in areas without network infrastructure.
  • sidelink may be referred to as a transmission/reception path for signals between terminals or a transmission/reception path for signals between terminals and relays.
  • Sidelink may be used interchangeably with the PC5 interface.
  • the base station below is an entity that performs resource allocation of terminals and relays, and may be a base station that supports both V2X communication and general cellular communication, or a base station that supports only V2X communication.
  • the base station may be referred to as an NR base station (e.g., gNB), an LTE base station (e.g., eNB), or an RSU (road site unit).
  • a terminal may include not only a general user equipment, a mobile station, but also a vehicle supporting vehicular-to-vehicular (V2V) communication, a vehicle or pedestrian handset (e.g., a smart phone) supporting vehicular-to-pedestrian (V2P) communication, a vehicle supporting vehicular-to-network (V2N) communication, or a vehicle supporting vehicular-to-infrastructure (V2I) communication, and an RSU equipped with a terminal function, an RSU equipped with a base station function, or an RSU equipped with a part of a base station function and a part of a terminal function.
  • V2V vehicle supporting vehicular-to-vehicular
  • V2P vehicle or pedestrian handset
  • V2N vehicle supporting vehicular-to-network
  • V2I vehicle supporting vehicular-to-infrastructure
  • a terminal may be referred to as a vehicle supporting vehicular-to-vehicular (V2V) communication, a vehicle or a pedestrian's handset (e.g., a smartphone) supporting vehicular-to-pedestrian (V2P) communication, a vehicle supporting vehicular-to-network (V2N) communication, or a vehicle supporting vehicular-to-infrastructure (V2I) communication.
  • V2V vehicle supporting vehicular-to-vehicular
  • V2P vehicular-to-pedestrian
  • V2N vehicle supporting vehicular-to-network
  • V2I vehicle supporting vehicular-to-infrastructure
  • a terminal may be referred to as a user device supporting device-to-device communication of a public safety network.
  • a terminal may be referred to as an RSU (road side unit) equipped with a terminal function, an RSU equipped with a base station function, or an RSU equipped with a part of a base station function and a part of a terminal function.
  • RSU road side unit
  • a relay may be referred to as a user device that supports V2X communication between vehicles or devices of a public safety network.
  • a relay may be referred to as a device equipped with a terminal function, a device equipped with a base station function, or a device equipped with a part of a terminal function and a part of a base station function.
  • FIG. 2 is a diagram illustrating a configuration of a base station in a wireless communication system according to an embodiment of the present disclosure.
  • the configuration illustrated in Fig. 2 can be understood as the configuration of a base station (110).
  • Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware or software, or a combination of hardware and software.
  • a base station (110) may include a wireless communication unit (210), a backhaul communication unit (220), a storage unit (230), and/or a control unit (240).
  • the components of the base station (110) are not limited to the examples described above.
  • the base station (110) may include more or fewer components than the components described above.
  • the wireless communication unit (210), the backhaul communication unit (220), the storage unit (230), and the control unit (240) may be implemented in the form of a single chip.
  • the control unit (240) may include one or more processors.
  • the base station (110) may include a transceiver and a controller coupled with the transceiver.
  • the base station (110) may include at least one transceiver and at least one processor coupled with the at least one transceiver.
  • the base station (110) may include a memory storing instructions to be executed by the controller, a transceiver, and a controller.
  • the wireless communication unit (210) may perform functions for transmitting and/or receiving signals through a wireless channel.
  • the wireless communication unit (210) may perform a conversion function between a baseband signal and a bit stream according to a physical layer specification of the system.
  • the wireless communication unit (210) may generate complex symbols by encoding and modulating a transmission bit stream.
  • the wireless communication unit (210) may restore a reception bit stream by demodulating and decoding a baseband signal.
  • the wireless communication unit (210) may be replaced with a transceiver, a receiver, and/or a transmitter.
  • the wireless communication unit (210) may up-convert a baseband signal into an RF (radio frequency) band signal and transmit the same through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal.
  • the wireless communication unit (210) may include an RFIC (radio frequency integrated circuit).
  • the wireless communication unit (210) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), and/or an analog to digital convertor (ADC).
  • the wireless communication unit (210) may include a plurality of transmit/receive paths. Furthermore, the wireless communication unit (210) may include at least one antenna array composed of a plurality of antenna elements. For example, at least one antenna array may include at least one antenna element.
  • the wireless communication unit (210) may be composed of a digital unit and an analog unit.
  • the analog unit may be implemented or composed of a plurality of sub-units depending on operating power, and/or operating frequency, etc.
  • the digital unit may be implemented or composed of at least one processor (e.g., a digital signal processor (DSP)).
  • DSP digital signal processor
  • the expressions may be composed or may be implemented may be replaced with the expression may include.
  • the analog unit may include a plurality of sub-units depending on operating power, and/or operating frequency, etc.
  • the digital unit may include at least one processor.
  • the wireless communication unit (210) transmits and/or receives an RF (radio frequency) signal.
  • the wireless communication unit (210) may be referred to as a 'transmitter', a 'receiver', or a 'transceiver'.
  • transmission and reception performed through a wireless channel are used to mean that the processing described above is performed by the wireless communication unit (210).
  • the backhaul communication unit (220) may provide an interface for performing communication with other nodes within the network.
  • the backhaul communication unit (220) may convert a bit string transmitted from the base station (110) to another node, such as another access node, another base station, an upper node, a core network, etc., into a physical signal.
  • the backhaul communication unit (220) may convert a physical signal received from another node into a bit string.
  • the storage (230) can store data for basic programs, applications, and/or setting information for the operation of the base station (110).
  • the storage (230) can be composed of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory.
  • the storage (230) can provide stored data upon request of the control unit (240).
  • control unit (240) can control the overall operations of the base station (110).
  • the control unit (240) can transmit and/or receive a signal through the wireless communication unit (210) or through the backhaul communication unit (220).
  • the control unit (240) can record and read data in the storage unit (230).
  • the control unit (240) can perform functions of a protocol stack required by a communication standard.
  • the protocol stack may be included in the wireless communication unit (210).
  • the control unit (240) may include at least one processor.
  • the control unit (240) may control the base station (110) to perform operations according to the embodiments described below.
  • FIG. 3 is a diagram illustrating a configuration of a terminal in a wireless communication system according to an embodiment of the present disclosure.
  • Fig. 3 can be understood as the configuration of a terminal (120).
  • Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware or software, or a combination of hardware and software.
  • a terminal (120) may include a communication unit (310), a storage unit (320), and/or a control unit (330).
  • the components of the terminal (120) are not limited to the examples described above.
  • the terminal (120) may include more or fewer components than the components described above.
  • the communication unit (310), the storage unit (320), and the control unit (330) may be implemented in the form of a single chip.
  • the control unit (330) may include one or more processors.
  • the terminal (120) may include a transceiver and a controller coupled with the transceiver.
  • the terminal (120) may include at least one transceiver and at least one processor coupled with the at least one transceiver.
  • the terminal (120) may include a memory storing instructions to be executed by the controller, a transceiver, and a controller.
  • the communication unit (310) performs functions for transmitting and/or receiving signals via a wireless channel.
  • the communication unit (310) may perform a function of converting between a baseband signal and a bit stream according to a physical layer specification of the system.
  • the communication unit (310) may generate complex symbols by encoding and modulating a transmission bit stream.
  • the communication unit (310) may restore a reception bit stream by demodulating and decoding a baseband signal.
  • the communication unit (310) may up-convert a baseband signal into an RF band signal and then transmit it through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal.
  • the communication unit (310) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and/or an ADC.
  • the communication unit (310) may include at least one RFIC, at least one intermediate frequency integrated circuit (IFIC), and/or at least one communication processor (CP).
  • IFIC intermediate frequency integrated circuit
  • CP communication processor
  • the communication unit (310) may include a plurality of transmit/receive paths.
  • the communication unit (310) may include at least one antenna array composed of a plurality of antenna elements.
  • the communication unit (310) may be composed of digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFIC)).
  • the digital circuits and analog circuits may be implemented in one package.
  • the communication unit (310) may include a plurality of RF chains.
  • the communication unit (310) may perform beamforming.
  • the communication unit (310) may transmit and/or receive RF signals. Accordingly, all or part of the communication unit (310) may be referred to or referred to as a 'transmitter', a 'receiver', or a 'transmitter-receiver'.
  • transmission and reception performed through a wireless channel may be used to mean that the processing described above is performed by the communication unit (310).
  • the storage unit (320) can store data such as basic programs, application programs, and setting information for the operation of the terminal (120).
  • the storage unit (320) can be composed of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory.
  • the storage unit (320) can provide stored data according to a request from the control unit (330).
  • control unit (330) controls the overall operations of the terminal (120).
  • the operations of the terminal (120) described in FIGS. 1 to 8 below can be substantially understood as operations of the controller (330).
  • control unit (330) can transmit and/or receive signals through the communication unit (310).
  • control unit (330) can record and read data in the storage unit (320).
  • control unit (330) can perform functions of a protocol stack required by a communication standard.
  • control unit (330) may include at least one processor or microprocessor, or the control unit (330) may be a part of a processor.
  • a part of the communication unit (310) and the control unit (330) may be referred to as a CP (communication processor).
  • the control unit (330) may control the terminal (120) to perform operations according to one embodiment described below.
  • FIG. 4 is a diagram illustrating the configuration of a communication unit in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 4 illustrates an exemplary configuration of the wireless communication unit (210) of FIG. 2 or the communication unit (310) of FIG. 3.
  • FIG. 4 illustrates components for performing beamforming as part of the wireless communication unit (210) of FIG. 2 or the communication unit (310) of FIG. 3.
  • a wireless communication unit (210) or a communication unit (310) may include an encoding and modulation unit (402), a digital beamforming unit (404), a plurality of transmission paths (406-1 to 406-N), and/or an analog beamforming unit (408).
  • the encoding and modulation unit (402) can perform channel encoding.
  • channel encoding at least one of a low density parity check (LDPC) code, a convolution code, or a polar code can be used.
  • LDPC low density parity check
  • the encoding and modulation unit (402) can generate modulation symbols by performing constellation mapping.
  • the digital beamforming unit (404) may perform beamforming on a digital signal (e.g., modulation symbols). For example, the digital beamforming unit (404) may multiply the modulation symbols by beamforming weights. The beamforming weights are used to change the magnitude and phase of a signal and may be referred to as a 'precoding matrix' or a 'precoder'.
  • the digital beamforming unit (404) may output digital beamformed modulation symbols to a plurality of transmission paths (406-1 to 406-N).
  • the modulation symbols may be multiplexed or the same modulation symbols may be provided to a plurality of transmission paths (406-1 to 406-N).
  • the plurality of transmission paths (406-1 to 406-N) can convert digital beamformed digital signals into analog signals.
  • each of the plurality of transmission paths (406-1 to 406-N) can include an inverse fast fourier transform (IFFT) operation unit, a cyclic prefix (CP) insertion unit, a DAC, and/or an up-conversion unit.
  • the CP insertion unit is for an orthogonal frequency division multiplexing (OFDM) scheme and can be excluded when another physical layer scheme (e.g., filter bank multi-carrier (FBMC)) is applied. That is, the plurality of transmission paths (406-1 to 406-N) can provide independent signal processing processes for a plurality of streams generated through digital beamforming.
  • some of the components of the plurality of transmission paths (406-1 to 406-N) can be used in common.
  • the analog beamforming unit (408) can perform beamforming on an analog signal.
  • the digital beamforming unit (404) can multiply the analog signals by beamforming weights.
  • the beamforming weights can be used to change the magnitude and phase of the signal.
  • the analog beamforming unit (440) can be configured in various ways depending on the connection structure between the plurality of transmission paths (406-1 to 406-N) and the antennas.
  • each of the plurality of transmission paths (406-1 to 406-N) can be connected to one antenna array.
  • the plurality of transmission paths (406-1 to 406-N) can be connected to one antenna array.
  • the plurality of transmission paths (406-1 to 406-N) can be adaptively connected to one antenna array or to two or more antenna arrays.
  • FIG. 5 is a diagram illustrating a structure of time-frequency resources of a wireless communication system according to an embodiment of the present disclosure.
  • the horizontal axis represents the time domain
  • the vertical axis represents the frequency domain.
  • the minimum transmission unit in the time domain is an OFDM symbol or a DFT-S-OFDM symbol
  • N symb OFDM symbols or DFT-S-OFDM symbols (530) can be included in one slot (505).
  • the length of a subframe in an NR system can be defined as 1.0 ms
  • the length of a radio frame (500) can be defined as 10 ms.
  • the minimum transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system transmission bandwidth can include a total of N BW subcarriers (525). Specific values such as N symb and N BW can be variably applied depending on the system.
  • a basic unit of a time-frequency resource domain is a resource element (RE) (510), which may be indicated by an OFDM symbol index or a DFT-S-OFDM symbol index and a subcarrier index.
  • a resource block (RB (515)) may be defined as N RB consecutive subcarriers (520) in the frequency domain.
  • the time-frequency resource structure as in Fig. 5 can be applied to the Uu interface.
  • the time-frequency resource structure as in Fig. 5 can be applied substantially identically or similarly to the side link (or, PC-5).
  • a terminal e.g., a Remote UE or a remote terminal
  • a sidelink relay also referred to as a Relay or Relay UE or a terminal relay
  • operation procedures of the terminal, the sidelink relay, and the other terminal for managing the end-to-end PC5 connection established between the two terminals are described.
  • a sidelink relay may be authenticated to be used for at least one or a combination of a specific service, a specific terminal, a specific sidelink flow, a specific sidelink bearer, a specific unicast link, a specific source identifier, or a specific destination identifier.
  • the sidelink relay may configure or establish a direct connection with an authenticated terminal at the time of installation.
  • the sidelink relay according to an embodiment of the present disclosure may configure or establish a sidelink direct connection with an authenticated terminal upon receiving a Relay discovery message from an authenticated terminal.
  • the sidelink relay may configure or establish a sidelink direct connection with an authenticated terminal upon receiving a Relay discovery message as a response to a Relay discovery message transmitted by the sidelink relay itself from the authenticated terminal.
  • a method in which a “connection instruction via relay” is included in a PC5 direct link establishment request message for a PC5 direct link establishment request used by a sidelink relay and a terminal for relay connection a method in which a “PC5 direct link establishment message for relay use” is defined separately in the PC5 direct link establishment request message, and/or a method in which a general PC5 direct link establishment request message transmitted in a sidelink radio bearer (which may be expressed as SLRB) for relay use is used can be utilized.
  • SLRB sidelink radio bearer
  • a remote terminal and a sidelink relay that manage an end-to-end unicast connection established between two terminals is described, taking as an example the case where a T400 timer expires when exchanging a PC5 RRC message between two remote terminals in the PC5-RRC layer of the end-to-end unicast connection between the two remote terminals and the case where an integrity protection failure occurs in the PC5-PDCP layer.
  • FIG. 6 describes a procedure in which an end-to-end sidelink unicast connection setup between a terminal and another terminal is managed based on the expiration of a T400 timer through a sidelink relay in case that a direct connection is established between a terminal and another terminal through a sidelink relay and signaling and data are transmitted and/or received.
  • the T400 timer may be a waiting time until a terminal transmits a PC5 RRC message (e.g., RRCReconfigurationSidelink message) including configuration information for end-to-end sidelink unicast connection setup with another terminal through a sidelink relay and receives a PC5 RRC message (e.g., RRCReconfigurationCompleteSidelink message or RRCReconfigurationFailureSidelink message) corresponding to a response message to the PC5 RRC message from another terminal through the sidelink relay.
  • a PC5 RRC message e.g., RRCReconfigurationSidelink message
  • RRCReconfigurationCompleteSidelink message or RRCReconfigurationFailureSidelink message e.g., RRCReconfigurationCompleteSidelink message or RRCReconfigurationFailureSidelink message
  • timer used to manage the end-to-end sidelink unicast connection in various embodiments of the present disclosure is described as the T400 timer, this is only an example.
  • a separate timer e.g., T400-indirect
  • T400-indirect timer may be defined to have a different value from the T400 timer for PC5 RRC message exchange for establishing an end-to-end sidelink unicast connection between terminals through a sidelink relay, and of course, a separate timer (e.g., T400-indirect timer) may be applied to the end-to-end sidelink unicast connection between two remote terminals.
  • the T400 timer may be used for the sidelink unicast connection between each remote terminal and the sidelink relay.
  • FIG. 6 is a diagram illustrating a signal flow for managing a terminal connection between remote terminals in a wireless communication system that performs communication via a terminal relay according to one embodiment of the present disclosure.
  • UE1 (600) may determine whether to perform, configure or establish a direct connection with UE2 (650), UE1 (600) may decide to search for a sidelink relay (630) that can support the direct connection with UE2 (650), and UE1 (600) may perform a Relay discovery procedure.
  • the Relay discovery procedure may also include a case where UE2 (650) searches for a sidelink relay (630) that can support the direct connection with UE1 (600).
  • the Relay discovery procedure may be a procedure where UE1 (600) or UE2 (650) transmits a relay discovery message to search for a sidelink relay (630) that can support the direct connection.
  • the relay discovery procedure may correspond to a procedure in which UE1 (600) or UE2 (650) monitors a relay discovery message transmitted by the sidelink relay (630) to receive a relay discovery message from the sidelink relay (630) that can support direct connection with the counterpart terminal.
  • the Relay discovery message may be a standalone message containing information about sidelink relay discovery, or may be a message integrated or comprised in a PC5 direct link establishment request message (e.g., Direct communication request message) that UE1 (600) transmits to establish a direct connection with UE2 (650).
  • a PC5 direct link establishment request message e.g., Direct communication request message
  • the sidelink relay (630) may perform a unicast connection procedure with UE2 (650), which corresponds to the counterpart remote terminal of UE1 (600), at step 602 (PC5 unicast connection establishment).
  • UE2 (650) determines that it can establish a direct connection with UE1 (600) through the sidelink relay (630)
  • it may perform a unicast connection procedure with the sidelink relay (630) at step 602.
  • the SLRB configuration for transmitting and receiving user traffic i.e., the configuration for the SL-DRB (data radio bearer) may be omitted in steps 601 and 602.
  • UE1 (600) and UE2 (650) may establish an end-to-end unicast connection (E2E (end-to-end) PC5 unicast connection established) in step 603 separately from the unicast connection (steps 601 and 602) with the sidelink relay (630).
  • E2E end-to-end unicast connection
  • the end-to-end unicast connection may be initiated from a procedure in which UE1 (600) transmits a Direct communication request message to UE2 (650) through relay transmission of the sidelink relay (630).
  • UE1 (600) or UE2 (650) uses a PC5 direct link establishment request message (e.g., Direct communication request message) transmission procedure as a procedure for searching for a sidelink relay (630) that can support connection with UE2 (650)
  • some of the signaling messages e.g., PC5-S (signaling) signaling message, PC5-RRC message
  • PC5-S (signaling) signaling message, PC5-RRC message may be transmitted during the relay search procedure for the sidelink relay (630), and some of the signaling messages may be transmitted after the relay search procedure for the sidelink relay (630).
  • an E2E SLRB (sidelink radio bearer) configuration for an end-to-end unicast connection between UE1 (600) and UE2 (650) may include configuration information applicable to signaling (SL-SRB) and/or configuration information applicable to user traffic (SL-DRB) transmitted through an end-to-end unicast connection between UE1 (600) and UE2 (650) connected via a sidelink relay (630).
  • the E2E SLRB configuration may be acquired by a source remote terminal and provided to a counterpart remote terminal.
  • the E2E SLRB configuration may be acquired by a sidelink relay and provided to a source remote terminal/destination remote terminal.
  • the E2E SLRB configuration information may be configured based on QoS (quality of service) information of signaling or user traffic transmitted and received between UE1 (600) and UE2 (650).
  • QoS quality of service
  • an E2E SLRB configuration can be configured that is mapped to information such as a QoS profile and a PQI (PC5 QoS identifier).
  • information included in the E2E SLRB configuration can include SL-SDAP (service data adaptation protocol) entity configuration information of a data bearer corresponding to user traffic, and/or SL-PDCP entity configuration information.
  • information included in the E2E SLRB configuration can include SL-PDCP entity configuration information in addition to the SL-RRC entity of a signaling bearer corresponding to signaling.
  • a HbH (Hop-by-Hop) SLRB configuration applied to each of the link between UE1 (600) and the sidelink relay (630) and the link between the sidelink relay (630) and UE2 (650) may include setting information applied to each link when signaling (SL-SRB) or user traffic (SL-DRB) transmitted through the end-to-end unicast connection between UE1 (600) and UE2 (650) is transmitted through the sidelink relay (630).
  • the HbH SLRB configuration may be acquired by a source remote terminal and provided to the sidelink relay and the destination remote terminal.
  • the HbH SLRB configuration can be acquired by a relay terminal and provided to a source remote terminal and a destination remote terminal, or can be acquired by each remote terminal and provided to a sidelink relay.
  • HbH SLRB configuration information may be configured based on QoS information of signaling or user traffic to be transmitted and received between UE1 (600) and UE2 (650).
  • QoS information of signaling or user traffic may be transmitted and received between UE1 (600) and UE2 (650).
  • SLRB configuration mapped to information such as QoS profile and PQI may be configured.
  • QoS information applied to HbH SLRB configuration setting may correspond to QoS that splits E2E QoS according to each link situation.
  • the operation of splitting E2E QoS into QoS of each link (or hop) may be performed by a source remote terminal or a relay terminal or a serving base station.
  • information included in the HbH SLRB configuration may include at least one or a combination of SL-SRAP (sidelink relay adaption protocol) entity configuration information, SL-RLC (radio link control) entity configuration information, SL-MAC entity configuration information, or SL-PHY entity configuration information of a data bearer corresponding to user traffic.
  • information included in the HbH SLRB configuration may include at least one or a combination of SL-SRAP entity configuration information, SL-RLC entity configuration information, SL-MAC entity configuration information, or SL-PHY entity configuration information of a signaling bearer corresponding to signaling.
  • information included in the HbH SLRB configuration corresponding to each link may include [Table 2].
  • information included in the HbH SLRB configuration corresponding to each link may include at least one of the information elements included in [Table 2].
  • an entity by protocol layer set for a unicast connection may be composed of an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer for a data bearer corresponding to user traffic.
  • An entity by protocol layer may be composed of an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer for a signaling bearer corresponding to signaling.
  • an entity by protocol layer set for an end-to-end unicast connection between UE1 (600) and UE2 (650) and an entity by protocol layer set for a unicast connection between UE1 (600) and a sidelink relay for relaying signaling and user traffic between UE1 (600) and UE2 (650) may be set separately.
  • the protocol layer entities established in the end-to-end unicast connection between UE1 (600) and UE2 (650) and the protocol layer entities established in the unicast connection between UE2 (650) and a sidelink relay for relaying signaling and user traffic between UE1 (600) and UE2 (650) can be established separately.
  • UE1 (600) may transmit an RRCReconfigurationSidelink message including PC5-RRC configuration information for end-to-end unicast connection to UE2 (650) at step 604 by using the relay of the sidelink relay (630) (RRCReconfigurationSidelink).
  • the RRCReconfigurationSidelink message at step 604 may correspond to a message for configuring a PC5-RRC entity during establishment of an end-to-end unicast connection between UE1 (600) and UE2 (650) or may correspond to a message for configuring a PC5-RRC entity after establishment of an end-to-end unicast connection between UE1 (600) and UE2 (650).
  • UE1 (600) may transmit an RRCReconfigurationSidelink message to UE2 (650) and start a T400 timer at step 605 (e.g., T400 started).
  • UE1 (600) may receive an RRCReconfigurationCompleteSidelink message or an RRCReconfigurationFailureSidelink message as a response message transmitted by UE2 (650) using the relay of the sidelink relay (630) before the T400 timer expires.
  • UE1 (600) may stop the T400 timer and process the response messages received from UE2 (650).
  • UE1 (600) may identify or check T400 timer expiration at step 606 (e.g., T400 expired). UE1 (600) may determine that it has not received a response message from UE2 (650) until the T400 timer expires, and UE1 (600) may perform end-to-end unicast connection management procedures due to T400 timer expiration for the end-to-end unicast connection at step 607 (UE1 peforms the procedures to handle E2E PC5 unicast connection problem due to T400 expiry). For example, UE1 (600) may perform PC5 RRC connection release procedures.
  • UE1 (600) may transmit a signaling message notifying that there is a problem with the end-to-end unicast connection. For example, UE1 (600) may delete configuration information configured for the end-to-end unicast connection. For example, UE1 (600) can perform a sidelink relay reselection procedure.
  • the operation performed by UE1 (600) at step 607 may include the examples of [Table 3].
  • the operation performed by UE1 (600) at step 607 may include at least one of the operations described in [Table 3].
  • the operation performed by UE1 (600) at step 607 for the PC5 unicast connection established with the sidelink relay may include the examples of [Table 4].
  • the operation performed for the PC5 unicast connection established with the sidelink relay may include at least one of the operations described in [Table 4].
  • the remote terminal can perform an end-to-end PC5 RRC connection release procedure with the remote terminal.
  • the remote terminal can send a signaling message to the sidelink relay to inform that a problem has occurred in the end-to-end unicast connection.
  • This signaling message can be sent through the PC5-RRC message or the PC5-S signaling message of the PC5 unicast established between the remote terminal and the sidelink relay, and can provide information such as E2E PC5 RRC connection failure notification (or E2E PC5 RRC connection release notification).
  • a remote terminal can release/delete a PC5-RRC entity and configuration information, a PC5-SDAP entity and configuration information, and/or a PC5-PDCP entity and configuration information that are configured for an end-to-end unicast connection with a counterpart remote terminal.
  • a remote terminal can delete relay configuration information for a counterpart remote terminal (e.g., configuration information of an SRAP entity for the counterpart remote terminal, PC5-Relay RLC channel information for the counterpart remote terminal, etc.).
  • Remote terminals (source remote terminal, destination remote terminal) can perform a sidelink relay reselection procedure.
  • the remote terminal When a remote terminal performs an end-to-end unicast connection release with another remote terminal and it is determined that signaling and user traffic transmission/reception with another remote terminal no longer need to be performed using the relay transmission of the sidelink relay, that is, when it is determined that the sidelink unicast connection for the purpose of relay transmission between the remote terminal and the sidelink relay does not need to be maintained, the remote terminal can perform a sidelink unicast connection release procedure for the purpose of relay transmission with the sidelink relay.
  • the sidelink unicast connection release procedure for the purpose of relay transmission between the remote terminal and the sidelink relay can be triggered by the remote terminal or the sidelink relay.
  • the sidelink unicast disconnection procedure for relay transmission purposes between a remote terminal and a sidelink relay may include the following examples: If the PC5-RRC connection with the U2U relay UE is determined to be released (corresponding to the operation of the remote UE) (or if the PC5-RRC connection with the U2U Remote UE is determined to be released (corresponding to the operation of the sidelink relay)), the UE (remote UE or sidelink relay) indicates upper layers to trigger PC5 unicast link release.
  • the UE (remote terminal or sidelink relay) shall: /In the procedure below, specific destination corresponds to the sidelink relay from the perspective of the remote terminal, and to the remote terminal from the perspective of the sidelink relay.
  • a DRB may be established, so in this case, an operation to release the established DRB is performed.
  • 2> release the SRBs of this destination release the PDCP entity, RLC entity and the logical channel of the sidelink SRB for PC5-RRC message of the specific destination
  • This operation can be handled by the procedure in [Table 3] or the procedure in [Table 5].
  • the remote terminal can notify the sidelink relay of the disconnection of the end-to-end PC5 unicast connection, etc.
  • the sidelink relay can perform an operation for processing the notification of disconnection of the end-to-end PC5 unicast connection between the two remote terminals. This will be described in detail later in FIG. 8.
  • FIG. 7 is a diagram illustrating a signal flow for managing a terminal connection between remote terminals in a wireless communication system that performs communication via a terminal relay according to one embodiment of the present disclosure.
  • UE1 (700) may determine or identify whether it can perform a direct connection with UE2 (750).
  • UE1 (700) may decide to search for a sidelink relay (730) that can support a direct connection with UE2 (750).
  • UE1 (700) may perform a Relay discovery procedure.
  • the Relay discovery procedure may also include a case where UE2 (750) searches for a sidelink relay (730) that can support a direct connection with UE1 (700).
  • the Relay discovery procedure may be a procedure where UE1 (700) or UE2 (750) transmits a relay discovery message to search for a sidelink relay (730) that can support a direct connection.
  • the relay discovery procedure may correspond to a procedure in which UE1 (700) or UE2 (750) monitors a relay discovery message transmitted by the sidelink relay (730) to receive a relay discovery message from the sidelink relay (730) that can support direct connection with the counterpart terminal.
  • the Relay discovery message may include a standalone message containing information about sidelink relay discovery.
  • the Relay discovery message may be a message integrated into a PC5 direct link establishment request message (e.g., Direct communication request message) transmitted by UE1 (700) to establish a direct connection with UE2 (750).
  • a PC5 direct link establishment request message e.g., Direct communication request message
  • UE1 (700) may select a sidelink relay (730) that is determined to support direct connection with UE2 (750), and UE1 (700) may perform a unicast connection procedure with the sidelink relay (730) in step 701 (PC5 unicast connection established). For example, UE1 (700) may establish a unicast connection with the sidelink relay (730).
  • the sidelink relay (730) may perform a unicast connection procedure with UE2 (750), which corresponds to the counterpart remote terminal of UE1 (700), in step 702 (PC5 unicast connection established). For example, if UE2 (750) determines that it can establish a direct connection with UE1 (700) through the sidelink relay (730), it may perform a unicast connection procedure with the sidelink relay (730) in step 702.
  • SLRB configuration for user traffic transmission and reception i.e., configuration for SL-DRB, may be omitted in steps 701 and 702.
  • SLRBs (SL-SRB0, SL-SRB1, SL-SRB2, SL-SRB3) for sidelink signaling transmitted and received in the unicast connection establishment procedure between UE1 (700) and the sidelink relay (730) in steps 701 and 702 may have the specified SLRB settings applied.
  • SLRBs (SL-SRB0, SL-SRB1, SL-SRB2, SL-SRB3) for sidelink signaling transmitted and received in the unicast connection establishment procedure between UE2 (750) and the sidelink relay (730) may have the specified SLRB settings applied.
  • UE1 (700) and UE2 (750) can set up or establish an end-to-end unicast connection (E2E PC5 unicast connection established) in step 703 separately from the unicast connection (steps 701 and 702) with the sidelink relay (730).
  • E2E PC5 unicast connection established E2E PC5 unicast connection established
  • an end-to-end unicast connection may start with a procedure in which UE1 (700) transmits a Direct communication request message to UE2 (750) through relay transmission of a sidelink relay (730).
  • UE1 (700) and UE2 (750) may perform a PC5 security procedure for processing sidelink authentication and encryption key setup through relay transmission of the sidelink relay (730).
  • the end-to-end PC5 security procedure of UE1 (700) and UE2 (750) may be configured as a procedure for exchanging encryption and integrity protection algorithms and parameters to support integrity protection and encryption (integrity, verification, ciphering) to be applied to PDCP PDUs in a PDCP entity for end-to-end data or signaling (PC5-S signaling, PC5-RRC) of UE1 (700) and UE2 (750).
  • PC5-S signaling PC5-RRC
  • an E2E SLRB (sidelink radio bearer) configuration for an end-to-end unicast connection between UE1 (700) and UE2 (750) may include configuration information applied to signaling (SL-SRB) or user traffic (SL-DRB) transmitted through an end-to-end unicast connection between UE1 (700) and UE2 (750) connected via a sidelink relay (730).
  • SL-SRB signaling
  • SL-DRB user traffic
  • the E2E SLRB configuration may be acquired by a source remote terminal and provided to a counterpart remote terminal.
  • the E2E SLRB configuration may be acquired by a sidelink relay and provided to a source remote terminal/destination remote terminal.
  • E2E SLRB configuration setting information may be configured based on QoS information of signaling or user traffic transmitted and received between UE1 (700) and UE2 (750).
  • E2E SLRB configuration mapped to information such as QoS profile and PQI may be configured.
  • information included in E2E SLRB configuration may include SL-SDAP entity setting information of data bearer corresponding to user traffic and/or SL-PDCP entity setting information.
  • information included in E2E SLRB configuration may include SL-PDCP entity setting information in addition to SL-RRC entity of signaling bearer corresponding to signaling.
  • information included in an E2E SLRB configuration corresponding to an end-to-end unicast connection between UE1 (700) and UE2 (750) may include [Table 1].
  • information included in the E2E SLRB configuration may include at least one of the information elements described in [Table 1].
  • the HbH SLRB configuration may be acquired by a source remote terminal and provided to the sidelink relay and the destination remote terminal.
  • the HbH SLRB configuration can be acquired by a relay terminal and provided to a source remote terminal and a destination remote terminal, or each remote terminal can acquire it and provide it to a sidelink relay.
  • HbH SLRB configuration setting information may be configured based on QoS information of signaling or user traffic to be transmitted and received between UE1 (700) and UE2 (750).
  • QoS information of signaling or user traffic may be transmitted and received between UE1 (700) and UE2 (750).
  • an SLRB configuration mapped to information such as QoS profile and PQI may be configured.
  • QoS information applied to HbH SLRB configuration setting may correspond to QoS that splits E2E QoS according to each link situation.
  • the operation of splitting E2E QoS into QoS of each link (or hop) may be performed by a source remote terminal or a relay terminal or a serving base station.
  • information included in an HbH SLRB configuration may include at least one or a combination of SL-SRAP entity configuration information, SL-RLC entity configuration information, SL-MAC entity configuration information, or SL-PHY entity configuration information of a data bearer corresponding to user traffic.
  • information included in an HbH SLRB configuration may include at least one or a combination of SL-SRAP entity configuration information, SL-RLC entity configuration information, SL-MAC entity configuration information, or SL-PHY entity configuration information of a signaling bearer corresponding to signaling.
  • a protocol layer entity set for a unicast connection may be configured with an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, and/or a PHY layer for a data bearer corresponding to user traffic.
  • a protocol layer entity set for a unicast connection may be configured with an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and/or a PHY layer for a signaling bearer corresponding to signaling.
  • a protocol layer entity set for an end-to-end unicast connection between UE1 (700) and UE2 (750) and a protocol layer entity set for a unicast connection between UE1 (700) and a sidelink relay for relaying signaling and user traffic between UE1 (700) and UE2 (750) may be set separately.
  • the protocol layer entities established in the end-to-end unicast connection between UE1 (700) and UE2 (750) and the protocol layer entities established in the unicast connection between UE2 (750) and a sidelink relay for relaying signaling and user traffic between UE1 (700) and UE2 (750) can be established separately.
  • UE1 (700) when UE1 (700) identifies or determines an integrity protection failure for a PC5-PDCP (packet data convergence protocol) PDU (protocol data unit) received from UE2 (750) by using the relay of the sidelink relay (730), UE1 (700) may perform an end-to-end unicast connection management procedure with UE2 (750) at step 705 (UE1 peforms the procedures to handle E2E PC5 unicast connection problem due to integrity check failure detection by PDCP entity).
  • PC5-PDCP packet data convergence protocol
  • PDU protocol data unit
  • an end-to-end unicast connection management procedure when performing an end-to-end unicast connection management procedure when determining or identifying an integrity protection failure for a PC5-PDCP PDU corresponding to an end-to-end unicast connection between UE1 (700) and UE2 (750), it may actually correspond to an integrity protection failure for a PC5-PDCP PDU of a signaling bearer (e.g., SL-SRB2 and SL-SRB3) during the end-to-end unicast connection.
  • a signaling bearer e.g., SL-SRB2 and SL-SRB3
  • an integrity protection failure when an integrity protection failure is determined for a PC5-PDCP PDU corresponding to an end-to-end unicast connection between UE1 (700) and UE2 (750), in the case where an end-to-end unicast connection management procedure is performed, it may correspond to an integrity protection failure for at least one PC5-PDCP PDU of a signaling bearer or a data bearer during the end-to-end unicast connection.
  • the remote terminal can notify the sidelink relay of the disconnection of the end-to-end PC5 unicast connection, etc.
  • the sidelink relay can perform an operation for processing the notification of disconnection of the end-to-end PC5 unicast connection between the two remote terminals. This will be described with reference to FIG. 8.
  • FIG. 8 is a diagram illustrating a signal flow between a remote terminal and a terminal relay that manages a terminal-to-terminal connection in a wireless communication system that performs communication through a terminal relay according to one embodiment of the present disclosure.
  • the remote terminal (800) may transmit a signaling message notifying the occurrence of a problem in the end-to-end PC5 unicast connection to the sidelink relay (830) (or, relay UE_) at step 802 (E2E PC5 connection problem notification).
  • the transmitted signaling message may be delivered through a PC5-RRC message or a PC5-S signaling message corresponding to the PC5 unicast connection established between the remote terminal (800) and the sidelink relay (830).
  • the message transmitted at step 802 may include at least one or a combination of information such as identification information for the end-to-end PC5 unicast connection (e.g., layer-2 ID of the counterpart remote terminal, local ID of the counterpart remote terminal used by the SRAP entity, etc.), end-to-end PC5 unicast connection release notification, or end-to-end PC5 unicast connection failure notification.
  • identification information for the end-to-end PC5 unicast connection e.g., layer-2 ID of the counterpart remote terminal, local ID of the counterpart remote terminal used by the SRAP entity, etc.
  • end-to-end PC5 unicast connection release notification e.g., end-to-end PC5 unicast connection release notification
  • end-to-end PC5 unicast connection failure notification e.g., end-to-end PC5 unicast connection failure notification.
  • the remote terminal (800) may perform the procedures to handle E2E PC5 unicast connection problem at step 803.
  • An embodiment of the operations performed by the remote terminal (800) at step 803 may include [Table 3].
  • the operations performed by the remote terminal (800) at step 803 may include at least one of the operations described in [Table 3].
  • an example of an operation performed by the remote terminal (800) in step 803 may include [Table 4].
  • the operation performed by the remote terminal (800) in step 803 may include at least one of the operations described in [Table 4].
  • the sidelink relay (830) may perform, at step 804, an operation of handling an end-to-end PC5 unicast connection release (or failure) notification of two remote terminals based on the information of step 802 (Relay UE performs the procedures to handle E2E PC5 unicast connection problem notification).
  • An embodiment of the operation performed by the sidelink relay (830) at step 804 may include [Table 5].
  • the operation performed by the sidelink relay (830) at step 804 may include at least one of the operations described in [Table 5].
  • an embodiment of the operation performed in step 804 may include [Table 6].
  • the operation performed by the sidelink relay (830) in step 804 may include at least one of the operations described in [Table 6].
  • a sidelink relay may perform a procedure to delete configuration information of an SRAP entity configured for relaying signaling and user traffic corresponding to a signaling bearer and data bearer between two remote terminals.
  • the configuration information of a SRAP entity may include, for example, at least one or a combination of an SRAP context for a destination remote terminal of an end-to-end PC5 unicast connection, or PC5 Relay RLC channels for a destination remote terminal of an end-to-end PC5 unicast connection.
  • a sidelink relay may perform a procedure to release the SRAP entity established for a remote terminal when it no longer needs to support relay transmissions for that remote terminal.
  • the PC5-S layer entity of the remote terminal may notify the PC5-RRC layer entity or the PC5-PDCP layer entity of the remote terminal of the occurrence of the problem in the end-to-end unicast connection.
  • the PC5-RRC layer entity or the PC5-PDCP layer entity may notify the sidelink relay of the occurrence of the problem in the end-to-end unicast connection as in various embodiments proposed in the present invention.
  • Each remote terminal may perform an operation when a problem occurs in the end-to-end unicast connection.
  • the sidelink relay may perform an operation when it is instructed to perform a problem in the end-to-end unicast connection. If deemed necessary, the remote terminal may perform an operation of reselecting a sidelink relay that can relay signaling and user traffic between the two remote terminals.
  • the source remote terminal or the destination remote terminal or the sidelink relay may determine that a sidelink radio link failure has occurred for the link on which the problem occurred for the PC5 unicast connection, and may trigger a sidelink relay reselection procedure.
  • an example of operations performed by a remote terminal and a sidelink relay when a problem occurs in a PC5 unicast connection between the sidelink relay and the remote terminal is as shown in [Table 7].
  • the UE shall: 1> upon indication from sidelink RLC entity that the maximum number of retransmissions for a specific destination has been reached; or 1> upon T400 expiry for a specific destination; or 1> upon indication from MAC entity that the maximum number of consecutive HARQ DTX for a specific destination has been reached; or 1> upon integrity check failure indication from sidelink PDCP entity concerning SL-SRB2 or SL-SRB3 for a specific destination: 2> consider sidelink radio link failure to be detected for this destination; 2
  • a release procedure can be performed.
  • Information about entities and contexts to be released/deleted can include, for example, information in [Table 2]); 2> discard the NR sidelink communication related configuration of this destination; 2> reset the sidelink specific MAC of this destination; 2> consider the PC5-RRC connection is released for the destination; 2> indicate the release of the PC5-RRC connection to the upper layers for this destination (ie PC5 is unavailable); 2> if UE is in RRC_CONNECTED: 3> perform the sidelink UE information for NR sidelink communication procedure; 2> if UE is acting as L2 U2U Remote UE: 3> release the RRC, PDCP, SDAP for its peer Remote UE (This is an example of an operation to release an end-to-end PC5 unicast connection with a remote terminal that is establishing an end-to-end PC5 unicast connection with the remote terminal) 3> perform relay UE reselection procedure for its peer Remote UE (A procedure for reselect
  • a computer-readable storage medium storing one or more programs (software modules) may be provided.
  • the one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors in an electronic device.
  • the one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.
  • These programs may be stored in a random access memory, a non-volatile memory including a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, a magnetic cassette. Or, they may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • CD-ROM compact disc-ROM
  • DVDs digital versatile discs
  • each configuration memory may be included in multiple numbers.
  • the program may be stored in an attachable storage device that is accessible via a communications network, such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof.
  • the storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communications network may be connected to the device performing an embodiment of the present disclosure.
  • the components included in the disclosure are expressed in the singular or plural form depending on the specific embodiment presented.
  • the singular or plural expressions are selected to suit the presented situation for the convenience of explanation, and the present disclosure is not limited to the singular or plural components, and even if a component is expressed in the plural form, it may be composed of the singular form, or even if a component is expressed in the singular form, it may be composed of the plural form.

Landscapes

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

Abstract

La présente divulgation se rapporte à un système de communication 5G ou 6G permettant de prendre en charge des débits de transmission de données supérieurs. Ce procédé, effectué par un premier UE dans un système de communication sans fil, peut comprendre les étapes consistant à : identifier soit l'expiration d'un temporisateur associé à une connexion de bout en bout (E2E) pour une communication de liaison latérale avec un second UE par l'intermédiaire d'un UE relais, soit la défaillance d'un contrôle d'intégrité d'un SRB SL pour la connexion E2E ; et supprimer un réglage de SRAP pour la connexion E2E.
PCT/KR2024/004398 2023-04-06 2024-04-04 Procédé et dispositif de gestion de connexion de bout en bout configurée par l'intermédiaire d'un relais de terminal dans un système de communication sans fil Ceased WO2024210552A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202480035824.4A CN121220178A (zh) 2023-04-06 2024-04-04 用于在无线通信系统中管理通过终端中继配置的端到端连接的方法和设备

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020230045536A KR20240149672A (ko) 2023-04-06 2023-04-06 무선 통신 시스템에서 단말 릴레이를 통해 설정된 종단간 연결을 관리하는 방법 및 장치
KR10-2023-0045536 2023-04-06

Publications (2)

Publication Number Publication Date
WO2024210552A2 true WO2024210552A2 (fr) 2024-10-10
WO2024210552A3 WO2024210552A3 (fr) 2025-06-26

Family

ID=92972285

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/004398 Ceased WO2024210552A2 (fr) 2023-04-06 2024-04-04 Procédé et dispositif de gestion de connexion de bout en bout configurée par l'intermédiaire d'un relais de terminal dans un système de communication sans fil

Country Status (3)

Country Link
KR (1) KR20240149672A (fr)
CN (1) CN121220178A (fr)
WO (1) WO2024210552A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4681755A1 (fr) 2024-07-19 2026-01-21 Air Liquide Medical Systems Appareil de ventilation à électrovanne proportionnelle à ouverture contrôlée

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4681755A1 (fr) 2024-07-19 2026-01-21 Air Liquide Medical Systems Appareil de ventilation à électrovanne proportionnelle à ouverture contrôlée

Also Published As

Publication number Publication date
WO2024210552A3 (fr) 2025-06-26
KR20240149672A (ko) 2024-10-15
CN121220178A (zh) 2025-12-26

Similar Documents

Publication Publication Date Title
WO2022158807A1 (fr) Procédé et dispositif de gestion de la mobilité d'un mode de connexion d'un terminal distant par l'intermédiaire d'un terminal de relais dans un système de communication sans fil
WO2023121214A1 (fr) Procédé et dispositif de prise en charge de commande de configuration de qos pour liaison latérale dans un système de communication sans fil
WO2022235117A1 (fr) Procédé et appareil de prise en charge d'acquisition d'informations de système par un terminal distant de liaison latérale sur un relais de liaison latérale
WO2023121198A1 (fr) Procédé et appareil pour prendre en charge une opération de commutation de chemin d'un ue à distance sur une liaison latérale dans un système de communication sans fil
WO2024112004A1 (fr) Procédé et appareil pour améliorer un rétablissement rrc à l'aide d'une mobilité de couche inférieure dans un système de communication mobile de prochaine génération
WO2023090855A1 (fr) Procédé et système d'auto-optimisation de canal d'accès aléatoire dans un système de communication sans fil
WO2021066538A1 (fr) Procédé et appareil permettant de traiter une distribution en désordre pour une couche pdcp dans un système de communication d2d sans fil
WO2024210552A2 (fr) Procédé et dispositif de gestion de connexion de bout en bout configurée par l'intermédiaire d'un relais de terminal dans un système de communication sans fil
WO2024232711A1 (fr) Procédé et appareil de configuration d'une priorité d'un signal de référence de positionnement de liaison latérale dans un système de communication sans fil
WO2024210401A1 (fr) Procédé et appareil d'émission-réception d'informations de capacité d'ue associées à un positionnement de liaison latérale dans un système de communication sans fil
WO2024019396A1 (fr) Procédé et appareil de connexion initiale pour répéteur commandé par réseau dans un système de communication mobile de prochaine génération
WO2021066421A1 (fr) Procédé et dispositif pour effectuer une communication entre terminaux dans un système de communication sans fil
WO2024091066A1 (fr) Procédé et appareil de traitement d'intégrité d'un paquet d'ue distant émis par l'intermédiaire d'un relais d'ue dans un système de communication sans fil
WO2023229314A1 (fr) Procédé et appareil pour optimiser un accès aléatoire dans un système de communication sans fil
WO2025014277A1 (fr) Procédé et appareil pour configurer et prendre en charge diverses versions pdcp dans une architecture ran divisée dans un système de communication
WO2023234693A1 (fr) Procédé et appareil pour une opération lors d'une détection de rlf dans une sl-ca
WO2023204576A1 (fr) Dispositif et procédé permettant de prendre en charge une découverte de relais de liaison latérale dans un système de communication sans fil
WO2025234754A1 (fr) Procédé et appareil d'accès sans fil basé sur l'absence de contention pour dispositif ido ambiant dans un système de communication mobile de prochaine génération
WO2026084341A1 (fr) Procédé et appareil de demande de répétition automatique sur la base d'informations de couche inférieure dans un système de communication mobile de prochaine génération
WO2025211769A1 (fr) Procédé et dispositif de prise en charge de communication de l'ido ambiant dans un système de communication mobile de prochaine génération
WO2025033865A1 (fr) Procédé et appareil associés à la mesure de qoe dans un système de communication sans fil
WO2024019505A1 (fr) Procédé et dispositif de gestion de communication de relais par l'intermédiaire d'un terminal de relais entre deux terminaux distants dans un système de communication sans fil
WO2026095750A1 (fr) Procédé et appareil pour prendre en charge une pluralité de supports pour un service à faible latence d'un flux de qos dans un système de communication sans fil
WO2025100810A1 (fr) Procédé et appareil d'optimisation de transfert intercellulaire dans un système de communication sans fil
WO2023075494A1 (fr) Procédé et dispositif pour améliorer la sécurité dans une couche dans un système de communication mobile de nouvelle génération

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: 24785252

Country of ref document: EP

Kind code of ref document: A2

WWE Wipo information: entry into national phase

Ref document number: 202517095801

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202517095801

Country of ref document: IN

122 Ep: pct application non-entry in european phase

Ref document number: 24785252

Country of ref document: EP

Kind code of ref document: A2