SIDELINK COMMUNICATION METHOD CONSIDERING HEIGHT INFORMATION AND APPARATUS THEREFOR

Abstract

A sidelink communication method considering height information and an apparatus therefor are provided. A method of transmitting data by a first user equipment (UE) to a second UE in a wireless communication system includes transmitting a physical sidelink control channel (PSCCH) including first sidelink control information (SCI) to the second UE, transmitting a physical sidelink shared channel (PSSCH) including second SCI related to the first SCI to the second UE, and receiving a physical sidelink feedback channel (PSFCH) for the PSSCH from the second UE. The second SCI includes control information about a hybrid automatic repeat request (HARQ) operation, and the control information about the HARQ operation includes control information about a height.

Claims

1. A method of transmitting data by a first user equipment (UE) to a second UE in a wireless communication system, the method comprising: transmitting a physical sidelink control channel (PSCCH) including first sidelink control information (SCI) to the second UE; transmitting a physical sidelink shared channel (PSSCH) including second SCI related to the first SCI to the second UE; and receiving a physical sidelink feedback channel (PSFCH) for the PSSCH from the second UE, wherein the second SCI includes control information about a hybrid automatic repeat request (HARQ) operation, and wherein the control information about the HARQ operation includes control information about a height.

2. The method of claim 1, wherein the control information about the HARQ operation includes a zone ID, and wherein the zone ID includes the control information about the height, determined in consideration of a sidelink zone length (sl-ZoneLength), and a horizontal distance x and a vertical distance y at the same height in relationship with a current position of the first UE or the second UE, and a height z.

3. The method of claim 2, wherein the sidelink zone length (sl-ZoneLength) includes, through radio resource control (RRC) signaling, configuration information about a first length L1 applied commonly to the horizontal distance x and the vertical distance y, and a second length L2 applied to the height z.

4. The method of claim 3, wherein the second length L2 is set to be larger than the first length L1.

5. The method of claim 3, wherein the zone ID (Zone_ID) satisfies:
Zone_ID=1st zone_id*N2+z1, or
Zone_ID=z1*(2*N1)+1st zone_id, based on a first zone ID (1st zone_id) determined based on the horizontal distance x and the vertical distance y, wherein z1 satisfies
z1=Floor(z/L2)Mod N2, wherein N1 represents the number of zones in the horizontal distance x and the vertical distance y, and N2 represents the number of zones in the height z.

6. The method of claim 5, wherein N2 is set to be smaller than N1.

7. The method of claim 5, wherein the first zone ID (1st zone_id) satisfies
x.sub.1=Floor(x/L1)Mod N1;
y.sub.1=Floor(y/L1)Mod N1;
1st zone_id=y.sub.1*N1+x.sub.1.

8. The method of claim 1, wherein the control information about the HARQ operation includes a destination ID, and the destination ID includes control information about a height of the second UE.

9. The method of claim 8, wherein the destination ID is configured by a combination of a first bitstream corresponding to a service common ID and a second bitstream indicating a range of the height of the second UE.

10. The method of claim 1, wherein the control information about the HARQ operation includes a destination ID and minimum communication range (MCR) information, and wherein the control information about the height is indicated by a combination of the destination ID and the MCR information.

11. A first user equipment (UE) for performing sidelink communication in a wireless communication system, the first UE comprising: at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, wherein the operations comprise: transmitting a physical sidelink control channel (PSCCH) including first sidelink control information (SCI) to a second UE; transmitting a physical sidelink shared channel (PSSCH) including second SCI related to the first SCI to the second UE; and receiving a physical sidelink feedback channel (PSFCH) for the PSSCH from the second UE, wherein the second SCI includes control information about a hybrid automatic repeat request (HARQ) operation, and wherein the control information about the HARQ operation includes control information about a height.

12. A processor for performing operations for a first user equipment (UE) performing sidelink communication in a wireless communication system, the operations comprising: transmitting a physical sidelink control channel (PSCCH) including first sidelink control information (SCI) to a second UE; transmitting a physical sidelink shared channel (PSSCH) including second SCI related to the first SCI to the second UE; and receiving a physical sidelink feedback channel (PSFCH) for the PSSCH from the second UE, wherein the second SCI includes control information about a hybrid automatic repeat request (HARQ) operation, and wherein the control information about the HARQ operation includes control information about a height.

13. 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 first user equipment (UE), the operations comprising: transmitting a physical sidelink control channel (PSCCH) including first sidelink control information (SCI) to a second UE; transmitting a physical sidelink shared channel (PSSCH) including second SCI related to the first SCI to the second UE; and receiving a physical sidelink feedback channel (PSFCH) for the PSSCH from the second UE, wherein the second SCI includes control information about a hybrid automatic repeat request (HARQ) operation, and wherein the control information about the HARQ operation includes control information about a height.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the principle of the disclosure. In the drawings:

[0051] FIG. 1 is a diagram illustrating V2X communication based on pre-NR RAT and V2X communication based on NR in comparison.

[0052] FIG. 2 illustrates the structure of an NR system according to an embodiment of the present disclosure.

[0053] FIG. 3 illustrates functional split between the NG-RAN and the 5GC according to an embodiment of the present disclosure.

[0054] FIG. 4 illustrates a radio protocol architecture according to an embodiment of the present disclosure.

[0055] FIG. 5 illustrates a radio protocol architecture for SL communication according to an embodiment of the present disclosure.

[0056] FIG. 6 illustrates a synchronization source or a synchronization reference of V2X according to an embodiment of the present disclosure.

[0057] FIG. 7 illustrates a procedure of performing V2X or SL communication by a UE based on a transmission mode according to an embodiment of the present disclosure.

[0058] FIG. 8 illustrates a communication system 1 applied to the present disclosure.

[0059] FIG. 9 illustrates wireless devices applicable to the present disclosure.

[0060] FIG. 10 illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure.

[0061] FIG. 11 illustrates a vehicle applied to the present disclosure.

[0062] FIG. 12 illustrates a robot applied to the present disclosure.

[0063] FIG. 13 illustrates an AI device applied to the present disclosure.

DETAILED DESCRIPTION

[0064] In various embodiments of the present disclosure, “/” and “,” should be interpreted as “and/or”. For example, “A/B” may mean “A and/or B”. 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”.

[0065] 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”.

[0066] 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 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved-UTRA (E-UTRA), or the like. IEEE 802.16m is an evolution of IEEE 802.16e, offering backward compatibility with an IRRR 802.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.

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

[0068] While the following description is given mainly in the context of LTE-A or 5G NR for the clarity of description, the technical idea of an embodiment of the present disclosure is not limited thereto.

[0069] FIG. 2 illustrates the structure of an NR system according to an embodiment of the present disclosure.

[0070] Referring to FIG. 2, 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.

[0071] In FIG. 2, 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 5G 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.

[0072] FIG. 3 illustrates functional split between the NG-RAN and the 5GC according to an embodiment of the present disclosure.

[0073] Referring to FIG. 3, 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.

[0074] 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 1 (L1), Layer 2 (L2) and Layer 3 (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.

[0075] FIG. 4 illustrates a radio protocol architecture according to an embodiment of the present disclosure.

[0076] The embodiment of FIG. 4 may be combined with various embodiments of the present disclosure. Specifically, FIG. 4(a) illustrates a radio protocol architecture for a user plane, and FIG. 4(b) illustrates a radio protocol architecture for a control plane. The user plane is a protocol stack for user data transmission, and the control plane is a protocol stack for control signal transmission.

[0077] Referring to FIG. 4, 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.

[0078] 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.

[0079] 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.

[0080] 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).

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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).

[0087] 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.

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

[0089] FIG. 5 illustrates a radio protocol architecture for SL communication according to an embodiment of the present disclosure. Specifically, FIG. 5(a) illustrates a user-plane protocol stack in LTE, and FIG. 5(b) illustrates a control-plane protocol stack in LTE.

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

[0091] The SLSS is an SL-specific sequence, and 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-127 M-sequences may be used for the S-PSS, and length-127 gold sequences may be used for the S-SSS. For example, the UE may detect an initial signal and acquire synchronization using the S-PSS. For example, the UE may acquire detailed synchronization using the S-PSS and the S-SSS, and may detect a synchronization signal ID.

[0092] A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel on which basic (system) information that the UE needs to know first before transmission and reception of an SL signal is transmitted. For example, the basic information may include SLSS related information, a duplex mode (DM), time division duplex uplink/downlink (TDD UL/DL) configuration, resource pool related information, the type of an application related to the SLSS, a subframe offset, and broadcast information. For example, for evaluation of PSBCH performance, the payload size of PSBCH in NR V2X may be 56 bits including CRC of 24 bits.

[0093] The S-PSS, S-SSS, and PSBCH may be included in a block format (e.g., an SL synchronization signal (SS)/PSBCH block, hereinafter sidelink-synchronization signal block (S-SSB)) supporting periodic transmission. The S-SSB may have the same numerology (i.e., SCS and CP length) as a physical sidelink control channel (PSCCH)/physical sidelink shared channel (PSSCH) in the carrier, and the transmission bandwidth thereof may be within a (pre)set sidelink BWP (SL BWP). For example, the bandwidth of the S-SSB may be 11 resource blocks (RBs). For example, the PSBCH may span 11 RBs. The frequency position of the S-SSB may be (pre)set. Accordingly, the UE does not need to perform hypothesis detection at a frequency to discover the S-SSB in the carrier.

[0094] Hereinafter, synchronization acquisition by an SL UE will be described.

[0095] In TDMA and FDMA systems, accurate time and frequency synchronization is essential. Inaccurate time and frequency synchronization may lead to degradation of system performance due to inter-symbol interference (ISI) and inter-carrier interference (ICI). The same is true for V2X. For time/frequency synchronization in V2X, a sidelink synchronization signal (SLSS) may be used in the PHY layer, and master information block-sidelink-V2X (MIB-SL-V2X) may be used in the RLC layer.

[0096] FIG. 6 illustrates a synchronization source or a synchronization reference of V2X according to an embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure.

[0097] Referring to FIG. 6, in V2X, a UE may be directly synchronized with a global navigation satellite system (GNSS) or may be indirectly synchronized with the GNSS through a UE (in network coverage or out of network coverage) that is directly synchronized with the GNSS. If the GNSS is configured as a synchronization source, a UE may calculate a direct frame number (DFN) and a subframe number using coordinated universal time (UTC) and a (pre)configured DFN offset.

[0098] 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.

[0099] 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.

[0100] 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.

[0101] An SL synchronization source may be associated with a synchronization priority level. For example, the relationship between synchronization sources and synchronization priority levels may be defined as shown in Table 1 or Table 2. Table 1 or Table 2 are purely exemplary and the relationship between the synchronization sources and the synchronization priority levels may be defined in various manners.

TABLE-US-00001 TABLE 1 Priority GNSS-based eNB/gNB-based Level Synchronization Synchronization P0 GNSS eNB/gNB P1 All UEs directly All UEs directly synchronized synchronized with eNB/gNB with GNSS P2 All UEs indirectly All UEs indirectly synchronized synchronized with eNB/gNB with GNSS P3 All other UEs GNSS P4 N/A All UEs directly synchronized with GNSS P5 N/A All UEs indirectly synchronized with GNSS P6 N/A All other UEs

TABLE-US-00002 TABLE 2 Priority GNSS-based eNB/gNB-based level synchronization synchronization P0 GNSS eNB/gNB P1 All UEs synchronized All UEs synchronized directly with GNSS directly with eNB/gNB P2 All UEs synchronized All UEs synchronized indirectly with GNSS indirectly with eNB/gNB P3 eNB/gNB GNSS P4 All UEs synchronized All UEs synchronized directly with eNB/gNB directly with GNSS P5 All UEs synchronized All UEs synchronized indirectly with eNB/gNB indirectly with GNSS P6 Remaining UE(s) with Remaining UE(s) with lower priority lower priority

[0102] In Table 1 or Table 2, P0 may represent the highest priority, and P6 may represent the lowest priority. In Table 1 or Table 2, the BS may include at least one of a gNB or an eNB.

[0103] 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.

[0104] For example, the UE may (re)select a synchronization reference and obtain synchronization from the synchronization reference. Based on the obtained synchronization, the UE may perform SL communication (e.g., PSCCH/PSSCH transmission/reception, physical sidelink feedback channel (PSFCH) transmission/reception, S-SSB transmission/reception, reference signal transmission/reception, etc.).

[0105] FIG. 7 illustrates a procedure of performing V2X or SL communication by a UE based on a transmission mode according to an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, a transmission mode may also be referred to as a mode or a resource allocation mode. For convenience of 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.

[0106] For example, FIG. 7(a) illustrates a UE operation related to LTE transmission mode 1 or LTE transmission mode 3. Alternatively, for example, FIG. 7(a) illustrates a UE operation related to NR resource allocation mode 1. For example, LTE transmission mode 1 may be applied to general SL communication, and LTE transmission mode 3 may be applied to V2X communication.

[0107] For example, FIG. 7(b) illustrates a UE operation related to LTE transmission mode 2 or LTE transmission mode 4. Alternatively, for example, FIG. 7(b) illustrates a UE operation related to NR resource allocation mode 2.

[0108] Referring to FIG. 7(a), in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, a BS may schedule SL resources to be used by a UE for SL transmission. For example, in step S8000, the BS may transmit information related to an SL resource and/or information related to a UL resource to a first UE. For example, the UL resource may include a PUCCH resource and/or a PUSCH resource. For example, the UL resource may be a resource for reporting SL HARQ feedback to the BS.

[0109] 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 1 resource or a CG type 2 resource. In the present specification, the DG resource may be a resource configured/allocated by the BS for/to the first UE through downlink control information (DCI). In the present specification, the CG resource may be a (periodic) resource configured/allocated by the BS for/to the first UE through DCI and/or RRC messages. For example, in the case of the CG type 1 resource, the BS may transmit an RRC message including information related to the CG resource to the first UE. For example, in the case of the CG type 2 resource, the BS may transmit the RRC message including the information related to the CG resource to the first UE, and the BS may transmit DCI related to activation or release of the CG resource to the first UE.

[0110] In step S8010, the first UE may transmit a PSCCH (e.g., sidelink control information (SCI) or a 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, a 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 through the PSFCH. In step S8040, the first UE may transmit/report HARQ feedback information to the BS through a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the BS may include information generated by the first UE based on the 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 include DCI for scheduling of SL. For example, a format of the DCI may include DCI format 3_0 or DCI format 3_1.

[0111] Table 3 shows an example of DCI for scheduling SL.

TABLE-US-00003 TABLE 3 3GPP TS 38.212 7.3.1.4.1 Format 3_0 DCI format 3_0 is used for scheduling of NR PSCCH and NR PSSCH in one cell. The following information is transmitted by means of the DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS- RNTI: - Resource pool index -┌log.sub.2 I┐ bits, where I is the number of resource pools for transmission configured by the higher layer parameter sl-TxPoolScheduling. - Time gap - 3 bits determined by higher layer parameter sl-DCI-ToSL-Trans, as defined in clause 8.1.2.1 of [6, TS 38.214] - HARQ process number - 4 bits as defined in clause 16.4 of [5, TS 38.213] - New data indicator - 1 bit as defined in clause 16.4 of [5, TS 38.213] - Lowest index of the subchannel allocation to the initial transmission - ┌log.sub.2(N.sub.subchannel.sup.Sl)┐ bits as defined in clause 8.1.2.2 of [6, TS 38.214] - SCI format 1-A fields according to clause 8.3.1.1: - Frequency resource assignment. - Time resource assignment. - PSFCH-to-HARQ feedback timing indicator -┌log.sub.2 N.sub.fb_timing┐ bits, where N.sub.fb_timing is the number of entries in the higher layer parameter sl-PSFCH-ToPUCCH, as defined in clause 16.5 of [5, TS 38.213] - PUCCH resource indicator - 3 bits as defined in clause 16.5 of [5, TS 38.213]. - Configuration index - 0 bit if the UE is not configured to monitor DCI format 3_0 with CRC scrambled by SL- CS-RNTI; otherwise 3 bits as defined in clause 8.1.2 of [6, TS 38.214]. If the UE is configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled by SL-RNTI. - Counter sidelink assignment index - 2 bits - 2 bits as defined in clause 16.5.2 of [5, TS 38.213] if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic - 2 bits as defined in clause 16.5.1 of [5, TS 38.213] if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static - Padding bits, if required 7.3.1.4.2 Format 3_1 DCI format 3_1 is used for scheduling of LTE PSCCH and LTE PSSCH in one cell. The following information is transmitted by means of the DCI format 3_1 with CRC scrambled by SL-L-CS-RNTI: - Timing offset - 3 bits determined by higher layer parameter sl-TimeOffsetEUTRA, as defined in clause 16.6 of [5, TS 38.213] - Carrier indicator -3 bits as defined in 5.3.3.1.9A of [11, TS 36.212]. - Lowest index of the subchannel allocation to the initial transmission - ┌log.sub.2(N.sub.subchannel.sup.Sl)┐ bits as defined in 5.3.3.1.9A of [11, TS 36.212]. - Frequency resource location of initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212] - Time gap between initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212] - SL index - 2 bits as defined in 5.3.3.1.9A of [11, TS 36.212] - SL SPS configuration index - 3 bits as defined in clause 5.3.3.1.9A of [11, TS 36.212]. - Activation/release indication - 1 bit as defined in clause 5.3.3.1.9A of [11, TS 36.212].

[0112] Referring to FIG. 7(b), in LTE transmission mode 2, LTE transmission mode 4, or NR resource allocation mode 2, a UE may determine an SL transmission resource within SL resources configured by a BS/network or within preconfigured SL resources. For example, the configured SL resources or the preconfigured SL resources 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 from the configured resource pool. For example, the UE may perform sensing and resource (re)selection procedures, thereby selecting a resource by itself within a selection window. For example, the sensing may be performed in a subchannel unit. For example, in step S8010, the first UE that selects a resource by itself from a resource pool may transmit a PSCCH (e.g., SCI or 1st-stage SCI) to the second UE using the resource. In step S8020, the first UE may transmit a PSSCH (e.g., 2nd-stage SCI, a 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.

[0113] Referring to FIG. 7(a) or FIG. 7(b), for example, the first UE may transmit SCI to the second UE on the PSCCH. Alternatively, for example, the first UE may transmit two consecutive SCI (e.g., 2-stage SCI) on the PSCCH and/or PSSCH to the second UE. In this case, the second UE may decode the two consecutive SCI (e.g., 2-stage SCI) to receive the PSSCH from the first UE. In the present disclosure, the SCI transmitted on the PSCCH may be referred to as 1st SCI, first SCI, 1st-stage SCI, or a 1st-stage SCI format, and the SCI transmitted on the PSSCH may be referred to as 2nd SCI, second SCI, 2nd-stage SCI, or a 2nd-stage SCI format. For example, the 1st-stage SCI format may include SCI format 1-A, and the 2nd-stage SCI format may include SCI format 2-A and/or SCI format 2-B.

[0114] Table 4 shows an example of the 1st-stage SCI format.

TABLE-US-00004 TABLE 4 3GPP TS 38.212 8.3.1.1 SCI format 1-A SCI format 1-A is used for the scheduling of PSSCH and 2.sup.nd-stage-SCI on PSSCH The following information is transmitted by means of the SCI format 1-A:  - Priority − 3 bits as specified in clause 5.4.3.3 of [12, TS 23.287] and  clause 5.22.1.3.1 of [8, TS 38.321].  [00001]$‐\mathrm{Frequency}\mathrm{resource}\mathrm{assignment}-.Math.{\log }_2\left(\frac{N_{\mathrm{subChannel}}^{\mathrm{SL}}\left(N_{\mathrm{subChannel}}^{\mathrm{SL}}+1\right)}{2}\right).Math.$  bits when the value of the higher layer parameter sl-MaxNumPerReserve  is configured to 2; otherwise  [00002]$.Math.{\log }_2\left(\frac{N_{\mathrm{subChannel}}^{\mathrm{SL}}\left(N_{\mathrm{subChannel}}^{\mathrm{SL}}+1\right)\left(2N_{\mathrm{subChannel}}^{\mathrm{SL}}+1\right)}{6}\right).Math.\mathrm{bits}\mathrm{when}\mathrm{the}$  value of the higher layer parameter sl-MaxNumPerReserve is  configured to 3, as defined in clause 8.1.2.2 of [6, TS 38.214].  - Time resource assignment − 5 bits when the value of the higher layer  parameter sl-MaxNumPerReserve is configured to 2; otherwise 9 bits  when the value of the higher layer parameter sl-MaxNumPerReserve  is configured to 3, as defined in clause 8.1.2.1 of [6, TS 38.214].  - Resource reservation period − ┌log.sub.2 N.sub.rsv_period┐ bits as defined in  clause 8.1.4 of [6, TS 38.214], where N.sub.rsv_period is the number of entries  in the higher layer parameter sl-ResourceReservePeriodList, if higher  layer parameter sl-MultiReserveResource is configured; 0 bit otherwise.  - DMRS pattern − ┌log.sub.2 N.sub.pattern┐ bits as defined in clause 8.4.1.1.2 of  [4, TS 38.211], where N.sub.pattern is the number of DMRS patterns  configured by higher layer parameter sl-PSSCH-DMRS-  TimePatternList.  - 2.sup.nd-stage SCI format − 2 bits as defined in Table 8.3.1.1-1.  - Beta_offset indicator − 2 bits as provided by higher layer parameter  sl-BetaOffsets2ndSCI and Table 8.3.1.1-2.  - Number of DMRS port − 1 bit as defined in Table 8.3.1.1-3.  - Modulation and coding scheme − 5 bits as defined in clause 8.1.3 of  [6, TS 38.214].  - Additional MCS table indicator − as defined in clause 8.1.3.1 of [6, TS  38.214]: 1 bit if one MCS table is configured by higher layer parameter  sl-Additional-MCS-Table; 2 bits if two MCS tables are configured by  higher layer parameter sl- Additional-MCS-Table; 0 bit otherwise.  - PSFCH overhead indication − 1 bit as defined clause 8.1.3.2 of [6, TS  38.214] if higher layer parameter sl-PSFCH-Period = 2 or 4; 0 bit  otherwise.  - Reserved − a number of bits as determined by higher layer parameter  sl-NumReservedBits, with value set to zero. Table 8.3.1.1-1: 2.sup.nd-stage SCI formats Value of 2nd-stage SCI format field 2nd-stage SCI format 00 SCI format 2-A 01 SCI format 2-B 10 Reserved 11 Reserved Table 8.3.1.1-2: Mapping of Beta_offset indicator values to indexes in Table 9.3-2 of [5, TS38.213] Value of Beta_offset index in Beta_offset indicator Table 9.3-2 of [5, TS38.213] 00 1st index provided by higher layer parameter sl-BetaOffsets2ndSCI 01 2nd index provided by higher layer parameter sl-BetaOffsets2ndSCI 10 3rd index provided by higher layer parameter sl-BetaOffsets2ndSCI 11 4th index provided by higher layer parameter sl-BetaOffsets2ndSCI Table 8.3.1.1-3: Number of DMRS port(s) Value of the Number of DMRS port field Antenna ports 0 1000 1 1000 and 1001

[0115] Table 5 shows an example of the 2nd-stage SCI format.

TABLE-US-00005 TABLE 5 3GPP TS 38.212 8.4.1.1 SCI format 2-A SCI format 2-A is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes ACK or NACK, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. The following information is transmitted by means of the SCI format 2-A: - HARQ process number - 4 bits as defined in clause 16.4 of [5, TS 38.213]. - New data indicator - 1 bit as defined in clause 16.4 of [5, TS 38.213]. - Redundancy version - 2 bits as defined in clause 16.4 of [6, TS 38.214]. - Source ID - 8 bits as defined in clause 8.1 of [6, TS 38.214]. - Destination ID - 16 bits as defined in clause 8.1 of [6, TS 38.214]. - HARQ feedback enabled/disabled indicator - 1 bit as defined in clause 16.3 of [5, TS 38.213]. - Cast type indicator - 2 bits as defined in Table 8.4.1.1-1. - CSI request - 1 bit as defined in clause 8.2.1 of [6, TS 38.214]. Table 8.4.1.1-1: Cast type indicator Value of Cast type indicator Cast type 00 Broadcast 01 Groupcast when HARQ-ACK information includes ACK or NACK 10 Unicast 11 Groupcast when HARQ-ACK information includes only NACK 8.4.1.2 SCI format 2-B SCI format 2-B is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. The following information is transmitted by means of the SCI format 2-B: - HARQ process number - 4 bits as defined in clause 16.4 of [5, TS 38.213]. - New data indicator - 1 bit as defined in clause 16.4 of [5, TS 38.213]. - Redundancy version - 2 bits as defined in clause 16.4 of [6, TS 38.214]. - Source ID - 8 bits as defined in clause 8.1 of [6, TS 38.214]. - Destination ID - 16 bits as defined in clause 8.1 of [6, TS 38.214]. - HARQ feedback enabled/disabled indicator - 1 bit as defined in clause 16.3 of [5, TS 38.213]. - Zone ID - 12 bits as defined in clause 5.8.11 of [9, TS 38.331]. - Communication range requirement - 4 bits determined by higher layer parameter sl-ZoneConfigMCR-Index.

[0116] As shown in Table 5 above, the 2nd-stage SCI includes control information for a HARQ operation. For example, a destination ID or a zone ID of SCI format 2-A and SCI format 2-B may also be referred to as the control information for the HARQ operation, as information for specifying a target that is requested to transmit HARQ feedback.

[0117] An embodiment of the present disclosure proposes that the control information for the HARQ operation, particularly, the zone ID, be determined in consideration of a height z, as well as an SL zone length (sl-ZoneLength), and a horizontal distance x and a vertical distance y at the same height in the relationship with a current position of a first UE or a second UE, in order to smoothly perform SL communication in a three-dimensional space in which an unmanned aerial vehicle (UAV), for example, operates.

[0118] It may be possible that vertical coordinates for a height are less precise than horizontal coordinates therefor. For example, when the zone ID is determined, a zone length of the height z may use a separate parameter, and a legacy operation may be regarded as a special case in which there is only one zone length for the height.

[0119] Specifically, the SL zone length (sl-ZoneLength) may include configuration information about a first length L1 applied commonly to the horizontal distance x and the vertical distance y and about a second length L2 applied to the height z, through radio resource control (RRC) signaling.

[0120] As described above, it is desirable that the second length L2 related to the height be set to be larger than the first length L1 in a horizontal plane.

[0121] The zone ID (Zone_ID) may satisfy Equation 1 or Equation 2 below, based on a first zone ID (1st zone_id) which is determined based on the horizontal distance x and the vertical distance y.

Zone_ID=1st zone_id*N2+z1  [Equation 1]

Zone_ID=z1*(2*N1)+1st zone_id  [Equation 2]

[0122] In this case, z1 may satisfy Equation 3 below.

z1=Floor(z/L2)Mod N2  [Equation 3]

[0123] In this case, N1 represents the number of zones in the horizontal distance x and the vertical distance y, and N2 represents the number of zones in the height z.

[0124] Similarly, N2 represents the number of zones related to the height and may be desirably set to be less than N1.

[0125] Under such assumptions, the first zone ID (1st zone_id) may satisfy Equation 4 below.

x.sub.1=Floor(x/L1)Mod N1;

y.sub.1=Floor(y/L1)Mod N1;

1st zone_id=y.sub.1*N1+x.sub.1.  [Equation 4]

[0126] According to current standard regulations, since N1 is regulated as 64, when z1=Floor (z/L2) Mod N2 (where N2 is the number of zones in the height, this is configurable) is applied, the zone ID may be calculated as in Equation 5 or Equation 6 below.

Zone_ID=legacy zone ID*N+z1  [Equation 5]

Zone_ID=z1*128+legacy zone ID.  [Equation 6]

[0127] However, it is obvious that numbers in the subsequent standard may be changed with respect even to the horizontal direction as opposed to the current standard regulations.

[0128] Meanwhile, an embodiment of the present disclosure proposes that a first UE (transmission UE) specify information of a height or a range of the height in which a second UE (reception UE) that should receive messages is located, rather than the first UE directly indicating a height value thereof.

[0129] For example, the range of a height may be determined between z_min and z_max and may be split into N zones. Next, the start and length of a zone in which messages should be received may be indicated. Among UEs located at the corresponding height, UEs within a predetermined distance in a horizontal plane may perform a feedback operation. In the case of a flight vehicle operating at a constant height, such as a UAV, there may be a case in which the flight vehicle only needs to transmit data to a reception end only around the height thereof.

[0130] Meanwhile, another embodiment of the present disclosure proposes a method of adding the above-described height information using a destination ID. Although the height information may be transmitted in a part of second SCI, adding one format of a new length may be burdensome in terms of standardization. For this viewpoint, the destination ID may be used.

[0131] As an example, a specific destination ID may be set to be an ID received by only a UE in a zone of a specific height.

[0132] Specifically, a destination ID for a specific service may be generated by combining bits (a first bitstream) corresponding to a service common ID and bits (a second bitstream) corresponding to a height zone of a UE that is to receive the service. As a specific example of the latter, the bits for the height zone of the UE that is to receive the service may be indicated by a resource indication value (RIV) which is determined based on the start and length of the height zone.

[0133] As another example, a minimum communication range (MCR) value may be configured with respect to each destination ID and the height information may be included in the MCR value. Currently, since the MCR is configured with respect to every resource pool, a specific destination ID may be designated in an additional resource pool configuration, and a separately signaled zone or MCR configuration may be exceptionally applied to the corresponding destination ID.

[0134] A spare field may be used among current MCR fields of SCI format 2B. A distance value in the horizontal plane and information about a height zone of a reception UE may be mapped altogether to each spare field and operation may be performed based on the mapping.

[0135] Referring to FIG. 7(a) or 7(b), in step S8030, the first UE may receive a PSFCH based on Table 6. For example, the first UE and the second UE may determine a PSFCH resource based on Table 6, and the second UE may transmit HARQ feedback to the first UE using the PSFCH resource.

[0136] Further, the second UE that is to transmit the PSFCH may be specified based on the added height information as described above.

TABLE-US-00006 TABLE 6 3GPP TS 38.213 16.3 UE procedure for reporting HARQ-ACK on sidelink A UE can be indicated by an SCI format scheduling a PSSCH reception, in one or more sub-channels from a number of N.sub.subch.sup.PSSCH sub-channels, to transmit a PSFCH with HARQ-ACK information in response to the PSSCH reception. The UE provides HARQ-ACK information that includes ACK or NACK, or only NACK. A UE can be provided, by sl-PSFCH-Period-r16, a number of slots in a resource pool for a period of PSFCH transmission occasion resources. If the number is zero, PSFCH transmissions from the UE in the resource pool are disabled. A UE expects that a slot t′.sub.k.sup.SL (0 ≤ k < T′.sub.max) has a PSFCH transmission occasion resource if k mod N.sub.PSSCH.sup.PSFCH = 0, where t′.sub.k.sup.SL is defined in [6, TS 38.214], and T′.sub.max is a number of slots that belong to the resource pool within 10240 msec according to [6, TS 38.214], and N.sub.PSSCH.sup.PSFCH is provided by sl-PSFCH-Period-r16. A UE may be indicated by higher layers to not transmit a PSFCH in response to a PSSCH reception [11, TS 38.321]. If a UE receives a PSSCH in a resource pool and the HARQ feedback enabled/disabled indicator field in an associated SCI format 2-A or a SCI format 2-B has value 1 [5, TS 38.212], the UE provides the HARQ-ACK information in a PSFCH transmission in the resource pool. The UE transmits the PSFCH in a first slot that includes PSFCH resources and is at least a number of slots, provided by sl-MinTimeGapPSFCH-r16, of the resource pool after a last slot of the PSSCH reception. A UE is provided by sl-PSFCH-RB-Set-r16 a set of M.sub.PRB,set.sup.PSFCH PRBs in a resource pool for PSFCH transmission in a PRB of the resource pool. For a number of N.sub.subch sub-channels for the resource pool, provided by sl-NumSubchannel, and a number of PSSCH slots associated with a PSFCH slot that is less than or equal to N.sub.PSSCH.sup.PSFCH, the UE allocates the [(i + j .Math. N.sub.PSSCH.sup.PSFCH) .Math. M.sub.subch,slot.sup.PSFCH, (i + 1 + j .Math. N.sub.PSSCH.sup.PSFCH) .Math. M.sub.subch,slot.sup.PSFCH − 1] PRBs from the M.sub.PRB,set.sup.PSFCH PRBs to slot i among the PSSCH slots associated with the PSFCH slot and sub-channel j, where M.sub.subch,slot.sup.PSFCH = M.sub.PRB,set.sup.PSFCH/(N.sub.subch .Math. N.sub.PSSCH.sup.PSFCH, 0 ≤ i < N.sub.PSSCH.sup.PSFCH, 0 ≤ j < N.sub.subch, and the allocation starts in an ascending order of i and continues in an ascending order of j. The UE expects that M.sub.PRB,set.sup.PSFCH is a multiple of N.sub.subch .Math. N.sub.PSSCH.sup.PSFCH. A UE determines a number of PSFCH resources available for multiplexing HARQ-ACK information in a PSFCH transmission as R.sub.PRB,CS.sup.PSFCH = N.sub.type.sup.PSFCH .Math. M.sub.subch,slot.sup.PSFCH .Math. N.sub.CS.sup.PSFCH where N.sub.CS.sup.PSFCH is a number of cyclic shift pairs for the resource pool and, based on an indication by higher layers, - N.sub.type.sup.PSFCH = 1 and the M.sub.subch,slot.sup.PSFCH PRBS are associated with the starting sub-channel of the corresponding PSSCH - N.sub.type.sup.PSFCH = N.sub.subch.sup.PSSCH and the N.sub.subch.sup.PSSCH .Math. M.sub.subch,slot.sup.PSFCH PRBS are associated with one or more sub-channels from the N.sub.subch.sup.PSSCH sub-channels of the corresponding PSSCH The PSFCH resources are first indexed according to an ascending order of the PRB index, from the N.sub.type.sup.PSFCH .Math. M.sub.subch,slot.sup.PSFCH PRBs, and then according to an ascending order of the cyclic shift pair index from the N.sub.CS.sup.PSFCH cyclic shift pairs. A UE determines an index of a PSFCH resource for a PSFCH transmission in response to a PSSCH reception as (P.sub.ID + M.sub.ID) mod R.sub.PRB,CS.sup.PSFCH where P.sub.ID is a physical layer source ID provided by SCI format 2-A or 2-B [5, TS 38.212] scheduling the PSSCH reception, and M.sub.ID is the identity of the UE receiving the PSSCH as indicated by higher layers if the UE detects a SCI format 2-A with Cast type indicator field value of “01”; otherwise, M.sub.ID is zero. A UE determines a m.sub.0 value, for computing a value of cyclic shift a [4, TS 38.211], from a cyclic shift pair index corresponding to a PSFCH resource index and from N.sub.CS.sup.PSFCH using Table 16.3-1. Table 16.3-1: Set of cyclic shift pairs m.sub.0 Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift N.sub.CS.sup.PSFCH Pair Index 0 Pair Index 1 Pair Index 2 Pair Index 3 Pair Index 4 Pair Index 5 1 0 — — — — — 2 0 3 — — — — 3 0 2 4 — — — 6 0 1 2 3 4 5 A UE determines a m.sub.cs value, for computing a value of cyclic shift α [4, TS 38.211], as in Table 16.3-2 if the UE detects a SCI format 2-A with Cast type indicator field value of “01” or “10”, or as in Table 16.3-3 if the UE detects a SCI format 2-B or a SCI format 2-A with Cast type indicator field value of “11”. The UE applies one cyclic shift from a cyclic shift pair to a sequence used for the PSFCH transmission [4, TS 38.211]. Table 16.3-2: Mapping of HARQ-ACK information bit values to a cyclic shift, from a cyclic shift pair, of a sequence for a PSFCH transmission when HARQ-ACK information includes ACK or NACK HARQ-ACK Value 0 (NACK) 1 (ACK) Sequence cyclic shift 0 6 Table 16.3-3: Mapping of HARQ-ACK information bit values to a cyclic shift, from a cyclic shift pair, of a sequence for a PSFCH transmission when HARQ-ACK information includes only NACK HARQ-ACK Value 0 (NACK) 1 (ACK) Sequence cyclic shift 0 N/A

[0137] Referring to FIG. 7(a), in step S8040, the first UE may transmit SL HARQ feedback to the BS via a PUCCH and/or a PUSCH based on Table 7.

TABLE-US-00007 TABLE 7 3GPP TS 38.213 16.5 UE procedure for reporting HARQ-ACK on uplink A UE can be provided PUCCH resources or PUSCH resources [12, TS 38.331] to report HARQ-ACK information that the UE generates based on HARQ-ACK information that the UE obtains from PSFCH receptions, or from absence of PSFCH receptions. The UE reports HARQ-ACK information on the primary cell of the PUCCH group, as described in Clause 9, of the cell where the UE monitors PDCCH for detection of DCI format 3_0. For SL configured grant Type 1 or Type 2 PSSCH transmissions by a UE within a time period provided by sl-PeriodCG, the UE generates one HARQ-ACK information bit in response to the PSFCH receptions to multiplex in a PUCCH transmission occasion that is after a last time resource, in a set of time resources. For PSSCH transmissions scheduled by a DCI format 3_0, a UE generates HARQ-ACK information in response to PSFCH receptions to multiplex in a PUCCH transmission occasion that is after a last time resource in a set of time resources provided by the DCI format 3_0. For each PSFCH reception occasion, from a number of PSFCH reception occasions, the UE generates HARQ-ACK information to report in a PUCCH or PUSCH transmission. The UE can be indicated by a SCI format to perform one of the following and the UE constructs a HARQ-ACK codeword with HARQ-ACK information, when applicable - if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of “10” - generate HARQ-ACK information with same value as a value of HARQ-ACK information the UE determines from a PSFCH reception in the PSFCH reception occasion and, if the UE determines that a PSFCH is not received at the PSFCH reception occasion, generate NACK - if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of “01” - generate ACK if the UE determines ACK from at least one PSFCH reception occasion, from the number of PSFCH reception occasions, in PSFCH resources corresponding to every identity MID of the UEs that the UE expects to receive the PSSCH, as described in Clause 16.3; otherwise, generate NACK - if the UE receives a PSFCH associated with a SCI format 2-B or a SCI format 2-A with Cast type indicator field value of “11” - generate ACK when the UE determines absence of PSFCH reception for each PSFCH reception occasion from the number of PSFCH reception occasions; otherwise, generate NACK After a UE transmits PSSCHs and receives PSFCHs in corresponding PSFCH resource occasions, the priority value of HARQ-ACK information is same as the priority value of the PSSCH transmissions that is associated with the PSFCH reception occasions providing the HARQ-ACK information. The UE generates a NACK when, due to prioritization, as described in Clause 16.2.4, the UE does not receive PSFCH in any PSFCH reception occasion associated with a PSSCH transmission in a resource provided by a DCI format 3_0 with CRC scrambled by a SL-RNTI or, for a configured grant, in a resource provided in a single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority value of the NACK is same as the priority value of the PSSCH transmission. The UE generates a NACK when, due to prioritization as described in Clause 16.2.4, the UE does not transmit a PSSCH in any of the resources provided by a DCI format 3_0 with CRC scrambled by SL-RNTI or, for a configured grant, in any of the resources provided in a single period and for which the UE is provided a PUCCH resource to report HARQ- ACK information. The priority value of the NACK is same as the priority value of the PSSCH that was not transmitted due to prioritization. The UE generates an ACK if the UE does not transmit a PSCCH with a SCI format 1-A scheduling a PSSCH in any of the resources provided by a configured grant in a single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority value of the ACK is same as the largest priority value among the possible priority values for the configured grant. A UE does not expect to be provided PUCCH resources or PUSCH resources to report HARQ-ACK information that start earlier than (N + 1) .Math. (2048 + 144) .Math. κ .Math. 2.sup.μ .Math. T.sub.c after the end of a last symbol of a last PSFCH reception occasion, from a number of PSFCH reception occasions that the UE generates HARQ-ACK information to report in a PUCCH or PUSCH transmission, where - κ and T.sub.c are defined in [4, TS 38.211] - μ = min (μ.sub.SL, μ.sub.UL), where μ.sub.SL is the SCS configuration of the SL BWP and μ.sub.UL is the SCS configuration of the active UL BWP on the primary cell - N is determined from μ according to Table 16.5-1 Table 16.5-1: Values of N μ N 0 14 1 18 2 28 3 32 With reference to slots for PUCCH transmissions and for a number of PSFCH reception occasions ending in slot n, the UE provides the generated HARQ-ACK information in a PUCCH transmission within slot n + k, subject to the overlapping conditions in Clause 9.2.5, where k is a number of slots indicated by a PSFCH-to-HARQ_feedback timing indicator field, if present, in a DCI format indicating a slot for PUCCH transmission to report the HARQ-ACK information, or k is provided by sl-PSFCH-ToPUCCH-CG-Type1-r16. k = 0 corresponds to a last slot for a PUCCH transmission that would overlap with the last PSFCH reception occasion assuming that the start of the sidelink frame is same as the start of the downlink frame [4, TS 38.211]. For a PSSCH transmission by a UE that is scheduled by a DCI format, or for a SL configured grant Type 2 PSSCH transmission activated by a DCI format, the DCI format indicates to the UE that a PUCCH resource is not provided when a value of the PUCCH resource indicator field is zero and a value of PSFCH-to-HARQ feedback timing indicator field, if present, is zero. For a SL configured grant Type 1 PSSCH transmission, a PUCCH resource can be provided by sl- N1PUCCH-AN-r16 and sl-PSFCH-ToPUCCH-CG-Type1-r16. If a PUCCH resource is not provided, the UE does not transmit a PUCCH with generated HARQ-ACK information from PSFCH reception occasions. For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a set of PUCCH resources for O.sub.UCI HARQ-ACK information bits, as described in Clause 9.2.1. The PUCCH resource determination is based on a PUCCH resource indicator field [5, TS 38.212] in a last DCI format 3_0, among the DCI formats 3_0 that have a value of a PSFCH-to-HARQ_feedback timing indicator field indicating a same slot for the PUCCH transmission, that the UE detects and for which the UE transmits corresponding HARQ-ACK information in the PUCCH where, for PUCCH resource determination, detected DCI formats are indexed in an ascending order across PDCCH monitoring occasion indexes. A UE does not expect to multiplex HARQ-ACK information for more than one SL configured grants in a same PUCCH. A priority value of a PUCCH transmission with one or more sidelink HARQ-ACK information bits is the smallest priority value for the one or more HARQ-ACK information bits. In the following, the CRC for DCI format 3_0 is scrambled with a SL-RNTI or a SL-CS-RNTI.

[0138] Examples of Communication Systems Applicable to the Present Disclosure

[0139] The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, without being limited to, a variety of fields requiring wireless communication/connection (e.g., 5G) between devices.

[0140] Hereinafter, a description will be given in more detail with reference to the drawings. In the following drawings/description, the same reference symbols may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless described otherwise.

[0141] FIG. 8 illustrates a communication system 1 applied to the present disclosure.

[0142] Referring to FIG. 8, a communication system 1 applied to the present disclosure includes wireless devices, BSs, and a network. Herein, the wireless devices represent devices performing communication using RAT (e.g., 5G NR or LTE) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, 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 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. 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). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. 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.

[0143] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. V2V/V2X communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0144] Wireless communication/connections 150a, 150b, or 150c may be established between the wireless devices 100a to 100f/BS 200, or BS 200/BS 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G 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 BS s/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.

[0145] Examples of Wireless Devices Applicable to the Present Disclosure

[0146] FIG. 9 illustrates wireless devices applicable to the present disclosure.

[0147] Referring to FIG. 9, a first wireless device 100 and a second wireless device 200 may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to {the wireless device 100x and the BS 200} and/or {the wireless device 100x and the wireless device 100x}.

[0148] The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 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(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

[0149] The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 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(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

[0150] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102 and 202 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. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

[0151] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. 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 102 and 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 configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

[0152] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0153] The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas 108 and 208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.

[0154] Examples of a Vehicle or an Autonomous Driving Vehicle Applicable to the Present Disclosure

[0155] FIG. 10 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.

[0156] Referring to FIG. 10, a vehicle or autonomous driving 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.

[0157] The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle 100. The control unit 120 may include an ECU. The driving unit 140a may cause the vehicle or the autonomous driving vehicle 100 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 100 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.

[0158] For example, the communication unit 110 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 120 may control the driving unit 140a such that the vehicle or the autonomous driving vehicle 100 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 110 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 110 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.

[0159] Examples of a vehicle and AR/VR applicable to the present disclosure

[0160] FIG. 11 illustrates a vehicle applied to the present disclosure. The vehicle may be implemented as a transport means, an aerial vehicle, a ship, etc.

[0161] Referring to FIG. 11, a vehicle 100 may include a communication unit 110, a control unit 120, a memory unit 130, an I/O unit 140a, and a positioning unit 140b.

[0162] The communication unit 110 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 120 may perform various operations by controlling constituent elements of the vehicle 100. The memory unit 130 may store data/parameters/programs/code/commands for supporting various functions of the vehicle 100. The I/O unit 140a may output an AR/VR object based on information within the memory unit 130. The I/O unit 140a may include an HUD. The positioning unit 140b may acquire information about the position of the vehicle 100. The position information may include information about an absolute position of the vehicle 100, information about the position of the vehicle 100 within a traveling lane, acceleration information, and information about the position of the vehicle 100 from a neighboring vehicle. The positioning unit 140b may include a GPS and various sensors.

[0163] As an example, the communication unit 110 of the vehicle 100 may receive map information and traffic information from an external server and store the received information in the memory unit 130. 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 130. The control unit 120 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 (1410 and 1420). The control unit 120 may determine whether the vehicle 100 normally drives within a traveling lane, based on the vehicle position information. If the vehicle 100 abnormally exits from the traveling lane, the control unit 120 may display a warning on the window in the vehicle through the I/O unit 140a. In addition, the control unit 120 may broadcast a warning message regarding driving abnormity to neighboring vehicles through the communication unit 110. According to situation, the control unit 120 may transmit the vehicle position information and the information about driving/vehicle abnormality to related organizations.

[0164] Examples of a Robot Applicable to the Present Disclosure

[0165] FIG. 12 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.

[0166] Referring to FIG. 12, a robot 100 may include a communication unit 110, a control unit 120, a memory unit 130, an I/O unit 140a, a sensor unit 140b, and a driving unit 140c. Herein, the blocks 110 to 130/140a to 140c correspond to the blocks 110 to 130/140 of FIG. 14, respectively.

[0167] The communication unit 110 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 120 may perform various operations by controlling constituent elements of the robot 100. The memory unit 130 may store data/parameters/programs/code/commands for supporting various functions of the robot 100. The I/O unit 140a may obtain information from the exterior of the robot 100 and output information to the exterior of the robot 100. 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 100, 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 100 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.

[0168] Example of AI Device to which the Present Disclosure is Applied.

[0169] FIG. 13 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.

[0170] Referring to FIG. 13, an AI device 100 may include a communication unit 110, a control unit 120, a memory unit 130, an I/O unit 140a/140b, a learning processor unit 140c, and a sensor unit 140d. The blocks 110 to 130/140a to 140d correspond to blocks 110 to 130/140 of FIG. 14, respectively.

[0171] The communication unit 110 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, 200, or 400 of FIG. 13) or an AI server (e.g., 400 of FIG. 13) using wired/wireless communication technology. To this end, the communication unit 110 may transmit information within the memory unit 130 to an external device and transmit a signal received from the external device to the memory unit 130.

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

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

[0174] The input unit 140a may acquire various types of data from the exterior of the AI device 100. 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 140 may obtain at least one of internal information of the AI device 100, surrounding environment information of the AI device 100, and user information, using various sensors. The sensor unit 140 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.

[0175] 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 (400 of FIG. 13). The learning processor unit 140c may process information received from an external device through the communication unit 110 and/or information stored in the memory unit 130. In addition, an output value of the learning processor unit 140c may be transmitted to the external device through the communication unit 110 and may be stored in the memory unit 130.

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