Patent Application
20240414601
The following description relates to a wireless communication system, and more particularly, to an operation method and apparatus related to sidelink DRX and/or handover.
Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. In general, a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of the multiple access system include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system, and a multi carrier frequency division multiple access (MC-FDMA) system.
A wireless communication system uses various radio access technologies (RATs) such as long term evolution (LTE), LTE-advanced (LTE-A), and wireless fidelity (WiFi). 5th generation (5G) is such a wireless communication system. Three key requirement areas of 5G include (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC). Some use cases may require multiple dimensions for optimization, while others may focus only on one key performance indicator (KPI). 5G supports such diverse use cases in a flexible and reliable way.
eMBB goes far beyond basic mobile Internet access and covers rich interactive work, media and entertainment applications in the cloud or augmented reality (AR). Data is one of the key drivers for 5G and in the 5G era, we may for the first time see no dedicated voice service. In 5G, voice is expected to be handled as an application program, simply using data connectivity provided by a communication system. The main drivers for an increased traffic volume are the increase in the size of content and the number of applications requiring high data rates. Streaming services (audio and video), interactive video, and mobile Internet connectivity will continue to be used more broadly as more devices connect to the Internet. Many of these applications require always-on connectivity to push real time information and notifications to users. Cloud storage and applications are rapidly increasing for mobile communication platforms. This is applicable for both work and entertainment. Cloud storage is one particular use case driving the growth of uplink data rates. 5G will also be used for remote work in the cloud which, when done with tactile interfaces, requires much lower end-to-end latencies in order to maintain a good user experience. Entertainment, for example, cloud gaming and video streaming, is another key driver for the increasing need for mobile broadband capacity. Entertainment will be very essential on smart phones and tablets everywhere, including high mobility environments such as trains, cars and airplanes. Another use case is augmented reality (AR) for entertainment and information search, which requires very low latencies and significant instant data volumes.
One of the most expected 5G use cases is the functionality of actively connecting embedded sensors in every field, that is, mMTC. It is expected that there will be 20.4 billion potential Internet of things (IoT) devices by 2020. In industrial IoT, 5G is one of areas that play key roles in enabling smart city, asset tracking, smart utility, agriculture, and security infrastructure.
URLLC includes services which will transform industries with ultra-reliable/available, low latency links such as remote control of critical infrastructure and self-driving vehicles. The level of reliability and latency are vital to smart-grid control, industrial automation, robotics, drone control and coordination, and so on.
Now, multiple use cases will be described in detail.
5G may complement fiber-to-the home (FTTH) and cable-based broadband (or data-over-cable service interface specifications (DOCSIS)) as a means of providing streams at data rates of hundreds of megabits per second to giga bits per second. Such a high speed is required for TV broadcasts at or above a resolution of 4K (6K, 8K, and higher) as well as virtual reality (VR) and AR. VR and AR applications mostly include immersive sport games. A special network configuration may be required for a specific application program. For VR games, for example, game companies may have to integrate a core server with an edge network server of a network operator in order to minimize latency.
The automotive sector is expected to be a very important new driver for 5G, with many use cases for mobile communications for vehicles. For example, entertainment for passengers requires simultaneous high capacity and high mobility mobile broadband, because future users will expect to continue their good quality connection independent of their location and speed. Other use cases for the automotive sector are AR dashboards. These display overlay information on top of what a driver is seeing through the front window, identifying objects in the dark and telling the driver about the distances and movements of the objects. In the future, wireless modules will enable communication between vehicles themselves, information exchange between vehicles and supporting infrastructure and between vehicles and other connected devices (e.g., those carried by pedestrians). Safety systems may guide drivers on alternative courses of action to allow them to drive more safely and lower the risks of accidents. The next stage will be remote-controlled or self-driving vehicles. These require very reliable, very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will execute all driving activities, while drivers are focusing on traffic abnormality elusive to the vehicles themselves. The technical requirements for self-driving vehicles call for ultra-low latencies and ultra-high reliability, increasing traffic safety to levels humans cannot achieve.
Smart cities and smart homes, often referred to as smart society, will be embedded with dense wireless sensor networks. Distributed networks of intelligent sensors will identify conditions for cost- and energy-efficient maintenance of the city or home. A similar setup can be done for each home, where temperature sensors, window and heating controllers, burglar alarms, and home appliances are all connected wirelessly. Many of these sensors are typically characterized by low data rate, low power, and low cost, but for example, real time high definition (HD) video may be required in some types of devices for surveillance.
The consumption and distribution of energy, including heat or gas, is becoming highly decentralized, creating the need for automated control of a very distributed sensor network. A smart grid interconnects such sensors, using digital information and communications technology to gather and act on information. This information may include information about the behaviors of suppliers and consumers, allowing the smart grid to improve the efficiency, reliability, economics and sustainability of the production and distribution of fuels such as electricity in an automated fashion. A smart grid may be seen as another sensor network with low delays.
The health sector has many applications that may benefit from mobile communications. Communications systems enable telemedicine, which provides clinical health care at a distance. It helps eliminate distance barriers and may improve access to medical services that would often not be consistently available in distant rural communities. It is also used to save lives in critical care and emergency situations. Wireless sensor networks based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
Wireless and mobile communications are becoming increasingly important for industrial applications. Wires are expensive to install and maintain, and the possibility of replacing cables with reconfigurable wireless links is a tempting opportunity for many industries. However, achieving this requires that the wireless connection works with a similar delay, reliability and capacity as cables and that its management is simplified. Low delays and very low error probabilities are new requirements that need to be addressed with 5G
Finally, logistics and freight tracking are important use cases for mobile communications that enable the tracking of inventory and packages wherever they are by using location-based information systems. The logistics and freight tracking use cases typically require lower data rates but need wide coverage and reliable location information.
A wireless communication system is a multiple access system that supports communication of multiple users by sharing available system resources (a bandwidth, transmission power, etc.). Examples of multiple access systems include a CDMA system, an FDMA system, a TDMA system, an OFDMA system, an SC-FDMA system, and an MC-FDMA system.
Sidelink (SL) refers to a communication scheme in which a direct link is established between user equipments (UEs) and the UEs directly exchange voice or data without intervention of a base station (BS). SL is considered as a solution of relieving the BS of the constraint of rapidly growing data traffic.
Vehicle-to-everything (V2X) is a communication technology in which a vehicle exchanges information with another vehicle, a pedestrian, and infrastructure by wired/wireless communication. V2X may be categorized into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication may be provided via a PC5 interface and/or a Uu interface.
As more and more communication devices demand larger communication capacities, there is a need for enhanced mobile broadband communication relative to existing RATs. Accordingly, a communication system is under discussion, for which services or UEs sensitive to reliability and latency are considered. The next-generation RAT in which eMBB, MTC, and URLLC are considered is referred to as new RAT or NR. In NR, V2X communication may also be supported.
For V2X communication, a technique of providing safety service based on V2X messages such as basic safety message (BSM), cooperative awareness message (CAM), and decentralized environmental notification message (DENM) was mainly discussed in the pre-NR RAT. The V2X message may include location information, dynamic information, and attribute information. For example, a UE may transmit a CAM of a periodic message type and/or a DENM of an event-triggered type to another UE.
For example, the CAM may include basic vehicle information including dynamic state information such as a direction and a speed, vehicle static data such as dimensions, an external lighting state, path details, and so on. For example, the UE may broadcast the CAM which may have a latency less than 100 ms. For example, when an unexpected incident occurs, such as breakage or an accident of a vehicle, the UE may generate the DENM and transmit the DENM to another UE. For example, all vehicles within the transmission range of the UE may receive the CAM and/or the DENM. In this case, the DENM may have priority over the CAM.
In relation to V2X communication, various V2X scenarios are presented in NR. For example, the V2X scenarios include vehicle platooning, advanced driving, extended sensors, and remote driving.
For example, vehicles may be dynamically grouped and travel together based on vehicle platooning. For example, to perform platoon operations based on vehicle platooning, the vehicles of the group may receive periodic data from a leading vehicle. For example, the vehicles of the group may widen or narrow their gaps based on the periodic data.
For example, a vehicle may be semi-automated or full-automated based on advanced driving. For example, each vehicle may adjust a trajectory or maneuvering based on data obtained from a nearby vehicle and/or a nearby logical entity. For example, each vehicle may also share a dividing intention with nearby vehicles.
Based on extended sensors, for example, raw or processed data obtained through local sensor or live video data may be exchanged between vehicles, logical entities, terminals of pedestrians and/or V2X application servers. Accordingly, a vehicle may perceive an advanced environment relative to an environment perceivable by its sensor.
Based on remote driving, for example, a remote driver or a V2X application may operate or control a remote vehicle on behalf of a person incapable of driving or in a dangerous environment. For example, when a path may be predicted as in public transportation, cloud computing-based driving may be used in operating or controlling the remote vehicle. For example, access to a cloud-based back-end service platform may also be used for remote driving.
A scheme of specifying service requirements for various V2X scenarios including vehicle platooning, advanced driving, extended sensors, and remote driving is under discussion in NR-based V2X communication.
Embodiment(s) is to provide a handover-related operation of a sidelink transmission user equipment (TX UE) and DRX configuration setting of a reception user equipment (RX UE) after handover.
According to an embodiment of the present disclosure, an operation method of a sidelink transmission (TX) user equipment (UE) in a wireless communication system includes establishing a PC5 connection with a reception (RX) UE by the TX UE, transmitting a first sidelink DRX configuration to the RX UE by the TX UE, transmitting a measurement report to a source base station (BS) by the TX UE, receiving a handover command from the source BS by the TX UE, and performing a handover procedure by the TX UE, wherein the TX UE transmits a second sidelink DRX configuration to the RX UE based on completion of the handover procedure, and the second sidelink DRX configuration is configured by a target BS of the handover procedure.
According to an embodiment of the present disclosure, a transmission (TX) user equipment (UE) in a wireless communication system includes at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that when executed causes the at least one processor to perform operations including establishing a PC5 connection with a reception (RX) UE by the TX UE, transmitting a first sidelink DRX configuration to the RX UE by the TX UE, transmitting a measurement report to a source base station (BS) by the TX UE, receiving a handover command from the source BS by the TX UE, and performing a handover procedure by the TX UE, wherein the TX UE transmits a second sidelink DRX configuration to the RX UE based on completion of the handover procedure, and the second sidelink DRX configuration is configured by a target BS of the handover procedure.
According to an embodiment of the present disclosure, a processor for performing operations for a transmission (TX) user equipment (UE) in a wireless communication system includes establishing a PC5 connection with a reception (RX) UE by the TX UE, transmitting a first sidelink DRX configuration to the RX UE by the TX UE, transmitting a measurement report to a source base station (BS) by the TX UE, receiving a handover command from the source BS by the TX UE, and performing a handover procedure by the TX UE, wherein the TX UE transmits a second sidelink DRX configuration to the RX UE based on completion of the handover procedure, and the second sidelink DRX configuration is configured by a target BS of the handover procedure.
An embodiment of the present disclosure provides a non-volatile computer-readable storage medium for storing at least one computer program including an instruction for causing at least one processor to perform operations for a transmission (TX) user equipment (UE) when being executed by the at least one processor, the operations including establishing a PC5 connection with a reception (RX) UE by the TX UE, transmitting a first sidelink DRX configuration to the RX UE by the TX UE, transmitting a measurement report to a source base station (BS) by the TX UE, receiving a handover command from the source BS by the TX UE, and performing a handover procedure by the TX UE, wherein the TX UE transmits a second sidelink DRX configuration to the RX UE based on completion of the handover procedure, and the second sidelink DRX configuration is configured by a target BS of the handover procedure.
According to an embodiment of the present disclosure, an operation method of a target base station (BS) in a wireless communication system includes setting a second sidelink DRX configuration by the target BS, transmitting a handover command to a transmission (TX) user equipment (UE) that transmits a first sidelink DRX configuration to a reception (RX) UE after establishing a PC5 connection with a reception UE by the target BS, wherein the second sidelink DRX configuration is transmitted to the RX UE based on completion of a handover procedure of the TX UE.
The second sidelink DRX configuration may be included in the handover command.
The second SL DRX configuration may be based on assistance information.
The TX UE may request assistance information from the RX UE based on the measurement report being triggered
The TX UE may transmit the assistance information to the target BS.
The TX UE may communicate with at least one of another UE, a UE related to an autonomous driving vehicle, a base station (BS), or a network.
The second sidelink DRX configuration may be included in the handover command.
The target BS may receive assistance information of the RX UE from the TX UE.
The target BS may transmit an SL DRX configuration based on the assistance information to the TX UE.
According to an embodiment, a target base station (BS) may set a DRX configuration of a reception (RX) user equipment (UE) after handover, and thus may reduce latency up to a new SL DRX configuration after handover.
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the principle of the disclosure. In the drawings:
In various embodiments of the present disclosure, “/” and “,” should be interpreted as “and/or”. For example, “A/B” may mean “A and/or B”. Further, “A, B” may mean “A and/or B”. Further, “A/B/C” may mean “at least one of A, B and/or C”. Further, “A, B, C” may mean “at least one of A, B and/or C”.
In various embodiments of the present disclosure, “or” should be interpreted as “and/or”. For example, “A or B” may include “only A”, “only B”, and/or “both A and B”. In other words, “or” should be interpreted as “additionally or alternatively”.
Techniques described herein may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier-frequency division multiple access (SC-FDMA), and so on. CDMA may be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved-UTRA (E-UTRA), or the like. IEEE 802.16m is an evolution of IEEE 802.16e, offering backward compatibility with an IRRR 802.16e-based system. UTRA is a part of universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using evolved UTRA (E-UTRA). 3GPP LTE employs OFDMA for downlink (DL) and SC-FDMA for uplink (UL). LTE-advanced (LTE-A) is an evolution of 3GPP LTE.
A successor to LTE-A, 5th generation (5G) new radio access technology (NR) is a new clean-state mobile communication system characterized by high performance, low latency, and high availability. 5G NR may use all available spectral resources including a low frequency band below 1 GHZ, an intermediate frequency band between 1 GHz and 10 GHz, and a high frequency (millimeter) band of 24 GHz or above.
While the following description is given mainly in the context of LTE-A or 5G NR for the clarity of description, the technical idea of an embodiment of the present disclosure is not limited thereto.
Referring to
eNBs 20 may be connected to each other via an X2 interface. An eNB 20 is connected to an evolved packet core (EPC) 39 via an S1 interface. More specifically, the eNB 20 is connected to a mobility management entity (MME) via an S1-MME interface and to a serving gateway (S-GW) via an S1-U interface.
The EPC 30 includes an MME, an S-GW, and a packet data network-gateway (P-GW). The MME has access information or capability information about UEs, which are mainly used for mobility management of the UEs. The S-GW is a gateway having the E-UTRAN as an end point, and the P-GW is a gateway having a packet data network (PDN) as an end point.
Based on the lowest three layers of the open system interconnection (OSI) reference model known in communication systems, the radio protocol stack between a UE and a network may be divided into Layer 1 (L1), Layer 2 (L2) and Layer 3 (L3). These layers are defined in pairs between a UE and an Evolved UTRAN (E-UTRAN), for data transmission via the Uu interface. The physical (PHY) layer at L1 provides an information transfer service on physical channels. The radio resource control (RRC) layer at L3 functions to control radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and an eNB.
Referring to
Data is transmitted on physical channels between different PHY layers, that is, the PHY layers of a transmitter and a receiver. The physical channels may be modulated in orthogonal frequency division multiplexing (OFDM) and use time and frequencies as radio resources.
The MAC layer provides services to a higher layer, radio link control (RLC) on logical channels. The MAC layer provides a function of mapping from a plurality of logical channels to a plurality of transport channels. Further, the MAC layer provides a logical channel multiplexing function by mapping a plurality of logical channels to a single transport channel. A MAC sublayer provides a data transmission service on the logical channels.
The RLC layer performs concatenation, segmentation, and reassembly for RLC serving data units (SDUs). In order to guarantee various quality of service (QOS) requirements of each radio bearer (RB), the RLC layer provides three operation modes, transparent mode (TM), unacknowledged mode (UM), and acknowledged Mode (AM). An AM RLC provides error correction through automatic repeat request (ARQ).
The RRC layer is defined only in the control plane and controls logical channels, transport channels, and physical channels in relation to configuration, reconfiguration, and release of RBs. An RB refers to a logical path provided by L1 (the PHY layer) and L2 (the MAC layer, the RLC layer, and the packet data convergence protocol (PDCP) layer), for data transmission between the UE and the network.
The user-plane functions of the PDCP layer include user data transmission, header compression, and ciphering. The control-plane functions of the PDCP layer include control-plane data transmission and ciphering/integrity protection.
RB establishment amounts to a process of defining radio protocol layers and channel features and configuring specific parameters and operation methods in order to provide a specific service. RBs may be classified into two types, signaling radio bearer (SRB) and data radio bearer (DRB). The SRB is used as a path in which an RRC message is transmitted on the control plane, whereas the DRB is used as a path in which user data is transmitted on the user plane.
Once an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is placed in RRC_CONNECTED state, and otherwise, the UE is placed in RRC_IDLE state. In NR, RRC_INACTIVE state is additionally defined. A UE in the RRC_INACTIVE state may maintain a connection to a core network, while releasing a connection from an eNB.
DL transport channels carrying data from the network to the UE include a broadcast channel (BCH) on which system information is transmitted and a DL shared channel (DL SCH) on which user traffic or a control message is transmitted. Traffic or a control message of a DL multicast or broadcast service may be transmitted on the DL-SCH or a DL multicast channel (DL MCH). UL transport channels carrying data from the UE to the network include a random access channel (RACH) on which an initial control message is transmitted and an UL shared channel (UL SCH) on which user traffic or a control message is transmitted.
The logical channels which are above and mapped to the transport channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a multicast traffic channel (MTCH).
A physical channel includes a plurality of OFDM symbol in the time domain by a plurality of subcarriers in the frequency domain. One subframe includes a plurality of OFDM symbols in the time domain. An RB is a resource allocation unit defined by a plurality of OFDM symbols by a plurality of subcarriers. Further, each subframe may use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) in a corresponding subframe for a physical DL control channel (PDCCH), that is, an L1/L2 control channel. A transmission time interval (TTI) is a unit time for subframe transmission.
Referring to
Referring to
Referring to
In a normal CP (NCP) case, each slot may include 14 symbols, whereas in an extended CP (ECP) case, each slot may include 12 symbols. Herein, a symbol may be an OFDM symbol (or CP-OFDM symbol) or an SC-FDMA symbol (or DFT-s-OFDM symbol).
Table 1 below lists the number of symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslot according to an SCS configuration u in the NCP case.
Table 2 below lists the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to an SCS in the ECP case.
In the NR system, different OFDM (A) numerologies (e.g., SCSs, CP lengths, and so on) may be configured for a plurality of cells aggregated for one UE. Accordingly, the (absolute time) duration of a time resource including the same number of symbols (e.g., a subframe, slot, or TTI) (collectively referred to as a time unit (TU) for convenience) may be configured to be different for the aggregated cells.
In NR, various numerologies or SCSs may be supported to support various 5G services. For example, with an SCS of 15 kHz, a wide area in traditional cellular bands may be supported, while with an SCS of 30/60 kHz, a dense urban area, a lower latency, and a wide carrier bandwidth may be supported. With an SCS of 60 kHz or higher, a bandwidth larger than 24.25 GHz may be supported to overcome phase noise.
An NR frequency band may be defined by two types of frequency ranges, FR1 and FR2. The numerals in each frequency range may be changed. For example, the two types of frequency ranges may be given in [Table 3]. In the NR system, FR1 may be a “sub 6 GHz range” and FR2 may be an “above 6 GHz range” called millimeter wave (mmW).
As mentioned above, the numerals in a frequency range may be changed in the NR system. For example, FR1 may range from 410 MHz to 7125 MHz as listed in [Table 4]. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, and 5925 MHz) or above. For example, the frequency band of 6 GHz (or 5850, 5900, and 5925 MHz) or above may include an unlicensed band. The unlicensed band may be used for various purposes, for example, vehicle communication (e.g., autonomous driving).
Referring to
A carrier includes a plurality of subcarriers in the frequency domain. An RB may be defined by a plurality of (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) may be defined by a plurality of consecutive (physical) RBs ((P) RBs) in the frequency domain and correspond to one numerology (e.g., SCS, CP length, or the like). A carrier may include up to N (e.g., 5) BWPs. Data communication may be conducted in an activated BWP. Each element may be referred to as a resource element (RE) in a resource grid, to which one complex symbol may be mapped.
A radio interface between UEs or a radio interface between a UE and a network may include L1, L2, and L3. In various embodiments of the present disclosure, L1 may refer to the PHY layer. For example, L2 may refer to at least one of the MAC layer, the RLC layer, the PDCH layer, or the SDAP layer. For example, L3 may refer to the RRC layer.
Now, a description will be given of sidelink (SL) communication.
Referring to
Alternatively, a UE may be directly synchronized with a BS or may be synchronized with another UE that is synchronized in time/frequency with the BS. For example, the BS may be an eNB or a gNB. For example, when a UE is in network coverage, the UE may receive synchronization information provided by the BS and may be directly synchronized with the BS. Next, the UE may provide the synchronization information to another adjacent UE. If a timing of the BS is configured as a synchronization reference, the UE may follow a cell associated with a corresponding frequency (when the UE is in cell coverage in frequency) or a primary cell or a serving cell (when the UE is out of cell coverage in frequency), for synchronization and DL measurement.
The BS (e.g., serving cell) may provide a synchronization configuration for a carrier used for V2X/SL communication. In this case, the UE may conform to the synchronization configuration received from the BS. If the UE fails to detect any cell in the carrier used for V2X/SL communication and fails to receive the synchronization configuration from the serving cell, the UE may conform to a preset synchronization configuration.
Alternatively, the UE may be synchronized with another UE that has failed to directly or indirectly acquire the synchronization information from the BS or the GNSS. A synchronization source and a preference may be preconfigured for the UE. Alternatively, the synchronization source and the preference may be configured through a control message provided by the BS.
An SL synchronization source may be associated with a synchronization priority level. For example, the relationship between synchronization sources and synchronization priorities may be defined as shown in Table 5 or 6. Table 5 or 6 is merely an example, and the relationship between synchronization sources and synchronization priorities may be defined in various forms.
In Table 5 or 6, P0 may mean the highest priority, and P6 may mean the lowest priority. In Table 5 or 6, the BS may include at least one of a gNB or an eNB.
Whether to use GNSS-based synchronization or BS-based synchronization may be configured (in advance). In single-carrier operation, the UE may derive the transmission timing of the UE from an available synchronization reference with the highest priority.
Hereinafter, a sidelink synchronization signal (SLSS) and synchronization information will be described.
As an SL-specific sequence, the SLSS may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS). The PSSS may be referred to as a sidelink primary synchronization signal (S-PSS), and the SSSS may be referred to as a sidelink secondary synchronization signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 gold sequences may be used for the S-SSS. For example, the UE may use the S-PSS to detect an initial signal and obtain synchronization. In addition, the UE may use the S-PSS and the S-SSS to obtain detailed synchronization and detect a synchronization signal ID.
A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information that the UE needs to know first before SL signal transmission and reception. For example, the default information may include information related to an SLSS, a duplex mode (DM), a time division duplex (TDD) UL/DL configuration, information related to a resource pool, an application type related to the SLSS, a subframe offset, broadcast information, or the like. For example, for evaluation of PSBCH performance in NR V2X, the payload size of the PSBCH may be 56 bits including a CRC of 24 bits.
The S-PSS, S-SSS, and PSBCH may be included in a block format (e.g., SL synchronization signal (SS)/PSBCH block) supporting periodical transmission (hereinafter, the SL SS/PSBCH block is referred to as a sidelink synchronization signal block (S-SSB)). The S-SSB may have the same numerology (i.e., SCS and CP length) as that of a physical sidelink control channel (PSCCH)/physical sidelink shared channel (PSSCH) on a carrier, and the transmission bandwidth may exist within a configured (or preconfigured) SL BWP. For example, the S-SSB may have a bandwidth of 11 RBs. For example, the PSBCH may span 11 RBs. In addition, the frequency position of the S-SSB may be configured (in advance). Therefore, the UE does not need to perform hypothesis detection on frequency to discover the S-SSB in the carrier.
The NR SL system may support a plurality of numerologies with different SCSs and/or CP lengths. In this case, as the SCS increases, the length of a time resource on which the transmitting UE transmits the S-SSB may decrease. Accordingly, the coverage of the S-SSB may be reduced. Therefore, in order to guarantee the coverage of the S-SSB, the transmitting UE may transmit one or more S-SSBs to the receiving UE within one S-SSB transmission period based on the SCS. For example, the number of S-SSBs that the transmitting UE transmits to the receiving UE within one S-SSB transmission period may be pre-configured or configured for the transmitting UE. For example, the S-SSB transmission period may be 160 ms. For example, an S-SSB transmission period of 160 ms may be supported for all SCSs.
For example, when the SCS is 15 kHz in FR1, the transmitting UE may transmit one or two S-SSBs to the receiving UE within one S-SSB transmission period. For example, when the SCS is 30 kHz in FR1, the transmitting UE may transmit one or two S-SSBs to the receiving UE within one S-SSB transmission period. For example, when the SCS is 60 KHz in FR1, the transmitting UE may transmit one, two or four S-SSBs to the receiving UE within one S-SSB transmission period.
For example,
For example,
Referring to
For example, a first UE may receive information related to a Dynamic Grant (DG) resource and/or information related to a Configured Grant (CG) resource from a BS. For example, the CG resource may include a CG type 1 resource or a CG type 2 resource. In the present specification, the DG resource may be a resource that the BS configures/allocates to the first UE over Downlink Control Information (DCI). In the present specification, the CG resource may be a (periodic) resource configured/allocated by the BS to the first UE over a DCI and/or an RRC message. For example, in the case of the CG type 1 resource, the BS may transmit an RRC message including information related to the CG resource to the first UE. For example, in the case of the CG type 2 resource, the BS may transmit an RRC message including information related to the CG resource to the first UE, and the BS may transmit DCI related to activation or release of the CG resource to the first UE.
In a step S8010, the first UE may transmit PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second UE based on the resource scheduling. In a step S8020, the first UE may transmit PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In a step S8030, the first UE may receive PSFCH related to the PSCCH/PSSCH from the second UE. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second UE over the PSFCH. In a step S8040, the first UE may transmit/report HARQ feedback information to the BS over PUCCH or PUSCH. For example, the HARQ feedback information reported to the BS may include information generated by the first UE based on HARQ feedback information received from the second UE. For example, the HARQ feedback information reported to the BS may include information generated by the first UE based on a preset rule. For example, the DCI may be a DCI for scheduling of SL. For example, the format of the DCI may include DCI format 3_0 or DCI format 3_1. Table 7 shows one example of DCI for scheduling of SL.
Referring to
Referring to
Table 9 shows exemplary 2nd-stage SCI formats.
Referring to
Referring to
Table 12 below shows details of selection and reselection of an SL relay UE defined in 3GPP TS 36.331. The contents of Table 12 are used as the prior art of the present disclosure, and related necessary details may be found in 3GPP TS 36.331.
A MAC entity may be configured by an RRC as a DRX function of controlling a PDCCH monitoring activity of a UE for C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI, and SL Semi-Persistent Scheduling V-RNTI of the MAC entity. When using a DRX operation, a MAC entity should monitor PDCCH according to prescribed requirements. When DRX is configured in RRC_CONNECTED, a MAC entity may discontinuously monitor PDCCH for all activated serving cells.
RRC may control a DRX operation by configuring the following parameters.
Aserving cell of a MAC entity may be configured by RRC in two DRX groups having separate DRX parameters. When the RRC does not configure a secondary DRX group, a single DRX group exists only and all serving cells belong to the single DRX group. When two DRX groups are configured, each serving cell is uniquely allocated to each of the two groups. DRX parameters separately configured for each DRX group include drx-onDurationTimer and drx-Inactivity Timer. A DRX parameter common to a DRX group is as follows.
drx-onDurationTimer, drx-Inactivity Timer.
DRX parameters common to a DRX group are as follows.
drx-SlotOffset, drx-RetransmissionTimerDL, drx-Retrans drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.
In addition, in a Uu DRX operation of the related art, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL are defined. When UE HARQ retransmission is performed, it is secured to make transition to a sleep mode during RTT timer (drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) or to maintain an active state during Retransmission Timer (drx-RetransmissionTimerDL, drx-Retransmission TimerUL).
In addition, for details of SL DRX, SL DRX-related contents of TS 38.321 and R2-2111419 may be referred to as the related art.
Tables 13 to 16 below are descriptions related to sidelink DRX disclosed in the 3GPP TS 38.321 V16.2.1 and are used as the prior art of the present disclosure.
Table 17 below shows a portion of the Rel-17 V2X WID (RP-201385).
PC5 unicast link configuration procedure in terms of PC5-RRC of Rel-16 NR V2X may be reused to configure a secure unicast link for L2 UE-to-Network relaying between a remote UE and a relay UE before the remote UE establishes Uu RRC connection with a network through a relay UE.
When a first RRC message for configuring connection with a gNB by a remote UE for both in-coverage and out-of-coverage begins, a PC5 L2 configuration for transmission between the remote UE and the UE-to-Network Relay UE may be based on the RLC/MAC configuration defined in the standard. Establishment of Uu SRB1/SRB2 and DRB of the remote UE may comply with a procedure of configuring a legacy Uu for L2 UE-to-Network Relay.
A higher-level connection configuration procedure shown in
In operation S1200, the Remote and Relay UE may perform a search procedure and may configure PC5-RRC connection in operation S1201 based on the existing Rel-16 procedure.
In operation S1202, the remote UE may transmit a first RRC message (i.e., RRCSetupRequest) for connection configuration with a gNB through the relay UE using a basic L2 configuration of PC5. The gNB responds to the remote UE with an RRCSetup message (S1203). Transfer of RRCSetup to the remote UE may use a basic configuration. When the relay UE does not begin in RRC_CONNECTED, the relay UE needs to perform connection configuration thereof when receiving a message about the basic L2 configuration of PC5. In the current operation, a details for the RRCSetupRequest/RRCSetup message to the remote UE by the relay UE may be discussed in operation WI.
In operation S1204, the gNB and the relay UE may perform a relay channel configuration procedure through Uu. According to a configuration of the gNB, the relay/remote UE may configure an RLC channel for relaying SRB1 to the remote UE through PC5. The current operation prepares a relay channel for SRB1.
In operation S1205, the remote UE SRB1 message (e.g., RRCSetupComplete message) may be transmitted to the gNB through the relay UE using the SRB1 relay channel via PC5. The remote UE may be RRC-connected through Uu.
In operation S1206, the remote UE and the gNB configures security using a legacy procedure and transmits a security message through the relay UE.
In operation S1210, the gNB configures an additional RLC channel between the gNB and the relay UE for traffic relay. According to a configuration of the gNB, the relay/remote UE configures an additional RLC channel between the remote UE and the relay UE for traffic relay. The gNB transmits RRCReconfiguration to the remote UE through the relay UE to configure the relay SRB2/DRB. The remote UE transmits RRCReconfigurationComplete through the relay UE in response to the gNB.
In the case of L2 UE-to-Network relay in addition to connection configuration
A PC5 unicast link configuration procedure in terms of PC5-RRC of Rel-16 NR V2X may be reused for the remote UE to establish a secure unicast link between the remote UE and the relay UE for L2 UE-to-network relaying before the remote UE establishes Uu RRC connection with the network through the relay UE.
When the remote UE starts a first RRC message for connection establishment with the gNB for both in-coverage and out-of-coverage, the PC5 L2 configuration for transmission between the remote UE and the UE-to-network relay UE may be based on the RLC/MAC configuration defined in the standard. The establishment of Uu SRB1/SRB2 and DRB of the remote UE complies with a legacy Uu configuration procedure for the L2 UE-to-network relay.
A higher level connection establishment procedure shown in
In operation S1200, the remote and relay UE may perform a discovery procedure and may establish a PC5-RRC connection in operation S1201 based on the existing Rel-16 procedure.
In operation S1202, the remote UE may transmit a first RRC message (i.e. RRCSetupRequest) for establishing a connection with the gNB through the relay UE by using the basic L2 configuration of PC5. The gNB may responds to the remote UE with an RRCSetup message (S1203). Transmission of RRCSetup to the remote UE uses the basic configuration of PC5. When the relay UE is not started in RRC_CONNECTED, the relay UE needs to perform connection establishment thereof upon receiving a message for the basic L2 configuration of the PC5. In this operation, the details for transmission of an RRCSetupRequest/RRCSetup message to the remote UE by the relay UE may be discussed in operation WI.
In operation S1204, the gNB and the relay UE perform a relay channel configuration procedure through the Uu. According to the configuration of the gNB, the relay remote/remote UE configures an RLC channel for relaying the SRB1 to the remote UE through a PC5 network. In this operation, a relay channel for SRB1 is prepared.
In operation S1205, the remote UE SRB1 message (e.g., RRCSetupComplete message) may be transmitted to the gNB through the relay UE by using the SRB1 relay channel through the PC5. The remote UE may be RRC-connected through the Uu.
In operation S1206, the remote UE and the gNB may configure security according to a legacy procedure and transmits the security message through the Relay UE.
In operation S1210, the gNB may configure an additional RLC channel between the gNB and the relay UE for traffic relay. According to the configuration of the gNB, the relay/remote UE may configure an additional RLC channel between the remote UE and the relay UE for traffic relay The gNB transmits RRCReconfiguration to the remote UE through the relay UE to configure the relay SRB2/DRB. The remote UE may transmit RRCReconfigurationComplete as a response to the gNB through the relay UE.
In the case of L2 UE-to-Network relay in addition to the connection establishment
Hereinafter, a handover-related operation method of a sidelink transmission (Tx) UE according to an embodiment will be described.
The TX UE may establish a PC5 connection with a reception (RX) UE (S1301 of
The TX UE may transmit a second sidelink DRX reconfiguration to the RX UE based on completion of the handover procedure, and the second sidelink DRX configuration may be configured by a target BS of the handover procedure. The second sidelink DRX configuration may be included in the handover command.
As described above, the target BS may configure a DRX configuration of the RX UE, that is, the second sidelink DRX configuration after the handover, and thus latency may be reduced up to a new SL DRX configuration after the handover.
For the DRX configuration of the target BS, the TX UE may report SL DRX-related information received from the RX UE to a serving BS, and the serving BS may transmit the information to a target cell. That is, when a UE (e.g., TX UE) performs handover, the UE may report SL DRX-related assistance information (e.g., which may be interpreted as SL DRX-related parameter information preferred by the peer UE (e.g., cycle or offset)) (and/or SL DRX-related parameter information that the peer UE currently uses/applies) (ADD_INFO)) received from a PEER UE (e.g., RX UE) to a serving cell of the UE.
The serving cell may deliver ADD_INFO information (through a backhaul link (e.g., X2 interface)) to the target cell (on which the UE performs a handover). The target cell may determine SL DRX configuration information (PDRX_INFO) of the peer UE (which performs SL communication with the UE) based on ADD_INFO information, and then transmit the same to the serving cell. Then, the serving cell may transmit the PDRX_INFO information to the UE, and the UE may signal the PDRX_INFO information to the peer UE (after completion of the handover procedure).
Here, when the UE reports ADD_INFO information to the serving cell, the UE may signal the information along with ID information of the peer UE (e.g., (L1 or L2) (source and/or destination) ID) (and/or information on a BS on which the peer UE performs (RRC) connection (and/or camps) (e.g., RRC connection state (e.g., RRC_CONNECTED, idle, and inactive) of (physical) CELL ID) and/or peer UE, and/or peer UE-related UU DRX configuration-related information, and/or cast type information related to SL communication (which is performed by peer UE).
The ADD_INFO may be fed back after the UE transmits a request message (RQT_MSG) (related to SL DRX assistance information) (which is predefined) to the peer UE. For example, when the UE performs a handover (and/or when the UE establishes an RRC connection with a BS), the RQT_MSG may be allowed to be transmitted along (limitedly). For example, reporting the ADD_INFO information to the serving cell (and/or (handover) target cell) by the UE may be performed only when the UE receives a request from the (handover) target cell (and/or the serving cell).
When all or some conditions are satisfied, the UE (e.g., TX UE) may be allowed to report ADD_INFO information (which is related to SL DRX configuration (CUR_DRXCFG) that is currently used/applied by the peer UE (e.g., RX UE) and/or used to determine CUR_DRXCFG of the peer UE) (which is pre-received from the peer UE) to the serving cell (and/or the UE may be allowed to report ADD_INFO information fed back after transmitting the RQT_MSG to the peer UE) and/or the UE may be (limitedly) allowed to transmit the RQT_MSG to the peer UE (and/or the UE may be allowed to transmit the RQT_MSG to the peer UE and to receive feedback of ADD_INFO information).
In connection with transmission of the RQT_MSG to the peer UE (e.g., RX UE) by the UE (e.g., TX UE) (for receiving the ADD_INFO information), the prohibit timer (RQT_PHBTIMER) may be configured/defined (and/or in connection with transmission/report of the ADD_INFO information to the UE by the peer UE, the prohibit timer (RPT_PHBTIMER) may be configured/defined). For example, the RQT_PHBTIMER may be interpreted as a parameter for adjusting a frequency/time interval at which the UE at which the UE may request the peer UE to report the ADD_INFO information (and/or the RPT_PHBTIMER may be interpreted as a parameter for adjusting a frequency/time interval at which the peer UE may report the ADD_INFO information (for request of updating SL DRX configuration used/configured by the peer UE) to the UE. For example, the (aforementioned) RQT_PHBTIME value (and/or RPT_PHBTIMER value) may be differently (and/or independently) for each service type/kind (and/or priority and/or QoS parameter/profile and/or (L1 or L2) destination ID (and/or source ID) and/or TX profile and/or whether to enable/disable HARQ feedback and/or logical channel (and/or radio bearer) and/or (SL communication-related) cast type).
For example, when (some or all of) the following conditions are satisfied, even if the RQT_PHBTIMER runs, the UE may exceptionally transmit the RQT_MSG to the peer UE. For example, the peer UE, which receives this, reports the ADD_INFO information to the UE, regardless of the running of the RPT_PHBTIMER (and/or RQT_PHBTIMER).
When the RQT_MSG is received from the UE, the peer UE may be configured to (always) report the ADD_INFO information regardless of running of the RPT_PHBTIMER (e.g., which may be interpreted as if reception of the RQT_MSG overrides running of the RPT_PHBTIMER).
When (some or all of) the following conditions are satisfied, even if the RPT_PHBTIMER runs, the peer UE may be allowed to exceptionally transmit the ADD_INFO information to the UE (for request of updating SL DRX configuration used/configured by the peer UE) to the UE.
When the UE (, TX UE) (and/or peer UE (e.g., RX UE)) (which performs DRX-based SL communication) releases related PC5 RRC CONNECTION, the UE may be configured to report (state) information therefor to a serving cell thereof. For example, when a corresponding rule is applied, the serving cell may efficiently determine the necessity of an alignment operation between UU/SL DRX configurations.
With regard to the above description, an operation method of a target BS may include setting a second sidelink DRX configuration by the target BS, and transmitting a handover command to a transmission (TX) UE that transmits a first sidelink DRX configuration to the RX UE after establishing a PC5 connection with a reception UE by the target BS, and in this case, the second sidelink DRX configuration may be transmitted to the RX UE based on completion of a handover procedure of the TX UE.
In the above description, the second SL DRX configuration may be based on assistance information. In this regard, the TX UE may request the assistance information from the RX UE based on that the measurement report is triggered and may transmit the received assistance information to a target BS. Hereinafter, the DRX-related assistance information will be described. In the following description, the peer UE may be the RX UE. In the following description, the assistance information may be used in the aforementioned embodiment related to
When measurement and reporting are triggered, the TX UE may transmit may transmit a message requesting assistance information to the peer UE (RX UE). The peer UE receiving this may transmit one or more information shown in Table 18 below as assistance information to the TX UE.
Subsequently, the TX UE, which receives assistance information from the peer UE, may raise the information to a network/gNB through SidelinkUEInformationNR or UEAssistanceInformation. Here, the assistance information raised to the network/gNB may be limited to a portion of the information received from the peer UE. For example, the information may also include (periodic) traffic pattern information of preferred SL DRX configuration information of the UE (and/or which is limited to mode2 RRC CONNECTED UE) (e.g., traffic generating pattern/period, slot/timing offset, traffic size, or traffic generating form (e.g., periodic or aperiodic)) (or traffic-related priority information (and/or requirements (e.g., target error rate or (remaining) latency budget)).
When the TX UE transmits a message requesting assistance information and does not receive additional assistance information from the peer UE after a certain time (timer expiration), the TX UE may report information related to SL DRX currently operating (the corresponding information is the same as assistance information raised to the network described above).
When the TX UE receives assistance information from the TX UE and the plurality of peer UEs, the TX UE raises the assistance information together with the layer2 ID of the peer UE at once through (one) SidelinkUEInformationNR or UEAssistanceInformation message.
When the UE moves to another BS/cell due to mobility, a serving BS connected to the UE transmits pre-received SidelinkUEInformationNR or UEAssistanceInformation to a target BS through an inter-node RRC message.
When the serving cell moves from the serving cell to the target cell, (all or a part of) information received from the UE is transmitted to handover PreparationInformation.
Based on the information included in the handover PreparationInformation received from the source BS, the target BS includes the SL DRX configuration currently aligned with the target BS and Uu link in the handover command (RRC reconfiguration) (in detail, MAC-cellGroupConfig or sl-Configdedicated NR) and transmits the same to the TX UE through the source BS. When there is a peer UE performing several SL DRX operations connected to the TX UE, the target BS may transmit an SL DRX pattern to each peer UE through the source BS by including an SL DRX pattern to be assigned to each peer UE. In this case, the destination ID/QOS flow ID of each peer UE may be included and transmitted.
The TX UE receiving the handover command (RRC reconfiguration) may transmit SL DRX configuration of the corresponding content to each peer UE. The information may be a response to assistance information requested by the TX UE to the peer UE. When there are several DRX peer UEs connected to the TX UE, the TX UE may extract and transmit only the necessary contents to the corresponding peer UE according to the destination ID/QoS flow ID of each peer UE. After receiving the handover command, the TX UE may transmit and apply SL configuration to peer UE(s) and communicate with the peer UE or, after completely transmitting a handover (RRC reconfiguration complete) complete message to the garget gNB, the TX may transmit and apply the message to the peer UE and communicate with the peer UE. Alternatively, after receiving the handover command, the TX UE may use the default DRX configuration until completely transmitting the handover (RRC reconfiguration complete) complete message to the target gNB. When the TX UE uses the default DRX configuration for this reason, the TX UE may inform the RX UE of this.
Through the above-described configuration, the peer UE enables the TX UE to continuously receive data while performing power saving (SL DRX operation) by using the SL configuration allocated by a new target BS even after a handover operation.
The RX UE may be configured to follow the following (partial) rule when rejecting the SL DRX configuration (to be used by the RX UE) received (updated) from the TX UE through RRC reconfiguration/PC5 RRC reconfiguration (and/or predefined (physical layer and/or higher layer) signaling).
When the RX UE feeds back that only information related to SL DRX configuration on the RRC reconfiguration is rejected, to the TX UE (e.g., a cause field is included in RRC_reconfiguration_FAILURE_SIDELINK), (even if the remaining information (e.g., DRB update information) on the RRC reconfiguration is in a complete state) an existing timer related to (RRC reconfiguration) (e.g., T400) may be re-started (without being stopped) (e.g., application of the corresponding rule may be interpreted as if a separate timer for an SL DRX reconfiguration procedure/operation is operated) or may complete the SR DRX reconfiguration procedure/operation until the existing timer related to (RRC reconfiguration) expires. For example, when rejection only for SL DRX configuration on RRC reconfiguration is indicted to the RX UE (and/or the TX UE), the previous SL DRX configuration may be continuously applied (e.g., which is limited when the previously applied SL DRX configuration is present) (and/or an SL DRX operation is not applied (e.g., when the previously applied SL DRX configuration is not present)), the remaining information (e.g., DRB update information) on the completed COMPLETE RRC reconfiguration may be (newly) applied to perform SL communication. Here, for example, in this case, the TX UE may reconfigure only the rejected SL DRX configuration through the RRC reconfiguration procedure.
Alternatively, the RX UE may instruct the TX UE to separately (or independently) signal feedback indicating complete (e.g., RRC_reconfiguration_complete_sidelink) (and/or rejection) of the remaining information (e.g., DRB update information) on the RRC reconfiguration and feedback indicating rejection (e.g., RRC_reconfiguration_failure_sidelink) (and/or complete) for the SL DRX configuration on the RRC reconfiguration.
Alternatively, when the RX UE feeds back rejection for the SL DRX configuration to the TX UE, the RX UE may be configured to (always) transmit SL DRX configuration-related assistance information (preferred by the RX UE). For example, when the TX UE receives, as a feedback, rejection of the SL DRX configuration on the RRC reconfiguration from the RX UE, the TX UE may be configured to (always) transmit a request message about SL DRX configuration-related assistance information (preferred by the RX UE).
Alternatively, for example, only when (some or all of) the following conditions are satisfied, the RX UE may allow the TX UE to restrict rejection for the SL DRX configuration on the RRC reconfiguration. In other words, for example, when (some or all of) the following conditions are not satisfied, it may be interpreted that rejection is not capable of being fed back.
For example, when there is change/difference compared with assistance information (related to SL DRX configuration (preferred by the RX UE)) provided by an RX UE used for generating/determining an SL DRX configuration that is RRC-reconfigured
Here, for example, the event may occur when the RX UE is configured with SL DRX information of a related session from another TX UE and/or when the (maximum) alignment between a UU DRX pattern and an SL DRX pattern is performed (by changing an RRC_IDLE (and/or RRC_INACTIVE) state to an RRC_CONNECTED state) (and/or when the (maximum) alignment between the UU DRX pattern and the SL DRX pattern is performed by changing the UU DRX pattern (even if the current state is an RRC_CONNECTED state) and/or when feedback is received from the BS that the (maximum) alignment of the UU DRX is not to be performed on the SL DRX pattern reported by the RX UE, from the BS (and/or when feedback is received from the BS to perform the (maximum) alignment of the SL DRX pattern on the UU DRX pattern).
For example, when the rule is applied, the RX UE may be configured to (always) transmit together the updated ((preferred) SL scheduled DRX configuration-related) assistance information when the RX UE feeds back rejection for the SL DRX configuration on the RRC reconfiguration to the TX UE.
When receiving traffic generation-related information (e.g. periodicity, offset, or size) of the RX UE from the TX UE, the RX UE may be configured to assume/consider the (SL DRX configuration-related and (preferred by the RX UE)) assistance information as an implicit request message to feedback the assistance information.
When the UE transmits a packet/message (e.g., DCR, DCA, or PC5-S) without a QoS profile from an upper/higher layer (e.g., a V2X layer or an application layer) to an AS layer (and/or when a packet/message with a TX profile without an associated service type/kind is transmitted from the upper/higher layer to the AS layer and/or when a field indicating whether to apply a default (broadcast (and/or groupcast) DRX configuration (and/or certain QoS profile-related (broadcast (and/or groupcast)) DRX configuration) onto the TX profile is defined and the upper/higher layer transmits a packet/message with a TX profile with the field of ‘ON’ to the AS layer), the AS layer may (implicitly) apply/assume a preconfigured default (broadcast (and/or groupcast)) DRX configuration and (and/or (broadcast (and/or groupcast) preconfigured QoS profile (associated with this type/kind of packet/message)) DRX configuration and perform SL transmission (and/or reception).
The proposal of the present disclosure may be extensively applied to not only a parameter (and a timer) included in a default/common sidelink DRX configuration, default/common sidelink DRX pattern, or a default/common sidelink DRX configuration but also a parameter (and timer) included in a UE-pair specific sidelink DRX configuration, a UE-pair specific sidelink DRX pattern, or a UE-pair specific sidelink DRX configuration. The onduration term mentioned in the proposal of the present disclosure may be expanded and interpreted as an active up state (rf module is “on”) to receive/transmit a wireless signal), and the offduration term may be extensively interpreted as a sleep Time (which may not mean that the TX UE needs to operate in a section of operating in a sleep mode state (RF module is “Off”) for power saving and needs to obligatory operate in a sleep mode in a sleep time. If necessary, even in the sleep time, the TX UE is allowed to operate in the active time for a while for the sensing operation/transmission operation). “Whether the (partial) proposed method/rule is applied and/or a related parameter (e.g., threshold) may also be specifically configured (differently or independently) according to a resource pool, a congestion level, a service priority (and/or type), QoS requirement (e.g., latency or reliability) or PQI, a traffic type (e.g., (a) periodic generation, sidelink transmission resource allocation mode (mode 1, mode 2), or the like.
For example, whether the proposed rule according to the present disclosure is applied (and/or a related parameter value) may also be configured specifically (and/or independently, and/or differently) for at least one of a resource pool, a service/packet type (and/or a priority), a QoS requirement (e.g., URLLC/EMBB traffic, reliability, latency), PQI, cast type (e.g., unicast, groupcast, and broadcast), a (resource pool) congestion level (e.g., CBR), a SL HARQ feedback method (e.g., NACK only feedback and ACK/NACK feedback), the case in which a HARQ feedback enabled MAC PDU (and/or HARQ feedback disabled MAC PDU) is transmitted, whether to configure a PUCCH-based SL HARQ feedback reporting operation, the case in which pre-emption (and/or re-evaluation) is performed (or a resource is reselected based thereon), (L2 or L1) (source and/or destination) identifier, (L2 or L1) (combination of source layer ID and destination layer ID) identifier, (L2 or L1) (combination of a pair of source layer ID and destination layer ID and cast type) identifier, PC5 RRC Connection/Link, the case in which SL DRX is performed, SL mode type (resource allocation mode 1 and resource allocation mode 2), and the case in which (a) periodic resource reservation is performed.
The term “predetermined time” mentioned in the proposal of the present disclosure is a time period for which a UE operates by a predefined time as an active time to receive a sidelink signal or sidelink data from a counterpart UE or a time period for which the UE operates as much as a time of a specific timer (a timer for ensuring that the UE is capable of operating as an Active Time in a DRX operation of a sidelink DRX Retransmission Timer or a sidelink DRX Inactivity Timer or RX UE) as an active time.
The proposal and proposed rule according to the present disclosure (and/or related parameter setting value) may also be applied to a mmWave sidelink operation.
In the above description, the “Tx UE” may be interpreted as a UE performing data transmission (e.g., PSCCH/PSSCH) (to a (target) Rx UE), a UE performing transmission of SL CSI-RS (and/or SL CSI reporting request indicator) (to a (target) RX UE), a UE performing transmission of a (predefined) RS (e.g., PSSCH DM-RS) (and/or SL (L1) RSRP reporting request indicator) to be used to measure SL (L1) RSRP (to a (target) RX UE), and/or a UE transmitting an RS (e.g., DM-RS or CSI-RS) on a (control) channel (e.g., PSCCH, PSSCH) and/or (on the corresponding (control) channel) to be used in a SL radio link monitoring (RLM) (and/or SL radio link failure (RLF)) operation (of the (target) RX UE).
In the above description, the “Rx UE” may be interpreted as a UE transmitting SL HARQ feedback (to the Tx UE) according to whether decoding of data received from the Tx UE is successful (and/or whether detecting/decoding of the PSCCH (related to PSSCH scheduling) transmitted by the Tx UE is successful), a UE performing transmission of SL CSI to (to the TX UE) based on the SL CSI-RS (and/or SL CSI reporting request indicator) from the TX UE, a UE transmitting an SL (L1) RSRP measurement value (to the TX UE) based on an (predefined) RS received from the TX UE (and/or SL (L1) RSRP reporting request indicator), a UE transmitting data thereof (to the TX UE), and/or a UE performing an RLM (and/or RLF) operation based on a (preconfigured) (control) channel received from the TX UE and/or an RS (on the corresponding (control) channel).
When the RX UE transmits SL HARQ feedback information for the PSSCH (and/or PSCCH) received from the TX UE, all/some methods below may be considered. This method may be limitedly applied only when the RX UE successfully decodes/detects the PSCCH for scheduling the PSSCH.
OPTION 1) NACK information is transmitted only when decoding/reception of the PSSCH fails.
OPTION 2) ACK information is transmitted when decoding/reception of the PSSCH is successful, and NACK information is transmitted when decoding/reception of the PSSCH fails.
This may be interpreted that one or more pieces of information are transmitted through sidelink control information (SCI). One or more pieces of information below may be transmitted through first SCI (and/or second SCI).
In the above description, “PSCCH” may be interpreted as SCI (and/or first SCI (or second SCI) and/or PSSCH) (and/or the “SCI” may be interpreted as the PSCCH (and/or first SCI (or second SCI) and/or the PSSCH) and/or the “PSSCH” may be interpreted as the second SCI (and/or the PSCCH)). Here, the “first SCI” and the “second SCI” refer to each of two groups to which SCI configuration fields are separated in consideration of a (relatively) high SCI payload size, and the first SCI and the second SCI may be transmitted through different channels (e.g., the first SCI is transmitted through the PSCCH and the second SCI is piggybacked on the PSSCH and transmitted with data (or through the (independent) PSCCH)).
In the above description, the “configuration (or definition)” may be interpreted as (pre-) configuration (resource pool specifically) (through predefined signaling (e.g., SIB, MAC, or RRC)) from a BS (or network) (or designation through signaling (e.g. PC5 RRC) predefined between UEs. The “RLF” may be interpreted as at least one of out-of-synch (OOS) and in-synch (IS). The “RB” may be interpreted as a subcarrier. In the above, the “packet (or traffic)” may be interpreted as a transport block (TB) (or MAC PDU). In the above the “codeblock group (CGB)” may be interpreted as a TB. In the above, the “source ID” may be interpreted as a “destination ID”. In the above, the “L1 ID” may be interpreted as an “L2 ID”. In the above, the “retransmission resource reservation/selection” may be interpreted as reservation/selection of a potential retransmission resource of which actual use is determined based on SL HARQ feedback information. In the above, the “sub-selection window” may be interpreted as a selection window (and/or a preset number of resource sets within a selection window). In the above, the “SL mode 1 operation” may refer to the case in which a BS directly schedules an SL TX resource of a UE through predefined signaling (e.g., DCI), and the “SL mode 2 operation” may refer to the case in which the UE independently selects an SL TX resource within a preset resource pool (from a BS or a network). The “dynamic grant” may be interpreted as “configured (or SPS) grant” (or a combination of configured (or SPS) grant and dynamic grant). In the above, the “configured grant” may be interpreted as “TYPE 1 configured grant” (or “TYPE 2 configured grant”). In the above, the “channel” may be interpreted as a “signal”. In the above, the “cast (type)” may be interpreted as “unicast (and/or groupcast and/or broadcast)”. In the above, the “resource” may be interpreted as a “slot” (or “symbol”). In the above, the “priority” may be interpreted as “LCP” (and/or “latency” and/or “reliability” and/or “minimum required communication range” and/or “PPPP” and/or “priority” and/or “SLRB” and/or “QoS profile/parameter” and/or “requirement”).
In the above, a (physical) channel used when the RX UE transmits at least one of SL HARQ feedback, SL CSI, and SL (L1) RSRP to the TX UE may be referred to as a “physical sidelink feedback channel (PSFCH)”.
When SL communication is performed, a resource reservation operation may include two representative methods.
This may be interpreted as the form of informing location information of a transmission resource less than K on any (or specific) transmission point of SCI when K transmission resources (related to a specific TB) are reserved. Signaling of only the location information of less than K transmission resources on one SCI (at any (or specific) view) may be for preventing performance degradation due to an excessive increase in SCI payload. As an example,
This may be interpreted as the form of informing information on K transmission-related resource locations on SCI at any (or specific) transmission time point when K transmission resources (related to a specific TB) is reserved.
Whether the rule is applied (and/or a parameter value related to the proposed method/rule according to the present disclosure) may be configured/allowed specifically (or differently or independently) for at least one of the following elements/parameters.
In addition, the “configuration” (“designation” or “definition”) may be interpreted as the form provided by a BS to a UE through a predefined (physical layer or higher layer) channel/signal (e.g. SIB, RRC, or MAC CE) (and/or the form provided through PRE-configuration and/or the form of informing information of other UEs through predefined (physical layer or higher layer) channel/signal (e.g., SL MAC CE, or PC5 RRC) by the UE. The “PSFCH” may be interpreted as “(NR or LTE) PSSCH (and/or (NR or LTE) PSCCH) (and/or (NR or LTE) SL SSB (and/or UL channel signal))”. The proposed methods according to the present disclosure may be combined with each other and may be extensively applied (using a method in a new form).
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
The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. V2V/V2X communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
Wireless communication/connections 150a, 150b, or 150c may be established between the wireless devices 100a to 100f/BS 200, or BS 200/BS 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as UL/DL communication 150a, sidelink communication 150b (or, D2D communication), or inter BS communication (e.g. relay, integrated access backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150a and 150b. For example, the wireless communication/connections 150a and 150b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.
Referring to
The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.
The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.
Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.
The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.
The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.
The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas 108 and 208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.
Referring to
The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle 100. The control unit 120 may include an ECU. The driving unit 140a may cause the vehicle or the autonomous driving vehicle 100 to drive on a road. The driving unit 140a may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit 140b may supply power to the vehicle or the autonomous driving vehicle 100 and include a wired/wireless charging circuit, a battery, etc. The sensor unit 140c may acquire a vehicle state, ambient environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like.
For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the driving unit 140a such that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140c may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit 110 may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles.
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 or BSs. The control unit 120 may perform various operations by controlling constituent elements of the vehicle 100. The memory unit 130 may store data/parameters/programs/code/commands for supporting various functions of the vehicle 100. The I/O unit 140a may output an AR/VR object based on information within the memory unit 130. The I/O unit 140a may include an HUD. The positioning unit 140b may acquire information about the position of the vehicle 100. The position information may include information about an absolute position of the vehicle 100, information about the position of the vehicle 100 within a traveling lane, acceleration information, and information about the position of the vehicle 100 from a neighboring vehicle. The positioning unit 140b may include a GPS and various sensors.
As an example, the communication unit 110 of the vehicle 100 may receive map information and traffic information from an external server and store the received information in the memory unit 130. The positioning unit 140b may obtain the vehicle position information through the GPS and various sensors and store the obtained information in the memory unit 130. The control unit 120 may generate a virtual object based on the map information, traffic information, and vehicle position information and the I/O unit 140a may display the generated virtual object in a window in the vehicle (1410 and 1420). The control unit 120 may determine whether the vehicle 100 normally drives within a traveling lane, based on the vehicle position information. If the vehicle 100 abnormally exits from the traveling lane, the control unit 120 may display a warning on the window in the vehicle through the I/O unit 140a. In addition, the control unit 120 may broadcast a warning message regarding driving abnormity to neighboring vehicles through the communication unit 110. According to situation, the control unit 120 may transmit the vehicle position information and the information about driving/vehicle abnormality to related organizations.
Referring to
The communication unit 110 may transmit and receive signals (e.g., media data and control signals) to and from external devices such as other wireless devices, hand-held devices, or media servers. The media data may include video, images, and sound. The control unit 120 may perform various operations by controlling constituent elements of the XR device 100a. For example, the control unit 120 may be configured to control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata generation and processing. The memory unit 130 may store data/parameters/programs/code/commands needed to drive the XR device 100a/generate XR object. The I/O unit 140a may obtain control information and data from the exterior and output the generated XR object. The I/O unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit 140b may obtain an XR device state, surrounding environment information, user information, etc. The sensor unit 140b may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone and/or a radar. The power supply unit 140c may supply power to the XR device 100a and include a wired/wireless charging circuit, a battery, etc.
For example, the memory unit 130 of the XR device 100a may include information (e.g., data) needed to generate the XR object (e.g., an AR/VR/MR object). The I/O unit 140a may receive a command for manipulating the XR device 100a from a user and the control unit 120 may drive the XR device 100a according to a driving command of a user. For example, when a user desires to watch a film or news through the XR device 100a, the control unit 120 transmits content request information to another device (e.g., a hand-held device 100b) or a media server through the communication unit 130. The communication unit 130 may download/stream content such as films or news from another device (e.g., the hand-held device 100b) or the media server to the memory unit 130. The control unit 120 may control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata generation/processing with respect to the content and generate/output the XR object based on information about a surrounding space or a real object obtained through the I/O unit 140a/sensor unit 140b.
The XR device 100a may be wirelessly connected to the hand-held device 100b through the communication unit 110 and the operation of the XR device 100a may be controlled by the hand-held device 100b. For example, the hand-held device 100b may operate as a controller of the XR device 100a. To this end, the XR device 100a may obtain information about a 3D position of the hand-held device 100b and generate and output an XR object corresponding to the hand-held device 100b.
Referring to
The communication unit 110 may transmit and receive signals (e.g., driving information and control signals) to and from external devices such as other wireless devices, other robots, or control servers. The control unit 120 may perform various operations by controlling constituent elements of the robot 100. The memory unit 130 may store data/parameters/programs/code/commands for supporting various functions of the robot 100. The I/O unit 140a may obtain information from the exterior of the robot 100 and output information to the exterior of the robot 100. The I/O unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit 140b may obtain internal information of the robot 100, surrounding environment information, user information, etc. The sensor unit 140b may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, a radar, etc. The driving unit 140c may perform various physical operations such as movement of robot joints. In addition, the driving unit 140c may cause the robot 100 to travel on the road or to fly. The driving unit 140c may include an actuator, a motor, a wheel, a brake, a propeller, etc. Example of AI device to which the present disclosure is applied.
Referring to
The communication unit 110 may transmit and receive wired/radio signals (e.g., sensor information, user input, learning models, or control signals) to and from external devices such as other AI devices (e.g., 100x, 200, or 400 of
The control unit 120 may determine at least one feasible operation of the AI device 100, based on information which is determined or generated using a data analysis algorithm or a machine learning algorithm. The control unit 120 may perform an operation determined by controlling constituent elements of the AI device 100. For example, the control unit 120 may request, search, receive, or use data of the learning processor unit 140c or the memory unit 130 and control the constituent elements of the AI device 100 to perform a predicted operation or an operation determined to be preferred among at least one feasible operation. The control unit 120 may collect history information including the operation contents of the AI device 100 and operation feedback by a user and store the collected information in the memory unit 130 or the learning processor unit 140c or transmit the collected information to an external device such as an AI server (400 of
The memory unit 130 may store data for supporting various functions of the AI device 100. For example, the memory unit 130 may store data obtained from the input unit 140a, data obtained from the communication unit 110, output data of the learning processor unit 140c, and data obtained from the sensor unit 140. The memory unit 130 may store control information and/or software code needed to operate/drive the control unit 120.
The input unit 140a may acquire various types of data from the exterior of the AI device 100. For example, the input unit 140a may acquire learning data for model learning, and input data to which the learning model is to be applied. The input unit 140a may include a camera, a microphone, and/or a user input unit. The output unit 140b may generate output related to a visual, auditory, or tactile sense. The output unit 140b may include a display unit, a speaker, and/or a haptic module. The sensing unit 140 may obtain at least one of internal information of the AI device 100, surrounding environment information of the AI device 100, and user information, using various sensors. The sensor unit 140 may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, and/or a radar.
The learning processor unit 140c may learn a model consisting of artificial neural networks, using learning data. The learning processor unit 140c may perform AI processing together with the learning processor unit of the AI server (400 of
The above-described embodiments of the present disclosure are applicable to various mobile communication systems.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0126718 | Sep 2021 | KR | national |
| 10-2021-0130086 | Sep 2021 | KR | national |
| 10-2021-0133300 | Oct 2021 | KR | national |
This application is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2022/014360, filed on Sep. 26, 2022, which claims the benefit of earlier filing date and right of priority to Korean Application Nos. 10-2021-0126718, filed on Sep. 24, 2021, 10-2021-0130086, filed on Sep. 30, 2021, and 10-2021-0133300, filed on Oct. 7, 2021, the contents of which are all incorporated by reference herein in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2022/014360 | 9/26/2022 | WO |
