Patent Description:
Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. In general, a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of the multiple access system include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system, and a multi carrier frequency division multiple access (MC-FDMA) system.

A wireless communication system uses various radio access technologies (RATs) such as long term evolution (LTE), LTE-advanced (LTE-A), and wireless fidelity (WiFi). 5th generation (<NUM>) is such a wireless communication system. Three key requirement areas of <NUM> include (<NUM>) enhanced mobile broadband (eMBB), (<NUM>) massive machine type communication (mMTC), and (<NUM>) ultra-reliable and low latency communications (URLLC). Some use cases may require multiple dimensions for optimization, while others may focus only on one key performance indicator (KPI). <NUM> supports such diverse use cases in a flexible and reliable way.

eMBB goes far beyond basic mobile Internet access and covers rich interactive work, media and entertainment applications in the cloud or augmented reality (AR). Data is one of the key drivers for <NUM> and in the <NUM> era, we may for the first time see no dedicated voice service. In <NUM>, voice is expected to be handled as an application program, simply using data connectivity provided by a communication system. The main drivers for an increased traffic volume are the increase in the size of content and the number of applications requiring high data rates. Streaming services (audio and video), interactive video, and mobile Internet connectivity will continue to be used more broadly as more devices connect to the Internet. Many of these applications require always-on connectivity to push real time information and notifications to users. Cloud storage and applications are rapidly increasing for mobile communication platforms. This is applicable for both work and entertainment. Cloud storage is one particular use case driving the growth of uplink data rates. <NUM> will also be used for remote work in the cloud which, when done with tactile interfaces, requires much lower end-to-end latencies in order to maintain a good user experience. Entertainment, for example, cloud gaming and video streaming, is another key driver for the increasing need for mobile broadband capacity. Entertainment will be very essential on smart phones and tablets everywhere, including high mobility environments such as trains, cars and airplanes. Another use case is augmented reality (AR) for entertainment and information search, which requires very low latencies and significant instant data volumes.

One of the most expected <NUM> use cases is the functionality of actively connecting embedded sensors in every field, that is, mMTC. It is expected that there will be <NUM> billion potential Internet of things (IoT) devices by <NUM>. In industrial IoT, <NUM> is one of areas that play key roles in enabling smart city, asset tracking, smart utility, agriculture, and security infrastructure.

URLLC includes services which will transform industries with ultra-reliable/available, low latency links such as remote control of critical infrastructure and self-driving vehicles. The level of reliability and latency are vital to smart-grid control, industrial automation, robotics, drone control and coordination, and so on.

Now, multiple use cases will be described in detail.

<NUM> may complement fiber-to-the home (FTTH) and cable-based broadband (or data-over-cable service interface specifications (DOCSIS)) as a means of providing streams at data rates of hundreds of megabits per second to giga bits per second. Such a high speed is required for TV broadcasts at or above a resolution of <NUM> (<NUM>, <NUM>, and higher) as well as virtual reality (VR) and AR. VR and AR applications mostly include immersive sport games. A special network configuration may be required for a specific application program. For VR games, for example, game companies may have to integrate a core server with an edge network server of a network operator in order to minimize latency.

The automotive sector is expected to be a very important new driver for <NUM>, with many use cases for mobile communications for vehicles. For example, entertainment for passengers requires simultaneous high capacity and high mobility mobile broadband, because future users will expect to continue their good quality connection independent of their location and speed. Other use cases for the automotive sector are AR dashboards. These display overlay information on top of what a driver is seeing through the front window, identifying objects in the dark and telling the driver about the distances and movements of the objects. In the future, wireless modules will enable communication between vehicles themselves, information exchange between vehicles and supporting infrastructure and between vehicles and other connected devices (e.g., those carried by pedestrians). Safety systems may guide drivers on alternative courses of action to allow them to drive more safely and lower the risks of accidents. The next stage will be remote-controlled or self-driving vehicles. These require very reliable, very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will execute all driving activities, while drivers are focusing on traffic abnormality elusive to the vehicles themselves. The technical requirements for self-driving vehicles call for ultra-low latencies and ultra-high reliability, increasing traffic safety to levels humans cannot achieve.

Smart cities and smart homes, often referred to as smart society, will be embedded with dense wireless sensor networks. Distributed networks of intelligent sensors will identify conditions for cost- and energy-efficient maintenance of the city or home. A similar setup can be done for each home, where temperature sensors, window and heating controllers, burglar alarms, and home appliances are all connected wirelessly. Many of these sensors are typically characterized by low data rate, low power, and low cost, but for example, real time high definition (HD) video may be required in some types of devices for surveillance.

The consumption and distribution of energy, including heat or gas, is becoming highly decentralized, creating the need for automated control of a very distributed sensor network. A smart grid interconnects such sensors, using digital information and communications technology to gather and act on information. This information may include information about the behaviors of suppliers and consumers, allowing the smart grid to improve the efficiency, reliability, economics and sustainability of the production and distribution of fuels such as electricity in an automated fashion. A smart grid may be seen as another sensor network with low delays.

The health sector has many applications that may benefit from mobile communications. Communications systems enable telemedicine, which provides clinical health care at a distance. It helps eliminate distance barriers and may improve access to medical services that would often not be consistently available in distant rural communities. It is also used to save lives in critical care and emergency situations. Wireless sensor networks based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communications are becoming increasingly important for industrial applications. Wires are expensive to install and maintain, and the possibility of replacing cables with reconfigurable wireless links is a tempting opportunity for many industries. However, achieving this requires that the wireless connection works with a similar delay, reliability and capacity as cables and that its management is simplified. Low delays and very low error probabilities are new requirements that need to be addressed with <NUM>
Finally, logistics and freight tracking are important use cases for mobile communications that enable the tracking of inventory and packages wherever they are by using location-based information systems. The logistics and freight tracking use cases typically require lower data rates but need wide coverage and reliable location information.

A wireless communication system is a multiple access system that supports communication of multiple users by sharing available system resources (a bandwidth, transmission power, etc.). Examples of multiple access systems include a CDMA system, an FDMA system, a TDMA system, an OFDMA system, an SC-FDMA system, and an MC-FDMA system.

Sidelink (SL) refers to a communication scheme in which a direct link is established between user equipments (UEs) and the UEs directly exchange voice or data without intervention of a base station (BS). SL is considered as a solution of relieving the BS of the constraint of rapidly growing data traffic.

Vehicle-to-everything (V2X) is a communication technology in which a vehicle exchanges information with another vehicle, a pedestrian, and infrastructure by wired/wireless communication. V2X may be categorized into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication may be provided via a PC5 interface and/or a Uu interface.

As more and more communication devices demand larger communication capacities, there is a need for enhanced mobile broadband communication relative to existing RATs. Accordingly, a communication system is under discussion, for which services or UEs sensitive to reliability and latency are considered. The next-generation RAT in which eMBB, MTC, and URLLC are considered is referred to as new RAT or NR. In NR, V2X communication may also be supported.

<FIG> is a diagram illustrating V2X communication based on pre-NR RAT and V2X communication based on NR in comparison.

For V2X communication, a technique of providing safety service based on V2X messages such as basic safety message (BSM), cooperative awareness message (CAM), and decentralized environmental notification message (DENM) was mainly discussed in the pre-NR RAT. The V2X message may include location information, dynamic information, and attribute information. For example, a UE may transmit a CAM of a periodic message type and/or a DENM of an event-triggered type to another UE.

For example, the CAM may include basic vehicle information including dynamic state information such as a direction and a speed, vehicle static data such as dimensions, an external lighting state, path details, and so on. For example, the UE may broadcast the CAM which may have a latency less than <NUM>. For example, when an unexpected incident occurs, such as breakage or an accident of a vehicle, the UE may generate the DENM and transmit the DENM to another UE. For example, all vehicles within the transmission range of the UE may receive the CAM and/or the DENM. In this case, the DENM may have priority over the CAM.

In relation to V2X communication, various V2X scenarios are presented in NR. For example, the V2X scenarios include vehicle platooning, advanced driving, extended sensors, and remote driving.

For example, vehicles may be dynamically grouped and travel together based on vehicle platooning. For example, to perform platoon operations based on vehicle platooning, the vehicles of the group may receive periodic data from a leading vehicle. For example, the vehicles of the group may widen or narrow their gaps based on the periodic data.

For example, a vehicle may be semi-automated or full-automated based on advanced driving. For example, each vehicle may adjust a trajectory or maneuvering based on data obtained from a nearby vehicle and/or a nearby logical entity. For example, each vehicle may also share a dividing intention with nearby vehicles.

Based on extended sensors, for example, raw or processed data obtained through local sensor or live video data may be exchanged between vehicles, logical entities, terminals of pedestrians and/or V2X application servers. Accordingly, a vehicle may perceive an advanced environment relative to an environment perceivable by its sensor.

Based on remote driving, for example, a remote driver or a V2X application may operate or control a remote vehicle on behalf of a person incapable of driving or in a dangerous environment. For example, when a path may be predicted as in public transportation, cloud computing-based driving may be used in operating or controlling the remote vehicle. For example, access to a cloud-based back-end service platform may also be used for remote driving.

A scheme of specifying service requirements for various V2X scenarios including vehicle platooning, advanced driving, extended sensors, and remote driving is under discussion in NR-based V2X communication.

Prior art is found in LG Electronics Inc, "Running CR of TS <NUM> for Sidelink enhancement", R2-<NUM>, and in Seungmin Lee, LG Electomics, RP220945.

preferred embodiments of the invention are set out in the dependent claims.

An object of the present disclosure is to provide operations related to a manner of performing and transmitting a logical channel prioritization (LCP) procedure of data having the same Destination Layer-<NUM> ID (DST L2 ID) but different SL DRX configurations.

In various embodiments of the present disclosure, "/" and "," should be interpreted as "and/or". Further, "A, B" may mean "A and/or B". Further, "A/B/C" may mean "at least one of A, B and/or C". Further, "A, B, C" may mean "at least one of A, B and/or C".

In various embodiments of the present disclosure, "or" should be interpreted as "and/or". For example, "A or B" may include "only A", "only B", and/or "both A and B". In other words, "or" should be interpreted as "additionally or alternatively".

Techniques described herein may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier-frequency division multiple access (SC-FDMA), and so on. CDMA may be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, evolved-UTRA (E-UTRA), or the like. IEEE <NUM> is an evolution of IEEE <NUM>. 16e, offering backward compatibility with an IRRR <NUM>. 16e-based system. UTRA is a part of universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using evolved UTRA (E-UTRA). 3GPP LTE employs OFDMA for downlink (DL) and SC-FDMA for uplink (UL). LTE-advanced (LTE-A) is an evolution of 3GPP LTE.

A successor to LTE-A, 5th generation (<NUM>) new radio access technology (NR) is a new clean-state mobile communication system characterized by high performance, low latency, and high availability. <NUM> NR may use all available spectral resources including a low frequency band below <NUM>, an intermediate frequency band between <NUM> and <NUM>, and a high frequency (millimeter) band of <NUM> or above.

While the following description is given mainly in the context of LTE-A or <NUM> NR for the clarity of description, the technical idea of an embodiment of the present disclosure is not limited thereto.

<FIG> illustrates the structure of an LTE system according to an embodiment of the present disclosure. This may also be called an evolved UMTS terrestrial radio access network (E-UTRAN) or LTE/LTE-A system.

Referring to <FIG>, the E-UTRAN includes evolved Node Bs (eNBs) <NUM> which provide a control plane and a user plane to UEs <NUM>. A UE <NUM> may be fixed or mobile, and may also be referred to as a mobile station (MS), user terminal (UT), subscriber station (SS), mobile terminal (MT), or wireless device. An eNB <NUM> is a fixed station communication with the UE <NUM> and may also be referred to as a base station (BS), a base transceiver system (BTS), or an access point.

eNBs <NUM> may be connected to each other via an X2 interface. An eNB <NUM> is connected to an evolved packet core (EPC) <NUM> via an S1 interface. More specifically, the eNB <NUM> is connected to a mobility management entity (MME) via an S1-MME interface and to a serving gateway (S-GW) via an S1-U interface.

The EPC <NUM> includes an MME, an S-GW, and a packet data network-gateway (P-GW). The MME has access information or capability information about UEs, which are mainly used for mobility management of the UEs. The S-GW is a gateway having the E-UTRAN as an end point, and the P-GW is a gateway having a packet data network (PDN) as an end point.

Based on the lowest three layers of the open system interconnection (OSI) reference model known in communication systems, the radio protocol stack between a UE and a network may be divided into Layer <NUM> (L1), Layer <NUM> (L2) and Layer <NUM> (L3). These layers are defined in pairs between a UE and an Evolved UTRAN (E-UTRAN), for data transmission via the Uu interface. The physical (PHY) layer at L1 provides an information transfer service on physical channels. The radio resource control (RRC) layer at L3 functions to control radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and an eNB.

<FIG> illustrates a user-plane radio protocol architecture according to an embodiment of the disclosure.

<FIG> illustrates a control-plane radio protocol architecture according to an embodiment of the disclosure. A user plane is a protocol stack for user data transmission, and a control plane is a protocol stack for control signal transmission.

Referring to <FIG>, the PHY layer provides an information transfer service to its higher layer on physical channels. The PHY layer is connected to the medium access control (MAC) layer through transport channels and data is transferred between the MAC layer and the PHY layer on the transport channels. The transport channels are divided according to features with which data is transmitted via a radio interface.

Data is transmitted on physical channels between different PHY layers, that is, the PHY layers of a transmitter and a receiver. The physical channels may be modulated in orthogonal frequency division multiplexing (OFDM) and use time and frequencies as radio resources.

The MAC layer provides services to a higher layer, radio link control (RLC) on logical channels. The MAC layer provides a function of mapping from a plurality of logical channels to a plurality of transport channels. Further, the MAC layer provides a logical channel multiplexing function by mapping a plurality of logical channels to a single transport channel. A MAC sublayer provides a data transmission service on the logical channels.

The RLC layer performs concatenation, segmentation, and reassembly for RLC serving data units (SDUs). In order to guarantee various quality of service (QoS) requirements of each radio bearer (RB), the RLC layer provides three operation modes, transparent mode (TM), unacknowledged mode (UM), and acknowledged Mode (AM). An AM RLC provides error correction through automatic repeat request (ARQ).

The RRC layer is defined only in the control plane and controls logical channels, transport channels, and physical channels in relation to configuration, reconfiguration, and release of RBs. An RB refers to a logical path provided by L1 (the PHY layer) and L2 (the MAC layer, the RLC layer, and the packet data convergence protocol (PDCP) layer), for data transmission between the UE and the network.

The user-plane functions of the PDCP layer include user data transmission, header compression, and ciphering. The control-plane functions of the PDCP layer include control-plane data transmission and ciphering/integrity protection.

RB establishment amounts to a process of defining radio protocol layers and channel features and configuring specific parameters and operation methods in order to provide a specific service. RBs may be classified into two types, signaling radio bearer (SRB) and data radio bearer (DRB). The SRB is used as a path in which an RRC message is transmitted on the control plane, whereas the DRB is used as a path in which user data is transmitted on the user plane.

Once an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is placed in RRC_CONNECTED state, and otherwise, the UE is placed in RRC_IDLE state. In NR, RRC_INACTIVE state is additionally defined. A UE in the RRC_INACTIVE state may maintain a connection to a core network, while releasing a connection from an eNB.

DL transport channels carrying data from the network to the UE include a broadcast channel (BCH) on which system information is transmitted and a DL shared channel (DL SCH) on which user traffic or a control message is transmitted. Traffic or a control message of a DL multicast or broadcast service may be transmitted on the DL-SCH or a DL multicast channel (DL MCH). UL transport channels carrying data from the UE to the network include a random access channel (RACH) on which an initial control message is transmitted and an UL shared channel (UL SCH) on which user traffic or a control message is transmitted.

The logical channels which are above and mapped to the transport channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a multicast traffic channel (MTCH).

A physical channel includes a plurality of OFDM symbol in the time domain by a plurality of subcarriers in the frequency domain. One subframe includes a plurality of OFDM symbols in the time domain. An RB is a resource allocation unit defined by a plurality of OFDM symbols by a plurality of subcarriers. Further, each subframe may use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) in a corresponding subframe for a physical DL control channel (PDCCH), that is, an L1/L2 control channel. A transmission time interval (TTI) is a unit time for subframe transmission.

<FIG> illustrates the structure of an NR system according to an embodiment of the present disclosure.

Referring to <FIG>, a next generation radio access network (NG-RAN) may include a next generation Node B (gNB) and/or an eNB, which provides user-plane and control-plane protocol termination to a UE. In <FIG>, the NG-RAN is shown as including only gNBs, by way of example. A gNB and an eNB are connected to each other via an Xn interface. The gNB and the eNB are connected to a <NUM> core network (5GC) via an NG interface. More specifically, the gNB and the eNB are connected to an access and mobility management function (AMF) via an NG-C interface and to a user plane function (UPF) via an NG-U interface.

<FIG> illustrates functional split between the NG-RAN and the 5GC according to an embodiment of the present disclosure.

Referring to <FIG>, a gNB may provide functions including inter-cell radio resource management (RRM), radio admission control, measurement configuration and provision, and dynamic resource allocation. The AMF may provide functions such as non-access stratum (NAS) security and idle-state mobility processing. The UPF may provide functions including mobility anchoring and protocol data unit (PDU) processing. A session management function (SMF) may provide functions including UE Internet protocol (IP) address allocation and PDU session control.

<FIG> illustrates a radio frame structure in NR, to which embodiment(s) of the present disclosure is applicable.

Referring to <FIG>, a radio frame may be used for UL transmission and DL transmission in NR. A radio frame is <NUM> in length, and may be defined by two <NUM>-ms half-frames. An HF may include five <NUM>-ms subframes. A subframe may be divided into one or more slots, and the number of slots in an SF may be determined according to a subcarrier spacing (SCS).

In a normal CP (NCP) case, each slot may include <NUM> symbols, whereas in an extended CP (ECP) case, each slot may include <NUM> symbols. Herein, a symbol may be an OFDM symbol (or CP-OFDM symbol) or an SC-FDMA symbol (or DFT-s-OFDM symbol).

Table <NUM> below lists the number of symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslot according to an SCS configuration µ in the NCP case.

Table <NUM> below lists the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to an SCS in the ECP case.

In the NR system, different OFDM(A) numerologies (e.g., SCSs, CP lengths, and so on) may be configured for a plurality of cells aggregated for one UE. Accordingly, the (absolute time) duration of a time resource including the same number of symbols (e.g., a subframe, slot, or TTI) (collectively referred to as a time unit (TU) for convenience) may be configured to be different for the aggregated cells.

In NR, various numerologies or SCSs may be supported to support various <NUM> services. For example, with an SCS of <NUM>, a wide area in traditional cellular bands may be supported, while with an SCS of <NUM>/<NUM>, a dense urban area, a lower latency, and a wide carrier bandwidth may be supported. With an SCS of <NUM> or higher, a bandwidth larger than <NUM> may be supported to overcome phase noise.

An NR frequency band may be defined by two types of frequency ranges, FR1 and FR2. The numerals in each frequency range may be changed. For example, the two types of frequency ranges may be given in [Table <NUM>]. In the NR system, FR1 may be a "sub <NUM> range" and FR2 may be an "above <NUM> range" called millimeter wave (mmW).

As mentioned above, the numerals in a frequency range may be changed in the NR system. For example, FR1 may range from <NUM> to <NUM> as listed in [Table <NUM>]. That is, FR1 may include a frequency band of <NUM> (or <NUM>, <NUM>, and <NUM>) or above. For example, the frequency band of <NUM> (or <NUM>, <NUM>, and <NUM>) or above may include an unlicensed band. The unlicensed band may be used for various purposes, for example, vehicle communication (e.g., autonomous driving).

<FIG> illustrates a slot structure in an NR frame according to an embodiment of the present disclosure.

Referring to <FIG>, a slot includes a plurality of symbols in the time domain. For example, one slot may include <NUM> symbols in an NCP case and <NUM> symbols in an ECP case. Alternatively, one slot may include <NUM> symbols in an NCP case and <NUM> symbols in an ECP case.

A carrier includes a plurality of subcarriers in the frequency domain. An RB may be defined by a plurality of (e.g., <NUM>) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) may be defined by a plurality of consecutive (physical) RBs ((P)RBs) in the frequency domain and correspond to one numerology (e.g., SCS, CP length, or the like). A carrier may include up to N (e.g., <NUM>) BWPs. Data communication may be conducted in an activated BWP. Each element may be referred to as a resource element (RE) in a resource grid, to which one complex symbol may be mapped.

A radio interface between UEs or a radio interface between a UE and a network may include L1, L2, and L3. In various embodiments of the present disclosure, L1 may refer to the PHY layer. For example, L2 may refer to at least one of the MAC layer, the RLC layer, the PDCH layer, or the SDAP layer. For example, L3 may refer to the RRC layer.

Now, a description will be given of sidelink (SL) communication.

<FIG> illustrates a radio protocol architecture for SL communication according to an embodiment of the present disclosure. Specifically, <FIG> illustrates a user-plane protocol stack in LTE, and <FIG> illustrates a control-plane protocol stack in LTE.

<FIG> illustrates a radio protocol architecture for SL communication according to an embodiment of the present disclosure. Specifically, <FIG> illustrates a user-plane protocol stack in NR, and <FIG> illustrates a control-plane protocol stack in NR.

<FIG> illustrates a synchronization source or synchronization reference of V2X according to an embodiment of the present disclosure.

Referring to <FIG>, in V2X, a UE may be directly synchronized with global navigation satellite systems (GNSS). Alternatively, the UE may be indirectly synchronized with the GNSS through another UE (within or out of network coverage). If the GNSS is configured as a synchronization source, the UE may calculate a direct frame number (DFN) and a subframe number based on a coordinated universal time (UTC) and a configured (or preconfigured) DFN offset.

Alternatively, a UE may be directly synchronized with a BS or may be synchronized with another UE that is synchronized in time/frequency with the BS. For example, the BS may be an eNB or a gNB. For example, when a UE is in network coverage, the UE may receive synchronization information provided by the BS and may be directly synchronized with the BS. Next, the UE may provide the synchronization information to another adjacent UE. If a timing of the BS is configured as a synchronization reference, the UE may follow a cell associated with a corresponding frequency (when the UE is in cell coverage in frequency) or a primary cell or a serving cell (when the UE is out of cell coverage in frequency), for synchronization and DL measurement.

The BS (e.g., serving cell) may provide a synchronization configuration for a carrier used for V2X/SL communication. In this case, the UE may conform to the synchronization configuration received from the BS. If the UE fails to detect any cell in the carrier used for V2X/SL communication and fails to receive the synchronization configuration from the serving cell, the UE may conform to a preset synchronization configuration.

Alternatively, the UE may be synchronized with another UE that has failed to directly or indirectly acquire the synchronization information from the BS or the GNSS. A synchronization source and a preference may be preconfigured for the UE. Alternatively, the synchronization source and the preference may be configured through a control message provided by the BS.

SL synchronization sources may be associated with synchronization priority levels. For example, a relationship between synchronization sources and synchronization priorities may be defined as shown in Table <NUM> or <NUM>. Table <NUM> or <NUM> is merely an example, and the relationship between synchronization sources and synchronization priorities may be defined in various ways.

In Table <NUM> or <NUM>, P0 may mean the highest priority, and P6 may mean the lowest priority. In Table <NUM> or <NUM>, the BS may include at least one of a gNB or an eNB.

Whether to use GNSS-based synchronization or eNB/gNB-based synchronization may be (pre)configured. In a single-carrier operation, the UE may derive a transmission timing thereof from an available synchronization reference having the highest priority.

Hereinafter, a sidelink synchronization signal (SLSS) and synchronization information will be described.

As an SL-specific sequence, the SLSS may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS). The PSSS may be referred to as a sidelink primary synchronization signal (S-PSS), and the SSSS may be referred to as a sidelink secondary synchronization signal (S-SSS). For example, length-<NUM>-sequences may be used for the S-PSS, and length-<NUM> gold sequences may be used for the S-SSS. For example, the UE may use the S-PSS to detect an initial signal and obtain synchronization. In addition, the UE may use the S-PSS and the S-SSS to obtain detailed synchronization and detect a synchronization signal ID.

A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information that the UE needs to know first before transmitting and receiving SL signals. For example, the default information may include information related to an SLSS, a duplex mode (DM), a time division duplex (TDD) UL/DL configuration, information related to a resource pool, an application type related to the SLSS, a subframe offset, broadcast information, etc. For example, for evaluation of PSBCH performance in NR V2X, the payload size of the PSBCH may be <NUM> bits including a CRC of <NUM> bits.

The S-PSS, S-SSS, and PSBCH may be included in a block format (e.g., SL synchronization signal (SS)/PSBCH block) supporting periodical transmission (hereinafter, the SL SS/PSBCH block is referred to as a sidelink synchronization signal block (S-SSB)). The S-SSB may have the same numerology (i.e., SCS and CP length) as that of a physical sidelink control channel (PSCCH)/physical sidelink shared channel (PSSCH) on a carrier, and the transmission bandwidth may exist within a configured (or preconfigured) SL BWP. For example, the S-SSB may have a bandwidth of <NUM> RBs. For example, the PSBCH may span <NUM> RBs. In addition, the frequency position of the S-SSB may be configured (or preconfigured). Therefore, the UE does not need to perform hypothesis detection on frequency to discover the S-SSB on the carrier.

The NR SL system may support a plurality of numerologies with different SCSs and/or different CP lengths. In this case, as the SCS increases, the length of a time resource used by a transmitting UE to transmit the S-SSB may decrease. Accordingly, the coverage of the S-SSB may be reduced. Therefore, in order to guarantee the coverage of the S-SSB, the transmitting UE may transmit one or more S-SSBs to a receiving UE within one S-SSB transmission period based on the SCS. For example, the number of S-SSBs that the transmitting UE transmits to the receiving UE within one S-SSB transmission period may be pre-configured or configured for the transmitting UE. For example, the S-SSB transmission period may be <NUM>. For example, an S-SSB transmission period of <NUM> may be supported for all SCSs.

For example, when the SCS is <NUM> in FR1, the transmitting UE may transmit one or two S-SSBs to the receiving UE within one S-SSB transmission period. For example, when the SCS is <NUM> in FR1, the transmitting UE may transmit one or two S-SSBs to the receiving UE within one S-SSB transmission period. For example, when the SCS is <NUM> in FR1, the transmitting UE may transmit one, two, or four S-SSBs to the receiving UE within one S-SSB transmission period.

<FIG> illustrates a procedure of performing V2X or SL communication by a UE depending on a transmission mode according to an embodiment of the present disclosure. The embodiemnt of <FIG> may be combined with various embodiemnts of the present disclosure. In various embodiments of the present disclosure, a transmission mode may be referred to as a mode or a resource allocation mode. For the convenience of the following description, a transmission mode in LTE may be referred to as an LTE transmission mode, and a transmission mode in NR may be referred to as an NR resource allocation mode.

For example, <FIG> illustrates a UE operation related to LTE transmission mode <NUM> or LTE transmission mode <NUM>. Alternatively, for example, <FIG> illustrates a UE operation related to NR resource allocation mode <NUM>. For example, LTE transmission mode <NUM> may apply to general SL communication, and LTE transmission mode <NUM> may apply to V2X communication.

For example, <FIG> illustrates a UE operation related to LTE transmission mode <NUM> or LTE transmission mode <NUM>. Alternatively, for example, <FIG> illustrates a UE operation related to NR resource allocation mode <NUM>.

Referring to <FIG>, in LTE transmission mode <NUM>, LTE transmission mode <NUM>, or NR resource allocation mode <NUM>, a BS may schedule an SL resource to be used for SL transmission by a UE. For example, in step S8000, the BS may transmit information related to an SL resource and/or information related to a UE resoruce to a first UE. For exmaple, the UL resource may include a PUCCH resource and/or a PUSCH resource. For exmaple, the UL resource may be a resource to report SL HARQ feedback to the BS.

For example, the first UE may receive information related to a Dynamic Grant (DG) resource and/or information related to a Configured Grant (CG) resource from the BS. For example, the CG resource may include a CG type <NUM> resource or a CG type <NUM> resource. In the present specification, the DG resource may be a resource configured/allocated by the BS to the first UE in Downlink Control Information (DCI). In the present specification, the CG resource may be a (periodic) resource configured/allocated by the BS to the first UE in DCI and/or an RRC message. For example, for the CG type <NUM> resource, the BS may transmit an RRC message including information related to the CG resource to the first UE. For example, for the CG type <NUM> resource, the BS may transmit an RRC message including information related to the CG resource to the first UE, and the BS may transmit DCI for activation or release of the CG resource to the first UE.

In step S8010, the first UE may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second UE based on the resource scheduling. In step S8020, the first UE may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S8030, the first UE may receive a PSFCH related to the PSCCH/PSSCH from the second UE. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second UE over the PSFCH. In step S8040, the first UE may transmit/report HARQ feedback information to the BS over a PUCCH or PUSCH. For example, the HARQ feedback information reported to the BS may include information generated by the first UE based on HARQ feedback information received from the second UE. For example, the HARQ feedback information reported to the BS may include information generated by the first UE based on a preset rule. For example, the DCI may be a DCI for scheduling of SL. For example, the format of the DCI may include DCI format 3_0 or DCI format 3_1. Table <NUM> shows one example of DCI for scheduling of SL.

Referring to <FIG>, in an LTE transmission mode <NUM>, an LTE transmission mode <NUM>, or an NR resource allocation mode <NUM>, a UE may determine an SL transmission resource within an SL resource configured by a BS/network or a preconfigured SL resource. For example, the configured SL resource or the preconfigured SL resource may be a resource pool. For example, the UE may autonomously select or schedule resources for SL transmission. For example, the UE may perform SL communication by selecting a resource by itself within a configured resource pool. For example, the UE may perform sensing and resource (re)selection procedures to select a resource by itself within a selection window. For example, the sensing may be performed in unit of a sub-channel. For example, in the step S8010, the first UE having self-selected a resource in the resource pool may transmit PSCCH (e.g., Side Link Control Information (SCI) or <NUM>st-stage SCI) to the second UE using the resource. In the step S8020, the first UE may transmit PSSCH (e.g., <NUM>nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In the step S8030, the first UE may receive PSFCH related to the PSCCH/PSSCH from the second UE.

Referring to <FIG>, for example, the first UE may transmit the SCI to the second UE on the PSCCH. Alternatively, for example, the first UE may transmit two consecutive SCIs (e.g., two-stage SCI) to the second UE on the PSCCH and/or PSSCH. In this case, the second UE may decode the two consecutive SCIs (e.g., two-stage SCI) to receive the PSSCH from the first UE. In the present specification, the SCI transmitted on the PSCCH may be referred to as a <NUM>st SCI, a <NUM>st-stage SCI, or a <NUM>st-stage SCI format, and the SCI transmitted on the PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI format. For example, the 1st-stage SCI format may include SCI format <NUM>-A, and the <NUM>nd-stage SCI format may include SCI format <NUM>-A and/or SCI format <NUM>-B. Table <NUM> shows one example of a <NUM>st-stage SCI format.

Table <NUM> shows exemplary <NUM>nd-stage SCI formats.

Referring to <FIG>, in step S8030, a first UE may receive a PSFCH based on Table <NUM>. For example, the first UE and a second UE may determine a PSFCH resource based on Table <NUM>, and the second UE may transmit HARQ feedback to the first UE on the PSFCH resource.

Referring to <FIG>, in step S8040, the first UE may transmit SL HARQ feedback to the BS over a PUCCH and/or PUSCH based on Table <NUM>.

Table <NUM> below shows details of selection and reselection of an SL relay UE defined in 3GPP TS <NUM>. The contents of Table <NUM> are used as the prior art of the present disclosure, and related necessary details may be found in 3GPP TS <NUM>.

A MAC entity may be configured by an RRC as a DRX function of controlling a PDCCH monitoring activity of a UE for C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI, and SL Semi-Persistent Scheduling V-RNTI of the MAC entity. When using a DRX operation, a MAC entity should monitor PDCCH according to prescribed requirements. When DRX is configured in RRC_CONNECTED, a MAC entity may discontinuously monitor PDCCH for all activated serving cells.

RRC may control a DRX operation by configuring the following parameters.

A serving cell of a MAC entity may be configured by RRC in two DRX groups having separate DRX parameters. When the RRC does not configure a secondary DRX group, a single DRX group exists only and all serving cells belong to the single DRX group. When two DRX groups are configured, each serving cell is uniquely allocated to each of the two groups. DRX parameters separately configured for each DRX group include drx-onDurationTimer and drx-InactivityTimer. A DRX parameter common to a DRX group is as follows.

DRX parameters common to a DRX group are as follows.

drx-SlotOffset, drx-RetransmissionTimerDL, drx-Retrans drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.

In addition, in a Uu DRX operation of the related art, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL are defined. When UE HARQ retransmission is performed, it is secured to make transition to a sleep mode during RTT timer (drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) or to maintain an active state during Retransmission Timer (drx-RetransmissionTimerDL, drx-RetransmissionTimerUL).

In addition, for details of SL DRX, SL DRX-related contents of TS <NUM> and R2-<NUM> may be referred to as the related art.

Tables <NUM> to <NUM> below show the details of sidelink DRX disclosed in 3GPP TS <NUM> V16. <NUM>, which are used as the prior art of the present disclosure.

A sidelink UE may transmit a SidelinkUEInformationNR message to a network. The purpose of the RRC message is to inform the network that the UE is interested or no longer interested in receiving NR sidelink communication, to request allocation or release of a transmission resource for NR sidelink communication, and to report a parameter related to the NR sidelink communication. The SidelinkUEInformationNR includes sl-QoS-InfoList including a QoS profile of sidelink QoS flow and sl-DestinationIdentity indicating a destination to which SL failure is reported for unicast. In addition, UEAssistanceInformation refers to content disclosed in 3GPP TS <NUM>.

The UEAssistanceInformation is for indicating UE assistance information to the network, and is transmitted from the UE to the network. The UEAssistanceInformation may include an sl-QoS-FlowIdentity element. The sl-QoS-FlowIdentity is an ID that uniquely identifies one sidelink QoS flow between the UE and the network within a UE scope, and has a unique value for different destinations and cast types. In addition, the UEAssistanceInformation refers to content disclosed in 3GPP TS <NUM>.

Tables <NUM> and <NUM> below are related to a logical channel disclosed in 3GPP TS <NUM>, and are used as prior art of the present disclosure.

Table <NUM> below shows an agreement in a 3GPP RAN2 conference related to Groupcast (GC) and Broadcast (BC), and is used as prior art of the present disclosure.

In a Groupcast (GC) operation for SL DRX, the same DST L2 ID mav be derived for different services. In particular, this may occur when a Destination Layer-<NUM> ID (hereinafter referred to as DST L2 ID) for GC is generated by the UE itself. When the same DST L2 ID is generated for different services, a TX profile value for each service may also be configured differently. In this case, a gNB may need to know which TX profile a TX UE uses for resource grant allocation or resource pool configuration. In addition, an RX UE receiving this also needs to know which TX profile the TX UE uses and a corresponding DRX configuration to receive a groupcast packet without loss.

Hereinafter, a method of operating a UE related to a case in which the same L2 DST ID is generated for different services during GC transmission and an apparatus related thereto will be described.

For transmission related to group cast according to an embodiment, the UE selects a destination having a logical channel (LCH) with a highest priority among available sidelink data for transmission (S <NUM> in <FIG>). A Medium Access Control Protocol Data Unit (MAC PDU) is generated from data related to the destination (S <NUM>) and the MAC PDU is transmitted at an active time (S1203).

Here, the data related to the destination is data related to the active time among a plurality of data related to the destination, and the UE may determine data related to the active time among a plurality of data related to the destination based on a service ID (or group ID). The service ID (or group ID) may be transferred to an Access Stratum (AS) layer from a higher layer of the UE and the plurality of data related to the destination may be related to the same Destination Layer-<NUM> ID (DST L2 ID). In addition, one TX profile may be related to the service ID (or group ID), and the TX profile may include configurations related to sidelink Discontinuous Reception (DRX). The configuration related to the sidelink DRX may include information indicating the active time.

In other words, the plurality of data related to the destination may be for one (same) DST L2 ID, and several service IDs (or group IDs) may be related to the destination. As described above, since one TX profile (including active time indication information) is related to the service ID (or group ID), a plurality of data with different active times may be related to the destination (DST L2 ID). In this case, conventionally, it was not possible to distinguish a plurality of data related to the same DST L2 ID but with different active times, but according to the present disclosure, the plurality of data is distinguished through a service ID (or group ID), and thus a MAC PDU is generated by correcting only data related to a specific active time.

That is, in a Logical Channel Prioritization (LCP) operation, data (/logical channel) with the highest priority (value) among available data for the logical channel is selected, and then one MAC PDU is generated by collecting data having the same L2 DST ID, cast type, and an indication (/service ID/group ID) as the corresponding data. Even if data have the same L2 DST ID, different DRX configurations may be applied and transmitted according to an indication (/service ID/group ID) related to the corresponding L2 DST ID.

Regarding the indication, a higher layer of the TX UE transmits an indication indicating that the same DST L2 ID has been generated for different services together with the DST L2 ID (and/or TX profile) when transmitting a packet to the AS layer. At this time, the indication value is replaced with a service ID That is, when a packet is transmitted from a higher layer to the AS layer, the service ID of the packet is transmitted together. The AS layer receiving this may reflect it during LCP operation.

In summary, when the same L2 DST address is generated for different service IDs (and/or group IDs) and the TX profile applied to each service ID (and/or group ID) is changed to be DRX-enabled or DRX-disabled, the same MAC PDU may be generated for the same serving ID and the corresponding MAC PDU is transmitted to a DRX active timer according to the TX profile of the corresponding service during an LCP operation of the AS layer using a serving ID during transmission of a packet to the AS layer, transmitted by the higher layer.

As such, when transmitting a packet from the higher layer to the AS layer, the service ID may be transmitted together, and the same MAC PDU is generated for the same service ID during the LCP operation of the AS layer, and thus data with different TX profiles (active times) may be prevented from the multiplexed in one MAC PDU. Through this, data having the same DST L2 ID but different SL DRX configurations may be multiplexed and transmitted according to each SL DRX configuration. In addition, UEs having respective L2 IDs and DRX active times may receive all PDUs related to a specific service in the DRX active timer according to the TX profile of the service.

As another example, if the case in which a TX profile is DRX-enabled (or drx-Compatible) and the case in which the TX profile is DRX-disabled (or drx-Incompatible) are mapped to the same L2 ID, an operation may also be limited by applying and transmitting the corresponding DRX configuration according to the TX profile that is DRX-enabled. That is, if a plurality of service IDs are related with one DST L2 ID, and a DRX-enabled TX profile (active time) and a DRX-disabled TX profile (active time) are related with the plurality of service IDs, respectively, the TX profiles may be all treated as DRX-enabled TX profiles and data may be transmitted at the active time of the DRX-enabled TX profile.

Alternatively, since a MAC PDU is generated for each indication (/service ID/group ID) according to the LCP operation as described above, data may be transmitted in a period corresponding to the active time of each DRX profile according to a DRX profile of a group ID associated with each MAC PDU. For example, even if data have the same DST L2 ID, MAC PDUs related to the DRX-enabled TX profile may transmit data only during the active time of the corresponding SL DRX configuration, and MAC PDUs related to the DRX-disabled TX profile may transmit data at any time ('always on').

As another example, a higher layer of the RX UE may transmit a service ID (/group ID/indication) of a packet to be received to the AS layer together with an L2 ID to be received. Depending on QoS profile information of the packet to be received, it may be possible to determine which SL DRX configuration to apply for reception. However, if the data to be received has the same L2 ID but different service IDs (/group ID/indication) and/or TX profiles are transmitted in the higher layer, it may be necessary to determine which SL DRX configuration to apply for reception. For example, for the same receiving L2 ID, when a DRX-enabled TX profile is applied to one service and a DRX-disabled TX profile is applied to another service, the RX UE may receive data according to a DRX configuration corresponding to a group ID (service ID/indication) for the corresponding L2 ID. The RX UE receiving the DRX-enabled TX profile may receive data at an active time of the corresponding DRX configuration, and the RX UE receiving the DRX-disable TX profile may always wake up. RX UEs receiving two TX profiles (DRX-enabled TX profile and DRX-disable TX profile) for the same L2 ID may always receive data (always wake-up).

When the TX UE reports the TX profile along with the DST L2 ID to the gNB (using SUI/AUI), it may be necessary to inform which TX profile is applied. This may be for resource pool configuration and/or resource grant.

Alternatively, the UE may report only information on a DRX-based TX profile to a base station (BS), and the UE may receive resource information allocated by the BS based on information on the DRX-based TX profile. When the DRX-enabled TX profile and the DRX-disabled TX profile are assigned to the same DST L2 ID, the (TX) UE may report only information on the DRX-based TX profile (only the corresponding QoS profile) to the BS. In this case, the BS allocates resources to a location corresponding to the active time of the DRX configuration to be used by the TX UE, which may be inferred from this.

Alternatively, two different (for each group ID/service ID/indication) TX profile and QoS profile L2 DST ID may be reported to the BS. In this case, the TX UE may indicate a group ID (/service ID/indication) to the SR/BSR when requesting resource allocation.

Alternatively, the TX UE may report the group ID (/service ID/indication) to the gNB. For example, the DST L2 ID, cast type, and QoS profile for each group ID are transmitted to the gNB. At this time, it may separately indicate that two (/multiple) different group IDs are configured for the same L2 ID. This may be seen as playing a different role than the aforementioned indication.

Hereinafter, embodiments related to the case in which available DRX configurations are different when the same L2 DST address is generated for different serving IDs (and/or group IDs) and QoS profiles of respective serving IDs (and/or group IDs) are different will be described (Needless to say, even in this case, the LCP procedure in consideration with the aforementioned group ID(/service ID/indication) may be applied in the same way).

As an example, a TX UE (/RX UE) may apply a different DRX configuration according to a group ID. For example, when the same DST L2 ID is generated for different services, a group ID (/service ID/indication described above) may be transmitted together when a packet is transmitted from a higher layer to the AS layer. The TX UE may determine the SL DRX configuration according to a QoS profile according to each group ID (/service ID). For example, for the same DST L2 ID, different DRX configurations (e.g., on-duration, inactive time, DRC cycle, start offset, slot offset etc.) may be applied and transmitted according to the group ID (/service ID).

As another example, when the TX UE reports a DST L2 ID, a TX profile, a cast type, etc. to a BS through SUI/AUI, etc., a QoS profile may be transmitted for each group ID (/service ID/indication). In this case, a gNB may consider that the TX UE uses a DRX configuration suitable for a QoS profile for each group ID (/service ID), and allocate an appropriate resource. To this end, the TX UE may transmit a group ID (/service ID/indication) in SR/BSR when requesting a resource. For example, the TX UE may report a DST L2 ID, a TX profile, a cast type, a QoS profile, etc. together with the group ID for each group ID (service ID).

Alternatively, the TX UE may indicate that different group IDs (/service IDs) are mapped to the same L2 ID, and indicate how many group IDs (/service IDs) have become one same L2 ID. Instead of reporting a Group ID directly, several group IDs may be indicated by simple numerical values (<NUM>, <NUM>, <NUM>, etc.) to report a DST L2 ID, a TX profile, a cast type, a QoS profile, etc. for each numerical value representing each group ID. This may reduce signaling overhead compared to using a group ID (/service ID) or the like.

When the RX UE derives several L2 IDs with the same group IDs(/service IDs) to be received by the RX UE, the RX UE may estimate a DRX configuration using a QoS profile corresponding to each group ID (/service ID) and receive desired data by applying each DRX configuration for each group ID(/service ID).

A UE related to the above description includes at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations, the operations including selecting a destination having a logical channel (LCH) with a highest priority among available sidelink data for transmission; generating a Medium Access Control Protocol Data Unit (MAC PDU) from data related to the destination; and transmitting the MAC PDU at an active time, wherein the data related to the destination is data related to the active time among a plurality of data related to the destination, and the UE determines the data related to the active time among the plurality of data related to the destination based on a service ID.

The UE may communicate with at least one of another UE, a UE related to an autonomous vehicle, a BS, or a network.

In addition, in a processor for performing operations for the UE, the operations include: selecting a destination having logical channel (LCH) with a highest priority among available sidelink data for transmission; generating a Medium Access Control Protocol Data Unit (MAC PDU) from data related to the destination; and transmitting the MAC PDU at an active time, wherein the data related to the destination is data related to the active time among a plurality of data related to the destination, and the UE determines the data related to the active time among the plurality of data related to the destination based on a service ID.

In addition, in a non-volatile computer readable storage medium storing at least one computer program including instructions that when executed by at least one processor, cause the at least one processor to perform operations for a UE, the operations including: selecting a destination having a logical channel (LCH) with a highest priority among sidelink data available for transmission; generating a Medium Access Control Protocol Data Unit (MAC PDU) from data related to the destination; and transmitting the MAC PDU at an active time, wherein the data related to the destination is data related to the active time among a plurality of data related to the destination, and the UE determines the data related to the active time among the plurality of data related to the destination based on a service ID.

Referring to <FIG>, a communication system <NUM> applied to the present disclosure includes wireless devices, BSs, and a network. Herein, the wireless devices represent devices performing communication using RAT (e.g., <NUM> NR or LTE) and may be referred to as communication/radio/<NUM> devices. The wireless devices may include, without being limited to, a robot 100a, vehicles 100b-<NUM> and 100b-<NUM>, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet of things (IoT) device 100f, and an artificial intelligence (AI) device/server <NUM>. Herein, the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). 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) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). For example, the BSs and the network may be implemented as wireless devices and a specific wireless device 200a may operate as a BS/network node with respect to other wireless devices.

For example, the vehicles 100b-<NUM> and 100b-<NUM> may perform direct communication (e.g. V2V/V2X communication).

Wireless communication/connections 150a, 150b, or 150c may be established between the wireless devices 100a to 100f/BS <NUM>, or BS <NUM>/BS <NUM>. Herein, the wireless communication/connections may be established through various RATs (e.g., <NUM> NR) such as UL/DL communication 150a, sidelink communication 150b (or, D2D communication), or inter BS communication (e.g. relay, integrated access backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150a and 150b. For example, the wireless communication/connections 150a and 150b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

The one or more processors <NUM> and <NUM> may generate one or more Protocol Data Units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

As an 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 the one or more processors <NUM> and <NUM>.

Unclaimed examples of a vehicle or an autonomous driving vehicle applicable to the present disclosure.

<FIG> illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure. The vehicle or autonomous driving vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned aerial vehicle (AV), a ship, etc..

Referring to <FIG>, a vehicle or autonomous driving vehicle <NUM> may include an antenna unit <NUM>, a communication unit <NUM>, a control unit <NUM>, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d.

The control unit <NUM> may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle <NUM>. The control unit <NUM> may include an ECU. The driving unit 140a may cause the vehicle or the autonomous driving vehicle <NUM> to drive on a road. The driving unit 140a may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit 140b may supply power to the vehicle or the autonomous driving vehicle <NUM> and include a wired/wireless charging circuit, a battery, etc. The sensor unit 140c may acquire a vehicle state, ambient environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight 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 illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like.

For example, the communication unit <NUM> may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit <NUM> may control the driving unit 140a such that the vehicle or the autonomous driving vehicle <NUM> may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit <NUM> may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140c may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit <NUM> may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles.

<FIG> illustrates a vehicle applied to the present disclosure. The vehicle may be implemented as a transport means, an aerial vehicle, a ship, etc..

Referring to <FIG>, a vehicle <NUM> may include a communication unit <NUM>, a control unit <NUM>, a memory unit <NUM>, an I/O unit 140a, and a positioning unit 140b.

The communication unit <NUM> may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles or BSs. The control unit <NUM> may perform various operations by controlling constituent elements of the vehicle <NUM>. The memory unit <NUM> may store data/parameters/programs/code/commands for supporting various functions of the vehicle <NUM>. The I/O unit 140a may output an AR/VR object based on information within the memory unit <NUM>. The I/O unit 140a may include an HUD. The positioning unit 140b may acquire information about the position of the vehicle <NUM>. The position information may include information about an absolute position of the vehicle <NUM>, information about the position of the vehicle <NUM> within a traveling lane, acceleration information, and information about the position of the vehicle <NUM> from a neighboring vehicle. The positioning unit 140b may include a GPS and various sensors.

As an example, the communication unit <NUM> of the vehicle <NUM> may receive map information and traffic information from an external server and store the received information in the memory unit <NUM>. The positioning unit 140b may obtain the vehicle position information through the GPS and various sensors and store the obtained information in the memory unit <NUM>. The control unit <NUM> may generate a virtual object based on the map information, traffic information, and vehicle position information and the I/O unit 140a may display the generated virtual object in a window in the vehicle (<NUM> and <NUM>). The control unit <NUM> may determine whether the vehicle <NUM> normally drives within a traveling lane, based on the vehicle position information. If the vehicle <NUM> abnormally exits from the traveling lane, the control unit <NUM> may display a warning on the window in the vehicle through the I/O unit 140a. In addition, the control unit <NUM> may broadcast a warning message regarding driving abnormity to neighboring vehicles through the communication unit <NUM>. According to situation, the control unit <NUM> may transmit the vehicle position information and the information about driving/vehicle abnormality to related organizations.

<FIG> illustrates an XR device applied to the present disclosure. The XR device may be implemented by an HMD, an HUD mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc..

Referring to <FIG>, an XR device 100a may include a communication unit <NUM>, a control unit <NUM>, a memory unit <NUM>, an I/O unit 140a, a sensor unit 140b, and a power supply unit 140c.

The communication unit <NUM> may transmit and receive signals (e.g., media data and control signals) to and from external devices such as other wireless devices, hand-held devices, or media servers. The media data may include video, images, and sound. The control unit <NUM> may perform various operations by controlling constituent elements of the XR device 100a. For example, the control unit <NUM> may be configured to control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata generation and processing. The memory unit <NUM> may store data/parameters/programs/code/commands needed to drive the XR device 100a/generate XR object. The I/O unit 140a may obtain control information and data from the exterior and output the generated XR object. The I/O unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit 140b may obtain an XR device state, surrounding environment information, user information, etc. The sensor unit 140b may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone and/or a radar. The power supply unit 140c may supply power to the XR device 100a and include a wired/wireless charging circuit, a battery, etc..

For example, the memory unit <NUM> of the XR device 100a may include information (e.g., data) needed to generate the XR object (e.g., an AR/VR/MR object). The I/O unit 140a may receive a command for manipulating the XR device 100a from a user and the control unit <NUM> may drive the XR device 100a according to a driving command of a user. For example, when a user desires to watch a film or news through the XR device 100a, the control unit <NUM> transmits content request information to another device (e.g., a hand-held device 100b) or a media server through the communication unit <NUM>. The communication unit <NUM> may download/stream content such as films or news from another device (e.g., the hand-held device 100b) or the media server to the memory unit <NUM>. The control unit <NUM> may control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata generation/processing with respect to the content and generate/output the XR object based on information about a surrounding space or a real object obtained through the I/O unit 140a/sensor unit 140b.

The XR device 100a may be wirelessly connected to the hand-held device 100b through the communication unit <NUM> and the operation of the XR device 100a may be controlled by the hand-held device 100b. For example, the hand-held device 100b may operate as a controller of the XR device 100a. To this end, the XR device 100a may obtain information about a 3D position of the hand-held device 100b and generate and output an XR object corresponding to the hand-held device 100b.

<FIG> illustrates a robot applied to the present disclosure. The robot may be categorized into an industrial robot, a medical robot, a household robot, a military robot, etc., according to a used purpose or field.

Referring to <FIG>, a robot <NUM> may include a communication unit <NUM>, a control unit <NUM>, a memory unit <NUM>, an I/O unit 140a, a sensor unit 140b, and a driving unit 140c. Herein, the blocks <NUM> to <NUM>/140a to 140c correspond to the blocks <NUM> to <NUM>/<NUM> of <FIG>, respectively.

The communication unit <NUM> may transmit and receive signals (e.g., driving information and control signals) to and from external devices such as other wireless devices, other robots, or control servers. The control unit <NUM> may perform various operations by controlling constituent elements of the robot <NUM>. The memory unit <NUM> may store data/parameters/programs/code/commands for supporting various functions of the robot <NUM>. The I/O unit 140a may obtain information from the exterior of the robot <NUM> and output information to the exterior of the robot <NUM>. The I/O unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit 140b may obtain internal information of the robot <NUM>, surrounding environment information, user information, etc. The sensor unit 140b may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, a radar, etc. The driving unit 140c may perform various physical operations such as movement of robot joints. In addition, the driving unit 140c may cause the robot <NUM> to travel on the road or to fly. The driving unit 140c may include an actuator, a motor, a wheel, a brake, a propeller, etc..

<FIG> illustrates an AI device applied to the present disclosure. The AI device may be implemented by a fixed device or a mobile device, such as a TV, a projector, a smartphone, a PC, a notebook, a digital broadcast terminal, a tablet PC, a wearable device, a Set Top Box (STB), a radio, a washing machine, a refrigerator, a digital signage, a robot, a vehicle, etc..

Referring to <FIG>, an AI device <NUM> may include a communication unit <NUM>, a control unit <NUM>, a memory unit <NUM>, an I/O unit 140a/140b, a learning processor unit 140c, and a sensor unit 140d. The blocks <NUM> to <NUM>/140a to 140d correspond to blocks <NUM> to <NUM>/<NUM> of <FIG>, respectively.

The communication unit <NUM> may transmit and receive wired/radio signals (e.g., sensor information, user input, learning models, or control signals) to and from external devices such as other AI devices (e.g., 100x, <NUM>, or <NUM> of <FIG>) or an AI server (e.g., <NUM> of <FIG>) using wired/wireless communication technology. To this end, the communication unit <NUM> may transmit information within the memory unit <NUM> to an external device and transmit a signal received from the external device to the memory unit <NUM>.

The control unit <NUM> may determine at least one feasible operation of the AI device <NUM>, based on information which is determined or generated using a data analysis algorithm or a machine learning algorithm. The control unit <NUM> may perform an operation determined by controlling constituent elements of the AI device <NUM>. For example, the control unit <NUM> may request, search, receive, or use data of the learning processor unit 140c or the memory unit <NUM> and control the constituent elements of the AI device <NUM> to perform a predicted operation or an operation determined to be preferred among at least one feasible operation. The control unit <NUM> may collect history information including the operation contents of the AI device <NUM> and operation feedback by a user and store the collected information in the memory unit <NUM> or the learning processor unit 140c or transmit the collected information to an external device such as an AI server (<NUM> of <FIG>). The collected history information may be used to update a learning model.

The memory unit <NUM> may store data for supporting various functions of the AI device <NUM>. For example, the memory unit <NUM> may store data obtained from the input unit 140a, data obtained from the communication unit <NUM>, output data of the learning processor unit 140c, and data obtained from the sensor unit <NUM>. The memory unit <NUM> may store control information and/or software code needed to operate/drive the control unit <NUM>.

The input unit 140a may acquire various types of data from the exterior of the AI device <NUM>. For example, the input unit 140a may acquire learning data for model learning, and input data to which the learning model is to be applied. The input unit 140a may include a camera, a microphone, and/or a user input unit. The output unit 140b may generate output related to a visual, auditory, or tactile sense. The output unit 140b may include a display unit, a speaker, and/or a haptic module. The sensing unit <NUM> may obtain at least one of internal information of the AI device <NUM>, surrounding environment information of the AI device <NUM>, and user information, using various sensors. The sensor unit <NUM> may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, and/or a radar.

The learning processor unit 140c may learn a model consisting of artificial neural networks, using learning data. The learning processor unit 140c may perform AI processing together with the learning processor unit of the AI server (<NUM> of <FIG>). The learning processor unit 140c may process information received from an external device through the communication unit <NUM> and/or information stored in the memory unit <NUM>. In addition, an output value of the learning processor unit 140c may be transmitted to the external device through the communication unit <NUM> and may be stored in the memory unit <NUM>.

The above-described embodiments of the present disclosure are applicable to various mobile communication systems.

Claim 1:
A transmission method related to a groupcast of a user equipment, UE, in a wireless communication system, the method comprising:
receiving a service ID from a higher layer,
selecting (S1401) a destination having a logical channel, LCH, with a highest priority among available sidelink data for transmission;
collecting data with same service ID as the service ID among a plurality of data related to the destination, wherein each of the plurality of data are related to two or more service ID,
generating (S1402) a Medium Access Control Protocol Data Unit, MAC PDU, from the collected data; and
transmitting (S1403) the MAC PDU at an active time of a Discontinuous Reception, DRX, cycle related to a TX profile which is configured to the service ID.