Control device and communication method

Abstract

This control device performs carrier aggregation between other control devices, the control device comprising: a control unit that sets an interface for performing the carrier aggregation; and a transmission unit that transmits, to the other control devices, first information for performing at least one of addition and deletion of a secondary cell in the interface.

Description

Control Device and Communication Method

[0001] The present invention relates to a control device and a communication method in a wireless communication system.

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), standardization of technologies for further increasing system capacity, further increasing data transmission speed, and further reducing latency in the radio section is being carried out (for example, Non-Patent Document 1 and Non-Patent Document 2).

[0003] Also, in the O-RAN Alliance (Registered Trademark) (Open Radio Access Network Alliance), based on the above technologies, standardization of technologies for realizing a flexible network architecture to ensure interoperability between different vendors (multi-vendor) is being carried out (for example, Non-Patent Document 3).

[0004] 3GPP TS 38.401 V18.3.0 (2024-09) 3GPP TS 38.473 V18.3.0 (2024-09) O-RAN.WG1.OAD-R003-v12.00

[0005] Currently, in O-RAN (Registered Trademark), in order to support carrier aggregation (CA) (Inter O-DU CA) between multi-vendor O-RAN distributed units (O-DU: O-RAN Distributed Unit), it is being discussed to newly formulate an interface.

[0006] However, in the above interface, procedures such as what messages are exchanged between O-DUs and how settings are made have not been discussed. If the procedures between O-DUs for realizing Inter O-DU CA are not properly carried out, Inter O-DU CA cannot be realized, and there is a risk that the user experience will deteriorate due to unstable terminal connection.

[0007] The present invention has been made in view of the above problems, and an object thereof is to appropriately perform carrier aggregation between DUs.

[0008] The disclosed technology provides a control device for performing carrier aggregation between other control devices, the control device comprising: a control unit that sets up an interface for performing the carrier aggregation; and a transmission unit that transmits first information to the other control devices for adding or deleting secondary cells at the interface.

[0009] According to the disclosed technology, carrier aggregation between DUs can be performed appropriately.

[0010] Figure 1 is a diagram (1) showing an example of the configuration of a wireless communication system. Figure 2 is a diagram (2) showing an example of the configuration of a wireless communication system. Figure 3 is a diagram showing an example of the configuration of the O-RAN system architecture. Figure 4 is an example of a sequence diagram related to messages for setting up / resetting the D2 interface. Figure 5 is an example of a sequence diagram related to messages for adding an SCell. Figure 6 is an example of a sequence diagram related to messages for deleting an SCell. Figure 7 is an example of a sequence diagram related to messages for changing the settings related to an SCell. Figure 8 is an example of a sequence diagram related to messages for reconfiguring an SCell. Figure 9 is an example of a sequence diagram related to messages for releasing SCell resources in Inter O-DU CA. Figure 10 is an example of a sequence diagram related to messages for updating DU settings. Figure 11 is an example of a sequence diagram related to messages for reporting load information. Figure 12 is an example of a sequence diagram related to messages for passing backlogged data. Figure 13 is an example of a sequence diagram related to messages for indicating data delivery status. Figure 14 is a diagram showing an example of the functional configuration of a base station. Figure 15 shows an example of the functional configuration of a terminal. Figure 16 shows an example of the hardware configuration of a base station and a terminal. Figure 17 shows an example of the configuration of a vehicle.

[0011] Embodiments of the present invention will be described below with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the embodiments described below.

[0012] In the following explanation, " / " means "and / or" unless otherwise specified, or unless the context makes it clear that it has a different meaning.

[0013] In the operation of the wireless communication system of this embodiment, existing technologies will be used as appropriate. However, such existing technologies include, for example, existing LTE (Long Term Evolution), but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (for example, NR (New Radio)), unless otherwise specified.

[0014] In the embodiments described below, terms such as Synchronization Signal (SS), Primary SS (PSS), Secondary SS (SSS), Physical Broadcast Channel (PBCH), Physical Random Access Channel (PRACH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), and Physical Uplink Shared Channel (PUSCH), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. The above terms in NR may also be called SS, PSS, SSS, PBCH, PRACH, etc., without any particular distinction from LTE.

[0015] In this embodiment, the duplexing scheme may be a time division duplex (TDD) scheme, a frequency division duplex (FDD) scheme, or any other scheme (for example, a flexible duplex).

[0016] In this embodiment, "configuring" wireless parameters means either pre-configuring predetermined values, or configuring wireless parameters notified by a base station or terminal.

[0017] In this embodiment, the core network is referred to as a 5G core, but this is for convenience of description and is not limited to 5G. For example, the 5G core may be a 6G core.

[0018] In this embodiment, for example, the terms O-CU, CU, and gNB-CU may be used interchangeably. Similarly, for DU and RU, the terms O-DU, DU, and gNB-DU may be used interchangeably, and the terms O-RU, RU, and gNB-RU may be used interchangeably.

[0019] <System Configuration> <Wireless Communication System> Figure 1 is a diagram (1) showing an example of the configuration of a wireless communication system.

[0020] The wireless communication system in this embodiment includes a base station 10 and a terminal 20. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple of each.

[0021] The base station 10 is a communication device that provides one or more cells and communicates wirelessly with the terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain, the time domain may be defined by the number of orthogonal frequency division multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks.

[0022] The base station 10 transmits synchronization signals (SS) and system information (SI) to the terminal 20. SS are, for example, PSS and SSS. SI is transmitted, for example, via PBCH or PDSCH, and is also called broadcast information. SS and SI may also be referred to as a synchronization signal block (SSB: SS / PBCH Block).

[0023] Base station 10 transmits control signals or data to terminal 20 on the downlink (DL) and receives control signals or data from terminal 20 on the uplink (UL). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Both base station 10 and terminal 20 are also capable of applying Multiple Input Multiple Output (MIMO) communication to DL or UL. Furthermore, both base station 10 and terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using carrier aggregation (CA). In addition, terminal 20 may communicate via the PCell of base station 10 and the primary secondary cell group cell (PSCell) of other base stations 10 using dual connectivity (DC).

[0024] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. Terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from base station 10 and performs propagation path (channel) quality measurement based on the reception results of said reference signals.

[0025] Figure 2 is a diagram (2) showing an example of the configuration of a wireless communication system.

[0026] Terminal 20 communicates with base stations 10a and 10b provided by the NR system (hereinafter, when base stations 10a and 10b are not distinguished, they may be referred to as "base station 10"). Furthermore, terminal 20 supports NR-NR dual connectivity, i.e., NR-DC, where base station 10a is the master node (MN) and base station 10b is the secondary node (SN). Terminal 20 can simultaneously transmit or receive with base station 10a (MN) and base station 10b (SN) by simultaneously utilizing multiple component carriers (CCs) provided by base station 10a (MN) and base station 10b (SN).

[0027] Terminal 20 may communicate with base station 10a provided by the LTE system and base station 10b provided by the NR system. Furthermore, terminal 20 may support LTE-NR dual connectivity, i.e., EN-DC, where base station 10a is the MN and base station 10b is the SN. Terminal 20 can simultaneously transmit or receive with base station 10a (MN) and base station 10b (SN) by simultaneously utilizing multiple CCs provided by base station 10a (MN) and base station 10b (SN).

[0028] Terminal 20 may communicate with base station 10a provided by the NR system and base station 10b provided by the LTE system. Furthermore, terminal 20 may support NR-LTE dual connectivity, i.e., NE (NR-E-UTRA (Evolved Universal Terrestrial Radio Access Network))-DC, where base station 10a is the MN and base station 10b is the SN. Terminal 20 can simultaneously transmit or receive with base station 10a (MN) and base station 10b (SN) by simultaneously utilizing multiple CCs provided by base station 10a (MN) and base station 10b (SN).

[0029] Terminal 20 may communicate with base station 10a and base station 10b provided by the NR system. Furthermore, terminal 20 may support NR-NR dual connectivity, i.e., NR-DC, where base station 10a is the MN and base station 10b is the SN. Terminal 20 can simultaneously transmit or receive with base station 10a (MN) and base station 10b (SN) by simultaneously utilizing multiple CCs provided by base station 10a (MN) and base station 10b (SN).

[0030] Terminal 20 may perform communication using one serving cell, or it may perform communication using multiple serving cells (for example, CA or DC). The processing operation in this embodiment may be performed with the system configuration shown in Figure 1, the system configuration shown in Figure 2, or any other system configuration.

[0031] ≪O-RAN System≫ Figure 3 shows an example of the configuration of the O-RAN system architecture.

[0032] The O-RAN system architecture includes an O-RAN central base station (O-CU10A), an O-RAN distributed station (O-DU10B), and an O-RAN radio unit (O-RU10C). The base station 10, described later, may also include the O-CU10A, O-DU10B, and O-RU10C.

[0033] The O-CU10A includes the O-CU-CP (Control Plane) and O-CU-UP (User Plane), and performs overall network control and user data management. Although not shown in Figure 3, the O-CU10A is connected to the 5G core via the NG interface. The O-CU10A is also connected to the O-DU10B shown below via the F1 interface.

[0034] The O-DU10B is responsible for managing radio resources and performing base station functions, including data transmission and control relay. The O-DU10B is connected to the O-CU10A via the F1 interface and to the O-RU10C shown below via the Open FH (Open Fronthaul) interface. The O-DU10B also transmits and receives user data with other O-DU10B units via the D2-U (User plane) interface and transmits and receives control information with other O-DU10B units via the D2-C (Control plane) interface.

[0035] The O-RU10C is responsible for transmitting and receiving wireless signals and communicates wirelessly with terminal 20. The O-RU10C is connected to the O-DU10B via the Open FH interface.

[0036] It is considered insufficient to simply establish a D2 interface between O-DUs in order to perform Inter O-DU CA. The newly established D2 interface will require at least the following: D2 interface configuration, SCell configuration, reconnection during CA, and message transmission and reception related to transferred data.

[0037] However, details regarding the sending and receiving of messages in the D2 interface have not yet been discussed. If the necessary procedures between O-DUs for Inter O-DU CA are not properly performed, Inter O-DU CA cannot be realized. This could lead to an unstable connection between terminal 20 and base station 10, potentially preventing users from obtaining sufficient communication speeds and degrading the user experience.

[0038] Therefore, a specific example of this embodiment relating to the detailed procedure for properly performing Inter O-DU CA will be described. In the following example, assuming that various situations within each node are notified between DUs using the interface in the network, the content of such notification will be explained with diagrams. In the following example, the PCell side is the master DU (DU#1), and the SCell side is the secondary DU (DU#2). Note that the secondary DU is not limited to DU#2, but may be multiple (DU#2, DU#3, ..., DU#n).

[0039] <Specific Examples> <Specific Example 1> Messages for setting up the D2 interface may be sent and received in order to exchange application-level configuration data necessary for two DUs to properly interoperate on the D2-C interface. In addition, messages for resetting the D2 interface may be sent and received in order to reset the configured D2 interface environment.

[0040] Figure 4 is an example of a sequence diagram related to messages for setting up / resetting the D2 interface.

[0041] For the setup of the D2 interface, in step S101, O-DU10B1, which is DU#1, may send a D2 SETUP REQUEST message to O-DU10B2, which is DU#2. The D2 SETUP REQUEST message may include a Served Cells List IE (Information Element), which is a list of serving cells.

[0042] After receiving the D2 SETUP REQUEST message, in step S102, O-DU10B2, which is DU#2, may send a D2 SETUP RESPONSE message to O-DU10B1, which is DU#1. The D2 SETUP RESPONSE message may include a Served Cells List IE (Information Element), which is a list of serving cells.

[0043] For resetting the D2 interface, in step S103, O-DU10B1 which is DU#1 may send a D2 RESET REQUEST message to O-DU10B2 which is DU#2. Note that the D2 RESET REQUEST message may include a Served Cells List IE (Information Element) which is a list of serving cells.

[0044] After receiving the D2 RESET REQUEST message, in step S104, O-DU10B2 which is DU#2 may send a D2 RESET ACKNOWLEDGE message to O-DU10B1 which is DU#1. Note that the D2 RESET ACKNOWLEDGE message may include a Served Cells List IE (Information Element) which is a list of serving cells.

[0045] As described above, necessary setting information can be efficiently transmitted and received between O-DUs by messages for setting up the D2 interface, and a quick connection can be established. Also, by messages for resetting the D2 interface, the state between O-DUs can be reset at the time of failure occurrence, setting change, etc., thereby improving the reliability of the system.

[0046] ≪Specific Example 2≫ For performing Inter O-DU CA between two DUs, messages for setting up addition / release of SCell may be transmitted and received. In this specific example, it is assumed that O-DU10B2 which is DU#2 is added / removed as an SCell for O-CU10A1 which is CU#1 and O-DU10B1 which is DU#1. More specifically, it is assumed that O-DU10B1 (DU#1) which is the master DU having a PCell basically has all cells, and O-CU10A1 (CU#1) causes cells in O-DU10B2 (DU#2) which is the secondary DU to be added / removed via O-DU10B1 (DU#1) which is the master DU. Note that it is also assumed that the setup of the F1 interface has been performed for all O-DU10Bs.

[0047] In the following specific examples, the term "Release" may be used interchangeably with "liberation".

[0048] <<Specific Example 2-1>> Messages for setting data necessary for adding an SCell may be transmitted and received. The message may include SCell to Be Setup Item IEs including items related to the SCell to be set up. The SCell to Be Setup Item IEs may include an SCell ID (Identification) / SCellIndex / SCell UL Configured / servingCellMO (Measurement Object), etc.

[0049] FIG. 5 is an example of a sequence diagram related to a message for adding an SCell.

[0050] In step S201, it is assumed that an opportunity to add an SCell occurs at O-CU10A1 (CU#1).

[0051] In step S202, O-DU10B1 (DU#1) receives a Measurement Report indicating the received signal quality from the terminal 20.

[0052] In step S203, O-DU10B1 (DU#1) transmits a UL RRC Message Transfer message to O-CU10A1 (CU#1) in order to convey the received Measurement Report message, etc.

[0053] In step S204, O-CU10A1 (CU#1) transmits a UE Context Modification Request message to O-DU10B1 (DU#1) in order to convey information related to adding an SCell, etc.

[0054] In step S205, O-DU10B1 (DU#1) transmits an SCell Addition Request message to O-DU10B2 (DU#2) in order to add O-DU10B2 (DU#2).

[0055] In step S206, O-DU10B2 (DU#2) sends a SCell Addition Request Acknowledge message, which is an acknowledgment of the SCell Addition Request message, to O-DU10B1 (DU#1).

[0056] In step S207, O-DU10B1 (DU#1) sends a UE Context Modification Response message containing full configuration information to O-CU10A1 (CU#1).

[0057] In step S208, O-CU10A1 (CU#1) sends a DL RRC Message Transfer message to O-DU10B1 (DU#1) to convey information related to the addition of SCell.

[0058] In step S209, O-DU10B1 (DU#1) sends an RRC Reconfiguration message to terminal 20 in order to perform settings related to the addition of SCell.

[0059] In step S210, terminal 20 sends an RRC Reconfiguration Complete message to O-DU10B1 (DU#1).

[0060] In step S211, O-DU10B1 (DU#1) sends a UL RRC Message Transfer message to O-CU10A1 (CU#1) to convey the received RRC Reconfiguration Complete message.

[0061] In step S212, O-CU10A1 (CU#1) sends a UE Context Modification Request message to O-DU10B1 (DU#1) to convey information related to the addition of SCell.

[0062] In step S213, O-DU10B1 (DU#1) sends a UE Context Modification Response message containing full configuration information to O-CU10A1 (CU#1).

[0063] In step S214, O-DU10B1 (DU#1) sends a SCell Reconfiguration Complete message to O-DU10B2 (DU#2) to indicate that the SCell addition is complete.

[0064] In step S215, terminal 20 performs a random access procedure with O-DU10B2 (DU#2) to initiate a connection to the added SCell.

[0065] As described above, by adding DU#2 on the SCell side via a message for adding SCell, it becomes possible to properly perform the processing related to Inter O-DU CA.

[0066] ≪Specific Example 2-2≫ Messages may be sent and received to set the data necessary to delete an SCell. Such messages may include an SCell to Be Removed List IE containing items related to the SCell to be deleted. The SCell to Be Removed List IE may include the SCell ID, etc.

[0067] Figure 6 is an example of a sequence diagram related to messages for SCell deletion.

[0068] In step S301, the trigger for deleting SCell occurred in O-CU10A1 (CU#1).

[0069] In step S302, O-CU10A1 (CU#1) sends a UE Context Modification Request message to O-DU10B1 (DU#1) to convey information related to SCell deletion.

[0070] In step S303, O-DU10B1 (DU#1) sends a SCell Release Request message to O-DU10B2 (DU#2) in order to delete O-DU10B2 (DU#2) on the SCell side.

[0071] In step S304, O-DU10B2 (DU#2) sends a SCell Release Request Acknowledge message, which is an acknowledgment of the SCell Release Request message, to O-DU10B1 (DU#1).

[0072] In step S305, O-DU10B1 (DU#1) sends a UE Context Modification Response message containing full configuration information to O-CU10A1 (CU#1).

[0073] In step S306, O-CU10A1 (CU#1) sends a DL RRC Message Transfer message to O-DU10B1 (DU#1) to convey information related to SCell deletion.

[0074] In step S307, O-DU10B1 (DU#1) sends an RRC Reconfiguration message to terminal 20 in order to perform settings related to SCell deletion.

[0075] In step S308, terminal 20 sends an RRC Reconfiguration Complete message to O-DU10B1 (DU#1).

[0076] In step S309, O-DU10B1 (DU#1) sends a UL RRC Message Transfer message to O-CU10A1 (CU#1) to convey the received RRC Reconfiguration Complete message.

[0077] In step S310, O-CU10A1 (CU#1) sends a UE Context Modification Request message to O-DU10B1 (DU#1) to convey information related to SCell deletion.

[0078] In step S311, O-DU10B1 (DU#1) sends a UE Context Modification Response message to O-CU10A1 (CU#1) that includes full configuration information, including information related to the deletion of SCell.

[0079] As described above, by deleting DU#2 on the SCell side using a message for SCell deletion, it becomes possible to properly perform the processing related to Inter O-DU CA.

[0080] ≪Specific Example 3≫ When performing Inter O-DU CA between two DUs, messages for various SCell-related setting changes (Modifications) may be sent and received. These messages may include the SCell to Be Setup Item IEs and SCell to Be Removed List IEs mentioned above. In addition, one or more of the following settings may be changed by these messages.

[0081] • Security Key • UL Configuration • PDU (Packet Data Unit) Session (QoS (Quality of Service) Flow, 5QI (QoS Identifier)) • UE AMBR (Aggregate Maximum Bit Rate) UL • DRX (Discontinuous Reception) Cycle • Measurement GAP related

[0082] In the specific examples described above and thereafter, the term "modification" may be used interchangeably with "correction" and "update," and may also encompass the meanings of "addition," "deletion," and "release."

[0083] Figure 7 is an example of a sequence diagram related to messages for changing SCell settings.

[0084] In the case of a change in SCell settings triggered by O-DU10B2 (DU#2), in step S701, O-DU10B2 (DU#2) sends a SCell Modification Required message to O-DU10B1 (DU#1).

[0085] In step S702, O-DU10B1 (DU#1) sends a SCell Modification Request message to O-DU10B2 (DU#2) to request a change in the SCell settings.

[0086] In step S703, O-DU10B2 (DU#2) sends a SCell Modification Response message to O-DU10B1 (DU#1) in response to the received request for a change in the SCell settings.

[0087] Note that the sequence diagram in Figure 7 shows the case where the setting change related to SCell is triggered by O-DU10B2 (DU#2). On the other hand, in the case where the setting change related to SCell is triggered by O-DU10B1 (DU#1), the processing in step S701 is not performed, and processing starts from step S702.

[0088] As described above, by changing the settings related to SCell through messages for changing SCell settings, it becomes possible to properly perform processing related to Inter O-DU CA.

[0089] ≪Specific Example 4≫ When performing Inter O-DU CA between two DUs, a message may be sent and received to indicate that the SCell reconfiguration is complete. This message may be the same as the message in step S214 of Figure 5.

[0090] Figure 8 is an example of a sequence diagram related to messages for SCell reconfiguration.

[0091] In step S801, O-DU10B1 (DU#1) sends a SCell Reconfiguration Complete message to O-DU10B2 (DU#2) to indicate that the SCell reconfiguration is complete.

[0092] The SCell Reconfiguration Complete message may be used when adding or removing SCells.

[0093] As described above, by notifying the SCell O-DU10B2 (DU#2) that the SCell reconfiguration is complete via a message indicating completion of the SCell reconfiguration, it becomes possible to properly perform the processing related to Inter O-DU CA.

[0094] ≪Specific Example 5≫ If terminal 20 reconnects to the cell (PCell) of the master DU (DU#1) while Inter O-DU CA is being performed between two DUs, terminal 20 will be unable to continue the CA. Therefore, a message to release the SCell resource to the secondary DU (DU#2) may be sent or received. This message may mean the same message as in steps S303 / S304 in Figure 6.

[0095] Figure 9 is an example of a sequence diagram related to messages for releasing SCell resources in Inter O-DU CA.

[0096] In step S901, terminal 20 sends an RRC Reestablishment Request message to O-DU10B1 (DU#1). The RRC Reestablishment Request message may include the previously used C-RNTI (old C-RNTI (Cell-Radio Network Temporary Identifier)) and the previously used PCI (old PCI (Physical Cell Identity)).

[0097] In step S902, O-DU10B1 (DU#1) includes the lower layer settings of terminal 20 in the Initial UL RRC Message Transfer message and sends it to O-CU10A (CU#1).

[0098] In step S903, O-CU10A (CU#1) sends a DL RRC Message Transfer message containing an RRC Reestablishment message to O-DU10B1 (DU#1). The DL RRC Message Transfer message may also contain the previously used gNB-DU UE F1AP ID (old gNB-DU UE F1AP (F1 Application Protocol) ID).

[0099] In step S904, O-DU10B1 (DU#1) sends an RRC Reestablishment message to terminal 20. In step S904, O-DU10B1 (DU#1) may obtain a UE context, which is a set of information associated with terminal 20, based on the old gNB-DU UE F1AP ID, and replace the old C-RNTI and old PCI with a new C-RNTI and a new PCI.

[0100] In step S905, terminal 20 sends an RRC Reestablishment Complete message to O-DU10B1 (DU#1).

[0101] In step S906, O-DU10B1 (DU#1) encapsulates the received RRC Reestablishment Complete message into a UL RRC Message Transfer message and sends it to O-CU10A (CU#1).

[0102] In step S907, O-CU10A1 (CU#1) triggers the UE context modification procedure by sending a UE Context Modification Request message to O-DU10B1 (DU#1).

[0103] In step S908, O-DU10B1 (DU#1) sends a SCell Release Request message to O-DU10B2 (DU#2) to instruct DU#2 to release the SCell resource.

[0104] In step S909, O-DU10B2 (DU#2) sends a SCell Release Request Acknowledge message, which is an acknowledgment of the SCell Release Request message, to O-DU10B1 (DU#1).

[0105] In step S910, O-DU10B1 (DU#1) responds to O-CU10A1 (CU#1) with a UE Context Modification Response message.

[0106] In step S911, O-CU10A1 (CU#1) includes the RRC Reconfiguration message in the DL RRC Message Transfer message and sends it to O-DU10B1 (DU#1).

[0107] In step S912, O-DU10B1 (DU#1) transmits the received RRC Reconfiguration message to terminal 20.

[0108] In step S913, terminal 20 sends an RRC Reconfiguration Complete message to O-DU10B1 (DU#1).

[0109] In step S914, O-DU10B1 (DU#1) includes the received RRC Reconfiguration Complete message in the UL RRC Message Transfer message and sends it to O-CU10A1 (CU#1).

[0110] In step S915, O-CU10A1 (CU#1) triggers the UE context modification procedure by sending a UE Context Modification Request message to O-DU10B1 (DU#1).

[0111] In step S916, O-DU10B1 (DU#1) responds to O-CU10A1 (CU#1) with a UE Context Modification Response message.

[0112] As described above, by releasing the SCell resource through a message for releasing the SCell resource, it becomes possible to properly perform the processing related to Inter O-DU CA.

[0113] ≪Specific Example 6≫ When performing Inter O-DU CA between two DUs, messages for updating the DU Configuration may be sent and received in order to update the settings necessary to enable correct interoperability between the DUs for the served cells. Such messages may include, for example, settings related to adding / deleting / deactivating cells. Such messages may include Served Cells To Add Item IE, which contains items related to the served cell to be added; Served Cells To Delete Item IE, which contains items related to the served cell to be deleted; Served Cells Status Item IE, which contains items related to the status of the served cell; Switching Off Ongoing IE, etc.

[0114] Figure 10 is an example of a sequence diagram related to messages for updating DU settings.

[0115] For example, suppose CU#1 triggers an update to the DU configuration. In this case, in step S1001, O-CU10A1 (CU#1) sends a gNB-DU Configuration Update message to O-DU10B1 (DU#1).

[0116] In step S1002, O-DU10B1 (DU#1) sends a gNB-DU Configuration Update message to O-DU10B2 (DU#2).

[0117] In step S1003, O-DU10B2 (DU#2) sends a gNB-DU Configuration Update Acknowledge message to O-DU10B1 (DU#1), which is an acknowledgment of the received gNB-DU Configuration Update message.

[0118] In step S1004, O-DU10B1 (DU#1) sends a gNB-DU Configuration Update Acknowledge message, which is an acknowledgment of the received gNB-DU Configuration Update message, to O-CU10A1 (CU#1).

[0119] For example, suppose DU#1 triggers an update to the DU configuration. In this case, in step S1011, O-DU10B1 (DU#1) sends a gNB-DU Configuration Update message to O-CU10A1 (CU#1).

[0120] In step S1012, O-DU10B1 (DU#1) sends a gNB-DU Configuration Update message to O-DU10B2 (DU#2).

[0121] In step S1013, O-DU10B2 (DU#2) sends a gNB-DU Configuration Update Acknowledge message to O-DU10B1 (DU#1), which is an acknowledgment of the received gNB-DU Configuration Update message.

[0122] In step S1014, O-CU10A1 (CU#1) sends a gNB-DU Configuration Update Acknowledge message, which is an acknowledgment of the received gNB-DU Configuration Update message, to O-DU10B1 (DU#1).

[0123] For example, suppose DU#2 triggers an update to the DU configuration. In this case, in step S1021, O-DU10B2 (DU#2) sends a gNB-DU Configuration Update message to O-DU10B1 (DU#1).

[0124] In step S1022, O-DU10B1 (DU#1) sends a gNB-DU Configuration Update message to O-CU10A1 (CU#1).

[0125] In step S1023, O-CU10A1 (CU#1) sends a gNB-DU Configuration Update Acknowledge message, which is an acknowledgment of the received gNB-DU Configuration Update message, to O-DU10B1 (DU#1).

[0126] In step S1024, O-DU10B1 (DU#1) sends a gNB-DU Configuration Update Acknowledge message, which is an acknowledgment of the received gNB-DU Configuration Update message, to O-DU10B2 (DU#2).

[0127] As described above, updating the DU settings via the message for updating the DU settings makes it possible to properly perform the processes related to Inter O-DU CA.

[0128] ≪Specific Example 7≫ When performing Inter O-DU CA between two DUs, messages containing information about load such as traffic may be sent and received. Such messages may include a Cell To Report List, which is a list of cells that report.

[0129] Figure 11 is an example of a sequence diagram related to messages for reporting load information.

[0130] In step S1101, O-DU10B1 (DU#1) sends a Resource Status Request message to O-DU10B2 (DU#2) to request a report of information regarding the load.

[0131] In step S1102, O-DU10B2 (DU#2) responds to the received Resource Status Request message with a Resource Status Response message.

[0132] As described above, by reporting load-related information from DU#2 to DU#1 via a message for reporting load-related information, it becomes possible to properly perform the processing related to Inter O-DU CA.

[0133] ≪Specific Example 8≫ When performing Inter O-DU CA between two DUs, messages for the transfer of stagnant data generated during SCell addition / deletion may be sent and received.

[0134] Figure 12 is an example of a sequence diagram related to messages for the transfer of stagnant data.

[0135] In step S1201, O-DU10B2 (DU#2) sends a Data Forwarding message to O-DU10B1 (DU#1) to forward the accumulated data generated during SCell addition / deletion. Alternatively, in step S1201, O-DU10B2 (DU#2) may forward the accumulated data generated during SCell addition / deletion to O-DU10B1 (DU#1).

[0136] As described above, the message for transferring accumulated data allows DU#2 to transfer accumulated data generated during SCell addition / deletion to DU#1, thereby enabling proper processing related to Inter O-DU CA.

[0137] ≪Specific Example 9≫ When performing Inter O-DU CA between two DUs, messages indicating the data delivery status may be sent and received.

[0138] Figure 13 is an example of a sequence diagram related to messages used to indicate the status of data delivery.

[0139] In step S1301, O-DU10B2 (DU#2) sends a Downlink Data Delivery Status message to O-DU10B1 (DU#1) to report the status of DL data delivery.

[0140] As described above, by reporting the delivery status of DL data from DU#2 to DU#1 through messages indicating the data delivery status, it becomes possible to properly perform the processing related to Inter O-DU CA.

[0141] <Functional Configuration> An example of the functional configuration of the base station 10 and terminal 20, including O-CU10A, O-DU10B, and O-RU10C, which perform the processes and operations described above, is described below. The base station 10 and terminal 20 include functions to implement the embodiments described above. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiments.

[0142] ≪Base Station≫ Figure 14 shows an example of the functional configuration of a base station.

[0143] The base station 10, including O-CU10A, O-DU10B, and O-RU10C, has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 14 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to this embodiment.

[0144] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also includes the function of transmitting messages between O-CU 10A, O-DU 10B, and O-RU 10C. Furthermore, the transmitting unit 110 has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20.

[0145] The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from higher layers, for example, from the received signals. The receiving unit 120 also includes the function of receiving messages between O-CU 10A, O-DU 10B, and O-RU 10C. Furthermore, the receiving unit 120 receives inter-network node messages from other network nodes.

[0146] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to Inter O-DU CA.

[0147] As described in the embodiment, the control unit 140 performs control related to setting, instructing, and notifying about Inter O-DU CA. The control unit 140 may set up an interface for performing Inter O-DU CA. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0148] <Terminal> Figure 15 shows an example of the functional configuration of a terminal.

[0149] The terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 15 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0150] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 transmits a Measurement Report and an RRC message to the base station 10. The transmitting unit 210 transmits PUSCH and the like based on the wireless resources identified by the control unit 240. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals and the like transmitted from the base station 10. The receiving unit 220 receives setting information, instructions, and notifications related to Inter O-DU CA from the base station 10. The receiving unit 220 receives PDSCH and the like based on the wireless resources identified by the control unit 240. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores various pre-set setting information.

[0151] The control unit 240 performs control related to settings, instructions, and notifications regarding Inter O-DU CA, as described in the embodiment. The control unit 240 may also measure the received signal quality in order to transmit a Measurement Report. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0152] <Hardware Configuration> The block diagrams (Figures 14 and 15) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

[0153] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0154] Figure 16 shows an example of the hardware configuration of a base station and a terminal.

[0155] For example, the base station 10, terminal 20, etc. in this embodiment may function as a computer that processes the wireless communication method of this embodiment. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, storage device 1002, auxiliary storage device 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0156] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in Figure 17, or it may be configured to omit some of the devices.

[0157] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0158] The processor 1001 controls the entire computer, for example, by running an operating system (OS). The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0159] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 14 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 15 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. The above-mentioned various processes have been described as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line.

[0160] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0161] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0162] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of FDD and TDD. For example, the transmitting / receiving antenna, amplifier section, transmitting / receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting / receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0163] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED (Light-Emitting Diode) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0164] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0165] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0166] The O-CU 10A included in the base station 10 may be interpreted as a control device, communication device, aggregation device, central device, management device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, the O-CU 10A may be interpreted as a central unit, aggregation node, etc.

[0167] The O-DU 10B included in the base station 10 may be interpreted as a control device, communication device, distribution device, high-PHY device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, the O-DU 10B may be interpreted as a distributed unit, distributed node, etc.

[0168] The O-RU10C included in the base station 10 may be interpreted as a radio device, RF (Radio Frequency) device, low PHY device, etc. Each device may be rephrased as a unit, node, etc. For example, O-RU10C may be interpreted as a radio unit, radio node, etc.

[0169] Figure 17 shows an example of a vehicle configuration.

[0170] The vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0171] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0172] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (I / O (Input / Output) ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0173] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0174] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0175] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS (Global Navigation Satellite System)), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0176] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0177] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0178] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012.

[0179] The electronic control unit 2010, various sensors 2021-2028, and information service unit 2012 may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0180] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0181] For example, embodiments of the present invention are as follows:

[0182] <1> A control device that performs carrier aggregation between other control devices, comprising: a control unit that sets up an interface for performing the carrier aggregation; and a transmitting unit that transmits first information to the other control device for performing at least one of adding or deleting a secondary cell at the interface. <2> The control device according to <1>, wherein the addition or deletion of the secondary cell is performed by a control device for an aggregation base station to the other control device via the control device. <3> The control device according to <1> or <2>, wherein the transmitting unit transmits second information to the other control device indicating the completion of at least one of adding or deleting a secondary cell. <4> The control device according to any one of <1> to <3>, wherein the transmitting unit transmits third information to the other control device for updating the settings of the self-control device and at least one of the other control devices. <5> The control device according to any one of <1> to <4>, wherein the transmitting unit transmits fourth information to the other control device for requesting a report of load information. <6> A communication method performed by a control device that performs carrier aggregation between other control devices, comprising the steps of: setting up an interface for performing the carrier aggregation; and transmitting a first information to the other control devices at the interface for adding or deleting a secondary cell.

[0183] In any of the above configurations, the control device, represented by the DU, can appropriately perform carrier aggregation between DUs.

[0184] <Supplement to Embodiments> Although these embodiments have been described above, the disclosed invention is not limited to these embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used.

[0185] The classification of items in the above description is not essential to the present invention, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other).

[0186] The boundaries of functional units or processing units in a functional block diagram do not necessarily correspond to the boundaries of physical parts. Multiple functional units may operate within a single physical part, or a single functional unit may operate within multiple physical parts.

[0187] The processing procedures described in the embodiments may be rearranged in order, as long as there is no contradiction. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 and the software operated by the processor of the terminal 20 according to this embodiment may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0188] The notification of information / messages is not limited to the embodiments described herein and may be carried out by other means. For example, the notification of information / messages may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Media Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Information / messages notified by higher layer signaling may be called configuration information. Information / messages notified by physical layer signaling may be called control information. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0189] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th Generation mobile communication system), 5G (5th Generation mobile communication system), 5G-A (5G-Advanced), Beyond 5G, 6G (6th Generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (Wideband-Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra Wide It may be applied to at least one of the following: systems utilizing LTE-Band, Bluetooth®, or other appropriate systems, and next-generation systems extended based thereon. Alternatively, multiple systems may be applied in combination (for example, at least one of LTE and LTE-A combined with 5G).

[0190] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0191] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME (Mobility Management Entity) or an S-GW (Serving Gateway), etc., but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0192] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0193] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0194] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0195] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0196] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technologies (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0197] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0198] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, the signal may be a message. Furthermore, CC may be called carrier frequency, cell, frequency carrier, etc.

[0199] The terms “system” and “network” as used in this disclosure are interchangeable.

[0200] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0201] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0202] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "Transmission / Reception Point (TRP)", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base station 10 may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0203] Base station 10 can accommodate one or more (e.g., three) cells. If base station 10 accommodates multiple cells, the entire coverage area of ​​base station 10 can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in this coverage.

[0204] In this disclosure, the transmission of information by the base station 10 to the terminal 20 may be interpreted as the base station 10 instructing the terminal 20 to perform control or operation based on the information.

[0205] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0206] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0207] At least one of the base station 10 and the terminal 20 may be called a transmitting device, receiving device, communication device, control device, etc. At least one of the base station 10 and the terminal 20 may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station 10 and the terminal 20 may be an IoT (Internet of Things) device such as a sensor.

[0208] Furthermore, the base station 10 in this disclosure may be read as a terminal 20. For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between the base station 10 and the terminal 20 is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In such a case, the terminal 20 may have the functions that the base station 10 has as described above. Also, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals 20 (for example, "side"). For example, uplink channel, downlink channel, etc. may be read as side channel.

[0209] Similarly, the terminal 20 in this disclosure may be read as a base station 10. In this case, the base station 10 may be configured to have the functions that the terminal 20 has.

[0210] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0211] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0212] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0213] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0214] Any reference to elements using designations such as “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0215] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0216] Where the terms “include,” “including,” and their variations are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

[0217] A wireless frame may consist of one or more frames in the time domain. Each of these one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0218] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0219] A slot may consist of one or more symbols in the time domain (such as OFDM symbols or SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols). A slot may also be a time unit based on neurology.

[0220] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (or PUSCH) mapping type B.

[0221] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0222] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 millisecond (ms)), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0223] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station 10 schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0224] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0225] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that make up the minimum time unit for scheduling may be controlled.

[0226] A TTI with a time length of 1 ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0227] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0228] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0229] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0230] One or more RBs may also be called a Physical RB (PRB), Subcarrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0231] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0232] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common RBs (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0233] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0234] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0235] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0236] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0237] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0238] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0239] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Accordingly, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0240] 10 Base station 10A O-CU 10B O-DU 10C O-RU 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023, Air pressure sensor 2024, Vehicle speed sensor 2025, Acceleration sensor 2026, Brake pedal sensor 2027, Shift lever sensor 2028, Object detection sensor 2029, Accelerator pedal sensor 2030, Driver assistance system unit 2031, Microprocessor 2032, Memory (ROM, RAM) 2033, Communication port (I / O port)

Claims

1. A control device for performing carrier aggregation between other control devices, comprising: a control unit for setting up an interface for performing the carrier aggregation; and a transmission unit for transmitting first information to the other control devices for adding or deleting at least one of secondary cells at the interface.

2. The control device according to claim 1, wherein the addition or deletion of the secondary cell is performed by a control device for an aggregated base station via the control device to the other control devices.

3. The control device according to claim 1, wherein the transmitting unit transmits a second piece of information indicating the completion of at least one of the addition or deletion of the secondary cell to the other control device.

4. The control device according to claim 1, wherein the transmitting unit transmits a third piece of information to the other control device for updating the settings of the self-control device and at least one of the other control devices.

5. The control device according to claim 1, wherein the transmitting unit transmits a fourth piece of information to the other control device for requesting a report of information regarding the load.

6. A communication method performed by a control device that performs carrier aggregation between other control devices, comprising the steps of: setting up an interface for performing the carrier aggregation; and transmitting a first information to the other control devices at the interface for adding or deleting a secondary cell.

Images