Patent Application
20240357702
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.
For example, MAC reset may include at least one Uu interface MAC reset or Sidelink interface MAC reset (For example, MAC reset related to PC5-RRC connection with another UE). For example, if UE is requested sidelink interface MAC reset and if UE is running SL DRX timer, UE may stop the sidelink DRX timer. For example, the SL DRX timer may include timer for active time. For example, if UE is requested sidelink interface MAC reset and if UE is running SL DRX timer, UE may stop PSCCH/PSSCH monitoring. However, if sidelink interface MAC reset related to RRC connection with another UE is requested, operation of sidelink resource allocation mode 1 that UE is performing (For example, or triggered), and/or operation of Uu DRX timer that UE is running may not be clearly defined.
In embodiment, a method for performing wireless communication by a first device is provided. The first device may establish PC5-RRC connection with a second device. For example, the first device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the first device may start the Uu DRX timer. For example, the first device may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, the first device performing wireless communication may be provided. The first device comprising at least one memory storing instructions; at least one transceiver; and at least one processor connected to the at least one memory and the at least one transceiver, wherein the at least one processor is adapted to execute instructions to perform operations comprising: may establish PC5-RRC connection with a second device. For example, based on the instructions executed by the at least one processor, the first device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, based on the instructions executed by the at least one processor, the first device may start the Uu DRX timer. For example, based on the instructions executed by the at least one processor, the first device may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, the apparatus configured for control the first device may be provided. The apparatus comprising at least one processor; and at least one memory connected to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the first device to perform operations comprising: may establish PC5-RRC connection with a second device. For example, based on the instructions executed by the at least one processor, the first device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, based on the instructions executed by the at least one processor, the first device may start the Uu DRX timer. For example, based on the instructions executed by the at least one processor, the first device may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, a non-transitory computer-readable storage medium storing instructions may be provided. The instructions, based on being executed by at least one processor, cause the at least one processor to perform operations comprising: the first device to establish PC5-RRC connection with a second device. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the first device to obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the first device to start the Uu DRX timer. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the first device to stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, a method for performing wireless communication by a second device may be provided. The second device may establish PC5-RRC connection with a first device. For example, the second device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, the second device performing wireless communication may be provided. The second device comprising at least one memory storing instructions; at least one transceiver; and at least one processor connected to the at least one memory and the at least one transceiver, wherein the at least one processor is adapted to execute instructions to perform operations comprising: may establish PC5-RRC connection with a first device. For example, based on the instructions executed by the at least one processor, the second device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, the apparatus configured for control the second device may be provided. The apparatus comprising at least one processor; and at least one memory connected to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the second device to perform operations comprising: may establish PC5-RRC connection with a first device. For example, based on the instructions executed by the at least one processor, the second device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
In an embodiment, a non-transitory computer-readable storage medium storing instructions may be provided. The instructions, based on being executed by at least one processor, cause the at least one processor to perform operations comprising: the second device to establish PC5-RRC connection with a first device. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the second device to obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
A user equipment (UE) may efficiently perform sidelink (SL) communication.
In the present disclosure, “A or B” may mean “only A”, “only B” or “both A and B.” In other words, in the present disclosure, “A or B” may be interpreted as “A and/or B”. For example, in the present disclosure, “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 disclosure 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 disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present disclosure, 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 disclosure, “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 disclosure 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 disclosure 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”.
In the following description, ‘when, if, or in case of’ may be replaced with ‘based on’.
A technical feature described individually in one figure in the present disclosure may be individually implemented, or may be simultaneously implemented.
In the present disclosure, a higher layer parameter may be a parameter which is configured, pre-configured or pre-defined for a UE. For example, a base station or a network may transmit the higher layer parameter to the UE. For example, the higher layer parameter may be transmitted through radio resource control (RRC) signaling or medium access control (MAC) signaling.
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 a SL channel or a 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 a 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.
For example, (a) of
For example, (b) of
Referring to (a) of
For example, the first UE may receive information related to dynamic grant (DG) resource(s) and/or information related to configured grant (CG) resource(s) from the base station. For example, the CG resource(s) may include CG type 1 resource(s) or CG type 2 resource(s). In the present disclosure, the DG resource(s) may be resource(s) configured/allocated by the base station to the first UE through a downlink control information (DCI). In the present disclosure, the CG resource(s) may be (periodic) resource(s) configured/allocated by the base station to the first UE through a DCI and/or an RRC message. For example, in the case of the CG type 1 resource(s), the base station may transmit an RRC message including information related to CG resource(s) to the first UE. For example, in the case of the CG type 2 resource(s), the base station may transmit an RRC message including information related to CG resource(s) to the first UE, and the base station may transmit a DCI related to activation or release of the CG resource(s) to the first UE.
In step S610, the first UE may transmit a PSCCH (e.g., sidelink control information (SCI) or 1st-stage SCI) to a second UE based on the resource scheduling. In step S620, the first UE may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S630, 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 S640, the first UE may transmit/report HARQ feedback information to the base station through the PUCCH or the PUSCH. For example, the HARQ feedback information reported to the base station may be 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 base station may be information generated by the first UE based on a pre-configured rule. For example, the DCI may be a DCI for SL scheduling. For example, a format of the DCI may be a DCI format 3_0 or a DCI format 3_1.
Hereinafter, an example of DCI format 3_0 will be described.
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:
Referring to (b) of
Referring to (a) or (b) of
Hereinafter, an example of SCI format 1-A will be described.
SCI format 1-A is used for the scheduling of PSSCH and 2nd-stage-SCI on PSSCH.
The following information is transmitted by means of the SCI format 1-A:
Hereinafter, an example of SCI format 2-A will be described.
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:
Hereinafter, an example of SCI format 2-B will be described.
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:
Referring to (a) or (b) of
Referring to (a) of
For example, the SL HARQ feedback may be enabled for unicast. In this case, in a non-code block group (non-CBG) operation, if the receiving UE decodes a PSCCH of which a target is the receiving UE and if the receiving UE successfully decodes a transport block related to the PSCCH, the receiving UE may generate HARQ-ACK. In addition, the receiving UE may transmit the HARQ-ACK to the transmitting UE. Otherwise, if the receiving UE cannot successfully decode the transport block after decoding the PSCCH of which the target is the receiving UE, the receiving UE may generate the HARQ-NACK. In addition, the receiving UE may transmit HARQ-NACK to the transmitting UE.
For example, the SL HARQ feedback may be enabled for groupcast. For example, in the non-CBG operation, two HARQ feedback options may be supported for groupcast.
For example, if the groupcast option 1 is used in the SL HARQ feedback, all UEs performing groupcast communication may share a PSFCH resource. For example, UEs belonging to the same group may transmit HARQ feedback by using the same PSFCH resource.
For example, if the groupcast option 2 is used in the SL HARQ feedback, each UE performing groupcast communication may use a different PSFCH resource for HARQ feedback transmission. For example, UEs belonging to the same group may transmit HARQ feedback by using different PSFCH resources.
In the present disclosure, HARQ-ACK may be referred to as ACK, ACK information, or positive-ACK information, and HARQ-NACK may be referred to as NACK, NACK information, or negative-ACK information.
Hereinafter, an RRC connection establishment between UEs will be described.
For V2X or SL communication, a transmitting UE may need to establish a (PC5) RRC connection with a receiving UE. For example, the UE may obtain V2X-specific SIB. For a UE which is configured to transmit V2X or SL communication by a higher layer and which has data to be transmitted, if a frequency at which at least the UE is configured to transmit SL communication is included in the V2X-specific SIB, the UE may establish an RRC connection with another UE without including a transmission resource pool for the frequency. For example, if an RRC connection is established between the transmitting UE and the receiving UE, the transmitting UE may perform unicast communication with respect to the receiving UE through the established RRC connection.
When the RRC connection is established between the UEs, the transmitting UE may transmit an RRC message to the receiving UE.
Referring to
The receiving UE may perform antenna/resource de-mapping, demodulation, and decoding for received information. The information may be transferred to the RRC layer via the MAC layer, the RLC layer, and the PDCP layer. Accordingly, the receiving UE may receive the RRC message generated by the transmitting UE.
V2X or SL communication may be supported for a UE of an RRC_CONNECTED mode, a UE of an RRC_IDLE mode, and a UE of an (NR) RRC_INACTIVE mode. That is, the UE of the RRC_CONNECTED mode, the UE of the RRC_IDLE mode, and the UE of the (NR) RRC_INACTIVE mode may perform V2X or SL communication. The UE of the RRC_INACTIVE mode or the UE of the RRC_IDLE mode may perform V2X or SL communication by using a cell-specific configuration included in V2X-specific SIB.
RRC may be used to exchange at least UE capability and AS layer configuration. For example, a UE 1 may transmit UE capability and AS layer configuration of the UE 1 to a UE 2, and the UE 1 may receive UE capability and AS layer configuration of the UE 2 from the UE 2. In case of UE capability transfer, an information flow may be triggered during or after PC5-S signaling for a direct link setup.
In case of the AS layer configuration, an information flow may be triggered during or after PC5-S signaling for a direct link setup.
In case of the groupcast, one-to-many PC5-RRC connection establishment may not be required between group members.
Hereinafter, SL radio link monitoring (RLM) will be described.
In case of AS-level link management of unicast, SL radio link monitoring (RLM) and/or radio link failure (RLF) declaration may be supported. In case of RLC acknowledged mode (AM) in SL unicast, the RLF declaration may be triggered by an indication from RLC indicating that the maximum number of retransmissions has been reached. An AS-level link status (e.g., failure) may need to be informed to a higher layer. Unlike the RLM procedure for unicast, a groupcast-related RLM design may not be considered. The RLM and/or RLF declarations may not be necessary between group members for groupcast.
For example, a transmitting UE may transmit a reference signal to a receiving UE, and the receiving UE may perform SL RLM by using the reference signal. For example, the receiving UE may declare SL RLF by using the reference signal. For example, the reference signal may be referred to as an SL reference signal.
An SL DRX configuration referred to in this disclosure may include at least one or more of the following parameters.
For example, an SL DRX configuration may include one or more of the information listed below.
The following SL DRX timer mentioned in this disclosure may be used for the following purposes.
For example, a UE may extend an SL DRX on-duration timer by an SL DRX inactivity timer period. Also, when a UE receives a new packet (e.g., new PSSCH transmission) from a counterpart UE, the UE may start an SL DRX inactivity timer to extend the SL DRX on-duration timer.
For example, an SL DRX inactivity timer may be used to extend an SL DRX duration timer period, which is a period in which an RX UE performing an SL DRX operation should basically operate as an active time to receive a PSCCH/PSSCH of the other TX UE. That is, an SL DRX on-duration timer may be extended by an SL DRX inactivity timer period. In addition, when an RX UE receives a new packet (e.g., new PSSCH transmission) from a counterpart TX UE, the RX UE may start an SL DRX inactivity timer to extend the SL DRX on-duration timer.
For example, when a UE starts an SL DRX HARQ RTT timer, the UE may determine that a counterpart UE will not transmit a sidelink retransmission packet to it until the SL DRX HARQ RTT timer expires, and may operate in a sleep mode while the corresponding timer is running. For example, when a UE starts an SL DRX HARQ RTT timer, the UE may not monitor sidelink retransmission packets from a counterpart UE until the SL DRX HARQ RTT timer expires. For example, when an RX UE that has received a PSCCH/PSSCH transmitted by a TX UE transmits SL HARQ NACK feedback, the RX UE may start an SL DRX HARQ RTT timer. In this case, an RX UE may determine that a counterpart TX UE will not transmit a sidelink retransmission packet to it until an SL DRX HARQ RTT timer expires, and the RX UE may operate in a sleep mode while the corresponding timer is running.
For example, during the corresponding timer period, a UE may receive or monitor a retransmission sidelink packet (or PSSCH assignment) transmitted by a counterpart UE. For example, an RX UE may receive or monitor a retransmission sidelink packet (or PSSCH assignment) transmitted by a counterpart TX UE while an SL DRX retransmission timer is running.
The following Uu DRX timer mentioned in this disclosure may be used for the following purposes.
For example, the Uu DRX HARQ RTT TimerSL can be used in a period in which the UE performing the Uu DRX operation does not have to monitor DCI (PDCCH) for SL Mode 1 operation transmitted by the base station. That is, while the Uu DRX HARQ RTT TimerSL is operating, the UE may not need to monitor the PDCCH for SL Mode 1 operation. In other words, Uu DRX HARQ RTT TimerSL may mean a minimum duration before an SL retransmission grant is expected.
For example, it can be used in a period in which a UE performing a Uu DRX operation monitors DCI (PDCCH) for SL Mode 1 operation transmitted by a base station. That is, while Uu DRX Retransmission TimerSL is in operation, the UE can monitor the PDCCH transmitted by the base station for SL Mode 1 operation. In other words, Uu DRX Retransmission TimerSL may mean a maximum duration until an SL retransmission grant is received.
In an embodiment, the name of the timer (Sidelink DRX Onduration Timer, Sidelink DRX Inactivity Timer, Sidelink DRX HARQ RTT Timer, Sidelink DRX Retransmission Timer, Uu DRX HARQ RTT TimerSL, Uu DRX Retransmission TimerSL, etc) is illustrative, timer performing identical/similar features based on the content described of each timer is considered identical/similar timer regardless of the name.
Meanwhile, according to an embodiment of the present disclosure, for example, upon request for MAC reconfiguration and MAC reset from upper layer, procedure performing MAC reconfiguration and MAC reset by MAC entity was supported.
In embodiment(s) of the present disclosure, for example, in NR V2X communication, MAC configuration for that Sidelink DRX operation may be reconfigured or reset by MAC entity.
Referring to
In step S1230, for example, the TX UE may receive, from the BS, information related to at least one SL resource. For example, the at least one SL resource (For example, SL grant) may include at least one of configured grant (CG) resource allocated to the TX UE via CG configuration information or dynamic grant (DG) resource allocated to the TX UE via downlink control information (DCI) related to DG. For example, information related to CG resource may be received, from the BS, via the RRC message. In step S1240 and step S1242, for example, the TX XE may transmit, to the RX UE, PSCCH (For example, first SCI transmitted via PSCCH)/PSSCH (For example, second SCI, MAC PDU transmitted via PSSCH), based on the CG resource or the DG resource. In step S1244, (For example, if PSFCH resource is configured) RX UE may transmit, to the TX UE, SL HARQ information (For example, SL HARQ NACK information, SL HARQ ACK information) for received PSCCH/PSSCH.
In step S1250, for example, the TX UE may start DRX HARQ RTT timer. For example, if the TX UE (For example, if UL resource is configured) report, to the BS, SL HARQ NACK, TX UE may start DRX HARQ RTT timer.
For example, MAC reset may include at least one Uu interface MAC reset or Sidelink interface MAC reset (For example, MAC reset related to PC5-RRC connection with another UE). In step S1270, for example, TX UE and/or RX UE may be requested to MAC reset related to PC5-RRC connection, TX UE and/or RX UE may detect request of the MAC reset related to PC5-RRC connection. For example, MAC reset may perform operation related to the PC5-RRC connection (For example, at least one of flushing the soft buffers for all Sidelink processes for all TB(s) associated to the PC5-RRC connection; considering all Sidelink processes for all TB(s) associated to the PC5-RRC connection as unoccupied: canceling triggered Scheduling Request procedure only associated to the PC5-RRC connection: canceling triggered Sidelink Buffer Status Reporting procedure only associated to the PC5-RRC connection: canceling triggered Sidelink CSI Reporting procedure associated to the PC5-RRC connection: stopping all timers associated to the PC5-RRC connection: resetting/initializing parameter associated to the PC5-RRC connection (For example, numConsecutiveDTX, SBj for each logical channel)).
For example, if UE is requested sidelink interface MAC reset and if UE is running SL DRX timer, UE may stop the sidelink DRX timer. For example, if UE is requested sidelink interface MAC reset and if UE is running SL DRX timer, UE may stop PSCCH/PSSCH monitoring.
However, if sidelink interface MAC reset related to RRC connection with another UE is requested, operation of sidelink resource allocation mode 1 that UE is performing (For example, or triggered), and/or operation of Uu DRX timer that UE is running may not be clearly defined. For example, if TX UE and/or RX UE is requested to MAC reset related to PC5-RRC connection, at least one timer not related to PC5-RRC may not be stopped. For example, Uu DRX timer of TX UE may be started/running (For example, may not be stopped) For example, in step S1260, before MAC reset is requested related to PC5-RRC, DRX HARQ RTT timer of TX UE may be running. For example, in step S1260, before MAC reset related to PC5-RRC is requested to the TX UE and after DRX HARQ RTT timer of TX UE is expired, DRX retransmission timer of TX UE is started/running. For example, in step S1270, TX UE and/or RX UE may be requested to MAC reset related to PC5-RRC (For example, may detect request of MAC reset). For example, in step S1270, if TX UE and/or RX UE may be requested to MAC reset related to PC5-RRC, DRX HARQ RTT timer of TX UE and/or DRX retransmission timer of TX UE may be started/running (For example, may not be stopped). For example, in step S1280, TX UE may be allocated, from BS, DG-based retransmission resource (For example, SL retransmission grant).
As a result, though the TX UE is requested to sidelink interface MAC reset, so TX UE may not have to monitor mode 1 DCI (PDCCH) of BS for allocation of SL retransmission grant, overhead may occurred because the TX UE performs DCI (PDCCH) monitoring.
For example, BS may unnecessarily allocate, to TX UE, DG-based retransmission resource. Furthermore, for example, TX UE's monitoring operation for sidelink (retransmission) grant may be unnecessarily performed. For example, Uu DRX operation may be unnecessarily performed despite triggered sidelink MAC reset. For example, as Uu DRX operation is unnecessarily performed, power of the UE may be wasted. For example, as Uu DRX operation is unnecessarily performed, sidelink communication between TX UE and RX UE may be later.
According to an embodiment of the present disclosure, operation of the MAC reset for MAC configuration may be performed. For example, if Sidelink Specific MAC Reset (SL Specific MAC Reset is occurred by SL RLF/PC5 RRC reconfiguration failure/PC5 DRX configuration failure/Security Check Failure/Integrity Check Failure/higher layer request/etc) is occurred, UE may perform MAC Reset operation related to Sidelink operation. For example, while running of the MAC Reset operation related to Sidelink operation or when starting MAC Reset related to Sidelink operation, UE may stop all timer that are running associated to Sidelink DRX (For example, SL drx-InactivityTimer, SL drx-RetransmissionTimer, SL drx-HARQ-RTT-Timer, and/or timer used for extending Sidelink DRX Onduration interval and/or timer used for that UE operates as Awake state) or may consider/regard/determine all timer operating associated to Sidelink DRX as expired. For example, all timer associated to Sidelink DRX operation operating related to Sidelink data transmission/reception that is running in PC5 Unicast link (or PC5 RRC Connection) occurred Sidelink Specific MAC Reset may be stopped or may be processed to be stopped.
According to an embodiment of the present disclosure, if configuration related to Sidelink DRX operation (For example, Sidelink DRX operation timer) has different configuration value per PC5 Unicast link or per PC5 RRC Connection, Sidelink DRX configuration parameter configured for Direction of PC5 Unicast Link (For example, pair of L2 source ID and L2 Destination ID)/PC5 RRC Connection that is occurred Sidelink specific MAC Reset may be reset (For example, stop of Sidelink DRX Timer and/or consideration of expiration of the Sidelink DRX Timer).
According to an embodiment of the present disclosure, if configuration related to Sidelink DRX operation (For example, Sidelink DRX operation timer) has different configuration value per PC5 Unicast link or per PC5 RRC Connection, Sidelink DRX configuration parameter configured for Direction of PC5 Unicast Link (For example, pair of L2 source ID and L2 Destination ID)/PC5 RRC Connection that is occurred Sidelink specific MAC Reset may be reset (For example, stop of Sidelink DRX Timer and/or consideration of expiration of the Sidelink DRX Timer).
According to an embodiment of the present disclosure, if Sidelink specific MAC Reset is occurred, UE regard timer related to uu DRX (For example, drx-Retransmission TimerSL), timer related to Sidelink DRX (For example, SL drx-InactivityTimer, SL drx-RetransmissionTimer, SL drx-HARQ-RTT-Timer, and timer used for extending Sidelink DRX Onduration interval and/or timer used for that UE operates as Awake state) to be stopped and/or expired, UE may prevent interval of active time of the Uu DRX (Uu DRX operation for supporting sidelink mode 1 operation) and/or active time of Sidelink DRX from being extended. For example, according to an embodiment of the present disclosure, by regarding timer related to UU DRX (For example, Uu DRX operation for supporting sidelink mode 1)/Sidelink DRX operation to be stopped or expired, UE may be prevented from remaining in the Awake state. For example, according to an embodiment of the present disclosure, UE may reduce power consumption through proposal of the present disclosure.
Referring to
Referring to
In step S1430, for example, the TX UE may receive, from the BS, information related to at least one SL resource. For example, the at least one SL resource (For example, SL grant) may include at least one of configured grant (CG) resource allocated to the TX UE via CG configuration information or dynamic grant (DG) resource allocated to the TX UE via downlink control information (DCI) related to DG. For example, information related to CG resource may be received, from the BS, via the RRC message. In step S1440 and step S1442, for example, the TX XE may transmit, to the RX UE, PSCCH (For example, first SCI transmitted via PSCCH)/PSSCH (For example, second SCI, MAC PDU transmitted via PSSCH), based on the CG resource or the DG resource. In step S1444, (For example, if PSFCH resource is configured) RX UE may transmit, to the TX UE, SL HARQ information (For example, SL HARQ NACK information, SL HARQ ACK information) for received PSCCH/PSSCH.
In step S1450, for example, the TX UE may start DRX HARQ RTT timer. For example, if the TX UE (For example, if UL resource is configured) report, to the BS, SL HARQ NACK, TX UE may start DRX HARQ RTT timer.
For example, MAC reset may include at least one Uu interface MAC reset or Sidelink interface MAC reset (For example, MAC reset related to PC5-RRC connection with another UE).
For example, Uu DRX timer of TX UE may be started/running (For example, may not be stopped). For example, in step S1460, before TX UE is requested to MAC reset related to PC5-RRC, DRX HARQ RTT timer of TX UE may be running. For example, in step S1460, before TX UE is requested to MAC reset related to PC5-RRC and after DRX HARQ RTT timer of TX UE is expired, DRX retransmission timer of TX UE may be started/running.
In step S1470, for example, TX UE and/or RX UE may be requested to MAC reset related to PC5-RRC connection, for example, TX UE and/or RX UE may detect request of the MAC reset related to PC5-RRC connection. In step S1470, for example, TX UE and/or RX UE may be requested to MAC reset related to PC5-RRC connection, and may determine whether Uu DRX timer is running.
In step S1472, for example, if TX UE is requested to MAC reset related to PC5-RRC, and Uu DRX timer is running, TX UE may stop running Uu DRX timer. For example, in step S1472, if TX UE and/or RX UE is requested MAC reset related to PC5-RRC and before DRX retransmission timer of TX UE is triggered, DRX retransmission timer of TX UE may not be triggered. For example, TX UE may report, to BS, information for MAC reset related to PC5-RRC
For example, MAC reset may perform operation related to the PC5-RRC connection (For example, at least one of flushing the soft buffers for all Sidelink processes for all TB(s) associated to the PC5-RRC connection: considering all Sidelink processes for all TB(s) associated to the PC5-RRC connection as unoccupied: canceling triggered Scheduling Request procedure only associated to the PC5-RRC connection: canceling triggered Sidelink Buffer Status Reporting procedure only associated to the PC5-RRC connection: canceling triggered Sidelink CSI Reporting procedure associated to the PC5-RRC connection: stopping all timers associated to the PC5-RRC connection: resetting/initializing parameter associated to the PC5-RRC connection (For example, numConsecutiveDTX, SBj for each logical channel)). For example, if UE is requested sidelink interface MAC reset and if UE is running SL DRX timer, UE may stop the sidelink DRX timer. For example, if UE is requested sidelink interface MAC reset and if UE is running SL DRX timer, UE may stop PSCCH/PSSCH monitoring.
As a result, for example, if TX UE is requested sidelink interface MAC reset, TX UE may not perform monitoring for DCI (PDCCH). For example, if TX UE is requested to sidelink interface MAC reset, overhead is not unnecessarily occurred because TX UE performs monitoring DCI (PDCCH).
Therefore, if sidelink interface MAC reset related to RRC connection with another UE is requested, operation of sidelink resource allocation mode 1 that UE is performing (For example, or triggered), and/or operation of Uu DRX timer that UE is running may be clearly defined. For example, if TX UE and/or RX UE is requested to MAC reset related to PC5-RRC connection, at least one timer not related to PC5-RRC may be stopped. For example, in step S1472, DRX HARQ RTT timer of TX UE and/or DRX retransmission timer of TX UE may be stopped. For example, in step S1480, TX UE may not be allocated, from BS, DG-based retransmission resource (For example, SL retransmission grant). For example, in step S1472, TX UE may not perform retransmission (For example, HARQ retransmission) for existing TB to RX UE.
Therefore, an embodiment of the present disclosure may have various effectiveness. For example, according to an embodiment of the present disclosure, monitoring operation for performable sidelink (retransmission) grant may not be unnecessarily performed although sidelink MAC configuration is reset by triggered sidelink MAC reset. For example, according to an embodiment of the present disclosure, Uu DRX operation may not be unnecessarily performed although sidelink MAC configuration is reset by triggered sidelink MAC reset. For example, according to an embodiment of the present disclosure, as Uu DRX operation is not unnecessarily performed, power of the UE may not be wasted. For example, according to an embodiment of the present disclosure, as Uu DRX operation is not unnecessarily performed, signalling overhead due to Uu DRX operation may be reduced. For example, according to an embodiment of the present disclosure, as monitoring operation of sidelink retransmission grant is not unnecessarily performed, sidelink communication may be effectively performed. For example, according to an embodiment of the present disclosure, as monitoring operation of sidelink retransmission grant is not performed, low latency of the sidelink communication may be enhanced.
In addition, an on-duration mentioned in the proposal of the present disclosure can be extended and interpreted as an active time period (e.g., time to wake-up state (e.g., RF module turned on) to receive/transmit radio signals), an off-duration may be extended and interpreted as a sleep time (e.g., a time for operating in a sleep mode state (e.g., a state in which an RF module is turned off) for power saving). It does not mean that a TX UE is obligated to operate in a sleep mode in a sleep time interval. If necessary, a TX UE may be allowed to operate in an active time for a while for a sensing operation and/or a transmission operation even in sleep time.
For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for a resource pool. For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for congestion level. For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for a priority of a service. For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for a service type. For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for a QoS requirement (e.g., latency, reliability). For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for PQI(5QI(5G QoS identifier) for PC5). For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for a traffic type (e.g., a periodic generation or a aperiodic generation). For example, whether the (part of) proposed method/rule of the present disclosure is applied and/or a related parameter (e.g., threshold) may be configured specifically (or differently or independently) for an SL transmission resource allocation mode (e.g., mode 1 or mode 2).
For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a resource pool. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a type of service/packet. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a priority of service/packet. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for QoS requirements (e.g., URLLC/EMBB traffic, reliability, latency). For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for PQI. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a cast type (e.g., unicast, groupcast, broadcast). For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for (resource pool) congestion level (e.g., CBR). For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for SL HARQ feedback scheme (e.g., NACK-only feedback, ACK/NACK feedback). For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for HARQ Feedback Enabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for HARQ Feedback Disabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for whether PUCCH-based SL HARQ feedback reporting operation is set. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a resource reselection based on pre-emption or pre-emption. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a re-evaluation or re-selection of resources based on re-evaluation.
For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for (L2 or L1) (source and/or destination) identifier. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for (L2 or L1) (Combination of Source ID and Destination ID) Identifier. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for (L2 or L1) (a combination of source ID and destination ID pair and cast type) identifier. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for the direction of a pair of source layer ID and destination layer ID. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for PC5 RRC connection/link. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for the case of performing SL DRX. For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for SL mode type (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether the proposed rule of the present disclosure is applied and/or related parameter setting values may be configured specifically (or differently or independently) for a case of performing (a) periodic resource reservation.
The certain time referred to in the proposal of the present disclosure may refer to a time during which a UE operates as an active time for a predefined time in order to receive a sidelink signal or sidelink data from a counterpart UE. A certain time referred to in the proposal of the present disclosure may refer to a time during which a UE operates as an active time for a specific timer (e.g., a sidelink DRX retransmission timer, a sidelink DRX inactivity timer, or a timer that guarantees operation as active time in DRX operation of an RX UE) time in order to receive a sidelink signal or sidelink data from a counterpart UE. In addition, whether the proposal and proposal rule of the present disclosure are applied (and/or related parameter setting values) may also be applied to mmWave SL operation.
Referring to
Additionally or alternatively, the first device may determine that the Uu DRX timer may be expired, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the second device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the PC5-RRC connection with the second device may include at least one SL unicast link with the second device.
Additionally or alternatively, Uu DRX timer related to all SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the all SL unicast link among the at least one SL unicast link is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the PC5-RRC connection with the second device may include at least one SL unicast link with the second device.
Additionally or alternatively, Uu DRX timer related to first SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the first SL unicast link among the at least one SL unicast link is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the first device may stop monitoring for receiving the SL retransmission grant, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the second device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the DRX retransmission timer may be stopped, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the second device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the DRX HARQ RTT timer may be stopped, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the second device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the DRX configuration may include information related to SL DRX timer.
Additionally or alternatively, the information related to the SL DRX timer and the DRX configuration including the information related to the Uu DRX timer may be obtained.
Additionally or alternatively, the first device may start SL DRX timer related to the PC5-RRC connection.
Additionally or alternatively, the first device may stop the SL DRX timer, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the second device is requested, and based on that the SL DRX timer related to the PC5-RRC connection is running.
Additionally or alternatively, the PC5-RRC connection with the second device may include at least one SL unicast link with the second device.
Additionally or alternatively, SL DRX timer related to all SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the all SL unicast link among the at least one SL unicast link is requested, and based on that the started SL DRX timer is running.
Additionally or alternatively, the PC5-RRC connection with the second device may include at least one SL unicast link with the second device.
Additionally or alternatively, SL DRX timer related to first SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the first SL unicast link among the at least one SL unicast link is requested, and based on that the started SL DRX timer is running.
Additionally or alternatively, the SL DRX timer may include at least one of SL DRX onduration timer, SL DRX inactivity timer, SL DRX retransmission timer, or SL DRX HARQ RTT timer.
Additionally or alternatively, the sidelink SL specific MAC reset for the PC5-RRC connection may be requested, based on at least one of SL radio link failure (RLF), PC5-RRC reconfiguration failure, PC5 DRX configuration failure, security check failure, integrity check failure, listen before talk (LBT) failure, or request from upper layer.
The proposed method may be adapted to the device according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) may establish PC5-RRC connection with a second device. For example, the processor (102) of the first device (100) may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the processor (102) of the first device (100) may start the Uu DRX timer. For example, the processor (102) of the first device (100) may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
According to an embodiment of the present disclosure, the first device performing wireless communication may be provided. The first device comprising at least one memory storing instructions: at least one transceiver; and at least one processor connected to the at least one memory and the at least one transceiver, wherein the at least one processor is adapted to execute instructions to perform operations comprising: may establish PC5-RRC connection with a second device. For example, based on the instructions executed by the at least one processor, the first device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, based on the instructions executed by the at least one processor, the first device may start the Uu DRX timer. For example, based on the instructions executed by the at least one processor, the first device may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
According to an embodiment of the present disclosure, the apparatus configured for control the first device may be provided. The apparatus comprising at least one processor; and at least one memory connected to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the first device to perform operations comprising: may establish PC5-RRC connection with a second device. For example, based on the instructions executed by the at least one processor, the first device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, based on the instructions executed by the at least one processor, the first device may start the Uu DRX timer. For example, based on the instructions executed by the at least one processor, the first device may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. The instructions, based on being executed by at least one processor, cause the at least one processor to perform operations comprising: establish PC5-RRC connection with a second device. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the first device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the first device may start the Uu DRX timer. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the first device may stop the started Uu DRX timer, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
Referring to
Additionally or alternatively, it may be determined that the Uu DRX timer may be expired, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the first device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the PC5-RRC connection with the first device may include at least one SL unicast link with the second device.
Additionally or alternatively, Uu DRX timer related to all SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the all SL unicast link among the at least one SL unicast link is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the PC5-RRC connection with the first device may include at least one SL unicast link with the second device.
Additionally or alternatively, Uu DRX timer related to first SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the first SL unicast link among the at least one SL unicast link is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, monitoring for receiving the SL retransmission grant may be stopped, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the first device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the DRX retransmission timer may be stopped, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the first device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the DRX HARQ RTT timer may be stopped, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the first device is requested, and based on that the started Uu DRX timer is running.
Additionally or alternatively, the DRX configuration may include information related to SL DRX timer.
Additionally or alternatively, the information related to the SL DRX timer and the DRX configuration including the information related to the Uu DRX timer may be obtained.
Additionally or alternatively, the second device may start SL DRX timer related to the PC5-RRC connection.
Additionally or alternatively, the second device may stop the SL DRX timer, based on that the sidelink SL specific MAC reset for the PC5-RRC connection with the first device is requested, and based on that the SL DRX timer related to the PC5-RRC connection is running.
Additionally or alternatively, the PC5-RRC connection with the first device may include at least one SL unicast link with the second device.
Additionally or alternatively, SL DRX timer related to all SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the all SL unicast link among the at least one SL unicast link is requested, and based on that the started SL DRX timer is running.
Additionally or alternatively, the PC5-RRC connection with the first device may include at least one SL unicast link with the second device.
Additionally or alternatively, SL DRX timer related to first SL unicast link among the at least one SL unicast link may be stopped, based on that MAC reset related to the first SL unicast link among the at least one SL unicast link is requested, and based on that the started SL DRX timer is running.
Additionally or alternatively, the SL DRX timer may include at least one of SL DRX onduration timer, SL DRX inactivity timer, SL DRX retransmission timer, or SL DRX HARQ RTT timer.
Additionally or alternatively, the sidelink SL specific MAC reset for the PC5-RRC connection may be requested, based on at least one of SL radio link failure (RLF), PC5-RRC reconfiguration failure, PC5 DRX configuration failure, security check failure, integrity check failure, listen before talk (LBT) failure, or request from upper layer.
The proposed method may be adapted to the device according to various embodiments of the present disclosure. First, the processor (202) of the second device (200) may establish PC5-RRC connection with a first device. For example, the processor (202) of the second device (200) may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
According to an embodiment of the present disclosure, the second device performing wireless communication may be provided. The second device comprising at least one memory storing instructions: at least one transceiver; and at least one processor connected to the at least one memory and the at least one transceiver, wherein the at least one processor is adapted to execute instructions to perform operations comprising: may establish PC5-RRC connection with a first device. For example, based on the instructions executed by the at least one processor, the second device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
According to an embodiment of the present disclosure, the apparatus configured for control the second device may be provided. The apparatus comprising at least one processor; and at least one memory connected to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the second device to perform operations comprising: may establish PC5-RRC connection with a first device. For example, based on the instructions executed by the at least one processor, the second device may obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. The instructions, based on being executed by at least one processor, cause the at least one processor to perform operations comprising: the second device to establish PC5-RRC connection with a first device. For example, the instructions, based on being executed by at least one processor, cause the at least one processor to: the second device to obtain discontinuous reception (DRX) configuration including information related to Uu DRX timer. For example, the Uu DRX timer may be at least one of DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer or DRX retransmission timer. For example, time that the DRX retransmission timer is running may be a time included in active time of the first device. For example, the Uu DRX timer may be started. For example, the started Uu DRX timer may be stopped, based on that sidelink (SL) specific medium access control (MAC) reset for the PC5-RRC connection with the second device is request, and based on that the started Uu DRX timer is running. For example, the DRX HARQ RTT timer may be a minimum duration before SL retransmission grant is expected by the first device. For example, the DRX retransmission timer may be a maximum duration until the SL retransmission grant is received by the first device.
Various embodiments of the present disclosure may be combined with each other.
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 at least one memory 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 at least one memory 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 the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2022/012314, filed on Aug. 18, 2022, which claims the benefit of U.S. Provisional Application No. 63/235,131, filed on Aug. 19, 2021, the contents of which are all incorporated by reference herein in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2022/012314 | 8/18/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 62235131 | Sep 2015 | US |
