Method and device for performing communication in wireless communication system
The method and apparatus address the challenge of managing carrier selection and QoS flows in wireless communication systems by using advanced technologies to optimize data transmission and reception, ensuring efficient communication services that meet the demands of future wireless communication systems like 6G.
Patent Information
- Application Number
- PCT/KR2024/006345
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-08-10
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-14
AI Technical Summary
Current wireless communication systems, particularly in the context of 5G and future 6G, face challenges in efficiently managing carrier selection and quality of service (QoS) flows to ensure optimal data transmission and reception, especially in scenarios requiring high data rates, low latency, and energy efficiency across a vast number of connected devices.
The proposed method and apparatus involve a device capable of obtaining and processing information about multiple carriers, acquiring packets based on QoS flows, and performing transmission or reception by selecting appropriate carriers, with the ability to trigger carrier reselection based on changes in QoS flows, utilizing advanced technologies such as AI, THz communication, and non-terrestrial networks to enhance communication efficiency.
This approach enables efficient communication services by optimizing carrier selection and QoS management, supporting high data rates, low latency, and energy efficiency, thereby meeting the stringent requirements of future wireless communication systems like 6G, including intelligent connectivity and ubiquitous coverage.
Smart Images

Figure KR2024006345_14112024_PF_FP_ABST
Abstract
Description
Method and device for performing communication in a wireless communication system
[0001] The present disclosure relates to a wireless communication system.
[0002] 5G NR, the successor to LTE (long-term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.
[0003] The 6G (wireless communication) system aims to achieve (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements as shown in Table 1 below. For example, Table 1 can represent an example of the requirements of a 6G system.
[0004] Per device peak data rate1 TbpsE2E latency1 msMaximum spectral efficiency100bps / HzMobility supportUp to 1000km / hrSatellite integrationFullyAIFullyAutonomous vehicleFullyXRFullyHaptic CommunicationFully
[0005] The present disclosure provides a device and method for effectively providing services in a wireless communication system. In particular, the present disclosure provides a method and device for communication.
[0006] In one embodiment, a method performed by a first device may be provided. The method may include: obtaining information about a plurality of carriers; obtaining a packet based on a quality of service (QoS) flow; and performing transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0007] In one embodiment, a first device configured to perform wireless communication may be provided. The first device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the first device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0008] In one embodiment, a processing device configured to control a first device may be provided. The processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, cause the first device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0009] In one embodiment, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. The instructions, when executed, may cause a first device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0010] In one embodiment, a method performed by a second device may be provided. The method may include: obtaining information about a plurality of carriers; obtaining a packet based on a quality of service (QoS) flow; and performing reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0011] In one embodiment, a second device configured to perform wireless communication may be provided. The second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, cause the second device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0012] In one embodiment, a processing device configured to control a second device may be provided. The processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, cause the second device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0013] In one embodiment, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. The instructions, when executed, may cause a second device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0014] The present disclosure can provide a device and method capable of effectively providing services in a wireless communication system. For example, communication can be performed efficiently through the embodiments proposed in the present disclosure.
[0015] FIG. 1 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.
[0016] FIG. 2 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.
[0017] FIG. 3 illustrates an example of a typical scenario of an NTN based on a transparent payload, according to one embodiment of the present disclosure.
[0018] FIG. 4 illustrates an example of a typical scenario of an NTN based on a regenerative payload, according to one embodiment of the present disclosure.
[0019] FIG. 5 illustrates an example of a sensing operation according to one embodiment of the present disclosure.
[0020] FIG. 6 illustrates a slot structure of a frame according to one embodiment of the present disclosure.
[0021] FIG. 7 illustrates an example of a BWP according to one embodiment of the present disclosure.
[0022] FIG. 8 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.
[0023] FIG. 9 illustrates an example of a wireless communication environment according to one embodiment of the present disclosure.
[0024] FIG. 10 illustrates a procedure for RLF detection according to one embodiment of the present disclosure.
[0025] FIG. 11 illustrates a procedure for RLF detection according to one embodiment of the present disclosure.
[0026] FIG. 12 illustrates a procedure for LBT detection according to one embodiment of the present disclosure.
[0027] FIG. 13 illustrates a procedure for beam failure detection according to an embodiment of the present disclosure.
[0028] FIG. 14 illustrates an example of a relationship between a QoS flow and a carrier according to an embodiment of the present disclosure.
[0029] FIG. 15 illustrates an example of a procedure for providing a QoS flow according to one embodiment of the present disclosure.
[0030] FIG. 16 illustrates an example of a procedure related to changing a QoS flow according to one embodiment of the present disclosure.
[0031] FIG. 17 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure.
[0032] FIG. 18 illustrates a method for a second device to perform wireless communication according to one embodiment of the present disclosure.
[0033] FIG. 19 illustrates a communication system (1) according to one embodiment of the present disclosure.
[0034] FIG. 20 illustrates a wireless device according to an embodiment of the present disclosure.
[0035] FIG. 21 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.
[0036] FIG. 22 illustrates a wireless device according to one embodiment of the present disclosure.
[0037] FIG. 23 illustrates a mobile device according to one embodiment of the present disclosure.
[0038] FIG. 24 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure.
[0039] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."
[0040] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."
[0041] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".
[0042] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”
[0043] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."
[0044] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.
[0045] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.
[0046] In this specification, higher layer parameters may be parameters that are set for the terminal, preset, or predefined. For example, a base station or network may transmit higher layer parameters to the terminal. For example, higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.
[0047] In this specification, "configured or defined" may be interpreted as being configured or preset to a device through predefined signaling (e.g., SIB, MAC, RRC) from a base station or network. In this specification, "configured or defined" may be interpreted as being preset to a device.
[0048] The technology proposed in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.
[0049] The technology proposed in this specification can be implemented with 6G wireless technology and applied to various 6G systems. For example, 6G systems can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.
[0050] FIG. 1 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 1 can be combined with various embodiments of the present disclosure.
[0051] New network characteristics in 6G may include:
[0052] - Satellite integrated network
[0053] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, upgrading the wireless evolution from "connected objects" to "connected intelligence." AI can be applied at every stage of the communication process (or at every signal processing step, as described below).
[0054] - Seamless integration of wireless information and energy transfer
[0055] - Ubiquitous super 3D connectivity: Access to networks and core network functions of drones and very low Earth orbit satellites will create super 3D connectivity in 6G ubiquitous.
[0056] Some general requirements for the new network characteristics of 6G, such as the above, may be as follows:
[0057] - small cell networks
[0058] - Ultra-dense heterogeneous network
[0059] - High-capacity backhaul
[0060] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communications is a key feature of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.
[0061] - Softwarization and virtualization
[0062] Below, the core implementation technologies of the 6G system are described.
[0063] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.
[0064] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by utilizing sub-THz communication with a wide bandwidth and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (Sub-THz band) is considered a major portion of the THz band for cellular communications. Adding the Sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF. Figure 2 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of FIG. 2 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.
[0065] - Large-scale MIMO technology
[0066] - Hologram beamforming (HBF)
[0067] - Optical wireless technology
[0068] - Free-space optical transmission backhaul network (FSO backhaul network)
[0069] - Quantum communication
[0070] - Cell-free communication
[0071] - Integration of wireless information and power transmission
[0072] - Integration of wireless communication and sensing
[0073] - Integrated access and backhaul network
[0074] - Big data analysis
[0075] - Reconfigurable intelligent surface
[0076] - metaverse
[0077] - Blockchain
[0078] Unmanned aerial vehicles (UAVs): UAVs, or drones, will be a key element in 6G wireless communications. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base stations (BSs) can be installed on UAVs to provide cellular connectivity. UAVs may offer specific capabilities not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled mobility. During emergencies such as natural disasters, deploying terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in wireless communications. This technology facilitates three fundamental requirements for wireless networks: enhanced mobile broadband (eMBB), URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.
[0079] - Advanced air mobility (AAM): AAM is a higher concept than urban air mobility (UAM), which is an air transportation method available in urban areas, and can refer to a means of transportation that includes movement between regional hubs as well as within urban areas.
[0080] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless communication. Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, in the future, autonomous driving will go beyond simply providing warnings or guidance messages to drivers and may require active intervention in vehicle operation and direct control of the vehicle in dangerous situations. To this end, the amount of information that needs to be transmitted and received may become enormous, so 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.
[0081] - Non-terrestrial networks (NTN): NTN may refer to a network or network segment that uses radio frequency (RF) resources mounted on a satellite (or unmanned aerial system (UAS) platform). FIG. 3 illustrates an example of a typical NTN scenario based on a transparent payload according to an embodiment of the present disclosure. FIG. 4 illustrates an example of a typical NTN scenario based on a regenerative payload according to an embodiment of the present disclosure. The embodiments of FIG. 3 or FIG. 4 may be combined with various embodiments of the present disclosure. Referring to FIG. 3, a satellite (or UAS platform) may create a service link with a UE. The satellite (or UAS platform) may be connected to a gateway via a feeder link. The satellite may be connected to a data network via the gateway. A beam footprint may refer to an area where a signal transmitted by a satellite can be received. Referring to Figure 4, a satellite (or UAS platform) can establish a service link with a UE. A satellite (or UAS platform) connected to a UE can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the playback payload, a satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between a satellite and another satellite, a feeder link between the satellite and the gateway may be required. Figures 3 and 4 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios.For example, a satellite (or UAS platform) may implement a transparent or regenerative (with onboard processing) payload. For example, a satellite (or UAS platform) may generate multiple beams over a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and minimum elevation angle. For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered. For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, a regenerative payload may be substantially equivalent to equipping the satellite (or UAS platform) with all or part of the base station functionality.
[0082] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a device to connect to the object through a network, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, i.e., a sensing operation, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing may provide an opportunity to enhance existing communication systems from a communication network to a wireless communication and sensing network. FIG. 5 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure. Specifically, FIG. 5 (a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 5 (b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).
[0083] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.
[0084] The physical layer provides information transmission services to higher layers using physical channels. The physical layer is connected to the upper layer, the Medium Access Control (MAC) layer, via a transport channel. Data travels between the MAC layer and the physical layer through the transport channel. Transport channels are classified based on how and with what characteristics data is transmitted over the wireless interface.
[0085] Data travels between different physical layers, i.e., between the physical layers of a transmitter and a receiver, via a physical channel. This physical channel can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.
[0086] The MAC layer provides services to the upper layer, the radio link control (RLC) layer, through logical channels. The MAC layer provides mapping from multiple logical channels to multiple transport channels. Furthermore, the MAC layer provides logical channel multiplexing, which maps multiple logical channels to a single transport channel. The MAC sublayer provides data transmission services on logical channels.
[0087] The RLC layer performs the concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). To guarantee the various Quality of Service (QoS) required by radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).
[0088] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transport channels, and physical channels, related to the configuration, reconfiguration, and release of radio bearers. RB refers to a logical path provided by Layer 1 (physical layer or PHY layer) and Layer 2 (MAC layer, RLC layer, Packet Data Convergence Protocol (PDCP) layer, and Service Data Adaptation Protocol (SDAP) layer) for data transmission between the terminal and the network.
[0089] The functions of the PDCP layer in the user plane include the transmission of user data, header compression, and ciphering. The functions of the PDCP layer in the control plane include the transmission of control plane data and encryption / integrity protection.
[0090] The Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane. It performs mapping between QoS flows and data radio bearers, marking QoS flow identifiers (IDs) within downlink and uplink packets, and more.
[0091] Establishing an RB refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. RBs can be further divided into two types: the Signaling Radio Bearer (SRB) and the Data Radio Bearer (DRB). The SRB is used as a channel to transmit RRC messages in the control plane, while the DRB is used as a channel to transmit user data in the user plane.
[0092] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state. Otherwise, it is in the RRC_IDLE state. For NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state can maintain a connection with the core network while releasing the connection with the base station.
[0093] Downlink transmission channels that transmit data from the network to the terminal include the Broadcast Channel (BCH), which transmits system information, and the downlink Shared Channel (SCH), which transmits user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH or a separate downlink Multicast Channel (MCH). Meanwhile, uplink transmission channels that transmit data from the terminal to the network include the Random Access Channel (RACH), which transmits initial control messages, and the uplink Shared Channel (SCH), which transmits user traffic or control messages.
[0094] Logical channels that are located above the transport channel and are mapped to the transport channel include the Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Multicast Control Channel (MCCH), and Multicast Traffic Channel (MTCH).
[0095] Radio frames can be used for uplink and downlink transmission. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame can contain five 1 ms subframes (SF). A subframe can be divided into one or more slots, and the number of slots within a subframe can be determined by the subcarrier spacing (SCS). Each slot can contain 12 or 14 OFDM (A) symbols, depending on the cyclic prefix (CP).
[0096] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).
[0097] Table 2 below illustrates the number of symbols per slot (Nslotsymb), the number of slots per frame (Nframe,uslot), and the number of slots per subframe (Nsubframe,uslot) depending on the SCS setting (u) when normal CP or extended CP is used.
[0098] CP type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot Normal CP15kHz (u=0)1410130kHz (u=1)1420260kHz (u=2)14404120kHz (u=3)14808240kHz (u=4)1416016Extended CP60kHz (u=2)12404
[0099] FIG. 6 illustrates a slot structure of a frame according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.
[0100] Referring to FIG. 6, a slot includes a plurality of symbols in the time domain. A carrier includes a plurality of subcarriers in the frequency domain. An RB (Resource Block) may be defined as a plurality (e.g., 12) of consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) may be defined as a plurality of consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed through activated BWPs. Each element may be referred to as a Resource Element (RE) in the resource grid, and one complex symbol may be mapped to it.
[0101] A Bandwidth Part (BWP) can be a contiguous set of physical resource blocks (PRBs) for a given numerology. A PRB can be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.
[0102] FIG. 7 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 7 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 7, it is assumed that there are three BWPs.
[0103] Referring to Figure 7, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other. Furthermore, a PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.
[0104] The BWP can be set by Point A, an offset from Point A (NstartBWP), and a bandwidth (NsizeBWP). For example, Point A can be an outer reference point of a PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and Point A. For example, the bandwidth can be the number of PRBs in a given numerology.
[0105] SLSS (Sidelink Synchronization Signal) is a SL (sidelink) specific sequence and may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal) and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS and length-127 Gold sequences may be used for S-SSS. For example, a terminal may detect an initial signal (signal detection) and obtain synchronization using S-PSS. For example, the terminal can obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.
[0106] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in order to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).
[0107] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.
[0108] In this specification, PSCCH may be replaced by a control channel, a physical control channel, a sidelink-related control channel, a sidelink-related physical control channel, etc. In this specification, PSSCH may be replaced by a shared channel, a physical shared channel, a sidelink-related shared channel, a sidelink-related physical shared channel, etc.
[0109] FIG. 8 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.
[0110] Referring to (a) of FIG. 8, in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S800, the base station may transmit information related to SL resources and / or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.
[0111] For example, a first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from a base station. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that a base station configures / allocates to the first terminal via downlink control information (DCI). In this specification, a CG resource may be a (periodic) resource that a base station configures / allocates to the first terminal via DCI and / or an RRC message. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station may transmit a DCI related to activation or release of the CG resource to the first terminal.
[0112] In step S810, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S820, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S830, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S840, the first terminal may transmit / report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.
[0113] Referring to (b) of FIG. 8, in resource allocation mode 2, the terminal can determine SL transmission resources within SL resources set by the base station / network or preset SL resources. For example, the set SL resources or preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting resources within the set resource pool. For example, the terminal can select resources within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S810, the first terminal that has selected resources within the resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal using the resources. In step S820, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S830, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal.
[0114] Referring to (a) or (b) of FIG. 8, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.
[0115] Referring to (a) or (b) of FIG. 8, in step S830, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.
[0116] Referring to (a) of FIG. 8, in step S840, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.
[0117] FIG. 9 illustrates an example of a wireless communication environment according to embodiments of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.
[0118] Referring to FIG. 9, a first device (910), a second device (920), and a third device (930) are exemplified as some of the devices that utilize a wireless channel in a wireless communication system. FIG. 9 illustrates only one first device (910), one second device (920), and one third device (930), but is not limited thereto.
[0119] According to the present disclosure, the first device (910), the second device (920), and / or the third device (930) can transmit and receive wireless signals in the millimeter wave (mmWave) band. For example, to improve channel gain, the first device (910), the second device (920), and / or the third device (930) can perform beamforming. Here, the beamforming can include transmit beamforming and receive beamforming. For example, the first device (910), the second device (920), and / or the third device (930) can impart directionality to a transmit signal or a receive signal. For example, the first device (910), the second device (920), and / or the third device (930) may select serving beams (912, 913, 921, 931) through a beam search or beam management procedure. After the serving beams (912, 913, 921, 931) are selected, communication may be performed through resources that are in a quasi-co-located (QCL) relationship with the resources that transmitted the serving beams (912, 913, 921, 931).
[0120] According to the present disclosure, the first device (910), the second device (920), and / or the third device (930) may include an antenna array. Each antenna included in the antenna array may be referred to as an array element or an antenna element. The antenna array may be configured in various forms, such as a linear array or a multi-layer array. The antenna array may be referred to as a massive antenna array. For example, the antenna array may include a plurality of sub-arrays each including a plurality of antenna elements.
[0121] Meanwhile, in the conventional NR Uu (operation between a base station and a UE), a new beam management operation has been introduced at mmWave frequencies. For example, the beam management operation may be beam scheduling, beam selection, beam failure recovery, etc. In the present disclosure, the beam management (e.g., beam failure recovery) operation is proposed as follows. For example, the following proposal may be an operation related to beam management in NR. Meanwhile, the following proposal is not limited to NR. For example, the following proposal may be an operation related to beam management in sidelink. Meanwhile, the following proposal is not limited to sidelink. For example, the following proposal may be an operation related to beam management in NR sidelink.
[0122] The terminal can perform the following motion-based FR2 (mmWave frequency-based communication) operations. For example, FR2 may be sidelink FR2. For example, sidelink FR2 may be sidelink mmWave frequency-based communication. Meanwhile, the motion-based operations below are not limited to sidelink FR2. The present disclosure is not limited to sidelink FR2. For example, the present disclosure can be applied to 5G FR2 or FR2 beyond 5G (e.g., 6G FR2).
[0123] - Beam sweeping operation: The terminal may perform an operation of sweeping the beams to be used for communication to find the best beam (e.g., a transmission beam, a reception beam). For example, the terminal may perform an operation of covering a spatial area using the transmission and / or reception beams for a predetermined time interval in a predetermined manner. For example, communication in the beam sweeping operation may be sidelink communication.
[0124] - Beam measurement operation: The terminal can perform an operation of measuring a reference signal (RS) transmitted by a counterpart terminal and finding an RS whose measurement value is greater than a threshold.
[0125] - Beam selection operation: The terminal can perform an operation of selecting the best beam (e.g., transmission beam, reception beam) based on the beam measurement result.
[0126] - Beam reporting operation: The terminal can perform an operation of reporting the selected best beam to the other terminal or base station.
[0127] - Beam pairing operation: Terminals can perform an operation to synchronize (pair) beams (e.g., transmission beam / reception beam) with each other to enable communication through beams (e.g., transmission beam / reception beam) between terminals.
[0128] (Sidelink) (In FR2) For beam management (e.g., beam sweeping, beam measurement, beam selection, beam pairing) of terminals, terminals can transmit and receive reference signals (RS) to select / decide and adjust / manage BEAMs that can be used between each other.
[0129] In the present disclosure, (sidelink) DRX configuration may include at least one or more of the following parameters.
[0130] - SL drx-onDurationTimer: Duration at the start of the SL DRX cycle
[0131] - SL drx-SlotOffset: Delay before the start of SL drx-onDurationTimer
[0132] - SL drx-InactivityTimer: Duration after a PSCCH opportunity instructing a new SL transmission to the MAC entity.
[0133] - SL drx-StartOffset: Subframe where the SL DRX cycle starts
[0134] - SL drx-Cycle: SL DRX Cycle
[0135] - SL drx-HARQ-RTT-Timer (per HARQ process or per sidelink process): Minimum duration before allocation for HARQ retransmission expected by the MAC entity.
[0136] - SL drx-RetransmissionTimer (per HARQ process or per sidelink process): Maximum duration until a retransmission is received.
[0137] In this disclosure, the (sidelink) DRX timer below can be used for the following purposes.
[0138] - (Sidelink) DRX Onduration Timer: (Sidelink) The period during which a UE performing DRX operation must basically operate as an active time to receive PSCCH / PSSCH from the other UE.
[0139] - (Sidelink) DRX Inactivity Timer: A period for extending the (sidelink) DRX Onduration period, which is a period during which a UE performing (sidelink) DRX operation must basically operate as an active time in order to receive PSCCH / PSSCH of the counterpart UE. For example, the (sidelink) DRX Onduration timer can be extended by the period of the (sidelink) DRX Inactivity timer. For example, when the UE receives a PSCCH (1st SCI and 2nd SCI) for a new TB from the counterpart UE or a new packet (new PSSCH transmission), the UE can start the (sidelink) DRX Inactivity timer and extend the (sidelink) DRX Onduration timer.
[0140] - (Sidelink) DRX HARQ RTT Timer: A period during which a UE performing (sidelink) DRX operation operates in sleep mode until it receives a retransmission packet (e.g., or PSSCH allocation) transmitted by a counterpart UE. For example, if a UE starts a (sidelink) DRX HARQ RTT timer, the UE may determine that the counterpart UE will not transmit a (sidelink) retransmission packet to it until the (sidelink) DRX HARQ RTT timer expires, and may operate in sleep mode during the timer (or may not monitor the (sidelink) channel / signal transmitted by the Tx UE).
[0141] - (Sidelink) DRX Retransmission Timer: A period during which a UE performing (sidelink) DRX operation operates as an active time to receive a retransmission packet (e.g., or PSSCH allocation) transmitted by a counterpart UE. During this timer period, the UE can monitor the reception of a retransmission (sidelink) packet (e.g., or PSSCH allocation) transmitted by the counterpart UE.
[0142] For example, the names of the timers (e.g., (Sidelink) DRX Onduration Timer, (Sidelink) DRX Inactivity Timer, (Sidelink) DRX HARQ RTT Timer, (Sidelink) DRX Retransmission Timer, etc.) are examples, and timers that perform the same / similar function based on the description of each timer can be considered the same / similar timer regardless of the name.
[0143] For example, PSFCH reception may be performed. For example, the MAC entity may perform a HARQ-based (sidelink) RLF detection procedure for each PSSCH transmission. For example, the MAC entity may perform a HARQ-based (sidelink) RLF detection procedure for each PSSCH transmission if the PSSCH transmission occurs for a pair of source Layer-2 IDs and destination Layer-2 IDs corresponding to a PC5-RRC connection established by a higher layer.
[0144] FIG. 10 illustrates a procedure for RLF detection according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.
[0145] Referring to FIG. 10, for example, HARQ-based (sidelink) RLF (radio link failure) detection can be performed.
[0146] For example, if a transmitting terminal does not receive a physical feedback channel (e.g., PSFCH) (e.g., HARQ ACK or HARQ NACK) from a receiving terminal after transmitting a physical control channel / physical shared channel (e.g., PSCCH / PSSCH), the transmitting terminal may increase a discontinuous transmission (DTX) count by 1 and declare a (SL) RLF when the DTX count reaches a threshold. For example, when declaring an (SL) RLF for a unicast link, the terminal may release the PC5 RRC connection that declared the (SL) RLF and report (e.g., report) a PC5 link identifier associated with the released PC5 RRC connection to a higher layer (e.g., a V2X layer). For example, the terminal may report (e.g., report) to the base station that an (SL) RLF has occurred. For example, when reporting, the terminal may report (e.g., report) together the unicast link information where the RLF occurred (e.g., destination layer 2 ID) and the cause (cause) of the (SL) RLF occurrence (e.g., (SL) RLF).
[0147] For example, a HARQ-based (sidelink) RLF detection procedure can be used to detect (sidelink) RLF based on the number of consecutive discontinuous transmissions (DTXs) in a PSFCH reception occasion for a PC5-RRC connection.
[0148] For example, RRC can set the following parameters to control HARQ-based (sidelink) RLF detection. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can be set. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can indicate the maximum number of DTX (e.g., consecutive HARQ DTX) before triggering an RLF.
[0149] For example, the following UE variables can be used for HARQ-based (sidelink) RLF detection: For example, the DTX maintained for each PC5-RRC connection (e.g., numConsecutiveDTX) can be set.
[0150] For example, the (sidelink) HARQ entity may (re)initialize the DTX (e.g., numConsecutiveDTX) to 0 when establishing the PC5-RRC connection or (re)establishing the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX), if any, for each PC5-RRC connection established from the upper layer. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be set to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be (re)configured to a value different from 3.
[0151] For example, the (sidelink) HARQ entity may increment the DTX (e.g., numConsecutiveDTX) by 1 for each PSFCH reception opportunity associated with a PSSCH transmission. For example, the (sidelink) HARQ entity may increment the DTX (e.g., numConsecutiveDTX) by 1 for each PSFCH reception opportunity associated with a PSSCH transmission if there is no PSFCH reception in the PSFCH reception opportunity.
[0152] For example, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission. For example, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, increase the DTX (e.g., numConsecutiveDTX) by 1 if there is no PSFCH reception in the PSFCH reception opportunity, and may instruct RRC to perform HARQ-based (sidelink) RLF detection if the DTX (e.g., numConsecutiveDTX) reaches a maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, as illustrated in FIG. 10, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be set to 3. For example, as illustrated in FIG. 10, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission, if the DTX (e.g., numConsecutiveDTX) reaches a maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) of 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be (re)configured to a value different from 3.
[0153] For example, the (sidelink) HARQ entity may reinitialize DTX (e.g., numConsecutiveDTX) to 0 for each PSFCH reception opportunity associated with a PSSCH transmission. For example, the (sidelink) HARQ entity may reinitialize DTX (e.g., numConsecutiveDTX) to 0 for each PSFCH reception opportunity associated with a PSSCH transmission, unless there is no PSFCH reception in the PSFCH reception opportunity (e.g., if else for “if there is no PSFCH reception in the PSFCH reception opportunity”).
[0154] In FIG. 10, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) is shown to be set to 3, but is not limited thereto. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be (re)set to a value other than 3.
[0155] In multi-carrier operation or carrier aggregation (CA), there may be multiple carriers involved in a PC5-RRC connection. There may be issues with detecting RLF and indicating RLF detection to upper layers when detecting DTX peaks on only some carriers.
[0156] FIG. 11 illustrates a procedure for RLF detection according to an embodiment of the present disclosure. The embodiment of FIG. 11 can be combined with various embodiments of the present disclosure.
[0157] Referring to FIG. 11, for example, HARQ-based (sidelink) RLF (radio link failure) detection can be performed.
[0158] For example, in V2X (e.g., LTE), a terminal supporting multi-channel operation (e.g., multi-carrier operation or carrier aggregation) can select a specific (sidelink) carrier for transmitting (sidelink) data, select available resources on the selected (sidelink) carrier, and transmit (sidelink) data through the selected resources and carrier.
[0159] According to the present disclosure, carrier (re-)selection and / or resource (re-)selection (and / or unicast communication) operations of a terminal supporting multi-carrier (e.g., multi-carrier operation) may be proposed as follows.
[0160] According to the present disclosure, the CBR threshold(s) associated with (sidelink) carrier(s) / (SL) BWP(s) / (SL) HARQ entities can be set per priority or per QoS profile (e.g., PDB, reliability) or per SL Radio Bearer or per logical channel.
[0161] For example, when a transmitting terminal declares a (sidelink) RLF on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all available carriers that have been configured) (e.g., when discontiuous transmission (DTX) (e.g., an event in which a PSFCH for a PSCCH / PSSCH transmission is not received) occurs on a specific carrier for a preset threshold, the transmitting terminal may declare an RLF on that carrier), the transmitting terminal may trigger a carrier reselection procedure to replace the carrier where the RLF occurred with another carrier. For example, when a (sidelink) RLF is declared on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all available carriers that have been configured), the carrier reselection procedure may be triggered to reselect a new carrier. For example, resources being used or selected on the carrier where the RLF occurred may be released and resources to be used on the new carrier may be reselected (e.g., the terminal may trigger resource reselection so that the newly reselected resources can be used on the newly selected carrier) and mapped to the newly selected carrier. For example, a transmitting terminal can select a newly selected carrier and new resources to use on that carrier, and transmit (sidelink) data using the selected carrier and selected resources.
[0162] For example, PSFCH reception may be performed. For example, the MAC entity may perform a HARQ-based (sidelink) RLF detection procedure for each PSSCH transmission. For example, the MAC entity may perform a HARQ-based (sidelink) RLF detection procedure for each PSSCH transmission if the PSSCH transmission occurs for a pair of source Layer-2 IDs and destination Layer-2 IDs corresponding to a PC5-RRC connection established by a higher layer.
[0163] For example, a HARQ-based (sidelink) RLF detection procedure can be used to detect a (sidelink) RLF based on the number of consecutive discontinuous transmissions (DTXs) in a PSFCH reception opportunity (occasion) for a PC5-RRC connection. For example, for each carrier associated with the PC5-RRC connection, a HARQ-based (sidelink) RLF detection procedure can be used to detect a (sidelink) RLF based on the number of consecutive discontinuous transmissions (DTXs) in a PSFCH reception opportunity (occasion) for the PC5-RRC connection.
[0164] For example, RRC can set the following parameters to control HARQ-based (sidelink) RLF detection. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can be set. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can indicate the maximum number of DTX (e.g., consecutive HARQ DTX) before triggering an RLF.
[0165] For example, the following UE variables can be used for HARQ-based (sidelink) RLF detection: For example, the DTX maintained for each PC5-RRC connection (e.g., numConsecutiveDTX) can be set. For example, the DTX maintained for each carrier for each PC5-RRC connection (e.g., numConsecutiveDTX) can be set.
[0166] For example, the (sidelink) HARQ entity may (re)initialize the DTX (e.g., numConsecutiveDTX) to 0 for each PC5-RRC connection established from the upper layer, if any, upon establishment of the PC5-RRC connection or upon (re)establishment of the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may (re)initialize the DTX (e.g., numConsecutiveDTX) to 0 for each PC5-RRC connection established from the upper layer, if any, upon establishment of the PC5-RRC connection or upon (re)establishment of the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, as illustrated in FIG. 10, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be set to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be (re)set to a value other than 3.
[0167] For example, the (sidelink) HARQ entity may increment the DTX (e.g., numConsecutiveDTX) by 1 for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may increment the DTX (e.g., numConsecutiveDTX) by 1 for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may increment the DTX (e.g., numConsecutiveDTX) by 1 for each PSFCH reception opportunity associated with a PSSCH transmission if there is no PSFCH reception in the PSFCH reception opportunity. For example, in (SL) operation with shared spectrum channel access, a terminal (e.g., UE) may increment DTX (e.g., numConsecutiveDTX) by 1 when the terminal (e.g., UE) fails to detect HARQ feedback on all relevant PSFCH resources.
[0168] For example, the (sidelink) HARQ entity may trigger a TX carrier (re)selection procedure for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may trigger a TX carrier (re)selection procedure for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may trigger a TX carrier (re)selection procedure for each PSFCH reception opportunity associated with a PSSCH transmission if one or more of the selected carriers are considered as carriers for HARQ-based (sidelink) RLF detection. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may trigger a TX carrier (re)selection procedure for each PSFCH reception opportunity associated with a PSSCH transmission if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for the carrier for which HARQ-based (sidelink) RLF detection applies. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may trigger a TX carrier (re)selection procedure for each PSFCH reception opportunity associated with a PSSCH transmission, if one or more selected carriers are considered as carriers for HARQ-based (sidelink) RLF detection, if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for the carriers subject to HARQ-based (sidelink) RLF detection.For example, in triggering a TX carrier (re)selection procedure, the TX carrier (re)selection procedure may be triggered as initiated in the TX carrier (re)selection below. For example, in the selected one or more carriers, the carrier may be selected as initiated in the TX carrier (re)selection below. For example, as illustrated in FIG. 11, for a first carrier, which is one of each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, trigger the TX carrier (re)selection procedure if the first carrier, which is one of the selected one or more carriers, is considered as a carrier for HARQ-based (sidelink) RLF detection, and if the DTX (e.g., numConsecutiveDTX) reaches 3, which is the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for the first carrier that is applied for HARQ-based (sidelink) RLF detection. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be (re)set to a value other than 3.
[0169] For example, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) carrier failure detection for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) carrier failure detection for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) carrier failure detection for each PSFCH reception opportunity associated with a PSSCH transmission if one or more of the selected carriers are considered as carriers for HARQ-based (sidelink) RLF detection. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC for HARQ-based (sidelink) carrier failure detection, for each PSFCH reception opportunity associated with a PSSCH transmission, if the DTX (e.g., numConsecutiveDTX) for the carrier applicable for HARQ-based (sidelink) RLF detection reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, instruct RRC to perform HARQ-based (sidelink) carrier failure detection if the DTX (e.g., numConsecutiveDTX) for the selected carriers is considered as a carrier for HARQ-based (sidelink) RLF detection, and if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for the carriers subject to HARQ-based (sidelink) RLF detection.For example, from the selected one or more carriers, the carrier may be selected as disclosed in the TX carrier (re)selection below. For example, as illustrated in FIG. 11, for a first carrier, which is one of each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, instruct RRC to perform HARQ-based (sidelink) carrier failure detection if the first carrier, which is one of the selected one or more carriers, is considered as a carrier for HARQ-based (sidelink) RLF detection, if the DTX (e.g., numConsecutiveDTX) reaches 3, which is the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for the first carrier, which is a carrier applicable to HARQ-based (sidelink) RLF detection. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can be (re)set to a value other than 3.
[0170] For example, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission if one or more of the selected carriers are considered as carriers for HARQ-based (sidelink) RLF detection. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC for HARQ-based (sidelink) RLF detection, for each PSFCH reception opportunity associated with a PSSCH transmission, if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for all carriers for which HARQ-based (sidelink) RLF detection applies. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, instruct RRC to perform HARQ-based (sidelink) RLF detection if one or more selected carriers are considered as carriers for HARQ-based (sidelink) RLF detection, and if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for all carriers subject to HARQ-based (sidelink) RLF detection.For example, from the selected one or more carriers, the carrier may be selected as disclosed in the TX carrier (re)selection below. For example, as illustrated in FIG. 11, for each carrier associated with the PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with the PSSCH transmission, instruct the RRC to perform HARQ-based (sidelink) RLF detection if the selected one or more carriers, the first carrier and the second carrier, are considered as carriers for HARQ-based (sidelink) RLF detection, if the DTX (e.g., numConsecutiveDTX) reaches 3, which is the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) for all carriers applicable to HARQ-based (sidelink) RLF detection, the first carrier and the second carrier. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can be (re)set to a value other than 3.
[0171] For example, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission if the DTX (e.g., numConsecutiveDTX) reaches a maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may instruct RRC to perform HARQ-based (sidelink) RLF detection for each PSFCH reception opportunity associated with a PSSCH transmission if the DTX (e.g., numConsecutiveDTX) reaches a maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, instruct RRC to perform HARQ-based (sidelink) RLF detection if the selected one or more carriers are not considered as carriers for HARQ-based (sidelink) RLF detection (e.g., else for “if the selected one or more carriers are considered as carriers for HARQ-based (sidelink) RLF detection”), and if the DTX (e.g., numConsecutiveDTX) reaches the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX). For example, among the selected one or more carriers, a carrier may be selected as described in TX carrier (re)selection below. For example, as illustrated in FIG. 10, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be set to 3.For example, as illustrated in FIG. 10, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may, for each PSFCH reception opportunity associated with a PSSCH transmission, instruct RRC to perform HARQ-based (sidelink) RLF detection if the selected one or more carriers are not considered as carriers for HARQ-based (sidelink) RLF detection (e.g., else for “if the selected one or more carriers are considered as carriers for HARQ-based (sidelink) RLF detection”), and if the DTX (e.g., numConsecutiveDTX) reaches a maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) of 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may not be limited to 3. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) can be (re)set to a value other than 3.
[0172] For example, the (sidelink) HARQ entity may reinitialize the DTX (e.g., numConsecutiveDTX) to 0 for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may reinitialize the DTX (e.g., numConsecutiveDTX) to 0 for each PSFCH reception opportunity associated with a PSSCH transmission. For example, for each carrier associated with a PC5-RRC connection, the (sidelink) HARQ entity may reinitialize the DTX (e.g., numConsecutiveDTX) to 0 for each PSFCH reception opportunity associated with a PSSCH transmission, unless there is no PSFCH reception in the PSFCH reception opportunity (e.g., if else for “if there is no PSFCH reception in the PSFCH reception opportunity”).
[0173] For example, when a transmitting terminal declares a (sidelink) RLF on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all available carriers that have been configured) (e.g., when discontiuous transmission (DTX) (e.g., an event in which a PSFCH for a PSCCH / PSSCH transmission is not received) occurs on a specific carrier for a preset threshold, the transmitting terminal may declare an RLF on that carrier), the transmitting terminal may trigger a carrier reselection procedure to replace the carrier where the RLF occurred with another carrier. For example, when a (sidelink) RLF is declared on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all available carriers that have been configured), the carrier reselection procedure may be triggered to reselect a new carrier. For example, resources being used or selected on the carrier where the RLF occurred may be released and resources to be used on the new carrier may be reselected (e.g., the terminal may trigger resource reselection so that the newly reselected resources can be used on the newly selected carrier) and mapped to the newly selected carrier. For example, a transmitting terminal can select a newly selected carrier and new resources to use on that carrier, and transmit (sidelink) data using the selected carrier and selected resources.
[0174] By not indicating an RLF when a DTX peak is detected only in some carriers, the PC5-RRC connection can be prevented from being terminated due to an RLF being indicated even when a DTX peak is not detected in any of the multiple carriers, thereby preventing the PC5-RRC connection from being terminated due to an RLF being indicated even when there are available carriers where a DTX peak is not detected. By indicating an RLF only when a DTX peak is detected in multiple carriers, the PC5-RRC connection can be prevented from being terminated due to an RLF being indicated even when there are available carriers where a DTX peak is not detected. By terminating the PC5-RRC connection only when a DTX peak is detected in multiple carriers, the PC5-RRC connection can be prevented from being terminated even when there are available carriers where a DTX peak is not detected.
[0175] In Fig. 11, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) is shown to be set to 3, but is not limited thereto. For example, the maximum DTX (e.g., (sl-)maxNumConsecutiveDTX) may be (re)set to a value other than 3.
[0176] FIG. 12 illustrates a procedure for LBT detection according to an embodiment of the present disclosure. The embodiment of FIG. 12 can be combined with various embodiments of the present disclosure.
[0177] Referring to FIG. 12, for example, a lower layer of a MAC entity may perform a (SL) LBT procedure. For example, as in 3GPP TS 37.213, a lower layer of a MAC entity may perform a (SL) LBT procedure. For example, a lower layer of a MAC entity may perform a (SL) LBT procedure, and if a channel is identified as occupied, transmission may not be performed by a lower layer of the MAC entity according to the (SL) LBT procedure. For example, when a lower layer of a MAC entity performs a LBT procedure before transmission and the transmission is not performed, an (SL) LBT failure indication may be transmitted from a lower layer of the MAC entity to the MAC entity. For example, if there is no separate disclosure, when the (SL) LBT procedure is performed for transmission, the action may be performed as disclosed in the present disclosure regardless of whether an (SL) LBT failure indication is received from a lower layer of the MAC entity. For example, when the (SL) LBT is not performed from a lower layer of the MAC entity, an (SL) LBT failure indication may not be received from the lower layer of the MAC entity.
[0178] For example, the (sidelink) LBT failure and / or recovery procedure may be performed as follows:
[0179] For example, a MAC entity may be configured by RRC with (SL) LBT failure detection and / or recovery procedures. (SL) Consistent LBT failures may be detected on a per-RB-set basis by counting (SL) LBT failure indication(s) for every (SL) transmission from a lower layer of the MAC entity to the MAC entity.
[0180] For example, RRC can set the following parameters in the (SL) LBT failure recovery configuration (e.g., (sl-)lbt-FailureRecoveryConfig):
[0181] - (SL) Maximum count of (SL) LBT failure instances for consistent LBT failure detection (e.g., (sl-)lbt-FailureInstanceMaxCount)
[0182] - (SL) LBT failure detection timer for consistent LBT failure detection (e.g., (sl-)lbt-FailureDetectionTimer)
[0183] - (SL) LBT recovery timer for recovery from triggered (SL) consistent LBT failures (e.g., (sl-)LBT-RecoveryTimer)
[0184] For example, the following UE variables can be used in a (SL) consistent LBT failure detection procedure:
[0185] - LBT_COUNTER (e.g. SL_LBT_COUNTER) (e.g. RB (set) by): Counter for (SL) LBT failure indications, initially set to 0.
[0186] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may increment the LBT_COUNTER (e.g., SL_LBT_COUNTER) for the RB set by 1. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if a (SL) LBT failure indication is received from a lower layer for an RB set in the configured pool(s) of resources in the (SL) BWP, the MAC entity may increment the LBT_COUNTER (e.g., SL_LBT_COUNTER) for the RB set by 1. For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if an (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may increment the LBT_COUNTER (e.g., SL_LBT_COUNTER) for the set of RBs by 1.
[0187] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer for a set of RBs. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if a (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer for the set of RBs. For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if an (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart the (sl-)lbt-FailureDetectionTimer for the set of RBs.
[0188] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity can trigger a (SL) consistent LBT failure for a set of RBs in the (SL) BWP. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the LBT_COUNTER (e.g., SL_LBT_COUNTER) is greater than or equal to (sl-)lbt-FailureInstanceMaxCount, the MAC entity can trigger a (SL) consistent LBT failure for a set of RBs in the (SL) BWP. For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the LBT_COUNTER (e.g., SL_LBT_COUNTER) is greater than or equal to 3, which is (sl-)lbt-FailureInstanceMaxCount, the MAC entity can trigger a (SL) consistent LBT failure for a set of RBs in the (SL) BWP. For example, (sl-)lbt-FailureInstanceMaxCount is not limited to 3. For example, (sl-)lbt-FailureInstanceMaxCount can be set to a value different from 3.
[0189] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity can indicate to the upper layer of the MAC entity (e.g., to RRC) (SL) consistent LBT failure-based (sidelink) RLF detection for all destination IDs associated with the unicast service. For example, for an (activated) (SL) BWP (e.g. configured with (sl-)lbt-FailureRecoveryConfig), if a consistent LBT failure is triggered on all RB sets of the configured pool(s) of resources in the (SL) BWP, the MAC entity may indicate to the upper layer of the MAC entity (e.g., to RRC) (sidelink) RLF detection based on the (SL) consistent LBT failure for all destination IDs associated with the unicast service.
[0190] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if a (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer. For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if an (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart the (sl-)lbt-FailureDetectionTimer.
[0191] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if all triggered (SL) consistent LBT failures in the RB set are canceled, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the (sl-)lbt-FailureDetectionTimer has expired for an RB set, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set. For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if all triggered (SL) consistent LBT failures in the RB set have been canceled, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set.For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the (sl-)lbt-FailureDetectionTimer has expired for an RB set, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set.
[0192] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureDetectionTimer is reset by upper layers, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureInstanceMaxCount is reset by upper layers, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets. For example, as illustrated in FIG. 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureDetectionTimer is reset by upper layers, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets.For example, as illustrated in Figure 12, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureInstanceMaxCount is reset by the upper layer, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets.
[0193] For example, a transmitting terminal (e.g., supporting (sidelink) carrier aggregation operation and (sidelink) unlicensed band operation) may trigger a carrier reselection procedure to replace the carrier on which the LBT failure occurred with another carrier when it declares an LBT failure (e.g., consistent or one shot) on a specific (sidelink) carrier (e.g., one of the selected carriers, all selected carriers, or all configured available carriers). For example, a carrier reselection procedure may be triggered when it declares an LBT failure (e.g., consistent or one shot) on a specific (sidelink) carrier (e.g., one of the selected carriers, all selected carriers, or all configured available carriers). For example, when an LBT failure occurs (e.g., consistent or one shot), the resources being used or selected on the carrier can be released and resources to be used on a new carrier can be reselected (e.g., the UE can trigger resource reselection so that the newly reselected resources can be used on the newly selected carrier) and mapped to the newly selected carrier. For example, the transmitting UE can select the newly selected carrier and new resources to be used on the newly selected carrier, and transmit (sidelink) data using the selected carrier and the selected resources.
[0194] FIG. 13 illustrates a procedure for beam failure detection according to an embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.
[0195] Referring to FIG. 13, if a terminal detects a threshold amount of failures in a beam being used for communication, the terminal may trigger a beam failure recovery procedure to perform a beam recovery procedure. For example, if a terminal detects a threshold amount of failures in a beam being used for sidelink communication, the terminal may trigger a sidelink beam failure recovery procedure to perform a beam recovery procedure. For example, if the MAC layer of the terminal receives a threshold amount of beam failure instances from the physical layer, the terminal may trigger a beam failure recovery procedure to perform a beam recovery procedure. For example, the beam recovery procedure by triggering a beam failure recovery procedure may be performed by the MAC layer of the terminal. For example, if the MAC layer of a terminal receives a threshold number of beam failure instances from the physical layer, the terminal may trigger a sidelink beam failure recovery procedure to perform a beam recovery procedure. For example, the beam recovery procedure by triggering a sidelink beam failure recovery procedure may be performed by the MAC layer of the terminal. Although the present disclosure has been described with respect to sidelink beam failure, it is not limited thereto. For example, the present disclosure may be applied to beam failures other than sidelink beam failure as well as sidelink beam failure.
[0196] In FIG. 13, for example, the MAC layer may configure a beam failure recovery procedure that is used to notify when a beam failure is detected by the RRC. For example, a beam failure may be detected by counting beam failure instance indications to the MAC entity from a lower layer. For example, the RRC may configure a beam failure instance maximum count and a beam failure detection timer. For example, the beam failure instance maximum count may determine how many beam failure events must pass before the terminal triggers beam failure recovery. For example, the beam failure instance maximum count may be set to 3. For example, the beam failure detection timer may be a timer for beam failure detection. For example, if a beam failure instance indication is received from a lower layer, the beam failure detection timer may be started or restarted. For example, if a beam failure instance indication is received from a lower layer, the beam failure instance counter can be increased by 1. For example, if the beam failure instance counter is greater than or equal to a maximum count of beam failure instances, a beam failure can be detected. For example, if the beam failure instance counter is greater than or equal to 3, a beam failure can be detected. For example, if the beam failure instance counter is greater than or equal to a maximum count of beam failure instances, a beam failure recovery procedure can be triggered.For example, if the beam failure instance counter is greater than or equal to 3, a beam failure recovery procedure can be triggered. For example, if the beam failure detection timer expires, the beam failure instance counter can be set to 0.
[0197] In Fig. 13, the maximum count of beam failure instances is set to 3, but this is not limited to this. For example, the maximum count of beam failure instances may be set to a value other than 3.
[0198] In this disclosure, the following follow-up actions of the terminal are proposed when the (SL) BFR procedure fails.
[0199] When beam failure recovery (BFR) is triggered, the terminal may transmit a (SL) BFR MAC CE (e.g., for the purpose of indicating that there is a problem with the currently operating transmit beam or receive beam, or for the purpose of indicating that there is a problem with a reference signal associated with the currently operating transmit beam or receive beam, or for the purpose of indicating a best transmit beam or a best receive beam for beam failure recovery when BFR is triggered) and may also start a (SL) BFR timer to initiate the (SL) BFR process. If feedback (e.g., a (SL) BFR confirmation MAC CE or HARQ ACK feedback) for the transmitted (SL) BFR MAC CE is not received by the time the BFR timer expires, the terminal may initiate the following procedure.
[0200] - The terminal can re-trigger the BFR process by retransmitting (SL) BFR MAC CE (for example, to indicate that there is a problem with the currently operating transmit beam or receive beam, or to indicate that there is a problem with the reference signal associated with the currently operating transmit beam or receive beam, or to indicate the best transmit beam or best receive beam for beam failure recovery when BFR is triggered).
[0201] - The terminal may consider the (SL) BFR process as a failure and declare (SL) RLF for the PC5 RRC connection for which (SL) BFR was triggered and report it to the base station or the other terminal (with cause: (SL) beam failure recovery (BFR) fail-based (sidelink) RLF).
[0202] - The terminal can re-trigger or re-perform at least one operation among beam sweeping, beam selection, or beam pairing.
[0203] For example, if a terminal detects a threshold amount of failure in a beam being used for (sidelink) communication, the terminal can trigger a (sidelink) beam failure recovery procedure to perform a procedure for recovering the beam. In the present disclosure, when a threshold amount of (sidelink) beam failure occurs, the BFR operation of the terminal can be defined as follows:
[0204] For example, a terminal (e.g., supporting (sidelink) carrier aggregation operation and (sidelink) FR2 operation) may trigger a carrier reselection procedure to replace the carrier on which the beam failure occurred with another carrier when a beam failure occurs (e.g., when the MAC layer receives a beam failure instance from the physical layer) on a specific (sidelink) carrier (e.g., one of the selected carriers, all selected carriers, or all configured available carriers) or when a beam failure recovery procedure is triggered or when a beam failure recovery procedure fails. For example, if a beam failure occurs on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all configured available carriers), or if a beam failure recovery procedure is triggered, or if a beam failure recovery procedure fails, a carrier reselection procedure may be triggered to reselect a new carrier. For example, resources being used or selected on the carrier where a beam failure occurs, or a beam failure recovery procedure is triggered, or if a beam failure recovery procedure fails, may be released and resources to be used on a new carrier may be reselected (e.g., a UE may trigger resource reselection to use newly reselected resources on the newly selected carrier) and mapped to the newly selected carrier.For example, the terminal can select a newly selected carrier and new resources to use on that carrier, and transmit and receive (sidelink) data using the selected carrier and selected resources.
[0205] For example, a MAC reset operation may be performed. If a (sidelink) specific reset of a MAC entity is requested by a higher layer for a PC5-RRC connection, the MAC entity may:
[0206] For example, if a (sidelink) specific reset of the MAC entity is requested by a higher layer for a PC5-RRC connection, the MAC entity may flush the soft buffers for all (sidelink) processes for all TB(s) associated with the PC5-RRC connection.
[0207] For example, if a (sidelink) specific reset of the MAC entity is requested by a higher layer for a PC5-RRC connection, the MAC entity may consider all (sidelink) processes for all TB(s) associated with the PC5-RRC connection to be free.
[0208] For example, the MAC entity may cancel triggered scheduling request procedures, if any, associated only with the PC5-RRC connection (e.g., if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection).
[0209] For example, the MAC entity may cancel the triggered (sidelink) buffer status reporting procedure, if any, associated only with the PC5-RRC connection (e.g., if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection).
[0210] For example, the MAC entity may cancel the triggered (sidelink) CSI reporting procedure, if any, associated with the PC5-RRC connection (e.g., if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection).
[0211] For example, the MAC entity may cancel the triggered (sidelink) DRX command MAC CE associated with the PC5-RRC connection (e.g., if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection).
[0212] For example, if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection, the MAC entity may cancel the triggered (sidelink) inter-UE coordination-request transmission procedure, if any, associated with the PC5-RRC connection.
[0213] For example, if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection, the MAC entity may cancel the triggered (sidelink) inter-UE coordination-information reporting procedure, if any, associated with the PC5-RRC connection.
[0214] For example, if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection, the MAC entity may stop all timers (if running) associated with the PC5-RRC connection.
[0215] For example, the MAC entity may reset the DTX (e.g., numConsecutiveDTX) associated with the PC5-RRC connection (e.g., if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection).
[0216] For example, the MAC entity may initialize SBj to 0 for each logical channel associated with the PC5-RRC connection (e.g., if a (sidelink) specific reset of the MAC entity is requested by a higher layer for the PC5-RRC connection).
[0217] For example, a MAC reset operation may be performed. For example, the UE may perform a MAC reset operation per specific (sidelink) carrier in operation or configured / per specific (sidelink) BWP / per specific (sidelink) resource pool / per specific (sidelink) HARQ entity. For example, if the UE declares a (sidelink) RLF on a specific (sidelink) carrier, or declares a (consistent) LBT failure, or declares a beam failure, or beam failure recovery fails, the UE may reset all MAC operation procedures in operation on the corresponding carrier (e.g., the (sidelink) RLF generating carrier, or the carrier declaring a (consistent) LBT failure, or the carrier declaring a beam failure, or the carrier declaring a beam failure, or the carrier where beam failure recovery fails). For example, if the UE requests from a higher layer (e.g., V2X layer or RRC layer) or if the CBR measurement value of a specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity is measured to be higher (e.g., lower) than a CBR threshold associated with the specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity, the UE may perform a MAC reset operation of the specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity that is in operation or has been configured.For example, when the terminal receives a NACK feedback greater than a threshold value from a request from a higher layer (e.g., a V2X layer or an RRC layer) or from a specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity, or when discontiuous transmission (DTX) occurs for a preset threshold value, the terminal may perform a MAC reset operation of the operating or configured specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity.
[0218] For example, the terminal may perform the following actions upon sidelink MAC reset per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity.
[0219] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may flush soft buffers for all (sidelink) processes for all TB(s) associated with the PC5-RRC connection.
[0220] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may consider all (sidelink) processes for all TB(s) associated with the PC5-RRC connection to be unoccupied.
[0221] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) buffer status reporting procedure, if any, associated only with the PC5-RRC connection.
[0222] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) buffer status reporting procedure, if any, associated only with the PC5-RRC connection.
[0223] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) CSI reporting procedure associated with the PC5-RRC connection, if any.
[0224] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel a triggered (sidelink) DRX command MAC CE (e.g., a triggered (sidelink) DRX command MAC CE reporting procedure) associated with the PC5-RRC connection (e.g., associated only with the PC5-RRC connection), if any.
[0225] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) IUC-Request (inter-UE coordination-request) transmission procedure associated with the PC5-RRC connection, if any.
[0226] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) IUC-information (inter-UE coordination-information) reporting procedure associated with the PC5-RRC connection, if any.
[0227] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may stop all timers (if running) associated with the PC5-RRC connection.
[0228] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may reset the DTX (e.g., numConsecutiveDTX) associated with the PC5-RRC connection.
[0229] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may reset the LBT counter (e.g., SL_LBT_COUNTER) associated with the PC5-RRC connection.
[0230] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may reset an LBT counter (e.g., SL_LBT_COUNTER) associated with the (sidelink) carrier.
[0231] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the terminal may initialize SBj to 0 for each logical channel associated with the PC5-RRC connection.
[0232] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) consistent LBT failure (MAC CE) reporting procedure associated with the (sidelink) carrier, if any.
[0233] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the procedure by reporting a triggered consistent LBT failure (MAC CE) associated with the (sidelink) carrier (e.g., MAC CE reporting for the purpose of reporting a sidelink consistent LBT failure to the base station), if any. For example, according to an embodiment of the present disclosure, the UE may include in the consistent LBT failure MAC CE information the (sidelink) carrier index on which the consistent LBT failure occurred.
[0234] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) beam failure recovery procedure associated with the (sidelink) carrier, if any.
[0235] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) beam failure recovery (MAC CE) reporting procedure associated with the (sidelink) carrier, if any.
[0236] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel a triggered beam failure recovery (MAC CE) reporting procedure (e.g., sidelink beam failure recovery MAC CE reporting that the UE reports to the base station) associated with the (sidelink) carrier, if any. For example, according to an embodiment of the present disclosure, the UE may include in the beam failure recovery MAC CE beam information / beam resource signal information on which beam failure occurred and (sidelink) carrier index information on which beam failure occurred.
[0237] For example, a MAC reset operation may be performed. For example, the terminal may perform a MAC reset operation procedure when it declares a (sidelink) RLF in all (sidelink) carriers / all (sidelink) BWPs / all (sidelink) resource pools / all (sidelink) HARQ entities that are in operation or have been configured, or when it declares a (consistent) LBT failure, or when it declares a beam failure, or when beam failure recovery fails.
[0238] For example, a terminal may perform the following actions upon a sidelink MAC reset:
[0239] For example, (e.g., upon a sidelink MAC reset) the terminal may flush soft buffers for all (sidelink) processes for all TB(s) associated with the PC5-RRC connection.
[0240] For example, (e.g., upon a sidelink MAC reset) the terminal may consider all (sidelink) processes for all TB(s) associated with the PC5-RRC connection to be unoccupied.
[0241] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel the triggered (sidelink) buffer status reporting procedure, if any, associated only with the PC5-RRC connection.
[0242] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel the triggered (sidelink) buffer status reporting procedure, if any, associated only with the PC5-RRC connection.
[0243] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel the triggered (sidelink) CSI reporting procedure associated with the PC5-RRC connection, if any.
[0244] For example, (e.g., upon sidelink MAC reset), the UE may cancel a triggered (sidelink) DRX command MAC CE (e.g., a triggered (sidelink) DRX command MAC CE reporting procedure) associated with the PC5-RRC connection (e.g., associated only with the PC5-RRC connection), if any.
[0245] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel a triggered (sidelink) inter-UE coordination-request transmission procedure associated with the PC5-RRC connection, if any.
[0246] For example, (e.g., upon a sidelink MAC reset) the UE may cancel the triggered (sidelink) inter-UE coordination-information reporting procedure associated with the PC5-RRC connection, if any.
[0247] For example, upon a sidelink MAC reset (e.g.), the terminal may stop all timers (if running) associated with the PC5-RRC connection.
[0248] For example, (e.g., upon a sidelink MAC reset) the terminal may reset the DTX (e.g., numConsecutiveDTX) associated with the PC5-RRC connection.
[0249] For example, (e.g., upon a sidelink MAC reset) the terminal may reset the LBT counter (e.g., SL_LBT_COUNTER) associated with the PC5-RRC connection.
[0250] For example, (e.g., upon a sidelink MAC reset) the terminal may reset the LBT counter (e.g., SL_LBT_COUNTER) associated with all available (e.g., or configured) (sidelink) carriers.
[0251] For example, upon a sidelink MAC reset (e.g.), the terminal may initialize SBj to 0 for each logical channel associated with the PC5-RRC connection.
[0252] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel any triggered (sidelink) consistent LBT failure (MAC CE) reporting procedure associated with any available (e.g., or configured) (sidelink) carrier, if any.
[0253] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel the procedure by reporting a triggered consistent LBT failure (MAC CE) associated with any available (e.g., or configured) (sidelink) carrier (e.g., MAC CE reporting for the purpose of reporting a sidelink consistent LBT failure to the base station).
[0254] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel any triggered (sidelink) beam failure recovery procedure associated with any available (e.g., or configured) (sidelink) carrier, if any.
[0255] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel any triggered (sidelink) beam failure recovery (MAC CE) reporting procedure associated with any available (e.g., or configured) (sidelink) carrier, if any.
[0256] For example, (e.g., upon a sidelink MAC reset) the terminal may cancel any triggered beam failure recovery (MAC CE) reporting procedure (e.g., sidelink beam failure recovery MAC CE reporting that the terminal reports to the base station) associated with any available (e.g., or configured) (sidelink) carrier, if any.
[0257] For example, upon a sidelink MAC reset (e.g.), the terminal may cancel a triggered carrier re-selection procedure, if any, associated with the PC5-RRC connection.
[0258] For example, a MAC reset operation may be performed. For example, the UE may perform a MAC reset operation per specific (sidelink) carrier in operation or configured / per specific (sidelink) BWP / per specific (sidelink) resource pool / per specific (sidelink) HARQ entity. For example, if the UE declares a (sidelink) RLF on a specific (sidelink) carrier, or declares a (consistent) LBT failure, or declares a beam failure, or beam failure recovery fails, the UE may reset all MAC operation procedures in operation on the corresponding carrier (e.g., the (sidelink) RLF generating carrier, or the carrier declaring a (consistent) LBT failure, or the carrier declaring a beam failure, or the carrier declaring a beam failure, or the carrier where beam failure recovery fails). For example, if the UE requests from a higher layer (e.g., V2X layer or RRC layer) or if the CBR measurement value of a specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity is measured to be higher (e.g., lower) than a CBR threshold associated with the specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity, the UE may perform a MAC reset operation of the specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity that is in operation or has been configured.For example, when the terminal receives a NACK feedback greater than a threshold value from a request from a higher layer (e.g., a V2X layer or an RRC layer) or from a specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity, or when discontiuous transmission (DTX) occurs for a preset threshold value, the terminal may perform a MAC reset operation of the operating or configured specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity.
[0259] For example, the terminal may perform the following actions upon sidelink MAC reset per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity.
[0260] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may flush soft buffers for all (sidelink) processes for all TB(s) associated with the (sidelink) carrier.
[0261] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may consider all (sidelink) processes for all TB(s) associated with the (sidelink) carrier to be unoccupied.
[0262] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel triggered (sidelink) buffer status reporting procedures, if any, associated only with the (sidelink) carrier.
[0263] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel triggered (sidelink) buffer status reporting procedures, if any, associated only with the (sidelink) carrier.
[0264] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) CSI reporting procedure associated with the (sidelink) carrier, if any.
[0265] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel a triggered (sidelink) DRX command MAC CE (e.g., a triggered (sidelink) DRX command MAC CE reporting procedure) associated with the (sidelink) carrier (e.g., associated only with the (sidelink) carrier), if any.
[0266] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel a triggered (sidelink) IUC-Request (inter-UE coordination-request) transmission procedure associated with the (sidelink) carrier, if any.
[0267] For example, upon sidelink MAC reset (e.g. per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) IUC-information (inter-UE coordination-information) reporting procedure associated with the (sidelink) carrier, if any.
[0268] For example, upon a sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may stop all timers (if running) associated with the (sidelink) carrier.
[0269] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may reset the DTX (e.g., numConsecutiveDTX) associated with the (sidelink) carrier.
[0270] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may reset an LBT counter (e.g., SL_LBT_COUNTER) associated with the (sidelink) carrier.
[0271] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may reset an LBT counter (e.g., SL_LBT_COUNTER) associated with the (sidelink) carrier.
[0272] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may initialize SBj to 0 for each logical channel associated with the (sidelink) carrier.
[0273] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) consistent LBT failure (MAC CE) reporting procedure associated with the (sidelink) carrier, if any.
[0274] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the procedure by reporting a triggered consistent LBT failure (MAC CE) associated with the (sidelink) carrier (e.g., MAC CE reporting for the purpose of reporting a sidelink consistent LBT failure to the base station), if any. For example, according to an embodiment of the present disclosure, the UE may include in the consistent LBT failure MAC CE information the (sidelink) carrier index on which the consistent LBT failure occurred.
[0275] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) beam failure recovery procedure associated with the (sidelink) carrier, if any.
[0276] For example, upon sidelink MAC reset (e.g., per specific sidelink carrier and / or per specific (sidelink) BWP and / or per specific (sidelink) resource pool and / or per specific (sidelink) HARQ entity), the UE may cancel the triggered (sidelink) beam failure recovery (MAC CE) reporting procedure associated with the (sidelink) carrier, if any.
[0277] For example, upon a sidelink MAC reset (e.g.), the terminal may cancel a triggered carrier re-selection procedure, if any, associated with the PC5-RRC connection.
[0278] For example, a (partial) MAC reset operation may be performed. For example, the terminal may perform a MAC reset operation per specific (sidelink) carrier in operation or configured / per specific (sidelink) BWP / per specific (sidelink) resource pool / per specific (sidelink) HARQ entity. For example, when a terminal declares a (sidelink) RLF or declares a (consistent) LBT failure or declares a beam failure or beam failure recovery fails on a specific (sidelink) carrier, the terminal may reset only some of the MAC operating procedures running on the corresponding carrier (e.g., the carrier that generated the (sidelink) RLF or the carrier that declared the (consistent) LBT failure or the carrier that declared the beam failure or the carrier that generated the beam failure recovery) (e.g., the terminal may perform a (partial) MAC reset of some MAC parameters related to some specific (sidelink) carrier).For example, the UE may perform a (partial) MAC reset operation of the operating or configured specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity, if the CBR measurement value of the specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity is measured to be higher (e.g., lower) than a CBR threshold associated with the specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity. For example, when the terminal receives a NACK feedback greater than a threshold value from a request from a higher layer (e.g., V2X layer or RRC layer) or from a specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity, or when DTX occurs for a preset threshold value, the terminal may perform a (partial) MAC reset operation of the operating or configured specific (sidelink) carrier / specific (sidelink) BWP / specific (sidelink) resource pool / specific (sidelink) HARQ entity.
[0279] For example, when a terminal performs a (partial) MAC reset, it may perform a (partial) MAC reset only for some of the following (sidelink) related MAC parameters.
[0280] For example, the terminal may stop (sidelink) DRX timers (e.g., onduration timer, inactivity timer, HARQ RTT timer, retransmission timer) (e.g., when the terminal is (partial) MAC reset).
[0281] For example, the terminal may cancel a triggered (sidelink) scheduling request procedure (e.g., upon a (partial) MAC reset).
[0282] For example, the terminal may cancel a triggered buffer status reporting procedure (e.g., upon a (partial) MAC reset).
[0283] For example, the terminal may cancel a triggered (sidelink) DRX command MAC CE transmission (e.g., upon a (partial) MAC reset).
[0284] For example, the terminal may cancel the triggered inter-UE coordination (IUC) information MAC CE transmission (e.g., upon a (partial) MAC reset).
[0285] For example, the terminal may cancel a triggered inter-UE coordination (IUC) request MAC CE transmission (e.g., upon a (partial) MAC reset).
[0286] For example, the terminal may cancel a triggered CSI reporting procedure (e.g., upon a (partial) MAC reset).
[0287] For example, the terminal may reset the DTX (e.g., numConsecutiveDTX) counting (e.g., upon a (partial) MAC reset).
[0288] For example, upon a (partial) MAC reset, the terminal may flush soft buffers for all (sidelink) processes for all TB(s) associated with the (sidelink) carrier.
[0289] For example, the terminal may cancel a triggered carrier (re-)selection procedure associated with a PC5-RRC connection (e.g., upon a (partial) MAC reset).
[0290] For example, if a (SL) RLF is declared for a specific PC5 RRC connection (e.g., or a unicast link), and a carrier (re-)selection procedure is triggered on the PC5 RRC connection (e.g., or a unicast link) where the (SL) RLF occurred, the terminal may cancel the triggered carrier (re-)selection procedure.
[0291] For example, if a MAC reset is triggered for a specific PC5 RRC connection (e.g., or a unicast link), the terminal may cancel the triggered carrier (re-)selection procedure if there is a triggered carrier (re-)selection procedure on the PC5 RRC connection (e.g., or a unicast link) for which the MAC reset was triggered.
[0292] For example, if an existing QoS flow (e.g., PFI and / or PQFI) service is replaced by a new QoS flow service (e.g., a new service with different PFI or PQFI) for a PC5 unicast link, the terminal may cancel, if any, triggered carrier (re-)selection procedure exists for an existing QoS flow (e.g., PFI and / or PQFI) service of the same (e.g., or current) PC5 RRC connection (e.g., or unicast link). For example, the terminal may cancel, if any, triggered carrier (re-)selection procedure associated to an existing QoS flow of the same PC5-RRC connection.
[0293] For example, when the AS layer of a terminal receives an indication of termination of a PC5 RRC connection or a PC5 unicast link from a higher layer (e.g., a V2X layer), the AS layer may cancel a “triggered carrier (re-)selection procedure” associated with the PC5 RRC connection or PC5 unicast link, if any.
[0294] For example, if an existing PC5 unicast service (e.g., or a PC5 RRC connection-related service) is changed to another PC5 unicast service (e.g., or a PC5 RRC connection-related service), the AS layer of the terminal may cancel the “triggered carrier (re-)selection procedure” associated with the existing PC5 unicast service (e.g., or a PC5 RRC connection-related service).
[0295] For example, if a transmitting terminal declares a PC5 RRC reconfiguration failure on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all configured available carriers) (e.g., the terminal may declare a PC5 RRC reconfiguration failure if it transmits an RRC reconfiguration (sidelink) (e.g., RRCReconfigurationSidelink) message on the (sidelink) carrier and does not receive an RRC reconfiguration complete (sidelink) (e.g., RRCReconfigurationCompleteSidelink) message or an RRC reconfiguration failure (sidelink) (e.g., RRCReconfigurationFailureSidelink) message until the T400 timer expires), it may trigger a carrier reselection procedure to replace the carrier on which the PC5 RRC reconfiguration failure occurred with another carrier. For example, if a (sidelink) PC5 RRC reconfiguration failure is declared on a specific (sidelink) carrier (e.g., one of the selected carriers, or all selected carriers, or all available carriers that have been configured), a carrier reselection procedure may be triggered to reselect a new carrier. For example, resources being used or selected on the carrier where the PC5 RRC reconfiguration failure occurred may be released and resources to be used on the new carrier may be reselected (e.g., the UE may trigger resource reselection to use the newly reselected resources on the newly selected carrier) and mapped to the newly selected carrier.For example, a transmitting terminal can select a newly selected carrier and new resources to use on that carrier, and transmit (sidelink) data using the selected carrier and selected resources.
[0296] For example, when (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity (re-)selection is triggered in multi-carrier operation, a terminal (e.g., a transmitting terminal) may select a sidelink carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity when HARQ feedback enabled data is available for a logical channel or when both HARQ feedback enabled data and HARQ feedback disabled data are available for a logical channel (e.g., where HARQ feedback enabled data and HARQ feedback disabled data may be mapped to the same (sidelink) unicast service or groupcast service or broadcast service).
[0297] When transmitting and receiving (sidelink) data in a multi-carrier, the terminal may consider only the (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity that allows (sidelink) data transmission, including the (SL) resource pool for which the PSFCH is set, as a (re-)selectable candidate (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity.
[0298] For example, if the CBR measurement value of all the (sidelink) data transmission allowed (sidelink) carriers / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities that include the (SL) resource pools for which PSFCH is configured is higher than the CBR threshold for a pre-configured data-related priority (e.g., (sidelink) priority), the terminal may keep the existing selected (sidelink) carrier / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities or (re-)select the (sidelink) carrier / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities by converting the attribute of the data to HARQ feedback disabled.
[0299] For example, in multi-carrier operation, if (SL) RLF is declared and (sidelink) carrier reselection is triggered, the UE (e.g., the transmitting UE) may reselect (sidelink) carrier(s) to use (e.g., preferentially) among the remaining (sidelink) carrier(s) except the (SL) RLF declared (sidelink) carrier(s) and regenerate (sidelink) grants for the reselected (sidelink) carrier(s). For example, if the (SL) RLF declared (sidelink) carrier is the only (e.g., remaining) (sidelink) carrier allowed to transmit the relevant packet / service, the UE may not trigger both (sidelink) carrier reselection and (sidelink) grant regeneration. For example, if the (sidelink) carrier for which (SL) RLF is declared is the only (e.g., remaining) (sidelink) carrier allowed to transmit the relevant packet / service, the terminal may regenerate the (sidelink) grant by triggering only (sidelink) grant regeneration without triggering (sidelink) carrier reselection.
[0300] For example, when a (SL) RLF occurs in a unicast session or PC5 RRC connection, a multi-carrier capable terminal may start a “resource reuse timer” and release the resources in use in all (sidelink) carriers / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities associated with the PC5 RRC connection where the (SL) RLF occurred. For example, the terminal may stop using (e.g., or terminate) any resource being used by any (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection on which the (SL) RLF occurred, or reserve any resource based on any (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection on which the (SL) RLF occurred, or stop any resource selection operation based on any (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection on which the (SL) RLF occurred, while the “resource reuse timer” is running.For example, when the “resource reuse timer” expires, the UE may resume using resources that are in use by all (sidelink) carriers / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities associated with the PC5 RRC connection where the (SL) RLF occurred or that it has reserved based on all (sidelink) carriers / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities associated with the PC5 RRC connection where the (SL) RLF occurred, or may restart resource (re-)selection operations based on all (sidelink) carriers / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities associated with the PC5 RRC connection.
[0301] For example, according to an embodiment of the present disclosure, when an (SL) RLF occurs in a unicast session or a PC5 RRC connection, a multi-carrier capable terminal may start a “resource reuse timer” and cancel (e.g., exclude) the use of resources in use by a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection in which the (SL) RLF occurred (e.g., a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity in which discontiuous transmission (DTX) occurs a threshold amount among multiple (sidelink) carriers / (SL) BWP / (sidelink) resource pools / (SL) HARQ entities associated with the PC5 RRC connection). For example, the terminal may stop using (e.g., cancel or exclude) resources that are in use by a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection on which the (SL) RLF occurred, or reserve resources based on the specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection on which the (SL) RLF occurred, or stop resource selection operation based on the specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection on which the (SL) RLF occurred, while the “resource reuse timer” is running.For example, when the “resource reuse timer” expires, the terminal may resume using resources that are in use by a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection where the (SL) RLF occurred or reserved based on a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection where the (SL) RLF occurred, or may restart resource (re-)selection operation based on a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection.
[0302] For example, according to an embodiment of the present disclosure, when an (SL) RLF occurs in a unicast session or a PC5 RRC connection, a multi-carrier supporting terminal excludes resources being used by a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity associated with the PC5 RRC connection where the (SL) RLF occurs (e.g., a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity in which discontiuous transmission (DTX) occurs as much as a threshold among a plurality of (sidelink) carriers / (SL) BWP / (sidelink) resource pools / (SL) HARQ entities associated with the PC5 RRC connection) (e.g., or a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity in which discontiuous transmission (DTX) occurs as much as a threshold). BWP / (sidelink) resource pool / (SL) HARQ entity-based resource (re-)selection operations can be excluded), a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity (e.g., associated with a PC5 RRC connection where (SL) RLF occurred) (e.g.,Among multiple (sidelink) carriers / (SL) BWPs / (sidelink) resource pools / (SL) HARQ entities associated with a PC5 RRC connection, resources from a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity) in which discontiuous transmission (DTX) does not occur as much as a threshold may be used. (For example, or a resource (re-)selection operation based on a specific (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity) in which discontiuous transmission (DTX) does not occur as much as a threshold may be performed.)
[0303] For example, the number of discontiuous transmission (DTX) thresholds can be set differently depending on (sidelink) priority or (sidelink) reliability or QoS profile or CBR or PQI or LCH or (sidelink) carrier / (SL) BWP / (sidelink) resource pool / (SL) HARQ entity.
[0304] For example, for a pair of source Layer-2 ID and destination Layer-2 ID, there may be multiple radio bearers. For example, for a pair of source Layer-2 ID and destination Layer-2 ID, there may be multiple radio bearers, each of which may correspond to a different (PC5) QoS level. For example, the AS layer may determine mapping of multiple (PC5) QoS flows to the same radio bearer based on the information provided above. For example, an L2 (Layer 2) link may be performed for all nearby terminals (UEs) identified by the destination Layer-2 ID. For example, in broadcast and groupcast mode communications, multiple carriers may be provided by the V2X layer for QoS flows for transmission. For example, the carrier(s) that may be used to transmit data may be provided by the V2X layer per QoS flow.
[0305] FIG. 14 illustrates an example of a relationship between a QoS flow and a carrier according to an embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure.
[0306] Referring to FIG. 14, for example, in carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. For example, a terminal (UE) may simultaneously receive or transmit on one or more component carriers (CCs) depending on the capabilities of the terminal (UE).
[0307] For example, (NR) (PC5) carrier aggregation operation may be supported. For example, (PC5) carrier aggregation (CA) operation may be supported for (NR-based) unicast, groupcast, and broadcast mode communications via a PC5 reference point. For example, the V2X layer may provide radio frequencies (e.g., carriers) depending on the configuration.
[0308] For example, the V2X layer may provide the (NR) (e)Tx profile to the AS layer, e.g., when providing other information such as radio frequency(s) (e.g., carrier(s)) for a (PC5) QoS flow for transmission. For example, when there is no (NR) (e)Tx profile mapped to be available for a (PC5) QoS flow for transmission, the V2X layer may not provide the NR (e)Tx profile to the AS layer.
[0309] For example, (for broadcast or groupcast), the AS layer can decide whether (NR) (PC5) CA operation is required, and for example, based on the NR (e)Tx profile, radio frequency(s) (e.g., carrier(s)) for the (PC5) QoS flow for transmission can be provided by the V2X layer.
[0310] For example, (for unicast), two terminals (UEs) can exchange (SL) CA related capabilities at the AS layer for (NR) (PC5) CA operation.
[0311] For example, the (NR) (e)Tx profile may be an enhanced transmission mechanism or format to be used by a terminal (UE) over (NR) (PC5) RAT (e.g., related to (PC5) carrier aggregation).
[0312] For example, carrier aggregation (CA) may be supported (in sidelink) (only for Mode 2 and / or V2X cases). For example, a UE (using Mode 2 resource allocation) may perform carrier (re)selection and select one or more carriers (to be used for sidelink).
[0313] For example, the carrier(s) that can be used to transmit data can be provided by the V2X layer per QoS flow. For example, the LCP can ensure that data from a sidelink radio bearer (SLRB) is transmitted on a carrier that all mapped QoS flows are allowed to use. For example, the carrier(s) that can be used to transmit data can be provided by the V2X layer per QoS flow, and the LCP can ensure that data from a sidelink radio bearer (SLRB) is transmitted on a carrier that all mapped QoS flows are allowed to use.
[0314] For example, in V2X (e.g., LTE), a terminal supporting multi-channel operation (e.g., multi-carrier operation or carrier aggregation) can select a specific (sidelink) carrier for transmitting (sidelink) data, select available resources on the selected (sidelink) carrier, and transmit (sidelink) data through the selected resources and carrier.
[0315] According to the present disclosure, carrier (re-)selection and / or resource (re-)selection (and / or unicast communication) operations of a terminal supporting multi-carrier (e.g., multi-carrier operation) may be proposed as follows.
[0316] According to the present disclosure, the CBR threshold(s) associated with (sidelink) carrier(s) / (SL) BWP(s) / (SL) HARQ entities can be set per priority or per QoS profile (e.g., PDB, reliability) or per SL Radio Bearer or per logical channel.
[0317] For example, as illustrated in FIG. 14, carrier #1 and carrier #2 may be provided for QoS flow #1. For example, as illustrated in FIG. 14, carrier #1 and carrier #2, which may be used to transmit data, may be provided by the V2X layer in QoS flow #1. For example, as illustrated in FIG. 14, carrier #2 and carrier #3 may be provided for QoS flow #2. For example, as illustrated in FIG. 14, carrier #2 and carrier #3, which may be used to transmit data, may be provided by the V2X layer in QoS flow #2. For example, as illustrated in FIG. 14, carrier #3 may be provided for QoS flow #3. For example, as illustrated in FIG. 14, carrier #3, which may be used to transmit data, may be provided by the V2X layer in QoS flow #3. For example, FIG. 14 illustrates only QoS flow #1, QoS flow #2, and QoS flow #3, but is not limited thereto. For example, FIG. 14 illustrates only carrier #1, carrier #2, and carrier #3, but is not limited thereto.
[0318] By dedicating carriers to specific QoS flows, the network can optimize reliability and efficiency. This configuration can minimize the risk of congestion and interference between different types of data flows, thereby improving reliability and network efficiency. By allocating carriers based on the specific needs of each QoS flow, the system can ensure that resources are not wasted on low-priority data that does not require high bandwidth or low latency. This targeted allocation can help manage scarce resources more efficiently and enable the network to support greater data transmission capacity without additional frequency or bandwidth.
[0319] For example, when the V2X layer provides multiple carriers to the AS in the QoS flow to carrier mapping information (for groupcast and broadcast), the TX profile can be used to indicate whether the transmission corresponding to the QoS flow is backward compatible or not. When backward compatibility is required, the TX UE can use only the legacy carrier without PDCP duplication, or at least use PDCP duplication together with the legacy carrier.
[0320] For example, carrier selection can be performed at the MAC layer (for groupcast and broadcast), and can be based on the CBR and logical channel priorities of the configured carriers.
[0321] For example, (sidelink) packet duplication may be supported for (sidelink) CA and may be performed at the PDCP (packet data convergence protocol) layer. For example, for (sidelink) packet duplication for transmission, a PDCP (packet data convergence protocol) PDU (protocol data unit) may be duplicated within a PDCP (packet data convergence protocol) entity. For example, duplicated PDCP (packet data convergence protocol) PDUs of the same PDCP (packet data convergence protocol) entity may be submitted to two different RLC entities and may be associated with two different (sidelink) logical channels, respectively. For example, duplicated PDCP (packet data convergence protocol) PDUs (protocol data units) of the same PDCP (packet data convergence protocol) entity may only be allowed to be transmitted on different (sidelink) carriers. For example, for a (SL) DRB (data radio bearer), (sidelink) packet duplication may be (pre-)configured if the TX profile indicates that backward compatibility is required.For example, for a (SL) DRB (data radio bearer), if the TX profile indicates that backward compatibility is not required, (sidelink) packet duplication may be (pre-)configured. For example, for a (SL) DRB (data radio bearer), if the TX profile indicates that backward compatibility is required, (sidelink) packet duplication may be determined by the TX UE. For example, for an applicable (SL) SRB (signaling radio bearer), whether to use duplication (e.g., (sidelink) packet duplication) may be determined by the TX UE. For example, (in unicast), a TX terminal (UE) can transmit duplication (e.g., (sidelink) packet duplication) settings to a RX terminal (UE) in PC5-RRC.
[0322] For example, for a pair of source Layer-2 ID and destination Layer-2 ID, there may be multiple radio bearers. For example, for a pair of source Layer-2 ID and destination Layer-2 ID, there may be multiple radio bearers, each of which may correspond to a different (PC5) QoS level. For example, the AS layer may determine mapping of multiple (PC5) QoS flows to the same radio bearer based on the information provided above. For example, an L2 (Layer 2) link may be performed for all nearby terminals (UEs) identified by the destination Layer-2 ID. For example, in broadcast and groupcast mode communications, multiple carriers may be provided by the V2X layer for QoS flows for transmission. For example, the carrier(s) that may be used to transmit data may be provided by the V2X layer per QoS flow.
[0323] FIG. 15 illustrates an example of a procedure for providing a QoS flow according to an embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.
[0324] Referring to FIG. 15, for example, in carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. For example, a terminal (UE) may simultaneously receive or transmit on one or more component carriers (CCs) depending on the capabilities of the terminal (UE).
[0325] For example, (NR) (PC5) carrier aggregation operation may be supported. For example, (PC5) carrier aggregation (CA) operation may be supported for (NR-based) unicast, groupcast, and broadcast mode communications via a PC5 reference point. For example, the V2X layer may provide radio frequencies (e.g., carriers) depending on the configuration.
[0326] For example, the V2X layer may provide the (NR) (e)Tx profile to the AS layer, e.g., when providing other information such as radio frequency(s) (e.g., carrier(s)) for a (PC5) QoS flow for transmission. For example, when there is no (NR) (e)Tx profile mapped to be available for a (PC5) QoS flow for transmission, the V2X layer may not provide the NR (e)Tx profile to the AS layer.
[0327] For example, (for broadcast or groupcast), the AS layer can decide whether (NR) (PC5) CA operation is required, and for example, based on the NR (e)Tx profile, radio frequency(s) (e.g., carrier(s)) for the (PC5) QoS flow for transmission can be provided by the V2X layer.
[0328] For example, (for unicast), two terminals (UEs) can exchange (SL) CA related capabilities at the AS layer for (NR) (PC5) CA operation.
[0329] For example, the (NR) (e)Tx profile may be an enhanced transmission mechanism or format to be used by a terminal (UE) over (NR) (PC5) RAT (e.g., related to (PC5) carrier aggregation).
[0330] For example, carrier aggregation (CA) may be supported (in sidelink) (only for Mode 2 and / or V2X cases). For example, a UE (using Mode 2 resource allocation) may perform carrier (re)selection and select one or more carriers (to be used for sidelink).
[0331] For example, the carrier(s) that can be used to transmit data can be provided by the V2X layer per QoS flow. For example, the LCP can ensure that data from a sidelink radio bearer (SLRB) is transmitted on a carrier that all mapped QoS flows are allowed to use. For example, the carrier(s) that can be used to transmit data can be provided by the V2X layer per QoS flow, and the LCP can ensure that data from a sidelink radio bearer (SLRB) is transmitted on a carrier that all mapped QoS flows are allowed to use.
[0332] For example, in V2X (e.g., LTE), a terminal supporting multi-channel operation (e.g., multi-carrier operation or carrier aggregation) can select a specific (sidelink) carrier for transmitting (sidelink) data, select available resources on the selected (sidelink) carrier, and transmit (sidelink) data through the selected resources and carrier.
[0333] According to the present disclosure, carrier (re-)selection and / or resource (re-)selection (and / or unicast communication) operations of a terminal supporting multi-carrier (e.g., multi-carrier operation) may be proposed as follows.
[0334] According to the present disclosure, the CBR threshold(s) associated with (sidelink) carrier(s) / (SL) BWP(s) / (SL) HARQ entities can be set per priority or per QoS profile (e.g., PDB, reliability) or per SL Radio Bearer or per logical channel.
[0335] For example, in step S1510, the V2X layer (of the TX UE) may provide QoS-specific carrier(s) information to the AS layer (of the TX UE). For example, in step S1510, carrier(s) that can be used to transmit data may be provided to the AS layer (of the TX UE) by the V2X layer (of the TX UE) per QoS flow. For example, in step S1520, the AS layer (layer) of the TX UE may transmit data to the RX UE(s). For example, in step S1520, the AS layer (layer) of the TX UE may transmit data to the RX UE(s) based on the carrier(s) provided by the V2X layer per QoS flow.
[0336] By dedicating carriers to specific QoS flows, the network can optimize reliability and efficiency. This configuration can minimize the risk of congestion and interference between different types of data flows, thereby improving reliability and network efficiency. By allocating carriers based on the specific needs of each QoS flow, the system can ensure that resources are not wasted on low-priority data that does not require high bandwidth or low latency. This targeted allocation can help manage scarce resources more efficiently and enable the network to support greater data transmission capacity without additional frequency or bandwidth.
[0337] For example, when the V2X layer provides multiple carriers to the AS in the QoS flow to carrier mapping information (for groupcast and broadcast), the TX profile can be used to indicate whether the transmission corresponding to the QoS flow is backward compatible or not. When backward compatibility is required, the TX UE can use only the legacy carrier without PDCP duplication, or at least use PDCP duplication together with the legacy carrier.
[0338] For example, carrier selection can be performed at the MAC layer (for groupcast and broadcast), and can be based on the CBR and logical channel priorities of the configured carriers.
[0339] For example, (sidelink) packet duplication may be supported for (sidelink) CA and may be performed at the PDCP (packet data convergence protocol) layer. For example, for (sidelink) packet duplication for transmission, a PDCP (packet data convergence protocol) PDU (protocol data unit) may be duplicated within a PDCP (packet data convergence protocol) entity. For example, duplicated PDCP (packet data convergence protocol) PDUs of the same PDCP (packet data convergence protocol) entity may be submitted to two different RLC entities and may be associated with two different (sidelink) logical channels, respectively. For example, duplicated PDCP (packet data convergence protocol) PDUs (protocol data units) of the same PDCP (packet data convergence protocol) entity may only be allowed to be transmitted on different (sidelink) carriers. For example, for a (SL) DRB (data radio bearer), (sidelink) packet duplication may be (pre-)configured if the TX profile indicates that backward compatibility is required.For example, for a (SL) DRB (data radio bearer), if the TX profile indicates that backward compatibility is not required, (sidelink) packet duplication may be (pre-)configured. For example, for a (SL) DRB (data radio bearer), if the TX profile indicates that backward compatibility is required, (sidelink) packet duplication may be determined by the TX UE. For example, for an applicable (SL) SRB (signaling radio bearer), whether to use duplication (e.g., (sidelink) packet duplication) may be determined by the TX UE. For example, (in unicast), a TX terminal (UE) can transmit duplication (e.g., (sidelink) packet duplication) settings to a RX terminal (UE) in PC5-RRC.
[0340] As wireless communication technology evolves, network demands increase. By reselecting carriers based on changes in QoS requirements, systems can dynamically adapt to varying network conditions (such as congestion or signal degradation). This can improve overall network efficiency by ensuring that transmissions always occur on the most optimal path.
[0341] FIG. 16 illustrates an example of a procedure related to changing a QoS flow according to an embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure.
[0342] Referring to FIG. 16, for example, in step S1610, all existing PC5 QoS flows can be changed. For example, in order to change all existing PC5 QoS flows, the V2X layer can provide information about the PC5 QoS flows to the AS layer. For example, in order to change all existing PC5 QoS flows, the V2X layer can provide the AS layer with a PFI for the PC5 QoS flows. For example, in order to change all existing PC5 QoS flows, the V2X layer can provide the AS layer with corresponding PC5 QoS parameters for the PC5 QoS flows. For example, to modify all existing PC5 QoS flows, the V2X layer may provide the AS layer with the source / destination Layer-2 ID for broadcast and groupcast mode communication for the PC5 QoS flows or the PC5 link identifier for unicast.
[0343] For example, in step S1620, the MAC entity may trigger a TX carrier (re-)selection procedure. For example, if multiple carrier frequencies are set, the MAC entity may trigger a TX carrier (re-)selection procedure.
[0344] For example, TX carrier (re-)selection may be performed.
[0345] For example, if a CBR measurement result is available, the MAC entity can consider the CBR of the carrier as being measured by the lower layer. For example, if a CBR measurement result is available, the MAC entity can consider the CBR of the carrier as being measured by the lower layer. For example, if a CBR measurement result is not available, the MAC entity can consider the CBR of the carrier as being set by the corresponding index (e.g., (sl-)defaultTxConfigIndex) from the upper layer.
[0346] For example, if TX carrier (re)selection is triggered for a (sidelink) process, the MAC entity may consider a carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel. For example, if TX carrier (re)selection is triggered for a (sidelink) process, the MAC entity may consider a carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel if a (sidelink) grant has not been selected on all allowed carriers for the (sidelink) logical channel on which data is available as instructed by the upper layers. For example, if TX carrier (re)selection is triggered for a (sidelink) process, for each carrier configured by the upper layers associated with the concerned (sidelink) logical channel, the MAC entity may consider a carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel. For example, if TX carrier (re)selection is triggered for a (sidelink) process, if the CBR of the carrier is lower than a CBR threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqReselection), the MAC entity may consider the carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel. For example, if TX carrier (re)selection is triggered for a (sidelink) process, taking into account HARQ feedback enablement for the (sidelink) logical channel (e.g., (sl-)HARQ-FeedbackEnabled), the MAC entity may consider the carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel.For example, if TX carrier (re)selection is triggered for a (sidelink) process, and if multiple resource pools are configured on the carrier, it is up to the UE implementation which particular resource pool is used to determine the CBR of this carrier, and the MAC entity may consider the carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel. For example, if TX carrier (re)selection is triggered for a (sidelink) process, and if multiple resource pools are configured on the carrier, it is up to the UE implementation which particular resource pool is used to determine the CBR of this carrier, and the MAC entity may consider the carrier as a candidate carrier for TX carrier (re)selection for the concerned (sidelink) logical channel, taking into account HARQ feedback enable (e.g., (sl-)HARQ-FeedbackEnabled) for the (sidelink) logical channel.For example, when a TX carrier (re)selection is triggered for a (sidelink) process, if a (sidelink) grant is not selected on all allowed carriers for a (sidelink) logical channel for which data is available as instructed by upper layers, then for each carrier configured by upper layers associated with the concerned (sidelink) logical channel, if the CBR of the carrier is lower than a CBR threshold (e.g., (sl-)threshCBR-FreqReselection) associated with the priority of the (sidelink) logical channel, the MAC entity, taking into account HARQ feedback enablement for the (sidelink) logical channel (e.g., (sl-)HARQ-FeedbackEnabled), determines which particular resource pool is used to determine the CBR of this carrier if multiple resource pools are configured on the carrier, and it is up to the UE implementation which specific resource pool is used to determine the CBR of this carrier, and the MAC entity determines whether the carrier is selected for the TX carrier for the concerned (sidelink) logical channel. It can be considered as a candidate carrier for (re)selection.
[0347] For example, if TX carrier (re)selection is triggered for a (sidelink) process, the MAC entity may select a carrier and a pool of associated (e.g., carrier-associated) resources. For example, if TX carrier (re)selection is triggered for a (sidelink) process, if at least one (sidelink) grant has been selected on all allowed carriers for data-available (sidelink) logical channels as indicated by higher layers (e.g., if “no (sidelink) grant has been selected on all allowed carriers for data-available (sidelink) logical channels as indicated by higher layers”), the MAC entity may select a carrier and a pool of associated (e.g., carrier-associated) resources. For example, if a TX carrier (re)selection is triggered for a (sidelink) process, then for each (sidelink) logical channel allowed on the carrier for which data is available and for which TX carrier (re)selection is triggered, the MAC entity may select a carrier and a pool of associated (e.g., carrier-associated) resources, if any. For example, if a TX carrier (re)selection is triggered for a (sidelink) process, then for each (sidelink) logical channel allowed on the carrier for which data is available and for which TX carrier (re)selection is triggered, the MAC entity may select a carrier and a pool of associated (e.g., carrier-associated) resources, if any, if the CBR of the carrier is lower than a threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqKeeping).For example, when TX carrier (re)selection is triggered for a (sidelink) process, for each (sidelink) logical channel allowed on the carrier for which data is available and for which TX carrier (re)selection is triggered, the MAC entity, if any, may select a pool of resources from the carrier and its associated (e.g., associated with the carrier) resources, if the CBR of the carrier is lower than a threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqKeeping). For example, if TX carrier (re)selection is triggered for a (sidelink) process, if at least one (sidelink) grant has been selected on all allowed carriers for (sidelink) logical channels on which data is available as indicated by upper layers (e.g., if “no (sidelink) grant has been selected on all allowed carriers for (sidelink) logical channels on which data is available as indicated by upper layers”), then for each allowed (sidelink) logical channel on which data is available and for which TX carrier (re)selection is triggered, if the CBR of the carrier, if any, is lower than a threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqKeeping), then the MAC entity, if any, is assigned to the carrier and its associated (e.g., associated with the carrier) You can choose a pool of resources.
[0348] For example, if TX carrier (re)selection is triggered for a (sidelink) process, the MAC entity may consider, for each carrier configured by the upper layers for which (sidelink) logical channels are allowed, a carrier as a candidate carrier for TX carrier (re)selection. For example, if TX carrier (re)selection is triggered for a (sidelink) process, if at least one (sidelink) grant has been selected on all allowed carriers for data-available (sidelink) logical channels as indicated by the upper layers (e.g., if no (sidelink) grant has been selected on all allowed carriers for data-available (sidelink) logical channels as indicated by the upper layers) (else), the MAC entity may consider, for each carrier configured by the upper layers for which (sidelink) logical channels are allowed, a carrier as a candidate carrier for TX carrier (re)selection. For example, when a TX carrier (re)selection is triggered for a (sidelink) process, if data is not available, or there is no (sidelink) logical channel allowed on the carrier for which a TX carrier (re)selection is triggered, or for each (sidelink) logical channel allowed on the carrier for which data is available and a TX carrier (re)selection is triggered, if any, then the CBR of the carrier is higher than a threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqKeeping) or equal to a threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqKeeping) (e.g., "data is available and a TX carrier (re)selection is triggered, for each (sidelink) logical channel allowed on the carrier for which a TX carrier (re)selection is triggered, if any,For each (sidelink) logical channel allowed on the carrier for which data is available and TX carrier (re)selection is triggered, if the CBR of the carrier is lower than a threshold (e.g., (sl-)threshCBR-FreqKeeping), then the MAC entity may, for each carrier configured by the upper layer for which (sidelink) logical channels are allowed, consider the carrier as a candidate carrier for TX carrier (re)selection. For example, if TX carrier (re)selection is triggered for the (sidelink) process, then for each carrier configured by the upper layer for which (sidelink) logical channels are allowed, the MAC entity may, for each carrier configured by the upper layer for which (sidelink) logical channels are allowed, consider the carrier as a candidate carrier for TX carrier (re)selection. For example, if TX carrier (re)selection is triggered for the (sidelink) process, then if the CBR of the carrier is lower than a threshold (e.g., (sl-)threshCBR-FreqKeeping) for the (sidelink) logical channels, then For each carrier configured by the upper layer for which the (sidelink) logical channel is allowed, the MAC entity may consider the carrier as a candidate carrier for TX carrier (re)selection if the CBR of the carrier is lower than a threshold associated with the priority of the channel (e.g., (sl-)threshCBR-FreqReselection). For example, when TX carrier (re)selection is triggered for the (sidelink) process, for each carrier configured by the upper layer for which the (sidelink) logical channel is allowed, the MAC entity may consider the carrier as a candidate carrier for TX carrier (re)selection if the CBR of the carrier is lower than a threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqReselection). For example,If TX carrier (re)selection is triggered for a (sidelink) process, if at least one (sidelink) grant has been selected on all allowed carriers for (sidelink) logical channels on which data is available as indicated by upper layers (e.g., if “no (sidelink) grant has been selected on all allowed carriers for (sidelink) logical channels on which data is available as indicated by upper layers”), then TX carrier (re)selection is triggered for a (sidelink) process, if data is not available, or there are no (sidelink) logical channels allowed on the carrier for which TX carrier (re)selection is triggered, or for each (sidelink) logical channel on the carrier for which data is available and TX carrier (re)selection is triggered, if any, the CBR of the carrier is higher than a threshold (e.g., (sl-)threshCBR-FreqKeeping) associated with the priority of the (sidelink) logical channel and If the associated threshold (e.g., (sl-)threshCBR-FreqKeeping) is equal to (e.g., “for each (sidelink) logical channel allowed on the carrier for which data is available and TX carrier (re)selection is triggered, if the carrier’s CBR is lower than the threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqKeeping)”, then (else for “for each (sidelink) logical channel allowed on the carrier for which data is available and TX carrier (re)selection is triggered, if any”), if the carrier’s CBR is lower than the threshold associated with the priority of the (sidelink) logical channel (e.g., (sl-)threshCBR-FreqReselection)For each carrier configured by the upper layer for which (sidelink) logical channels are allowed, if the CBR of the carrier is lower than a threshold value (e.g., (sl-)threshCBR-FreqReselection) associated with the priority of the (sidelink) logical channel, the MAC entity may, for each carrier configured by the upper layer for which (sidelink) logical channels are allowed, consider the carrier as a candidate carrier for TX carrier (re)selection.
[0349] For example, the MAC entity may select one or more carriers from among the candidate carriers. For example, the MAC entity may select one or more carriers and a pool of associated (e.g., associated) resources from among the candidate carriers. For example, the MAC entity may select one or more carriers from among the candidate carriers in order of increasing CBR starting from the lowest CBR. For example, the MAC entity may select one or more carriers from among the candidate carriers and a pool of associated (e.g., associated) resources from among the candidate carriers in order of increasing CBR starting from the lowest CBR. For example, if one or more carriers are considered as candidate carriers for TX carrier (re)selection, the MAC entity may select one or more carriers from among the candidate carriers and a pool of associated (e.g., associated) resources from among the candidate carriers in order of increasing CBR starting from the lowest CBR. For example, if TX carrier (re)selection is triggered for each (sidelink) logical channel on which data is allowed on the available carrier, the MAC entity may select one or more carriers and a pool of associated (e.g., associated with one or more carriers) resources from among the candidate carriers in increasing order of CBR, starting from the lowest.For example, if more than one carrier is considered as a candidate carrier for TX carrier (re)selection, and if TX carrier (re)selection is triggered for each (sidelink) logical channel allowed on the data-available carrier, the MAC entity may select one or more carriers and a pool of associated (e.g., associated with one or more carriers) resources from among the candidate carriers in order of increasing CBR, starting with the lowest CBR.
[0350] For example, the MAC entity can select a pool of resources (e.g., one pool of resources) for which PSFCH resources are configured from among the pools of resources. For example, if enable is set for a (sidelink) logical channel, the MAC entity can select a pool of resources (e.g., one pool of resources) for which PSFCH resources are configured from among the pools of resources. For example, if enable is set for a (sidelink) logical channel, the MAC entity can select a pool of resources (e.g., one pool of resources) for which PSFCH resources are configured from among the pools of resources, excluding the pools in the information related to discovery of resource pools (e.g., (sl-)BWP-DiscPoolConfig or (sl-)BWP-DiscPoolConfigCommon), if configured. For example, the MAC entity may select one or more carriers and a pool of resources associated with them (e.g., associated with one or more carriers) from among the candidate carriers, and if the enable is set for the (sidelink) logical channel, the MAC entity may select a pool of resources for which PSFCH resources are configured (e.g., one of the pools of resources), excluding the pools in the information related to discovery of resource pools (e.g., (sl-)BWP-DiscPoolConfig or (sl-)BWP-DiscPoolConfigCommon), if configured.
[0351] For example, a MAC entity may select any pool of resources from among the pools of resources. For example, if disable is set for a (sidelink) logical channel, the MAC entity may select any pool of resources from among the pools of resources. For example, if disable is set for a (sidelink) logical channel, the MAC entity may select any pool of resources from among the pools of resources, excluding pools in the information related to discovery of resource pools (e.g., (sl-)BWP-DiscPoolConfig or (sl-)BWP-DiscPoolConfigCommon), if set. For example, a MAC entity may select one or more carriers and a pool of resources associated with them (e.g., associated with one or more carriers) from among the candidate carriers, and if a disable is set for a (sidelink) logical channel, the MAC entity may select all pools of resources from among the pools of resources, excluding pools in the information related to discovery of resource pools (e.g., (sl-)BWP-DiscPoolConfig or (sl-)BWP-DiscPoolConfigCommon), if set.
[0352] For example, it may be left to the UE implementation to decide how many carriers to select based on UE performance.
[0353] For example, it may be left to the UE implementation to determine which (sidelink) logical channel is allowed on the carrier for which data is available and TX carrier (re)selection is triggered.
[0354] For example, it may be left to the UE implementation to decide whether the resource pool for CBR measurements is reused as the resource pool for (SL) grant generation.
[0355] For example, in V2X (e.g., LTE), a terminal supporting multi-channel operation (e.g., multi-carrier operation or carrier aggregation) can select a specific (sidelink) carrier for transmitting (sidelink) data, select available resources on the selected (sidelink) carrier, and transmit (sidelink) data through the selected resources and carrier.
[0356] For example, if a carrier update (e.g., and / or service update / change and / or QoS Flow (e.g., PFI or PQFI) update / change) occurs for a specific sidelink session (e.g., PC5 Unicast Session / link or groupcast session or broadcast session) at a higher layer (e.g., V2X layer or PC5 layer or RRC layer), resource reselection and carrier reselection may be triggered for the sidelink session (e.g., PC5 Unicast Session / link or groupcast session or broadcast session) at the AS layer (e.g., or the AS layer action may be interpreted by the UE as triggering resource reselection and carrier reselection). For example, when a carrier update (e.g., and / or service update / change and / or QoS Flow (e.g., PFI or PQFI) update / change) occurs for a specific sidelink session (e.g., PC5 Unicast Session / link or groupcast session or broadcast session) at a higher layer (e.g., V2X layer or PC5 layer or RRC layer), the sidelink grant allocated or created or selected in the existing carrier (e.g., and / or existing service or existing QoS Flow (e.g., PFI or PQFI)) for the sidelink session (e.g., PC5 Unicast Session / link or groupcast session or broadcast session) may be cleared at the AS layer (e.g., or the AS layer action may be interpreted as the UE clearing the allocated or created or selected sidelink grant).For example, if a carrier update (e.g., and / or service update / change and / or QoS Flow (e.g., PFI or PQFI) update / change) for a specific sidelink session (e.g., PC5 Unicast Session / link or groupcast session or broadcast session) occurs at a higher layer (e.g., V2X layer or PC5 layer or RRC layer), the existing carrier for the sidelink session (e.g., PC5 Unicast Session / link or groupcast session or broadcast session) may be released at the AS layer (or the AS layer action may be interpreted as the UE releasing the existing carrier).
[0357] For example, in multi-carrier operation, if (SL) RLF is declared and (sidelink) carrier reselection is triggered, the UE (e.g., the transmitting UE) may reselect (sidelink) carrier(s) to use (e.g., preferentially) among the remaining (sidelink) carrier(s) except the (SL) RLF declared (sidelink) carrier(s) and regenerate (sidelink) grants for the reselected (sidelink) carrier(s). For example, if the (SL) RLF declared (sidelink) carrier is the only (e.g., remaining) (sidelink) carrier allowed to transmit the relevant packet / service, the UE may not trigger both (sidelink) carrier reselection and (sidelink) grant regeneration. For example, if the (sidelink) carrier for which (SL) RLF is declared is the only (e.g., remaining) (sidelink) carrier allowed to transmit the relevant packet / service, the terminal may regenerate the (sidelink) grant by triggering only (sidelink) grant regeneration without triggering (sidelink) carrier reselection.
[0358] As wireless communication technologies evolve, network requirements increase. Triggering carrier reselection based on changes in QoS flows provides a framework for adapting to future technologies and requirements, ensuring the network is robust and capable of supporting new services and applications. Triggering carrier reselection based on changes in QoS flows allows for more granular management of QoS parameters. Different types of data flows (e.g., video streaming, web browsing) may have distinct QoS requirements. Reselecting carriers based on these requirements can significantly improve the user experience by ensuring that high-priority traffic, such as real-time video, receives the necessary bandwidth and low latency.
[0359] For example, resource reselection and carrier reselection may be triggered even if only some resources are reselected for a sidelink grant, or the UE may trigger resource reselection and carrier reselection only if the sidelink grant (e.g., all associated resources) is cleared and reselected.
[0360] For example, the UE may trigger resource reselection and carrier reselection only when a preset number of the above events (e.g., only some resources in a sidelink grant are reselected, or a sidelink grant (e.g., all related resources) is cleared and reselected) occurs (e.g., and / or a CBR above a preset threshold level is measured on the existing carrier and / or a candidate carrier CBR value is smaller than the existing carrier CBR value by a preset offset or more).
[0361] For example, the above rule may be applied only to sidelink grants related to aperiodic resource reservations. For example, the above rule may not be limited to sidelink grants related to aperiodic resource reservations.
[0362] The operation of the present disclosure can be applied to all (sidelink) unicast / groupcast / broadcast operations.
[0363] In embodiments of the present disclosure, “channel” may be replaced with “carrier” or “a set of resource blocks of a specific carrier” or “band”.
[0364] In the present disclosure, multi-carrier can be extended to be interpreted as carrier aggregation (CA).
[0365] In the present disclosure, sidelink multi-carrier can be extended and interpreted as sidelink carrier aggregation (CA). In the present disclosure, sidelink carrier aggregation (CA) can be extended and interpreted as sidelink multi-carrier.
[0366] The (sidelink) resource pool (e.g., or (sidelink) HARQ entity) exemplified in the present disclosure may be interpreted as a sidelink resource pool (e.g., or (sidelink) HARQ entity) for a specific sidelink carrier.
[0367] In order to ensure HARQ feedback enabled MAC PDU transmission in (sidelink) multi-carrier operation, the base station may expect the terminal to configure PSFCH resources in an exceptional pool (e.g., a normal TX pool or a normal RX pool) on at least one (sidelink) carrier / SL BWP / SL HARQ entity among multiple (sidelink) carriers / SL BWP / SL HARQ entities to which the same unicast service or the same source layer-2 ID / destination layer-2 ID pair (e.g., or the same groupcast / broadcast service or the same destination layer-2 ID) are mapped. The present disclosure is not limited thereto.
[0368] When a base station forms a unicast session, groupcast, or broadcast session that performs HARQ feedback enabled MAC PDU transmission, the base station may restrict the terminal to include at least one carrier that includes an exceptional pool (e.g., a normal TX pool or a normal RX pool) in which the PSFCH resource is set. The present disclosure is not limited thereto.
[0369] When a terminal forms a unicast session, groupcast, or broadcast session that performs HARQ feedback enabled MAC PDU transmission, it may be restricted to include at least one carrier that includes an exceptional pool (e.g., a normal TX pool or a normal RX pool) in which PSFCH resources are configured. The present disclosure is not limited thereto.
[0370] In the present disclosure, the CBR threshold(s) associated with (sidelink) carrier(s) / (SL) BWP(s) / (SL) HARQ entities can be set per priority or per QoS profile (e.g., PDB, reliability) or per SL Radio Bearer or per logical channel.
[0371] In the present disclosure, a (sidelink) carrier can be extended to be interpreted as a (sidelink) BWP or a (sidelink) HARQ entity.
[0372] In the present disclosure, a (sidelink) carrier, a (sidelink) BWP, a (SL) resource pool, or a (sidelink) HARQ entity may be substituted for each other. For example, a (sidelink) carrier, a (sidelink) BWP, a (SL) resource pool, or a (sidelink) HARQ entity may be applied as substitutes for each other.
[0373] In an embodiment of the present disclosure, a unicast service may be interpreted as a pair of a source layer-2 ID and a destination layer-2 ID (Source Layer-2 ID and Destination Layer-2 ID pair).
[0374] In embodiments of the present disclosure, the groupcast service may be interpreted as a Groupcast Destination Layer-2 ID.
[0375] In embodiments of the present disclosure, a broadcast service may be interpreted as a Broadcast Destination Layer-2 ID.
[0376] In embodiments of the present disclosure, “carrier” may be replaced with “band” or “resource block set of a specific carrier” or “resource pool set of a specific carrier” or “channel”.
[0377] In embodiments of the present disclosure, the beam management operation may be interpreted as being replaced with beam selection or spatial filter selection or beam pairing or spatial filter pairing or beam failure recovery (BFR) or spatial filter recovery or beam sweeping or spatial filter sweeping or beam switching or spatial filter sweeping or reference signal (RS) resource measurement or reference signal (RS) resource measurement report operation or beam report or spatial filter report.
[0378] In embodiments of the present disclosure, the beam may be interpreted as being replaced with a transmitting beam and / or a receiving beam.
[0379] In embodiments of the present disclosure, the beam may be interpreted as being replaced by an RS or RS resource or a spatial filter resource.
[0380] In the embodiments of the present disclosure, RS may be interpreted as being replaced with an RS resource or a spatial filter resource.
[0381] In the embodiments of the present disclosure, the transmitting terminal may be interpreted as a terminal transmitting a beam, a terminal transmitting a beam RS, a terminal transmitting a beam RS resource, etc.
[0382] In the embodiment of the present disclosure, the receiving terminal may be interpreted as a terminal that receives a beam, a terminal that receives a beam RS, a terminal that receives a beam RS resource, etc.
[0383] In an embodiment of the present disclosure, the transmission beam or reception beam information transmitted and received by the terminal may be interpreted as being replaced with resource information of a reference signal (RS) associated with the transmission beam and resource information of a reference signal (RS) associated with the reception beam.
[0384] In an embodiment of the present disclosure, the DCR (direct communication request) message and / or the DCA (direct communication accept) message may be interpreted as being replaced with a PC5-S (sidelink) DCR message and / or a PC5-S (sidelink) DCA message.
[0385] Although the embodiments of the present disclosure have exemplified (SL) CSI-RS as an RS for beam management, the present disclosure is not limited thereto. The proposed operations of the present disclosure can be equally extended and applied to cases where a reference signal (RS) other than (SL) CSI-RS (e.g., (sidelink) SSB) is used as an RS for beam management.
[0386] Although the embodiments of the present disclosure have exemplified RSRP as an RS measurement for beam management, the present disclosure is not limited thereto. The proposed operations of the present disclosure can be equally extended and applied to other measurement operations (e.g., RSSI (received signal strength indicator) measurement, etc.) as RS measurement for beam management.
[0387] In embodiments of the present disclosure, spatial settings and / or transmission configuration indicator (TCI) information and / or quasi-colocation (QCL) information and / or beams may refer to each other and / or may be interpreted as being replaced with beam-related information, beam direction, spatial domain transmission filter and / or spatial domain reception filter. For example, the spatial domain transmission filter may be a spatial domain TX filter. For example, the spatial domain reception filter may be a spatial domain RX filter.
[0388] In embodiments of the present disclosure, the beam may be interpreted as being replaced by a spatial filter.
[0389] In embodiments of the present disclosure, the transmit / transmit beam may be interpreted as being replaced by a spatial transmission (TX) filter or a spatial domain transmission (TX) filter.
[0390] In embodiments of the present disclosure, a beam may be interpreted as a transmit beam or a receive beam or a spatial filter or a spatial transmission (TX) filter or a spatial domain transmission (TX) filter or a spatial reception (RX) filter or a spatial domain reception (RX) filter.
[0391] In embodiments of the present disclosure, the reception beam may be interpreted as being replaced by a spatial reception (RX) filter or a spatial domain reception (RX) filter.
[0392] In an embodiment of the present disclosure, the fact that the spatial setting information (or beam information) for transmission is the same may mean that the spatial domain TX filter of the terminal is the same for two different transmission signals. In an embodiment of the present disclosure, the fact that the spatial setting information (or beam information) for reception is the same may mean that the two different reception signals are in a QCL 'TypeD' relationship and / or use the same spatial RX parameters.
[0393] For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (and / or independently and / or differently) according to the SL-CAPC (Channel Access Priority Class). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (and / or independently and / or differently) according to the SL-LBT type (e.g., Type 1 LBT, Type 2A LBT, Type 2B LTB, or Type 2C LBT). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (and / or independently and / or differently) according to the FBE (Frame Based LBT). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or the relevant parameters (e.g., thresholds) may be set specifically (and / or independently and / or differently) depending on whether LBE (Load Based LBT) is applied.
[0394] For example, whether (some) of the proposed schemes / rules of the present disclosure are applied and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set depending on whether LBT succeeds / fails, LBT-related energy detection levels, sidelink channels (PSCCH / PSSCH, PSFCH, SL-SSB (or S-SSB)), whether MCSt (Multi-Consecutive Slot Transmission) is applied, whether multi-PSFCH occasions are applied, resource order / location for setting MCSt, whether multiple starting points are set within one slot, whether the 1st starting point (or 2nd starting point) is applied, etc.
[0395] Whether (some) of the proposed methods / rules of the present disclosure are applied and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set according to whether LBT is successful / failure, LBT-related energy detection level, sidelink channel (PSCCH / PSSCH, PSFCH, SL-SSB), whether MCSt (multi-consecutive slot transmission) is applied, whether multi-PSFCH (multi-PSFCH) occasion is applied, resource order / location constituting MCSt, whether multiple starting points are set within one slot, whether 1st starting point (or 2nd starting point) is applied, etc.
[0396] For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the resource pool. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the congestion level. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the priority of the service. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the type of service. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to QoS requirements (e.g., latency, reliability). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to PQI (5QI (5G QoS identifier) for PC5). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or the associated parameters (e.g., thresholds)) may be set specifically (and / or independently and / or differently) depending on the traffic type (e.g., periodic generation and / or aperiodic generation).For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured according to a (SL) transmission resource allocation mode (e.g., mode 1 and / or mode 2). For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured according to a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not need to support sidelink DRX operation).
[0397] For example, the present disclosure may determine whether a proposed rule is applied (and / or a related parameter setting value) whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or when PUCCH resources are not configured), resource pool (e.g., resource pool with PSFCH configured, resource pool without PSFCH configured), service / packet type (and / or priority), QoS profile or QoS requirement (e.g., URLLC / EMBB traffic, reliability, latency), PQI, PFI, cast type (e.g., unicast, groupcast, broadcast, (resource pool) congestion level (e.g., CBR), SL HARQ feedback scheme (e.g., NACK only feedback, ACK / NACK feedback), HARQ feedback enabled MAC PDU. In case of transmitting (and / or HARQ feedback disabled MAC PDU), whether to set PUCCH-based SL HARQ feedback reporting operation, in case of (non)performing (or resource reselection-based) pre-emption (and / or re-evaluation), (L2 or L1) (source and / or destination) identifier, (L2 or L1) (combination of source layer ID and destination layer ID) identifier, (L2 or L1) (combination of a pair of source layer ID and destination layer ID and cast type) identifier,For at least one of a direction of a pair of source layer ID and destination layer ID, a PC5 RRC connection / link, a case of SL DRX (non)performance (or support), an SL mode type (resource allocation mode 1, resource allocation mode 2), (non)periodic resource reservation performance, a Tx profile (e.g., a Tx profile indicating that the service supports (sidelink) DRX operation, a Tx profile indicating that the service does not need to support (sidelink) DRX operation), it can be configured specifically (and / or independently and / or differently).
[0398] For example, the applicability of the proposals and proposed rules of the present disclosure (and / or the associated parameter settings) may also be applied to mmWave SL operation.
[0399] FIG. 17 illustrates a method for a first device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.
[0400] Referring to FIG. 17, in step S1710, the first device can obtain information on multiple carriers. In step S1720, the first device can obtain a packet based on a quality of service (QoS) flow. In step S1730, the first device can perform transmission based on at least one carrier among the multiple carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the multiple carriers based on a change in the QoS flow.
[0401] For example, the transmission may be performed based on at least one carrier associated with the QoS flow among the plurality of carriers.
[0402] For example, the transmission of data may be performed based on at least one carrier associated with the QoS flow among the plurality of carriers.
[0403] For example, based on a change in the QoS flow, resource reselection associated with the transmission may be triggered.
[0404] For example, based on the above carrier reselection being triggered, a new grant may be generated based on at least one reselected carrier.
[0405] For example, based on a change in the QoS flow, a grant based on at least one carrier among the plurality of carriers associated with the QoS flow may be cleared.
[0406] For example, based on a change in the QoS flow, at least one carrier among the plurality of carriers associated with the QoS flow may be released.
[0407] For example, the QoS flow can be changed at a higher layer of the first device.
[0408] For example, the upper layer of the first device may be a V2X (vehicle to everything) layer of the first device.
[0409] For example, the upper layer of the first device may be the PC5 layer of the first device.
[0410] For example, the upper layer of the first device may be an RRC (radio resource control) layer of the first device.
[0411] For example, the carrier reselection may be triggered at a lower layer of the first device.
[0412] For example, the lower layer of the first device may be triggered in the access stratum (AS) layer of the first device.
[0413] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) can obtain information on multiple carriers. Then, the processor (102) of the first device (100) can obtain packets based on a quality of service (QoS) flow. Then, the processor (102) of the first device (100) can control the transceiver (106) to perform transmission based on at least one carrier among the multiple carriers and the QoS flow. For example, carrier reselection can be triggered to select one or more carriers among the multiple carriers based on a change in the QoS flow.
[0414] According to one embodiment of the present disclosure, a first device configured to perform wireless communication may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0415] According to one embodiment of the present disclosure, a processing device configured to control a first device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0416] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a first device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform transmission based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0417] FIG. 18 illustrates a method for a second device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure.
[0418] Referring to FIG. 18, in step S1810, the second device can obtain information on multiple carriers. In step S1820, the second device can obtain a packet based on a quality of service (QoS) flow. In step S1830, the second device can perform reception based on at least one carrier among the multiple carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the multiple carriers based on a change in the QoS flow.
[0419] For example, the reception may be performed based on at least one carrier associated with the QoS flow among the plurality of carriers.
[0420] For example, the reception of data may be performed based on at least one carrier associated with the QoS flow among the plurality of carriers.
[0421] For example, based on a change in the QoS flow, resource reselection associated with the reception may be triggered.
[0422] For example, based on the above carrier reselection being triggered, a new grant may be generated based on at least one reselected carrier.
[0423] For example, based on a change in the QoS flow, a grant based on at least one carrier among the plurality of carriers associated with the QoS flow may be cleared.
[0424] For example, based on a change in the QoS flow, at least one carrier among the plurality of carriers associated with the QoS flow may be released.
[0425] For example, the QoS flow can be changed at a higher layer of the second device.
[0426] For example, the upper layer of the second device may be a V2X (vehicle to everything) layer of the second device.
[0427] For example, the upper layer of the second device may be the PC5 layer of the second device.
[0428] For example, the upper layer of the second device may be an RRC (radio resource control) layer of the second device.
[0429] For example, the carrier reselection may be triggered at a lower layer of the second device.
[0430] For example, the lower layer of the second device may be triggered in the AS (access stratum) layer of the second device.
[0431] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the second device (200) can obtain information on multiple carriers. Then, the processor (202) of the second device (200) can obtain packets based on a quality of service (QoS) flow. Then, the processor (202) of the second device (200) can control the transceiver (206) to perform reception based on at least one carrier among the multiple carriers and the QoS flow. For example, carrier reselection can be triggered to select one or more carriers among the multiple carriers based on a change in the QoS flow.
[0432] According to one embodiment of the present disclosure, a second device configured to perform wireless communication may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the second device to: acquire information about a plurality of carriers; acquire a packet based on a quality of service (QoS) flow; and perform reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0433] According to one embodiment of the present disclosure, a processing device configured to control a second device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the second device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0434] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a second device to: obtain information about a plurality of carriers; obtain a packet based on a quality of service (QoS) flow; and perform reception based on at least one carrier among the plurality of carriers and the QoS flow. For example, carrier reselection may be triggered to select one or more carriers among the plurality of carriers based on a change in the QoS flow.
[0435] The various embodiments of the present disclosure may be combined with each other.
[0436] Below, a description is given of devices to which various embodiments of the present disclosure can be applied.
[0437] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.
[0438] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.
[0439] FIG. 19 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 19 can be combined with various embodiments of the present disclosure.
[0440] Referring to FIG. 19, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., an Advanced Air Mobility (AAM)). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may also be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.
[0441] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.
[0442] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).
[0443] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.
[0444] FIG. 20 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure.
[0445] Referring to FIG. 20, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 19.
[0446] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). Furthermore, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.
[0447] A second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.
[0448] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.
[0449] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.
[0450] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.
[0451] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.
[0452] FIG. 21 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 21 can be combined with various embodiments of the present disclosure.
[0453] Referring to FIG. 21, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operations / functions of FIG. 21 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 20. The hardware elements of FIG. 21 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 20. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 20. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 20, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 20.
[0454] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 21. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (e.g., an UL-SCH transport block, a DL-SCH transport block). The wireless signal may be transmitted through various physical channels (e.g., a PUSCH or a PDSCH).
[0455] Specifically, the codeword can be converted into a bit sequence scrambled by a scrambler (1010). The scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by a precoding matrix W of N*M. Here, N is the number of antenna ports, and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on complex modulation symbols. In addition, the precoder (1040) can perform precoding without performing transform precoding.
[0456] The resource mapper (1050) can map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources can include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. The signal generator (1060) generates a wireless signal from the mapped modulation symbols, and the generated wireless signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) can include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.
[0457] The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 21. For example, a wireless device (e.g., 100, 200 of FIG. 20) can receive wireless signals from the outside through an antenna port / transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.
[0458] Figure 22 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see Figure 19). The embodiment of Figure 22 may be combined with various embodiments of the present disclosure.
[0459] Referring to FIG. 22, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 20 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 20. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 20. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).
[0460] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 19, 100a), a vehicle (Fig. 19, 100b-1, 100b-2), an XR device (Fig. 19, 100c), a portable device (Fig. 19, 100d), a home appliance (Fig. 19, 100e), an IoT device (Fig. 19, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 19, 400), a base station (Fig. 19, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.
[0461] In FIG. 22, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be interconnected entirely via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.
[0462] Below, the implementation example of Fig. 22 is described in more detail with reference to the drawings.
[0463] FIG. 23 illustrates a mobile device according to an embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch, smartglasses), or a portable computer (e.g., a laptop, etc.). The mobile device may be referred to as a Mobile Station (MS), a User Terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure.
[0464] Referring to FIG. 23, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 of FIG. 22, respectively.
[0465] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control components of the mobile device (100) to perform various operations. The control unit (120) can include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / codes / commands required for operating the mobile device (100). In addition, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the mobile device (100) and can include a wired / wireless charging circuit, a battery, etc. The interface unit (140b) can support connection between the mobile device (100) and other external devices. The interface unit (140b) can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can input or output video information / signals, audio information / signals, data, and / or information input from a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker, and / or a haptic module.
[0466] For example, in the case of data communication, the input / output unit (140c) obtains information / signals (e.g., touch, text, voice, image, video) input by the user, and the obtained information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals, and can directly transmit the converted wireless signals to other wireless devices or to a base station. In addition, the communication unit (110) can receive wireless signals from other wireless devices or base stations, and then restore the received wireless signals to the original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).
[0467] Figure 24 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like. The embodiment of Figure 24 may be combined with various embodiments of the present disclosure.
[0468] Referring to FIG. 24, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 22, respectively.
[0469] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.
[0470] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.
[0471] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.
Claims
1. A method performed by a first device in a wireless communication system, A step of obtaining information about multiple carriers; A step of acquiring packets based on QoS (quality of service) flow; and A step of performing transmission based on at least one carrier among the plurality of carriers and the QoS flow; including; A method wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
2. In paragraph 1, A method in which the transmission is performed based on at least one carrier associated with the QoS flow among the plurality of carriers.
3. In paragraph 2, A method in which the transmission of data is performed based on at least one carrier associated with the QoS flow among the plurality of carriers.
4. In paragraph 1, A method in which resource reselection related to the transmission is triggered based on a change in the above QoS flow.
5. In paragraph 1, A method wherein a new grant is generated based on at least one reselected carrier based on the triggering of the above carrier reselection.
6. In paragraph 2, A method wherein, based on a change in the above QoS flow, a grant based on at least one carrier among the plurality of carriers associated with the QoS flow is cleared.
7. In paragraph 2, A method wherein, based on a change in the QoS flow, at least one carrier among the plurality of carriers associated with the QoS flow is released.
8. In paragraph 1, A method in which the above QoS flow is changed in an upper layer of the first device.
9. In paragraph 8, A method wherein the upper layer of the first device is a V2X (vehicle to everything) layer of the first device.
10. In paragraph 8, A method wherein the upper layer of the first device is the PC5 layer of the first device.
11. In paragraph 8, A method wherein the upper layer of the first device is an RRC (radio resource control) layer of the first device.
12. In paragraph 1, A method wherein the carrier reselection is triggered in a lower layer of the first device.
13. In paragraph 12, A method in which the lower layer of the first device is triggered in the AS (access stratum) layer of the first device.
14. In a first device configured to perform wireless communication, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Obtain information about multiple carriers; Acquire packets based on QoS (quality of service) flow; and Perform transmission based on at least one carrier among the above multiple carriers and the QoS flow, A first device, wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
15. In a processing device set to control the first device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Obtain information about multiple carriers; Acquire packets based on QoS (quality of service) flow; and Perform transmission based on at least one carrier among the above multiple carriers and the QoS flow, A processing device, wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Obtain information about multiple carriers; Acquire packets based on QoS (quality of service) flow; and Perform transmission based on at least one carrier among the above multiple carriers and the QoS flow, A non-transitory computer-readable storage medium, wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
17. In a method performed by a second device in a wireless communication system, A step of obtaining information about multiple carriers; A step of acquiring packets based on QoS (quality of service) flow; and A step of performing reception based on at least one carrier among the plurality of carriers and the QoS flow; including; A method wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
18. In a second device configured to perform wireless communication, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second device causes: Obtain information about multiple carriers; Acquire packets based on QoS (quality of service) flow; and Perform reception based on at least one carrier among the above multiple carriers and the QoS flow, A second device, wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
19. In a processing device set to control a second device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second device causes: Obtain information about multiple carriers; Acquire packets based on QoS (quality of service) flow; and Perform reception based on at least one carrier among the above multiple carriers and the QoS flow, A processing device, wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the second device to: Obtain information about multiple carriers; Acquire packets based on QoS (quality of service) flow; and Perform reception based on at least one carrier among the above multiple carriers and the QoS flow, A non-transitory computer-readable storage medium, wherein carrier reselection is triggered to select one or more carriers from among the plurality of carriers based on a change in the above QoS flow.
Citation Information
Patent Citations
Sidelink communication method and apparatus
EP4068815A1
Method and apparatus for triggering transmission carrier selection in wireless communication system
US20220167459A1
