Patent Application
20210314925
The present disclosure relates to a method for transmitting uplink data by using a preconfigured uplink resource in a wireless communication system supporting a narrowband Internet of things system, and a device therefor.
Mobile communication systems have been developed to provide voice services, while ensuring activity of users. However, coverage of the mobile communication systems has been extended up to data services, as well as voice service, and currently, an explosive increase in traffic has caused shortage of resources, and since users expect relatively high speed services, an advanced mobile communication system is required.
Requirements of a next-generation mobile communication system include accommodation of explosive data traffic, a significant increase in a transfer rate per user, accommodation of considerably increased number of connection devices, very low end-to-end latency, and high energy efficiency. To this end, there have been researched various technologies such as dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband, device networking, and the like.
An embodiment of the present disclosure provides a method which may perform transmission of uplink data by considering a collision with a specific operation of a UE which is in an RRC idle state when the uplink data is transmitted by using a preconfigured UL resource (PUR) in a wireless communication system supporting a narrowband Internet of things, and a device therefor.
Furthermore, an embodiment of the present disclosure also provides a configuration of a search space related to the PUR.
Furthermore, an embodiment of the present disclosure also provides dynamically performing retransmission of the uplink data in the PUR.
The technical objects of the present disclosure are not limited to the aforementioned technical objects, and other technical objects, which are not mentioned above, will be apparently appreciated by a person having ordinary skill in the art from the following description.
According to an embodiment of the present disclosure, a method for transmitting, by a user equipment (UE), uplink data by using a preconfigured uplink (UL) resource (PUR) in a wireless communication system supporting a narrowband Internet of things (NB-IoT) system includes: receiving information related to the PUR for transmitting the uplink data in an RRC connected state; and transmitting the uplink data by using the PUR in an RRC idle state. The information related to the PUR includes information indicating a specific carrier for monitoring a first search space related to the PUR, and when the first search space overlaps with a second search space in which downlink control information (DCI) related to a specific operation is transmitted, the second search space has a priority.
In the transmitting of the uplink data, a Narrowband Physical Downlink Control Channel (NPDCCH) is received by monitoring the first search space in the specific carrier, and the specific carrier is an anchor carrier or a non-anchor carrier.
When the first search space is a legacy search space, the specific carrier is a carrier for monitoring the legacy search space.
When the first search space is a new search space other than the legacy search space, the specific carrier is the anchor carrier.
The Narrowband Physical Downlink Control Channel (NPDCCH) includes information related to retransmission of the uplink data.
When the first search space and the second search space overlap with each other in at least one domain of a time or a frequency, the first search space is not monitored in the overlapping domain.
The specific operation is an operation related to at least one of a paging process or a random access (RACH) process, and downlink control information (DCI) related to the specific operation is received by monitoring the second search space in the overlapping domain.
The second search space is a Common Search Space (CSS).
The Common Search Space (CSS) is a type-1 CSS or a type-2 CSS.
The downlink control information (DCI) related to the specific operation includes information for scheduling a paging narrowband physical downlink shared channel (NPDSCH).
The downlink control information (DCI) related to the specific operation includes information for scheduling a narrowband physical downlink shared channel (NPDSCH) through which a random access response (RAR) grant is transmitted.
The PUR is a dedicated resource.
According to another embodiment of the present disclosure, a user equipment (UE) for transmitting uplink data by using a preconfigured uplink (UL) resource (PUR) in a wireless communication system supporting a narrowband Internet of things (NB-IoT) system includes: a transceiver transceiving a radio signal; a memory; and a processor connected to the transceiver and the memory. The processor is configured to: receive information related to the PUR for transmitting the uplink data in an RRC connected state, and transmit the uplink data by using the PUR in an RRC idle state. The information related to the PUR includes information indicating a specific carrier for monitoring a first search space related to the PUR, and when the first search space overlaps with a second search space in which downlink control information (DCI) related to a specific operation is transmitted, the second search space has a priority.
The processor is configured to receive a Narrowband Physical Downlink Control Channel (NPDCCH) by monitoring the first search space in the specific carrier, and the specific carrier is an anchor carrier or a non-anchor carrier.
According to yet another embodiment of the present disclosure, a device for transmitting uplink data by using a preconfigured uplink (UL) resource (PUR) in a wireless communication system supporting a narrowband Internet of things (NB-IoT) system, includes: a memory; and a processor connected to the memory. The processor is configured to: receive information related to the PUR in an RRC connected state, and transmit the uplink data by using the PUR in an RRC idle state. The information related to the PUR includes information indicating a specific carrier for monitoring a first search space related to the PUR, and when the first search space overlaps with a second search space in which downlink control information (DCI) related to a specific operation is transmitted, the second search space has a priority.
In the present disclosure, information related to a preconfigured UL resource (PUR) is transmitted through radio resource control (RRC) signaling, and when a first search space related to the PUR and a second search space in which downlink control information (DCI) related to a specific operation is transmitted overlap with each other, the second search space has a priority. Accordingly, the present disclosure can lower complexity of a UE and reduce power consumption, and minimize an influence of the overlapping of the first search space and the second search space on a system.
Furthermore, in the present disclosure a carrier for monitoring the corresponding search space is configured differently according to whether to utilize a conventional search space as the first search space related to the PUR. Accordingly, the present disclosure can remove ambiguity caused by introduction of a new search space for the PUR.
Furthermore, in the present disclosure, a narrowband physical downlink control channel (NPDCCH) received by monitoring the first search space related to the PUR includes information related to retransmission of the uplink data. Since the retransmission of the uplink data can be dynamically scheduled, the present disclosure can provide flexibility to a base station operation.
Effects obtainable in the present disclosure are not limited to the aforementioned effects and other unmentioned effects will be clearly understood by those skilled in the art from the following description.
Reference will now be made in detail to embodiments of the disclosure, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. In general, a suffix such as “module” and “unit” may be used to refer to elements or components. Use of such a suffix herein is merely intended to facilitate description of the disclosure, and the suffix itself is not intended to give any special meaning or function. It will be noted that a detailed description of known arts will be omitted if it is determined that the detailed description of the known arts can obscure the embodiments of the disclosure. The accompanying drawings are used to help easily understand various technical features and it should be understood that embodiments presented herein are not limited by the accompanying drawings. As such, the disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings.
In the present disclosure, a base station means a terminal node of a network directly performing communication with a terminal. In the present document, specific operations described to be performed by the base station may be performed by an upper node of the base station in some cases. That is, it is apparent that in the network constituted by multiple network nodes including the base station, various operations performed for communication with the terminal may be performed by the base station or other network nodes other than the base station. A base station (BS) may be generally substituted with terms such as a fixed station, Node B, evolved-NodeB (eNB), a base transceiver system (BTS), an access point (AP), and the like. Further, a ‘terminal’ may be fixed or movable and be substituted with terms such as user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), a wireless terminal (WT), a Machine-Type Communication (MTC) device, a Machine-to-Machine (M2M) device, a Device-to-Device (D2D) device, and the like.
Hereinafter, a downlink means communication from the base station to the terminal and an uplink means communication from the terminal to the base station. In the downlink, a transmitter may be a part of the base station and a receiver may be a part of the terminal. In the uplink, the transmitter may be a part of the terminal and the receiver may be a part of the base station.
Specific terms used in the following description are provided to help appreciating the disclosure and the use of the specific terms may be modified into other forms within the scope without departing from the technical spirit of the disclosure.
The following technology 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-FDMA (SC-FDMA), non-orthogonal multiple access (NOMA), and the like. The CDMA may be implemented by radio technology universal terrestrial radio access (UTRA) or CDMA2000. The TDMA may be implemented by radio technology such as Global System for Mobile communications (GSM)/General Packet Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE). The OFDMA may be implemented as radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), and the like. The UTRA is a part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) as a part of an evolved UMTS (E-UMTS) using evolved-UMTS terrestrial radio access (E-UTRA) adopts the OFDMA in a downlink and the SC-FDMA in an uplink. LTE-advanced (A) is an evolution of the 3GPP LTE.
The embodiments of the disclosure may be based on standard documents disclosed in at least one of IEEE 802, 3GPP, and 3GPP2 which are the wireless access systems. That is, steps or parts which are not described to definitely show the technical spirit of the disclosure among the embodiments of the disclosure may be based on the documents. Further, all terms disclosed in the document may be described by the standard document.
3GPP LTE/LTE-A/NR is primarily described for clear description, but technical features of the disclosure are not limited thereto.
Three major requirement areas of 5G include (1) an enhanced mobile broadband (eMBB) area, (2) a massive machine type communication (mMTC) area and (3) an ultra-reliable and low latency communications (URLLC) area.
Some use cases may require multiple areas for optimization, and other use case may be focused on only one key performance indicator (KPI). 5G support such various use cases in a flexible and reliable manner.
eMBB is far above basic mobile Internet access and covers media and entertainment applications in abundant bidirectional tasks, cloud or augmented reality. Data is one of key motive powers of 5G, and dedicated voice services may not be first seen in the 5G era. In 5G, it is expected that voice will be processed as an application program using a data connection simply provided by a communication system. Major causes for an increased traffic volume include an increase in the content size and an increase in the number of applications that require a high data transfer rate. Streaming service (audio and video), dialogue type video and mobile Internet connections will be used more widely as more devices are connected to the Internet. Such many application programs require connectivity always turned on in order to push real-time information and notification to a user. A cloud storage and application suddenly increases in the mobile communication platform, and this may be applied to both business and entertainment. Furthermore, cloud storage is a special use case that tows the growth of an uplink data transfer rate. 5G is also used for remote business of cloud. When a tactile interface is used, further lower end-to-end latency is required to maintain excellent user experiences. Entertainment, for example, cloud game and video streaming are other key elements which increase a need for the mobile broadband ability. Entertainment is essential in the smartphone and tablet anywhere including high mobility environments, such as a train, a vehicle and an airplane. Another use case is augmented reality and information search for entertainment. In this case, augmented reality requires very low latency and an instant amount of data.
Furthermore, one of the most expected 5G use case relates to a function capable of smoothly connecting embedded sensors in all fields, that is, mMTC. Until 2020, it is expected that potential IoT devices will reach 20.4 billions. The industry IoT is one of areas in which 5G performs major roles enabling smart city, asset tracking, smart utility, agriculture and security infra.
URLLC includes a new service which will change the industry through remote control of major infra and a link having ultra-reliability/low available latency, such as a self-driving vehicle. A level of reliability and latency is essential for smart grid control, industry automation, robot engineering, drone control and adjustment.
Multiple use cases are described more specifically.
5G may supplement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as means for providing a stream evaluated from gigabits per second to several hundreds of mega bits per second. Such fast speed is necessary to deliver TV with resolution of 4K or more (6K, 8K or more) in addition to virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include immersive sports games. A specific application program may require a special network configuration. For example, in the case of VR game, in order for game companies to minimize latency, a core server may need to be integrated with the edge network server of a network operator.
An automotive is expected to be an important and new motive power in 5G, along with many use cases for the mobile communication of an automotive. For example, entertainment for a passenger requires a high capacity and a high mobility mobile broadband at the same time. The reason for this is that future users continue to expect a high-quality connection regardless of their location and speed. Another use example of the automotive field is an augmented reality dashboard. The augmented reality dashboard overlaps and displays information, identifying an object in the dark and notifying a driver of the distance and movement of the object, over a thing seen by the driver through a front window. In the future, a wireless module enables communication between automotives, information exchange between an automotive and a supported infrastructure, and information exchange between an automotive and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver can drive more safely, thereby reducing a danger of an accident. A next step will be a remotely controlled or self-driven vehicle. This requires very reliable, very fast communication between different self-driven vehicles and between an automotive and infra. In the future, a self-driven vehicle may perform all driving activities, and a driver will be focused on things other than traffic, which cannot be identified by an automotive itself. Technical requirements of a self-driven vehicle require ultra-low latency and ultra-high speed reliability so that traffic safety is increased up to a level which cannot be achieved by a person.
A smart city and smart home mentioned as a smart society will be embedded as a high-density radio sensor network. The distributed network of intelligent sensors will identify the cost of a city or home and a condition for energy-efficient maintenance. A similar configuration may be performed for each home. All of a temperature sensor, a window and heating controller, a burglar alarm and home appliances are wirelessly connected. Many of such sensors are typically a low data transfer rate, low energy and a low cost. However, for example, real-time HD video may be required for a specific type of device for surveillance.
The consumption and distribution of energy including heat or gas are highly distributed and thus require automated control of a distributed sensor network. A smart grid collects information, and interconnects such sensors using digital information and a communication technology so that the sensors operate based on the information. The information may include the behaviors of a supplier and consumer, and thus the smart grid may improve the distribution of fuel, such as electricity, in an efficient, reliable, economical, production-sustainable and automated manner. The smart grid may be considered to be another sensor network having small latency.
A health part owns many application programs which reap the benefits of mobile communication. A communication system can support remote treatment providing clinical treatment at a distant place. This helps to reduce a barrier for the distance and can improve access to medical services which are not continuously used at remote farming areas. Furthermore, this is used to save life in important treatment and an emergency condition. A radio sensor network based on mobile communication can provide remote monitoring and sensors for parameters, such as the heart rate and blood pressure.
Radio and mobile communication becomes increasingly important in the industry application field. Wiring requires a high installation and maintenance cost. Accordingly, the possibility that a cable will be replaced with reconfigurable radio links is an attractive opportunity in many industrial fields. However, to achieve the possibility requires that a radio connection operates with latency, reliability and capacity similar to those of the cable and that management is simplified. Low latency and a low error probability is a new requirement for a connection to 5G.
Logistics and freight tracking is an important use case for mobile communication, which enables the tracking inventory and packages anywhere using a location-based information system. The logistics and freight tracking use case typically requires a low data speed, but a wide area and reliable location information.
The disclosure described below can be implemented by combining or modifying respective embodiments to meet the above-described requirements of 5G.
The following describes in detail technical fields to which the disclosure described below is applicable.
Artificial Intelligence (AI)
Artificial intelligence means the field in which artificial intelligence or methodology capable of producing artificial intelligence is researched. Machine learning means the field in which various problems handled in the artificial intelligence field are defined and methodology for solving the problems are researched. Machine learning is also defined as an algorithm for improving performance of a task through continuous experiences for the task.
An artificial neural network (ANN) is a model used in machine learning, and is configured with artificial neurons (nodes) forming a network through a combination of synapses, and may mean the entire model having a problem-solving ability. The artificial neural network may be defined by a connection pattern between the neurons of different layers, a learning process of updating a model parameter, and an activation function for generating an output value.
The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons. The artificial neural network may include a synapse connecting neurons. In the artificial neural network, each neuron may output a function value of an activation function for input signals, weight, and a bias input through a synapse.
A model parameter means a parameter determined through learning, and includes the weight of a synapse connection and the bias of a neuron. Furthermore, a hyper parameter means a parameter that needs to be configured prior to learning in the machine learning algorithm, and includes a learning rate, the number of times of repetitions, a mini-deployment size, and an initialization function.
An object of learning of the artificial neural network may be considered to determine a model parameter that minimizes a loss function. The loss function may be used as an index for determining an optimal model parameter in the learning process of an artificial neural network.
Machine learning may be classified into supervised learning, unsupervised learning, and reinforcement learning based on a learning method.
Supervised learning means a method of training an artificial neural network in the state in which a label for learning data has been given. The label may mean an answer (or a result value) that must be deduced by an artificial neural network when learning data is input to the artificial neural network. Unsupervised learning may mean a method of training an artificial neural network in the state in which a label for learning data has not been given. Reinforcement learning may mean a learning method in which an agent defined within an environment is trained to select a behavior or behavior sequence that maximizes accumulated compensation in each state.
Machine learning implemented as a deep neural network (DNN) including a plurality of hidden layers, among artificial neural networks, is also called deep learning. Deep learning is part of machine learning. Hereinafter, machine learning is used as a meaning including deep learning.
Robot
A robot may mean a machine that automatically processes a given task or operates based on an autonomously owned ability. Particularly, a robot having a function for recognizing an environment and autonomously determining and performing an operation may be called an intelligence type robot.
A robot may be classified for industry, medical treatment, home, and military based on its use purpose or field.
A robot includes a driving unit including an actuator or motor, and may perform various physical operations, such as moving a robot joint. Furthermore, a movable robot includes a wheel, a brake, a propeller, etc. in a driving unit, and may run on the ground or fly in the air through the driving unit.
Self-Driving (Autonomous-Driving)
Self-driving means a technology for autonomous driving. A self-driving vehicle means a vehicle that runs without a user manipulation or by a user's minimum manipulation.
For example, self-driving may include all of a technology for maintaining a driving lane, a technology for automatically controlling speed, such as adaptive cruise control, a technology for automatic driving along a predetermined path, a technology for automatically configuring a path when a destination is set and driving.
A vehicle includes all of a vehicle having only an internal combustion engine, a hybrid vehicle including both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include a train, a motorcycle, etc. in addition to the vehicles.
In this case, the self-driving vehicle may be considered to be a robot having a self-driving function.
Extended Reality (XR)
Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). The VR technology provides an object or background of the real world as a CG image only. The AR technology provides a virtually produced CG image on an actual thing image. The MR technology is a computer graphics technology for mixing and combining virtual objects with the real world and providing them.
The MR technology is similar to the AR technology in that it shows a real object and a virtual object. However, in the AR technology, a virtual object is used in a form to supplement a real object. In contrast, unlike in the AR technology, in the MR technology, a virtual object and a real object are used as the same character.
The XR technology may be applied to a head-mount display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop, a desktop, TV, and a digital signage. A device to which the XR technology has been applied may be called an XR device.
The AI device 100 may be implemented as a fixed device or mobile device, such as TV, a projector, a mobile phone, a smartphone, a desktop computer, a notebook, a terminal for digital broadcasting, a personal digital assistants (PDA), a portable multimedia player (PMP), a navigator, a tablet PC, a wearable device, a set-top box (STB), a DMB receiver, a radio, a washing machine, a refrigerator, a desktop computer, a digital signage, a robot, and a vehicle.
Referring to
The communication unit 110 may transmit and receive data to and from external devices, such as other AI devices 100a to 100er or an AI server 200, using wired and wireless communication technologies. For example, the communication unit 110 may transmit and receive sensor information, a user input, a learning model, and a control signal to and from external devices.
In this case, communication technologies used by the communication unit 110 include a global system for mobile communication (GSM), code division multi access (CDMA), long term evolution (LTE), 5G, a wireless LAN (WLAN), wireless-fidelity (Wi-Fi), Bluetooth™ radio frequency identification (RFID), infrared data association (IrDA), ZigBee, near field communication (NFC), etc.
The input unit 120 may obtain various types of data.
In this case, the input unit 120 may include a camera for an image signal input, a microphone for receiving an audio signal, a user input unit for receiving information from a user, etc. In this case, the camera or the microphone is treated as a sensor, and a signal obtained from the camera or the microphone may be called sensing data or sensor information.
The input unit 120 may obtain learning data for model learning and input data to be used when an output is obtained using a learning model. The input unit 120 may obtain not-processed input data. In this case, the processor 180 or the learning processor 130 may extract an input feature by performing pre-processing on the input data.
The learning processor 130 may be trained by a model configured with an artificial neural network using learning data. In this case, the trained artificial neural network may be called a learning model. The learning model is used to deduce a result value of new input data not learning data. The deduced value may be used as a base for performing a given operation.
In this case, the learning processor 130 may perform AI processing along with the learning processor 240 of the AI server 200.
In this case, the learning processor 130 may include memory integrated or implemented in the AI device 100. Alternatively, the learning processor 130 may be implemented using the memory 170, external memory directly coupled to the AI device 100 or memory maintained in an external device.
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, or user information using various sensors.
In this case, sensors included in the sensing unit 140 include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertia sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a photo sensor, a microphone, LIDAR, and a radar.
The output unit 150 may generate an output related to a visual sense, an auditory sense or a tactile sense.
In this case, the output unit 150 may include a display unit for outputting visual information, a speaker for outputting auditory information, and a haptic module for outputting tactile information.
The memory 170 may store data supporting various functions of the AI device 100. For example, the memory 170 may store input data obtained by the input unit 120, learning data, a learning model, a learning history, etc.
The processor 180 may determine at least one executable operation of the AI device 100 based on information, determined or generated using a data analysis algorithm or a machine learning algorithm. Furthermore, the processor 180 may perform the determined operation by controlling elements of the AI device 100.
To this end, the processor 180 may request, search, receive, and use the data of the learning processor 130 or the memory 170, and may control elements of the AI device 100 to execute a predicted operation or an operation determined to be preferred, among the at least one executable operation.
In this case, if association with an external device is necessary to perform the determined operation, the processor 180 may generate a control signal for controlling the corresponding external device and transmit the generated control signal to the corresponding external device.
The processor 180 may obtain intention information for a user input and transmit user requirements based on the obtained intention information.
In this case, the processor 180 may obtain the intention information, corresponding to the user input, using at least one of a speech to text (STT) engine for converting a voice input into a text string or a natural language processing (NLP) engine for obtaining intention information of a natural language.
In this case, at least some of at least one of the STT engine or the NLP engine may be configured as an artificial neural network trained based on a machine learning algorithm. Furthermore, at least one of the STT engine or the NLP engine may have been trained by the learning processor 130, may have been trained by the learning processor 240 of the AI server 200 or may have been trained by distributed processing thereof.
The processor 180 may collect history information including the operation contents of the AI device 100 or the feedback of a user for an operation, may store the history information in the memory 170 or the learning processor 130, or may transmit the history information to an external device, such as the AI server 200. The collected history information may be used to update a learning model.
The processor 18 may control at least some of the elements of the AI device 100 in order to execute an application program stored in the memory 170. Moreover, the processor 180 may combine and drive two or more of the elements included in the AI device 100 in order to execute the application program.
Referring to
The AI server 200 may include a communication unit 210, a memory 230, a learning processor 240 and a processor 260.
The communication unit 210 may transmit and receive data to and from an external device, such as the AI device 100.
The memory 230 may include a model storage unit 231. The model storage unit 231 may store a model (or artificial neural network 231a) which is being trained or has been trained through the learning processor 240.
The learning processor 240 may train the artificial neural network 231a using learning data. The learning model may be used in the state in which it has been mounted on the AI server 200 of the artificial neural network or may be mounted on an external device, such as the AI device 100, and used.
The learning model may be implemented as hardware, software or a combination of hardware and software. If some of or the entire learning model is implemented as software, one or more instructions configuring the learning model may be stored in the memory 230.
The processor 260 may deduce a result value of new input data using the learning model, and may generate a response or control command based on the deduced result value.
Referring to
The cloud network 10 may configure part of cloud computing infra or may mean a network present within cloud computing infra. In this case, the cloud network 10 may be configured using the 3G network, the 4G or long term evolution (LTE) network or the 5G network.
That is, the devices 100a to 100e (200) configuring the AI system 1 may be interconnected over the cloud network 10. Particularly, the devices 100a to 100e and 200 may communicate with each other through a base station, but may directly communicate with each other without the intervention of a base station.
The AI server 200 may include a server for performing AI processing and a server for performing calculation on big data.
The AI server 200 is connected to at least one of the robot 100a, the self-driving vehicle 100b, the XR device 100c, the smartphone 100d or the home appliances 100e, that is, AI devices configuring the AI system 1, over the cloud network 10, and may help at least some of the AI processing of the connected AI devices 100a to 100e.
In this case, the AI server 200 may train an artificial neural network based on a machine learning algorithm in place of the AI devices 100a to 100e, may directly store a learning model or may transmit the learning model to the AI devices 100a to 100e.
In this case, the AI server 200 may receive input data from the AI devices 100a to 100e, may deduce a result value of the received input data using the learning model, may generate a response or control command based on the deduced result value, and may transmit the response or control command to the AI devices 100a to 100e.
Alternatively, the AI devices 100a to 100e may directly deduce a result value of input data using a learning model, and may generate a response or control command based on the deduced result value.
Hereinafter, various embodiments of the AI devices 100a to 100e to which the above-described technology is applied are described. In this case, the AI devices 100a to 100e shown in
AI+Robot to which the disclosure can be applied
An AI technology is applied to the robot 100a, and the robot 100a may be implemented as a guidance robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flight robot, etc.
The robot 100a may include a robot control module for controlling an operation. The robot control module may mean a software module or a chip in which a software module has been implemented using hardware.
The robot 100a may obtain state information of the robot 100a, may detect (recognize) a surrounding environment and object, may generate map data, may determine a moving path and a running plan, may determine a response to a user interaction, or may determine an operation using sensor information obtained from various types of sensors.
In this case, the robot 100a may use sensor information obtained by at least one sensor among LIDAR, a radar, and a camera in order to determine the moving path and running plan.
The robot 100a may perform the above operations using a learning model configured with at least one artificial neural network. For example, the robot 100a may recognize a surrounding environment and object using a learning model, and may determine an operation using recognized surrounding environment information or object information. In this case, the learning model may have been directly trained in the robot 100a or may have been trained in an external device, such as the AI server 200.
In this case, the robot 100a may directly generate results using the learning model and perform an operation, but may perform an operation by transmitting sensor information to an external device, such as the AI server 200, and receiving results generated in response thereto.
The robot 100a may determine a moving path and running plan using at least one of map data, object information detected from sensor information, or object information obtained from an external device. The robot 100a may run along the determined moving path and running plan by controlling the driving unit.
The map data may include object identification information for various objects disposed in the space in which the robot 100a moves. For example, the map data may include object identification information for fixed objects, such as a wall and a door, and movable objects, such as a flowport and a desk. Furthermore, the object identification information may include a name, a type, a distance, a location, etc.
Furthermore, the robot 100a may perform an operation or run by controlling the driving unit based on a user's control/interaction. In this case, the robot 100a may obtain intention information of an interaction according to a user's behavior or voice speaking, may determine a response based on the obtained intention information, and may perform an operation.
AI+Self-driving to which the disclosure can be applied
An AI technology is applied to the self-driving vehicle 100b, and the self-driving vehicle 100b may be implemented as a movable type robot, a vehicle, an unmanned flight body, etc.
The self-driving vehicle 100b may include a self-driving control module for controlling a self-driving function. The self-driving control module may mean a software module or a chip in which a software module has been implemented using hardware. The self-driving control module may be included in the self-driving vehicle 100b as an element of the self-driving vehicle 100b, but may be configured as separate hardware outside the self-driving vehicle 100b and connected to the self-driving vehicle 100b.
The self-driving vehicle 100b may obtain state information of the self-driving vehicle 100b, may detect (recognize) a surrounding environment and object, may generate map data, may determine a moving path and running plan, or may determine an operation using sensor information obtained from various types of sensors.
In this case, in order to determine the moving path and running plan, like the robot 100a, the self-driving vehicle 100b may use sensor information obtained from at least one sensor among LIDAR, a radar and a camera.
Particularly, the self-driving vehicle 100b may recognize an environment or object in an area whose view is blocked or an area of a given distance or more by receiving sensor information for the environment or object from external devices, or may directly receive recognized information for the environment or object from external devices.
The self-driving vehicle 100b may perform the above operations using a learning model configured with at least one artificial neural network. For example, the self-driving vehicle 100b may recognize a surrounding environment and object using a learning model, and may determine the flow of running using recognized surrounding environment information or object information. In this case, the learning model may have been directly trained in the self-driving vehicle 100b or may have been trained in an external device, such as the AI server 200.
In this case, the self-driving vehicle 100b may directly generate results using the learning model and perform an operation, but may perform an operation by transmitting sensor information to an external device, such as the AI server 200, and receiving results generated in response thereto.
The self-driving vehicle 100b may determine a moving path and running plan using at least one of map data, object information detected from sensor information or object information obtained from an external device. The self-driving vehicle 100b may run based on the determined moving path and running plan by controlling the driving unit.
The map data may include object identification information for various objects disposed in the space (e.g., road) in which the self-driving vehicle 100b runs. For example, the map data may include object identification information for fixed objects, such as a streetlight, a rock, and a building, etc., and movable objects, such as a vehicle and a pedestrian. Furthermore, the object identification information may include a name, a type, a distance, a location, etc.
Furthermore, the self-driving vehicle 100b may perform an operation or may run by controlling the driving unit based on a user's control/interaction. In this case, the self-driving vehicle 100b may obtain intention information of an interaction according to a user' behavior or voice speaking, may determine a response based on the obtained intention information, and may perform an operation.
AI+XR to which the disclosure can be applied
An AI technology is applied to the XR device 100c, and the XR device 100c may be implemented as a head-mount display, a head-up display provided in a vehicle, television, a mobile phone, a smartphone, a computer, a wearable device, home appliances, a digital signage, a vehicle, a fixed type robot or a movable type robot.
The XR device 100c may generate location data and attributes data for three-dimensional points by analyzing three-dimensional point cloud data or image data obtained through various sensors or from an external device, may obtain information on a surrounding space or real object based on the generated location data and attributes data, and may output an XR object by rendering the XR object. For example, the XR device 100c may output an XR object, including additional information for a recognized object, by making the XR object correspond to the corresponding recognized object.
The XR device 100c may perform the above operations using a learning model configured with at least one artificial neural network. For example, the XR device 100c may recognize a real object in three-dimensional point cloud data or image data using a learning model, and may provide information corresponding to the recognized real object. In this case, the learning model may have been directly trained in the XR device 100c or may have been trained in an external device, such as the AI server 200.
In this case, the XR device 100c may directly generate results using a learning model and perform an operation, but may perform an operation by transmitting sensor information to an external device, such as the AI server 200, and receiving results generated in response thereto.
AI+Robot+Self-driving to which the disclosure can be applied
An AI technology and a self-driving technology are applied to the robot 100a, and the robot 100a may be implemented as a guidance robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flight robot, etc.
The robot 100a to which the AI technology and the self-driving technology have been applied may mean a robot itself having a self-driving function or may mean the robot 100a interacting with the self-driving vehicle 100b.
The robot 100a having the self-driving function may collectively refer to devices that autonomously move along a given flow without control of a user or autonomously determine a flow and move.
The robot 100a and the self-driving vehicle 100b having the self-driving function may use a common sensing method in order to determine one or more of a moving path or a running plan. For example, the robot 100a and the self-driving vehicle 100b having the self-driving function may determine one or more of a moving path or a running plan using information sensed through LIDAR, a radar, a camera, etc.
The robot 100a interacting with the self-driving vehicle 100b is present separately from the self-driving vehicle 100b, and may perform an operation associated with a self-driving function inside or outside the self-driving vehicle 100b or associated with a user got in the self-driving vehicle 100b.
In this case, the robot 100a interacting with the self-driving vehicle 100b may control or assist the self-driving function of the self-driving vehicle 100b by obtaining sensor information in place of the self-driving vehicle 100b and providing the sensor information to the self-driving vehicle 100b, or by obtaining sensor information, generating surrounding environment information or object information, and providing the surrounding environment information or object information to the self-driving vehicle 100b.
Alternatively, the robot 100a interacting with the self-driving vehicle 100b may control the function of the self-driving vehicle 100b by monitoring a user got in the self-driving vehicle 100b or through an interaction with a user. For example, if a driver is determined to be a drowsiness state, the robot 100a may activate the self-driving function of the self-driving vehicle 100b or assist control of the driving unit of the self-driving vehicle 100b. In this case, the function of the self-driving vehicle 100b controlled by the robot 100a may include a function provided by a navigation system or audio system provided within the self-driving vehicle 100b, in addition to a self-driving function simply.
Alternatively, the robot 100a interacting with the self-driving vehicle 100b may provide information to the self-driving vehicle 100b or may assist a function outside the self-driving vehicle 100b. For example, the robot 100a may provide the self-driving vehicle 100b with traffic information, including signal information, as in a smart traffic light, and may automatically connect an electric charger to a filling inlet through an interaction with the self-driving vehicle 100b as in the automatic electric charger of an electric vehicle.
AI+Robot+XR to which the Disclosure can be Applied
An AI technology and an XR technology are applied to the robot 100a, and the robot 100a may be implemented as a guidance robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flight robot, a drone, etc.
The robot 100a to which the XR technology has been applied may mean a robot, that is, a target of control/interaction within an XR image. In this case, the robot 100a is different from the XR device 100c, and they may operate in conjunction with each other.
When the robot 100a, that is, a target of control/interaction within an XR image, obtains sensor information from sensors including a camera, the robot 100a or the XR device 100c may generate an XR image based on the sensor information, and the XR device 100c may output the generated XR image. Furthermore, the robot 100a may operate based on a control signal received through the XR device 100c or a user's interaction.
For example, a user may identify a corresponding XR image at timing of the robot 100a, remotely operating in conjunction through an external device, such as the XR device 100c, may adjust the self-driving path of the robot 100a through an interaction, may control an operation or driving, or may identify information of a surrounding object.
AI+Self-driving+XR to which the disclosure can be applied
An AI technology and an XR technology are applied to the self-driving vehicle 100b, and the self-driving vehicle 100b may be implemented as a movable type robot, a vehicle, an unmanned flight body, etc.
The self-driving vehicle 100b to which the XR technology has been applied may mean a self-driving vehicle equipped with means for providing an XR image or a self-driving vehicle, that is, a target of control/interaction within an XR image. Particularly, the self-driving vehicle 100b, that is, a target of control/interaction within an XR image, is different from the XR device 100c, and they may operate in conjunction with each other.
The self-driving vehicle 100b equipped with the means for providing an XR image may obtain sensor information from sensors including a camera, and may output an XR image generated based on the obtained sensor information. For example, the self-driving vehicle 100b includes an HUD, and may provide a passenger with an XR object corresponding to a real object or an object within a screen by outputting an XR image.
In this case, when the XR object is output to the HUD, at least some of the XR object may be output with it overlapping a real object toward which a passenger's view is directed. In contrast, when the XR object is displayed on a display included within the self-driving vehicle 100b, at least some of the XR object may be output so that it overlaps an object within a screen. For example, the self-driving vehicle 100b may output XR objects corresponding to objects, such as a carriageway, another vehicle, a traffic light, a signpost, a two-wheeled vehicle, a pedestrian, and a building.
When the self-driving vehicle 100b, that is, a target of control/interaction within an XR image, obtains sensor information from sensors including a camera, the self-driving vehicle 100b or the XR device 100c may generate an XR image based on the sensor information. The XR device 100c may output the generated XR image. Furthermore, the self-driving vehicle 100b may operate based on a control signal received through an external device, such as the XR device 100c, or a user's interaction.
Example of Communication System to Which Present Disclosure is Applied
Referring to 5, a communication system 1 applied to the present disclosure includes a wireless device, a BS, and a network. Here, the wireless device may mean a device that performs communication by using a wireless access technology (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication/wireless/5G device. Although not limited thereto, the wireless device may include a robot 100a. vehicles 100b-1 and 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet of Thing (IoT) device 100f, and an AI device/server 400. For example, the vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing inter-vehicle communication, and the like. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented as a form such as a head-mounted device (HMD), a head-up display (HUD) provided in the vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, digital signage, a vehicle, a robot, etc. The hand-held device may include the smart phone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a computer (e.g., a notebook, etc.), and the like. The home appliance device may include a TV, a refrigerator, a washing machine, and the like. The IoT device may include a sensor, a smart meter, and the like. For example, the BS and the network may be implemented even the wireless device and a specific wireless device 200a may operate a BS/network node for another wireless device.
The wireless devices 100a to 100f may be connected to a network 300 through a BS 200. An artificial intelligence (AI) technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to an AI server 400 through the network 300. The network 300 may be configured by using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f may communicate with each other through the BS 200/network 300, but may directly communicate with each other without going through the BS/network (e.g., sidelink communication). For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle to Vehicle (V2V)/Vehicle to everything (V2X) communication). Further, the IoT device (e.g., sensor) may perform direct communication with other IoT devices (e.g., sensor) or other wireless devices 100a to 100f
Wireless communications/connections 150a, 150b, and 150c may be made between the wireless devices 100a to 100f and the BS 200 and between the BS 200 and the BS 200. Here, the wireless communication/connection may be made through various wireless access technologies (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-BS communication 150c (e.g., relay, Integrated Access Backhaul (IAB). The wireless device and the BS/the wireless device and the BS and the BS may transmit/receive radio signals to/from each other through wireless communications/connections 150a, 150b, and 150c. For example, the wireless communications/connections 150a, 150b, and 150c may transmit/receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least some of various configuration information setting processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), a resource allocation process, and the like for transmission/reception of the radio signal may be performed.
Devices to which the disclosure may apply
Referring to
According to an embodiment, the first device 610 may be a base station, and the second device 620 may be a UE, and each may be represented as a wireless device.
The base station 610 includes a processor 611, a memory 612, and a transceiver 613. The processor 611 implements the functions, processes or steps, and/or methods proposed in the present specification. Wireless interface protocol layers may be implemented by the processor. The memory 612 is connected with the processor and stores various pieces of information for driving the processor. The transceiver 613 is connected with the processor to transmit and/or receive wireless signals. Specifically, the transceiver 613 may include a transmitter that transmits radio signals and a receiver that receives radio signals.
The UE 620 includes a processor 621, a memory 622, and a transceiver 623.
The processor 621 implements the functions, processes or steps, and/or methods proposed above in connection with
The memory 612 and 622 may be positioned inside or outside the processor 611 and 621 and be connected with the processor 611 and 621 via various known means.
The base station 610 and/or the UE 620 may include a single or multiple antennas.
The first device 610 and the second device 620 according to another embodiment are described.
The first device 610 may be a base station, a network node, a transmission terminal, a reception terminal, a radio device, a wireless communication device, a vehicle, an autonomous vehicle, a connected car, an unmanned aerial vehicle (UAV) or drone, an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather/environment device, or a device related to fourth industrial revolution or 5G service.
The second device 620 may be a base station, a network node, a transmission terminal, a reception terminal, a radio device, a wireless communication device, a vehicle, an autonomous vehicle, a connected car, an unmanned aerial vehicle (UAV) or drone, an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather/environment device, or a device related to fourth industrial revolution or 5G service.
For example, the UE may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistants (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an Ultrabook, a wearable device, for example, a watch-type terminal (smartwatch), a glass-type terminal (smart glass), or head mounted display (HMD). For example, the HMD may be a display device worn on the head. For example, HMD may be used to implement VR, AR or MR.
For example, the drone may be an unmanned aerial vehicle that may be flown by wireless control signals. For example, the VR device may include a device that implements virtual-world objects or background. For example, the AR device may include a device that connects and implements virtual-world objects or background on real-world objects or background. For example, the MR device may include a device that combines and implements virtual-world objects or background with real-world objects or background. For example, the hologram device may include a device that implements a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing a light interference phenomenon (so-called holography) that occurs when two laser beams meet. For example, the public safety device may include an image relay device or an image device wearable on a user's body. For example, the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors. For example, the medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating or preventing a disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, alleviating or correcting an injury or disorder. For example, the medical device may be a device used for the purpose of examining, replacing or modifying a structure or function. For example, the medical device may be a device used for the purpose of controlling pregnancy. For example, the medical device may include a device for treatment, a device for surgery, a device for (in-vitro) diagnosis, a hearing aid or a device for procedure. For example, the security device may be a device installed to prevent possible hazards and maintain safety. For example, the security device may be a camera, CCTV, recorder, or black box. For example, the fintech device may be a device capable of providing financial services such as mobile payment. For example, the fintech device may include a payment device or a point-of-sales (POS) device. For example, the weather/environment device may include a device that monitors or predicts the weather/environment.
The first device 610 may include at least one or more processors, such as the processor 611, at least one or more memories, such as the memory 612, and at least one or more transceivers, such as the transceiver 613. The processor 611 may perform the functions, procedures, and/or methods described above. The processor 611 may perform one or more protocols. For example, the processor 611 may perform one or more layers of the air interface protocol. The memory 612 may be connected to the processor 611 and may store various types of information and/or commands. The transceiver 613 may be connected to the processor 611 and be controlled to transmit and receive wireless signals.
The second device 620 may include at least one processor, such as the processor 621, at least one memory device, such as the memory 622, and at least one transceiver, such as the transceiver 623. The processor 621 may perform the functions, procedures, and/or methods described above. The processor 621 may implement one or more protocols. For example, the processor 621 may implement one or more layers of the air interface protocol. The memory 622 may be connected to the processor 621 and may store various types of information and/or commands. The transceiver 623 may be connected to the processor 621 and be controlled to transmit and receive wireless signals.
The memory 612 and/or the memory 622 may be connected inside or outside the processor 611 and/or the processor 621 or may be connected to other processors through various technologies such as wired or wireless connection.
The first device 610 and/or the second device 620 may have one or more antennas. For example, the antenna 614 and/or the antenna 624 may be configured to transmit and receive wireless signals.
Referring to
UL (communication from the UE to the base station) is handled by the base station 710 in a similar manner to those described above in connection with the functions of the receiver in the UE 720. Each Tx/Rx module 725 receives signals via its respective antenna 726. Each Tx/Rx module provides RF carrier and information to the Rx processor 723. The processor 721 may be related to the memory 724 that stores program code and data. The memory may be referred to as a computer readable medium.
In the disclosure, the wireless device may be a base station, a network node, a transmission terminal, a reception terminal, a radio device, a wireless communication device, a vehicle, an autonomous vehicle, an unmanned aerial vehicle (UAV) or drone, an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather/environment device, or a device related to fourth industrial revolution or 5G service. For example, the drone may be an unmanned aerial vehicle that may be flown by wireless control signals. For example, the MTC device and IoT device may be devices that need no human involvement or control and may be, e.g., smart meters, vending machines, thermostats, smart bulbs, door locks, or various sensors. For example, the medical device may be a device for diagnosing, treating, mitigating, or preventing disease or a device used for testing, replacing, or transforming the structure or function, and may be, e.g., a piece of equipment for treatment, surgery, (extracorporeal) diagnosis device, hearing aid, or procedure device. For example, the security device may be a device for preventing possible risks and keeping safe, which may include, e.g., a camera, a CCTV, or a blackbox. For example, the fintech device may be a device capable of providing mobile payment or other financial services, which may include, e.g., a payment device or point-of-sales (PoS) device. For example, the weather/environment device may mean a device that monitors and forecasts weather/environment.
In the disclosure, the UE may encompass, e.g., mobile phones, smartphones, laptop computers, digital broadcast terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation, slate PCs, tablet PCs, Ultrabooks, wearable devices (e.g., smartwatches, smart glasses, or head-mounted displays (HMDs), or foldable devices. For example, the HMD, as a display wom on the human's head, may be used to implement virtual reality (VR) or augmented reality (AR).
3GPP LTE/LTE-A support a radio frame structure type 1 which may be applicable to Frequency Division Duplex (FDD) and a radio frame structure which may be applicable to Time Division Duplex (TDD).
The size of a radio frame in the time domain is represented as a multiple of a time unit of T_s=1/(15000*2048) in
(a) of
A radio frame includes 10 subframes. A radio frame includes 20 slots of T_slot=15360*T_s=0.5 ms length, and 0 to 19 indexes are given to each of the slots. One subframe includes consecutive two slots in the time domain, and subframe i includes slot 2i and slot 2i+1. The time required for transmitting a subframe is referred to as a transmission time interval (TTI). For example, the length of the subframe i may be 1 ms and the length of a slot may be 0.5 ms.
A UL transmission and a DL transmission in the FDD are distinguished in the frequency domain. Whereas there is no restriction in the full duplex FDD, a UE may not transmit and receive simultaneously in the half duplex FDD operation.
One slot includes a plurality of Orthogonal Frequency Division Multiplexing (OFDM) symbols in the time domain and includes a plurality of Resource Blocks (RBs) in a frequency domain. In 3GPP LTE, OFDM symbols are used to represent one symbol period because OFDMA is used in downlink. An OFDM symbol may be called one SC-FDMA symbol or symbol period. An RB is a resource allocation unit and includes a plurality of contiguous subcarriers in one slot.
(b) of
A type 2 radio frame includes two half frame of 153600*T_s=5 ms length each. Each half frame includes 5 subframes of 30720*T_s=1 ms length.
In the frame structure type 2 of a TDD system, an uplink-downlink configuration is a rule indicating whether uplink and downlink are allocated (or reserved) to all subframes.
Table 1 shows the uplink-downlink configuration.
Referring to Table 1, in each subframe of the radio frame, ‘D’ represents a subframe for a DL transmission, ‘U’ represents a subframe for UL transmission, and ‘S’ represents a special subframe including three types of fields including a Downlink Pilot Time Slot (DwPTS), a Guard Period (GP), and a Uplink Pilot Time Slot (UpPTS).
A DwPTS is used for an initial cell search, synchronization or channel estimation in a UE. A UpPTS is used for channel estimation in an eNB and for synchronizing a UL transmission synchronization of a UE. A GP is duration for removing interference occurred in a UL owing to multi-path delay of a DL signal between a UL and a DL.
Each subframe i includes slot 2i and slot 2i+1 of T_slot=15360*T_s=0.5 ms.
The UL-DL configuration may be classified into 7 types, and the position and/or the number of a DL subframe, a special subframe and a UL subframe are different for each configuration.
A point when the downlink is changed to the uplink or a point when the uplink is switched to the downlink is referred to as a switching point. Switch-point periodicity means a period in which an aspect in which the uplink subframe and the downlink subframe are switched is similarly repeated and both 5 ms and 10 ms are supported. When the downlink-downlink switch-point periodicity is 5 ms, the special subframe S exists for each half-frame and when the downlink-uplink switch-point periodicity is 5 ms, the special subframe S exists only in a first half-frame.
In all configurations, subframes #0 and #5 and the DwPTS are periods only for the downlink transmission. The UpPTS and the subframe and a subframe immediately following the subframe are always periods for the uplink transmission.
The uplink-downlink configuration as system information may be known by both the base station and the UE. The base station transmits only an index of configuration information whenever the configuration information is changed to notify the UE of a change of an uplink-downlink assignment state of the radio frame. Further, the configuration information as a kind of downlink control information may be transmitted through a physical downlink control channel (PDCCH) similar to another scheduling information and as broadcast information may be commonly transmitted to all UEs in a cell through a broadcast channel.
Table 2 represents configuration (length of DwPTS/GP/UpPTS) of a special subframe.
The structure of a radio subframe according to the example of
Narrowband Internet of Things (NB-IoT)
Narrowband Internet of things (NB-IoT) as a standard for supporting low complexity and low cost devices is defined to perform only relatively simple operations compared to legacy LTE devices. The NB-IoT follows a basic structure of LTE, but operates based on contents defined below. If the NB-IoT reuses a channel or signal of the LTE, the NB-IoT may follow the standard defined in the legacy LTE.
Uplink
The following narrowband physical channels are defined:
The following uplink narrowband physical signals are defined:
In terms of N_sc{circumflex over ( )}UL, an uplink bandwidth and slot duration T_slot are given by
Resource Unit
Resource units are used to describe the mapping of the NPUSCH to resource elements. A resource unit is defined as NsymbULNslotsUL consecutive SC-FDMA symbols in the time domain and NscRU consecutive subcarriers in the frequency domain, where NscRU and NsymbUL are given by Table 4.
Table 4 shows an example of supported combinations of NscRU, NslotsUL, and NsymbUL.
Narrowband uplink shared channel (NPUSCH)
The narrowband physical uplink shared channel supports two formats:
NPUSCH format 1, used to carry the UL-SCH
NPUSCH format 2, used to carry uplink control information
Scrambling shall be done according to clause 5.3.1 of TS36.211. The scrambling sequence generator shall be initialized with cint−nRNTI·214+nf mod 2·213+└ns/2┘÷NIDNcell where ns is the first slot of the transmission of the codeword. In case of NPUSCH repetitions, the scrambling sequence shall be reinitialized according to the above formula after every MidenticalNPUSCH transmission of the codeword with ns and nf set to the first slot and the frame, respectively, used for the transmission of the repetition. The quantity MidenticalNPUSCH is given by clause 10.1.3.6 in TS36.211.
Table 5 specifies the modulation mappings applicable for the narrowband physical uplink shared channel.
Narrowband Physical Downlink Control Channel (NPDCCH)
A narrowband physical downlink control channel transports control information. The narrowband physical downlink control channel is transmitted through aggregation of one or two consecutive narrowband control channel elements (NCCEs), here, the narrowband control channel elements correspond to 6 consecutive subcarriers in the subframe, and here, NCCE 0 occupies subcarriers 0 to 5 and NCCE 1 occupies subcarriers 6 to 11. The NPDCCH supports various formats listed in Table 1-26. In the case of NPDCCH format 1, all NCCEs belong to the same subframe. One or two NPDCCHs may be transmitted in the subframe.
Table 6 shows an example of supported NPDCCH formats.
Scrambling should be performed according to Section 6.8.2 of TS36.211. A scrambling sequence should be initialized at a beginning of subframe k0 according to Section 16.6 of TS36.213 after every fourth NPDCCH subframe having cinit=└n2/2┘2 +NIDNcell, and here, n1 a represents a first slot of an NPDCCH subframe in which scrambling is (re-)initialized.
Modulation is performed by using a QPSK modulation scheme according to Section 6.8.3 of TS36.211.
Layer mapping and precoding are performed according to Section 6.6.3 of TS36.211 by using the same antenna port.
A block y(0) . . . y(Mymb−1) of complex-value symbols is mapped to resource elements (k.l) in a sequence starting as y(0) through an associated antenna port satisfying all of the following criteria.
They are parts of NCCE(s) allocated for NPDCCH transmission, and
it is assumed that they are not sued for transmission of NPBCH, NPSS, or NSSS, and
it is assumed that they are not used by the UE for an NRS, and
they (if exists) do not overlap with resource elements used for PBCH, PSS, SSS, or CRS as defined in Section 6 of TS36.211, and
an index l of the first slot of the subframe satisfies l≥lNPDCCHStart, and here, lNPDCCHStart is provided by Section 16.6.1 of 3GPP TS 36.213.
Mapping to resource elements (k,l) through an antenna port p satisfying the aforementioned criteria is an increase order of an index l after a first index k, which starts from the first slot of the subframe and ends with the second slot.
The NPDCCH transmission may be configured by higher layers having transmission gaps in which the NPDCCH transmission is delayed. The configuration is the same as that described for the NPDSCH in Section 10.2.3.4 of TS36.211.
In the case where a subframe other than the NB-IoT downlink subframe, the UE does not expect the NPDCCH in the subframe i. In the case of NPDCCH transmission, in subframes other than the NB-IoT downlink subframes, the NPDCCH transmissions are delayed up to a next NB-IoT downlink subframe.
Referring to
Each element on the resource grid is referred to as a resource element, and one resource block (RB) includes 12×7 resource elements. The number of RBs N{circumflex over ( )}DL included in a downlink slot depends on a downlink transmission bandwidth.
The structure of an uplink slot may be the same as that of a downlink slot.
Referring to
A PCFICH is transmitted in the first OFDM symbol of a subframe and carries information about the number of OFDM symbols (i.e., the size of a control region) which is used to transmit control channels within the subframe. A PHICH is a response channel for uplink and carries an acknowledgement (ACK)/not-acknowledgement (NACK) signal for a Hybrid Automatic Repeat Request (HARQ). Control information transmitted in a PDCCH is called Downlink Control Information (DCI). DCI includes uplink resource allocation information, downlink resource allocation information, or an uplink transmission (Tx) power control command for a specific UE group.
The PDCCH may carry resource allocation and a transmission format (also referred to as a downlink (DL) grant) of a downlink-shared channel (DL-SCH), resource allocation information (also referred to as an uplink (UL) grant) of an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information on the DL-SCH, resource allocation of an upper layer control message such as a random access response transmitted on a PDSCH, activation of a set of transmission power control (TPC) commands for individual UEs in a predetermined UE group and a voice over Internet protocol (VoIP), and the like. A plurality of PDCCHs may be transmitted in the control region and the UE may monitor the plurality of PDCCHs. The PDCCH is configured by one control channel element or a set of a plurality of consecutive control channel elements (CCEs). The CCE is a logical allocation unit used for providing a coding rate depending on a state of a radio channel to the PDCCH. The CCE corresponds to a plurality of resource element groups. A format of the PDCCH and the number of bits of the PDCCH available are determined according to an association relationship between the number of CCEs and the coding rate provided by the CCEs.
The eNB decides a PDCCH format according to the DCI to be sent to the UE and attaches cyclic redundancy check (CRC) to the control information. The CRC is masked with a radio network temporary identifier (RNTI) according to an owner or a purpose of the PDCCH. The CRC may be masked with a unique identifier (e.g., cell-RNTI (C-RNTI)) of the UE in the case of the PDCCH for a specific UE. Alternatively, in the case of the PDCCH for the paging message, the CRC may be masked with a paging indication identifier (e.g., paging-RNTI (P-RNTI)). In the case of the PDCCH for system information, more specifically, a system information block (SIB), the CRC may be masked with a system information-RNTI (SI-RNTI). The CRC may be masked with a random access-RNTI (RA-RNTI) in order to indicate a random access response which is a response to transmission of a random access preamble of the UE.
Referring to
A Resource Block (RB) pair is allocated to a PUCCH for one UE within a subframe. RBs belonging to an RB pair occupy different subcarriers in each of 2 slots. This is called that an RB pair allocated to a PUCCH is frequency-hopped in a slot boundary.
Semi-Persistent Scheduling (SPS)
Semi-Persistent Scheduling (SPS) is a scheduling scheme in which resources are allocated to a specific UE so as to be continuously maintained for a specific time interval.
When a predetermined amount of data is transmitted for a specific time like Voice over Internet Protocol (VoIP), it is not necessary to transmit control information every data transmission interval for resource allocation, so the waste of the control information may be reduced by using the SPS scheme. In the so-called SPS method, a time resource region in which the resources may be allocated to the UE is first allocated.
In this case, in the semi-persistent allocation method, the time resource region allocated to the specific UE may be configured to have periodicity. Then, the allocation of time-frequency resources is completed by allocating a frequency resource region as necessary.
The allocation of the frequency resource region may be referred to as so-called activation. When the semi-persistent allocation method is used, the resource allocation is maintained during a predetermined period by one signaling, repeated resource allocation need not be performed, thereby reducing signaling overhead.
Thereafter, when resource allocation for the UE is no longer needed, signaling for releasing frequency resource allocation may be transmitted from the eNB to the UE. Releasing the allocation of the frequency resource region may be referred to as deactivation.
In the current LTE, for the SPS for uplink and/or downlink, in which subframes the SPS is to be transmitted/received is first notified to the UE through Radio Resource Control (RRC) signaling. That is, the time resource is first allocated among the time-frequency resources allocated to the SPS through the RRC signaling. In order to notify the subframe which may be used, for example, a periodicity and an offset of the subframe may be notified. However, since the UE receives only the time resource region through RRC signaling, even if the UE receives the RRC signaling, the UE does not immediately perform transmission/reception by the SPS, and completes the time-frequency resource allocation by allocating the frequency resource region as necessary. The allocation of the frequency resource region may be referred to as activation and releasing the allocation of the frequency resource region may be referred to as deactivation.
Therefore, after receiving the PDCCH indicating activation, the UE allocates the frequency resource according to the RB allocation information included in the received PDCCH, and applies modulation and code rate depending on Modulation and Coding Scheme (MCS) information to start transmission/reception according to the subframe periodicity and offset allocated through the RRC signaling.
Then, the UE stops transmission/reception when receiving the PDCCH indicating the deactivation from the eNB. If a PDCCH indicating activation or reactivation is received after stopping transmission and reception, transmission and reception are resumed again with the subframe period and offset allocated by RRC signaling using an RB allocation or an MCS designated by the PDCCH. That is, the allocation of time resources is performed through RRC signaling, but the transmission and reception of the actual signal may be performed after receiving the PDCCH indicating the activation and reactivation of the SPS, and the interruption of the transmission and reception of the signal is performed by the PDCCH indicating the deactivation of the SPS.
Specifically, when the SPS is activated by the RRC, the following information may be provided.
Unlike this, when the SPS is deactivated by the RRC, a configured grant or a configured assignment should be discarded.
Further, the SPS is supported only in SpCell and is not supported for RN communication with E-UTRAN together with an RN subframe configuration.
In relation to the downlink SPS, after the semi-persistent downlink assignment is configured, the MAC entity needs to consider sequentially that the N-th assignment occurs in a subframe, as shown in Equation 1 below.
(10*SFN+subframe)=[(10*SFNstart time+subframestart time)+N*semiPersistSchedIntervalDL] modulo 10240 [Equation 1]
In Equation 1, SFNstart time and subframestart time mean SFN and subframe in which the configured downlink assignment is (re)initialized, respectively. For BL UEs or UEs of enhanced coverage, the SFNstate time and subframestate time may refer to the SFN and subframe of the first PDSCH transmission in which the configured downlink assignment is (re)initialized.
In contrast, in relation to the uplink SPS, after the semi-persistent uplink assignment is configured, the MAC entity needs to consider sequentially that the N-th grant occurs in the subframe, as shown in Equation 2 below.
(10*SFN+subframe)=[(10*SFNstart time+subframestart time)+N*semiPersistSchedIntervalUL+Subframe_Offset*(N modulo 2)] modulo 10240 [Equation 2]
In Equation 2, SFNstart time and subframestate time mean SFN and subframe in which the configured uplink grant is (re)initialized, respectively. For the BL UEs or the UEs of enhanced coverage, the SFNstate time and subframestart time may refer to the SFN and subframe of the first PDSCH transmission in which the configured uplink grant is (re)initialized.
Table 7 below is an example of an RRC message (SPS-Config) for specifying the above-described SPS configuration.
PDCCH/EPDCCH/MPDCCH Validation for Semi-Persistent Scheduling
The UE may validate the PDCCH including the SPS indication when all of the following conditions are satisfied. First, the CRC parity bit added for the PDCCH payload should be scrambled with the SPS C-RNTI, and second, a New Data Indicator (NDI) field should be set to zero. Here, in the case of DCI formats 2, 2A, 2B, 2C, and 2D, the new data indicator field indicates one of the activated transport blocks.
Furthermore, the UE may validate the EPDCCH including the SPS indication when all of the following conditions are satisfied. First, the CRC parity bit added for the EPDCCH payload should be scrambled with the SPS C-RNTI, and second, the New Data Indicator (NDI) field should be set to zero. Here, in the case of DCI formats 2, 2A, 2B, 2C, and 2D, the new data indicator field indicates one of the activated transport blocks.
Further, the UE may validate the MPDCCH including the SPS indication when all of the following conditions are satisfied. First, the CRC parity bit added for the MPDCCH payload should be scrambled with the SPS C-RNTI, and second, the New Data Indicator (NDI) field should be set to zero.
When each field used for the DCI format is configured according to Table 4 or Table 5, Table 6, and Table 7 below, the validation is completed. When the validation is completed, the UE recognizes the received DCI information as valid SPS activation or deactivation (or release). On the other hand, when the validation is not completed, the UE recognizes that the non-matching CRC is included in the received DCI format.
Table 8 shows fields for PDCCH/EPDCCH validation indicating SPS activation.
Table 9 shows fields for PDCCH/EPDCCH validation indicating SPS deactivation (or release).
Table 10 shows fields for MPDCCH validation indicating SPS activation.
Table 11 shows fields for MPDCCH validation indicating SPS deactivation (or release).
When the DCI format indicates SPS downlink scheduling activation, the TPC command value for the PUCCH field may be used as an index indicating four PUCCH resource values set by a higher layer.
Table 12 shows PUCCH resource values for downlink SPS.
Procedure Related to Downlink Control Channel in NB-IoT
A procedure related to a Narrowband Physical Downlink Control Channel (NPDCCH) used in an NB-IoT will be described.
The UE needs to monitor NPDCCH candidates (i.e., a set of NPDCCH candidates) according to a configuration by a higher layer signaling for control information. Here, the monitoring may imply attempting to decode each of the MPDCCHs in the set according to all monitored DCI formats. The set of the NPDCCH candidates to be monitored may be defined as an NPDCCH search space. In this case, the UE may perform monitoring by using an identifier (e.g., C-RNTI, P-RNTI, SC-RNTI, or G-RNTI) corresponding to the corresponding NPDCCH search space.
In this case, the UE needs to monitor one or more a) a Type1-NPDCCH common search space, b) a Type2-NPDCCH common search space, and c) an NPDCCH UE-specific search space. In this case, the UE need not simultaneously monitor the NPDCCH UE-specific search space and the Type1-NPDCCH common search space. Furthermore, the UE need not simultaneously monitor the NPDCCH UE-specific search space and the Type2-NPDCCH common search space. Furthermore, the UE need not simultaneously monitor the Type1-NPDCCH common search space and the Type2-NPDCCH common search space.
The NPDCCH search space in an aggregation level and a repetition level is defined by the set of the NPDCCH candidates. Here, each NPDCCH candidate is repeated in R consecutive NB-IoT downlink subframes other than a subframe used for transmission of a system information (SI) message that starts in subframe k.
In the case of the NPDCCH UE-specific search, the aggregation and repetition levels defining the corresponding search space and the corresponding monitored NPDCCH candidates are listed as shown in Table 13 as a value of RMAX is substituted with a parameter al-Repetition-USS configured by the higher layer.
In the case of the Type1-NPDCCH common search space, the aggregation and repetition levels defining the corresponding search space and the corresponding monitored NPDCCH candidates may be listed as shown in Table 14 as a value of RMAX is substituted with a parameter al-Repetition-CSS-Paging configured by the higher layer.
In the case of the Type2-NPDCCH common search space, the aggregation and repetition levels defining the corresponding search space and the corresponding monitored NPDCCH candidates may be listed as shown in Table 15 as a value of RMAX is substituted with a parameter npdcch-MaxNumRepetitions-RA configured by the higher layer.
In this case, the position of the starting subframe k is given by k=kb. Here, kb represents a b-th consecutive NB-IoT downlink subframe from the subframe k0 except for a subframe used for transmitting an SI message, the b is u×R, and the u represents 0, 1, . . . (RMAX/R)−1. Further, the subframe k0 represents a subframe satisfying Equation 3.
(10nf+└ns/2┘)mod T=αoffset·T, where T=Rmax·G [Equation 3]
In the case of the NPDCCH UE-specific search space, G shown in Equation 3 is given by a higher layer parameter nPDCCH-startSF-UESS and αoffset is given by a higher layer parameter nPDCCH-startSFoffset-UESS. Furthermore, in the case of the NPDCCH Type2-NPDCCH common search space, G shown in Equation 3 is given by a higher layer parameter nPDCCH-startSF-Type2CSS and αoffset is given by a higher layer parameter nPDCCH-startSFoffset-Type2CSS. Furthermore, in the case of the Type1-NPDCCH common search space, k is k0 and is determined from a position of an NB-IoT paging opportunity subframe.
When the UE is configured by the higher layer as a PRB for monitoring an NPDCCH UE-specific search area, the UE should monitor the NPDCCH UE-specific search space in the PRB configured by the higher layer. In this case, the UE does not expect that an NPSS, an NSSS, and an NPBCH are received in the corresponding PRB. On the contrary, when the PRB is not configured by the higher layer, the UE should monitor the NPDCCH UE-specific search space on the same PRB as detecting the NPSS/NSSS/NPBCH.
When the NB-IoT UE detects the NPDCCH having DCI format NO which is terminated in subframe n and when transmission of the corresponding NPUSCH format 1 starts in subframe n+k, the UE need not monitor the NPDCCH of the random subframe which starts within the range from subframe n+1 up to subframe n+k−1. When the NB-IoT UE detects the NPDCCH having DCI format N1 or DCI format N2 which ends in subframe n and when transmission of the corresponding NPDSCH starts in subframe n+k, the UE need not monitor the NPDCCH of the random subframe which starts within the range from subframe n+1 up to subframe n+k−1.
Furthermore, when the NB-IoT UE detects the NPDCCH having the DCI format N1 which ends in subframe n and when transmission of the corresponding NPUSCH format starts in subframe n+k, the UE need not monitor the NPDCCH of the random subframe which starts within the range from subframe n+1 up to subframe n+k−1.
Furthermore, when the NB-IoT UE detects the NPDCCH having DCI format N1 for “PUCCH order” which is terminated in subframe n and when transmission of the corresponding NPRACH starts in subframe n+k, the UE need not monitor the NPDCCH of the random subframe which starts within the range from subframe n+1 up to subframe n+k−1.
Furthermore, when the NB-IoT UE has NPUSCH transmission which ends in subframe n, the UE need not monitor the NPDCCH of a random subframe which starts within a range from subframe n+1 up to subframe n+3.
Furthermore, when the NPDCCH candidate of the NPDCCH search space ends in subframe n and when the UE is configured to monitor the NPDCCH candidate of another NPDCCH search space which starts before subframe n+5, the NB-IoT UE need not monitor the NPDCCH candidate of the NPDCCH search space.
In connection with an NPDCCH starting position, a starting OFDM symbol for the NPDCCH is given by an index lNPDCCHStart in a first slot of subframe k. In this case, when the higher layer parameter operarionModeInfo indicates ‘00’ or ‘01’, the index lNPDCCHStart is given by the higher layer parameter eutaControlRegionSize. Unlike this, when the higher layer parameter operarionModeInfo indicates ‘10’ or ‘11’m, the index lNPDCCHStart is 0.
NPDCCH Validation for Semi-Persistent Scheduling (SPS)
Only when all of the following conditions are satisfied, the UE may determine that the NPDCCH allocating semi-persistent scheduling is valid.
When all fields for the used DCI format NO are configured are configured according to Table 16 or 17 below, the validity of the NPDCCH may be confirmed.
When the validity of the NPDCCH is confirmed, the UE should regard the NPDCCH as valid semi-persistent scheduling activation or release according to received DCI information.
When the validity of the NPDCCH is not confirmed, the UE should regard that the received DCI information is received together with a CRC which is not matched.
Downlink Control Information (DCI) Format
DCI transmits downlink or uplink scheduling information for one cell and one RNTI. Here, the RNTI is implicitly encoded with CRC.
As the DCI format related to the NB-IoT, the DCI format N0, the DCI format N1, and the DCI format N2 may be considered.
First, the DCI format NO may be used for scheduling of the NPUSCH in one uplink (UL) cell and may transmit the following information.
Next, DCI format N1 is used for scheduling of one NPDSCH codeword in one cell and a random access procedure initiated by an NPDCCH order. In this case, DCI corresponding to the NPDCCH order may be carried by the NPDCCH.
The DCI format N1 may transmit the following information.
Only when the NPDCCH order indicator is set to ‘1’, a cyclic redundancy check (CRC) of the format N1 is scrambled with C-RNTI, and all remaining fields are configured as follows, the format N1 is used for the random access process initiated by the NPDCCH order.
Otherwise, the following remaining information is transmitted.
When the CRC of the format N1 is scrambled with RA-RNTI, the following information (i.e., field) among the information (i.e., fields) is reserved.
In this case, the number of information bits of the format N1 is smaller than the number of information bits of the format NO, ‘0’ should be appended until a payload size of the format N1 is equal to the payload size of the format NO.
Next, the DCI format N2 may be used for paging and direct indication and may transmit the following information.
When the value of the flag is 0, the DCI format N2 includes (or transmits) direct indication information (e.g., 8 bits) and reserved information bits for configuring the same size as the format N2 in which the value of the flag is 1.
On the contrary, when the value of the flag is 1, the DCI format N2 includes (or transmits) the resource assignment (e.g., 3 bits), the modulation and coding scheme (e.g., 4 bits), the repetition number (e.g., 4 bits), and the DCI subframe repetition number (e.g., 3 bits).
Resource Allocation for Uplink Transmission with Configured Grant
When PUSCH resource allocation is semi-persistently configured by a higher layer parameter ConfiguredGrantConfig of the bandwidth (BWP) information element and PUSCH transmission corresponding to the configured grant is triggered, the next higher layer parameter is applied to the PUSCH transmission:
When the higher layer does not deliver a transport block to be transmitted in a resource allocated for uplink transmission without a grant, the UE does not transmit anything in the resource configured by ConfiguredGrantConfig.
A set of permitted periods P is defined in [12, TS 38.331].
Transport Block Repetition for Uplink Transmission with a Configured Grant
Higher layer configuration parameters repK and repK-RV define K repetition to be applied to the transmitted transport block and a redundancy version (RV) pattern to be applied to repetition. Among K repetitions, for a case of n-th transmission (n=1, 2, . . . , K), the corresponding transmission is associated with a (mod(n−1,4)+1)-th value in a configured RV sequence. Initial transmission of the transport block may start in the following cases.
For a random RV sequence, the repetition should end at a first reach timing among a case of transmission repeated at K times, a case of the last transmission occasion among K repetitions with a period P, or a case of receiving a UL grant for scheduling the same TB within the period P.
In regard to a time duration for transmission of K repetitions, the UE does not expect to set a time duration longer than a time duration derived by the period P.
For both type 1 and type 2 PUSCH transmissions, when repK>1 is configured in the UE, the UE should repeat the TB through repK consecutive slots by applying the same symbol allocation in each slot. When a symbol of a slot allocated for the PUSCH is determined as a downlink symbol in a UE procedure for determining a slot configuration defined in Section 11.1 of TS 38.213, transmission in the corresponding slot is skipped for multi-slot PUSCH transmission.
Initial Access Procedure of NB-IoT
In a general signal transmission/reception procedure of NB-IoT, an initial access procedure to the base station by the NB-IoT UE is briefly described. Specifically, the initial access procedure to the base station by the NB-IoT UE may be constituted by a procedure of searching an initial cell and a procedure of acquiring the system information by the NB-IoT UE.
In this regard, a specific signaling procedure between a UE and a base station (e.g., NodeB, eNodeB, eNB, gNB, etc.) related to the initial access of NB-IoT may be illustrated as in
As illustrated in
The NB-IoT UE may receive a MasterInformationBlock-NB (MIB-NB) on an NB Physical Broadcast Channel (NPBCH) (S1230).
The MIB-NB uses a fixed schedule with a period of 640 ms and repetitions made within 640 ms. The first transmission of the MIB-NB is scheduled in subframe #0 of radio frames with SFN mod 64=0, and scheduled in subframe #0 of radio frames in which repetitions are all different. The transmissions are arranged in eight independently decodable blocks with a time duration of 80 ms.
Thereafter, the NB-IoT UE may receive a SystemInformationBlockType1-NB (SIB1-NB) on the PDSCH (S1240).
The SIB1-NB uses a fixed schedule with a period of 2560 ms. SIB1-NB transmission occurs in subframe #4 of all different frames in 16 consecutive frames. The start frame for the first transmission of the SIB1-NB is derived by a cell PCID and the number of repetitions at the period of 2560 ms. The repetitions are made at an equal interval within the period of 2560 ms. The TBS for the SystemInformationBlockType1-NB and the repetitions made within 2560 ms are indicated by a field scheduleInfoSIB1 of the MIB-NB.
An SI message is transmitted within time domain windows (referred to as SI windows) which occur periodically by using scheduling information provided by the SystemInformationBlockType1-NB. Each SI message is associated with an SI window, and SI windows of other SI messages do not overlap. That is, only SI corresponding to one SI window is transmitted. When the SI message is configured, the length of the SI window is common to all SI messages.
In the SI window, the corresponding SI message may be transmitted multiple times through 2 or 8 consecutive NB-IoT downlink subframes according to the TBS. The UE uses detailed time/frequency domain scheduling information and other information. The other information may be, for example, a transmission format for the SI message in a field schedulingInfoList of the SystemInformationBlockType1-NB. The UE need not accumulate multiple SI messages in parallel, but may need to accumulate the SI messages over multiple SI windows depending on a coverage condition.
The SystemInformationBlockType1-NB configures the length and the transmission period of the SI window for all SI messages.
Further, the NB-IoT UE may receive a SystemInformationBlockType2-NB (SIB2-NB) on the PDSCH (S1250).
Meanwhile, as illustrated in
Random Access Procedure of NB-IoT
In the general signal transmission/reception procedure of the NB-IoT, a random access procedure to the base station by the NB-IoT UE is briefly described. Specifically, the random access procedure to the base station by the NB-IoT UE may be performed through a procedure of transmitting the preamble to the base station and receiving a response thereto.
In this regard, a specific signaling procedure between a UE and a base station (e.g., NodeB, eNodeB, eNB, gNB, etc.) related to the random access of the NB-IoT may be illustrated as in
As illustrated in
The NB-IoT supports only a contention-based random access and a PDCCH order when downlink data arrives. The NB-IoT reuses the eMTC PRACH resource classification according to a coverage level. A set of PRACH resources is provided for each application coverage level configured with the system information (SI). The UE selects a PRACH resource based on a coverage level determined by downlink measurement such as reference signal reception power (RSRP), and transmits a random access preamble (MSG1) by using the selected PRACH resource (S1310). In the NB-IoT, the PRACH may mean a narrowband physical random access channel (NPRACH). The random access procedure is performed in either an anchor carrier or a non-anchor carrier in which the PRACH resource is configured with the SI. The preamble transmission may be repeated up to {1, 2, 4, 8, 16, 32, 64, 128} times in order to enhance coverage.
When transmitting the preamble, the UE first calculates a random access radio network temporary identifier (RA-RNTI) from a preamble transmission time. RA-RNTI is given by RA-RNTI=1+floor (SFN_id/4), and SFN_id represents an index (i.e., preamble) of a first radio frame of a specific PRACH.
Thereafter, the UE monitors the PDCCHs within the time window to find the PDCCH for the DCI format N1 scrambled with RA-RNTI in which the random access response (RAR) message is displayed. The time window (or RAR window) starts at subframe (SF)+3 subframe (SF) of a last preamble and has a CE dependent length given in the system information block type 2-narrowband (SIB2-NB).
When the preamble transmission is unsuccessful, for example, when the associated RAR message is not received, the UE transmits another preamble. Such an operation is performed up to a maximum number, and the maximum number depends on a CE level. When the RAR is not received even though the preamble is transmitted at the maximum number, the UE performs the corresponding operation at a next (i.e., higher) CE level. When the total number of access attempt is reached, the associated failure is reported to the RRC. Through the RAR, the UE acquires a temporary C-RNTI, a timing advance command, etc. The MSG3 is temporally aligned and required for transmission through the NPUSCH. The RAR provides a UL grant including all related data for transmission of the MSG3.
The scheduled message MSG3 is transmitted for starting a contention resolution process. An associated contention resolution message MSG4 is finally transmitted to the UE in order to indicate successful completion of the RACH procedure. The contention resolution process is basically the same as the LTE. That is, the UE transmits identification through the MSG3, and when the UE receives the MSG4 indicating the identification, the random access procedure is successfully completed.
Hereafter, in regard to the random access procedure of the NB-IOT, the NPRACH which the NB-IoT UE transmits to the base station will be described in detail with reference to
A physical layer random access preamble is based on a single subcarrier frequency hopping symbol group.
As illustrated in
Parameter values of frame structures 1 and 2 are shown in Tables 18 and 19, respectively.
When transmission of the random access preamble is triggered by the MAC layer, the transmission of the random access preamble is limited to a specific time and a frequency resource. In each NPRACH resource configuration, a maximum of 3 NPRACH resource configurations may be configured in cells corresponding to different coverage levels. The NPRACH resource configuration is given by periodicity, the repetition number, a starting time, a frequency location, and the number of subcarriers.
Due to a specific uplink transmission scheme in the NB-IoT, tone information is further included in the RAR message, and an equation for deriving the Random Access Radio Network Temporary Identifier (RA-RNTI) is newly defined. In order to support transmission repetition, corresponding parameters including an RAR window size and a medium access control (MAC) contention resolution timer are extended.
Referring to
When transmission of the random access preamble is triggered by the MAC layer, the transmission of the random access preamble is limited to a specific time and a frequency resource. In each NPRACH resource configuration, a maximum of 3 NPRACH resource configurations may be configured in cells corresponding to different coverage levels. The NPRACH resource configuration is given by periodicity, the repetition number, a starting time, a frequency location, and the number of subcarriers. For example, an NPRACH configuration provided by a higher layer (e.g., RRC) may include the following.
NPRACH resource periodicity, NperiodNPRACH (nprach-Periodicity)
frequency location of the first subcarrier allocated to NPRACH NscoffsetNPRACH (nprach-SubcarrierOffset)
The number of subcarriers allocated to NPRACH), NscNPRACH (nprach-NumSubcarriers) The number of starting sub-carriers allocated to contention based NPRACH random access, Nsc_contNPRACH (nprach-NumCBRA-StartSubcarriers)
The number of NPRACH repetitions per attempt, NrepNPRACH (numRepetitionsPerPreambleAttempt)
NPRACH starting time, NstartNPRACH (nprach-StartTime),
Fraction for calculating starting subcarrier index for the range of NPRACH subcarriers reserved for indication of UE support for multi-tone msg3 transmission NMSG2NPRACH (nprach-SubcarrierMSG3-RangeStart)
NPRACH transmission can start only NstartNPRACH·30720Ts time units after the start of a radio frame fulfilling nf mod(NperiodNPRACH/10)=0. After transmissions of 4·64(TCP+TSEQ) time units, a gap of 40·30720Ts rime units shall be inserted.
NPRACH configurations where NscoffsetNPRACH+NscNPRACH>NscUL are invalid.
The NPRACH starting subcarriers allocated to contention based random access are split in two sets of subcarriers, {0,1, . . . ,Nsc
The frequency location of the NPRACH transmission is constrained within NscRA=12 subcarriers. Frequency hopping shall be used within the 12 subcarriers, where the frequency location of the ith symbol group is given by nscRA(i)=nstart+ñscRA(i) where nstart=NscoffsetNPRACH+└ninit/NscRA┘·NscRA and
where ńSCRA(0)=ninit mod NscRA with ninit being the subcarrier selected by the MAC layer from {0, 1, . . . , NscNPRACH−1}, and the pseudo random sequence c(n) is given by Section 7.2 of GPP TS36.211. The pseudo random sequence generator shall be initialized with Cinit=NIDNcell.
In each NPRACH occurrence, {12, 24, 36, 48} subcarriers may be supported. Further, the random access preamble transmission (i.e., PRACH) may be repeated up to {1, 2, 4, 8, 16, 32, 64, 128} times to enhance coverage.
The contents (3GPP system, frame structure, NB-IoT system, etc.) described above may be applied in combination with methods proposed in the present disclosure to be described below or may be supplemented to clarify technical features of the methods proposed in the present disclosure.
Narrowband (NB)-LTE refers to a system for supporting low complexity and low power consumption with a system bandwidth (system BW) corresponding to 1 Physical Resource Block (PRB) of LTE system. The NB-IoT system may be primarily used as a communication mode for implementing the internet of things (IoT) by supporting a device such as machine-type communication (MTC) in a cellular system.
Narrowband LTE uses orthogonal frequency division multiplexing (OFDM) parameters such as the subcarrier spacing similarly as in the conventional LTE system. In the narrowband LTE, 1 PRB may be allocated for the narrowband LTE in a legacy LTE band without additional band allocation, so there is an advantage in that the frequency may be efficiently used. The downlink physical channel of the narrowband LTE is defined as NPSS/NSSS, NPBCH, NPDCCH/NEPDCCH, NPDSCH, etc. in the case of downlink and is named by adding N in order to distinguish the NB-LTE from the LTE.
For legacy LTE and LTE eMTC, Semi-Persistent Scheduling (SPS) is introduced and used. An initial UE receives SPS configuration setup information through RRC signaling.
When the UE receives SPS activation DCI with SPS-C-RNTI, the UE operates according to the SPS configuration by using information previously received through RRC signaling. Specifically, in the SPS operation of the UE, semi-persistent scheduling configuration information received through the RRC signaling, resource scheduling information included in the corresponding downlink control information (DCI), MCS information, and the like are used.
When the UE receives SPS release DCI with SPS-C-RNTI, the SPS configuration is released. When the UE receives the SPS release DCI with SPS-C-RNTI again, the UE performs the SPS operation similarly as described above.
When the UE receives SPS configuration release information through the RRC signaling after receiving the SPS release DCI with SPS-C-RNTI, the corresponding UE may not detect the downlink control information until receiving the SPS configuration setup information indicating the SPS activation again. The reason is that the corresponding UE does not know an RNTI value related to the SPS configuration (SPS-C-RNTI value).
The SPS basically has the advantage of reducing the DCI overhead of the base station. However, in the narrowband Internet of things (NB-IoT) system, in addition to reducing the downlink control information overhead of the base station, the semi-persistent scheduling (SPS) may be additionally introduced by a method for battery saving and latency reduction of the NB-IoT UE.
Accordingly, the present disclosure proposes a method for maintaining the legacy complexity with a higher layer signal, a signal to be included in the downlink control information, etc., when the semi-persistent scheduling information is introduced in the narrowband Internet of things (NB-IoT) system. An operation required for SPS in each of an idle mode and a connected mode will also be proposed.
In the present disclosure, an expression ‘monitoring the search space’ means a series of processes of decoding the narrowband physical downlink control channel (NPDCCH) as large as a specific region according to the downlink control information (DCI) format to be received through he corresponding search space and then scrambling the corresponding cyclic redundancy check (CRC) with a predetermined specific RNTI value to check whether the corresponding value matches a desired value.
Additionally, since each UE recognizes a single physical resource block (PRB) as each carrier in the narrowband LTE system, the PRB mentioned below in relation to the embodiment of the present disclosure has the same meaning as the carrier.
Referring to
In S1520, the UE in the idle mode transmits uplink data by using the preconfigured uplink resource (PUR). The aforementioned signaling is just an example applied to the present disclosure and the technical spirit of the present disclosure is not limited to each step and description for each step. According to another embodiment, in step S820, the UE in the idle mode may transmit the uplink data again by checking to receive a retransmission instruction after transmitting the uplink data.
Hereinafter, an idle mode operation of a UE in which semi-persistent scheduling is configured will be reviewed.
In regard to a semi-persistent scheduling operation of the UE, the following may be considered. The UE in the idle mode should store an RRC configuration in order to perform the SPS operation.
The operation proposed by the present disclosure may be applied when a specific UE is instructed with suspension of RRC connection in an RRC connected state and the specific UE moves to an RRC_Idle state. For convenience of description, a narrowband Internet of Things (NB-IoT)-based system is mainly described, but the present disclosure may be applied to other systems as well as an eMTC system. Among terms used in connection to the embodiment of the present disclosure, deactivation has an opposite meaning to activation.
A method may be considered in which the SPS configuration is performed through the RRC signaling, and (re)activation/deactivation/retransmission of the SPS operation is performed through signaling or downlink control information (DCI).
Specifically, similarly to the semi-persistent scheduling (SPS) which operates in the connected mode, the SPS configuration may be delivered to be UE-specific through the RRC signaling. Thereafter, the UE detects the DCI or detects a specific signal to be instructed with (re)activation, deactivation, or retransmission related to the SPS operation from the base station.
In this case, the following method may be considered as a detailed method for instructing (re)activation, deactivation, or retransmission by using the downlink control information (DCI).
A method for introducing a new search space for an idle mode SPS operation may be considered.
Specifically, a legacy search space may be maintained and the new search space may be introduced for transmission/reception according to the semi-persistent scheduling (SPS).
The new search space may become a UE specific search space or a common search space. In the case of the common search space, (re)activation, deactivation, or retransmission may be instructed to the UE group.
Hereinafter, the new search space is referred to as a Semi-Persistent Scheduling Search Space (SPS-SS). A search space period, a search space monitoring duration, etc., may be additionally required for a parameter (Rmax, G, alpha offset, etc.) for configuring the legacy search space (SS) as the parameter for the Semi-Persistent Scheduling Search Space (SPS-SS).
The search space period means a period in which the UE should wake up in order to monitor the search space. A start point of the search space period may be a timing at which the SPS configuration is received through the RRC signaling. As another example, the start point may be configured to be separately indicated through the RRC signaling,
An example of a specific operation related to the search space period is as follows. When the search space period is set to 12 hours, the UE in the idle mode may wake up once every 12 hours and monitor the search space at a timing predetermined by Rmax, G, alpha offset, etc.
An example of a specific operation related to the search space monitoring duration is as follows. The UE in the idle mode wakes up every search space period and monitors the semi-persistent scheduling search space (SPS-SS). In this case, the UE may monitor the semi-persistent scheduling search space (SPS-SS) as long as the search space monitoring duration.
The search space monitoring duration may be defined in units of PDCCH period (pp), or defined in units of absolute time (e.g., ms).
As a specific example, when the search space period is set to 12 hours and the search space monitoring duration is set to 10 pp, the UE in the idle mode wakes up every 12 hours and monitors the semi-persistent scheduling search space (SPS-SS) as long as 10 pp and then sleeps again.
When the search space period for the new search space, the search space monitoring duration, etc., are configured, resources for SPS transmission/reception may be determined by configuring an SPS period, an SPS tx/rx duration, etc.
According to an embodiment, the SPS period, the SPS tx/rx duration, etc., may be set independently of the search space period or the search space monitoring duration.
According to another embodiment, there may be a case where any one of the parameter (SPS period and SPS transmission/reception duration) for the SPS transmission and the parameter (search space period and search space monitoring duration) for the new search space is not set. In this case, the remaining values may be set according to the set parameter value.
In addition, the tx/rx duration may be set in the following units. The SPS tx/rx duration may be defined in units of a total repeated transmission number related to how many times the signal should be repeatedly transmitted for transmission of the narrowband physical downlink shared channel (NPDSCH) or narrowband physical uplink shared channel (NPUSCH). As another example, the unit may be defined as an absolute time (e.g., ms).
When the corresponding SPS tx/rx duration is set to the absolute time, the SPS tx/rx operation may be performed as follows by considering an end point of the last subframe (SF). Specifically, the SPS tx/rx operation may be performed when the end point of the last subframe (SF) of the narrowband physical downlink shared channel (NPDSCH) or the narrowband physical uplink shared channel (NPUSCH) to be transmitted (or received) is set.
Embodiment 1-1 will be described below in detail with reference to
Referring to
In
Unlike as illustrated in
In the case of Embodiment 1-1, the search space monitoring number increases as compared with the conventional scheme without the SPS operation, but the idle mode UE need not monitor all search spaces.
A method for adding a specific parameter to the conventional search space (e.g., monitoring window, monitoring period, etc.) may be considered.
Specifically, a method for not introducing the new search space, which is not similar to Embodiment 1-1 may be additionally considered. That is, the search space period, the search space monitoring duration, etc., proposed in Embodiment 1-1 above may be additionally set in the legacy search space (e.g., UE specific search space or common search space).
As compared with Embodiment 1-1, since the new search space is not introduced, new search space information need not be provided through radio resource control (RRC). The remaining operation is similar to the operation in Embodiment 1-1.
The embodiment has an advantage in that the UE in the idle mode need not monitor all search spaces similarly to Embodiment 1-1, but the monitoring number of the search space increases as compared with the conventional scheme without the SPS operation.
A method for sharing the legacy search space may be considered. Specifically, the legacy search space which the legacy NB-IoT UE uses in the idle mode may be used for DCI detection related to the semi-persistent scheduling operation.
As a specific example, the legacy search space such as Type-1 CSS capable of detecting paging or type-1A CSS, type-2A CSS, etc., for Single Cell Point-to-Multipoint (SC-PTM) may be shared to indicate an SPS related operation. That is, the listed search spaces may be used to indicate SPS (re)activation, deactivation, or retransmission in addition to the legacy use.
In applying the embodiment, a DCI payload size may be considered in order to prevent a blind detection number of the UE from increasing. Specifically, the DCI payload size for the SPS operation may be set to be the same as the payload size of the DCI which may be transmitted in each (legacy) search space.
According to the embodiment, the search space monitoring number performed by the UE in the legacy idle mode is maintained. Accordingly, among SPS operation methods utilizing the downlink control information (DCI), this method may be most advantageous in terms of power saving of the UE. However, in the case of the embodiment, since the SPS operation is indicated through the common search space (CSS), there is a characteristic that the SPS operation is indicated not to be UE specific, but to be UE group specific.
A method for additionally indicating (re)activation/deactivation/retransmission through signal detection will be described below in detail with reference to
A method of using a WUS like signal may be considered. A wake up signal for determining whether to monitor the legacy paging search space may be configured to be used as a signal indicating (re)activation, deactivation, or retransmission of the SPS.
Specifically, the type of the legacy wake up signal and parameters such as a root index, a scrambling sequence, etc., are changed and configured to be distinguished from the wake up signal. Furthermore, the corresponding parameters may be configured to be UE specific or UE group specific and configured to indicate the SPS related operation.
Hereinafter, a UE/base station operation related to the wake up signal (WUS) will be described below with reference to
The UE receives, from the base station, the configuration information related to the wake up signal (WUS) through the higher layer signaling. The UE receives the wake up signal from the base station for a configured maximum WUS duration 17A (17B corresponds to Gap).
The wake up signal (WUS) means a signal used for the UE to indicating whether the UE monitors the narrowband physical downlink control channel (NPDCCH) to receive the paging in a specific cell. The wake up signal is associated with one or more paging occasions (PO) according to whether to configure extended DRX.
Operations of the UE and the base station related to reception of a Narrowband wake up signal (NWUS) may be summarized as follows. The following operations may be described or applied in relation to the methods proposed in the present disclosure.
The operation of the base station related to the Narrowband wake up signal (NWUS) is as follows.
The base station generates a sequence for the wake up signal (or used for the wake up signal) in a specific subframe.
The base station maps the generated sequence to at least one resource element (RE). The base station transmits the wake up signal to the UE on the mapped resource element. The at least one resource element (RE) may mean at least one of a time resource, a frequency resource, or an antenna port.
The operation of the UE related to the Narrowband wake up signal (NWUS) is as follows.
The UE receives the wake up signal (WUS) from the base station. Alternatively, the UE may assume that the wake up signal (WUS) is transmitted from the base station on a specific resource element (RE).
The UE may check (or determine) whether to receive the paging based on the received wake up signal.
When the paging is transmitted, the UE receives the paging based on a paging reception related operation and performs a procedure of transitioning from the RRC idle mode to the RRC connected mode.
A method similar to an operation according to type 1 configured grant may be considered. That is, transmitting the SPS configuration to be UE specific through the RRC signaling is the same as in Embodiment 1, but (re)activation or (re)configuration is indicated through the RRC signaling.
The embodiment has a largest difference from Embodiment 1 in that since the SPS operation (activation, configuration, etc.) is indicated through the RRC signaling, the search space need not be monitored to indicate the SPS operation.
Information included in the SPS configuration (or SPS reconfiguration) may include at least one of the following information. Specifically, the information included in the SPS configuration may include at least one of an SPS interval, HARQ number for the SPS operation ((# of HARQ for SPS), a modulation coding scheme (MCS) to be included in DL/UL grant (i.e., DCI formats N0 and N1 with C-RNTI), a resource unit (RU), resource assignment, the repetition number, and the like.
According to an embodiment, when the UE is instructed with the SPS configuration (or SPS reconfiguration) through the RRC signaling, the corresponding operation may be configured to immediately indicate activation (or reactivation). According to another embodiment, when the UE may be instructed with the SPS configuration (or SPS reconfiguration) through the RRC signaling and then the corresponding UE may configure the corresponding semi-persistent scheduling (SPS) to be activated (or reactivated) at the moment of moving to the RRC idle state.
A UE in which the SPS configuration is activated may return to the RRC connected state and perform the SPS tx/rx operation until receiving a release instruction from the base station. Specifically, until receiving the release of the SPS configuration from the base station through the RRC signaling, the UE may assume that the configured grant is valid and perform the SPS tx/rx operation.
In order for the UE to assume that the configured grant is valid, the following may be premised. Specifically, it may be premised that the timing advance (TA) is valid at the time of transmission/reception in order for the configured grant to be valid. As a result, the UE may determine whether the timing advance (TA) is valid at the time of transmission/reception is valid in order to determine the validity of the configured grant.
According to the embodiment, since the downlink control information (DCI) need not be monitored for the SPS operation, battery saving of the UE may be achieved.
However, once the semi-persistent scheduling (SPS) is configured in the connected mode, the UE is continuously in an activation state in the idle mode. Therefore, in order for the base station to reconfigure, deactivate, or release the corresponding semi-persistent scheduling (SPS), the UE needs to be switched to the connected mode state again.
Additionally, the retransmission operation when using this method can be divided into detailed proposal methods as follows.
Hereinafter, embodiments related to the retransmission operation will be described.
A method for configuring SPS retransmission not to be performed in the RRC idle state may be considered.
Specifically, a reception success probability of communication using the resource configured through the RRC signaling may be configured to be high. The UE may be configured to perform transmission/reception through the corresponding resource and not perform the retransmission operation.
In order to increase the reception success probability, a repetition scheme introduced in NR may be applied in addition to the repetition used previously.
Specifically, for a repetition number R indicating the number of repeated transmissions of the narrowband physical downlink/uplink shared channel (NPDSCH/NPUSCH), the UE performs repeated transmission using a fixed Redundancy Version (RV) value. Here, by using RV values and R2 additionally indicated through the RRC signaling, the UE may be configured to perform transmission/reception repeatedly. R2 represents a value indicating how many times the RV value is changed and additionally transmitted.
For example, it is assumed that R set through the RRC signaling for uplink semi-persistent scheduling (UL SPS) is 16, the RV value is {0, 2, 3, 1}, and R2 indicates 4. According to the set values, the UE repeatedly performs transmission 16 times for each RV value, and performs such an operation 4 times while changing the RV value.
More specifically, the UE sets the initial RV value to 0 and repeatedly transmits NPUSCH 16 times, and then repeatedly transmits the NPUSCH 16 times by setting the RV to 2. The UE performs repeated transmissions 16 times even for each of RV 3 and RV 1, and then performs an operation according to the legacy idle mode until the next SPS resource exists.
Since the UE is configured to perform retransmission in the idle mode, the base station should use a paging signal to request retransmission of UL data or retransmit downlink data to the UE. Specifically, the base station resumes the RRC connection by transmitting the paging to the UE which is in the idle mode due to the RRC connection which is suspended. The base station may schedule the retransmission using a dynamic grant for the UE switched to the connected mode.
Additionally, the base station may instruct SPS deactivation (or release or reconfiguration) to a UE in which SPS transmission/reception is activated using a paging narrowband physical downlink shared channel (paging NPDSCH). In this case, a UE in which SPS transmission/reception is activated through the RRC signaling may perform deactivation, release, or reconfiguration of the semi-persistent scheduling (SPS) in the idle mode. That is, there is a battery saving effect in that the UE may perform the SPS operation without being switched to the connected mode.
A method for indicating SPS retransmission through downlink control information (DCI) or signaling may be considered. Specifically, a method for indicating the SPS operation through downlink control information (or signaling) may be applied only to the SPS retransmission.
Since the downlink control information (or signaling) indicates only retransmission, compact DCI having a small payload size may be configured to be used. A resource for retransmission may be configured to be indicated together with the SPS configuration through the RRC signaling.
In the embodiment, although the UE should monitor the search space, there is an advantage that the base station may dynamically schedule the SPS retransmission.
A method for transmitting the SPS configuration through the RRC signaling and indicating the SPS operation (activation/deactivation/retransmission) using the paging narrowband physical downlink shared channel (paging NPDSCH) may be considered.
In the case of Embodiment 1 above, the SPS operation is indicated through the downlink control information (DCI). Therefore, the base station may dynamically indicate (re)activation, deactivation, or retransmission. However, a search space that should be monitored by a legacy idle mode UE increases.
In Embodiment 2 above, since the SPS operation is indicated through the RRC signaling, the search space monitored by the idle mode UE does not increase. However, in order to perform deactivation (or release), RRC signaling should be performed after switching the UE in the idle mode to the connected mode.
In the case of the embodiment, an SPS related parameter is configured through the RRC signaling, and the SPS operation is indicated by using the paging narrowband physical downlink shared channel (paging NPDSCH). Specifically, by including the SPS uplink/downlink grant (UL/DL grant) in the payload of the paging narrowband physical downlink shared channel, (re)activation, deactivation, or retransmission may be indicated through the SPS uplink/downlink grant (UL/DL grant).
The uplink/downlink grant (UL/DL grant) included in the paging narrowband physical downlink shared channel (NPDSCH) may be configured to be UE specific.
The following method may be considered in order to configure the uplink/downlink (UL/DL) grant. As an example, the UE may be configured to receive a new UE specific ID from the base station through the RRC signaling. As another example, the UE may be configured to use resumeIdentity which is a parameter which the UE already has.
The configuration of a validation field for confirming that the uplink/downlink grant (UL/DL grant) indicates (re)activation or deactivation may be made similarly to the LTE or eMTC system. Retransmission may be indicated by setting a new data indicator (NDI) value to 1.
According to the embodiment, the number of search spaces to be monitored by the UE in the idle mode does not increase compared to the number of search spaces monitored by a legacy idle mode UE. This means that a battery usage does not increase while supporting the SPS operation. In addition, the base station may dynamically instruct (re)activation, deactivation, or retransmission, and the UE need not switch to the connected mode to receive the corresponding indication.
A method for additionally utilizing a common search space (e.g., Type1-CSS, Type1A-CSS) in order to indicate the SPS operation of (re)activation, deactivation, or retransmission may be considered.
Embodiment 3 described above indicates SPS (re)activation, deactivation, or retransmission by using only the payload of the NPDSCH, but in the case of the embodiment, a search space in which the downlink control information for scheduling the NPDSCH is transmitted is additionally utilized
In a corresponding search space, candidates of the NPDCCH used for the original purpose and candidates of the NPDCCH indicating the SPS operation may be configured not to overlap. This is to prevent an influence on the legacy UE.
Specifically, the narrowband physical downlink control channel (NPDCCH) candidates in which the downlink control information for indicating the SPS operation is transmitted may be configured to be transmitted not to overlap with the narrowband physical downlink control channel (NPDCCH) candidates according to the type 1-common search space (Type1-CSS or Type1A-CSS).
In order for the base station to simultaneously transmit legacy downlink control information (legacy DCI) and downlink control information for SPS indication, the maximum repetition number (Rmax) of both downlink control information may be set to be large and the repetition number may be set to a small value.
Furthermore, the base station indicates a fake repetition different from an actual repetition number value to a field indicating a legacy DCI repetition number to control to control a start timing of the legacy physical downlink shared channel (NPDSCH).
Through such a configuration, the UE may monitor the downlink control information indicating the SPS operation between the legacy downlink control information (legacy DCI) and the legacy physical downlink shared channel (legacy NPDSCH). The RNTI value for monitoring for the downlink control information indicating the SPS operation may be set through the RRC signaling to be UE specific (or UE group specific).
A method for using a paging occasion or a new indication parameter in order to indicate the SPS operation such as (re)activation, deactivation, or retransmission may be considered.
When the SPS operation is indicated by reusing the legacy common search space (CSS) as in Embodiment 3-1 above, another UE may also wake up in addition to the UE that uses the preconfigured UL resource (PUR).
In the case of this embodiment, a PUR paging opportunity (PPO) is configured so that the base station may indicate the SPS operation only to the terminals using the PUR. The PUR paging opportunity (PPO) may be broadcast through system information. The UE may indicate the SPS operation such as activation/deactivation/retransmission through the PUR paging opportunity (PPO).
The UE may be configured to monitor both a paging opportunity (PO) and a PUR paging opportunity (PPO) for a legacy paging procedure. Only one of the paging opportunity (PO) and the PUR paging opportunity (PPO) may be considered from the viewpoint of battery saving.
Specifically, a UE capable of using the aging opportunity (PO) and the PUR paging opportunity (PPO) may be configured to perform the legacy paging procedure by using the PUR paging opportunity (PPO). Since the base station knows, in advance, which UE uses the PUR based on a non-contention-based SPS resource (PUR), a legacy paging signal for the corresponding UE may also be configured through the PUR Paging Opportunity (PPO).
According to an embodiment, the PUR paging opportunity (PPO) may be applied to be replaced by the wake up signal. That is, only a UE to which the PUR is allocated may be configured to monitor the paging by using a Group Wise Wake UP signal for waking up the UE to which the PUR is allocated.
According to another embodiment, a wake up signal for waking up the UE in which the PUR is configured may be configured to exist in front of the PUR paging opportunity (PPO). The base station may inform the UE that paging containing activation/deactivation/retransmission, etc., through the corresponding wake up signal is delivered.
By a different scheme from the paging occasion, a system information change notification which may be recognized only by the UEs using the PUR may be added or a system information channel monitored by the UEs using the PUR may be configured. The methods may also wake up only the UE using the PUR as proposed above.
The paging opportunity (or the SI Change Notification or SI Channel) may be configured differently depending on the PUR type. That is, a paging occasion configuration or resource may be different according to the PUR type used by the UE. When a part or the entirety of the downlink channel for monitoring the PUR overlaps with the system information, the UE may configure the monitoring DL channel for the PUR to be prioritized. In this case, since the UE performs the SPS operation for the PUR in the idle mode, it may be preferable to first confirm the monitoring DL channel for the PUR and confirm the system information in a next period.
Hereinafter, a RACH procedure will be described with reference to
A method for utilizing the RACH procedure in relation to the preconfigured resource (PUR) for the SPS operation may be considered. It is preferable that used power of a UE entering the RRC idle state is minimized. However, in this case, an oscillator drift of the UE occurs, and as a result, it may be difficult to ensure the timing advance (TA).
Therefore, when a method in which the timing advance (TA) is ensured while the UE periodically does not consume power is considered, the PUR may be used based on the RACH procedure as illustrated in
Hereinafter, it will be described in detail according to a time sequence.
The base station may configure a resource that may perform an idle mode semi-persistent scheduling request (IM-SPS request) in the UE.
A narrow physical random access channel (NPRACH) for triggering IM-SPS may be indicated to UEs which receive the SPS configuration in the RRC connected state and move to the RRC idle state. The NPRACH preamble may be delivered to the UE through the system information block (SIB) or RRC signaling.
The NPRACH preamble may be configured to be indicated through one of a contention based random access (CBRA) or contention free random access (CFRA) resource. In this case, it may be preferable that the NPRACH preamble is indicated through the CFRA resource without a contention process in order reduce power consumption of the UE.
The CFRA resource may be indicated to be UE specific through the RRC signaling. NPRACH resource related parameters (period, repetition number or CE level, PRB index, etc.) may also be configured to be delivered together.
The UE that is indicated with one of the CFRA resources transmits the corresponding NPRACH preamble to request the IM-SPS (IM-SPS request). The base station may accept the IM-SPS request through a preamble response message (MSG2). A Transport Block Size (TBS) required for the UE may follow a similar structure to Early Data Transmission (EDT) or may be configured according to a request from the UE in the RRC connected state.
A UE that does not receive the SPS configuration in the RRC connected state may be configured to trigger the IM-SPS in the RRC idle state. Specifically, the base station may indicate the NPRACH preamble for triggering the IM-SPS through an SIB (e.g., SIB-NB, SIB22-NB, etc.). The NPRACH preamble may be configured to be indicated as one of the CBRA resources. The NPRACH resource related parameters (period, repetition number (or CE level), PRB index, etc.) may also be delivered together through the system information block (SIB).
When the UE that is indicated with one of the CBRA resources requests the IM-SPS by transmitting the corresponding NPRACH preamble, the base station may accept the IM-SPS request through MSG4. The UE may request the SPS period, the TBS, etc., through MSG3.
The base station that accepts the trigger of the IM-SPS of the UE may indicate parameters related to the IM-SPS to the corresponding UE. The parameters related to the IM-SPS may include at least one of timing advance (TA), transmission power control (TPC), radio network temporary identifier (RNTI), duration, periodicity, TBS, resource allocation (RA), and repetition.
The UE that receives the IM-SPS related parameters may transmit uplink data within a valid transmission interval or as large as a valid transmission number. When transmitting the last NPUSCH of the transmission period, the UE may indicate that the corresponding transmission is the last transmission. The base station may determine that the corresponding IM-SPS is terminated according to the indication.
When the base station receives the indication for the last transmission, the base station may be configured to give a feedback to the corresponding UE. In addition, when uplink transmission skipping (UL skipping) is allowed in the transmission interval according to the IM-SPS, if the uplink transmission (UL skipping) occurs as large as a number indicated by the base station, the IM-SPS may be configured to be implicitly released. The base station may be configured to implicitly indicate the release of the IM-SPS. The base station may be configured to perform an HARQ-feedback and the corresponding HARQ-feedback may be indicated together with explicit release.
When the uplink transmission skipping is allowed, the base station may be configured to inform the number of NPUSCHs actually transmitted from the UE. An ACK/NACK may be configured to be indicated in the form of a bitmap for each corresponding NPUSCH.
When the UE is indicated with the NACK, the UE may perform retransmission even though the IM-SPS transmission interval ends and may additionally notify the timing advance (TA) or transmission power control (TPC) value while indicating the NACK. As another method, the NPUSCH in which the NACK occurs may be configured to be retransmitted in a next SPS interval.
When the UE determines that there is no uplink to be transmitted in spite of being indicated with the resource that may trigger the IM-SPS, the corresponding NPRACH preamble may be configured not to be transmitted. As another method, when the UE is indicated with the resource that may trigger the IM-SPS, the UE may be configured to perform the IM-SPS request and performs IM-SPS transmission first once, and then be indicated with a back-off parameter through a feedback channel or signal from the base station and determine a time at which the IM-SPS request may be transmitted next.
An item which may be commonly applied to the aforementioned embodiments will be described below in detail.
In the aforementioned embodiments, collision handling may be additionally considered. In this regard, when the SPS related operation collides with the legacy operation, the UE may operate by giving a priority to any one of both operations.
When an operation related to a predetermined region or data which may exert a large influence on the system of the UE collides with the SPS related operation, the UE may be configured to operate by giving the priority to the operation related to the preconfigured region or data.
According to an embodiment, the preconfigured region or data may be related to at least one of the paging or the RACH procedure.
Specifically, when an operation related to data transmitted in relation to the SPS or the SPS-SS partially or totally overlaps with the operation related to the preconfigured region or data in terms of the time or frequency, the UE may operate by giving the priority to the operation related to the preconfigured region or data.
Data transmitted in relation to the SPS may be a narrowband physical downlink/downlink shared channel (SPS NPDSCH/NPUSCH) or a narrowband physical downlink control channel (NPDCCH) indicting the SPS operation such as activation/deactivation/retransmission.
The preconfigured region or data may be at least any one of a region in which the wake up signal WUS may be transmitted, the paging narrowband physical downlink shared channel (NPDSCH), or and a type-1 common search space (CS S) in which the narrowband physical downlink control channel (NPDCCH) for scheduling the paging NPDSCH.
Since monitoring the paging by the idle mode UE is important to the operation of the entire system, the preconfigured region or data may be configured to have a higher priority to the data or search space (i.e., SPS NPDSCH/NPUSCH or SPS SS) related to the SPS transmission.
When even the entirety or a part of the preconfigured region or data overlaps with the data transmitted in relation to the SPS or the semi-persistent scheduling search space (SPS-SS) on the time or frequency, the UE may be configured not to transmit/receive the data related to the SPS operation.
A priority for the collision handling may be equally applied between the RACH procedure and the SPS transmission. The preconfigured region or data may include at least one of an NPRACH resource that should transmit the NPRACH preamble or type-2 common search space (CSS) in which an NPDCCH for scheduling an NPDSCH to which a random access response (RAR) grant is to be transmitted may be transmitted.
In relation to the operation according to the priority, the UE may be configured to postpone transmission of the corresponding data rather than drop the data related to the SPS operation according to the priority. The corresponding operation may be applied to a UE which may receive an indication of early termination from the base station.
That is, when the NPUSCH transmission overlaps with the paging search space, the UE temporarily stops the NPUSCH transmission according to the SPS configuration. In a state in which the NPUSCH transmission is stopped, the UE determines whether the early termination is made by monitoring the paging search space. When the UE receives the early termination, the UE may stop the NPUSCH transmission and when the UE does not receive the indication of the early termination, the UE may perform the remaining NPUSCH transmission according to the SPS configuration.
In the aforementioned embodiments, a method for controlling the timing advance (TA) or power through the retransmission may be considered.
Specifically, in relation to the embodiments considering the SPS retransmission, the timing advance (TA) control and the power control may be configured to be performed through retransmission.
A method for gradually increasing transmission (tx) power according to a retransmission number indicated by the base station for the timing advance (TA) or transmission (tx) power control from the viewpoint of the uplink semi-persistent scheduling (UL SPS) may be considered. When the retransmission number reaches the maximum retransmission number, the UE may determine that there is a problem in the timing advance (TA) or transmission (tx) power. As a result, the UE may transmit an RRC connection resume request message to the base station in order to move to the RRC connected state.
According to an embodiment, when the retransmission number reaches the maximum retransmission number, the corresponding SPS configuration may be configured to be implicitly deactivated (or released).
According to an embodiment, when the base station intends to indicate retransmission for the preconfigured uplink resource (PUR) for the SPS operation through a downlink channel or signal, the base station may be configured to additionally indicate the timing advance (TA) or transmission power (TP) value together with parameters for retransmission. That is, since the timing advance (TA) is wrong, before the UE performs a procedure for tracking, the base station indicates the timing advance (TA) or transmission power (TP) value in advance to contribute the battery saving of the UE.
According to another embodiment, the RACH procedure may be used to control the timing advance (TA) and the power for the idle mode SPS operation. Specifically, when SPS transmission/reception is performed at a set number of times or a predetermined number of times or a specific time has elapsed, the UE may be configured to receive confirmation from the base station so as to continuously use the corresponding SPS transmission/reception by transmitting the NPRACH preamble and receiving the random access response (RAR).
The base station may configure the NPRACH preamble for SPS confirmation. When the base station receives the NPRACH preamble for the SPS confirmation, the base station may deliver Random Access Preamble Identifier (RAPID) and timing advance (TA) values to the UE or explicitly deliver a confirm message.
The base station may indicate an RACH carrier and a CE level for performing the SPS confirmation to the UE through SIB-NB (e.g., SIB2-NB or SIB22-NB). When there is a limit in a part for dividing the NPRACH preamble for the SPS confirmation, MSG3 may be configured to be scrambled to Semi-persistent Cell RNTI (SPS-C-RNTI) instead of Temporary Cell RNTI (TC-RNTI).
When there is a feedback channel for TA tracking, the UE may acquire the timing advance TA again according to a preconfigured condition.
Specifically, 1) when the timing advance (TA) value is out of a specific range or corresponds to a specific value, 2) when the base station indicates retransmission of a specific number of times or more, 3) a timer for TA tracking expires, the UE performing the SPS transmission/reception in any one of the above 1) to 3) may obtain the timing advance (TA) again by performing the RACH procedure.
In the RACH procedure for acquiring the timing advance (TA) again, MSG3 may include information indicating that the MSG3 is transmitted for TA update. The UE may receive the ACK from the base station through MSG4 and terminate the RACH procedure or receive an indication for idle mode SPS reconfiguration/release from the base station.
When the random access procedure (RA) is triggered in the feedback channel for TA tracking, a dedicated resource to be used for MSG1 may be designated to the UE and UE-ID to be used in MSG3 may be indicated.
When there is a TA valid window based on the timer for TA tracking, if the timing advance (TA) is acquired again by using the RACH procedure (e.g., early data transmission) until the corresponding timer expires, the time of the corresponding timer may increase or the corresponding timer may be configured to be reset.
A UE that is configured with the idle mode SPS may transmit information indicating the operation for TA update instead of transmitting uplink (UL) data through early data transmission (EDT).
The UE that receives the SPS configuration in the idle mode may be instructed to perform the RACH procedure for TA tracking. To this end, the base station may transmit, to the UE, configuration information (e.g., NPRACH preamble index, CE level, preamble transmission carrier, RAR carrier, RNTI value, EDT timer, etc.) for the RACH procedure together with the SPS configuration.
The UE that receives the SPS configuration in the idle mode as described above may be configured to perform the SPS transmission/reception at a period according to the SPS configuration and then perform the RACH procedure (e.g., EDT) at a specific period. The RACH procedure may be configured to be additionally performed at a time when the semi-persistent scheduling (SPS) resource and the NPRACH resource collide with each other.
When there is no feedback channel for TA tracking, if the base station determines that the timing advance (TA) value exceeds a specific range or corresponds to a specific value, the base station may indicate a narrowband physical downlink control channel (NPDCCH) order based RACH procedure.
In terms of the uplink semi-persistent scheduling (UL SPS), the base station may be configured to determine the timing advance (TA) by configuring the UE to continuously transmit minimum data (e.g., SRS, etc.) without an uplink transmission skipping (UL skipping) operation.
Even though the uplink transmission skipping (UL skipping) is indicated, the UE may be configured not to allow the uplink transmission skipping in order to perform the TA tracking at a specific period. In order for the UE in the idle mode to receive the indication for the aforementioned operation, downlink control information indicating the NPDCCH order may be transmitted even in the common search space (e.g., Type1-CSS, Type1A-CSS, or Type2A-CSS).
Additionally, a configuration (e.g., MSG1 dedicated resource, UE-ID, RNTI value, etc.) for NPRACH trigger may be together included at the time of the idle mode SPS configuration. An MSG1 resource may be implicitly mapped according to a specific location of the semi-persistent scheduling (SPS) resource configured through the RRC signaling and the contention based random access (CBRA) may be performed in spite of the NPDCCH order based NPRACH.
While the RACH procedure for TA update is being performed, the SPS configuration indicated by the RRC may be considered invalid until it is confirmed that the timing advance (TA) is valid and the UE may not perform the corresponding transmission/reception operation.
Additionally, the UE that is instructed with the UL idle mode SPS may transmit a preconfigured specific signal for the TA tracking even though the uplink transmission skipping according to the UL SPS is enabled. According to an embodiment, the preconfigured specific signal may be transmitted in the SPS resource specified by at least any one of a specific period, a specific interval, or a specific number. As an example, in N-th uplink transmission according to the SPS resource, the preconfigured specific signal may be transmitted for the TA tracking.
According to an embodiment, the preconfigured specific signal may be an uplink demodulation reference signal (UL DMRS) or a narrowband physical random access (NPRACH) preamble. However, although not limited thereto, the preconfigured specific signal may be another type of uplink signal specifically indicated to be UE specific by the base station.
In regard to the TA feedback, the UE may detect downlink control information scrambled with an RNTI value defined based on the location of the time and/or frequency of uplink semi-persistent scheduling (UL SPS resource). The TA feedback of the UE may be performed by being divided into a UE ID in the MAC of a narrowband physical downlink shared channel payload (NPDSCH payload) scheduled by the corresponding downlink control information.
In this case, the downlink control information may be transmitted together in a search space indicating (re)activation/deactivation of the SPS configuration. In order to prevent an increase in the number of blind detection (BD) times, the payload size of the downlink control information may be adjusted to be the same as the payload size according to the search space through zero padding.
According to an embodiment, the UE may be configured to monitor (or detect) a downlink channel or signal for TA tracking.
Specifically, the UE may be configured to monitor specific downlink control information of the NPDCCH search space for TA tracking, or detect at least one signal of a Narrowband Reference Signal ( ), a Narrowband Primary Synchronization Signal (NPSS), a Narrowband Secondary Synchronization Signal (NSSS), or a Wake Up Signal (WUS).
The SPS resource may be used to control the timing advance (TA) and the power for the idle mode SPS operation.
Specifically, the UE may transmit a TA validity request or a Tx power control request to the base station through the configured resource. The base station may update the corresponding information through a feedback channel.
When TA update or power control is performed through the above configuration, a resource for TA update or Transmission Power control (TPC) need not be separately configured.
In the following description, both the TA and the TPC may be interpreted as TA update and/or TPC update.
According to an embodiment, MSG1 for requesting the TA update and the Tx power control may be transmitted by configuring a resource of a longer period than that of the configured semi-persistent scheduling resource.
The resource through which the corresponding MSG1 is transmitted may be a part of the configured semi-persistent scheduling (SPS) resource or a resource for Early Data Transmission (EDT). The base station may configure dedicated MSG1 for requesting the TA update and the Tx power control in the UE.
As the timing advance (TA) value used when transmitting the corresponding MSG1, a latest timing advance (TA) value may be configured to be used. The UE transmitting the MSG1 may be configured to monitor the random access response message (RAR) to receive only timing advance (TA) command information of the RAR and ignore the uplink (UL) grant for the remaining MSG3 transmission.
When the UE transmits MSG1 for requesting the control of the timing advance (TA) and the power as described above and the base station confirms that transmission of the MSG1, the base station may be configured to transmit a Tx power command to a UL grant location of the RAR. In addition, information included in MSG2 which is a response to MSG1 used for the purpose may be configured in a different format or interpreted differently from MSG2 in the legacy random access process. Alternatively, based on the delivered MSG2 information (e.g., TA and/or TPC), when there is data to be transmitted to the SPS resource, the UE may send the corresponding data and when there is no data, the UE may inform the base station that the MSG2 information is well received by transmitting dummy data.
As another method, the UE that receives the random access response message (RAR) receives the timing advance (TA) command and an MSG3 uplink (UL) grant to continuously use the configured semi-persistent scheduling (SPS) resource (for example, a timer meaning an interval in which the SPS resource is valid) after transmitting the MSG3 and receiving the MSG4. The MSG4 may reconfigure the semi-persistent scheduling (SPS) resource (for example, a timer reset meaning the interval in which the SPS resource is valid may be performed at the time of receiving the MSG4).
Hereinafter, a method for determining the validity of the timing advance (TA) value of the UE will be described in detail.
A TA validity confirmation algorithm for determining the validity of the timing advance (TA) value which the corresponding UE currently has at a timing when the UE which intends to transmit the uplink data through the preconfigured UL resource (PUR) for the SPS operation or according to a period configured by the base station, or according to a preconfigured period may be performed.
The TA validity confirmation algorithm may be constituted by AND operations of various determination criteria including TA validity timer, Narrowband Reference Signal Received Power ((N)RSRP) detection, Time Difference of Arrival (TDoA), and the like. That is, when all determination criterions included in the corresponding algorithm are positive (or mean that there is no problem), it may be determined that the timing advance (TA) value of the corresponding UE is valid.
The base station may independently set thresholds of respective determination criteria. A case where a TA validity timer and a narrowband reference signal reception power (NRSRP) level are included in the validity confirmation algorithm will be described below in detail as an example.
It is assumed that the base station indicates 10 min with the TA validity timer value and X dBm with the narrowband reference signal reception power (NRSRP) level in relation to each threshold. When the current TA validity timer does not currently expire and the narrowband reference signal reception power (NRSRP) level is equal to or more than X dBm at the corresponding timing, the UE may determine that the current timing advance (TA) value is valid. The UE may transmit the uplink data in the PUR according to the corresponding determination result.
In relation to the start time of the TA validity timer, when the UE enters an idle mode for the first time after being configured from the base station, the TA validity timer may start a count. As another example, the TA validity timer may (re)start when the valid timing advance (TA) value is received from the base station through an immediate previous TA update procedure (e.g., RACH, EDT, etc.).
Since an operation of measuring the NRSRP each time the TA validity confirmation algorithm is performed is not beneficial in terms of the power saving of the UE, an NRSRP measurement period may be introduced. It may be configured that the UE is configured to be configured with the NRSRP measurement period from the base station and measures the NRSRP according to the corresponding period to apply a comparison result with a threshold configured from the base station to the TA validity confirmation algorithm.
In this case, a period in which the TA validity confirmation algorithm is performed and a period in which the NRSRP is measured may be independent of each other. Therefore, except for the period in which the TA validation algorithm is performed, when the UE determines that the current UE's NRSRP value is less than the threshold in the NRSRP measurement period, the UE may immediately determine that the current timing advance (TA) of the corresponding UE is invalid. The UE may attempt the TA update according to the corresponding determination result.
When the timing advance (TA) is invalid, the UE may not transmit the uplink data in a subsequent PUR. Alternatively, when the timing advance (TA) is invalid, it may be configured that the subsequent PUR is also invalid.
Thereafter, when the timing advance (TA) becomes valid through the TA update, the UE may transmit the uplink data in the PUR after the corresponding timing. Further, when the timing advance (TA) is valid, it may be configured that the subsequent PUR is also valid.
The base station may independently configure the PUR for each type. The type of PUR may include at least one of a Dedicated PUR, a Contention free shared PUR, or a Contention based shared PUR. The PUR for each type may be defined to be cell specific and/or CE-level specific.
As a method which may perform the TA update by using only two steps (e.g., MSG1 and MSG2 or NPUSCH and NPDCCH+NPDSCH) other than the legacy RACH procedure or EDT procedure for the TA update, the following method may be considered.
Method 1: The timing advance (TA) may be updated by using only MSG1 and MSG2.
The method may be applied to the contention free based PUR (e.g., dedicated PUR) and the contention free shared PUR. The base station may allocate a specific NPRACH resource and an NPRACH preamble for performing the TA update to be UE specific. The specific NPRACH resource may be specified by at least one of a carrier index, a period, a starting offset, a resource subcarrier number, or a repetition number.
A dedicated NPRACH resource for the TA update of the UE using the PUR may be limited to be used only in an NPRACH resource configured in a specific relationship with a PUR period. Further, NPRACH preamble transmission for the TA update may be allowed only in a preconfigured NPRACH resource.
The NPRACH preamble for the TA update is preferably a preamble for the contention based random access (CBRA). The reason is that ambiguity does not occur in the base station operation only when the UE that transmits the corresponding preamble should be one specific UE designated by the base station. Therefore, the base station may know which UE transmits the preamble through a preamble index in advance. When the base station detects the corresponding preamble index, the base station may update the TA value for the corresponding UE through the random access response (RAR).
According to an embodiment, since the base station knows that the corresponding UE transmits the NPRACH preamble for the TA update, the base station may be configured not to transmit the UL grant for the random access response (RAR).
Additionally, the base station may transmit the RNTI value configured to be used for the PUR to the corresponding UE once more for the confirmation operation. The base station may exchange the RNTI value configured to be used for the PUR through the corresponding random access response (RAR). When the UE need not perform MSG3 and MSG4 procedure operations in such a configuration, an advantage may be obtained in terms of a battery life.
However, the number of NPRACH resources to be configured in advance by the base station may increase. The base station should be able to share legacy NPRACH resources that do not additionally allocate the NPRACH resource for the TA update and in this case, the NPRACH preamble resources may be significantly insufficient.
In the method, since the base station configures a lot of NPRACH resources for updating the timing advance (TA) of the UE for the PUR transmission, overload is large in terms of resource utilization.
Method 1-1: As a method for solving the overload in the aforementioned resource utilization, a method for configuring the NPRACH preamble to be transmitted in the PUR will be described below.
A detailed example is described below. It is assumed that the base station is configured to use 3.75 kHz subcarrier spacing single tones #k to #k+11 for dedicated PUR transmission in 12 different UEs, respectively. The period for the TA update may be set to a period that is N times larger than the period of the dedicated PUR set by the base station. 12 different UEs transmit different NPRACH preambles configured from the base station in the PUR positioned in the TA update period to update the TA. As another example, it is assumed that the base station is configured to use 15 kHz subcarrier spacing single tones #k to #k+2 for dedicated PUR transmission in 3 different UEs, respectively. Similarly, 3 different UEs transmit different NPRACH preambles configured from the base station in the PUR positioned in the TA update period to update the TA. Since one of the PURs is used as the NPRACH resource for the TA update in such a configuration, there is an advantage in that a burden of the NPRACH resource which should be configured in advance by the base station is reduced.
However, the following items should be considered in order to update the TA through the second method.
First, all of time domain sizes of the PURs of the UEs configured back-to-back should be the same as each other. An example of the time domain size may be a repetition number.
Second, the corresponding UEs should update the timing advance (TA) at the same period. The corresponding method may be used even in the contention free based shared (CFS) PUR in addition to the dedicated PUR.
Method 2: A method for transmitting a known sequence in the PUR may be considered.
When the timing advance (TA) is updated by using the NPRACH preamble, there is an advantage that a timing advance (TA) in a range such as an initial access procedure may be estimated. When the timing advance (TA) of the UE using the PUR becomes invalid, it is determined that the TA may be updated to the extent of TA tracking in most cases. Therefore, it may be configured that the base station and the UE transmit the known sequence known thereby to the PUR instead of the NPRACH preamble to perform the TA update. In this case, the known sequence may be a QAM type signal, the DMRS sequence may be mapped in an order indicated in advance by the base station, and the DMRS sequence may be an RACH sequence (in the case of eMTC). There is an advantage in that the base station need not additionally allocate/spare the NPRACH resource for the PUR UE. However, the range of the TA which may be estimated may be limited to a cyclic prefix (CP) length of the NPUSCH.
Additionally, the proposed TA update methods may be configured to be performed when the timing advance (TA) of the corresponding UE is invalid, but when it is predicted that the timing advance (TA) will become invalid before next PUR transmission, the UE may be configured to perform the TA update in the TA update resource configured at the timing before the corresponding PUR. The base station may transmit only the TA command in the form of MAC CE in response to the corresponding information. Thereafter, the UE may operate to report to the UE that the timing advance (TA) of the UE is updated as much as the corresponding TA command through an initial PUR transmitted by applying the corresponding TA command.
The following cases may be considered as an algorithm that may predict that the timing advance (TA) of the corresponding terminal will be invalid before the next PUR transmission. As an example, when an NACK for PUR transmission is received (continuously) at a specific number of time (e.g., X times) (or Y % within a specific interval) or more, it may be predicted that the timing advance (TA) will become invalid. As another example, when an ACK for PUR transmission is not received (continuously) at a specific number of time (e.g., X times) (or Y % within a specific interval) or more, it may be predicted that the timing advance (TA) will become invalid.
This may also be a case where the UE directly determines when the TA validity timer expires know thereby and the TA validity timer expires before the next PUR. Furthermore, this may also be a case where the base station directly receives an indication that the timing advance (TA) of the corresponding UE is invalid through a physical channel such as the feedback channel from the UE.
Additionally, in a UE that is configured to use a TA update method not using the NPRACH preamble, the TA update may not be easy when the timing advance (TA) is actually changed a lot for any reason. Therefore, in order to supplement such a disadvantage, the UE that is configured to use the TA update method not using the NPRACH preamble may be configured to perform the TA update method using the NPRACH preamble when the timing advance (TA) is not updated within a specific threshold (e.g., timing window, number of attempts, etc.).
As an example, when the UE that performs the TA update through a method for transmitting a known to the PUR fails to update the timing advance (TA) while attempting the TA update N times, the base station may be configured to perform the TA update by using a preconfigured TA update dedicated NPRACH preamble. When such a method is used, the TA update may be attempted through the PUR and the TA may be actually updated, and as a result, an NPRACH preamble for the TA update may be configured at a larger period than the methods using the NPRACH preamble among the methods proposed as above.
Even in any method, when the UE is updated with a valid timing advance (TA) through the TA update, a TA validation timer may be configured to restart.
When one or a plurality of criteria for determining the TA validity for PUR transmission are configured or when there is no UL data to be sent by the UE, if it is configured that the PUR transmission may be skipped, when the UE should apply the TA validity criterion needs to be configured.
When it is configured that the TA validity should be determined by applying the TA validity criterion before every PUR, there is no UL data to be sent to the corresponding PUR by the UE, and as a result, the PUR is intended to be skipped, but it should be determined whether a current timing advance (TA) is valid according to the TA validity criterion. In this case, since even a UE that does not perform the PUR transmission continuously should test the TA validity by consuming the power of the UE (e.g., serving cell NRSRP measurements, etc.), there is a disadvantage in terms of the battery life of the UE.
Therefore, the timing when the UE determines whether the TA is valid by applying the TA validity criterion may be configured as a timing before a specific subframe (i.e., specific time) of a subframe in which the corresponding PUR transmission starts when there is UL data to be transmitted to a specific PUR by the corresponding UE. That is, when there is no UL data to be sent, it may be advantageous because unnecessary power need not be wasted for TA validity test.
As another method, when there is no UL data to be sent to the corresponding PUR by the UE, operations (e.g., serving cell NRSRP measurements, etc.) of the UE should use the power among the TA validity criteria may be configured not to be performed. In this case, the TA alignment timer performs the validity test before every PUR location and in an operation such as narrowband reference signal reception power (NRSRP) measurements, the validity test is performed only when there is UL data to be transmitted. Even in this case, when there is no UL data to be sent, it may be advantageous because unnecessary power need not be wasted for the TA validity test.
According to an embodiment, when there is no UL data to be sent to the PUR by the UE, a timer (or a timer that should perform operations of consuming the power of the UE among the TA validity criteria) for validity determination according to the TA validity criterion may be configured to be held. When the corresponding timer is held and there is UL data to be sent to the subsequent PUR, the TA validity may be configured to be determined by restarting a timer that should perform the TA validity criterion.
Furthermore, the size of the corresponding cell may be implicitly indicated to the UE through the (N)PRACH preamble format configured in the corresponding cell. The UE may determine the size of the corresponding cell by using the information and if the cell size is small, the TA validity test may be intermittently performed. That is, the test period may be configured to be longer than when the cell size is not determined to be small (e.g., a general cell size).
For example, when the base station is indicates an (N)PRACH preamble format in which a cyclic prefix (CP) length is set to be short, such as FDD NPRACH preamble format 0, or TDD NPRACH preamble format 0-a, (or eMTC PRACH preamble format 4). The UE may be configured to perform the test at a longer period by a specific multiple of a TA validity test period indicated by the base station or by a specific multiple of a predefined TA validity test period.
In this case, the specific multiple may be indicated by the base station or may be predefined in a specification. When the corresponding method is applied, the UE may maintain the same level of TA validity in spite of performing only tests a smaller number of times compared to the general number of TA validity tests, and as a result, there is an advantage in terms of power saving of the UE.
Additionally, transmission power of the UE may be added based on the TA validity criteria. That is, when the UL TX power value of the UE is not larger than a specific threshold set by the base station, the UE may configure that the power may not be transmitted to the corresponding PUR. Since a UL Tx max power value which may be used with a change in a downlink CE level of the UE may be set, this method may be used as an indirect index indicating whether the current PUR may be used.
A UE that intends to perform transmission to a specific PUR may determine that the TA alignment timer expires through the TA validity test (or determine that the TA alignment timer will soon expire), and perform an operation for the TA update. When the corresponding UE fails to receive a TA update command from the base station, a UE operation needs to be defined.
When the UE fails to receive the TA update command from the base station for a time duration in which the TA update command may be received, the UE may regard that the current TA update is not required. Such an operation has an advantage of being simple, but a case where the base station sends the TA update command, but the UE fails to receive the TA update command may not be considered.
As another method, when the UE fails to receive the TA update command from the base station for the time duration in which the TA update command may be received, the UE may be configured to continuously operate on the assumption that the current timing advance (TA) is invalid. Thereafter, the UE may preferably perform an operation such as legacy RACH/EDT again.
As another method, when the UE fails to receive the TA update command from the base station for the time duration in which the TA update command may be received, the UE may determine that a current PUR configuration is invalid (that is, the current PUR configuration is released). In such a case, since an operation of the UE which processes that the PUR is released (the base station should also know that) may be a desirable operation in terms of resource utilization of the base station and an actual timing advance (TA) may be changed a lot, it may be preferable that the UE conservatively operates until the UE receives explicit information from the base station.
Hereinafter, a mechanism for the base station to facilitate BD will be described in detail.
When skipping of uplink data (that is, a case where when there is data to be sent, data is not sent) is allowed in a resource configured as idle mode uplink semi-persistent scheduling (UL SPS), the base station should perform blind detection (BD) regardless of whether the UE transmits data. This may become a burden for the base station, and even when no UE transmits the data, the corresponding resource may not be used for other purposes (e.g., NPUSCH, NPRACH, etc.). Therefore, a method for informing the base station of whether the UE transmits the data to a semi-permanent scheduling (SPS) resource may be considered.
As a first method, the UE transmits a preconfigured signal/channel at a specific location in relation to the SPS resource to inform the base station of transmitting the data by using the corresponding SPS resource.
Specifically, the specific location may be a location configured from the base station before the semi-persistent scheduling (SPS) resource or a location separated from the SPS resource by a predetermined number of subframes (SFs), slots, or symbols. The UE transmits a predetermined signal/channel at the specific location to inform the base station of transmitting the data in the corresponding SPS resource.
According to an embodiment, the corresponding signal/channel may be configured to be cell specific. In this case, when the base station transmits that even one UE transmits the data to the corresponding resource, the base station should perform blind detection (BD) for the corresponding resource, and as a result, the base station may be commonly configured in the same cell. Meanwhile, since the corresponding signal/channel should be distinguished from a signal/channel used in an adjacent cell, a cell ID, a frame index, etc., may be required for the corresponding signal/channel.
When the idle mode SPS resource is independently configured for each CE level, the corresponding signal/channel may be configured differently for each CE level even in the same cell. When only one signal/channel is used in the same cell, the base station needs to appropriately configure the idle mode SPS resource so as to prevent a location to which the corresponding signal/channel is transmitted from overlapping for each CE level.
That is, when an important element indicating whether even any UE is to actually transmit the data in the SPS resource from the standpoint of the base station, all or some UEs using the corresponding resource may be configured to use the same signal/channel other than a different signal/channel for each UE.
As a second method, the UE may inform the base station of whether to transmit the data to the idle mode SPS resource. In this case, a specific period may be a period in which the UE wakes up from a sleep in order to monitor or receive a paging or a wake up signal or a period such as DRX or eDRX. Characteristically, the specific period may be larger than or equal to the period of the idle mode SPS resource.
A UE that notifies data transmission by using this method has an advantage of informing the base station of whether to transmit one or more SPS resources through one notification. The one notification may be transmitted in the form of each bitmap to be UE specific or may be a cell specific signal/channel as mentioned above.
According to an embodiment, the UE transmits uplink control information (UCI) to inform the base station of whether to transmit the data in the idle mode SPS resource. In this case, the uplink control information (UCI) may include HARQ process ID, initial transmission/retransmission or not, Transport Block Size (TBS), and the like and this may be included in MSG1/MSG3 or DMRS.
According to this method, since the base station need not perform blind detection (BD) for a region which the UE does not transmit, there is an effect in terms of power saving of the base station and further, since the corresponding resource may be used to be dedicated for other purposes, there is an advantage even in terms of efficient resource utilization.
According to an embodiment, a notification related to whether to transmit the uplink data may be utilized other purposes. Specifically, the UE may inform the base station of not transmitting the uplink data to the SPS resource (i.e., PUR).
That is, when the UE informs the base station of not transmitting the uplink (UL) data to the PUR, the base station may use the PUR for different UEs by detecting the corresponding signal. The embodiment has an advantage in the case of the dedicated PUR. Specifically, when a specific PUR is allocated to a single UE, if the corresponding UE notifies that the specific PUR is not used, the base station may reallocate the corresponding PUR resource to another UE.
A signal related to whether to transmit the uplink data may be transmitted away in front of the PUR resource by a specific location, but may be delivered to the frontmost part of the corresponding PUR resource. For example, when it is assumed that the PUR resources allocated by the base station are K subframes, N subframes among them may be used for notifying that the UL data is transmitted or not transmitted to the PUR. If it is notified that the data is transmitted in the PUR resource, the UE may transmit the UL data in K−N subframes.
Hereinafter, an SPS search space configuration will be reviewed in detail.
A carrier to be monitored in relation to the search space for idle mode semi-persistent scheduling (Idle mode SPS) may be indicated by RRC.
Specifically, when the search space for the idle mode SPS is newly introduced or a legacy search space configuration is reused, the carrier to be monitored in relation to the search space for the idle mode SPS may be indicated through RRC signaling.
As an example, when the search space is newly introduced for the idle mode SPS and the base station does not explicitly indicate the corresponding carrier, the UE may be configured to monitor the corresponding search space in an anchor DL carrier.
As another example, when the legacy search space configuration is reused and the base station does not explicitly indicate the carrier to be monitored in relation to the search space for the idle mode SPS, the UE may be configured to monitor the search space at the same location as the carrier corresponding to the legacy search space.
Specifically, when a legacy USS is reused as the search space for the idle mode SPS, the base station may explicitly indicate the carrier for the idle mode SPS. When the base station does not explicitly indicate the corresponding carrier information, the NPDCCH for the idle mode SPS may be configured to be transmitted in the same carrier as the carrier for monitoring the legacy USS.
Hereinafter, an HARQ procedure related to the SPS will be reviewed in detail.
The maximum number of HARQ processes usable for the idle mode SPS may be determined based on an HARQ capability of each UE.
In the case of narrowband Internet of things (NB-IoT), the maximum number of HARQ processes usable for the idle mode SPS by a single HARQ capable UE becomes 1 and the maximum number of HARQ processes usable for the idle mode SPS by two HARQ capable UEs becomes 2. Like eMTC, in the case of 8 HARQ or 16 HARQ capable UEs, the maximum number of HARQ processes usable for the idle mode SPS becomes 8 or 16.
Meanwhile, the base station may indicate the actual number of HARQ processes to be used for the idle mode SPS through an RRC configuration. When the actual number of HARQ processes to be used for the idle mode SPS indicated by the base station is larger than the number of HARQ processes which the corresponding UE may have, the UE may discard a related configuration by regarding that the corresponding RRC configuration is invalid.
Hereinafter, early termination related to the idle mode SPS will be reviewed in detail.
The UE may additionally receive an indication of the early termination from the base station. Specifically, when the indication of (re)activation/deactivation/retransmission is received through the downlink control information (DCI) of the search space for the idle mode SPS or the payload of the paging narrowband physical downlink shared channel (NPDSCH), the UE may additionally receive the indication of the early transmission.
When the base station semi-statically indicates the UL resource and the repetition number and then determines that the uplink data need not be received from the UE any longer, the base station may indicate the early transmission to the UE.
According to an embodiment, when receiving the indication of (re)activation/deactivation of the SPS configuration from the base station while transmitting the NPUSCH according to the SPS configuration, the UE may stop transmission of the NPUSCH which is repeatedly transmitted.
According to an embodiment, by newly defining a validation scheme for the early termination, the base station may explicitly indicate the early termination to the UE. Alternatively, by adding a field of 1 bit to a field of the UL grant, the base station may explicitly indicate the early termination to the UE.
Hereinafter, items which may be additionally considered in related to the method for indicating the SPS operation by using the paging or wake up signal will be described in detail.
Among the aforementioned embodiments or methods, the following method may be considered for an operation of the base station which indicates (re)activation or deactivation or retransmission or release by using the paging NPDCCH/NPDSCH or wake up signal (WUS).
(1) The WUS for a purpose of indicating SPS (re)activation or deactivation, or retransmission or release may be additionally configured in the SPS configuration.
That is, in this method, in the case of a UE supporting the SPS operation, a WUS resource for AN SPS-related indication purpose and a WUS resource for a paging indication purpose are separately configured. For the SPS-related indication purpose, retransmission, (re)activation, deactivation, or release may be configured to be indicated by using different WUSs. The corresponding WUS is configured differently from the WUS for the paging purpose, and as a result, the corresponding WUS should be able to be distinguished from a legacy WUS operation. In this case, the overhead of the base station may increase and a time for which the UE wakes up in order to receive the WUS for the SPS-related indication purpose may increase.
(2) A method may be considered in which some WUS resources classified by grouping in the WUS for the paging purpose are used for the SPS-related indication purpose.
In this method, there is an advantage in that separate resource allocation for the WUS for the SPS indication purpose is not required, but a capacity capable of grouping the WUSs for the paging purpose is reduced and collision may thus occur.
(3) A new paging occasion for the UEs configured with the SPS operation may be independently configured by using the SIB or RRC signaling.
The new paging occasion may be configured to be shorter than the DRX (or eDRX) period of the legacy paging occasion. The shortened period may be configured to be dependent on a time during which the timing advance (TA) between the UE and the base station performing the SPS operation may be maintained. When the new paging occasion is introduced, a location at which the WUS is transmitted may also be configured according to the corresponding paging occasion (PO).
Hereinafter, a UE initiate release process will be described in detail in relation to the operation of the idle mode semi-persistent scheduling (IM-SPS).
There are several methods described above as the method for indicating the release by the base station in a situation where the timing advance (TA) is correct, but when the UE in the RRC idle state reaches a situation where the TA may not be correct for any reason, the UE may need to perform self-release.
When the TA tracking is performed through the RACH procedure, if the UE fails in the TA tracking within a time according to a specific number of times or a specific timer, the idle mode semi-persistent scheduling (IM-SPS) may be configured to be self-released.
As another method, the base station may be configured to periodically transmit a (re-) confirm message for the idle mode semi-persistent scheduling (IM-SPS) through the downlink channel or signal. When the UE fails to receive the (re-)confirm message within the time according to the specific number of times or specific timer, the UE may self-release the idle mode semi-persistent scheduling (IM-SPS).
The specific number of times and the specific timer value of the above methods may be indicated by the base station or may be defined as a specific value in advance when the SPS is configured through the RRC signaling.
As another scheme, a method in which the UE informs the base station of release or reconfiguration of the idle mode semi-persistent scheduling (IM-SPS) may be considered.
In the case of performing the TA tracking through the RACH procedure, the UE may be configured to report, to the base station, that the RACH procedure is to request the release or reconfiguration of the idle mode semi-persistent scheduling (IM-SPS) through the MSG3. The base station may confirm the release/reconfiguration request of the idle mode semi-persistent scheduling (IM-SPS) through the MSG4.
According to an embodiment, the UE may perform the corresponding operation after returning to the connected mode through an RRC resume request. Specifically, the UE that returns to the connected mode may perform a scheduling request/buffer status report (SR/BSR) and perform an idle mode semi-persistent scheduling (IM-SPS) release/reconfiguration request by using the narrowband physical uplink shared channel (NPUSCH). In this regard, the base station may confirm the corresponding request and the UE may be configured to operate according to the indication of the base station.
When there is no data to be sent by the UE or uplink data transmission skipping is performed continuously or discontinuously N times (in this case, N is a natural number equal to or more than 1), corresponding semi-persistent scheduling (SPS) resource is automatically released or information for informing the base station of the release may be transmitted in an ‘SPS resource after skipping N times’. In such a configuration, there is an advantage in that the UE may perform the self-release without receiving release information from the base station.
In the case where the uplink data transmission skipping is continuous or discontinuous, a detailed operation related to the release of the SPS configuration will be described below.
In the release of the SPS configuration due to skipping of uplink data transmission N times, the SPS configuration may be configured to be released when there is skipping N times for consecutive PURs.
In this case, only when skipping is continuously performed for N consecutive PURs, the release may be configured to be automatically (implicitly) released. For example, it may be assumed that the UE does not transmit the UL data for N−1 consecutive PURs.
Thereafter, when the UE transmits the UL data to the immediately subsequent PUR, the skipping count of N−1, which has already been skipped, may be initialized, and the UE may newly start a count for filling the skipping count N from the beginning. In this case, the SPS configuration is maintained.
On the contrary, when the corresponding UE does not transmit the UL data to the immediately subsequent PUR, the UE may be configured to determine that skipping of consecutive PURs is completed N times and (automatically) (implicitly) release the SPS configuration.
Even though the base station fails to receive the UL data in N−1 consecutive PURs, when the base station receives the UL data in the immediately subsequent PUR, the skipping count of N−1 in which skipping is already completed may be initialized and the count for filling a skipping count of N may newly start from the beginning.
In this method, since the PUR configuration for the SPS operation is continued for UEs that do not perform N-times consecutive skipping, the UE that intends to the uplink data in the PUR need not receive a new PUR configuration. The UE that receives the SPS configuration through the RRC signaling need not re-enters the connected mode and there is an advantage in terms of the power saving of the UE.
Meanwhile, in the release of the SPS configuration due to N-times skipping of uplink data transmission, the SPS configuration may be configured to be released when there is N-times skipping N for the PUR regardless of consecutive/inconsecutive PURs.
Unlike the method in which the number of skipping times is counted only when the UL data is skipped for the aforementioned consecutive PURs, the release may be configured to be (automatically) (implicitly) allowed when skipping the UL data for N-times PURs regardless of consecutiveness/inconsecutiveness.
For example, it may be assumed that the UE does not transmit the UL data for N−1-times consecutive PURs (regardless of consecutiveness/inconsecutiveness). Thereafter, even though the corresponding UE transmits the UL data in the immediately subsequent PUR, the skipping count of N−1 counted above is not initialized but maintained. At a moment when the skipping count of N is filled because the corresponding UE does not transmit the UL data in the subsequent PUR (regardless of consecutiveness/inconsecutiveness), the PUR configuration may be configured to be (automatically) (implicitly) released.
The advantage of applying this method is that the base station may efficiently manage the resource. The reason is that resources are limited to allocate the PURs to all of a large number of UEs that want to use the PUR. Therefore, when the base station gives a total of N-times skipping occasions to the UE and the UE that performs N-times skipping intends to transmit the uplink data in the PUR again, the base station may be configured with new PUR.
Further, in the case of the method for releasing the PUR configuration only N-times consecutive skipping, the UE may intentionally send the UL data in the PUR which exists immediately after skipping the PUR N−1 times. In this case, the UE may occupy the corresponding PUR without a limit. Such a problem may be solved by setting the skipping count which is a condition of the release to a total of N times regardless of consecutiveness/inconsecutiveness.
Furthermore, even though skipping is allowed when there is no data to be sent by the UE, when confirmation of the UE for (re)activation and release transmitted by the base station is required, skipping may be configured not to be allowed. The configuration of a skipping exception interval has an advantage in that the base station may receive the confirmation of the UE for (re)activation and release.
Additionally, it may be configured to be expected that the base station does not send a retransmission request for the confirmation transmitted by the UE. The reason for such a configuration is that since confirmation information transmitted by is not actual UL data, retransmission of the corresponding information may not be required in terms of the UE. Accordingly, when the base station requests retransmission for the corresponding information, the UE may determine that the request for retransmission is invalid.
Downlink control information indicating retransmission may be introduced in a PUR in which HARQ is introduced. The base station may be configured to explicitly release a PUR which operates in the idle mode through the NPDCCH indicating the corresponding retransmission.
The release of the PUR may be indicated by using a specific 1-bit field of the downlink control information indicating the corresponding retransmission. Alternatively, by a specific field value of a corresponding downlink control information format (DCI format) to a predetermined value, it may be configured to deliver that the corresponding release indication is valid. Alternatively, it may be configured that a DL grant other than a retransmission UL grant (UL grant) may come through the NPDCCH indicating the corresponding retransmission, and the release of the PUR may be configured to be explicitly indicated through the NPDSCH scheduled by the corresponding DL grant.
According to an embodiment, when the UE that fails to receive the indication of the explicit release for the PUR from the base station enters the connected mode, the UE may be configured to determine that the legacy PUR configuration is released. In order to configure to reuse the corresponding PUR configuration value, the base station may explicitly instruct the UE entering the connected mode to use the legacy PUR configuration.
Hereinafter, an idle mode operation of a UE in which semi-persistent scheduling is configured will be reviewed.
Among the aforementioned embodiments or methods, methods that may be used even in the connected mode may be basically applied. Meanwhile, the legacy connected mode SPS is applied to LTE/eMTC and SPS for a BSR purpose is introduced into the narrowband Internet of things (NB-IoT). When SPS for a unicast purpose is introduced into the NB-IoT, the following items may be considered.
First, a dynamic grant based deactivation may be considered.
Since the connected mode UE continuously monitors the UE-specific search space (USS), the connected mode UE may receive the indication such as (re-) activation/deactivation/retransmission from the base station by using a search space such as a dynamic grant.
The base station may be configured to indicate dynamic grant based deactivation. Whether the dynamic grant based deactivation is indicated may be distinguished according to a transmission/reception timing of the NPDSCH/NPUSCH according to the corresponding dynamic grant and a transmission/reception timing of the NPDSCH/NPUSCH according to the SPS grant.
When the NPDSCH/NPUSCH transmission/reception timing according to the dynamic grant overlaps with the NPDSCH/NPUSCH transmission/reception timing according to the SPS grant at least partly, the UE may determine that the dynamic grant indicates SPS deactivation.
When the NPDSCH/NPUSCH transmission/reception timing according to the dynamic grant does not overlap with the NPDSCH/NPUSCH transmission/reception timing according to the SPS grant, the UE may determine that the dynamic grant indicates the SPS deactivation.
Second, an item related to the HARQ procedure may be considered.
In a state in which 2 HARQ capable UEs are instructed to perform 2 HARQ, when using one HARQ process for the SPS purpose, the UE may be configured to expect only single HARQ. Specifically, when the corresponding UE monitors a UE specific search space (USS) which exists during a specific period (e.g. PDCCH period) from a resource instructed to be transmitted/received according to the configured grant after the SPS is (re)activated, the corresponding UE may be configured to expect only the single HARQ.
Hereinafter, a shared resource among types of resources related to the semi-persistent scheduling operation will be described in detail with reference to
As a method in which multiple UEs share the resource for a configured resource in the idle mode and/or connected mode, MU-MIMO may be considered. An example of a situation considering the MU-MIMO may be illustrated as in
The base station may configure UL SPS information in each UE through the SIB or RRC signaling. The configuration may include an SPS share resource, DMRS for each UE and/or PUSCH orthogonal cover code (OCC) for each UE, a channel/signal configuration (e.g., period, offset, etc.) indicating (re-)activation/deactivation/retransmission, and the like.
Thereafter, activated UEs may transmit the NPUSCH to a share resource according to a configuration of each UE. The uplink data transmission skipping (UL skipping) may be allowed and each UE may also receive an indication how many UEs share the corresponding shared resource.
Thereafter, all UEs that are configured with each shared resource may monitor and/or detect a region in which a channel and/or a signal indicating (re-) activation/deactivation/retransmission may be transmitted.
Characteristically, in the case of using the shared resource as described above, the SPS operation such as (re-)activation/deactivation/retransmission may be performed in the form of a UE group.
In this case, when the downlink control information (DCI) performs a role of indicating (re-)activation/deactivation/retransmission, a search space in which the DCI may be transmitted may be configured similarly to the random access response (RAR) search space. That is, the corresponding DCI may be scrambled with different RNTI values according to which shared resource is transmitted and the UE may also know the corresponding RNTI value according to information such as the time and/or frequency of the shared resource transmitted thereby.
In addition, the search space in which the corresponding DCI may be transmitted may be configured to be the same as a search space in which the DCI indicating (re-) activation/deactivation may be received. In this case, the RNTI value may be predetermined according to the time and/or frequency of the shared resource as mentioned above.
Additionally, the DCI payload size may be configured to equally by performing zero padding on the shorter side to prevent an increase in blind detection (BD). A specific field of the corresponding DCI may indicate the ACK/NACK in the form of the bitmap. The location/order of each bit constituting the corresponding bitmap may be implicitly mapped by the demodulation reference signal sequence (DMRS sequence) or the orthogonal cover code (OCC).
Further, a DL assignment field of the corresponding DCI may schedule an NPDSCH for adaptive retransmission. A specific field of the corresponding DCI may be configured to indicate whether there is adaptive retransmission scheduling information for the NACK of the ACK/NACK indicated in the form of the bitmap as described above. In this case, the UE that detects the ACK need not receive a subsequent NPDSCH.
On the contrary, when the UE that detects the NACK receives an indication that there is no adaptive retransmission information in the NPDSCH in the aforementioned specific field, the UE need not receive the subsequent NPDSCH and performs non-adaptive retransmission in a next UL SPS resource.
When the UE that detects the NACK receives an indication that there is the adaptive retransmission information in the NPDSCH in the aforementioned specific field, the UE need not receive the subsequent NPDSCH. In addition, the UE may read the UL grant of the payload (e.g., MAC message, etc.) of the corresponding NPDSCH, and accordingly perform dynamic UL retransmission or adaptive retransmission in the next UL SPS resource.
Unlike described above, when there is no downlink control information (DCI) indicating (re-)activation/deactivation and the operation such as (re-)activation/deactivation is indicated to the NPDSCH scheduled by the corresponding DCI, a specific field of the corresponding DCI may indicate whether the indication for the operation such as the (re-) activation/deactivation is included in the subsequent NPDSCH.
In this case, a UE which is not activated or does not transmit the NPUSCH due to the UL data transmission skipping (UL skipping) may also attempt to detect the corresponding DCI. In addition, the RNTI value for this may be delivered through the system information block (SIB) or RRC signaling.
When receiving an indication that information indicating (re-)activation/deactivation in the specific field of the DCI detected by the UE, the corresponding UE needs to receive the NPDSCH. The UE may perform the operation such as the (re-)activation/deactivation according to the information included in the NPDSCH.
Additionally, the base station may configure the shared resource to a plurality of UEs through the RRC signaling or system information and a resource suitable for each UE may be configured to be selected by applying a UE ID or a UE specific value to a predetermined specific equation.
Alternatively, as a method applicable to a system that similarly uses uplink/downlink (UL/DL) carriers, such as time division duplex (TDD), the following item may be considered.
The base station may independently configure a UL SPS transmission resource of each UE through the RRC signaling. In addition, each UE may determine whether the uplink data of another UE is transmitted based on energy detection by sensing the corresponding UL resource from a location prior to the starting subframe (SF) of the resource configured thereto by K subframes (K SFs) (e.g., K=4) to determine whether a preconfigured grant of the corresponding UE is valid.
Hereinafter, in
Referring to
In S2010, the UE receives information related to the PUR for transmitting the uplink data in the RRC connected state.
According to an embodiment, the information related to the PUR may include information indicating a specific carrier for monitoring a first search space related to the PUR.
According to an embodiment, the specific carrier may be an anchor carrier or a non-anchor carrier.
The base station may explicitly indicate the specific carrier to the UE, but when there is no explicit indication, the specific carrier may vary depending on whether the first search space is a legacy search space.
Specifically, when the first search space is the legacy search space, the specific carrier may be a carrier for monitoring the legacy search space. When the first search space is a new search space other than the legacy search space, the specific carrier may be the anchor carrier. The base station may explicitly indicate the specific carrier to the UE.
The first search space as a search space configured through the information related to the PUR may be referred to as a Semi-Persistent Scheduling Search Space (SPS-SS).
In S2020, the UE transmits the uplink data by using the PUR in the RRC idle state.
According to an embodiment, when the first search space overlaps with a second search space in which downlink control information (DCI) related to a specific operation is transmitted, the second search space has a priority.
According to an embodiment, the UE may receive a Narrowband Physical Downlink Control Channel (NPDCCH) by monitoring the first search space in the specific carrier. The Narrowband Physical Downlink Control Channel (NPDCCH) may include information related to retransmission of the uplink data. The Narrowband Physical Downlink Control Channel (NPDCCH) may be Downlink Control Information.
According to an embodiment, when the first search space and the second search space overlap with each other in at least one domain of a time or a frequency, the first search space may not be monitored in the overlapping domain.
According to an embodiment, the specific operation may be an operation related to at least one of a paging process or a random access process (RACH process), and the UE may receive downlink control information (DCI) related to the specific operation by monitoring the second search space in the overlapping domain.
According to an embodiment, the PUR may be a dedicated resource.
Hereinafter, in
According to an embodiment, a specific operation which exerts a large influence on a system among operations of a UE in an RRC idle state may be configured to have a higher priority than the operation related to the PUR.
Specifically, when a first search space the PUR overlaps with a second search space in which downlink control information (DCI) related to the specific operation is transmitted, the second search space has a priority.
Referring to
In S2021, when the first search space and the second search space overlap with each other in any one domain of a time or a frequency, the UE may not monitor the first search space (S2022). The UE may receive the downlink control information (DCI) related to the specific operation by monitoring the second search space.
According to an embodiment, the second search space may be a Common Search Space (CSS). The Common Search Space (CSS) may be a type-1 CSS or a type-2 CSS.
According to an embodiment, the downlink control information (DCI) related to the specific operation may include information for scheduling a paging narrowband physical downlink shared channel (NPDSCH).
According to an embodiment, the downlink control information (DCI) related to the specific operation may include information for scheduling a narrowband physical downlink shared channel (NPDSCH) through which a random access response (RAR) grant is transmitted.
In S2021, when the first search space and the second search space do not overlap with each other in any one domain of the time or the frequency, the UE may monitor the first search space (S2023). The UE may receive a narrowband physical downlink control channel (NPDCCH) by monitoring the first search space. The NPDCCH may include information related to retransmission of the uplink data.
In terms of implementation, the operation of the UE described above may be specifically implemented by terminal devices 620 and 720 illustrated in
For example, the processor may be configured to receive information related to a PUR for transmission of uplink data in an RRC connected state and transmit the uplink data by using the PUR in an RRC idle state. The information related to the PUR may include information indicating a particular carrier for monitoring a first search space related to the PUR.
The processor may receive a narrowband physical downlink control channel (NPDCCH) by monitoring the first search space. When the first search space overlaps with a second search space in which downlink control information (DCI) related to a specific operation is transmitted, the second search space has a priority.
Hereinafter, in
Referring to
In S2210, the base station may transmit information related to the PUR to a UE in an RRC connected state.
According to an embodiment, the information related to the PUR may include information indicating a specific carrier for monitoring a first search space related to the PUR.
According to an embodiment, the specific carrier may be an anchor carrier or a non-anchor carrier.
The specific carrier may vary depending on whether the first search space is a legacy search space.
Specifically, when the first search space is the legacy search space, the specific carrier may be a carrier for monitoring the legacy search space. When the first search space is a new search space other than the legacy search space, the specific carrier may be the anchor carrier.
The first search space as a search space configured through the information related to the preconfigured uplink resource may be referred to as a Semi-Persistent Scheduling Search Space (SPS-SS).
In S2220, the base station may receive the uplink data from the UE in the RRC idle state through the PUR.
The base station may transmit a narrowband physical downlink control channel (NPDCCH) related to the PUR through the first search space. The Narrowband Physical Downlink Control Channel (NPDCCH) may include downlink control information (DCI) including information related to retransmission of the uplink data.
The base station may transmit downlink control information (DCI) related to a specific operation through the second search space.
According to an embodiment, when the first search space overlaps with the second search space, the base station may configure the second search space to have a priority. That is, the base station may configure the UE to preferentially receive the downlink control information (DCI) transmitted through the second search space.
According to an embodiment, when the first search space and the second search space overlap with each other in at least one domain of a time or a frequency, the base station may configure the UE not to monitor the first search space in the overlapping domain.
According to an embodiment, the specific operation may be an operation related to at least one of a paging process or a random access (RACH) process.
According to an embodiment, the second search space may be a Common Search Space (CSS). The Common Search Space (CSS) may be a type-1 CSS or a type-2 CSS.
According to an embodiment, the downlink control information (DCI) related to the specific operation may include information for scheduling a paging narrowband physical downlink shared channel (NPDSCH).
According to an embodiment, the downlink control information (DCI) related to the specific operation may include information for scheduling a narrowband physical downlink shared channel (NPDSCH) through which a random access response (RAR) grant is transmitted.
According to an embodiment, the PUR may be a dedicated resource for the UE in the RRC idle state.
In terms of implementation, the operation of the base station described above may be specifically implemented by terminal devices 610 and 710 illustrated in
For example, the processor may be configured to transmit information related to a PUR for transmission of uplink data to a UE in an RRC connected state and receive the uplink data from a UE in an RRC idle state through the PUR.
In this case, the information related to the PUR may include information indicating a specific carrier for monitoring a first search space related to the PUR. When the first search space overlaps with the second search space, the processor may configure the second search space to have a priority.
Effects according to the present disclosure described in
In the present disclosure, information related to a preconfigured UL resource (PUR) is transmitted through radio resource control (RRC) signaling, and when a first search space related to the PUR and a second search space in which downlink control information (DCI) related to a specific operation is transmitted overlap with each other, the second search space has a priority. Accordingly, the present disclosure can lower complexity of a UE and reduce power consumption, and minimize an influence of the overlapping of the first search space and the second search space on a system.
Furthermore, in the present disclosure a carrier for monitoring the corresponding search space is configured differently according to whether to utilize a conventional search space as the first search space related to the PUR. Accordingly, the present disclosure can remove ambiguity caused by introduction of a new search space for the PUR.
Furthermore, in the present disclosure, a narrowband physical downlink control channel (NPDCCH) received by monitoring the first search space related to the PUR includes information indicating retransmission of the uplink data. Since the retransmission of the uplink data can be dynamically scheduled, the present disclosure can provide flexibility to a base station operation.
The embodiments described above are implemented by combinations of components and features of the disclosure in predetermined forms. Each component or feature should be considered selectively unless specified separately. Each component or feature may be carried out without being combined with another component or feature. Moreover, some components and/or features are combined with each other and can implement embodiments of the disclosure. The order of operations described in embodiments of the disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced by corresponding components or features of another embodiment. It is apparent that some claims referring to specific claims may be combined with another claims referring to the claims other than the specific claims to constitute the embodiment or add new claims by means of amendment after the application is filed.
Embodiments of the disclosure can be implemented by various means, for example, hardware, firmware, software, or combinations thereof. When embodiments are implemented by hardware, one embodiment of the disclosure can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
When embodiments are implemented by firmware or software, one embodiment of the disclosure can be implemented by modules, procedures, functions, etc. performing functions or operations described above. Software code can be stored in a memory and can be driven by a processor. The memory is provided inside or outside the processor and can exchange data with the processor by various well-known means.
It is apparent to those skilled in the art that the disclosure can be embodied in other specific forms without departing from essential features of the disclosure. Accordingly, the aforementioned detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the disclosure should be determined by rational construing of the appended claims, and all modifications within an equivalent scope of the disclosure are included in the scope of the disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2018-0092742 | Aug 2018 | KR | national |
| 10-2018-0092761 | Aug 2018 | KR | national |
| 10-2019-0114492 | Sep 2018 | KR | national |
| 10-2018-0134003 | Nov 2018 | KR | national |
| 10-2018-0138082 | Nov 2018 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2019/010150 | 8/9/2019 | WO | 00 |
