Base station and communication method

Abstract

The base station has: a receiving unit that receives, in a terminal, capability information containing information indicating a first group and information indicating a second group, the first group being constituted of one or more frequency band combinations that can be used only for a specific dual connectivity, the second group being constituted of one or more frequency band combinations that can be used for the specific dual connectivity; a control unit that, regarding a third group constituted of the one or more frequency band combinations of the first group and the one or more frequency band combinations of the second group, gives a plurality of indexes corresponding to the plurality of frequency band combinations of the third group to be able to determine each of the plurality of frequency band combinations of the third group; and a transmitting unit that transmits, to other base stations, a signal containing the indexes that can be used for inter-base station communication.

Description

Technical Field

[0001] This invention relates to base stations and communication methods in wireless communication systems. Background Technology

[0002] In New Radio (also known as "NR" or "5G"), which is the successor system to Long Term Evolution (LTE), technologies are being researched to meet requirements such as high-capacity systems, high-speed data transmission, low latency, simultaneous connection of a large number of terminals, low cost, and power saving (e.g., Non-Patent Literature 1).

[0003] In NR systems, similar to dual connectivity in LTE systems, a technology is being introduced that splits data between LTE system base stations (eNB) and NR system base stations (gNB) and transmits and receives data simultaneously through these base stations, known as LTE-NR dual connectivity, NR-NR dual connectivity, or multi-RAT (Multi Radio Access Technology) dual connectivity (hereinafter referred to as "MR-DC") (e.g., Non-Patent Document 2).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: 3GPP TS 38.300V15.4.0 (2018-12)

[0007] Non-patent document 2: 3GPP TS 37.340V15.4.0 (2018-12)

[0008] Non-patent document 3: 3GPP TS 38.101-3V15.3.0 (2018-09)

[0009] Non-patent document 4: 3GPP TSG-RAN WG2 Meeting #105, R2-1900292, Athens, Greece, 25 Feb-01 Mar 2019 Summary of the Invention

[0010] The problem that the invention aims to solve

[0011] NR E-UTRA Dual Connectivity (NE-DC) refers to a dual connection where the primary node is a gNB and the secondary node is an eNB. In NE-DC, the terminal connects to both the gNB, which operates as the primary node, and the eNB, which operates as the secondary node. The gNB is connected to the 5GC (5G Core Network).

[0012] A method is needed to coordinate and configure NE-DC frequency band combinations between base stations based on UE capability signaling from the terminal indicating the frequency band combinations that can be used for NE-DC.

[0013] Methods for solving problems

[0014] According to one aspect of the present invention, a network node is provided, comprising: a receiving unit, in a terminal, receiving a signal containing information representing a first group and information representing a second group, the first group consisting of one or more frequency band combinations usable only for a specific dual connection, and the second group consisting of one or more frequency band combinations usable for said specific dual connection; a control unit, assigning a plurality of indices corresponding to the plurality of frequency band combinations of the third group, which consists of the one or more frequency band combinations of the first group and the one or more frequency band combinations of the second group, to uniquely identify each frequency band combination in the plurality of frequency band combinations of the third group; and a transmitting unit, transmitting a signal containing information representing the plurality of frequency band combinations of the third group, which is usable for communication between network nodes, to other network nodes.

[0015] Invention Effects

[0016] According to an embodiment, a method is provided that enables coordination among base stations and setting of NE-DC frequency band combinations based on UE capability signaling from a terminal indicating frequency band combinations that can be used for NE-DC. Attached Figure Description

[0017] Figure 1 This is a diagram illustrating a structural example of the network architecture in the implementation method.

[0018] Figure 2 This is a diagram illustrating a structural example of a wireless communication system in an implementation embodiment.

[0019] Figure 3 This is a timing diagram used to illustrate the first operational example in the implementation method.

[0020] Figure 4This is a diagram used to illustrate an example of an information element used in the first operational example of the implementation.

[0021] Figure 5 This is a diagram illustrating an example of the structure of an intra-band contiguous EN-DC component carrier.

[0022] Figure 6 An example representing the structure of an intra-band non-contiguous EN-DC component carrier.

[0023] Figure 7 This is a timing diagram used to illustrate the second operational example in the implementation method.

[0024] Figure 8 This is a diagram used to illustrate an example of an information element used in the second operational example of the implementation.

[0025] Figure 9 This is a diagram representing an example of a specification change.

[0026] Figure 10 This is a diagram representing an example of a specification change.

[0027] Figure 11 This is a diagram representing an example of a specification change.

[0028] Figure 12 This is a diagram representing an example of a specification change.

[0029] Figure 13 This is a diagram representing an example of a specification change.

[0030] Figure 14 This is a diagram representing an example of a specification change.

[0031] Figure 15 This is a diagram representing an example of a specification change.

[0032] Figure 16 This is a diagram representing an example of a specification change.

[0033] Figure 17 This is a diagram illustrating an example of the functional structure of a base station in an implementation scheme.

[0034] Figure 18 This is a diagram illustrating an example of the functional structure of a terminal in an implementation method.

[0035] Figure 19 This is a diagram illustrating an example of the hardware structure of a base station or terminal in an implementation method.

[0036] Figure 20This is a diagram representing an example of a specification change.

[0037] Figure 21 This is a diagram representing an example of a specification change.

[0038] Figure 22 This is a diagram representing an example of a specification change. Detailed Implementation

[0039] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are examples, and the present invention is not limited to the embodiments described below.

[0040] In the operation of the wireless communication system according to embodiments of the present invention, existing technology is appropriately used. However, this existing technology is, for example, existing LTE, but is not limited to existing LTE. Furthermore, the term "LTE" as used in this specification is assumed to have a broad meaning, including LTE-Advanced and subsequent modes (e.g., NR), unless otherwise specified.

[0041] Furthermore, in the embodiments of the present invention described below, terms such as Synchronization signal (SS), Primary SS (PSS), Secondary SS (SSS), Physical Broadcast Channel (PBCH), and Physical Random Access Channel (PRACH) used in existing LTE are used. However, this is for ease of explanation, and other names may be used to refer to the same signals, functions, etc. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily specified as "NR-".

[0042] Furthermore, in embodiments of the present invention, the duplex mode can be either time-division duplex (TDD) mode, frequency-division duplex (FDD) mode, or other modes (e.g., flexible duplex, etc.).

[0043] Furthermore, in embodiments of the present invention, the “configured” wireless parameters can mean that specific values ​​are pre-configured, or that wireless parameters are configured as notified from base station 10 or terminal 20.

[0044] Figure 1 This is a diagram illustrating a structural example of the network architecture in an embodiment of the present invention. For example... Figure 1 As shown, the wireless network architecture in the embodiments of the present invention includes 4G-CU, 4G-RU (Remote Unit, Remote Radio Station), Evolved Packet Core (EPC), etc. on the LTE-Advanced side. The wireless network architecture in the embodiments of the present invention includes 5G-CU, 5G-DU, etc. on the 5G side.

[0045] like Figure 1 As shown, the 4G-CU includes layers up to Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and L1 (Layer 1, PHY, or Physical Layer), and connects to the 4G-RU via the Common Public Radio Interface (CPRI). The network node containing both the 4G-CU and 4G-RU is referred to as an Evolved Node B (eNB).

[0046] On the 5G side, such as Figure 1As shown, the 5G-CU includes an RRC layer, connects to the 5G-DU via a fronthaul (FH) interface, and connects to the 5G Core Network (5GC) via an NG interface. Furthermore, the 5G-CU connects to the 4G-CU via an X2 interface. The PDCP layer in the 4G-CU serves as the junction or separation point in the case of 4G-5G Dual Connectivity (DC), i.e., E-UTRA-NR Dual Connectivity (EN-DC). The network node containing both the 5G-CU and 5G-DU is referred to as the next-generation Node B (gNB). Alternatively, the 5G-CU can be called gNB-CU, and the 5G-DU can be called gNB-DU.

[0047] In addition, such as Figure 1 As shown, carrier aggregation (CA) is performed between 4G-RUs, and data conversion (DC) is performed between 4G-RUs and 5G-DUs. Additionally, although not illustrated, user equipment (UE) is wirelessly connected via the RF of either the 4G-RU or the 5G-DU and transmits and receives packets.

[0048] in addition, Figure 1 The diagram illustrates the wireless network architecture for LTE-NR DC, specifically EN-DC (E-UTRA-NR Dual Connectivity). However, the same wireless network architecture can also be used when the 4G-CU is separated into a CU-DU, or when NR operates standalone. When the 4G-CU is separated into a CU-DU, the functions involved in the RRC and PDCP layers can be transferred to the 4G-CU, with the RLC layer and below contained within the 4G-DU. Additionally, separating the CU-DU can reduce the CPRI data rate.

[0049] In addition, a 5G-CU can be connected to multiple 5G-DUs. Furthermore, NR-NR Dual Connectivity (NR-DC) can be achieved by connecting the UE to multiple 5G-CUs, or NR-DC can be achieved by connecting the UE to multiple 5G-DUs and a single 5G-CU.

[0050] Figure 2 This is a diagram illustrating a structural example of a wireless communication system according to an embodiment of the present invention. Figure 2 This is a schematic diagram representing a wireless communication system with Multi-RAT Dual Connectivity (MR-DC).

[0051] like Figure 2 As shown, terminal 20 (which may also be user equipment 20, UE 20) communicates with base station 10A provided through the LTE system and base station 10B provided through the NR system (hereinafter, base station 10A and base station 10B may also be referred to as "base station 10" without distinguishing between them). Furthermore, terminal 20 may also support LTE-NR dual connectivity, i.e., EN-DC, where base station 10A is the primary node (hereinafter also referred to as "MN") and base station 10B is the secondary node (hereinafter also referred to as "SN"). Terminal 20 can simultaneously utilize multiple component carriers provided by base station 10A as the primary node and base station 10B as the secondary node to perform simultaneous transmission or reception with both base station 10A as the primary node and base station 10B as the secondary node.

[0052] Furthermore, embodiments of the present invention are not limited to the above-described situations. For example, in Figure 2 In this configuration, base station 10A can be a base station provided via an NR system, and base station 10B can be a base station provided via an LTE system. In this case, terminal 20 can also support NR-LTE dual connectivity, i.e., NE-DC, where base station 10A is set as MN and base station 10B is set as SN. Terminal 20 can simultaneously utilize multiple component carriers provided by base station 10A (as the primary node) and base station 10B (as the secondary node) to perform simultaneous transmission or reception with both base station 10A (as the primary node) and base station 10B (as the secondary node). Furthermore, for example, in... Figure 2 In this configuration, base station 10A can also be a base station provided via an NR system, and base station 10B can also be a base station provided via an NR system. In this case, terminal 20 can also support NR-NR dual connectivity, i.e., NR-DC, where base station 10A is set as MN and base station 10B is set as SN.

[0053] Furthermore, the following embodiments mainly describe LTE-NR dual connectivity, but the base station 10 and terminal 20 involved in the embodiments of the present invention are not limited to LTE-NR dual connectivity, and can be applied to dual connectivity, i.e., MR-DC, between multiple wireless communication systems utilizing different RATs.

[0054] When LTE component carriers and NR component carriers are configured in the same frequency band and EN-DC is set, the LTE component carriers and NR component carriers are contained within the same frequency band. For example, consider the case where the LTE component carrier is configured in the lower frequency band portion of the frequency band, and the NR component carrier is configured in the higher frequency band portion of the frequency band. Furthermore, as another possibility, consider the case where the LTE component carrier is configured in the higher frequency band portion of the frequency band, and the NR component carrier is configured in the lower frequency band portion of the frequency band.

[0055] In this situation, in order to ensure that the frequency band of the LTE component carrier does not overlap with the frequency band of the NR component carrier, certain information needs to be communicated between the eNB and the gNB.

[0056] The following approach is proposed: listing multiple scenarios (configuration modes of component carriers) envisioned in the case of intra-band contiguous EN-DC and intra-band non-contiguous EN-DC, and transmitting information representing the center frequency and bandwidth of each component carrier among the multiple component carriers used in each scenario.

[0057] This method ensures that portions of the frequency band of the configured LTE component carrier do not overlap with portions of the frequency band of the configured NR component carrier. However, this method may increase the amount of information that should be transmitted from the eNB to the gNB.

[0058] Thus, when setting LTE component carriers and NR component carriers in the same frequency band, and setting EN-DC (which can also be NE-DC or NR-DC) (intra-band EN-DC (which can also be intra-band NE-DC (intra-band NE-DC) or intra-band NR-DC (intra-band NR-DC))), in order to prevent the frequency band portion of the set LTE (or NR) component carrier from overlapping with the frequency band portion of the set NR (or LTE) component carrier, it is necessary to reduce... Figure 2 Base station 10A will notify the information to Figure 2 The amount of information at base station 10B.

[0059] (Method 1)

[0060] The following describes an example of Method 1. In Method 1, within the intra-band EN-DC, to ensure that a portion of the frequency band of the configured LTE component carrier does not overlap with a portion of the frequency band of the configured NR component carrier, the amount of information transmitted from base station 10A to base station 10B is reduced. Furthermore, the application of Method 1 is not limited to intra-band EN-DC. Where necessary, by appropriately applying modifications, Method 1 can be applied to both intra-band NE-DC and intra-band NR-DC.

[0061] First, for clarity, consider the following example: On base station 10A, only one component carrier is configured in a single frequency band. In this case, base station 10A, acting as the master node, notifies base station 10B of the lower and upper positions of the configured component carrier on the frequency axis. Upon receiving this information from base station 10A, base station 10B can use it to configure one or more component carriers in a frequency band other than the one specified at the lower and upper positions on the aforementioned frequency axis within the same frequency band. Alternatively, on base station 10A, if multiple component carriers are configured in a single frequency band, base station 10A simply notifies base station 10B of the lower and upper positions of each configured component carrier on the frequency axis. Upon receiving information from base station 10A indicating the lower and upper positions of each component carrier on the frequency axis, base station 10B can use the received information to set one or more component carriers in a frequency band outside the frequency band corresponding to the lower and upper positions of each component carrier on the frequency axis within the aforementioned single frequency band.

[0062] (Example of Method 1)

[0063] Next, refer to Figure 3The operation example of Method 1 will be described below. First, in step S101, base station 10A determines to set one or more frequency bands for one or more LTE component carriers in a single frequency band. Next, base station 10A creates information indicating the lower and upper positions of each frequency band in the one or more frequency bands used to set one or more LTE component carriers on the frequency axis. Then, in step S102, base station 10A sends the created information indicating the lower and upper positions of each frequency band on the frequency axis to base station 10B. Upon receiving the information from base station 10A indicating the lower and upper positions of each set component carrier on the frequency axis, base station 10B can use the received information to set one or more NR component carriers in a frequency band other than the frequency bands corresponding to the lower and upper positions of each component carrier on the frequency axis within the aforementioned single frequency band. Furthermore, if the base station 10B receives information from the base station 10A indicating the lower and upper positions of each set component carrier on the frequency axis, and if there are certain circumstances, such as interference with other communications based on the base station 10B, requiring the resetting of the frequency position of any component carrier set by the base station 10A, the base station 10B may send information to the base station 10A requesting the resetting of the frequency position of that component carrier.

[0064] According to Method 1, regarding all scenarios of component carrier configuration, compared to notifying information indicating the center frequency and bandwidth of each of the multiple component carriers used in each scenario, the amount of information transmitted can be reduced.

[0065] Figure 4 This is a diagram representing an example of the information elements used in the operation example of method 1. Figure 4 This is an example of the RRC message "CG-ConfigInfo" between intermediate nodes. "CG-ConfigInfo" is sent from the LTE-RAN master node to the NG-RAN secondary node. Alternatively, "CG-ConfigInfo" can also be sent from the NG-RAN master node to the LTE-RAN secondary node. "CG-ConfigInfo" is an information element used to perform connection establishment, modification, or release within a secondary group.

[0066] like Figure 4As shown, "CG-ConfigInfo" contains the information element "CG-ConfigInfo-IEs". "CG-ConfigInfo-IEs" contains "configuredFrequencyRangeMCG". "configuredFrequencyRangeMCG" specifies whether the master node is an LTE node or an NR node. If the master node is an LTE node, the lower and upper positions of each frequency band in one or more frequency bands of one or more LTE component carriers on the frequency axis are specified via "FrequencyRangeEUTRA". If the master node is an NR node, the lower and upper positions of each frequency band in one or more frequency bands of one or more NR component carriers on the frequency axis are specified via "FrequencyRangeNR".

[0067] (Method 2)

[0068] The following describes an example of Method 2. In Method 2, within the intra-band EN-DC, to ensure that a portion of the frequency band of the configured LTE component carrier does not overlap with a portion of the frequency band of the configured NR component carrier, the amount of information transmitted from base station 10A to base station 10B is reduced. Furthermore, the application of Method 2 is not limited to intra-band EN-DC. When necessary, by appropriately applying modifications, Method 2 can be applied to intra-band NE-DC and intra-band NR-DC.

[0069] In method 2, a table showing the structure of the component carriers of intra-band contiguous EN-DC is used. Figure 5 Or a table showing the structure of the component carriers of intra-band non-contiguous EN-DC. Figure 6 ).

[0070] Figure 5 This is a diagram showing an example of a table illustrating the EN-DC configuration (the structure of LTE component carriers and NR component carriers) and the bandwidth combination set (a set of combinations of bandwidths) for intra-band contiguous EN-DC.

[0071] according to Figure 5 The table specifies the E-UTRA-NR configuration / bandwidth combination set for each EN-DC configuration used in the downlink and uplink EN-DC configurations (e.g., DC_(n)41AA). For example, in the case of DC_(n)41AA, the used E-UTRA band is 41, and the used NR band is n41. In this case, the uplink band is 2496MHz to 2690MHz, and the downlink band is 2496MHz to 2690MHz (TDD is applied). The maximum aggregated bandwidth is 120MHz.

[0072] The bandwidth combination set is defined as two types (0 and 1). When the bandwidth combination set is 0, the bandwidth of the LTE component carrier is 20MHz, and the bandwidth of the NR component carrier is any one of 40MHz, 60MHz, 80MHz, and 100MHz. When the bandwidth combination set is 1, the bandwidth of the LTE component carrier is 20MHz, and the bandwidth of the NR component carrier is any one of 40MHz, 50MHz, 60MHz, 80MHz, and 100MHz.

[0073] For example, as an example where the LTE component carrier is configured in the lower frequency portion and the NR component carrier is configured in the higher frequency portion when the bandwidth combination set is 0, the table shows the possible combinations of the bandwidth of the LTE component carrier and the bandwidth of the NR component carrier, which can be any combination of {20MHz, 40MHz}, {20MHz, 60MHz}, {20MHz, 80MHz}, and {20MHz, 100MHz}.

[0074] Furthermore, for example, as an example where the NR component carrier is configured in the lower frequency portion and the LTE component carrier is configured in the higher frequency portion when the bandwidth combination set is 0, the table shows the cases where any combination of {40MHz, 20MHz}, {60MHz, 20MHz}, {80MHz, 20MHz}, and {100MHz, 20MHz} can be used.

[0075] Therefore, utilizing Figure 5 The table, by notifying base station 10B of the index used to specify EN-DC configuration and bandwidth combination from base station 10A, allows base station 10B to set the frequency position of the NR component carrier so that it does not overlap with the portion of the frequency band used by base station 10A to set the LTE component carrier. In this case, parameters indicating that the LTE component carrier is allocated to the lower frequency portion of the aggregated frequency band of the set LTE component carrier and NR component carrier can also be added to the aggregated frequency band. For example, such parameters can be set to define componentCarrierPositionEUTRA and have componentCarrierPositionEUTRA take the value {lower, upper}.

[0076] Alternatively, in order to explicitly specify the position of the LTE component carrier, for example, base station 10A may send to base station 10B information indicating the center frequency of the frequency band of the configured LTE component carrier, information indicating the lower frequency position of the frequency band of the configured LTE component carrier, and / or information indicating the upper frequency position of the frequency band of the configured LTE component carrier, based on the index used to specify the EN-DC configuration and band combination.

[0077] In this case, for example, a new index may be defined based on the aforementioned index and the information indicating the center frequency of the frequency band of the configured LTE component carrier, and the defined new index may be notified from base station 10A to base station 10B. Alternatively or additionally, a new index may be defined based on the aforementioned index and the information indicating the lower frequency position of the frequency band of the configured LTE component carrier, and the defined new index may be notified from base station 10A to base station 10B. Alternatively or additionally, a new index may be defined based on the aforementioned index and the information indicating the upper frequency position of the frequency band of the configured LTE component carrier, and the defined new index may be notified from base station 10A to base station 10B.

[0078] Figure 6 This is a diagram illustrating an example of a table showing the structure of an intra-band non-contiguous EN-DC component carrier.

[0079] according to Figure 6 The table specifies the E-UTRA-NR configuration / bandwidth combination set for each EN-DC configuration (e.g., DC_41A_n41A) used in both the downlink and uplink EN-DC configurations. For example, in the case where the used EN-DC configuration is DC_41A_n41A, the used E-UTRA band is 41, and the used NR band is n41. In this case, the uplink band is 2496MHz to 2690MHz, and the downlink band is 2496MHz to 2690MHz (TDD is applied). The maximum aggregated bandwidth is 120MHz.

[0080] The bandwidth combination set is defined as two types (0 and 1). When the bandwidth combination set is 0, the bandwidth of the LTE component carrier is 20MHz, and the bandwidth of the NR component carrier is any one of 40MHz, 60MHz, 80MHz, and 100MHz. When the bandwidth combination set is 1, the bandwidth of the LTE component carrier is 20MHz, and the bandwidth of the NR component carrier is any one of 40MHz, 50MHz, 60MHz, 80MHz, and 100MHz.

[0081] For example, as an example where the LTE component carrier is configured in the lower frequency portion and the NR component carrier is configured in the higher frequency portion when the bandwidth combination set is 0, the table shows the possible combinations of the bandwidth of the LTE component carrier and the bandwidth of the NR component carrier, which can be any combination of {20MHz, 40MHz}, {20MHz, 60MHz}, {20MHz, 80MHz}, and {20MHz, 100MHz}.

[0082] Furthermore, for example, as an example where the NR component carrier is configured in the lower frequency portion and the LTE component carrier is configured in the higher frequency portion when the bandwidth combination set is 0, the table shows the cases where any combination of {40MHz, 20MHz}, {60MHz, 20MHz}, {80MHz, 20MHz}, and {100MHz, 20MHz} can be used.

[0083] Therefore, utilizing Figure 6The table, by notifying base station 10B of the index used to specify EN-DC configuration and bandwidth combination from base station 10A, allows base station 10B to set the frequency position of the NR component carrier so that it overlaps with a portion of the frequency band used by base station 10A to set the LTE component carrier. In this case, parameters indicating that the LTE component carrier is allocated to the lower frequency portion of the aggregated frequency band of the set LTE component carrier and NR component carrier can also be added to the transmitted frequency band. For example, such parameters can be set to define componentCarrierPositionEUTRA and have componentCarrierPositionEUTRA take the value {lower, upper}.

[0084] Alternatively, in order to explicitly specify the location of the LTE component carrier, for example, base station 10A may send information indicating the center frequency of the frequency band of the configured LTE component carrier, information indicating the lower frequency position of the frequency band of the configured LTE component carrier, and / or information indicating the upper frequency position of the frequency band of the configured LTE component carrier, based on the specified EN-DC configuration and band combination index, to base station 10B.

[0085] In this case, for example, a new index may be defined based on the aforementioned index and the information indicating the center frequency of the frequency band of the configured LTE component carrier, and the defined new index may be notified from base station 10A to base station 10B. Alternatively or additionally, a new index may be defined based on the aforementioned index and the information indicating the lower frequency position of the frequency band of the configured LTE component carrier, and the defined new index may be notified from base station 10A to base station 10B. Alternatively or additionally, a new index may be defined based on the aforementioned index and the information indicating the upper frequency position of the frequency band of the configured LTE component carrier, and the defined new index may be notified from base station 10A to base station 10B.

[0086] According to Method 2, for all scenarios regarding the configuration of component carriers, compared to the method of notifying information in each scenario about the center frequency and bandwidth of each of the multiple component carriers used, the amount of information transmitted can be reduced.

[0087] (Example of Method 2)

[0088] Next, refer to Figure 7 The operation example of Method 2 will be described below. First, in step S201, base station 10A determines one or more frequency bands within a single frequency band for configuring one or more LTE component carriers. Next, base station 10A, referring to a table specifying E-UTRA-NR configuration / bandwidth combination sets for each EN-DC configuration used in the downlink and uplink EN-DC configurations, determines the index of the E-UTRA-NR configuration / bandwidth combination set corresponding to the one or more frequency bands of the configured one or more LTE component carriers. In step S202, base station 10A transmits a signal representing the determined index to base station 10B. Upon receiving an index from base station 10A representing an E-UTRA-NR configuration / bandwidth combination set corresponding to one or more frequency bands of one or more configured LTE component carriers, base station 10B can use the received index to configure the frequency band for each component carrier within the aforementioned single frequency band, based on the E-UTRA-NR configuration / bandwidth combination set. Furthermore, if there are situations, such as interference with other communications based on base station 10B, where the frequency position of any component carrier configured by base station 10A needs to be reset, base station 10B can also send information to base station 10A requesting the reset of the frequency position of that component carrier.

[0089] Figure 8 This is a diagram showing an example of the information elements used in the operation example of method 2. Figure 8This is an example of the RRC message "CG-ConfigInfo" between intermediate nodes. "CG-ConfigInfo" is sent from the LTE-RAN master node to the NG-RAN slave node. Alternatively, "CG-ConfigInfo" can also be sent from the NG-RAN master node to the LTE-RAN slave node. "CG-ConfigInfo" is an information element used to perform connection establishment, modification, or release within the slave group.

[0090] Figure 8 The “CG-ConfigInfo” shown contains the information element “CG-ConfigInfo-IEs”. “CG-ConfigInfo-IEs” contains “allowedBandwidthCombinationSet”. “allowedBandwidthCombinationSet” represents information about the E-UTRA-NR configuration / bandwidth combination set. For example, “allowedBandwidthCombinationSet” can also be an index. Furthermore, “componentCarrierPositionEUTRA” contained in “CG-ConfigInfo-IEs” can be set to either lower or upper. Setting “componentCarrierPositionEUTRA” to lower corresponds to being allocated to the lower frequency portion of a band where LTE component carriers are aggregated. Setting “componentCarrierPositionEUTRA” to upper corresponds to being allocated to the higher frequency portion of a band where LTE component carriers are aggregated.

[0091] The examples above primarily illustrate signaling examples usable in the EN-DC scenario. The following examples illustrate signaling between nodes in the NE-DC scenario.

[0092] Dual connectivity using both E-UTRA and NR wireless access technologies is called Multi-RAT-Dual Connectivity (MR-DC). In MR-DC, one of the E-UTRA node and the NR node operates as the master node, and the other operates as the slave node. NRE-UTRA Dual Connectivity (NR E-UTRA Dual Connectivity (NE-DC)) refers to a master node (e.g., Figure 2The base station 10A) is a gNB and the secondary node (e.g., Figure 2 The base station 10B provides dual connectivity for the eNB. In the NE-DC, the terminal 20 is connected to both the gNB, which operates as the master node, and the eNB, which operates as the slave node. The gNB is connected to the 5GC (5G-Core Network).

[0093] (Proposal 1)

[0094] The following example of signaling is illustrated: This signaling is used to set the NE-DC frequency band combination between base stations when terminal 20 supports frequency band combinations usable only for NE-DC. This is based on UE capability signaling from terminal 20 indicating frequency band combinations usable only for NE-DC. The supportedBandCombinationList field can be used as an inter-node message for MR-DC.

[0095] When terminal 20 supports frequency band combinations that can only be used for NE-DC, for example, for gNB as the master node, terminal 20 notifies the frequency band combination through dedicated supportedBandCombinationListNEDC-Only capability signaling.

[0096] However, using the `supportedBandCombinationListNEDC-only` field as an inter-node message for MR-DC has not yet been envisioned. That is, the following scenario has not been considered: A master node, notified via the `supportedBandCombinationListNEDC-only` field of a frequency band combination that is only available for NE-DC, restricts the frequency band combination for a sub-cell group (SCG) according to one or more frequency band combinations notified via the `supportedBandCombinationListNEDC-only` field.

[0097] As a solution to the aforementioned problem, for example, one could consider adding a new field to the CG-ConfigInfo IE to adjust the functionality between MR-DC nodes based on one or more band combinations notified from terminal 20 via the supportedBandCombinationListNEDC-only field. When setting NE-DC band combinations between MR-DC nodes based on CG-ConfigInfo, for example, it is also possible for the slave node to request one or more band combinations within supportedBandCombinationListNEDC-Only, i.e., band combinations other than those permitted by the master node. Furthermore, it is also possible for the slave node to notify the master node of band combinations selected from one or more band combinations within supportedBandCombinationListNEDC-Only, i.e., those permitted by the master node.

[0098] Figure 9 as well as Figure 10 This is a diagram representing an example of a specification change. Figure 9 as well as Figure 10 An example of making changes to the CG-Config message is shown. This CG-Config message can also be a message sent from the secondary node to the primary node.

[0099] For example, such as Figure 9 As shown in the example, fields related to NE-DC, such as selectedBandCombinationNEDC and requestedBC-NEDC, can also be appended to the CG-Config message.

[0100] Figure 10 Indicates that in such Figure 9 The example shown illustrates the changes made to the CG-Config field descriptions when the CG-Config message is modified.

[0101] like Figure 10As the example shows, the requestedBC-MRDC field can also be used to request the setting of any band combination in the supportedBandCombinationList in UE-MRDC-Capability (in the case of EN-DC or NE-DC) or UE-NR-Capability (in the case of NR-DC). It can also be used to request corresponding feature sets that are prohibited from use in the master node (i.e., outside of allowedBC-ListMRDC) for the renegotiation of UE capabilities permitted for SCG settings. In the case of NE-DC, and if this field is included in the CG-Config message, the requestedBC-NEDC field may not be included.

[0102] In addition, such as Figure 10 As shown in the example, the requestedBC-NE-DC field can also be used to request the configuration of any band combination in the supportedBandCombinationListNEDC-Only, and to request the corresponding feature sets that are prohibited from use in the master node (i.e., outside of allowedBC-ListNEDC) in order to renegotiate the UE capability for SCG configuration. The requestedBC-MRDC field may or may not be included if this field is included in the CG-Config message. This field may also be used only in the case of NE-DC.

[0103] In addition, such as Figure 10As shown in the examples, in the cases of EN-DC, NE-DC, and NR-DC, the selectedBandCombination field can also represent the band combination selected by the secondary node from one or more band combinations permitted by allowedBC-ListMRDC. If the band combination and / or feature set selected by the secondary node for SCG is changed (that is, even if the new selection of the band combination and / or feature set is permitted by allowedBC-ListMRDC), the secondary node can also notify the primary node of this field. In the case of NE-DC, and if this field is included in the CG-Config message, selectedBandCombinationNEDC may not be included.

[0104] In addition, such as Figure 10 As shown in the example, in the case of NE-DC, the `selectedBandCombinationNEDC` field can also represent the band combination selected by the secondary node from one or more band combinations permitted through `allowedBC-ListNEDC`. If the band combination and / or feature set selected by the secondary node for the SCG is changed (that is, even if the new selection of the band combination and / or feature set is permitted through `allowedBC-ListNEDC`), the secondary node can also notify the primary node of this field. If this field is included in the CG-Config message, `selectedBandCombination` may or may not be included. This field can also be used only in the case of NE-DC.

[0105] Figure 11 as well as Figure 12 This is a diagram representing an example of a specification change. Figure 11 as well as Figure 12 This example illustrates a change made to the CG-ConfigInfo message. This CG-ConfigInfo message can also be a message sent from the master node to the slave node.

[0106] For example, such as Figure 11As shown in the example, the allowedBC-ListNEDC field, used for notifications related to NE-DC, can also be appended to the CG-ConfigInfo message.

[0107] Figure 12 Indicates that in such Figure 11 The example shown illustrates the changes made to the CG-ConfigInfo field descriptions when the CG-ConfigInfo message is modified.

[0108] like Figure 12 As shown in the example, the allowedBC-ListNEDC field can also represent a list of indices for specifying one or more band combinations within NE-DC capabilities from which the secondary node is allowed to select SCG band combinations. Each element in the allowedBC-ListNEDC field can also represent a band combination numbered according to supportedBandCombinationListNEDC-Only. All MR-DC band combinations represented by this field can also be a superset of one or more MCG bands selected by the primary node. If allowedBC-ListMRDC is included in the CG-ConfigInfo message and this field is not included, the secondary node is not allowed to select SCG band combinations from supportedBandCombinationListNEDC-Only. If allowedBC-ListMRDC is not included in the CG-ConfigInfo message and this field is included, the secondary node is not allowed to select SCG band combinations from supportedBandCombinationList. This field can also be used only in the case of NE-DC.

[0109] (operation example)

[0110] For example, suppose terminal 20 supports one or more frequency band combinations that can be used only for NE-DC. Terminal 20 may also notify the master node of one or more frequency band combinations that can be used only for NE-DC using `supportedBandCombinationListNEDC-Only`, which indicates one or more frequency band combinations that can be used only for NE-DC. The master node, having received information from terminal 20 indicating one or more frequency band combinations that can be used only for NE-DC, may, for example, include the allowedBC-ListNEDC in the CG-ConfigInfo message containing information indicating one or more frequency band combinations that can be used only for NE-DC, and send the CG-ConfigInfo message to the slave node. The slave node may also select any one of the one or more frequency band combinations that can be used only for NE-DC as notified from the master node, include information indicating the selected frequency band combination in `selectedBandCombinationNEDC`, and notify the master node of a CG-Config message containing `selectedBandCombinationNEDC`. According to this method, in the case of NE-DC, the master node and the slave node can set the frequency band combination that can be used only for NE-DC, as indicated by the supportedBandCombinationListNEDC-Only, which is notified from the terminal 20.

[0111] (Proposal 2)

[0112] The following describes another example of signaling for setting NE-DC band combinations between base stations when terminal 20 supports band combinations usable only for NE-DC. This is based on UE capability signaling from terminal 20 indicating band combinations usable only for NE-DC. In the following example, existing signaling is applied to NE-DC only band combinations. An indicator is added to CG-ConfigInfo and CG-Config to indicate whether CG-ConfigInfo and CG-Config are for NE-DC only use, thus enabling the use of existing signaling in the case of NE-DC.

[0113] If terminal 20 supports a frequency band combination that can only be used for NE-DC, for example, terminal 20 notifies the gNB, which is the master node, of the frequency band combination through a dedicated supportedBandCombinationListNEDC-Only capability signaling.

[0114] However, it is not envisioned that the `supportedBandCombinationListNEDC-only` field be used as an inter-node message in MR-DC. That is, it is not envisioned that a master node notified via the `supportedBandCombinationListNEDC-only` field of a frequency band combination usable only for NE-DC would restrict the frequency band combination for a sub-cell group (SCG) to one or more frequency band combinations notified via the `supportedBandCombinationListNEDC-only` field.

[0115] As a solution to the aforementioned problem, for example, one could consider adding a new field to the CG-ConfigInfo IE to adjust the functionality between MR-DC nodes based on one or more band combinations notified from terminal 20 via the supportedBandCombinationListNEDC-only field. When setting NE-DC band combinations between MR-DC nodes based on CG-Config, for example, it is also possible for the slave node to request one or more band combinations within supportedBandCombinationListNEDC-Only, i.e., band combinations other than those permitted by the master node. Furthermore, it is also possible for the slave node to notify the master node of band combinations selected from one or more band combinations within supportedBandCombinationListNEDC-Only, i.e., those permitted by the master node.

[0116] Figure 13 as well as Figure 14 This is a diagram representing an example of a specification change. Figure 13 as well as Figure 14 An example of making changes to the CG-Config message is shown. This CG-Config message can also be a message sent from the secondary node to the primary node.

[0117] For example, such as Figure 13As shown in the example, you can also add the field `useBandCombinationListNEDC-Only` to the CG-Config message for making notifications related to NE-DC.

[0118] Figure 14 Indicates that in such Figure 13 The example shown illustrates the changes made to the CG-Config field descriptions when the CG-Config message is modified.

[0119] like Figure 14 As shown in the example, when the value of the `useBandCombinationListNEDC-Only` field is set to true, the `requestedBC-MRDC` field can also be used to request the setting of frequency band combinations in `supportedBandCombinationListNEDC-Only`, and can also be used to request feature sets that are prohibited from use in the primary node (i.e., outside of `allowedBC-ListMRDC`) for the renegotiation of UE capabilities permitted for SCG settings. The `selectedBandCombination` field can also represent the frequency band combination selected by the secondary node from one or more frequency band combinations permitted through `allowedBC-ListMRDC`. If the frequency band combination and / or feature set selected by the secondary node for SCG is changed (i.e., even if the new selection of frequency band combination and / or feature set is permitted through `allowedBC-ListMRDC`), the secondary node can also notify the primary node of this field. This field can also be used only in the case of NE-DC.

[0120] ( Figure 14 (Example of a variation)

[0121] Furthermore, the band combinations for NE-DC are included not only in the `supportedBandCombinationListNEDC-only` field but also in the `supportedBandCombinationList`. Therefore, to uniquely specify the band combinations for NE-DC, for example, consider sorting one or more band combinations in `supportedBandCombinationList` in ascending order of their original indices within `supportedBandCombinationList`. Then, sort one or more band combinations in `supportedBandCombinationListNEDC-Only` in ascending order of their original indices within `supportedBandCombinationListNEDC-Only`. Based on this, re-index the sorted band combinations in ascending order. However, in this embodiment, the band combinations are sorted in ascending order of their indices, but the sorting method is not limited to ascending order. For example, the band combinations could also be sorted in descending order of their indices.

[0122] For example, let's say the indices assigned to the NE-DC-oriented band combinations in supportedBandCombinationList are #1, #2, and #3, and the indices assigned to the band combinations in supportedBandCombinationListNEDC-Only are #2, #3, and #4. In this case, the band combinations #1, #2, and #3 in supportedBandCombinationList are sorted, then the band combinations #2, #3, and #4 in supportedBandCombinationListNEDC-Only are sorted, and new indices 1, 2, and 3 are assigned to the band combinations #1, #2, and #3 in supportedBandCombinationList, and new indices 4, 5, and 6 are assigned to the band combinations #2, #3, and #4 in supportedBandCombinationListNEDC-Only, thus uniquely specifying the NE-DC-oriented band combinations.

[0123] Figure 20 This is a diagram representing an example of a specification change. Figure 20 The changes to the BandCombinationInfoSN field are shown. For example... Figure 20As shown, the bandCombinationIndex field indicates the position of the band combination in the supportedBandCombinationList. For example, when useBandCombinationListNEDC-Only is set to true, the bandCombinationIndex field can also indicate that one or more band combinations for NE-DC contained in supportedBandCombinationList are sorted in ascending order of their original indices in supportedBandCombinationList. Then, one or more band combinations contained in supportedBandCombinationListNEDC-Only are sorted in ascending order of their original indices in supportedBandCombinationListNEDC-Only. Based on this, any one of the multiple indices reassigned in ascending order for the sorted band combinations is used.

[0124] Furthermore, this embodiment is not limited to this example. For instance, when useBandCombinationListNEDC-Only is set to true, the bandCombinationIndex field can also indicate that one or more band combinations contained in supportedBandCombinationListNEDC-Only are sorted in ascending order according to the original index of the one or more band combinations in supportedBandCombinationListNEDC-Only. Then, one or more band combinations for NE-DC contained in supportedBandCombinationList are sorted in ascending order according to the original index of the one or more band combinations in supportedBandCombinationList. Based on this, any one of the multiple indices reassigned in ascending order for the sorted multiple band combinations is used.

[0125] Figure 15 as well as Figure 16 This is a diagram representing an example of a specification change. Figure 15 as well as Figure 16 This example illustrates a change made to the CG-ConfigInfo message. This CG-ConfigInfo message can also be a message sent from the master node to the slave node.

[0126] For example, such as Figure 15 As shown in the example, you can also add a field like useBandCombinationListNEDC-Only to the CG-ConfigInfo message for making notifications related to NE-DC.

[0127] Figure 16 Indicates that in such Figure 15 The example shown illustrates the changes made to the CG-ConfigInfo field descriptions when the CG-ConfigInfo message is modified.

[0128] like Figure 16 As shown in the example, when the `useBandCombinationListNEDC-Only` field is set to true, the `allowedBC-ListMRDC` field can also represent one or more band combinations from the NE-DC capabilities, from which the secondary node is allowed to select SCG band combinations. Each element in the `allowedBC-ListMRDC` field can also represent one of the band combinations numbered according to `supportedBandCombinationListNEDC-Only`. All MR-DC band combinations represented by this field can also be a superset of one or more MCG bands selected by the primary node. If `allowedBC-ListMRDC` is included in the CG-ConfigInfo message and this field is not included, the secondary node is not allowed to select SCG band combinations from `supportedBandCombinationListNEDC-Only`. If the allowedBC-ListMRDC field is not included in the CG-ConfigInfo message, but is included in the CG-ConfigInfo message, the secondary node is not allowed to select the SCG band combination from the supportedBandCombinationList. This field can also be used only in the case of NE-DC.

[0129] (operation example)

[0130] For example, suppose terminal 20 supports one or more frequency band combinations that can be used only for NE-DC. Terminal 20 uses `supportedBandCombinationListNEDC-Only`, which indicates one or more frequency band combinations that can be used only for NE-DC, to notify the master node that one or more frequency band combinations that can be used only for NE-DC. The master node, having received the information from terminal 20 indicating one or more frequency band combinations that can be used only for NE-DC, may also set the value of the `useBandCombinationListNEDC-Only` field contained in the `CG-ConfigInfo` message to true and send the `CG-ConfigInfo` message to the slave node. The slave node can also receive the CG-ConfigInfo message notified from the master node, check whether the value of the useBandCombinationListNEDC-Only field is set to true, select any one of one or more frequency band combinations that can be used only for NE-DC from allowedBC-ListMRDC, include the information representing the selected frequency band combination in selectedBandCombination, include selectedBandCombination in the CG-Config message, set the value of the useBandCombinationListNEDC-Only field in the CG-Config message to true, and notify the master node of the CG-Config message. According to this method, in the case of NE-DC, the master node and the slave node can set the frequency band combinations that can be used only for NE-DC as indicated by supportedBandCombinationListNEDC-Only notified from slave terminal 20.

[0131] ( Figure 16 (Example of a variation)

[0132] Furthermore, the band combinations for NE-DC are included not only in the NEDC-only field of supportedBandCombinationList, but also in supportedBandCombinationList. Therefore, it is also possible to... Figure 21 The example shows how to modify the `useBandCombinationListNEDC-Only` field. That is, as shown in the example... Figure 21As shown in the example, when the `useBandCombinationListNEDC-Only` field is set to true, the `allowedBC-ListMRDC` field can also represent one or more band combinations from the NE-DC capabilities, from which the sub-node is allowed to select SCG band combinations. Each element in the `allowedBC-ListMRDC` field can also represent a band combination numbered according to `supportedBandCombinationList` and `supportedBandCombinationListNEDC-Only`. All MR-DC band combinations represented by this field can also be a superset of one or more MCG bands selected by the master node.

[0133] Furthermore, NE-DC-oriented band combinations are included not only in the `supportedBandCombinationListNEDC-only` field but also in the `supportedBandCombinationList`. Therefore, to uniquely specify NE-DC-oriented band combinations, one could consider, for example, sorting one or more band combinations in `supportedBandCombinationList` in ascending order of their original indices within `supportedBandCombinationList`, then sorting one or more band combinations in `supportedBandCombinationListNEDC-Only` in ascending order of their original indices within `supportedBandCombinationListNEDC-Only`, and finally re-indexing the sorted band combinations in ascending order.

[0134] Figure 22 This is a diagram representing an example of a specification change. Figure 22 The changes to the BandCombinationInfo field are shown. Figure 22As shown, the bandCombinationIndex field indicates the position of the band combination in the supportedBandCombinationList. For example, when useBandCombinationListNEDC-Only is set to true, the bandCombinationIndex field can also represent the index of any of the multiple indices reassigned in ascending order for the NE-DC-oriented band combinations contained in the supportedBandCombinationList, sorted according to the original index of the band combination in the supportedBandCombinationList, then sorted according to the original index of the band combination in the supportedBandCombinationListNEDC-Only, and finally reassigned in ascending order for the sorted band combinations.

[0135] (Device Structure)

[0136] Next, an example of the functional structure of the base station 10 and terminal 20 performing the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions implemented in the above embodiments. It is also possible that the base station 10 and terminal 20 each possess only a portion of the functions described in the embodiments.

[0137] <Base Station 10>

[0138] Figure 17 This is a diagram illustrating an example of the functional structure of base station 10 in an embodiment of the present invention. (See diagram for example.) Figure 17 As shown, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. Figure 17 The functional structure shown is merely an example. The names of the functional partitions and functional units can be arbitrary, provided that the operations described in the embodiments of this invention can be performed.

[0139] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. Furthermore, the transmitting unit 110 transmits inter-network node messages to other network nodes. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc., to the terminal 20. Furthermore, the receiving unit 120 receives inter-network node messages from other network nodes.

[0140] The setting unit 130 stores the preset setting information and various setting information sent to the terminal 20 into a storage device, and reads them from the storage device as needed. The content of the setting information includes, for example, settings related to the communication of the terminal 20, such as settings for the radio bearer or the sub-cell.

[0141] As described in the embodiment, control unit 140 generates information set within a single frequency band, indicating the lower and upper positions of each component carrier on the frequency axis. Transmitting unit 110 transmits the information generated by control unit 140 indicating the lower and upper positions of each component carrier on the frequency axis to other network nodes. Furthermore, receiving unit 120 can also receive signals from other network nodes requesting a resetting of the frequency band of any one of the set component carriers.

[0142] Furthermore, the control unit 140 determines one or more frequency bands within a single frequency band for configuring one or more LTE component carriers. Referring to a table stored in the configuration unit 130 showing indices for downlink and uplink EN-DC configurations, the control unit 140 determines an index representing the E-UTRA-NR configuration / bandwidth combination set corresponding to the configured frequency bands of the one or more LTE component carriers. The transmitting unit 110 transmits the index determined by the control unit 140 to other network nodes. Additionally, the receiving unit 120 may also receive signals from other network nodes requesting a reconfiguration of the frequency band of any of the configured component carriers. Furthermore, the receiving unit 120 receives from the terminal 20 a supportedBandCombinationListNEDC-Only representing one or more frequency band combinations usable only for NE-DC, and detects information indicating one or more frequency band combinations usable only for that NE-DC. Control unit 140 may, for example, make the allowedBC-ListNEDC contained in the CG-ConfigInfo message include information indicating one or more frequency band combinations that can be used only for NE-DC, and transmission unit 110 may also send the CG-ConfigInfo message to the secondary node.

[0143] Terminal 20

[0144] Figure 18 This is a diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention. (See diagram for example.) Figure 10 As shown, terminal 20 has a sending unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 18 The functional structure shown is merely an example. The names of functional partitions and functional units can be arbitrary, as long as the operations involved in the embodiments of this invention can be performed.

[0145] The transmitting unit 210 generates a transmission signal based on the transmission data and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the receiving unit 220 has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc., transmitted from the base station 10. Additionally, for example, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc., to other terminals 20 as D2D communication, and the receiving unit 220 receives PSCCH, PSSCH, PSDCH, or PSBCH from other terminals 20.

[0146] The setting unit 230 stores various setting information received from the base station 10 or the terminal 20 via the receiving unit 220 into a storage device, and reads it from the storage device as needed. In addition, the setting unit 230 also stores preset setting information. The content of the setting information includes, for example, setting information related to communication of the terminal 20, such as settings for the radio bearer or sub-cell.

[0147] As described in the embodiment, the control unit 240 performs wireless communication using EN-DC (or possibly NR-DC or NE-DC). Furthermore, the control unit 240 receives information related to wireless communication from the base station 10, controls the wireless communication of the terminal 20 based on this information, and reports the necessary information to the base station 10. Alternatively, functional units related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and functional units related to signal reception in the control unit 240 may be included in the receiving unit 220. The control unit 240 sets information indicating one or more frequency band combinations usable only for NE-DC in the supportedBandCombinationListNEDC-Only, and the transmitting unit 210 transmits a signal containing the supportedBandCombinationListNEDC-Only to the base station 10, thereby notifying the base station 10 of one or more frequency band combinations usable only for that NE-DC.

[0148] (Hardware Structure)

[0149] The block diagrams used in the description of the above embodiments ( Figure 17 as well as Figure 18 () represents a block of functional units. These functional blocks (components) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., wired, wireless, etc.) connecting two or more physically or logically separate devices, and using these multiple devices. Functional blocks can also be implemented by combining software with the aforementioned single or multiple devices.

[0150] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that enables sending can also be called a transmitting unit or a transmitter. As mentioned above, the implementation method is not particularly limited for either.

[0151] For example, the base station 10, terminal 20, etc. in one embodiment of this disclosure can function as a computer for processing the wireless communication method of this disclosure. Figure 19 This diagram illustrates an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of this disclosure. The base station 10 and the terminal 20 can be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0152] Additionally, in the following description, the term "device" can be replaced with circuit, equipment, unit, etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured without including any of the devices.

[0153] The functions of the wireless base station 10 and the terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the storage device 1002, which are then processed by the processor 1001 and controlled for communication based on the communication device 1004, or for controlling at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0154] The processor 1001 controls the computer as a whole by enabling the operating system to operate. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the aforementioned control unit 140, control unit 240, etc., may also be implemented by the processor 1001.

[0155] 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 performs various processes based on them. As a program, a program is used that causes the computer to perform at least a portion of the operations described in the above embodiments. For example, Figure 17 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Furthermore, for example... Figure 18 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. While the various processes described above have been executed by a single processor 1001, they can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be mounted on one or more chips. Furthermore, the program can be transmitted from a network via an electrical communication line.

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

[0157] The auxiliary storage device 1003 is a computer-readable recording medium, and may be composed of at least one of the following: optical discs such as CompactDisc ROM (CD-ROM), hard disk drives, flexible disks, optical discs (e.g., compact optical discs, digital multifunction optical discs, Blu-ray discs), smart cards, flash memory (e.g., card, stick, key drives), floppy disk drives, magnetic stripes, etc. The aforementioned storage medium may also be, for example, a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0158] Communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. Communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transmitting and receiving antennas, amplifier units, transmitting and receiving units, transmission path interfaces, etc., may also be implemented by communication device 1004. The transmitting and receiving units can also be physically or logically separated through transmitting and receiving units.

[0159] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED (light-emitting diode) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., touch panel).

[0160] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for information communication. The bus 1007 can be constructed using a single bus or using different buses between devices.

[0161] Furthermore, the base station 10 and the terminal 20 can also be configured with hardware including a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field-programmable gate array (FPGA), etc., and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can be implemented using at least one of these hardware components.

[0162] (Summary of Implementation Methods)

[0163] This specification discloses at least the following base stations, network nodes, and communication methods.

[0164] A network node comprises: a receiving unit, in a terminal, receiving a signal containing information representing a first group and information representing a second group, the first group consisting of one or more frequency band combinations usable only for a specific dual connection, and the second group consisting of one or more frequency band combinations usable for the specific dual connection; a control unit, assigning multiple indices corresponding to the multiple frequency band combinations of the third group, which consists of one or more frequency band combinations of the first group and one or more frequency band combinations of the second group, to uniquely identify each frequency band combination in the multiple frequency band combinations of the third group; and a transmitting unit, transmitting a signal containing information representing the multiple frequency band combinations of the third group, which can be used for communication between network nodes, to other network nodes. The base station includes: a receiving unit, in a terminal, receiving capability information including information representing a first group and information representing a second group, the first group consisting of one or more frequency band combinations that can be used only for a specific dual connection, and the second group consisting of one or more frequency band combinations that can be used for the specific dual connection; a control unit, which, with respect to a third group consisting of multiple frequency band combinations comprising one or more frequency band combinations of the first group and one or more frequency band combinations of the second group, assigns multiple indices corresponding to the multiple frequency band combinations of the third group to determine each frequency band combination among the multiple frequency band combinations of the third group; and a transmitting unit, which transmits a signal containing the indices that can be used for inter-base station communication to other base stations.

[0165] Based on the above structure, the master node, which is notified by the supportedBandCombinationList and the supportedBandCombinationListNEDC-only field of the frequency band combinations available for NE-DC, can specify the frequency band combination for the sub-cell group (SCG) according to the multiple frequency band combinations notified by the supportedBandCombinationList and the supportedBandCombinationListNEDC-only field.

[0166] The network nodes and / or base stations can also be primary nodes and support New Radio (NR) communication, and the other network nodes can also be secondary nodes and support LTE (Long Term Evolution) communication.

[0167] Based on the above structure, in the case of NE-DC, coordination can be carried out between base stations and frequency band combinations can be set.

[0168] The network nodes and / or base stations can also be connected to the 5G Core Network (5GC).

[0169] Based on the above structure, in the case of NE-DC, coordination can be carried out between base stations and frequency band combinations can be set.

[0170] The response signal received from the other networks and / or other base stations may also contain information indicating the frequency band combination selected by the other network nodes from among the multiple frequency band combinations of the third group.

[0171] Based on the above structure, in the case of NE-DC, the master node can set the frequency band combination selected by the slave node.

[0172] A network node-based communication method includes: in a terminal, receiving a signal containing information representing a first group and information representing a second group, the first group consisting of one or more frequency band combinations usable only for a specific dual connection, and the second group consisting of one or more frequency band combinations usable for the specific dual connection; assigning multiple indices corresponding to the multiple frequency band combinations of the third group, which consists of one or more frequency band combinations of the first group and one or more frequency band combinations of the second group, to uniquely identify each frequency band combination in the multiple frequency band combinations of the third group; and transmitting a signal containing information representing the multiple frequency band combinations of the third group, which can be used for communication between network nodes, to other network nodes. A base station-based communication method includes: in a terminal, receiving capability information comprising information representing a first group and information representing a second group, the first group consisting of one or more frequency band combinations usable only for a specific dual connection, and the second group consisting of one or more frequency band combinations usable for the specific dual connection; assigning multiple indices corresponding to the multiple frequency band combinations of the third group, which consists of the one or more frequency band combinations of the first group and the one or more frequency band combinations of the second group, to determine each frequency band combination among the multiple frequency band combinations of the third group; and transmitting a signal containing the indices, capable of being used for inter-base station communication, to other base stations.

[0173] Based on the above structure, the master node, which is notified by the supportedBandCombinationListNEDC-only field that the frequency band combination that can be used only for NE-DC, can specify the frequency band combination for the sub-cell group (SCG) in accordance with one or more frequency band combinations notified by the supportedBandCombinationListNEDC-only field.

[0174] (Supplement to the implementation method)

[0175] While embodiments of the present invention have been described above, the disclosed invention is not limited to these embodiments, and those skilled in the art will understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential in the present invention, and items described in two or more items may be combined as needed, and items described in one item may be applied to items described in other items (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. The operation of multiple functional units may be physically performed by one component, or the operation of one functional unit may be physically performed by multiple components. Regarding the processing described in the embodiments, the order of processing may be interchanged as long as there is no contradiction. For ease of explanation, a functional block diagram has been used to describe the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. According to embodiments of the present invention, software operated by the processor of the base station 10 and software operated by the processor of the terminal 20 according to embodiments of the present invention can be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other suitable storage medium.

[0176] Furthermore, the notification of information is not limited to the methods / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through 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 (Master Information Block (MIB), System Information Block (SIB)), other signals, or combinations thereof). Additionally, RRC signaling may be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0177] The various methods / implementations described in this disclosure can also be applied to at least one of LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems extended based on them. In addition, multiple systems can be used in combination (e.g., a combination of LTE and at least one of LTE-A with 5G).

[0178] The processing procedures, timing, flowcharts, etc., of the various methods / implementations described in this specification may be rearranged as long as they do not contradict each other. For example, regarding the methods described in this disclosure, the elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.

[0179] In this specification, specific operations are assumed to be performed by base station 10, but sometimes they may also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, various operations performed for communication with terminal 20 can obviously be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., consider MME (Mobility Management Entity) or S-GW (Serving-Gateway), but are not limited to these). In the above, the case of one other network node besides base station 10 is illustrated, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

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

[0181] Input and output information can be stored in a specific area (e.g., a storage device) or managed using management tables. Input and output information can be overwritten, updated, or added. Output information can also be deleted. Input information can also be sent to other devices.

[0182] The determination in this disclosure can be made by a value represented by one bit (0 or 1), or by a true or false value (Boolean: true or false), or by a comparison of values ​​(e.g., comparison with a specific value).

[0183] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as referring to instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

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

[0185] The information, signals, etc., described in this disclosure can be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the foregoing description can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0186] Furthermore, the terms used in this disclosure and / or those 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 also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as a carrier frequency, cell, frequency carrier, etc.

[0187] The terms “system” and “network” are used interchangeably in this disclosure.

[0188] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0189] The names used for the above parameters are not limiting names at any point. Furthermore, the formulas, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, and therefore the various names assigned to these various channels and information elements are not limiting names at any point.

[0190] In this disclosure, the terms "base station (BS)," "wireless base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Base stations are sometimes also referred to as macrocells, small cells, femtocells, picocells, etc.

[0191] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH)). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0192] In this disclosure, the terms “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” and “terminal” are used interchangeably.

[0193] Mobile stations are sometimes referred to by those skilled in the art as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handheld devices, user agents, mobile clients, clients, or some other appropriate terms.

[0194] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a mobile body, or the mobile body itself. This mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an IoT (Internet of Things) device such as a sensor.

[0195] Furthermore, the base station in this disclosure can be replaced by a user terminal. For example, various methods / implementations of this disclosure can also be applied to a structure that replaces the communication between the base station and the user terminal with communication between multiple terminals 20 (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal 20 can be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0196] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station can be configured to have the functions of the aforementioned user terminal.

[0197] The terms "determining" and "determining" used in this specification sometimes encompass a variety of operations. For example, "determining" and "determining" can refer to judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), and ascertaining. Furthermore, "determining" and "determining" can refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory). Additionally, "determining" and "determining" can refer to resolving, selecting, choosing, establishing, and comparing. In other words, "determining" and "determining" can refer to certain operations as performing a "determining" or "determining". In addition, "judgment (decision)" can also be replaced with "assuming", "expecting", "considering", etc.

[0198] The terms “connected,” “coupled,” or any variations thereof, mean any direct or indirect connection or combination between two or more elements, and can include cases where there is one or more intermediate elements between the two mutually “connected” or “coupled” elements. The combination or connection between elements can be physical, logical, or a combination thereof. For example, “connection” can also be replaced by “access.” In the context of this disclosure, it is possible to consider two elements being mutually “connected” or “coupled” by using at least one of one or more wires, cables, and printed electrical connections, and as several non-limiting and non-exhaustive examples, by using electromagnetic energy with wavelengths in the wireless frequency domain, microwave domain, and optical (both visible and invisible) domains.

[0199] The reference signal can also be simply referred to as RS (Reference Signal), and depending on the standard applied, it can also be called a pilot.

[0200] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the term "based on" means both "based on only" and "based on at least".

[0201] Any reference to elements using terms such as "first," "second," etc., as used in this disclosure is not intended to impose a comprehensive limitation on the number or order of these elements. These designations are used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements can be used, or that the first element must precede the second element in some form.

[0202] Alternatively, the "unit" in the structure of the above devices can be replaced with "component", "circuit", "equipment", etc.

[0203] In this disclosure, the terms "include," "including," and variations thereof are used, and these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure means not a logical XOR.

[0204] In this disclosure, when articles such as a, an, and the from English are added through translation, this disclosure includes cases where the noun following these articles is in the plural form.

[0205] In this disclosure, the term "A is different from B" can also mean "A and B are not the same." Additionally, the term can also mean "A and B are different from C respectively." Terms such as "separate" and "combined" can also be interpreted as "different."

[0206] The various methods / implementations described in this disclosure can be used individually, in combination, or switched during execution. Furthermore, notification of specific information (e.g., a "It is X" notification) is not limited to explicit notification, but can also be implicit (e.g., by not notifying the user of that specific information).

[0207] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions are not limited to the embodiments described herein. The inventions disclosed herein can be implemented as modifications and variations without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and does not imply any limitation on the inventions disclosed herein.

[0208] This international patent application claims priority to Japanese Patent Application No. 2020-033804, filed on February 28, 2020, and the entire contents of Japanese Patent Application No. 2020-033804 are incorporated herein by reference.

[0209] Explanation of reference numerals in the attached figures

[0210] 10 base stations

[0211] 110 Transmitting Unit

[0212] 120 receiving unit

[0213] 130 Setting Unit

[0214] 140 Control Unit

[0215] 20 User Equipment

[0216] 210 Transmitting Unit

[0217] 220 Receiving Unit

[0218] 230 Setting Unit

[0219] 240 Control Unit

[0220] 1001 processor

[0221] 1002 Storage device

[0222] 1003 Auxiliary storage device

[0223] 1004 Communication device

[0224] 1005 Input Device

[0225] 1006 Output device.

Claims

1. A base station, comprising: The receiving unit, in the terminal, receives capability information including information representing a first group and information representing a second group, wherein the first group consists of one or more frequency band combinations that can be used only for a specific dual connection, and the second group consists of one or more frequency band combinations that can be used for the specific dual connection. The control unit assigns multiple indices corresponding to the multiple frequency band combinations of the third group, which consists of one or more frequency band combinations of the first group and one or more frequency band combinations of the second group, to determine each frequency band combination in the multiple frequency band combinations of the third group. as well as The transmitting unit sends a signal containing the index, which can be used for inter-base station communication, to other base stations. The multiple indices represent the positions in the list of multiple frequency band combinations of the third group. The base station is a master node and supports New Radio (NR) communication. The other base stations are secondary nodes and support Long Term Evolution (LTE) communication. The base station is connected to the 5G Core Network (5GC).

2. The base station as described in claim 1, wherein, The response signal received from the other base stations contains information indicating the frequency band combination selected by the other base stations from among multiple frequency band combinations in the third group.

3. A communication method, which is a base station-based communication method, having: In the terminal, the step of receiving capability information including information representing a first group and information representing a second group, wherein the first group consists of one or more frequency band combinations that can be used only for a specific dual connection, and the second group consists of one or more frequency band combinations that can be used for the specific dual connection; Regarding a third group consisting of multiple frequency band combinations, which is composed of one or more frequency band combinations of the first group and one or more frequency band combinations of the second group, the steps are as follows: assigning multiple indices corresponding to the multiple frequency band combinations of the third group to determine each frequency band combination in the multiple frequency band combinations of the third group; as well as The step of sending a signal containing the index, which can be used for inter-base station communication, to other base stations. The multiple indices represent the positions in the list of multiple frequency band combinations of the third group. The base station is a master node and supports New Radio (NR) communication. The other base stations are secondary nodes and support Long Term Evolution (LTE) communication. The base station is connected to the 5G Core Network (5GC).

Images