METHOD FOR TRANSMITTING AND RECEIVING PUCCH IN A WIRELESS COMMUNICATION SYSTEM AND APPARATUS THEREFOR
The method for Redcap terminals to perform initial connection procedures without frequency hopping addresses bandwidth limitations, enhancing communication efficiency and reliability by disabling frequency hopping within the terminal's maximum bandwidth, thus supporting seamless operation in mixed terminal environments.
Patent Information
- Application Number
- JP2023504798
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-11-05
- Filing Date
- 2022-01-14
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2042-01-14
AI Technical Summary
Reduced capability (Redcap) terminals face challenges with initial UL BWP exceeding their bandwidth, leading to issues in performing connection procedures and transmitting/receiving Msg3 PUSCH and PUCCH without frequency hopping in wireless communication systems.
A method and apparatus for Redcap terminals to perform initial connection procedures without frequency hopping by disabling frequency hopping and setting the initial uplink bandwidth to be within the terminal's maximum bandwidth, allowing transmission of Msg3 PUSCH and PUCCH without frequency hopping.
This approach enables efficient resource utilization and minimizes network settings impact, facilitating low-delay and high-reliability communication for Redcap terminals in environments with general terminals, ensuring seamless operation and reduced network interference.
Smart Images

Figure 0007577188000038 
Figure 0007577188000039 
Figure 0007577188000040
Abstract
Description
[Technical field]
[0001] The present specification relates to wireless communication systems, and more particularly to a method and apparatus for transmitting and receiving a physical uplink control channel (PUCCH). [Background technology]
[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, the explosive increase in traffic has caused resource shortages and users are demanding faster services, so there is a demand for more advanced mobile communication systems.
[0003] The next generation mobile communication system has many requirements, including the ability to accommodate explosive data traffic, a dramatic increase in the transmission rate per user, a significantly increased number of connected devices, extremely low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.
[0004] Meanwhile, a reduced bandwidth is considered to be a main feature of a reduced capability (Redcap) terminal. In particular, for a Redcap terminal having such a feature, PUSCH / PUCCH frequency hopping in the initial UL BWP can exceed the reduced bandwidth of the terminal. Summary of the Invention [Problem to be solved by the invention]
[0005] This specification proposes a method and an apparatus for performing an optional access procedure (or an initial access procedure) in a situation where the initial UL BWP is larger than the bandwidth of the Redcap terminal.
[0006] This specification also proposes a method and an apparatus for a Redcap terminal to execute an optional connection procedure in a communication environment in which a Redcap terminal and a general terminal (for example, a terminal that is not a Redcap terminal) coexist.
[0007] Furthermore, this specification proposes a method and an apparatus for transmitting and receiving Msg3 PUSCH without frequency hopping when the initial UL BWP is larger than the bandwidth of a RedCap terminal.
[0008] Furthermore, this specification proposes a method and an apparatus for transmitting and receiving PUCCH (or HARQ-ACK information) for Msg4 without frequency hopping when the initial UL BWP is larger than the bandwidth of a RedCap terminal.
[0009] The technical problems to be achieved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present invention pertains from the following description. [Means for solving the problem]
[0010] This specification proposes a method for transmitting a physical uplink control channel (PUCCH) in a wireless communication system. The method, which is performed by a reduced capability (Redcap) terminal, includes the steps of transmitting an optional access preamble to a base station, receiving an optional access response from the base station based on the optional access preamble, and transmitting a message (Msg) 3 (physical uplink shared channel (PUSCH)) to the base station based on the optional access response. The method includes (comprising; configuring; establishing; setting; including; containing) a step of receiving Msg4 from the base station based on the Msg3 PUSCH, and transmitting a PUCCH for the Msg4 to the base station, where at least one of the Msg3 PUSCH and / or the PUCCH can be transmitted without frequency hopping based on the initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0011] Also, in the method herein, the initial uplink bandwidth may be a bandwidth of an initial uplink bandwidth part (BWP).
[0012] Also, in the method herein, the bandwidth of the Redcap terminal may be the maximum bandwidth supported by the Redcap terminal.
[0013] Further, in the method herein, the frequency hopping of the PUCCH may be set to "disable".
[0014] Further, in the method herein, the optional connection response may include a frequency hopping flag for the Msg3 PUSCH, and the frequency hopping flag may be set to '0'.
[0015] Further, in the method herein, the unsolicited connection response may be received based on a frequency readjustment based on the bandwidth of the Redcap terminal not including resources for the unsolicited connection response.
[0016] Also, in the method herein, the starting position of the unsolicited connection response window can be set by system information.
[0017] Further, in the method herein, the PUCCH may include hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the Msg4.
[0018] In addition, a reduced capability (Redcap) terminal configured to transmit a physical uplink control channel (PUCCH) in a wireless communication system of the present specification includes at least one transceiver, at least one processor, and at least one memory operatively connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, the operations including transmitting an optional connection preamble to a base station, receiving an optional connection response from the base station based on the optional connection preamble, transmitting a message (Msg) 3 physical uplink shared channel (PUSCH) to the base station based on the optional connection response, receiving Msg4 from the base station based on the Msg3 PUSCH, and transmitting a PUCCH for the Msg4 to the base station, At least one of the PUSCH and / or the PUCCH may be transmitted without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0019] Furthermore, this specification proposes a method for receiving a physical uplink control channel (PUCCH) in a wireless communication system, the method being performed by a base station, comprising the steps of receiving an optional connection preamble from a reduced capability (redcap) terminal, and sending an optional connection response to the redcap terminal based on the optional connection preamble; The method includes receiving a message (Msg) 3 (physical uplink shared channel, PUSCH) from the Redcap terminal based on the voluntary access response, transmitting Msg4 to the Redcap terminal based on the Msg3 PUSCH, and receiving a PUCCH for the Msg4 from the Redcap terminal, At least one of the Msg3 PUSCH and / or the PUCCH may be transmitted without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0020] Also, in the method herein, the initial uplink bandwidth may be a bandwidth of an initial uplink bandwidth part (BWP).
[0021] Also, in the method herein, the bandwidth of the Redcap terminal may be the maximum bandwidth supported by the Redcap terminal.
[0022] Further, in the method herein, frequency hopping of the PUCCH may be set to "disable."
[0023] Further, in the method herein, the optional connection response may include a frequency hopping flag for the Msg3 PUSCH, and the frequency hopping flag may be set to '0'.
[0024] Further, in the method herein, the voluntary connection response may be transmitted based on frequency retuning based on the bandwidth of the Redcap terminal not including resources for the voluntary connection response.
[0025] Also, in the method herein, the start of the unsolicited connection response window may be set by system information.
[0026] Further, in the method herein, the PUCCH may include hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the Msg4.
[0027] In addition, in the wireless communication system of the present specification, a base station configured to receive a physical uplink control channel (PUCCH) includes at least one transceiver, at least one processor, and at least one memory operatively connected to the at least one processor and storing instructions for performing operations based on which the at least one processor is executed, the operations including receiving an voluntary access preamble from a reduced capability (Redcap) terminal, transmitting an voluntary access response to the Redcap terminal based on the voluntary access preamble, receiving a message (Msg) 3 physical uplink shared channel (PUSCH) from the Redcap terminal based on the voluntary access response, transmitting Msg4 to the Redcap terminal based on the Msg3 PUSCH, and receiving a PUCCH for the Msg4 from the Redcap terminal, At least one of the Msg3PUSCH and / or the PUCCH can be received without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0028] Further, a processing apparatus configured to control a reduced capability (Redcap) terminal to transmit a physical uplink control channel (PUCCH) in a wireless communication system of the present specification includes at least one processor and at least one memory operatively connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, the operations including transmitting an voluntary connection preamble to a base station, receiving an voluntary connection response from the base station based on the voluntary connection preamble, transmitting a message (Msg) 3 physical uplink shared channel (PUSCH) to the base station based on the voluntary connection response, receiving Msg4 from the base station based on the Msg3 PUSCH, and transmitting a PUCCH for the Msg4 to the base station, wherein the Msg3 PUSCH is a PUSCH for the PUSCH. At least one of the PUSCH and / or PUCCH may be transmitted without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0029] Further, in a computer-readable storage medium storing at least one instruction for causing the at least one processor to control operations based on being executed by the at least one processor of the present specification, the operations include the steps of transmitting an optional connection preamble to a base station, receiving an optional connection response from the base station based on the optional connection preamble, transmitting a message (Msg) 3 physical uplink shared channel (PUSCH) to the base station based on the optional connection response, receiving an Msg4 from the base station based on the Msg3 PUSCH, and transmitting a physical uplink control channel (physical, PUCCH) for the Msg4 to the base station, wherein at least one of the Msg3 PUSCH and / or the PUCCH may be transmitted without frequency hopping based on an initial uplink bandwidth being greater than the bandwidth of a reduced capability (Redcap) terminal. Effect of the Invention
[0030] According to the present specification, in a situation where the initial UL BWP is larger than the bandwidth of the RedCap terminal, it is possible to minimize the impact of NR network (or base station) settings and perform an optional access procedure (or initial access procedure).
[0031] Furthermore, according to the present specification, in a communication environment in which Redcap terminals and general terminals coexist, it is possible to improve resource efficiency and realize a low-latency, highly reliable communication system.
[0032] In addition, according to the present specification, when the initial UL BWP is larger than the bandwidth of the RedCap terminal, the Msg3 PUSCH is transmitted and received without frequency hopping, thereby making it possible to effectively perform an optional access procedure without delay.
[0033] In addition, according to the present specification, when the initial UL BWP is larger than the bandwidth of the RedCap terminal, the PUCCH (or HARQ-ACK information) for Msg4 is transmitted and received without frequency hopping, thereby making it possible to effectively perform an optional access procedure without delay.
[0034] The effects obtained by the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief description of the drawings]
[0035] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present invention, provide embodiments of the present invention and, together with the detailed description, explain the technical features of the present invention. [Figure 1] An example of the overall system structure of NR to which the method proposed in this specification can be applied is shown. [Diagram 2] 2 illustrates the relationship between uplink and downlink frames in a wireless communication system in which the method proposed herein can be applied; [Diagram 3] 1 shows an example of a frame structure in an NR system. [Figure 4] 1 shows an example of a resource grid supported by a wireless communication system in which the methods proposed herein can be applied. [Diagram 5] 1 shows the slot structure of an NR frame to which the method proposed in this specification can be applied. [Figure 6] 1 shows an example of an antenna port and neurology specific resource grid to which the method proposed in this specification can be applied. [Figure 7] 1 shows physical channels and general signal transmission used in the 3GPP (registered trademark: the same applies below) system. [Figure 8] The SSB structure is illustrated. [Figure 9] Illustrates SSB transmission. [Figure 10] An example of an arbitrary connection process is shown below. [Figure 11] FIG. 1 is a diagram for explaining a two-step RACH procedure. [Figure 12] 13 shows a flowchart of a procedure for reporting device type information to a base station. [Figure 13] This shows how the base station schedules the Msg3 PUSCH in the Redcap UE bandwidth without FH when the initial UL bandwidth is larger than the Redcap UE bandwidth. [Figure 14] Method 2-2 is shown for case 1, where the initial UL bandwidth is larger than the Redcap UE bandwidth. [Figure 15] Method 2-2 is shown for Case 2, where the initial UL bandwidth is larger than the Redcap UE bandwidth. [Figure 16] An example of Method 2-2 for Case 3 where the initial UL bandwidth is larger than the Redcap UE bandwidth is shown. [Figure 17] This is an example of applying modulo operation to case 1. [Figure 18] This is an example in which mirroring is applied to case 1. [Figure 19] 1 is a flowchart for explaining a method of operating a terminal proposed in this specification. [Figure 20] 1 is a flowchart for explaining a method of operating a base station proposed in this specification. [Figure 21] 1 shows a communication system 1 to which the present specification is applied. [Figure 22] 1 illustrates a wireless device to which the present invention can be applied. [Figure 23] 1 shows another example of a wireless device to which the present specification is applied. [Figure 24] 1 illustrates a mobile device to which the present specification is applied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0036] Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. The detailed description disclosed below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of the present invention, and is not intended to show the only embodiments in which the present invention can be practiced. The following detailed description includes specific details to provide a complete understanding of the present invention. However, those skilled in the art will appreciate that the present invention can be practiced without such specific details.
[0037] In some cases, well-known structures and devices are omitted or illustrated in block diagram form, focusing on the core functions of each structure and device, in order to avoid obscuring the concept of the present invention.
[0038] Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next GeneRATion NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, robot, AI module, Unmanned Aerial Vehicle (UAV), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.
[0039] The following technologies may be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented in a wireless technology such as GSM (Global System for Mobile communications / GPRS (General Packet Radio Service / EDGE (Enhanced Data RATes for GSM Evolution)). OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd GeneraTion Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.
[0040] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onwards. In detail, LTE technology from 3GPP TS 36.xxx Release 10 onwards is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onwards. LTE / NR may be referred to as a 3GPP system. "xxx" refers to the detailed number of a standard document. LTE / NR may be commonly referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, reference may be made to matters described in standard documents published before the present invention. For example, the following documents may be referenced.
[0041] 3GPP LTE
[0042] -36.211:Physical channels and modulation
[0043] -36.212:Multiplexing and channel coding
[0044] -36.213:Physical layer procedures
[0045] -36.300:Overall description
[0046] -36.331:Radio Resource Control(RRC)
[0047] 3GPP NR
[0048] -38.211:Physical channels and modulation
[0049] -38.212:Multiplexing and channel coding
[0050] -38.213:Physical layer procedures for control
[0051] -38.214:Physical layer procedures for data
[0052] -38.300:NR and NG-RAN Overall Description
[0053] -36.331:Radio Resource Control (RRC) protocol specification
[0054] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to conventional radio access technology is emerging. In addition, massive MTC (Machine Type Communications), which connects a large number of devices and things to provide various services anytime and anywhere, is also one of the important issues to be considered in next-generation communication. In addition, the design of communication systems that take into account reliability and latency-sensitive services / terminals is being discussed. Thus, the introduction of next-generation radio access technology that takes into account eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (ULtra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience, this technology is referred to as NR in this specification. NR is an expression that shows an example of 5G wireless access technology (radio access technology, RAT).
[0055] The three main requirement areas for 5G include (1) the Enhanced Mobile Broadband (eMBB) area, (2) the massive Machine Type Communication (mMTC) area, and (3) the Ultra-reliable and Low Latency Communications (URLLC) area.
[0056] Some use cases may require multiple areas for optimization, while others may only be focused on one Key Performance Indicator (KPI). 5G will support such diverse use cases in a flexible and reliable way.
[0057] eMBB goes far beyond basic mobile Internet access and covers rich interactive work, media and entertainment applications in the cloud or augmented reality. Data is one of the core drivers of 5G, and it is possible that we will not see dedicated voice services for the first time in the 5G era. In 5G, voice is expected to be handled simply as an application using the data connection provided by the communication system. The main causes for the increased traffic volume are the increase in content size and the increase in the number of applications that require high data transmission rates. Streaming services (audio and video), interactive video and mobile Internet connections are more widely used as more devices are connected to the Internet. Many such applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly increasing on mobile communication platforms, which can be applied to both work and entertainment, and cloud storage is a particular use case that is driving the growth of uplink data transmission rates. 5G will also be used for remote work in the cloud, which requires much lower end-to-end latency to maintain an excellent user experience when haptic interfaces are used. Entertainment, e.g., cloud gaming and video streaming, is another key factor that increases the demand for mobile broadband capabilities. Entertainment is essential on smartphones and tablets everywhere, including in high mobility environments such as trains, cars, and airplanes. Another use case is augmented reality and information retrieval for entertainment, where augmented reality requires very low latency and instantaneous data volume.
[0058] Also, one of the most anticipated use cases for 5G is its ability to seamlessly connect embedded sensors in all sectors, i.e. mMTC. It is predicted that the number of potential IoT devices will reach 20.4 billion by 2020. Industrial IoT is one area where 5G will play a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.
[0059] URLLC includes new services transforming industries through ultra-reliable / available low-latency links such as remote control of critical infrastructure and self-driving vehicles. Reliability and latency levels are essential for smart grid control, industrial automation, robotics, drone control and coordination.
[0060] A number of use cases will be described in more detail below.
[0061] 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated at hundreds of megabits per second to gigabits per second. Such high speeds are required to deliver TV at resolutions of 4K and above (6K, 8K and beyond), as well as virtual and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include most immersive sports. Certain application programs may require special network configurations. For example, in the case of VR games, gaming companies may have to integrate their core servers with the network operator's edge network servers to minimize latency.
[0062] Automotive is expected to be an important new driver in 5G with many use cases for mobile communications to vehicles. For example, entertainment for passengers will require simultaneous high capacity and high mobility mobile broadband, because future users will expect continuous high quality connectivity regardless of their location and speed. Another use case in the automotive field is the augmented reality dashboard, which displays information overlaid on top of what the driver sees through the front window, identifying objects in the dark and informing the driver about the object's distance and movement. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and between cars and other connected devices (e.g. devices carried by pedestrians). Safety systems will be able to guide drivers on alternative courses of action to drive more safely and reduce the risk of accidents. The next step will be remotely piloted or self-driven vehicles, which will require very reliable and very fast communication between different autonomous vehicles and between cars and infrastructure. In the future, autonomous vehicles will perform all driving activities, leaving the driver to focus only on traffic anomalies that the vehicle itself cannot identify. The technical requirements for autonomous vehicles demand ultra-low latency and ultra-high speed reliability to increase traffic safety to a level unattainable by humans.
[0063] Smart cities and smart homes, also referred to as smart society, are embedded with high density wireless sensor networks. A distributed network of intelligent sensors identifies requirements for cost and energy efficient maintenance of the city or home. A similar setup can be made for each home. Temperature sensors, window and heating controllers, burglar alarms and home appliances are all wirelessly connected. Many of these sensors typically have low data transmission rates, low power consumption and low cost. However, for example, real-time HD video may be required by certain types of devices for surveillance.
[0064] The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of distributed sensor networks. A smart grid interconnects such sensors using digital information and communication technologies to collect and act upon information. This information can include supplier and consumer actions, allowing the smart grid to improve the efficiency, reliability, economy, sustainability of production, and distribution of fuels, such as electricity, in an automated manner. A smart grid can also be viewed as another sensor network with low latency.
[0065] The health sector has many applications that can benefit from mobile communications. Communication systems can support telemedicine to provide clinical care over long distances. This helps to reduce the barriers of distance and can improve access to medical services that are not sustainably available in remote rural areas. It can also be used to save lives in critical care and emergency situations. Mobile-based wireless sensor networks can provide remote monitoring and sensing for parameters such as heart rate and blood pressure.
[0066] Wireless and mobile communications are becoming more and more important in industrial applications. Wiring is expensive to install and maintain. The possibility to replace cables with reconfigurable wireless links is therefore an attractive opportunity in many industrial sectors. However, achieving this requires that wireless connections operate with similar latency, reliability and capacity as cables, and that their management is simplified. Low latency and very low error probability are new requirements that need to be addressed with 5G.
[0067] Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable tracking of inventory and packages anywhere. Logistics and freight tracking use cases typically require low data rates, but require wide range and reliable location information.
[0068] In addition, use cases for areas spanning mMTC and eMBB, or mMTC and URLLC, are considered important.
[0069] New RAT systems including NR use OFDM transmission scheme or a similar transmission scheme. New RAT systems may follow OFDM parameters different from those of LTE. Or, new RAT systems may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Or, one cell may support multiple numerologies. That is, terminals operating with different numerologies can coexist in one cell.
[0070] A numerology corresponds to one subcarrier spacing in the frequency domain. By scaling the reference subcarrier spacing to an integer N, different numerologies can be defined.
[0071] Definition of Terms
[0072] eLTE eNB: eLTE eNB is an evolution of eNB that supports connectivity to EPC and NGC.
[0073] gNB: A node that supports NR as well as linking with NGC.
[0074] New RAN: A radio access network that supports NR or E-UTRA or interworks with NGC.
[0075] Network slice: A network slice is a network defined by opeRATor to provide an optimized solution for a specific market scenario calling for specific requirements with end-to-end reach.
[0076] network function: A network function is a logical node within a network infrastructure with a well-defined external interface and a well-defined functional behavior.
[0077] NG-C: A control plane interface used as the NG2 reference point between the new RAN and NGC.
[0078] NG-U: User plane interface used as NG3 reference point between new RAN and NGC.
[0079] Non-standalone NR: A deployment configuration in which a gNB requests an LTE eNB to an EPC as an anchor for control plane connection, or requests an eLTE eNB to an NGC as an anchor for control plane connection.
[0080] Non-independent E-UTRA: A deployment configuration in which an eLTE eNB requests a gNB from the NGC as an anchor for control plane connectivity.
[0081] User Plane Gateway: The termination point of the NG-U interface.
[0082] System in general
[0083] FIG. 1 shows an example of the overall system architecture of NR to which the method proposed in this specification can be applied.
[0084] Referring to FIG. 1, the NG-RAN consists of the NG-RA user plane (new AS sublayer / PDCP / RLC / MAC / PHY) and gNBs that provide control plane (RRC) protocol termination for the UE (User Equipment).
[0085] The gNBs are interconnected through an Xn interface.
[0086] In addition, the gNB is connected to the NGC via an NG interface.
[0087] More specifically, the gNB is connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.
[0088] NR (New RAT) Numerology and Frame Structure
[0089] In the NR system, multiple numerologies can be supported. Here, the numerology can be defined by the subcarrier spacing and CP (Cyclic Prefix) overhead. In this case, the spacing between multiple subcarriers can be derived by scaling the spacing between the basic subcarriers to an integer N (or μ). In addition, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band.
[0090] In addition, NR systems can support a variety of frame structures according to multiple numerologies.
[0091] The following describes the Orthogonal Frequency Division Multiplexing (OFDM) numerology and frame structure that can be considered in an NR system.
[0092] The multiple OFDM numerologies supported in the NR system can be defined as shown in Table 1.
[0093] [Table 1]
[0094] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services, such as 15kHz SCS to support wide areas in traditional cellular bands, 30kHz / 60kHz SCS to support dense-urban, lower latency and wider carrier bandwidth, and 60kHz or higher SCS to support bandwidths larger than 24.25GHz to overcome phase noise.
[0095] The NR frequency band is defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in Table 2 below. FR2 can also refer to millimeter wave (mmW).
[0096] [Table 2]
[0097] [Table 3]
[0098] FIG. 2 shows the relationship between uplink and downlink frames in a wireless communication system in which the method proposed herein can be applied.
[0099] [Table 4]
[0100] [Table 5]
[0101] Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or an uplink slot can be used.
[0102] [Table 6]
[0103] [Table 7]
[0104] [Table 8]
[0105] An example of a frame structure in an NR system is shown in Figure 3. Figure 8 is for convenience of explanation only and does not limit the scope of this specification.
[0106] [Table 9]
[0107] A mini-slot can also consist of 2, 4 or 7 symbols, and may consist of more or less symbols.
[0108] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered.
[0109] Hereinafter, the physical resources that can be considered in an NR system will be described in detail.
[0110] First, with respect to antenna ports, the antenna ports are defined such that the channel on which the symbols on the antenna port are carried can be inferred from the channel on which the other symbols on the same antenna port are carried. If the large-scale properties of the channel on which the symbols on one antenna port are carried can be inferred from the channel on which the symbols on the other antenna port are carried, the two antenna ports can be said to be in a quasi co-located (QC / QCL) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.
[0111] FIG. 4 illustrates an example of a resource grid that may be supported in a wireless communication system in accordance with some embodiments herein.
[0112] [Table 10]
[0113] FIG. 5 shows the slot structure of an NR frame to which the method proposed herein can be applied.
[0114] A slot includes multiple symbols in the time domain. For example, in the case of normal CP, one slot includes seven symbols, and in the case of extended CP, one slot includes six symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple (P) consecutive RBs in the frequency domain and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication is performed via the activated BWPs, and only one BWP can be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol can be mapped to it.
[0115] FIG. 6 shows an example of a resource grid by antenna port and numerology to which the method proposed in this specification can be applied.
[0116] [Table 11]
[0117] Point A serves as a common reference point for the resource block grid and can be obtained as follows:
[0118] - offsetToPointA for the PCell downlink represents the frequency offset between Point A and the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block used by the UE for initial cell selection, and is expressed in resource block units assuming a subcarrier spacing of 15 kHz for FR1 and a subcarrier spacing of 60 kHz for FR2;
[0119] -absoluteFrequencyPointA represents the frequency-location of Point A expressed as ARFCN (absolute radio-frequency channel number).
[0120] Common resource blocks are numbered from 0 upwards in the frequency domain for subcarrier spacing.
[0121] [Table 12]
[0122]
number
[0123] [Table 13]
[0124]
number
[0125] Bandwidth part (BWP)
[0126] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the RF for the entire CC turned on, the terminal battery may be consumed significantly. Alternatively, when considering multiple use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) operating in one wideband CC, different numerologies (e.g., sub-carrier spacing) may be supported for each frequency band in the CC. Alternatively, the capacity for the maximum bandwidth may differ for each terminal. In consideration of this, the base station can instruct the terminal to operate only in a portion of the bandwidth that is not the entire bandwidth of the wideband CC, and the portion of the bandwidth is defined as a bandwidth portion (BWP) for convenience. The BWP can be composed of resource blocks (RBs) that are continuous on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration).
[0127] Meanwhile, the base station can set multiple BWPs even within one CC set in the terminal. For example, a BWP occupying a relatively small frequency region can be set in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated in a specific BWP, some UEs can be set to other BWPs for load balancing. Alternatively, taking into account frequency domain inter-cell interference cancellation between adjacent cells, some spectrums in the entire bandwidth can be excluded, and both BWPs can be set in the same slot. That is, the base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC, can activate at least one DL / UL BWP among the configured DL / UL BWP(S) at a particular time (by L1 signaling or MAC CE or RRC signaling, etc.), can instruct switching to other configured DL / UL BWPs (by L1 signaling or MAC CE or RRC signaling, etc.), or can switch to a predetermined DL / UL BWP when a timer value expires based on a timer. In this case, although it is defined as an activated DL / UL BWP, in a situation where the terminal is in an initial access process or before an RRC connection is set up, it may not be able to receive a configuration for the DL / UL BWP. In such a situation, the DL / UL BWP assumed by the terminal is defined as an initial active DL / UL BWP.
[0128] Physical Channels and General Signaling
[0129] Figure 7 illustrates physical channels and general signal transmission used in a 3GPP system. In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and transmits information to the base station via an uplink (UL standard). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / application of the information exchanged.
[0130] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S701). To this end, the terminal can receive a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and acquire information such as a cell ID. Then, the terminal can receive a Physical Broadcast Channel (PBCH) from the base station to acquire broadcast information within the cell. Meanwhile, the terminal can receive a Downlink Reference Signal (DL RS) in the initial cell search stage to check the state of the downlink channel.
[0131] After completing the initial cell search, the terminal can acquire more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information carried on the PDCCH (S702).
[0132] Meanwhile, when the terminal first connects to the base station or there are no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) to the base station (S703 to S706). To this end, the terminal can transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S703 and S705) and receive a response message (RAR Random Access Response) to the preamble through a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, the terminal can further perform a contention resolution procedure (S706).
[0133] After performing the above-mentioned procedures, the terminal may then perform PDCCH / PDSCH reception (S707) and Physical Uplink Shared Channel (PUSCH / Physical Uplink Control Channel (PUCCH) transmission (S708) as a general uplink / downlink signal transmission procedure. In particular, the terminal may receive downlink control information (DCI) via the PDCCH. Here, the DCI includes control information such as resource allocation information of the terminal, and may be applied in different formats depending on the purpose of use.
[0134] Meanwhile, the control information that the terminal transmits to the base station through the uplink or that the terminal receives from the base station may include a downlink / uplink ACK / NACK signal, a CQI (Channel Quality Indicator), a PMI (Precoding Matrix, Index), an RI (Rank Indicator), etc. The terminal may transmit the above-mentioned control information such as CQI / PMI / RI through the PUSCH and / or PUCCH.
[0135] Initial Access (IA) and Random Access (RA) Processes
[0136] SSB (Synchronization Signal Block) transmission and related operations
[0137] Figure 8 illustrates an SSB structure. Based on the SSB, the UE can perform cell search, system information acquisition, beam alignment for initial connection, DL measurement, etc. The SSB is mixed with the SS / PBCH (Synchronization Signal / Physical Broadcast channel) block.
[0138] Referring to FIG. 8, an SSB is composed of a PSS, an SSS, and a PBCH. An SSB is composed of four consecutive OFDM symbols, and a PSS, a PBCH, an SSS / PBCH, or a PBCH is transmitted for each OFDM symbol. Each of the PSS and the SSS is composed of one OFDM symbol and 127 subcarriers, and the PBCH is composed of three OFDM symbols and 576 subcarriers. The PBCH is encoded / decoded based on a polar code and modulated / demodulated according to Quadrature Phase Shift Keying (QPSK). The PBCH in the OFDM symbol is composed of data resource elements (REs) to which complex modulation values of the PBCH are mapped, and DMRS REs to which a demodulation reference signal (DMRS) for the PBCH is mapped. There are three DMRS REs for each resource block of an OFDM symbol, and three data REs exist between the DMRS REs.
[0139] Cell search
[0140] Cell search refers to a process in which a UE acquires time / frequency synchronization of a cell and detects a cell identifier (ID) (e.g., a physical layer Cell ID, PCI) of the cell. The PSS is used to detect a cell ID in a cell ID group, and the SSS is used to detect a cell ID group. The PBCH is used for SSB (time) index detection and half-frame detection.
[0141] The UE cell search process can be summarized as shown in Table 5 below.
[0142] [Table 14-1] [Table 14-2] [Table 14-3]
[0143] There are 336 cell ID groups, and there are 3 cell IDs for each cell ID group. There are 1008 cell IDs in total. Information about the cell ID group to which the cell ID of a cell belongs is provided / obtained via the SSS of the cell, and information about the cell ID of one of the 336 cells in the cell ID is provided / obtained via the PSS. Figure 9 illustrates an example of SSB transmission.
[0144] SSB is transmitted periodically according to the SSB periodicity. The SSB basic period assumed by the UE during initial cell search is defined as 20 ms. After cell connection, the SSB periodicity can be set by the network (e.g., BS) to one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms}. An SSB burst set is configured at the beginning of the SSB period. The SSB burst set consists of a 5 ms time window (i.e., half frame), and the SSB can be transmitted up to L times within the SS burst set. The maximum number of SSB transmissions L is given by the following depending on the carrier frequency band: One slot contains up to two SSBs.
[0145] - For frequency range up to 3 GHz, L = 4
[0146] - For frequency range from 3GHz to 6 GHz, L = 8
[0147] - For frequency range from 6 GHz to 52.6 GHz, L = 64
[0148] The time positions of the SSB candidates within the SS burst set can be defined according to the spacing of the subcarriers. The time positions of the SSB candidates are indexed (SSB index) from 0 to L-1 according to the time order within the SSB burst set (i.e., half frame).
[0149] Multiple SSBs can be transmitted within the frequency span of a carrier. The physical layer cell identifiers of such SSBs are not unique, and other SSBs may have different physical layer cell identifiers.
[0150] The UE can obtain DL synchronization by detecting the SSB. The UE can identify the structure of the SSB burst set based on the detected SSB (time) index, and can thereby detect the symbol / slot / half-frame boundary. The frame / half-frame number to which the detected SSB belongs can be identified using the system frame number (SFN) information and the half-frame indication information.
[0151] Specifically, the UE can obtain a 10-bit SFN for the frame to which the PBCH belongs from the PBCH. Next, the UE can obtain 1-bit half-frame indication information. For example, if the UE detects a PBCH with a half-frame indication bit set to 0, it can determine that the SSB to which the PBCH belongs belongs to the first half-frame in the frame, and if the UE detects a PBCH with a half-frame indication bit set to 1, it can determine that the SSB to which the PBCH belongs belongs to the second half-frame in the frame. Finally, the UE can obtain an SSB index of the SSB to which the PBCH belongs based on the DMRS sequence and the PBCH payload carried by the PBCH.
[0152] Obtaining System Information
[0153] SI is divided into a master information block (MIB) and multiple system information blocks (SIB). System information (SI) other than MIB can be referred to as Remaining Minimum System Information (RMSI). For more information, see below.
[0154] -MIB includes information / parameters for monitoring the PDCCH that schedules the PDSCH carrying SIB1 (System Information Block 1) and is transmitted by the BS via the PBCH of the SSB. For example, the UE can confirm that a CORESET (Control Resource Set) for a Type0-PDCCH common search space exists based on the MIB. The Type0-PDCCH common search space is a type of PDCCH search space and is used to transmit a PDCCH that schedules an SI message. If the Type0-PDCCH common search space exists, the UE can determine (i) a number of contiguous resource blocks and one or more consecutive symbols that constitute the CORESET and (ii) a PDCCH opportunity (e.g., a time domain position for PDCCH reception) based on information in the MIB (e.g., pdcch-ConfigSIB1). If the Type0-PDCCH common search space does not exist, PDCCH-ConfigSIB1 provides information on the frequency location where the SSB / SIB1 exists and the frequency range where the SSB / SIB1 does not exist.
[0155] SIB1 includes information regarding availability and scheduling (e.g., transmission period, SI-window size) of the remaining SIBs (hereinafter, SIBx, where x is an integer equal to or greater than 1). For example, SIB1 may indicate whether SIBx is broadcast periodically or provided at the request of the UE in an on-demand manner. If SIBx is provided in an on-demand manner, SIB1 may include information required for the UE to perform an SI request. SIB1 is transmitted via a PDSCH, and a PDCCH that schedules SIB1 is transmitted via a Type0-PDCCH common search space, and SIB1 is transmitted via a PDSCH indicated by the PDCCH.
[0156] - SIBx is contained in SI messages and transmitted over the PDSCH, each SI message being transmitted within a periodically occurring time window (i.e., the SI window).
[0157] Channel Measurement and Rate-Matching
[0158] In the SSB burst set, a maximum of L SSBs can be transmitted, and the number / location of the SSBs actually transmitted may vary depending on the BS / cell. The number / location of the SSBs actually transmitted is used for rate matching and measurement, and information about the actually transmitted SSBs is provided to the UE.
[0159] Random Access Process
[0160] The UE's optional connection process can be summarized as shown in Table 6 and FIG.
[0161] [Table 15]
[0162] The voluntary access process is used for various purposes. For example, the voluntary access process is used for network initial access, handover, and UE triggered UL data transmission. The UE can obtain UL synchronization and UL transmission resources through the voluntary access process. The voluntary access process can be divided into a contention-based voluntary access process and a contention-free voluntary access process.
[0163] An example of an arbitrary connection process is shown in Figure 10. In particular, Figure 10 shows a contention-based arbitrary connection process.
[0164] First, the UE may send an Optional Access Preamble as Msg1 of an Optional Access process in the UL via the PRACH (eg, see 1701 in FIG. 10(a)).
[0165] Two different lengths of arbitrary access preamble sequences are supported: the long sequence length 839 applies to 1.25 and 5 kHz subcarrier spacings, and the short sequence length 139 applies to 15, 30, 60 and 120 kHz subcarrier spacings.
[0166] Multiple preamble formats are defined by one or more RACH OFDM symbols and different cyclic prefixes (and / or guard times). A RACH configuration for a cell is provided to a UE in the system information of the cell. The RACH configuration includes information on the spacing of PRACH subcarriers, available preambles, preamble formats, etc. The RACH configuration includes association information between SSBs and RACH (time-frequency) resources. The UE transmits an optional connection preamble on a RACH time-frequency resource associated with a detected or selected SSB.
[0167] A threshold value of SSBs for RACH resource association can be set by the network, and a RACH preamble is transmitted or retransmitted based on an SSB whose measured reference signal received power (RSRP) meets the threshold value. For example, the UE can select one of the SSBs that meets the threshold value and transmit or retransmit a RACH preamble based on the RACH resource associated with the selected SSB.
[0168] When the BS receives an voluntary access preamble from the UE, the BS transmits a random access response (RAR) message Msg2 to the UE (see, for example, 1703 in FIG. 10(a)). A PDCCH for scheduling a PDSCH carrying an RAR is CRC-masked with a random access (RA) radio network temporary identifier (RNTI) (RA-RNTI) and transmitted. A UE that detects a PDCCH masked with a RA-RNTI can receive an RAR from a PDSCH scheduled by a DCI carried by the PDCCH. The UE checks whether the random access response information for the preamble it transmitted, i.e., Msg1, is present in the RAR. Whether or not there is voluntary access information for the Msg1 it transmitted can be determined by whether or not there is an voluntary access preamble ID for the preamble transmitted by the UE. If there is no response to Msg1, the UE may retransmit the RACH preamble within a certain number of times while performing power ramping, as shown in Fig. 10(b). The UE calculates the PRACH transmit power of the preamble retransmission based on the recent path loss and a power ramping counter.
[0169] The voluntary access response information includes timing advance information for UL synchronization, an UL grant, and a UE temporary cell RNTI (cell RNTI, C-RNTI). When a temporary UE receives the voluntary access response information for itself on the PDSCH, the UE knows the timing advance information for UL synchronization, the initial UL grant, and the UE temporary cell RNTI (cell RNTI, C-RNTI). The timing advance information is used to control uplink signal transmission timing. In order to allow the UE's PUSCH / PUCCH transmission to be better aligned with the subframe timing at the network stage, the network (e.g., BS) can measure the time difference between PUSCH / PUCCH / SRS reception and subframes and transmit timing advance information based on the measured time difference. The UE can transmit UL transmission on the uplink shared channel as Msg3 of the voluntary access process based on the voluntary access response information (e.g., see 1705 in FIG. 10(a)). Msg3 may include an RRC connection request and a UE identifier. In response to Msg3, the network may send Msg4, which may be treated as a contention resolution message on the DL (e.g., see 1707 in FIG. 10(a)). By receiving Msg4, the UE may enter the RRC connected state.
[0170] Meanwhile, the contention-free voluntary access process may be used in the process of handing over the UE to another cell or BS, or may be executed when requested by a command from the BS. The basic process of the contention-free voluntary access process is similar to the contention-based voluntary access process. However, unlike the contention-based voluntary access process in which the UE randomly selects a preamble to be used from a plurality of voluntary access preambles, in the case of the contention-free voluntary access process, a preamble to be used by the UE (hereinafter, a dedicated voluntary access preamble) is assigned to the UE by the BS. Information on the dedicated voluntary access preamble may be included in an RRC message (e.g., a handover command) or may be provided to the UE via a PDCCH order. When the voluntary access process is started, the UE transmits a dedicated voluntary access preamble to the BS. When the UE receives the voluntary access process from the BS, the voluntary access process is completed.
[0171] As mentioned above, the UL grant in the RAR schedules a PUSCH transmission to the UE. The PUSCH carrying the initial UL transmission due to the UL grant in the RAR is sometimes referred to as the Msg3 PUSCH. The contents of the RAR UL grant, starting from the MSB and ending with the LSB, are given in Table 7.
[0172] [Table 16]
[0173] The TPC command is used to determine the transmit power of the Msg3 PUSCH and is interpreted, for example, according to Table 8.
[0174] [Table 17]
[0175] In a contention-free optional access process, the CSI request field in the RAR UL grant indicates whether the UE should include aperiodic CSI reporting in the corresponding PUSCH transmission. The subcarrier spacing for Msg3 PUSCH transmission is provided by an RRC parameter. The UE shall transmit PRACH and Msg3 PUSCH on the same uplink carrier of the same serving cell. The UL BWP for Msg3 PUSCH transmission is indicated by SIB1 (System Information Block 1).
[0176] 11 is a diagram for explaining the two-step RACH procedure, in which (a) of FIG. 11 shows a contention-based arbitrary connection (CBRA) and (b) of FIG. 11 shows a non-contention-free arbitrary connection (CFRA).
[0177] In FIG. 11, message A (MSGA) includes a preamble and a payload (PUSCH payload). The preamble and the payload are multiplexed by time division multiplexing (TDM). Message B (MSGB) may be sent in response to message A for contention resolution, fallback indication(s), and / or backoff indication.
[0178] Technical terms used herein
[0179] UE: User Equipment
[0180] SSB: Synchronization Signal Block
[0181] MIB: Master Information Block
[0182] RMSI: Remaining Minimum System Information
[0183] FR1: Frequency Range 1. Refers to the frequency range below 6GHz (e.g. 450MHz to 6000MHz).
[0184] FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) range above 24 GHz (e.g., 24,250 MHz to 52,600 MHz).
[0185] BW: Bandwidth
[0186] BWP: Bandwidth Part
[0187] RNTI: Radio Network Temporary Identifier
[0188] CRC: Cyclic Redundancy Check
[0189] SIB: System Information Block
[0190] SIB1: SIB1 = RMSI (Remaining Minimum System Information) for NR devices. Broadcasts information necessary for cell connection of NR terminals.
[0191] CORESET (Control Resource SET): Time / frequency resource on which the NR terminal attempts to decode candidate PDCCH
[0192] CORESET#0: CORESET of Type 0-PDCCH CSS set for NR device (configured in MIB)
[0193] Type 0-PDCCH CSS set: A search space set in which an NR UE monitors a set of PDCCH candidates for a DCI format having a CRC scrambled by SI-RNTI.
[0194] MO: PDCCH Monitoring Occasion for Type0-PDCCH CSS set
[0195] SIB1-R: (additional) SIB1 for reduced capability NR device. Can be limited to being generated in a different TB from SIB1 and transmitted on a separate PDSCH.
[0196] CORESET♯0-R: CORESET♯0 for reduced capability NR devices
[0197] Type0-PDCCH-R CSS set: A search space set in which a Redcap terminal monitors a set of PDCCH candidates for a DCI format having a CRC scrambled by SI-RNTI.
[0198] MO-R: PDCCH Monitoring Occasion for Type0-PDCCH CSS set
[0199] Cell-defined SSB (CD-SSB): Among NR SSBs, SSBs that include RMSI scheduling information
[0200] Non-cell defining SSB (non-CD-SSB): An SSB that is located in the NR sync raster but does not contain RMSI scheduling information for that cell for measurement purposes, but may contain information indicating the location of the cell defining SSB.
[0201] SCS: subcarrier spacing
[0202] SI-RNTI: System Information Radio-Network Temporary Identifier
[0203] Camp on: "Camp on" can be a terminal state in which the terminal is camped on a cell and is ready to receive potential dedicated services.
[0204] TB: Transport Block
[0205] RSA (Redcap standalone): A cell that supports only Redcap devices or services.
[0206] SIB1(-R)-PDSCH: PDSCH that transmits SIB1(-R)
[0207] SIB1(-R)-DCI: DCI for scheduling SIB1(-R)-PDSCH. DCI format 1_0 with CRC (Cyclic Redundancy Check) scrambled by SI-RNTI.
[0208] SIB1(-R)-PDCCH: PDCCH that transmits SIB1(-R)-DCI
[0209] FDRA:Frequency Domain Resource Allocation
[0210] TDRA:Time Domain Resource Allocation
[0211] RA: Random Access
[0212] MSGA: Preamble and payload transmission for optional connection procedure for 2-step RA type.
[0213] MSGB: Response to MSGA in a 2-step optional connection procedure. MSGB consists of response(s) with contention resolution, fallback indication(s), and a backoff indication.
[0214] RO-N: RO (RACH Occasion) for normal UE 4-step RACH and 2-step RACH (if configured)
[0215] RO-N1, RO-N2: When separate RO is configured for normal UE 2-step RACH, it is classified as RO-N1 (4-step) or RO-N2 (2-step).
[0216] RO-R: RO (RACH Occasion) configured separately from RO-N for Redcap UE 4-step RACH and 2-step RACH (if configured)
[0217] RO-R1,RO-R2: If separate RO is configured for Redcap UE 2-step RACH, it is divided into RO-R1 (4-step) and RO-R2 (2-step).
[0218] PG-R: Redcap UE MsgA-Preambles Group
[0219] RAR: Random Access Response
[0220] RAR window: the time window to monitor RA response(s)
[0221] FH: Frequency Hopping
[0222] Recently, in addition to the main 5G use cases (mMTC, eMBB, and URLLC), the importance / interest in use case areas spanning mMTC and eMBB, or mMTC and URLLC, is increasing. There is an increasing need for terminals that can efficiently support such use cases in terms of device cost, power consumption, form factor, etc.
[0223] In this specification, a terminal for such a purpose is referred to as a (NR) reduced capability UE / device, or, in a reduced form, as a (NR) Redcap UE / device. In addition, a general NR terminal that supports all or one or more of the 5G main use cases is referred to as an NR (normal) UE / device, in distinction from a redcap device. A redcap terminal may be a terminal that intentionally reduces some of the capabilities of the 5G key capabilities (peak data rate, user experienced data rate, latency, mobility, connection density, energy efficiency, spectrum efficiency, area traffic efficiency) defined in IMT-2020 in order to achieve all or part of low device cost / complexity, low power consumption, small form factor, etc.
[0224] For convenience, the 5G use case area spanning mMTC and eMBB, or mMTC and URLLC, which is the target use case for Redcap devices, is referred to as the Redcap use case in this specification.
[0225] For example, a Redcap use case could look like this:
[0226] [redcap use cases]
[0227] Connected industries
[0228] - Sensors and actuators will be connected to the 5G network and core.
[0229] - Includes massive IWSN (Industrial Wireless Sensor Network) use cases and requirements.
[0230] - URLLC services with very high requirements, but also relatively low-cost services with requirements for small device form factors with battery life of several years.<relatively low-end service>
[0231] - The requirements for such services are higher than those for LPWA (Low Power Wide Area, i.e. LTE-M / NB-IOT), but lower than those for URCCC and eMBB.
[0232] For example, such environmental devices may include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc.
[0233] Smart City
[0234] - Smart city vertical involves data collection and processing to more efficiently monitor and control urban resources and provide services to city residents.
[0235] - In particular, the deployment of surveillance cameras is an integral part of smart cities, but also in factories and industrial sectors.
[0236] Wearables
[0237] - Wearables use cases include smart watches, rings, eHealth related devices, and medical monitoring devices.
[0238] - One feature for the above use case is the small size of the device.
[0239] The redcap use case may not be supported by some Low Power Wireless Area (LPWA) terminals (e.g., LTE-M, NB-IoT, etc.) in terms of bit rate, latency, etc. NR terminals can support it functionally, but it may be inefficient in terms of terminal manufacturing costs, form factor, battery life, etc.
[0240] Supporting the above use case areas in 5G networks with redcap terminals that have characteristics such as low cost, low power, and small form factor can reduce terminal manufacturing and maintenance costs.
[0241] Redcap use cases have a wide variety of requirements in terms of device complexity, target bit rate, latency, power consumption, etc., but these redcap requirements can be divided into general requirements that apply commonly to all redcap use cases and use case specific requirements that apply only to specific use case(s).
[0242] For example, some typical generic and use case specific requirements might look like this:
[0243] [Redcap requirements]
[0244] Generic requirements
[0245] - device complexity / cost: The primary motivation for the new device type is to lower device cost and complexity compared to Rel-15 / Rel-16 high-end eMBB and URLLC devices. This is a commercial sensor.
[0246] - device size: A requirement for most high-end use cases is to enable device designs with compact form factors.
[0247] - deployment scenarios: The system shall support all FR1 / FR2 bands for FDD and TDD.
[0248] Use case specific requirements
[0249] Industrial wireless sensors
[0250] -reference bit RATe: < 2 Mbps (potentially UL heavy traffic)
[0251] end-to-end latency: < 100 ms; ~ 5-10 ms for safety related sensors
[0252] Battery: at least a few years
[0253] - communication service availability: 99.99%
[0254] - Stationery
[0255] Video Surveillance
[0256] - Reference bit RATe: < 2-4 Mbps for economic video; ~7.5-25 Mbps for high-end video (UL heavy traffic)
[0257] - Latency: < 500 ms
[0258] - Reliability: 99%-99.9%.
[0259] Wearables
[0260] - Reference bit RATe: 10-50 Mbps in DL and >= 5 Mbps in UL for smart wearable application
[0261] - Peak bit RATe: 150 Mbps in DL and 50 Mbps in UL
[0262] -Battery: multiple days (up to 1-2 weeks)
[0263] Table 9 shows examples of use case specific requirements for the three typical Redcap use cases.
[0264] [Table 18]
[0265] 1) Safety-related sensors
[0266] 2) Less complex than typical NR devices
[0267] The Redcap requirement can be met by various functions (combinations) provided by the terminal and base station. The following are examples of features and sub-features that the terminal / base station supports to meet the Redcap requirement:
[0268] [Redcap UE features]
[0269] Complexity reduction features
[0270] - Reduced number of UE RX / TX antennas
[0271] - UE Bandwidth reduction
[0272] - Half-Duplex-FDD
[0273] - Relaxed UE processing time
[0274] -Relaxed UE processing capability
[0275] Power saving
[0276] - Reduced PDCCH monitoring by smaller numbers of BDs and CCE limits
[0277] - Extended DRX for RRC Inactive and / or Idle
[0278] - RRM relaxation for stationary devices
[0279] -Coverage recovery / enhancement
[0280] The redcap use case can define and support one or more terminals, but in this specification, both of the following cases (Case A / Case B) are considered.
[0281] Case A: Support redcap use case in one device type (single device type case)
[0282] Case B: Support Redcap use case on multiple device types
[0283] In case A, a redcap terminal may be a terminal that satisfies all of the redcap requirements (i.e., general requirements and use case specific requirements) and / or a terminal that supports all redcap use cases. In this case, since various requirements must be satisfied simultaneously, there may be a cost increase due to the increased complexity of the terminal, but at the same time, cost reduction effects can be expected through mass production due to the expansion of use cases.
[0284] In the case of Case B, the Redcap use case requirements may be quite diverse, and a terminal type may be defined and supported for each Redcap use case. Even in this case, all general requirements may be commonly satisfied. In this case, each device type defined for each use case is called a redcap device type. Case B includes a case where a number of similar use cases are grouped in terms of requirements and supported by a single terminal type. Each Redcap device type may support a predefined part or a specific combination of Redcap UE functions. In this way, when multiple Redcap device types are defined and Redcap use cases are supported, there is an advantage that a specific Redcap use case can be supported through a Redcap terminal that is more optimized in terms of cost, power consumption, etc. For example, the IWS use case can be supported through a dedicated terminal that is very small, inexpensive, and power-efficient.
[0285] The Redcap use cases and generic requirements or use case specific requirements mentioned in this specification are not necessarily required to be supported or satisfied, and whether they are supported or satisfied may be determined in the form of a trade-off taking into account factors such as cost / complexity, power consumption, and form factor of the Redcap device or device type.
[0286] In this specification, reduced capability may include meanings such as reduced / low complexity / low cost / reduced bandwidth.
[0287] Redcap device type classification and how to report it to the base station
[0288] When the Redcap use case is supported by multiple device types (i.e., Case B), the following method can be considered to classify the Redcap device type. The following method can also be applied to distinguish a Redcap device from an NR terminal in Case A.
[0289] In order to support Redcap terminal operation that is different from NR terminal, the Redcap terminal may need to report its device type information to the base station. FIG. 12 shows a flowchart of a procedure for reporting device type information to the base station. The reporting procedure can reuse the UE capability transfer procedure defined in a predefined standard (e.g., 3GPP TS 38.331) as follows. The base station acquires Redcap device type information through reception of UE capability information and uses the acquired terminal information when scheduling the corresponding terminal.
[0290] For example, the base station / network may request UE capabilities from the terminal in the RRC_CONNECTED state (SH102), and / or the terminal may transmit Redcap device type information in the UE capability information (SH104).
[0291] [Classification method 1]
[0292] Redcap device types can be classified based on one of the main requirements. The main requirements that can be the basis for classification can be, for example, supported max data rate (peak bit RATe), latency, mobility (stationary / fixed, portable, mobile, etc.), battery lifetime, complexity, coverage, etc. A combination of UE features that should be mandatory or can be selectively supported for each classified Redcap device type can be defined in a predefined specification (e.g., 3GPP specification). This can be to reduce the overhead of separately signaling whether a feature is supported for each device type. In this specification, being defined in a predefined specification can also mean being defined / configured / promised between the terminal and the base station.
[0293] The Redcap device type information included in the UE capability information and reported by the terminal to the base station / network may be, for example, a specific field (e.g., RedcapDeviceType) of the UE-NR-Capability IE (Information Element). For example, if the Redcap device type is classified as Redcap device type 1, 2, ..., the value of the RedcapDeviceType field can be expressed as an integer value such as 1, 2, ... or a combination of letters and integers such as r1, r2, .... Therefore, the terminal has an advantage in terms of signaling overhead by reporting the device type and its related parameters by including them in a single field in the capability information.
[0294] For example, the Redcap device type may be classified based on the maximum data rate supported, and the terminal may report the Redcap device type to the base station based on this classification.
[0295] The maximum supported data rate of an NR terminal can be defined / determined in a predefined standard (e.g., 3GPP TS 38.306) using the following formula:
[0296] Supported max data rate
[0297] general
[0298] The maximum DL and UL data rates supported by the terminal may be calculated according to the band or band combination supported by the terminal. A terminal supporting NR (e.g., NR SA, MR-DC) may have to support the calculated DL and UL maximum data rates defined below.
[0299] Supported max data rate
[0300] For NR, the approximate data rate for a given number of aggregated carriers in a band or combination of bands can be calculated by Equation 3:
[0301]
number
[0302] [Table 19]
[0303] is the overhead and can take the following values:
[0304] For the frequency range FR1 for DL, 0.14
[0305] For the frequency range FR2 for DL, 0.18
[0306] For frequency range FR1 for UL, 0.08
[0307] For frequency range FR2 for UL, 0.10
[0308] Only one of the UL or SUL carriers is counted for a cell operating SUL.
[0309] An approximate maximum data rate can be calculated for each delay band or band combination as the maximum of the approximate data rates calculated using the above formula.
[0310] [Table 20]
[0311] In the case of EUTRA in the MR-CD case, the approximate data rate for a given number of aggregated carriers in a band or combination of bands can be calculated by the following equation (4):
[0312]
number
[0313] Here, J is the number of EUTRA component carriers aggregated in the MR-DC band combination.
[0314] TBS i is the total maximum number of DL-SCH transport block bits received or the total maximum number of UL-SCH transport block bits transmitted within 1 ms TTI of the jth CC derived from a predefined standard (e.g., 3GPP TS36.213) based on the number of PRBs based on the bandwidth of the jth CC according to the indicated UE capability based on the maximum MIMO layer of the jth CC supported by the terminal and the maximum modulation order for the jth CC.
[0315] The approximate maximum data rate can be calculated as the maximum of the approximate data rates calculated using Equation 4 for each supported band or band combination.
[0316] For MR-DC, the approximate maximum data rate can be calculated as the sum of the approximate maximum data rates from NR and EUTRA.
[0317] In this case, the parameters required for the formula to calculate the maximum supported data rate that the NR UE should support may be reported by the UE at the request of the base station in the RRC_CONNECTED state. Such parameters are as follows. The upper elements refer to the upper RRC Information Element (IE) to which these parameters belong.
[0318] FeatureSetDownlink
[0319] -scalingFactor
[0320] FeatureSetDownlinkPerCC
[0321] -maxNumberMIMO-LayersPDSCH
[0322] -supportedModulationOrderDL
[0323] -supportedBandwidthDL
[0324] - supportedSubCarrierSpacingDL
[0325] FeatureSetUplink
[0326] -scalingFactor
[0327] FeatureSetUplinkPerCC
[0328] - maxNumberMIMO-LayersCB-PUSCH
[0329] - maxNumberMIMO-LayersNonCB-PUSCH
[0330] -supportedModulationOrderUL
[0331] -supportedBandwidthUL
[0332] - supportedSubCarrierSpacingUL
[0333] In the case of a redcap terminal, in the case of a method of classifying a redcap device type based on the maximum data rate supported, the parameter values for each device type are defined in a predefined specification (e.g., 3GPP specification), and the terminal can indicate the parameter information together with the redcap device type information to the base station by setting the value of the RedcapDeviceType field of the UE-NR-Capability IE to a specific value. Compared to the conventional operation in which the NR terminal includes the parameters in the UE capability information and transmits them to the base station, the redcap terminal can expect a signaling overhead reduction effect by reporting the device type and the associated parameters through one field. The base station obtains the device type and the maximum supported data rate and the values of the parameters listed above through the value of the RedcapDeviceType field, and uses them for terminal scheduling, etc.
[0334] [Classification method 2]
[0335] Alternatively, instead of classifying redcap device types based on primary requirements, redcap device types can be classified based on combinations of UE features that must be supported or can be supported selectively, which may be a more appropriate approach when the features that are supported or can be supported for each use case are clear.
[0336] A combination of UE features predefined in a standard (e.g., 3GPP specification) predefined by redcap device type may be referred to as a feature set. A feature set that must be mandatory supported by device type among the combinations of UE features may be referred to as a mandatory feature set for the corresponding device type or for a device type.
[0337] In this method, the definition of the Redcap device type may not be explicitly stated in a predefined specification (e.g., a 3GPP specification), which may mean that the Redcap use case is supported by separate terminal types that support different feature sets.
[0338] In this method, the redcap terminal can report the redcap device type or the use cases it supports to the base station by reporting a predefined feature set to the base station. This can be considered as a method that further conforms to the basic philosophy of NR, which aims to support various use cases through various optional functions without distinguishing between separate UE categories. The feature set can be replaced by a combination of capability parameters (i.e., a capability parameter set). The feature set can be a mandatory feature set defined in a standard (e.g., 3GPP specification) predefined for each redcap device type.
[0339] For the above operation, a set of candidate features (i.e., a feature pool) for the Redcap device (type) is defined or set in a predefined standard (e.g., 3GPP Specification), and the Redcap device can report a mandatory feature set defined for each type based on its type to the base station. The terminal can further report an optional feature set to the base station in addition to the mandatory feature set. The terminal can perform additional operations or operations further optimized for a specific user case by further selecting and reporting an optional feature set. For example, in the case of a device type for a surveillance camera use case, when a wired power supply terminal and a power supply terminal via a battery coexist, the mandatory feature set does not include a power saving feature, but may specify or include an optional feature. This allows the terminal to selectively support the feature according to the detailed form of the terminal and report to the base station if it supports the feature.
[0340] The base station can determine whether a feature is supported based on the presence or absence of the corresponding parameter in the feature set reported by the red cap terminal and reflect this when scheduling the corresponding terminal.
[0341] [Classification method 3]
[0342] Alternatively, the redcap device type can be classified based on a combination of capability parameters. The combination of capability parameters for classifying the redcap device type can be parameters that determine the redcap requirements. For example, the capability parameters that determine the redcap device type can be the bandwidth, modulation order, number of MIMO layers, etc. that the terminal supports, which determine the maximum data rate requirements that the terminal supports. The parameter values can be a list of actual supportable values or the maximum value of the supported values.
[0343] For example, the capabilities parameters that determine the redcap device type could be:
[0344] -Supported Bandwidth(NRB):(max) UE channel bandwidth or (max) UE transmission bandwidth; RB unit
[0345] - Supported modulation order(Qm): Qm=2 for QPSK; 4 for 16 QAM; 6 for 64 QAM; etc.
[0346] - Supported number of MIMO layers (NL): can be replaced by Number of antennas (Na)
[0347] The combination of capability parameters that determine the redcap device type may be referred to as the capability parameter set of that device type. For example, the redcap device type can be defined by dividing the capability parameter set value in ascending (or descending) order of supported max data rate. The following example shows the case where M device types are defined in ascending order of supported max data rate.
[0348] Redcap device type separated by capability parameter set value(s) (example):
[0349] - Device Type 1: {NL, NRB, Qm}={1, 25, 2}
[0350] - Device Type 2: {NL, NRB, Qm}={1, 25, 4}, or {1, 52, 2}
[0351] - Device Type 3: {NL, NRB, Qm}={1, 52, 4}, or {1, 106, 2}
[0352] - Device Type 4: {NL, NRB, Qm}={1, 106, 4}, or {2, 106, 2}
[0353] - Device Type 5: {NL, NRB, Qm}={1, 106, 6}
[0354] - Device Type6: {NL, NRB, Qm}={2, 106, 4}
[0355] - Device Type 7: {NL, NRB, Qm}={2, 106, 6}
[0356] -…
[0357] - Device Type M: {NL, NRB, Qm}={X, Y, Z}
[0358] For example, in the case of NR FR1 (Frequency Range 1, i.e., 6 GHz or lower band), N RBThe value can be one of the values defined in Table 10 (maximum number of RBs that can be set for each UE channel bandwidth). The above example is a value based on subcarrier spacing (SCS) = 15 kHz. If the Redcap device supports SCS = 30 kHz and the cell to be connected uses SCS = 30 kHz for data transmission, the NRB value based on SCS = 15 kHz in the above example will be SCS = 30 kHz by referring to Table 10. It can be replaced with the corresponding value.
[0359] Table 10 shows the maximum transmission bandwidth setting N by subcarrier spacing (SCS) in NR FR1. RB Shows.
[0360] [Table 21]
[0361] In the above device type classification example, device types 2 / 3 / 4 are cases where one device type is defined by multiple capability set values. When device types are classified based on the maximum supported data rate as described above, multiple capacity parameter set values defining one device type may mean combinations that support the same or similar maximum supported data rate.
[0362] Using the device types defined in the above examples, the supportable device types for each use case can be defined as follows: Based on the supportable device types, the base station can limit cell connections or perform subscription-based barring.
[0363] Supported device type(s) by use case (example)
[0364] - IWS: Device types 1,2
[0365] - Video Surveillance: Device types 2,3
[0366] - Wearables: Device type: Device types 4, 5, 6, 7
[0367] In order to avoid increased costs due to market segmentation caused by excessive device type subdivision, the number of device types M may be limited. For example, if M is limited to 1, it is possible to support all of the target use cases with a single device type without dividing the Redcap terminal into multiple device types.
[0368] In another example, when M is limited to 3, the device type classification and the supportable device types for each use case can be defined as follows:
[0369] Device type classification by capability set value(s) (e.g. M=3):
[0370] - Device Type 1: {NL, NRB, Qm}={1, 25, 2} (or {1, 25, 4} or {1, 52, 2})
[0371] - Device Type 2: {NL, NRB, Qm}={1, 52, 4} or {1, 106, 2}
[0372] - Device Type 3: {NL, NRB, Qm}={2, 106, 6}
[0373] Supported device type(s) by use case (e.g. for M=3)
[0374] - IWS:Device types 1
[0375] - Video Surveillance: Device types 3
[0376] - Wearables: Device type: Device types 7
[0377] UE max bandwidth (i.e., Redcap UE bandwidth capability) can be determined as the minimum bandwidth that satisfies the bit rate required in the target use case. Reducing the UE max bandwidth can be expected to reduce RF element and / or baseband processing costs and reduce power consumption. Here, the required bit rate can mean a peak rate or a maximum supported data rate, taking into account that device manufacturing costs are determined by a peak rate rather than an average bit rate or a reference bit rate, or a maximum supported data rate.
[0378] When determining the maximum bandwidth supporting the requested bit rate, other parameters that determine the requested bit rate (e.g., number of antennas (NL), modulation order (Qm), etc.) can be assumed to have specific values. For example, in the above example, for device type 3, a peak rate of about 28 MHz can be supported. In this case, the required max bandwidth is 20 MHz (106 RBs) when {NL=1, Qm=2} is assumed, and 10 MHz (52 RBs) when {NL=1, Qm=4} is assumed. Alternatively, the required max bandwidth can be 5 MHz (25 RBs) when {NL=2, Qm=4} is assumed.
[0379] - Device type 3: {NL, NRB, Qm} = {1, 52, 4} or {1, 106, 2}
[0380] Within the max UE bandwidth of a redcap UE, transmission bandwidth can be allocated by network configuration using RRC signaling, etc., and transmission / reception can be performed.
[0381] The UE min bandwidth can be defined as the minimum of the NR UE channel bandwidth (or transmission bandwidth) that is greater than or equal to the NR SSB bandwidth.
[0382] For example, in FR1, for NR SSB with SCS=15 kHz, UEmin BW=5 MHz, and for NR SSB with SCS=30 kHz, UEmin BW=10 MHz.
[0383] As another example, in FR2, for NR SSB with SCS=120 kHz, UEmin BW=40 MHz, and for NR SSB with SCS=240 kHz, BW=80 MHz.
[0384] This could be to achieve low power consumption by supporting services with low bit rate requirements with minimal bandwidth, as well as to support connections to NR cells via NR SSBs.
[0385] Classification method 4
[0386] Considering that the bandwidth capability of the redcap UE is determined by the required bit rate of each use case, the Redcap device type can be classified based on the UE bandwidth capability. For example, the bandwidth capability that determines the Redcap device type can be the (maximum) UE channel bandwidth or the (maximum) UE transmission bandwidth (i.e., the supported bandwidth (NRB)) expressed in RBs. Alternatively, the bandwidth capability can be the minimum UE channel bandwidth or the minimum UE transmission bandwidth. Specifically, the following classifications are possible:
[0387] - Classification method 4-1) Classify according to Max bandwidth and use according to the actual data sending / receiving bandwidth (<=max bandwidth) setting
[0388] - Classification method 4-2) Classify according to Min bandwidth and use according to the actual data sending / receiving bandwidth (>=min bandwidth) setting
[0389] - Classification method 4-3) Define one or more supportable bandwidth (set) for each device type, and use the actual data transmission / reception bandwidth settings within that bandwidth (set).
[0390] For classification methods 4-1 / 2 / 3, the max bandwidth may be limited to a value smaller than the NR bandwidth (e.g., 20 MHz), and the min bandwidth may be greater than or equal to the SSB bandwidth (e.g., 5 MHz for 15 kHz SSB).
[0391] How Redcap UE supports initial connection and UL frequency hopping
[0392] In a new radio (NR) cell supporting a Redcap terminal (user equipment, UE), it may be preferable to share as many resources as possible between a normal UE and a Redcap UE in terms of resource efficiency. That is, in a cell where a normal UE and a Redcap UE coexist or can coexist, it may be preferable to share as many resources as possible between a normal UE and a Redcap UE in terms of resource efficiency. If resources available / schedulable for a normal UE and resources available / schedulable for a Redcap UE are completely separated from each other, there may be problems such as reduced resource utilization and limited scheduling flexibility from the perspective of a base station.
[0393] However, in the following cases (1) to (4), the conventional method may not effectively support resource sharing between normal UE and Redcap UE in the random access process for cell connection.
[0394] (1) When a (additional) repetition is required for a Redcap UE due to differences in coverage performance between an NR UE and a Redcap UE in Message 2 (msg2) (e.g., random access response, RAR), msg4, or msgB steps, etc.
[0395] (2) When the initial uplink (UL) bandwidth part (BWP) cannot be set within the max UE bandwidth of the Redcap UE, taking into account the impact on Legacy NR UE
[0396] (3) When the impact on NR UE during optional connection cannot be avoided due to UE processing time relaxation of Redcap UE, etc.
[0397] (4) In the case where a separate initial UL BWP is established and operated for Redcap UE due to reasons such as 1 / 2 / 3 above
[0398] For example, in the case of (1), repetition in the random access channel (RACH) process of the Redcap UE can be applied to at least one of Msg1-4 / MsgA-B in the same manner, or individually with independent settings for each message.
[0399] In this specification, a method for supporting initial connection and UL frequency hopping of a redcap UE in an NR cell where normal UEs and redcap UEs coexist is proposed.
[0400] Specifically, this specification proposes a method for receiving an optional connection response from a redcap UE (hereinafter, the first embodiment), a method for transmitting an Msg3 PUSCH from a redcap UE (hereinafter, the second embodiment), and a method for transmitting an Msg4 ACK / NACK PUCCH from a redcap UE (hereinafter, the third embodiment).
[0401] The embodiments described herein below are divided for convenience of explanation, and it is understood that some methods and / or configurations of one embodiment may be replaced with methods and / or configurations of another embodiment or may be applied in combination with each other.
[0402] A slot, a subframe, a frame, etc., referred to in the embodiments described herein may correspond to specific examples of a certain time unit used in a wireless communication system. That is, when applying the method proposed in the present specification, the time unit, etc., may be replaced with another time unit applied in another wireless communication system.
[0403] The contents carefully reviewed above (3GPP system, frame structure, NR system, etc.) can be applied in combination with the method proposed in this specification described below and / or can be supplemented to clarify the technical features of the method proposed in this specification.
[0404] In this specification, "()" can be interpreted as excluding the contents in the parentheses or including the contents in the parentheses. And / or in this specification, "()" can mean the group of elements (or contents) in the parentheses, or the abbreviation / full name of the term before the parentheses, and / or the English description of the contents before the parentheses. Of course.
[0405] In this specification, " / " can be interpreted as both the case where all of the contents separated by the / are included (and) and the case where only a part of the separated contents is included (or).
[0406] First embodiment
[0407] In this embodiment, we pay close attention to how to receive a random access response (RAR) from a Redcap UE.
[0408] Redcap UEs can support limited UE bandwidth, taking into account the complexity of the UE. When a random access channel (RACH) occupation (RO) is configured in the conventional manner for an NR UE, the initial UL bandwidth of such a UE may not include the entire frequency domain of the RO. In this case, the Redcap UE may need to perform a frequency retuning operation and receive a random access response (RA) after transmitting a random access preamble (RA preamble) during the random access (RA) process for initial access. In addition, a UE operating as half-duplex FDD in a frequency division duplex (FDD) band (during the initial access process) may also need to receive an RAR after frequency retuning.
[0409] In such a case, during uplink (UL)-to-downlink (DL) or transmit (Tx)-to-receive (Rx) switching (with frequency retuning), downlink (DL) reception including physical downlink control channel (PDCCH) monitoring may be impossible, so the RAR window of the Redcap UE may start X symbols or X'us later than the RAR window of the normal UE. For example, X or X' may be a transition time (N) defined in a predefined specification (e.g., 3GPP TS 38.211). Rx-Tx Or N Tx-Rx) and / or frequency retuning time. Alternatively, X or X' may be defined in a new predefined specification (e.g., 3GPP specification) taking into account the characteristics of the Redcap UE, or may be a value configured by the base station as a higher layer configuration via system information.
[0410] For example, a conventional RAR window for an NR UE is specified in predefined standards (e.g., 3GPP TS 38.213, 3GPP TS 38.321) as follows:
[0411] In connection with the Type 1 random access procedure, in response to a physical random access channel (PRACH) transmission, the UE may attempt to detect DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a corresponding random access radio network temporary identifier (RA-RNTI) during a window controlled by higher layers. The window may start from the first symbol of the earliest control resource set (CORESET) configured to receive a PDCCH of the Type1-PDCCH Common search space (CSS) set, which is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. Here, the symbol duration may correspond to a subcarrier spacing (SCS) for the Type1-PDCCH CSS set. The length of the window in number of slots may be provided in the ra-ResponseWindow based on the SCS of the Type1-PDCCH CSS set.
[0412] And / or when an Unsolicited Access Preamble is sent in conjunction with a Random Access Response reception, regardless of the possible occurrence of a measurement gap, the MAC entity shall:
[0413] When a contention-free random access preamble for a beam failure recovery request is transmitted by a MAC entity, the MAC entity may start the ra-ResponseWindow configured in BeamFailureRecoveryConfig at the first PDCCH occasion described in a predefined standard (e.g., 3GPP TS38.213) at the end of the random access preamble transmission. The MAC entity may monitor PDCCH transmissions in the search space indicated by the recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is running.
[0414] Otherwise, the MAC entity may start the ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH occasion described in a predefined standard (e.g., 3GPP TS 38.213) at the end of the optional connection preamble transmission. The MAC entity may monitor the PDCCH of the SpCell for any connection response identified by the RA-RNTI while the ra-ResponseWindow runs.
[0415] In order to define the RAR window of the Redcap UE in the above manner (i.e., a predefined standard), the Redcap UE can monitor DCI format 1_0 scrambled with a random access-radio network temporary identifier (RA-RNTI) CRC from the first symbol of the earliest control resource set (CORESET) starting at least X symbols or X'us from the last symbol of the RO used for RA preamble transmission after RA preamble transmission. Also, the period for monitoring the physical downlink control channel (PDCCH) for RAR reception (i.e., the start point of the RAR window or the point at which the RAR window counter starts) can be defined as the first symbol of the earliest CORESET starting at least X symbols or X'us from the last symbol of the RO used for RA preamble transmission.
[0416] The values of X or X' are as described above. Alternatively, the value of X in symbols can be one greater than the number of smallest symbol lengths greater than the transition time and / or frequency retuning time.
[0417] For the RAR window of a Redcap UE (in addition to the RAR window for a normal UE), a separate RAR window for the Redcap UE is used. The size of the RAR window can be determined by the setting value of the RAR window counter. And / or, the size of the separate RAR window for the Redcap UE can have the same size as the existing RAR window (without separate size setting) or can be set separately. If it has the same size, the RAR window of the Redcap UE can be a staggered form of the conventional RAR window.
[0418] And / or, the base station may use the same RAR window as a normal UE or share the RAR window without defining a separate RAR window for the Redcap UE. In this case, the base station may ensure that the base station meets the above-mentioned transition time and / or frequency retuning time requirements by implementing the base station.
[0419] Second embodiment
[0420] In this embodiment, we take a closer look at how Redcap UE sends Msg3 PUSCH.
[0421] During the RA procedure for initial attachment of an NR UE, Msg3 physical uplink shared channel (PUSCH) transmissions can be scheduled by the RAR UL grant. The RAR UL grant field configuration and the associated Msg3 PUSCH frequency domain resource allocation (FDRA) and Frequency Hopping (FH) information are specified in predefined standards (e.g., 3GPP TS 38.213) as follows:
[0422] For Type-1 Optional Access Procedure, the RAR UL grant schedules the PUSCH transmission from the UE. The contents of the RAR UL grant starting from the most significant bit (MSB) and ending at the least significant bit (LSB) are shown in Table 11.
[0423] If the value of the frequency hopping flag is 0, the UE transmits the PUSCH without frequency hopping, otherwise, the UE transmits the PUSCH with frequency hopping.
[0424] The UE determines the MCS for PUSCH transmission from the first 16 indices of the applicable MCS index table for PUSCH.
[0425] The TPC command value is used to set the power of the PUSCH transmission and is interpreted according to Table 12.
[0426] The CSI request field is reserved.
[0427] The ChannelAccess-CPext field indicates a channel access type and a cyclic prefix (CP) extension for operating with a shared spectrum channel access.
[0428] Table 11 shows the optional connection response grant content field size.
[0429] [Table 22]
[0430] [Table 23]
[0431] For PUSCH transmissions scheduled by a RAR UL grant, an active UL BWP is indicated by higher layers.
[0432] If useInterlace-PUCCH-PUSCH is not provided by BWP-UplinkCommon and BWP-UplinkDedicated, to determine the frequency domain resource allocation for PUSCH transmission within the active UL BWP:
[0433] - If the active UL BWP and the initial UL BWP have the same SCS and the same CP length, and the active UL BWP contains all the RBs of the initial UL BWP or the active UL BWP is the initial UL BWP, the initial UL BWP is used.
[0434] - Otherwise, the RB numbering starts from the first RB of the active UL BWP and the maximum number of RBs for frequency domain resource allocation is the same as the number of RBs in the initial UL BWP.
[0435] [Table 24]
[0436] The frequency offset of the second hop for PUSCH transmission or Msg3 PUSCH retransmission with frequency hopping scheduled by RAR UL grant is shown in Table 13.
[0437] Table 13 shows the frequency offset for the second hop of a PUSCH transmission with frequency hopping scheduled by an RAR UL grant or Msg3 PUSCH retransmission.
[0438] [Table 25]
[0439] As specified above (i.e., predefined standard), in the conventional RA procedure for initial access, Msg3 FDRA and frequency hopping (FH) can be determined based on the initial terminal bandwidth (initial UL bandwidth). The initial UL bandwidth can mean the bandwidth of the initial ULBWP.
[0440] However, in an NR cell that simultaneously supports normal UE and Redcap UE, if the initial UL BWP is not limited to the maximum terminal bandwidth (max UE bandwidth) of the Redcap UE due to legacy impact (i.e., if the initial UL bandwidth is larger than the Redcap UE bandwidth), the following Msg3 PUSCH transmission method for Redcap UE may be considered.
[0441] In the following manner, when a separate initial UL BWP for Redcap UE is configured and operated for the above reason, Redcap UE bandwidth may include the meaning of a separate initial UL BWP for Redcap or the bandwidth of the separate initial UL BWP. And / or, the bandwidth of a separate U initial UL BWP for Redcap UE may be limited to less than the Redcap UE bandwidth. For the above reason, in this specification, the meaning of "the bandwidth of the initial UL BWP or the initial UL bandwidth is larger than the Redcap UE bandwidth" or "the base station must configure the initial UL bandwidth for normal UE to be larger than the Redcap UE bandwidth" may include the meaning of "a separate initial UL BWP for Redcap is configured / has been configured" for such a reason.
[0442] It is to be understood that the methods described below are only divided for the convenience of explanation, and that the components of one method may be substituted with the components of another method, or may be applied in combination with each other.
[0443] (Method 2-1)
[0444] In this method, if the initial UL bandwidth is larger than the Redcap UE bandwidth, FH is turned off.
[0445] If the base station must set the initial UL bandwidth for normal UE to be larger than the Redcap UE bandwidth, it can turn off the FH of Msg3 PUSCH and schedule the 1st frequency hop indicated by the FDRA of the RAR UL grant to be within the Redcap UE bandwidth. This allows the base station to receive all PUSCH transmissions of normal UE and Redcap UE. For example, in this specification, the initial UL bandwidth can refer to an initial uplink bandwidth part (initial UL BWP).
[0446] And / or, for this purpose, the base station may set the value of the FH flag in the RAR UL grant to 0. And / or, the FH flag in the RAR UL grant is separately configured and used to enable () / disable () FH of the Redcap UE. And / or, if the initial UL bandwidth is larger than the Redcap UE bandwidth, the terminal may assume that FH is off (or the FH flag value is 0) and transmit the Msg3 PUSCH in the above manner via a frequency domain indicated by the FDRA in the RAR UL grant.
[0447] Figure 13 illustrates a method for a base station to schedule Msg3 PUSCH in the Redcap UE bandwidth without FH when the initial UL bandwidth is larger than the Redcap UE bandwidth. Referring to Figure 13, the Redcap UE can transmit PUSCH through resources contained in the Redcap UE bandwidth without performing frequency hopping.
[0448] (Method 2-2)
[0449] This method is a method for interpreting the FDRA and / or FH flags of the RAR UL grant differently.
[0450] If the base station must set the initial UL bandwidth for a normal UE to be larger than the Redcap UE bandwidth, the Redcap UE may apply / interpret the PUSCH scheduling result indicated by the FDRA and / or FH flag of the RAR UL grant, or field values such as the FDRA and / or FH flag, in a manner different from that of a normal UE. If the Initial UL bandwidth is larger than the Redcap UE bandwidth, the PUSCH scheduling result indicated by the FDRA and / or FH flag of the RAR UL grant may be as follows:
[0451] [Case 1] The 1st frequency hop is within the Redcap UE bandwidth, and the 2nd frequency hop is outside it.
[0452] [Case 2] 1st frequency hop is outside the Redcap UE bandwidth, 2nd frequency hop is included
[0453] [Case 3] When the 1st frequency hop and the 2nd frequency hop all belong to the Redcap UE bandwidth
[0454] [Case 4] When the 1st frequency hop and 2nd frequency hop are outside the Redcap UE bandwidth
[0455] As in Cases 1 and 2, when FH for Msg3 PUSCH is enabled and only one of the two frequency hops belongs to the Redcap UE bandwidth, the base station can transmit the 1st hop and 2nd hop without FH using the frequency resources of the hop belonging to that Redcap UE bandwidth.
[0456] FIG. 14 illustrates Method 2-2 when the initial UL bandwidth is larger than the Redcap UE bandwidth, Case 1.
[0457] Referring to FIG. 14, when the bandwidth of the initial UL bandwidth part (BWP) is larger than the Redcap UE bandwidth, and in the case of Case 1, the Msg3 PUSCH (or the 1st hop 1410 and the 2nd hop 1420) can be transmitted without FH in the frequency domain of the 1st frequency hop 1410 or as instructed by the FDRA of the RAR UL grant.
[0458] FIG. 15 illustrates Method 2-2 for Case 2, where the initial UL bandwidth is larger than the Redcap UE bandwidth.
[0459] Referring to FIG. 15, when the bandwidth of the initial UL BWP is larger than the Redcap UE bandwidth, in Case 2, the Msg3 PUSCH (or the 1st hop 1510 and the 2nd hop 1520 can be transmitted without FH in the frequency domain of the 2nd hop 1520 belonging to the Redcap UE bandwidth.
[0460] FIG. 16 illustrates an example of Method 2-2 when the initial UL bandwidth is larger than the Redcap UE bandwidth, Case 3.
[0461] Referring to FIG. 16, in case 3, since the 1st hop 1610 and the 2nd hop 1620 all belong to the Redcap UE bandwidth, Msg3 PUSCH can be transmitted from the 1st hop 1610 and the 2nd hop 1620 indicated by the FDRA and FH flag of the RAR UL grant (FH on).
[0462] In case 4, the Msg3 PUSCH can be transmitted at the 1st hop (or 2nd hop) without FH. In this case, since the 1st hop (or 2nd hop) does not belong to the initial UL bandwidth that the Redcap UE received through system information, the Redcap UE can transmit the Msg3 PUSCH after frequency retuning. For example, the system information can be system information block 1 (SIB1). And / or, in this case, the Redcap UE considers that the cell has barred the Redcap UE or does not allow the Redcap UE to connect, and the Redcap UE can continue to perform a cell search (cell search) process for other connectable cells.
[0463] And / or, the base station may barr the Redcap UE by making a part or all of the Msg3 PUSCH indicated by the FDRA and / or FH flag value of the RAR UL grant not belong to the Redcap UE bandwidth or the initial UL bandwidth of the Redcap UE. Alternatively, the base station may barr the Redcap UE by making the Msg3 PUSCH scheduling result indicated by the FDRA and / or FH flag value of the RAR UL grant belong to any one of Case 1, Case 2, or Case 4.
[0464] And / or, the Redcap UE can interpret the Msg3 PUSCH scheduling information based on the Redcap initial UL bandwidth. The Redcap UE can determine the final hop by applying a modulo operation (for the missing hop) based on its (separate) initial UL bandwidth. And / or, the base station can set the reference Redcap initial UL bandwidth cell-specific via system information (e.g., SIB1). Otherwise, the initial UL bandwidth information of the Redcap UE can be transmitted to the base station early in the Msg1 stage.
[0465] And / or, for convenience of modulo operation, normal UE initial UL bandwidth may be limited to N * Redcap UE initial UL bandwidth (e.g., N=1, 2, 4, 8, or a positive integer). For example, a separate initial UL BWP for Redcap may be set to have a bandwidth value of floor(initial_UL_bandwidth / N). Here, initial_UL_bandwidth means the bandwidth of the initial UL BWP for normal UE and may be in resource block (RB) units. FIG. 17 is an example when N=2. FIG. 17 shows method 2-2 for case 1, where the initial UL bandwidth is larger than the Redcap UE bandwidth. That is, FIG. 17 is an example of applying modulo operation to case 1.
[0466] 17, the initial UL BWP is twice (N=2) the Redcap UE initial UL bandwidth (or Redcap UE bandwidth). The Redcap UE can determine the final 2nd hop 1730 by applying a modulo operation based on the Redcap UE initial UL bandwidth (or Redcap UE bandwidth) based on the fact that the 2nd hop 1720 is different from the Redcap UE initial UL bandwidth (or Redcap UE bandwidth). The Redcap UE can transmit PUSCH at the 1st hop 1710 and the final 2nd hop 1730.
[0467] And / or, the example of Figure 17 shows that performing a modulo operation based on the Redcap UE initial UL bandwidth may produce a result that cannot obtain frequency diversity gain. To improve this drawback, a method of arranging hops at symmetrical positions based on the boundaries of the Redcap initial UL bandwidth, other than a simple modulo operation, can be considered.
[0468] FIG 18 shows the method 2-2 when the initial UL bandwidth is larger than the Redcap UE bandwidth and in case 1. That is, FIG 18 is an example of applying mirroring to case 1.
[0469] 18, when the 2nd hop 1820 is out of the Redcap UE initial bandwidth (or Redcap UE bandwidth), the 2nd hop 1820 can be mirrored and configured based on the upper border of the Redcap initial UL bandwidth. The Redcap UE can transmit a PUSCH at the 2nd hop 1830 mirrored with the 1st hop 1810.
[0470] The mirroring method of FIG. 18 is expected to have a frequency diversity gain in contrast to the example of FIG.
[0471] And / or, in the case of Redcap UE, the Msg3 PUSCH can be transmitted in a frequency domain separated from normal UE by applying a frequency offset to the FDRA value of the RAR UL grant and transmitting it. This method may have an advantage of facilitating detection in the base station compared to a method in which some frequency hops are superimposed. And / or, when FH enable is indicated in the RAR UL grant, the frequency offset value of the 2nd hop may be interpreted differently from the conventional one, or an additional frequency offset may be applied to the conventional frequency offset value of the 2nd hop. In the former case, the Redcap UE can determine the frequency location of the 2nd hop by multiplying the 2nd hop location value calculated based on a predefined standard (e.g., Table 13) by a scaling factor (as an example, the scaling factor can be redcap_UE_initial_UL_bandwidth / normal_UE_initial_UL_bandwidth), or by applying the UE bandwidth of the Redcap UE or the initial UL bandwidth of the Redcap UE instead of the initial UL bandwidth of the normal_UE.
[0472] In the method 2-1 and the method 2-2, the Redcap UE bandwidth can be replaced with the RO bandwidth configured to be used by the Redcap UE for initial access. That is, FH off can be determined, FH can be performed, and FDRA can be interpreted based on the RO bandwidth. In this case, the RO can mean an RO that is separately configured for the Redcap UE, or an RO that is configured for the NR UE without any separate configuration. In this case, the Redcap UE can operate assuming the RO bandwidth as the initial UL BWP of the Redcap UE.
[0473] (Method 2-3)
[0474] This method is a method for identifying a Redcap UE via Msg3 PUSCH transmission.
[0475] According to the method proposed above, Msg3 PUSCH of normal UE and Redcap UE can be transmitted to resources that are divided in the time / frequency domain or to different FH patterns. In this case, the base station can distinguish the UE (type) (e.g., normal UE or Redcap UE) by performing blind decoding (BD) (or blind detection) on the divided Msg3 PUSCH time / frequency transmission resources or FH patterns. This method is used to distinguish from normal UE in the Msg3 stage when early UE ID is not supported in Msg1. And / or, this method is used to provide additional UE (type) information together with early UE ID in Msg1.
[0476] For example, the additional UE (type) information may be information regarding the number of Rx antenna branches (or ports), or an indication of whether a particular function of the Redcap UE is supported. And / or, this method may be applied for (additional) UE identification even when the initial UL bandwidth size is the same as that of the normal UE. The division of the Msg3 PUSCH resource may not be limited to the frequency domain. As an example, the TDRA value indicated in the RAR UL grant may be interpreted differently (e.g., by applying an additional offset), or the Msg3 PUSCH of the normal UE and the Redcap UE may be divided and transmitted in the form of time division multiplexing (TDM).
[0477] (Method 2-4)
[0478] This method is a method for retransmitting Msg3 PUSCH.
[0479] After transmitting Msg3 PUSCH by one of the above methods, the Redcap UE may receive an instruction to retransmit Msg3 PUSCH from the base station. The Msg3 PUSCH retransmission may be indicated via DCI format 0_0 with CRC scrambling in the temporary cell (TC)-RNTI. If retransmission is indicated via DCI, information such as FDRA / time domain resource assignment (TDRA) and FH for Msg3 PUSCH retransmission may follow the instruction of the Msg3 retransmission DCI. If the initial UL bandwidth is larger than the Redcap UE bandwidth, the interpretation / operation of FDRA / TDRA and / or FH may be applied according to the previous RAR UL grant and the proposed method.
[0480] When Redcap UE fails in initial transmission of Msg3 and receives a retransmission instruction, Redcap UE uses resources that are differentiated from normal UEs in a different way from initial transmission. For example, if Redcap UE transmits frequency resources such as FDRA and FH pattern that are differentiated from normal UEs in initial transmission, Redcap UE that receives a retransmission command can apply a time offset to the TDRA value and transmit using resources that are differentiated from normal UEs in the TDM method.
[0481] Third embodiment
[0482] In this embodiment, we take a closer look at how Redcap UE sends Msg4 ACK / NACK PUCCH.
[0483] The PUCCH transmission method before receiving a dedicated PUCCH resource configuration is specified in a predefined standard (eg, 3GPP TS 38.213) as follows.
[0484] [Table 26]
[0485] The UE shall transmit PUCCH with frequency hopping if useInterlacePUCCH-PUSCH is not provided in BWP-UplinkCommon, otherwise the UE shall transmit PUCCH without frequency hopping.
[0486] The orthogonal cover code with index 0 is used for PUCCH resources with PUCCH format 1 in Table 14.
[0487] The UE transmits the PUCCH using the same spatial domain transmission filter as the PUSCH transmission scheduled by the RAR UL grant.
[0488] If the UE is provided with a pdsch-HARQ-ACK-Codebook, the UE shall generate at most one HARQ-ACK information bit.
[0489] [Table 27-1] [Table 27-2]
[0490] Table 14 shows the PUCCH resource set before the dedicated PUCCH resource is configured.
[0491] [Table 28]
[0492] As specified in the above-mentioned predefined standard, PUCCH transmission before setting dedicated PUCCH resources always performs FH based on the initial UL bandwidth. When the initial UL bandwidth is larger than the Redcap UE bandwidth, the FH problem can be applied in the same manner as the content previously proposed by Msg3 PUSCH. That is, at least one of the methods 2-1 to 2-4 of the second embodiment can be applied to PUCCH transmission.
[0493] [Table 29]
[0494] Previously, user multiplexing via time domain OCC (Orthogonal Cover Code) was not supported when transmitting PUCCH during initial access. With the introduction of Redcap, time domain OCC can be supported when transmitting PUCCH via dedicated PUCCH resources to secure additional physical uplink control channel (PUCCH) transmission resources. In this case, the user multiplexing capability using time domain OCC is determined by the spreading factor (N SF If user multiplexing via time domain OCC is supported when transmitting PUCCH during initial access, the PUCCH transmission resource determination method may be further modified by N SF For example, in the method of determining the first (or second) frequency hop (PRB index) for the PUCCH transmission, N SF can be applied.
[0495] [Table 30]
[0496] And / or, similar to the Msg3 PUSCH, the Redcap UE can transmit the PUCCH in a frequency region separated from that of the normal UE by applying a cell-specific frequency offset to the PUCCH transmission frequency resource for the normal UE and transmitting the PUCCH. In this case, the PUCCH transmission frequency resource can be determined by adding an additional cell-specific frequency offset by reusing (a part of) Table 14. For this purpose, the cell-specific frequency offset can be included in the SIB (e.g., the initial UL BWP setting BWP-UplinkCommon(-R) of SIB1) and transmitted.
[0497] Although the PUCCH FH has been described based on intra-slot FH, it can be similarly applied to the case where inter-slot FH is supported.
[0498] The Msg4 ACK / NACK PUCCH transmission method in this specification (ie, the third embodiment) can be similarly applied to the MsgB ACK / NACK PUCCH transmission method when supporting two-step RACH.
[0499] FIG. 19 is a flowchart for explaining the operation method of the terminal proposed in this specification.
[0500] Referring to FIG. 19, first, a reduced capability (Redcap) terminal (100 / 200 in FIG. 21 to FIG. 24) can transmit an optional access preamble to a base station in step S1901. For example, a Redcap terminal can mean a terminal whose (maximum) bandwidth is smaller than the NR bandwidth (or initial UL BWP). For example, the (maximum) bandwidth of a Redcap terminal can be 20 MHz.
[0501] And / or, the operations of FIG. 19 can be performed by a normal terminal as well as a Redcap terminal.
[0502] For example, the operation of the Redcap terminal transmitting the optional connection preamble in step S1901 can be realized by the above-mentioned devices of Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit the optional connection preamble.
[0503] And / or, the Redcap terminal (100 / 200 in FIG. 21 to FIG. 24) may receive an voluntary connection response from the base station based on the voluntary connection preamble in step S1902.
[0504] And / or, the unsolicited connection response may be received based on frequency retuning based on the fact that the bandwidth of the Redcap terminal does not include resources (or ROs) for the unsolicited connection response, i.e., the Redcap terminal may change the position of the starting frequency of the bandwidth of the Redcap terminal so that the bandwidth includes resources for the unsolicited connection response.
[0505] And / or the random access response window (RARwindow) can be set to start X symbols or X'us later than the RAR window of a normal terminal, where X or X' is a transition time (N) defined in a predefined standard (e.g., 3GPP TS 38.211). Rx-Tx Or N Tx-Rx) and / or may be greater than or equal to the frequency retuning time, and / or X or X' may be a value defined in consideration of the characteristics of a Redcap UE. And / or the start (time) position of the RAR window may be set by system information. That is, X or X' may be a value set by higher layer configuration via system information. For example, a general terminal may refer to a terminal that is not a Redcap terminal.
[0506] For any operation of receiving a connection response other than and / or, refer to the contents of the first embodiment. That is, for specific contents of the above-mentioned operations or operations that can be substituted / changed, refer to the contents of the first embodiment.
[0507] For example, the operation of the Redcap terminal receiving the optional connection response in step S1902 can be realized by the above-mentioned devices of Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the optional connection response.
[0508] And / or, the Redcap terminal (100 / 200 in FIG. 21 to FIG. 24) may transmit a message (Msg) 3 (physical uplink shared channel (PUSCH)) to the base station based on the voluntary access response in step S1903. In this specification, the Msg3 PUSCH may be referred to as Msg3 or PUSCH.
[0509] For example, the operation of the Redcap terminal transmitting the Msg3 PUSCH in step S1903 can be realized by the above-mentioned devices in Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206 to transmit the Msg3 PUSCH.
[0510] And / or, the Redcap terminal (100 / 200 in FIG. 21 to FIG. 24) may receive Msg4 from the base station based on the Msg3 PUSCH in step S1904.
[0511] For example, the operation of the Redcap terminal receiving Msg4 in step S1904 can be realized by the above-mentioned devices in Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206 to receive Msg4.
[0512] And / or, the Redcap terminal (100 / 200 in FIG. 21 to FIG. 24) can transmit a PUCCH for Msg4 to the base station in step S1905.
[0513] In particular, at least one of the Msg3 PUSCH and / or PUCCH may be transmitted without frequency hopping based on the initial uplink bandwidth being larger than the bandwidth of the Redcap terminal, and / or the initial uplink bandwidth may be the bandwidth of the initial uplink bandwidth part (BWP), and / or the bandwidth of the Redcap terminal may be the maximum bandwidth supported by the Redcap terminal.
[0514] And / or, frequency hopping for PUCCH may be set to "disable". For example, the Redcap terminal may receive information (e.g., higher layer parameter disable-FH-PUCCH) to deactivate or disable frequency hopping for PUCCH via Radio Resource Control (RRC) signaling. For example, the base station may set frequency hopping for PUCCH to "disable" based on the fact that the initial uplink bandwidth is larger than the bandwidth of the Redcap terminal.
[0515] And / or, the optional connection response may include a frequency hopping flag for Msg3 PUSCH (e.g., Table 11). And / or, the frequency hopping flag may be set to "0". For example, the information (or field) and information size included in the optional connection response may be as shown in Table 11. For example, the base station may set the frequency hopping flag for Msg3 PUSCH to "0" based on the fact that the initial uplink bandwidth is larger than the bandwidth of the Redcap terminal.
[0516] And / or, the PUCCH may include hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for Msg4.
[0517] And / or, for the operation of transmitting Msg3 PUSCH, the contents of the second embodiment may be referred to. And / or, for the operation of transmitting PUCCH for Msg4, the contents of the third embodiment may be referred to. That is, for the specific contents of the above-mentioned operations or operations that can be substituted / changed, the contents of the second to third embodiments may be referred to.
[0518] For example, the operation of the Redcap terminal transmitting the PUCCH in step S1905 can be realized by the above-mentioned devices of Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit the PUCCH.
[0519] And / or, for more specific matters regarding any connection procedure / process, reference may be made to the contents described with reference to FIG.
[0520] Although the above-mentioned terminal operation is mainly described in the four-stage RACH operation, the method proposed in this specification can also be applied to the two-stage RACH operation. For example, the method proposed in this specification can also be applied to the PUSCH of MsgA / PUCCH of MsgB. And / or, the contents described with reference to FIG. 11 regarding the two-stage RACH can be referred to.
[0521] The operation of the terminal described with reference to FIG. 19 is similar to the operation of the terminal described with reference to FIGS. 1 to 18 (for example, the first to third embodiments), and therefore other detailed description will be omitted.
[0522] The above signaling and operations may be realized by the apparatuses (e.g., FIGS. 21-24) described below. For example, the above signaling and operations may be processed by one or more processors of FIGS. 21-24, and the above signaling and operations may be stored in a memory in the form of instructions / programs (e.g., instructions, executable codes) for driving at least one processor of FIGS. 21-24.
[0523] For example, a processing apparatus configured to control a Redcap terminal to transmit a PUCCH in a wireless communication system includes at least one processor and at least one memory operably connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, the operations including the steps of transmitting an optional connection preamble to a base station, receiving an optional connection response from the base station based on the optional connection preamble, transmitting an Msg3 PUSCH to the base station based on the optional connection response, receiving an Msg4 from the base station based on the Msg3 PUSCH, and transmitting a PUCCH for the Msg4 to the base station, wherein at least one of the Msg3 PUSCH and / or the PUCCH may be transmitted without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0524] For example, in a computer-readable storage medium storing at least one instruction for causing the at least one processor to control operations based on being executed by the at least one processor, the operations include the steps of transmitting an optional connection preamble to a base station, receiving an optional connection response from the base station based on the optional connection preamble, transmitting an Msg3 PUSCH to the base station based on the optional connection response, receiving an Msg4 from the base station based on the Msg3 PUSCH, and transmitting a PUCCH for Msg4 to the base station. At least one of the Msg3 PUSCH and / or the PUCCH may be transmitted without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of a Redcap terminal.
[0525] FIG. 20 is a flow chart for explaining the operation method of the base station proposed in this specification.
[0526] Referring to FIG. 20, first, a base station (100 / 200 in FIG. 21 to FIG. 24) can receive an optional access preamble from a reduced capability (Redcap) terminal in step S2001. And / or, a Redcap terminal can mean a terminal whose (maximum) bandwidth is smaller than the NR bandwidth (or initial UL BWP). For example, the (maximum) bandwidth of a Redcap terminal can be 20 MHz.
[0527] And / or, in the operation of FIG. 20, the Redcap terminal is replaced with a normal terminal.
[0528] For example, the operation of the base station receiving the optional connection preamble in step S2001 can be realized by the above-mentioned devices of Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the optional connection preamble.
[0529] And / or, the base station (100 / 200 in FIG. 21 to FIG. 24) may transmit an voluntary connection response to the Redcap terminal based on the voluntary connection preamble in step S2002.
[0530] And / or, the unsolicited connection response can be transmitted based on frequency retuning based on the fact that the resource (or RO) for the unsolicited connection response is not included in the bandwidth of the Redcap terminal, i.e., the Redcap terminal can change the position of the starting frequency of the bandwidth of the Redcap terminal so that the resource for the unsolicited connection response is included in the bandwidth.
[0531] And / or, the random access response window (RARwindow) can be set to start Xsymbols or X'us after the RAR window of a normal terminal. For example, X or X' is a transition time (N) defined in a predefined standard (e.g., 3GPP TS 38.211). Rx-Tx Or N Tx-Rx ) and / or a frequency retuning time, and / or X or X' may be a value defined in consideration of the characteristics of a Redcap UE. And / or the start (time) position of the RAR window may be set by system information. That is, X or X' may be a value set by higher layer configuration via system information. For example, a general terminal may refer to a terminal that is not a Redcap terminal.
[0532] For any operation of transmitting a connection response other than and / or, the contents of the first embodiment may be referred to. That is, for specific contents of the above-mentioned operations or operations that can be substituted / changed, the contents of the first embodiment may be referred to.
[0533] For example, the operation of the base station in step S2002 to transmit the optional connection response can be realized by the above-mentioned devices in Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit the optional connection response.
[0534] And / or, the base station (100 / 200 in FIG. 21 to FIG. 24) may receive a message (Msg) 3 physical uplink shared channel (PUSCH) from the Redcap terminal based on the voluntary connection response in step S2003. In this specification, the Msg3 PUSCH may be referred to as Msg3 or PUSCH.
[0535] For example, the operation of the base station receiving the Msg3 PUSCH in step S2003 can be realized by the above-mentioned devices in Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the Msg3 PUSCH.
[0536] And / or, the base station (100 / 200 in FIG. 21 to FIG. 24) can transmit Msg4 to the Redcap terminal based on the Msg3 PUSCH in step S2004.
[0537] For example, the operation of the base station transmitting Msg4 in step S2004 can be realized by the above-mentioned devices in Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit Msg4.
[0538] And / or, the base station (100 / 200 in FIG. 21 to FIG. 24) may receive a PUCCH for Msg4 from the Redcap terminal in step S2005.
[0539] In particular, at least one of the Msg3 PUSCH and / or PUCCH may be received without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal, and / or the initial uplink bandwidth may be the bandwidth of an initial uplink bandwidth portion (BWP), and / or the bandwidth of the Redcap terminal may be the maximum bandwidth supported by the Redcap terminal.
[0540] And / or, frequency hopping for PUCCH may be set to "disable". For example, the Redcap terminal may receive information to deactivate or disable frequency hopping for PUCCH (e.g., higher layer parameter disable-FH-PUCCH) via Radio Resource Control (RRC) signaling. For example, the base station may set frequency hopping for PUCCH to "disable" based on the initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0541] And / or, any connection response may include a frequency hopping flag for Msg3 PUSCH (e.g., Table 11). And / or, the frequency hopping flag may be set to "0". For example, the information (or field) and information size included in any connection response may be as shown in Table 11. For example, the base station may set the frequency hopping flag for Msg3 PUSCH to "0" based on the fact that the initial uplink bandwidth is larger than the bandwidth of the Redcap terminal.
[0542] And / or, the PUCCH may include hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for Msg4.
[0543] And / or, the operation of receiving Msg3 PUSCH may refer to the contents of the second embodiment. And / or, the operation of receiving PUCCH for Msg4 may refer to the contents of the third embodiment. That is, the specific contents of the above-mentioned operations or alternative / changeable operations may refer to the contents of the second to third embodiments.
[0544] For example, the operation of the base station receiving the PUCCH in step S2005 can be realized by the above-mentioned devices in Figures 21 to 24. For example, referring to Figure 22, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the PUCCH.
[0545] And / or, for more specific matters regarding any connection procedure / process, reference may be made to the contents described with reference to FIG.
[0546] Although the above base station operation is mainly described in the four-step RACH operation, the method proposed in this specification can also be applied to the two-step RACH operation. For example, the method proposed in this specification can also be applied to the PUSCH of MsgA / PUCCH of MsgB. And / or, the contents described with reference to FIG. 11 regarding the two-step RACH can be referred to.
[0547] The operation of the base station described with reference to FIG. 20 is similar to the operation of the base station described with reference to FIGS. 1 to 19 (for example, the first to third embodiments), and therefore other detailed descriptions will be omitted.
[0548] The above signaling and operations may be realized by the apparatuses (e.g., FIGS. 21-24) described below. For example, the above signaling and operations may be processed by one or more processors of FIGS. 21-24, and the above signaling and operations may be stored in a memory in the form of instructions / programs (e.g., instructions, executable codes) for driving at least one processor of FIGS. 21-24.
[0549] For example, a processing apparatus configured to control a base station to receive a PUCCH in a wireless communication system includes at least one processor and at least one memory operably connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, the operations including receiving an optional connection preamble from a Redcap terminal, transmitting an optional connection response to the Redcap terminal based on the optional connection preamble, receiving an Msg3 PUSCH from the Redcap terminal based on the optional connection response, transmitting an Msg4 to the Redcap terminal based on the Msg3 PUSCH, and receiving a PUCCH of the Msg4 from the Redcap terminal, wherein at least one of the Msg3 PUSCH and / or the PUCCH can be received without frequency hopping based on an initial uplink bandwidth being larger than a bandwidth of the Redcap terminal.
[0550] For example, in a computer-readable storage medium storing at least one instruction for causing the at least one processor to control operations based on being executed by the at least one processor, the operations include steps of receiving an optional connection preamble from a Redcap terminal, transmitting an optional connection response to the Redcap terminal based on the optional connection preamble, receiving Msg3 from the Redcap terminal based on the optional connection response, transmitting Msg4 to the Redcap terminal based on the Msg3 PUSCH, and receiving a PUCCH of the Msg4 from the Redcap terminal, where at least one of the Msg3 PUCCH and / or the PUCCH can be received without frequency hopping based on an initial uplink bandwidth being larger than the bandwidth of the Redcap terminal.
[0551] An example of a communication system to which the present invention is applied
[0552] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to a variety of fields requiring wireless communication / connection (e.g., 5G) between devices.
[0553] Hereinafter, the present invention will be described in more detail with reference to the drawings. In the following drawings and description, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise stated.
[0554] FIG. 21 illustrates a communication system 1 to which the present invention is applied.
[0555] Referring to FIG. 21, the communication system 1 applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device means a device that communicates using a wireless connection technology (e.g., 5GNR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot 100a, a vehicle 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a handheld device (Hand-held device) 100d, a home appliance 100e, an IoT (Internet of Thing) device 100f, and an AI device / server 400. For example, the vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, and the like. Here, the vehicle may include a UAV (Unmanned Aerial Vehicle) (e.g., a drone). The XR devices include Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) devices, and may be embodied in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. The mobile devices may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a computer (e.g., a laptop, and the like), and the like. The home appliances may include a TV, a refrigerator, a washing machine, and the like. The IoT devices may include a sensor, a smart meter, and the like. For example, a base station and a network may be embodied by a wireless device, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.
[0556] The wireless devices 100a to 100f can be connected to a network 300 via a base station 200. AI (Artificial Intelligence) technology can be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f can be connected to an AI server 400 via a network 3000. The network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, the vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Furthermore, an IoT device (eg, a sensor) can directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.
[0557] Wireless communications / connections 150a, 150b, and 150c can be established between the wireless devices 100a to 100f and the base station 200, and between the base stations 200 and 200. Here, the wireless communication / connection may be performed via various wireless connection technologies (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-base station communication 150c (e.g., relay, IAB (IntegRATed Access Backhaul)). Through the wireless communication / connections 150a, 150b, and 1500c, a wireless device and a base station / wireless device, and a base station and a base station can transmit / receive wireless signals to each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, based on various proposals of the present invention, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.
[0558] Examples of wireless devices to which the present invention can be applied
[0559] FIG. 22 illustrates a wireless device to which the present invention can be applied.
[0560] 22, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {first wireless device 100, second wireless device 200} can correspond to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.
[0561] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be coupled 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 code including instructions for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be mixed with an RF (Radio Frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.
[0562] The second wireless device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 2080. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including a fourth information / signal via the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled 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 code including instructions for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be mixed with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.
[0563] The hardware elements of the wireless device 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be embodied by one or more processors 102, 202. For example, one or more processors 102, 202 may embodi one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP, etc.). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information to the one or more transceivers 106, 206 according to the functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein.
[0564] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be embodied using firmware or software in the form of code, instructions and / or collections of instructions.
[0565] The one or more memories 104, 204 may be coupled to the one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may comprise ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.
[0566] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or operational flowcharts, etc., of this document to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Also, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein, via one or more antennas 108, 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received wireless signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, wireless signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To this end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.
[0567] Examples of wireless device applications to which this invention can be applied
[0568] 23 shows another example of a wireless device to which the present invention is applied. The wireless device may be embodied in various forms depending on the use case / service.
[0569] 23, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 22 and may be configured with various elements, components, units, and / or modules. For example, the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit may include a communication circuit 112 and a transceiver(s) 114. For example, the communication circuit 112 may include one or more processors 102, 202 and / or one or more memories 104, 204 of FIG. 22. For example, the transceiver(s) 114 may include one or more transceivers 106, 206 and / or one or more antennas 108, 208 of FIG. 22. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140, and controls the overall operation of the wireless device. For example, the control unit 120 can control electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. In addition, the control unit 120 can transmit information stored in the memory unit 130 to an outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, or store information received from an outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.
[0570] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Without being limited thereto, the wireless device may be embodied in the form of a robot (FIG. 21, 100a), a vehicle (FIG. 21, 100b-1, 100b-2), an XR device (FIG. 21, 100c), a mobile device (FIG. 21, 100d), a home appliance (FIG. 21, 100e), an IoT device (FIG. 21, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a Fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (FIG. 21, 400), a base station (FIG. 21, 200), a network node, or the like. The wireless device may be mobile or fixed depending on the use case / service.
[0571] In FIG. 23, various elements, components, units / parts, and / or modules in the wireless devices 100 and 200 may be interconnected entirely via a wired interface, or at least some of them may be connected wirelessly via the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected via a wire, and the control unit 120 and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit 110. Also, each element, component, unit / part, and / or module in the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured with one or more processor sets. For example, the control unit 120 may be configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 may be composed of a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.
[0572] Examples of portable devices to which this specification applies
[0573] 24 illustrates a mobile device to which the present invention is applied. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a mobile computer (e.g., a notebook computer, etc.). The mobile device may be referred to as a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless terminal (WT).
[0574] 24, the portable device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input / output unit 140c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 in FIG. 23, respectively.
[0575] The communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) to and from other wireless devices and base stations. The control unit 120 can control components of the portable device 100 to perform various operations. The control unit 120 can include an AP (Application Processor). The memory unit 130 can store data / parameters / programs / codes / commands required for operating the portable device 100. The memory unit 130 can also store input / output data / information, etc. The power supply unit 140a supplies power to the portable device 100 and can include wired / wireless charging circuits, a battery, etc. The interface unit 140b can support connection between the portable device 100 and other external devices. The interface unit 140b can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit 140c can receive or output video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module, etc.
[0576] For example, in the case of data communication, the input / output unit 140c may acquire information / signals (e.g., touch, text, voice, image, video) input by a user, and the acquired information / signals may be stored in the memory unit 130. The communication unit 110 may convert the information / signals stored in the memory into wireless signals, and transmit the converted wireless signals directly to another wireless device or to a base station. In addition, the communication unit 110 may receive wireless signals from another wireless device or a base station, and then restore the received wireless signals to the original information / signals. The restored information / signals may be stored in the memory unit 130 and then output in various forms (e.g., text, voice, image, video, haptic) via the input / output unit 140c.
[0577] The wireless communication technology realized in the wireless device (e.g., 100, 200) of this specification includes not only LTE, NR, and 6G, but also Narrowband Internet of Things for low power communication. At this time, for example, NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology, and is realized in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology realized in the wireless device (e.g., 100, 200) of this specification communicates based on LTE-M technology. At this time, as an example, LTE-M technology is an example of LPWAN technology, and may be called various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology is realized in at least one of various standards such as 1) LTE CAT0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (e.g., 100, 200) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), which consider low power communication, but are not limited to the above names. As an example, ZigBee technology can create personal area networks (PANs) related to small / low power digital communication based on various standards such as IEEE802.15.4, and may be called by various names.
[0578] The above-described embodiments are combinations of the components and features of the present invention in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly specified. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to constitute an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some configurations or features of an embodiment may be included in another embodiment, or may be replaced with corresponding configurations or features of another embodiment. It is obvious that claims that do not have an explicit reference relationship in the claims may be combined to constitute an embodiment, or may be included in a new claim by amendment after filing.
[0579] Embodiments of the present invention may be implemented by various means, such as hardware, firmware, software, or a combination thereof. In a hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.
[0580] In the case of a firmware or software implementation, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above. The software code may be stored in a memory and executed by a processor. The memory may be located inside or outside the processor and may exchange data with the processor by various means known in the art.
[0581] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the essential features of the present invention. Therefore, the above detailed description should not be interpreted as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention.
[0582] [Industrial Applicability] The method of transmitting and receiving PUCCH in the wireless communication system in this specification has been described mainly with reference to examples applied to the 3GPP LTE / LTE-A system and the 5G system (New RAT system), but can also be applied to various other wireless communication systems such as Beyond 5G, 6G, and Beyond 6G.
Claims
1. 1. A method for transmitting a physical uplink control channel (PUCCH) in a wireless communication system, the method being performed by a reduced capability (Redcap) User Equipment (UE), the method comprising: transmitting an optional connection preamble to a base station (BS); receiving an voluntary connection response from the base station based on the voluntary connection preamble; transmitting a physical uplink shared channel (PUSCH) to the base station based on the optional connection response; receiving a physical downlink shared channel (PDSCH) for contention resolution from the base station based on the PUSCH; determining the PUCCH resource based on a resource block (RB) offset based on a frequency hopping (FH) of the PUCCH being disabled, and adding an additional RB offset for PUCCH FH disabled; transmitting the PUCCH, including hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the PDSCH, to the base station on the resource.
2. The initial uplink bandwidth is greater than the bandwidth of the Redcap terminal; The method of claim 1 , wherein the initial uplink bandwidth is a bandwidth of an initial uplink bandwidth part (BWP).
3. The method of claim 2 , wherein the bandwidth of the Redcap terminal is a maximum bandwidth supported by the Redcap terminal.
4. The optional connection response includes a frequency hopping flag for the PUSCH, The method of claim 2 , wherein the frequency hopping flag is set to “0”.
5. The method of claim 2 , wherein the voluntary connection response is received based on frequency retuning based on resources for the voluntary connection response not being included in a bandwidth of the Redcap terminal.
6. The method of claim 5 , wherein the start position of the unsolicited connection response window is set by system information.
7. The method of claim 1 , wherein the RB offset is for a normal UE.
8. In a wireless communication system, a reduced capability (Redcap) terminal (User Equipment (UE)) configured to transmit a physical uplink control channel (PUCCH), comprising: at least one transceiver; at least one processor; at least one memory operatively connected to the at least one processor and storing instructions that perform operations based on being executed by the at least one processor; The operation includes: transmitting an optional connection preamble to a base station (BS); receiving an voluntary connection response from the base station based on the voluntary connection preamble; transmitting a physical uplink shared channel (PUSCH) to the base station based on the optional connection response; receiving a physical downlink shared channel (PDSCH) for contention resolution from the base station based on the PUSCH; determining the PUCCH resource based on a resource block (RB) offset based on a frequency hopping (FH) of the PUCCH being disabled, and adding an additional RB offset for PUCCH FH disabled; transmitting the PUCCH, including hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the PDSCH, to the base station in the resource.
9. 1. A method for receiving a physical uplink control channel (PUCCH) by a base station in a wireless communication system, comprising: receiving an optional connection preamble from a reduced capability (Redcap) User Equipment (UE); sending an voluntary connection response to the Redcap terminal based on the voluntary connection preamble; receiving a physical uplink shared channel (PUSCH) from the Redcap terminal based on the voluntary connection response; transmitting a physical downlink shared channel (PDSCH) for contention resolution to the Redcap terminal based on the PUSCH; Based on the frequency hopping (FH) of the PUCCH being disabled, the PUCCH resource is determined based on adding a resource block (RB) offset and an additional RB offset for PUCCH FH disabled; receiving, from the Redcap terminal, the PUCCH including hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the PDSCH in the resources.
10. The initial uplink bandwidth is greater than the bandwidth of the Redcap terminal; 10. The method of claim 9, wherein the initial uplink bandwidth is a bandwidth of an initial uplink bandwidth part (BWP).
11. The method of claim 10 , wherein the bandwidth of the Redcap terminal is a maximum bandwidth supported by the Redcap terminal.
12. The optional connection response includes a frequency hopping flag for the PUSCH, The method of claim 9 , wherein the frequency hopping flag is set to “0”.
13. The method of claim 10, wherein the voluntary connection response is transmitted based on frequency retuning based on resources for the voluntary connection response not being included in a bandwidth of the Redcap terminal.
14. The method of claim 13, wherein the start position of the unsolicited connection response window is set by system information.
15. The method of claim 9, wherein the RB offset is for a normal UE.
Citation Information
Patent Citations
Method for transmitting or receiving signals for multiple transport block scheduling, and apparatus therefor
WO2020204489A1
