Method and device for monitoring wake-up signal

Abstract

The present disclosure relates to a communication method and system for aggregating a fifth generation (5G) communication system, which utilizes Internet of Things (IoT) technology to support higher data rates than fourth generation (4G) systems. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, health care, digital education, smart retail, security and safety services. A method and apparatus for monitoring a wake-up signal and a method and apparatus for protecting unicast V2X communication are provided.

Description

Technical Field

[0001] The present invention relates to a wireless communication system. More specifically, the present disclosure relates to an apparatus, method and system for monitoring a wake-up signal (WUS) in a wireless communication system. In addition, the present disclosure relates to an apparatus, method and system for protecting unicast vehicle-to-everything (V2X) communication in a wireless communication system. Background Art

[0002] In order to meet the demand for wireless data services that has increased since the deployment of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) or quasi-5G communication system. Therefore, 5G or quasi-5G communication systems are also referred to as "post-4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mm wave)) bands, such as the 60GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, in 5G communication systems, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed. In addition, in 5G communication systems, development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. is underway. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] The Internet is a human-centered connectivity network where humans generate and consume information, and is now developing into the Internet of Things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) is an Internet where IoT technology and big data processing technology are combined through connection with cloud servers. Technology elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" have recently been studied for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. This IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart devices and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.

[0005] Meanwhile, WUS in 5G communication systems has been studied in many aspects recently. In addition, there is a recent need to enhance V2X communication in various ways.

[0006] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination or assertion is made as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0007] [Technical issues]

[0008] Recently, there is a need to enhance WUS in 5G communication systems. Moreover, V2X communication needs to be enhanced in various ways.

[0009] [Solution to the problem]

[0010] Aspects of the present disclosure address at least the above-mentioned problems and / or disadvantages and provide at least the advantages described below. Therefore, one aspect of the present invention is to provide a communication method and system for aggregating a fifth generation (5G) communication system to support higher data rates than the fourth generation (4G).

[0011] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0012] According to one aspect of the present invention, a method performed by a terminal is provided. The method includes receiving a radio resource control (RRC) message from a base station, the RRC message including a physical downlink control channel (PDCCH) configuration for a downlink bandwidth part (BWP) of a serving cell, the PDCCH configuration including search space configuration information and control resource set (CORESET) configuration information, wherein the search space configuration of the search space configuration information corresponds to the CORESET of the CORESET configuration information, and the search space configuration includes information for a wake-up signal (WUS), identifying a PDCCH monitoring opportunity of the WUS based on the search space configuration and the CORESET, and receiving downlink control information including the WUS from the base station by monitoring the PDCCH monitoring opportunity, wherein the downlink control information is received based on a power saving radio network temporary identifier (PS-RNTI) common to the BWP of the serving cell.

[0013] According to another aspect of the present disclosure, a method performed by a base station is provided. The method includes sending a radio resource control (RRC) message to a terminal, the RRC message including a physical downlink control channel (PDCCH) configured radio resource control (RRC) message for a downlink bandwidth part (BWP) of a serving cell, the PDCCH configuration including search space configuration information and control resource set (CORESET) configuration information, wherein the search space configuration of the search space configuration information corresponds to the CORESET of the CORESET configuration information, and the search space configuration includes information for a wake-up signal (WUS), and in a PDCCH monitoring opportunity of the WUS identified by the search space configuration and the CORESET, sending downlink control information including the WUS to the terminal, wherein the downlink control information is sent based on a power saving radio network temporary identifier (PS-RNTI) common to the BWP of the serving cell.

[0014] According to another aspect of the present disclosure, a terminal is provided. The terminal includes: a transceiver configured to send and receive signals; a controller configured to send and receive signals; and the controller is configured to: receive a radio resource control (RRC) message from a base station, the RRC message including a physical downlink control channel (PDCCH) configuration for a downlink bandwidth part (BWP) of a serving cell, the PDCCH configuration including search space configuration information and control resource set (CORESET) configuration information, wherein the search space configuration of the search space configuration information corresponds to the CORESET of the CORESET configuration information, and the search space configuration includes information for a wake-up signal (WUS), identify a PDCCH monitoring opportunity of the WUS based on the search space configuration and the CORESET, and receive downlink control information including the WUS from the base station by monitoring the PDCCH monitoring opportunity, wherein the downlink control information is received based on a power saving radio network temporary identifier (PS-RNTI) common to the BWP of the serving cell.

[0015] According to another aspect of the present disclosure, a base station is provided. The base station includes: a transceiver configured to send and receive signals; a controller configured to send and receive signals; and the controller configured to: send a radio resource control (RRC) message to a terminal, the RRC message including a physical downlink control channel (PDCCH) configuration for a downlink bandwidth part (BWP) of a serving cell, the PDCCH configuration including search space configuration information and control resource set (CORESET) configuration information, wherein the search space configuration of the search space configuration information corresponds to the CORESET of the CORESET configuration information, and the search space configuration includes information for a wake-up signal (WUS), and in a PDCCH monitoring opportunity based on the search space configuration and the WUS identified by the CORESET, send downlink control information including the WUS to the terminal, wherein the downlink control information is sent based on a power saving radio network temporary identifier (PS-RNTI) common to the BWP of the serving cell.

[0016] Other aspects, advantages, and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description in conjunction with the accompanying drawings, which discloses various embodiments of the present disclosure.

[0017] [Beneficial Effects of the Invention]

[0018] According to various embodiments of the present disclosure, WUS in a 5G communication system can be effectively enhanced. In addition, according to various embodiments of the present disclosure, V2X communication can be developed in various ways. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0020] Figure 1A An example of a discontinuous reception (DRX) cycle in a radio resource control (RRC) connected state of a next generation radio (NR) according to an embodiment of the present disclosure is shown;

[0021] Figure 1B shows an example of an on-duration and a wake-up signal (WUS) according to an embodiment of the present disclosure;

[0022] Figure 1C An example of determining a physical downlink control channel (PDCCH) monitoring opportunity for a wake-up signal (WUS) according to an embodiment of the present disclosure is shown;

[0023] Figure 1D Another example of determining a PDCCH monitoring opportunity of a WUS according to an embodiment of the present disclosure is shown;

[0024] Figure 1E Another example of determining a PDCCH monitoring opportunity of a WUS according to an embodiment of the present disclosure is shown;

[0025] Figure 1F Another example of determining a PDCCH monitoring opportunity of a WUS according to an embodiment of the present disclosure is shown;

[0026] Figure 1G is a block diagram of a terminal according to an embodiment of the present disclosure;

[0027] Figure 1H is a block diagram of a base station according to an embodiment of the present disclosure;

[0028] Figure 2A An example of a Next Generation Radio Access Network (NG-RAN) architecture associated with a PC5 interface according to an embodiment of the present disclosure is shown;

[0029] Figure 2B shows an example of different layers of security keys according to an embodiment of the present disclosure;

[0030] Figure 2C An example of establishing security keys during connection establishment and key update procedures according to an embodiment of the present disclosure is shown;

[0031] Figure 2D Another example of establishing security keys during connection establishment and key update procedures according to an embodiment of the present disclosure is shown;

[0032] Figure 2EAn example of the use of an integrity algorithm according to an embodiment of the present disclosure is shown;

[0033] Figure 2F An example of the use of an encryption algorithm according to an embodiment of the present disclosure is shown;

[0034] Figure 2G An example of multiple unicast links between user equipment (UE) associated with vehicle-to-everything (V2X) according to an embodiment of the present disclosure is shown;

[0035] Figure 2H An example of a security key hierarchy according to an embodiment of the present disclosure is shown;

[0036] Fig.2I Another example of a security key according to an embodiment of the present disclosure is shown;

[0037] Figure 2J Another example of a security key hierarchy according to an embodiment of the present disclosure is shown;

[0038] Figure 2K An example of a medium access control (MAC) protocol data unit (PDU) structure including a link identifier (ID) according to an embodiment of the present disclosure is shown;

[0039] Figure 2L Another example of a MAC PDU structure including a link ID according to an embodiment of the present disclosure is shown;

[0040] Figure 2M is a block diagram of a terminal according to an embodiment of the present disclosure; and

[0041] Figure 2N is a block diagram of a base station according to an embodiment of the present disclosure.

[0042] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

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

[0044] The terms and words used in the following description and claims are not limited to the bibliographic meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for limiting the disclosure defined by the attached claims and their equivalents.

[0045] It is to 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.

[0046] The term "substantially" means that the features, parameters or values ​​described need not be achieved precisely, 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 eliminate the effects that the features are intended to provide.

[0047] Those skilled in the art know that the combination of the blocks of the flowchart (or sequence diagram) and the flowchart 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 loaded program instructions are executed by the processor, they create a device for performing the functions described in the flowchart. Because the computer program instructions can be stored in a computer-readable memory that can be used for a special-purpose computer or a programmable data processing device, it is also possible to create an article that performs the functions described in the flowchart. 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 operations of the functions described in the flowchart.

[0048] The blocks of the flow chart 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 an order different from the order listed. For example, two blocks listed in sequence may be executed simultaneously or in reverse order.

[0049] In this specification, the words "unit", "module", etc. may refer to software components or hardware components, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) capable of performing a function or operation. However, "unit", 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 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, and 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.

[0050] 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.

[0051] 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), Node B (NB), evolved NB (eNB), access point (AP), 5G NB (5G NB), or next-generation Node B (gNB).

[0052] A “UE” is an entity communicating with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.

[0053] Embodiment 1 - Apparatus and method for monitoring a wake-up signal

[0054] In recent years, several broadband wireless technologies have been developed to meet the increasing 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 the mobility of users. 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 has the disadvantage of lacking resources to meet the growing demand for high-speed data services. Therefore, the fifth generation of wireless communication systems are being developed to meet the growing demand for high-speed data services, supporting ultra-reliability and low latency applications.

[0055] The fifth generation of wireless communication systems will be implemented not only in lower frequency bands, but also in higher frequency (mm wave) bands, such as 10 GHz to 100 GHz bands, in order to achieve higher data rates. In order to reduce 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 massive antenna technology are considered in the design of the fifth generation of wireless communication systems. In addition, the fifth generation of wireless communication systems is expected to solve different use cases with 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 of wireless communication systems will be flexible enough to serve UEs with completely different capabilities, depending on the use cases and market segments that the UE serves for end customers. Several exemplary use cases that the fifth generation of wireless communication systems are expected to solve are enhanced mobile broadband (eMBB), massive machine type communication (m-MTC), ultra-reliable low latency communication (URLL), etc. eMBB requirements (such as tens of Gbps data rates, low latency, high mobility, etc.) address the market segment representing wireless broadband users who need Internet connectivity anywhere, all the time and on-the-go. m-MTC requirements such as very high connection density, infrequent data transfers, very long battery life, low mobility addresses the market segment representing the Internet of Things (IoT) / Internet of Everything (IoE), foreseeing connectivity of billions of devices. URLL requirements such as very low latency, very high reliability and variable mobility address the market segment representing industrial automation applications, with vehicle-to-vehicle / vehicle-to-infrastructure communications foreseen as one of the enablers for autonomous vehicles.

[0056] In the fifth generation wireless communication system operating in the higher frequency (mm wave) band, the UE and the gNB communicate with each other using beamforming. Beamforming technology is used to mitigate propagation path loss and increase the propagation distance for communication on the higher frequency band. Beamforming enhances the transmission and reception performance using high-gain antennas. Beamforming can be classified 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 using multiple antennas to allow the area reached by propagation to be densely located in a specific direction.

[0057] In this case, the aggregation of multiple antennas can be referred to as an antenna array, and each antenna included in the 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, and the like. The use of TX beamforming results in an increase in signal directivity, thereby increasing the propagation distance. In addition, since the signal is hardly transmitted in directions other than the directivity direction, the signal interference acting on the other 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 the RX signal transmitted in a specific direction by allowing the 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 an effect of blocking interference signals.

[0058] 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 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 to 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 RX beam patterns in different directions. Each of these receive patterns can also be referred to as an RX beam.

[0059] The fifth generation wireless communication system (also known as the next generation radio or NR) supports independent operation mode as well as dual connectivity (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or NBs) connected via a non-ideal backhaul. One node acts as a master node (MN) and the other node acts as a secondary node (SN). The MN and the SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports multi-RAT dual connectivity (MR-DC) operation, whereby a UE under RRC connection (RRC_CONNECTED) is configured to utilize radio resources provided by two different schedulers, which are located in two different nodes connected via a non-ideal backhaul and provide E-UTRA (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access) (ie, if the node is ng-eNB) or NR access (ie, if the node is gNB). In the NR of a UE under RRC connection (RRC_CONNECTED) without carrier aggregation (CA) / DC configured, only one serving cell includes a primary cell. For UEs in an RRC connection (RRC_CONNECTED) configured with CA / DC, the term "serving cell" is used to refer to a set of cells including a specific cell and all secondary cells. In NR, the term Master Cell Group (MCG) refers to a set of serving cells associated with a master node, which includes a primary cell (PCell) and optionally one or more secondary cells (SCells). In NR, the term Secondary Cell Group (SCG) refers to a serving cell group associated with a secondary node, which includes a primary SCG cell (PSCell) and optionally one or more SCells. In NR, PCell refers to a serving cell in an MCG operating on a primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. In NR for UEs configured with CA, an Scell ​​is a cell that provides additional radio resources on top of a specific cell. PSCell refers to a serving cell in an SCG, where the UE performs random access when performing a reconfiguration with a synchronization procedure. For dual connectivity operations, the term SpCell (i.e., specific cell) refers to the PCell of an MCG or the PSCell of an SCG, otherwise the term specific cell refers to the PCell.

[0060] In the fifth generation wireless communication system (also known as next generation radio or NR), the next generation Node B (gNB) or base station in the cell broadcast synchronization signal and physical broadcast channel (PBCH) block (SSB) consists of the primary synchronization signal (PSS) and the secondary synchronization signal (SSS) and system information. The system information includes the common parameters required for communication in the cell. In the fifth generation wireless communication system (also known as next generation radio or NR), the system information (SI) is divided into a master information block (MIB) and multiple system information blocks (SIBs), where:

[0061] -MIB is always transmitted on PBCH with a period of 80ms, repeated within 80ms, and includes the parameters required to obtain SIB1 from the cell;

[0062] - SIB1 is transmitted on the downlink shared channel (DL-SCH) with a periodicity of 160ms and variable transmission repetition. The default transmission repetition period of SIB1 is 20ms, but the actual transmission repetition period is network-implemented. SIB1 includes information about the availability and scheduling of other SIBs (e.g., mapping of SIBs to SI messages, periodicity, SI window size), with an indication of whether one or more SIBs are provided only on demand, and the configuration required for the UE to perform the SI request in this case. SIB1 is a cell-specific SIB;

[0063] The SIBs except SIB1 are carried in the System Information (SI) message, which is sent on the DL-SCH. Only SIBs with the same period can be mapped to the same SI message.

[0064] In the fifth generation wireless communication system (or NR), the physical downlink control channel (PDCCH) is used to schedule downlink (DL) transmission on the physical downlink shared channel (PDSCH) and uplink (UL) transmission on the physical uplink shared channel (PUSCH), wherein the downlink control information (DCI) on the PDCCH includes: downlink allocation including at least the modulation and coding format, resource allocation, and hybrid automatic repeat request HARQ information associated with the DL-SCH; uplink scheduling includes at least the modulation and coding format, resource allocation and hybrid ARQ information related to the uplink shared channel (UL-SCH). In addition to scheduling, PDCCH can 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 a time slot format; notification of one or more UEs of a physical resource block (PRB) and an orthogonal frequency division multiplexing (OFDM) symbol where the UE can assume that no transmission is intended for the UE; transmission of transmit power control (TPC) commands for the physical uplink control channel (PUCCH) and PUSCH; transmission of one or more TPC commands for sounding reference signal (SRS) transmissions by one or more UEs; switching of the active bandwidth portion of a UE; and initiation of a random access procedure.

[0065] The UE monitors a set of PDCCH candidates in the configured monitoring opportunities 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 an on-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 includes 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. Interleaved and non-interleaved CCE to REG mapping are supported in the CORESET. Polarity coding is used for PDCCH. Each resource element group carrying PDCCH carries its own demodulation reference signal (DMRS). Quadrature phase shift keying (QPSK) modulation is used for PDCCH.

[0066] In NR, a list of search space configurations is signaled by the gNB for each configured bandwidth part (BWP), where each search configuration is uniquely identified by an identifier. The search space configured identifiers for specific purposes (e.g., paging reception, SI reception, random access response (RAR) reception) are explicitly signaled by the gNB. In the NR search space configuration, the parameters Monitoring-periodicity-PDCCH-slot, Monitoring-offset-PDCCH-slot, Monitoring-symbols-PDCCH-within-slot, and On-Duration are included. The UE uses the parameters PDCCH monitoring period (Monitoring-periodicity-PDCCH-slot), PDCCH monitoring offset (Monitoring-offset-PDCCH-slot) and PDCCH monitoring pattern (Monitoring-symbols-PDCCH-within-slot) to determine the PDCCH monitoring opportunity within the time slot. The PDCCH monitoring opportunity exists in the time slot x to x+on duration, where the time slot with number x in the radio frame with number y satisfies the following equation 1:

[0067] (y*(number of slots in a radio frame)+x-Monitoring-offset-PDCCH-slot)mod(Monitoring-periodicity-PDCCH-slot)=0; Equation 1

[0068] The starting symbol of the PDCCH monitoring opportunity in each slot with a PDCCH monitoring opportunity is given by Monitoring-symbols-PDCCH-within-slot. The length of the PDCCH monitoring opportunity (in symbols) is given in a set (corset) associated with the search space. The search space configuration includes an identifier of the CORESET configuration associated with it. A list of CORESET configurations for each configured BWP is signaled by the gNB, where each CORESET configuration is uniquely identified by an identifier. Note that each radio frame has an on-duration of 10ms. A radio frame is identified by a radio frame number or a system frame number. Each radio frame includes a number of slots, where the number of slots in a radio frame and the duration of the slots depend on the subcarrier spacing. The number of slots in a radio frame and the duration of the slots depend on the radio frame for each supported subcarrier spacing (SCS) predefined in the NR. Each CORESET configuration is associated with a TCI (Transmission Configuration Indicator) state list. Each TCI state is configured with a DL Reference Signal (RS) Identifier (ID) (SSB or Channel State Information Reference Signal (CSI-RS)). The TCI state list corresponding to the CORESET configuration is sent by the gNB via RRC signaling. A TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB to transmit PDCCH in the PDCCH monitoring search space opportunities (the DL TX beam is quasi-collocated (QCLed) with the SSB / CSI RS of the TCI state).

[0069] In NR, bandwidth adaptation (BA) is supported. With BA, the UE's receive and transmit bandwidth does not have to be as large as the cell's bandwidth 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).

[0070] BA is achieved by configuring BWPs for RRC connected UEs and telling the UE which of the configured BWPs is currently active. 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 always one active UL and DL BWP at any point in time. BWP switching for serving cells is used to activate inactive BWPs and deactivate active BWPs each time. BWP switching is controlled by the PDCCH indicating a downlink allocation or uplink grant, by the bwp-Inactivity timer, by RRC signaling or by the media access control (MAC) entity itself when the random access procedure is initiated. When adding a SpCell or activating an SCell, the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, respectively, are active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP for the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL. When the BWP inactivity timer expires, the UE switches the active DL BWP to the default DL BWP or the initial DL BWP (if no default DL BWP is configured).

[0071] Figure 1A An example of a discontinuous reception (DRX) cycle in an RRC connected state of NR according to an embodiment of the present disclosure is shown.

[0072] refer to Figure 1AIn NR, a UE in an RRC connected state may be configured with discontinuous reception (DRX). The DRX cycle consists of an "on duration" and a "DRX cycle". During the "on duration", the UE should monitor the scheduling channel, i.e., the PDCCH, and during the "DRX cycle", the UE may skip monitoring the PDCCH addressed to certain RNTIs in order to save battery. The MAC entity in the UE may be configured by an RRC with a DRX function, which controls the UE's PDCCH monitoring activity, which is used for the C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI of the MAC entity.

[0073] In the DRX cycle, the on-duration is the on-duration during which the UE waits to receive the PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE remains awake and starts the inactivity timer. The inactivity timer is the on-duration during which the UE waits for the successful decoding of the PDCCH from the last successful decoding of the PDCCH. If the decoding fails, the UE can return to sleep. The UE will restart the inactivity timer after a single successful decoding of the PDCCH used only for the first transmission (i.e. not for retransmission). The active time in the DRX cycle is the total on-duration during which the UE monitors the PDCCH. This includes the "on-duration" of the DRX cycle, the time when the UE performs continuous reception and the inactivity timer has not expired, and the time when the UE performs continuous reception while waiting for a retransmission opportunity.

[0074] The serving cells can be configured by RRC in two groups. When RRC does not configure a secondary DRX group, there is only one DRX group. When two DRX groups are configured, each serving cell group called a DRX group is configured by RRC with its own set of parameters: drx-onDurationTimer and drx-InactivityTimer. When two DRX groups are configured, the two groups share the following parameter values: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerULTimer.

[0075] When the DRX cycle is configured, the active time of the service cells in the DRX group includes the following time: the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any service cell in the DRX group; or the raContentionResolutionTimer or msgB-ResponseWindow is running; or a scheduling request is being sent on the PUCCH and the scheduling request is suspended; or after successfully receiving a random access response for a random access preamble that the MAC entity did not select in the contention-based random access preamble, no PDCCH indicating a new transmission of the C-RNTI addressed to the MAC entity is received.

[0076] The UE may be configured to have a short DRX cycle and a long DRX cycle. When drx-InactivityTimer expires, if a short DRX cycle is configured: After the drx-InactivityTimer expires, the UE starts or restarts the drx-ShortCycleTimer in the first symbol and uses the short DRX cycle. If no short DRX cycle is configured, the UE uses the long DRX cycle. When drx-ShortCycleTimer expires: The UE uses the long DRX cycle.

[0077] If a DRX Command MAC CE is received by the UE and if a short DRX cycle is configured: the UE starts or restarts the drx-ShortCycleTimer in the first symbol after the end of the DRX Command MAC CE reception and uses a short DRX cycle. If the UE receives a DRX Command MAC CE and if a short DRX cycle is not configured, the UE uses a long DRX cycle. If a long DRX Command MAC CE is received: the UE stops the drx-ShortCycleTimer and uses a long DRX cycle.

[0078] If a short DRX cycle is used, and [(SFNX10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle): drx-onDurationTimer starts from the start of the subframe after drx-SlotOffset. If a long DRX cycle is used, and [(SFNX10) + subframe number] modulo (drx-LongCycle) = drx-StartOffset, drx-onDurationTimer starts from the start of the subframe after drx-SlotOffset.

[0079] Figure 1B An example of on-duration and wake-up signaling (WUS) according to an embodiment of the present disclosure is shown.

[0080] Reference Figure 1B , in order to further enhance UE power saving, wake-up signaling (WUS, 1b-20) is discussed in Release 16 of the NR standard. For WUS, the UE monitors the PDCCH addressed to the Power Save Radio Network Temporary Identifier (PS-RNTI). The PS-RNTI is signaled to the UE by the gNB. The same PS-RNTI can be assigned to several UEs. The UE monitors the WUS before the start of the on-duration. The WUS indicates whether the UE needs to wake up to monitor the PDCCH at the next occurrence of the on-duration.

[0081] The search space configuration for WUS monitoring is indicated by the gNB. The UE monitors the last PDCCH monitoring opportunity before the on-duration, or the UE monitors the last PDCCH monitoring opportunity that is at least offset from the on-duration (1b-10). The UE assumes that in the PDCCH monitoring opportunity of the UE for WUS monitoring, the PDCCH is sent by the gNB according to the activated TCI state (i.e. beam). The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated to the UE by the gNB. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission in the PDCCH monitoring opportunity of the search space (the DL TX beam is QCLed using the SSB / CSI RS of the TCI state).

[0082] In a cell, a UE monitoring a WUS in a cell may be located in the coverage areas of different beams. Therefore, the network must ensure that the WUS monitoring timings (i.e., the PDCCH monitoring timings (PMOs) of the UEs for WUS monitoring) in different beams are different. UEs in the coverage areas of different beams may be assigned different search space configurations so that the PMOs configured by each search space configuration do not overlap. UEs in the coverage areas of different beams may be configured to have different offsets. When the UE is in the coverage areas of different beams, different start times of the on-duration period may be configured. The problem is that the gNB needs to perform RRC reconfiguration whenever the UE is relocated to the coverage area of ​​a different beam. This may result in significant signaling overhead and additional wake-up time to receive the reconfiguration message. A system and method are needed to overcome this problem.

[0083] Example 1-1

[0084] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0085] 1. The UE receives the search space configuration of WUS from the gNB.

[0086] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in the list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier for the WUS or by including a field in the search space configuration that indicates the DCI format for the WUS may be monitored in the search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration for the WUS is indicated in the search space configuration of the WUS.

[0087] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell. In one embodiment, a MAC control element (CE) can be used to indicate the search space identifier of WUS to the UE.

[0088] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0089] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0090] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell in which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0091] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0092] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0093] If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0094] 3.UE receives the offset of WUS from gNB.

[0095] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the offset is common to all configured BWPs of the serving cell. In an alternative embodiment, the offset is BWP-specific, i.e., signaled separately for each configured BWP. The offset may be provided for all configured BWPs or for some configured BWPs.

[0096] If the offset for WUS is BWP-specific, the UE uses that offset in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH for WUS. Otherwise, the UE shall use the offset of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH for WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the offset for WUS is signaled only for the serving cells in which the UE needs to monitor WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled.

[0097] In one embodiment, the offset indicates the time before the on-duration that the UE starts monitoring the PDCCH to detect the WUS.The UE monitors the PDCCH monitoring occasions in the time slots indicated by the duration field of the search space configuration for the WUS.

[0098] 4. Alternatively, among the PDCCH monitoring opportunities configured by the search space of the WUS, the latest "N" PDCCH monitoring opportunities that are at least "offset" before the On Duration are numbered sequentially.

[0099] A. The number may start from the first PDCCH monitoring opportunity "offset" from at least the on-duration until at least the Nth PDCCH monitoring opportunity "offset" from the on-duration. Alternatively, the number may start from the Nth PDCCH monitoring opportunity "offset" from at least the on-duration until at least the first PDCCH monitoring opportunity "offset" from the on-duration.

[0100] B. Note that these "N" PDCCH monitoring opportunities may be in one slot or multiple slots (contiguous or non-contiguous), depending on the search space configuration parameters.

[0101] C. In one embodiment, "N" is the total number of TCI states in the TCI state list of the CORESET or CORESET configuration of the WUS.

[0102] D. In an alternative embodiment, N is configured as N<=the total number of TCI states in the TCI state list.

[0103] E. In one embodiment, in a time division duplex (TDD) cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that do not overlap with the UL symbols and are at least offset before the on-duration are numbered sequentially. In other words, in the valid PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that are at least "offset" before the on-duration are numbered sequentially.

[0104] i. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0105] F. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with UL symbols or flexible symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that do not overlap with UL symbols or flexible symbols and are at least offset before the on-duration are numbered sequentially. In other words, in the valid PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that are at least "offset" before the on-duration are numbered sequentially.

[0106] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0107] Alternatively, if in the first Ts slot indicated by the Duration field of the WUS search space configuration f, the On Duration starts at slot "X" and is between slot X-Offset and slot X-1, or, if no duration is provided, the On Duration is in slot T S =1, the PDCCH monitoring opportunities are numbered sequentially.

[0108] Alternatively, if the OnDuration starts in slot X, then the valid PDCCH monitoring opportunities of the WUS are numbered sequentially starting from slot X-Offset, before the OnDuration.

[0109] 5. If the i-th TCI state is active in the TCI state list configured by the CORSET or CORESET of the WUS, the UE monitors the i-th PDCCH monitoring opportunity of the WUS (i.e., the i-th PDCCH monitoring opportunity in the PDCCH monitoring opportunity numbered in operation 4), where i = 1, 2, ... N. The activated TCI state is signaled to the UE by the gNB using MAC CE.

[0110] A. The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission (the DL TX beam is QCLed using the SSB / CSI-RS of the TCI state).

[0111] Figure 1C An example of determining a physical downlink control channel (PDCCH) monitoring opportunity of a WUS according to an embodiment of the present disclosure is shown.

[0112] refer to Figure 1C, in Example 1-1, there are 4 TCI states in the TCI state list. There is one PDCCH monitoring opportunity in a time slot, and 2 consecutive time slots of PDCCH monitoring opportunities with WUS occur every 10 time slots (1c-10). Therefore, the last 4 PDCCH monitoring opportunities (1c-20) that are "offset" at least before the connection duration (1c-30) are numbered in sequence. If the first TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 1 (1c-20). If the second TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 2 (1c-20). If the third TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 3 (1c-20). If the fourth TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 4 (1c-20). The UE performs this operation before each connection duration.

[0113] Example 1-2

[0114] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0115] 1. The UE receives the search space configuration of WUS from the gNB.

[0116] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0117] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. In one embodiment, the MAC CE can be used to indicate the search space identifier of WUS to the UE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell.

[0118] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0119] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0120] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell in which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0121] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0122] This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or for some configured BWPs.

[0123] A. If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cells for which the UE needs to monitor WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0124] 3. Among the PDCCH monitoring occasions configured by the search space of WUS, the most recent "N" NPDCCH monitoring occasions before the on-duration period are numbered sequentially.

[0125] A. The number may start from the first PDCCH monitoring opportunity before the on-duration period until the Nth NPDCCH monitoring opportunity before the on-duration period. Alternatively, the number may start from the Nth PDCCH monitoring opportunity before the on-duration period until the first PDCCH monitoring opportunity before the on-duration period.

[0126] B. Note that these "N" PDCCH monitoring opportunities may be in one slot or multiple slots (contiguous or non-contiguous), depending on the search space configuration parameters.

[0127] C. In one embodiment, "N" is the total number of TCI states in the TCI state list of the CORESET or CORESET configuration of the WUS.

[0128] D. In an alternative embodiment, N is configured as N<=the total number of TCI states in the TCI state list.

[0129] E. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that do not overlap with the UL symbols before the on-duration are numbered sequentially. In other words, in the valid PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities before the on-duration are numbered sequentially.

[0130] i. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0131] F. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with UL symbols or flexible symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that do not overlap with UL symbols or flexible symbols before the on-duration are numbered sequentially. In other words, in the valid PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities before the on-duration are numbered sequentially.

[0132] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0133] 4. If the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the i-th PDCCH monitoring opportunity of the WUS (i.e., the i-th PDCCH monitoring opportunity in the PDCCH monitoring opportunity numbered in operation 3), where i = 1, 2, ... N. The activated TCI state is signaled to the UE by the gNB using MAC CE.

[0134] A. The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission (the DL TX beam is QCLed using the SSB / CSI RS of the TCI state).

[0135] Figure 1D Another example of determining a PDCCH monitoring opportunity for a WUS according to an embodiment of the present disclosure is shown.

[0136] refer to Figure 1D, in Example 1-2, there are 4 TCI states in the TCI state list. There is one PDCCH monitoring opportunity in a time slot, and 2 consecutive time slots of PDCCH monitoring opportunities with WUS occur every 10 time slots (1d-10). Therefore, the last 4 PDCCH monitoring opportunities (1d-20) before the connection duration (1d-30) are numbered in sequence. If the first TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 1 (1d-20). If the second TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 2 (1d-20). If the third TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 3 (1d-20). If the fourth TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 4 (1d-20). The UE performs this operation before each connection duration.

[0137] Examples 1-3

[0138] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0139] 1. The UE receives the search space configuration of WUS from the gNB.

[0140] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0141] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. In one embodiment, the MAC CE can be used to indicate the search space identifier of WUS to the UE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell.

[0142] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0143] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0144] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0145] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0146] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0147] If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0148] 3.UE receives the offset of WUS from gNB.

[0149] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the offset is common to all configured BWPs of the serving cell. In an alternative embodiment, the offset is BWP-specific, i.e., it is signaled separately for each configured BWP. The offset may be provided for all configured BWPs or for some configured BWPs.

[0150] If the offset for WUS is BWP-specific, the UE uses that offset in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH for WUS. Otherwise, the UE shall use the offset of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH for WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the offset for WUS is signaled only for the serving cells in which the UE needs to monitor WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled.

[0151] 4. The UE receives the length of the WUS monitoring window from the gNB.

[0152] A. The length can be in time slots. The duration of a time slot is determined based on the SCS.

[0153] B. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the length of the WUS monitoring window is common to all configured BWPs of the serving cell. In another embodiment, the length of the WUS monitoring window is BWP-specific, i.e., it is signaled separately for each configured BWP. The length of the WUS monitoring window may be provided for all configured BWPs or for some configured BWPs.

[0154] 5. Among the PDCCH monitoring opportunities configured by the search space of WUS, the PDCCH monitoring opportunities in the WUS monitoring window are numbered sequentially. The WUS monitoring window starts at "offset + monitoring window length" relative to the on duration. The WUS monitoring window ends at the offset relative to the on duration. Alternatively, the WUS monitoring window starts at the offset relative to the on duration. The WUS monitoring window ends at least "p" time slots before the start of the on duration. "p" can also be signaled by the gNB. Alternatively, the WUS monitoring window occurs between time slots "X" and "X offset", where X is the time slot at the start of the on duration and the WUS monitoring window is the first Ts time slot given by the duration field of the search space configuration of WUS.

[0155] A. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., considered invalid. The remaining PDCCH monitoring opportunities are considered valid. Among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that do not overlap with the UL symbols are numbered sequentially in the WUS monitoring window. In other words, in the WUS monitoring window, the valid PDCCH monitoring opportunities of the WUS are numbered sequentially.

[0156] In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0157] B. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with UL symbols or flexible symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the WUS monitoring window, the PDCCH monitoring opportunities configured by the search space of the WUS that do not overlap with UL symbols or flexible symbols are numbered sequentially. In other words, in the WUS monitoring window, the valid PDCCH monitoring opportunities of the WUS are numbered sequentially.

[0158] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0159] 6. In one embodiment, if the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the i-th PDCCH monitoring opportunity of the WUS (i.e., the i-th PDCCH monitoring opportunity in the PDCCH monitoring opportunity of the warp number in operation 4), where i=1, 2...N. Alternatively, if the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the k-th PDCCH monitoring opportunity of the WUS in the WUS monitoring window, where k mod N=I; N is the total number of TCI states in the CORESET of the WUS or the TCI state list configured by the CORESET. Alternatively, the [xXN+K]-th PDCCH monitoring opportunity of the WUS in the WUS monitoring window corresponds to the K-th TCI state, where x=0, 1,...X-1, K=1, 2,...N, N is the number of TCI states in the TCI state list, and X is equal to CEIL (the number of PDCCH monitoring opportunities in the monitoring window / N). Here, CEIL(x) represents the smallest integer greater than or equal to x.

[0160] A. The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission (the DL TX beam is QCLed using the SSB / CSI RS of the TCI state).

[0161] Figure 1E Another example of determining a PDCCH monitoring opportunity of a WUS according to an embodiment of the present disclosure is shown.

[0162] refer to Figure 1E , there are 4 PDCCH monitoring opportunities for WUS (1E-20) in the WUS monitoring window, and these PDCCH monitoring opportunities are numbered sequentially from 1 to 4. If the first TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 1 (1e-10). If the second TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 2 (1e-10). If the third TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 3 (1e-10). If the fourth TCI state in the TCI state list is active, the UE monitors PDCCH monitoring opportunity number 4 (1e-10). The UE performs this operation before each on-duration.

[0163] In embodiments 1-3 of the present disclosure, the parameter "offset" is not configured by the gNB. The WUS monitoring window starts from the first / last PDCCH monitoring opportunity of the WUS (i.e., the PDCCH monitoring opportunity configured by the search space of the WUS or the valid PDCCH monitoring opportunity from the PDCCH monitoring opportunity configured by the search space of the WUS, as explained previously) before the on duration (1e-30). Optionally, the WUS monitoring window starts from the time slot including the first / last PDCCH monitoring opportunity of the WUS before the on duration (1e-30).

[0164] Examples 1-4

[0165] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0166] 1. The UE receives the search space configuration of WUS from the gNB.

[0167] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0168] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. In one embodiment, the MAC CE can be used to indicate the search space identifier of WUS to the UE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell.

[0169] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0170] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0171] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of the WUS is the serving cell for which the WUS configuration is signaled.

[0172] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0173] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0174] If the PS-RNTI of the WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. Otherwise, the UE will use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of the WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell in which the UE monitors the PDCCH of the WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell (e.g., only in the SpCell) as described above, and the WUS is only applied to non-secondary DRX groups, or alternatively, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For non-secondary DRX groups, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0175] 3. The UE receives a list of one or more offsets for the WUS from the gNB.

[0176] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the list is common to all configured BWPs of the serving cell. In another embodiment, the list is BWP-specific, i.e., a separate signal is sent for each configured BWP. The list may be provided for all configured BWPs or for some configured BWPs.

[0177] If the offset list for WUS is BWP-specific, the UE uses the offset list in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH for WUS. Otherwise, the UE will use the offset list of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH for WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the offset list for WUS is signaled only for the serving cell in which the UE needs to monitor WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled.

[0178] In one embodiment, instead of using an offset list, an offset may be indicated for each TCI state in the TCI state list.

[0179] 4. Among the PDCCH monitoring occasions configured by the search space of the WUS, the latest "N" PDCCH monitoring occasions at least "offset" before the On Duration are numbered sequentially.

[0180] A. The number may start from the first PDCCH monitoring opportunity "offset" from at least the on-duration until at least the Nth PDCCH monitoring opportunity "offset" from the on-duration. Alternatively, the number may start from the Nth PDCCH monitoring opportunity "offset" from at least the on-duration until at least the first PDCCH monitoring opportunity "offset" from the on-duration.

[0181] B. Note that these "N" PDCCH monitoring opportunities may be in one slot or multiple slots (contiguous or non-contiguous), depending on the search space configuration parameters.

[0182] C. In one embodiment, "N" is the total number of TCI states in the TCI state list of the CORESET or CORESET configuration of the WUS.

[0183] D. In an alternative embodiment, N is configured as N<=the total number of TCI states in the TCI state list.

[0184] E. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that do not overlap with the UL symbols and are at least offset before the on-duration are numbered sequentially. In other words, in the valid PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that are at least "offset" before the on-duration are numbered sequentially.

[0185] i. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0186] F. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with UL symbols or flexible symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that do not overlap with UL symbols or flexible symbols and are at least offset before the on-duration are numbered sequentially. In other words, in the valid PDCCH monitoring opportunities configured by the search space of the WUS, the most recent "N" PDCCH monitoring opportunities that are at least "offset" before the on-duration are numbered sequentially.

[0187] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0188] 5. If the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the most recent PDCCH monitoring occasion of the WUS, which is at least the i-th offset before the on-duration. Here, the i-th offset refers to the i-th offset in the offset list received from the gNB. In one embodiment, the i-th offset refers to the offset corresponding to the i-th TCI state.

[0189] A. The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission (the DL TX beam is QCLed using the SSB / CSI RS of the TCI state).

[0190] Figure 1F Another example of determining a PDCCH monitoring opportunity of a WUS according to an embodiment of the present disclosure is shown. Figure 1FIn this embodiment 1-4, there are 4 TCI states in the TCI state list. The gNB signals 4 offsets to the UE, one offset corresponding to each TCI state. If the first TCI state in the TCI state list is active, the UE monitors the most recent PDCCH monitoring opportunity (1f-10) offset by at least O1 before the on-duration (1f-30). If the second TCI state in the TCI state list is active, the UE monitors the most recent PDCCH monitoring opportunity (1f-10) offset by at least O3 before the on-duration (1f-30). If the third TCI state in the TCI state list is active, the UE monitors the PDCCH monitoring opportunity (1f-10) offset by at least O3 before the on-duration (1f-30). If the fourth TCI state in the TCI state list is active, the UE monitors the most recent PDCCH monitoring opportunity (1f-10) offset by at least O4 before the on-duration (1f-30). The UE performs this operation before each on-duration.

[0191] Examples 1-5

[0192] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0193] 1. The UE receives the search space configuration of WUS from the gNB.

[0194] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0195] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. In one embodiment, the MAC CE can be used to indicate the search space identifier of WUS to the UE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell.

[0196] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0197] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0198] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0199] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0200] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0201] If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0202] 3. The UE receives a list of one or more PDCCH monitoring opportunity numbers for WUS from the gNB.

[0203] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the list is common to all configured BWPs of the serving cell. In another embodiment, the list is BWP-specific, i.e., a separate signal is sent for each configured BWP. The list may be provided for all configured BWPs or for some configured BWPs.

[0204] If the list of PDCCH monitoring opportunity numbers for WUS is BWP-specific, the UE uses the list of PDCCH monitoring opportunity numbers in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE will use the list of PDCCH monitoring opportunity numbers of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the list of PDCCH monitoring opportunity numbers for WUS is signaled only to the serving cell for which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0205] In one embodiment, instead of using a list of PDCCH monitoring opportunity numbers, a PDCCH monitoring opportunity number may be indicated for each TCI state in the TCI state list.

[0206] 4. The PDCCH monitoring opportunities configured by the search space of the WUS are numbered sequentially in a system frame number (SFN) period starting from SFN 0.

[0207] A. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., considered invalid. The remaining PDCCH monitoring opportunities are considered valid. Of the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that do not overlap with the UL symbols are numbered sequentially starting from SFN 0. In other words, the valid PDCCH monitoring opportunities from the PDCCH monitoring opportunities configured by the search space of the WUS are numbered sequentially starting from SFN 0.

[0208] i. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0209] B. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with UL symbols or flexible symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. Of the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that do not overlap with UL symbols or flexible symbols are numbered sequentially starting from SFN 0. In other words, the valid PDCCH monitoring opportunities from the PDCCH monitoring opportunities configured by the search space of the WUS are numbered sequentially starting from SFN 0.

[0210] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0211] 5. If the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the PDCCH monitoring opportunity identified by the PDCCH monitoring opportunity number in the i-th entry of the PDCCH monitoring opportunity number list. Alternatively, if the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the PDCCH monitoring opportunity identified by the PDCCH monitoring opportunity number corresponding to the i-th TCI state.

[0212] A. The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission (the DL TX beam is QCLed using the SSB / CSI RS of the TCI state).

[0213] It should be noted that multiple PDCCH monitoring opportunity numbers may be sent for each TCI state. In one embodiment, a time slot number and / or a subframe number and / or a radio frame number may be signaled for each TCI state, and the UE may monitor the PDCCH monitoring opportunity configured by the search space of the WUS in the indicated time slot number and / or a subframe number and / or a radio frame number, wherein the time slot number and / or a subframe number and / or a radio frame number corresponds to the activated TCI state.

[0214] Examples 1-6

[0215] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0216] 1. The UE receives the search space configuration of WUS from the gNB.

[0217] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0218] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. In one embodiment, the MAC CE can be used to indicate the search space identifier of WUS to the UE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell.

[0219] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0220] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0221] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0222] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0223] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0224] If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0225] 3. The UE receives a list of one or more PDCCH monitoring opportunity numbers for WUS from the gNB.

[0226] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the list is common to all configured BWPs of the serving cell. In another embodiment, the list is BWP-specific, i.e., a separate signal is sent for each configured BWP. The list may be provided for all configured BWPs or for some configured BWPs.

[0227] If the list of PDCCH monitoring opportunity numbers for WUS is BWP-specific, the UE uses the list of PDCCH monitoring opportunity numbers in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE will use the list of PDCCH monitoring opportunity numbers of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the list of PDCCH monitoring opportunity numbers for WUS is signaled only to the serving cell for which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0228] In one embodiment, instead of using a list of PDCCH monitoring opportunity numbers, a PDCCH monitoring opportunity number may be indicated for each TCI state in the TCI state list.

[0229] 4. The PDCCH monitoring opportunities configured by the search space of the WUS are numbered sequentially (from 0 or from 1) in each DRX cycle. In one embodiment, the DRX cycle length is a short DRX cycle length. In an alternative embodiment, the DRX cycle length is a long DRX cycle length. A DRX cycle is the duration between the start points of two consecutive on durations.

[0230] A. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. Of the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that do not overlap with the UL symbols are numbered sequentially (from 0 or from 1) in each DRX cycle. In other words, the valid PDCCH monitoring opportunities from the PDCCH monitoring opportunities configured by the search space of the WUS are numbered sequentially starting from SFN 0.

[0231] i. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0232] B. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with UL symbols or flexible symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. Of the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that do not overlap with UL symbols or flexible symbols are numbered sequentially in each DRX cycle. In other words, valid PDCCH monitoring opportunities from the PDCCH monitoring opportunities configured by the search space of the WUS are numbered sequentially in each DRX cycle.

[0233] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0234] C. If a short DRX cycle is used, and [(SFNХ10)+subframe number] modulo(drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle); or

[0235] If a long DRX cycle is used, and [(SFNХ10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset:

[0236] The OnDuration starts from the start of the subframe after drx-SlotOffset. drx-ShortCycle, drx-LongCycle, drx-StartOffset are signaled by the gNB.

[0237] 5. If the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the PDCCH monitoring opportunity identified by the PDCCH monitoring opportunity number in the i-th entry of the PDCCH monitoring opportunity number list. Alternatively, if the i-th TCI state is active in the CORESET of the WUS or the TCI state list configured by the CORESET, the UE monitors the PDCCH monitoring opportunity identified by the PDCCH monitoring opportunity number corresponding to the i-th TCI state.

[0238] A. The CORESET configuration associated with the search space includes a list of TCI states. One TCI state in the TCI state list is activated and indicated by the gNB to the UE. The TCI state indicates the DL TX beam used by the gNB for PDCCH transmission (the DL TX beam is QCLed using the SSB / CSI RS of the TCI state).

[0239] It should be noted that multiple PDCCH monitoring opportunity numbers may be sent for each TCI state.

[0240] Examples 1-7

[0241] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0242] 1. The UE receives the search space configuration of WUS from the gNB.

[0243] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0244] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) may be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. Configuration may be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS may be included in the PDCCH-configCommon IE. The list of search space configurations may be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell.

[0245] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0246] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0247] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0248] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0249] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0250] If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0251] 3. The UE receives a list of one or more PDCCH monitoring opportunity numbers for WUS from the gNB.

[0252] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the list is common to all configured BWPs of the serving cell. In another embodiment, the list is BWP-specific, i.e., a separate signal is sent for each configured BWP. The list may be provided for all configured BWPs or for some configured BWPs.

[0253] If the list of PDCCH monitoring opportunity numbers for WUS is BWP-specific, the UE uses the list of PDCCH monitoring opportunity numbers in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE will use the list of PDCCH monitoring opportunity numbers of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the list of PDCCH monitoring opportunity numbers for WUS is signaled only to the serving cell for which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0254] In one embodiment, instead of using a list of PDCCH monitoring opportunity numbers, a PDCCH monitoring opportunity number may be indicated for each TCI state in the TCI state list.

[0255] 5. The UE receives the length of the WUS monitoring window from the gNB.

[0256] A. The length can be in time slots. The duration of a time slot is determined based on the SCS. It can be one or more time slots. In one embodiment, the length of the WUS monitoring window can be predefined (e.g., 1 time slot) so the gNB does not signal it.

[0257] B. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the length of the WUS monitoring window is common to all configured BWPs of the serving cell. In another embodiment, the length of the WUS monitoring window is BWP-specific, i.e., it is signaled separately for each configured BWP. The length of the WUS monitoring window may be provided for all configured BWPs or for some configured BWPs.

[0258] C. The WUS monitoring window starts at "offset + monitoring window length" relative to the on duration. The WUS monitoring window ends at an offset relative to the on duration. The UE monitors the PDCCH monitoring opportunities configured by the search space for WUS in the WUS monitoring window relative to the offset of the on duration. Alternatively, the WUS monitoring window starts at an offset relative to the on duration. The WUS monitoring window ends at least "p" time slots before the start of the on duration. "p" may also be signaled by the gNB. Alternatively, the WUS monitoring window occurs between time slots "X" and "X offset", where X is the time slot at the start of the on duration and the WUS monitoring window is the first Ts time slot given by the duration field of the search space configuration for WUS.

[0259] i. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors the PDCCH monitoring opportunities that do not overlap with the UL symbols in the WUS monitoring window. In other words, in the WUS monitoring window, the UE monitors the valid PDCCH monitoring opportunities of the WUS.

[0260] E. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0261] i. In one embodiment, in a TDD cell, among the PDCCH monitoring opportunities configured by the search space of WUS, the PDCCH monitoring opportunities overlapping with UL symbols or flexible symbols are excluded, i.e., considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the WUS monitoring window, the UE monitors the PDCCH monitoring opportunities configured by the search space of WUS that do not overlap with UL symbols or flexible symbols. In other words, in the WUS monitoring window, the UE monitors the valid PDCCH monitoring opportunities of WUS.

[0262] 6. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0263] If there are multiple PDCCH monitoring opportunities of the WUS in the WUS monitoring window, when a PDCCH addressed to the PS-RNTI is received in a PDCCH monitoring opportunity in the WUS monitoring window, the UE is not required to monitor the remaining PDCCH monitoring opportunities of the WUS in the WUS monitoring window.

[0264] Examples 1-8

[0265] In one method of the present disclosure, the UE determines the PDCCH monitoring opportunity of the WUS as follows:

[0266] 1. The UE receives the search space configuration of WUS from the gNB.

[0267] A. A list of search space configurations may be signaled by the gNB. Each search space configuration in the list is uniquely identified by a search space identifier. The search space configurations in this list that the UE should monitor for the WUS may be explicitly indicated by the gNB. The gNB may indicate this by indicating the search space identifier of the WUS or by including a field in the search space configuration that indicates the DCI format that may monitor the WUS in this search space configuration. The gNB may indicate multiple search space configurations for the WUS. A list of CORESET configurations is signaled by the gNB. Each CORESET configuration in the list is uniquely identified by a CORESET identifier. The CORESET identifier of the CORESET configuration of the WUS is indicated in the search space configuration of the WUS.

[0268] i. The above configuration (search space configuration list, CORESET configuration list, and search space identifier of WUS) can be received by the UE in an RRC message (e.g., RRCReconfiguration message). The configuration can be BWP-specific, that is, it is signaled separately for each configured BWP. Configuration can be provided for all configured BWPs or some configured BWPs. The search space identifier of WUS can be included in the PDCCH-configCommon IE. The list of search space configurations can be included in the PDCCH-configIE. PDCCH-configCommon and PDCCH-config are included in the BWP configuration of the serving cell. In one embodiment, the search space identifier of WUS can be indicated to the UE using MAC CE.

[0269] B. The UE shall use the WUS search space configuration and CORESET configuration explicitly indicated by the gNB.

[0270] i. The configuration may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). The configuration may be BWP-specific, i.e., it is signaled separately for each configured BWP. The configuration may be provided for all configured BWPs or some configured BWPs. The search space configuration for the WUS may be included in the PDCCH-config IE.

[0271] If the search space / CORESET configuration of the WUS is BWP-specific, the UE uses the search space / CORESET configuration of the active DL BWP of the WUS to determine the PDCCH monitoring occasions of the WUS. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of the WUS. If the search space / CORESET configuration of the WUS is BWP-specific, the UE monitors the PDCCH of the WUS (or in other words, considers the configuration of the WUS) if the search space / CORESET configuration of the WUS is signaled for the active BWP. Otherwise, if the search space / CORESET configuration of the WUS is not BWP-specific, the UE uses the search space / CORESET configuration of the serving cell of the WUS to determine the PDCCH monitoring occasions of the WUS, where the serving cell is the cell in which the UE monitors the PDCCH of the WUS. In one embodiment, the serving cell is a SpCell. In an alternative embodiment, the search space / CORESET configuration of the WUS is signaled only for the serving cell that the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH for WUS is the serving cell for which the WUS configuration is signaled. In an embodiment in which multiple DRX groups are configured, the UE monitors the WUS only in one serving cell as described above (e.g., only in the SpCell), and the WUS is applied only to the non-secondary DRX group, or optionally, the WUS is applied to two DRX groups. In another embodiment, in which multiple DRX groups are configured, the UE monitors the WUS of different DRX groups in different serving cells. For the non-secondary DRX group, the UE monitors the WUS in the SpCell. For the secondary DRX group, the UE monitors the WUS in the serving cell signaled by the gNB.

[0272] 2. The UE receives the RNTI of the WUS (i.e., PS-RNTI) from the gNB.

[0273] A. This may be received by the UE in an RRC message (e.g., RRCReconfiguration message). In one embodiment, the PS-RNTI is common to all configured BWPs of the serving cell. In another embodiment, the PS-RNTI is BWP-specific, i.e., it is signaled separately for each configured BWP. The PS-RNTI may be provided for all configured BWPs or some of the configured BWPs.

[0274] If the PS-RNTI of WUS is BWP-specific, the UE uses the PS-RNTI in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the PS-RNTI of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the PS-RNTI of WUS is signaled only for the serving cell in which the UE needs to monitor the WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0275] 3.UE receives the offset of WUS from gNB.

[0276] A. This may be received by the UE in an RRC message (e.g., an RRCReconfiguration message). In one embodiment, the offset is common to all configured BWPs of the serving cell. In an alternative embodiment, the offset is BWP-specific, i.e., it is signaled separately for each configured BWP. The offset may be provided for all configured BWPs or for some configured BWPs.

[0277] If the offset for WUS is BWP-specific, the UE uses that offset in the configuration of the active DL BWP. Here, the active DL BWP is the active DL BWP of the serving cell in which the UE monitors the PDCCH of WUS. Otherwise, the UE shall use the offset of the serving cell, where the serving cell is the cell in which the UE monitors the PDCCH of WUS. In one embodiment, the serving cell is the SpCell. In an alternative embodiment, the offset of WUS is signaled only for the serving cells in which the UE needs to monitor WUS. Therefore, the serving cell for which the UE monitors the PDCCH of WUS is the serving cell for which the WUS configuration is signaled.

[0278] 4. Among the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors the most recent PDCCH monitoring opportunity that is at least "offset" before the on-duration. Alternatively, the UE monitors the most recent PDCCH monitoring opportunity before the on-duration. Alternatively, the UE monitors all PDCCH monitoring opportunities configured by the search space of the WUS.

[0279] A. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbols are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors the most recent PDCCH monitoring opportunity that does not overlap with the UL symbol and is at least "offset" before the on-duration. Alternatively, in the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors the most recent PDCCH monitoring opportunity that does not overlap with the UL symbol before the on-duration. Alternatively, in the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors all PDCCH monitoring opportunities that do not overlap with the UL symbol before the on-duration but are outside the UE's active time.

[0280] i. In one embodiment, the UL symbol is determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0281] B. In one embodiment, in a TDD cell, in the PDCCH monitoring opportunities configured by the search space of the WUS, the PDCCH monitoring opportunities that overlap with the UL symbol or the flexible symbol are excluded, i.e., are considered invalid. The remaining PDCCH monitoring opportunities are considered valid. In the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors the most recent PDCCH monitoring opportunity that does not overlap with the UL symbol or the flexible symbol and is at least "offset" before the on-duration. Alternatively, in the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors the most recent PDCCH monitoring opportunity that does not overlap with the UL symbol or the flexible symbol before the on-duration. Alternatively, in the PDCCH monitoring opportunities configured by the search space of the WUS, the UE monitors all PDCCH monitoring opportunities that do not overlap with the UL symbol or the flexible symbol before the on-duration but are outside the UE's active time.

[0282] i. In one embodiment, the UL symbols and flexible symbols are determined based on the tdd-UL-DL-ConfigurationCommonIE received from the gNB (e.g., in SIB1).

[0283] In embodiments 1-1 to 1-8 of the present disclosure, the search space / CORESET configuration of the WUS may be configured separately for the short DRX cycle and the long DRX cycle. During DRX operation, if the UE is in the short DRX cycle mode, the UE uses the search space / CORESET configuration of the WUS corresponding to the short DRX cycle. During DRX operation, if the UE is in the long DRX cycle mode, the UE uses the search space / CORESET configuration of the WUS corresponding to the long DRX cycle. During DRX operation, when the short DRX cycle expires, the UE uses the search space / CORESET configuration of the WUS corresponding to the short DRX cycle. If only one search space / CORESET configuration of the WUS is signaled, the UE applies it to both the short DRX cycle mode and the long DRX cycle mode.

[0284] In Embodiments 1-1 to 1-8 of the present disclosure, the UE monitors the PDCCH monitoring opportunity of the WUS only outside the active time.

[0285] In an embodiment of the present disclosure, if WUS is configured in the active BWP, and if both the short DRX cycle and the long DRX cycle are configured, the UE monitors the PDCCH of the PS-RNTI addressed to the WUS (where the wake-up bit is included in the DCI of the received PDCCH), or applies the WUS to determine whether to start the on-duration only in the short DRX cycle mode. This means that if the UE is in the long DRX cycle mode or is using the long DRX cycle, and [(SFNХ10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, it will always start the drx-onDurationTimer from the start of the subframe after drx-SlotOffset. If the UE is in short DRX cycle mode or is using a short DRX cycle, and [(SFNХ10)+subframe number] modulo(drx-ShortCycle)=drx-StartOffset: If a WUS is received, it will start the drx-onDurationTimer from the start of the subframe after drx-SlotOffset. Otherwise, it will not start.

[0286] In an alternative embodiment, if WUS is configured in the active BWP, and if both short and long DRX cycles are configured, the UE monitors the PDCCH addressed to the PS-RNTI of the WUS (where the wake-up bit is included in the DCI of the received PDCCH), or applies the WUS to determine whether to start the on-duration period in long DRX cycle mode. This means that if the UE is in short DRX cycle mode or is using a short DRX cycle, and [(SFNХ10)+subframe number] modulo(drx-ShortCycle)=drx-StartOffset, it will always start the drx-onDurationTimer from the start of the subframe after drx-SlotOffset. If the UE is in long DRX cycle mode or is using a long DRX cycle, and [(SFNХ10) + subframe number] modulo(drx-LongCycle) = drx-StartOffset: If a WUS is received, it will start drx-onDurationTimer from the start of the subframe after drx-SlotOffset. Otherwise it will not start. Note that it was previously described when the UE uses a long DRX cycle, and when it uses a short DRX cycle.

[0287] In an alternative embodiment, if both short and long DRX cycles are configured, the network may indicate whether the WUS is monitored in short DRX cycle mode or long DRX cycle mode.

[0288] In one embodiment, if there is only one DRX group configured for the CG and a WUS is received on the SpCell (a PDCCH addressed to the PS-RNTI is received on the SpCell and the wake-up bit in the DCI is set to 1, then the WUS is considered to be received), then the received WUS is applied (as described above) to all service cells of the CG. In one embodiment, if there are multiple DRX groups configured for the CG and a PDCCH addressed to the PS-RNTI is received on the SpCell and the wake-up bit in the DCI is set to 1, then the WUS is considered to be received and applied (as described above) to the service cells of the non-auxiliary DRX group. In one embodiment, if there are multiple DRX groups configured for the CG and a WUS is received on the SpCell (a PDCCH addressed to the PS-RNTI is received on the SpCell and the wake-up bit in the DCI is set to 1, then the WUS is considered to be received), then the received WUS is applied to the service cells of both the non-auxiliary DRX group and the auxiliary DRX group. In one embodiment, if there are multiple DRX groups configured for the CG, and a PDCCH addressed to the PS-RNTI is received on the SpCell, and the wake-up bit in the DCI of the non-secondary DRX group is set to 1, then the WUS is considered to be received and applied to the serving cell of the non-secondary DRX group. In one embodiment, if there are multiple DRX groups configured for the CG, and a PDCCH addressed to the PS-RNTI is received on the SpCell, and the wake-up bit in the DCI of the secondary DRX group is set to 1, then the WUS is considered to be received and applied to the serving cell of the secondary DRX group.

[0289] The above-mentioned embodiments 1 to 8 have been described for monitoring WUS of a connected mode DRX cycle. However, these methods can also be applied to monitoring WUS of an idle / inactive mode DRX cycle. In the case of idle mode, the "on duration" in embodiments 1 to 8 is equivalent to a paging occasion, where the UE monitors the PDCCH addressed to the P-RNTI to receive a paging message. The UE monitors the WUS before the paging occasion, and only when the WUS is received, the UE monitors the PDCCH addressed to the P-RNTI in its PO. In the case of an idle mode search space configuration / coreset, the RNTI for WUS monitoring and the offset for WUS monitoring as defined in embodiments 1 to 8 can be signaled in the system information without using an RRCReconfiguration message. In the case of an idle mode DRX cycle, these configurations are signaled for the initial DL BWP (i.e., the active BWP in idle / inactive).

[0290] Figure 1G is a block diagram of a terminal according to an embodiment of the present invention.

[0291] Reference Figure 1G The terminal includes a transceiver 1g-10, a controller 1g-20, and a memory 1g-30. The controller 1g-20 may refer to a circuit, an application-specific integrated circuit (ASIC), or at least one processor. The transceiver 1g-10, the controller 1g-20, and the memory 1g-30 are configured to perform the operations of the UE shown in the figure, for example, Figures 1A to 1F , or as described above. Although the transceiver 1g-10, the controller 1g-20, and the memory 1g-30 are shown as separate entities, they may be implemented as a single entity, such as a single chip. Alternatively, the transceiver 1g-10, the controller 1g-20, and the memory 1g-30 may be electrically connected or coupled to each other.

[0292] The transceiver 1g-10 may transmit and receive signals to and from other network entities (eg, base stations).

[0293] The controller 1g-20 can control the terminal to perform the functions according to one of the above embodiments. For example, the controller 1g-20 controls the transceiver 1g-10 and / or the memory 1g-30 to receive at least one parameter associated with the PMO of the WUS and monitor the PMO of the WUS before the on-duration period.

[0294] In one embodiment, the operation of the terminal can be implemented using a memory 1g-30 storing corresponding program codes. Specifically, the terminal can be equipped with a memory 1g-30 to store program codes for implementing desired operations. In order to perform the desired operations, the controller 1g-20 can read and execute the program codes stored in the memory 1g-30 by using at least one processor or a central processing unit (CPU).

[0295] Figure 1H is a block diagram of a base station according to an embodiment of the present invention.

[0296] Reference Figure 1H , the base station includes a transceiver 1h-10, a controller 1h-20, and a memory 1h-30. The controller 1h-20 may refer to a circuit, an application-specific integrated circuit (ASIC), or at least one processor. The transceiver 1h-10, the controller 1h-20, and the memory 1h-30 are configured to perform the operations of the UE shown in the figure, for example, Figures 1A to 1F The operation of the UE shown in, or as described above. Although the transceiver 1h-10, the controller 1h-20, and the memory 1h-30 are shown as separate entities, they can be implemented as a single entity, such as a single chip. Alternatively, the transceiver 1h-10, the controller 1h-20, and the memory 1h-30 can be electrically connected or coupled to each other.

[0297] The transceiver 1h-10 can send signals to other network entities (e.g., terminals) and receive signals from other network entities (e.g., terminals).

[0298] The controller 1h-20 can control the UE to perform a function according to one of the above embodiments. For example, the controller 1h-20 controls the transceiver 1h-10 and / or the memory 1h-30 to send at least one parameter associated with the PMO of the WUS before the on-duration period, and to send the WUS in the PMO of the WUS before the on-duration period.

[0299] In one embodiment, the operation of the base station can be implemented using a memory 1h-30 storing corresponding program codes. Specifically, the base station can be equipped with a memory 1h-30 to store program codes for implementing the desired operation. In order to perform the desired operation, the controller 1h-20 can read and execute the program code stored in the memory 1h-30 by using at least one processor or central processing unit (CPU).

[0300] Embodiment 2 - Apparatus and method for protecting unicast V2X communication

[0301] In 5G wireless communication systems, random access (RA) is supported. Random access (RA) is used to achieve UL time synchronization. RA is used in the UL by non-synchronized UEs in the RRC connected state during initial access, handover, RRC connection re-establishment process, scheduling request transmission, secondary cell group (SCG) addition / modification, beam failure recovery, and data or control information transmission. Several types of random access procedures are supported.

[0302] Contention-based Random Access (CBRA): This is 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 gNB sends the RAR on the PDSCH. The PDCCH that schedules the PDSCH carrying the RAR is addressed to the Random Access Radio Network Temporary Identifier (RA-RNTI). The RA-RNTI identifies the time-frequency resource (also known as physical RA channel (PRACH) opportunity or PRACH transmission (TX) opportunity or RA channel (RACH) opportunity) where the RA preamble is detected by the gNB. The RA-RNTI is calculated as follows: RA-RNTI=1+s_id+14*t_id+14*80*f_id+14*80*8*ul_carrier_id, where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH opportunity in which the UE has sent Msg1, i.e., the RA preamble code; 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 normal UL (NUL) carrier, 1 for supplementary UL (SUL) carrier).

[0303] Several RARs for various random access preambles detected by the gNB may be multiplexed by the gNB in ​​the same RAR MAC PDU. If the RAR in the MAC PDU includes the RA preamble identifier (RAPID) of the RA preamble sent by the UE, the RAR corresponds to a RA preamble transmission by the UE. If no RAR corresponding to its RA preamble transmission is received during the RAR window, and the UE has not sent a RA preamble 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 fallback may be applied before returning to the first step.

[0304] If a RAR corresponding to its 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 identifier (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. While the contention resolution timer is running, if the UE receives a physical downlink control channel (PDCCH) addressed to the C-RNTI included in Msg3, the contention resolution is considered successful, the contention resolution timer is stopped and the RA process is completed. While the contention resolution timer is running, if the UE receives a contention resolution MAC CE including the UE's contention resolution identification (the first X bits of the common control channel (CCCH) service data unit (SDU) sent in Msg3), the contention resolution is considered successful, the contention resolution timer is stopped and the RA process 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. A backoff may be applied before returning to the first step.

[0305] Contention Free Random Access (CFRA): This is also known as legacy CFRA or 4-step CFRA. The CFRA procedure is used for handovers that require low latency, timing advance establishment of 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 addressed to the RA-RNTI. The RAR conveys the RA preamble identifier and timing alignment information. The RAR may also include an UL grant. The RAR is transmitted in a RAR window similar to the Contention Based RA (CBRA) procedure. The CFRA is considered to be successfully completed after receiving the RAR sent by the UE including the RAPID of the RA preamble. In case RA is initiated for beam failure recovery, the CFRA is considered to be successfully completed if a PDCCH addressed to the C-RNTI is received in the search space for beam failure recovery. If the RAR window expires and the RA is not successfully completed, and the UE has not sent the RA preamble a configurable (configured by the gNB in ​​the RACH configuration) number of times, the UE retransmits the RA preamble.

[0306] 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 RSs. If there is no SSB / CSI RS with DL RSRP above a threshold among the SSB / CSI RSs for which contention-free random access resources (i.e., dedicated preambles / ROs) are provided by the gNB, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during the RA procedure, one random access attempt may be CFRA, while the other random access attempt may be CBRA.

[0307] 2-step Contention Based Random Access (2-step CBRA): In the first step, the UE sends a random access preamble on PRACH and a payload 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 the response from the network (i.e., gNB) within the configured window. The response is also referred to as MsgB. If the CCCH SDU is sent in the MsgA payload, the UE performs contention resolution using the contention resolution information in the MsgB. If the C-RNTI is sent in the MsgA payload, the contention resolution is successful if the UE receives a PDCCH addressed to the C-RNTI. If the contention resolution is successful, the random access procedure is considered to be completed successfully. Instead of using the contention resolution information corresponding to the transmitted MsgA, the MsgB may include backoff information corresponding to the random access preamble sent in the MsgA. If the fallback information is received, the UE sends Msg3 and performs contention resolution using Msg4 as in the CBRA process. If the contention resolution is successful, the random access procedure is considered to be successfully completed. If the contention resolution fails at the fallback (i.e., when sending MSg3), the UE resends MsgA. If the configured window for the UE to monitor the network response after sending MsgA expires and the UE does not receive MsgB including contention resolution information or fallback 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.

[0308] The MsgA payload may include one or more of a common control channel (CCCH) SDU, a dedicated control channel (DCCH) SDU, a dedicated traffic channel (DTCH) SDU, a buffer status report (BSR) MAC 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. A UE ID such as a C-RNTI may be carried in a MAC CE, where the MAC CE is included in the MAC PDU. Other UE IDs (e.g., a 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, idle mode ID, inactive mode ID, etc. The UE ID may be different in different situations where the UE performs a RA process. When the UE performs RA after power-on (before it attaches to the network), the UE ID is a random ID. When the UE performs RA in an idle state after attaching to the network, the UE ID is an S-TMSI. If the UE has an assigned C-RNTI (e.g., in a connected state), the UE ID is a C-RNTI. In the case where the UE is in an inactive state, the UE ID is a recovery ID. In addition to the UEID, some additional ctrl information may be sent in MsgA. Control information may be included in the MAC PDU of 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 (e.g., one or more DL TX beam IDs or one or more SSB IDs), a beam failure recovery indication / information, a data indicator, a cell / BS / TRP exchange indication, a connection reconstruction indication, a reconfiguration completion or a switching completion message, etc. One or more.

[0309] 2-step Contention-Free Random Access (2-step CFRA): In this case, the gNB allocates a dedicated random access preamble and PUSCH resources for MsgA transmission to the UE. The RO for preamble transmission may also be indicated. In the first step, the UE sends a random access preamble on PRACH and payload on PUSCH using contention-free random access resources (i.e., dedicated preamble / PUSCH resources / RO). In the second step, after MsgA transmission, the UE monitors for a response from the network (i.e., gNB) within the configured window. If the UE receives a PDCCH addressed to the C-RNTI, the random access procedure is considered to be successfully completed.

[0310] 4G and 5G wireless communication systems support vehicular communication services. Vehicular communication services are represented by vehicle-to-everything (V2X) services and can include four different types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). In the fifth generation (or NR) wireless communication system, V2X sidelink communications are enhanced to support enhanced V2X use cases, which are broadly arranged into four use case groups:

[0311] 1) Vehicle Grouping enables vehicles to dynamically form groups that travel together. All vehicles in the group receive information from the lead vehicle to manage the group. This information allows vehicles to travel closer than normal in a coordinated manner, going in the same direction and traveling together.

[0312] 2) Extended sensors enable the exchange of raw or processed data collected by local sensors or live video images between vehicles, road station units, pedestrian devices, and V2X application servers. Vehicles can increase their perception of the environment beyond what their own sensors can detect and have a broader and more holistic view of the local situation. High data rate is one of the key features.

[0313] 3) Advanced driving allows semi-autonomous or fully autonomous driving. Each vehicle and / or RSU shares its own perception data obtained from its local sensors with nearby vehicles, allowing the vehicles to synchronize and coordinate their trajectories or actions. Each vehicle also shares its driving intentions with nearby vehicles.

[0314] 4) Remote driving enables remote drivers or V2X applications to operate remote vehicles for passengers who cannot drive themselves or remote vehicles located in hazardous environments. For situations where changes are limited and routes are predictable, such as public transportation, cloud-based driving can be used. High reliability and low latency are the main requirements.

[0315] Figure 2A An example of a Next Generation Radio Access Network (NG-RAN) architecture associated with a PC5 interface according to an embodiment of the present disclosure is shown.

[0316] V2X services may be provided by the PC5 interface and / or the Uu interface. Support for V2X services via the PC5 interface is provided by NR sidelink communication or V2X sidelink communication, which is a communication mode whereby UEs can communicate directly with each other over the PC5 interface using NR technology or EUTRA technology, respectively, without traversing any network nodes. This communication mode is supported when the UE is served by the RAN and when the UE is outside the RAN coverage. Only UEs authorized for V2X services can perform NR or V2X sidelink communications. The NG-RAN architecture supports Figure 1A to Figure 1GThe PC5 interface shown. When the UE is within the coverage of the NG-RAN, regardless of the RRC state of the UE, and when the UE is outside the coverage of the NG-RAN, sidelink transmission and reception over the PC5 interface are supported. Support for V2X services over the PC5 interface can be provided by NR sidelink communications and / or V2X sidelink communications. NR sidelink communications can be used to support services other than V2X services.

[0317] NR or V2X sidelink communication can support three types of transmission modes. First, unicast transmission, characterized by: support for at least one PC5-RRC connection between peer UEs; transmission and reception of control information and user traffic between peer UEs in the side link; support for sidelink HARQ feedback; support for radio link control (RLC) AM; and support for sidelink RLM of two peer UEs to detect RLF. Second, multicast transmission, characterized by: transmission and reception of user traffic between UEs belonging to a group in the side link; support for sidelink HARQ feedback. Third, broadcast transmission, characterized by: transmission and reception of user traffic between UEs in the side link.

[0318] The access stratum (AS) protocol stack for the control plane in the PC5 interface consists of RRC, Packet Data Convergence Protocol (PDCP), RLC and MAC sublayers, and the physical layer. The AS protocol stack for the user plane in the PC5 interface consists of the Service Data Adaptation Protocol (SDAP), PDCP, RLC and MAC sublayers, and the physical layer. A UE supporting NR sidelink communication can operate in two modes for resource allocation:

[0319] - Scheduled resource allocation (also called Mode 1), characterized by:

[0320] *UE needs to be in RRC connection (RRC_CONNECTED) in order to send data;

[0321] *UE requests transmission resources from gNB. gNB schedules transmission resources for transmission of sidelink control information and data.

[0322] -UE autonomous resource selection (also known as Mode 2), characterized by:

[0323] * The UE itself selects resources from the resource pool and performs transport format selection to transmit sidelink control information and data;

[0324] *UE performs sensing for (re)selection of sidelink resources. Based on the sensing results, UE (re)selects some specific sidelink resources and reserves multiple sidelink resources.

[0325] In the following, secure key establishment for one-to-one communication is explained.

[0326] Figure 2B An example of different layers of security keys according to an embodiment of the present disclosure is shown. Figure 2B ,To protect the PC5-S signaling messages for one-to-one or unicast ,communication, four different key layers are used, such as Figures 2A to 2N shown.

[0327] Long-term key (2b-10): This is the key provided to the UE and is the root of security for one-to-one communication. The long-term key is identified by the long-term ID. This is a common key for one-to-one communication.

[0328] K D (2b-20): This is a 256-bit root key shared between two entities communicating using one-to-one communication. It can be refreshed by rerunning authentication signaling using the long-term key. To generate K D-sess (The next level of keys), random numbers are exchanged between communicating entities. K can be maintained even when there is no active one-to-one communication session between UEs. D . K D ID is used to identify K D .

[0329] K D-sess (2b-30): This is a 256-bit key that is the root of the actual security context used to protect data transmission between UEs. It is derived from the root key when a unicast connection is established. During communication between UEs, K can be refreshed by running the rekey procedure. D-sess (e.g., when a PDCP counter rolls over). The actual keys used in the confidentiality and integrity algorithms are derived directly from K D-sess Export. 16 bit K D-sess ID Identification D-sess .

[0330] PEK (2b-40) and PIK (2b-50): Proximity Services (ProSe) Encryption Key (PEK) and ProSe Integrity Key (PIK) are used in the selected confidentiality and integrity algorithms, respectively. They are derived from K D-sess , and whenever K D-sess Automatically refresh when changed.

[0331] Figure 2C and Figure 2D An example of establishing security keys during connection establishment and key update procedures according to various embodiments of the present disclosure is shown. These details can be found in 3GPP TS 33.303 and are therefore omitted here.

[0332] Reference Figure 2C , in operation 2c-10, UE_1 sends a direct communication request to UE_2. In response, in operation 2c-20, direct authentication and key establishment occur between UE_1 and UE_2. In operation 2c-30, UE_2 sends a direct security mode command to UE_1. In operation 2c-40, UE_1 sends a direct security mode complete message to UE_2. Thereafter, in operation 2c-50, each of UE_1 and UE-2 may send signaling and user plane traffic with a new security context, and delete the old security context on UE_2.

[0333] Reference Figure 2D , in operation 2d-10, UE_1 sends a direct communication request to UE_2. In response, in operation 2d-20, direct authentication and key establishment occur between UE_1 and UE_2. In operation 2d-30, UE_2 sends a direct security mode command to UE_1. In operation 2d-40, UE_1 sends a direct security mode complete message to UE_2. Thereafter, in operation 2d-50, each of UE_1 and UE-2 may send signaling and user plane traffic with a new security context and delete the old security context on UE_2. In operation 2d-60, when a signaling message protected with a new security context is received, the old security context is deleted on UE_1.

[0334] In the following, protection of one-to-one business is explained.

[0335] Protection of signaling and user plane data between UEs is provided at the PDCP layer. Since security is not maintained through the loss of a connection, all signaling messages that need to be sent before security is established can be sent unprotected. Except for the direct security mode command, which only sends integrity protection, all other signaling messages should be integrity protected and can be confidentiality protected.

[0336] Bearers with Logical Channel Identifier (LCID) = 28 should be used to carry unprotected signaling messages.

[0337] The bearer with LCID=29 shall be used for Direct Security Mode Command and Direct Security Mode Complete.

[0338] The bearer with LCID=30 should be used for other signaling messages with confidentiality and integrity protected.

[0339] Bearers with LCID=1 to 10 can be used for user plane services with confidentiality protection.

[0340] Hereinafter, integrity protection is explained.

[0341] The input parameters of the integrity algorithm are a 128-bit integrity key called KEY, a 32-bit COUNT, a 5-bit bearer identifier called BEARER, a 1-bit direction of transmission (ie, DIRECTION), and the message itself (ie, MESSAGE).

[0342] -The KEY used is PIK; PIK is composed of K D-sess Calculate. When K D-sess When calculating the PIK, the following parameters are used to form the input S to the key derivation function (KDF is specified in Annex B of TS 33.220):

[0343] *FC=0x4B;P0=0x01;L0=length of P0 (i.e. 0x00 0x01);P1=algorithm identifier;L1=length of algorithm identifier (i.e. 0x00 0x01);

[0344] - Direction is set to 1 for direct link signalling sent by a UE sending a Direct Security Mode Command for this security context, otherwise to 0;

[0345] - Set BEARER[0] to BEARER[4] to LCID;

[0346] -COUNT[0] to COUNT

[15] are set to K D-sess ID; and

[0347] - A counter is input to COUNT

[16] to COUNT

[31] , where the counter is a 16-bit PDCP sequence number (SN).

[0348] Figure 2E An example of using the integrity algorithm EIA to authenticate the integrity of a message according to an embodiment of the present disclosure is shown.

[0349] refer to Figure 2E Based on these input parameters, the sender calculates a 32-bit message authentication code (MAC-I) using the integrity algorithm EIA. The message authentication code is then attached to the message when it is sent. For the integrity protection algorithm, the receiver calculates the expected message authentication code (XMAC-I) on the received message in the same way as the sender calculates the message authentication code on the sent message, and verifies the data integrity of the message by comparing it with the received message authentication code (i.e., MAC-I).

[0350] Hereinafter, confidentiality protection is explained.

[0351] The input parameters of the encryption algorithm are a 128-bit key named KEY, a 32-bit COUNT, a 5-bit bearer identifier BEARER, a 1-bit direction of transmission (ie, DIRECTION), and the length of the required key stream (ie, LENGTH).

[0352] -The KEY used is PEK; from K D-sess Calculate PEK. When K D-sess When calculating the PIK, the following parameters are used to form the input S to the key derivation function (KDF is specified in Annex B of TS 33.220):

[0353] *FC=0x4B;P0=0x00;L0=length of P0 (i.e. 0x00 0x01);P1=algorithm identifier;L1=length of algorithm identifier (i.e. 0x00 0x01);

[0354] The direction of the direct link signaling sent by the UE that sends the direct security mode command for the security context is set to 1, otherwise it is set to 0;

[0355] Set BEARER[0] to BEARER[4] to LCID;

[0356] COUNT[0] to COUNT

[15] are set to K D-sess ID; and

[0357] The counter is input to COUNT

[16] to COUNT

[31] , where the counter is a 16-bit PDCP SN.

[0358] Figure 2F An example of encrypting plaintext by applying a key stream using binary addition of each bit of the plaintext and the key stream using the encryption algorithm EEA according to an embodiment of the present disclosure is shown.

[0359] The plaintext can be recovered by using the same input parameters and applying binary addition to each bit of the ciphertext to generate the same keystream.

[0360] Based on the input parameters, the algorithm generates an output keystream block KEYSTREAM, which is used to encrypt the input plaintext block PLAINTEXT to produce an output ciphertext block CIPHERTEXT.

[0361] The input parameter LENGTH will only affect the length of the KEYSTREAMBLOCK, not the actual bits within it.

[0362] Several issues regarding the above process are described below.

[0363] Problem 1: In 4G wireless communication systems, signaling messages for unicast communication are generated by the PC5 protocol layer and carried on the radio bearer on the user plane. In 5G wireless communication systems, RRC between UEs is also supported for unicast communication. Therefore, in addition to the signaling messages generated by the PC5 protocol layer, signaling messages are also generated by RRC. The problem is that security keys are used for integrity and confidentiality protection of RRC messages exchanged between UEs for unicast communication.

[0364] Question 2: In LTE-based V2X communication, only PDCP SN is used in PDCP operation. In NR-based V2X communication, PDCP SN and hyperframe number (HFN) are supported in PDCP operation. When the PDCP SN flips, the HFN is updated. If only the PDCP SN is used as input for the integrity and encryption algorithms, the input parameters (COUNT, DIRECTION, BEARER) will be the same for several data packets. This is undesirable from a security point of view. If only the PDCP SN is used, the key needs to be refreshed when the PDCP SN flips to avoid the above problems. However, this will result in key refresh, which will cause interruption and signaling overhead.

[0365] Question 3: Multiple sidelink (SL) radio bearers (RBs) can be established between a given [source layer 2ID, destination layer 2ID] pair. Each SLRB between a [source layer 2ID, destination layer 2ID] pair has a unique LCID. Signaling messages are carried on the SLRBs. The bearer (S1-SRB0) with LCID=0 will be used to carry unprotected PC5-S signaling messages. The bearer (SL-SRB1) with LCID=1 should be used for PC5-S signaling messages that are integrity protected only, namely Direct Security Mode Command and Direct Security Mode Complete. The bearer (SL-SRB2) with LCID=2 should be used for other PC5-S signaling messages that are confidentiality and integrity protected. The bearer (SL-SRB3) with LCID=3 is used to carry RRC messages.

[0366] Figure 2G An example of multiple unicast links between user equipments (UEs) associated with V2X according to an embodiment of the present disclosure is shown.

[0367] refer to Figure 2GIn NR, multiple unicast links can be established between the same pair of UEs. UE AUE A sends a direct update key request to UE B. The source layer L2 ID, the destination layer L2 ID and LCID 0 are included in the MAC PDU. If multiple unicast links are established between a pair of UEs, upon receiving this message, UE B cannot determine the unicast link for which UE A requested to update the key. The same problem will occur for Security Mode Command, Security Mode Complete and other signaling messages.

[0368] Question 4: For V2X communication, the UE needs to obtain the V2X SIB from the cell where it is camped. In NR, the V2X SIB can be provided as needed:

[0369] -RRC starts sending an SI request, which triggers the RA process;

[0370] -Send SI request in Msg1 or Msg3 according to configuration;

[0371] - Upon receiving the SI request ACK, the UE obtains the SI from the SI window.

[0372] Critical / delay-sensitive V2X communications may be delayed while providing V2X SIB as needed.

[0373] Example 2-1: Integrity / Confidentiality Protection for One-to-One Communication

[0374] Problem: In LTE-based V2X communication, only PDCP SN is used in PDCP operation. In NR-based V2X communication, PDCP SN and HFN are supported in PDCP operation. When the PDCP SN flips, the HFN is updated. If only PDCP SN is used as input to the integrity and ciphering algorithms, the input parameters (COUNT, DIRECTION, BEARER) will be the same for several packets. This is undesirable from a security point of view. If only PDCP SN is used, keys need to be refreshed when / before the PDCP SN flips to avoid the above issues. However, this results in key refreshes, which cause interruptions and signaling overhead.

[0375] Example 2-1-1: Integrity protection for one-to-one communication

[0376] In an embodiment of the present disclosure for integrity protection of messages, the input parameters of the integrity algorithm are a 128-bit integrity key called KEY, a 48-bit COUNT, a 6-bit bearer identifier called BEARER, a 1-bit direction of transmission (i.e., DIRECTION), and the message itself (i.e., MESSAGE).

[0377] -KEY is the security key used for integrity protection;

[0378] - Direction is set to 1 for direct link signalling sent by a UE sending a Direct Security Mode Command for this security context, otherwise to 0;

[0379] - Set BEARER[0] to BEARER[5] to LCID, where LCID is 6 digits;

[0380] -COUNT[0] to COUNT

[47] are set to K D-sess ID+HFN+PDCP SN;

[0381] *COUNT[0] to COUNT

[15] are set to K D-sess ID;

[0382] *COUNT

[16] to COUNT

[32] are set to HFN;

[0383] *COUNT

[33] to COUNT

[47] are set to PDCP SN.

[0384] Figure 2E The use of the integrity algorithm EIA to authenticate the integrity of the message is shown. Based on these input parameters, the sender calculates a 32-bit message authentication code (MAC-I) using the integrity algorithm EIA. The message authentication code is then attached to the message when it is sent. For the integrity protection algorithm, the receiver calculates the expected message authentication code (XMAC-I) on the received message in the same way as the sender calculates the message authentication code on the sent message, and verifies the data integrity of the message by comparing it with the received message authentication code (i.e., MAC-I).

[0385] Where the integrity algorithm is 128-EIA2 (128-bit Advanced Encryption Standard (AES) in Cipher-based Message Authentication Code (CMAC) mode), the input parameters and message are encoded as follows.

[0386] The bit length of MESSAGE is BLENGTH.

[0387] The input to CMAC mode is a bit string M of length MLen. M is constructed as follows:

[0388] M 0 ..M 47 =COUNT[0]..COUNT

[47]

[0389] M 4 ..M 53 =BEARER[0]..BEARER[5]

[0390] M54 =DIRECTION

[0391] M 55 ..M 63 =0 9 (ie 9 zeros)

[0392] M 64 ..M BLENGTH+63 =MESSAGE[0]..MESSAGE[BLENGTH-1]

[0393] Therefore MLen=BLENGTH+64.

[0394] AES in CMAC mode is used with these inputs to produce a message authentication code T(MACT) of length Tlen=32.

[0395] T is used directly as a 128-EIA2 output MACT[0]..MACT

[31] , where MACT[0] is the most significant bit of T.

[0396] Example 2-1-2: Confidentiality protection for one-to-one communication

[0397] In the embodiment of the present disclosure for confidentiality protection, the input parameters of the encryption algorithm are a 128-bit key named KEY, a 48-bit COUNT, a 6-bit bearer identifier BEARER, a 1-bit direction of transmission (i.e., DIRECTION), and the required length of the key stream (i.e., LENGTH).

[0398] -KEY is a security key used for confidentiality protection;

[0399] - Direction is set to 1 for direct link signalling sent by a UE sending a Direct Security Mode Command for this security context, otherwise to 0;

[0400] - Set BEARER[0] to BEARER[5] to LCID, where LCID is 6 digits;

[0401] -COUNT[0] to COUNT

[47] are set to K D-sess ID+HFN+PDCP SN;

[0402] *COUNT[0] to COUNT

[15] are set to K D-sess ID;

[0403] *COUNT

[16] to COUNT

[32] are set to HFN;

[0404] *COUNT

[33] to COUNT

[47] are set to PDCP SN.

[0405] Figure 2F It is shown that the encryption algorithm EEA is used to encrypt the plaintext by applying the key stream using binary addition of each bit of the plaintext and the key stream. The plaintext can be recovered by using the same input parameters and applying the same key stream generated by binary addition of each bit of the ciphertext.

[0406] Based on the input parameters, the algorithm generates an output keystream block KEYSTREAM, which is used to encrypt the input plaintext block PLAINTEXT to produce an output ciphertext block CIPHERTEXT.

[0407] The input parameter LENGTH will affect only the length of the KEYSTREAMBLOCK, not the actual bits in it.

[0408] In case the integrity algorithm is 128-EEA2 (128-bit AES in counter (CTR) mode), CTR mode T 1 、T 2 ,…,T i , ... The sequence of 128-bit counter blocks required should be constructed as follows:

[0409] The most significant 64 bits of T1 are COUNT[0]..COUNT

[47] / BEARER[0]..BEARER[5] / DIRECTION / 0 9 (i.e., 9 zero bits). The bits are written from the most significant bit on the left to the least significant bit on the right, so for example COUNT[0] is T 1 The most significant bit of .

[0410] T 1 The least significant 64 bits are all 0.

[0411] Subsequent counter blocks are then obtained by applying the standard integer increment function mod 264 to the least significant 64 bits of the previous counter block.

[0412] Embodiment 2-2: Security key of RRC message for one-to-one communication

[0413] Problem: In 4G wireless communication systems, signaling messages for unicast communication are generated by the PC5 protocol layer and carried on the radio bearer on the user plane. In 5G wireless communication systems, RRC between UEs is also supported for unicast communication. Therefore, in addition to the signaling messages generated by the PC5 protocol layer, signaling messages are also generated by RRC. The problem is that security keys are used for integrity and confidentiality protection of RRC messages exchanged between UEs for unicast communication.

[0414] Example 2-2-1

[0415] Figure 2H An example of a security key hierarchy according to an embodiment of the present disclosure is shown.

[0416] refer to Figure 2H In addition to PIK and PEK, UE also obtains D-sess Generate two additional security keys (PEKrrc(2h-10) and PIKrrc(2h-20)). The key hierarchy is in Figure 2H Shown in.

[0417] -PIK is used for integrity protection of PC5-S signaling messages.

[0418] -PEK is used for confidentiality protection of PC5-S signaling messages.

[0419] -PIKrrc (2h-20) is used for integrity protection of PC5-RRC signaling messages.

[0420] -PEKrrc (2h-10) is used for confidentiality protection of PC5-RRC signaling messages.

[0421] When from K D-sess When generating a PIK or PEK or PEKrrc(2h-10) or PIKrrc(2h-20), the following parameters shall be used to form the input S to the KDF specified in Annex B of TS 33.220:

[0422] - FC = 0x4B;

[0423] - P0 = 0x00, if the PEK is being exported; or

[0424] - P0 = 0x01, if the PIK is being exported; or

[0425] - P0 = 0x02, if PEKrrc is being exported; or

[0426] - P0 = 0x03, if PIKrrc is being exported;

[0427] - L0 = length of P0 (i.e. 0x00 0x01);

[0428] - P1 = algorithm identifier (note that the algorithm identifier can be different for RRC and PC5-S keys);

[0429] - L1 = length of the algorithm identifier (ie, 0x00 0x01).

[0430] The PDCP layer in the UE will then use one of these keys for protection depending on the type of message being sent and received (using the method explained above). If the PDCP counter of the SLRB (i.e., the PDCP COUNT including the HFN and PDCP SN) of any of the PC5-S signaling messages and / or PC5-RRC signaling messages carrying a unicast connection between a pair of UEs rolls over or is about to roll over, the re-key procedure is initiated to generate a new K D-sess . Then generate PEKrrc, PIKrrc, PIK and PEK again.

[0431] Example 2-2-2

[0432] Fig.2I Another example of a security key hierarchy according to an embodiment of the present invention is described.

[0433] Reference Fig.2I , UE generates K from the root key D-sess and K D-sess-rrc (2i-10). The key hierarchy is Fig.2I Shown in.

[0434] -PIK and PEK then self-K D-sess Export out.

[0435] -PIKrrc(2i-30) and PEKrrc(21-20) from K D-sess-rrc Export out.

[0436] -PIK is used for integrity protection of PC5-S signaling messages.

[0437] -PEK is used for confidentiality protection of PC5-S signaling messages.

[0438] -PIKrrc(2i-30) is used for integrity protection of PC5-RRC signaling messages.

[0439] -PEKrrc(2i-20) is used for confidentiality protection of PC5-RRC signaling messages.

[0440] When from K D-sess When generating a PIK or PEK, the following parameters are used to form the input S to the Key Derivation Function (KDF) specified in Annex B of TS 33.220:

[0441] -FC=0x4B

[0442] - P0 = 0x00, if the PEK is being exported, or

[0443] - P0 = 0x01 if the PIK is being exported

[0444] -L0 = length of P0 (i.e. 0x00 0x01)

[0445] P1 = Algorithm Identifier (Note that the algorithm identifier can be different for RRC and PC5-S keys)

[0446] - L1 = length of the algorithm identifier (ie, 0x00 0x01).

[0447] When from K D-sess-rrc When generating PEKrrc(2i-20) or PIKrrc(2i-30), the following parameters are used to form the input S to the KDF specified in Annex B of TS33.220:

[0448] -FC=0x4B

[0449] - P0 = 0x00, if PEKrrc is being exported, or

[0450] - P0 = 0x01, if PIKrrc is being exported

[0451] -L0 = length of P0 (i.e. 0x00 0x01)

[0452] -P1 = Algorithm identifier

[0453] - L1 = length of the algorithm identifier (ie, 0x00 0x01).

[0454] The PDCP layer in the UE will then use one of these keys for protection depending on the type of message being sent and received (using the method explained earlier).

[0455] - If the PDCP counter of the SLRB carrying the PC5-S signaling message for a unicast connection between a pair of UEs rolls over or is about to roll over, the re-key procedure is initiated to generate a new K D-sess . Then generate PIK and PEK again.

[0456] - If the PDCP counter of the SLRB carrying the PC5-RRC signaling message of the unicast connection between a pair of UEs rolls over or is about to roll over, the re-key procedure is initiated to generate a new K D-sess-rrc . Then generate PIKrrc and PEKrrc again.

[0457] Example 2-2-3

[0458] Figure 2J Another example of a security key hierarchy according to an embodiment of the present invention is shown.

[0459] Reference Figure 2J UE from K D-sessGenerate two security keys. The key hierarchy is in Figure 2J Shown in.

[0460] PIK (2j-20) is used for integrity protection of PC5-S and PC5-RRC signaling messages and user services.

[0461] PEK (2j-10) is used for confidentiality protection of PC5-S and PC5-RRC signaling messages and user services.

[0462] When from K D-sess When generating a PIK or PEK, the following parameters are used to form the input S to the KDF specified in Annex B of TS33.220:

[0463] -FC=constant (e.g., 0x4B or 0x7E), where 0x4B is used when the communication between the UE pair uses the sidelink communication based on the first RAT (i.e., LTE), and 0x7E is used when the communication between the UE pair uses the sidelink communication based on the second RAT (i.e., NR).

[0464] - P0 = 0x00, if the PEK is being exported, or

[0465] - P0 = 0x01, if the PIK is being exported, or

[0466] -L0 = length of P0 (i.e. 0x00 0x01)

[0467] -P1 = Algorithm identifier

[0468] - L1 = length of the algorithm identifier (ie, 0x00 0x01).

[0469] The PDCP layer in the UE will then use one of these keys to protect (using the method explained earlier) the messages and user traffic sent and received between a pair of UEs. If the PDCP counters (i.e., the PDCP counters including the HFN and SN) of SL SRB1 or SL SRB2 (SL SRB1 and SL SRB2 carry PC5-S signaling messages that need to be protected) and / or SL SRB3 (SL SRB3 carries PC5-RRC signaling messages) or any SLDRB of a unicast connection between a pair of UEs rolls over or is about to roll over, the rekey procedure is initiated to generate a new K D-sess . Then generate PIK and PEK again.

[0470] Embodiment 2-3: Handling multiple unicast connections / links associated with the same source layer L2 ID and destination layer L2 ID

[0471] Several SLRBs can be established between a given [source layer 2ID, destination layer 2ID] pair. Each SLRB between a [source layer 2ID, destination layer 2ID] pair has a unique LCID. Signaling messages are transmitted on SLSRBs. The bearer (SL-SRB0) with LCID=0 should be used to carry unprotected PC5-S signaling messages. The bearer (SL-SRB1) with LCID=1 should be used for direct security mode commands and direct security mode completion. The bearer (SL-SRB2) with LCID=2 should be used for other PC5-S signaling messages with confidentiality and integrity protected. The bearer (SL-SRB3) with LCID=3 will be used for other PC5-RRC signaling messages with confidentiality and integrity protected.

[0472] In NR, multiple unicast links can be established between the same pair of UEs. UE A sends a direct update key request to UE B. The source layer L2 ID, the destination layer L2 ID and LCID 0 are included in the MAC PDU. If multiple unicast links are established between a pair of UEs, upon receiving this message, UE B cannot determine the unicast link for which UE A requested the key update. The same problem will occur for Security Mode Command, Security Mode Complete and other signaling messages.

[0473] Example 2-3-1

[0474] In a first method of the present disclosure, a PC5-S message of a [source layer L2 ID, destination layer L2 ID] pair is mapped to one of three SL radio bearers regardless of an associated unicast link.

[0475] - The bearer with LCID=0 (SL-SRB0) carries unprotected signalling messages.

[0476] - Bearer with LCID=1 (SL-SRB0) is used for Direct Security Mode Command and Direct Security Mode Complete.

[0477] - The bearer with LCID = 2 (SL-SRBO) is used for other signalling messages which are confidentiality and integrity protected.

[0478] The unicast link ID is included in the PDCP header by the transmitter. The upper layers provide the unicast link ID to the AS along with the PC5-S signaling message. Based on the receiver, the UE can map the received message to the appropriate unicast link and apply the security context accordingly. In an alternative embodiment, the unicast link ID can be included in the MAC PDU or the side link control information (SCI).

[0479] Assume that there are two unicast links: link #1 and link #2 between UE A and UE B.

[0480] -UE A L2 ID::X; UE B L2 ID::Y

[0481] -UE A sends an update key request for link #1

[0482] - Map the Update Key Request to the SLRB associated with [Source Layer L2 ID: X, Destination Layer L2 ID: Y, LCID 0]

[0483] - Set LinkID to Link#1 in the PDCP header

[0484] - [Source layer L2 ID: X, destination layer L2 ID: Y, LCID: 0] is added to the MAC header

[0485] -UE B receives a MAC PDU addressed to [source layer L2 ID: X, destination layer L2 ID: Y, LCID: 0]

[0486] *UE maps the received MAC SDU to the SLRB associated with [source layer L2 ID: X, destination layer L2 ID: Y, LCID 0]

[0487] *Based on LCID 0, it is known that this is a signaling message and is unprotected. Based on LinkID, the unicast link associated with the packet is determined.

[0488] Example 2-3-2

[0489] In the second method of the present disclosure, regardless of the associated unicast link, PC5-S messages for the [source layer L2ID, destination layer L2ID] pair are mapped to a single SL radio bearer. The bearer with LCID=X carries all PC5-S signaling messages, where X is predefined or reserved.

[0490] The unicast link ID is included in the PDCP header by the transmitter. Based on this, the receiver can map the received message to the appropriate unicast link and apply the security context accordingly. In an alternative embodiment, the unicast link ID can be included in the MAC PDU or SCI.

[0491] The security protection type is included by the transmitter in the PDCP header. The security protection type can be set to no protection, integrity only protected, integrity and confidentiality protected. Based on this, the receiver can determine the security level and process the data packet accordingly.

[0492] Assume that there are two unicast links: link #1 and link #2 between UE A and UE B.

[0493] -UE A L2 ID: X; UE B L2 ID: Y

[0494] -UE A sends a signaling message for link #1

[0495] - Signaling messages are mapped to the SLRB associated with [source layer L2 ID: X, destination layer L2 ID: Y, LCID A]

[0496] - Set LinkID to Link#1 in the PDCP header

[0497] - [Source layer L2 ID: X, destination layer L2 ID: Y, LCID: A] is added to the MAC header

[0498] -UE B receives a MAC PDU addressed to [source layer L2 ID: X, destination layer L2 ID: Y, LCID: A]

[0499] *UE maps the received MAC SDU to the SLRB associated with [source layer L2 ID: X, destination layer L2 ID: Y, LCID A]

[0500] *Based on LCID A, it is known that this is a signaling message. Based on LinkID, the unicast link associated with the packet is determined. Based on the security protection type field, it is known whether no protection, integrity only protection, integrity and confidentiality protection are applied to the received signaling message.

[0501] Example 2-3-3

[0502] In the third method of the present disclosure, the PC5-S message for [source layer L2 ID, destination layer L2 ID, unicast link ID] is mapped to one of three SL radio bearers.

[0503] - The bearer with LCID=0 (SL-SRB0) carries unprotected signalling messages.

[0504] - Bearer with LCID=1 (SL-SRB0) is used for Direct Security Mode Command and Direct Security Mode Complete.

[0505] - The bearer with LCID = 2 (SL-SRB0) is used for other signalling messages with confidentiality and integrity protected.

[0506] The unicast link ID is included in the MAC PDU by the transmitter. Based on this, the UE can map the received MAC SDU to the appropriate SL radio bearer.

[0507] Embodiment 2-4-1: MAC PDU format for including link ID (Option 1)

[0508] Figure 2K An example of a MAC PDU structure including a link ID according to an embodiment of the present disclosure is shown.

[0509] refer to Figure 2K , the link ID is included in the SL SCH MAC header of the SL SCH MAC PDU as shown in 2K-10. Therefore, the MAC SDU of one unicast link is multiplexed in the MAC PDU.

[0510] In one embodiment, the Link ID field may always be present in the SL SCH MAC header. For broadcast / multicast, it may be set to a predetermined value.

[0511] Alternatively, for unicast MAC PDUs only, the Link ID field may be included in the SL SCH MAC header.A unicast MAC PDU may be indicated via 1 bit in the SCI or MAC header or using the V bit in the MAC header, or may be implicitly determined based on the L2 ID.

[0512] In this option, for each MAC PDU associated with the SCI:

[0513] Operation 1: Selecting a ProSe target layer of a sidelink logical channel having the highest priority among sidelink logical channels having data available for transmission and having the same transmission format as the selected sidelink logical channel corresponding to the ProSe target layer;

[0514] Operation 2: Allocate resources to a sidelink logical channel having the highest priority among the sidelink logical channels that belong to the selected ProSe target layer and have data available for transmission;

[0515] Operation 3: If the logical channel selected in operation 2 is unicast: If any resources remain, the sidelink logical channels and unicast links belonging to the selected ProSe destination layer of the logical channel selected in operation 2 are served in descending order of priority until the data of the sidelink logical channel or the SL grant is exhausted, whichever occurs first. Sidelink logical channels configured with the same priority should be served equally.

[0516] Action 3: If the logical channel selected in Action 2 is not unicast: If any resources remain, the sidelink logical channels belonging to the selected ProSe destination layer are served in descending order of priority until the data of the sidelink logical channel or the SL grant is exhausted, whichever occurs first. Sidelink logical channels configured with the same priority should be served equally.

[0517] Embodiment 2-4-2: MAC PDU format for including link ID (Option 2)

[0518] Figure 2L Another example of a MAC PDU structure including a link ID according to an embodiment of the present disclosure is shown.

[0519] refer to Figure 2L , the link ID is included in the SLSCH MAC subheader of the SL SCH MAC SDU in the SL SCH MAC PDU, as shown in 21-20. Therefore, MAC SDUs of different unicast links can be multiplexed in the MAC PDU.

[0520] In one embodiment, the Link ID field may always be present in the SL SCH MAC subheader. For broadcast / multicast, it may be set to a predetermined value.

[0521] Alternatively, the Link ID field may be included in the SL SCH MAC subheader only for unicast MAC PDUs.A unicast MAC PDU may be indicated via 1 bit in the SCI or MAC header or using the V bit in the MAC header, or may be implicitly determined based on the L2 ID.

[0522] Embodiment 2-5: Handling interruption caused by SI acquisition

[0523] Problem: For V2X communication, UE needs to obtain V2X SIB from the camped cell. In NR, V2X SIB can be provided on demand.

[0524] -RRC initiates the sending of SI request, which triggers the RA process

[0525] -Send SI request in Msg1 or Msg3 depending on configuration

[0526] - Upon receiving the SI request ACK, the UE obtains the SI from the SI window

[0527] Critical / delay-sensitive V2X communications may be delayed while providing V2X SIB as needed.

[0528] method:

[0529] -UE obtains SIB1 from the camping / serving cell.

[0530] * According to SIB1, V2X SIB is supported in the camping / serving cell. V2X SIB is not broadcast but provided on demand.

[0531] -Initiate V2X service. UE initiates the acquisition of V2X SIB.

[0532] *On-demand SI request process is initiated to obtain V2X SIB.

[0533] -Until V2X SIB acquisition is completed

[0534] * Option 1: The UE uses an abnormal resource pool for V2X communication, where the abnormal resource pool is provided in the pre-configuration.

[0535] *Option 2: The UE uses the pre-configured transmission resource pool for V2X communication.

[0536] * Option 3: If the UE is not within the coverage of the frequency required to perform V2X communication, the UE performs Option 1 or Option 2.

[0537] *Once V2X SIB acquisition is completed,

[0538] **UE uses the resource pool indicated in the acquired V2X SIB for V2X communication (if UE is idle / inactive)

[0539] **UE requests resources from gNB. UE uses resources configured in dedicated signaling (if UE is in connected state).

[0540] Embodiment 2-6: SI on demand in RRC connection

[0541] In the RRC connected state to obtain non-broadcast SIBs, the UE sends / transmits an SI request message (i.e., an RRC message including a list of one or more SIBs required by the UE) to the gNB.

[0542] The gNB sends a response (e.g., RRCReconfiguration message) including one or more SIBs requested by the UE. If the response (e.g., RRCReconfiguration message) cannot accommodate all requested SIBs due to the limitation of the response message size, some mechanism is required to obtain the remaining requested SIBs.

[0543] - Option 1: In one embodiment, the UE may resend a request for the SIB(s) which is not included in the response (eg, RRCReconfiguration message).

[0544] - Option 2: In an alternative embodiment, the gNB may send multiple responses (e.g., RRCReconfiguration messages), each including a subset of the requested SIBs.

[0545] * In this option, upon receiving a response (eg, RRCReconfiguration message), how does the UE know whether there is another response (eg, RRCReconfiguration message) message.

[0546] *In one embodiment, if the response (e.g., RRCReconfiguration message) does not include all requested SIBs, the UE may wait for a period of time before sending the request again. The waiting time may be UE-implemented or predefined (e.g., 1) or configured by the gNB in ​​RRC signaling.

[0547] *In an alternative embodiment, the response (eg, RRCReconfiguration message) may include some indication as to whether the remaining SIBs are in another response (eg, RRCReconfiguration message).

[0548] - Option 3: In an alternative embodiment, the gNB may broadcast SIBs that were requested but not included in the response (e.g., RRCReconfiguration message). Therefore, upon receiving a response (e.g., RRCReconfiguration message) in which all requested SIBs are not included, the UE assumes that those SIBs are broadcast by the gNB. The UE obtains the SIBs from the SI window moments of those SIBs in the current modification cycle. Alternatively, the UE obtains the SIBs from the SI window moments of those SIBs in the next modification cycle. Alternatively, the UE obtains the SIBs from the SI window moments of those SIBs in the current modification cycle or the next modification cycle.

[0549] In one embodiment, the source gNB forwards the most recent SI request message received from the UE to target the gNB during handover. The SI request message may be included in the IEAS context. The AS context is then sent in the handover preparation message to target the gNB. The advantage is that the UE can avoid sending an SI request message in the target cell at handover. Note that if the content of the SI request to be sent in the target cell is different from the content of the last SI request message sent in the source gNB, the UE will send an SI request message to the target cell at handover.

[0550] In the current design, if no common search space is configured in the active DL BWP, the UE does not monitor the SI update indication. It is assumed that the updated SI (required in connected state) is provided via dedicated RRC signaling. How does the gNB know which SIB is required for the UE in connected state? This is not an issue in Rel15 as all UEs only need SIB1.

[0551] - Option 1: In one embodiment, the UE can inform the gNB which SIB(s) it needs. Hence, whenever these SIBs are updated and no common search space for SI acquisition / paging is configured in the active BWP, the gNB provides the updated SIBs in dedicated RRC signaling.

[0552] - Option 2: In another embodiment, if no common search space for SI acquisition / paging is configured in the active BWP, the gNB can always provide all updated SIBs that the UE may need to connect to in dedicated RRC signaling.

[0553] - Option 3: In another embodiment, the gNB may use other feature-specific messages / content to know which SIBs are required by the UE. Hence, whenever these SIBs are updated and no common search space for SI acquisition / paging is configured in the active BWP, the gNB provides the updated SIBs in dedicated RRC signaling.

[0554] In one embodiment, the SI request process in the RRC connection may be as follows:

[0555] The RRC initiates sending a SI request message (i.e., an RRC message including a list of one or more SIBs required by the UE) to the gNB.

[0556] Upon receiving the RLC ACK / HARQ ack for the SI request, the UE starts the timer.

[0557] - If the UE receives a response corresponding to the sent SI request (e.g., RRCReconfiguration message), the timer is stopped. It may include one or more requested SIBs.

[0558] - If the timer expires, the UE acquires the requested SIBs from the SI window occasions of those SIBs in the modification period of receiving RLC ACK / HARQ ack.

[0559] In an alternative embodiment, the SI request procedure in an RRC connection may be as follows:

[0560] The RRC initiates sending a SI request message (i.e., an RRC message including a list of one or more SIBs required by the UE) to the gNB.

[0561] The UE starts a timer.

[0562] - If the UE receives a response corresponding to the sent SI request (e.g., RRCReconfiguration message), the timer is stopped. It may include one or more requested SIBs.

[0563] - If the timer expires, the UE obtains the requested SIBs from the SI window instances of those SIBs in the current modification period.

[0564] - (Backup) If the timer expires, the UE acquires the requested SIBs from the SI window occasion of those SIBs in the next modification period.

[0565] - (Backup) If the timer expires, the UE obtains the requested SIBs from the SI window instances of those SIBs in the current and next modification period.

[0566] In one embodiment, after sending the SI Request message, the UE waits for a response from the gNB. Upon receiving a response (e.g., an RRCReconfiguration message) in which the requested SIB(s) are not included (i.e., the Response IE in the message is empty), the UE assumes that the requested SIB(s) are broadcast by the gNB. The UE obtains them from the SI window moments of those SIBs in the current modification period. Alternatively, the UE obtains them from the SI window moments of those SIBs in the next modification period. Alternatively, the UE obtains them from the SI window moments of those SIBs in the current modification period or the next modification period. In one embodiment, the gNB may indicate the number of modification periods or indicate the current / next modification period in the response (e.g., an RRCReconfiguration message) for obtaining the requested SIB(s).

[0567] Figure 2M is a block diagram of a terminal according to an embodiment of the present disclosure.

[0568] Reference Figure 2M The terminal includes a transceiver 2m-10, a controller 2m-20, and a memory 2m-30. The controller 2m-20 may refer to a circuit, an application-specific integrated circuit (ASIC), or at least one processor. The transceiver 2m-10, the controller 2m-20, and the memory 2m-30 are configured to perform the operations of the UE shown in the figure, for example, Figures 2A to 2L Operation of the UE shown, or as described above. Although the transceiver 2m-10, the controller 2m-20, and the memory 2m-30 are shown as separate entities, they can be implemented as a single entity, such as a single chip. Alternatively, the transceiver 2m-10, the controller 2m-20, and the memory 2m-30 can be electrically connected or coupled to each other.

[0569] The transceiver 2m-10 may send and receive signals to and from other network entities (eg, base stations).

[0570] The controller 2m-20 can control the terminal to perform the functions according to one of the above embodiments. For example, the controller 2m-20 controls the transceiver 2m-10 and / or the memory 2m-30 to perform integrity protection and / or confidentiality protection using a security key.

[0571] In one embodiment, the operation of the terminal can be implemented using a memory 2m-30 storing corresponding program codes. Specifically, the terminal can be equipped with a memory 2m-30 to store program codes for implementing desired operations. In order to perform the desired operation, the controller 2m-20 can read and execute the program codes stored in the memory 2m-30 by using at least one processor or central processing unit (CPU).

[0572] Figure 2N is a block diagram of a base station according to an embodiment of the present disclosure.

[0573] Reference Figure 2N The base station includes a transceiver 2n-10, a controller 2n-20, and a memory 2n-30. The controller 2n-20 may refer to a circuit, an application specific integrated circuit (ASIC), or at least one processor. The transceiver 2n-10, the controller 2n-20, and the memory 2n-30 are configured to perform the operations of the UE shown in the figure, such as Figures 2A to 2L Operation of the UE shown, or as described above. Although the transceiver 2n-10, the controller 2n-20 and the memory 2n-30 are shown as separate entities, they can be implemented as a single entity, such as a single chip. Alternatively, the transceiver 2n-10, the controller 2n-20 and the memory 2n-30 can be electrically connected or coupled to each other.

[0574] The transceiver 2n-10 may send signals to and receive signals from other network entities (eg, terminals).

[0575] The controller 2n-20 may control the UE to perform a function according to one of the above embodiments. For example, the controller 2n-20 controls the transceiver 2n-10 and / or the memory 2n-30 to perform integrity protection and / or confidentiality protection using a security key.

[0576] In one embodiment, the operation of the base station can be implemented using a memory 2n-30 storing corresponding program codes. Specifically, the base station can be equipped with a memory 2n-30 to store program codes for implementing the desired operation. In order to perform the desired operation, the controller 2n-20 can read and execute the program code stored in the memory 2n-30 by using at least one processor or central processing unit (CPU).

[0577] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.

[0578] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving a radio resource control (RRC) reconfiguration message from a base station, the RRC reconfiguration message comprising a physical downlink control channel (PDCCH) configuration for a downlink bandwidth part (BWP) of a specific cell (SpCell), wherein the RRC reconfiguration message comprises one or more search space configurations, one or more control resource set (CORESET) configurations, information about a power saving radio network temporary identifier (PS-RNTI), and information about a PS offset, and wherein a search space configuration of the one or more search space configurations is associated with a wake-up signal (WUS), and the search space configuration is associated with a CORESET configuration of the one or more CORESET configurations; Based on the search space configuration and the CORESET configuration, identifying a PDCCH monitoring opportunity for the WUS; and Based on the PS-RNTI and the PS offset, receiving downlink control information DCI including the WUS from the base station on the SpCell by monitoring the PDCCH monitoring opportunity; The PS-RNTI and the PS offset are cell-specific for the SpCell.

2. The method according to claim 1, in, The PDCCH configuration for the downlink BWP of the SpCell includes the one or more search space configurations and the one or more control resource set CORESET configurations.

3. The method according to claim 1, wherein: The search space configuration and the CORESET configuration are BWP-specific for the downlink BWP.

4. The method according to claim 1, wherein: In a case where a short discontinuous reception DRX cycle and a long DRX cycle are configured for the terminal, monitoring the PDCCH monitoring opportunity for the DCI including the WUS during the long DRX cycle, and Wherein the method further comprises: A DRX operation is performed based on the received WUS.

5. A method performed by a base station in a wireless communication system, the method comprising: Sending a radio resource control RRC reconfiguration message to a terminal, the RRC reconfiguration message including a physical downlink control channel PDCCH configuration for a downlink bandwidth part BWP of a specific cell SpCell, wherein the RRC reconfiguration message includes one or more search space configurations, one or more control resource set CORESET configurations, information about a power saving radio network temporary identifier PS-RNTI, and information about a PS offset, and wherein a search space configuration in the one or more search space configurations is associated with a wake-up signal WUS, and the search space configuration is associated with a CORESET configuration in the one or more CORESET configurations; and In a PDCCH monitoring opportunity of the WUS based on the search space configuration and the CORESET configuration, sending downlink control information DCI including the WUS to the terminal on the SpCell, where the DCI is sent based on the PS-RNTI and the PS offset; The PS-RNTI and the PS offset are cell-specific for the SpCell.

6. The method according to claim 5, in, The PDCCH configuration for the downlink BWP of the SpCell includes the one or more search space configurations and the one or more control resource set CORESET configurations.

7. The method according to claim 5, wherein: The search space configuration and the CORESET configuration are BWP-specific for the downlink BWP.

8. The method according to claim 5, wherein: In a case where a short discontinuous reception DRX cycle and a long DRX cycle are configured for the terminal, sending the DCI including the WUS in the PDCCH monitoring opportunity during the long DRX cycle, and Wherein a DRX operation is performed based on the transmitted WUS.

9. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as A controller configured to: receiving, via the transceiver, a radio resource control RRC reconfiguration message from a base station, the RRC reconfiguration message comprising a physical downlink control channel PDCCH configuration for a downlink bandwidth part BWP of a specific cell SpCell, wherein the RRC reconfiguration message comprises one or more search space configurations, one or more control resource set CORESET configurations, information about a power saving radio network temporary identifier PS-RNTI, and information about a PS offset, wherein a search space configuration in the one or more search space configurations is associated with a wake-up signal WUS, and the search space configuration is associated with a CORESET configuration in the one or more CORESET configurations; Based on the search space configuration and the CORESET configuration, identifying a PDCCH monitoring opportunity for the WUS; and Receiving, via the transceiver, downlink control information DCI including the WUS from the base station on the SpCell by monitoring the PDCCH monitoring opportunity based on the PS-RNTI and the PS offset; The PS-RNTI and the PS offset are cell-specific for the SpCell.

10. The terminal according to claim 9, in, The PDCCH configuration for the downlink BWP of the SpCell includes the one or more search space configurations and the one or more control resource set CORESET configurations.

11. The terminal according to claim 9, wherein: The search space configuration and the CORESET configuration are BWP-specific for the downlink BWP.

12. The terminal according to claim 9, wherein: In a case where a short discontinuous reception DRX cycle and a long DRX cycle are configured for the terminal, monitoring the PDCCH monitoring opportunity for the DCI including the WUS during the long DRX cycle, and The controller is further configured to: A DRX operation is performed based on the received WUS.

13. A base station in a wireless communication system, the base station comprising: Transceiver; as well as A controller configured to: sending, via the transceiver, a radio resource control RRC reconfiguration message to a terminal, the RRC reconfiguration message comprising a physical downlink control channel PDCCH configuration for a downlink bandwidth part BWP of a specific cell SpCell, wherein the RRC reconfiguration message comprises one or more search space configurations, one or more control resource set CORESET configurations, information about a power saving radio network temporary identifier PS-RNTI, and information about a PS offset, and wherein a search space configuration in the one or more search space configurations is associated with a wake-up signal WUS, and the search space configuration is associated with a CORESET configuration in the one or more CORESET configurations; and Sending, via the transceiver, downlink control information DCI including the WUS to the terminal on the SpCell in a PDCCH monitoring opportunity of the WUS based on the search space configuration and the CORESET configuration, wherein the DCI is sent based on the PS-RNTI and the PS offset; The PS-RNTI and the PS offset are cell-specific for the SpCell.

14. The base station according to claim 13, in, The PDCCH configuration for the downlink BWP of the SpCell includes the one or more search space configurations and the one or more control resource set CORESET configurations.

15. The base station according to claim 13, wherein: The search space configuration and the CORESET configuration are BWP-specific for the downlink BWP.

16. The base station according to claim 13, wherein: In a case where a short discontinuous reception DRX cycle and a long DRX cycle are configured for the terminal, sending the DCI including the WUS in the PDCCH monitoring opportunity during the long DRX cycle, and Wherein a DRX operation is performed based on the transmitted WUS.

Images