Completion mechanism for transmissions using preconfigured uplink resources
By using pre-configured uplink resources (PUR) and timing advance command (TAC) MAC control elements in NB-IoT and MTC networks, the high power consumption of wireless devices in the RRC_IDLE and RRC_INACTIVE states is solved, achieving low-power and high-efficiency uplink data transmission.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- LG ELECTRONICS INC
- Filing Date
- 2020-09-29
- Publication Date
- 2026-06-19
Smart Images

Figure CN114503621B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a completion mechanism for transmissions using pre-configured uplink resources (PUR). Background Technology
[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for achieving high-speed packet communication. Many proposals have been put forward for LTE objectives, including those aimed at reducing costs for users and providers, improving quality of service, and expanding and improving coverage and system capacity. 3GPP LTE requires, as a high level of compliance, reduced cost per bit, increased service availability, flexible use of frequency bands, a simple architecture, open interfaces, and appropriate terminal power consumption.
[0003] The International Telecommunication Union (ITU) and 3GPP have begun work to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components needed to successfully standardize the new RATs that meet both urgent market demands and longer-term requirements outlined by the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, even in the more distant future, NR should be able to utilize any spectrum band available for wireless communication, at least up to 100 GHz.
[0004] NR is a single technology framework designed to address all use cases, requirements, and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). NR will be inherently forward compatible.
[0005] In Release 13, Narrowband Internet of Things (NB-IoT) and LTE for MTC (LTE-M) were standardized to provide wide-area connectivity for the Internet of Things. The technological evolution in Release 14 goes beyond the basic functionality specified in Release 13. Summary of the Invention
[0006] Technical issues
[0007] Pre-configured uplink resources (PURs) are designed for NB-IoT and MTC networks to conserve power during data transmission. The UE can transmit UL data in RRC_IDLE and / or RRC_INACTIVE without a random access procedure and / or state transition to a connected state (e.g., RRC_CONNECTED). A method may be needed to complete the process for transmitting using PURs.
[0008] Technical solution
[0009] In one aspect, a method is provided performed by a wireless device configured to operate in a wireless communication system. The method includes, when in a Radio Resource Control (RRC) idle state and / or an RRC inactive state, i) performing uplink (UL) data transmission to the network using pre-configured uplink resources (PUR), ii) attempting to obtain downlink (DL) information from the network on a Physical Downlink Shared Channel (PDSCH), and iii) considering the UL data transmission using the PUR to be successful based on the DL information including only the Timing Advance Command (TAC) Media Access Control (MAC) control element (CE).
[0010] On the other hand, an apparatus for implementing the above method is provided.
[0011] Beneficial effects
[0012] This disclosure can have various beneficial effects.
[0013] For example, the UE can effectively determine whether UL data transmission using PUR is successful based on DL information. If the DL information only includes TAC MAC CE, the UE can consider UL data transmission using PUR to be successful.
[0014] For example, the UE does not need the PDCCH and can directly obtain DL information on the PDSCH. The network can configure PDSCH scheduling information through UL resource configuration. By skipping PDCCH monitoring, the UE can reduce the power consumption of PDCCH monitoring and obtain DL information quickly.
[0015] The beneficial effects that can be obtained through specific embodiments of this disclosure are not limited to those listed above. For example, various technical effects may be present that can be understood and / or derived from this disclosure by those skilled in the art. Therefore, the specific effects of this disclosure are not limited to those explicitly described herein, but may include a variety of effects that can be understood or derived from the technical features of this disclosure. Attached Figure Description
[0016] Figure 1 An example of a communication system applying embodiments of the present disclosure is shown.
[0017] Figure 2 Examples of wireless devices applying embodiments of the present disclosure are shown.
[0018] Figure 3 Examples of wireless devices applying embodiments of the present disclosure are shown.
[0019] Figure 4 Another example of a wireless device applying embodiments of the present disclosure is shown.
[0020] Figure 5 An example of a UE applying an embodiment of this disclosure is shown.
[0021] Figure 6 and Figure 7 An example of a protocol stack in a 3GPP-based wireless communication system applying embodiments of the present disclosure is shown.
[0022] Figure 8 The frame structure in a 3GPP-based wireless communication system applying embodiments of the present disclosure is shown.
[0023] Figure 9 An example of a data flow in a 3GPP NR system applying embodiments of the present disclosure is shown.
[0024] Figure 10 An example of the general process of transmission using PUR is shown.
[0025] Figure 11 This shows another example of the general process of transmission using PUR.
[0026] Figure 12 An example of a method performed by a wireless device configured to operate in a wireless communication system to which embodiments of the present disclosure are applied is shown.
[0027] Figure 13 Examples of methods performed by wireless devices and network nodes configured to operate in a wireless communication system to which embodiments of the present disclosure are applied are shown.
[0028] Figure 14 An example of a method for obtaining DL information on the PDSCH in RRC_IDLE and / or RRC_INACTIVE, in which embodiments of this disclosure are applied, is shown.
[0029] Figure 15 An example of a TAC MAC CE applying an embodiment of the present disclosure is shown.
[0030] Figure 16 An example of a TAC MAC CE including a UL transmission response is shown, applying an embodiment of the present disclosure.
[0031] Figure 17 Another example of a TAC MAC CE including a UL transmission response, which applies an embodiment of this disclosure, is shown.
[0032] Figure 18 An example of transmission using PUR for control plane cellular IoT (CIoT) evolution packet system (EPS) / 5G system (5GS) optimization is shown, applying embodiments of the present disclosure.
[0033] Figure 19 An example of PUR-based transmission for CIoT EPS optimization using embodiments of this disclosure is shown.
[0034] Figure 20 An example of PUR-based transmission for user plane CIoT 5GS optimization is shown, applying an embodiment of this disclosure. Detailed Implementation
[0035] The following technologies, devices, and systems can be applied to a variety of wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), or Enhanced Data Rate Evolution of GSM (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in DL and SC-FDMA in UL. Advanced LTE (LTE-A) is an evolution of 3GPP LTE.
[0036] For ease of description, embodiments of this disclosure are primarily described with respect to 3GPP-based wireless communication systems. However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 3GPP-based wireless communication system, the aspects of this disclosure that are not limited to 3GPP-based wireless communication systems are applicable to other mobile communication systems.
[0037] For any terms and techniques not specifically described in this invention, please refer to wireless communication standard documents published prior to this disclosure.
[0038] In this disclosure, "A or B" may mean "A only", "B only", or "both A and B". In other words, "A or B" in this disclosure may be interpreted as "A and / or B". For example, "A, B or C" in this disclosure may mean "A only", "B only", "C only", or "any combination of A, B and C".
[0039] In this disclosure, a forward slash ( / ) or a comma (,) can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".
[0040] In this disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, the expressions "at least one of A or B" or "at least one of A and / or B" in this disclosure may be interpreted as the same as "at least one of A and B".
[0041] Additionally, in this disclosure, "at least one of A, B, and C" may mean "A only", "B only", "C only" or "any combination of A, B, and C". Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".
[0042] Similarly, the brackets used in this disclosure may mean "for example". Specifically, when shown as "Control Message (PDCCH)", "PDCCH" can be proposed as an example of "Control Message". In other words, "Control Message" in this disclosure is not limited to "PDCCH", and "PDDCH" can be proposed as an example of "Control Message". Furthermore, even when shown as "Control Message (i.e., PDCCH)", "PDCCH" can be proposed as an example of "Control Message".
[0043] The technical features described individually in one of the accompanying drawings of this disclosure can be implemented individually or simultaneously.
[0044] Not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operation flowcharts disclosed herein can be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).
[0045] The present disclosure will be described in more detail below with reference to the accompanying drawings. Unless otherwise stated, the same reference numerals in the following drawings and / or description may refer to the same and / or corresponding hardware blocks, software blocks and / or functional blocks.
[0046] Figure 1 An example of a communication system applying embodiments of the present disclosure is shown.
[0047] Figure 1 The 5G use cases shown are merely illustrative, and the technical features of this disclosure can be applied to... Figure 1 Other 5G use cases not shown.
[0048] The three main demand categories for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine Type Communications (mMTC), and (3) Ultra Reliable Low Latency Communications (URLLC).
[0049] Some use cases may require multiple categories for optimization, while others may focus on only one key performance indicator (KPI). 5G uses a flexible and reliable approach to support such a variety of use cases.
[0050] eMBB goes far beyond basic mobile internet access, encompassing a rich array of two-way work, media, and entertainment applications in the cloud and augmented reality. Data is one of the core drivers of 5G, and for the first time in the 5G era, dedicated voice services may not be available. In 5G, voice is expected to be simply processed as an application using the data connection provided by the communication system. The primary reason for the increase in traffic is the increase in content size and the number of applications requiring high data transmission rates. As more devices connect to the internet, streaming services (audio and video), conversational video, and mobile internet access will be more widely used. Many of these applications require always-on connectivity to push real-time information and alerts to users. Cloud storage and applications are rapidly increasing in mobile communication platforms and can be applied to both work and entertainment. Cloud storage is a specific use case for accelerating the growth of uplink data transmission rates. 5G is also being used for remote work in the cloud. When using haptic interfaces, 5G requires lower end-to-end latency to maintain a good user experience. Entertainment, such as cloud gaming and video streaming, is another core element increasing the demand for mobile broadband capabilities. Entertainment is essential for smartphones and tablets in highly mobile environments, including anywhere, such as trains, vehicles, and airplanes. Other use cases include augmented reality (AR) and information retrieval for entertainment. In this case, AR requires very low latency and instantaneous data volumes.
[0051] Additionally, one of the most anticipated 5G use cases involves the ability to seamlessly connect embedded sensors across all sectors, known as mMTC (modular machine-type communications). The number of potential Internet of Things (IoT) devices is expected to reach 20.4 billion by 2020. Industrial IoT is one of the key categories enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.
[0052] URLLC includes new services that will transform industries such as autonomous vehicles through remote control of key infrastructure and ultra-reliable / available low-latency links. These levels of reliability and latency are essential for controlling smart grids, automating industry, enabling robotics, and controlling and managing drones.
[0053] 5G is a means of providing streaming speeds rated at hundreds of megabits per second to gigabits per second and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Delivering TVs with resolutions of 4K or higher (6K, 8K, etc.) as well as virtual reality and augmented reality require such speeds. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. Certain applications may require special network configurations. For example, for VR games, game companies need to integrate their core servers into the network operator's edge network servers to minimize latency.
[0054] Along with many use cases for vehicular mobility communications, automobiles are expected to become a significant new driving force in 5G. For example, passenger entertainment demands high synchronization capacity and mobile broadband with high mobility. This is because future users continue to expect high-quality connectivity regardless of their location and speed. Another use case in the automotive field is AR dashboards. AR dashboards allow drivers to identify objects in the dark beyond what is visible through the windshield and display distances and movement of objects by overlaying information spoken to the driver. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices (e.g., devices that accompany pedestrians). Safety systems will guide alternative routes, allowing drivers to drive more safely and reducing the risk of accidents. The next stage will be remotely controlled or autonomous vehicles. This requires extremely high reliability and very fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities, and drivers will only focus on abnormal traffic conditions that vehicles cannot identify. The technological requirements for autonomous vehicles demand ultra-low latency and ultra-high reliability, enabling traffic safety to reach levels unattainable by humans.
[0055] Smart cities and smart homes / buildings, as mentioned in the context of a smart society, will be embedded in high-density wireless sensor networks. Distributed networks of smart sensors will identify cost and energy-efficient maintenance needs for cities or homes. Similar configurations can be implemented for individual households. All temperature sensors, window and heating controllers, burglar alarms, and home appliances will be wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, certain types of devices may require real-time HD video for monitoring.
[0056] The consumption and distribution of energy, including heat and gas, are allocated at a high level, necessitating automated control of distribution sensor networks. Smart grids use digital information and communication technologies to collect information and connect sensors to each other to act based on the collected data. Since this information may include the behavior of supply companies and consumers, smart grids can improve the distribution of fuels such as electricity through methods that are efficient, reliable, economically feasible, production sustainable, and automated. A smart grid can also be viewed as another sensor network with low latency.
[0057] Mission-critical applications (such as e-health) are one of the use cases for 5G. The health component includes many applications that can benefit from mobile communications. Communication systems can support telemedicine, enabling the delivery of clinical care in remote locations. Telemedicine can help reduce distance barriers and improve access to healthcare services that are not continuously available in remote rural areas. Telemedicine is also used to administer vital treatments and save lives in emergency situations. Mobile communication-based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
[0058] Wireless and mobile communications are becoming increasingly important in industrial applications. Cabling is costly in terms of installation and maintenance. Therefore, the possibility of replacing cables with reconfigurable wireless links presents an attractive opportunity in many industries. However, to achieve this replacement, it is necessary to establish wireless connections with latency, reliability, and capacity similar to those of cables, and the management of wireless connections needs to be simplified. When connecting to 5G, low latency and a very low error probability become new requirements.
[0059] Logistics and freight tracking is a key use case for mobile communications that utilizes location-based information systems to enable inventory and package tracking anywhere. Logistics and freight use cases typically require low data rates but demand location information with wide coverage and reliability.
[0060] refer to Figure 1 The communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 The 5G network is illustrated as an example of a network for communication system 1, but the embodiments of this disclosure are not limited to 5G systems and can be applied to future communication systems beyond 5G systems.
[0061] The BS 200 and network 300 can be implemented as wireless devices, and a particular wireless device can operate as a BS / network node relative to other wireless devices.
[0062] Wireless devices 100a to 100f represent devices that use radio access technology (RAT) (e.g., 5G New RAT (NR) or LTE) to perform communication and may be referred to as communication / radio / 5G devices. Wireless devices 100a to 100f may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, IoT devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.
[0063] In this disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). UE may include, for example, cellular phones, smartphones, laptop computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation systems, personal computers (PCs), tablet PCs, ultrabooks, vehicles, vehicles with autonomous driving capabilities, connected cars, UAVs, AI modules, robots, AR devices, VR devices, MR devices, hologram devices, public safety devices, MTC devices, IoT devices, medical devices, fintech devices (or financial devices), security devices, weather / environment devices, devices related to 5G services, or devices related to the Fourth Industrial Revolution.
[0064] UAVs can be, for example, aircraft that are piloted via wireless control signals without a human on board.
[0065] VR devices may include, for example, devices for realizing objects or backgrounds in a virtual world. AR devices may include, for example, devices implemented by attaching objects or backgrounds in a virtual world to objects or backgrounds in a real world. MR devices may include, for example, devices implemented by blending objects or backgrounds in a virtual world into objects or backgrounds in a real world. Holographic devices may include, for example, devices for recording and reproducing stereoscopic information using the interference of light generated when two lasers meet, a phenomenon known as holography.
[0066] Public safety equipment may include, for example, image relay devices or image devices that can be worn on a user's body.
[0067] MTC devices and IoT devices can be, for example, devices that do not require direct human intervention or manipulation. For example, MTC devices and IoT devices can include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.
[0068] Here, the radio communication technologies implemented in the wireless devices of this disclosure may include narrowband Internet of Things (NB-IoT) technologies for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology, implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and referred to by various names such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technology implemented in the wireless devices of this disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN, which takes into account low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may be based on various specifications such as IEEE 802.15.4 to generate personal area networks (PANs) associated with small / low-power digital communication, and may be referred to by various names.
[0069] Medical devices can be, for example, devices used for the purpose of diagnosing, treating, alleviating, curing, or preventing disease. For example, a medical device can be a device used for the purpose of diagnosing, treating, alleviating, or correcting an injury or lesion. For example, a medical device can be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device can be a device used for regulating pregnancy. For example, medical devices can include devices for treatment, devices for operation, devices for (in vitro) diagnostics, hearing aids, or devices for procedures.
[0070] Security devices can be, for example, devices installed to prevent potential hazards and maintain safety. Security devices can be cameras, closed-circuit television (CCTV), recorders, or black boxes.
[0071] Fintech devices can be, for example, devices capable of providing financial services such as mobile payments. For instance, fintech devices can include payment devices or point-of-sale (POS) systems.
[0072] Weather / environmental equipment may include, for example, devices used to monitor or predict weather / environment.
[0073] Wireless devices 100a to 100f can be connected to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can be connected to AI server 400 via network 300. Network 300 can be configured using 3G networks, 4G (e.g., LTE) networks, 5G (e.g., NR) networks, and super 5G networks. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication with each other without going through BS 200 / network 300 (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
[0074] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. Wireless devices 100a to 100f and BS 200 / wireless devices 100a to 100f can mutually send / receive radio signals via wireless communication / connections 150a, 150b, and 150c. For example, wireless communication / connections 150a, 150b, and 150c can send / receive signals via various physical channels. Therefore, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping) and resource allocation processes for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.
[0075] Figure 2 Examples of wireless devices applying embodiments of the present disclosure are shown.
[0076] refer to Figure 2 The first wireless device 100 and the second wireless device 200 can send / receive radio signals to / from external devices via various RATs (e.g., LTE and NR). Figure 2 In this context, {first wireless device 100 and second wireless device 200} can correspond to Figure 1 At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}.
[0077] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a radio signal including the first information / signal via the transceiver 106. The processor 102 may receive a radio signal including a second information / signal via the transceiver 106, and then store the information obtained by processing the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing part or all of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each of transceivers 106 may include a transmitter and / or a receiver. Transceivers 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, first wireless device 100 may represent a communication modem / circuit / chip.
[0078] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, the processor 202 may process information in the memory 204 to generate a third message / signal, and then transmit a radio signal including the third message / signal via the transceiver 206. The processor 202 may receive a radio signal including a fourth message / signal via the transceiver 206, and then store the information obtained by processing the fourth message / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information relating to the operation of the processor 202. For example, the memory 204 may store software code including commands for performing part or all of the processes controlled by the processor 202 or for performing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each of transceivers 206 may include a transmitter and / or a receiver. Transceivers 206 may be used interchangeably with RF units. In this disclosure, second wireless device 200 may represent a communication modem / circuit / chip.
[0079] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as Physical (PHY), Layer 1, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptive Protocol (SDAP) layer). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and acquire PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure.
[0080] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 for being driven by one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of code, commands, and / or command sets.
[0081] One or more memories 104 and 204 can be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 can be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computationally readable storage media, and / or combinations thereof. One or more memories 104 and 204 can be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 can be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.
[0082] One or more transceivers 106 and 206 can transmit user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 can perform control such that one or more transceivers 106 and 206 can transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 can perform control such that one or more transceivers 106 and 206 can receive user data, control information, or radio signals from one or more other devices.
[0083] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein via one or more antennas 108 and 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).
[0084] One or more transceivers 106 and 206 can convert received radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., can be processed by one or more processors 102 and 202. One or more transceivers 106 and 206 can also convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, transceivers 106 and 206, under the control of processors 102 and 202, can upconvert OFDM baseband signals to a carrier frequency using their (analog) oscillators and / or filters, and transmit the upconverted OFDM signals at the carrier frequency. Transceivers 106 and 206 can receive OFDM signals at the carrier frequency and, under the control of transceivers 102 and 202, downconvert OFDM signals to OFDM baseband signals using their (analog) oscillators and / or filters.
[0085] In embodiments of this disclosure, the UE can operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In embodiments of this disclosure, the BS can operate as a receiving device in the UL and as a transmitting device in the DL. Hereinafter, for ease of description, it is primarily assumed that the first wireless device 100 is the UE and the second wireless device 200 is the BS. For example, a processor 102 connected to, mounted on, or started therein of the first wireless device 100 can be configured to perform UE behavior according to embodiments of this disclosure or to control the transceiver 106 to perform UE behavior according to embodiments of this disclosure. A processor 202 connected to, mounted on, or started therein of the second wireless device 200 can be configured to perform BS behavior according to embodiments of this disclosure or to control the transceiver 206 to perform BS behavior according to embodiments of this disclosure.
[0086] In this disclosure, BS is also referred to as node B (NB), e-node B (eNB), or gNB.
[0087] Figure 3 Examples of wireless devices applying embodiments of the present disclosure are shown.
[0088] Wireless devices can be implemented in various forms depending on the use case / service (see reference). Figure 1 ).
[0089] refer to Figure 3 Wireless devices 100 and 200 can correspond to Figure 2 The wireless devices 100 and 200 can be configured from various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 2 One or more processors 102 and 202 and / or Figure 2 One or more memories 104 and 204. For example, transceiver 114 may include Figure 2 One or more transceivers 106 and 206 and / or Figure 2One or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory 130, and add-on components 140 and controls the overall operation of each of wireless devices 100 and 200. For example, control unit 120 can control the electrical / mechanical operation of each of wireless devices 100 and 200 based on programs / code / commands / information stored in memory unit 130. Control unit 120 can transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store in memory unit 130 information received from an external source (e.g., other communication devices) via wireless / wired interface through communication unit 110.
[0090] The additional component 140 can be configured differently depending on the type of wireless devices 100 and 200. For example, the additional component 140 may include at least one of a power unit / battery, an input / output (I / O) unit (e.g., an audio I / O port, a video I / O port), a drive unit, and a computing unit. Wireless devices 100 and 200 can be implemented in the following forms (but are not limited to): robots ( Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR equipment ( Figure 1 100c), handheld devices ( Figure 1 100d), home appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcasting terminals, hologram devices, public safety equipment, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices ( Figure 1 400 in the middle), BS ( Figure 1 The 200 devices, network nodes, etc., can be used in mobile or fixed locations, depending on the usage examples / services.
[0091] exist Figure 3In wireless devices 100 and 200, all of the various elements, components, units / parts, and / or modules can be connected to each other via wired interfaces, or at least a portion thereof can be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 can be connected via a wire, and control unit 120 and first units (e.g., 130 and 140) can be wirelessly connected via communication unit 110. Each element, component, unit / part, and / or module within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured by a collection of one or more processors. As an example, control unit 120 may be configured by a collection of communication control processors, application processors (APs), electronic control units (ECUs), graphics processing units, and memory control processors. As another example, memory 130 may be configured by RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and / or combinations thereof.
[0092] Figure 4 Another example of an intangible device applying embodiments of the present disclosure is shown.
[0093] refer to Figure 4 Wireless devices 100 and 200 can correspond to Figure 2 The wireless devices 100 and 200 can be configured from various elements, components, units / parts and / or modules.
[0094] The first wireless device 100 may include at least one transceiver, such as transceiver 106, and at least one processing chip, such as processing chip 101. Processing chip 101 may include at least one processor, such as processor 102, and at least one memory, such as memory 104. Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store software code 105 implementing instructions that, when executed by processor 102, execute the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 105 may implement instructions that, when executed by processor 102, execute the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 105 may control processor 102 to execute one or more protocols. For example, software code 105 may control processor 102 to execute one or more layers of a radio interface protocol.
[0095] The second wireless device 200 may include at least one transceiver, such as transceiver 206, and at least one processing chip, such as processing chip 201. Processing chip 201 may include at least one processor, such as processor 202, and at least one memory, such as memory 204. Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store software code 205 implementing instructions that, when executed by processor 202, execute the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 205 may implement instructions that, when executed by processor 202, execute the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, software code 205 may control processor 202 to execute one or more protocols. For example, software code 205 may control processor 202 to execute one or more layers of a radio interface protocol.
[0096] Figure 5 An example of a UE applying an embodiment of this disclosure is shown.
[0097] refer to Figure 5 UE 100 can correspond to Figure 2 The first wireless device 100 and / or Figure 4 The first wireless device 100.
[0098] The UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 1112, a display 114, a keyboard 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.
[0099] Processor 102 can be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 can be configured to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A layer of the radio interface protocol can be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuits, and / or data processing devices. Processor 102 may be an application processor. Processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of processor 102 can be found in [the following text is missing from the original extract]. SNAPDRAGON manufactured TM Series processors, by EXYNOS manufactured TMSeries processors, by The A-series processors manufactured by HELIO manufactured TM Series processors, by Manufactured ATOM TM It can be found in the series of processors or the corresponding next-generation processors.
[0100] Memory 104 is operatively coupled to processor 102 and stores various information for operating processor 102. Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When embodiments are implemented in software, the techniques described herein can be implemented using modules (e.g., processes, functions, etc.) that perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. Modules may be stored in memory 104 and executed by processor 102. Memory 104 may be implemented within or outside processor 102, in which case these modules may be communicatively coupled to processor 102 via various means as known in the art.
[0101] Transceiver 106 is operatively coupled to processor 102 and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry for processing radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.
[0102] The power management module 110 manages the power supply to the processor 102 and / or transceiver 106. The battery 112 supplies power to the power management module 110.
[0103] Display 114 outputs the results processed by processor 102. Keypad 116 receives input used by processor 102. Keypad 16 can be displayed on display 114.
[0104] The SIM 118 is an integrated circuit designed to securely store International Mobile Subscriber Identity (IMSI) numbers and their associated keys, which are used to identify and verify subscribers on mobile devices such as mobile phones and computers. It can also store contact information on many SIM cards.
[0105] Speaker 120 outputs sound-related results processed by processor 102. Microphone 122 receives sound-related inputs used by processor 102.
[0106] Figure 6 and Figure 7 An example of a protocol stack in a 3GPP-based wireless communication system applying embodiments of the present disclosure is shown.
[0107] In particular, Figure 6 The diagram illustrates an example of the user plane protocol stack for the radio interface between the UE and the BS. Figure 7 This diagram illustrates an example of the control plane protocol stack for the radio interface between the UE and the BS. The control plane refers to the path through which control messages for invocation by the UE and network management are transmitted. The user plane refers to the path through which data generated in the application layer, such as voice data or Internet packet data, is transmitted. (Reference) Figure 6 The user plane protocol stack can be divided into Layer 1 (i.e., the physical (PHY) layer) and Layer 2. (See reference...) Figure 7 The control plane protocol stack can be divided into Layer 1 (i.e., PHY layer), Layer 2, Layer 3 (e.g., RRC layer), and Non-Access Layer (NAS). Layers 1, 2, and 3 are referred to as the Access Layer (AS).
[0108] In 3GPP LTE systems, Layer 2 is divided into the following sublayers: MAC, RLC, and PDCP. In 3GPP NR systems, Layer 2 is divided into the following sublayers: MAC, RLC, PDCP, and SDAP. The PHY layer provides transport channels to the MAC sublayer, the MAC sublayer provides logical channels to the RLC sublayer, the RLC sublayer provides RLC channels to the PDCP sublayer, and the PDCP sublayer provides radio bearers to the SDAP sublayer. The SDAP sublayer provides Quality of Service (QoS) streams to the 5G core network.
[0109] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing MAC SDUs belonging to one or different logical channels into transport blocks (TBs) delivered to the physical layer on the transport channel / demultiplexing MAC SDUs belonging to one or different logical channels from transport blocks (TBs) delivered from the physical layer on the transport channel; scheduling information reporting; error correction via Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs via dynamic scheduling; priority handling between logical channels of a UE via logical channel prioritization; and padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. Mapping restrictions in logical channel prioritization control which parameter set(s), cell(s), and transmission timing(s) a logical channel(s) can use.
[0110] Different types of data transfer services are provided by the MAC. To accommodate these different data transfer services, several types of logical channels are defined, each supporting the transfer of a specific type of information. Each logical channel type is defined by the type of information being transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used only for the transfer of control plane information, and traffic channels are used only for the transfer of user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used for broadcasting system control information; the Paging Control Channel (PCCH) is a downlink logical channel for transferring paging information, system information change notifications, and indications of ongoing Public Warning Service (PWS) broadcasts; the Common Control Channel (CCCH) is a logical channel used to send control information between the UE and the network and is used by UEs without an RRC connection to the network; and the Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel used between the UE and the network to send dedicated control information and is used by UEs with an RRC connection. The Dedicated Traffic Channel (DTCH) is a point-to-point logical channel dedicated to a single UE for transferring user information. DTCHs can exist in both the uplink and downlink. In the downlink, the following connections exist between the logical channels and the transport channels: the ability to map the BCCH to the broadcast channel (BCH); the ability to map the BCCH to the downlink shared channel (DL-SCH); the ability to map the PCCH to the paging channel (PCH); the ability to map the CCCH to the DL-SCH; the ability to map the DCCH to the DL-SCH; and the ability to map the DTCH to the DL-SCH. In the uplink, the following connections exist between the logical channels and the transport channels: the ability to map the CCCH to the uplink shared channel (UL-SCH); the ability to map the DCCH to the UL-SCH; and the ability to map the DTCH to the UL-SCH.
[0111] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Node (AM). RLC configuration is per logical channel and independent of parameter sets and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper-layer PDUs; sequence numbering independent of either PDCP (UM or AM); error correction via ARQ (AM only); RLC SDU segmentation (AM and UM) and re-segmentation (AM only); SDU reassembly (AM and UM); duplicate detection (AM only); RLC SDU discarding (AM and UM); RLC reconstruction; and protocol error detection (AM only).
[0112] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); user data transmission; reordering and deduplication detection; in-order delivery; PDCP PDU routing (in the case of split bearers); PDCP SDU retransmission; encryption, decryption, and integrity protection; PDCP SDU discarding; PDCP reconstruction and data recovery for RLC AM; PDCP status reporting for RLC AM; and PDCP PDU deduplication and deduplication indication for lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; encryption, decryption, and integrity protection; control plane data transmission; reordering and deduplication detection; in-order delivery; and PDCP PDU deduplication and deduplication indication for lower layers.
[0113] In the 3GPP NR system, the main services and functions of SDAP include: mapping QoS flows to data radio bearers; marking QoS flow IDs (QFIs) in both DL and UL packets; and configuring a single SDAP protocol entity for each individual PDU session.
[0114] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcasting system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between UE and NG-RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers (SRB) and data radio bearers (DRB); mobility functions (including: handover and context transfer, UE cell selection and reselection, and control of cell selection and reselection, and inter-RAT mobility); QoS management functions; control of UE measurement reporting and reporting; detection and recovery of radio link failures; and NAS message transfer / from / to NAS and from / to UE.
[0115] Figure 8 The frame structure in a 3GPP-based wireless communication system applying embodiments of the present disclosure is shown.
[0116] Figure 8The frame structure shown is purely exemplary and the number of subframes, slots, and / or symbols in the frame can be varied. In 3GPP-based wireless communication systems, OFDM parameter sets (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) can be configured differently across multiple cells aggregated for a UE. For example, if the UE is configured with different SCSs for cell aggregation for a cell, the (absolute time) duration of time resources (e.g., subframes, slots, or TTIs) comprising the same number of symbols can be different across the aggregated cells. In this document, symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) symbols).
[0117] refer to Figure 8 Downlink and uplink transmissions are organized into frames. Each frame has a T f = 10ms duration. Each frame is divided into two half-frames, each half-frame having a duration of 5ms. Each half-frame consists of 5 subframes, where the duration of each subframe is T. sf It is 1ms. Each subframe is divided into time slots, and the number of time slots in a subframe depends on the subcarrier spacing. Each time slot consists of 14 or 12 OFDM symbols based on the cyclic prefix (CP). In normal CP, each time slot consists of 14 OFDM symbols, and in extended CP, each time slot consists of 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing Δf = 2. u *15kHz.
[0118] The table below is based on subcarrier spacing Δf = 2 u *15kHz indicates the number of OFDM symbols N per slot for normal CP. slot symb Number of time slots per frame N frame,u slot and the number of time slots N per subframe subframe,u slot .
[0119] [Table 1]
[0120] u <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16
[0121] Table 2 is based on the subcarrier spacing Δf = 2 u *15kHz indicates the number of OFDM symbols N per slot for extended CP. slot symb Number of time slots per frame N frame,u slot and the number of time slots N per subframe subframe,u slot .
[0122] [Table 2]
[0123] u <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 2 12 40 4
[0124] A time slot comprises multiple symbols (e.g., 14 or 12 symbols) in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a Common Resource Block (CRB) N is generated from the signaling at a higher layer (e.g., RRC signaling). start,u grid Initially, N was defined. size,u grid,x *N RB sc Subcarriers and N subframe,u symb A resource grid of OFDM symbols, where N size,u grid,x N is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for downlink and UL for uplink. RB sc N is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N... RB sc Typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there exists a resource grid. The carrier bandwidth N used for the subcarrier spacing configuration u... size,u grid These are given by higher-level parameters (e.g., RRC parameters). Each element in the resource grid used for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and a complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing the symbol position relative to a reference point in the time domain. In a 3GPP-based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.
[0125] In 3GPP NR systems, RBs are classified into CRBs and Physical Resource Blocks (PRBs). For subcarrier spacing configuration u, CRBs are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 in CRB 0 for subcarrier spacing configuration u coincides with 'point A', which serves as the common reference point for the resource block grid. In 3GPP NR systems, PRBs are defined within the Bandwidth Part (BWP) and numbered from 0 to N. size BWP,i -1 is the number, where i is the number of the bandwidth section. The physical resource block n within bandwidth section i... PRB With public resource block n CRB The relationship between n is as follows: PRB =n CRB +Nsize BWP,i , where N size BWP,i The bandwidth portion is the common resource block starting relative to CRB 0. A BWP consists of multiple consecutive RBs. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Only one BWP configured for the UE can be activated at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.
[0126] NR bands can be defined as two types of frequency ranges, namely FR1 and FR2. The numerical values of the frequency ranges can be changed. For example, the frequency ranges of the two types (FR1 and FR2) can be shown in Table 3 below. For ease of explanation, in the frequency ranges used in NR systems, FR1 can mean "sub-6 GHz range", FR2 can mean "above 6 GHz range", and can be referred to as millimeter wave (mmW).
[0127] [Table 3]
[0128] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz-6000MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz
[0129] As mentioned above, the frequency range of the NR system can be varied. For example, FR1 may include a frequency band from 410MHz to 7125MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925MHz, etc.) or more. For example, the 6GHz (or 5850, 5900, 5925MHz, etc.) or more frequency bands included in FR1 may include unlicensed bands. Unlicensed bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).
[0130] [Table 4]
[0131] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz
[0132] In this disclosure, the term "cell" can refer to a geographical area to which one or more nodes provide a communication system, or it can refer to radio resources. A "cell" as a geographical area can be understood as the coverage area in which a node can provide services using a carrier, and a "cell" as a radio resource (e.g., time-frequency resource) is associated with bandwidth as a frequency range configured by a carrier. A "cell" associated with radio resources is defined by a combination of downlink and uplink resources, such as a combination of DL component carriers (CC) and UL CCs. A cell can be configured by downlink resources only, or it can be configured by both downlink and uplink resources. Since the DL coverage area, which is the range in which a node can transmit valid signals, and the UL coverage area, which is the range in which a node can receive valid signals from a UE, depend on the carrier carrying the signal, a node's coverage area can be associated with the coverage area of the "cell" of radio resources used by the node. Therefore, the term "cell" can sometimes be used to refer to the service coverage area of a node, at other times to radio resources, or at other times to the range in which signals using radio resources can reach with effective strength.
[0133] In CA, two or more CCs are aggregated. The UE can receive or transmit simultaneously on one or more CCs, depending on its capabilities. CA is supported for both continuous and non-continuous CCs. When CA is configured, the UE has only one RRC connection with the network. During RRC connection establishment / re-establishment / handover, one serving cell provides NAS mobility information, and during RRC connection re-establishment / handover, one serving cell provides security input. This cell is called the primary cell (PCell). The PCell is the cell operating on the primary frequency, where the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capabilities, secondary cells (SCells) can be configured to form a set of serving cells together with the PCell. An SCell is a cell that provides additional radio resources on top of a specific cell (SpCell). The set of serving cells configured for the UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the primary cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). SpCell supports PUCCH transmission and contention-based random access and is always active. MCG is a group of serving cells associated with the primary node, consisting of SpCells (PCells) and optionally one or more SCells. For a UE with a DC configured, SCG is a subset of serving cells associated with the secondary node, consisting of PSCells and zero or more SCells. For a UE in RRC_CONNECTED without a CA / DC configured, there is only one serving cell consisting of PCells. For a UE in RRC_CONNECTED with a CA / DC configured, the term "serving cell" is used to refer to the set of cells consisting of SpCells and all SCells. In the DC, two MAC entities are configured in the UE: one for the MCG and one for the SCG.
[0134] Figure 9 An example of a data flow in a 3GPP NR system applying embodiments of the present disclosure is shown.
[0135] refer to Figure 9 “RB” indicates a radio bearer, and “H” indicates a header. Radio bearers are classified into two groups: DRBs for user plane data and SRBs for control plane data. MAC PDUs are sent to and received from external devices via the PHY layer using radio resources. MAC PDUs arrive at the PHY layer in the form of transport blocks.
[0136] In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their respective physical channels, the Physical Uplink Shared Channel (PUSCH) and the Physical Random Access Channel (PRACH), and the downlink transport channels DL-SCH, BCH, and PCH are mapped to the Physical Downlink Shared Channel (PDSCH), the Physical Broadcast Channel (PBCH), and the PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to the Physical Uplink Control Channel (PUCCH), and downlink control information (DCI) is mapped to the Physical Downlink Control Channel (PDCCH). MAC PDUs related to UL-SCH are transmitted by the UE via PUSCH based on UL authorization, and MAC PDUs related to DL-SCH are transmitted by the BS via PDSCH based on DL assignment.
[0137] The RRC state indicates whether the UE's RRC layer is logically connected to the E-UTRAN's RRC layer. In LTE / LTE-A, the UE is in the RRC connected state (RRC_CONNECTED) when an RRC connection is established between the UE's RRC layer and the E-UTRAN's RRC layer. Otherwise, the UE is in the RRC idle state (RRC_IDLE). In NR, an additional RRC inactive state (RRC_INACTIVE) is introduced. RRC_INACTIVE can be used for various purposes. For example, it can effectively manage Massive Machine Type Communication (MMTC) UEs in RRC_INACTIVE. A transition from one of the three states to another occurs when certain conditions are met.
[0138] Predefined operations can be performed based on the RRC status. In RRC_IDLE, Public Land Mobile Network (PLMN) selection, System Information (SI) broadcast, Cell Reselection Mobility, Core Network (CN) paging, and Discontinuous Receiver Optimization (DRX) configured by the NAS can be performed. The UE should have been assigned an identifier (ID) that uniquely identifies the UE within the tracking area. No RRC context is stored in the BS.
[0139] In RRC_CONNECTED, the UE has an RRC connection with the network (i.e., E-UTRAN / NG-RAN). A network CN connection (both C / U plane) is also established for the UE. The UE AS context is stored in both the network and the UE. The RAN knows the cell to which the UE belongs. The network is able to send and / or receive data to / from the UE. Mobility control, including measurements, is also performed.
[0140] Most operations performed in RRC_IDLE can also be performed in RRC_INACTIVE. However, instead of CN paging in RRC_IDLE, RAN paging is performed in RRC_INACTIVE. In other words, in RRC_IDLE, paging of mobile terminal (MT) data is initiated by the core network, and the paging area is managed by the core network. In RRC_INACTIVE, paging is initiated by NG-RAN, and the RAN-based notification area (RNA) is managed by NG-RAN. Furthermore, instead of the DRX configured by NAS for CN paging in RRC_IDLE, the DRX for RAN paging in RRC_INACTIVE is configured by NG-RAN. Simultaneously, in RRC_INACTIVE, a 5GC-NG-RAN connection is established for the UE (both C / U planes), and the UE AS context is stored in both NG-RAN and the UE. NG-RAN knows the RNA to which the UE belongs.
[0141] Pre-configured uplink resources (PURs) are designed for NB-IoT and MTC networks to conserve power during data transmission. The network can configure PURs for predictable service patterns for UEs in idle (e.g., RRC_IDLE) and / or inactive (e.g., RRC_INACTIVE) states. UEs can transmit UL data in RRC_IDLE and / or RRC_INACTIVE without a random access procedure and / or a state transition to a connected state (e.g., RRC_CONNECTED).
[0142] Regarding the use of PUR for transmission, the following has been agreed upon.
[0143] - For UEs with effective timing advance, transmission in a dedicated PUR in RRC_IDLE is supported.
[0144] -eNB can (re)configure and release dedicated PURs via dedicated RRC signaling.
[0145] - Supports periodic dedicated PURs with duration.
[0146] - Supports dedicated PURs with the possibility of being configured as single shot.
[0147] - If a dedicated PUR is indicated to be enabled in the cell, the UE can execute a dedicated PUR request / information.
[0148] - The network determines the dedicated PUR configuration.
[0149] - Requests / messages can include: the requested transport block size (TBS) and the periodicity of the request.
[0150] - When the eNB does not detect "m" consecutive UE transmissions, the dedicated PUR configuration can be released.
[0151] - When a UE performs a random access procedure on a new cell, it must release the dedicated PUR.
[0152] - Capable of setting up dedicated PUR configurations without predefined ends (unlimited).
[0153] - Capable of configuring TBS for dedicated PURs for both NB-IoT and eMTC, up to the maximum supported based on UE class and TBS capabilities.
[0154] - For the user plane, when transmitting using a dedicated PUR, the UE can send a dedicated PUR release request / (re)configuration request.
[0155] -RRC response messages require UE support and can be used in all situations.
[0156] - In some cases, L1 signaling is sufficient to respond, that is, no RRC response message is required.
[0157] - L1 signaling for response can only be sent after the eNB has determined that there is no pending DL data or signaling.
[0158] - The configuration of a dedicated PUR provided by RRC signaling may not be updated via L1 signaling.
[0159] Providing the UE with a UE-specific radio network temporary identifier (RNTI) for a dedicated PUR is feasible. Public or shared RNTIs are also feasible.
[0160] - The RNTI used for D-PUR is transmitted with signals along with other dedicated PUR configurations.
[0161] As described below, the current PUR design may always require monitoring the PDCCH. When DL information needs to be delivered on the PDSCH, the UE can first monitor the PDCCH to obtain PDSCH scheduling information. Then, the UE can receive the DL information via the PDSCH scheduled through the PDCCH.
[0162] Figure 10 An example of the general process of transmission using PUR is shown.
[0163] (1) The network configures PUR for the UE.
[0164] (2) The UE uses PUR to send UL data in RRC_IDLE and / or RRC_INACTIVE.
[0165] (3) The UE receives a response to the UL data transmission using PUR.
[0166] In order to receive a response to UL data transmission using PUR, the UE will monitor the PDCCH. Then, if further information such as Timing Advance Command (TAC) MAC Control Element (CE) is to be delivered on the PDSCH, the UE can use the scheduling information in the PDCCH to monitor the PDSCH.
[0167] Figure 11 Another example of the general process of transmission using PUR is shown.
[0168] (1) The UE uses PUR to send UL data in RRC_IDLE and / or RRC_INACTIVE.
[0169] (2) UE monitors PDCCH. PDCCH can carry scheduling information of PDSCH. PDCCH can carry responses to UL data transmission using PUR via L1 signaling.
[0170] (3) The UE obtains DL data / information on the PDSDH scheduled by the scheduling information in the PDCCH. The DL data / information may include a response to UL data transmission using PUR via RRC signaling. The DL data / information may further include TACMAC CE, etc.
[0171] In summary, after transmitting UL data using PUR, the UE can determine the completion of UL data transmission based on the response to the UL data transmission using PUR.
[0172] The response to UL data transmission using PUR can be an L1 signaling response received via PDCCH. After receiving the L1 signaling response via PDCCH, the UE can determine that the UL data transmission using PUR was successful and can consider the UL data transmission process using PUR to be completed without monitoring PDSCH.
[0173] Alternatively, the response to UL data transmission using PUR can be an L3 signaling response received via PDSCH. The UE can first monitor the PDCCH that schedules the PDSCH and can receive the response to UL data transmission using PUR via the PDSCH. After receiving the L3 signaling response via PDSCH, the UE can determine that the UL data transmission using PUR is successful and can consider the process of UL data transmission using PUR to be complete.
[0174] Meanwhile, because PUR-related configurations can persist for a long time, updating UL timing is important to avoid data transmission failures due to asynchronous UL transmissions and to save power. In some cases, even if the UE receives an L1 signaling acknowledgment via PDCCH to confirm the completion of UL data transmission using PUR, if the UE requires uplink timing alignment, it can receive a TAC MAC CE via PDSCH for uplink timing alignment. The UL data transmission using PUR can end after receiving the TAC MAC CE.
[0175] Therefore, a method may be needed for completing the process of UL data transmission using PUR via TAC MAC CE. Furthermore, in some cases, it may be beneficial for the UE to directly acquire DL information on the PDSCH without monitoring the PDCCH to reduce power consumption and to acquire DL information quickly on the PDSCH.
[0176] The following figures were created to illustrate specific embodiments of this disclosure. The names of specific devices or signals / messages / fields shown in the figures are provided as examples, and therefore the technical features of this disclosure are not limited to the specific names used in the following figures.
[0177] Figure 12 An example of a method performed by a wireless device configured to operate in a wireless communication system, applying embodiments of the present disclosure, is shown.
[0178] In step S1200, the wireless device receives the configuration of the PUR from the network.
[0179] In some implementations, the configuration of the PUR can be received via dedicated RRC signaling, L2 signaling (i.e., MAC CE), or L1 signaling (i.e., DCI). The configuration of the PUR can be received in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE.
[0180] In some implementations, the PUR configuration may further include information regarding DL transmissions associated with UL data transmissions using the PUR. Information regarding DL transmissions may include at least one of DL licensing and / or DL assignment. Information regarding DL transmissions may include DL reception time, the number of time slots per radio frame, subframe intervals, etc. DL reception time may be absolute time or time associated with UL data transmissions.
[0181] In step S1210, when in the RRC idle state and / or RRC inactive state, the wireless device i) performs UL data transmission to the network using PUR, ii) attempts to obtain DL information from the network on PDSCH, and iii) considers the UL data transmission using PUR to be successful based on the DL information including only TAC MAC CE.
[0182] In some implementations, DL information including only TAC MAC CE can be considered a response to UL data transmission.
[0183] In some implementations, the TAC MAC CE may consist of a single octet including a timing advance group (TAG) identifier field and a TAC field.
[0184] In some implementations, the wireless device may further indicate to the upper layer of the wireless device that the UL data transmission using PUR is successful.
[0185] In some implementations, DL information can be scheduled via scheduling information received from the network. The scheduling information can be received via PUR configuration. The scheduling information can be received via L1 signaling, L2 signaling, broadcast signaling, or dedicated RRC signaling. The scheduling information may include timing information regarding UL data transmission. The scheduling information may include scheduling parameters for PDSCH, including at least one of the following: SFN, number of time slots per radio frame, time slot number in the frame used for PDSCH, start point of the radio frame used for PDSCH, starting PRB of PDSCH, and / or number of subframes indicating the interval following UL data transmission using the PUR.
[0186] In some implementations, the PDCCH may not be monitored for obtaining DL information.
[0187] In some implementations, the wireless device can perform a PUR transmission failure procedure based on the absence of DL information and / or the DL information indicating that UL data transmission using PUR has failed. For example, it can be determined that DL information has not been acquired based on the expiration of a timer in the absence of any DL information. The timer can start when UL data transmission using PUR to the network is performed. For example, it can be determined that DL information has not been acquired based on the absence of information during a certain number of subframes.
[0188] In some implementations, the wireless device can communicate with at least one of a mobile device, a network, and / or an autonomous vehicle, in addition to the wireless device itself.
[0189] Furthermore, from the above... Figure 12 The method described in the text, from the perspective of wireless devices, can be derived from... Figure 2The first wireless device 100 shown Figure 3 The wireless device 100 shown Figure 4 The first wireless device 100 and / or shown Figure 5 The UE 100 shown is executed.
[0190] More specifically, the wireless device includes at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and storing instructions that, based on execution by the at least one processor, perform operations.
[0191] The operation includes receiving the configuration of the PUR from the network.
[0192] In some implementations, the configuration of the PUR can be received via dedicated RRC signaling, L2 signaling (i.e., MAC CE), or L1 signaling (i.e., DCI). The configuration of the PUR can be received in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE.
[0193] In some implementations, the PUR configuration may further include information regarding DL transmissions associated with UL data transmissions using the PUR. Information regarding DL transmissions may include at least one of DL licensing and / or DL assignment. Information regarding DL transmissions may include DL reception time, the number of time slots per radio frame, subframe intervals, etc. DL reception time may be absolute time or time associated with UL data transmissions.
[0194] The operation includes, when in an RRC idle state and / or an RRC inactive state, i) performing UL data transmission to the network using PUR, ii) attempting to obtain DL information from the network on the PDSCH, and iii) considering the UL data transmission using PUR successful based on DL information including only TAC MAC CE.
[0195] In some implementations, DL information including only TAC MAC CE can be considered a response to UL data transmission.
[0196] In some implementations, the TAC MAC CE may consist of a single octet including a TAG identifier field and a TAC field.
[0197] In some implementations, the operation may further include instructing the upper layer of the wireless device that the UL data transmission using PUR has been successful.
[0198] In some implementations, DL information can be scheduled via scheduling information received from the network. The scheduling information can be received via PUR configuration. The scheduling information can be received via L1 signaling, L2 signaling, broadcast signaling, or dedicated RRC signaling. The scheduling information may include timing information regarding UL data transmission. The scheduling information may include scheduling parameters for PDSCH, including at least one of the following: SFN, number of time slots per radio frame, time slot number in the frame used for PDSCH, start point of the radio frame used for PDSCH, starting PRB of PDSCH, and / or number of subframes indicating the interval following UL data transmission using the PUR.
[0199] In some implementations, the PDCCH may not be monitored for obtaining DL information.
[0200] In some implementations, a wireless device can perform a PUR transmission failure procedure based on the absence of DL information and / or the DL information indicating that UL data transmission using PUR has failed. For example, it can be determined that DL information has not been acquired based on the expiration of a timer in the absence of any DL information. The timer can start when UL data transmission using PUR to the network is performed. For example, it can be determined that DL information has not been acquired based on the absence of information during a certain number of subframes.
[0201] Furthermore, from the above... Figure 12 The method described in the article, which involves controlling the wireless device's perspective, can be implemented through controls included in... Figure 2 The processor 102 in the first wireless device 100 shown controls the processor 102 included in the first wireless device 100. Figure 3 The wireless device 100 shown includes a communication unit 110 and / or a control unit 120, which control the communication unit 110 and / or control unit 120 included in the wireless device 100. Figure 4 The processor 102 in the first wireless device 100 shown, and / or through control of the processor 102 included in the first wireless device 10 ... Figure 5 The processor 102 in the UE 100 shown here executes this.
[0202] More specifically, an apparatus for being configured to operate in a wireless communication system (e.g., a wireless device) includes at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one processor is configured to perform operations including acquiring a PUR (Programmable Receiver), and when in an RRC idle state and / or an RRC inactive state, i) control the wireless device to perform UL (Ultra-Low) data transmission using the PUR to the network, ii) attempt to acquire DL (Low-Level) information from the network on the PDSCH, and iii) consider the UL data transmission using the PUR to be successful based on the DL information including only the TAC MAC CE (Traceability Component CE).
[0203] Furthermore, from the above... Figure 12 The method described in the article, which involves viewing a wireless device from a different angle, can be stored in a format including... Figure 4 The software code 105 in the memory 104 of the first wireless device 100 shown is executed.
[0204] More specifically, at least one computer-readable medium (CRM) stores instructions that are based on being executed by at least one processor and perform operations including: acquiring the configuration of the PUR, and, when in an RRC idle state and / or an RRC inactive state, i) controlling the wireless device to perform UL data transmission to the network using the PUR, ii) attempting to acquire DL information from the network on the PDSCH, and iii) considering the UL data transmission using the PUR to be successful based on the DL information including only the TAC MAC CE.
[0205] Figure 13 Examples of methods performed by wireless devices and network nodes configured to operate in a wireless communication system, applying embodiments of the present disclosure, are shown.
[0206] In step S1300, the network node sends the PUR configuration to the wireless device.
[0207] In some implementations, the configuration of the PUR can be sent via dedicated RRC signaling, L2 signaling (i.e., MAC CE), or L1 signaling (i.e., DCI). The configuration of the PUR can be received in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE.
[0208] In some implementations, the PUR configuration may further include information regarding DL transmissions associated with UL data transmissions using the PUR. Information regarding DL transmissions may include at least one of DL licensing and / or DL assignment. Information regarding DL transmissions may include DL reception time, the number of time slots per radio frame, subframe intervals, etc. DL reception time may be absolute time or time associated with UL data transmissions.
[0209] In step S1310, when the wireless device is in an RRC idle state and / or an RRC inactive state, the network node receives UL data transmission using PUR from the wireless device.
[0210] In step S1320, the network node sends DL information to the wireless device that includes only TAC MAC CE.
[0211] In some implementations, the TAC MAC CE may consist of a single octet including a timing advance group (TAG) identifier field and a TAC field.
[0212] In some implementations, DL information can be scheduled via scheduling information sent to the wireless device. The scheduling information can be sent via the configuration of the PUR. The scheduling information can be sent via L1 signaling, L2 signaling, broadcast signaling, or dedicated RRC signaling. The scheduling information may include timing information regarding UL data transmission. The scheduling information may include scheduling parameters for PDSCH, including at least one of the following: SFN, number of time slots per radio frame, time slot number in the frame used for PDSCH, start point of the radio frame used for PDSCH, starting PRB of PDSCH, and / or number of subframes indicating the interval following UL data transmission using the PUR.
[0213] In step S1330, the wireless device considers the UL data transmission using PUR to be successful based on the DL information that includes only TAC MAC CE.
[0214] Furthermore, from the above... Figure 13 The method described in the text, from the perspective of network nodes, can be derived from... Figure 2 The second wireless device 100 shown represents a network node, Figure 3 The device 100 shown, and / or Figure 4 The second wireless device 200 shown is executed.
[0215] More specifically, the network node includes at least one transceiver, at least one processor, and at least one computer memory, the at least one computer memory being operatively connected to the at least one processor and storing instructions based on the instructions executed by the at least one processor to perform operations including: sending a PUR configuration to a wireless device, and when the wireless device is in an RRC idle state and / or an RRC inactive state, i) receiving UL data transmission using the PUR from the wireless device, and ii) sending DL information to the wireless device consisting only of TAC MAC CE. UL data transmission using the PUR is considered successful based on the DL information consisting only of TAC MAC CE.
[0216] Figure 14 Examples of methods for obtaining DL information on PDSCH in RRC_IDLE and / or RRC_INACTIVE, to which embodiments of this disclosure are applied, are shown.
[0217] In step S1400, the UE receives the PUR configuration from the network.
[0218] In some implementations, the network can configure the PUR via dedicated RRC signaling or L2 signaling (i.e., MAC CE) or L1 signaling (i.e., DCI) in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE.
[0219] In some implementations, the network may also use PUR to configure DL transmission information associated with UL transmissions. DL transmission information may include at least one of DL licensing and / or DL assignment. DL transmission information may include DL reception time, the number of time slots per radio frame, subframe intervals, etc. DL reception time may be absolute time and / or time associated with UL transmissions.
[0220] In step S1410, the UE receives PDSCH scheduling information from the network.
[0221] In some implementations, PDSCH scheduling information can be delivered along with PUR configuration.
[0222] In some implementations, PDSCH scheduling information can be delivered via L1 signaling, L2 signaling, broadcast signaling, and / or dedicated RRC signaling.
[0223] In some implementations, PDSCH scheduling information may include absolute time and / or time associated with UL transmission.
[0224] In some implementations, PDSCH scheduling information may include scheduling parameters for PDSCH. These scheduling parameters may include at least one of the following: SFN, number of slots per radio frame, slot number in the frame, start point of the radio frame for PDSCH, starting PRB of PDSCH, and / or number of subframes indicating the interval following a transmission using a PUR.
[0225] In some implementations, the UE can perform a connection release procedure with the network. The UE can receive an RRC release message from the network. After receiving the RRC release message, the UE can enter RRC_IDLE and / or RRC_INACTIVE.
[0226] In step S1420, the UE sends UL data using PUR to the network.
[0227] In some implementations, the UE can start a timer when transmitting UL data. The UE's MAC layer or RRC layer can maintain the timer. When the timer expires without acquiring any DL information, the UE can consider the UL transmission using PUR to have failed.
[0228] In step S1430, the UE attempts to obtain DL information on the PDSCH.
[0229] In some implementations, the UE may refer to the PDSCH scheduling information received in step S1410. In this case, the UE may not need to monitor the PDCCH to obtain DL information on the PDSCH.
[0230] In some implementations, if the PDSCH scheduling information received in step S1410 is unavailable, the UE can monitor the PDCCH to obtain DL information on the PDSCH.
[0231] In some implementations, DL information may include at least one of the following: UL transmission response, TAC MAC CE, coverage enhancement level, DL user data information, etc.
[0232] In some implementations, if the DL information includes TAC MAC CE but does not include a UL transmission response, the UE may consider the UL transmission using PUR to be successful. In other words, if the DL information only includes TAC MAC CE, the UE may consider the UL transmission using PUR to be successful based on the DL information that only includes TAC MAC CE.
[0233] Figure 15 An example of a TAC MAC CE applying an embodiment of the present disclosure is shown.
[0234] The TAC MAC CE is identified by a MAC PDU subheader with a Logical Channel ID (LCID).
[0235] TAC MAC CE has a fixed size and consists of a single octet, as defined below:
[0236] -TAG Id: This field indicates the TAG identifier of the addressed TAG. TAGs containing SpCells have a TAG identifier of 0. The field length is 2 bits.
[0237] - Timing Advance Command: This field indicates the index value T used to control the amount of timing adjustment that must be applied to the MAC entity. A (0, 1, 2...63). This field has a length of 6 bits.
[0238] Figure 16 An example of a TAC MAC CE including a UL transmission response applied to an embodiment of this disclosure is shown.
[0239] The UE can receive a TAC MAC CE that includes the TAC. The TAC MAC CE may also include an acknowledgment bit (in...). Figure 16 (represented as "A" in the text). If the response field indicates that the UL transmission using PUR has failed, the UE can apply UL timing advance and execute the PUR transmission failure procedure.
[0240] Figure 17 Another example of a TAC MAC CE including a UL transmission response, which applies an embodiment of this disclosure, is shown.
[0241] The UE can receive a TAC MAC CE that includes a TAC. The TAC MAC CE may also include an acknowledgment field (in...). Figure 17 The UE information is represented as “A”), the UE-specific RNTI, and the timing advance group identifier (TAG-ID). When the UE information matches the UE-specific RNTI or TAG-ID, the UE can apply UL timing advance.
[0242] return Figure 14 In step S1440, if the UE does not obtain any DL information on the PDSCH and / or the DL information indicates that the UL transmission using PUR has failed, the UE performs the PUR transmission failure procedure.
[0243] In some implementations, the UE can determine that it has not obtained DL information on the PDSCH by the expiration of a timer that has already started during UL transmission.
[0244] In some implementations, if no information is acquired during a certain number of subframes, the UE can determine that no DL information has been acquired.
[0245] Figure 18 An example of optimizing transmission using PUR for a control plane cellular IoT (CIoT) evolution packet system (EPS) / 5G system (5GS) using embodiments of the present disclosure is shown.
[0246] The transmission characteristics using PUR for control plane CIoT EPS optimization and control plane CIoT 5GS optimization are as follows:
[0247] -Use PUR resources to send UL user data in the NAS message cascaded in the RRC EarlyDataRequest message on CCCH;
[0248] - If there is no downlink data, the (ng-)eNB can terminate the process by sending a Level 1 response that optionally includes a time advance command, a MAC time advance command, or an RRCEarlyDataComplete without user data.
[0249] - If so, DL user data is sent in a NAS message concatenated in the RRCEarlyDataComplete message on CCCH;
[0250] - No conversion to RRC CONNECTED.
[0251] In step S1800, the UE has determined that it can use PUR resources (e.g., enabling PUR in the cell, effective time alignment, etc.).
[0252] In step S1810, the UE sends an RRCEarlyDataRequest message containing UL user data in a NAS message (e.g., dedicatedInfoNas) via PUR resources.
[0253] If the UL data is too large to be included in the RRCEarlyDataRequest, the UE can use the PUR resource to send an RRCConnectionRequest. This process will revert to the traditional RRC connection establishment procedure, and a new Cell Radio Network Temporary Identifier (C-RNTI) can be assigned.
[0254] After step S1810, the (ng-)eNB can request the UE to suspend the transmission using the PUR by sending a Level 1 backoff instruction.
[0255] In step S1820, the MO-EDT process for control plane CIoT EPS / 5GS optimization is performed.
[0256] In step S1830, if the (ng-)eNB knows that there is no pending DL data or signaling, the (ng-)eNB can send a Layer 1 ACK, which may optionally include time advance adjustment, to the UE to update the TA and terminate the process.
[0257] In step S1832, if the (ng-)eNB knows that there is no further data or signaling, the (ng-)eNB can send a time advance command to update the TA and terminate the process.
[0258] In step S1834, the (ng-)eNB can send an RRCEarlyDataComplete message, which may optionally include DL user data from a NAS message (e.g., dedicatedInfoNAS). It can also include a time advance command.
[0259] If the MME / AMF or (ng-)eNB decides to move the UE to RRC_CONNECTED mode, an RRCConnectionSetup message is sent in steps S1830 to S1834 to fall back to the traditional RRC connection establishment procedure, and a new C-RNTI can be assigned. The (ng-)eNB will discard the zero-length NAS PDU received in the RRCConnectionSetupComplete message.
[0260] If none of the following responses—Level 1 Response, MAC Time Advance Command, RRCEarlyDataComplete, and (in the case of fallback) RRCConnectionSetup—is received in response to RRCEarlyDataRequest, the UE considers the UL data transmission unsuccessful.
[0261] In step S1840, the S1 / AN release process is executed.
[0262] Figure 19 An example of a transmission using PUR for user plane CIoT EPS optimization is shown, in which embodiments of this disclosure are applied. Figure 20 An example of a transmission using PUR optimized for user plane CIoT 5GS is shown, illustrating an embodiment of this disclosure.
[0263] The transmission characteristics of PUR used for user plane CIoT EPS optimization and user plane CIoT 5GS optimization are as follows:
[0264] - The UE is in RRC_IDLE and has valid PUR resources;
[0265] - The NextHopChainingCount has been provided to the UE in the RRCConnectionRelease message with the suspension indication;
[0266] - Send UL user data on DTCH that is multiplexed with the RRCConnectionResumeRequest message on CCCH;
[0267] -Optionally, DL user data can be sent on the DTCH, which is multiplexed with the RRCConnectionRelease message on the DCCH;
[0268] - Encrypt user data in UL and DL. Export the key using NextHopChainingCount provided in the RRCConnectionRelease message of the previous RRC connection;
[0269] - Use the newly exported key to perform integrity protection and encryption on RRCConnectionRelease messages;
[0270] - No conversion to RRC CONNECTED.
[0271] In steps S1900 / S2000, the UE has verified the PUR resources according to the configured criteria.
[0272] In steps S1910 / S2010, the UE sends the RRCConnectionResumeRequest message along with UL user data via PUR resources.
[0273] If the user data is too large to be fully included in a transmission using a PUR, the UE can use a PUR to send an RRCConnectionResumeRequest and user data segments. This process will revert to the traditional RRC connection recovery procedure and will be able to assign a new C-RNTI.
[0274] After steps S1910 / S2010, the (ng-)eNB can request the UE to suspend transmission using the PUR by sending a Level 1 backoff instruction.
[0275] In steps S1920 / S2020, the MO-EDT process for user plane CIoT EPS / 5GS optimization is performed.
[0276] In steps S1930 / S2030, the (ng-)eNB may optionally send an RRCConnectionRelease message along with the DL user data. It may also include a time advance command.
[0277] If the MME / AMF or (ng-)eNB decides to move the UE to RRC_CONNECTED mode, an RRCConnectionResume message is sent in step S1930 / S2030 to fall back to the RRC connection recovery procedure. In this case, the RRCConnectionResume message is integrity protected and encrypted using the key derived in step S1900 / S2000, and the UE ignores the NextHopChainingCount included in the RRCConnectionResume message. A new C-RNTI can be assigned. DL data can be sent on the DTCH multiplexed with the RRCConnectionResume message. Furthermore, an RRCConnectionSetup message can also be sent in step S1930 / S2030 to fall back to the RRC connection establishment procedure.
[0278] This disclosure can have various beneficial effects.
[0279] For example, the UE can effectively determine whether UL data transmission using PUR is successful based on DL information. If the DL information only includes TAC MAC CE, the UE can consider UL data transmission using PUR to be successful.
[0280] For example, the UE does not need the PDCCH and can directly obtain DL information on the PDSCH. The network can use UL resource configuration to configure PDSCH scheduling information. By skipping PDCCH monitoring, the UE can reduce the power consumption of PDCCH monitoring and obtain DL information quickly.
[0281] The beneficial effects that can be obtained through specific embodiments of this disclosure are not limited to those listed above. For example, various technical effects may be present that can be understood and / or derived from this disclosure by those skilled in the art. Therefore, the specific effects of this disclosure are not limited to those explicitly described herein, but may include a variety of effects that can be understood or derived from the technical features of this disclosure.
[0282] The claims in this specification can be combined in various ways. For example, the technical features in the method claims can be combined to implement or perform in an apparatus, and the technical features in the apparatus claims can be combined to implement or perform in a method. Furthermore, the technical features in the method claims and apparatus claims can be combined to implement or perform in a method. Other implementations are within the scope of the appended claims.
Claims
1. A method performed by a wireless device, the method comprising: Receive pre-configured uplink resource (PUR) settings from the network; Transmissions using PUR are initiated from Radio Resource Control (RRC) idle without a random access procedure and / or state transition to connected state; Following the transmission using PUR, the Physical Downlink Control Channel (PDCCH) is monitored based on a timer, wherein the timer starts at the end of the transmission using PUR; While the timer is running, based on (i) downlink (DL) information being acquired, and (iii) the DL information including only the Timing Advance Command (TAC) Media Access Control (MAC) control element (CE), the transmission using PUR is considered successful; and Based on the expiration of the timer, it is considered that the transmission using PUR has failed.
2. The method according to claim 1, wherein, The TAC MAC CE is considered to be a response to the transmission using PUR.
3. The method according to claim 1, wherein, The TAC MAC CE consists of a single octet including a timing advance group (TAG) identifier field and a TAC field.
4. The method according to claim 1, wherein, The method further includes: While the timer is running, based on (i) the acquisition of the DL information and (iii) the DL information including only TAC MAC CE, the upper layer of the wireless device is informed that the transmission using PUR is successful.
5. The method according to claim 1, wherein, The DL information is scheduled using scheduling information received from the network.
6. The method according to claim 5, wherein, The scheduling information is included in the PUR configuration.
7. The method according to claim 5, wherein, The scheduling information is received via L1 signaling, L2 signaling, broadcast signaling, or dedicated RRC signaling.
8. The method according to claim 5, wherein, The scheduling information includes time information regarding the transmission using PUR.
9. The method according to claim 1, wherein, The method further includes: The transmission using PUR is considered to have failed if (i) the DL information is not acquired and / or (ii) the DL information indicates that the transmission using PUR has failed.
10. The method according to claim 1, wherein, The wireless device communicates with at least one of a mobile device, a network, and / or an autonomous vehicle other than the wireless device.
11. A wireless device, comprising: At least one transceiver; At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and storing instructions that, based on execution by the at least one processor, perform operations including: Receive pre-configured uplink resource (PUR) settings from the network; Transmissions using PUR are initiated from Radio Resource Control (RRC) idle without a random access procedure and / or state transition to connected state; Following the transmission using PUR, the Physical Downlink Control Channel (PDCCH) is monitored based on a timer, wherein the timer starts at the end of the transmission using PUR; While the timer is running, based on (i) downlink (DL) information being acquired, and (iii) the DL information including only the Timing Advance Command (TAC) Media Access Control (MAC) control element (CE), the transmission using PUR is considered successful; and Based on the expiration of the timer, it is considered that the transmission using PUR has failed.
12. A wireless device, comprising: At least one processor; and At least one computer memory, operatively connected to the at least one processor, The at least one processor is configured to perform operations including the following: Receive pre-configured uplink resource (PUR) settings from the network; Transmissions using PUR are initiated from Radio Resource Control (RRC) idle without a random access procedure and / or state transition to connected state; Following the transmission using PUR, the Physical Downlink Control Channel (PDCCH) is monitored based on a timer, wherein the timer starts at the end of the transmission using PUR; While the timer is running, based on (i) downlink (DL) information being acquired, and (iii) the DL information including only the Timing Advance Command (TAC) Media Access Control (MAC) control element (CE), the transmission using PUR is considered successful; and Based on the expiration of the timer, it is considered that the transmission using PUR has failed.