Measurement configuration method

Abstract

This disclosure describes methods, systems, and devices for configuring measurement objects in a wireless communication network. Multiple candidate serving cell measurement object (MO) identifiers (IDs) are provided from a centralized unit (CU) to a distributed unit (DU). The DU selects a serving cell MO to be used for a user equipment (UE) from the multiple candidate serving cell MO IDs. Based on the serving cell MO, the DU configures a per-bandwidth part (BWP) serving cell MO configuration.

Description

Technical Field

[0001] The present subject matter generally relates to wireless communications and, more particularly, to methods, devices, and systems for configuring measurement objects in a wireless communication network. Background Art

[0002] Measurements can be used to determine properties of a wireless network under a given configuration. Measurements can inform decisions made by wireless participants, such as user equipment and base stations, leading to better resource management and improved quality of service. Because current measurement techniques in wireless communication systems suffer from various drawbacks, limitations, and disadvantages, the inventive systems, methods, components, and apparatus described herein are needed. Summary of the Invention

[0003] This subject matter relates to methods, devices, and systems for improving measurement techniques in wireless communications. Specifically, this subject matter relates to configuring bandwidth parts (BWPs), including non-cell-defining synchronization signal blocks (NCD-SSBs). Techniques for configuring measurement configurations after BWPs, including NCD-SSBs, are disclosed.

[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 part (BWP) based on the serving cell MO.

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

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

[0007] In some other embodiments, an apparatus for wireless communication may include: a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0008] In some other embodiments, a device for wireless communication may include: a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

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

[0010] These and other aspects and their implementations are described in more detail in the drawings, description, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 An example of a wireless communication system including one wireless base station and one or more user equipments is shown.

[0012] Figure 2 An example of a base station is shown.

[0013] Figure 3 An example of a user device is shown.

[0014] Figure 4 An example of a base station is shown. DETAILED DESCRIPTION

[0015] The present subject matter will now be described in detail hereinafter with reference to the accompanying drawings, which form a part hereof and show by way of illustration specific examples of embodiments. However, it is to be noted that the present subject matter can be embodied in various forms and, therefore, it is intended that the subject matter covered or claimed be construed as not limited to any of the embodiments described below.

[0016] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied from the context rather than their explicitly stated meanings. Likewise, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" as used herein do not necessarily refer to different implementations. For example, it is intended that the claimed subject matter include all or part of the example embodiments or combinations of implementations.

[0017] In general, terms can be understood at least in part from their usage in the context. For example, terms used herein, such as "and", "or" or "and / or" can have multiple meanings that depend at least in part on the context in which the terms are used. Typically, "or" if used in an associative list, such as A, B or C, is intended to mean A, B and C (here in an inclusive sense) as well as A, B or C (here in an exclusive sense). In addition, the terms "one or more" or "at least one" as used herein, depending at least in part on the context, can be used to describe any feature, structure or characteristic in a singular sense, or can be used to describe a combination of features, structures or characteristics in a plural sense. Similarly, terms such as "a", "an" or "the" can also be understood to express singular usage or plural usage, depending at least in part on the context. In addition, the terms "based on" or "determined by..." can be understood to not necessarily be intended to express an exclusive set of factors, but rather can allow for the presence of additional factors that are not necessarily explicitly described, which also depends at least in part on the context.

[0018] Figure 1 A schematic diagram of an example wireless communication system 100 is shown, which includes a plurality of communication nodes (or simply nodes) configured to wirelessly communicate with each other. Generally speaking, the communication nodes include at least one user equipment 102 and at least one radio access node 104. Figure 1 The example wireless communication system 100 in FIG. 1 is shown as including two user equipments 102 (including a first user equipment 102(1) and a second user equipment 102(2)) and one wireless access node 104. However, various other examples of the wireless communication system 100 including any of various combinations of one or more user equipments 102 and / or one or more wireless access nodes 104 are possible.

[0019] In general, user equipment described herein, such as user equipment 102, may include a single electronic device or apparatus, or multiple electronic devices or apparatuses (e.g., a network) capable of wireless communication over a network. User equipment may include or be otherwise referred to as a user terminal, user terminal device, or user equipment (UE). Furthermore, a user device may be or include, but is not limited to, a mobile device (e.g., a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer), a vehicle, or other vessel (powered by human power, motor, or engine, such as a car, airplane, train, boat, or bicycle, as non-limiting examples), or a fixed or stationary device (e.g., a desktop computer, or other computing device that is typically not moved for extended periods of time, such as a home appliance, other relatively heavy devices including the Internet of Things (IoT), or computing devices used in commercial or industrial environments, as non-limiting examples). In various embodiments, the user device 102 may include a transceiver circuit 106 coupled to an antenna 108 to enable wireless communication with the wireless access node 104. The transceiver circuit 106 may also be coupled to a processor 110, which may further 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, causes the processor 110 to implement the various methods described herein.

[0020] Furthermore, in general, a wireless access node, such as wireless access node 104, as described herein, may include a single electronic device or apparatus, or multiple electronic devices or apparatuses (e.g., a network), and may include one or more base stations or other wireless network access points capable of wirelessly communicating with one or more user devices and / or with one or more other wireless access nodes 104 via the network. For example, in various embodiments, wireless access node 104 may include a 4G LTE base station, a 5G NR base station, a 5G centralized cell base station, a 5G distributed cell base station, a next-generation Node B (gNB), an enhanced Node B (eNB), or other similar or next-generation (e.g., 6G) base station. Wireless access node 104 may include a transceiver circuit 114 coupled to an antenna 116, which may include an antenna tower 118 in various implementations, to enable wireless communication with user device 102 or another wireless access node 104. Transceiver circuit 114 may also be coupled to one or more processors 120, which may be further coupled to a memory 122 or other storage device. The memory 122 may store instructions or codes therein, which, when the processor 120 reads and executes these instructions or codes, enable the processor 120 to implement one or more methods described herein.

[0021] In various embodiments, two communication nodes in wireless system 100—e.g., user equipment 102 and wireless access node 104, two user equipment 102 without wireless access node 104, or two wireless access nodes 104 without user equipment 102—can be configured to communicate wirelessly in or through a mobile network and / or wireless access network in accordance with one or more standards and / or specifications. Generally, standards and / or specifications may define rules or procedures under which communication nodes may communicate wirelessly, and in various embodiments, may include those for communicating in millimeter (mm) wavebands and / or having multiple antenna schemes and beamforming capabilities. Additionally or alternatively, standards and / or specifications may be those defining wireless access technologies and / or cellular technologies, such as fourth generation (4G) long term evolution (LTE), fifth generation (5G) new radio (NR), or unlicensed new radio (NR-U), as non-limiting examples.

[0022] Furthermore, in the wireless system 100, communication nodes are configured to communicate wirelessly with each other. Typically, in the wireless system 100, communication between two communication nodes may be or include transmission or reception, and typically both are performed simultaneously, depending on the perspective of the particular nodes in the communication. 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 node or a transmitting node or device, and the second node may be referred to as a destination node or a receiving node or device, and the communication may be viewed as transmission by the first node and reception by 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 simultaneously act as a transmitting / source node and a receiving / destination node, or may switch between acting as a source / transmitting node and a destination / receiving node.

[0023] Furthermore, a specific signal may be characterized or defined as an uplink (UL) signal, a downlink (DL) signal, or a sidelink (SL) signal. An uplink signal is a signal transmitted from user equipment 102 to wireless access node 104. A downlink signal is a signal transmitted from wireless access node 104 to user equipment 102. A sidelink signal is a signal transmitted from one user equipment 102 to another user equipment 102, or a signal transmitted from one wireless access node 104 to another wireless access node 104. Furthermore, for sidelink transmission, a first / source user equipment 102 transmits a sidelink signal directly to a second / destination user equipment 102 without forwarding the sidelink signal to wireless access node 104.

[0024] Furthermore, signals transmitted between communication nodes in system 100 may be characterized or defined as data signals or control signals. Generally, data signals are signals that include or carry data, such as multimedia data (e.g., voice and / or image data), while control signals are signals that carry control information that configures communication nodes to communicate with each other in a particular manner or otherwise controls how communication nodes transmit data signals to each other. Furthermore, certain signals may be defined or characterized by a combination 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.

[0025] For at least some specifications, such as 5G NR, data and control signals are sent and / or carried on physical channels. Typically, a physical channel corresponds to a set of time-frequency resources used to send signals. Different types of physical channels can be used to send different types of signals. For example, a physical data channel (or only a data channel) is used to send data signals, and a physical control channel (or only a control channel) is used to send control signals. Example types of physical data channels include, but are not limited to: a physical downlink shared channel (PDSCH) for transmitting downlink data signals, a physical uplink shared channel (PUSCH) for transmitting uplink data signals, and a physical sidelink shared channel (PSSCH) for transmitting sidelink data signals. In addition, example types of physical control channels include, but are not limited to: a physical downlink control channel (PDCCH) for transmitting downlink control signals, a physical uplink control channel (PUCCH) for transmitting uplink control signals, and a physical sidelink control channel (PSCCH) for transmitting sidelink control signals. For simplicity, unless otherwise specified, a particular type of physical channel used in this document is also used to refer to a signal sent on that particular type of physical channel, and / or a transmission on that particular type of transmission. For example, PDSCH refers to the physical downlink shared channel itself, a downlink data signal sent on the PDSCH, or a downlink data transmission. Therefore, when a communication node transmits or receives the PDSCH, it means that the communication node is transmitting or receiving a signal on the PDSCH.

[0026] In addition, for at least some specifications, such as 5G NR, and / or for at least some types of control signals, the control signals sent by the communication nodes may include control information that contains information required to enable the transmission of one or more data signals and / or the scheduling of one or more data channels (or one or more transmissions on a data channel) between the communication nodes. For example, such control information may include information required to correctly receive, decode, and demodulate data signals received on a physical data channel during a data transmission, and / or information for an uplink scheduling grant that informs a user equipment of the resources and transmission format to be used for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) that is sent from the radio access node 104 to the user equipment 102 in the downlink direction. In other embodiments, the control information includes uplink control information (UCI) that is sent from the user equipment 102 to the radio access node 104 in the uplink direction, or sidelink control information (SCI) that is sent from one user equipment 102(1) to another user equipment 102(2) in the sidelink direction.

[0027] Furthermore, in the wireless communication system 100, the slot format of the plurality of time slots (opportunities) or frames may be configured by the wireless access node 104 or specified by the protocol. In some examples, a time slot may be indicated or specified as a downlink time slot, a flexible time slot, or an uplink time slot. Furthermore, in various embodiments, an orthogonal frequency division multiplexing (OFDM) symbol may be indicated or specified as a downlink symbol, a flexible symbol, or an uplink symbol.

[0028] Figure 2 An example base station 200 is shown. The example base station 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for transmitting / 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., fiber 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.

[0029] 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 processors 124 to perform 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 assignments, and / or other parameters.

[0030] Figure 3An example of a terminal device 300 (e.g., user equipment (UE)) is shown. UE 300 may be a mobile device, such as a smartphone or a mobile communication module arranged in a vehicle. UE 300 may include a communication interface 302, system circuitry 304, an input / output interface (I / O) 306, a display circuit 308, and a storage device 309. The display circuitry may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuits. For example, system circuitry 304 may be implemented by one or more system-on-chips (SoCs), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuitry 304 may be part of the implementation of any desired functionality in UE 300. In this regard, the system circuitry 304 may include logic to, for example, facilitate decoding and playing music and videos, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; run applications; accept user input; save and retrieve application data; establish, maintain, and terminate cellular phone calls or data connections (e.g., Internet connections); establish, maintain, and terminate wireless network connections, Bluetooth connections, or other connections; and display relevant information on the user interface 310. The 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 the I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, a universal serial bus (USB) connector, a memory card slot, a radiation sensor (e.g., an IR sensor), and other types of input.

[0031] Reference Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that handles the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. A transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, a waveform shaper, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving signals via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The signals transmitted and received may conform to any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver that supports 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 from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0032] Reference Figure 3 , the system circuitry 304 may include one or more processors 321 and memory 322. The memory 322 may store, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to implement the desired functionality of the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received via the communication interface 302. In various implementations, the system power of the UE 300 may be supplied by a power storage device (e.g., a battery or a transformer).

[0033] This subject matter describes several example embodiments, which may be partially or fully described in detail with reference to Figures 1-4 The base station 200 and / or the UE 300 are implemented.

[0034] Base station 200 can configure a serving cell with one cell-defining SSB (CD-SSB) and one or more non-cell-defining SSBs (NCD-SSBs). UE 300 can be configured with a downlink BWP in RRC Connected mode, with one or more BWPs. A BWP is a set of frequency resources in the frequency domain. Each downlink BWP can be configured with a CD-SSB, an NCD-SSB, or neither.

[0035] 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 (legacy serving cell MO) or may be configured as a per-BWP serving cell MO based on the NCD-SSB associated with the downlink BWP.

[0036] The BWP can be configured with a per-BWP serving cell MO. If a per-BWP serving cell MO is configured, when the BWP is activated, the UE 300 can perform serving cell measurements based on the per-BWP serving cell MO. Otherwise, the UE 300 can perform serving cell measurements based on the CD-SSB-based serving cell MO.

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

[0038] Figure 4 This section describes an overall architecture with a centralized unit (CU) / distributed unit (DU) split. A gNB 405 may include a gNB centralized unit (gNB-CU 410) ("CU" 410) and one or more gNB distributed units (gNB-DUs 415) ("DUs" 415). The gNB-CU 410 and gNB-DUs 415 may be connected via an F1 interface 420. The gNB-CU 410 may be defined as a logical node that hosts the radio resource control (RRC), SDAP, and PDCP protocols for a gNB, or the RRC and PDCP protocols for an en-gNB, and controls the operation of one or more gNB-DUs 415. The gNB-DU 415 may be defined as a logical node that hosts the RLC, MAC, and PHY layers of the gNB 405 or en-gNB, and the operation of the gNB-DU 415 may be partially controlled by the gNB-CU 410. A gNB-DU 415 may support one or more cells. A cell may be supported by only one gNB-DU 415.

[0039] In the conventional 3GPP TS 38.473 specification, serving cell MO and measurement gaps are configured using the following procedure: (1) CU 410 configures the content of serving cell MO in the measConfig IE; (2) CU 410 indicates the identifier (ID) of the serving cell MO to DU 415 during the UE context establishment or UE context modification procedure. CU 410 can request DU 415 to configure measurement gaps by including the measConfig IE in the UE context establishment 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 per UE or per FR. DU 415 (1) configures the content of the servingCellConfig IE by including the serving cell MO ID. Specifically, DU 415 assigns the serving cell MO ID value indicated by the CU to the servingCellMO IE in the servingCellConfig IE; and (2) DU 415 configures the measurement gap according to the request of CU 410 and fills the measurement gap information in the measConfig IE. Then, DU 415 includes the servingCellConfig IE and the measConfig IE in the UE Context Setup Response message or the UE Context Modification Response message to CU 410. Then, CU 410 sends an RRC message to the UE based on the corresponding IE sent from DU 415 for the UE, and the RRC message includes the servingCellConfig IE and the measConfig IE.

[0040] According to this topic, after introducing per-BWP serving cell MO, the problems of serving cell MO and measurement gap configuration are solved, overcoming the shortcomings of the traditional 3GPP TS 38.473 specification. Specifically, the procedures defined in the traditional 3GPP TS 38.473 specification do not consider the configuration of per-BWP serving cell MO.

[0041] 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 MODIFY REQUEST message because there is no IE defined to convey this information.

[0042] In the current 3GPP TS 38.473 specification, since the BWP configuration is configured by the DU 415 rather than the CU 410, the CU 410 has no way of knowing whether the DU 415 will configure the downlink BWP for the UE 300 to include the NCD-SSB, or which NCD-SSB will be configured for the downlink BWP when the CU 410 initiates the UE context establishment or UE context modification procedure. Therefore, the CU 410 cannot determine whether per-BWP serving cell MO configuration and the corresponding MO ID are required.

[0043] In the current 3GPP TS 38.473 specification, when CU 410 initiates the UE context establishment or UE context modification process, CU 410 has no way of knowing whether the CD-SSB-based serving cell MO is useful. The CD-SSB-based serving cell MO will be applied in the following cases: (1) when there is a downlink BWP containing CD-SSB, or (2) when the downlink BWP contains NCD-SSB but no per-BWP serving cell MO is configured for the downlink BWP. In this case, when the downlink BWP is activated, UE 300 will perform serving cell measurements based on the CD-SSB-based serving cell MO. If neither case (1) nor (2) occurs, UE 300 will not apply the CD-SSB-based serving cell MO. Therefore, the serving cell MOID carried in the current UE context establishment request message or UE context modification request message is useless, but CU 410 is not aware of this. CU 410 can continue to configure the CD-SSB-based serving cell MO to UE 300 in the RRC message.

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

[0045] With the introduction of per-BWP serving cell MO, CU 410 cannot determine which frequency of the configured SSBs in the serving cell will be measured. This is because the determination depends on whether CD-SSB-based serving cell MO is applied, whether per-BWP serving cell MO is configured, and which NCD-SB is configured. Therefore, before DU 415 performs BWP configuration for the UE, CU 410 cannot simply determine whether measurement gaps are required.

[0046] In summary, after the introduction of per-BWP serving cell MO, the method described in the current 3GPP TS 38.473 specification cannot provide an effective solution for configuring serving cell MO based on CD-SSB and NCD-SSB, and cannot provide an effective solution for configuring measurement gaps.

[0047] As used herein, a BWP containing an SSB shall refer to at least one of the following situations: (1) the frequency domain resources of the BWP contain SSB frequency domain resources; and / or (2) the BWP is configured with an SSB; that is, the SSB is associated with the BWP.

[0048] The terms SSB, CD-SSB, and NCD-SSB used in this document shall all refer to an SSB burst, which may be understood as carrying one or more synchronization signal (SS) blocks.

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

[0050] The DU 415 may configure the serving cell MO ID or the serving cell MO ID per BWP in one of the following cases.

[0051] In the first case, if DU 415 configures a downlink BWP including an NCD-SSB and CU 410 indicates the ID of the serving cell MO based on the NCD-SSB, DU 415 may include the ID of the serving cell MO in the configuration of the downlink BWP. In other words, DU 415 may configure the serving cell MO per BWP as the aforementioned serving cell MO based on the NCD-SSB.

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

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

[0054] In the fourth case, if the CU 410 does not indicate the ID of the CD-SSB-based serving cell MO, (1) the DU 415 may not configure the downlink BWP including the CD-SSB; and / or (2) the DU 415 may not configure the downlink BWP including the NCD-SSB without configuring the per-BWP serving cell MO ID for the downlink BWP.

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

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

[0057] 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. Either of the above response messages may include at least one of the following: (1) information indicating whether the BWP configured for the UE 300 uses a CD-SSB-based serving cell MO; and / or (2) information indicating which NCD-SSB-based serving cell MO is configured for the BWP configured for the UE 300.

[0058] In the message between CU 410 and DU 415, the NCD-SSB-based serving cell MO can be associated with the NCD-SSB using one of the following methods: (1) associating the serving cell MO ID with the NCD-SSB ID; (2) associating the serving cell MO ID with the frequency information of the NCD-SSB.

[0059] In the message between CU 410 and DU 415, the serving cell MO based on NCD-SSB can be identified using one of the following methods: (1) the ID of the NCD-SSB associated with the serving cell MO; (2) the frequency information of the NCD-SSB associated with the serving cell MO; (3) the measurement object ID (MO ID).

[0060] In addition, if the measConfig IE is included in the UE Context Setup Request message or the UE Context Modify Request message, the DU 415 may determine the measurement gap. The DU 415 may determine the measurement gap based on one or more of the following: (1) information included in the measConfig IE; (2) a result of which serving cell MO is used by the UE 300 according to the techniques disclosed herein, 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. Subsequently, the DU 415 may include the measurement gap configuration in the measConfig, which is included in the response message.

[0061] After receiving the response message, DU 415 may perform the following operations: For serving cell MOs that are not configured for any BWP of UE 300, CU 410 may remove them from the measConfig IE, or CU 410 may not include serving cell MOs in the measConfig IE. The measConfig IE may be sent to UE 300 in an RRC message.

[0062] DU 415 can configure the BWP based on various factors, including the capabilities of UE 300. In this example, DU 415 can also consider preferences and / or candidate serving cell MO information provided by CU 410. After configuration for UE 300, DU 415 can inform CU 410 which serving cell MO to use or not to use. CU 410 can then remove candidate serving cell MOs that are not configured for UE 300. At the same time, DU 415 can also determine measurement gaps based on the results of the serving cell MO configuration and measurement configuration provided by CU 410. Therefore, only one step (including one request and one response) is required to complete the serving cell MO configuration and measurement gap configuration.

[0063] Alternatively or additionally, DU 415 may indicate the BWP configuration to CU 410, and CU 410 may configure the serving cell measurement object. In a message sent from DU 415 to CU 410 (e.g., a UE context setup response message or a UE context modification response message), DU 415 may indicate the BWP configuration information of UE 300 to CU 410. The BWP configuration information may include at least one of the following items: (1) whether there is a BWP including a CD-SSB; (2) information about the BWP including the CD-SSB, and may further include at least one of the following: (a) a BWP ID of the BWP; and / or (b) the type of the BWP, such as the first activated BWP, the initial downlink BWP, the reduced capability (RedCap) specific initial downlink BWP, or the default BWP; and / or (3) information about the BWP including the NCD-SSB, and may further include one or more of the following items: the number of BWPs of this type, the BWPID of the BWP of this type, and / or information about the NCD-SSB included in the BWP, such as the ID of the NCD-SSB, the frequency of the NCD-SSB, or other information for CU 410 to identify the NCD-SSB.

[0064] DU 415 may also indicate a preference for per-BWP serving cell MO configuration to CU 410. The preference may be one of: (1) preferably configuring per-BWP serving cell MO for BWPs including NCD-SSBs, or (2) preferably not configuring per-BWP serving cell MO for BWPs including NCD-SSBs.

[0065] CU 410 may configure the serving cell MO configuration for UE 300 based on the BWP configuration information sent from DU 415 to CU 410. CU 410 may indicate the configured serving cell MO information to DU 415 in a subsequent message (e.g., a UE Context Modification Request message). The UE Context Modification Request message may include one or more of the following: (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.

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

[0067] When using the technology according to the present subject matter, DU 415 may first notify CU 410 of BWP configuration information. The BWP configuration information may include whether CD-SSB is configured for the downlink BWP of UE 300, whether NCD-SSB is configured (i.e., included) in the downlink BWP of UE 300, or some other detailed information of the corresponding BWP.

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

[0069] Therefore, DU 415 can complete serving cell MO configuration for both traditional serving cell MO based on CD-SSB and per-BWP serving cell MO based on NCD-SSB.

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

[0071] In a conventional NR system, system information (SI) can be categorized into the master information block (MIB), SI block 1 (SIB1), and other SI. The UE 300 receives other SI by monitoring the PDCCH timings defined by the search space. The search space used to receive other SI can 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.

[0072] After handover, UE 300 may obtain the SI of the target cell by one of the following methods: (1) UE 300 monitors PDCCH timing according to the common search space configured for SI reception; and / or (2) the target cell transmits the SI to UE 300 via a dedicated RRC message.

[0073] In a legacy NR system, a RedCap UE may be configured with a downlink BWP that does not have a common search space for SI (including SIB1 and other SI) reception.

[0074] During the handover process, the UE will activate the first activated downlink BWP of the target cell and initiate a RACH procedure in the first activated downlink BWP. However, the first activated downlink BWP may be configured so that it is not configured with a common search space for SI reception. Therefore, the UE 300 cannot obtain the SI of the target cell by monitoring the PDCCH opportunities in the first activated downlink BWP of the target cell.

[0075] In this case, in order to facilitate the handover process, the base station 200 must send SI to the UE 300 via a dedicated RRC message.

[0076] 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. In order to determine whether it is necessary to include SI in the dedicated message, the CU 410 needs to know the configuration of the first activated downlink BWP for the UE 300.

[0077] To address these issues according to the present subject matter, CU 410 may first request DU 415 to establish a UE context by sending a UE context setup request message during a handover process. DU 415 may configure a serving cell configuration, including a BWP configuration. The BWP configuration may include a first activated downlink BWP configuration.

[0078] In the case that the first activated downlink BWP does not include a CD-SSB or a control resource set (CORSET) of zero, the DU 415 may not configure a common search space for SI reception.

[0079] Subsequently, the DU 415 may indicate to the CU 410 in the UE Context Setup Response message one of the following: (1) dedicated SI transmission is required; (2) the first activated downlink BWP does not include a CD-SSB; (3) the first activated downlink BWP is not configured with a common search space for SI reception (i.e., search space zero or a search space used for other SI); and / or (4) the first activated downlink BWP is a RedCap-specific initial downlink BWP.

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

[0081] Using the techniques according to the present subject matter, CU 410 may know whether dedicated SI transmission is needed for UE 300. When the first activated BWP is not configured with a common search space for receiving SI, UE 300 may acquire SI without monitoring PDCCH opportunities.

[0082] According to the present subject matter, during a UE context establishment or UE modification procedure, CU 410 may provide DU 415 with a list of candidate serving cell MO IDs. DU 415 may configure a per-BWP serving cell MO based on the candidate serving cell MO IDs. CU 410 may also indicate a preference for a per-BWP serving cell MO configuration. DU 415 may indicate the serving cell MO for UE 300 to CU 410. DU 415 may determine measurement gaps based on the measConfig IE sent from CU 410 and the determination of the per-BWP serving cell MO configuration. CU 410 may remove candidate serving cell MOs not used by UE 300 from the measConfig IE. During a UE context establishment or modification procedure, DU 415 may notify CU 410 of the BWP configuration, for example, whether a BWP including an NCD-SSB exists. CU 410 may configure the serving cell MO based on the per-BWP serving cell MO configuration. DU 415 may indicate a preference for a per-BWP serving cell MO configuration. During handover, if the first activated downlink BWP is not configured with a common search space for SI, DU 415 may inform CU 410 that dedicated SI transmission is required for UE 300. CU 410 may then include the SI in a dedicated RRC message to UE 300.

[0083] This subject matter describes methods, apparatus, and computer-readable media for wireless communications. This subject matter addresses the issue of scheduling multiple transmissions for one or more cells by reducing the number of bits required to indicate scheduled transmissions. The methods, apparatus, and computer-readable media described herein can improve the performance of wireless transmissions between user equipment and base station 200, thereby increasing efficiency and overall performance. The methods, apparatus, and computer-readable media described herein can improve the overall efficiency of wireless communication systems.

[0084] The foregoing description and accompanying drawings provide specific example embodiments and implementations. However, the subject matter described may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any example embodiment set forth herein. The subject matter claimed or covered is intended to be reasonably broad in scope. For example, among other aspects, the subject matter may be embodied as a method, device, component, system, or non-transient computer-readable medium for storing computer code. Thus, embodiments may take the form of, for example, hardware, software, firmware, storage media, or any combination thereof. For example, a component, device, or system comprising a memory and a processor may implement the above-described method embodiments by executing computer code stored in a memory.

[0085] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied by the context rather than the meanings explicitly stated. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, it is contemplated that claimed subject matter includes combinations of all or part of the example embodiments.

[0086] In general, terms can be understood, at least in part, by their usage in context. For example, terms used herein, such as "and," "or," or "and / or," may include multiple meanings that depend, at least in part, on the context in which the terms are used. Typically, "or," if used in an associative list, such as A, B, or C, is intended to mean A, B, and C (used herein in an inclusive sense) as well as A, B, or C (used herein in an exclusive sense). Furthermore, 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, depending, at least in part, on the context. Similarly, terms such as "a," "an," or "the" may be understood to convey singular usage, or to convey plural usage, depending, at least in part, on the context. Furthermore, the term "based on" may be understood to not necessarily be intended to convey an exclusive set of factors, but rather may allow for the presence of additional factors that are not necessarily explicitly described, again depending, at least in part, on the context.

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

[0088] Furthermore, the features, advantages, and characteristics described herein may be combined in any suitable manner in one or more embodiments. Based on the description herein, one of ordinary skill in the relevant art will recognize that the present solution may be implemented without the specific features or advantages of one or more particular embodiments. In other cases, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.

[0089] The subject matter of the present disclosure may also relate to or include, among other things:

[0090] The first aspect includes a method for measurement configuration in a wireless communication network, comprising: providing multiple 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 multiple candidate serving cell MO IDs; and configuring, by the DU, a serving cell MO configuration per bandwidth part (BWP) based on the serving cell MO.

[0091] The second aspect includes the method of aspect 1, further comprising: indicating, by the CU, a preference for serving cell MO configuration.

[0092] The third aspect includes the method of aspect 1 or 2, further comprising: determining, by the DU, the measurement gap based on per-BWP serving cell MO configuration.

[0093] The fourth aspect includes the method of any of the above aspects, further comprising: the CU removing the candidate serving cells MO that are not selected by the DU from the measConfig IE.

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

[0095] The sixth aspect includes the method of any of the above aspects, further including: the DU uses a response message to respond to the UE context establishment request message or the UE modification request message, and the response message includes at least one of the following items: whether the service cell MO is based on the cell-defined synchronization signal block (CD-SSB), and the CD-SSB is configured by the BWP configured for the UE; or whether the service cell MO is based on the non-cell-defined synchronization signal block (NCD-SSB), and the NCD-SSB is configured by the BWP configured for the UE.

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

[0097] The eighth aspect includes the method of any of the preceding aspects, 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.

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

[0099] The tenth aspect includes the method of any of the preceding aspects, wherein the multiple candidate serving cell MO IDs are based on a measurement configuration, the measurement configuration including a frequency list, and the CU requests the DU to generate a measurement gap and a measurement gap type for the frequency list.

[0100] The eleventh aspect includes the method of any of the preceding aspects, further comprising: configuring the downlink BWP by the DU.

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

[0102] The thirteenth aspect includes the method of any of the preceding aspects, wherein the CU does not indicate the ID of the serving cell MO based on the NCD-SSB; and the method further includes: the DU does not configure the per-BWP serving cell MO configuration for the configured downlink BWP.

[0103] The fourteenth aspect includes the method of any of the preceding aspects, further comprising: configuring, by the DU, a downlink BWP including a CD-SSB.

[0104] The fifteenth aspect includes the method of any of the preceding aspects, further comprising: configuring, by the DU, a downlink BWP including an NCD-SSB; and not configuring, by the DU, a per-BWP service cell MO for the configured downlink BWP.

[0105] The sixteenth aspect includes the method of any of the preceding aspects, wherein the ID of the CD-SSB-based service cell MO is not indicated by the CU; and the method further includes: the DU does not configure the downlink BWP including the CD-SSB.

[0106] The seventeenth aspect includes the method of any of the preceding aspects, wherein the ID of the CD-SSB-based service cell MO is not indicated by the CU; and the method further includes: configuring a downlink BWP including NCD-SSB by the DU; and configuring the per-BWP service cell MO ID for the downlink BWP.

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

[0108] The nineteenth aspect includes the method of any of the preceding aspects, further including: the DU does not configure a downlink BWP including an NCD-SSB.

[0109] The twentieth aspect includes the method of any of the preceding aspects, further comprising: the DU does not configure a downlink BWP including a CD-SSB.

[0110] A twenty-first aspect includes the method of any of the preceding aspects, further comprising: configuring, by the DU, a downlink BWP including an NCD-SSB; and configuring a per-BWP serving cell MO ID for the downlink BWP.

[0111] Aspect 22 includes the method of any of the preceding aspects, wherein the preference is a CD-SSB-based service cell MO, and the CD-SSB-based service cell MO is configured to a downlink BWP including CD-SSB or NCD-SSB.

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

[0113] Aspect 24 includes the method of any of the preceding aspects, wherein the serving cell MO ID is indicated by the CU using one or more of the following items: an NCD-SSB identifier associated with the serving cell MO; frequency information of the NCD-SSB associated with the serving cell MO; or MO ID.

[0114] Aspect 25 includes the method of any of the preceding aspects, wherein the measurement gap is further determined based on: information included in the measConfig IE; whether the CD-SSB-based service cell MO is configured for the UE's BWP; whether the NCD-SSB-based service cell MO is configured through the UE's BWP, and which of the NCD-SSB-based service cell MOs is configured.

[0115] Aspect 26 includes the method of any of the preceding aspects, wherein after the CU receives the response message: the CU does not include unselected candidate serving cells in the IEmeasConfig; and sends the IE measConfig to the UE in a radio resource control (RRC) message.

[0116] Aspect twenty-seven includes a method for measurement configuration in a wireless communication network, comprising: sending a message from the DU to the CU, the message indicating the BWP configuration information of the UE; sending the service cell MO configuration by the CU to the DU; and configuring the service cell MO identifier for the UE based on the service cell MO configuration by the DU.

[0117] The twenty-eighth aspect includes the method of aspect 27, further including: the DU indicates the preference for per-BWP serving cell MO configuration to the CU; and the CU configures the serving cell MO configuration for the UE based on the message indicating the BWP configuration information.

[0118] The twenty-ninth aspect includes the method of aspect 27 or 28, wherein the message is: a UE context establishment response message; or a UE context modification response message.

[0119] A 30th aspect includes the method of any of aspects 27-29, wherein the BWP configuration information includes at least one of the following items: whether the BWP includes CD-SSB; the BWP identifier of the BWP; the type of BWP; the number of types of BWP; the BWP identifier of the type of BWP; the identifier of the NCD-SSB; or the frequency of the NCD-SSB.

[0120] Aspect 31 includes the method of any one of aspects 27-30, wherein the preference includes one or more of the following items: for a BWP including an NCD-SSB, a preference for MO per BWP service cell is configured; or for a BWP including an NCD-SSB, a preference for MO per BWP service cell is not configured.

[0121] Aspect 32 includes the method of any one of aspects 27-31, further including: the CU indicates the configured service cell MO information to the DU in the UE context modification request message.

[0122] Aspect thirty-third includes the method of any one of aspects 27-32, wherein the UE context modification request message includes at least one of the following items: an identifier of a serving cell MO based on CD-SSB; or an identifier of a serving cell MO based on NCD-SSB.

[0123] A thirty-fourth aspect includes the method of any one of aspects 27-33, wherein the serving cell MO identifier is based on CD-SSB, and the method further includes: configuring the serving cell MO IE based on CD-SSB by the DU.

[0124] A thirty-fifth aspect includes the method of any one of aspects 27-34, wherein the serving cell MO is based on NCD-SSB, and the method further includes: configuring, by the DU, a per-BWP serving cell MO configuration for a BWP including NCD-SSB.

[0125] A thirty-sixth aspect includes a method for measurement configuration in a wireless communication network, comprising: sending a UE context establishment response message by the CU to the DU, wherein the UE context establishment response message includes at least one of the following items: dedicated system information transmission is required; the activated downlink BWP does not include a CD-SSB; the activated downlink BWP is not configured with a common search space for system information reception; or the activated downlink BWP is a reduced capability (RedCap) specific initial downlink BWP.

[0126] A thirty-seventh aspect includes the method of aspect 36, wherein the BWP configuration comprises: an activated downlink BWP configuration.

[0127] Aspect 38 includes the method of aspect 36 or 37, further including: configuring, by the DU, a service cell configuration including a BWP configuration; indicating, by the DU, a UE context establishment response message to the CU; and sending, by the CU, a dedicated RRC message including system information (SI) to the UE.

[0128] A thirty-ninth aspect includes the method of any one of aspects 36-38, wherein the dedicated RRC message is an RRC reconfiguration message for handover.

[0129] The fortieth aspect relates to a device for wireless communication, the device comprising: a processor; and a memory in communication with the processor, the memory storing a plurality of instructions executable by the processor so that the device implements the method of any of the aforementioned aspects.

[0130] A forty-first aspect relates to a non-transitory computer-readable medium comprising instructions, which, when executed by one or more processors, are used to implement the method of any one of aspects 1-39.

Claims

1. A measurement configuration method in a wireless communication network, comprising: Receiving, by a distributed unit DU, a list of candidate serving cell measurement object identifiers (MO) from a centralized unit CU, wherein one or more candidate serving cell MOIDs are based on a non-cell definition synchronization signal block (NCD-SSB) indicated by the CU to the DU; The DU selects a serving cell MO to be used for the user equipment UE from the candidate serving cell MO ID list; The DU configures a serving cell MO configuration for a bandwidth part BWP according to the serving cell MO; as well as The DU sends indication information to the CU, where the indication information indicates: which service cell MOID based on the non-cell definition synchronization signal block NCD-SSB is configured for the BWP configured for the UE.

2. The method according to claim 1, wherein The candidate serving cell MO ID list is provided in a UE context setup request message or a UE context modification request message sent from the CU to the DU.

3. The method according to claim 2, further comprising: The DU sends a response message to the UE context setting request message or the UE context modification request message, wherein the response message includes the indication information.

4. The method according to claim 3, wherein the response message includes the serving cell MO configuration for the BWP, wherein the serving cell MO configuration for the BWP is included in a serving cell MO information element IE, and the serving cell MO IE is included in a servingCellConfigIE.

5. The method according to claim 1, wherein The serving cell MOID is indicated by the CU to the DU together with the following items: Frequency information of the NCD-SSB associated with the serving cell MO.

6. The method according to any one of claims 1 to 3, further comprising: The downlink BWP is configured by the DU.

7. The method according to claim 6, wherein The downlink BWP includes an NCD-SSB; and the method further includes: The serving cell MO configuration for the BWP is configured by the DU based on the NCD-SSB.

8. A measurement configuration method in a wireless communication network, comprising: The centralized unit CU sends a list of candidate serving cell measurement object MO identifiers IDs to the distributed unit DU, wherein one or more candidate serving cell MOIDs are based on the non-cell definition synchronization signal block NCD-SSB indicated by the CU; and The CU receives indication information from the DU, where the indication information indicates which NCD-SSB-based serving cell MO is configured for the bandwidth part BWP configured for the UE, and the indicated MOID is selected from a candidate serving cell MOID list.

9. The method according to claim 8, wherein the candidate serving cell MOID list is transmitted in a UE context setup request message or a UE context modification request message from the CU to the DU.

10. The method according to claim 8 or 9, wherein the indication information is transmitted in a UE context setup response message or a UE context modification response message from the DU to the CU.

11. The method according to claim 8 or 9, wherein: The configured serving cell MO is related to the following items: Frequency information of the NCD-SSB associated with the serving cell MO.

12. The method according to claim 8 or 9, further comprising: The CU configures a serving cell MO configuration for the UE based on the serving cell MO configuration for the BWP; or The CU sends a dedicated RRC message including the serving cell MO configuration to the UE.

13. A wireless communication device comprising: processor; and a memory in communication with the processor, the memory storing a plurality of instructions executable by the processor, causing the apparatus to: Implement the method according to any one of claims 1 to 7.

14. A wireless communication device comprising: processor; and a memory in communication with the processor, the memory storing a plurality of instructions executable by the processor, causing the apparatus to: Implement the method according to any one of claims 8 to 12.

Images