Patent Description:
The Internet of Everything (IoE), which is a combination of the loT technology and the Big Data processing technology through connection with a cloud server, has emerged.

Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the <NUM> technology and the loT technology.

Generally, mobile communication systems have been developed for providing a high quality mobile communication services to a user. With the dramatic development of communication technologies, the mobile communication systems are now capable of providing high-speed data communication services as well as voice communication services. A Long Term Evolution (LTE) is a technology for implementing a packet-based communication at a higher data rate of a maximum of about <NUM> Mbps. In order to meet the demand for an increased wireless data traffic, since deployment of 4th generation (<NUM>) communication systems, efforts have been made to develop an improved 5th generation (<NUM>) communication systems or an LTE-Advanced communication system. Therefore, the <NUM> or LTE-Advanced communication system is also called a 'beyond <NUM> network' or a 'post LTE system'. The <NUM> communication systems operate in sub-<NUM> spectrum bands, where all transmissions and receptions take place in an Omni-directional manner.

In order to achieve a high data transmission rate, the <NUM> communication system is considered to be implemented in a millimeter wave (mm Wave) or extremely higher frequency bands as well, for e.g., <NUM>, <NUM>, etc., so as to accomplish higher data rates. In such instances, a User Equipment (UE) of the <NUM> system must support bandwidth on the order of <NUM> in a single carrier. In other words, without using carrier aggregation, the user of the <NUM> must support bandwidths of this order. Several challenges arise in this regard as the user of the UE must support wide bandwidth such as Radio Frequency (RF), power consumption, scheduling etc. As the user of the UE need not always require such wide bandwidth, there exists a concept of 1st RF and 2nd RF bandwidth in the wide bandwidth. However, the goal is to avoid the user of the UE from monitoring wide bandwidth all the time as it is not power efficient.

<NPL>) discusses methods for DCI-based activation/deactivation signalling retransmission in all configured BWPs and addresses the problem of reliability of DCI based activation/deactivation.

From <CIT> a low-cost terminal implementation for power consumption reduction is known, providing a cell-bandwidth and a power-saving bandwidth, lower than the cell-bandwidth.

The objective of the present invention is to solve at least one of the above technical deficiencies, particularly the data forwarding problem during the movement of a UE between an LTE system and a <NUM> system.

A first aspect of the invention comprises a method as set forth in claim <NUM>.

A second aspect of the invention comprises a method as set forth in claim <NUM>.

A third aspect of the invention comprises a base station as set forth in claim <NUM>.

A fourth aspect of the invention comprises a user equipment as set forth in claim <NUM>.

Some referred embodiments are defined in the dependent claims.

Additional aspects and advantages of the present invention will be partially appreciated and become apparent from the descriptions below, or will be well learned from the practices of the present invention.

The principal object of the embodiments herein is to provide a method and system for handling a Radio Link Monitoring (RLM) using Bandwidth Part (BWP) configurations in the wireless communication system.

Another object of the embodiments herein is to detect an active BWP based on the BWP configurations from the base station.

Another object of the embodiments herein is to perform the RLM on the active BWP using the BWP configurations.

Another object of the embodiments herein is to detect that the active BWP is deactivated from the base station based on the BWP configuration.

Another object of the embodiments herein is to perform a retransmission on a configured active BWP from the plurality of BWPs by recombining a data associated with the deactivated BWP and the configured active BWP using a Hybrid Automatic Repeat Request (HARQ) buffer.

Another object of the embodiments herein is to report an in-sync measurement for each BWP to the base station.

Another object of the embodiments herein is to report an out-sync measurement for each BWP to the base station.

The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:.

Accordingly the embodiments herein provide a method and system for handling a RLM using BWP configurations in the wireless communication system. The method includes receiving, by a User Equipment (UE), the BWP configurations for each BWPs in a plurality of BWPs of a total bandwidth from a base station using one of a MAC Control Element (MAC-CE), a Radio Resource Control (RRC) message, and a Downlink Control Indicator (DCI), wherein the BWP configurations comprising one of a single active BWP and multiple active BWP in the plurality of BWPs. Further, the method includes detecting, by the UE, an active BWP based on the BWP configurations from the base station, wherein at least one of the active BWP and a deactivated BWP in the plurality of BWPs are indicated using one of the MAC CE and the DCI in the RRC message. Further, the method includes performing, by the UE, the RLM on the active BWP using the BWP configurations.

In an embodiment, performing the RLM on the active BWP using the BWP configurations includes detecting, by the UE, that the active BWP is deactivated from the base station based on the BWP configuration. Further, the method includes performing, by the UE, a retransmission on a configured active BWP from the plurality of BWPs by recombining a data associated with the deactivated BWP and the configured active BWP using a Hybrid Automatic Repeat Request (HARQ) buffer.

In an embodiment, MAC CE indicates an association between a Bandwidth Part-Identity (BWP-ID) and a BWP-ID index of the active BWP.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in a plurality of BWPs of the total bandwidth from the base station includes receiving an Uplink Bandwidth Part (UL BWP) and a Downlink Bandwidth Part (DL BWP) for each BWPs in the plurality of BWPs. Further, the method includes receiving an association between the UL BWP and the DL BWP using the RRC message from the base station.

In an embodiment, a bundling window is received for the UL BWP and the DL BWP.

In an embodiment, the association comprises a pairing relationship between the UL BWP and the DL BWP, wherein the pairing relationship is received from the base station.

In an embodiment, the pairing relationship between the UL BWP and DL BWP is received from the base station for Time Division Duplexing (TDD) mode of operation and a Frequency Division Duplexing (FDD) mode of operation.

In an embodiment, the active BWP is indicated to the UE using one of the MAC CE and the DCI in the RRC message, includes receiving, by the UE, the BWP configurations comprise one of:.

Further, the method includes tuning, by the UE, to the active BWP based on the BWP configurations.

In an embodiment, the BWP configurations comprising one of the single active BWP and multiple active BWP in the plurality of BWPs includes indicating, by the UE, a capability information to the base station. Further, the method includes receiving, by the UE, at least one of a number of soft bits, a soft buffer partitioning for each BWP, and a maximum number of HARQ processes based on the capability information from the base station. Further, the method includes activating, by the UE, one of the single active BWP and the multiple active BWP in the plurality of BWP based on the capability information.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving at least one of a timer value, a maximum number of NACK, and a Discontinuous reception (DRx) timer from the base station using the MAC Control Element (MAC-CE), the Radio Resource Control (RRC) message, and the Downlink Control Indicator (DCI).

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving, by the UE, a QCL relationship between a Demodulation Reference Signal (DMRS) and at least one reference signal for each BWP during a RRC connection using the Radio Resource Control (RRC) message.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving by the UE, a QCL relationship between a Demodulation Reference Signal (DMRS) and at least one reference signal for the activated BWP using one of the MAC Control Element (MAC-CE), and the Downlink Control Indicator (DCI).

In an embodiment, the at least one reference signal is one of a Synchronization Signal (SS) block and a Channel State Information Reference Signal (CSI-RS).

In an embodiment, the UL BWP and the DL BWP are activated by receiving a measurement gap information within a configured frequency range of the active BWP from the base station and activating the UL BWP and the DL BWP based on the measurement gap information.

In an embodiment, the measurement gap information is used to retune at least one of a Sounding Reference Signaling (SRS) and a Channel State Information Reference Signal (CSI-RS).

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving one of a default Radio Link Monitoring Bandwidth Part (RLM BWP) and Radio Link Monitoring Reference signal (RLM RS) resources for each BWPs.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving, by the UE, at least one of a default Bandwidth Part (BWP), a current active Bandwidth Part (BWP) for the RLM, and one of Radio Link Monitoring Reference signal (RLM RS) resources for each BWPs and the Radio Link Monitoring Reference signal (RLM RS) resources for the BWP on which RLM is to be performed from the base station. Further, the method includes receiving, by the UE, interference measurement resources on the BWP on which RLM is to be performed from the base station.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving, by the UE, at least one of Control-Resource Set (CORESET) configurations comprising in-sync RLM resources, QCL relationship information across the each BWP of the plurality of BWPs, and an interference measurement resources for the BWP from the base station. Further, the method includes monitoring, by the UE, an in-sync measurement on at least one of the single active BWP and the multiple active BWP based on the QCL information. Further, the method includes reporting, by the UE, the in-sync measurement of each BWP to the base station.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving, by the UE, at least one of Control-Resource Set (CORESET) configurations comprising an out-of-sync RLM resources, QCL relationship information across the each BWP of the plurality of BWPs, and an interference measurement resources for the BWP. Further, the method includes monitoring, by the UE, an out-sync measurement and a BWP threshold value on at least one of the single active BWP and the multiple active BWP based on the QCL information. Further, the method includes reporting, by the UE, the out-sync measurement of each BWP to the base station.

In an embodiment, the BWP configurations comprise a BWP threshold for the UE to trigger Out-Of-Sync (OOS), when the multiple active BWP are activated.

In an embodiment, the CORESET configurations are configured for at least one of the configured active BWP and a default BWP, wherein the default BWP is an initial active BWP indicated from the base station during an initial access configuration.

In an embodiment, the CORESET configuration comprises: a pre-defined location and a size of the initial active BWP for the UL transmission and the DL transmission using Master Information Block (MIB) and a Remaining Minimum System Information (RMSI).

In an embodiment, the method further includes receiving a location of the CORESET configuration using a Physical Broadcast Channel (PBCH) from the base station.

In an embodiment, the location is received as an offset in Resource Blocks (RBs) number using one of a SSB numerology and a RMSI numerology.

In an embodiment, receiving, by the UE, the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the base station, further includes receiving a set of BWPs by using at least one of a common PRB indexing and a different PRB indexing.

In an embodiment, further comprises: receiving an Uplink Physical Resource Block (UL PRB) for the common PRB indexing from the base station.

In an embodiment, further comprises: receiving frequency locations of a PRB associated with the common PRB indexing, for DL BWP and the UL BWP using at least one of the RMSI and the RRC message from the base station.

In an embodiment, further comprises: receiving a PRB offset level indication associated with the common PRB indexing from the base station, wherein the PRB offset level indication indicates a range from an initial PRB value to an Absolute Frequency Channel Number (ARFCN).

In an embodiment, the CORESET configurations indicate a RMSI location as the offset in RBs using a reference SSB numerology and RMSI numerology.

In an embodiment, the RMSI location is common across the SS block, partially common across the SS block and different for each SS block.

In an embodiment, the total bandwidth is a wideband CC comprising multiple SSB.

In an embodiment, the UE is configured to fallback from the configured active BWP to the default BWP for performing the radio link monitoring based on a timer value.

Accordingly the embodiments herein provide a User Equipment (UE) for handling a RLM using BWP configurations in a wireless communication system. The UE includes a RLM engine operably coupled with a memory and a processor. The RLM engine is configured to receive the BWP configurations for each BWPs in a plurality of BWPs of a total bandwidth from a base station using one of a MAC Control Element (MAC-CE), a Radio Resource Control (RRC) message, and a Downlink Control Indicator (DCI), wherein the BWP configurations comprising one of a single active BWP and multiple active BWP in the plurality of BWPs. Further, the RLM engine is configured to detect an active BWP based on the BWP configurations from the base station, wherein at least one of the active BWP and a deactivated BWP in the plurality of BWPs are indicated using one of the MAC CE and the DCI in the RRC message. Furthermore, the RLM engine is configured to perform the RLM on the active BWP using the BWP configurations.

Many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications.

In accordance with an aspect of the present disclosure, an embodiment of the present invention provides a method of a base station in a wireless communication system, the method comprising: transmitting, to a user equipment (UE), a master information block (MIB) including initial downlink bandwidth part (BWP) configuration information; and transmitting, to the UE, Remaining Minimum System Information (RMSI) including initial uplink bandwidth part (BWP) configuration information, wherein the RMSI is transmitted based on the initial downlink bandwidth part (BWP) configuration information.

The method further comprisies transmitting, to the UE, radio resource control (RRC) message including BWP configuration information; and transmitting, to the UE, downlink control information (DCI) including information indicating an active BWP based on the BWP configuration information, wherein the active BWP includes an uplink BWP and a downlink BWP paired with the uplink BWP.

Radio link monitoring (RLM) configuration information and information on Quasi co-location (QCL) relationship between a first reference signal and a second reference signal are associated with the BWP configuration information.

The method further comprisies transmitting, to the UE, a first data based on the active BWP; identifying a change of the active BWP based on the DCI; and transmitting, to the UE, a second data based on the changed active BWP, wherein the first data and the second data are combined in the UE.

In accordance with another aspect of the present disclosure, another embodiment of the present invention provides a method of a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a base station, a master information block (MIB) including initial downlink bandwidth part (BWP) configuration information; and receiving, from the base station, Remaining Minimum System Information (RMSI) including initial uplink bandwidth part (BWP) configuration information, wherein the RMSI is received based on the initial downlink bandwidth part (BWP) configuration information.

The method further comprisies receiving, from the base station, radio resource control (RRC) message including BWP configuration information; and receiving, from the base station, downlink control information (DCI) including information indicating an active BWP based on the BWP configuration information, wherein the active BWP includes an uplink BWP and a downlink BWP paired with the uplink BWP.

The method further comprisies receiving, from the base station, a first data based on the active BWP; and receiving, from the base station, a second data based on a changed active BWP, wherein the changed active BWP is identified based on the DCI, and wherein the first data and the second data are combined.

In accordance with another aspect of the present disclosure, another embodiment of the present invention provides a base station in a wireless communication system, the base station comprising: a transceiver; and a processor operably connected to the transceiver, the processor configured to: transmit, to a user equipment (UE), a master information block (MIB) including initial downlink bandwidth part (BWP) configuration information; and transmit, to the UE, Remaining Minimum System Information (RMSI) including initial uplink bandwidth part (BWP) configuration information, wherein the RMSI is transmitted based on the initial downlink bandwidth part (BWP) configuration information.

The processor is further configured to: transmit, to the UE, radio resource control (RRC) message including BWP configuration information; and transmit, to the UE, downlink control information (DCI) including information indicating an active BWP based on the BWP configuration information, wherein the active BWP includes an uplink BWP and a downlink BWP paired with the uplink BWP.

In accordance with another aspect of the present disclosure, another embodiment of the present invention provides a user equipment (UE) in a wireless communication system, the UE comprising: a transceiver; and a processor operably connected to the transceiver, the processor configured to: receive, from a base station, a master information block (MIB) including initial downlink bandwidth part (BWP) configuration information; and receive, from the base station, a Remaining Minimum System Information (RMSI) including initial uplink bandwidth part (BWP) configuration information, wherein the RMSI is received based on the initial downlink bandwidth part (BWP) configuration information.

The processor is further configured to: receive, from the base station, radio resource control (RRC) message including BWP configuration information; and receive, from the base station, downlink control information (DCI) including information indicating an active BWP based on the BWP configuration information, wherein the active BWP includes an uplink BWP and a downlink BWP paired with the uplink BWP.

The processor is further configured to:receive, from the base station, a first data based on the active BWP; and receive, from the base station, a second data based on a changed active BWP, wherein the changed active BWP is identified based on the DCI, and wherein the first data and the second data are combined.

As traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, storage circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware and/or software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

The term 'NR' is "new radio" is the term used by 3GPP specification for discussing activities about <NUM> communication systems.

The term "base station" and "gNB" used herein can be used interchangeably without departing from the scope of the embodiments. Further, the term "mapping" and "association" used herein can be used interchangeably without departing from the scope of the embodiments.

Embodiments herein provide a method and system for handling a RLM using BWP configurations in the wireless communication system. The method includes receiving, by a UE, the BWP configurations for each BWPs in a plurality of BWPs of the total bandwidth from a base station using one of a MAC Control Element (MAC-CE), a Radio Resource Control (RRC) message, and a Downlink Control Indicator (DCI). Further, the method includes detecting, by the UE, an active BWP from the base station based on the BWP configurations. Further, the method includes performing, by the UE, the RLM on the active BWP using the BWP configurations.

Unlike conventional methods and systems, the proposed method can be used to retransmit a data of the deactivated BWP along with data of the active BWP, when a BWP is de-activated. This results in providing a functionality such as a HARQ buffer may not be flushed when BWP is de-activated. Hence this can avoid wastage of data in the BWP.

Unlike conventional methods and systems, the proposed method can be used for managing wideband operations in a power efficient manner. This enables high data rates and also better power consumption efficiency.

The proposed method can be used to configure an initial active UL BWP configuration and an initial active DL BWP configuration for each BWP using the RMSI.

<FIG> is a schematic diagram illustrating a BWP configuration for a wideband operations in a wireless communication system, according to a prior art. In conventional methods, several aspects of the wideband operation such as configuring search space locations, supporting Multi-user Multiple-Input and Multiple-Output MU-MIMO for different users with different bandwidth capability sizes, bandwidth indication granularity, resource block group size, PRB bundling granularity, bandwidth configurations etc. have to be addressed. A generic term known as Bandwidth Part (BWP) is defined as a set of contiguous PRBs in frequency domain which are configured for a user. Resource allocation will be done within a BWP. Several BWP may be configured to the user but only one will be activated at a given time instant. Within the BWP, various issues mentioned above have to be addressed since each BWP is configured in a UE specific manner. Furthermore, when different users are considered for the case of supporting MU-MIMO in the downlink, the sizes of the BWP supported by each user must also be accounted for as it impacts the pre-coding design, the channel and interference estimation as a result of the same etc. BWP is a concept which does not need any RF involvement and it is a layer-<NUM> concept. Multiple BWP may be configured and activated to a UE and this entails new operations regarding monitoring timeline, BW sizes supported etc..

<FIG> is a block diagram of a wireless communication system in which the UE <NUM> communicates with a BS <NUM> for performing a RLM, according to an embodiment as disclosed herein. In an embodiment, the UE <NUM> includes a transceiver <NUM>, a RLM engine <NUM>, a communicator <NUM>, a processor <NUM> and a memory <NUM>. The UE <NUM> can be for e.g., a cellular telephone, a smartphone, a personal computer (PC), a minicomputer, a desktop, a laptop, a handheld computer, Personal Digital Assistant (PDA), or the like. The UE <NUM> may support multiple Radio access technologies (RAT) such as, for e.g., Code-division multiple access (CDMA), General Packet Radio Service (GPRS), Evolution-Data Optimized EVDO (EvDO), Time-division multiple access (TDMA), GSM(Global System for Mobile Communications, WiMAX (Worldwide Interoperability for Microwave Access) technology, LTE, LTE Advanced and <NUM> communication technologies.

The transceiver <NUM> can be configured to communicate with the BS <NUM> for performing a transmission and reception of signals. The BS <NUM> can be for example but not limited to a next Generation NodeB (gNB), evolved NodeB (eNB), NR, and the like.

In an embodiment, the RLM engine <NUM> receives the BWP configurations for each BWPs in a plurality of BWPs of the total bandwidth from the BS <NUM>. The BWP configurations are received using one of a MAC Control Element (MAC-CE), a Radio Resource Control (RRC) message, and a Downlink Control Indicator (DCI).

In an embodiment, the RLM engine <NUM> detects an active BWP from the BS <NUM> based on the BWP configurations. In an embodiment, the RLM engine <NUM> performs the RLM on the active BWP using the BWP configurations.

In an embodiment, the RLM engine <NUM> detects that the active BWP is deactivated from the BS <NUM> based on the BWP configuration. Further, the RLM engine <NUM> performs a retransmission on a configured active BWP from the plurality of BWPs by recombining a data associated with a deactivated BWP and the configured active BWP using a Hybrid Automatic Repeat Request (HARQ) buffer.

In an embodiment, the RLM engine <NUM> receives one of an activation of the MAC CE and a deactivation of the MAC CE from the BS <NUM> using the RRC message. In an embodiment, the MAC CE indicates an association between the BWP-ID and a BWP-ID index.

In an embodiment, the RLM engine <NUM> receives an Uplink Bandwidth Part (UL BWP) and a Downlink Bandwidth Part (DL BWP) for each BWPs in a plurality of BWPs. Further, the RLM engine <NUM> receives an association between the UL BWP and the DL BWP using the RRC message from the BS <NUM>. The association includes a pairing relationship between the UL BWP and the DL BWP from the BS <NUM>.

In an embodiment, the RLM engine <NUM> activates the BWP based on the BWP configuration from the BS <NUM>. In an embodiment, the RLM engine <NUM> receives the activation of a Component Carrier (CC) using the MAC-CE and activation of the BWP inside the CC from the BS <NUM>. Further, the RLM engine <NUM> tunes to a specific CC and the BWP.

The MAC-CE based will require ACK/NACK from the UE <NUM> to confirm the BWP activation/de-activation. For the case of BWP activation along with CA based, i.e., activate Scell and also the BWP inside this Scell can be done via <NUM>-stage mechanism: MAC-CE <NUM> activates Scell i.e., CC and then MAC-CE <NUM> activates BWP inside the Scell. Another option is to define combined carrier and BWP Id where both can be activated simultaneously via MAC-CE <NUM>. A new MAC CE is needed for this activation since the joint CIF and BWP Id indicators must be defined. A same mechanism can be used for UL CC and UL BWP. Either an independent activation for this or some implicit activation can be relied upon for the case of UL BWP.

In another embodiment, the RLM engine <NUM> receives the activation of Component Carrier (CC) and the BWP using the MAC-CE from the BS <NUM>. Further, the RLM engine <NUM> tunes to the specific CC and the BWP.

In an embodiment, the RLM engine <NUM> activates one of the single active BWP and the multiple active BWP in the plurality of BWPs of the total bandwidth is based on indicating by the UE <NUM> a capability information to the BS <NUM>. Further, the RLM engine <NUM> receives at least one of a number of soft bits, a soft buffer partitioning, and HARQ process for each BWP during the multiple BWP activation from the BS <NUM> based on the capability information.

In an embodiment, when there is multiple active BWP within one CC, then multiple HARQ entities could be defined. Further, each HARQ can operate independently. The HARQ codebook could be defined per BWP, per numerology, pooling across numerology. One of the BWP can be defined for PUCCH which carries the HARQ ACK for all BWP belonging to same numerology. The following options can be defined for dynamic HARQ ACK codebook design.

For the UE <NUM> configured with multiple active BWP with different PDCCH monitoring periodicities (can be the same numerology or different numerology), HARQ-ACK timing can be with respect to one of the configured PDCCH monitoring periodicities. Regardless of FDD or TDD operation, when a first PDCCH monitoring periodicity is P times longer than a second PDCCH monitoring periodicity, for HARQ-ACK codebook determination, the first PDCCH monitoring periodicity corresponds to a bundling window with size of P slots for cells using the second PDCCH monitoring periodicity and operation can resemble the one in LTE for FDD-TDD CA or TDD CA with different UL-DL configurations. As shown in figure below, the slot duration is different for two DL BWP. Assuming <NUM> bits in DCI to indicate the HARQ-ACK timing of <NUM>, <NUM>, <NUM> and <NUM> slot (with reference to slots for PUCCH transmissions), and the UE <NUM> is configured to monitor PDCCH in every DL slot on each DL BWP. Then, for a given UL slot, e.g., #<NUM> UL slot, the associated bundling window for DL BWP1 consists of DL slot #<NUM> ~<NUM> and DL slot #<NUM>~#<NUM> for DL BWP2. Although we used the term slots, it could be configured in terms of mini-slots/ symbols.

In an embodiment, the RLM engine <NUM> receives at least one of a timer value and a maximum number of NACK, and Discontinuous reception (DRx) timer from the BS <NUM> using the MAC Control Element (MAC-CE), the Radio Resource Control (RRC) message, and the Downlink Control Indicator (DCI).

In an embodiment, the RLM engine <NUM> receives the BWP configurations for each BWPs in a plurality of BWPs of the total bandwidth from the BS <NUM> includes receiving a QCL relationship between a Demodulation Reference Signal (DMRS) and at least one reference signal for each BWP during a RRC connection using the Radio Resource Control (RRC) message.

In an embodiment, the RLM engine <NUM> receives the QCL relationship between a Demodulation Reference Signal (DMRS) and at least one reference signal for the activated BWP using the MAC Control Element (MAC-CE), and the Downlink Control Indicator (DCI) during RRC connection for at least one of activation BWP and deactivation of one BWP among the plurality of BWPs. In an example, the at least one reference signal is one of a Synchronization Signal (SS) block and a Channel State Information Reference Signal (CSI-RS).

In an embodiment, When SS and CSI-RS across different BWP exists, then some relationship may be indicated to the user about how to rely on measurements done on one BWP and use it on another BWP. This is required for the case where the UE <NUM> doesn't have to scan for all SS blocks on all BWP. Then UE can perform measurements for beam management and/or mobility much faster. The UE <NUM> is signaled with a QCL relationship across multiple SS Blocks in different BWP:.

UE can be configured that all the SS blocks/ CSI-RS in different BWP within a "unit resource" are QCL'ed in a set of parameters; and the SS blocks/ CSI-RS across different unit resources are not QCL'ed in these set of parameters.

For DMRS used in each BWP, the QCL RS is signaled per BWP during RRC Connection establishment.

Or during BWP changing only (only done based on need, may be too much overhead).

In an embodiment, the RLM engine <NUM> activates the UL BWP and the DL BWP based on receiving a measurement gap for an outside of a configured frequency range of the active BWP from the BS <NUM>. In an embodiment, the gap measurements is to retune at least one of Sounding Reference Signaling (SRS) and a Channel State Information Reference Signal (CSI-RS).

The BS <NUM> configures the measurement gap for the UE <NUM> based on the following procedure:.

In an embodiment, the RLM engine <NUM> receives a BWP identify from the plurality of BWPs for performing the RLM. Further, the RLM engine <NUM> receives one of a default Radio Link Monitoring (RLM) Bandwidth Part (BWP) and Radio Link Monitoring Reference signal (RLM RS) resources for each BWPs.

In an embodiment, the RLM engine <NUM> receives at least one of a default Bandwidth Part (BWP), a current active Bandwidth Part (BWP) for the RLM, and one of Radio Link Monitoring Reference signal (RLM RS) resources for each BWPs and the Radio Link Monitoring Reference signal (RLM RS) resources for the BWP on which RLM to be performed from the BS <NUM>. Further, the RLM engine <NUM> receives interference measurement resources on the BWP on which RLM to be performed from the BS <NUM>.

In an embodiment, the RLM engine <NUM> receives at least one of Control-Resource Set (CORESET) configurations includes in-sync RLM resources, QCL relationship information across the each BWP of the plurality of BWPs, and an interference measurement resources for the BWP. Further, the RLM engine <NUM> monitors an in-sync measurement on at least one of the single active BWP and the multiple active BWP based on the QCL information. Further, the RLM engine <NUM> reports the in-sync measurement for each BWP to the BS <NUM>.

In an embodiment, when multiple active BWP are configured for the UE, then the UE 200may trigger OOS only when the RLM on each of these BWP is found to satisfy the RLM threshold constraints. If the estimated link quality corresponding to hypothetical PDCCH BLER based on all configured X RLM-RS resource(s) is below Q_out threshold on all the multiple active BWP (in case the RLM resources are configrued in every BWP) or on the single BWP where RLM measurements are performed or on the default RLM BWP. On each of these BWP the number of RLM resources configrued by the gNB to theUE 200will be indicated by gNB toUE 200as "X" RLM resources.

For in-synch measurements, theUE 200will be configured to monitor the USS or CSS by the gNB. If USS, UE 200cna monitor in the current active BWp. For the case of multiple active BWP, UE 200will monitor in synch for each of the BWP which is active. If any of these multiple active BWP will be OOS condition satisfied, then the UE 200may not trigger RLF. Only this BWP can be de-activated. Rest can operate as it is.

In an embodiment, the RLM engine <NUM> receives at least one of Control-Resource Set (CORESET) configurations includes an out-of-sync RLM resources, QCL relationship information across the each BWP of the plurality of BWPs, and an interference measurement resources for the BWP. Further, the RLM engine <NUM> monitors an out-sync measurement and a BWP threshold value on at least one of the single active BWP and the multiple active BWP based on the QCL information. Further, the RLM engine <NUM> reports the out-sync measurement to the BS <NUM>.

The BWP_th is configured by gNB to the UE <NUM> to figure out when the UE <NUM> can trigger OOS in case of multiple active BWP. This can be fixed in spec or indicated to the UE. BWP_th>=<NUM>. If beams are used for determining beam failure and then the beam condition is used to trigger RLF, then the beams being used across BWP should be jointly used. If different beams are used across different active BWP, then RLF/RLM is done per BWP group using the same set of beams. The beam recovery/failure and the RLF will be together done based on these groups and per group.

In an embodiment, the BWP configurations includes the BWP threshold for the UE <NUM> to trigger Out-Of-Sync (OOS), when the multiple active BWP are activated. In an embodiment, the CORESET configurations are configured for at least one of the configured active BWP and a default BWP, where the default BWP is an initial active BWP indicated from the BS <NUM> during an initial access configuration.

For RLM purposes UE <NUM> chooses a single RS for indicating periodic IS or OOS. For each BWP, UE <NUM> can use RS within that BWP for RLM purposes. This can be used for RLF operations. When the RS is present in some BWP and not the current active BWP (in case of single active BWP), then the UE <NUM> must hop to that BWP for getting the periodic IS and OOS measurements and then declare RLM measurements and RLF. The UE <NUM> can fallback to the default BWP for the case of RLM/ RLF purposes. This is crucial since some BWP may or may not have SS and CSI-RS configured. The gnb <NUM> configures the BWP which UE <NUM> must use for RLM purposes it could be <NUM> per numerology (for all BWP with same numerology) or <NUM> for all possible numerologies. Regardless of same or different RLF parameters per BWP, when BWP is switched UE <NUM> might reset or inherit the # of indications given so far in previous BWP. This behavior can be indicated to UE <NUM> by the gnb <NUM>.

In an embodiment, the RLM engine <NUM> receives a pre-defined location and a size of the initial active BWP for the UL transmission and the DL transmission using Master Information Block (MIB) and a RMSI from the BS <NUM>. The RLM engine <NUM> receives a location of the CORESET configuration in the Physical Broadcast Channel (PBCH) of the SS block (SSB). In an embodiment, the location is received as an offset in Resource Blocks (RBs) using one of a SSB numerology and a RMSI numerology.

In an embodiment, the pairing relationship between the UL BWP and DL BWP is received from the BS <NUM> for Time Division Duplexing (TDD) mode of operation and a Frequency Division Duplexing (FDD) mode of operation.

The relationship may be fixed in specification or indicated by the gnb <NUM>. There could be a fixed frequency dependent relationship between UL and DL where the center/start RB location of the UL and DL BWP can be linked if and only if |fUL-fDL|<threshold. Further, the BS <NUM> can explicitly indicate the association between UL and DL during BWP activation/de-activation via DCI/MAC-CE/RRC is given to the UE. There could be one-one, one-many or many-to-one mapping possible for the same. These could be semi-static mapping changes between UL and DL BWP pairs can be supported via RRC, UE specific higher layer signaling.

In an embodiment, the RLM engine <NUM> receives at least one of a common PRB indexing and a different PRB indexing for a plurality of BWPs in the total bandwidth using the RMSI. In an embodiment, receiving Uplink Physical Resource Block (UL PRB) for the common PRB indexing from the BS <NUM>.

In an embodiment, the RLM engine <NUM> receives frequency locations of the PRB for DL BWP and the UL BWP using at least one of the RMSI and the RRC message. The RLM engine <NUM> receives an offset from Absolute Frequency Channel Number (ARFCN) for Uplink Control Carrier (UL CC) to the PRB for the common PRB indexing. In an embodiment, the CORESET configuration indicates RMSI location as the offset in RBs using a reference SSB numerology and RMSI numerology. In an embodiment, the RMSI location is common across SS block, partially common across SS block and different for each SS block.

In an embodiment, the total bandwidth is a wideband CC includes multiple SSB. In an embodiment, a CORESET size is at least one of a fixed size for initial access and a variable size as indicated in the MIB of the PBCH.

In an embodiment, the communicator <NUM> is configured to communicate with the UE <NUM> and internally between hardware components in the BS <NUM>. In an embodiment, the processor <NUM> is configured to process various instructions stored in the memory <NUM> for handling the RLM using BWP configuration in the wireless communication system.

The memory <NUM> may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory <NUM> may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory <NUM> is non-movable. In some examples, the memory <NUM> can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

Although the <FIG> shows various hardware components of the UE <NUM> but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE <NUM> may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function of handling the RLM in the wireless communication system.

<FIG> is a block diagram illustrating the RLM engine <NUM> of the UE <NUM>, according to an embodiment as disclosed herein. In an embodiment, the RLM engine <NUM> includes a BWP configuration engine <NUM>, an activation/deactivation engine <NUM>, an association engine <NUM>, a retransmission engine <NUM> and a measurement engine <NUM>.

In an embodiment, the BWP configuration engine <NUM> receives BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the BS <NUM>. In an embodiment, the activation/deactivation engine <NUM> detects the active BWP from the BS <NUM> based on the BWP configurations. In an embodiment, the activation/deactivation engine <NUM> performs the RLM on the active BWP using the BWP configurations.

In an embodiment, the activation/deactivation engine <NUM> detects that the active BWP is deactivated from the BS <NUM> based on the BWP configuration. Further, the activation/deactivation engine <NUM> performs the retransmission on the configured active BWP from the plurality of BWPs by recombining a data associated with the deactivated BWP and the configured active BWP using the Hybrid Automatic Repeat Request (HARQ) buffer.

In an embodiment, the activation/deactivation engine <NUM> receives one of the activation of the MAC CE and the deactivation of the MAC CE from the BS <NUM> using the RRC message.

In an embodiment, the BWP configuration engine <NUM> receives the Uplink Bandwidth Part (UL BWP) and the Downlink Bandwidth Part (DL BWP) for each BWPs in the plurality of BWPs. Further, the association engine <NUM> receives the association between the UL BWP and the DL BWP using the RRC message from the BS <NUM>.

In an embodiment, the activation/deactivation engine <NUM> activates the BWP based on the BWP configuration from the BS <NUM>. In an embodiment, the activation/deactivation engine <NUM> receives the activation of a Component Carrier (CC) using the MAC-CE and activation of the BWP inside the CC from the BS <NUM>. Further, the activation/deactivation engine <NUM> tunes to the specific CC and the BWP.

In another embodiment, the activation/deactivation engine <NUM> receives the activation of Component Carrier (CC) and the BWP using the MAC-CE from the BS <NUM>. Further, the activation/deactivation engine <NUM> tunes to the specific CC and the BWP.

In an embodiment, the activation/deactivation engine <NUM> activates one of the single active BWP and the multiple active BWP in the plurality of BWPs of the total bandwidth is based on indicating by the UE <NUM> a capability information to the BS <NUM>. Further, the BWP configuration engine <NUM> receives at least one of a number of soft bits, the soft buffer partitioning, and HARQ process for each BWP during the multiple BWP activation from the BS <NUM> based on the capability information.

In an embodiment, the BWP configuration engine <NUM> receives at least one of the timer value and the maximum number of NACK, and Discontinuous reception (DRx) timer from the BS <NUM> using the MAC Control Element (MAC-CE), the Radio Resource Control (RRC) message, and the Downlink Control Indicator (DCI).

In an embodiment, the BWP configuration engine <NUM> receives the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the BS <NUM> includes receiving the QCL relationship between a Demodulation Reference Signal (DMRS) and at least one reference signal for each BWP during a RRC connection using the Radio Resource Control (RRC) message.

In an embodiment, the BWP configuration engine <NUM> receives the QCL relationship between the Demodulation Reference Signal (DMRS) and the at least one reference signal for the activated BWP using the MAC Control Element (MAC-CE), and the Downlink Control Indicator (DCI) during RRC connection for at least one of activation BWP and deactivation of one BWP among the plurality of BWPs.

In an embodiment, the activation/deactivation engine <NUM> activates the UL BWP and the DL BWP based on receiving the measurement gap for the outside of the configured frequency range of the active BWP from the BS <NUM>.

In an embodiment, the BWP configuration engine <NUM> receives the BWP identity from the plurality of BWPs for performing the RLM. Further, the activation/deactivation engine <NUM> receives one of the default Radio Link Monitoring (RLM) Bandwidth Part (BWP) and Radio Link Monitoring Reference signal (RLM RS) resources for each BWPs.

In an embodiment, the BWP configuration engine <NUM> receives at least one of the default Bandwidth Part (BWP), the current active Bandwidth Part (BWP) for the RLM, and one of Radio Link Monitoring Reference signal (RLM RS) resources for each BWPs and the Radio Link Monitoring Reference signal (RLM RS) resources for the BWP on which RLM to be performed from the BS <NUM>. Further, the BWP configuration engine <NUM> receives interference measurement resources on the BWP on which RLM to be performed from the BS <NUM>.

In an embodiment, the BWP configuration engine <NUM> receives at least one of Control-Resource Set (CORESET) configurations includes the in-sync RLM resources, the QCL relationship information across the each BWP of the plurality of BWPs, and the interference measurement resources for the BWP. Further, the measurement engine <NUM> monitors the in-sync measurement on the at least one of the single active BWP and the multiple active BWP based on the QCL information. Further, the measurement engine <NUM> reports the in-sync measurement for each BWP to the BS <NUM>.

In an embodiment, the BWP configuration engine <NUM> receives the at least one of Control-Resource Set (CORESET) configurations includes the out-of-sync RLM resources, the QCL relationship information across the each BWP of the plurality of BWPs, and the interference measurement resources for the BWP. Further, the measurement engine <NUM> monitors the out-sync measurement and the BWP threshold value on the at least one of the single active BWP and the multiple active BWP based on the QCL information. Further, the measurement engine <NUM> reports the out-sync measurement to the BS <NUM>.

In an embodiment, the BWP configuration engine <NUM> receives the pre-defined location and the size of the initial active BWP for the UL transmission and the DL transmission using Master Information Block (MIB) and the RMSI from the BS <NUM>. The BWP configuration engine <NUM> receives the location of the CORESET configuration in the Physical Broadcast Channel (PBCH) of the SS block (SSB). In an embodiment, the location is received as the offset in Resource Blocks (RBs) using one of the SSB numerology and the RMSI numerology.

In an embodiment, the BWP configuration engine <NUM> receives at least one of the common PRB indexing and the different PRB indexing for the plurality of BWPs in the total bandwidth using the RMSI. In an embodiment, receiving Uplink Physical Resource Block (UL PRB) for the common PRB indexing from the BS <NUM>.

In an embodiment, the BWP configuration engine <NUM> receives frequency locations of the PRB for DL BWP and the UL BWP using at least one of the RMSI and the RRC message. The BWP configuration engine <NUM> receives the offset from Absolute Frequency Channel Number (ARFCN) for Uplink Control Carrier (UL CC) to the PRB for the common PRB indexing.

<FIG> is a flow diagram <NUM> illustrating various operations, implemented on the UE, for handling the RLM using the BWP configurations, according to embodiments as disclosed herein.

At step <NUM>, the method includes receiving the BWP configurations for each BWPs in the plurality of BWPs of the total bandwidth from the BS <NUM> using one of the MAC Control Element (MAC-CE), the Radio Resource Control (RRC) message, and the Downlink Control Indicator (DCI), where the BWP configurations comprising one of a single active BWP and multiple active BWP in the plurality of BWPs. In an embodiment, the method allows the BWP configuration engine <NUM> to receive the BWP configurations for each BWPs in a plurality of BWPs of a total bandwidth from the base station using one of a MAC Control Element (MAC-CE), the Radio Resource Control (RRC) message, and the Downlink Control Indicator (DCI), wherein the BWP configurations comprising one of the single active BWP and multiple active BWP in the plurality of BWPs.

At step <NUM>, the method includes detecting the active BWP based on the BWP configurations from the base station <NUM>. In an embodiment, the method allows the activation/deactivation engine <NUM> to detect the active BWP based on the BWP configurations from the base station <NUM>.

At step <NUM>, the method includes performing the RLM on the active BWP using the BWP configurations. In an embodiment, the method allows the activation/deactivation engine <NUM> to perform the RLM on the active BWP using the BWP configurations.

The various actions, acts, blocks, steps, or the like in the flow diagram <NUM> may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

At step <NUM>, the method includes detecting that the active BWP is deactivated from the base station <NUM> based on the BWP configuration. In an embodiment, the method allows the activation/deactivation engine <NUM> to detect that the active BWP is deactivated from the base station <NUM> based on the BWP configuration.

At step <NUM>, the method includes performing the retransmission on the configured active BWP from the plurality of BWPs by recombining the data associated with the deactivated BWP and the configured active BWP using a Hybrid Automatic Repeat Request (HARQ) buffer. In an embodiment, the method allows the activation/deactivation engine <NUM> to perform the retransmission on the configured active BWP from the plurality of BWPs by recombining the data associated with the deactivated BWP and the configured active BWP using a Hybrid Automatic Repeat Request (HARQ) buffer.

<FIG> illustrates an activation/deactivation of the MAC control element, according to an embodiment as disclosed herein. The activation/Deactivation of the MAC CE involves the following procedure. The MAC CE indicates a mapping between a BWP-ID and an index given by the MAC CE. The mapping is configured in RRC connection configuration message to the UE. The RRC configuration message indicates a size of the MAC CE, since a number of BWP can be changed by the RRC and is done for every reconfiguration of the BWPs for the UE <NUM> in a UE <NUM> specific manner. Otherwise, a maximum bit field size is fixed for all UEs and then zero padded from a Least Significant Bit (LSB) or a Most Significant Bit (MSB) to ensure common design for all different types of the UE.

In an example, as shown in the table <NUM>, if BWPId = <NUM> and BWPIdIndex = <NUM> means that the physical BWPId <NUM> will be activated by using the C1 bit field in the MAC CE.

If X bits are active, then X BWPs are activated.

If multiple BWPs are used only for case of multiple numerology support and, that there is only <NUM> BWP per numerology then, at most three simultaneous BWP activations will be allowed in NR considering # numerology per band. Hence, <NUM> bits are enough to indicate which BWP is activated. For the case when multiple active BWP can be used for same numerology, more bits are needed and the size of this MAC CE depends on the limitations based on all UEs which can support "X" simultaneously active BWP.

The table <NUM> illustrates the mapping of the BWPId Index to BWPId via RRC. The BS is configured to indicate the mapping to the UE, when the BWP is configured or re-configured via the RRC. In an embodiment, the indication can be provided using one of RMSI, DCI and MAC CE. Further, a similar mapping procedure is followed for performing the BWP activation of DL and UL. A different MAC CE for each DL and UL can be sent for the UE <NUM> where each indicated by RRC. The BS can be configured to indicate separate sizes for the DL MAC CE and the UL MAC CE to the UE, as the number of BWP can be different. The indication can be provided using the RMSI, RACH configuration, RRC connection establishment procedure or via RRC signaling in the connected mode.

<FIG> illustrates a method for calculating the UE <NUM> capability in terms of BWP and HARQ technique, according to an embodiment as disclosed herein. The following HARQ procedures may be defined for a case of single and multiple active BWP accordingly. The UE <NUM> is configured to send a capability indication to the BS <NUM>. Upon receiving the capability indication, the BS <NUM> indicates to the UE <NUM> the following behavior via the DCI:.

The BS <NUM> can be configured to indicate the UE <NUM><NUM> a soft buffer partitioning per BWP in case the BS supports multiple active BWP for the UE. In multiple active BWP scenario, different data rates can exist per BWP and each BWP has its own TB even though the number of actually used HARQ processes can be similar/same. As shown in the below table <NUM>, the maximum number of simultaneously active BWP that one UE <NUM> can support can be dependent on the maximum number of HARQ processes depending on the UE <NUM> capability. The UE <NUM> capability is exchanged during RRC CONN setup phase. Then the gnb <NUM> will configure at least one of a total number of soft bits, a soft buffer, maximum number of HARQ processes, maximum number of simultaneously active BWP, soft buffer partitioning handling to the UE.

<FIG> illustrates a channel state in bundling window for downlink BWP with different numerology, according to an embodiment as disclosed herein. When there is multiple active BWP within one CC, then multiple HARQ entities could be defined. Then each HARQ could operate independently. The HARQ codebook could be defined per BWP, per numerology, pooling across numerology. One of the BWP can be defined for PUCCH which carries the HARQ ACK for all BWP belonging to same numerology. The following options can be defined for dynamic HARQ ACK codebook design For a UE <NUM> configured with multiple active BWP with different PDCCH monitoring periodicities (can be the same numerology or different numerology), HARQ-ACK timing can be with respect to one of the configured PDCCH monitoring periodicities. Regardless of FDD or TDD operation, when a first PDCCH monitoring periodicity is P times longer than a second PDCCH monitoring periodicity, for HARQ-ACK codebook determination, the first PDCCH monitoring periodicity corresponds to a bundling window with size of P slots for cells using the second PDCCH monitoring periodicity and operation can resemble the one in LTE for FDD-TDD CA or TDD CA with different UL-DL configurations. As shown in <FIG>, the slot duration is different for two DL BWP. Assuming <NUM> bits in DCI to indicate the HARQ-ACK timing of <NUM>, <NUM>, <NUM> and <NUM> slot (with reference to slots for PUCCH transmissions), and the UE <NUM> is configured to monitor PDCCH in every DL slot on each DL BWP. Then, for a given UL slot, e.g., #<NUM> UL slot, the associated bundling window for DL BWP1 consists of DL slot #<NUM> ~<NUM> and DL slot #<NUM>~#<NUM> for DL BWP2. Although we used the term slots, it could be configured in terms of mini-slots/ symbols.

<FIG> illustrates the channel state to determine HARQ-ACK codebook for a particular group of BWPs, according to an embodiment as disclosed herein. In an embodiment, the use of {Counter DAI, Total DAI, Timing Indication} for HARQ-ACK codebook determination. The counters are maintained for a group of BWPs.

The DAI (Downlink Assignment Index) is an index, which is communicated to UE <NUM> by BS to prevent ACK/NACK reporting errors due to HARQ ACK/NAK bundling procedure performed by the UE. In an embodiment, the Dynamic HARQ ACK codebook determination is desirable for minimizing HARQ-ACK payload and improving resource utilization and coverage. The total Downlink Assignment Index DAI and counter DAI based method from release <NUM> enhanced Carrier Aggregation (eCA) can be a starting point. The DAI is determined or accumulated within a bundling window that can include a variable number of PDSCH transmissions and the last PDSCH transmission can be determined from the HARQ-ACK timing indication in the DCI.

<FIG> illustrates the channel state to determine HARQ-ACK codebook for the particular group of BWPs, according to an embodiment as disclosed herein. In an embodiment, the use of {Counter DAI, Total DAI, Timing Indication} for HARQ-ACK codebook determination. The counters are maintained for all BWPs jointly.

For the operation of a DAI field, BWPs using different PDCCH monitoring periodicities can be divided into respective groups according to the PDCCH monitoring periodicity. A value of a DAI field in a DL DCI format is set with respect to BWPs with same PDCCH monitoring periodicity. Figure x below illustrates an example for the functionality of {Counter DAI, Total DAI, Timing Indication} fields where the Counter DAI and the Total DAI functionality is as for en LTE. Alternatively, the value of DAI is set to the total number of PDCCHs across all scheduled DL BWPs in the order of PDCCH occasion in time domain, as shown in <FIG>. These mechanisms change in the manner DAI is counted a) within a small group of BWPs with some common property or b) for all BWPs together.

<FIG> illustrates a DRx timer determination for the activation and de-activation of the BWP, according to an embodiment as disclosed herein. The timer based activation/de-activation mechanism for BWP as follows:
Based on a timer, the UE <NUM> may monitor smaller BW and wider BW. The smaller BW can be the default BWP where the UE <NUM> will come back based on timer expiry.

<FIG> illustrates a method for DCI indication to the UE, according to an embodiment as disclosed herein. As shown in the <FIG>, a new timer is introduced, in which the new timer is remove the necessity of DCI indication for fallback to default BWP and de-link from DRx concept.

The BS indicates to the UE <NUM> via DCI/MAC/RRC these timers and its values where these timers can be longer length compared to onDuration and dRxlnactivity. This enables for more flexible data traffic adaption. They need not be coupled with DRx. They can be used for full buffer traffic/ video etc. where the data may change to low and high load on and off manner. But this can be by the gnb <NUM> configuration. The gnb <NUM> indicates to UE <NUM> these timers via RRC/ DCI/ MAC-CE and then also indicates the starting of the timer based operations.

<FIG> is an example scenario illustrating a method of DCI-based BWP activation and timer-based fall back mode operation, according to an embodiment as disclosed herein. Consider that one of configured BWPs becomes default BWP which is decided by the gnb <NUM>. Similar to C-DRX timer, an UE <NUM> has a timer which is reset whenever PDCCH is received. If the UE <NUM> doesn't receive any PDCCH until timer is expired, UE <NUM> goes to default BWP and monitors PDCCH again. From the gnb <NUM> perspective, after BWP switching indication, the gnb <NUM> transmits data within configured active BWP. If a certain number of consequent NACK is received, the gnb <NUM> may acknowledge the UE <NUM> misses BWP switching indication. Then, the gnb <NUM> goes to default BWP and resume transmission with the UE. The timer duration and the number of maximum NACK can be configurable via RRC signaling to provide network flexibility.

<FIG> is an example scenario for the BWP configuration, according to an embodiment as disclosed herein.

Initial active BWP Configuration: As shown in the <FIG>, there is no explicit indication of BWP Configuration to the UE <NUM> by the BS. The UE <NUM> is not needed to open its RF BW for more than the RMSI. So if UE <NUM> is such that it opens up minimum, then RMSI BW is minimum BW necessary to finish initial access. The following procedure is identified.

PBCH in SSB indicates CORESET location as offset in RB number using the reference numerology for SS or via the numerology configured for RMSI. The CORESET size could be fixed for initial access in the specification or else, indicate size of CORESET in PBCH MIB. This CORESET indicates RMSI location as offset in RBs again via the reference SSB numerology or in terms of the RMSI numerology. The CORESET indicates RMSI size and allocation via CORESET. Else, fixed size of RMSI BW assumed. Note that all these signaling is from the gnb <NUM> to UE.

<FIG> is an example scenario for the BWP configuration, according to an embodiment as disclosed herein. In an embodiment, the UE <NUM> may not know system BW during initial access stage. Instead, the UE <NUM> can perform initial access by using initial active BWP as shown in <FIG>.

<FIG> illustrate sequence diagrams depicting a signaling message communicated between the BS and UE, according to an embodiment as disclosed herein. The following mechanisms are used for indication of the initial active BWP for the UE <NUM> start or center location and the size. The possible techniques are:.

In an embodiment, the BWP configuration engine <NUM> receives the initial active BWP Indicated via RMSI, in this case, RMSI reception has to be performed by using another mechanism such as PRB offset indication. As shown in the <FIG>, the BS <NUM> indicates the initial active DL BWP to the UE <NUM>.

<FIG> illustrate sequence diagrams depicting the signaling message communicated between the BS and UE, according to an embodiment as disclosed herein. Similar to <FIG>, the BS <NUM> indicates the initial active UL BWP to the UE <NUM>.

<FIG> is a schematic diagram illustrating UL PRB indication for the common PRB indexing, according to an embodiment as disclosed herein. The issue herein is to how to indicate reference point PRB <NUM> for FDD UL:.

<FIG> illustrate sequence diagrams depicting the signaling message communicated between the BS and UE, according to an embodiment as disclosed herein. As shown in the <FIG>, the BS <NUM> indicates RMSI with UL information (ARFCN) and UL PRB <NUM> offset to the UE <NUM><NUM>.

<FIG> illustrate the BWP configuration based on the common PRB indexing, according to an embodiment as disclosed herein.

As shown in the <FIG>, the BS indicates the BWP configuration based on the common PRB indexing is indicated to the UE <NUM><NUM>.

After RRC connection, the UE <NUM> can be configured a set of BWPs by using common PRB indexing.

After RRC conn, UE <NUM> can be configured a set of BWPs by using common PRB indexing.

In another embodiment, for common PRB indexing for FDD UL, in order to indicate where PRB <NUM> is to UE, ARFCN for UL cell can be used. Instead of using the lowest SS block, since FDD UL doesn't have SS block, the gnb <NUM> can indicate an offset from ARFCN for UL cell to PRB <NUM> to UE. This offset information can be contained together in RMSI or indicated to UE <NUM> via RRC signaling at connection setup or in connected mode when this is needed. Then, UE <NUM> can generate UL common PRB indexing with both UL ARFCN and the offset information. Meanwhile, unlike DL, UE <NUM> may have to know right and left most PRB of UL to keep spectrum mask regulation for UL transmission. For the reason, the right most PRB information may be included in RMSI or via RRC (UE specific higher layer signaling) as well. For UL common PRB indexing, an offset from ARFCN for UL CC to PRB <NUM> should be indicated to UE <NUM> via RMSI.

<FIG> are schematic diagram illustrating a method for performing a Random Access channel (RACH) procedure using an initial active BWP configuration considering multiple SSBs, according to an embodiment as disclosed herein.

As shown in the <FIG>, the SSB1 and SSB2 indicate potential locations of the SS blocks inside the WB Carrier and each location can contain multiple physical SS blocks (<NUM> to L-<NUM>) and timing index between them must be same, although physical beams may be different.

As shown in the <FIG>, a RMSI location for all SSB, having common information for all SSB are indicated:.

The proposed method needs retuning to support SSB at different edges.

The common RMSI location can prevent the UE <NUM> from reading SSB at other frequency locations to get cell information for whole WB.

The proposed method can support only if RMSI contents are not SSB location specific i.e., do not carry offset from SSB.

NW resource saving due to avoiding too many RMSI locations.

Prevents the gnb <NUM> flexibility for optimizations on the beam sweeping/ patterns and using some QCL information across beams at different SSB locations.

Too many bits in PBCH to indicate RMSI in some common location.

Common RMSI indicates common RACH configuration.

As shown in the <FIG>, a different RMSI location for each SSB, where the each SSB has its own RMSI.

The UE <NUM> can support different cell-ID in case needed.

As shown in the <FIG> where the UE <NUM> will handle RACH and initial operations based on multiple SSB and multiple RMSI etc..

<FIG> is a flow diagram <NUM> illustrating various operations performed by the UE <NUM> based on the initial active BWP configuration, according to embodiments as disclosed herein.

At step <NUM>, the method includes detecting, by the UE <NUM>, SSB. In an embodiment, the method allows the BWP configuration engine <NUM> to detect the SSB. At step <NUM>, the method includes decoding, by the UE <NUM>, PBCH. In an embodiment, the method allows the BWP configuration engine <NUM> to decode the PBCH from the SSB.

At step <NUM>, the method includes determining, by the UE <NUM>, subcarrier offset of SSB from PRB grid and the RMSI location integer number of PRB in SSB/RMSI numerology. In an embodiment, the method allows the BWP configuration engine <NUM> to determine the subcarrier offset of SSB from PRB grid and the RMSI location integer number of PRB in SSB/RMSI numerology. At step <NUM>, the method includes decoding, by the UE <NUM>, RMSI. In an embodiment, the method allows the BWP configuration engine <NUM> to decode the RMSI.

The following behavior for a NR UE <NUM> can be performed, the behavior includes UE <NUM> receives the SSB, decodes PBCH and obtains information regarding the initial active BWP (RMSI location and the SSB offset from the PRB grid). The RMSI location is found using a) the SSB offset which is needed to align with the PRB grid and b) the RMSI location indicated via PBCH in terms of integer number of Pseudorandom Binary Sequence (PRBs). Depending on the supported UE <NUM> minimum BW, the UE <NUM> may or may not retune to receive RMSI (if the UE <NUM> minimum BW covers both SSB and RMSI, then no retuning is needed; else the UE <NUM> will retune from SSB BW to RMSI BW location).

In an embodiment, the integer number of PRBs indicated by the PBCH can be in terms of the numerology of a) SSB, b) RMSI numerology or c) some reference numerology for the accessed band which will be defined in specification. Otherwise, the location can be indicated as an offset in number of sub-carriers/ exact frequency location.

The location of RMSI can be indicated as follows:.

In an embodiment, the CORESET location inside this RMSI BW can be located at the any of the following:.

The size of CORESET may be fixed in specification, or indicated via PBCH or implicitly derived from some parameters indicated via PBCH.

In an embodiment, in the post RRC connection, a UE <NUM> may be configured with a default BWP which the UE <NUM> may use for all connected mode operations. This default BWP may be UE <NUM> specifically configured to the UE <NUM> by the gNB <NUM> and enables the load balancing purposes for the gnb <NUM> (can also allow for connected mode paging in this BWP). This default BWP may or may not have an SS block (since this is purely for load balancing purposes and for fall back mode of operations), hence the UE <NUM> must be indicated to use the initial BWP for measurement purposes in case the UE <NUM> BW does not include a SSB i.e., for narrow band users retuning may be needed for measurement while for a wideband UE <NUM> the default BWP can be configured to include the SSB as well.

Measurements for RRM: For the case of neighbor cell measurements, it is typically beneficial for the UE <NUM> to assume the presence of SS blocks of the neighbor cell at the same location of serving cell to avoid retuning. However, with the presence of multiple SS blocks, presence of default SS block locations (cell defining SS block) in a wideband carrier per UE, it is necessary to define a fool proof mechanism for the measurements.

In general as in 3GPP standard, to make the UE <NUM> measurement behaviour clear, the UE <NUM> should be indicated with one specific SSB in the UE's serving cell which is used for measurement for mobility purpose in multiple SSBs scenario. Further, it is mentioned that "A measurement is defined as a SSB based intra-frequency measurement provided the centre frequency of the SSB of the serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs are also the same. " Else, it is defined as inter-frequency measurement when either the centre frequency or the SCS of the SSBs are different.

Based on these, the proposed method can be concluded that the cell-defining SSB can be used for mobility purposes. Furthermore, the proposed method can be concluded that a single SSB BW is used for measurement purposes. The proposed method must be mandated for the UE <NUM> to use one SSB BW for measurements. Which SSB the UE <NUM> uses can be.

When CSI-RS is also present, the following combinations may be possible and must be further studied if they should be considered or not:.

SSB locations for WB carrier: From a network perspective, SSB can be located at any location on the SS frequency raster within the wideband CC. Also it is preferred that a UE <NUM> finds only one SSB within its BW during the course of initial cell selection to avoid any confusion about the SSB strength and location. Therefore, it is preferred that the SSB BW do not overlap in frequency. Hence in a wideband carrier, the number of SSB could depend on the network bandwidth and the UE <NUM> minimum BW. Further considering the FDM of RMSI and SSB, the SSB locations should be appropriately spaced apart.

In an embodiment, some of the SSB may be located off the SS-raster i.e., say in sub-carrier offset. These will not be found by UE <NUM> during normal mode of operation. Will be configured by network on-demand. This is used for additional measurement accuracy within a wideband carrier.

Quasi-colocation (QCL) Assumption across multiple SSB in frequency: The following options can be considered for the case of QCL across multiple SSB in frequency domain:.

During RRC configuration of BWP, the UE <NUM> may be indicated the relationship between BWPs and the SSB. This helps UE <NUM> to understand which BWP can rely on which SSB for DL synch measurements. Same can be followed for the case of UL RACH and using of TA values.

SS block to RMSI Mapping: It is agreed that cell-defining SSB has an RMSI associated with it for all <NUM> systems. However, it is still under discussion as to whether this mapping is one-to-one or many-to-one. Many-to-one RMSI mapping can be considered in NR to reduce the network signaling overhead for RMSI.

In NR, the following RMSI-SSB mapping can be considered:.

The type of association is network implementation. However this can be done depending on how the SSB indices are designed by the gnb <NUM> and how they are behaving across the frequency locations and if they can share the same RMSI (PRACH configuration for example since UL should perform PRACH on same type of beams).

For case (b) and case (c), some more consideration is needed especially regarding common PRB indexing which is done on the entire wideband carrier. Options (b) and (c) should be supported form network side to reduce RMSI network overhead. Then RMSI must indicate PRACH configuration supported for multiple SSB in frequency. This indicates that the multiple SSB with same indices but in different frequency locations must be QCL'ed. Hence, only when such QCL is known to be possible from network implementation, the gnb <NUM> can decide to provide such many-to-one and many-to-many mapping between SSB and RMSI.

For common PRB indexing, since different UE <NUM> may find different cell-defining SSB, indication of the offset from PRBO to the lowest PRB of the SSB accessed by the UE <NUM> via RMSI is not feasible. Since different SSB will need different offset indications for the purpose of indexing. This indexing may be useful for OSI, paging etc. Furthermore, UE <NUM> must explicitly indicate the SSB location to the gnb <NUM> during the RRC connection establishment procedure so that the gnb <NUM> can indicate the appropriate offset to the UE. Therefore, UE <NUM> specific signaling of the offset indication/SSB frequency location should be considered in NR. If RMSI indication is deemed necessary, the offset must be from PRBO to the lowest PRB of the RMSI which is common across multiple SSBs must be supported. Thus common PRB indexing can be done in cases (b) and (c) as follows:.

Common PRB indexing without SSB:For common PRB indexing for carrier without SSB such as FDD UL carrier and Scell without SSB, in order to indicate where PRB <NUM> is to UE, ARFCN for the carrier can be a good option for start position to indicate offset to PRB <NUM>. If PRB grid is center-oriented and always aligned with center of carrier regardless of numerology, ARFCN is very appropriate to indicate offset to PRB <NUM> in terms of PRB level. This offset information can be additionally contained in system information for FDD UL or RRC reconfiguration message for Scell addition. On the contrary, if PRB grid is not aligned with ARFCN due to odd number of PRBs or other reasons, subcarrier spacing level offset should be added on PRB level offset similar to indication to resolve floating synch issue.

Lack of PRB numbers for common PRB indexing: According to bandwidth part related agreement in RAN1 #<NUM> meeting, common PRB index is for maximum number of PRBs for a given numerology defined in 3GPP standard. Since maximum number of PRBs is decided to <NUM> PRBs i.e., <NUM> subcarriers, currently, considering different subcarrier spacing, bandwidth spanned by common PRB indexing will be different depending on which SCS is used. Therefore, as shown below figure, a UE <NUM> cannot be configure d a bandwidth part with lower subcarrier spacing, SCS <NUM> outside its common PRB indexing due to PRB number limitation. To resolve this issue, combinations of PRB indexing per numerology can be used. For example, PRB <NUM> with SCS <NUM> can be expressed as PRB <NUM> with SCS <NUM> + PRB <NUM> with SCS <NUM>. The information can be contained when bandwidth parts are configured to a UE via RRC signaling.

The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in the <FIG> include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

Claim 1:
A method executed by a base station (<NUM>) in a wireless communication system, the method comprising:
transmitting, to a user equipment, UE, (<NUM>) a master information block, MIB, including initial downlink bandwidth part, BWP, configuration information;
transmitting, to the UE, remaining minimum system information, RMSI, including initial uplink BWP configuration information; and
transmitting, to the UE, radio resource control, RRC, message including BWP configuration information, the BWP configuration information comprising information on an uplink BWP and information on a downlink BWP,
wherein the RMSI is transmitted based on the initial downlink BWP configuration information, and
wherein association between the uplink BWP and the downlink BWP is indicated by the RRC message, the association comprising a pairing relationship between the uplink BWP and the downlink BWP.