Patent Grant
11575476
This disclosure relates to a wireless communication system.
Sidelink (SL) communication is a communication scheme in which a direct link is established between User Equipments (UEs) and the UEs exchange voice and data directly with each other without intervention of an evolved Node B (eNB). SL communication is under consideration as a solution to the overhead of an eNB caused by rapidly increasing data traffic.
Vehicle-to-everything (V2X) refers to a communication technology through which a vehicle exchanges information with another vehicle, a pedestrian, an object having an infrastructure (or infra) established therein, and so on. The V2X may be divided into 4 types, such as vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). The V2X communication may be provided via a PC5 interface and/or Uu interface.
Meanwhile, as a wider range of communication devices require larger communication capacities, the need for mobile broadband communication that is more enhanced than the existing Radio Access Technology (RAT) is rising. Accordingly, discussions are made on services and user equipment (UE) that are sensitive to reliability and latency. And, a next generation radio access technology that is based on the enhanced mobile broadband communication, massive Machine Type Communication (MTC), Ultra-Reliable and Low Latency Communication (URLLC), and so on, may be referred to as a new radio access technology (RAT) or new radio (NR). Herein, the NR may also support vehicle-to-everything (V2X) communication.
Regarding V2X communication, a scheme of providing a safety service, based on a V2X message such as BSM (Basic Safety Message), CAM (Cooperative Awareness Message), and DENM (Decentralized Environmental Notification Message) is focused in the discussion on the RAT used before the NR. The V2X message may include position information, dynamic information, attribute information, or the like. For example, a UE may transmit a periodic message type CAM and/or an event triggered message type DENM to another UE.
For example, the CAM may include dynamic state information of the vehicle such as direction and speed, static data of the vehicle such as a size, and basic vehicle information such as an exterior illumination state, route details, or the like. For example, the UE may broadcast the CAM, and latency of the CAM may be less than 100 ms. For example, the UE may generate the DENM and transmit it to another UE in an unexpected situation such as a vehicle breakdown, accident, or the like. For example, all vehicles within a transmission range of the UE may receive the CAM and/or the DENM. In this case, the DENM may have a higher priority than the CAM.
Thereafter, regarding V2X communication, various V2X scenarios are proposed in NR. For example, the various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, remote driving, or the like.
For example, based on the vehicle platooning, vehicles may move together by dynamically forming a group. For example, in order to perform platoon operations based on the vehicle platooning, the vehicles belonging to the group may receive periodic data from a leading vehicle. For example, the vehicles belonging to the group may decrease or increase an interval between the vehicles by using the periodic data.
For example, based on the advanced driving, the vehicle may be semi-automated or fully automated. For example, each vehicle may adjust trajectories or maneuvers, based on data obtained from a local sensor of a proximity vehicle and/or a proximity logical entity. In addition, for example, each vehicle may share driving intention with proximity vehicles.
For example, based on the extended sensors, raw data, processed data, or live video data obtained through the local sensors may be exchanged between a vehicle, a logical entity, a UE of pedestrians, and/or a V2X application server. Therefore, for example, the vehicle may recognize a more improved environment than an environment in which a self-sensor is used for detection.
For example, based on the remote driving, for a person who cannot drive or a remote vehicle in a dangerous environment, a remote driver or a V2X application may operate or control the remote vehicle. For example, if a route is predictable such as public transportation, cloud computing based driving may be used for the operation or control of the remote vehicle. In addition, for example, an access for a cloud-based back-end service platform may be considered for the remote driving.
Meanwhile, a scheme of specifying service requirements for various V2X scenarios such as vehicle platooning, advanced driving, extended sensors, remote driving, or the like is discussed in NR-based V2X communication.
According to an embodiment, a method of operating a first apparatus 100 in a wireless communication system is proposed. The method may comprise: receiving a configured grant from a base station; obtaining a first hybrid automatic repeat request (HARQ) process identifier (ID) related to a first period of the configured grant; transmitting a first physical sidelink shared channel (PSSCH) to a second apparatus, based on a first resource included in the first period; obtaining a second HARQ process ID related to a second period of the configured grant; and transmitting a second PSSCH to the second apparatus, based on a second resource included in the second period.
The user equipment (UE) can efficiently perform SL communication.
In the present specification, “A or B” may mean “only A”, “only B” or “both A and B.” In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in the present specification, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”.
A slash (/) or comma used in the present specification may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.
In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”.
In addition, in the present specification, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”.
In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (PDCCH)”, it may mean that “PDCCH” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., PDCCH)”, it may also mean that “PDCCH” is proposed as an example of the “control information”.
A technical feature described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.
The technology described below may be used in various wireless communication 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. The CDMA may be implemented with a radio technology, such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA may be implemented with a radio technology, such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA may be implemented with a radio technology, such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), and so on. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility with a system based on the IEEE 802.16e. The UTRA is part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in a downlink and uses the SC-FDMA in an uplink. LTE-advanced (LTE-A) is an evolution of the LTE.
5G NR is a successive technology of LTE-A corresponding to a new Clean-slate type mobile communication system having the characteristics of high performance, low latency, high availability, and so on. 5G NR may use resources of all spectrum available for usage including low frequency bands of less than 1 GHz, middle frequency bands ranging from 1 GHz to 10 GHz, high frequency (millimeter waves) of 24 GHz or more, and so on.
For clarity in the description, the following description will mostly focus on LTE-A or 5G NR. However, technical features according to an embodiment of the present disclosure will not be limited only to this.
Referring to
The embodiment of
Layers of a radio interface protocol between the UE and the network can be classified into a first layer (layer 1, L1), a second layer (layer 2, L2), and a third layer (layer 3, L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system. Among them, a physical (PHY) layer belonging to the first layer provides an information transfer service by using a physical channel, and a radio resource control (RRC) layer belonging to the third layer serves to control a radio resource between the UE and the network. For this, the RRC layer exchanges an RRC message between the UE and the BS.
Referring to
Between different physical layers, i.e., a physical layer of a transmitter and a physical layer of a receiver, data are transferred through the physical channel. The physical channel is modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and utilizes time and frequency as a radio resource.
The MAC layer provides services to a radio link control (RLC) layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides data transfer services over logical channels.
The RLC layer performs concatenation, segmentation, and reassembly of Radio Link Control Service Data Unit (RLC SDU). In order to ensure diverse quality of service (QoS) required by a radio bearer (RB), the RLC layer provides three types of operation modes, i.e., a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). An AM RLC provides error correction through an automatic repeat request (ARQ).
A radio resource control (RRC) layer is defined only in the control plane. The RRC layer serves to control the logical channel, the transport channel, and the physical channel in association with configuration, reconfiguration and release of RBs. The RB is a logical path provided by the first layer (i.e., the physical layer or the PHY layer) and the second layer (i.e., a MAC layer, an RLC layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer) for data delivery between the UE and the network.
Functions of a packet data convergence protocol (PDCP) layer in the user plane include user data delivery, header compression, and ciphering. Functions of a PDCP layer in the control plane include control-plane data delivery and ciphering/integrity protection.
A service data adaptation protocol (SDAP) layer is defined only in a user plane. The SDAP layer performs mapping between a Quality of Service (QoS) flow and a data radio bearer (DRB) and QoS flow ID (QFI) marking in both DL and UL packets.
The configuration of the RB implies a process for specifying a radio protocol layer and channel properties to provide a particular service and for determining respective detailed parameters and operations. The RB can be classified into two types, i.e., a signaling RB (SRB) and a data RB (DRB). The SRB is used as a path for transmitting an RRC message in the control plane. The DRB is used as a path for transmitting user data in the user plane.
When an RRC connection is established between an RRC layer of the UE and an RRC layer of the E-UTRAN, the UE is in an RRC_CONNECTED state, and, otherwise, the UE may be in an RRC_IDLE state. In case of the NR, an RRC_INACTIVE state is additionally defined, and a UE being in the RRC_INACTIVE state may maintain its connection with a core network whereas its connection with the BS is released.
Data is transmitted from the network to the UE through a downlink transport channel. Examples of the downlink transport channel include a broadcast channel (BCH) for transmitting system information and a downlink-shared channel (SCH) for transmitting user traffic or control messages. Traffic of downlink multicast or broadcast services or the control messages can be transmitted on the downlink-SCH or an additional downlink multicast channel (MCH). Data is transmitted from the UE to the network through an uplink transport channel. Examples of the uplink transport channel include a random access channel (RACH) for transmitting an initial control message and an uplink SCH for transmitting user traffic or control messages.
Examples of logical channels belonging to a higher channel of the transport channel and mapped onto the transport channels include a broadcast channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), a multicast traffic channel (MTCH), etc.
Referring to
In case of using a normal CP, each slot may include 14 symbols. In case of using an extended CP, each slot may include 12 symbols. Herein, a symbol may include an OFDM symbol (or CP-OFDM symbol) and a Single Carrier-FDMA (SC-FDMA) symbol (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol).
Table 1 shown below represents an example of a number of symbols per slot (Nslotsymb), a number slots per frame (Nframe,uslot), and a number of slots per subframe (Nsubframe,uslot) based on an SCS configuration (u), in a case where a normal CP is used.
Table 2 shows an example of a number of symbols per slot, a number of slots per frame, and a number of slots per subframe based on the SCS, in a case where an extended CP is used.
In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, and so on) between multiple cells being integrate to one UE may be differently configured. Accordingly, a (absolute time) duration (or section) of a time resource (e.g., subframe, slot or TTI) (collectively referred to as a time unit (TU) for simplicity) being configured of the same number of symbols may be differently configured in the integrated cells.
In the NR, multiple numerologies or SCSs for supporting diverse 5G services may be supported. For example, in case an SCS is 15 kHz, a wide area of the conventional cellular bands may be supported, and, in case an SCS is 30 kHz/60 kHz a dense-urban, lower latency, wider carrier bandwidth may be supported. In case the SCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz may be used in order to overcome phase noise.
An NR frequency band may be defined as two different types of frequency ranges. The two different types of frequency ranges may be FR1 and FR2. The values of the frequency ranges may be changed (or varied), and, for example, the two different types of frequency ranges may be as shown below in Table 3. Among the frequency ranges that are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2 may mean an “above 6 GHz range” and may also be referred to as a millimeter wave (mmW).
As described above, the values of the frequency ranges in the NR system may be changed (or varied). For example, as shown below in Table 4, FR1 may include a band within a range of 410 MHz to 7125 MHz. More specifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1 mat include an unlicensed band. The unlicensed band may be used for diverse purposes, e.g., the unlicensed band for vehicle-specific communication (e.g., automated driving).
Referring to
A carrier includes a plurality of subcarriers in a frequency domain. A Resource Block (RB) may be defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A Bandwidth Part (BWP) may be defined as a plurality of consecutive (Physical) Resource Blocks ((P)RBs) in the frequency domain, and the BWP may correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include a maximum of N number BWPs (e.g., 5 BWPs). Data communication may be performed via an activated BWP. Each element may be referred to as a Resource Element (RE) within a resource grid and one complex symbol may be mapped to each element.
Hereinafter, a bandwidth part (BWP) and a carrier will be described.
The BWP may be a set of consecutive physical resource blocks (PRBs) in a given numerology. The PRB may be selected from consecutive sub-sets of common resource blocks (CRBs) for the given numerology on a given carrier
For example, the BWP may be at least any one of an active BWP, an initial BWP, and/or a default BWP. For example, the UE may not monitor downlink radio link quality in a DL BWP other than an active DL BWP on a primary cell (PCell). For example, the UE may not receive PDCCH, physical downlink shared channel (PDSCH), or channel state information-reference signal (CSI-RS) (excluding RRM) outside the active DL BWP. For example, the UE may not trigger a channel state information (CSI) report for the inactive DL BWP. For example, the UE may not transmit physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) outside an active UL BWP. For example, in a downlink case, the initial BWP may be given as a consecutive RB set for a remaining minimum system information (RMSI) control resource set (CORESET) (configured by physical broadcast channel (PBCH)). For example, in an uplink case, the initial BWP may be given by system information block (SIB) for a random access procedure. For example, the default BWP may be configured by a higher layer. For example, an initial value of the default BWP may be an initial DL BWP. For energy saving, if the UE fails to detect downlink control information (DCI) during a specific period, the UE may switch the active BWP of the UE to the default BWP.
Meanwhile, the BWP may be defined for SL. The same SL BWP may be used in transmission and reception. For example, a transmitting UE may transmit an SL channel or an SL signal on a specific BWP, and a receiving UE may receive the SL channel or the SL signal on the specific BWP. In a licensed carrier, the SL BWP may be defined separately from a Uu BWP, and the SL BWP may have configuration signaling separate from the Uu BWP. For example, the UE may receive a configuration for the SL BWP from the BS/network. For example, the UE may receive a configuration for the Uu BWP from the BS/network. The SL BWP may be (pre-)configured in a carrier with respect to an out-of-coverage NR V2X UE and an RRC_IDLE UE. For the UE in the RRC_CONNECTED mode, at least one SL BWP may be activated in the carrier.
Referring to
The BWP may be configured by a point A, an offset NstartBWP from the point A, and a bandwidth NsizeBWP. For example, the point A may be an external reference point of a PRB of a carrier in which a subcarrier 0 of all numerologies (e.g., all numerologies supported by a network on that carrier) is aligned. For example, the offset may be a PRB interval between a lowest subcarrier and the point A in a given numerology. For example, the bandwidth may be the number of PRBs in the given numerology.
Hereinafter, V2X or SL communication will be described.
A sidelink synchronization signal (SLSS) may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS), as an SL-specific sequence. 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, a UE may use the S-PSS for initial signal detection and for synchronization acquisition. For example, the UE may use the S-PSS and the S-SSS for acquisition of detailed synchronization and for detection of a synchronization signal ID.
A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information which must be first known by the UE before SL signal transmission/reception. For example, the default information may be information related to SLSS, a duplex mode (DM), a time division duplex (TDD) uplink/downlink (UL/DL) configuration, information related to a resource pool, a type of an application related to the SLSS, a subframe offset, broadcast information, or the like. For example, for evaluation of PSBCH performance, in NR V2X, a payload size of the PSBCH may be 56 bits including 24-bit cyclic redundancy check (CRC).
The S-PSS, the S-SSS, and the PSBCH may be included in a block format (e.g., SL synchronization signal (SS)/PSBCH block, hereinafter, sidelink-synchronization signal block (S-SSB)) supporting periodical 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 a carrier, and a transmission bandwidth may exist within a (pre-)configured sidelink (SL) BWP. For example, the S-SSB may have a bandwidth of 11 resource blocks (RBs). For example, the PSBCH may exist across 11 RBs. In addition, a frequency position of the S-SSB may be (pre-)configured. Accordingly, the UE does not have to perform hypothesis detection at frequency to discover the S-SSB in the carrier.
Referring to
For example, the UE 1 may select a resource unit corresponding to a specific resource in a resource pool which implies a set of series of resources. In addition, the UE 1 may transmit an SL signal by using the resource unit. For example, a resource pool in which the UE 1 is capable of transmitting a signal may be configured to the UE 2 which is a receiving UE, and the signal of the UE 1 may be detected in the resource pool.
Herein, if the UE 1 is within a connectivity range of the BS, the BS may inform the UE 1 of the resource pool. Otherwise, if the UE 1 is out of the connectivity range of the BS, another UE may inform the UE 1 of the resource pool, or the UE 1 may use a pre-configured resource pool.
In general, the resource pool may be configured in unit of a plurality of resources, and each UE may select a unit of one or a plurality of resources to use it in SL signal transmission thereof.
Hereinafter, resource allocation in SL will be described.
For example, (a) of
For example, (b) of
Referring to (a) of
Referring to (b) of
Meanwhile, in various embodiments of the present disclosure, a transmitting UE (i.e., TX UE) may be a UE which transmits data to (target) receiving UE(s) (i.e., RX UE(s)). For example, the TX UE may be a UE which performs PSCCH transmission and/or PSSCH transmission. For example, the TX UE may be a UE which transmits SL CSI-RS(s) and/or a SL CSI report request indication to (target) RX UE(s). For example, the TX UE may be a UE which transmits a (pre-defined) reference signal(s) (e.g., PSSCH demodulation reference signal (DM-RS)) and/or SL (L1) RSRP report request indicator, which is/are used for SL (L1) RSRP measurement, to (target) to RX UE(s). For example, the TX UE may be a UE which transmits a (control) channel (e.g., PSCCH, PSSCH, etc.) and/or reference signal(s) (e.g., DM-RS(s), CSI-RS(s), etc.) through the (control) channel, which is/are used for SL radio link monitoring (RLM) operation(s) and/or SL radio link failure (RLF) operation(s) of (target) RX UE(s).
Meanwhile, in various embodiments of the present disclosure, a receiving UE (i.e., RX UE) may be a UE which transmits SL HARQ feedback to transmitting UE(s) (i.e., TX UE(s)), based on whether or not data transmitted by TX UE(s) is decoded successfully and/or whether or not a PSCCH (related to PSSCH scheduling) transmitted by TX UE(s) is detected/decoded successfully. For example, the RX UE may be a UE which performs SL CSI transmission to TX UE(s) based on SL CSI-RS(s) and/or a SL CSI report request indication received from TX UE(s). For example, the RX UE may be a UE which transmits, to TX UE(s), an SL (L1) RSRP measurement value measured based on (pre-defined) reference signal(s) and/or SL (L1) RSRP report request indication received from TX UE(s). For example, the RX UE may be a UE which transmits its own data to TX UE(s). For example, the RX UE may be a UE which performs SL RLM operation(s) and/or SL RLF operation(s) based on a (pre-configured) (control) channel and/or reference signal(s) through the (control) channel received from TX UE(s).
Meanwhile, in various embodiments of the present disclosure, when a receiving UE transmits SL HARQ feedback information for a PSSCH and/or a PSCCH received from a transmitting UE, the following method may be considered or partly considered. Here, for example, the corresponding scheme or some schemes may be limitedly applied only when a receiving UE successfully decodes/detects a PSCCH for scheduling a PSSCH.
Meanwhile, in various embodiments of the present disclosure, for example, a TX UE may transmit at least one of the following information to an RX UE through SCI. Here, for example, a TX UE may transmit at least one of the following information to an RX UE through first SCI and/or second SCI.
Meanwhile, in various embodiments of the present disclosure, for example, a PSCCH may be replaced/substituted with at least one of a SCI, a first SCI (1st-stage SCI), and/or a second SCI (2nd-stage SCI), or vice versa. For example, a SCI may be replaced/substituted with at least one of a PSCCH, a first SCI, and/or a second SCI, or vice versa. For example, a PSSCH may be replaced/substituted with a second SCI and/or a PSCCH, or vice versa, since a transmitting UE may transmit second SCI to a receiving UE through PSSCH. for example, if SCI configuration fields are divided into two groups in consideration of a (relatively) high SCI payload size, an SCI including a first SCI configuration field group may be referred to as a first SCI or a 1st SCI, and an SCI including a second SCI configuration field group may be referred to as a second SCI or a 2nd SCI. For example, the 1st SCI and the 2nd SCI may be transmitted through different channels. For example, the transmitting UE may transmit the first SCI to the receiving UE through the PSCCH. For example, the second SCI may be transmitted to the receiving UE through an (independent) PSCCH, or may be transmitted in a piggyback manner together with data through the PSSCH.
On the other hand, in various embodiments of the present disclosure, for example, “configuration” or “definition” may mean (resource pool specific) (pre-)configuration (through predefined signaling (e.g., SIB, MAC, RRC, etc.)) from a base station or a network. For example, “A is configured” may mean “a base station/network transmits information related to A to a UE”. Or, for example, “A is configured” may mean “A is designated through pre-defined signaling (e.g., PC5 RRC) between UEs”.
Meanwhile, in various embodiments of the present disclosure, for example, “RLF” may be interpreted as mutually extended to at least one of out of synch (00S) and in synch (IS). Meanwhile, in various embodiments of the present disclosure, for example, a resource block (RB) may be replaced/substituted with a subcarrier, or vice versa. For example, a packet or a traffic may be replaced/substituted with a transport block (TB) or a medium access control protocol data unit (MAC PDU) according to a transmission layer, or vice versa. For example, a code block group (CBG) may be replaced/substituted with a TB, or vice versa. For example, a source ID may be replaced/substituted with a destination ID, or vice versa. For example, an L1 ID may be replaced/substituted with an L2 ID, or vice versa. For example, the L1 ID may be an L1 source ID or an L1 destination ID. For example, the L2 ID may be an L2 source ID or an L2 destination ID.
Meanwhile, in various embodiments of the present disclosure, for example, operation(s) of a TX UE to reserve/select/determine retransmission resource(s) may include operation(s) of the TX UE to reserve/select/determine potential retransmission resource(s) in which actual use is determined based on SL HARQ feedback information received from RX UE(s).
Meanwhile, in various embodiments of the present disclosure, a sub-selection window may be replaced/substituted with a selection window and/or a pre-configured number of resource sets within the selection window, or vice versa.
Meanwhile, in various embodiments of the present disclosure, SL MODE 1 may refer to a resource allocation method or a communication method in which a base station directly schedules SL transmission resource(s) for a TX UE through pre-defined signaling (e.g., DCI or RRC message). For example, SL MODE 2 may refer to a resource allocation method or a communication method in which a UE independently selects SL transmission resource(s) in a resource pool pre-configured or configured from a base station or a network. For example, a UE performing SL communication based on SL MODE 1 may be referred to as a MODE 1 UE or MODE 1 TX UE, and a UE performing SL communication based on SL MODE 2 may be referred to as a MODE 2 UE or MODE 2 TX UE.
Meanwhile, in the present disclosure, for example, a dynamic grant (DG) may be replaced/substituted with a configured grant (CG) and/or a semi-persistent scheduling (SPS) grant, or vice versa. For example, the DG may be replaced/substituted with a combination of the CG and the SPS grant, or vice versa. For example, the CG may include at least one of a configured grant (CG) type 1 and/or a configured grant (CG) type 2. For example, in CG type 1, the grant may be provided by RRC signaling and may be stored as a configured grant. For example, in CG type 2, a grant may be provided by PDCCH, it may be stored or deleted as a configured grant based on L1 signaling indicating activation or deactivation of the grant. For example, in CG type 1, a base station may allocate a periodic resource to a TX UE through an RRC message. For example, in CG type 2, a base station may allocate a periodic resource to a TX UE through an RRC message, and a base station may dynamically activate or deactivate a periodic resource through DCI.
Meanwhile, in various embodiments of the present disclosure, a channel may be replaced/substituted with a signal, or vice versa. For example, transmission/reception of a channel may include transmission/reception of a signal. For example, transmission/reception of a signal may include transmission/reception of a channel. For example, cast may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa. For example, a cast type may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa.
Meanwhile, in various embodiments of the present disclosure, a resource may be replaced/substituted with a slot or a symbol, or vice versa. For example, the resource may include a slot and/or a symbol.
Meanwhile, in various embodiments of the present disclosure, a priority may be replaced/substituted with at least one of logical channel prioritization (LCP), latency, reliability, minimum required communication range, prose per-packet priority (PPPP), sidelink radio bearer (SLRB), a QoS profile, a QoS parameter, and/or requirement, or vice versa.
Meanwhile, in various embodiments of the present disclosure, for example, for convenience of description, a (physical) channel used when a RX UE transmits at least one of the following information to a TX UE may be referred to as a PSFCH.
Meanwhile, when performing sidelink communication, a method for a transmitting UE to reserve or pre-determine transmission resource(s) for receiving UE(s) may be representatively as follows.
For example, the transmitting UE may perform a reservation of transmission resource(s) based on a chain. Specifically, for example, if the transmitting UE reserves K transmission resources, the transmitting UE may transmit location information for less than K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, for example, the SCI may include location information for less than the K transmission resources. Alternatively, for example, if the transmitting UE reserves K transmission resources related to a specific TB, the transmitting UE may transmit location information for less than K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for less than the K transmission resources. In this case, for example, it is possible to prevent performance degradation due to an excessive increase in payloads of the SCI, by signaling only the location information for less than K transmission resources to the receiving UE(s) through one SCI transmitted at any (or specific) transmission time or the time resource by the transmitting UE.
Specifically, for example, (a) of
Meanwhile, for example, the transmitting UE may perform a reservation of transmission resource(s) based on a block. Specifically, for example, if the transmitting UE reserves K transmission resources, the transmitting UE may transmit location information for K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for K transmission resources. For example, if the transmitting UE reserves K transmission resources related to a specific TB, the transmitting UE may transmit location information for K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for K transmission resources. For example, (c) of
According to an embodiment of the present disclosure, when a mode (MODE) 1 UE performs TB transmission using an SL resource within a specific CG period, and/or when it performs TB transmission using SL retransmission resources additionally allocated through mode 1 DG downlink control information (DCI), linked with SL resources within a specific CG period, whether to toggling a new data indicator (NDI) on the SCI related to TB transmission may be configured to be determined according to the (part of) following rules. For example, the TB transmission may be an initial transmission or a retransmission. And, for example, it may be determined whether to designate an NDI value and/or designate/change an SL HARQ PROCESS ID according to the (part of) following rules. For example, in the present disclosure, SL HARQ PROCESS ID may mean SL PROCESS ID.
According to an embodiment of the present disclosure, when a CG period is changed, an NDI value on TB-related SCI transmitted through a (changed) “SL resource interlocked with a CG period (REL_CGRSC)” may be toggled. For example, (option 1-A) toggling an NDI value may be toggling compared to an NDI value on REL_CGRSC-related SCI of the previous CG period. Or, for example, (option 1-B) toggling an NDI value may be toggling compared to an NDI value on the previous nearest REL_CGRSC related SCI where an actual TB transmission was performed. For example, in the present disclosure, “REL_CGRSC” may be interpreted (limitedly) as a CG resource configured within a CG period and/or an SL retransmission resource additionally allocated through mode 1 DG DCI linked with a CG resource configured within a CG period. For example, in the present disclosure, only one TB transmission is possible through REL_CGRSC, in addition, it may be assumed that different TB transmissions are performed between different REL_CGRSCs. For example, in the Option 1-A scheme (and/or Option 1-B scheme) above, a change of CG periods of the pre-configured number of times may be interpreted as a factor for toggling an NDI value on SCI. For example, when applying the rules of Option 1-A and/or Option 1-B above, if different TB transmissions are performed using REL_CGRSC with different HARQ PROCESS IDs (HPN_DCI), SL HARQ PROCESS ID (HPN_SCI) designated on REL_CGRSC-related SCI of different HPN_DCI may be mapped/specified differently (e.g., one-to-one mapping). For example, a HARQ PROCESS ID may be derived through a predefined formula. For example, the predefined formula may include Equation 1 below.
HARQ Process ID=[floor(CURRENT_slot/sl-PeriodCG)]modulo sl-NrOfHARQ-Processes+sl-HARQ-ProcID-offset [Equation 1]
For example, HPN_DCI may be used to indicate linkage between a CG resource configured within a CG period and an SL retransmission resource additionally allocated through mode 1 DG DCI. For example, the HPN_DCI may be signaled through a predefined field on the mode 1 DG DCI.
According to an embodiment of the present disclosure, NDI values on different TB-related SCIs transmitted through REL_CGRSC related to different CG periods may be determined differently according to a mapping method between “REL_CGRSC-related HPN_DCI” and “HPN_SCI on TB-related SCI transmitted using (corresponding) REL_CGRSC”. For example, whether the NDI values on the different TB-related SCIs are TOGGLED may also be determined differently according to a mapping method between the HPN_DCI and the HPN_SCI. For example, NDI values on different TB-related SCIs transmitted through REL_CGRSC having different HPN_DCI to which the same HPN_SCI value is mapped may be configured to be toggled. For example, NDI values on different TB-related SCIs transmitted through REL_CGRSC with different HPN_DCIs to which different HPN_SCI values are mapped may be configured not to be toggled, or to be untoggled. For example, a rule in which NDI values on different TB-related SCIs are determined according to the above-described mapping method between HPN_DCI and HPN_SCI may be limitedly applied only when a PUCCH resource is not configured (or configured) for a mode 1 CG resource. For example, the PUCCH resource may be for the purpose of requesting additional retransmission resources. For example, when the same HPN_SCI value is mapped to a plurality of REL_CGRSCs having different HPN_DCIs, a UE may not expect that a mode 1 CG resource related PUCCH resource is configured.
According to an embodiment of the present disclosure, depending on whether a PUCCH resource is configured for a mode 1 CG resource, the mapping method between allowed “REL_CGRSC-related HPN_DCI” and “HPN_SCI on TB-related SCI transmitted using (corresponding) REL_CGRSC” may be configured differently. Here, for example, when a PUCCH resource is configured, HPN_SCI designated on REL_CGRSC-related SCI of different HPN_DCI may be mapped/specified differently (e.g., one-to-one mapping). On the other hand, for example, if a PUCCH resource is not configured, on REL_CGRSC-related SCIs of different HPN_DCIs, HPN_SCI mapping/designation of the same value (e.g., many to one mapping) may be allowed.
According to an embodiment of the present disclosure, REL_CGRSC until REL_CGRSC of HPN_DCI#X reappears, for example, from REL_CGRSC related to CG period of HPN_DCI#X to REL_CGRSC related to CG period of HPN_DCI#(X+HPNDCI_NUM−1), all NDI values on the related SCI may be configured to have the same toggling state (and/or value). Here, for example, X may be a pre-configured value (e.g., 0). For example, from a REL_CGRSC related to a CG period of HPN_DCI#X that reappeared after a CG period of HPN_DCI#(X+HPNDCI_NUM−1), to a REL_CGRSC relative to a CG period of HPN_DCI#(X+HPNDCI_NUM−1), an NDI value on related SCI may be toggled (vs. before). Here, for example, “HPNDCI_NUM” may mean the (maximum) number of (SL) HARQ PROCESS (IDs) configured for a mode 1 CG resource. For example, the (maximum) number of the (SL) HARQ PROCESS (ID) may mean the (maximum) number of HPN_SCIs or the (maximum) number of HPN_DCIs.
Referring to
For example, HPN_DCI related to DCI-based DG resource related to retransmission of a first TB initially transmitted in the first CG period of
For example, in the second CG period and/or the fourth CG period in
For example, in the fifth CG period of
According to an embodiment of the present disclosure, an NDI value on REL_CGRSC related SCI of HPN_DCI#Y may be toggled (compared to the previous one) when REL_CGRSC of the same HPN_DCI#Y appears again. Here, for example, the NDI value may be toggled (compared to the previous one) when a REL_CGRSC of the same HPN_DCI#Y reappears a pre-configured number of times. For example, a rule related to the reappearance of REL_CGRSC of HPN_DCI#Y may be independently applied/operated for each REL_CGRSC of different HPN_DCI.
According to an embodiment of the present disclosure, when a (pre-configured) timer value related to HPN_DCI#Z expires, an NDI value on a REL_CGRSC related SCI of HPN_DCI#Z may be toggled (compared to the previous one). Here, for example, a timer value of HPN_DCI#Z may mean a time during which a UE can expect DG DCI reception for allocating additional retransmission resources related to HPN_DCI#Z from a base station. Also, for example, when a timer value related to HPN_DCI#Z expires, a new transport block (TB) (compared to the previous) transmission may be performed through an HPN_DCI#Z related REL_CGRSC. For example, when a new TB transmission is performed, a UE may perform a new TB transmission after flushing a HPN_DCI#Z related buffer/MAC PDU.
According to an embodiment of the present disclosure, when TB transmission is performed through REL_CGRSC related to a specific CG period, whether to toggle an NDI on relevant SCI, designation of an NDI value, designation of an HPN_SCI value, and/or designation of an L1 ID (e.g., source/destination ID) may be made to be determined by a UE implementation.
According to an embodiment of the present disclosure, when a mode 1 UE performs TB transmission through REL_CGRSC related to a specific CG period, whether to toggle an NDI on relevant SCI, designation of an NDI value, and/or designation of an HPN_SCI value may be determined according to (a part of) the rules below.
For example, when a TX UE performs different TB transmissions with respect to the same target RX UE (and/or an RX UE related to the same session, and/or an RX UE related to the same cast type), using different CG period-related REL_CGRSC (and/or when a TX UE uses the same L1 (or L2) source ID and L1 (or L2) destination ID to perform different TB transmissions through different CG period-related REL_CGRSC), on REL_CGRSC-related SCIs of different CG periods, different HPN_SCI values (and/or the same (or different) NDI values) may be designated.
For example, when a TX UE performs different TB transmissions for different target RX UEs (and/or an RX UE related to the same session, and/or an RX UE related to the same cast type) by using different CG period-related REL_CGRSC (and/or when a TX UE uses the same L1 (or L2) source ID and L1 (or L2) destination ID to perform different TB transmissions through different CG period-related REL_CGRSC), in REL_CGRSC-related SCI of different CG periods, an HPN_SCI value and an NDI value may be identically (or differently) designated (or an HPN_SCI value may be designated as the same (or different), and an NDI value may be designated as different (or the same)).
For example, when a TX UE performs (TB) retransmission for the same target RX UE (and/or an RX UE related to the same session, and/or an RX UE related to the same cast type) by using REL_CGRSC related to a specific CG period (and/or when a TX UE performs retransmission (e.g., retransmission of TB) using the same L1 (or L2) source ID and L1 (or L2) destination ID), an HPN_SCI value and an NDI value may be identically designated on SCI.
According to an embodiment of the present disclosure, during mode 1 CG operation, when TB transmission is performed through retransmission resources (ADD_RRSC) additionally allocated through DG DCI, an NDI value on related SCI may be designated according to the rule below. For example, during mode 1 CG operation, when TB transmission is performed through a retransmission resource (ADD_RRSC) additionally allocated through DG DCI, whether to toggle NDI may also be determined according to the rule below.
For example, an NDI value on REL_CGRSC (LINK_CGRSC) related SCI (e.g., of a specific CG period) linked with ADD_RRSC may be configured to be used/maintained in the same way in an NDI on the ADD_RRSC related SCI. Here, for example, LINK_CGRSC may be derived through information such as CG index and/or HPN_DCI on the DG DCI scheduling ADD_RRSC, etc.
According to an embodiment of the present disclosure, a mode 1 UE may be configured to report the (part of) following information to a (serving) base station through predefined signaling. For example, the predefined signaling may include an RRC message and/or a medium access control (MAC) control element (CE).
Table 5 shows a procedure for flushing a HARQ buffer of a sidelink process.
Referring to Table 5, with respect to a sidelink grant occurring within a PSSCH period, when a configured sidelink grant is activated, and when a sidelink grant occurring within a PSSCH period corresponds to the first PSSCH transmission opportunity in a sidelink CG period of the configured sidelink grant, a MAC layer of a UE in each PSSCH duration: i) may configure a HARQ process ID as a HARQ process ID related to the PSSCH period, and if possible, may also configure HARQ process IDs related to all subsequent PSSCH sections occurring within the sidelink CG period for the configured sidelink grant as HARQ process IDs related to the PSSCH section, ii) may determine that the PSSCH period is used for initial transmission, iii) may flush a HARQ buffer of a sidelink process related to the HARQ process ID. For example, in the configured sidelink grant, a HARQ process ID related to the first slot of SL transmission may be determined based on the above equation.
Table 6 shows a procedure for toggling NDI.
Referring to
Referring to
For example, the first HARQ process ID may be mapped one-to-one with a first sidelink (SL) process ID related to the first PSSCH.
For example, the first HARQ process ID may be mapped one-to-one with the first SL process ID, based on that a resource related to a physical uplink control channel (PUCCH) related to the first PSSCH is configured.
For example, the first SL process ID may be included in first sidelink control information (SCI) related to the first PSSCH.
For example, SL identification information of the first apparatus related to the first PSSCH may be the same as SL identification information of the first apparatus related to the second PSSCH.
For example, a first SL process ID related to the first PSSCH may be the same as a second SL process ID related to the second PSSCH.
For example, additionally, the first apparatus may receive a dynamic grant including a third resource related to the first HARQ process ID from the base station; and retransmit the first PSSCH to the second apparatus, based on the third resource.
For example, an NDI related to the retransmitted first PSSCH may be the same as the NDI related to the first PSSCH.
For example, a third SL process ID related to the retransmitted first PSSCH may be the same as a first SL process ID related to the first PSSCH.
For example, additionally, the first apparatus may flush a buffer related to the second HARQ process ID, based on that the second HARQ process ID is the same as the first HARQ process ID.
For example, the buffer related to the second HARQ process ID may be flushed based on expiration of a timer related to the second HARQ process ID.
For example, additionally, the first apparatus may report a mapping relationship related to the first HARQ process ID and a first SL process ID related to the first PSSCH.
For example, the mapping relationship may be reported through a radio resource control (RRC) message or a medium access control (MAC) control element (CE).
The above-described embodiment may be applied to various devices to be described below. For example, a processor 102 of a first apparatus 100 may control a transceiver 106 to receive a configured grant from a base station. And, the processor 102 of the first apparatus 100 may obtain a first hybrid automatic repeat request (HARQ) process identifier (ID) related to a first period of the configured grant. And, the processor 102 of the first apparatus 100 may control the transceiver 106 to transmit a first physical sidelink shared channel (PSSCH) to a second apparatus, based on a first resource included in the first period. And, the processor 102 of the first apparatus 100 may obtain a second HARQ process ID related to a second period of the configured grant. And, the processor 102 of the first apparatus 100 may control the transceiver 106 to transmit a second PSSCH to the second apparatus, based on a second resource included in the second period
According to an embodiment of the present disclosure, a first apparatus for performing wireless communication may be proposed. For example, the first apparatus may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: receive a configured grant from a base station; obtain a first hybrid automatic repeat request (HARQ) process identifier (ID) related to a first period of the configured grant; transmit a first physical sidelink shared channel (PSSCH) to a second apparatus, based on a first resource included in the first period; obtain a second HARQ process ID related to a second period of the configured grant, wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and transmit a second PSSCH to the second apparatus, based on a second resource included in the second period, wherein a new data indicator (NDI) related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID.
According to an embodiment of the present disclosure, an apparatus configured to control a first user equipment (UE) may be proposed. For example, the apparatus may comprise: one or more processors; and one or more memories operably connectable to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: receive a configured grant from a base station; obtain a first hybrid automatic repeat request (HARQ) process identifier (ID) related to a first period of the configured grant; transmit a first physical sidelink shared channel (PSSCH) to a second UE, based on a first resource included in the first period; obtain a second HARQ process ID related to a second period of the configured grant, wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and transmit a second PSSCH to the second UE, based on a second resource included in the second period, wherein a new data indicator (NDI) related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID.
According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be proposed. For example, the instructions, when executed, may cause a first apparatus to: receive a configured grant from a base station; obtain a first hybrid automatic repeat request (HARQ) process identifier (ID) related to a first period of the configured grant; transmit a first physical sidelink shared channel (PSSCH) to a second apparatus, based on a first resource included in the first period; obtain a second HARQ process ID related to a second period of the configured grant, wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and transmit a second PSSCH to the second apparatus, based on a second resource included in the second period, wherein a new data indicator (NDI) related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID.
Referring to
For example, the first HARQ process ID may be mapped one-to-one with a first sidelink (SL) process ID related to the first PSSCH.
The above-described embodiment may be applied to various devices to be described below. For example, a processor 202 of a second apparatus 200 may control a transceiver 206 to receive a first physical sidelink shared channel (PSSCH) from a first apparatus, based on a first resource included in a first period of a configured grant. And, the processor 202 of the second apparatus 200 may control the transceiver to receive a second PSSCH from the first apparatus, based on a second resource included in a second period of the configured grant.
According to an embodiment of the present disclosure, a second apparatus for performing wireless communication may be proposed. For example, the second apparatus may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: receive a first physical sidelink shared channel (PSSCH) from a first apparatus, based on a first resource included in a first period of a configured grant; and receive a second PSSCH from the first apparatus, based on a second resource included in a second period of the configured grant, wherein a new data indicator (NDI) related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on a second hybrid automatic repeat request (HARQ) process identifier (ID) which is the same as a first HARQ process ID, wherein the first HARQ process ID is related to the first period, and wherein the second HARQ process ID is related to the second period.
For example, the first HARQ process ID may be mapped one-to-one with a first sidelink (SL) process ID related to the first PSSCH.
Hereinafter, device(s) to which various embodiments of the present disclosure can be applied will be described.
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.
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.
Referring to
Here, wireless communication technology implemented in wireless devices 100a to 100f of the present disclosure may include Narrowband Internet of Things for low-power communication in addition to LTE, NR, and 6G. In this case, for example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1, and/or LTE Cat NB2, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of the LPWAN and may be called by various names including enhanced Machine Type Communication (eMTC), and the like. For example, the LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-Bandwidth Limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may include at least one of Bluetooth, Low Power Wide Area Network (LPWAN), and ZigBee considering the low-power communication, and is not limited to the name described above. As an example, the ZigBee technology may generate personal area networks (PAN) related to small/low-power digital communication based on various standards including IEEE 802.15.4, and the like, and may be called by various names.
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. Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (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.
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 uplink/downlink 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.
Referring to
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.
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.
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.
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.
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.
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.
Referring to
Codewords may be converted into radio signals via the signal processing circuit 1000 of
Specifically, the codewords may be converted into scrambled bit sequences by the scramblers 1010. Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators 1020. A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper 1030. Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder 1040. Outputs z of the precoder 1040 may be obtained by multiplying outputs y of the layer mapper 1030 by an N*M precoding matrix W. Herein, N is the number of antenna ports and M is the number of transport layers. The precoder 1040 may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.
The resource mappers 1050 may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators 1060 may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators 1060 may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), and frequency up-converters.
Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures 1010 to 1060 of
Referring to
The additional components 140 may be variously configured according to types of wireless devices. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100a of
In
Hereinafter, an example of implementing
Referring to
The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit 120 may perform various operations by controlling constituent elements of the hand-held device 100. The control unit 120 may include an Application Processor (AP). The memory unit 130 may store data/parameters/programs/code/commands needed to drive the hand-held device 100. The memory unit 130 may store input/output data/information. The power supply unit 140a may supply power to the hand-held device 100 and include a wired/wireless charging circuit, a battery, etc. The interface unit 140b may support connection of the hand-held device 100 to other external devices. The interface unit 140b may include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit 140c may input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.
As an example, in the case of data communication, the I/O unit 140c may acquire information/signals (e.g., touch, text, voice, images, or video) input by a user and the acquired information/signals may be stored in the memory unit 130. The communication unit 110 may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit 110 may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit 130 and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit 140c.
Referring to
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 vehicle 100. The control unit 120 may include an Electronic Control Unit (ECU). The driving unit 140a may cause the vehicle or the autonomous 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 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.
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 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 vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles.
Claims in the present description can be combined in a various way. For instance, technical features in method claims of the present description can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method.
This application is a Continuation Application of International Application No. PCT/KR2021/004575, filed on Apr. 12, 2021, which claims the benefit of and priority to U.S. Provisional Application No. 63/008,505, filed on Apr. 10, 2020, the contents of which are all hereby incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20100077272 | Peisa | Mar 2010 | A1 |
| 20180123765 | Cao | May 2018 | A1 |
| 20180176945 | Cao | Jun 2018 | A1 |
| 20190053251 | Loehr | Feb 2019 | A1 |
| 20210051587 | Wu | Feb 2021 | A1 |
| 20210105096 | Chin | Apr 2021 | A1 |
| 20210144750 | Cao | May 2021 | A1 |
| 20210227464 | Kung | Jul 2021 | A1 |
| 20210235421 | Jul 2021 | A1 | |
| 20210289473 | Chae | Sep 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2020069088 | Apr 2020 | WO |
| Entry |
|---|
| Ericsson, “Feature lead summary #3 on resource allocation for NR sidelink Mode 1”, R1-2001285, 3GPP TSG RAN WG1 Meeting #100, e-Meeting, Feb. 24-Mar. 6, 2020, see sections 1-3. |
| Ericsson, “Feature lead summary #2 on resource allocation for NR sidelink Mode 1”, R1-1913417, 3GPP TSG RAN WG1 Meeting #99, Chongqing, China, Nov. 18-22, 2019, see sections 1-10. |
| Ericsson, “Feature lead summary #4 on resource allocation for NR sidelink Mode 1”, R1-2001367, 3GPP TSG RAN WG1 Meeting #100, e-Meeting, Feb. 24-Mar. 6, 2020, see sections 1-3. |
| Section 5.22.1.1 of 3GPP TS 38.321 V16.6.0. |
| Section 5.22.1.3.1 of 3GPP TS 38.321 V16.6.0. |
| Number | Date | Country | |
|---|---|---|---|
| 20220182192 A1 | Jun 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63008505 | Apr 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/KR2021/004575 | Apr 2021 | US |
| Child | 17680638 | US |
