Method and apparatus for performing bandwidth portion operation for system information request by REDCAP UE in wireless communication system

Abstract

The present disclosure relates to a method for performing an operation for a user equipment (UE) in a wireless communication system. Specifically, the method includes receiving information about a common initial downlink (DL) bandwidth portion (BWP) and a UE type specific initial DL BWP; performing a random access procedure using a random access resource on an initial uplink (UL) BWP of a supplemental uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type specific initial DL BWP, in which the PDCCH is monitored on the common initial downlink BWP based on initiating a random access procedure for a system information (SI) request and providing random access resources for the SI request by a higher layer.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing a bandwidth part (BWP) operation with respect to a system information (SI) request by a user equipment (UE) with reduced capability (RedCap) in the wireless communication system. Background Art

[0002] The introduction of new radio communication technologies has led to an increase in the number of user equipments (UEs) to which a base station (BS) provides services in a specified resource area, and has also led to an increase in the amount of data and control information sent by the BS to the UE. Since the resources available to the BS for communication with the UE are generally limited, new technologies are needed by which the BS can efficiently receive / send uplink / downlink data and / or uplink / downlink control information using limited radio resources. In particular, in applications where performance depends heavily on delay / latency, overcoming delay or latency has become an important challenge. Summary of the invention

[0003] Technical issues

[0004] Therefore, an object of the present disclosure is to provide a method and apparatus for performing a bandwidth part (BWP) operation with respect to a system information (SI) request by a user equipment (UE) with reduced capability (RedCap) in a wireless communication system.

[0005] Technical Solution

[0006] The object of the present disclosure can be achieved by a method for performing operations of a user equipment (UE) in a wireless communication system, comprising the following steps: receiving information about a common initial downlink (DL) bandwidth part (BWP) and a UE type-specific initial DL BWP; performing a random access procedure using random access resources on an initial uplink (UL) BWP of a supplementary uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type-specific initial DL BWP, wherein if the random access procedure is initiated for a system information (SI) request and random access resources for the SI request are provided by a higher layer, the PDCCH is monitored on the common initial DL BWP.

[0007] In addition, a user equipment (UE) in a wireless communication system is proposed, comprising: at least one transceiver; at least one processor; and at least one computer memory, which is operably connected to the at least one processor and stores instructions, which when executed cause the at least one processor to perform operations, the operations including: receiving information about a common initial downlink (DL) bandwidth part (BWP) and a UE type-specific initial DL BWP; performing a random access procedure using random access resources on an initial uplink (UL) BWP of a supplementary uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type-specific initial DL BWP, wherein if the random access procedure is initiated for a system information (SI) request and random access resources for the SI request are provided by a higher layer, the PDCCH is monitored on the common initial DL BWP.

[0008] Preferably, if the random access procedure is not initiated for the SI request or no random access resources for the SI request are provided based on higher layers, the PDCCH is monitored on the UE type specific initial DL BWP.

[0009] Preferably, the UE type specific initial DL BWP includes a reduced capability (RedCap) UE specific initial DL BWP.

[0010] Preferably, the initial UL BWP includes at least one of a common initial UL BWP and a reduced capability (RedCap) UE-specific initial UL BWP.

[0011] Preferably, performing the random access procedure includes selecting a random access resource for sending a random access preamble. Therefore, if the random access resource for the SI request is provided by a higher layer, the random access resource for the SI request is selected as the random access resource for sending the random access preamble.

[0012] Those skilled in the art will appreciate that the effects that can be achieved by the present disclosure are not limited to the effects specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description.

[0013] Beneficial Effects

[0014] According to the present disclosure, even if the SUL carrier is used for Msg1-based SI request by the RedCap UE, the RedCap UE can correctly receive the random access response in the legacy DL BWP.

[0015] Effects obtainable from the present disclosure may not be limited to the effects mentioned above. Also, those skilled in the art to which the present invention pertains can clearly understand other unmentioned effects from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are included to provide a further understanding of the present disclosure, illustrate embodiments of the present disclosure and together with the description serve to explain the principle of the present disclosure:

[0017] Figure 1 An example of a communication system 1 to which an embodiment of the present disclosure is applied is illustrated;

[0018] Figure 2 is a block diagram illustrating an example of a communication device capable of performing the method according to the present disclosure;

[0019] Figure 3 An example of a frame structure in a 3GPP-based wireless communication system is illustrated;

[0020] Figure 4 An example of a protocol stack in a wireless communication system based on the 3rd Generation Partnership Project (3GPP) is illustrated;

[0021] Figure 5 Figure 1 shows an example of data flow in a 3GPP New Radio (NR) system;

[0022] Figure 6 An example of PDSCH time domain resource allocation through PDCCH and an example of PUSCH time resource allocation through PDCCH are shown;

[0023] Figure 7 illustrates an example of physical layer processing at the transmit side;

[0024] Figure 8 illustrates an example of physical layer processing at a receiving side;

[0025] Fig. 9 and Fig.10 An example of a random access procedure supported by an NR system is shown; and

[0026] Fig.11 A flow chart illustrating an example of performing a Msg1-based SI request on a SUL by a RedCap UE according to the present disclosure. DETAILED DESCRIPTION

[0027] Reference will now be made in detail to exemplary embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. The detailed description given below with reference to the accompanying drawings is intended to explain exemplary embodiments of the present disclosure, rather than to illustrate the only embodiment that can be implemented according to the present disclosure. The following detailed description includes specific details in order to provide a thorough understanding of the present disclosure. However, it is apparent to those skilled in the art that the present disclosure can be practiced without these specific details.

[0028] The following techniques, devices, and systems may be applied to various 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 may be embodied by a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be embodied by a radio technology such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be embodied by a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE adopts OFDMA in DL and SC-FDMA in UL. LTE-Advanced (LTE-A) is an evolved version of 3GPP LTE.

[0029] For the convenience of description, the embodiments of the present disclosure are mainly described for a wireless communication system based on 3GPP. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a wireless communication system based on 3GPP, aspects of the present disclosure that are not limited to a wireless communication system based on 3GPP are applicable to other mobile communication systems. For terms and techniques that are not specifically described among the terms and techniques used in the present invention, reference may be made to wireless communication standard documents issued before the present disclosure. For example, reference may be made to the following documents.

[0030] 3GPP LTE

[0031] - 3GPP TS 36.211: Physical channels and modulation

[0032] - 3GPP TS 36.212: Multiplexing and channel coding

[0033] - 3GPP TS 36.213: Physical layer procedures

[0034] - 3GPP TS 36.214: Physical layer; Measurement

[0035] -3GPP TS 36.300: General description

[0036] - 3GPP TS 36.304: User Equipment (UE) procedures in idle mode

[0037] - 3GPP TS 36.314: Layer 2 - Measurement

[0038] - 3GPP TS 36.321: Medium Access Control (MAC) Protocol

[0039] - 3GPP TS 36.322: Radio Link Control (RLC) protocol

[0040] - 3GPP TS 36.323: Packet Data Convergence Protocol (PDCP)

[0041] - 3GPP TS 36.331: Radio Resource Control (RRC) protocol

[0042] 3GPP NR (e.g. 5G)

[0043] - 3GPP TS 38.211: Physical channels and modulation

[0044] - 3GPP TS 38.212: Multiplexing and channel coding

[0045] - 3GPP TS 38.213: Physical layer procedures for control

[0046] - 3GPP TS 38.214: Physical layer procedures for data

[0047] - 3GPP TS 38.215: Physical layer measurements

[0048] - 3GPP TS 38.300: General description

[0049] - 3GPP TS 38.304: User Equipment (UE) procedures in idle mode and RRC inactive state

[0050] - 3GPP TS 38.321: Medium Access Control (MAC) Protocol

[0051] - 3GPP TS 38.322: Radio Link Control (RLC) protocol

[0052] - 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0053] - 3GPP TS 38.331: Radio Resource Control (RRC) protocol

[0054] - 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0055] - 3GPP TS 37.340: Multiple Connectivity; General Description

[0056] In the present disclosure, a user equipment (UE) may be a fixed or mobile device. Examples of UE include various devices that send and receive user data and / or various control information to and from a base station (BS). In the present disclosure, a BS generally refers to a fixed station that performs communication with a UE and / or other BSs, and exchanges various data and control information with the UE and other BSs. The BS may be referred to as an advanced base station (ABS), a node B (NB), an evolved node B (eNB), a base station transceiver system (BTS), an access point (AP), a processing server (PS), etc. In particular, a BS of a UMTS is referred to as an NB, a BS of an enhanced packet core (EPC) / long term evolution (LTE) system is referred to as an eNB, and a BS of a new radio (NR) system is referred to as a gNB.

[0057] In the present disclosure, a node refers to a point that can send / receive a radio signal by communicating with a UE. Various types of BSs can be used as nodes regardless of their terminology. For example, a BS, a Node B (NB), an eNode B (eNB), a micro cell eNB (PeNB), a home eNB (HeNB), a relay, a repeater, etc. can be a node. In addition, a node may not be a BS. For example, a node may be a radio remote head (RRH) or a radio remote unit (RRU). The power level of an RRH or RRU is generally lower than that of a BS. Because an RRH or RRU (hereinafter referred to as RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, the cooperative communication between the RRH / RRU and the BS can be performed smoothly compared to the cooperative communication between the BSs connected via a radio line. At least one antenna is installed on each node. The antenna may include a physical antenna or an antenna port or a virtual antenna.

[0058] In the present disclosure, the term "cell" may refer to a geographical area to which one or more nodes provide a communication system, or to a radio resource. A "cell" of a geographical area may be understood as a coverage in which a node can provide a service using a carrier, and a "cell" as a radio resource (e.g., a time-frequency resource) is associated with a bandwidth (BW) as a frequency range configured by a carrier. A "cell" associated with a radio resource is defined by a combination of downlink resources and uplink resources, for example, a combination of a downlink (DL) component carrier (CC) and an uplink (UL) CC. A cell may be configured only by downlink resources, or may be configured by downlink resources and uplink resources. Because the DL coverage as a range in which a node can send a valid signal and the UL coverage as a range in which a node can receive a valid signal from a UE depend on the carrier carrying the signal, the coverage of a node may be associated with the coverage of a "cell" of a radio resource used by the node. Therefore, the term "cell" may sometimes be used to indicate the service coverage of a node, to indicate a radio resource at other times, or to indicate a range in which a signal using a radio resource can reach with effective strength at other times.

[0059] In the present disclosure, the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH) refer to a set of time-frequency resources or resource elements (REs) carrying downlink control information (DCI) and a set of time-frequency resources or REs carrying downlink data, respectively. In addition, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH) and the physical random access channel (PRACH) refer to a set of time-frequency resources or REs carrying uplink control information (UCI), a set of time-frequency resources or REs carrying uplink data, and a set of time-frequency resources or REs carrying random access signals, respectively.

[0060] In carrier aggregation (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 contiguous and non-contiguous CCs. When CA is configured, the UE has only one Radio Resource Control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information at RRC connection establishment / reestablishment / handover, and one serving cell provides security input at RRC connection reestablishment / handover. This cell is called the primary cell (PCell). A PCell is a cell operating on the primary frequency in which the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. Depending on the capabilities of the UE, a secondary cell (SCell) can be configured to form a set of serving cells together with the PCell. An SCell is a cell that provides additional radio resources over a special cell. Therefore, the set of serving cells configured for a UE always consists of one PCell and one or more SCells. In the present disclosure, for dual connectivity (DC) operation, the term "special cell" refers to the PCell of the master cell group (MCG) or the PSCell of the secondary cell group (SCG), and otherwise the term special cell refers to the PCell. The SpCell supports physical uplink control channel (PUCCH) transmission and contention-based random access and is always active. The MCG is a set of serving cells associated with the master node, including the SpCell (PCell) and optionally one or more SCells. The SCG is a subset of the serving cells associated with the secondary node, including the PSCell and zero or more SCells, for UEs configured with DC. For UEs in RRC_CONNECTED that are not configured with CA / DC, there is only one serving cell consisting of the PCell. For UEs in RRC_CONNECTED that are configured with CA / DC, the term "serving cell" is used to refer to the set of cells consisting of the SpCell and all SCells.

[0061] MCG is a set of service cells associated with a primary BS that terminates at least S1-MME, and SCG is a set of service cells associated with a secondary BS that provides additional radio resources to the UE but is not a primary BS. SCG includes a primary SCell (PSCell) and optionally one or more SCells. In DC, two MAC entities are configured in the UE: one for MCG and one for SCG. Each MAC entity is configured by RRC with a service cell that supports PUCCH transmission and contention-based random access. In the present disclosure, the term SpCell refers to such a cell, while the term SCell refers to other service cells. Depending on whether the MAC entity is associated with MCG or SCG, the term SpCell refers to the PCell of MCG or the PSCell of SCG, respectively.

[0062] In this disclosure, monitoring a channel refers to attempting to decode the channel. For example, monitoring a physical downlink control channel (PDCCH) refers to attempting to decode the PDCCH (or a PDCCH candidate).

[0063] In the present invention, "C-RNTI" refers to cell RNTI, "SI-RNTI" refers to system information RNTI, "P-RNTI" refers to paging RNTI, "RA-RNTI" refers to random access RNTI, "SC-RNTI" refers to single cell RNTI, "SL-RNTI" refers to side link RNTI, "SPS C-RNTI" refers to semi-persistent scheduling C-RNTI, and "CS-RNTI" refers to configured scheduling RNTI.

[0064] Figure 1 An example of a communication system 1 to which an embodiment of the present disclosure is applied is illustrated.

[0065] The three main demand categories for 5G include (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable low-latency communication (URLLC) category.

[0066] Some use cases may require multiple categories for optimization, while others may focus on just one key performance indicator (KPI). 5G supports this variety of use cases with a flexible and robust approach.

[0067] eMBB goes far beyond basic mobile Internet access and covers rich two-way work and media and entertainment applications in the cloud and augmented reality. Data is one of the core drivers of 5G, and in the 5G era, dedicated voice services may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application using the data connection provided by the communication system. The main reason for the increase in traffic is due to the increase in the size of the content and the increase in the number of applications requiring high data transmission rates. As more devices are connected 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 special use case that accelerates the growth of uplink data transmission rates. 5G is also used for remote work in the cloud. When using a tactile interface, 5G requires lower end-to-end latency to maintain a good user experience. Entertainment, such as cloud games and video streaming, is another core element that increases the demand for mobile broadband capabilities. Entertainment is necessary for smartphones and tablets in any place including high mobility environments such as trains, vehicles and airplanes. Other use cases are augmented reality and information search for entertainment. In this case, augmented reality requires very low latency and instantaneous data volume.

[0068] Additionally, one of the most anticipated 5G use cases involves the ability to smoothly connect embedded sensors in all fields, i.e. mMTC. The number of potential IoT devices is expected to reach 20.4 billion by 2020. Industrial IoT is one of the categories that performs the main role of enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0069] URLLC includes new services that will transform industries through remote control of key infrastructure and ultra-reliable / available low-latency links, such as self-driving vehicles. The levels of reliability and latency are necessary to control smart grids, automate industry, enable robotics, and control and adjust drones.

[0070] 5G is a means of providing streaming that is 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). Such fast speeds are required to deliver TV with a resolution of 4K or higher (6K, 8K, etc.) as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. Specific applications may require special network configurations. For example, for VR games, game companies need to merge core servers into the network operator's edge network servers in order to minimize latency.

[0071] Along with many use cases for vehicle mobile communications, cars are expected to become a new important driving force in 5G. For example, passenger entertainment requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect high-quality connections regardless of their location and speed. Another use case in the automotive field is the AR dashboard. The AR dashboard enables the driver to identify objects in the dark in addition to objects seen from the front window, and displays the distance to the object and the movement of the object by overlapping information that talks 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 accompanying pedestrians). The safety system guides alternative routes for behavior so that drivers can drive more safely, thereby reducing the risk of accidents. The next stage will be remote control or self-driving vehicles. This requires very high reliability and very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will perform all driving activities and drivers will only focus on abnormal traffic that the vehicle cannot recognize. The technical requirements for self-driving vehicles require ultra-low latency and ultra-high reliability, so that traffic safety is improved to a level that humans cannot reach.

[0072] Smart cities and smart homes / buildings referred to as smart societies will be embedded in high-density wireless sensor networks. Distributed networks of smart sensors will identify situations where cost and energy efficiency maintenance is required in a city or home. Similar configurations can be performed for individual households. All temperature sensors, window and heating controls, burglar alarms, and home appliances are connected wirelessly. Many of these sensors typically have low data transmission rates, power, and cost. However, certain types of equipment may require real-time HD video to perform monitoring.

[0073] The consumption and distribution of energy, including heat or gas, is highly distributed, making it necessary to automate the control of the distribution sensor network. Smart grids use digital information and communication technologies to collect information and connect sensors to each other in order to act on the collected information. Since this information may include the behavior of supply companies and consumers, smart grids can improve the distribution of fuels such as electricity by methods with efficiency, reliability, economic viability, production sustainability and automation. Smart grids can also be considered as another sensor network with low latency.

[0074] Mission-critical applications such as e-health are one of the 5G use cases. The health segment contains many applications that can benefit from mobile communications. The communication system can support telemedicine that provides clinical treatment in distant locations. Telemedicine can help reduce distance barriers and improve access to medical services that are not continuously available in remote rural areas. Telemedicine is also used to perform important treatments in emergency situations and save lives. Wireless sensor networks based on mobile communications can provide remote monitoring and sense parameters such as heart rate and blood pressure.

[0075] Wireless and mobile communications are gradually becoming important in the field of industrial applications. Cabling is high in terms of installation and maintenance costs. Therefore, the possibility of replacing cables with reconfigurable wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary to establish wireless connections with latency, reliability and capacity similar to those of cables and to simplify the management of wireless connections. When it is necessary to connect to 5G, low latency and very low error probability are new requirements.

[0076] Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable inventory and package tracking anywhere. Logistics and freight use cases typically require low data rates but require location information with wide range and reliability.

[0077] refer to Figure 1 , the communication system 1 includes a wireless device, a base station (BS) and a network. Figure 1 A 5G network is illustrated as an example of the network of the communication system 1 , but the embodiments of the present disclosure are not limited to the 5G system and can be applied to future communication systems beyond the 5G system.

[0078] The BS and the network may be implemented as wireless devices, and a particular wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0079] A wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication / radio / 5G device. The wireless device may include, but is not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. A vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). An XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head mounted device (HMD), a head up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebook computers). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0080] In the present disclosure, the wireless devices 100a to 100f may be referred to as user equipment (UE). The user equipment (UE) may include, for example, a cellular phone, a smart phone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a tablet personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with an autonomous driving function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a device related to 5G services, or a device related to the field of the fourth industrial revolution. An unmanned aerial vehicle (UAV) may be, for example, an aircraft driven by a wireless control signal without a human on board. A VR device may include, for example, a device for realizing an object or background of a virtual world. An AR device may include, for example, a device realized by connecting an object or background of a virtual world to an object or background of a real world. MR devices may include devices that are implemented, for example, by fusing objects or backgrounds of a virtual world into objects or backgrounds of a real world. Holographic devices may include devices that record and reproduce stereoscopic information to achieve 360-degree stereoscopic images, for example, using interference phenomena of light generated when two lasers, called holography, meet. Public safety devices may include, for example, image relay devices or image devices that can be worn on the user's body. MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation, for example. For example, MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors. Medical devices may be devices for purposes of, for example, diagnosis, treatment, relief, cure, or prevention of disease. For example, medical devices may be devices for purposes of diagnosis, treatment, relief, or correction of injury or damage. For example, medical devices may be devices for purposes of inspection, replacement, or modification of structure or function. For example, medical devices may be devices for purposes of adjusting pregnancy. For example, medical devices may include devices for treatment, devices for operation, devices for (in vitro) diagnosis, hearing aids, or devices for procedures. Safety devices may be devices that are installed, for example, to prevent possible dangers and maintain safety. For example, a security device may be a camera, CCTV, recorder, or black box. A fintech device may be, for example, a device that is capable of providing financial services such as mobile payments. For example, a fintech device may include a payment device or a point of sale (POS) system. A weather / environmental device may include, for example, a device for monitoring or predicting weather / environment.

[0081] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a super 5G network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without going through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0082] Wireless communication / connection 150a and 150b can be established between wireless devices 100a to 100f / BS 200-BS 200. In this article, wireless communication / connection can be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication). The wireless device and the BS / wireless device can send / receive radio signals to each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b can send / receive signals through various physical channels. To this end, at least a part of various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0083] Figure 2 is a block diagram illustrating an example of a communication device capable of performing the method according to the present disclosure.

[0084] refer to Figure 2 , the first wireless device 100 and the second wireless device 200 can transmit / receive radio signals to / from external devices through various RATs (eg, LTE and NR). Figure 2 In the example, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 1 {wireless devices 100a to 100f and BS 200} and / or {wireless devices 100a to 100f and wireless devices 100a to 100f}.

[0085] The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally include 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 functions, processes and / or methods described in the present disclosure. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then send a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing part or all of the processing controlled by the processor 102 or for executing the processes and / or methods described in the present disclosure. In this article, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceivers 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present invention, a wireless device may represent a communication modem / circuit / chip.

[0086] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include 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 functions, processes and / or methods described in the present disclosure. For example, the processor 202 may process the information in the memory 204 to generate a third information / signal, and then send a radio signal including the third information / signal through the transceiver 206. The processor 202 may receive a radio signal including a fourth information / signal through the transceiver 106, and then store the information obtained by processing the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing part or all of the processing controlled by the processor 202 or for executing the processes and / or methods described in the present disclosure. In this document, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceivers 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0087] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by, but 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 PHY, MAC, RLC, PDCP, RRC, and SDAP). 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) according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure and provide the generated signals to one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive signals (eg, baseband signals) from the one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure.

[0088] 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. Firmware or software may be used to implement the functions, processes, proposals, and / or methods disclosed in the present disclosure, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to perform the functions, processes, proposals, and / or methods disclosed in the present disclosure may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 so as to be driven by one or more processors 102 and 202. Firmware or software in the form of code, commands, and / or command sets may be used to implement the functions, processes, proposals, and / or methods disclosed in the present disclosure.

[0089] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0090] One or more transceivers 106 and 206 may send user data, control information, and / or radio signals / channels mentioned in the method and / or operation flow chart of the present disclosure to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the function, process, proposal, method, and / or operation flow chart disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. 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 functional, process, proposal, method and / or operation flow chart disclosed in the present disclosure through one or more antennas 108 and 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals into baseband signals so as to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals into RF band signals. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the transceivers 106 and 206 can up-convert the OFDM baseband signal to a carrier frequency through their (analog) oscillators and / or filters and transmit the up-converted OFDM signal at the carrier frequency under the control of the processors 102 and 202. The transceivers 106 and 206 can receive the OFDM signal at the carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through their (analog) oscillators and / or filters under the control of the transceivers 102 and 202.

[0091] In an embodiment of the present disclosure, a UE may operate as a transmitting device in an uplink (UL) and as a receiving device in a downlink (DL). In an embodiment of the present disclosure, a BS may operate as a receiving device in an UL and as a transmitting device in a DL. In the following, for the convenience of description, it is mainly assumed that the first wireless device 100 is a UE and the second wireless device 200 is a BS, unless otherwise mentioned or described. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 may be configured to perform a UE behavior according to an embodiment of the present disclosure or control a transceiver 106 to perform a UE behavior according to an embodiment of the present disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 may be configured to perform a BS behavior according to an embodiment of the present disclosure or control a transceiver 206 to perform a BS behavior according to an embodiment of the present disclosure.

[0092] In the present disclosure, at least one memory (eg, 104 or 204 ) may store instructions or programs, which, when executed, enable at least one processor operably connected thereto to perform operations according to some embodiments or implementations of the present disclosure.

[0093] In the present disclosure, a computer-readable storage medium stores at least one instruction or a computer program, which, when executed by at least one processor, causes the at least one processor to perform operations according to some embodiments or implementations of the present disclosure.

[0094] In the present disclosure, a processing device or apparatus may include at least one processor and at least one computer memory, which may be connected to the at least one processor and store instructions that, when executed, cause the at least one processor to perform operations according to some embodiments or implementations of the present disclosure.

[0095] Figure 3 An example of a frame structure in a 3GPP-based wireless communication system is illustrated.

[0096] Figure 3The illustrated frame structure is purely exemplary, and the number of subframes, time slots, and / or symbols in the frame may be changed differently. In a 3GPP-based wireless communication system, OFDM parameter sets (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be configured differently between multiple cells aggregated for one UE. For example, if a cell UE is configured with different SCSs for aggregated cells, the (absolute time) duration of time resources (e.g., subframes, time slots, or TTIs) including the same number of symbols may be different among the aggregated cells. In this document, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

[0097] refer to Figure 3 , downlink and uplink transmissions are organized into frames. Each frame has T f = 10 ms duration. Each frame is divided into two half-frames, each half-frame has a duration of 5 ms. Each half-frame consists of 5 sub-frames, each sub-frame has a duration of T sf is 1 ms. Each subframe is divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on the cyclic prefix (CP). In normal CP, each slot includes 14 OFDM symbols, while in extended CP, each slot includes 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing △f = 2 u *15 kHz. The following table is based on the subcarrier spacing △f = 2 u * 15 kHz shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe for normal CP.

[0098] [Table 1]

[0099]

[0100] The following table is based on the subcarrier spacing The number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe for the extended CP are shown.

[0101] [Table 2]

[0102]

[0103] A slot includes a number of 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) indicated by higher layer signaling (e.g., radio resource control (RRC) signaling) is allocated to each carrier. Start, define subcarriers and OFDM symbol resource grid, where is the number of resource blocks in the resource grid and the subscript x is DL for the downlink and UL for the uplink. is the number of subcarriers per resource block. In 3GPP-based wireless communication systems, Typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL) there is one resource grid. The carrier bandwidth for subcarrier spacing configuration u is Given by higher layer parameters (e.g., RRC parameters). Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE) and one 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, a resource block is defined by 12 consecutive subcarriers in the frequency domain.

[0104] In 3GPP NR systems, resource blocks are categorized into CRBs and physical resource blocks (PRBs). For subcarrier spacing configuration u, CRBs are numbered from 0 and upwards in the frequency domain. The center of subcarrier 0 of CRB 0 of subcarrier spacing configuration u coincides with 'point A' used as a common reference point for the resource block grid. In 3GPP NR systems, PRBs are defined within bandwidth parts (BWPs) and are numbered from 0 to where i is the number of the bandwidth part. Physical resource block n in bandwidth part i PRB With common resource block n CRB The relationship between is as follows: PRB = n CRB + ,in It is a common resource block where the bandwidth part starts relative to CRB 0. A BWP includes multiple consecutive resource blocks. 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 to a UE can be activated at a time. The active BWP defines the operating bandwidth of the UE within the operating bandwidth of the cell.

[0105] NR frequency bands are defined as 2 types of frequency ranges, FR1 and FR2. FR2 can also be called millimeter wave (mmW). The frequency ranges in which NR can operate are described in Table 3.

[0106] [Table 3]

[0107]

[0108] Figure 4 An example of a protocol stack in a 3GPP-based wireless communication system is illustrated.

[0109] In particular, Figure 4 (a) illustrates an example of a radio interface user plane protocol stack between a UE and a base station (BS), and Figure 4 (b) illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used for calling by the UE and network management are transmitted. The user plane refers to a path through which data generated in an application layer, such as voice data or Internet packet data, is transmitted. Reference Figure 4 (a), the user plane protocol stack can be divided into the first layer (layer 1) (ie, the physical (PHY) layer) and the second layer (layer 2). Figure 4 (b), the control plane protocol stack can be divided into layer 1 (ie, PHY layer), layer 2, layer 3 (eg, radio resource control (RRC) layer), and non-access stratum (NAS) layer. Layer 1, layer 2, and layer 3 are referred to as access stratum (AS).

[0110] The NAS control protocol terminates at the Access Management Function (AMF) on the network side and performs functions such as authentication, mobility management, and security control.

[0111] In the 3GPP LTE system, Layer 2 is divided into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP). In the 3GPP New Radio (NR) system, 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) flows to the 5G core network.

[0112] In the 3GPP NR system, the main services and functions of SDAP include: mapping between QoS flows and data radio bearers; marking QoS flow ID (QFI) in DL packets and UL packets. A single SDAP protocol entity is configured for each separate PDU session.

[0113] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by the 5G core (5GC) or NG-RAN; establishment, maintenance and release of the RRC connection between the UE and the NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer; UE cell selection and reselection and control of cell selection and reselection; inter-RAT mobility); QoS management functions; UE measurement reporting and control of reporting; detection of and recovery from radio link failure; NAS message transfer from UE to NAS / from NAS to UE.

[0114] 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: ROHC only; transfer of user data; reordering and duplicate detection; in-sequence delivery; PDCP PDU routing (in the case of split bearers); retransmission of PDCP SDU; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status report for RLC AM; PDCP PDU duplication and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-sequence delivery; PDCP PDU duplication and duplicate discard indication to lower layers.

[0115] The RLC sublayer supports three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). RLC configuration is per logical channel and does not depend on 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 sequence numbering in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDUs (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0116] 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 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 through HARQ (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs with the help of dynamic scheduling; priority handling between logical channels of one UE with the help of logical channel prioritization; padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. The mapping restrictions in logical channel prioritization control which parameter sets, cells, and transmission timings a logical channel can use. Different kinds of data transfer services are provided by MAC. In order to accommodate different kinds of data transfer services, multiple types of logical channels are defined, that is, each supports the transfer of a specific type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. The control channel is used only for the transfer of control plane information, while the traffic channel is used only for the transfer of user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used to broadcast system control information, the Paging Control Channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications, and indications of ongoing 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 for UEs that do not have an RRC connection with the network, and the Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel that sends dedicated control information between the UE and the network and is used by UEs with an RRC connection. The Dedicated Traffic Channel (DTCH) is a point-to-point logical channel dedicated to one UE for the transfer of user information. The DTCH can exist in both the uplink and downlink. In the downlink, the following connections exist between logical channels and transport channels: BCCH can be mapped to BCH; BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to PCH; CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, the following connections exist between logical channels and transport channels: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0117] Figure 5 Figure 2 shows an example of data flow in a 3GPP NR system.

[0118] exist Figure 5 In , "RB" means radio bearer, and "H" means header. Radio bearers are classified into two groups: data radio bearers (DRBs) for user plane data and signaling radio bearers (SRBs) for control plane data. MAC PDU is transmitted / received to / from an external device through the PHY layer using radio resources. MAC PDU arrives at the PHY layer in the form of a transport block.

[0119] In the PHY layer, uplink transport channels UL-SCH and RACH are mapped to the physical uplink shared channel (PUSCH) and physical random access channel (PRACH), respectively, while downlink transport channels DL-SCH, BCH and PCH are mapped to the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH) and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, while downlink control information (DCI) is mapped to PDCCH. MAC PDU related to UL-SCH is sent by UE via PUSCH based on UL grant, while MAC PDU related to DL-SCH is sent by BS via PDSCH based on DL assignment.

[0120] In order to send the data unit of the present disclosure on the UL-SCH, the UE should have uplink resources available for the UE. In order to receive the data unit of the present disclosure on the DL-SCH, the UE should have downlink resources available for the UE. Resource allocation includes time domain resource allocation and frequency domain resource allocation. In the present disclosure, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. The uplink grant is either dynamically received by the UE on the PDCCH, in a random access response, or semi-persistently configured to the UE by the RRC. The downlink assignment is either dynamically received by the UE on the PDCCH, or semi-persistently configured to the UE by RRC signaling from the BS.

[0121] In the UL, the BS can dynamically allocate resources to the UE via the cell radio network temporary identifier (C-RNTI) on the PDCCH. The UE always monitors the PDCCH to find possible grants for uplink transmission when its downlink reception is enabled (an activity managed by discontinuous reception (DRX) when configured). In addition, with the configured grant, the BS can allocate uplink resources for initial HARQ transmission to the UE. Two types of configured uplink grants are defined: type 1 and type 2. For type 1, the RRC directly provides the configured uplink grant (including periodicity). For type 2, the RRC defines the period of the configured uplink grant, while the PDCCH addressed to the configured scheduling RNTI (CS-RNTI) can signal and activate the configured uplink grant, or deactivate it; that is, the PDCCH addressed to the CS-RNTI indicates that the uplink grant can be implicitly reused according to the period defined by the RRC until it is deactivated.

[0122] In DL, the BS can dynamically allocate resources to the UE via the C-RNTI on the PDCCH. When its downlink reception is enabled (active managed by DRX when configured), the UE always monitors the PDCCH to find possible assignments. In addition, through semi-persistent scheduling (SPS), the BS can allocate downlink resources for initial HARQ transmissions to the UE: RRC defines the periodicity of the configured downlink assignments, while the PDCCH addressed to the CS-RNTI can signal and activate the configured downlink assignment, or deactivate it. In other words, the PDCCH addressed to the CS-RNTI indicates that the downlink assignment can be implicitly reused according to the period defined by the RRC until it is deactivated.

[0123] <Resource Allocation via PDCCH (ie, Resource Allocation via DCI)>

[0124] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH, wherein the downlink control information (DCI) on the PDCCH includes: a downlink assignment including at least a modulation and coding format related to the DL-SCH (e.g., a modulation and coding scheme (MCS) index IMCS), resource allocation, and hybrid ARQ information; or an uplink scheduling grant including at least a modulation and coding format, resource allocation, and hybrid ARQ information related to the UL-SCH. The size and use of the DCI carried by one PDCCH vary depending on the DCI format. For example, in the 3GPP NR system, DCI format 0_0 or DCI format 0_1 ​​is used to schedule the PUSCH in one cell, and DCI format 1_0 or DCI format 1_1 is used to schedule the PDSCH in one cell.

[0125] Figure 6 An example of PDSCH time domain resource allocation through the PDCCH and an example of PUSCH time resource allocation through the PDCCH are illustrated.

[0126] Downlink control information (DCI) carried by the PDCCH for scheduling PDSCH or PUSCH includes the value m of the row index m+1 of the allocation table for PDSCH or PUSCH. The predefined default PDSCH time domain allocation A, B or C is applied as the allocation table for PDSCH, or the RRC-configured pdsch-TimeDomainAllocationList is applied as the allocation table for PDSCH. The predefined default PUSCH time domain allocation A is applied as the allocation table for PUSCH, or the RRC-configured pusch-TimeDomainAllocationList is applied as the allocation table for PUSCH. Which PDSCH time domain resource allocation configuration is applied and which PUSCH time domain resource allocation table is applied are determined according to fixed / predefined rules (e.g., Table 5.1.2.1.1-1 in 3GPP TS 38.214 v15.3.0, Table 6.1.2.1.1-1 in 3GPP TS 38.214 v15.3.0).

[0127] Each index row in the PDSCH time domain allocation configuration defines a slot offset K0, a start and length indicator SLIV, or directly defines a start symbol S and an allocation length L, and a PDSCH mapping type to be assumed in PDSCH reception. Each index row in the PUSCH time domain allocation configuration defines a slot offset K2, a start and length indicator SLIV, or directly defines a start symbol S and an allocation length L, and a PUSCH mapping type to be assumed in PUSCH reception. K0 for PDSCH or K2 for PUSCH is the timing difference between a slot with a PDCCH and a slot with a PDSCH or PUSCH corresponding to the PDCCH. SLIV is a joint indication of the start symbol S relative to the start of a slot with a PDSCH or PUSCH, and the number of consecutive symbols L counted from symbol S. For PDSCH / PUSCH mapping type, there are two mapping types: one is mapping type A, in which a demodulation reference signal (DMRS) is located in the 3rd or 4th symbol of a slot depending on RRC signaling, and the other is mapping type B, in which the DMRS is located in the first allocated symbol.

[0128] The scheduling DCI includes a frequency domain resource assignment field that provides assignment information about resource blocks for PDSCH or PUSCH. For example, the frequency domain resource assignment field can provide the UE with information about the cell used for PDSCH or PUSCH transmission, information about the bandwidth part used for PDSCH or PUSCH transmission, and information about resource blocks used for PDSCH or PUSCH transmission.

[0129] <Resource Allocation via RRC>

[0130] As mentioned above, in the uplink, there are two types of transmissions without dynamic grants: configured grant type 1, in which the uplink grant is provided by RRC and stored as a configured grant; and configured grant type 2, in which the uplink grant is provided by PDCCH and stored or cleared as a configured uplink grant based on L1 signaling indicating activation or deactivation of the configured uplink grant. Type 1 and type 2 are configured by RRC per service cell and per BWP. Multiple configurations can only be activated simultaneously on different service cells. For type 2, activation and deactivation are independent among service cells. For the same service cell, the MAC entity is configured with type 1 or type 2.

[0131] When grant type 1 is configured, at least the following parameters are provided to the UE via RRC signaling from the BS:

[0132] - cs-RNTI, which is the CS-RNTI used for retransmission;

[0133] - Periodicity, which provides the periodicity of the configured license type 1;

[0134] - timeDomainOffset, which represents the offset of the resource in the time domain relative to SFN=0;

[0135] - timeDomainAllocation value m, which provides the row index m+1 pointing to the allocation table, indicating the combination of the starting symbol S and the length L and PUSCH mapping type;

[0136] - frequencyDomainAllocation, which provides frequency domain resource allocation; and

[0137] - mcsAndTBS, which provides the IMCS indicating the modulation order, target code rate and transport block size. When a configured grant type 1 is configured by RRC for a serving cell, the UE stores the uplink grant provided by RRC as the configured uplink grant for the indicated serving cell and initializes or reinitializes the configured uplink grant starting in a symbol according to timeDomainOffset and S (derived from SLIV) and recurring periodically. After configuring an uplink grant for the configured grant type 1, the UE considers that the uplink grant recurrence is associated with each symbol: [(SFN *numberOfSlotsPerFrame * (numberOfSymbolsPerSlot) + (number of slots in a frame × numberOfSymbolsPerSlot) + number of symbols in a slot] = (timeDomainOffset *numberOfSymbolsPerSlot + S + N * periodicity) modulo (1024 * numberOfSlotsPerFrame *numberOfSymbolsPerSlot), for all N >= 0.

[0138] When grant type 2 is configured, the UE provides at least the following parameters via RRC signaling from the BS:

[0139] - cs-RNTI, which is the CS-RNTI used for activation, deactivation and retransmission; and

[0140] - Periodicity which provides the periodicity of the configured grant type 2. The actual uplink grant is provided to the UE by PDCCH (addressed to the CS-RNTI). After configuring an uplink grant for the configured grant type 2, the UE considers that the uplink grant recurrence is associated with each symbol: [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot) + (number of slots in a frame * numberOfSymbolsPerSlot) + number of symbols in a slot] = [(SFN 开始时间 *numberOfSlotsPerFrame * numberOfSymbolsPerSlot + timeslot 开始时间 *numberOfSymbolsPerSlot + symbol 开始时间 ) + N * periodicity] modulo (1024 × numberOfSlotsPerFrame * numberOfSymbolsPerSlot), for all N >= 0, where SFN 开始时间 , Time Slot开始时间 and symbol 开始时间 are the SFN, slot and symbol, respectively, of the first transmission opportunity of the PUSCH for which the configured uplink grant is (re)initialized. numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively.

[0141] For a configured uplink grant, the HARQ process ID associated with the first symbol of the UL transmission is derived from the following equation:

[0142] HARQ process ID = [floor (CURRENT_symbol / periodicity)] modulo fHARQ-Processes

[0143] Where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in frame × numberOfSymbolsPerSlot + number of symbols in a slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively, as specified in TS 38.211. CURRENT_symbol refers to the symbol index of the first transmission opportunity of the repeated bundling that occurs. If the configured uplink grant is activated and the associated HARQ process ID is less than nrofHARQ-Processes, then a HARQ process is configured for the configured uplink grant.

[0144] For the downlink, the UE can be configured with semi-persistent scheduling (SPS) per serving cell and per BWP via RRC signaling from the BS. Multiple configurations can only be activated simultaneously on different serving cells. Activation and deactivation of DL SPS are independent among serving cells. For DL ​​SPS, DL assignments are provided to the UE by PDCCH and are stored or cleared based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, the following parameters are provided to the UE via RRC signaling from the BS:

[0145] - cs-RNTI, which is the CS-RNTI used for activation, deactivation and retransmission;

[0146] - nrofHARQ-Processes: It provides the number of configured HARQ processes for SPS;

[0147] - Periodicity, which provides the periodicity of the configured downlink assignments for SPS.

[0148] When the SPS is released by the upper layer, all corresponding configurations must be released.

[0149] After configuring downlink assignments for SPS, the UE continues to consider that the Nth downlink assignment occurs in the following time slots: (numberOfSlotsPerFrame*SFN + number of time slots in the frame) = [(numberOfSlotsPerFrame *SFN 开始时间 +Time Slot 开始时间 )+N*periodicity*numberOfSlotsPerFrame / 10] modulo (1024*numberOfSlotsPerFrame), where SFN 开始时间 and time slot 开始时间 are, respectively, the SFN and timeslot of the first transmission of the PDSCH, in which the configured downlink assignments are (re)initialized.

[0150] For a configured downlink assignment, the HARQ process ID associated with the timeslot where the DL transmission starts is derived from the following equation:

[0151] HARQ process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame × periodicity))] modulo nrofHARQ-Processes

[0152] where CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of slots in frame] and numberOfSlotsPerFrame refers to the number of consecutive slots per frame, as specified in TS 38.211.

[0153] If the cyclic redundancy check (CRC) of the corresponding DCI format is scrambled by the CS-RNTI provided by the RRC parameter CS-RNTI, the UE verifies the DL SPS assignment PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or scheduling release and the new data indicator field for the enabled transport block is set to 0. If all fields for the DCI format are set according to Table 4 or Table 5, the verification of the DCI format is achieved. Table 4 shows special fields of UL grant type 2 and DL SPS for scheduling activation PDCCH verification, and Table 5 shows special fields of UL grant type 2 and DL SPS for scheduling release PDCCH verification.

[0154] [Table 4]

[0155]

[0156] [Table 5]

[0157]

[0158] The resource assignment fields (e.g., the time domain resource assignment field providing the time domain resource assignment value m, the frequency domain resource assignment field providing the frequency resource block allocation, the modulation and coding scheme field) in the DCI format carried by the UL grant type 2 and DL SPS of the scheduling activation PDCCH provide the actual DL assignment and the actual UL grant, as well as the corresponding modulation and coding scheme. If the verification is achieved, the UE regards the information in the DCI format as a valid activation or valid release of the DL SPS or the configured UL grant type 2.

[0159] For UL, the processor 102 of the present disclosure may send (or control the transceiver 106 to send) the data unit of the present disclosure based on the UL grant available to the UE. The processor 202 of the present disclosure may receive (or control the transceiver 206 to receive) the data unit of the present disclosure based on the UL grant available to the UE.

[0160] For DL, the processor 102 of the present disclosure may receive (or control the transceiver 106 to receive) DL data of the present disclosure based on the DL assignment available to the UE. The processor 202 of the present disclosure may send (or control the transceiver 206 to send) DL data of the present disclosure based on the DL assignment available to the UE.

[0161] The data units of the present disclosure undergo physical layer processing at the transmitting side before transmission via the radio interface, and the radio signals carrying the data units of the present disclosure undergo physical layer processing at the receiving side. For example, a MAC PDU including a PDCP PDU according to the present disclosure may undergo the following physical layer processing.

[0162] Figure 7 An example of physical layer processing at the transmission side is illustrated.

[0163] The following tables show the mapping of transport channels (TrCHs) and control information to their corresponding physical channels. Specifically, Table 6 specifies the mapping of uplink transport channels to their corresponding physical channels, Table 7 specifies the mapping of uplink control channel information to its corresponding physical channels, Table 8 specifies the mapping of downlink transport channels to their corresponding physical channels, and Table 9 specifies the mapping of downlink control channel information to its corresponding physical channels.

[0164] [Table 6]

[0165]

[0166] [Table 7]

[0167]

[0168] [Table 8]

[0169]

[0170] [Table 9]

[0171]

[0172] <code>

[0173] Data and control streams from / to the MAC layer are encoded to provide transport and control services over the radio transmission link of the PHY layer. For example, transport blocks from the MAC layer are encoded as codewords at the transmitting side. The channel coding scheme is a combination of error detection, error correction, rate matching, interleaving, and mapping / splitting of transport channels or control information to / from physical channels.

[0174] In the 3GPP NR system, the following channel coding schemes are used for different types of TrCHs and different types of control information.

[0175] [Table 10]

[0176]

[0177] [Table 11]

[0178]

[0179] For the transmission of a DL transport block (i.e., DL MAC PDU) or a UL transport block (i.e., UL MAC PDU), a transport block CRC sequence is attached to provide error detection for the receiving side. In the 3GPP NR system, the communication device uses a low-density parity check (LDPC) code when encoding / decoding UL-SCH and DL-SCH. The 3GPP NR system supports two LDPC basemaps (i.e., two LDPC base matrices): an LDPC basemap optimized for small transport blocks and an LDPC basemap optimized for small transport blocks. Figure 1 and LDPC basis for larger transport blocks Figure 2 The LDPC basis is selected based on the transport block size and the coding rate R. Figure 1or 2. The coding rate R is indicated by the modulation and coding scheme (MCS) index IMCS. The MCS index is dynamically provided to the UE via the PDCCH that schedules the PUSCH or PDSCH, is provided to the UE via the PDCCH that activates or (re)initializes the UL configured grant 2 or DL ​​SPS, or is provided to the UE via RRC signaling related to the UL configured grant type 1. If the CRC-attached transport block is larger than the maximum code block size of the selected LDPC base map, the CRC-attached transport block can be split into code blocks and an additional CRC sequence is attached to each code block. LDPC base Figure 1 and LDPC basis Figure 2 The maximum code block size is 8448 bits and 3480 bits, respectively. If the CRC-attached transport block is not larger than the maximum code block size of the selected LDPC base map, the attached CRC transport block is encoded using the selected LDPC base map. Each code block of the transport block is encoded using the selected LDPC base map. The LDPC coded blocks are then rate matched individually. Code block concatenation is performed to create codewords for transmission on PDSCH or PUSCH. For PDSCH, at most 2 codewords (i.e., at most 2 transport blocks) can be sent simultaneously on the PDSCH. PUSCH can be used to transmit UL-SCH data and layer 1 / 2 control information. Although Figure 8 Not shown, layer 1 / 2 control information may be multiplexed with the codewords used for UL-SCH data.

[0180] <Scrambling and Modulation>

[0181] The bits of the codeword are scrambled and modulated to generate a block of complex-valued modulation symbols

[0182] <Layer Mapping>

[0183] The complex-valued modulation symbols of the codeword are mapped to one or more multiple-input multiple-output (MIMO) layers. A codeword can be mapped to up to 4 layers. PDSCH can carry two codewords, and thus PDSCH can support up to 8 layers of transmission. PUSCH supports a single codeword, and thus PUSCH can support up to 4 layers of transmission.

[0184] <Transform Precoding>

[0185] The DL transmission waveform is conventional OFDM using a cyclic prefix (CP). For DL, no transform precoding (in other words, discrete Fourier transform (DFT)) is applied.

[0186] The UL transmission waveform is traditional OFDM with CP having transform precoding functionality that performs DFT spreading which can be deactivated or enabled. In the 3GPP NR system, for UL, transform precoding can be optionally applied if enabled. Transform precoding extends UL data in a special way to reduce the peak-to-average power ratio (PAPR) of the waveform. Transform precoding is a form of DFT. In other words, the 3GPP NR system supports two options for the UL waveform: one is CP-OFDM (the same as the DL waveform), and the other is DFT-s-OFDM. Whether the UE has to use CP-OFDM or DFT-s-OFDM is configured by the BS via RRC parameters.

[0187] <Subcarrier mapping>

[0188] These layers are mapped to antenna ports. In DL, for the mapping from layers to antenna ports, transparent mode (non-codebook-based) mapping is supported, and how beamforming or MIMO precoding is performed is transparent to the UE. In UL, for the mapping from layers to antenna ports, both non-codebook-based mapping and codebook-based mapping are supported.

[0189] For each antenna port (i.e., layer) used for transmitting a physical channel (e.g., PDSCH, PUSCH), complex-valued modulation symbols are mapped to subcarriers in the resource blocks allocated to the physical channel.

[0190] <OFDM modulation>

[0191] The communication device on the transmitting side generates a time-continuous OFDM baseband signal on antenna port p and a subcarrier spacing configuration u for OFDM symbol l in the TTI of the physical channel by adding a cyclic prefix (CP) and performing IFFT. For example, for each OFDM symbol, the communication device at the transmitting side can perform an inverse fast Fourier transform (IFFT) on the complex-valued modulation symbols mapped to the resource blocks in the corresponding OFDM symbol, and add CP to the signal after IFFT to generate the OFDM baseband signal.

[0192] <Upconversion>

[0193] The communication device at the transmitting side upconverts the OFDM baseband signal of antenna port p, subcarrier spacing configuration u, and OFDM symbol l to the carrier frequency f0 of the cell to which the physical channel is assigned.

[0194] Figure 2The processors 102 and 202 therein can be configured to perform encoding, scrambling, modulation, layer mapping, transform precoding (for UL), subcarrier mapping, and OFDM modulation. The processors 102 and 202 can control the transceivers 106 and 206 connected to the processors 102 and 202 to upconvert the OFDM baseband signal to a carrier frequency to generate a radio frequency (RF) signal. The RF signal is transmitted to an external device via antennas 108 and 208.

[0195] Figure 8 FIG. illustrates an example of physical layer processing at the receiving side.

[0196] The physical layer processing at the receiving side is essentially the inverse processing of the physical layer processing at the transmitting side.

[0197] <Frequency downconversion>

[0198] The communication device at the receiving side receives an RF signal via an antenna at a carrier frequency. The transceivers 106 and 206 that receive the RF signal at the carrier frequency downconvert the carrier frequency of the RF signal to baseband to facilitate obtaining an OFDM baseband signal.

[0199] <OFDM demodulation>

[0200] The communication device at the receiving side obtains complex-valued modulation symbols via CP separation and FFT. For example, for each OFDM symbol, the communication device at the receiving side removes the CP from the OFDM baseband signal and performs an FFT on the CP-removed OFDM baseband signal to obtain the complex-valued modulation symbols for antenna port p, subcarrier spacing u, and OFDM symbol l.

[0201] <Subcarrier demapping>

[0202] Subcarrier demapping is performed on the complex-valued modulation symbols to obtain the complex-valued modulation symbols of the corresponding physical channel. For example, the processor 102 can obtain the complex-valued modulation symbols mapped to the subcarriers belonging to the PDSCH from among the complex-valued modulation symbols received in the bandwidth part. As another example, the processor 202 can obtain the complex-valued modulation symbols mapped to the subcarriers belonging to the PUSCH from among the complex-valued modulation symbols received in the bandwidth part.

[0203] <Transform de-precoding>

[0204] If transform precoding has been enabled for the uplink physical channel, transform de-precoding (e.g., IDFT) is performed on the complex-valued modulation symbols of the uplink physical channel. For the uplink physical channels and downlink physical channels for which transform precoding has been deactivated, transform de-precoding is not performed.

[0205] <Layer demapping>

[0206] The complex-valued modulation symbols are demapped into one or two codewords.

[0207] <Demodulation and Descrambling>

[0208] The complex-valued modulation symbols of the codeword are demodulated and descrambled into the bits of the codeword.

[0209] <Decode>

[0210] The codewords are decoded into transport blocks. For UL-SCH and DL-SCH, the LDPC basis is selected based on the transport block size and the coding rate R. Figure 1 Or 2. A codeword may include one or more coded blocks. Each coded block is decoded into a CRC-attached code block or a CRC-attached transport block using the selected LDPC base graph. If code block segmentation is performed on a CRC-attached transport block at the transmitting side, the CRC sequence is removed from the CRC-attached code block to obtain a code block. The code blocks are concatenated into CRC-attached transport blocks. The transport block CRC sequence is removed from the CRC-attached transport block to obtain a transport block. The transport block is delivered to the MAC layer.

[0211] In the physical layer processing at the above-mentioned transmitting and receiving sides, the time domain and frequency domain resources (e.g., OFDM symbols, subcarriers, carrier frequencies) related to subcarrier mapping, OFDM modulation, and frequency up / down conversion can be determined based on resource allocation (e.g., UL grant, DL assignment).

[0212] For uplink data transmission, the processor 102 of the present disclosure may apply the above-mentioned physical layer processing of the transmitting side (or control the transceiver 106 to apply) to the data unit of the present disclosure to wirelessly transmit the data unit. For downlink data reception, the processor 102 of the present disclosure may apply the above-mentioned physical layer processing of the receiving side (or control the transceiver 106 to apply) to the received radio signal to obtain the data unit of the present disclosure.

[0213] For downlink data transmission, the processor 202 of the present disclosure may apply the above-mentioned physical layer processing of the transmitting side (or control the transceiver 206 to apply) to the data unit of the present disclosure to wirelessly transmit the data unit. For uplink data reception, the processor 202 of the present disclosure may apply the above-mentioned physical layer processing of the receiving side (or control the transceiver 206 to apply) to the received radio signal to obtain the data unit of the present disclosure.

[0214] <Random Access (RA) Procedure>

[0215] Hereinafter, a random access (RA) procedure of the NR system is described.

[0216] In the NR system, two types of random access procedures are supported: 4-step RA type with Msg1 and 2-step RA type with MsgA.

[0217] Fig. 9 and Fig.10 An example of a random access procedure supported by the NR system is shown. Fig. 9 As shown in , two types of RA procedures support contention-based random access (CBRA) and contention-free random access (CFRA).

[0218] The UE selects the type of random access at the initiation of the random access procedure based on the network configuration. More specifically, when CFRA resources are not configured, the RSRP threshold is used by the UE to select between the 2-step RA type and the 4-step RA type. When CFRA resources for the 4-step RA type are configured, the UE selects the 4-step RA type. In addition, when CFRA resources for the 2-step RA type are configured, the UE selects the 2-step RA type.

[0219] The network does not configure CFRA resources for both 4-step and 2-step RA types for a bandwidth part (BWP) and only supports CFRA with 2-step RA type for handover.

[0220] The 2-step RA type MsgA includes a preamble on PRACH and a payload on PUSCH. After MsgA transmission, the UE monitors the response from the network within the configured window.

[0221] For CFRA, upon receiving the network response, the UE ends the random access procedure, such as Fig. 9 As shown in (d). For CBRA, if the contention resolution is successful when receiving the network response, the UE ends the random access procedure, as shown in Fig. 9 As shown in (d).

[0222] However, if a fallback indication is received in MsgB, the UE performs Msg3 transmission and monitors contention resolution, such as Fig.10 If contention resolution is unsuccessful after Msg3 (re)transmission, the UE returns to MsgA transmission.

[0223] If the 2-step random access procedure is not completed after multiple MsgA transmissions, the UE can be configured to switch to the 4-step CBRA procedure.

[0224] In addition, 2-step RA is used to send small and infrequent data when the UE is in RRC_INACTIVE state.

[0225] In the two-step RA, after the UE sends data with an RA preamble (referred to as MsgA), the UE starts the RAR window (by using a timer called msgB-ResponseWindow) and monitors for a response from the network within the RAR window (which is referred to as MsgB, where MsgB includes successRAR or fallbackRAR or both).

[0226] If successRAR is received within the RAR window, the UE considers the data transmission in MsgA to be successful.

[0227] Otherwise, if fallbackRAR is received within the RAR window, the UE considers the transmission of the RA preamble in MsgA to be successful, but the data transmission in MsgA is not successful, and uses the UL grant included in fallbackRAR to retransmit the data.

[0228] Otherwise, if neither successRAR nor fallbackRAR is received within the RAR window, the UE reselects an RA preamble and retransmits the data together with the reselected RA preamble in MsgA.

[0229] <RedCap UE's BWP Operations for SI Requests>

[0230] In 3GPP NR Release 17, the network can support UEs with reduced operating capabilities compared to ordinary UEs to reduce the UE implementation complexity of wearable devices or sensor nodes. Hereinafter, the UE with reduced capabilities is referred to as a RedCap UE.

[0231] To support RedCap UEs, the network can configure a separate initial UL BWP for RedCap UEs (i.e., the UL BWP configured by initialUplinkBWP-RedCap), and can configure a separate initial DL BWP for RedCap UEs (i.e., the DL BWP configured by initialDownlinkBWP-RedCap).

[0232] When a separate initial UL / DL BWP is configured for a RedCap UE, a RedCap UE in the RRC_IDLE or RRC_INACTIVE state uses the separate initial UL / DL BWP when performing a random access procedure, instead of the legacy initial UL / DL BWP (i.e., the UL BWP configured by initialUplinkBWP or the DL BWP configured by initialDownlinkBWP).

[0233] Here, a separate initial UL BWP for RedCap UEs can be configured only in a normal UL (NUL) carrier. That is, in a supplementary UL (SUL) carrier, a separate initial UL BWP for RedCap UEs may not be configured even if a separate initial UL BWP for RedCap UEs is configured in a NUL carrier.

[0234] When a random access procedure is initiated in a RedCap UE, before the RedCap UE performs a BWP operation, the RedCap UE selects an uplink carrier between a normal UL (NUL) carrier and a supplementary UL (SUL) carrier. Unless the carrier is selected due to a PDCCH command, the SUL carrier is selected when a SUL carrier is configured and the downlink path loss reference is less than the RSRP threshold (i.e., rsrp-ThresholdSSB-SUL). In other cases, the NUL carrier is selected.

[0235] In addition, random access may be performed to request system information or locate system information (ie, SI request). For SI request, if random access resources for SI request (ie, contention-free random access resources) have been explicitly provided by RRC on the selected UL carrier and the selected UL BWP, the UE uses a dedicated PRACH occasion and PRACH preamble (ie, dedicated random access resources) to send a random access preamble for the corresponding SI request (ie, SI request based on Msg1).

[0236] That is, when a NUL carrier is selected and a separate initial UL BWP for RedCap UE is configured, the RedCap UE uses a dedicated random access resource for SI request configured in the separate initial UL BWP for RedCap UE (e.g., configured by si-RequestConfig-RedCap-r17 or posSI-RequestConfig-RedCap-r17). In addition, when a SUL carrier is selected by the RedCap UE, the selected supplementary uplink (i.e., SUL carrier) can also be used by the RedCap UE for SI request or positioning SI request.

[0237] On the other hand, when a separate initial UL BWP or a separate DL BWP is configured for a RedCap UE, the RedCap UE in the RRC_IDLE or RRC_INACTIVE state uses the separate initial UL BWP and the separate initial DL BWP. In other words, when the RedCap UE is in the RRC_INACTIVE or RRC_IDLE state, if a separate initial UL BWP for the RedCap UE is configured in the selected UL carrier, the RedCap UE uses the initial UL BWP for the RedCap UE for the random access procedure.

[0238] Similarly, when the RedCap UE is in RRC_INACTIVE or RRC_IDLE state, if a separate initial DL BWP for the RedCap UE is configured, after the RedCap UE sends a random access preamble (e.g., Msg1 or MsgA), the RedCap UE monitors the search space for random access response (e.g., Msg2 or MsgB) configured in the separate initial DL BWP for the RedCap UE.

[0239] However, if a separate initial DL BWP for RedCap UE is configured, when the RedCap UE initiates a Msg1-based SI request on the SUL carrier, the RedCap UE will monitor the search space for random access response configured in the separate initial DL BWP for RedCap UE. On the other hand, because the network does not distinguish whether the RedCap UE or the non-RedCap UE sends the random access preamble for the SI request, the network sends the random access response to the RedCap UE using the legacy initial DL BWP. In this case, because the RedCap UE monitors the separate initial DL BWP for the RedCap UE, which is different from the legacy initial DL BWP, the RedCap UE will not be able to receive the random access response for the SI request, which results in RACH failure.

[0240] For example, assume that the network configures a separate initial DL BWP for RedCap UEs, and further configures dedicated random access resources for SI requests in the SUL carrier. Specifically, SIB1 includes si-SchedulingInfo, which contains si-RequestConfigSUL. si-SchedulingInfo containing si-RequestConfigSUL refers to dedicated random access resources for SI requests in the SUL carrier.

[0241] If the RedCap UE is required to request an SI message, the RedCap UE initiates a random access procedure for the SI request.

[0242] More specifically, the RedCap UE performs UL carrier selection and selects the SUL carrier. The RedCap UE then performs a Msg1-based SI request (i.e., a contention-free random access procedure for SI request) using the dedicated random access resources for SI request configured in the SUL carrier. Because there is no separate initial UL BWP for the RedCap UE in the SUL carrier, the RedCap UE uses the legacy initial UL BWP configured in the SUL carrier.

[0243] Thereafter, the RedCap UE monitors the search space configured in the separate initial DL BWP for RedCap UE in order to receive a random access response.

[0244] Because the network receives the random access preamble configured for non-RedCap UE, the network sends a random access response using the legacy initial DLBWP. However, because the RedCap UE is monitoring a separate initial DLBWP for RedCap UE, which is different from the legacy initial DL BWP, the RedCap cannot receive the random access response.

[0245] Therefore, when the SUL carrier is used by RedCap UE for Msg1 based SI requests, additional BWP operations are required in order to avoid erroneous UE behavior leading to RACH failure.

[0246] In the present disclosure, if a RedCap UE in RRC_IDLE or RRC_INACTIVE sends a random access preamble for an SI request using dedicated random access resources (i.e., contention-free random access resources) configured in the SUL carrier, it is recommended that the RedCap UE should use the legacy initial DL BWP to receive the random access response message even if a separate initial DL BWP for the RedCap UE is configured.

[0247] That is, when performing Msg1 based SI request using the SUL carrier, the RedCap UE uses the legacy initial DL BWP for the random access procedure even if a separate initial DL BWP for the RedCap UE is configured.

[0248] The network may configure dedicated random access resources for SI requests (i.e., contention-free random access resources for SI requests). Dedicated random access resources for SI requests can be configured in SUL carriers (e.g., via si-RequestConfigSUL or posSI-RequestConfigSUL) and NUL carriers (e.g., via si-RequestConfig or posSI-RequestConfig). In addition, for RedCap UEs, the network may configure dedicated random access resources for SI requests, which can be used by RedCap UEs (e.g., via si-RequestConfig-RedCap-r17 or posSI-RequestConfig-RedCap-r17).

[0249] When a RedCap UE needs to request SI or locate SI (for example, a RedCap UE needs to receive system information whose si-BroadcastStatus is set to notBroadcasting), the RedCap UE may initiate a random access procedure in order to perform the SI request.

[0250] When a RedCap UE performs a random access procedure for an SI request, the RedCap UE performs UL carrier selection regardless of whether a separate initial UL BWP for the RedCap UE is configured, that is, if no UL carrier is indicated by lower layers (eg, by a PDCCH order).

[0251] If no SUL carrier is configured, the RedCap UE selects the NUL carrier. However, if a SUL carrier is configured, the UL carrier is selected based on the RSRP of the downlink path loss reference. If the RSRP of the downlink path loss reference is less than the configured RSRP threshold, the RedCap UE selects the SUL carrier. Whereas, if the RSRP of the downlink path loss reference is greater than or equal to the configured RSRP threshold, the RedCap UE selects the NUL carrier.

[0252] After the RedCap UE selects an UL carrier, the RedCap UE performs a BWP operation. When a random access procedure is initiated by an SI request, the RedCap UE in RRC_INACTIVE or RRC_IDLE selects a UL BWP for the random access procedure. Specifically, if a separate initial UL BWP for the RedCap UE is configured in the selected UL carrier, the RedCap UE uses the separate initial UL BWP for the RedCap UE to perform the random access procedure.

[0253] However, if a separate initial UL BWP for the RedCap UE is not configured in the selected UL carrier, the RedCap UE uses the legacy initial UL BWP for the RedCap UE to perform the random access procedure.

[0254] When initiating a Random Access procedure by means of an SI request, a RedCap UE in RRC_INACTIVE or RRC_IDLE selects the DL BWP for the Random Access procedure as follows:

[0255] 1) If a separate initial DL BWP for RedCap UE is configured, and if dedicated random access resources (ie, contention-free random access resources) for SI request are configured in the selected UL carrier and the selected UL BWP, the RedCap UE selects a DL BWP based on the selected UL carrier.

[0256] Specifically, if the selected UL carrier is a NUL carrier, the RedCap UE uses a separate initial DL BWP for RedCap UE to perform a random access procedure, whereas, if the selected UL carrier is a SUL carrier, the RedCap UE uses a legacy initial DL BWP for RedCap UE to perform a random access procedure.

[0257] 2) If a separate initial DL BWP for RedCap UE is configured and there is no dedicated random access resource for SI request, the RedCap UE uses the separate initial DL BWP for RedCap UE to perform a random access procedure.

[0258] 3) However, if a separate initial DL BWP for RedCap UE is not configured, the RedCap UE uses the legacy initial DL BWP for RedCap UE to perform the random access procedure.

[0259] After the RedCap UE selects the UL BWP and the DL BWP to perform the random access procedure, the RedCap UE selects a random access resource to send a random access preamble. When a dedicated random access resource for SI request is configured for the selected UL carrier and the selected UL BWP, the UE sends a contention-free random access preamble (i.e., SI request based on Msg1) using the configured random access resource. On the other hand, when there is no dedicated random access resource for SI request for the selected UL carrier and the selected UL BWP, the UE performs a contention-based random access procedure to send a random access preamble.

[0260] After the RedCap UE sends the Random Access Preamble, the RedCap UE monitors the search space configured in the selected DL BWP in order to receive a Random Access Response from the network. For an SI request based on Msg1, when a Random Access Response is successfully received in the selected DL BWP, the Random Access procedure is successfully completed and the RedCap UE monitors the search space for system information in order to receive the requested SI message as defined in the 3GPP NR standard.

[0261] In summary, regarding the execution of the random access procedure:

[0262] At the initiation of the random access procedure, after selecting the carrier for performing the random access procedure, if initialUplinkBWP-RedCap is configured, the MAC entity of the RedCap UE in RRC_IDLE or RRC_INACTIVE mode shall perform the random access procedure by using the BWP configured by initialUplinkBWP-RedCap.

[0263] Otherwise (i.e., if initialUplinkBWP-RedCap is not configured), the MAC entity of a RedCap UE in RRC_IDLE or RRC_INACTIVE mode shall perform the random access procedure by using the BWP configured by initialUplinkBWP.

[0264] Next, regarding monitoring the PDCCH associated with performing the random access procedure:

[0265] If the random access procedure is initiated for an SI request and random access resources for the SI request have been explicitly provided by RRC, and if the selected carrier is a SUL carrier, the MAC entity of a RedCap UE in RRC_IDLE or RRC_INACTIVE mode shall monitor the PDCCH on the BWP configured by initialDownlinkBWP.

[0266] Otherwise (i.e., if the random access procedure was not initiated for an SI request and random access resources for an SI request have not been explicitly provided by RRC, or the selected carrier is not a SUL carrier), the MAC entity of a RedCap UE in RRC_IDLE or RRC_INACTIVE mode shall determine whether initialDownlinkBWP-RedCap is configured.

[0267] If initialDownlinkBWP-RedCap is configured, the MAC entity of RedCap UE shall monitor PDCCH on the BWP configured by initialDownlinkBWP-RedCap. Otherwise (i.e., initialDownlinkBWP-RedCap is not configured), the MAC entity of RedCap UE shall monitor PDCCH on the BWP configured by initialDownlinkBWP.

[0268] Alternatively, with respect to monitoring the PDCCH associated with performing a random access procedure, the MAC entity of a RedCap UE in RRC_IDLE or RRC_INACTIVE mode shall determine whether initialDownlinkBWP-RedCap is configured.

[0269] If initialDownlinkBWP-RedCap is configured, and if the random access procedure is initiated for an SI request and random access resources for the SI request have been explicitly provided by RRC, and if the selected carrier is a SUL carrier, the MAC entity of the RedCap UE shall monitor the PDCCH on the BWP configured by initialDownlinkBWP.

[0270] If, otherwise (i.e., if initialDownlinkBWP-RedCap is configured, but if the random access procedure has not been initiated for the SI request and random access resources for the SI request have not been explicitly provided by RRC, or if the selected carrier is not a SUL carrier), the MAC entity of a RedCap UE in RRC_IDLE or RRC_INACTIVE mode shall monitor PDCCH on the BWP configured by initialDownlinkBWP-RedCap.

[0271] Otherwise, (i.e., if initialDownlinkBWP-RedCap is not configured), the MAC entity of the RedCap UE shall monitor PDCCH on the BWP configured by initialDownlinkBWP.

[0272] Fig.11 A flow chart illustrating an example of performing a Msg1-based SI request on a SUL by a RedCap UE according to the present disclosure.

[0273] refer to Fig.11 , in A05, when the RedCap UE needs to request system information or positioning system information from the network, the RedCap UE initiates a random access process for SI request.

[0274] Next, in A10, the RedCap UE performs UL carrier selection. Specifically, when the downlink path loss reference is lower than a threshold, the RedCap UE selects the SUL carrier.

[0275] Next, in A15, the RedCap UE selects a random access resource to facilitate sending a random access preamble. When the network configures a dedicated random access resource for SI request in the SUL carrier, the RedCap UE selects a dedicated random access resource to facilitate sending a random access preamble (ie, SI request based on Msg1).

[0276] In A20, the RedCap UE monitors the search space (eg, monitors PDCCH) in the legacy initial BWP even if a separate initial DL BWP for the RedCap UE is configured. Then, in A25, the Redcap UE receives a random access response on the legacy initial BWP based on the detected PDCCH.

[0277] Finally, in A30, the RedCap UE monitors the search space for system information in order to receive the requested system information or the requested positioning system information.

[0278] According to the present disclosure, even if the SUL carrier for Msg1-based SI request is used by the RedCap UE, the RedCap UE may correctly receive the random access response in the legacy DL BWP.

Claims

1. A method for performing operations for a user equipment (UE) in a wireless communication system, the method comprising: receiving information about a common initial downlink (DL) bandwidth part (BWP) and a UE type specific initial DL BWP; performing a random access procedure using random access resources on an initial uplink (UL) BWP of a supplementary uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type specific initial DL BWP, The PDCCH is monitored on the common initial DL BWP based on initiating the random access procedure for a system information (SI) request and providing random access resources for the SI request by a higher layer.

2. The method according to claim 1, wherein: Based on not initiating the random access procedure for the SI request or based on not providing the random access resources for the SI request by the higher layer, monitoring the PDCCH on the UE type specific initial DLBWP.

3. The method according to claim 1, wherein: The UE type specific initial DL BWP includes a reduced capability (RedCap) UE specific initial DL BWP.

4. The method according to claim 1, wherein: The initial UL BWP includes at least one of a common initial UL BWP and a reduced capability (RedCap) UE-specific initial UL BWP.

5. The method according to claim 1, wherein: Performing the random access procedure includes selecting the random access resource for sending a random access preamble, Wherein, based on the random access resource for the SI request provided by the higher layer, the random access resource for the SI request is selected as the random access resource for sending the random access preamble.

6. A user equipment (UE) in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations comprising: receiving information about a common initial downlink (DL) bandwidth part (BWP) and a UE type specific initial DL BWP; performing a random access procedure using random access resources on an initial uplink (UL) BWP of a supplementary uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type specific initial DL BWP, The PDCCH is monitored on the common initial downlink BWP based on initiating the random access procedure for a system information (SI) request and providing random access resources for the SI request by a higher layer.

7. The UE according to claim 6, wherein: Based on not initiating the random access procedure for the SI request or based on not providing the random access resources for the SI request by the higher layer, monitoring the PDCCH on the UE type specific initial DL BWP.

8. The UE according to claim 6, wherein: The UE type specific initial DL BWP includes a reduced capability (RedCap) UE specific initial DL BWP.

9. The UE according to claim 6, wherein: The initial UL BWP includes at least one of a common initial UL BWP and a reduced capability (RedCap) UE-specific initial UL BWP.

10. The UE according to claim 6, wherein: Performing the random access procedure includes selecting the random access resource for sending a random access preamble, Wherein, based on the random access resource for the SI request provided by the higher layer, the random access resource for the SI request is selected as the random access resource for sending the random access preamble.

11. An apparatus for a user equipment (UE), the apparatus comprising: at least one processor; as well as at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations comprising: receiving information about a common initial downlink (DL) bandwidth part (BWP) and a UE type specific initial DL BWP; performing a random access procedure using random access resources on an initial uplink (UL) BWP of a supplementary uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type specific initial DL BWP, The PDCCH is monitored on the common initial downlink BWP based on initiating the random access procedure for a system information (SI) request and providing random access resources for the SI request by a higher layer.

12. A computer-readable storage medium storing at least one computer program, the computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a user equipment (UE), the operations comprising: receiving information about a common initial downlink (DL) bandwidth part (BWP) and a UE type specific initial DL BWP; performing a random access procedure using random access resources on an initial uplink (UL) BWP of a supplementary uplink (SUL) carrier; and monitoring a physical downlink control channel (PDCCH) on the common initial DL BWP or the UE type specific initial DL BWP, The PDCCH is monitored on the common initial downlink BWP based on initiating the random access procedure for a system information (SI) request and providing random access resources for the SI request by a higher layer.

Images