Base station device, terminal device, control method, and program for efficient management of connection configuration information

By employing reference and delta configurations for conditional handover and secondary cell management, the method addresses the inefficiencies in existing handover processes, enhancing communication continuity and reducing downtime in wireless communication systems.

WO2024237121A1PCT designated stage expired Publication Date: 2024-11-21KDDI CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/016874
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-02
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In cellular communication systems, the existing handover methods in wireless communication systems lead to prolonged periods of unavailable or insufficient communication quality due to the time gap between the deterioration of communication quality and the initiation of handover processes, which can be mitigated by proactive conditional handover and secondary cell management.

Method used

The implementation of a method using reference and delta configurations to efficiently manage conditional handover and conditional addition or change of secondary cells, where the base station device provides configuration information for multiple cells, allowing the terminal device to pre-configure and switch connections based on predetermined conditions, reducing data overhead and enabling proactive handover.

Benefits of technology

This approach significantly reduces the time of unavailable or insufficient communication by enabling proactive switching and addition of secondary cells, improving communication continuity and efficiency in wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024016874_21112024_PF_FP_ABST
    Figure JP2024016874_21112024_PF_FP_ABST
Patent Text Reader

Abstract

This base station device provides, to a connected terminal device, information for generating configuration information relating to a plurality of cells for conditional handover (CHO) or conditional secondary cell addition or change (CPAC) in the terminal device, the information including: a reference configuration which is common to two or more cells among the plurality of cells, and to which identification information for uniquely identifying the reference configuration is assigned; a delta configuration unique to each of the two or more cells; and identification information of the reference configuration with which the delta configuration should be combined. If at least one of the reference configuration and the delta configuration should be deleted or changed, the base station device specifies at least one of the reference configuration and the delta configuration and instructs the terminal device to delete or change the same.
Need to check novelty before this filing date? Find Prior Art

Description

Base station device, terminal device, control method, and program for efficient management of connection setting information

[0001] The present invention relates to a technique for efficiently managing wireless connection settings.

[0002] In cellular communication systems, handover techniques are used to ensure communication continuity by switching the connection destination of a terminal device in response to factors such as the terminal device's movement. A standard handover technique involves initiating a handover configuration process on the core network side after the communication quality of the terminal device's currently connected wireless link deteriorates, and then transmitting an instruction message from a base station device to the terminal device. However, this technique requires time for the process from the actual deterioration of communication quality to the transmission of the handover instruction, which can result in a prolonged period of communication inability or insufficient communication quality. In response to this, the Third Generation Partnership Project (3GPP (registered trademark)) is discussing a technique in which this configuration process is performed in advance, and the terminal device switches the connection destination cell without receiving an instruction message from a base station device when certain conditions are met (see Non-Patent Document 1). The certain conditions include, for example, when the wireless quality of a neighboring cell becomes better than the wireless quality of the currently connected cell by a predetermined level or more, or when the wireless quality of the currently connected cell falls below a predetermined value. This method significantly reduces the time during which communication is unavailable or communication quality is insufficient because the handover setup process in the core network is completed before a deterioration in communication quality that would require handover occurs. This type of handover is called conditional handover, or CHO.

[0003] Similarly, in a multi-connectivity (MC) or the like in which a terminal device is connected to multiple cells, a setting process is performed in advance, and when a predetermined condition is satisfied in the terminal device, the terminal device can add or change a secondary cell without receiving an instruction message from the base station device. Note that, hereinafter, this conditional addition or change of a secondary cell may be referred to as CPAC.

[0004] 3GPP TR38.874, V16.0.0, December 2018

[0005] In the study of the 3GPP Release 18 standard, it was agreed that in the above-mentioned configuration process, a configuration process using a common reference configuration for multiple candidate cells and a delta configuration that specifies a configuration value different from the reference configuration for each candidate cell is performed. However, the execution procedure of such a configuration process has not been clarified, and it is necessary to define an efficient procedure.

[0006] The present invention provides a method for efficiently performing configuration processing using a reference configuration and a delta configuration for conditional handover in a terminal device or for adding or changing a conditional secondary cell.

[0007] A base station device according to one aspect of the present invention has an acquisition means for acquiring information for generating configuration information regarding multiple cells for conditional handover (CHO) or conditional secondary cell addition or change (CPAC) in a connected terminal device, the information including a reference configuration common to two or more of the multiple cells and assigned with identification information that uniquely identifies the reference configuration, a delta configuration unique to each of the two or more cells, and the identification information of the reference configuration to which the delta configuration should be combined, a provision means for providing the information and conditions for executing the CHO or the CPAC to the terminal device, and an instruction means for specifying at least one of the reference configuration and the delta config and instructing the terminal device to delete or change at least one of the reference configuration and the delta config when at least one of the reference configuration and the delta config should be deleted or changed.

[0008] According to another aspect of the present invention, a terminal device includes an acquisition means for acquiring information for generating configuration information for multiple cells for conditional handover (CHO) or conditional secondary cell addition or modification (CPAC) from a base station device to which it is connected, the information including a reference configuration common to two or more of the multiple cells and a delta configuration specific to each of the two or more cells, and conditions for executing the CHO or the CPAC; a generation means for generating configuration information for communication in at least one of the two or more cells using the delta configuration and the reference configuration when an instruction to delete or modify specifying at least one of the reference configuration and the delta configuration is received; an execution means for executing the deletion or modification of at least one of the specified reference configuration and the delta configuration when the instruction to delete or modify specifying at least one of the reference configuration and the delta configuration is received; and an execution means for executing the CHO or the CPAC using the generated configuration information when the condition is met.

[0009] According to the present invention, it is possible to efficiently perform configuration processing using a reference config and a delta config regarding conditional handover in a terminal device or the addition or change of a conditional secondary cell.

[0010] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same or similar elements are designated by the same reference numerals.

[0011] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments of the present invention, and together with the description are used to explain the principles of the present invention. FIG. 1 is a diagram showing an example of the configuration of a wireless communication system. FIG. 2 is a diagram showing an example of the flow of processing executed in the wireless communication system. FIG. 3 is a diagram showing an example of the flow of processing executed in the wireless communication system. FIG. 4 is a diagram showing an example of the flow of processing executed in the wireless communication system. FIG. 5 is a diagram showing an example of the flow of processing to update setting information. FIG. 6 is a diagram showing an example of the flow of processing to determine the appropriateness of setting information. FIG. 7 is a diagram showing an example of the flow of processing to determine the appropriateness of setting information. FIG. 8 is a diagram showing an example of the hardware configuration of an MN, an SN, and a terminal device. FIG. 9 is a diagram showing an example of the functional configuration of a terminal device. FIG. 10 is a diagram showing an example of the functional configuration of an MN. FIG. 11 is a diagram showing an example of the functional configuration of an SN.

[0012] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all combinations of features described in the embodiments are necessarily essential to the invention. Two or more of the features described in the embodiments may be combined in any desired manner. Furthermore, the same reference numerals are used to designate identical or similar components, and redundant descriptions will be omitted.

[0013] 1 shows an example of the configuration of a wireless communication system according to this embodiment. This wireless communication system is a cellular communication system that complies with a cellular communication standard, such as the fifth generation (5G) standard defined by the Third Generation Partnership Project (3GPP (registered trademark)). Note that this is just one example, and the following discussion can be applied to any system in which a terminal device can continue communication while switching the cell to which it is connected.

[0014] In the wireless communication system of Fig. 1, a base station device provides wireless communication services to a terminal device 151. The terminal device 151 can be connected to two or more cells in parallel. Of these two or more cells, the cell that controls the communication of the terminal device 151 is called a primary cell, and the cell that connects to the terminal device 151 under the control of the base station device of the primary cell (master node: MN100) is called a secondary cell. Note that in this embodiment, for simplicity of explanation, it is assumed that the terminal device 151 is connected to MN100 and additionally connects to a secondary cell. The example of Fig. 1 shows an example in which cells that are candidate connection destinations as secondary cells for the terminal device 151 are provided by two base station devices (secondary nodes: SN101 and SN102).

[0015] A base station device may be composed of a central unit (CU) and a distributed unit (DU). The DU includes, for example, an antenna and radio frequency signal processing functions, and functions as an interface for transmitting and receiving radio signals to and from terminal devices. Each DU forms at least one cell. Meanwhile, the CU accommodates one or more DUs and is configured to control communications performed by those DUs. For example, the CU generates configuration information when a terminal device connects to each DU and notifies the terminal device of the information. In the example of FIG. 1, SN 101 functions as a CU, and DUs 111 to 113 can provide cells 131 to 133, respectively. SN 102 also functions as a CU, and DUs 121 to 123 can provide cells 141 to 143, respectively. Terminal device 151 is configured to connect to at least one of these cells and receive radio signals in the connected cell to receive wireless communication services. In addition, the terminal device 151 connects to a base station device that constitutes a cell that includes the location where the terminal device 151 itself is located, and in the following, this will be referred to as ``connecting to a cell (provided by that base station device).''

[0016] In this embodiment, pre-configuration for adding or changing a secondary cell is performed when the terminal device 151 establishes a connection with the primary cell, or when the wireless quality in the currently connected secondary cell deteriorates to a certain degree, for example. The pre-configuration state here refers to a state in which the settings of parameters, etc., for the case in which the terminal device 151 connects to a candidate cell to which the terminal device 151 is to connect have been completed, while the terminal device 151 does not actually establish a connection to that cell. The pre-configuration includes conditions for connecting to a cell for changing or adding a cell to which the terminal device 151 is to connect, and when the terminal device 151 determines that the conditions are satisfied, the terminal device 151 establishes synchronization with the new cell to which the terminal device 151 is to connect and attempts a connection. When changing the secondary cell to which the terminal device 151 is to connect, the terminal device 151 performs a disconnection process from the secondary cell from which the terminal device 151 is connected. Using such pre-configuration, the terminal device 151 autonomously switches or adds a secondary cell when it determines that the conditions are satisfied is called conditional secondary cell addition or change (CPAC). The terminal device 151 autonomously switches the primary cell to which the terminal device 151 is to connect when it determines that the conditions are satisfied is called conditional handover (CHO). Although the following embodiment will be described with a focus on CPAC, it can also be applied to CHO. That is, the following discussion can be applied to CHO by replacing the CPAC conditions with the CHO conditions and the CPAC presettings with the CHO presettings. Note that the types of messages may differ between CHO and CPAC, but those skilled in the art can substitute appropriate messages as appropriate.

[0017] When CPAC is performed, the connected MN 100 transmits a secondary cell addition request message (SGNB Addition Request) to another base station device that provides a cell that is a candidate for the secondary cell to be added or changed. Note that this secondary cell addition request may be initiated, for example, in response to a predetermined message (e.g., SGNB Change Required) being notified to the connected MN 100 from the base station device that provides the secondary cell to which the terminal device 151 is currently connected. In this case, the MN 100 may transmit the above-described secondary cell addition request in response to receiving the predetermined message. Then, another base station device (hereinafter, this base station device may be referred to as a "candidate base station") that provides a cell that is a candidate for the secondary cell to be added or changed includes information such as communication parameters to be used when the terminal device 151 adds or changes the secondary cell in a response message to that message (SGNB Addition Request Acknowledge), and transmits this to MN 100. Here, the candidate base station stores the transmitted information such as communication parameters as preconfigured information. In addition, MN 100 or the candidate base station determines the conditions that must be met when adding or changing the secondary cell. Then, MN 100 notifies the terminal device 151 of the preconfigured information including information on communication parameters to be used when adding or changing the secondary cell with the cell provided by the candidate base station as the secondary cell, and the conditions for such connection. This notification can be performed, for example, using a radio resource control (RRC) message. In one example, the pre-configuration information is notified to the terminal device 151 by an RRC Reconfiguration message.

[0018] Here, the pre-configuration information may include reference configuration information (Reference Config) that serves as a reference, and configuration information (Delta Config) that is the difference between each configuration information of a secondary cell candidate and the reference config. The Reference Config is configuration information common to multiple cells, and the Delta Config is information about the part of the configuration information of each cell that differs from the Reference Config. In other words, the Delta Config is configuration information unique to each cell. When the terminal device 151 receives the Reference Config and the Delta Config, it uses the setting values ​​of the configuration items included in the Delta Config. On the other hand, the terminal device 151 uses the setting values ​​specified in the Reference Config for configuration items not included in the Delta Config that are specified to be maintained in the Reference Config (specified as "Need M"), and may not use the setting values ​​of the Reference Config for other configuration items. Furthermore, for configuration items that are not included in the delta config and that are specified in the reference config as requiring that an operation related to the configuration item be performed only once (designated as "Need N"), the terminal device 151 can be notified from the MN 100 to the terminal device 151 of information for determining whether to perform the operation related to the configuration item only once in accordance with the setting value of the reference config, or to interpret this as an intention to delete the setting value of the reference config and determine not to perform the operation related to the configuration item. In this case, the MN 100 and the terminal device 151 may be configured in advance to perform one of the operations in a fixed manner, without requiring notification of this information. By using such a combination of the reference config and the delta config, it is possible to reduce the amount of data of configuration information notified to the terminal device 151.That is, the configuration information common to N cells is notified to the terminal device 151 only once for the multiple cells as the reference config, and the configuration information specific to each cell is notified to each cell by the delta config, thereby omitting notification of the portion of the configuration information for the (N-1) cells that corresponds to the reference config, thereby reducing the amount of data of the notified configuration information. Furthermore, the MN 100 can use the configuration information of one of the multiple candidate cells as the reference config, or use the configuration information of the serving cell currently being used for communication (if multiple cells are used as serving cells, any one of the multiple cells) as the reference config, or use the configuration information of a cell other than the candidate cell or the serving cell as the reference config. In this case, the MN 100 can notify the terminal device 151 of information for identifying which cell's configuration information to use as the reference config. As an example, when MN100 uses the configuration information of one of multiple serving cells (or candidate cells) as the reference configuration, it can efficiently specify the configuration information to be used as the reference configuration using existing identification information such as CellGroupId, SCellIndex, and condReconfigId that are uniquely assigned to the configuration information.

[0019] As described above, the delta config is composed of the configuration items in each cell's configuration information that include different setting values ​​from the reference config. Therefore, the smaller the difference between each cell's configuration information and the reference config, the fewer the number of configuration items included in the delta config, and the smaller the overall data volume of the delta config. On the other hand, if there is a large discrepancy between each cell's configuration information and the reference config, the number of configuration items included in the delta config will increase, and the amount of data will also increase. In some cases, almost all of the configuration items in the reference config will be replaced by the delta config's configuration items, which may increase the overall data volume of the configuration information.

[0020] In this embodiment, in consideration of such circumstances, multiple reference configurations can be set, and in addition to the multiple reference configurations, the terminal device 151 is notified of information indicating which of the multiple reference configurations the delta configuration for each candidate cell is based on. For example, the MN 100 notifies the terminal device 151 of information in the following format: First reference configuration (reference configuration ID = 1) Second reference configuration (reference configuration ID = 2) Information on cell 131 (first delta configuration, reference configuration ID = 1) Information on cell 132 (second delta configuration, reference configuration ID = 1) ... Information on cell 142 (fifth delta configuration, reference configuration ID = 2) Information on cell 143 (sixth delta configuration, reference configuration ID = 2) Here, the reference configuration ID is identification information that can uniquely identify one reference configuration. Of these pieces of information, information on the first reference config and the second reference config is notified to the terminal device 151 as information elements such as ReferenceConfigAddModlist. Furthermore, information on the delta config specific to each cell is notified to the terminal device 151 as a CondReconfigToAddMod information element. The CondReconfigToAddMod information element is prepared, for example, for each candidate cell. The CondReconfigToAddMod information element includes identification information (condReconfigId) specific to that information element, and, for each cell, information indicating a cell identifier, a reference config ID, a condition under which CPAC should be performed, and the delta config of that cell. Note that CPAC refers to the conditional addition and change of a secondary cell, but different conditions may be prepared for the addition of a secondary cell and the change of a secondary cell. For example, the terminal device 151 can extract a first reference configuration from the received information regarding the cell 131 using the information with reference configuration ID = 1, and generate configuration information for the cell 131 based on the first reference configuration and the first delta configuration.Similarly, the terminal device 151 can generate configuration information for cell 143 using the second reference configuration and the sixth delta configuration. This configuration eliminates the disadvantage of using a common reference configuration, even when the configuration information for connection between cell 131, cell 132, and cell 143 is significantly different from that between cell 131 and cell 132. Note that the reference configuration itself may be used as the configuration information for any of the cells. In other words, the configuration information of any of the cells may be used as the reference configuration. For example, the configuration information of cell 131 may be used as the first reference configuration, and / or the configuration information of cell 143 may be used as the second reference configuration. In this case, for example, MN 100 notifies terminal device 151 of information in the following format: First reference config (cell 131, reference config ID = 1) Second reference config (cell 143, reference config ID = 2) Information of cell 132 (second delta config, reference config ID = 1) ... Information of cell 142 (fifth delta config, reference config ID = 2) Note that this is just one example, and information in other formats may be notified to terminal device 151 as long as terminal device 151 is able to configure the configuration information of each cell. Note that the configuration information of each cell includes not only communication parameters but also CPAC conditions (condExecutionCond, conditions for adding / changing a cell, and an identifier for specifying separately defined execution conditions).

[0021] In one example, a different reference configuration may be used for each SN, or a common reference configuration may be used for multiple SNs and a different reference configuration may be used for one or more other SNs. Also, multiple reference configurations may be used within one SN. Such a group of cells using a common reference configuration may be determined, for example, by the MN 100 to which the terminal device 151 is connected, or may be determined by the SN, or such a group of cells may be determined between the MN 100 and the SN 101 and SN 102. Also, a group using a common reference configuration may be determined in advance.

[0022] Next, several examples of the flow of the process of determining the reference config and the delta config will be described.

[0023] First, as a first example, a case where MN 100 determines a reference configuration will be described. Once MN 100 determines a reference configuration, it notifies the SN that provides the cell that uses that reference configuration of the reference configuration. The SN determines the difference between the setting information in each cell that it provides and the notified reference configuration as the delta configuration of that cell and notifies MN 100. Note that the SN may reject the use of the notified reference configuration. In this case, the SN may notify MN 100 of another reference configuration to be used instead of the notified reference configuration and a delta configuration created based on the other reference configuration. Note that MN 100 may notify the SN of identification information (reference configuration ID) of the reference configuration to be notified to the SN and one or more identification information that can be assigned to another reference configuration if use of the reference configuration is rejected. In this case, when notifying the MN 100 of the above-mentioned other reference configuration, the SN can notify the MN 100 of the identification information assigned to the other reference configuration.

[0024] For example, as shown in FIG. 2, MN 100 sends an SgNB addition request to SN 101 including a first reference configuration (Reference config #1) (S201). SN 101 accepts the use of this first reference configuration and notifies each subordinate DU (DU 111 to DU 113) of this first reference configuration to generate a delta configuration (S202). Each DU prepares configuration information for UE 151's connection to its own device and notifies SN 101 of the delta configuration, which is the difference information between that configuration information and the first reference configuration (S205). SN 101 may request each DU to notify it of the configuration information for UE 151's connection, and the DU may notify SN 101 of the configuration information. In this case, SN 101 may generate a delta config for each DU from the first reference config and the notified setting information. When SN 101 acquires the delta config for each DU, it may notify MN 100 of the delta config information (S207). Note that SN 101 may notify MN 100 that it is using the first reference config notified by MN 100. Note that the notification from SN to MN 100 may be performed, for example, by using an information element in an SgNB addition request ACK. For example, information may be notified by a CG-CandidateList. Furthermore, a newly defined information element other than the CG-CandidateList may be used. This information exchange may be performed by any message that can be used for information exchange via the Xn interface between MN 100 and SN.

[0025] On the other hand, MN 100 sends an SgNB addition request to SN 102, including a second reference configuration (Reference config #2) (S203). SN 102 may reject the use of this second reference configuration and notify each subordinate DU (DU 121 to DU 123) of the third reference configuration to generate a delta configuration (S204). Each DU prepares configuration information for UE 151's connection to its own device and notifies SN 102 of the delta configuration, which is the difference information between that configuration information and the third reference configuration (S206). In this case, as in the above case, each DU may notify SN 102 of the configuration information itself, and SN 102 may generate a delta configuration using the third reference configuration. When the SN 102 acquires the delta config for each DU, it can notify the MN 100 of the delta config information (S208). In this case, the SN 102 notifies the MN 100 of the third reference config that is being used instead of the second reference config.

[0026] In addition, information transmission and reception between the CU and DU of the SN may be performed using a CPAC-related information element (IE) included in a UE context setup request, a UE context setup request response, a UE context release request, a UE context release command, a UE context release complete, a UE context modification request, or a UE context modification response. In addition, in an existing F1 interface message, a new IE for communication configuration using a reference configuration may be prepared, or a new F1 interface message may be prepared. This also applies to the following description. Information from a CU to a DU may be notified using a CU to DU RRC information element, and information from a DU to a CU may be notified using a DU to CU RRC information element. When multiple cells are formed in one DU, information specifying which cell the information transmitted and received relates to may also be transmitted and received between the DU and the CU.

[0027] When MN 100 acquires the delta config for each cell that is a candidate cell for the secondary cell in this manner, it notifies UE 151 of the delta config and information on the reference config (S209). In the example of Fig. 2, a first reference config related to configuration information for cells under SN 101, a third reference config related to configuration information for cells under SN 102, and the delta config for each cell are notified to UE 151. Here, as described above, each delta config is notified to UE 151 along with information (reference config ID) indicating which reference config it is associated with. In the example of Fig. 2, UE 151 is notified that the delta configs of DU 111 to DU 113 are associated with the first reference config, and that the delta configs of DU 121 to DU 123 are associated with the third reference config.

[0028] Next, as a second example, an example in which an SN determines a reference configuration will be described. As shown in Figure 3, MN 100 sends an SgNB addition request to SN 101 and SN 102. In this SgNB addition request, MN 100 may notify the SNs that a reference configuration and a delta configuration should be generated. At this time, MN 100 may also notify each SN of a usable reference configuration ID. This may define the maximum number of reference configurations that can be set in an SN. In the example of Figure 3, reference configuration IDs = 1 and 2 are notified to SN 101 (S301), and reference configuration IDs = 3 and 4 are notified to SN 102 (S304). 3, the reference configuration ID is notified from MN 100 to ensure that the MN 100 and the SNs have the same understanding of the reference configuration ID and to prevent the reference configuration IDs used in each SN from overlapping. However, this is just an example, and the same ID may be set in multiple SNs. For example, the reference configuration ID may be specified by combining identification information indicating the SN with its ID. In other words, the reference configuration of SN 101 with reference configuration ID=1 and the reference configuration of SN 102 with reference configuration ID=1 may be different configurations.In this case, the following information is stored: Reference config of SN=101: First reference config (reference config ID=1) Second reference config (reference config ID=2) Reference config of SN=102: Third reference config (reference config ID=1) Delta config of SN=101: Information of cell 131 (first delta config, reference config ID=1) Information of cell 132 (second delta config, reference config ID=1) Information of cell 133 (third delta config, reference config ID=2) Delta config of SN=102: Information of cell 141 (fourth delta config, reference config ID=1) Information of cell 142 (fifth delta config, reference config ID=1) Information such as the following information about cell 143 (sixth delta config, reference config ID = 1) is notified from MN 100 to terminal device 151 (S310). When acquiring configuration information about cell 132, for example, terminal device 151 extracts a first reference config based on SN = 101 and reference config ID = 1. Then, terminal device 151 can acquire configuration information about cell 132 using the first reference config and the second delta config. On the other hand, when acquiring configuration information about cell 143, for example, terminal device 151 extracts a third reference config based on SN = 102 and reference config ID = 1. Then, terminal device 151 can acquire configuration information about cell 143 using the third reference config and the sixth delta config. In the above example, a single reference configuration is identified by combining the identification information of each SN and the reference configuration ID, but this is not limiting. For example, more generally, a group of cells may be defined, and a single reference configuration may be identified based on the identification information of the group of cells and the reference configuration ID. Here, the group of cells may be multiple cells under multiple SNs.Here, a cell under one SN may belong to one group, or one or more cells under one SN may belong to a first group and another cell under that SN may belong to a second group. Even in this configuration, two or more reference configurations set in two or more groups can be identified using only the reference configuration ID, but by using the reference configuration ID in combination with the group identification information, it is possible to uniquely identify one reference configuration.

[0029] Note that a maximum number of SNs that provide candidate cells may be specified in the MN 100. In this case, when configuration information for cells provided by SNs exceeding the maximum number is to be configured, the MN 100 can instruct the SNs to use normal configuration information (full configuration) as is for the SNs exceeding the maximum number without using the reference configuration and delta configuration. In this case, the SN can instruct its subordinate DU to provide the full configuration instead of the delta configuration.

[0030] In addition, when the use of overlapping reference configuration IDs is permitted among multiple SNs (or groups of cells), for example, each SN may be notified of a numerical value indicating the maximum number of reference configurations that can be set in that SN. In addition to the reference configuration IDs notified as described above so that separate reference configuration IDs are used among multiple SNs, a numerical value indicating the maximum number of reference configurations that can be set in each SN may also be notified. As an example, the MN 100 may retain the maximum number of reference configurations that can be set in the terminal device 151 and determine the number of reference configurations that can be further set in the terminal device 151 from the number of reference configurations currently being set (notified) and this maximum number. Then, based on this number, the MN 100 may determine the above-mentioned maximum number to be notified to each SN. Alternatively, the MN 100 may notify the SNs only that a reference configuration and a delta configuration should be generated, without notifying the numerical value indicating the maximum number or the reference configuration ID. For example, if the maximum number of reference configurations is predetermined in the SN, it is sufficient to be notified that only the reference configuration and delta configuration should be generated.

[0031] Each SN sets a reference configuration within the maximum number of reference configurations that can be set for each SN. The SN can then notify each of its subordinate DUs of the reference configuration and instruct them to generate a delta configuration (S302, S303, S305). The DU generates a delta configuration based on the notified reference configuration and notifies the SN of the generated delta configuration (S306, S307). The SN aggregates the delta configurations generated in each DU and notifies the MN 100 of all the set reference configurations and delta configurations (S308, S309). The delta configuration is notified to the MN 100 together with information indicating which reference configuration it is associated with. For example, SN 101 notifies MN 100 that the delta configs of DU 111 and DU 112 are associated with the reference config with reference config ID = 1, and that the delta config of DU 113 is associated with the reference config with reference config ID = 2. In the above example, the SN generates a reference config, notifies the DU of the generated reference config, and the DU generates the delta config, but this is not limiting. For example, the SN may request the DU to provide configuration information to be notified to the terminal device 151, aggregate that configuration information, and generate a reference config based on that configuration information. For example, the SN may generate a reference config that minimizes the total data volume of the delta config and the reference config using a common reference config for multiple pieces of configuration information.

[0032] It should be noted that the SN does not need to use up all of the notified reference config IDs. In the example of Fig. 3, SN 102 can use reference config IDs = 3 and 4, but it can use only one reference config (reference config ID = 3) and generate delta configs for DU121 to DU123 based on this reference config. SN 102 then notifies MN 100 of all of these delta configs and reference configs, and that all delta configs are associated with the reference config with reference config ID = 3. MN 100 then notifies terminal device 151 of the acquired reference configs and delta configs, and information indicating which reference config each delta config is associated with.

[0033] As a third example, if MN 100 does not have a reference config, it can instruct SN 101 to generate a reference config and a delta config, and if it does have a reference config, it can notify SN 101 of the reference config and instruct SN 101 to generate a delta config. For example, as shown in Fig. 4, while MN 100 does not have a reference config, MN 100 instructs SN 101 to generate a reference config and a delta config (S401). Then, SN 101 can generate a reference config within its own device, and instruct DU 111 to DU 113 to generate a delta config (S402). Note that the example in Fig. 4 shows an example in which SN 101 generates a reference config, notifies DU 111 to DU 113 of the generated reference config, and DU 111 to DU 113 generate a delta config, but this is not limiting. For example, SN 101 may request DUs 111 to 113 to provide configuration information to be notified to terminal device 151, and aggregate the configuration information to generate a reference config. In either case, SN 101 notifies MN 100 of the acquired reference config and the delta config for the cell formed by each DU (S403, S404).

[0034] Thereafter, MN 100 instructs SN 102 to generate a delta config (S405). In this case, since MN 100 has the reference config notified by SN 101, it can notify SN 102 of this reference config and instruct it to generate a delta config. SN 102 may either accept or reject the use of this reference config. In the example of FIG. 4, it is assumed that SN 102 rejects the use of this reference config and decides to use another reference config. In this case, SN 102 notifies DU 121 to DU 123 of this other reference config (S406), and DU 121 to DU 123 generate delta configs based on this other reference config. Then, SN 102 collects delta configs from DU 121 to DU 123 (S407) and can notify MN 100 of the delta configs (S408). SN 102 can, for example, collect configuration information from each of DU 121 to DU 123 and generate a delta config candidate from the difference between the configuration information and the reference config notified by MN 100. SN 102 can then generate another reference config if the amount of data in the delta config exceeds a predetermined value. This is just one example, and the criteria for SN 102 to generate another reference config can be defined arbitrarily. MN 100 notifies terminal device 151 of the reference config it holds and the collected delta config (S409).

[0035] As described above, after the processing of Fig. 4 is completed, MN 100 will hold the first reference configuration used by SN 101 and the second reference configuration used by SN 102. After this, when MN 100 is to pre-configure yet another cell as a secondary cell candidate, it can notify the SN of the first reference configuration and the second reference configuration and instruct the SN to generate a delta configuration. In this way, MN 100 can notify the SN of all of the reference configurations it holds and instruct the SN to generate a delta configuration. However, this is just one example, and MN 100 may, for example, notify the SN of only a portion of the reference configurations it holds and instruct the SN to generate a delta configuration.

[0036] As described above, the terminal device 151 can acquire the reference config and the delta config for multiple cells that are candidates for addition or change as secondary cells. The MN 100 may transmit an instruction to the terminal device 151 to activate only some of these multiple cells. For example, as the terminal device 151 moves, the MN 100 may activate pre-configuration for cells within a predetermined distance from the location of the terminal device 151 and disable the pre-configuration for other cells. The terminal device 151 may, for example, recreate and store configuration information for cells for which pre-configuration is enabled, using the reference config and the delta config. Note that the terminal device 151 may measure the radio quality for activated cells and not measure the radio quality for non-activated cells. The MN 100 can specify the cells to be activated / deactivated, for example, using identification information (condReconfigId) unique to each information element for each cell. When multiple cells using a common reference configuration are enabled / disabled collectively, the reference configuration ID of the reference configuration may be specified. For example, the following information may be notified to the terminal device 151: Reference Config ID = 1: Disabled Reference Config ID = 2: Partially enabled condReconfigId = A: Enabled condReconfigId = B: Disabled Reference Config ID = 3: Fully enabled In the above example, when a reference configuration is partially enabled, information indicating whether each delta configuration using that reference configuration is enabled or disabled is specified, and when a reference configuration is fully enabled, all delta configurations using that reference configuration are considered to be enabled. However, this is not limited to this, and the reference configuration can be set to "enabled" in both cases where only a portion of the delta configuration that uses the reference configuration is enabled and where all of the delta configuration is enabled, and in that case, the enabled / disabled status can always be indicated individually for each delta configuration that uses that reference configuration.

[0037] The terminal device 151 measures the radio quality of the (enabled) cell to be measured, and in response to determining that the conditions for adding / changing a secondary cell are satisfied for a specific cell, notifies the MN 100 of an RRC Reconfiguration Complete message and accesses the specific cell. That is, the terminal device 151 can execute a random access procedure to access the specific cell.

[0038] Note that the terminal device 151 maintains the configuration information regarding the candidate cell even after the secondary cell is added or changed, but it is assumed that this configuration information should be deleted, for example, if the terminal device 151 moves far away from the candidate cell. Also, it can be assumed that at least one of the reference configuration and the delta configuration will need to be changed, for example, depending on whether a certain amount of time has passed since the reference configuration and the delta configuration were notified to the terminal device 151. Such deletion or change of the configuration is performed, for example, by an instruction from the MN 100.

[0039] The MN 100 or SN connected to the terminal device 151 may decide to delete the reference config set in the terminal device 151, for example, in response to a change or addition of a secondary cell candidate, or in response to the setting of new communication parameters based on the reference config and delta config. Hereinafter, the MN 100 or SN connected to the terminal device 151 may be referred to as the "network." Note that a network node other than the MN 100 or SN may decide to delete the reference config set in the terminal device 151, and the deletion instruction may be transmitted to the terminal device 151 via the MN 100 or SN.

[0040] For example, the network may decide to delete one of the reference configurations when the number of configured reference configurations reaches (exceeds) the maximum number. The network may, for example, send an instruction to the terminal device 151 to delete the oldest reference configuration. The network may also determine the reference configuration to delete based on the wireless quality measurement results in the terminal device 151. For example, the network may identify the maximum wireless quality of the cells using each of multiple reference configurations and decide to delete the reference configuration with the lowest maximum value (or the reference configuration that is not used in a cell whose wireless quality can be determined to be good). The network may also delete delta configurations for cells that are more than a predetermined distance away from the location of the terminal device 151, for example, as the terminal device 151 moves, and may decide to delete the specific reference configuration when all delta configurations referencing that specific reference configuration have been deleted. The network may also instruct the terminal device 151 that has set a reference configuration to delete the reference configuration, and have the terminal device 151 select which reference configuration to delete. In this case, the terminal device 151 may select and delete a reference configuration, and notify the network of the reference configuration ID of the deleted reference configuration.

[0041] The network removes cells that have generated delta configurations using the reference configuration to be deleted from the secondary cell candidates for the terminal device 151. For example, the MN 100 may send an SgNB Release Request to an SN that has a cell using the reference configuration to be deleted, instructing it to delete configuration information related to the cell. Note that when a specific reference configuration is deleted and delta configurations that reference the specific reference configuration are maintained, all delta configurations are also deleted. Furthermore, the cell corresponding to the delta configuration is removed from the secondary cell candidates. Note that when a specific reference configuration is deleted and delta configurations that reference the specific reference configuration are maintained, the delta configuration may be reconfigured based on a different reference configuration. Note that in this case, the MN 100 may specify a different reference configuration and instruct an SN that has a cell using the delta configuration to update its delta configuration. In this case, the SN may be forced to use a different reference configuration. That is, the SN may not be allowed to refuse to use the different reference configuration. For example, assume that reference configurations with reference configuration IDs = 1 and 2 are being used in one SN, and it is decided to delete the reference configuration with reference configuration ID = 2. In this case, the MN 100 may instruct the SN to reconfigure a delta configuration based on the reference configuration with reference configuration ID = 2 using the reference configuration with reference configuration ID = 1. It is possible to prevent the deletion of a reference configuration that is being used in any cell.

[0042] Furthermore, even when the terminal device 151 stops using the secondary cell or performs a handover of the primary cell, the reference config and delta config may not be deleted unless there is an explicit instruction from the MN 100. However, this is not limited to this. For example, the reference config generated in the handover source MN 100 may be deleted. On the other hand, the reference config generated in the SN may not be deleted. In this case, the handover source MN 100 may notify the handover target MN 100 of the reference config ID and the corresponding contents of the reference config, the SN that generated the reference config, information on candidate cells for the secondary cell, etc. Furthermore, the handover source MN 100 may notify the handover target MN 100 of information on the delta config that references the reference config (the delta config ID, the delta config contents, and the conditions for adding / changing a cell corresponding to the delta config). This eliminates the need to re-execute the configuration process for adding / changing the secondary cell in the handover destination MN 100. Furthermore, when the use of the secondary cell is stopped, when a handover of the primary cell is performed, or when the use of the primary cell is stopped or interrupted (when the RRC state transitions from connected mode to idle mode or inactive mode), the terminal device 151 can voluntarily delete the reference config and / or delta config without waiting for an explicit instruction from the MN 100. In this case, the dynamic memory for storing the reference config on the network side can be reduced, and there is no need to perform the process of sharing the reference config and delta config with other base station devices, thereby simplifying the implementation on the network side.

[0043] When the reference config is changed, a "delta reference config" may be used, which indicates only the setting items in the reference config that should be changed. For setting items set in the delta reference config, the reference config may be changed based on the value of that setting item, while the reference config may be maintained for other setting items. At this time, changing the reference config may also change the delta config. For this reason, a "delta-delta config" may be used, which indicates only the setting items in the delta config that should be changed. For setting items set in the delta-delta config, the delta config may be changed based on the value of that setting item, while the delta config may be maintained for other setting items. In this way, when the reference config (and delta config) is changed, only the difference value is exchanged between the MN 100, the SN, and the terminal device, making it possible to update the setting information with a small amount of data. In addition, when the reference configuration or delta configuration is significantly changed, the delta-reference configuration or delta-delta configuration may not be used, and the reference configuration or delta configuration that was previously used may be replaced with a newly generated reference configuration or delta configuration. In other words, the reference configuration or delta configuration that was previously used may be deleted, and the newly generated reference configuration or delta configuration may be stored in the terminal device 151.

[0044] When changing the reference configuration, the network notifies the terminal device 151 of either (1) a delta reference configuration or (2) a newly generated reference configuration. When the terminal device 151 receives the delta reference configuration, it replaces the configuration items specified by the delta reference configuration among the configuration items of the currently used reference configuration with the configuration values ​​of the delta reference configuration. When the terminal device 151 receives a newly generated reference configuration, it replaces the entire reference configuration it holds with the newly generated reference configuration. When a change occurs to a configuration item not specified by the delta configuration for each cell using the reference configuration, the terminal device 151 changes the configuration item for that cell and updates the configuration information. In this configuration, even if a change is made to the reference configuration, there may be cases where the configuration information for each cell is not updated due to the delta configuration. However, the terminal device 151 maintains the updated reference configuration for use in generating configuration information using the delta configuration of another cell thereafter. When updating a reference config, the reference config to be updated can be specified using a reference config ID. The updated reference config may inherit the reference config ID of the reference config before the update, or a new reference config ID may be assigned to the updated reference config.

[0045] On the other hand, when changing the delta configuration, the network notifies the terminal device 151 of either (1) the delta-delta configuration or (2) a newly generated delta configuration. When the terminal device 151 receives the delta-delta configuration for a specific cell, it replaces the configuration items specified by the delta-delta configuration among the configuration items of the delta configuration currently used for that cell with the configuration values ​​of the delta-delta configuration. Furthermore, when the terminal device 151 receives a newly generated delta configuration for a specific cell, it replaces the entire delta configuration of that cell that it holds with the newly generated delta configuration. Note that when updating the delta configuration, the delta configuration to be updated can be specified by a cell identifier or condReconfigId. When the delta configuration is changed, the terminal device 151 updates the configuration information of the cell that uses that delta configuration. The terminal device 151 updates the setting information by changing the setting items of the updated delta config in the setting information of the cell corresponding to the updated delta config in accordance with the update of the delta config.

[0046] The network may notify the terminal device 151 of a delta reference configuration for the existing first reference configuration and may instruct the terminal device 151 to maintain the first reference configuration when transmitting an instruction to generate a second reference configuration. For example, when the second reference configuration is to be used as the reference configuration for some cells among multiple cells using the first reference configuration and the first reference configuration is to be used as the reference configuration for the other cells, a new second reference configuration based on the existing first reference configuration may be generated and the first reference configuration may be maintained. In this case, a new reference configuration ID may be assigned to the second reference configuration, and the reference configuration ID may be notified to the terminal device 151. When the MN 100 decides to change the reference configuration, the MN 100 may instruct the SNs using that reference configuration to change the reference configuration in the same manner as the notification to the terminal device 151 described above. Furthermore, when the SN decides to change the reference configuration, the SN requests the MN 100 to change the reference configuration by specifying the reference configuration, and if the request is permitted, the MN 100 can change the reference configuration. In this case, if the MN 100 permits the change of the reference configuration, it notifies the SN of information indicating the permission, and also notifies the terminal device 151 of the permitted reference configuration.

[0047] In the above description, the process for updating either the reference configuration or the delta configuration has been described. However, as shown in FIG. 5, both the reference configuration and the delta configuration may be updated. That is, it is determined whether the reference configuration or the delta configuration should be updated (S501, S503). If the reference configuration should be updated (YES in S501), the delta-reference configuration or a newly prepared reference configuration is provided to the terminal device (and the SN, if necessary) (S502). Similarly, if the delta configuration should be updated (YES in S503), the delta-delta configuration or a newly prepared delta configuration is provided to the terminal device (and the SN, if necessary) (S504).

[0048] The terminal device 151 may generate configuration information for each cell based on the acquired reference configuration and delta configuration, but it must verify whether the configuration information is appropriate. For example, the terminal device 151 may determine that the configuration information is inappropriate if the configuration information includes parameters that exceed the capabilities of the terminal device (i.e., parameters that the terminal device 151 cannot execute). The terminal device 151 may also determine that the configuration information is inappropriate if the configuration information does not include necessary parameters or if the terminal device 151 cannot interpret the contents of the configuration information. For example, if the reference configuration is accidentally deleted, the necessary parameters may no longer exist in the delta configuration alone, and the configuration information is therefore determined to be inappropriate.

[0049] For example, as shown in FIG. 6 , when the terminal device 151 acquires the reference config and delta config for a secondary cell candidate (S601), it generates configuration information for the cell using the information (S602) and determines whether the configuration information is appropriate (S603). That is, the terminal device 151 determines whether the configuration information can be used for a cell in an environment where configuration information can be prepared (where the reference config and delta config are available). Then, if the configuration information generated by combining the reference config and delta config is appropriate, the terminal device 151 maintains the configuration information. On the other hand, if the configuration information is not appropriate, the terminal device 151 notifies the network (the connected MN 100 or SN) of the reference config ID and delta config identification information (condReconfigId) (S604). This notification is performed, for example, by an RRC Reconfiguration Complete message. Here, information indicating that an error has occurred is notified to the network. This notification can be performed, for example, by setting the failure type in the message to srb3-IntegrityFailure or scg-reconfigFailure. Upon receiving this notification, the network notifies the terminal device 151 of the reference config, delta config, and reference config ID based on the identification information of the reference config ID and delta config. Note that the terminal device 151 may determine which of the reference config portion and the delta config portion is inappropriate and notify the network to transmit the config that caused the inappropriateness. Note that if parameters that cannot be used by the terminal device 151 have been configured, the network may instruct the SN to reconfigure the reference config or delta config. In this way, the terminal device 151 can determine the appropriateness of the configuration information before actually adding / changing a secondary cell, and ensure that appropriate configuration information is prepared in advance.

[0050] Alternatively, as shown in FIG. 7 , the terminal device 151 may not generate configuration information immediately after acquiring the reference configuration and delta configuration, but may instead generate configuration information for a cell whose wireless quality measurement results satisfy a predetermined condition (S701, S702). In this case, the terminal device 151 checks the appropriateness of the generated configuration information (S703). If the terminal device 151 determines that the generated configuration information is inappropriate, it may subsequently generate configuration information for another cell whose wireless quality measurement results satisfy a predetermined condition. Even if there is no secondary cell whose wireless quality measurement results satisfy a predetermined condition, the terminal device 151 may switch the connection to another cell whose wireless quality is better than the current secondary cell if the configuration information in that cell is appropriate. If inappropriate configuration information is found, the terminal device 151 may notify the network of the inappropriate configuration information as described above (S704). In one example, after connecting to a cell with appropriate configuration information, the terminal device 151 can notify the network of the reference configuration ID and delta configuration identification information (condReconfigId) corresponding to the inappropriate configuration information using UE assistance information. Upon receiving this notification, the network modifies the reference configuration and delta configuration based on the reference configuration ID and delta configuration identification information, and notifies the reference configuration, delta configuration, and reference configuration ID again to the terminal device 151. In this way, by not generating configuration information at the time the reference configuration and delta configuration are acquired, but generating configuration information when predetermined conditions such as wireless quality conditions are satisfied and evaluating the appropriateness of the configuration information, it is possible to reduce the memory capacity required to store configuration information in the terminal device 151.

[0051] When the configuration information of the serving cell is used as the reference configuration, the configuration information of the serving cell may be changed between the time when the reference configuration and delta configuration are acquired and the time when the measurement result of the radio quality of one of the candidate cells satisfies a predetermined condition. In this case, the reference configuration will also be changed, and therefore the generated configuration information may be different between the case where the configuration information of the cell is generated using the reference configuration and delta configuration when the information is acquired and the case where the configuration information of the cell is generated when the measurement result of the radio quality of the candidate cell satisfies a predetermined condition. Therefore, the network and the terminal device 151 need to agree on the time when the cell configuration information is generated. For this reason, information specifying the timing at which the cell configuration information is generated may be notified from the network to the terminal device 151. Alternatively, the network and the terminal device 151 may be pre-configured to generate the cell configuration information at a fixed timing that is arbitrarily set in advance without notifying the information.

[0052] When using the configuration information of the serving cell as the reference config, the terminal device 151 may save the configuration information of the serving cell held by the terminal device 151 as the reference config at the time when the reference config and delta config are acquired. Also, in order to reduce the memory capacity for saving the configuration information in the terminal device 151, it is also possible to not save the reference config at the time when the reference config and delta config are acquired, but to save the configuration information of the serving cell at that time as the reference config in response to the satisfaction of predetermined conditions such as wireless quality conditions. Note that when the terminal device 151 saves the configuration information of the serving cell as the reference config at the time when the terminal device 151 acquires the reference config and delta config, it is expected that the contents of the serving cell configuration information and the reference config will no longer match when it receives a serving cell configuration change instruction from the network after saving the reference config. Therefore, in order to prevent this inconsistency, when a serving cell setting change instruction is received from the network after the reference configuration is saved, an instruction may be transmitted from the network to the terminal device 151 to make the same changes to both the serving cell and the reference configuration. In this case, instead of instructing the terminal device 151 to make overlapping changes, the network may instruct the terminal device 151 to make only the serving cell setting change, and the terminal device 151 may make the same changes to the reference configuration as the serving cell setting without any explicit instruction.

[0053] Furthermore, two types of information are defined for each setting item in the cell-related setting information: mandatory (required) and optional (non-required). If a mandatory (required) setting item is not notified to the terminal device 151, the setting information is determined to be inappropriate. Therefore, a message format for notifying conventional cell-related setting information that does not use a reference configuration must include mandatory (required) setting items. However, when setting information is generated using a reference configuration and a delta configuration, mandatory (required) setting items among the setting items related to the candidate cell may be notified by including them in the delta configuration rather than in the reference configuration. In this case, mandatory (required) setting items may be omitted from the reference configuration.

[0054] 8 is a diagram showing an example of the hardware configuration of the MN 100, SN, and terminal device 151 described above. In one example, the MN 100, SN, and terminal device 151 are configured to include a processor 801, a ROM 802, a RAM 803, a storage device 804, and a communication circuit 805. The processor 801 is a computer configured to include one or more processing circuits, such as a general-purpose CPU (Central Processing Unit) or an ASIC (Application Specific Integrated Circuit), and executes the overall processing of the MN 100, SN, and terminal device 151 and each process described below by reading and executing programs stored in the ROM 802 or storage device 804. The ROM 802 is a read-only memory that stores information such as programs related to the processing executed by the MN 100, SN, and terminal device 151 and various parameters. The RAM 803 functions as a workspace when the processor 801 executes a program, and is also a random access memory that stores temporary information. The storage device 804 is configured by, for example, a removable external storage device, etc. The communication circuit 805 is a communication circuit including a wired interface or a wireless interface for the MN 100, SN, and terminal device 151 to communicate with each other.

[0055] FIG. 9 is a diagram outlining an example of the functional configuration of the terminal device 151. Note that each functional unit shown in FIG. 9 may be realized, for example, by the processor 801 executing a program stored in the ROM 802 or the like, or dedicated hardware may be provided to realize each function. Also, FIG. 9 particularly illustrates functions related to the processing according to this embodiment, and the terminal device 151 may naturally have the functions of a normal terminal device that performs communication in accordance with, for example, the 3GPP (registered trademark) cellular communication standard. Also, two or more functional blocks shown in FIG. 9 may be integrated into a single functional block, or a single functional block may be divided into multiple functional blocks. The terminal device 151 includes, as its functions, a reference configuration acquisition unit 901, a delta configuration acquisition unit 902, a setting information generation unit 903, an appropriateness determination unit 904, and an information notification unit 905. Note that, although the functions of the secondary cell are described here, the terminal device 151 may also have similar functions for candidate cells that are handover destinations of the primary cell.

[0056] The reference configuration acquisition unit 901 acquires, for example, from the MN 100, a reference configuration that can be used for configuration information of a candidate cell for adding / changing a secondary cell. The reference configuration acquisition unit 901 acquires information associating a reference configuration with its reference configuration ID. The delta configuration acquisition unit 902 acquires a delta configuration that is used to generate configuration information for each of the above-mentioned candidate cells. The delta configuration is cell-specific information and is acquired in a format associated with a reference configuration ID to indicate which reference configuration the delta configuration should be used in combination with. Note that the reference configuration and delta configuration can be acquired together (in one message) from the MN 100, but this is not necessarily limited to this. That is, the reference configuration may be acquired in a first message, and the delta configuration may be acquired in a second message different from the first message. Furthermore, when configuration information is updated, only either the reference configuration or the delta configuration may be notified to the terminal device 151. The configuration information generation unit 903 combines the acquired delta config with a reference config having a reference config ID associated with the delta config to generate configuration information for a candidate cell associated with the delta config. The configuration information generation unit 903 may generate the configuration information when the reference config and delta config are acquired, or, for example, may generate configuration information for a cell whose wireless quality measured in the terminal device 151 satisfies a predetermined condition, and may not generate configuration information unless the predetermined condition is satisfied. The appropriateness determination unit 904 evaluates whether the configuration information generated by the configuration information generation unit 903 is usable by the terminal device 151, whether any required parameters are missing, whether the terminal device 151 can interpret the information, and so on, and determines whether the configuration information is appropriate. If the configuration information is inappropriate, the information notification unit 905 sends a predetermined notification to the connected MN 100 or SN.Thereafter, when at least one of the reference configuration and the delta configuration is updated, the information is acquired by the reference configuration acquisition unit 901 or the delta configuration acquisition unit 902, and the setting information can be updated.

[0057] FIG. 10 is a diagram outlining an example of the functional configuration of MN 100. Note that each functional unit shown in FIG. 10 may be realized, for example, by a processor 801 executing a program stored in ROM 802 or the like, or dedicated hardware may be provided to realize each function. FIG. 10 particularly illustrates functions related to the processing according to this embodiment, and MN 100 may naturally have the functions of a normal base station device that communicates in accordance with, for example, the 3GPP (registered trademark) cellular communication standard. Furthermore, two or more functional blocks shown in FIG. 10 may be integrated into a single functional block, or a single functional block may be divided into multiple functional blocks. The MN 100 includes, as its functions, a configuration generation instruction unit 1001, a reference configuration acquisition unit 1002, a delta configuration acquisition unit 1003, an update processing unit 1004, and an information notification unit 1005. Note that while a secondary cell will be described here, MN 100 may also have similar functions for candidate cells to which the primary cell is to be handed over.

[0058] The configuration generation instruction unit 1001 instructs an SN having a secondary cell candidate cell under its control to generate configuration information for connection to that cell. Here, the configuration generation instruction unit 1001 instructs the SN to generate configuration information, for example, in the form of a combination of a reference configuration and a delta configuration. For example, when the number of reference configurations reaches a maximum, the configuration generation instruction unit 1001 can instruct the SN to generate a full configuration so that no new reference configurations are configured thereafter. The reference configuration acquisition unit 1002 can, for example, generate a reference configuration in its own device. Furthermore, the reference configuration acquisition unit 1002 can, for example, receive a reference configuration generated in the SN from that SN. The delta configuration acquisition unit 1003 acquires, from the SN, a delta configuration unique to each cell under the SN. The delta configuration is associated with a reference configuration ID indicating which reference configuration it should be combined with. For example, when at least one of the reference config and the delta config needs to be updated, the update processing unit 1004 sends an instruction to the SN to generate a new reference config and a new delta config. After the update processing unit 1004 sends this instruction, at least one of the updated reference config and the new delta config is acquired by the reference config acquisition unit 1002 or the delta config acquisition unit 1003. The information notification unit 1005 provides the acquired reference config and the new delta config to the terminal device 151. The information notification unit 1005 can notify the terminal device 151 of information including a reference config ID indicating which reference config the delta config should be combined with.

[0059] FIG. 11 is a diagram outlining an example of the functional configuration of SN 101 and SN 102. Note that each functional unit shown in FIG. 11 may be realized, for example, by a processor 801 executing a program stored in a ROM 802 or the like, or dedicated hardware may be provided to realize each function. Also, FIG. 11 particularly illustrates functions related to the processing according to this embodiment, and SN 101 and SN 102 may naturally have the functions of a normal base station device that communicates in accordance with, for example, the 3GPP (registered trademark) cellular communication standard. Also, two or more functional blocks shown in FIG. 11 may be integrated into a single functional block, or a single functional block may be divided into multiple functional blocks. The SN 101 and SN 102 include, for example, an instruction receiving unit 1101, a reference configuration acquiring unit 1102, a delta configuration acquiring unit 1103, and an information notifying unit 1104 as their functions. Although the secondary cell will be described here, a base station device that is a candidate for the MN, instead of the SN, can have the same function as a candidate cell for handover of the primary cell.

[0060] The instruction receiving unit 1101 receives an instruction from the MN. For example, the instruction receiving unit 1101 may receive a message from the MN instructing the MN to generate a delta configuration. The instruction receiving unit 1101 may further receive an instruction from the MN indicating that a reference configuration should be generated. For example, when the instruction receiving unit 1101 receives an instruction including a reference configuration generated by the MN, the instruction receiving unit 1101 may identify that the instruction is an instruction to generate a delta configuration. When the instruction receiving unit 1101 receives an instruction not including a reference configuration, the instruction receiving unit 1101 may identify that the instruction is an instruction to generate a reference configuration and a delta configuration. The instruction receiving unit 1101 may receive an instruction to update at least one of the reference configuration and the delta configuration from the MN. The reference configuration acquiring unit 1102 may acquire, for example, the reference configuration included in the instruction received by the instruction receiving unit 1101. Furthermore, the reference configuration acquisition unit 1102 generates and acquires a new reference configuration, for example, when the instruction received by the instruction receiving unit 1101 does not include a reference configuration or when refusing to use the reference configuration included in the instruction. The delta configuration acquisition unit 1103 acquires, as a delta configuration, the difference between the setting information for communication in the subordinate cell and the reference configuration acquired by the reference configuration acquisition unit 1102. Note that the delta configuration acquisition unit 1103 may, for example, cause a subordinate DU to generate a delta configuration and acquire the generated delta configuration from the DU. The information notification unit 1104 notifies the MN of information about the acquired delta configuration. Note that, when a reference configuration is generated in the SN, the information notification unit 1104 notifies the MN of the reference configuration. The information notification unit 1104 associates the delta config with a reference config ID, which indicates which reference config the delta config should be combined with, and notifies the MN of the reference config ID.

[0061] At least a part of the functions of the MN described above may be performed by the SN to which the terminal device 151 is connected.

[0062] As described above, according to this embodiment, it is possible to appropriately configure and manage configuration information for communication in a cell to which a terminal device is to newly connect, using the reference config and delta config. Therefore, it is possible to efficiently perform configuration processing using the reference config and delta config related to conditional handover in the terminal device and the addition or change of a conditional secondary cell. This makes it possible to contribute to Goal 9 of the United Nations-led Sustainable Development Goals (SDGs), which is to "Develop resilient infrastructure, promote sustainable industrialization and foster innovation."

[0063] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention.

[0064] This application claims priority based on Japanese Patent Application No. 2023-079348, filed on May 12, 2023, the entire contents of which are incorporated herein by reference.

Claims

1. A base station device comprising: an acquisition means for acquiring information for generating configuration information regarding a plurality of cells for a conditional handover (CHO) or a conditional secondary cell addition or change (CPAC) in a connected terminal device, the information including a reference config common to two or more of the plurality of cells and assigned with identification information that uniquely identifies the reference config, a delta config unique to each of the two or more cells, and the identification information of the reference config to which the delta config is to be combined; a provision means for providing the information and conditions for executing the CHO or the CPAC to the terminal device; and an instruction means for, when at least one of the reference config and the delta config should be deleted or changed, specifying at least one of the reference config and the delta config and instructing the terminal device to delete or change the reference config or the delta config.

2. The base station device according to claim 1, wherein the instruction means uses the identification information to specify the reference configuration.

3. The base station device of claim 1, wherein the instruction means uses information to specify an information element that combines a cell identifier of a cell in which the delta config is used, or identification information of a reference config indicating whether the delta config should be combined with the delta config, and the condition for the CHO or the CPAC.

4. The base station device according to claim 1, wherein the instruction means instructs deletion of the reference config when there is no delta config to be combined with the reference config.

5. A base station device as described in claim 1, wherein when the instruction means instructs a change to the reference config or the delta config, it notifies the terminal device of difference information indicating the setting items to be changed in the reference config or the delta config.

6. The base station device according to claim 1, wherein when the instruction means instructs a change to the reference config or the delta config, it notifies the terminal device of the reference config or the delta config to be replaced.

7. A terminal device having: an acquisition means for acquiring information for generating configuration information for a plurality of cells for conditional handover (CHO) or conditional secondary cell addition or change (CPAC) from a connected base station device, the information including a reference config common to two or more of the plurality of cells and a delta config specific to each of the two or more cells, and a condition for executing the CHO or the CPAC; a generation means for generating configuration information for communication in at least one of the two or more cells using the delta config and the reference config; an execution means for, when a deletion or change instruction specifying at least one of the reference config and the delta config is received, executing the deletion or change of at least one of the specified reference config and the delta config; and an execution means for executing the CHO or the CPAC using the generated configuration information in response to the condition being satisfied.

8. A terminal device as described in claim 7, wherein the reference config is assigned identification information that uniquely identifies the reference config, and the information further includes the identification information of the reference config with which the delta config is to be combined.

9. A terminal device according to claim 7, wherein the instruction to delete or change includes the identification information as information specifying the reference configuration.

10. The terminal device of claim 7, wherein the instruction to delete or modify includes, as information specifying the delta config, information identifying an information element that combines the conditions for the CHO or the CPAC and the identification information of a reference config indicating whether the delta config should be combined with the delta config, or information specifying a cell identifier of a cell in which the delta config is used, or information specifying an information element that combines the conditions for the CHO or the CPAC and the identification information of a reference config indicating whether the delta config should be combined with the delta config.

11. A terminal device according to claim 7, which, when instructed to delete the reference config, deletes the reference config and also deletes the delta config to be combined with the reference config.

12. A terminal device as described in claim 7, wherein the instruction to change the reference config or the delta config includes difference information indicating setting items to be changed in the reference config or the delta config.

13. The terminal device of claim 7, wherein the instruction to change the reference configuration or the delta configuration includes the reference configuration or the delta configuration to be replaced.

14. The terminal device according to claim 7, wherein said execution means automatically deletes said reference config and said delta config when said terminal device transitions from a connected state to an idle state.

15. A terminal device as described in claim 7, which deletes the reference config and the delta config when use of a secondary cell is stopped without an instruction from the connected base station device.

16. A control method executed by a base station device, comprising: acquiring information for generating configuration information regarding a plurality of cells for a conditional handover (CHO) or a conditional secondary cell addition or change (CPAC) in a connected terminal device, the information including a reference config common to two or more of the plurality of cells and assigned with identification information that uniquely identifies the reference config, a delta config unique to each of the two or more cells, and the identification information of a reference config to which the delta config is to be combined; providing the information and conditions for executing the CHO or CPAC to the terminal device; and, when at least one of the reference config and the delta config should be deleted or changed, specifying at least one of the reference config and the delta config and instructing the terminal device to delete or change the reference config and the delta config.

17. A control method executed by a terminal device, comprising: acquiring, from a connected base station device, information for generating configuration information for a plurality of cells for conditional handover (CHO) or conditional secondary cell addition or change (CPAC), the information including a reference config common to two or more of the plurality of cells and a delta config specific to each of the two or more cells, and a condition for executing the CHO or the CPAC; generating configuration information for communication in at least one of the two or more cells using the delta config and the reference config; when an instruction to delete or change specifying at least one of the reference config and the delta config is received, executing the deletion or change of at least one of the specified reference config and the delta config; and executing the CHO or the CPAC using the generated configuration information in response to the condition being satisfied.

18. A program for causing a computer to function as a base station device according to any one of claims 1 to 6.

19. A program for causing a computer to function as a terminal device according to any one of claims 7 to 15.

Citation Information

Patent Citations

  • Water-soluble cutting oil, water-soluble cutting oil management device, and water-soluble cutting oil management method

    JP2023079348A