Method and device for processing BWP switching command based on UE type

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a wireless communication system. Specifically, the present disclosure relates to an apparatus and method for processing a BWP handover command based on a UE type.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for processing a BWP switching command based on UE type. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band to realize fast transmission speeds and new services, and can be realized not only in the "below 6 GHz" frequency band such as 3.5 GHz, but also in the "above 6 GHz" frequency band called millimeter wave including 28 GHz and 39 GHz. In addition, the implementation of 6G mobile communication technology (called Beyond 5G system) in the terahertz frequency band (for example, the frequency band of 95 GHz to 3THz) has been considered to realize a transmission speed 50 times faster than that of 5G mobile communication technology and an ultra-low latency of 1 / 10 of that of 5G mobile communication technology.

[0003] In the early stage of the development of 5G mobile communication technology, in order to support services and to meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine type communication (mMTC), standardization has been carried out on beamforming and massive MIMO for alleviating path loss of radio waves and increasing radio wave propagation distance in millimeter waves, dynamic operation of various parameter sets (e.g., operating multiple subcarrier intervals) and time slot formats for effectively utilizing millimeter wave resources, initial access schemes for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding schemes such as LDPC (low-density parity check) codes for large-capacity data transmission and polar codes for reliable transmission of control information, L2 preprocessing, and network slicing for providing a dedicated network dedicated to a specific service.

[0004] Currently, discussions are underway on the improvement and performance enhancement of 5G mobile communication technology in view of the services it supports, and physical layer standardization is underway on technologies such as V2X (Vehicle-to-Everything) which aims to assist driving decisions of autonomous vehicles based on information on the position and status of vehicles transmitted by vehicles and improve user convenience, NR-U (New Unlicensed Radio) which aims to operate systems that comply with various regulatory-related requirements in unlicensed bands, NR UE energy saving, non-terrestrial network (NTN) which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is not available, and positioning.

[0005] In addition, standardization is in progress on air interface architecture / protocols for technologies such as Industrial Internet of Things (IIoT) that supports new services through links and convergence with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying the random access procedure. Standardization is also in progress on system architecture / services for 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on the location of UE.

[0006] When such 5G mobile communication systems are commercialized, an explosively growing number of connected devices will be connected to the communication network; therefore, it is expected that the functions and performance of the 5G mobile communication systems and the integrated operation of the connected devices will need to be enhanced. To this end, new research is being conducted on extended reality (XR) for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., 5G performance improvement and complexity reduction by utilizing AI (artificial intelligence) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such advancements in 5G mobile communication systems will serve as the basis for not only new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, such as full-dimensional MIMO (FD-MIMO), multi-antenna transmission of array antennas or massive antennas, metamaterial lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing using OAM (orbital angular momentum) and RIS (Reconfigurable Smart Surface), but also full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization from the design stage by utilizing satellites and AI (artificial intelligence) and internalizing end-to-end AI support functions, and the development of next-generation distributed computing technology for achieving services at a level of complexity that exceeds the limit of UE operating capabilities by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] The present disclosure proposes an apparatus and method for processing a BWP switching command based on UE type.

[0009] The present disclosure proposes an apparatus and method for starting or restarting a BWP inactivity timer associated with a reduced capability UE.

[0010] The technical subject matter pursued by the present disclosure may not be limited to the above-mentioned technical subject matter, and other technical subject matter not mentioned may be clearly understood by those skilled in the art to which the present disclosure belongs through the following description.

[0011] [Solution to the problem] According to one aspect of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving a first message including configuration information related to at least one bandwidth part from a base station; receiving a second message from the base station, the second message including information indicating an active downlink bandwidth part from the at least one bandwidth part; switching to the active downlink bandwidth part; and starting or restarting a timer associated with bandwidth part inactivity when the terminal is a reduced capability terminal, a default downlink bandwidth part is not configured, an initial downlink bandwidth part for the reduced capability terminal is not configured, and the active downlink bandwidth part is not an initial downlink bandwidth part for a serving cell.

[0012] In an embodiment, the method further includes starting or restarting a timer associated with the inactivity of the bandwidth portion when the terminal is the reduced capability terminal, the default downlink bandwidth portion is not configured, the initial downlink bandwidth portion for the reduced capability terminal is configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion for the reduced capability terminal.

[0013] In an embodiment, the method further comprises starting or restarting a timer associated with the inactivity of the bandwidth portion when the terminal is not the reduced capability terminal, the default downlink bandwidth portion is not configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion and is not indicated by an identifier of a dormant bandwidth portion.

[0014] In an embodiment, the method further comprises starting or restarting a timer associated with inactivity of the bandwidth portion when the default downlink bandwidth portion is configured and the active downlink bandwidth portion is not indicated by an identifier of the default downlink bandwidth portion and is not indicated by an identifier of a dormant bandwidth portion.

[0015] In an embodiment, the first message comprises a Radio Resource Control (RRC) reconfiguration message.

[0016] In an embodiment, the second message comprises downlink control information (DCI).

[0017] According to one aspect of the present disclosure, a method performed by a base station in a wireless communication system is provided. The method includes: sending a first message including configuration information related to at least one bandwidth part to a terminal; sending a second message to the terminal, the second message including information indicating an active downlink bandwidth part from the at least one bandwidth part; and starting or restarting a timer associated with bandwidth part inactivity when the terminal is a reduced capability terminal, a default downlink bandwidth part is not configured, an initial downlink bandwidth part for the reduced capability terminal is not configured, and the active downlink bandwidth part is not an initial downlink bandwidth part for a serving cell.

[0018] In an embodiment, the method further includes starting or restarting a timer associated with the inactivity of the bandwidth portion when the terminal is the reduced capability terminal, the default downlink bandwidth portion is not configured, the initial downlink bandwidth portion for the reduced capability terminal is configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion for the reduced capability terminal.

[0019] In an embodiment, the method further comprises starting or restarting a timer associated with the inactivity of the bandwidth portion when the terminal is not the reduced capability terminal, the default downlink bandwidth portion is not configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion and is not indicated by an identifier of a dormant bandwidth portion.

[0020] In an embodiment, the method further comprises starting or restarting a timer associated with inactivity of the bandwidth portion when the default downlink bandwidth portion is configured and the active downlink bandwidth portion is not indicated by an identifier of the default downlink bandwidth portion and is not indicated by an identifier of a dormant bandwidth portion.

[0021] According to one aspect of the present disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver; and a controller, the controller is coupled to the transceiver and is configured to: receive a first message including configuration information related to at least one bandwidth part from a base station, receive a second message from the base station, the second message including information indicating an active downlink bandwidth part from the at least one bandwidth part, switch to the active downlink bandwidth part, and start or restart a timer associated with bandwidth part inactivity when the terminal is a reduced capability terminal, a default downlink bandwidth part is not configured, an initial downlink bandwidth part for the reduced capability terminal is not configured, and the active downlink bandwidth part is not an initial downlink bandwidth part for a serving cell.

[0022] According to one aspect of the present disclosure, a base station in a wireless communication system is provided. The base station includes a transceiver; and a controller, the controller is coupled to the transceiver and is configured to: send a first message including configuration information related to at least one bandwidth part to a terminal, send a second message including information indicating an active downlink bandwidth part from the at least one frequency band part to the terminal, and start or restart a timer associated with bandwidth part inactivity when the terminal is a reduced capability terminal, a default downlink bandwidth part is not configured, an initial downlink bandwidth part for the reduced capability terminal is not configured, and the active downlink bandwidth part is not an initial downlink bandwidth part for a serving cell.

[0023] [Beneficial effects of the invention] According to an embodiment of the present disclosure, an apparatus and method for processing a BWP switching command based on UE type are proposed.

[0024] According to an embodiment of the present disclosure, an apparatus and method for starting or restarting a BWP inactivity timer associated with a UE with reduced capability are proposed.

[0025] Advantageous effects obtainable by the present disclosure may not be limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those skilled in the art to which the present disclosure belongs through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 is an example showing the start or restart of the BWP inactivity timer according to the method of the present disclosure.

[0027] Figure 2 is a diagram showing a configuration of a terminal according to the present disclosure.

[0028] Figure 3 is a diagram showing a configuration of a base station according to the present disclosure. DETAILED DESCRIPTION

[0029] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are to be considered as examples only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications of the various embodiments described herein may be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

[0030] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are only used to enable people to clearly and consistently understand the present disclosure. Therefore, it should be understood by those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and is not intended to limit the disclosure defined by the attached claims and their equivalents.

[0031] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0032] The term "substantially" means that the features, parameters or values ​​described need not be achieved exactly, but deviations or changes, including, for example, tolerances, measurement errors, measurement precision limitations and other factors known to those skilled in the art, may occur in amounts that do not negate the effect that the features are intended to provide.

[0033] As known to those skilled in the art, the blocks of a flowchart (or sequence diagram) and the combination of flowcharts can be represented and executed by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the processor executes the loaded program instructions, they create a method for performing the functions described in the flowchart. Because the computer program instructions can be stored in a computer-readable memory available in a special-purpose computer or a programmable data processing device, an article of manufacture that performs the functions described in the flowchart can also be created. Because the computer program instructions can be loaded onto a computer or a programmable data processing device, when executed as a process, they can perform the operation of the functions described in the flowchart.

[0034] The blocks of the flowchart may correspond to a module, segment or code containing one or more executable instructions that implement one or more logical functions, or may correspond to a portion thereof. In some cases, the functions described by the blocks may be performed in a different order than listed. For example, two blocks listed in order may be executed simultaneously or in reverse order.

[0035] In this specification, the words "unit", "module", etc. may refer to software components or hardware components, such as field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs) that can perform functions or operations. However, "units", etc. are not limited to hardware or software. Units, etc. may be configured to reside in an addressable storage medium or drive one or more processors. Units, etc. may also refer to software components, object-oriented software components, class components, task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by components and units may be combinations of smaller components and units, or may be combined with other components and units to form larger components and units. Components and units may be configured to drive devices or one or more processors in a secure multimedia card.

[0036] Prior to the detailed description, terms or definitions necessary for understanding the present disclosure are described. However, these terms should be interpreted in a non-limiting manner.

[0037] A "base station (BS)" is an entity that communicates with a user equipment (UE) and may be referred to as a BS, base transceiver station (BTS), radio access network (RAN), Node B (NB), evolved NB (eNB), access point (AP), fifth generation (5G) NB (5GNB), or next generation NB (gNB).

[0038] A "user equipment (UE)" is an entity that communicates with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.

[0039] In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband users and to provide more and better applications and services. The second generation of wireless communication systems has been developed to provide voice services while ensuring user mobility. The third generation of wireless communication systems supports not only voice services but also data services. In recent years, the fourth generation of wireless communication systems has been developed to provide high-speed data services. However, currently, the fourth generation of wireless communication systems suffers from a lack of resources to meet the growing demand for high-speed data services. Therefore, the fifth generation of wireless communication systems (also known as next generation radio or NR) are being developed to meet the growing demand for high-speed data services and support ultra-reliability and low-latency applications.

[0040] The fifth generation wireless communication system supports not only lower frequency bands but also higher frequency (millimeter wave) bands, such as 10 GHz to 100 GHz bands, in order to achieve higher data rates. In order to mitigate the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming and / or massive antenna technology are being considered in the design of the fifth generation wireless communication system. In addition, the fifth generation wireless communication system is expected to address different use cases with very different requirements in terms of data rate, latency, reliability, mobility, etc. However, it is expected that the design of the air interface of the fifth generation wireless communication system will be flexible enough to serve UEs with very different capabilities depending on the use cases and market segments that the UE serves for the end customers. Several example use cases that the fifth generation wireless communication system is expected to address are enhanced mobile broadband (eMBB), massive machine type communication (m-MTC), ultra-reliable low latency communication (URLL), etc. The requirements of eMBB, such as data rates of tens of Gbps, low latency, high mobility, etc., address the market segments that represent traditional wireless broadband users who need Internet connectivity anytime, anywhere. m-MTC requirements, such as very high connection density, infrequent data transfer, very long battery life, low mobility addresses the market segment representing the connectivity of billions of devices envisioned by the Internet of Things (IoT) / Internet of Everything (IoE). URLL requirements, such as very low latency, very high reliability, and variable mobility, target the market segment representing industrial automation applications, vehicle-to-vehicle / vehicle-to-infrastructure communications, which are seen as one of the enablers of autonomous vehicles.

[0041] In the fifth generation wireless communication system operating in the high frequency (mmWave) band, UE and gNB communicate with each other using beamforming. Beamforming technology is used to mitigate propagation path loss and increase the propagation distance for communication in higher frequency bands. Beamforming improves transmission and reception performance using high gain antennas. Beamforming can be divided into transmit (TX) beamforming performed at the transmitting end and receive (RX) beamforming performed at the receiving end. In general, TX beamforming increases directivity by allowing the area reached by propagation to be densely positioned in a specific direction by using multiple antennas. In this case, the aggregation of multiple antennas can be referred to as an antenna array, and each antenna included in the antenna array can be referred to as an array element. The antenna array can be configured in various forms, such as a linear array, a planar array, etc. The use of TX beamforming leads to an increase in signal directivity, thereby increasing the propagation distance. In addition, since the signal is hardly transmitted in a direction other than the directivity direction, the signal interference acting on another receiving end is significantly reduced. The receiving end can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the strength of RX signals transmitted in a specific direction by allowing propagation to be concentrated in a specific direction, and excludes signals transmitted in directions other than the specific direction from the RX signal, thereby providing the effect of blocking interference signals. By using beamforming technology, the transmitter can generate multiple transmit beam patterns in different directions. Each of these transmit beam patterns can also be referred to as a transmit (TX) beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals in a cell because each narrow TX beam provides coverage for a portion of the cell. The narrower the TX beam, the higher the antenna gain, and therefore the greater the propagation distance of the signal transmitted using beamforming. The receiver can also generate multiple receive (RX) beam patterns in different directions. Each of these receive patterns can also be referred to as a receive (RX) beam.

[0042] CA (Carrier Aggregation) / Multiple Connections in the Fifth Generation Wireless Communication System: The fifth generation wireless communication system supports independent operation mode as well as dual connectivity (DC). In DC, a multi-Rx / Tx UE can be configured to utilize resources provided by two different nodes (or NBs) connected through a non-ideal backhaul. One node acts as a master node (MN) and the other acts as a secondary node (SN). The MN and the SN are connected through a network interface, and at least the MN is connected to the core network. NR also supports multi-RAT dual connectivity (MR-DC) operation, in which a UE in RRC_CONNECTED (connected radio resource control) is configured to utilize radio resources provided by two different schedulers, which are located in two different nodes connected through a non-ideal backhaul and provide E-UTRA (ie, if the node is an ng-eNB) or NR access (ie, if the node is a gNB). In NR of a UE that is not configured with CA / DC in RRC_CONNECTED, only one serving cell consists of a primary cell. For UEs in RRC_CONNECTED configured with CA / DC, the term "serving cell" is used to refer to the set of cells consisting of a special cell (SpCell) and all secondary cells (SCells). In NR, the term master cell group (MCG) refers to a set of serving cells associated with a primary node, including a PCell (primary cell) and optionally one or more SCells. In NR, the term secondary cell group (SCG) refers to a set of serving cells associated with a secondary node, including a PSCell (primary SCG cell) and optionally one or more SCells. In NR, a PCell (primary cell) refers to a serving cell operating on the primary frequency in an MCG, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In NR for UEs configured with CA, an Scell ​​is a cell that provides additional radio resources on top of a special cell. A primary SCG cell (PSCell) refers to a serving cell in an SCG, where the UE performs random access when performing a synchronization reconfiguration procedure. For dual connectivity operation, the term SpCell (ie, special cell) refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term special cell refers to the PCell.

[0043] UE states in fifth-generation wireless communication systems: In fifth-generation wireless communication systems, RRC can be in one of the following states: RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED. When an RRC connection has been established, the UE is in the RRC_CONNECTED state or the RRC_INACTIVE state. If this is not the case, that is, no RRC connection has been established, the UE is in the RRC_IDLE state. The RRC (Radio Resource Control) state can also be further characterized as follows: In RRC_IDLE, UE-specific DRX (discontinuous reception) can be configured by upper layers. The UE monitors short messages transmitted via DCI (downlink control information) with P-RNTI (paging RNTI (radio network temporary identity)); monitors the paging channel for CN (core network) paging using 5G-S-TMSI (5G-S-temporary mobile group identity); performs neighbor cell measurements and cell (re)selection; obtains system information and can transmit SI (system information) requests (if configured); performs logging of available measurements and the logged measurements configured UE location and time.

[0044] In RRC_INACTIVE, UE-specific DRX may be configured by upper layers or the RRC layer; the UE stores the UE inactive AS (access stratum) context; the RAN-based notification area is configured by the RRC layer. The UE monitors short messages transmitted via DCI with the P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI and RAN paging using the full-I RNTI; performs neighbor cell measurements and cell (re)selection; performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; obtains system information and may transmit an SI request (if configured); performs logging of available measurements and the logged measurements configured at the UE's location and time.

[0045] In RRC_CONNECTED, the UE stores the AS context and performs unicast data transmission to or from the UE. If configured, the UE monitors short messages transmitted using P-RNTI on the DCI; monitors the control channel associated with the shared data channel to determine whether data is scheduled for the control channel; provides channel quality and feedback information; performs neighbor cell measurements and measurement reports; and obtains system information.

[0046] Downlink control in fifth-generation wireless communication systems: In fifth-generation wireless communication systems, the physical downlink control channel (PDCCH) is used to schedule DL (downlink) transmission on PDSCH (physical downlink shared channel) and UL (uplink) transmission on PUSCH (physical uplink shared channel), where the downlink control information (DCI) on the PDCCH includes: downlink allocation including at least modulation and coding format, resource allocation, and hybrid ARQ information related to DL-SCH; uplink scheduling grant including at least modulation and coding format, resource allocation, and hybrid ARQ (hybrid automatic repeat request) information related to UL-SCH (downlink shared channel). In addition to scheduling, PDCCH can also be used for: Activation and deactivation of configured PUSCH transmissions with configured grants; Activation and deactivation of PDSCH semi-persistent transmissions; Notification of one or more UEs of the slot format; Notification of one or more UEs of PRBs and OFDM symbols in which the UE can assume that no transmission is intended for the UE; Transmission of TPC (Transmit Power Control) commands for PUCCH and PUSCH; Transmission of one or more TPC commands for SRS (Sounding Reference Signal) transmission by one or more UEs; Switching of the active bandwidth portion of the UE; Initiation of a random access procedure. The UE monitors a set of PDCCH candidates in the monitoring opportunities configured in one or more configured control resource sets (CORESETs) according to the corresponding search space configuration. A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource units Resource element groups (REGs) and control channel elements (CCEs) are defined within a CORESET, and each CCE consists of a set of REGs. The control channel is formed by the aggregation of CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. CORESET supports interleaved and non-interleaved CCE to REG mapping. Polar coding is used for PDCCH. Each resource element group carrying PDCCH carries its own DMRS. QPSK modulation is used for PDCCH.

[0047] In the fifth generation wireless communication system, a list of search space configurations is signaled by the gNB for each configured BWP (bandwidth part), where each search configuration is uniquely identified by an identity. The gNB explicitly signals the identity of the search space configuration to be used for a specific purpose (such as paging reception, SI reception, random access response reception). In NR, the search space configuration includes the parameters monitoring periodicity PDCCH slot, monitoring offset PDCCH slot, monitoring symbol PDCCH within the slot, and duration. The UE uses the parameters PDCCH monitoring period (monitoring periodicity PDCCH slot), PDCCH monitoring offset (monitoring offset PDCCH slot), and PDCCH monitoring mode (monitoring symbol PDCCH within the slot) to determine the PDCCH monitoring opportunity within the slot. The PDCCH monitoring opportunity exists in slots x to x + duration, where the slot numbered x in the radio frame numbered y satisfies the following equation:

[0048] The start symbol of the PDCCH monitoring opportunity in each slot with a PDCCH monitoring opportunity is given by the monitoring symbol PDCCH within the slot. The length of the PDCCH monitoring opportunity (in symbols) is given in the CORESET associated with the search space. The search space configuration includes the identity of the CORESET configuration associated with the search space configuration. A list of CORESET configurations is signaled by the gNB for each configured BWP, where each CORESET configuration is uniquely identified by the identity. Note that the duration of each radio frame is 10ms. A radio frame is identified by a radio frame number or a system frame number. Each radio frame comprises several slots, where the number of slots in a radio frame and the slot duration depends on the subcarrier spacing. The number of slots in a radio frame and the slot duration depends on the radio frame for each supported SCS (subcarrier spacing) predefined in the NR. Each CORESET configuration is associated with a list of TCI (Transmission Configuration Indicator) states. One DLRS ID (SSB (Synchronization Signal) or CSI RS (Channel State Information Reference Signal)) is configured for each TCI state. The gNB signals the TCI state list corresponding to the CORESET configuration through RRC signaling. One of the TCI states in the TCI state list is activated and indicated to the UE by the gNB. The TCI state represents the DL TX beam used for transmission of PDCCH by the gNB in ​​the PDCCH monitoring occasion of the search space (the DL TX beam is the SSB / CSI RSQCLed with TCI state).

[0049] Bandwidth Parts in Fifth Generation Wireless Communication Systems: In fifth generation wireless communication systems, bandwidth adaptation (BA) is supported. With BA, the receive and transmit bandwidth of the UE does not need to be as large as the bandwidth of the cell and can be adjusted: the width can be commanded to change (e.g., shrink during low activity to save power); the location can be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the total cell bandwidth of a cell is called a bandwidth part (BWP). BA is implemented by configuring an RRC-connected UE with a BWP and telling the UE which of the configured BWPs is currently the active BWP. When BA is configured, the UE only needs to monitor the PDCCH on one active BWP, i.e., it does not have to monitor the PDCCH on the entire DL frequency of the serving cell. In the RRC connected state, the UE is configured with one or more DL and UL BWPs for each configured serving cell (i.e., PCell or SCell). For an activated serving cell, there is one active UL and DL BWP at any point in time. BWP switching of a serving cell is used to activate an inactive BWP and deactivate an active BWP at one time. BWP switching is determined by the PDCCH (DCI) indicating downlink allocation or uplink grant, the BWP inactivity timer ( bwp-InactivityTimer ), RRC signaling or the MAC entity itself when the random access process starts. When adding a SpCell or activating an SCell, the first active downlink BWP Id ( firstActiveDownlinkBWP-Id ) and the first active uplink BWP Id ( firstActiveUplinkBWP-Id ) are active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP for the serving cell is indicated by either RRC or PDCCH. For non-paired spectrum, the DL BWP is paired with the UL BWP and BWP switching is common for both UL and DL. On expiration of the BWP inactivity timer, the UE switches the active DL BWP to the default DL BWP or the initial DL BWP (if no default DL BWP is configured). In RRC_IDLE and RRC_INACTIVE states, the UE receives downlink transmissions from the gNB in ​​the initial DL BWP and the UE sends uplink transmissions in the initial UL BWP. The initial DL BWP configuration is determined by the field Initial Downlink BWP ( initialDownlinkBWP ) is signaled. The initial UL BWP configuration is signaled by the field Initial Uplink BWP ( initialUplinkBWP ) sends a signal.

[0050] Random access in the fifth generation wireless communication system: In the 5G wireless communication system, random access (RA) is supported. Random access (RA) is used to achieve uplink (UL) time synchronization. RA is used for initial access, handover, radio resource control (RRC) connection reestablishment process, scheduling request transmission, secondary cell group (SCG) addition / modification, beam failure recovery, and during data or control information transmission in the UL by an unsynchronized UE in the RRC CONNECTED state. Several types of random access procedures are supported.

[0051] Contention-based random access (CBRA): Also known as 4-step CBRA. In this type of random access, the UE first sends a random access preamble (also known as Msg1) and then waits for a random access response (RAR) in the RAR window. The RAR is also known as Msg2. The next generation Node B (gNB) sends the RAR on the physical downlink shared channel (PDSCH). The PDCCH that schedules the PDSCH carrying the RAR is sent with the RA Radio Network Temporary Identity (RA-RNTI). The RA-RNTI identifies the time-frequency resources (also known as physical RA channel (PRACH) opportunity or PRACH transmission (TX) opportunity or RA channel (RACH) opportunity) in which the RA preamble is detected by the gNB. The calculation of the RA-RNTI is as follows:

[0052] Where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol in which the UE has transmitted the PRACH opportunity of Msg1, i.e., the RA preamble; 0≤s_id<14; t_id is the index of the first slot of the PRACH opportunity (0≤t_id<80); f_id is the index of the PRACH opportunity within the slot in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for the normal UL (NUL) carrier and 1 for the supplementary UL (SUL) carrier). Multiple RARs detected by the gNB for various random access preambles may be multiplexed in the same RAR media access control (MAC) protocol data unit (PDU) by the gNB. If the RAR includes the RA preamble identity (RAPID) of the RA preamble sent by the UE, the RAR in the MAC PDU corresponds to the RA preamble transmission of the UE. If a RAR corresponding to a UE's RA preamble transmission is not received during the RAR window and the UE has not sent a RA preamble for a configurable (configured by the gNB in ​​the RACH configuration) number of times, the UE returns to the first step, i.e. selecting a random access resource (preamble / RACH opportunity) and sending a RA preamble. A backoff may be applied before returning to the first step.

[0053] If a RAR corresponding to the UE's RA preamble transmission is received, the UE sends a message 3 (Msg3) in the UL grant received in the RAR. Msg3 includes messages such as RRC connection request, RRC connection reestablishment request, RRC handover confirmation, scheduling request, SI request, etc. It may include a UE identity (i.e., a cell radio network temporary identity (C-RNTI) or a system architecture evolution (SAE) temporary mobile user identity (S-TMSI) or a random number). After sending Msg3, the UE starts a contention resolution timer. When the contention resolution timer is running, if the UE receives a physical downlink control channel (PDCCH) sent to the C-RNTI included in Msg3, the contention resolution is considered to be successful, the contention resolution timer is stopped, and the RA procedure is completed. When the contention resolution timer is running, if the UE receives a contention resolution MAC control element (CE) including the UE's contention resolution identity (the first X bits of the common control channel (CCCH) service data unit (SDU) sent in Msg3), the contention resolution is considered to be successful, the contention resolution timer is stopped, and the RA procedure is completed. If the contention resolution timer expires and the UE has not sent a RA preamble for a configurable number of times, the UE returns to the first step, i.e. selecting random access resources (preamble / RACH opportunity) and sending a RA preamble. Before returning to the first step, a backoff may be applied.

[0054] Non-Contentious Random Access (CFRA): This is also known as legacy CFRA or 4-step CFRA. The CFRA procedure is used for scenarios such as handovers that require low latency, timing advance establishment of secondary cells (SCells), etc. The evolved Node B (eNB) allocates a dedicated random access preamble to the UE. The UE sends a dedicated RA preamble. The eNB sends a RAR on the PDSCH sent to the RA-RNTI. The RAR conveys the RA preamble identity and timing alignment information. The RAR may also include a UL grant. The RAR is sent in a RAR window similar to the contention-based RA (CBRA) procedure. The CFRA is considered to have been successfully completed upon receipt of the RAR including the RA preamble identity (RAPID) of the RA preamble sent by the UE. In case RA is initiated for beam failure recovery, the CFRA is considered to have been successfully completed if the PDCCH sent to the C-RNTI is received in the search space for beam failure recovery. If the RAR window expires and the RA is not completed successfully, and the UE has not sent the RA preamble for a configurable (configured by the gNB in ​​the RACH configuration) number of times, the UE resends the RA preamble.

[0055] For certain events such as handover and beam failure recovery, if a dedicated preamble is allocated to the UE during the first step of random access, i.e., during random access resource selection for Msg1 transmission, the UE determines whether to send a dedicated preamble or a non-dedicated preamble. Dedicated preambles are usually provided for a subset of SSB / CSI-RS. If there is no SSB / CSI RS with DL RSRP (reference signal received power) higher than a threshold among the SSB / CSI RS provided by the gNB for non-contention random access resources (i.e., dedicated preamble / RO), the UE selects the non-dedicated preamble. Otherwise, the UE selects the dedicated preamble. Therefore, during the RA procedure, one random access attempt can be CFRA, while the other random access attempt can be CBRA.

[0056] 2-step Contention-Based Random Access (2-step CBRA): In the first step, the UE transmits a random access preamble on PRACH and a payload (i.e., MAC PDU) on PUSCH. The random access preamble and payload transmission is also referred to as MsgA. In the second step, after the MsgA transmission, the UE monitors for a response from the network (i.e., gNB) within a configured window. The response is also referred to as MsgB. The next generation Node B (gNB) transmits MsgB on the Physical Downlink Shared Channel (PDSCH). The PDCCH scheduling the PDSCH carrying MsgB is sent with the MsgB Radio Network Temporary Identity (MSGB-RNTI). The MSGB-RNTI identifies the time-frequency resource (also referred to as Physical RA Channel (PRACH) opportunity or PRACH Transmission (TX) opportunity or RA Channel (RACH) opportunity) at which the gNB detects the RA preamble. The MSGB-RNTI is calculated as follows:

[0057] Where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH opportunity in which the UE has transmitted Msg1, i.e., the RA preamble; 0≤s_id<14; t_id is the index of the first time slot of the PRACH opportunity (0≤t_id<80); f_id is the index of the PRACH opportunity within the time slot in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for the normal UL (NUL) carrier and 1 for the supplementary UL (SUL) carrier).

[0058] If the CCCH SDU is transmitted in the MsgA payload, the UE performs contention resolution using the contention resolution information in MsgB. If the contention resolution identifier received in MsgB matches the first 48 bits of the CCCH (Common Control Channel) SDU (Service Data Unit) transmitted in MsgA, contention resolution is successful. If the C-RNTI is transmitted in the MsgA payload, contention resolution is successful if the UE receives a PDCCH sent to the C-RNTI. If contention resolution is successful, the random access procedure is considered to have been successfully completed. MsgB may include backoff information corresponding to the random access preamble transmitted in MsgA instead of the contention resolution information corresponding to the transmitted MsgA. If the backoff information is received, the UE sends Msg3 and performs contention resolution using Msg4 as in the CBRA procedure. If contention resolution is successful, the random access procedure is considered to have been successfully completed. If contention resolution fails at the time of backoff (i.e., when sending Msg3), the UE resends MsgA. If the configured window in which the UE monitors the network response after sending MsgA expires, and the UE does not receive MsgB including contention resolution information or backoff information as described above, the UE resends MsgA. If the random access procedure is not successfully completed even after sending MsgA a configurable number of times, the UE falls back to the 4-step RACH procedure, i.e., the UE only sends the PRACH preamble.

[0059] The MsgA payload may include one or more of a common control channel (CCCH) service data unit (SDU), a dedicated control channel (DCCH) SDU, a dedicated traffic channel (DTCH) SDU, a buffer status report (BSR) MAC control element (CE), a power headroom report (PHR) MAC CE, SSB information, a C-RNTI MAC CE, or padding. In the first step, MsgA may include a UE ID (e.g., a random ID, S-TMSI, C-RNTI, recovery ID, etc.) and a preamble. The UE ID may be included in the MAC PDU of MsgA. The UE ID (such as C-RNTI) may be carried in a MAC CE, where the MAC CE is included in the MAC PDU. Other UE IDs (such as random ID, S-TMSI, C-RNTI, recovery ID, etc.) may be carried in a CCCH SDU. The UE ID may be one of a random ID, S-TMSI, C-RNTI, recovery ID, IMSI (International Mobile Subscriber Identity), an idle mode ID, an inactive mode ID, etc. The UE ID may be different in different scenarios in which the UE performs the RA process. When the UE performs RA after power-on (before connecting to the network), the UE ID is a random ID. When the UE performs RA in the IDLE state after it is connected to the network, the UE ID is the S-TMSI. If the UE has an assigned C-RNTI (for example, in a connected state), the UE ID is the C-RNTI. In the case where the UE is in an inactive state, the UE ID is a recovery ID. In addition to the UE ID, some additional control information may also be transmitted in the MsgA. The control information may be included in the MAC PDU of the MsgA. The control information may include a connection request indication, a connection recovery request indication, an SI request indication, a buffer status indication, beam information (for example, one or more DL TX beam IDs or SSB IDs), a beam failure recovery indication / information, a data indicator, a cell / BS / TRP (transmit / receive point) switching indication, a connection reconstruction indication, a reconfiguration completion or a switching completion message, etc. One or more.

[0060] 2-step non-contention random access (2-step CFRA): In this case, the gNB allocates dedicated random access preamble and PUSCH resources to the UE for MsgA transmission. It can also indicate the RO that will be used for preamble transmission. In the first step, the UE transmits the random access preamble on PRACH and the payload on PUSCH using non-contention random access resources (i.e. dedicated preamble / PUSCH resources / RO). In the second step, after MsgA transmission, the UE monitors the response from the network (i.e. gNB) within the configured window. The response is also called MsgB.

[0061] The next generation Node B (gNB) transmits MsgB on the physical downlink shared channel (PDSCH). The PDCCH that schedules the PDSCH carrying MsgB is sent to the MsgB Radio Network Temporary Identity (MSGB-RNTI). The MSGB-RNTI identifies the time-frequency resource (also called physical RA channel (PRACH) opportunity or PRACH transmission (TX) opportunity or RA channel (RACH) opportunity) where the gNB detects the RA preamble. The MSGB-RNTI is calculated as follows:

[0062] Where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH opportunity for the UE to transmit Msg1, i.e., the RA preamble; 0≤s_id<14; t_id is the index of the first time slot of the PRACH opportunity (0≤t_id<80); f_id is the index of the PRACH opportunity within the time slot in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for the normal UL (NUL) carrier, and 1 for the supplementary UL (SUL) carrier).

[0063] If the UE receives the PDCCH sent to the C-RNTI, the random access procedure is considered to have been successfully completed. If the UE receives the backoff information corresponding to the preamble it transmitted, the random access procedure is considered to have been successfully completed.

[0064] For certain events such as handover and beam failure recovery, if a dedicated preamble and PUSCH resources are allocated to the UE during the first step of random access, i.e., during random access resource selection for MsgA transmission, the UE determines whether to send a dedicated preamble or a non-dedicated preamble. Dedicated preambles are usually provided for a subset of SSB / CSI-RS. If there is no SSB / CSI RS with DL RSRP above a threshold among the SSB / CSI-RS for which non-contention random access resources (i.e., dedicated preamble / RO / PUSCH resources) are provided by the gNB, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, in the RA procedure, one random access attempt can be a 2-step CFRA, while the other random access attempts can be a 2-step CBRA.

[0065] After initiating the random access procedure, the UE first selects a carrier (SUL or NUL). If the carrier for the random access procedure is explicitly signaled by the gNB, the UE selects the signaled carrier to perform the random access procedure. If the gNB does not explicitly signal the carrier for the random access procedure; and if the serving cell for the random access procedure is configured with supplementary uplink, and if the RSRP of the downlink path loss reference is less than the RSRP threshold SSB SUL ( rsrp-ThresholdSSB-SUL ): The UE selects the SUL carrier to perform the random access procedure. Otherwise, the UE selects the NUL carrier to perform the random access procedure. After selecting the UL carrier, the UE determines the UL and DL BWP for the random access procedure as specified in Section 5.15 of TS 38.321. The UE then determines whether to perform a 2-step RACH or a 4-step RACH for the random access procedure.

[0066] - If this random access procedure is initiated by a PDCCH order and if the RA-preamble index explicitly provided by the PDCCH is not 0b000000, the UE selects 4-step RACH.

[0067] - Otherwise, if 2-step non-contention random access resources are signaled by the gNB for this random access procedure, the UE selects 2-step RACH.

[0068] - Otherwise, if 4-step non-contention random access resources are signaled by the gNB for this random access procedure, the UE selects 4-step RACH.

[0069] - Otherwise, if the UL BWP selected for this random access procedure is configured with only 2-step RACH resources, the UE selects 2-step RACH.

[0070] - Otherwise, if the UL BWP selected for this random access procedure is configured with only 4-step RACH resources, the UE selects 4-step RACH.

[0071] - Otherwise, if the UL BWP selected for this random access procedure is configured with 2-step and 4-step RACH resources, - If the downlink path loss referenced RSRP is below the configured threshold, the UE selects 4-step RACH. Otherwise, the UE selects 2-step RACH.

[0072] In the current design, the gNB may send a PDCCH for BWP switching to the UE. If a PDCCH for BWP switching is received and the MAC entity (of the UE) switches the active DL BWP to the DL BWP indicated by the PDCCH, the UE / MAC entity in the UE performs the following operations: - If a default downlink BWP Id is configured ( defaultDownlinkBWP-Id ), and the MAC entity / UE switches to the default downlink BWP Id ( defaultDownlinkBWP-Id ) is not indicated and if the configured dormant BWP Id ( dormantBWP-Id ) nor DL ​​BWP indicated: ○ Start or restart the BWP inactivity timer associated with the active DL BWP ( bwp- InactivityTimer ).

[0073] - If no default downlink BWP Id is configured ( defaultDownlinkBWP-Id ), and the MAC entity switches to a DL BWP that is not the initial downlink BWP ( initialDownlinkBWP ) and is not configured by the dormant BWP Id ( dormantBWP-Id )instruct: ○ Start or restart the BWP inactivity timer associated with the active DL BWP ( bwp-InactivityTimer ).

[0074] One or more DL BWPs are configured by the gNB in ​​the RRCReconfiguration message. Each of these configured DL BWPs has a BWP ID. The gNB can configure the default downlink BWP-Id ( defaultDownlinkBWP-Id ) to indicate which of these configured DL BWPs is the default DLBWP. Parameter Default Downlink BWP-Id ( defaultDownlinkBWP-Id ) is set to the BWP ID of the DLBWP that is the default DL BWP. Similarly, the gNB can sleep BWP-Id by signaling parameter ( dormantBWP-Id ) to indicate which of these configured DL BWPs is the dormant DL BWP. Parameter dormantBWP-Id ( dormantBWP-Id ) is set to the BWP ID of the DL BWP that is the dormant DLBWP. If the active DL BWP is the dormant DL BWP, the UE stops monitoring PDCCH and transmitting SRS / PUSCH / PUCCH, but continues to perform CSI measurements, AGC (Automatic Gain Control) and beam management (if configured). Note that the dormant BWP-Id ( dormantBWP-Id ) can be configured for a secondary cell (SCell) instead of for a SpCell (ie, PCell or PSCell).

[0075] In the current design, an initial uplink BWP is configured in the cell (by the initial uplink BWP ( initialUplinkBWP) and an initial downlink BWP (indicated by the initial downlink BWP ( initialDownlinkBWP ) indication). To support reduced capability UEs (RedCap UEs), an additional initial uplink BWP (indicated by Initial Uplink BWP-RedCap ( initialUplinkBWP-RedCap ) indicates), and an additional downlink BWP can be configured on the downlink carrier of the serving cell (indicated by the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap )instruct).

[0076] In case no default downlink BWP-Id is configured by the gNB ( defaultDownlinkBWP-Id ) and the initial downlink BWP-RedCap is configured ( initialDownlinkBWP-RedCap ), according to the current specification, upon receiving the BWP switch to the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ) when the UE unnecessarily starts or restarts the BWP inactivity timer ( bwp-InactivityTimer This may further cause the BMP inactivity timer ( bwp-InactivityTimer ) when it expires, switching to the initial downlink BWP ( initialDownlinkBWP ). When the initial downlink BWP-RedCap is configured ( initialDownlinkBWP- RedCap ), the RedCap UE should not further switch to the initial downlink BWP ( initialDownlinkBWP ), because the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ) has been optimized for RedCap UE.

[0077] RedCap UE is a UE with the following reduced capabilities: - For FR1 (frequency range 1), the maximum bandwidth is 20 MHz, and for FR2, the maximum bandwidth is 100 MHz. UE features and corresponding capabilities related to UE bandwidth wider than 20 MHz in FR1 or wider than 100 MHz in FR2 are not supported by RedCapUE; - The maximum mandatory supported number of DRBs (Data Radio Bearers) is 8; - The mandatory supported PDCP (Packet Data Convergence Protocol) SN (Sequence Number) length is 12 bits, while 18 bits is optional; - The mandatory supported RLC (Radio Link Control) AM (Acknowledged Mode) SN length is 12 bits, while 18 bits is optional; - For FR1, if 1 Rx branch is supported, it is 1 DL MIMO layer, and if 2 Rx branches are supported, it is 2 DL MIMO layers; for FR2, 1 or 2 DL MIMO layers can be supported, while 2 Rx branches are always supported. For FR1 and FR2, UE features and corresponding capabilities related to more than 2 UE Rx branches or more than 2 DL MIMO layers, and UE features or capabilities related to more than 2 UE TX branches or more than 2 UL MIMO layers are not supported by RedCap UE; - CA (Carrier Aggregation), MR-DC (Multi-Radio Dual Connectivity), DAPS (Dual Active Protocol Stack), CPAC (Conditional PSCell Addition / Change) and IAB (Integrated Access Backhaul) related UE features and corresponding capabilities are not supported by RedCap UE.

[0078] RedCap UE transmits parameters in UE Capability Information message to gNB in ​​RRC_CONNECTED state supportOfRedCap-r17 , so that the gNB can know whether the UE is a RedCap UE. supportOfRedCap-r17 Indicates that the UE is a RedCap UE consisting of at least the following functional components: - Maximum FR1 RedCap UE bandwidth is 20 MHz; - Maximum FR2 RedCap UE bandwidth is 100 MHz; - Support of RedCap early indication based on Msg1, MsgA and Msg3 for random access; - Separate initial UL BWP for RedCap UE; - Separate initial DL BWP for RedCap UEs.

[0079] The UE is in RRC_CONNECTED. The UE receives an RRC reconfiguration message from the gNB. The RRC reconfiguration message includes configuring one or more dedicated DL BWPs and one or more dedicated UL BWPs for each serving cell. The gNB may configure the default downlink BWP-Id ( defaultDownlinkBWP-Id ) to indicate which of these configured DL BWPs is the default DL BWP. Parameter Default Downlink BWP-Id ( defaultDownlinkBWP-Id ) is set to the BWP ID of the DL BWP that is the default DL BWP. Similarly, the gNB can sleep BWP-Id by signaling parameter ( dormantBWP-Id) to indicate which of these configured DL BWPs is the dormant DL BWP. Parameter dormantBWP-Id ( dormantBWP-Id ) is set to the BWP ID of the DL BWP that is the dormant DL BWP. Note that the dormant BWP-Id ( dormantBWP-Id ) can be configured for a secondary cell (SCell) instead of a SpCell (i.e., PCell or PSCell). The gNB can signal the first active downlink BWP-Id ( firstActiveDownlinkBWP-Id ) to indicate which of these configured DL BWPs is the first active DL BWP. The gNB can do this by signaling the parameter First Active Uplink BWP-Id ( firstActiveUplinkBWP-Id ) to indicate which of these configured UL BWPs is the first active UL BWP. The gNB may also configure a BWP inactivity timer for zero, one or more serving cells in the RRC reconfiguration message ( bwp- InactivityTimer ).

[0080] For SpCell, upon receiving the RRC reconfiguration message, the first active downlink BWP-Id ( firstActiveDownlinkBWP-Id ) and the first active uplink BWP-Id ( firstActiveUplinkBWP-Id ) indicates that the DL BWP and UL BWP are activated. For SCell, if the SCell is configured with an sCell state that is set to be activated when the SCell is configured ( sCellState ), or an SCell activation / deactivation MAC CE or enhanced SCell activation / deactivation MAC CE that activates the SCell is received: the first active downlink BWP-Id of this SCell ( firstActiveDownlinkBWP-Id ) and the first active uplink BWP-Id ( firstActiveUplinkBWP-Id ) indicated DL BWP and UL BWP are activated.

[0081] The MAC entity or UE shall configure a BWP inactivity timer for each bwp-InactivityTimer ) to activate the serving cell by performing the following operations: 1> If a PDCCH for BWP switching is received and the MAC entity / UE switches the active DL BWP (in other words, a PDCCH is received and the DCI instructs the UE to switch the active DL BWP of the serving cell to one of the configured DL BWPs that is different from the current active DL BWP, the UE switches its active DL BWP to the DL BWP indicated in the DCI): 2> If the default downlink BWP-Id is configured ( defaultDownlinkBWP-Id), and the MAC entity / UE switches to a DL BWP that is not identified by the default downlink BWP-Id ( defaultDownlinkBWP-Id ) indication, and if a dormant BWP-Id is configured ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) instructions; or 2> If the default downlink BWP-Id is not configured ( defaultDownlinkBWP-Id ), and if the UE is not a RedCap UE, and the MAC entity / UE switches to a DL BWP that is not the initial downlink BWP ( initialDownlinkBWP ), and if a dormant BWP-Id is configured ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) instructions; or 2> If the default downlink BWP-Id is not configured ( defaultDownlinkBWP-Id ), and if the UE is a RedCap UE and the initial downlink BWP-RedCap is not configured ( initialDownlinkBWP-RedCap ), and the MAC entity / UE switches to a DL BWP that is not the initial downlink BWP ( initialDownlinkBWP ) and if a dormant BWP-Id is configured ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) instructions; or 2> If the default downlink BWP-Id is not configured ( defaultDownlinkBWP-Id ), and if the UE is a RedCap UE and the initial downlink BWP-RedCap is configured ( initialDownlinkBWP-RedCap ), and the MAC entity / UE switches to a DL BWP that is not the initial downlink BWP-RedCap ( initialDownlinkBWP- RedCap ), and if a dormant BWP-Id is configured ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP- Id )instruct: 3> Start or restart the BWP inactivity timer associated with the active DL BWP ( bwp-InactivityTimer ) (Note that here the active DL BWP is the DL BWP to which the UE switches upon receiving a BWP switching command).

[0082] Note that if the RedCap UE does not support carrier aggregation (i.e. does not support SCells), the gNB will not configure a dormant BWP-Id ( dormantBWP-Id ), because the dormant BWP-Id ( dormantBWP-Id) is used for SCells. If a dormant BWP-Id is configured in the above operation ( dormantBWP-Id ), such RedCap UE can skip checking the ID of the UE by the dormant BWS-Id ( dormantBWP-Id ) indicates the condition because a dormant BWP-Id has never been configured for such RedCap UE ( dormantBWP-Id ).

[0083] The gNB shall set a BWP inactivity timer for each UE configured with bwp-InactivityTimer ) performs the following operations (note that the gNB can know whether the UE is a RedCap UE based on the UE capabilities transmitted by the UE to the gNB): 1> If a PDCCH for DL ​​BWP switching of the serving cell is sent to the UE (in other words, a PDCCH is sent and the DCI instructs the UE to switch the active DL BWP of the serving cell to one of the configured DL BWPs that is different from the current active DL BWP, and the gNB switches the effective DL BWP of the UE’s serving cell to the indicated DL BWP in the DCI): 2> If the default downlink BWP-Id is configured for the serving cell ( defaultDownlinkBWP-Id ), and the gNB switches to a DL BWP that is not identified by the default downlink BWP-Id ( defaultDownlinkBWP-Id ) indication and if a dormant BWP-Id is configured ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) instructions; or 2> If the default downlink BWP-Id is not configured ( defaultDownlinkBWP-Id ), and if the UE is not a RedCap UE and the gNB switches to a DL BWP that is not the initial downlink BWP ( initialDownlinkBWP ), and if a dormant BWP-Id is configured ( initialDownlinkBWP ) nor by the dormant BWP-Id ( initialDownlinkBWP ) instructions; or 2> If the default downlink BWP-Id is not configured ( defaultDownlinkBWP-Id ), and if the UE is a RedCap UE and the initial downlink BWP-RedCap is not configured ( initialDownlinkBWP-RedCap ), and the gNB switches to a DL BWP that is not the initial downlink BWP ( initialDownlinkBWP ), and if a dormant BWP-Id is configured ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) instructions; or 2> If the default downlink BWP-Id is not configured (defaultDownlinkBWP-Id ), and if the UE is a RedCap UE and the initial downlink BWP-RedCap is configured ( initialDownlinkBWP-RedCap ), and the gNB switches to a DL BWP that is not the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ) and if a dormant BWP-Id is configured and not dormantBWP-Id )instruct: 3> Start or restart the BWP inactivity timer associated with the active DL BWP ( bwp-InactivityTimer ) (Note that here the active DL BWP is the DL BWP that the gNB switches to when transmitting a BWP switching command).

[0084] Note that if the RedCap UE does not support carrier aggregation (i.e. does not support SCells), the gNB will not configure a dormant BWP-Id ( dormantBWP-Id ), because the dormant BWP-Id ( dormantBWP-Id ) is used for SCells. For such RedCap UE, if the dormant BWP-Id ( dormantBWP-Id ), the gNB may skip checking whether the condition is determined by a dormant BWP-Id ( dormantBWP-Id ) indication, because a dormant BWP-Id has never been configured for such a RedCap UE ( dormantBWP-Id ).

[0085] In the embodiments of the present disclosure, the UE of the serving cell operates as follows: Figure 1 shown.

[0086] Figure 1 is an example diagram of starting or restarting the BWP inactivity timer according to the method of the present disclosure.

[0087] refer to Figure 1 In step 110, the UE receives an RRC reconfiguration message from the gNB. The RRC reconfiguration message includes configuring one or more dedicated DL BWPs and one or more dedicated UL BWPs for each serving cell. The gNB may configure the default downlink BWP-Id ( defaultDownlinkBWP-Id ) to indicate which of these configured DL BWPs is the default DL BWP. Parameter Default Downlink BWP-Id ( defaultDownlinkBWP-Id ) is set to the BWP ID of the DL BWP that is the default DL BWP. Similarly, the gNB can sleep BWP-Id by signaling parameter ( dormantBWP-Id ) to indicate which of these configured DL BWPs is the dormant DL BWP. Parameter dormantBWP-Id ( dormantBWP-Id) is set to the BWP ID of the DL BWP that is the dormant DL BWP. The gNB can signal the first active downlink BWP-Id ( firstActiveDownlinkBWP-Id ) to indicate which of these configured DL BWPs is the first active DL BWP. The gNB can do this by signaling the parameter First Active Uplink BWP-Id ( firstActiveUplinkBWP-Id ) indicates which of these configured UL BWPs is the first active UL BWP. The gNB may also configure a BWP inactivity timer for zero, one or more serving cells in the RRC reconfiguration message ( bwp-InactivityTimer ). And, for the serving cell, an active DL BWP is activated. The activated DL BWP is one of the configured DL BWPs with BWP ID 'X'. In an embodiment, the activated DL BWP is determined by the default downlink BWP-Id ( defaultDownlinkBWP-Id ) indicated by the initial DL BWP, or by the first active downlink BWP-Id ( firstActiveDownlinkBWP-Id ) or one of the first active DL BWP indicated by the DCI, the DCI including information about the DL BWP to be activated.

[0088] In step 120, the UE / MAC entity receives a PDCCH for switching the active DL BWP of the serving cell to a DL BWP with BWP ID 'Y'. In an embodiment, information of the DL BWP with BWP ID 'Y' is included in the DCI. The DL BWP with BWP ID 'Y' is one of the configured DL BWPs that is different from the currently active DL BWP with BWP ID 'X'.

[0089] In step 130, the UE / MAC entity switches the active DL BWP of the serving cell to the DLBWP with BWP ID 'Y'.

[0090] In step 140, the UE / MAC entity determines whether a default downlink BWP-Id ( defaultDownlinkBWP-Id ).

[0091] When a default downlink BWP-Id is configured for the serving cell ( defaultDownlinkBWP-Id ), in step 150, the UE / MAC entity determines whether the switched DL BWP (ie, the DL BWP with BWP ID 'Y') is neither the default downlink BWP-Id ( defaultDownlinkBWP-Id ) indicates that if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id) indication. When the default downlink BWP-Id ( defaultDownlinkBWP-Id ), the switched DL BWP (i.e. the DLBWP with BWP ID 'Y') is not replaced by the default downlink BW-Id ( defaultDownlinkBWP-Id ) indicates that if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) indicates that the UE / MAC entity starts or restarts the BWP inactivity timer ( bwp- InactivityTimer ).

[0092] When a default downlink BWP-Id is configured for the serving cell ( defaultDownlinkBWP-Id ), in step 160, the UE / MAC entity determines whether the UE is a RedCap UE.

[0093] In case the UE is not a RedCap UE, in step 170, the UE / MAC entity determines whether the switched DL BWP (ie, the DL BWP with BWP ID 'Y') is neither replaced by the initial downlink BWP ( initialDownlinkBWP ) indicates that if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWB-Id ( dormantBWP-Id ) indication. When no default downlink BWP-Id is configured for the serving cell ( defaultDownlinkBWP-Id ) and the UE is not a RedCap UE, the switched DL BWP (i.e. the DL BWP with BWP ID 'Y') is not replaced by the initial downlink BWP ( nitialDownlinkBWP ) indication, and if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) indication, the UE / MAC entity starts or restarts the BWP inactivity timer associated with the active DL BWP ( bwp-InactivityTimer ).

[0094] In the case where the UE is a RedCap UE, in step 180, the UE / MAC entity determines whether the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ), and the switched DL BWP (i.e., the DL BWP with BWP ID Y) is neither replaced by the initial downlink BWP ( initialDownlinkBWP ) indicates that if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id) indication. When no default downlink BWP-Id is configured for the serving cell ( defaultDownlinkBWP-Id ) and the UE is a RedCap UE and no initial downlink BWP-RedCap is configured for the serving cell ( initialDownlinkBWP-RedCap ), and the switched DLBWP (i.e., the DL BWP with BWP ID 'Y') is not replaced by the initial downlink BWP ( nitialDownlinkBWP ) indication, and if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP- Id ) indicates, the UE / MAC entity starts or restarts the BWP inactivity timer associated with the active DL BWP ( bwp- InactivityTimer ).

[0095] In step 190, the UE / MAC entity determines whether an initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ), and the switched DL BWP (i.e. the DL BWP with BWP ID 'Y') is neither supported by the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ) indicates that if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) indication. When the default downlink BWPId ( defaultDownlinkBWP-Id ) and the UE is a RedCap UE, the initial downlink BWP-RedCap is configured for the serving cell ( initialDownlinkBWP-RedCap ), and the switched DL BWP (i.e. DL BWP with BWPID 'Y') is not replaced by the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ) indication, and if a dormant BWP-Id is configured for the serving cell ( dormantBWP-Id ) nor by the dormant BWP-Id ( dormantBWP-Id ) indicates, the UE / MAC entity starts or restarts the BWP inactivity timer associated with the active DL BWP ( bwp- InactivityTimer ).

[0096] In an embodiment of the present disclosure, when the random access procedure is initiated, after selecting a carrier (NUL or SUL) for performing the random access procedure as described above, if the UE is a RedCap UE and the UE is in RRC_IDLE or RRC_INACTIVE mode, the MAC entity / UE shall: 1> If the initial uplink BWP-RedCap is configured for the selected carrier ( initialUplinkBWP-RedCap ): 2>By using the initial uplink BWP-RedCap ( initialUplinkBWP-RedCap ) configured BWP to perform the random access process as described above.

[0097] 1> Otherwise: 2> By using the initial uplink BWP ( initialUplinkBWP ) configured BWP to perform the random access process as described above.

[0098] 1> If the initial downlink BWP-RedCap is configured ( initialDownlinkBWP-RedCap ): 2> In the initial downlink BWP-RedCap ( initialDownlinkBWP-RedCap ) monitors PDCCH on the configured BWP.

[0099] 1> Otherwise: 2> In the initial downlink BWP ( initialDownlinkBWP ) monitors PDCCH on the configured BWP.

[0100] Figure 2 is a diagram showing a configuration of a terminal according to the present disclosure.

[0101] The terminal (UE) according to an embodiment of the present disclosure may include a transceiver 220 and a controller 210 controlling overall operations of the terminal. The transceiver 220 may include a transmitter 221 and a receiver 223 .

[0102] Transceiver 220 may send and receive signals to and from other network entities.

[0103] In the above-mentioned embodiment, the controller 210 can control the terminal to perform an operation. At the same time, the controller 210 and the transceiver 220 do not have to be implemented as separate modules, but can be implemented as an element, such as a single chip. The controller 210 and the transceiver 220 can be electrically connected. For example, the controller 210 can be a circuit, a dedicated circuit or at least one processor. In addition, the operation of the terminal can be performed by including a storage device storing a corresponding program code in a predetermined element in the terminal.

[0104] Figure 3 is a diagram showing a configuration of a base station according to the present disclosure.

[0105] The base station according to an embodiment of the present disclosure may include a transceiver 320 and a controller 310 controlling overall operations of the base station. The transceiver 320 may include a transmitter 321 and a receiver 323.

[0106] The transceiver 320 may send signals to a network entity and a terminal, and may also receive signals from a network entity and a terminal.

[0107] The controller 310 can control the base station to perform an operation in the above-mentioned embodiment. At the same time, the controller 310 and the transceiver 320 do not have to be implemented as separate modules, but can be implemented as one element, such as a single chip. The controller 310 and the transceiver 320 can be electrically connected. For example, the controller 310 can be a circuit, a dedicated circuit, or at least one processor. In addition, the operation of the base station can be performed by including a storage device storing a corresponding program code in a predetermined element in the base station.

[0108] It should be noted that Figures 1 to 3 The block diagrams, example diagrams of control / data signal transmission methods, example diagrams of operation processes, and diagrams shown in the are not intended to limit the scope of the present disclosure. Figures 1 to 3 All component parts, entities or operations shown in the drawings are explained as essential elements for implementing the present disclosure, and it should be understood that only a few of the elements may be used to implement the present disclosure within the scope without departing from the subject matter of the present disclosure.

[0109] When a predetermined element within a base station or UE device includes a storage device storing corresponding program codes, the operation of the base station or UE can be performed. That is, the controller of the base station or UE device can read and execute the program code stored in the storage device through a processor or a central processing unit (CPU) to perform the operation.

[0110] The various elements and modules of the entity, base station or UE used in this specification can be operated by using hardware circuits, for example, a combination of complementary metal oxide semiconductor-based logic circuits, firmware, software and / or hardware, or a combination of firmware and / or software inserted into a machine-readable medium. For example, various electrical structures and methods can be performed using transistors, logic gates, and circuits such as application-specific integrated circuits.

[0111] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications and changes may be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined as limited to the embodiments, but should be defined by the appended claims and their equivalents.

[0112] The embodiments of the present disclosure described and shown in the specification and the drawings are only specific examples proposed to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it will be understood by those skilled in the art that other variations based on the technical ideas of the present disclosure can be realized. In addition, the above-mentioned various embodiments can be used in combination as needed.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, a first message including configuration information associated with at least one bandwidth portion; receiving a second message from the base station, the second message comprising information indicating an active downlink bandwidth portion from the at least one bandwidth portion; switching to the active downlink bandwidth portion; In a case where the terminal is a reduced capability terminal, a default downlink bandwidth portion is not configured, an initial downlink bandwidth portion for the reduced capability terminal is not configured, and the active downlink bandwidth portion is not an initial downlink bandwidth portion for a serving cell, a timer associated with bandwidth portion inactivity is started or restarted.

2. The method according to claim 1, further comprising: In a case where the terminal is the reduced capability terminal, the default downlink bandwidth portion is not configured, the initial downlink bandwidth portion for the reduced capability terminal is configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion for the reduced capability terminal, a timer associated with inactivity of the bandwidth portion is started or restarted.

3. The method according to claim 1, further comprising: In case the terminal is not the reduced capability terminal, the default downlink bandwidth portion is not configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion and is not indicated by an identification of a dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

4. The method according to claim 1, further comprising: In case the default downlink bandwidth portion is configured and the active downlink bandwidth portion is not indicated by the identifier of the default downlink bandwidth portion and is not indicated by the identifier of the dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

5. The method according to claim 1, wherein: The first message comprises a radio resource control (RRC) reconfiguration message, and The second message includes downlink control information (DCI).

6. A method performed by a base station in a wireless communication system, the method comprising: sending a first message including configuration information related to at least one bandwidth part to a terminal; sending a second message to the terminal, the second message comprising information indicating an active downlink bandwidth portion from the at least one bandwidth portion; as well as In a case where the terminal is a reduced capability terminal, a default downlink bandwidth portion is not configured, an initial downlink bandwidth portion for the reduced capability terminal is not configured, and the active downlink bandwidth portion is not an initial downlink bandwidth portion for a serving cell, a timer associated with bandwidth portion inactivity is started or restarted.

7. The method according to claim 6, further comprising: In a case where the terminal is the reduced capability terminal, the default downlink bandwidth portion is not configured, the initial downlink bandwidth portion for the reduced capability terminal is configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion for the reduced capability terminal, a timer associated with inactivity of the bandwidth portion is started or restarted.

8. The method according to claim 6, further comprising: In case the terminal is not the reduced capability terminal, the default downlink bandwidth portion is not configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion and is not indicated by an identification of a dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

9. The method according to claim 6, further comprising: In case the default downlink bandwidth portion is configured and the active downlink bandwidth portion is not indicated by the identifier of the default downlink bandwidth portion and is not indicated by the identifier of the dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

10. The method according to claim 6, wherein: The first message comprises a radio resource control (RRC) reconfiguration message, and The second message includes downlink control information (DCI).

11. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: receiving, from a base station, a first message including configuration information related to at least one bandwidth part, receiving a second message from the base station, the second message comprising information indicating an active downlink bandwidth portion from the at least one bandwidth portion, switching to said active downlink bandwidth portion, In a case where the terminal is a reduced capability terminal, a default downlink bandwidth portion is not configured, an initial downlink bandwidth portion for the reduced capability terminal is not configured, and the active downlink bandwidth portion is not an initial downlink bandwidth portion for a serving cell, a timer associated with bandwidth portion inactivity is started or restarted.

12. The terminal according to claim 11, wherein: The controller is also configured to: In a case where the terminal is the reduced capability terminal, the default downlink bandwidth portion is not configured, the initial downlink bandwidth portion for the reduced capability terminal is configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion for the reduced capability terminal, a timer associated with inactivity of the bandwidth portion is started or restarted.

13. The terminal according to claim 11, wherein: The controller is also configured to: In case the terminal is not the reduced capability terminal, the default downlink bandwidth portion is not configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion and is not indicated by an identification of a dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

14. The terminal according to claim 11, wherein: The controller is also configured to: In case the default downlink bandwidth portion is configured and the active downlink bandwidth portion is not indicated by the identifier of the default downlink bandwidth portion and is not indicated by the identifier of the dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

15. The terminal according to claim 1, wherein: The first message comprises a radio resource control (RRC) reconfiguration message, and The second message includes downlink control information (DCI).

16. A base station in a wireless communication system, the base station comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: sending a first message including configuration information related to at least one bandwidth part to a terminal, sending a second message to the terminal, the second message comprising information indicating an active downlink bandwidth portion from the at least one bandwidth portion, and In a case where the terminal is a reduced capability terminal, a default downlink bandwidth portion is not configured, an initial downlink bandwidth portion for the reduced capability terminal is not configured, and the active downlink bandwidth portion is not an initial downlink bandwidth portion for a serving cell, a timer associated with bandwidth portion inactivity is started or restarted.

17. The base station according to claim 16, wherein: The controller is also configured to: In a case where the terminal is the reduced capability terminal, the default downlink bandwidth portion is not configured, the initial downlink bandwidth portion for the reduced capability terminal is configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion for the reduced capability terminal, a timer associated with inactivity of the bandwidth portion is started or restarted.

18. The base station according to claim 16, wherein: The controller is also configured to: In case the terminal is not the reduced capability terminal, the default downlink bandwidth portion is not configured, and the active downlink bandwidth portion is not the initial downlink bandwidth portion and is not indicated by an identification of a dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

19. The base station according to claim 16, wherein: The controller is also configured to: In case the default downlink bandwidth portion is configured and the active downlink bandwidth portion is not indicated by the identifier of the default downlink bandwidth portion and is not indicated by the identifier of the dormant bandwidth portion, a timer associated with inactivity of the bandwidth portion is started or restarted.

20. The base station according to claim 16, wherein: The first message comprises a radio resource control (RRC) reconfiguration message, and The second message includes downlink control information (DCI).

Images