Abstract: A central unit (1) that is a base station transmits, to a distributed unit (2) that is a base station, a message for requesting addition of a secondary cell of carrier aggregation. This message includes a first information element indicating whether the secondary cell initially should be activated or dormant. This can contribute, for example, to improvement for enabling direct setting of a secondary cell state in an architecture in which base stations are separated into a central unit and a distributed unit.
Title of the invention: distributed unit, central unit, and methods thereof.
Technical field
[0001]
This disclosure relates to wireless communication systems, and particularly to enhancements of carrier aggregation.
Background technology
[0002]
3rd Generation Partnership Project (3GPP) Release 15 will introduce enhancements of Long Term Evolution (LTE) carrier aggregation (CA). These enhancements are aimed at the rapid setup and activation of the Secondary Cell (SCell) (see Non-Patent Documents 1-4).
[0003]
One of these enhancements is the introduction of a new SCell state called the dormant state. When the SCell is dormant, the wireless terminal (i.e., User Equipment (UE)) measures and reports Channel State Information (CSI) but does not decode the Physical Downlink Control Channel (PDCCH). That is, the dormant SCell state (Dormant state SCell) is different from the activated SCell state (activated state SCell) in that at least the UE does not monitor (monitor) or decode the PDCCH. Also, the dormant SCell state differs from the deactivated SCell state (SCell in the deactivated state), at least in that the UE measures and reports the CSI.
[0004]
The other one of these enhancements is the direct SCell state configuration via RRC with Radio Resource Control (RRC). In existing CAs, when an SCell is added, it is initially deactivated. In contrast, the direct SCell state configuration allows the SCell to be initially activated or dormant via the RRC upon addition or handover of the SCell. Make it possible. eNB can specify the initial state of SCell as activated or dormant when setting SCell in RRC.
[0005]
Furthermore, as is well known, 3GPP is working on standardization of 5G for introduction after 2020. As used herein, the 5th generation mobile communication system is also referred to as a 5G system or a Next Generation (NextGen) System (NG System). The new Radio Access Technology (RAT) for the 5G System is called New Radio, NR, 5G RAT, or NG RAT. The new Radio Access Network (RAN) for the 5G System is called NextGen RAN, NG-RAN, or 5G-RAN. The new base station (NG-RAN node) in NG-RAN is called gNodeB or gNB. The new core network for the 5G System is called the 5G Core Network (5GC) or NextGen Core (NG Core). The wireless terminal (User Equipment (UE)) connected to the 5G System is called 5G UE, NextGen UE (NG UE) or simply UE.
[0006]
The main components of 5GC are Access and Mobility Management function (AMF), Session Management function (SMF), and User plane function (UPF). AMF is, for example, UE connection management and mobility management, NG-RAN control plane (CP) termination (eg, exchange of CP information with NG-RAN nodes), and NAS layer termination (eg NAS with UE). Exchange messages). SMF, for example, performs session management (Session Management (SM)) and terminates the session management part of NAS messages. UPF is an anchor point for Intra-RAT and Inter-RAT mobility (e.g. handover), and manages QoS flow (e.g. DL reflective QoS marking).
[0007]
The term "LTE" as used herein includes improvements and developments of LTE and LTE-Advanced to enable interworking with 5G Systems, unless otherwise noted. The improvements and developments of LTE and LTE-Advanced for interworking with the 5G System are also referred to as LTE-Advanced Pro, LTE +, or enhanced LTE (eLTE). For example, an eLTE eNB that functions as an NG-RAN node is also called an ng-eNB. In addition, the “Evolved Packet Core (EPC)”, “Mobility Management Entity (MME)”, “Serving Gateway (S-GW)”, and “Packet Data Network (PDN) Gateway (P-GW)” used herein. Terms relating to LTE networks or logical entities, such as ")", include these improvements and developments to enable interworking with the 5G System, unless otherwise noted. The improved EPC, MME, S-GW, and P-GW include, for example, enhanced EPC (eEPC), enhanced MME (eMME), enhanced S-GW (eS-GW), and enhanced P-GW (eP-GW). ) Also called.
[0008]
NR supports the use of different radio parameter sets in multiple frequency bands. Each radio parameter set is called "numerology". OFDM numerology for Orthogonal Frequency Division Multiplexing (OFDM) systems includes, for example, subcarrier spacing, system bandwidth, Transmission Time Interval (TTI) length, and sub. Includes subframe duration, Cyclic prefix length, and symbol duration. The 5G system provides various types of services with different service requirements, such as enhanced Mobile Broad Band (eMBB), Ultra Reliable and Low Latency Communication (URLLC), and multi-connection M2M communication (massive). Including Machine Type Communication: mMTC), support. The choice of Numerology depends on the service requirements.
[0009]
NR supports a wider channel bandwidths (e.g., 100s of MHz) than that of LTE. One channel band (i.e., BW Channel) is a radio frequency band (RF bandwidth) that supports one NR carrier. The channel bandwidth is also called the system bandwidth. LTE supports channel bandwidths up to 20 MHz, while 5G NR supports channel bandwidths up to, for example, 800 MHz.
[0010]
In order to efficiently support multiple 5G services, such as wideband services such as eMBB and narrowband services such as the Internet of Things (IoT), it is preferable to be able to multiplex these multiple services on a single channel band. .. In addition, if all 5G UEs must support transmission and reception in the transmission bandwidth for the entire channel bandwidth, this is the low cost and low power consumption of UEs for narrowband IoT services. May interfere with. Therefore, 3GPP allows one or more bandwidth parts (BWPs) to be set within the carrier band (i.e., channel band or system band) of each NR component carrier. The bandwidth part is also called the carrier bandwidth part. Multiple BWPs may be used for frequency division multiplexing (FDM) of different numerologies (e.g., subcarrier spacing (SCS)). For example, multiple BWPs may have different SCSs and different bandwidths.
[0011]
For example, the channel bandwidth of one component carrier is divided into BWP # 1 and BWP # 2, and these two BWPs are used for FDM of different numeros (e.g., different subcarrier spacing). In another example, the narrow band BWP # 1 is placed in the channel band of one component carrier, and the narrow band BWP # 2 is further placed in the BWP # 1 than the BWP # 1. When BWP # 1 or BWP # 2 is activated for a UE, the UE can reduce power consumption by not receiving and transmitting outside the active BWP (but within the channel bandwidth).
[0012]
One bandwidth part (BWP) is composed of frequency-consecutive and contiguous physical resource blocks (PRBs). The bandwidth of one BWP is at least as large as the synchronization signal (SS) / physical broadcast channel (PBCH) block bandwidth. The BWP may or may not include an SS / PBCH block (SSB).
[0013]
BWP configuration includes, for example, numerology, frequency location, and bandwidth (number of e.g., PRBs). A common PRB indexing is used for the downlink (DL) BWP configuration at least in the Radio Resource Control (RRC) connected state to specify the frequency location. Specifically, the offset from PRB 0 to the lowest PRB of the SS / PBCH block accessed by the UE is set by higher layer signaling. The reference point “PRB 0” is common to all UEs that share the same wideband component carrier.
[0014]
Each component carry One or more BWP configurations for a are quasi-statically signaled to the UE. Specifically, for each UE-specific serving cell, one or more DL BWPs (eg, up to four DL BWPs) and one or more UL BWPs (eg, up to four UL BWPs) are dedicated RRC. Can be set for UE by message. One or more DL BWPs and one or more UL BWPs set in the UE are referred to as DL BWP sets and UL BWP sets, respectively.
[0015]
Each of one or more BWPs (i.e., BWP set) set in the UE can be activated and deactivated. Activated BWP is called activated BWP (active BWP). That is, the UE receives a signal at any time (at a given time) on one or more of the configured DL BWP sets of activated DL BWP. Similarly, the UE sends a signal at any time (at a given time) on one or more of the configured UL BWP sets of activated UL BWP. It should be noted that in the current specification, only one DL BWP and only one UL BWP are activated at any time (at a given time).
[0016]
Next, the cloud RAN (C-RAN) deployment of NG-RAN will be explained. NG-RAN consists of a set of gNBs connected to 5GC via the NG interface. gNBs can be connected via the Xn interface. The gNB may be composed of a gNB Central Unit (gNB-CU) and one or more gNB Distributed Units (gNB-DUs). gNB-CU and gNB-DU are connected via the F1 interface. gNB-CU is a logical node that hosts gNB's Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols (or gNB's RRC and PDCP protocols). The gNB-DU is a logical node that hosts the gNB's Radio Link Control (RLC), MAC, and PHY layers.
[0017]
Furthermore, 3GPP is considering a CU-DU split architecture for LTE eNB. This is aimed at introducing eNB-CU and eNB-DU.
Prior art literature
Non-patent literature
[0018]
Non-Patent Document 1: Nokia, Nokia Shanghai Bell, “Stage-2 description of euCA”, 3GPP R2-1809245, 3GPP TSG-RAN WG2 Meeting # 102, Busan, South Korea, 21-25 May 2018
Non-Patent Document 2: Nokia, Nokia Shanghai Bell, “UE capability definitions for euCA”, 3GPP R2-1809246, 3GPP TSG-RAN WG2 Meeting # 102, Busan, South Korea, 21-25 May 2018
Non-Patent Document 3: Nokia, Nokia Shanghai Bell, “MAC functionality for euCA”, 3GPP R2-1809269, 3GPP TSG-RAN WG2 Meeting # 102, Busan, South Korea, 21-25 May 2018
Non-Patent Document 4: Nokia, Nokia Shanghai Bell, “Signalling for euCA (Enhancing LTE CA Utilization)”, 3GPP RP-182006, 3GPP TSG RAN Meeting # 81, Gold Coast, Australia, 10-13 September 2018
Outline of the invention
Problems to be solved by the invention
[0019]
The inventor examined the above-mentioned enhancement of carrier aggregation and found various problems. For example, when applying the direct SCell state configuration to the gNB CU-DU split architecture or the eNB CU-DU split architecture, it is not clear which of the CU and DU determines the direct SCell State, and the CU (or DU) is the DU. It is also unclear how to notify (or CU) of the direct SCell state.
[0020]
One of the objectives to be achieved by the embodiments disclosed herein is to provide devices, methods, and programs that contribute to improvements to enable direct SCell state configuration in a CU-DU split architecture. Is. It should be noted that this object is only one of the purposes that the embodiments disclosed herein seek to achieve. Other objectives or issues and novel features will be apparent from the description or accompanying drawings herein.
Means to solve problems
[0021]
In the first aspect, the central unit of the base station comprises at least one memory and at least one processor coupled to said at least one memory. The at least one processor is configured to send a first message requesting the addition of a carrier aggregation secondary cell to the distributed unit of the base station. The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
[0022]
In the second aspect, the distribution unit of the base station includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to receive a first message requesting the addition of a carrier aggregation secondary cell from the central unit of the base station. The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
[0023]
In a third aspect, the method in the central unit of a base station comprises sending a first message requesting the addition of a carrier aggregation secondary cell to the distributed unit of the base station. The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
[0024]
In the fourth aspect, the method in the distributed unit of the base station includes receiving a first message requesting the addition of a secondary cell of carrier aggregation from the central unit of the base station. The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
[0025]
In the fifth aspect, the program includes an instruction group (software code) for causing the computer to perform the method according to the third or fourth aspect described above when the program is read by the computer.
The invention's effect
[0026]
According to the above aspect, it is possible to provide a device, a method, and a program that contribute to the improvement for enabling the direct SCell state configuration in the CU-DU split architecture.
A brief description of the drawing
[0027]
FIG. 1 is a diagram showing a configuration example of a wireless communication network according to some embodiments.
FIG. 2 is a diagram showing a configuration example of a wireless communication network according to some embodiments.
FIG. 3 is a sequence diagram showing an example of signaling between a central node and a distributed node according to the first embodiment.
FIG. 4 is a diagram showing a specific example of the format of the UE CONTEXT SETUP REQUEST message according to the third embodiment.
FIG. 5 is a flowchart showing an example of the operation of the central node according to the first embodiment.
FIG. 6 is a flowchart showing an example of the operation of the distributed node according to the first embodiment.
FIG. 7 is a sequence diagram showing an example of signaling between a central node and a distributed node according to a second embodiment.
FIG. 8 is a flowchart showing an example of the operation of the central node according to the second embodiment.
FIG. 9 is a flowchart showing an example of the operation of the distributed node according to the second embodiment.
FIG. 10 is a sequence diagram showing an example of signaling between a central node and a distributed node according to a third embodiment.
FIG. 11 is a diagram showing a specific example of the format of the UE CONTEXT SETUP REQUEST message according to the third embodiment.
FIG. 12 is a diagram showing a specific example of the format of the UE CONTEXT MODIFICATION REQUEST message according to the third embodiment.
FIG. 13 is a diagram showing a specific example of the format of the UE INACTIVITY NOTIFICATION message according to the third embodiment.
FIG. 14 is a sequence diagram showing an example of signaling between a central node and a distributed node according to a fourth embodiment.
FIG. 15 is a sequence diagram showing an example of signaling between a central node and a distributed node according to a fifth embodiment.
FIG. 16 is a block diagram showing a configuration example of a central node (e.g., gNB-CU) according to some embodiments.
FIG. 17 is a block diagram showing a configuration example of a distributed node (e.g., gNB-DU) according to some embodiments.
Embodiment for carrying out the invention
[0028]
In the following, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and duplicate explanations are omitted as necessary for the sake of clarification of the explanations.
[0029]
The plurality of embodiments described below can be implemented independently or in combination as appropriate. These plurality of embodiments have novel features that differ from each other. Therefore, these plurality of embodiments contribute to solving different purposes or problems, and contribute to different effects.
[0030]
The plurality of embodiments shown below will be described with the 3GPP 5G system as the main target. However, these embodiments may be applied to other wireless communication systems.
[0031]
FIG. 1 shows a configuration example of a wireless communication network according to a plurality of embodiments including the present embodiment. In the example of FIG. 1, the wireless communication network includes a gNB Central Unit (gNB-CU) 1, a gNB Distributed Unit (gNB-DU) 2, and a wireless terminal (i.e., UE) 3. gNB-CU1 and gNB-DU2 are arranged in the Radio Access Network (RAN). The gNB-CU1 and each gNB-DU2 are connected by an interface 101. The interface 101 is an F1 interface. The gNB-CU1 may be connected to two or more gNB-DUs2. gNB-CU1 may be a logical node hosting gNB's RRC, SDAP, and PDCP protocols (or gNB's RRC and PDCP protocols). gNB-DU 2 may be a logical node hosting the RLC, MAC, and PHY layers of the gNB.
[0032]
GNB-CU1 and gNB-DU2 provide a primary cell (PCell) 10 and a secondary cell (SCell) 20 to UE3. UE3 communicates with gNB-CU1 and gNB-DU2 using carrier aggregation (CA) between the primary cell (PCell) 10 and the secondary cell (SCell) 20. UE3 may be connected to multiple base stations (i.e., Master gNB (MgNB) and Secondary gNB (SgNB)) simultaneously for dual connectivity. In this case, gNB-CU1 and gNB-DU2 in FIG. 1 may be MgNB CU and DU, or SgNB CU and DU. The PCell 10 and S Cell 20 in FIG. 1 may be PCell and SCell included in the Master Cell Group (MCG), or may be Primary SCG Cell (PSCell) and SCell included in the Secondary Cell Group (SCG). MCG's PCell and SCG's PSCell for dual connectivity are also called Special Cell (SpCell).
[0033]
As shown in FIG. 2, gNB-CU1 is a Control Plane (CP) Unit (ie, gNB-CU-CP) 11 and one or more User Plane (UP) Unit (ie, gNB-CU-UP). 12 may be included. In this case, the gNB-CU-CP11 is connected to the gNB-CU-UP12 via the control plane interface 201 (i.e., E1 interface). Further, the gNB-CU-CP11 is connected to the gNB-DU2 via the control plane interface 202 (i.e., F1-C interface). The gNB-CU-UP12 is connected to the gNB-DU2 via the user plane interface 203 (i.e., F1-U interface).
[0034]
FIG. 3 shows an example of the operation of gNB-CU1 and gNB-DU2 of the present embodiment. In step 301, gNB-CU1 sends a control message (i.e., F1 Application Protocol (F1AP) message) requesting the addition of SCell 20 to gNB-DU2. The control message may be a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message. The control message includes an information element (IE) indicating that the SCell 20 should be initially activated or dormant. In other words, when gNB-CU1 requests gNB-DU2 to add SCell 20, it indicates to gNB-DU2 that the SCell 20 to be added should be initially activated or dormant. The control message causes gNB-DU2 to activate or hibernate the SCell 20 after addition without deactivating it. Such behavior allows for a direct SCell state configuration in the gNB CU-DU split architecture.
[0035]
The information element indicating the initial state of SCell 20 may be, for example, SCell State IE. The information element may be included in the SCell to Be Setup Item IEs contained in the UE CONTEXT SETUP REQUEST message or the UE CONTEXT MODIFICATION REQUEST message. The gNB-CU1 may transmit the information element to the gNB-DU2 only when the initial state of the SCell 20 is the activated state or the dormant state. If the F1AP message requesting the addition of the SCell 20 does not contain the information element, gNB-DU2 does not specify the initial state of the SCell 20 or is allowed to deactivate the SCell 20 initially. You can think (consider). FIG. 4 shows an example of the format of the UE CONTEXT SETUP REQUEST message improved to include an information element (i.e., SCell State IE) indicating the initial state of the SCell 20.
[0036]
FIG. 5 shows an example of the operation of gNB-CU1 of the present embodiment. In step 501, gNB-CU1 determines the addition of SCell 20 for UE3 and further determines the initial state (i.e., Activated, Dormant, or Deactivated) of SCell 20 to be added. In step 502, gNB-CU1 requests the addition of SCell 20 and sends an F1AP message (e.g., UE CONTEXT SETUP REQUEST message or UE CONTEXT MODIFICATION REQUEST message) indicating the initial state of SCell 20 to gNB-DU2. The F1AP message may indicate that the initial state of the SCell 20 is the activated state or the dormant state. In other words, the F1AP message may indicate that the SCell 20 should not be initially (initially) deactivated.
[0037]
FIG. 6 shows an example of the operation of gNB-DU2 of this embodiment. In step 601 the gNB-DU2 requests the addition of the SCell 20 and receives an F1AP message indicating the initial state (activated state or dormant state) of the SCell 20 from the gNB-CU1. In step 602, gNB-DU2 sets SCell 20 in response to receiving the message. In addition, gNB-DU2 activates or hibernates the SCell 20 after addition without deactivating it.
[0038]
In some implementations, gNB-DU2 may send a response message to gNB-CU1. The response message may be an F1AP: UE CONTEXT SETUP RESPONSE message or an F1AP: UE CONTEXT MODIFICATION RESPONSE message. The gNB-DU2 may include an information element indicating the initial state of the added SCell 20 in the response message. The information element may be sCellState IE or may be included in CellGroupConfig IE. CellGroupConfig IE is included in the DU to CU RRC Information IE carried from gNB-DU2 to gNB-CU1 by the UE CONTEXT SETUP RESPONSE (or UE CONTEXT MODIFICATION RESPONSE) message.
[0039]
In some implementations, gNB-CU1 should receive an F1AP message containing assistance information from gNB-DU2 and the SCell 20 should initially be activated or hibernated based on the assistance information. May be determined. In other words, gNB-CU1 may determine that SCell 20 should not be initially (initially) deactivated. That is, the assistance information prompts gNB-CU1 to determine that the SCell 20 should be activated or dormant. The F1AP message carrying the assistance information may be a UE CONTEXT MODIFICATION REQUIRED message.
[0040]
Assistance information is not limited to, for example, but may include the following information. The assistance information may include information on the load status (e.g., cell load, radio resource usage, or number of active UEs) in the cell being used by UE3 as a serving cell. Further or instead, the assistance information may include usage (e.g., cell usage, cell utilization status) indicating how the UE 3 is using each serving cell. Further or instead, the assistance information may include information about the QoS satisfaction of UE3 (e.g., QoS performance, QoS satisfaction, or gap to required / expected QoS). Further or instead, the assistance information may include information about the characteristics expected by the UE 3 (e.g., expected / target data rate or throughput).
[0041]
The configuration example of the wireless communication network according to this embodiment is the same as the example shown in FIGS. 1 and 2. The present embodiment provides an example in which gNB-DU2 determines the initial state of the SCell 20 to be added.
[0042]
FIG. 7 shows an example of the operation of gNB-CU1 and gNB-DU2 of the present embodiment. In step 701, gNB-CU1 sends a control message (i.e., F1 Application Protocol (F1AP) message) requesting the addition of SCell 20 to gNB-DU2. The control message may be a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.
[0043]
In step 702, gNB-DU2 adds SCell 20 and determines the initial state (i.e., Activated, Dormant, or Deactivated) of SCell 20 in response to the reception of the message in step 701. For example, gNB-DU2 determines that the SCell 20 to be added is immediately activated or hibernated without being deactivated. Then, gNB-DU2 transmits a response message including an information element indicating the initial state of SCell 20 to gNB-CU1. The gNB-DU2 may transmit the information element to the gNB-CU1 only when the initial state of the SCell 20 is the activated state or the dormant state. In this case, when the message from gNB-DU2 does not include the information element, gNB-CU1 may consider that the initial state of SCell 20 is initially deactivated.
[0044]
The information element may be, for example, sCellState IE. The information element may be included in CellGroupConfig IE. CellGroupConfig IE is included in the DU to CU RRC Information IE carried from gNB-DU2 to gNB-CU1 by the UE CONTEXT SETUP RESPONSE (or UE CONTEXT MODIFICATION RESPONSE) message.
[0045]
When gNB-DU2 operates a plurality of SCell20s, gNB-DU2 includes an information element (eg, sCellState IE) indicating the initial state of SCell20 for each SCell20 in the response message and sends it to gNB-CU1. May be good. That is, the information element indicating the initial state of the SCell 20 described above may be a list of sCellState IE (sCellStateList IE).
[0 046]
The operation shown in FIG. 7 enables the direct SCell state configuration in the gNB CU-DU split architecture.
[0047]
In some implementations, gNB-CU1 may include assistance information in the message of step 701 to assist gNB-DU2 in determining the initial state of SCell 20. The gNB-DU2 may consider the assistance information to determine the initial state of the SCell 20 to be added. For example, the assistance information may indicate whether the addition of SCell 20 is urgent. When the assistance information indicates the additional urgency of the SCell 20, the gNB-DU2 may set the SCell 20 so that the initial state of the SCell 20 is the activated state or the dormant state.
[0048]
Further or instead, the assistance information may indicate the use or necessity (e.g., urgent, load balancing, or normal) of the SCell 20. Further or instead, the assistance information may indicate an additional purpose (e.g., load balancing, or throughput (improvement)) of the SCell 20.
[0049]
Further or instead, the assistance information may include information regarding the PDCP buffer of gNB-CU1 (e.g., PDCP buffer status, or PDCP buffer usage radio). The information may indicate the usage status (or load) of the PDCP buffer of gNB-CU1. In other words, the information may indicate that the PDCP buffer usage (or load) of gNB-CU1 is heavily loaded and therefore requires additional addition of SCell 20.
[0050]
FIG. 8 shows an example of the operation of gNB-CU1 of the present embodiment of the present embodiment. In step 801 the gNB-CU1 decides to add the SCell 20 for UE3 and sends an F1AP message requesting the addition of the SCell 20 to the gNB-DU2. The F1AP message may be, for example, a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message. In step 802, gNB-CU1 receives an F1AP message indicating the initial state of SCell 20 from gNB-DU2. The F1AP message may be, for example, a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message.
[0051]
FIG. 9 shows an example of the operation of gNB-DU2 of this embodiment. In step 901, gNB-DU2 receives an F1AP message requesting the addition of SCell 20 from gNB-CU1. In step 902, gNB-DU2 sets SCell 20 in response to receiving the message. Further, gNB-DU2 determines the initial state of the SCell 20 after the addition. For example, gNB-DU2 activates or hibernates SCell 20 after addition without deactivating it. In step 903, gNB-DU2 transmits an F1AP message (e.g., UE CONTEXT SETUP RESPONSE message or UE CONTEXT MODIFICATION RESPONSE message) indicating the initial state of SCell 20 to gNB-CU1.
[0052]
The configuration example of the wireless communication network according to this embodiment is the same as the example shown in FIGS. 1 and 2. In this embodiment, after SCell 20 has been added for UE3, gNB-CU1 changes the state of SCell 20 between activated, dormant, and deactivated states. Instruct or suggest to gNB-DU2 to do so. Such an operation allows the gNB-CU1 to control the current state of the SCell 20.
[0053]
FIG. 10 shows an example of the operation of gNB-CU1 and gNB-DU2 of the present embodiment. In step 1001, gNB-CU1 sends an F1AP message to gNB-DU2 instructing or proposing to change the state of SCell20. The F1AP message may be, for example, a UE CONTEXT MODIFICATION REQUEST message.
[0054]
In some implementations, gNB-CU1 may include an information element in the UE CONTEXT MODIFICATION REQUEST message to prompt gNB-DU2 to change the state of SCell20. The information element may be SCell State IE. The information element may be included in SCell to Be Modify Item IEs that are newly defined and included in the UE CONTEXT MODIFICATION REQUEST message.
[0055]
In some implementations, gNB-CU1 has one UE CONTEXT with both an information element indicating the removal of the SCell 20 and an information element indicating the setup of the SCell 20 in order to prompt the gNB-DU2 to change the state of the SCell 20. It may be included in the MODIFICATION REQUEST message. The information element indicating the removal of the SCell 20 may be SCell to Be Removed Item IEs, while the information element indicating the setup of the SCell 20 may be the SCell to Be Setup Item IEs. In this case, the SCell to Be Setup Item IEs may include an information element (e.g., SCell State IE) for indicating a change in the state of the SCell 20.
[0056]
In some implementations, gNB-CU1 may send a Cause indicating the purpose or background of the state change to gNB-DU2 in order to prompt gNB-DU2 to change the state of SCell20. The cause may be, for example, information indicating that UE3 is in an overheated state (i.e. overheating), or information indicating that the overheating state is to be eliminated. The gNB-CU1 may send the Cause to the gNB-DU2, for example, with instructions or suggestions to deactivate the SCell 20. Instead, gNB-CU1 decides to remove SCell20 from the settings for UE3 in response to receiving a report (eg, overheating assistance information) about overheating from UE3, and is an information element indicating the deletion of SCell20. You may also send the Cause to gNB-DU2.
[0057]
In some implementations, gNB-DU2 may send information related to UE3 activity associated with SCell 20 to gNB-CU1. Specifically, gNB-CU1 may send an F1AP message to gNB-DU2 that includes an information element indicating that the activity of UE3 may (or wants to be monitored) to be monitored. The F1AP message may be a UE CONTEXT SETUP REQUEST message (see FIG. 11) or a UE CONTEXT MODIFICATION REQUEST message (see FIG. 12). The messages shown in FIGS. 11 and 12 include an Inactivity Monitoring Request IE indicating whether the activity of UE3 may be monitored (or whether monitoring is requested). gNB-CU1 sets a value of "True" in Inactivity Monitoring Request IE when allowing (or requesting) monitoring of UE3 activity to gNB-DU2. The gNB-DU2 may send an F1AP: UE INACTIVITY NOTIFICATION message to the gNB-CU1. The activity information includes the communication status of UE3 in SCell 20 (or the status of the data radio bearer (DRB) of UE3, or the data communication status associated with the logical channel identifier (LCID)). Indicates whether it is active or not. The activity information may be referred to as non-activity information.
[0058]
The use of UE activity based on the data communication status associated with the LCID is effective, for example, in an implementation in which DRB data is transmitted or received only in a specific serving cell. More specifically, in some implementations, when UE3 sends the uplink data of a DRB, UE3 will have a specific serving cell pre-authorized by the RRC signaling of gNB (eg, gNB-CU1). Only the allowed Serving Cell) can send the uplink data. Similarly, the UE 3 can receive the downlink data only in a specific serving cell according to the judgment of gNB (e.g., gNB-DU2). This is the original logical channel (eg, LCID #) in the packet duplication (also called CA-type PDCP duplication) in which one PDCP packet (ie PDCP SDU) is duplicated and transmitted while performing carrier aggregation (CA). This is an indispensable technology for transmitting or receiving the data of 1) and the additional logical channel (eg, LCID # 2) for Packet duplication in different serving cells. In addition, the technique can be used with or without packet duplication. When the LCID is associated with a specific serving cell in this way, it is effective for gNB-DU2 to monitor the activity of the LCID and notify the information from gNB-DU2 to gNB-CU1 for SCell status management. Is.
[0059]
The gNB-CU1 may decide to change the state of the SCell 20 based on the received activity information. Specifically, when the activity information indicates that UE3 (or the DRB of UE3, or the logical channel) is not active, gNB-CU1 changes the state of SCell 20 from activated to dormant or activated to deactivated. You may decide to change to. FIG. 13 shows a specific example of the UE INACTIVITY NOTIFICATION message. In the example of FIG. 13, the SCell Activity List IE shows the activity (SCell Activity IE) of UE30 for each SCell.
[0060]
The configuration example of the wireless communication network according to this embodiment is the same as the example shown in FIGS. 1 and 2. In this embodiment, after SCell 20 has been added for UE3, gNB-DU2 changes the state of SCell 20 between activated, dormant, and deactivated states. do. At this time, gNB-DU2 may determine the state of SCell 20 based on the assistance information from gNB-CU1. Such an operation allows the gNB-DU2 to control the current state of the SCell 20. [0061]
FIG. 14 shows an example of the operation of gNB-CU1 and gNB-DU2 of the present embodiment. In step 1401, the gNB-CU1 sends an F1AP message to the gNB-DU2 that includes assistance information related to the change in the state of the SCell 20. The F1AP message may be, for example, a UE CONTEXT MODIFICATION REQUEST message.
[0062]
In some implementations, gNB-CU1 may include assistance information related to changing the state of SCell 20 in the UE CONTEXT MODIFICATION REQUEST message. The assistance information may be related to the load or state of UE3. The assistance information may be Overheating Assistance IE. Overheating Assistance IE may correspond to or relate to, for example, information (e.g., overheating assistance information) on the overheating problem reported by RRC signaling from UE3 to gNB (e.g., gNB-CU). Overheating Assistance IE may include information on recommended settings to eliminate heat generation problems (e.g., reduced UE Category, reduced Max CCs, reduced Max MIMO layers, or reduced Max active BWPs).
[0063]
The assistance information may be included in SCell to Be Modify Item IEs that is newly defined and included in the UE CONTEXT MODIFICATION REQUEST message. The gNB-DU2 may decide to change the state of the SCell 20 based on the assist information. For example, it may be determined to change the activated state SCell 20 to the dormant state or the deactivated state, and the UE 3 may be instructed to do so. Alternatively, it may be decided to delete SCell 20 and request or propose it to gNB-CU1. As a result, gNB-DU2 can manage the state of SCell 20 in consideration of the load or state of UE3.
[0064]
The configuration example of the wireless communication network according to this embodiment is the same as the example shown in FIGS. 1 and 2. In this embodiment, gNB-CU1 instructs or proposes to gNB-DU2 to activate two or more downlink BWPs among the plurality of BWPs set for SCell 20. The plurality of BWPs (i.e., BWP sets) set for SCell 20 may be DL BWPs or UL BWPs. gNB-DU2 may activate two or more downlink BWPs of SCell 20 based on instructions or suggestions from gNB-CU1. Such an operation allows the gNB-CU1 to control the number of active BWPs of the SCell 20.
[0065]
FIG. 15 shows an example of the operation of gNB-CU1 and gNB-DU2 of this embodiment. In step 1501, the gNB-CU1 sends an F1AP message to the gNB-DU2 instructing or proposing to the gNB-DU2 to activate two or more downlink BWPs of the SCell 20. In some implementations, gNB-CU1 includes an information element indicating the number of BWPs to be activated in the F1AP message (eg, UE CONTEXT SETUP REQUEST message or UE CONTEXT MODIFICATION REQUEST message) requesting the addition of SCell20. May be good. Further or instead, gNB-CU1 may include an information element indicating the number of BWPs activated in the F1AP message (e.g., UE CONTEXT MODIFICATION REQUEST message) requesting modification of UE CONTEXT.
[0066]
Subsequently, in the following, configuration examples of gNB-CU1 and gNB-DU2 according to the above-mentioned plurality of embodiments will be described. FIG. 16 is a block diagram showing a configuration example of gNB-CU1 according to the above-described embodiment. The configurations of gNB-CU-CP11 and gNB-CU-UP12 may be the same as those shown in FIG. Referring to FIG. 16, gNB-CU1 includes a network interface 1601, a processor 1602, and a memory 1603. The network interface 1601 is used to communicate with network nodes (e.g., gNB-DU2 and control pool (CP) and user plane (UP) nodes in 5GC). The network interface 1601 may include a plurality of interfaces. The network interface 1601 may include, for example, an optical fiber interface for CU-DU communication and a network interface compliant with the IEEE 802.3 series.
[0067]
Processor 1602 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Processor 1602 may include a plurality of processors. For example, the processor 1602 may include a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (eg, Central Processing Unit (CPU) or Micro Processing Unit (eg, Central Processing Unit (CPU)) that performs control plane processing. MPU)) may be included.
[0068]
Memory 1603 is composed of a combination of volatile memory and non-volatile memory. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. Non-volatile memory can be masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. The memory 1603 may include storage located away from the processor 1602. In this case, the processor 1602 may access the memory 1603 via the network interface 1601 or an I / O interface (not shown).
[0069]
The memory 1603 may store one or more software modules (computer programs) 1604 including instruction groups and data for performing processing by the gNB-CU1 described in the plurality of embodiments described above. In some implementations, processor 1602 may be configured to perform the processing of gNB-CU1 described in the embodiments described above by reading the software module 1604 from memory 1603 and executing it. good.
[0070]
FIG. 17 is a block diagram showing a configuration example of gNB-DU2 according to the above embodiment. Referring to FIG. 17, the gNB-DU2 includes a Radio Frequency transceiver 1701, a network interface 1703, a processor 1704, and a memory 1705. RF transceiver 1701 performs analog RF signal processing to communicate with NG UEs. The RF transceiver 1701 may include a plurality of transceivers. The RF transceiver 1701 is coupled with the antenna array 1702 and the processor 1704. The RF transceiver 1701 receives the modulation symbol data from the processor 1704, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 1702. Further, the RF transceiver 1701 generates a baseband reception signal based on the received RF signal received by the antenna array 1702, and supplies the baseband reception signal to the processor 1704. The RF transceiver 1701 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
[0071]
The network interface 1703 is used to communicate with network nodes (e.g., gNB-CU1, gNB-CU-CP11, gNB-CU-UP12). The network interface 1703 may include a plurality of interfaces. The network interface 1703 may include, for example, at least one of an optical fiber interface for CU-DU communication and an IEEE 802.3 series compliant network interface.
[0072]
The processor 1704 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The processor 1704 may include a plurality of processors. For example, the processor 1704 may include a modem processor (e.g., DSP) for digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) for control plane processing. Processor 1704 may include a digital beamformer module for beamforming. The digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and precoder.
[0073]
Memory 1705 is composed of a combination of volatile memory and non-volatile memory. Volatile memory is, for example, SRAM or DRAM or a combination thereof. Non-volatile memory can be MROM, EEPROM, flash memory, or a hard disk drive, or any combination thereof. The memory 1705 may include storage located away from the processor 1704. In this case, processor 1704 may access memory 1705 via network interface 1703 or an I / O interface (not shown).
[0074]
The memory 1705 may store one or more software modules (computer programs) 1706 containing the instruction group and data for performing the processing by the gNB-DU2 described in the plurality of embodiments described above. In some implementations, processor 1704 may be configured to perform the processing of gNB-DU2 described in the embodiments described above by reading the software module 1706 from memory 1705 and executing it. good.
[0075]
As described with reference to FIGS. 16 and 17, each of the processors included in the gNB-CU1 and gNB-DU2 according to the above-described embodiment is a group of instructions for causing a computer to perform the algorithm described with reference to the drawings. Execute one or more programs including. This program can be stored and supplied to a computer using various types of non-transitory computer readable medium. Non-temporary computer-readable media include various types of tangible storage media. Examples of non-temporary computer readable media are magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD- R, CD-R / W, semi-lead Includes body memory (eg, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)). The program may also be supplied to the computer by various types of transient computer readable medium. Examples of temporary computer readable media include electrical, optical, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
[0076]
The signaling between gNB-CU1 and gNB-DU2 described in the above embodiment may be performed between gNB-CU-CP11 and gNB-DU2.
[0077]
Although the above-described embodiment has been described assuming gNB-CU1 and gNB-DU2 in a 5G system, it can also be applied to other network configurations. For example, LTE eNB connected to 5GC is also called ng-eNB (or eLTE eNB), and like gNB, the functions of ng-eNB are CU (ie, ng-eNB-CU) and DU (ie, ng-eNB). -It is expected to be distributed to DU). The same or similar signaling as the signaling in the F1 interface between gNB-CU1 and gNB-DU2 described in the embodiments described above is the interface between ng-eNB-CU and ng-eNB-DU (eg, W1 interface). ) May be done.
[0078]
Furthermore, the above-described embodiment is merely an example relating to the application of the technical idea obtained by the inventor of the present invention. That is, the technical idea is not limited to the above-described embodiment, and it goes without saying that various changes can be made.
[0079]
For example, some or all of the above embodiments may be described as in the following appendix, but are not limited to the following.
[0080] [0080]
(Appendix 1)
It is a distributed unit of base stations
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
Received the first message requesting the addition of a carrier aggregation secondary cell from the central unit of the base station,
In response to the first message, the secondary cell was initially determined to be activated or hibernated.
Send a second message to the central unit indicating that the secondary cell is initially activated or hibernated.
Is configured as
Distributed unit.
[0081]
(Appendix 2)
The first message includes assistance information indicating whether or not the addition of the secondary cell is urgent.
Dispersion unit according to Appendix 1.
[0082]
(Appendix 3)
The first message includes assistance information regarding the additional purpose of the secondary cell.
Dispersion unit according to Appendix 1.
[0083]
(Appendix 4)
It is the central unit of the base station
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
A first message requesting the addition of a carrier aggregation secondary cell was sent to the distributed unit of the base station,
Receive a second message from the distributed unit indicating that the secondary cell is initially activated or hibernated.
Is configured as
Central unit.
[0084]
(Appendix 5)
The first message includes assistance information indicating whether or not the addition of the secondary cell is urgent.
The central unit described in Appendix 4.
[0085]
(Appendix 6)
The first message includes assistance information regarding the additional purpose of the secondary cell.
The central unit described in Appendix 4.
[0086]
(Appendix 7)
It is the central unit of the base station
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
It is configured to send a first message instructing or proposing to change the state of the secondary cell of carrier aggregation or deleting the secondary cell to the distributed unit of the base station.
Central unit.
[0087]
(Appendix 8)
The first message includes cause information indicating the purpose of changing or deleting the state of the secondary cell.
The central unit described in Appendix 7.
[0088]
(Appendix 9)
The cause information indicates that the wireless terminal associated with the secondary cell is in an overheated state, or is for eliminating the overheated state of the wireless terminal.
The central unit described in Appendix 8.
[0089]
(Appendix 10)
The at least one processor is configured to receive activity information related to the activity of the wireless terminal associated with the secondary cell from the distributed unit.
The central unit according to any one of Supplementary Provisions 7 to 9.
[0090]
(Appendix 11)
The activity information indicates the activity of the wireless terminal in each of the plurality of secondary cells activated for the wireless terminal.
The central unit according to Appendix 10.
[0091]
(Appendix 12)
The at least one processor is configured to determine the state change or deletion of the secondary cell based on the activity information.
The central unit according to Appendix 10 or 11.
[0092]
(Appendix 13)
It is a distributed unit of base stations
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
A first message instructing or proposing to change the state of the secondary cell of carrier aggregation or deleting the secondary cell is configured to be received from the central unit of the base station.
Distributed unit.
[0093]
(Appendix 14)
It is a distributed unit of base stations
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
Assistance information related to changing or deleting the state of the secondary cell of carrier aggregation is configured to be received from the central unit of the base station.
Distributed unit.
[0094]
(Appendix 15)
The at least one processor is configured to determine the state change or deletion of the secondary cell based on the assistance information.
The dispersion unit according to Appendix 14.
[0095]
(Appendix 16)
The assistance information indicates the load or status of the wireless terminal associated with the secondary cell.
Dispersion unit according to Appendix 14 or 15.
[0096]
(Appendix 17)
It is the central unit of the base station
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
Assistance information related to changing or deleting the state of the secondary cell of carrier aggregation is configured to be transmitted to the distributed unit of the base station.
Central unit.
[0097]
(Appendix 18)
It is the central unit of the base station
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
It is configured to send a message instructing or proposing to activate two or more of the plurality of bandwidth parts (BWPs) set for the carrier aggregation secondary cell to the distributed unit of the base station.
Central unit.
[0098]
(Appendix 19)
It is a distributed unit of base stations
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is
It is configured to receive a message from the central unit of the base station instructing or proposing to activate two or more of the plurality of bandwidth parts (BWPs) set for the carrier aggregation secondary cell.
Distributed unit.
[0099]
(Appendix B1)
It is the central unit of the base station
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is configured to send a first message requesting the addition of a carrier aggregation secondary cell to the distributed unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Central unit.
[0100]
(Appendix B2)
The first information element prompts the dispersion unit to activate or hibernate the secondary cell after the addition without deactivating it.
The central unit described in Appendix B1.
[0101]
(Appendix B3)
The at least one processor is configured to receive a second message containing assistance information from the distribution unit and determine based on the assistance information that the secondary cell should be activated or dormant. Be done,
The central unit according to Appendix B1 or B2.
[0102]
(Appendix B4)
The at least one processor further sends a third message to the distributed unit to instruct or propose to change the state of the secondary cell between active, hibernate, and deactivated states. Is configured to be sent to the distribution unit after the addition of
The central unit according to any one of the appendices B1 to B3.
[0103]
(Appendix B5)
The at least one processor is further configured to receive activity information of the wireless terminal associated with the secondary cell from the distributed unit and determine a change in the state of the secondary cell based on the activity information.
The central unit described in Appendix B4.
[0104]
(Appendix B6)
The first message further comprises a second information element instructing or suggesting to the distribution unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. ,
The central unit according to any one of the appendices B1 to B5.
[0105]
(Appendix B7)
The at least one processor further directs or proposes a fourth message to the distributed unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. Configured to send to said distribution unit,
The central unit according to any one of the appendices B1 to B5.
[0106]
(Appendix B8)
It is a distributed unit of base stations
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is configured to receive a first message requesting the addition of a carrier aggregation secondary cell from the central unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Distributed unit.
[0107]
(Appendix B9)
The at least one processor further responds to the reception of the first information element after the addition. The secondary cell of the above is configured to be activated or hibernated without being deactivated.
Dispersion unit according to Appendix B8.
[0108]
(Appendix B10)
The at least one processor is configured to send a second message containing assistance information to the central unit.
The assistance information prompts the central unit to determine that the secondary cell should be activated or dormant.
The dispersion unit according to Appendix B8 or B9.
[0109]
(Appendix B11)
The at least one processor further sends a third message to the distributed unit to instruct or propose to change the state of the secondary cell between active, hibernate, and deactivated states. Configured to receive from said central unit after addition of
The dispersion unit according to any one of Supplementary note B8 to B10.
[0110]
(Appendix B12)
The at least one processor is configured to change the state of the secondary cell according to the third message.
The dispersion unit according to Appendix B11.
[0111]
(Appendix B13)
The first message further comprises a second information element instructing or suggesting to the distribution unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. ,
The dispersion unit according to any one of Supplementary note B8 to B12.
[0112]
(Appendix B14)
The at least one processor further directs or proposes a fourth message to the distributed unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. Configured to receive from said central unit,
The dispersion unit according to any one of Supplementary note B8 to B13.
[0113]
(Appendix B15)
It is a method in the central unit of the base station,
A first message requesting the addition of a carrier aggregation secondary cell is provided to the distributed unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Method.
[0114]
(Appendix B16)
It is a method in the distributed unit of the base station,
A first message requesting the addition of a carrier aggregation secondary cell is provided from the central unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Method.
[0115]
(Appendix B17)
It is a program to make a computer perform the method in the central unit of the base station.
The method comprises sending a first message requesting the addition of a carrier aggregation secondary cell to the distributed unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
program.
[0116]
(Appendix B18)
It is a program to make a computer perform the method in the distributed unit of the base station.
The method comprises receiving a first message requesting the addition of a carrier aggregation secondary cell from the central unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
program.
[0117]
This application claims priority on the basis of Japanese application Japanese Patent Application No. 2018-207415 filed on November 2, 2018, and incorporates all of its disclosures herein.
Description of the sign
[0118]
1 gNB-CU
2 gNB-DU
3 UE
11 gNB-CU-CP
12 gNB-CU-UP
1602 processor
1603 memory
1604 modules
1704 processor
1705 memory
1706 modules
The scope of the claims
[Claim 1]
It is the central unit of the base station
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is configured to send a first message requesting the addition of a carrier aggregation secondary cell to the distributed unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Central unit.
[Claim 2]
The first information element prompts the dispersion unit to activate or hibernate the secondary cell after the addition without deactivating it.
The central unit according to claim 1.
[Claim 3]
The at least one processor is configured to receive a second message containing assistance information from the distribution unit and determine based on the assistance information that the secondary cell should be activated or dormant. Be done,
The central unit according to claim 1 or 2.
[Claim 4]
The at least one processor further sends a third message to the distributed unit to instruct or propose to change the state of the secondary cell between active, hibernate, and deactivated states. Is configured to be sent to the distribution unit after the addition of
The central unit according to any one of claims 1 to 3.
[Claim 5]
The at least one processor is further configured to receive activity information of the wireless terminal associated with the secondary cell from the distributed unit and determine a change in the state of the secondary cell based on the activity information.
The central unit according to claim 4.
[Claim 6]
The first message further comprises a second information element instructing or suggesting to the distribution unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. ,
The central unit according to any one of claims 1 to 5.
[Claim 7]
The at least one processor further directs or proposes a fourth message to the distributed unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. Configured to send to said distribution unit,
The central unit according to any one of claims 1 to 5.
[Claim 8]
It is a distributed unit of base stations
At least one memory and
With at least one processor coupled to the at least one memory,
Equipped with
The at least one processor is configured to receive a first message requesting the addition of a carrier aggregation secondary cell from the central unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Distributed unit.
[Claim 9]
The at least one processor is further configured to activate or hibernate the secondary cell after the addition in response to the reception of the first information element, without deactivating it. Ru,
The distributed unit according to claim 8.
[Claim 10]
The at least one processor is configured to send a second message containing assistance information to the central unit.
The assistance information prompts the central unit to determine that the secondary cell should be activated or dormant.
The dispersion unit according to claim 8 or 9.
[Claim 11]
The at least one processor further sends a third message to the distributed unit to instruct or propose to change the state of the secondary cell between active, hibernate, and deactivated states. Configured to receive from said central unit after addition of
The distribution unit according to any one of claims 8 to 10.
[Claim 12]
The at least one processor is configured to change the state of the secondary cell according to the third message.
The distributed unit according to claim 11.
[Claim 13]
The first message further comprises a second information element instructing or suggesting to the distribution unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. ,
The distribution unit according to any one of claims 8 to 12.
[Claim 14]
The at least one processor further directs or proposes a fourth message to the distributed unit to activate two or more downlink BWPs out of a plurality of downlink bandwidth parts (BWPs) in the secondary cell. Configured to receive from said central unit,
The distribution unit according to any one of claims 8 to 13.
[Claim 15]
It is a method in the central unit of the base station,
A first message requesting the addition of a carrier aggregation secondary cell is provided to the distributed unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Method.
[Claim 16]
It is a method in the distributed unit of the base station,
A first message requesting the addition of a carrier aggregation secondary cell is provided from the central unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Method.
[Claim 17]
A non-temporary computer-readable medium containing a program that allows a computer to perform the method in the central unit of a base station.
The method comprises sending a first message requesting the addition of a carrier aggregation secondary cell to the distributed unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Non-temporary computer readable medium.
[Claim 18]
It is a non-temporary computer-readable medium that stores a program for making a computer perform the method in the distributed unit of a base station.
The method comprises receiving a first message requesting the addition of a carrier aggregation secondary cell from the central unit of the base station.
The first message includes a first information element indicating that the secondary cell should be initially activated or dormant.
Non-temporary computer readable medium.
| # | Name | Date |
|---|---|---|
| 1 | 202117019338-TRANSLATIOIN OF PRIOIRTY DOCUMENTS ETC. [27-04-2021(online)].pdf | 2021-04-27 |
| 2 | 202117019338-STATEMENT OF UNDERTAKING (FORM 3) [27-04-2021(online)].pdf | 2021-04-27 |
| 3 | 202117019338-REQUEST FOR EXAMINATION (FORM-18) [27-04-2021(online)].pdf | 2021-04-27 |
| 4 | 202117019338-PRIORITY DOCUMENTS [27-04-2021(online)].pdf | 2021-04-27 |
| 5 | 202117019338-POWER OF AUTHORITY [27-04-2021(online)].pdf | 2021-04-27 |
| 6 | 202117019338-NOTIFICATION OF INT. APPLN. NO. & FILING DATE (PCT-RO-105) [27-04-2021(online)].pdf | 2021-04-27 |
| 7 | 202117019338-FORM 18 [27-04-2021(online)].pdf | 2021-04-27 |
| 8 | 202117019338-FORM 1 [27-04-2021(online)].pdf | 2021-04-27 |
| 9 | 202117019338-DRAWINGS [27-04-2021(online)].pdf | 2021-04-27 |
| 10 | 202117019338-DECLARATION OF INVENTORSHIP (FORM 5) [27-04-2021(online)].pdf | 2021-04-27 |
| 11 | 202117019338-COMPLETE SPECIFICATION [27-04-2021(online)].pdf | 2021-04-27 |
| 12 | 202117019338-CLAIMS UNDER RULE 1 (PROVISIO) OF RULE 20 [27-04-2021(online)].pdf | 2021-04-27 |
| 13 | 202117019338.pdf | 2021-10-19 |
| 14 | 202117019338-FORM 3 [19-10-2021(online)].pdf | 2021-10-19 |
| 15 | 202117019338-FER.pdf | 2022-02-11 |
| 16 | 202117019338-Proof of Right [22-06-2022(online)].pdf | 2022-06-22 |
| 17 | 202117019338-PETITION UNDER RULE 137 [22-06-2022(online)].pdf | 2022-06-22 |
| 18 | 202117019338-OTHERS [22-06-2022(online)].pdf | 2022-06-22 |
| 19 | 202117019338-FORM 3 [22-06-2022(online)].pdf | 2022-06-22 |
| 20 | 202117019338-FER_SER_REPLY [22-06-2022(online)].pdf | 2022-06-22 |
| 21 | 202117019338-DRAWING [22-06-2022(online)].pdf | 2022-06-22 |
| 22 | 202117019338-COMPLETE SPECIFICATION [22-06-2022(online)].pdf | 2022-06-22 |
| 23 | 202117019338-CLAIMS [22-06-2022(online)].pdf | 2022-06-22 |
| 24 | 202117019338-Others-010922.pdf | 2022-09-09 |
| 25 | 202117019338-Correspondence-010922.pdf | 2022-09-09 |
| 26 | 202117019338-FORM 3 [06-03-2023(online)].pdf | 2023-03-06 |
| 27 | 202117019338-PatentCertificate29-02-2024.pdf | 2024-02-29 |
| 28 | 202117019338-IntimationOfGrant29-02-2024.pdf | 2024-02-29 |
| 1 | SearchHistory(11)(1)E_04-02-2022.pdf |