Distributed unit included in base station, central unit, and communication method
By specifying data collection and applicability reporting through DataCollectionCandidateConfig and ApplicabilityReportList in a CU-DU separated architecture, the solution addresses operational inefficiencies in AI/ML model training, ensuring efficient data collection and reporting.
Patent Information
- Application Number
- JP2025107763
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-06-25
- Publication Date
- 2025-10-15
AI Technical Summary
Data collection and applicability reporting for AI/ML model training in a CU-DU separated architecture of base stations are not adequately addressed, leading to potential operational inefficiencies.
The DU generates and transmits DataCollectionCandidateConfig and ApplicabilityReportList to the CU, specifying data collection and applicability reporting procedures, enabling proper execution in a CU-DU separated architecture.
Ensures appropriate data collection and applicability reporting for AI/ML model training, enhancing operational efficiency in CU-DU separated architectures.
Smart Images

Figure 2025157265000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a distributed unit, a central unit and a communication method included in a base station. [Background technology]
[0002] The 3GPP (registered trademark) (3rd Generation Partnership Project) is considering the application of artificial intelligence / machine learning (AI / ML) technology to wireless communication technology in the sixth generation mobile communication system (6G). [Prior art documents] [Non-patent literature]
[0003] [Non-Patent Document 1] 3GPP TS 38.300 V18.5.0(2025-03) [Non-patent document 2] 3GPP TS 38.401 V18.5.0(2025-03) Summary of the Invention [Problem to be solved by the invention]
[0004] Previously, data collection for AI / ML model training and applicability reporting for AI / ML functions did not take into consideration application to a CU-DU separated architecture (CU-DU separated gNB).As a result, there is a risk that data collection for AI / ML model training and applicability reporting cannot be properly performed in a CU-DU separated architecture. [Means for solving the problem]
[0005] According to this embodiment, a first unit included in a base station and having a wireless interface with a terminal includes a control unit that generates setting information related to data collection in AI / ML, and a transmission unit that transmits the generated setting information to a second unit included in the base station and that controls the first unit. [Effects of the Invention]
[0006] According to this embodiment, the operation of sending and receiving setting information for collecting data related to AI / ML in a CU-DU separated architecture and information indicating the applicability of AI / ML functions is specified, and these operations can be executed appropriately. [Brief explanation of the drawings]
[0007] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 10 is a sequence diagram showing an example of an operation procedure for reporting applicability in the present embodiment. [Figure 3] FIG. 10 is a diagram showing DataCollectionCandidateConfig, which is an example of setting information related to AI / ML data collection in this embodiment. [Figure 4] FIG. 4 is a sequence diagram illustrating an example of an operation procedure of the wireless communication system according to the first embodiment. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of an operation procedure of the wireless communication system according to another example of the first embodiment. [Figure 6] FIG. 10 is a sequence diagram illustrating an example of an operation procedure of the wireless communication system according to another example of the first embodiment. [Figure 7] FIG. 10 is a diagram illustrating an example of an RRCReconfigurationComplete including information related to the applicability of radio measurement prediction configuration in this embodiment. [Figure 8] FIG. 10 is a sequence diagram showing an example of an operation procedure of a wireless communication system according to another example of the embodiment 2-1. [Figure 9]FIG. 10 is a sequence diagram showing an example of an operation procedure of a wireless communication system according to another example of the embodiment 2-1. [Figure 10] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to the present embodiment. [Figure 11] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to the present embodiment. [Figure 12] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0008] The present embodiment will be described below with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0009] In operation of the wireless communication system of this embodiment, existing technologies (e.g., LTE and NR (5G)) or future technologies (e.g., 6G) may be used as appropriate. The technologies used in the wireless communication system of this embodiment may not be limited to the above-mentioned LTE, NR, and 6G.
[0010] In the present embodiment described below, terms used in existing technologies, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. The above-mentioned 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 designated as "NR-".
[0011] In this embodiment, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or other methods (for example, flexible duplex, etc.).
[0012] In this embodiment, when radio parameters etc. are "configured," it may mean that a predetermined value is pre-configured, or that radio parameters notified from a base station or a terminal are set.
[0013] (System Configuration) Fig. 1 is a diagram for explaining a wireless communication system in this embodiment. As shown in Fig. 1, the wireless communication system in this embodiment includes a base station (gNB) 10 and a terminal (UE (User Equipment)) 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.
[0014] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. A TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe.
[0015] The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via the NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using Carrier Aggregation (CA). Furthermore, the terminal 20 may perform communication via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).
[0016] The base station 10 may be configured with a CU (Central Unit)-DU (Distributed Unit) split architecture. In this architecture, the functions of the base station (gNB) 10 are divided between a CU (gNB-CU) 10B and a DU (gNB-DU) 10A. The CU 10B typically processes higher layer protocol functions such as RRC and PDCP, controls one or more DUs 10A, and manages a wide coverage area and a large number of terminals 20. On the other hand, the DU 10A processes lower layer protocol functions such as RLC, MAC, and the physical layer, and is responsible for direct communication with the radio interface under the control of the CU 10B, transmitting and receiving radio signals to and from the terminals 20. The base stations (CUs 10B) may be connected to each other via an Xn interface. The CU 10B and the DU 10A may be connected to each other via an F1 interface. The DU 10A is an example of a first unit included in the base station 10 and having a radio interface with the terminals 20. The CU 10B is an example of a second unit that is included in the base station 10 and controls the DU 10A.
[0017] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.
[0018] AI / ML may be applied to the wireless communication system in this embodiment. AI / ML is a technology that learns based on data, recognizes patterns, and makes predictions. In wireless communication systems, AI / ML is used, for example, to improve the efficiency of data collection, optimize wireless resource management, detect / recover network faults, optimize mobility (cell switching, etc.), and improve beam management.
[0019] An AI / ML model refers to a mathematical or algorithmic structure that realizes such AI / ML functionality. An AI / ML model may be trained using training data and configured to perform a specific task (e.g., logging L1 measurements, determining applicable functions, predicting radio measurements).
[0020] The functions of an AI / ML model architecture may include, for example, data collection, AI / ML model training (hereinafter referred to as "model training"), and model inference. Data collection is the function that provides input data to the model training and model inference functions. Model training performs training, validation, and testing of the AI / ML model. As part of the model testing procedure, performance metrics of the AI / ML model may be generated. Model training may also be responsible for data preparation (e.g., data preprocessing and cleaning, formatting, and transformation). Model inference is the function that provides inference output (e.g., predictions or decisions). Model inference may provide control of model inference to model management / performance monitoring functions.
[0021] In this embodiment, at least one of a network-side AI / ML model and a UE-side AI / ML model may be used. The network-side AI / ML model and the UE-side AI / ML model may work together with data collection and applicability reporting mechanisms for different purposes. For example, data collection may be performed for network-side model training, and applicability may be reported for the UE-side model.
[0022] Data collection for model training in this embodiment will now be described.
[0023] Data collection for network-side model training may be initiated by OAM (Operation, Administration, and Maintenance) or the gNB.
[0024] For data collection for UE-side model training, the UE 20 may be configured by the gNB 10 to log L1 measurements in RRC messages. The UE 20 may be configured by the gNB 10 to report the logged data or L1 measurements in an Access Stratum (AS) buffer.
[0025] Periodic and radio condition-based event-triggered data logging may be supported. The UE 20 may be configured to perform data logging based on an L3 measurement event trigger. The UE 20 stores the logged data in an AS layer buffer. When the memory reserved for storing logged data becomes full, the UE 20 stops measuring and logging for data collection purposes and notifies the network that data is available. This data availability notification may also be sent when an absolute UE buffer threshold is reached or when a low power state of the UE 20 is detected. Upon receiving the availability notification, the network may request the UE 20 to transmit the available data.
[0026] To reduce power consumption of the UE 20, if a low power condition is detected, the UE 20 may notify the network of the low power condition. Upon receiving the low power condition notification, the network may deconfigure the UE 20 to release the data collection setting. How the buffer threshold is reached and the low power condition are determined may be based on the implementation of the UE 20. If the low power condition is cleared or the UE buffer is emptied, no additional signaling from the UE 20 may be required.
[0027] The network may configure the UE 20 whether to retain the logged data during handover. If configured to retain the data, the UE 20 may retain the logged data during handover and notify the network of the availability of the logged data after handover. If the UE 20 transitions to RRC_IDLE / INACTIVE or if the UE 20 detects a Radio Link Failure (RLF), the UE 20 may discard all stored data.
[0028] When the UE 20 logs data, the UE 20 may include:
[0029] - Data logging setting ID - Indication of a logging gap time interval longer than the set logging cycle - The serving cell's available NCGI (New Cell Global Identity) If NCGI is not available, the UE 20 may include an available PCI (Physical Cell Identity) and ARFCN (Absolute Radio Frequency Channel Number). Regarding data collection for model training on the UE side, the network may configure whether to allow the UE 20 to initiate a request for data collection configuration (e.g., start / stop, preferred configuration from a list of candidate configurations provided by the network). The network may provide data collection configuration to the UE 20 or release data collection configuration with or without a request from the UE 20.
[0030] Data collection settings in beam management may include:
[0031] - CSI-ResourceConfigId of set A - CSI-ResourceConfigId of set B - One or two association IDs (depending on whether set B is equal to or a subset of set A)
[0032] Applicability reporting supported by the wireless communication system in this embodiment will be described.
[0033] For the UE-side model, the network (e.g., gNB 10) provides inferred configuration based on the supported capabilities of the UE 20. The UE 20 may report its applicable capabilities, inapplicable capabilities, and their subsequent changes to the network. When the UE 20 reports that a capability has become inapplicable, the UE 20 may also indicate its preference for releasing the configuration (e.g., due to unavailability of the model at the local device). The applicability reporting procedure is shown in Figure 2.
[0034] Step S1 in FIG. 2: The network inquires about UE capability information.
[0035] Step S2: The UE 20 indicates its supported capabilities (capabilities that the UE 20 can indicate to the network) via UE capability information (eg, RRC / LPP signaling).
[0036] Step S3: The network provides the UE with an inference configuration (i.e., a complete inference configuration and / or a set of inference-related parameters) along with network-side additional conditions (if provided) via the CSI reporting configuration or OtherConfig.
[0037] Step S4: The UE 20 determines the applicable AI / ML functions based on the network side additional conditions (if provided), the UE side additional conditions (known internally by the UE) and the availability of models in the UE.
[0038] Step S5: The UE 20 reports its initial feature applicability in an RRCReconfigurationComplete message.
[0039] Step S6: If the CSI reporting configuration provides a periodic CSI configuration that matches the reported UE capabilities, the UE 20 autonomously activates the applicable AI / ML functions upon reporting the applicable AI / ML functions. If a semi-persistent CSI and / or aperiodic CSI configuration is provided, after reporting the applicable AI / ML functions, activation of the applicable AI / ML functions follows CSI measurement and reporting. That is, semi-persistent reporting is activated by MAC CE / DCI, and aperiodic CSI reporting is activated by DCI.
[0040] If no inference configurations are provided in step 3, the network may send an RRCReconfiguration message containing the inference configurations to the UE. Upon receiving one or more inference configurations, the UE maintains all inference configurations, regardless of whether they are applicable or not, until explicitly released by the network.
[0041] Step S7: If the network has configured applicability reporting for the UE 20 and applicability reporting is enabled via OtherConfig, and if the applicability of a feature has changed, the UE 20 may report the updated applicability and non-applicability of the feature in the UEAssistanceInformation message. If the Periodic CSI-ReportConfig becomes inapplicable, the UE 20 may notify the network of this fact without autonomously releasing the configuration, and the network may release the configuration. The UE 20 may continue inferring and reporting until the configuration is released. If an activated AI / ML feature becomes inapplicable, the UE 20 may not autonomously deactivate it, but may notify the network of the change in the applicability of the feature. Upon receiving notification from the UE that the feature has become inapplicable, the network may deactivate or release the activated feature.
[0042] During the handover, the UE 20 may receive additional network-side conditions and / or inference settings related to the target gNB via a handover command, and the UE may then report applicable / inapplicable AI / ML capabilities to the target gNB after the handover is complete.
[0043] For the network-side model, CSI measurements and CSI reports may be used to obtain input data for inference. For the network-side model, additional network-side requirements may be required based on the network implementation.
[0044] The DataCollectionCandidateConfig included in the RRC IE (Information Element) is used as configuration information for data collection for model training. DataCollectionCandidateConfig is defined as a list of candidate configurations that the UE 20 desires to be configured with radio resources for UE data collection. This allows the network to present multiple data collection configuration options to the UE 20, and the UE 20 to select the optimal configuration based on its own situation (e.g., remaining battery level, processing power, service type, etc.) and notify the network of its preference. This allows the network to allocate radio resources for data collection according to the UE 20's request, set specific collection parameters, and achieve efficient data collection while reducing the UE 20's battery consumption.
[0045] Conventionally, data collection and applicability reporting for AI / ML model training has not been considered for application to a CU-DU separated architecture (CU-DU separated gNB). Therefore, in a CU-DU separated architecture, there is a risk that data collection and applicability reporting for AI / ML model training cannot be properly performed.
[0046] In this embodiment, the operations of data collection and applicability reporting for AI / ML model training in a CU-DU separated architecture are specified so that these operations can be executed appropriately.
[0047] Example 1 Conventionally, in a CU-DU separated architecture, it was not clear whether the CU or the DU generates the configuration information related to data collection in AI / ML, and how to configure the configuration information in the UE.
[0048] A first example of the present embodiment specifies a method for configuring (notifying) configuration information related to data collection in AI / ML in a UE 20 in a CU-DU separated architecture. An example of the configuration information related to data collection in AI / ML in the first example is DataCollectionCandidateConfig (data collection candidate configuration) as shown in FIG. 3. The configuration information related to data collection in AI / ML is not limited to DataCollectionCandidateConfig and may have any name as long as it is information for any purpose related to data collection in AI / ML. DataCollectionCandidateConfig is used to indicate a list of candidate configurations prioritized by the UE when the UE desires to be configured with radio measurement resources for UE data collection.
[0049] According to the first embodiment, the DU 10A generates DataCollectionCandidateConfig. The DU 10A may send the generated DataCollectionCandidateConfig to the CU 10B.
[0050] Fig. 4 is a sequence diagram illustrating an example of an operation in the embodiment 1. Fig. 4 illustrates an example in which DataCollectionCandidateConfig is included in DU to CU RRC information in a UE context setup response.
[0051] In step S101, the CU 10B sends a UE context setup request to the DU 10A. The UE context setup request is a request message sent from the DU to the CU to set up a UE-specific context when the UE establishes a connection. The UE context setup request is an example of a message requesting setting information related to data collection in AI / ML.
[0052] According to the first embodiment, the DU 10A generates a DataCollectionCandidateConfig based on receiving a UE context setup request.
[0053] In step S102, the DU 10A sends a UE context setup response to the CU 10B. The UE context setup response includes DU to CU RRC information including DataCollectionCandidateConfig.
[0054] The DataCollectionCandidateConfig may include, for example, at least one of the following information:
[0055] - dataCollectionCandidateConfigId - CSI-ResourceConfigIdSetA (or the corresponding CSI-ResourceConfigId) - CSI-ResourceConfigIdSetB (or the corresponding CSI-ResourceConfigId) - associatedId1 (or the corresponding associated_Id) - associatedId2 (or the corresponding associated_Id) -retainLoggedMeasurements(true)
[0056] The dataCollectionCandidateConfigId is an ID for uniquely identifying a data collection candidate configuration.
[0057] CSI-ResourceConfigIdSetA indicates CSI resource configuration ID set A. It is an identifier of the resource configuration used by the UE to report radio state information. The corresponding CSI-ResourceConfigId points to a specific CSI resource configuration.
[0058] CSI-ResourceConfigIdSetB indicates CSI resource configuration ID set B. Similar to CSI-ResourceConfigIdSetA, it is an identifier of the resource configuration used by the UE to report radio state information. The corresponding CSI-ResourceConfigId) refers to a specific CSI resource configuration.
[0059] associatedId1 indicates the associated ID1, which is the first identifier associated with a particular data collection candidate configuration. The corresponding associated_Id similarly points to the associated identifier.
[0060] associatedId2 indicates the associated ID2, which is the second identifier associated with a particular data collection candidate configuration. The corresponding associated_Id also points to the associated identifier.
[0061] retainLoggedMeasurements(true) indicates that the UE 20 should retain the logged measurements available in the VarCSI-LogMeasReport upon completion of the handover execution.
[0062] In step S103, the CU 10B transmits OtherConfig, including DataCollectionCandidateConfig, to the UE 20 via the DU 10A. OtherConfig is an information element including configurations related to various settings. DataCollectionCandidateConfig indicates a list of configuration candidates that the UE desires to be configured with radio resources for UE data collection. This allows the UE 20 to be configured with DataCollectionCandidateConfig.
[0063] As another example of the first embodiment, as shown in FIG. 5, DataCollectionCandidateConfig may be included in DU to CU RRC information in a UE context modification response.
[0064] 5, in step S201, the CU 10B sends a UE context modification request to the DU 10A. The UE context modification request is a request message sent from the CU 10B to the DU 10A to change the context information of the UE.
[0065] The DU 10A generates a DataCollectionCandidateConfig based on receiving the UE context modification request.
[0066] In step S202, the DU 10A sends a UE context modification response to the CU 10B. The UE context modification response includes DU to CU RRC information including DataCollectionCandidateConfig. DataCollectionCandidateConfig may include the information described above in step S102 of FIG. 4.
[0067] As another example of the first embodiment, as shown in FIG. 6, DataCollectionCandidateConfig may be included in DU to CU RRC information in UE context modification required.
[0068] In step S301 of Fig. 6, the DU 10A sends a UE context modification required to the CU 10B. The UE context modification required includes RRC information from the DU to the CU, including a DataCollectionCandidateConfig. The DataCollectionCandidateConfig may include the information described above in step S102 of Fig. 4.
[0069] In step S302, the CU 10B sends a UE context modification confirm to the DU 10A.
[0070] As another example of the first embodiment, DataCollectionCandidateConfig may be included in UE associated signaling, that is, the DU 10A may transmit UE associated signaling including DataCollectionCandidateConfig to the CU 10B.
[0071] As another example of the first embodiment, DataCollectionCandidateConfig may be included in non-UE associated signaling, that is, the DU 10A may transmit non-UE associated signaling including DataCollectionCandidateConfig to the CU 10B.
[0072] According to the first embodiment, the operations of generating, transmitting and receiving setting information related to data collection related to AI / ML in a CU-DU separated architecture are specified, enabling the execution of data collection.
[0073] Example 2 As shown in Fig. 7, the UE 20 in this embodiment uses an RRCReconfigurationComplete (RRC reconfiguration complete message) to send an applicability report including information related to the applicability of settings related to radio measurement prediction configurations or AI / ML model inference settings. The applicability indicates whether the UE 20 can actually apply settings related to radio measurement prediction configurations or AI / ML model inference settings based on its own capabilities, internal conditions (UE-side additional conditions), and model availability (applicability). The settings related to radio measurement prediction configurations and AI / ML model inference settings are examples of settings related to AI / ML functions.
[0074] Example 2-1 Conventionally, in a CU-DU separated architecture, it has not been clear how to report information related to the applicability of radio measurement prediction settings between the CU and DU.
[0075] Example 2-1 of this embodiment specifies a method for transmitting and receiving information related to the applicability of radio measurement prediction settings between a CU and a DU in a CU-DU separated architecture. An example of the information related to applicability in this embodiment is ApplicabilityReportList. The information related to applicability is not limited to ApplicabilityReportList and may have any name as long as it is information related to the applicability of settings related to AI / ML functions (e.g., radio measurement prediction settings). ApplicabilityReportList indicates a list of setting applicability reports. The information related to applicability may also be referred to as applicability information indicating whether settings related to AI / ML functions are applicable to the UE 20.
[0076] According to Example 2-1, the DU 10A uses the applicability of the radio measurement prediction configuration (e.g., ApplicabilityReportList) to generate the radio measurement prediction configuration. Therefore, the DU 10A receives information related to the applicability of the radio measurement prediction configuration from the CU 10B.
[0077] The ApplicabilityReportList may be included in the UE associated signaling, that is, the CU 10B may transmit the UE associated signaling including the ApplicabilityReportList to the DU 10A.
[0078] Fig. 8 is a sequence diagram showing an example of the operation in Example 2-1. Fig. 8 shows an example in which ApplicabilityReportList is included in CU to DU RRC information in a UE context setup request.
[0079] In step S401 of Fig. 8, the CU 10B sends a UE context setup request to the DU 10A. The UE context setup request is a request sent from the CU to the DU to set up a UE-specific context when the UE establishes a connection. The UE context setup request includes CU to DU RRC information including an ApplicabilityReportList.
[0080] The ApplicabilityReportList may include, for example, at least one of the following information:
[0081] - applicabilityCellId (ServCellIndex) - applicabilityReportConfigId - csi-ReportConfigId - applicabilityStatus (applicable, inapplicable) - inapplicabilityCause
[0082] applicabilityCellId indicates the cell index of the serving cell for which the applicability information has been changed.
[0083] The applicabilityReportConfigId indicates the corresponding reportConfigId.
[0084] csi-ReportConfigId is the identifier of the CSI reporting configuration.
[0085] The applicabilityStatus indicates whether the setting is "applicable" or "inapplicable."
[0086] The inapplicabilityCause indicates the reason why a setting is not applicable.
[0087] In step S402, the DU 10A sends a UE context setup response to the CU 10B.
[0088] As another example of Example 2-1, the ApplicabilityReportList may be included in the CU to DU RRC information in the UE context modification request, as shown in Fig. 9. That is, the CU 10B may send a UE context modification request including the ApplicabilityReportList to the DU 10A.
[0089] 9, the UE 20 sends an RRCReconfigurationComplete or UEAssistanceInformation to the CU 10B. The UEAssistanceInformation is a message used to indicate UE assistance information to the network. The RRCReconfigurationComplete or UEAssistanceInformation may include an ApplicabilityReportList.
[0090] In step S502, the CU 10B sends a UE context modification request to the DU 10A. The UE context modification request includes CU to DU RRC information including an ApplicabilityReportList. The ApplicabilityReportList may include the information described above in step S401 of FIG. 8.
[0091] The DU 10A may generate configuration information (e.g., radio measurement prediction configuration) related to the AI / ML function based on the received ApplicabilityReportList.
[0092] In step S503, the DU 10A transmits a UE context modification response to the CU 10B. The UE context modification response may include setting information (e.g., radio measurement prediction setting) related to the generated AI / ML function. Note that the setting information related to the AI / ML function may be transmitted using any message, not limited to the UE context modification response.
[0093] According to the second embodiment, it is possible to define the operation of transmitting and receiving information related to the applicability of settings (e.g., radio measurement prediction settings) related to AI / ML functions in a CU-DU separation architecture.
[0094] (Example 2-2) The DU 10A uses csi-LogMeasAvailable{true} to trigger L1 radio measurement data collection. csi-LogMeasAvailable{true} indicates that the UE 20 has logged L1 radio measurements to report to the network. For example, the UE 20 may use csi-LogMeasAvailable{true} to explicitly notify the network that there is measurement history data to send based on a specific trigger (e.g., when a buffer becomes full or when the UE 20 transitions to a low power state).
[0095] Conventionally, in a CU-DU separated architecture, it is not clear whether the CU should report csi-LogMeasAvailable{true} to the DU.
[0096] Example 2-2 of this embodiment specifies a method for notifying information indicating that measurement values are held by the UE 20 (e.g., csi-LogMeasAvailable{true}) from the CU 10B to the DU 10 in a CU-DU separated architecture.
[0097] According to Example 2-2, csi-LogMeasAvailable{true} may be included in the UE associated signaling, that is, the CU 10B may transmit the UE associated signaling including csi-LogMeasAvailable{true} to the DU 10A.
[0098] As another example of Example 2-2, for example, csi-LogMeasAvailable{true} may be included in the CU to DU RRC information in the UE context setup request. That is, the CU 10B may send a UE context setup request including csi-LogMeasAvailable{true} to the DU 10A.
[0099] As another example of Example 2-2, for example, csi-LogMeasAvailable{true} may be included in the CU to DU RRC information in the UE context modification request. That is, the CU 10B may send a UE context modification request including csi-LogMeasAvailable{true} to the DU 10A.
[0100] According to Example 2-2, in a CU-DU separated architecture, it is possible to define the operations of transmitting and receiving information indicating that a terminal holds radio measurement values.
[0101] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station (gNB) 10 and the terminal (UE) 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for executing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions in the embodiments.
[0102] <Base station (gNB)> Fig. 10 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Fig. 10, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 10 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations in this embodiment. The transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.
[0103] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitter 110 transmits setting information, instructions, notifications, etc. related to a low-power wake-up signal to the terminal 20. The transmitter 110 transmits notifications related to switching of monitoring operations to the terminal. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 has a function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 receives inter-network node messages from other network nodes.
[0104] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information on the operations explained in the embodiments.
[0105] The control unit 140 controls the settings, instructions, and notifications related to the operations described in the embodiments. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
[0106] <Device (UE)> Fig. 11 is a diagram showing an example of the functional configuration of the terminal 20 in this embodiment. As shown in Fig. 11, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 11 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations in this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.
[0107] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitter 210 transmits capability information in a low-power wake-up signal to the base station 10. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiver 220 receives paging notification information and configuration information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiver 220 receives a low-power wake-up signal from the base station 10. The configuration unit 230 stores various configuration information received from the base station 10 by the receiver 220. The configuration unit 230 also stores pre-configured configuration information. The configuration information includes, for example, information on the operations described in the embodiments.
[0108] As described in the embodiments, the control unit 240 controls settings, instructions, and notifications related to the operations described in the embodiments. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.
[0109] (Hardware configuration) The block diagrams (FIGS. 10 and 11) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by hardware, software, or a combination of these. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using a single device that is physically or logically coupled, or may be realized by using two or more physically or logically separated devices that are connected directly or indirectly (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.
[0110] For example, the base station, terminal, network node, etc. in this embodiment may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 12 is a diagram showing an example of the hardware configuration of a base station and a terminal in one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0111] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as circuit, device, unit, module, chip, means, etc. The hardware configurations of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.
[0112] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls the reading, writing, or both reading and writing of data in the memory 1002 and storage 1003.
[0113] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 1001. Although only one processor 1001 is shown in the figure, there may be multiple processors.
[0114] The processor 1001 reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by a single processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line, or may be provided to the computer via the communication device 1004, for example.
[0115] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).
[0116] The memory 1002 is a computer-readable recording medium and may be configured, for example, as a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or a combination of at least two of these. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), or the like. The memory 1002 can store executable programs (program codes), software modules, and the like for executing the wireless communication method according to one embodiment of the present disclosure.
[0117] Storage 1003 is a computer-readable recording medium, and may be, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, or a combination of at least two of these. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, memory 1002, storage 1003, or a database, server, or other appropriate medium including both memory 1002 and storage 1003.
[0118] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or a combination of at least two of these. For example, a transmitting / receiving antenna, an amplifier unit, a transmitting / receiving unit, or a transmission path interface may be realized by the communication device 1004. The transmitting / receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated.
[0119] The input device 1005 is an input device that receives input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of at least two of these). The output device 1006 is an output device that performs output to the outside (for example, a display, a speaker, an LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0120] The processor 1001, memory 1002, and other devices are connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between the devices.
[0121] The base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0122] <Additional notes> (Additional note 1) a first unit included in a base station and having a radio interface with a terminal, a control unit that generates setting information related to data collection in AI / ML (Artificial Intelligence / Machine Learning); a transmitting unit included in the base station, the first unit transmitting the generated setting information to a second unit that controls the first unit; (Additional note 2) The first unit described in appendix 1 includes a receiving unit that receives applicability information from the second unit indicating whether the settings related to the AI / ML functions are applicable to the terminal. (Additional note 3) The first unit according to claim 2, wherein the receiving unit receives information indicating whether the terminal holds measurement values from the second unit. (Additional note 4) a second unit included in the base station and configured to control the first unit, a transmitter that transmits a message requesting setting information related to data collection in AI / ML (Artificial Intelligence / Machine Learning) to the first unit; a second unit comprising: a receiving unit that receives the setting information from the first unit; (Additional note 5) The receiving unit receives, from a terminal, applicability information indicating whether a setting related to the AI / ML function is applicable to the terminal; The second unit according to claim 3, wherein the transmitting unit transmits the applicability information to the first unit. (Additional note 6) A communication method executed by a first unit included in a base station and having a radio interface with a terminal, and a second unit controlling the first unit, comprising: sending a message from the first unit to the second unit requesting configuration information related to data collection in AI / ML (Artificial Intelligence / Machine Learning); transmitting the setting information from the second unit to the first unit.
[0123] According to the configuration described in the above appendix, the operation of sending and receiving setting information for collecting data related to AI / ML in the CU-DU separated architecture and information indicating the applicability of AI / ML functions is specified, and these operations can be executed appropriately.
[0124] (Supplementary explanation of the embodiment) Although the present embodiment has been described above, the disclosed invention is not limited to such an embodiment, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.
[0125] The aspects / embodiments described in the present disclosure may be categorized as Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA) (registered trademark), Global System for Mobile communications (GSM) (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) Engineers) 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE802.16 (WiMAX (registered trademark), IEEE802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Of course, "based on" may refer not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.
[0126] In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably.
[0127] Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.
[0128] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE 20)", "Device", "Module" and "Terminal" may be used interchangeably.
[0129] A terminal may be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.
[0130] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. The object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").
[0131] A base station in the present disclosure may be read as a terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)) or communication of a non-terrestrial network (NTN). In this case, the terminal 20 may be configured to have at least some of the functions of the base station 10 described above. Terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.
[0132] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the ground (for example, in the atmosphere or outer space).
[0133] In this disclosure, the term "terminal" may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.
[0134] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. The RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, or notification of a terminal's capabilities, or may be an information element within the message. Notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the terminal 20). Notification of information from one device to another device may be performed via one or more devices. With regard to any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically specified in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).
[0135] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0136] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.
[0137] In the present disclosure, the action of "a terminal receives information from a base station" accompanies the action of "the base station transmits the information to the terminal", "the base station generates the information", or both. Similarly, the action of "a terminal transmits information to a base station" accompanies the action of "the base station receives the information from the terminal". The actions of "the terminal is configured to..." or "configure UE 20 to..." may include the action of "the base station transmits configuration information regarding the configuration of the terminal" and the action of "the terminal configures a predetermined operation based on the configuration information".
[0138] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.
[0139] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.
[0140] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0141] The radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.
[0142] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. Note that a certain time unit may be divided into time units shorter than the certain time unit. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Any time unit in the present disclosure may be read as another time unit.
[0143] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.
[0144] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed, for example, of one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.
[0145] Resources in both the time domain and the frequency domain may be defined by one or more time / frequency units, each of which is composed of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) composed of one symbol and one subcarrier, a resource element group (REG) composed of a predetermined number of REs, or a control resource set (CORESET) composed of a predetermined number of symbols and a predetermined number of RBs.
[0146] The resources in the spatial domain may be defined, for example, by one or more spatial units, including, but not limited to, a beam, a layer of a multi-input multi-output (MIMO), an antenna port, or a combination of at least two of these.
[0147] The resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.
[0148] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0149] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc. [Explanation of symbols]
[0150] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device
Claims
1. a first unit included in a base station and having a radio interface with a terminal, a control unit that generates setting information related to data collection in AI / ML (Artificial Intelligence / Machine Learning); a transmitting unit included in the base station, configured to transmit the generated setting information to a second unit that controls the first unit;
2. The first unit according to claim 1 , further comprising: a receiving unit configured to receive applicability information from the second unit indicating whether a setting related to the AI / ML function is applicable to the terminal.
3. The first unit according to claim 2 , wherein the receiver receives, from the second unit, information indicating whether the terminal holds measurements.
4. a second unit included in the base station for controlling the first unit, a transmitter that transmits a message requesting setting information related to data collection in AI / ML (Artificial Intelligence / Machine Learning) to the first unit; a receiving unit that receives the setting information from the first unit;
5. The receiving unit receives, from a terminal, applicability information indicating whether a setting related to the AI / ML function is applicable to the terminal; The second unit according to claim 3 , wherein the transmitter transmits the applicability information to the first unit.
6. A communication method carried out by a first unit included in a base station and having a radio interface with a terminal, and a second unit controlling the first unit, the method comprising: sending a message from the first unit to the second unit requesting configuration information related to data collection in AI / ML (Artificial Intelligence / Machine Learning); transmitting the setting information from the second unit to the first unit.