Measurement setting method

Abstract

The present disclosure describes a method, system, and apparatus for configuring a measurement object in a wireless communication network. A plurality of candidate serving cell measurement object (MO) identifiers (IDs) are provided from a centralized unit (CU) to a distributed unit (DU). A serving cell MO is selected by the DU from the plurality of candidate serving cell MO IDs to be used for a user equipment (UE). A serving cell MO configuration per bandwidth part (BWP) is configured by the DU according to the serving cell MO.

Description

[Technical field]

[0001] The subject matter of this application relates generally to wireless communications. In particular, the subject matter of this application relates to methods, apparatus and systems for configuring measurement targets in wireless communications networks. [Background technology]

[0002] Measurements may be useful in determining properties of a wireless network under a given configuration. Measurements can inform decisions of wireless participants, such as user equipment and base stations, so that resources can be better managed and quality of service improved. Measurement techniques in wireless communication systems of the present application suffer from various deficiencies, limitations and shortcomings, which necessitate the inventive systems, methods, components and apparatus described herein. Summary of the Invention [Problem to be solved by the invention]

[0003] The subject matter of this application relates to methods, devices and systems for improving measurement techniques in wireless communications, and more particularly to configuring a bandwidth part (BWP) that includes a non-cell defining synchronization signal block (NCD-SSB). Techniques are disclosed for configuring a measurement configuration following a BWP that includes an NCD-SSB. [Means for solving the problem]

[0004] In some embodiments, a method for measurement configuration in a wireless communication network includes providing a plurality of candidate serving cell measurement object (MO) identifiers (IDs) from a centralized unit (CU) to a distributed unit (DU), selecting, by the DU, a serving cell MO to be used for a user equipment (UE) from the plurality of candidate serving cell MO IDs, and configuring, by the DU, a serving cell MO configuration per bandwidth (BWP) according to the serving cell MO.

[0005] In some embodiments, a method for measurement configuration in a wireless communication network includes sending a message from a DU to a CU indicating BWP configuration information of a UE, sending a serving cell MO configuration to the DU by the CU, and configuring a serving cell MO identifier for the UE by the DU in accordance with the serving cell MO configuration.

[0006] In some embodiments, a method for measurement configuration in a wireless communication network includes transmitting, by a CU, a UE context setup response message to a DU, the UE context setup response message including at least one of: a dedicated system information delivery is required, an active downlink BWP does not include CD-SSB, the active downlink BWP is not configured to have a common search space for system information reception, or the active downlink BWP is a reduced capability (RedCap) specific initial downlink BWP.

[0007] In some other embodiments, an apparatus for wireless communication comprises a memory storing instructions and a processing circuit in communication with the memory, the processing circuit being configured to perform the above-described method when the processing circuit executes the instructions.

[0008] In some other embodiments, an apparatus for wireless communication includes a memory storing instructions and a processing circuit in communication with the memory, the processing circuit being configured to perform the above-described method when the processing circuit executes the instructions.

[0009] In some other embodiments, a computer readable medium includes instructions that, when executed by a computer, cause the computer to perform the above-described method.

[0010] These and other aspects and their implementations are described in greater detail in the drawings, specification and claims. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a wireless communication system including one radio base station and one or more user equipments. [Diagram 2] FIG. 2 illustrates an example of a base station. [Diagram 3] FIG. 2 illustrates an example of a user device. [Figure 4] FIG. 2 illustrates an example of a base station. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The present subject matter will now be described in detail with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific embodiments of the present subject matter, and because the present subject matter may be embodied in many different forms, it is not intended that the claimed subject matter covered or claimed be construed as being limited to any of the embodiments set forth below.

[0013] Throughout the specification and claims, terms may have subtle meanings suggested or implied by the context beyond the explicitly stated meaning. Similarly, "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. "In one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, and the phrase "in another implementation" or "in other implementations" as used herein do not necessarily refer to different implementations. For example, the claimed subject matter is intended to include combinations of all or part of the example embodiments or implementations.

[0014] Generally, terms can be understood, at least in part, from their use in context. For example, the terms "and," "or," or "and / or" as used herein may include various meanings that depend, at least in part, on the context in which such terms are used. In general, when used to relate a list such as A, B, or C, "or" may mean A, B, and C (used herein in an inclusive sense) or A, B, or C (used herein in an exclusive sense). Also, the terms "one or more" or "at least one" as used herein may be used to describe any feature, structure, or characteristic in a singular sense or to describe a combination of features, structures, or characteristics in a plural sense, at least in part, depending on the context. Similarly, the terms "a," "one," "the," and the like may be understood to convey a singular usage or to convey a plural usage, at least in part, depending on the context. Also, the terms "based on" or "determined by" may be understood not necessarily to be intended to convey an exclusive set of elements. Alternatively, the presence of additional elements not necessarily explicitly recited may be permitted, also depending at least in part on the context.

[0015] 1 is a diagram illustrating an exemplary wireless communication system 100 including multiple communication nodes (or nodes for short) configured to wirelessly communicate with each other. Generally, the communication nodes include at least one user equipment 102 and at least one radio access node 104. The exemplary wireless communication system 100 of FIG. 1 is shown including two user equipments 102, including a first user equipment 102(1) and a second user equipment 102(2), and one radio access node 104. However, various other examples of wireless communication systems 100 including any of various combinations of one or more user equipments 102 and / or one or more radio access nodes 104 are possible.

[0016] In general, the user devices described herein, e.g., user device 102, may comprise a single electronic device or appliance or multiple electronic devices or appliances (e.g., a network thereof) capable of wireless communication over a network. A user device may include or be referred to as a user terminal, user terminal device, or user equipment (UE). A user device may also be or include, but is not limited to, a mobile device (e.g., a mobile phone, a smartphone, a smart watch, a tablet, a laptop computer, a vehicle or other vessel (human, motor, or engine powered, e.g., as non-limiting examples, a car, an airplane, a train, a boat, or a bicycle), or a fixed or stationary device (a desktop computer or other computing device that is not typically mobile for long periods of time, e.g., as non-limiting examples, a home appliance, other relatively heavy device including the Internet of Things (IoT), or a computing device used in a commercial or industrial environment). In various embodiments, the user device 102 may comprise a transceiver circuit 106 coupled to an antenna 108 to achieve wireless communication with the wireless access node 104. The transceiver circuitry 106 may also be coupled to a processor 110, which may also be coupled to a memory 112 or other storage device. The memory 112 may store instructions or code that, when read and executed by the processor 110, cause the processor 110 to implement the various methods described herein.

[0017] Additionally, generally, the radio access nodes described herein, e.g., the radio access node 104, may include a single electronic device or equipment, or multiple electronic devices or equipment (e.g., a network thereof), and may include one or more base stations or other radio network access points capable of wirelessly communicating with one or more user devices and / or one or more other radio access nodes 104 over a network. For example, the radio access node 104 may include a 4G LTE base station, a 5G NR base station, a 5G centralized unit base station, a 5G distributed unit base station, a next generation Node B (gNB), an enhanced Node B (eNB), or other similar or next generation (e.g., 6G) base station, in various embodiments. The radio access node 104 may include a transceiver circuit 114 coupled to an antenna 116. The transceiver circuit 114 may include an antenna tower 118 in various ways to facilitate wireless communication with the user device 102 or another radio access node 104. The transceiver circuitry 114 may also be coupled to one or more processors 120, which may also be coupled to a memory 122 or other storage device. The memory 122 may store instructions or code that, when read and executed by the processor 120, cause the processor 120 to implement one or more of the methods described herein.

[0018] In various embodiments, two communication nodes in the wireless system 100, e.g., a user equipment 102 and a radio access node 104, two user equipments 102 without a radio access node 104, or two radio access nodes 104 without a user equipment 102, may be configured to wirelessly communicate with each other in or over a mobile network and / or radio access network in accordance with one or more standards and / or specifications. In general, the standards and / or specifications may define rules or procedures by which the communication nodes may wirelessly communicate. These rules or procedures may include, in various embodiments, rules or procedures for communicating in the millimeter (mm) wave band and / or with multiple antenna schemes and beamforming capabilities. Additionally or alternatively, as non-limiting examples, the standards and / or specifications may specify radio access technologies and / or cellular technologies, such as 4th Generation (4G) Long Term Evolution (LTE), 5th Generation (5G) New Radio (NR), or New Radio Unlicensed (NR-U).

[0019] Additionally, in the wireless system 100, the communication nodes are configured to wirelessly communicate with each other. In general, communication between two communication nodes in the wireless system 100 may be or include transmission or reception. Depending on the particular node's perspective of the communication, it usually does both simultaneously. For example, for a given communication between a first node and a second node, where the first node transmits a signal to the second node and the second node receives a signal from the first node, the first node may be referred to as a source or transmitting node or device and the second node may be referred to as a destination or receiving node or device. The communication may be considered to be a transmission for the first node and a reception for the second node. Of course, since the communication nodes in the wireless system 100 can both transmit and receive signals, a single communication node may be both a transmitting / source node and a receiving / destination node, or may switch between a transmitting / source node and a destination / receiving node.

[0020] A particular signal may also be characterized or defined as an uplink (UL), downlink (DL), or sidelink (SL) signal. An uplink signal is a signal transmitted from a user equipment 102 to a radio access node 104. A downlink signal is a signal transmitted from a radio access node 104 to a user equipment 102. A sidelink signal is a signal transmitted from one user equipment 102 to another user equipment 102 or from one radio access node 104 to another radio access node 104. For sidelink transmission, a first user equipment (also referred to as a "source user equipment") 102 transmits a sidelink signal directly to a second user equipment (also referred to as a "destination user equipment") 102 without forwarding the sidelink signal to the radio access node 104.

[0021] Additionally, signals communicated between communication nodes in system 100 may be characterized or defined as data signals or control signals. In general, data signals are signals that contain or carry data, e.g., multimedia data (e.g., voice and / or image data), and control signals are signals that carry control information that in some way configures communication nodes to communicate with each other or controls how communication nodes communicate data signals with each other. Particular signals may also be defined or characterized by combinations of data / control and uplink / downlink / sidelink, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.

[0022] For at least some specifications, e.g., 5G NR, data and control signals are transmitted and / or carried on physical channels. In general, a physical channel corresponds to a set of time-frequency resources used for transmitting signals. Different types of physical channels may be used to transmit different types of signals. For example, a physical data channel (or simply referred to as a data channel) is used to transmit data signals, and a physical control channel (or simply referred to as a control channel) is used to transmit control signals. Types of physical data channels include, but are not limited to, a physical downlink shared channel (PDSCH) used to communicate downlink data signals, a physical uplink shared channel (PUSCH) used to communicate uplink data signals, and a physical sidelink shared channel (PSSCH) used to communicate sidelink data signals. Additionally, the types of physical control channels include, but are not limited to, a physical downlink control channel (PDCCH) used to communicate downlink control signals, a physical uplink control channel (PUCCH) used to communicate uplink control signals, and a physical sidelink control channel (PSCCH) used to communicate sidelink control signals. For simplicity, unless otherwise specified, a physical channel of a particular type is also used to refer to a signal transmitted on that particular type of physical channel and / or a transmission on that particular type of physical channel. As an example, a PDSCH refers to the physical downlink shared channel itself, a downlink data signal transmitted on the PDSCH, or a downlink data transmission. Thus, a communication node transmitting and receiving a PDSCH means that the communication node transmits and receives a signal on the PDSCH.

[0023] Additionally, for at least some specifications, e.g., for 5G NR and / or for at least some types of control signals, control signals transmitted by communication nodes may include control information including information necessary for enabling transmission of one or more data signals between communication nodes and / or for scaling one or more data channels (or one or more transmissions on a data channel). For example, such control information may include information necessary for proper reception, decoding and demodulation of data signals received on a physical data channel during data transmission and / or for uplink scheduling grants informing user equipments of the resources and transport formats to use for uplink data transmissions. In some embodiments, the control information includes downlink control information (DCI) transmitted in a downlink direction from the radio access node 104 to the user equipment 102. In other embodiments, the control information includes uplink control information (UCI) transmitted in an uplink direction from the user equipment 102 to the radio access node 104 or sidelink control information (SCI) transmitted in a sidelink direction from one user equipment 102(1) to another user equipment 102(2).

[0024] Additionally, in the wireless communication system 100, the slot format for multiple slots (occasions) or frames may be configured by the wireless access node 104 or defined by a protocol. In some examples, a slot may be designated or defined as a downlink slot, a flexible slot, or an uplink slot. Also, in various embodiments, an orthogonal frequency divisional multiplexing (OFDM) symbol may be designated or defined as a downlink symbol, a flexible symbol, or an uplink symbol.

[0025] 2 illustrates an example of a base station 200. The exemplary base station 200 may include radio transmit / receive (Tx / Rx) circuitry 208 for transmitting and receiving communications with UEs and / or other base stations. The base station 200 may also include network interface circuitry 209 for communicating with other base stations and / or a core network, e.g., optical or wired interconnects, Ethernet and / or other data transmission media / protocols. The base station 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

[0026] Base station 200 may also include system circuitry 204. System circuitry 204 may include a processor 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more of processors 124 to perform the functions of base station 200. Parameters 228 may include parameters that support execution of instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0027] FIG. 3 illustrates an example of a terminal device 300 (e.g., user equipment (UE)). The UE 300 may be a mobile device, e.g., a smartphone, or a mobile communication module located in a vehicle. The UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a storage device 309. The display circuit may include a user interface 310. The system circuit 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuit 304 may be implemented, for example, using one or more systems on a chip (SoC), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system circuit 304 may be part of the implementation of any desired functionality within the UE 300. In this regard, system circuitry 304 may include, by way of example, logic to facilitate decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV, executing applications, accepting user input, storing and retrieving application data, establishing, maintaining, and terminating cellular telephone calls or data connections, e.g., for Internet connectivity, establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections, and displaying related information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of input / output (I / O) interface 306 may include microphones, video and still cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other input types.

[0028] 3, the communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 for handling the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers including modulation / demodulation circuitry, digital to analog converters (DACs), shaping tables, analog to digital converters (ADCs), filters, wave shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving signals via one or more antennas or (in the case of some devices) over a physical (e.g., wired) medium. The transmitted and received signals may conform to any of a wide variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are also applicable to other wireless communication technologies, whether produced by the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0029] 3. The system circuitry 304 may include one or more processors 321 and memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to perform desired functions for the UE 300. The parameters 328 provide and define configuration and operation options for the instructions 326. The memory 322 may store BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 transmits or has already received via the communication interface 302. In various implementations, system power for the UE 300 may be provided by a power storage device, for example, a battery or a transformer 282.

[0030] The present subject matter describes several example embodiments that may be implemented in part or in whole on the base station 200 and / or UE 300 described with reference to FIGS.

[0031] The base station 200 may configure a serving cell with one cell defining SSB (CD-SSB) and one or more non-cell defining SSBs (NCD-SSB). The UE 300 may be configured in RRC CONNECTED mode with one or more downlink BWPs. A BWP is a range of frequency resources in the frequency domain. Each of the downlink BWPs may be configured to have at least one of a CD-SSB and an NCD-SSB, or none of them.

[0032] The base station 200 may configure one or more serving cell measurement objects (MOs) for the UE 300. The serving cell MO may be based on the CD-SSB (conventional serving cell MO) or may be configured as a serving cell MO per BWP based on the NCD-SSB associated with the downlink BWP.

[0033] The BWP may be configured to have a per-BWP serving cell MO. If the per-BWP serving cell MO is configured, the UE 300 may perform serving cell measurements based on the per-BWP serving cell MO if the BWP is activated. Otherwise, the UE 300 may perform serving cell measurements according to the serving cell MO based on the CD-SSB.

[0034] In the conventional 3GPP TS 38.473 specification, the serving cell MO is configured by including an information element (IE) servingCellMO in the servingCellConfig IE. The per-BWP serving cell MO is configured by including a servingCellMO IE-BWP in the IE BWP-DownlinkDedicated configured for each downlink BWP configured for the UE 300 in RRC CONNECTED mode.

[0035] FIG. 4 illustrates the overall architecture of the centralized unit (CU) / distributed unit (DU) split. The gNB 405 may include a gNB centralized unit (gNB-CU 410) ("CU" 410) and one or more gNB distributed units (gNB-DU 415) ("DU" 415). The gNB-CU 410 and the gNB-DU 415 may be connected via an F1 interface 420. The gNB-CU 410 may be defined as a logical node hosting the radio resource control (RRC), SDAP and PDCP protocols of the gNB or the RRC and PDCP protocols of the en-gNB, which controls the operation of one or more gNB-DUs 415. The gNB-DU 415 may be defined as a logical node hosting the RLC, MAC, PHY layers of the gNB 405 or the en-gNB. The operation of the gNB-DU 415 may be partially controlled by the gNB-CU 410. One gNB-DU 415 may support one or multiple cells. One cell may be supported by only one gNB-DU 415.

[0036] In the conventional 3GPP TS 38.473 specification, the serving cell MO and the measurement gaps are configured using the following procedure: (1) the CU 410 configures the content of the serving cell MO in the measConfig IE; (2) the CU 410 indicates the identifier (ID) of the serving cell MO to the DU 415 during the UE context setup or UE context modification procedure. The CU 410 may ask the DU 415 to configure the measurement gaps by including the measConfig IE in the UE context setup request message or the UE context modification request message. The measConfig IE includes a list of FR1 and / or FR2 frequencies for which the CU 410 requests the DU to generate measurement gaps on a per-UE or per-FR basis. The DU 415 (1) configures the content of the servingCellConfig IE by including the serving cell MO ID. Specifically, the DU 415 assigns the value of the serving cell MO ID indicated by the CU to the servingCellMO IE in the servingCellConfig IE. (2) The DU 415 configures a measurement gap according to the request by the CU 410, and fills in the measurement gap information in the measConfig IE. Then, the DU 415 includes the servingCellConfig IE and the measConfig IE in a UE context setup response message or a UE context modification response message to the CU 410. Then, the CU 410 sends an RRC message including the servingCellConfig IE and the measConfig IE to the UE according to the corresponding IE sent from the CU 415 for the UE.

[0037] According to the subject matter of the present application, the shortcomings of the conventional 3GPP TS 38.473 specification are overcome by solving the problem of serving cell MO and measurement gap configuration after introducing serving cell MO per BWP. Specifically, the procedure defined in the conventional 3GPP TS 38.473 specification does not consider the configuration of serving cell MO per BWP.

[0038] For example, in the current 3GPP TS 38.473 specification, the CU 410 cannot indicate the per-BWP serving cell MO ID in the UE context setup request or UE context modification request message because there is no IE defined to convey it.

[0039] In the current 3GPP TS 38.473 specification, since the BWP configuration is configured by the DU 415, not by the CU 410, when the CU 410 initiates a UE context setup or UE context modification procedure, the CU 410 cannot know whether the DU 415 configures a downlink BWP to include an NCD-SSB for the UE 300, or which NCD-SSB is configured for the downlink BWP. Therefore, the CU 410 cannot determine whether per-BWP serving cell MO configuration and corresponding MO ID are required.

[0040] In the current 3GPP TS 38.473 specification, when the CU 410 initiates a UE context setup or UE context modification procedure, the CU 410 cannot know whether the serving cell MO based on CD-SSB is useful or not. The serving cell MO based on CD-SSB is applied when (1) there is a downlink BWP including CD-SSB, or (2) the downlink BWP includes NCD-SSB, but the per-BWP serving cell MO is not configured for this downlink BWP. In this case, the UE 300 performs serving cell measurement based on the serving cell MO based on CD-SSB when the downlink BWP is activated. If neither case (1) nor case (2) occurs, the serving cell MO based on CD-SSB is not applied by the UE 300. Therefore, the serving cell MO ID carried in the current UE context setup request message or UE context modification request message is useless, but the CU 410 does not know this. The CU 410 may subsequently configure the CD-SSB based serving cell MO for the UE 300 in an RRC message.

[0041] In the current 3GPP TS 38.473 specification, the CU 410 determines whether a measurement gap is necessary based on the frequency of the serving cell measurements (ie, the frequency of CD-SSB), the frequency of the neighboring cells, and the capabilities of the UE 300 .

[0042] After introducing the per-BWP serving cell MO, the CU 410 cannot determine which frequency of the SSB configured in the serving cell is to be measured, because the decision depends on whether the serving cell MO based on CD-SSB is applied, whether the per-BWP serving cell MO is configured, and which NCD-SSB is configured. Therefore, before the BWP configuration is performed for the UE by the DU 415, the CU 410 cannot easily determine whether a measurement gap is required.

[0043] In summary, after the introduction of per-BWP serving cell MO, the approach described in the current 3GPP TS 38.473 specification cannot provide a valid solution for setting the serving cell MO based on CD-SSB and NCD-SSB, nor can it provide a valid solution for setting measurement gaps.

[0044] As used herein, a BWP that includes an SSB shall mean at least one of: (1) the SSB frequency domain resource is included within the frequency domain resource of the BWP; and / or (2) the BWP is configured to have the SSB, i.e., the SSB is associated with the BWP.

[0045] As used herein, the terms SSB, CD-SSB, and NCD-SSB all refer to an SSB burst that is understood to carry one or more synchronization signal (SS) blocks.

[0046] According to the subject matter of the present application, the CU 410 may indicate candidate serving cell MOs to the DU 415. The DU 415 may determine the configuration and / or measurement gaps. In the UE context setup request message and / or UE context modification request message sent from the CU 410 to the DU 415, the CU 410 may include one or more of: (1) one or more IDs of serving cell MOs that may be based on CD-SSB, (2) one or more IDs of serving cell MOs that may be based on NCD-SSB, and / or (3) a measurement configuration that may include a list of frequencies for which the CU 410 may request the DU 415 to generate a measurement gap and a measurement gap type.

[0047] The DU 415 may set the serving cell MO ID or the serving cell MO ID per BWP in one of the following cases:

[0048] In the first case, when a downlink BWP including an NCD-SSB is configured by the DU 415 and the ID of the serving cell MO based on the NCD-SSB is indicated by the CU 410, the DU 415 may include the ID of the serving cell MO in the configuration of the downlink BWP. That is, the DU 415 may configure the serving cell MO for each BWP as the serving cell MO based on the above-mentioned NCD-SSB.

[0049] In the second case, if the DU 415 configures a downlink BWP including an NCD-SSB, but the CU 410 does not indicate the ID of the serving cell MO based on this NCD-SSB, the DU 415 may not configure a serving cell MO per BWP for this downlink BWP.

[0050] In the third case, if the ID of the serving cell MO based on CD-SSB is indicated by the CU 410, the DU 415 may follow at least one of the following rules: (1) the DU 415 may configure a downlink BWP including this CD-SSB, (2) the DU 415 should configure a downlink BWP including this CD-SSB, and / or (3) the DU 415 may configure a downlink BWP including NCD-SSB but not configure a per-BWP serving cell MO ID for this downlink BWP.

[0051] In the fourth case, if the ID of the serving cell MO based on the CD-SSB is not indicated by the CU 410, (1) the DU 415 may not configure a downlink BWP including the CD-SSB, and / or (2) the DU 415 may not configure a downlink BWP including the NCD-SSB without configuring a serving cell MO ID per BWP for this downlink BWP.

[0052] In the fifth case, if the ID of the serving cell MO based on the NCD-SSB is indicated by the CU 410, the DU 415 may follow at least one of the following rules: (1) the DU 415 may configure a downlink BWP including this NCD-SSB and configure a serving cell MO ID per BWP for this downlink BWP; (2) the DU 415 may not configure a downlink BWP including this NCD-SSB; (3) the DU 415 should configure a downlink BWP including this NCD-SSB and configure a serving cell MO ID per BWP for this downlink BWP; (4) the DU 415 may not configure a downlink BWP including CD-SSB; and / or (5) the DU 415 may not configure a downlink BWP including this NCD-SSB without configuring a serving cell MO ID per BWP for this downlink BWP.

[0053] In the UE context setup request message or UE context modification request message, the CU 410 may indicate one of the following configuration preferences: (1) a serving cell MO based on CD-SSB may / should be configured for at least one downlink BWP, (2) the downlink BWP may / should include CD-SSB or NCD-SSB, and / or (3) NCD-SSB may / should be configured for at least one downlink BWP. The configuration preference may be indicated by the presence of the serving cell MO ID or by an explicit indicator.

[0054] In response to the UE Context Setup Request message or the UE Context Modification Request message, the DU 415 may respond with a UE Context Setup Response message or a UE Context Modification Response message, respectively. At least one of (1) information indicating whether a serving cell MO based on CD-SSB is used by the BWP configured for the UE 300 and / or (2) information indicating which serving cell MO based on NCD-SSB is configured for the BWP configured for the UE 300 may be included in any of the above-mentioned response messages.

[0055] In messages between the CU 410 and the DU 415, a serving cell MO based on an NCD-SSB may be associated with the NCD-SSB in one of the following ways: (1) associating the serving cell MO ID with the NCD-SSB ID; or (2) associating the serving cell MO ID with frequency information of the NCD-SSB.

[0056] In messages between the CU 410 and the DU 415, the serving cell MO based on the NCD-SSB may be identified in one of the following ways: (1) the ID of the NCD-SSB associated with this serving cell MO, (2) the frequency information of the NCD-SSB associated with this serving cell MO, or (3) the measurement object ID (MO ID).

[0057] Additionally, the DU 415 may determine the measurement gap if the measConfig IE is included in the UE Context Setup Request message or the UE Context Modification Request message. The DU 415 may determine the measurement gap based on one or more of: (1) the information included in the measConfig IE; (2) the result of which serving cell MO is used by the UE 300 according to the techniques disclosed in accordance with the subject matter of the present application, such as (a) whether a CD-SSB based serving cell MO is configured for the BWP of the UE 300, and / or (b) which NCD-SSB based serving cell MO is configured for the BWP of the UE 300. The DU 415 may then include the measurement gap configuration in the measConfig included in the response message.

[0058] Upon receiving the response message, the DU 415 may perform the following operations: For a serving cell MO that is not configured for any BWP of the UE 300, the CU 410 may remove it from the measConfig IE, or the CU 410 may not include this serving cell MO in the measConfig IE, which may be sent to the UE 300 in an RRC message.

[0059] The DU 415 may configure the BWP according to various factors including the capability of the UE 300. In this example, the preference and / or candidate serving cell MO information provided by the CU 410 may also be considered by the DU 415. After configuring for the UE 300, the DU 415 may inform the CU 410 which serving cell MO is used or not used. Then, the CU 410 may remove the candidate serving cell MO that is not configured for the UE 300. At the same time, the DU 415 may also determine a measurement gap based on the result of the serving cell MO configuration and the measurement configuration provided by the CU 410. Therefore, only one step including one request and one response is needed to complete the serving cell MO configuration and the measurement gap configuration.

[0060] Alternatively or additionally, the DU 415 indicates the BWP configuration to the CU 410. The CU 410 may configure the serving cell measurement target. In a message that may be sent from the DU 415 to the CU 410, such as a UE context setup response message or a UE context modification response message, the DU 415 may indicate the BWP configuration information of the UE 300 to the CU 410. The BWP configuration information may include at least one of: (1) whether a BWP including a CD-SSB exists; (2) information of a BWP that includes a CD-SSB and may further include at least one of (a) a BWP ID of the BWP, and / or (b) a type of BWP, e.g., a first active BWP, an initial downlink BWP, a reduced capability (RedCap) specific initial downlink BWP, or a default BWP; and / or (3) information of a BWP that includes an NCD-SSB, and may further include one or more of the amount of BWPs of this type, the BWP ID of the BWP of this type, and / or information of the NCD-SSB included in the BWP, e.g., the ID of the NCD-SSB, the frequency of the NCD-SSB, or other information used by CU 410 to identify the NCD-SSB.

[0061] The DU 415 may also indicate a preference for per-BWP serving cell MO configuration to the CU 410. This preference may be one of: (1) preferring to configure per-BWP serving cell MO for a BWP that includes an NCD-SSB, or (2) preferring not to configure per-BWP serving cell MO for a BWP that includes an NCD-SSB.

[0062] The CU 410 may configure the serving cell MO configuration for the UE 300 based on the BWP configuration information sent from the DU 415 to the CU 410. The CU 410 may indicate the configured serving cell MO information to the DU 415 in a subsequent message, for example, a UE context modification request message. The UE context modification request message may include one or more of: (1) an ID of the serving cell MO based on CD-SSB, and / or (2) an ID of the serving cell MO based on NCD-SSB.

[0063] Upon receiving the serving cell MO configuration, the DU 415 may configure a serving cell MO ID for the UE 300 according to this serving cell MO configuration information. If the ID of the serving cell MO based on the CD-SSB is included in the UE Context Modification Request message, the DU 415 may configure the serving cell MO IE included in the servingCellConfig IE accordingly (i.e., the DU 415 may configure the servingCellMO IE included in the servingCellConfig IE accordingly). If the ID of the serving cell MO based on the NCD-SSB is included, the DU 415 may configure a serving cell MO per BWP for the BWP including this NCD-SSB (i.e., the servingCellMO-BWP in the IE BWP-DownlinkDedicated of the BWP may be assigned to the ID of the serving cell MO).

[0064] With this technique according to the subject matter of the present application, the DU 415 may first notify the BWP configuration information to the CU 410. The BWP configuration information may include whether CD-SSB is configured for the downlink BWP of the UE 300, whether NCD-SSB is configured (included) in the downlink BWP of the UE 300, or some other detailed information of the corresponding BWP.

[0065] Then, the CU 410 may configure a serving cell MO based on the CD-SSB or NCD-SSB according to the BWP configuration information. The CU 410 may indicate to the DU 415 the serving cell MO ID of the configured serving cell MO.

[0066] Therefore, the DU 415 may terminate the serving cell MO configuration for both the conventional serving cell MO based on CD-SSB and the serving cell MO per BWP based on NCD-SSB.

[0067] Furthermore, the CU 410 may have complete information of the serving cell MO configuration after determining the serving cell MO configuration based on the BWP configuration information provided by the DU 415. The CU 410 may determine whether measurement is needed and whether to request the DU 415 to generate a measurement gap.

[0068] In a conventional NR system, system information (SI) can be classified into master information block (MIB), SI Block 1 (SIB1), and other SI. UE 300 receives other SI by monitoring PDCCH occasions defined by search spaces. The search space used to receive other SI may be search space zero (i.e., searchSpaceZero) or other SI search space (i.e., searchSpaceOtherSystemInformation) if configured. The search space used for SIB1 reception is search space zero.

[0069] During handover, the SI of the target cell may be acquired by the UE 300 in one of the following ways: (1) the UE 300 monitors PDCCH occasions according to a common search space for SI reception configuration, and / or (2) the target cell delivers the SI to the UE 300 via a dedicated RRC message.

[0070] In a conventional NR system, a RedCap UE may be configured to have a downlink BWP that does not have a common search space for receiving SI (including SIB1 and other SI).

[0071] During the handover procedure, the UE may activate the first active downlink BWP of the target cell and initiate a RACH procedure in the first active downlink BWP. However, the first active downlink BWP may be configured such that no common search space for SI reception is configured. Therefore, the UE 300 cannot acquire the SI of the target cell by monitoring PDCCH occasions in the first active downlink BWP of the target cell.

[0072] To facilitate the handover procedure, the base station 200 must then transmit the SI to the UE 300 via a dedicated RRC message.

[0073] However, in the CU / DU architecture, the BWP configuration is determined by the DU 415, while the dedicated RRC message is constructed by the CU 410, and whether to include SI in the RRC message is determined by the CU 410. To determine whether SI needs to be included in the dedicated message, the CU 410 needs to know the first active downlink BWP configuration for the UE 300.

[0074] To address these issues in accordance with the subject matter of the present application, the CU 410 may first request the DU 415 to set up a UE context during a handover procedure by sending a UE context setup request message. The DU 415 may configure a serving cell configuration including a BWP configuration. The BWP configuration may include a first active downlink BWP configuration.

[0075] If the first active downlink BWP does not include CD-SSB or Control Resource Set (CORESET) zero, the DU 415 may not configure a common search space for SI reception.

[0076] The DU 415 may then indicate to the CU 410 in the UE context setup response message one of: (1) dedicated SI delivery is required; (2) the first active downlink BWP does not include CD-SSB; (3) the first active downlink BWP does not have a common search space for SI reception (i.e., search space zero or a search space for other SI) configured; and / or (4) the first active downlink BWP is a RedCap specific initial downlink BWP.

[0077] The CU 410 may include the SI (SIB1 and / or other SI) in a dedicated RRC message that may be sent to the UE 300. The dedicated RRC message may be an RRC reconfiguration message used for handover.

[0078] Using this technique according to the present subject matter, the CU 410 may be informed whether dedicated SI delivery is required for the UE 300. If a common search space is not configured for the first active BWP to receive SI, the UE 300 may acquire SI without monitoring PDCCH occasions.

[0079] According to the subject matter of the present application, during a UE context setup or UE modification procedure, the CU 410 may provide a list of candidate serving cell MO IDs to the DU 415. The DU 415 may configure per-BWP serving cell MO according to the candidate serving cell MO IDs. The CU 410 may also indicate a preference for per-BWP serving cell MO configuration. The DU 415 may indicate to the CU 410 the serving cell MO to be used for the UE 300. The DU 415 may determine a measurement gap based on the measConfig IE sent from the CU 410 and the decision of the per-BWP serving cell MO configuration. The CU 410 may remove candidate serving cell MOs not used by the UE 300 from the measConfig IE. During a UE context setup or modification procedure, the DU 415 may inform the CU 410 whether there is a BWP configuration, e.g., a BWP including NCD-SSB. The CU 410 may configure the serving cell MO according to the per-BWP serving cell MO configuration. The DU 415 may indicate the preference of the per-BWP serving cell MO configuration. During handover, if the first active downlink BWP does not have a common search space for SI configured, the DU 415 may inform the CU 410 that a dedicated SI delivery is required for the UE 300. The CU 410 may include the SI in a dedicated RRC message to the UE 300.

[0080] The present subject matter describes methods, devices, and computer-readable media for wireless communication. The present subject matter addresses challenges associated with scheduling multiple transmissions in one or more cells by reducing the number of bits required to indicate the scheduled transmissions. The methods, devices, and computer-readable media described in the present subject matter help improve the performance of wireless transmissions between user equipment and base station 200, thereby improving efficiency and overall performance. The methods, devices, and computer-readable media of the present subject matter can improve the overall efficiency of a wireless communication system.

[0081] The above description and the accompanying drawings provide specific exemplary embodiments and implementations. The described subject matter may be embodied in various different forms, and therefore it is intended that the claimed subject matter covered or claimed be construed as not being limited to any exemplary embodiment described herein. A reasonably broad scope is intended for the subject matter claimed or covered. In particular, for example, the subject matter of the present application may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Thus, the embodiments may take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the method embodiments described above may be implemented by a component, device, or system including a memory and a processor by executing computer code stored in the memory.

[0082] Throughout the specification and claims, terms may have subtle meanings suggested or implied by context beyond their explicitly stated meaning. Similarly, "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, claimed subject matter is intended to include combinations of all or part of the example embodiments.

[0083] Generally, terms can be understood, at least in part, from their use in context. For example, the terms "and," "or," or "and / or" as used herein may include various meanings that depend, at least in part, on the context in which such terms are used. In general, when used to relate a list such as A, B, or C, "or" may mean A, B, and C (used herein in an inclusive sense) or A, B, or C (used herein in an exclusive sense). Also, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe a combination of features, structures, or characteristics in a plural sense, at least in part, depending on the context. Similarly, the terms "a," "one," "the," and the like may be understood to convey a singular usage or to convey a plural usage, at least in part, depending on the context. Also, the term "based on" may be understood to not necessarily be intended to convey an exclusive set of elements. Alternatively, the presence of additional elements not necessarily explicitly recited may be permitted, also depending at least in part on the context.

[0084] References to features, advantages, or similar language throughout this specification do not imply that all of the features and advantages that may be realized in the solution should or are included in any single realization thereof. Rather, the language referring to features and advantages means that the particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, descriptions of features and advantages and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0085] Moreover, the above features, advantages and characteristics of the solution may be combined in any suitable manner in one or more embodiments. In light of the description herein, one skilled in the art will appreciate that the solution of the present invention can be implemented in the absence of one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in a particular embodiment that may not be present in all embodiments of the solution.

[0086] The subject matter of the present disclosure may also relate to or include, among others, the following aspects:

[0087] A first aspect includes a method for measurement configuration in a wireless communication network, the method including: providing a plurality of candidate serving cell measurement object (MO) identifiers (IDs) from a centralized unit (CU) to a distributed unit (DU), selecting, by the DU, a serving cell MO to be used for a user equipment (UE) from the plurality of candidate serving cell MO IDs, and configuring, by the DU, a serving cell MO configuration per bandwidth (BWP) according to the serving cell MO.

[0088] A second aspect includes the method of the first aspect, further including indicating, by the CU, a preference for the serving cell MO configuration.

[0089] A third aspect includes the method of the first or second aspect, further comprising determining, by the DU, a measurement gap based on a serving cell MO configuration for each BWP.

[0090] A fourth aspect includes the method of any preceding aspect, further including removing, by the CU, candidate serving cell MOs that were not selected by the DU from a measConfig IE.

[0091] A fifth aspect includes the method of any preceding aspect, wherein the multiple candidate serving cell MO IDs are provided in a UE context setup request message or a UE modification request message sent from the CU to the DU.

[0092] A sixth aspect includes the method of any preceding aspect, further including the DU responding to the UE context setup request message or the UE modification request message with a response message including at least one of whether the serving cell MO is based on a cell-defined synchronization signal block (CD-SSB) configured by a BWP configured for the UE, or whether the serving cell MO is based on a non-cell defined synchronization signal block (NCD-SSB) configured for a BWP configured for the UE.

[0093] A seventh aspect includes the method of any preceding aspect, wherein the one or more candidate serving cell MO IDs are based on a cell-defined synchronization signal block (CD-SSB).

[0094] An eighth aspect includes the method of any preceding aspect, wherein one or more candidate serving cell MO IDs are based on a non-cell defined synchronization signal block (NCD-SSB) indicated by the CU.

[0095] A ninth aspect includes the method of any preceding aspect, wherein the step of configuring the per BWP serving cell MO configuration is further based on the NCD-SSB.

[0096] A tenth aspect includes the method of any preceding aspect, wherein the plurality of candidate serving cell MO IDs is based on a measurement configuration including a list of frequencies for which the CU requests the DU to generate the measurement gaps and measurement gap types.

[0097] An eleventh aspect includes the method of any preceding aspect, further including configuring a downlink BWP by the DU.

[0098] A twelfth aspect includes the method of any preceding aspect, wherein the downlink BWP includes an NCD-SSB, and the method further includes configuring a serving cell MO configuration per the BWP based on the NCD-SSB.

[0099] A thirteenth aspect includes the method of any preceding aspect, wherein the CU does not indicate a serving cell MO ID based on an NCD-SSB, and the method further includes not configuring a serving cell MO setting per BWP for a downlink BWP configured by the DU.

[0100] A fourteenth aspect includes the method of any preceding aspect, further including configuring, by the DU, a downlink BWP that includes the CD-SSB.

[0101] A fifteenth aspect includes the method of any preceding aspect, further including configuring, by the DU, a downlink BWP including an NCD-SSB, and not configuring, by the DU, a serving cell MO per BWP for the configured downlink BWP.

[0102] A sixteenth aspect includes the method of any preceding aspect, wherein an ID of a serving cell MO based on CD-SSB is not indicated by the CU, and the method further includes not configuring, by the DU, a downlink BWP that includes the CD-SSB.

[0103] A seventeenth aspect includes the method of any preceding aspect, wherein a serving cell MO ID based on CD-SSB is not indicated by the CU, and the method further includes configuring, by the DU, a downlink BWP including an NCD-SSB, and configuring a serving cell MO ID per BWP for the downlink BWP.

[0104] An eighteenth aspect includes the method of any preceding aspect, further including configuring, by the DU, a downlink BWP including the NCD-SSB, and configuring, by the DU, a per-BWP serving cell MO ID for the downlink BWP.

[0105] A nineteenth aspect includes the method of any preceding aspect, further including not configuring, by the DU, a downlink BWP that includes the NCD-SSB.

[0106] A twentieth aspect includes the method of any preceding aspect, further including not configuring, by the DU, a downlink BWP that includes a CD-SSB.

[0107] A 21st aspect includes the method of any preceding aspect, further including configuring, by the DU, a downlink BWP including the NCD-SSB, and configuring a per-BWP serving cell MO ID for the downlink BWP.

[0108] A twenty-second aspect includes the method of any preceding aspect, wherein the preference is a serving cell MO based on a CD-SSB configured in a downlink BWP that includes a CD-SSB or an NCD-SSB.

[0109] A twenty-third aspect includes the method of any preceding aspect, wherein the preference is a serving cell MO based on an NCD-SSB configured in a downlink BWP.

[0110] A 24th aspect includes the method of any preceding aspect, wherein the serving cell MO ID is indicated by the CU with one or more of an NCD-SSB identifier associated with the serving cell MO, frequency information of the NCD-SSB associated with the serving cell MO, or an MO ID.

[0111] A twenty-fifth aspect includes the method of any preceding aspect, wherein the measurement gap is determined further based on information included in the measConfig IE, whether a CD-SSB based serving cell MO is configured for the BWP of the UE, and whether and which NCD-SSB based serving cell MO is configured by the BWP of the UE.

[0112] A 26th aspect includes the method of any preceding aspect, wherein upon receiving the response message by the CU, the CU does not include unselected candidate serving cells in an IE measConfig and sends the IE measConfig in a Radio Resource Control (RRC) message to the UE.

[0113] A 27th aspect includes a method for measurement configuration in a wireless communication network, the method including: sending a message from a DU to a CU indicating BWP configuration information of a UE, sending, by the CU, a serving cell MO configuration to the DU, and configuring, by the DU, a serving cell MO identifier for the UE according to the serving cell MO configuration.

[0114] A 28th aspect includes the method of the 27th aspect, further including the DU indicating a serving cell MO setting preference per BWP to the CU, and the CU configuring the serving cell MO setting for the UE based on the message indicating the BWP setting information.

[0115] A 29th aspect includes the method of the 27th aspect or the 28th aspect, wherein the message is a UE context setup response message or a UE context modification response message.

[0116] A 30th aspect includes a method of any one of the 27th to 29th aspects, wherein the BWP setting information includes at least one of whether a BWP includes a CD-SSB, a BWP identifier of the BWP, a type of the BWP, a quantity of the BWPs of the type, a BWP identifier of the BWP of the type, an identifier of an NCD-SSB, or a frequency of the NCD-SSB.

[0117] A 31st aspect includes the method of any one of the 27th to 30th aspects, wherein the preference includes one or more of a preference to configure a serving cell MO per BWP for a BWP that includes an NCD-SSB, or a preference not to configure a serving cell MO per BWP for a BWP that includes an NCD-SSB.

[0118] A 32nd aspect includes a method of any one of the 27th to 31st aspects, further including the CU indicating the configured serving cell MO information to the DU in a UE context modification request message.

[0119] A 33rd aspect includes the method of any one of the 27th to 32nd aspects, wherein the UE context modification request message includes at least one of a serving cell MO identifier based on CD-SSB or a serving cell MO identifier based on NCD-SSB.

[0120] A 34th aspect includes any one of the methods of the 27th to 33rd aspects, wherein the serving cell MO identifier is based on a CD-SSB, and the method further includes the DU configuring the serving cell MO IE based on the CD-SSB.

[0121] A 35th aspect includes any one of the methods of the 27th to 34th aspects, wherein the serving cell MO is based on an NCD-SSB, and the method further includes the DU configuring a serving cell MO setting for each BWP for a BWP that includes the NCD-SSB.

[0122] A 36th aspect includes a method for measurement configuration in a wireless communication network, the method including: transmitting, by a CU, a UE context setup response message to a DU, the UE context setup response message including at least one of: a dedicated system information delivery is required, an active downlink BWP does not include CD-SSB, the active downlink BWP is not configured with a common search space for receiving system information, or the active downlink BWP is a reduced capability (RedCap) specific initial downlink BWP.

[0123] A thirty-seventh aspect includes the method of the thirty-sixth aspect, wherein the BWP configuration includes the active downlink BWP configuration.

[0124] A 38th aspect includes the method of the 36th or 37th aspect, further including: the DU configuring a serving cell configuration including a BWP configuration; the DU instructing the CU to transmit a UE context setup response message; and the CU transmitting a dedicated RRC message including system information (SI) to the UE.

[0125] A thirty-ninth aspect includes the method of any one of the thirty-sixth to thirty-eighth aspects, wherein the dedicated RRC message is an RRC reconfiguration message for handover.

[0126] A fortieth aspect relates to an apparatus for wireless communication comprising: a processor; and a memory in communication with the processor and storing a plurality of instructions executable by the processor such that the apparatus implements a method of any preceding aspect.

[0127] A forty-first aspect relates to a non-transitory computer-readable medium comprising instructions operable, when executed by one or more processors, to implement any one of the methods of the first to thirty-ninth aspects.

Claims

1. A method for measurement configuration in a wireless communication network, comprising: providing a plurality of candidate serving cell measurement object (MO) identifiers (IDs) from a centralized unit (CU) to a distributed unit (DU); selecting, by the DU, a serving cell MO to be used for a user equipment (UE) from the plurality of candidate serving cell MO IDs; By the DU, a serving cell MO setting is set for each bandwidth part (BWP) according to the serving cell MO; The method includes:

2. Indicating, by the CU, a preference for the serving cell MO configuration. The method of claim 1 further comprising:

3. The DU further includes determining a measurement gap based on a serving cell MO configuration per the BWP. The method of claim 1.

4. removing, by the CU, a candidate serving cell (MO) that was not selected by the DU from a measConfig IE; The method of claim 3 further comprising:

5. The plurality of candidate serving cell MO IDs are provided in a UE context setup request message or a UE modification request message transmitted from the CU to the DU. The method of claim 1.

6. Responding to the UE context setup request message or the UE modification request message by the DU with a response message including at least one of whether the serving cell MO is based on a cell-defined synchronization signal block (CD-SSB) configured by a BWP configured for the UE, or whether the serving cell MO is based on a non-cell-defined synchronization signal block (NCD-SSB) configured for a BWP configured for the UE. The method of claim 5 further comprising:

7. One or more candidate serving cell MO IDs are based on cell-defined synchronization signal blocks (CD-SSBs) The method of claim 1.

8. One or more candidate serving cell MO IDs are based on a non-cell-defined synchronization signal block (NCD-SSB) indicated by the CU. The method of claim 1.

9. The step of configuring a serving cell MO configuration per BWP is further based on the NCD-SSB. The method according to claim 8.

10. The plurality of candidate serving cell MO IDs are based on a measurement configuration including a list of frequencies at which the CU requests generation of the measurement gap and a measurement gap type for the DU. The method according to claim 3.

11. The DU configures a downlink BWP. The method of claim 1 further comprising:

12. The downlink BWP includes an NCD-SSB, and the method further includes configuring a serving cell MO configuration per the BWP based on the NCD-SSB. The method of claim 11.

13. The CU does not indicate an ID of a serving cell MO based on an NCD-SSB, and the method further includes not configuring a serving cell MO configuration per BWP for the configured downlink BWP by the DU. The method of claim 11.

14. and setting a downlink BWP including the CD-SSB by the DU. The method of claim 6 further comprising:

15. Configuring a downlink BWP including an NCD-SSB by the DU; The DU does not configure a serving cell MO for each BWP for the configured downlink BWP. The method of claim 6 further comprising:

16. The ID of a serving cell MO based on CD-SSB is not indicated by the CU, and the method further includes not configuring a downlink BWP including the CD-SSB by the DU. The method of claim 1.

17. The ID of a serving cell MO based on CD-SSB is not indicated by the CU, and the method further comprises: Configuring a downlink BWP including an NCD-SSB by the DU; Setting a serving cell MO ID for each downlink BWP; The method of claim 1 further comprising:

18. Configuring a downlink BWP including the NCD-SSB by the DU; The DU configures a serving cell MO ID for the downlink BWP. The method of claim 8 , further comprising:

19. The DU does not set a downlink BWP including the NCD-SSB. The method of claim 8 , further comprising:

20. The DU shall not set a downlink BWP including CD-SSB. The method of claim 8 , further comprising:

21. Configuring a downlink BWP including the NCD-SSB by the DU; Setting a serving cell MO ID for each downlink BWP; The method of claim 8 , further comprising:

22. The preference is a serving cell MO based on CD-SSB set in a downlink BWP including CD-SSB or NCD-SSB. The method of claim 2.

23. The preference is a serving cell MO based on NCD-SSB set to downlink BWP. The method of claim 2.

24. The serving cell MO ID is indicated by the CU with one or more of an NCD-SSB identifier associated with the serving cell MO, frequency information of the NCD-SSB associated with the serving cell MO, or an MO ID. The method according to claim 8.

25. The measurement gap is determined based on the information included in the measConfig IE, whether a CD-SSB based serving cell MO is configured for the BWP of the UE, whether an NCD-SSB based serving cell MO is configured by the BWP of the UE, and which NCD-SSB based serving cell MO is configured by the BWP of the UE. The method according to claim 4.

26. Upon receiving the response message by the CU, the CU does not include the non-selected candidate serving cells in the IE measConfig and sends the IE measConfig in a Radio Resource Control (RRC) message to the UE. The method according to claim 6.

27. A method for measurement configuration in a wireless communication network, comprising: Sending a message from the DU to the CU indicating BWP setting information of the UE; Sending, by the CU, a serving cell MO configuration to the DU; configuring, by the DU, a serving cell MO identifier for the UE according to the serving cell MO configuration; The method includes:

28. Indicating a serving cell MO configuration preference per BWP to the CU by the DU; Configuring, by the CU, the serving cell MO configuration for the UE based on the message indicating the BWP configuration information; 28. The method of claim 27, further comprising:

29. The message is a UE context setup response message or a UE context modification response message.

28. The method of claim 27.

30. The BWP setting information is Whether the BWP includes CD-SSB; A BWP identifier of the BWP; The type of the BWP, the amount of said BWP of said type; A BWP identifier of the BWP of said type; Identifier of the NCD-SSB, or The frequency of the NCD-SSB, At least one of 28. The method of claim 27.

31. The preference includes one or more of: a preference to set a serving cell MO per BWP for a BWP including an NCD-SSB; or a preference not to set a serving cell MO per BWP for a BWP including an NCD-SSB.

29. The method of claim 28.

32. The method further includes indicating the serving cell MO information set by the CU to the DU in a UE context modification request message.

28. The method of claim 27.

33. The UE context modification request message includes at least one of an identifier of a serving cell MO based on CD-SSB or an identifier of a serving cell MO based on NCD-SSB.

33. The method of claim 32.

34. The serving cell MO identifier is based on CD-SSB, and the method further includes configuring, by the DU, the serving cell MO IE based on the CD-SSB.

28. The method of claim 27.

35. The serving cell MO is based on an NCD-SSB, and the method further includes configuring, by the DU, a serving cell MO configuration per the BWP for a BWP that includes the NCD-SSB.

28. The method of claim 27.

36. A method for measurement configuration in a wireless communication network, comprising: sending, by the CU, a UE context setup response message to the DU; The UE context setup response message: The need for delivery of dedicated system information; The active downlink BWP does not include CD-SSB; The active downlink BWP is not configured to have a common search space for receiving system information; or the active downlink BWP is a reduced capacity (RedCap) specific initial downlink BWP; Contains at least one of method.

37. The BWP configuration includes the active downlink BWP configuration.

37. The method of claim 36.

38. Configuring a serving cell configuration including a BWP configuration by the DU; Instructing the CU to send a UE context setup response message by the DU; transmitting, by the CU, a dedicated RRC message including system information (SI) to the UE; 37. The method of claim 36, further comprising:

39. The dedicated RRC message is an RRC reconfiguration message for handover.

39. The method of claim 38.

40. An apparatus for wireless communication, comprising a processor and a memory in communication with said processor and storing a plurality of instructions executable by said processor such that said apparatus implements a method according to any one of claims 1 to 26. Device.

41. comprising instructions operable, when executed by one or more processors, to implement the method according to any one of claims 1 to 26. Non-transitory computer-readable medium.

42. An apparatus for wireless communication, comprising a processor and a memory in communication with said processor and storing a plurality of instructions executable by said processor such that said apparatus implements a method according to any one of claims 27 to 35. Device.

43. comprising instructions operable, when executed by one or more processors, to implement the method according to any one of claims 27 to 35. Non-transitory computer-readable medium.

44. An apparatus for wireless communication, comprising a processor and a memory in communication with said processor and storing a plurality of instructions executable by said processor such that said apparatus implements a method according to any one of claims 36 to 39. Device.

45. comprising instructions operable, when executed by one or more processors, to implement the method according to any one of claims 36 to 39. Non-transitory computer-readable medium.

Images