Base station and communication method

WO2026181441A1PCT designated stage Publication Date: 2026-09-03NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/041642
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-02-28
Filing Date
2025-11-28
Publication Date
2026-09-03

Smart Images

  • Figure JP2025041642_03092026_PF_FP_ABST
    Figure JP2025041642_03092026_PF_FP_ABST
Patent Text Reader

Abstract

This base station includes a distributed unit and a radio unit. The distributed unit and the radio unit have: a communication unit that transmits and receives, between the distributed unit and the radio unit, a full message including all parameters in configuration information relating to channel estimation and beamforming based on a sounding reference signal (SRS), and an update message including some updated parameters in the configuration information; and a control unit that updates the updated parameters using the full message and the update message.
Need to check novelty before this filing date? Find Prior Art

Description

Base Station and Communication Method

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

[0002] In NR (New Radio) (also referred to as "5G"), which is a wireless communication system based on the 3GPP (registered trademark) standard, and systems succeeding NR (for example, "6G"), technologies that satisfy requirements such as large-capacity systems, high data transmission rates, low latency, simultaneous connection of a large number of terminals, low cost, and power saving are being studied (for example, Non-Patent Document 1).

[0003] In addition, in O-RAN (Open-Radio Access Network), studies are being conducted to improve bandwidth requirements in the Open Fronthaul between a distributed unit (O-DU (Distributed Unit)) and a radio unit (O-RU (Radio Unit)) in a base station.

[0004] 3GPP TS 38.300 V18.3.0 (2024-09)

[0005] In the fronthaul split option in the conventional art, an SRS (Sounding Reference Signal) channel estimation and an SRS processing function are arranged in a distributed unit (O-DU). Here, in O-RAN, it is studied to improve the bandwidth of the open fronthaul by arranging the SRS channel estimation and the SRS processing function in a radio unit (O-RU) and executing beamforming (BF) based on SRS in the radio unit.

[0006] However, in the conventional art, since a large amount of data such as SRS channel estimation results and beamforming weights cannot be efficiently transmitted, there is a problem that bandwidth consumption in the open fronthaul cannot be improved.

[0007] The present invention has been made in view of the above points, and an object of the present invention is to efficiently transmit information related to channel estimation and beamforming in a wireless communication system.

[0008] According to the disclosed technology, a base station is provided which includes a distributed unit and a radio unit, the distributed unit and the radio unit having a communication unit that transmits and receives between the distributed unit and the radio unit a full message containing all parameters in configuration information relating to channel estimation and beamforming based on SRS (Sounding Reference Signal), and an update message containing some updated parameters in the configuration information, and a control unit that performs an update of the updated parameters using the full message and the update message.

[0009] According to the disclosed technology, information regarding channel estimation and beamforming can be transmitted efficiently in a wireless communication system.

[0010] This figure shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. This figure shows an example configuration (2) of a wireless communication system according to an embodiment of the present invention. This figure shows an example configuration (3) of a wireless communication system according to an embodiment of the present invention. This figure illustrates beamforming based on SRS according to an embodiment of the present invention. This figure shows an example of the structure of a Delta-Section according to an embodiment of the present invention. This figure shows an example of a first sequence diagram according to an embodiment of the present invention. This figure shows an example of a second sequence diagram according to an embodiment of the present invention. This figure shows an example of the functional configuration of a base station 10 according to an embodiment of the present invention. This figure shows an example of the functional configuration of a terminal 20 according to an embodiment of the present invention. This figure shows an example of the hardware configuration of a base station 10 or terminal 20 according to an embodiment of the present invention. This figure shows an example of the configuration of a vehicle 2001 according to an embodiment of the present invention.

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

[0012] Existing technologies may be used as appropriate in the operation of the wireless communication system according to the embodiment of the present invention.

[0013] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies may include, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0014] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies may include, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0015] Furthermore, in the embodiments of the present invention described below, terms 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), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".

[0016] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).

[0017] Furthermore, in embodiments of the present invention, "configuring" wireless parameters means that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured. Also, in the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.

[0018] Figure 1 shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. The wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.

[0019] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, in NR-PBCH and is also called broadcast information. Synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Also, both the base station 10 and the terminal 20 may communicate via Carrier Aggregation (CA) through secondary cells (SCell) and primary cells (PCell). Additionally, the terminal 20 may communicate via Dual Connectivity (DC) through the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10.

[0020] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, 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. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.

[0021] Furthermore, various requirements are being considered for the next generation of 6G. For example, these requirements may include ultra-broadband communication, mission-critical communication, ultra-massive connection, universal coverage, intelligent connection, and ubiquitous sensing.

[0022] Furthermore, these requirements may include ultra-high-speed communication, large-capacity communication, ultra-wide coverage, ultra-low power consumption, cost reduction, ultra-low latency, ultra-high reliability communication, ultra-high connectivity, and sensing.

[0023] To meet these requirements, the new concept aims for extensibility (e.g., making it more effective for future use), ease of operation, customizability (e.g., making it easier to operate), and sustainability (e.g., cost reduction, a more robust configuration, and resilience). Furthermore, guaranteed communication, ensuring a minimum level of performance at all times, is being considered.

[0024] Figure 2 shows an example configuration (2) of a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A that will be an MN (Master Node) and a base station 10B that will be an SN (Secondary Node) are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B.

[0025] A cell group provided by base station 10A, which is an MN (Mobile Network), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Mobile Network), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells.

[0026] Figure 3 shows an example configuration (3) of a wireless communication system according to an embodiment of the present invention. As shown in Figure 3, the radio unit O-RU10A communicates with the distributed unit O-DU10B and the SMO (Service Management and Operation) 30A via an Open Fronthaul (or simply a Fronthaul). The SMO 30A communicates with the central control unit O-CU10C via the O1 interface and with the virtualization environment O-Cloud 30B, which provides RAN functions, etc., via the O2 interface. The O-DU10B and O-CU10C communicate via the F1 interface.

[0027] O-DU, O-CU, O-RU, and SMO may be deployed on the same base station, on different base stations, or in different locations other than base stations (nearby, remote, etc.). They may be treated as base station equipment or as network nodes. Furthermore, O-DU and O-CU may be deployed on a virtualization infrastructure and may be denoted as vDU (virtual DU) and vCU (virtual CU), for example.

[0028] In O-RAN (Open-Radio Access Network), improvements are being considered to improve the bandwidth requirements in the open fronthaul between distributed units (O-DUs) and radio units (O-RUs) at base stations.

[0029] In conventional front hole splitting options, the SRS (Sounding Reference Signal) channel estimation and SRS processing functions are located in the distributed unit (O-DU). For example, in conventional technology, based on scheduling messages from the O-DU, an SRS IQ stream is sent from the O-RU to the O-DU, and SRS channel estimation and SRS processing are performed on the O-DU side. Furthermore, when using CIBF (Channel Information-Based Beamforming) in a Category B O-RU, estimated channel information is sent from the O-DU to the O-RU. Also, when using WDBF (Weight-Based Beamforming), the O-DU calculates beamforming weights using the estimated channels and sends them to the O-RU.

[0030] Figure 4 is a diagram illustrating beamforming based on SRS in an embodiment of the present invention. As shown in Figure 4, in O-RAN, it is being considered to place the SRS channel estimation and SRS processing functions in the radio unit (O-RU) and perform SRS-based beamforming in the radio unit. This makes it possible to significantly reduce the front hole bandwidth, as it is possible to omit the transmission of beamforming weights from the O-DU to the O-RU in the case of WDBF, and to omit the transmission of channel information from the O-DU to the O-RU in the case of CIBF.

[0031] However, conventional technologies have the problem of not being able to improve bandwidth consumption in open fronthaul because they cannot efficiently transmit large amounts of data such as SRS channel estimation and beamforming weights.

[0032] For example, in a beamforming fronthaul based on SRS, transmitting all information regarding channel estimation results and beamforming weights places a significant load on the fronthaul. Furthermore, even when adding section extensions to existing section types as needed, a large amount of information is transmitted redundantly.

[0033] Furthermore, from the perspective of real-time adaptability, in scenarios where dynamic changes such as multi-RAT (Radio Access Technology) operation and frequency reassignment occur frequently, rapid changes become difficult when the amount of information transmitted is large. Also, methods that transmit large amounts of data at once make it difficult to shorten the update cycle.

[0034] The following describes methods for efficiently transmitting channel estimation and beamforming information in a wireless communication system. Two methods are described below: Method 1 (Base Configuration, full configuration transmission), which transmits all configuration information related to channel estimation and beamforming, and Method 2 (Delta Update, differential update), which transmits only the differences from the previously transmitted configuration information. Initially, all information must be transmitted using Method 1, but depending on the situation, it is possible to reduce the amount of information transmitted by using Method 2.

[0035] (Method 1) Base Configuration (Full Configuration) This section describes a method for transmitting all configuration information related to channel estimation and beamforming. The data transmission direction is mainly from O-DU to O-RU, but it may also be transmitted from O-RU to O-DU. For example, O-RU may perform SRS channel estimation and transmit the estimation results to O-DU. Cases in which all configuration information is transmitted include when initial settings are transmitted, and when the configuration information is significantly changed. The configuration information may include, for example, UE list, number of antenna ports, SRS period / pattern, beamforming algorithm, and compression method. The format of the message transmitting the configuration information may use existing O-RAN specifications / newly defined section types / section extensions. Details of Method 1 (Methods 1-1 to 1-5), examples (Examples 1-1 to 1-10), and variations (Variations 1-1 to 1-3) are described below.

[0036] (Method 1-1) Definition of a new section type The O-DU and O-RU may assume that a newly defined section type (section type X) is used for transmitting information related to beamforming based on SRS.

[0037] Furthermore, O-DU and O-RU may assume that section type X includes a field for efficiently transmitting SRS channel estimation results / parameters necessary for beamforming.

[0038] Furthermore, O-DU and O-RU may assume that said Section Type X is transmitted in both the direction from O-DU to O-RU and the direction from O-RU to O-DU.

[0039] (Method 1-2) Definition of New Section Extension O-DU and O-RU may assume that a newly defined section extension (Section Extension Y) for transmitting additional information related to SRS-based beamforming is used.

[0040] Furthermore, O-DU and O-RU may assume that said Section Extension Y includes a field for efficiently transmitting configuration information / control parameters required for SRS processing.

[0041] Furthermore, O-DU and O-RU may assume that said Section Extension Y is transmitted in both the direction from O-DU to O-RU and the direction from O-RU to O-DU.

[0042] (Method 1-3) Efficient Information Transmission by Data Compression O-DU and O-RU may compress information such as SRS channel estimation results / beamforming weights and transmit and receive the compressed information via the fronthaul. Further, O-DU and O-RU may transmit and receive Section Type X / Section Extension Y in which the compressed information is set.

[0043] (Method 1-4) Ensuring Compatibility and Extensibility O-DU and O-RU may maintain compatibility with existing section types / section extensions, and may assume that the newly defined Section Type X / Section Extension Y is introduced / used.

[0044] (Method 1-5) Use of Existing Section Types / Section Extensions O-DU and O-RU may set information related to SRS-based beamforming in unused areas (reserved fields, reserved bits, etc.) of existing section types / section extensions, and may assume that the information is transmitted and received.

[0045] Note that the section type / section extension may also be referred to as a message, or information / field / format, etc. included in a message.

[0046] Examples are described below.

[0047] (Example 1-1) Definition and application of new section type X A newly defined section type (section type X) for transmitting information related to beamforming based on SRS may have, for example, the configuration described below.

[0048] The common header field of section type X may include the following information: · dataDirection (1 bit): indicates the direction of data (0: downlink, 1: uplink). · payloadVersion (3 bits): indicates version information of the payload. · filterIndex (4 bits): specifies the index of a filter. · frameId (8 bits): indicates a frame number. · subframeId (4 bits): indicates a subframe number. · slotId (6 bits): indicates a slot number. · startSymbolId (6 bits): indicates a start symbol ID. · numberOfSections (8 bits): indicates the number of sections. · sectionType (8 bits): sets the identifier of section type X (for example, the value is set to 128). · reserved (8 bits): bits reserved for future expansion.

[0049] The section field of section type X may include the following information: · sectionId (12 bits): an identifier of a section. · srsChannelEstimate (variable length): a field including an SRS channel estimation result.

[0050] Here, srsChannelEstimate may have the following data structure: • numAntennas (8 bits): Indicates the number of antennas. • channelCoefficients (complex array): Contains the channel coefficients for each antenna. Here, each coefficient may be represented by 16 bits each for I (In-phase component) and Q (Quadrature component).

[0051] (Continued from section field) ・beamformingParameters (variable length): Parameters required for beamforming.

[0052] Here, beamformingParameters may have the following data structure: • beamId (15 bits): beam identifier. • beamWeights (variable length): beamforming weights. Here, data compression may be applied to the weight data to reduce the amount of data.

[0053] (O-RU operation with respect to section type X) The O-RU may receive the SRS signal, perform channel estimation, and then store the estimation result in the srsChannelEstimate field in section type X.

[0054] Additionally, the O-RU may, if necessary, calculate beamforming parameters and store the calculation results in the beamformingParameters field.

[0055] Additionally, the O-RU may create a message of section type X and send it to the O-DU.

[0056] (O-DU operation with respect to section type X) The O-DU may analyze section type X received from the O-RU and obtain the information contained in srsChannelEstimate and beamformingParameters.

[0057] The O-DU may perform beamforming control / resource allocation for the entire network based on the information obtained from section type X received from the O-RU.

[0058] (Example 1-2) Definition and Application of Section Extension Y A newly defined section extension (section extension Y) for transmitting additional information regarding beamforming based on SRS may have the following configuration, for example.

[0059] The extension header field of section extension Y may include the following information: • extType (7 bits): Identifier of section extension Y (e.g., set to value 128). • ef (1 bit): Flag indicating whether the extension continues (0: end, 1: continue). • extLen (8 bits or 16 bits): Indicates the length of the section extension in 32-bit words.

[0060] The extended fields of section extension Y may include the following information: srsConfiguration: SRS configuration information, including the following: srsPeriodicity (8 bits): SRS transmission period. srsBandwidth (8 bits): SRS bandwidth. srsConfigurationIndex (10 bits): Index of the SRS configuration. controlParameters: Beamforming control parameters, including the following information: bfAlgorithmType (4 bits): Type of beamforming algorithm (e.g., 0 = maximum ratio combining, 1 = zero forcing). bfWeightUpdateInterval (8 bits): Update interval for beamforming weights.

[0061] (O-DU operation regarding section extension Y) The O-DU may create a message including section extension Y by setting SRS configuration information / beamforming control parameters in the field of section extension Y, and send the message to the O-RU.

[0062] (O-RU operation regarding section extension Y) The O-RU may analyze the section extension Y received from the O-DU and update the SRS transmission settings based on the information contained in srsConfiguration, or it may perform beamforming processing settings based on the information contained in controlParameters.

[0063] (Examples 1-3) Data Compression and Efficient Information Transmission The O-DU and O-RU may be transmitted, for example, by applying Block Floating Point compression to the channel coefficients using a field containing the following information as information regarding the channel estimation result: • bfwCompHdr (8 bits): Specifies the compression method and bit width. • bfwIqWidth (4 bits): Bit width for I / Q. • bfwCompMeth (4 bits): Compression method (e.g., 0001 = Block Floating Point).

[0064] The bfwCompParam includes the following information: • exponent (8 bits): The common exponent of the block.

[0065] As a method for compressing beamforming weights, μ-law compression is applied to reduce the amount of data through nonlinear quantization.

[0066] This reduces the amount of data for channel estimation results and beamforming weights, thereby improving the efficiency of fronthaul bandwidth utilization.

[0067] (Examples 1-4) Dynamic control using a combination of new section type X and section extension Y. The O-DU may send a message to the O-RU containing a section extension Y configured to instruct the O-RU to update the SRS settings / beamforming parameters depending on the network conditions.

[0068] The O-RU may perform SRS channel estimation / beamforming processing according to instructions received from the O-DU.

[0069] Furthermore, the O-RU may send a message to the O-DU containing a section type X with updated channel estimation results / beamforming parameters.

[0070] As described above, by using section type X and section extension Y in combination, real-time control such as beamforming becomes more efficient, and network performance can be optimized.

[0071] (Examples 1-5) Maintaining compatibility with existing section types: To ensure compatibility, O-DU and O-RU may use the same message structure as existing section types / section extensions, and newly defined section types X and section extensions Y may use unused type values / additionally defined fields.

[0072] Furthermore, O-RU and O-DU may, as a fallback function, automatically switch to communication using an existing section type if the O-RU / O-DU does not support a newly defined section type / section extension.

[0073] This allows for compatibility with existing equipment and enables phased deployment.

[0074] (Example 1-6) Information transmission utilizing reserved fields of existing section types For example, the following SRS information may be set in the reserved field (reserved) of an existing section type 6, and the information may be transmitted and received. ・reserved (4 bits) Here, each bit of reserved indicates the following information: Bit 0 (SRS sequence number): SRS sequence number transmitted in 3 bits (0 to 7). Bit 1 (SRS subband information): Flag indicating the presence or absence of a subband. Bit 2 (Beam ID information): Flag indicating the presence or absence of a beam ID. Bit 3 (RRM measurement information): Flag indicating the presence or absence of RRM measurement information.

[0075] Alternatively, the rb field (1 bit) in existing section types may be redefined as a flag indicating the presence or absence of CSI information.

[0076] (O-RU Operation) After receiving the SRS signal and performing channel estimation and necessary measurements, the O-RU may include the SRS sequence number and subband information in the reserved field. Here, the SRS sequence number is the number indicating the SRS sequence used, and the subband information is information indicating the start position and length of the subband used.

[0077] Furthermore, the O-RU may include beam ID information / RRM measurement information in the reserved field as needed. Here, the beam ID is an identifier for the beam used for beamforming, and the RRM measurement information is information such as RSSI, SINR, and channel quality indicator (CQI).

[0078] Additionally, the O-RU may indicate the presence or absence of CSI information in the rb field, and may include detailed CSI information in the data portion of Section Type 6.

[0079] (O-DU operation) The O-DU may parse the section type 6 message received from the O-RU, extract the necessary information from the reserved / redefined fields, and use the extracted information for scheduling, beamforming control, and resource allocation.

[0080] (Example 1-7) Information transmission utilizing the reserved field of a section extension For example, the reserved field (reserved) of an existing section extension 21 may be set with the following information, and the information may be transmitted and received. ・reserved (6 bits) Here, each bit of reserved represents the following information.

[0081] Bits 0-1 (Compression Method Selection): Specifies the compression method (00: Uncompressed, 01: Block Floating Point, 10: μ-law, 11: Other).

[0082] Bits 2-3 (Quantization Bits): Specifies the number of quantization bits (00: 4 bits, 01: 8 bits, 10: 12 bits, 11: 16 bits).

[0083] Bit 4 (Presence or absence of subsampling information): Indicates whether or not subsampling information is included.

[0084] Bit 5 (Presence or absence of additional channel information): Indicates whether additional information such as fading information and delay spread is included.

[0085] (O-DU operation) The O-DU may use section extension 21 to instruct the O-RU on the compression method and quantization bit depth. If subsampling information / additional channel information is required, it may be specified in the reserved field, and detailed information may be included in the data portion of section extension 21.

[0086] (O-RU operation) The O-RU may obtain compression parameters from the reserved field of section extension 21 received from the O-DU. Here, information regarding the channel estimation results may be compressed based on the specified compression scheme / quantization bit depth. The O-RU may also apply subsampling as needed and send additional channel information to the O-DU in combination with section type 6.

[0087] (Examples 1-8) Data protection for enhanced security O-DU and O-RU may assume that, as data encryption, an encryption method such as AES-256 is applied to important information transmitted in section type X / section extension Y.

[0088] O-DU and O-RU may assume that, as a measure of data integrity, an authentication code such as HMAC (Hash Based Message Authentication Code) is attached to each message.

[0089] This ensures the confidentiality and integrity of data, and reduces security risks.

[0090] (Example 1-9) Transmission of machine learning parameters by extending section extension Y O-DU and O-RU may assume that a field mlModelParameters containing the following information about machine learning parameters is added to section extension Y: ・modelType (4 bits): The type of machine learning model to use (e.g., 0 = linear regression, 1 = neural network). ・modelParameters (variable length): Parameters such as model weights and biases.

[0091] O-DU may set parameters related to updating machine learning models, etc., in section extension Y and send them to O-RU.

[0092] O-RU may use parameters related to updating the machine learning model, etc., included in section extension Y received from O-DU to perform processes such as channel prediction / beamforming optimization.

[0093] This makes it possible to improve communication performance by utilizing advanced machine learning algorithms.

[0094] (Example 1-10) Efficient reporting of channel state information (CSI) by section type X The O-DU and O-RU may assume that the compressed CSI (Channel State Information) is set in the csiReport (variable length) field of section type X shown below, and that section type X is transmitted from the O-RU to the O-DU. ・csiCompressionMethod (4 bits): Specifies the CSI compression method. ・compressedCsiData (variable length): Compressed CSI data.

[0095] This makes it possible to efficiently provide the required CSI from O-RU to O-DU while saving fronthaul bandwidth.

[0096] (Example 1-11) Application to Multi-User Beamforming The O-DU and O-RU may be assumed to transmit a section type X in which information on beamforming for multiple users is simultaneously set in the fields shown below: ・userId (16 bits): User identifier. ・beamformingParameters: Channel estimation results / beamforming parameters for each user.

[0097] The O-RU may receive SRS from multiple users' terminals, perform channel estimation using each SRS, set each user's information, including the channel estimation results, in section type X, and report it to the O-DU.

[0098] This makes it possible to streamline beamforming control in multi-user environments.

[0099] (Example 1-12) Frequency Hopping / Discontinuous PRB Allocation Support The O-DU and O-RU may assume that information regarding frequency hopping / discontinuous PRB (Physical Resource Block) allocation is set in the field frequencyHoppingParameters of section extension Y shown below. ・hoppingPattern (8 bits): Specifies the frequency hopping pattern. ・prbAllocation (variable length): Contains discontinuous PRB allocation information.

[0100] The O-DU may instruct the O-RU to perform the frequency hopping / discontinuous PRB assignment by transmitting a section extension Y containing the setting.

[0101] The O-RU may perform SRS transmission / beamforming processing based on the instructions, including section extension Y, received from the O-DU.

[0102] This enables efficient use of frequency resources and reduction of interference.

[0103] The following describes some variations.

[0104] (Modification 1-1) Sharing of statistical information on SRS data The O-RU may send statistical information about SRS (e.g., mean SNR, user distribution) to the O-DU instead of detailed SRS data. This can reduce the amount of data transmitted and improve the efficiency of fronthaul bandwidth utilization.

[0105] (Modification 1-2) Prediction of processing mode by machine learning The O-RU may use a machine learning model to predict / select the optimal SRS processing mode. Here, the SRS processing mode may be, for example, one of the following modes: ・Local processing mode: The O-RU performs SRS channel estimation and beamforming weight generation, and then performs beamforming. ・Shared processing mode: The O-RU performs SRS channel estimation and sends a portion of the estimation results (only the necessary parameters) to the O-DU. ・Fully shared mode: The O-RU sends SRS IQ data to the O-DU, and the O-DU performs the processing.

[0106] Furthermore, the O-RU may perform training / retraining of the machine learning model using training data acquired / generated by its own device. Alternatively, the O-RU may acquire the machine learning model from the O-DU, O-CU, or SMO. The O-RU may also transmit training data for training the machine learning model to the O-DU, O-CU, or SMO. Here, section type X / section extension Y may be used in the transmission and reception of the machine learning model / training data.

[0107] (Modification 1-3) Cooperation between multiple O-RUs The O-DU and O-RU may assume that SRS information is shared among multiple O-RUs to perform cooperative beamforming. Here, an O-RU may transmit SRS information to other O-RUs. Alternatively, an O-RU may receive SRS information from other O-RUs and perform beamforming-related processing based on said SRS information.

[0108] (Method 2) Delta Update (Differential Update) This method describes how to transmit only the difference between the transmitted configuration information and the configuration information already transmitted, for all configuration information related to channel estimation and beamforming. The direction of data transmission is mainly from O-DU to O-RU, as in Method 1, but it may also be transmitted from O-RU to O-DU. For example, O-RU may perform SRS channel estimation and transmit only a portion of the estimation results to O-DU.

[0109] O-DU and O-RU may be assumed to use a newly defined parameter (Delta-Section) to specify the identifier (BaseConfigId) of the base configuration information (Base Configuration), and to send only the parameters to be updated (such as UE ID and BF weight) from the specified configuration information.

[0110] Figure 5 shows an example of the structure of a Delta-Section in an embodiment of the present invention. Figure 5 includes the items set in the Delta-Section, a description of each item, and an example of the settings. Each item will be described below.

[0111] deltaSectionType is an identifier that indicates a section type specifically for differential updates. This identifier is assigned an unused type value (e.g., 0x90). O-RU and O-DU recognize that a message is for differential updates by referring to this ID.

[0112] `baseConfigId` is an identifier that indicates the corresponding full configuration (Base Configuration). This identifier is associated with the full configuration that is sent during system startup and major changes, and `Delta-Section` updates some of the settings within the configuration information specified by this identifier.

[0113] deltaCount indicates the number of differential parameters to be updated in the message. For example, if 2 is specified, the two subsequent items (deltaItem[0] and deltaItem[1]) will describe the differential parameters to be updated.

[0114] deltaItem[n] represents a pair of identifiers (targetParamId) indicating the parameter to be updated in the configuration information, and the updated value (newValue). If there are updates for multiple parameters, it will be in list format, such as deltaItem[0], deltaItem[1], ...

[0115] `targetParamId` is an identifier that indicates the parameter to be updated in the configuration information. Specific parameters such as the UE's beamforming algorithm and frequency allocation are specified.

[0116] `newValue` indicates the updated value. It is written in a format corresponding to the parameter being updated, such as algorithm type, frequency range, or BF weight. Here, `New Value` can be the new value after the update, or it can be the difference between the value before and after the update. For example, for beamforming weights, the difference between the value before and after the update can be set. When setting a difference, a flag indicating that it is a difference may be notified, or the difference may be set and notified using a different parameter (for example, `deltaValue` instead of `newValue`).

[0117] Furthermore, O-DU and O-RU may assume that configuration information for multiple terminals is transmitted simultaneously within a single frame by multiple Delta-Sections. Here, the premise is that the Base configuration is the configuration for each terminal, and if there are configuration differences between terminals, a Delta-section may be sent for each terminal identifier in the same frame. Alternatively, the terminal identifier associated with targetParamId and newValue may be included in a single deltaItem to notify each terminal of configuration updates.

[0118] By using Method 2, it becomes unnecessary to repeatedly transmit the full information, thus significantly saving fronthaul bandwidth.

[0119] For example, Method 2 may be carried out using the following procedure.

[0120] Step 1: The O-DU sends the full configuration (Base Configuration) to the O-RU as an initial setup.

[0121] Step 2: If environmental changes or RAT switching occur, the O-DU uses Delta-Section to send a message to the O-RU containing the updated parameters.

[0122] Step 3: The O-RU updates the parameter values ​​received in Step 2 by referring to the Base Configuration received in Step 1.

[0123] By following the above procedure, not all parameters are transmitted in step 2, which reduces bandwidth and allows for quick response to dynamic changes.

[0124] The following describes examples of Method 2 (Examples 2-1 and 2-2).

[0125] (Example 2-1) As an example of the SRS BF algorithm switching method 2, a procedure for transmitting only the difference setting information when switching the beamforming (BF) algorithm based on SRS (Sounding Reference Signal) will be described. Figure 6 is a diagram showing an example of the first sequence diagram in an embodiment of the present invention. The processing of each step will be described below.

[0126] S101: O-DU10B sends a message to O-RU10A containing all configuration information (Base Configuration) as the initial setting for the SRS BF algorithm. Here, the configuration information may include, for example, an algorithm based on MMSE (Minimum Mean Squared Error), an SRS transmission period of 10ms, and the number of ports for the three terminals (UE0, UE1, and UE2) of 2. Furthermore, the format of the message may use existing O-RAN specifications, newly defined section types, or section extensions.

[0127] Based on the received configuration information (Base Configuration), the O-RU10A stores / sets the initial settings for the SRS BF algorithm within its own device.

[0128] S102: O-DU10B detects changes in channel status. For example, O-DU10B may detect changes in channel status based on deterioration of SNR (Signal to Noise Ratio) / CQI (Channel Quality Indicator), increase in error rate, and increase in retransmission count obtained from RRM (Radio Resource Management) measurement / SRS report received from O-RU10A. Here, the RRM measurement / SRS report may be performed by O-RU10A based on SRS received from terminal 20. Alternatively, O-DU10B may detect changes in channel status based on feedback information received from O-RU10A.

[0129] Furthermore, based on the detection of changes in channel conditions, the O-DU10B decides to update the settings related to the SRS BF algorithm, which is part of the configuration information. For example, the O-DU10B may analyze the feedback information received from the O-RU10A and determine that the MMSE-based algorithm does not provide sufficient gain, and then decide to update the algorithm.

[0130] S103: O-DU10B decides to send differential configuration information in response to the channel status change detected in S102, and generates a message containing differential configuration information (Delta-Section). For example, O-DU10B may decide in the configuration information to change the beamforming algorithm for UE1 to an algorithm based on SVD (Singular Value Decomposition). Here, Delta-Section is set, for example, as targetParamId = BF_Algo_UE1, newValue = SVD.

[0131] S104: O-DU10B sends the message generated in S103 to O-RU10A.

[0132] S105: O-RU10A updates the settings for the SRS BF algorithm based on all the configuration information (Base Configuration) received in S101 and the differential configuration information (Delta-Section) received in S104. For example, O-RU10A refers to the baseConfigId of the received Delta-Section and updates the algorithm for UE1 from MMSE to SVD based on the initial full configuration (Base Configuration). This ensures that the SVD algorithm is applied to subsequent slots / frames and can accommodate changed channels. Furthermore, since O-RU10A does not change the algorithm settings for UE0 and UE2, the update of configuration information is minimal.

[0133] S106: O-RU10A communicates with terminal 20 using beamforming based on the settings updated in S105.

[0134] (Example 2-2) As an example of the second method for fine-tuning beamforming weights, the procedure for transmitting only the difference setting information when fine-tuning beamforming (BF) weights will be described. Figure 7 is a diagram showing an example of the second sequence diagram in an embodiment of the present invention. The processing of each step will be described below.

[0135] S201: During initial setup or significant configuration changes, the O-RU10A performs SRS channel estimation and BF weight generation, generating BF weights for each port of the four terminals (UE0, UE1, UE2, UE3), and stores all configuration information (Base Configuration) including these weights in its own device. At this point, the BF weights are not transmitted from the O-DU10B to the O-RU10A.

[0136] S202: O-RU10A uses the BF weights generated in S201 to communicate with terminals 20 (UE0, UE1, UE2, UE3).

[0137] S203:O-RU10A detects a decrease in link quality in UE2 by performing internal SRS measurement based on analysis of SRS received from the terminal.

[0138] The following describes two methods for fine-tuning the BF weights (Alt.1 (S204) and Alt.2 (S205-S208)).

[0139] (Alt.1) S204: O-RU10A calculates the BF weights based on internal processing and updates the currently set BF weights for UE2.

[0140] (Alt.2) S205: O-RU10A sends a report message to O-DU10B indicating the degraded link quality at UE2 detected in S203.

[0141] S206: O-DU10B calculates BF weights to improve the degraded link quality in UE2 and generates a message containing differential configuration information (Delta-Section) using the calculated BF weight values. For example, in Delta-Section, O-DU10B sets the BF weights for port 0 and port 1 of UE2 as follows: ・targetParamId = BFWeight_UE2_port0, newValue = Δw2_0 ・targetParamId = BFWeight_UE2_port1, newValue = Δw2_1 S207: O-DU10B sends the message generated in S206 to O-RU10A.

[0142] S208: Based on all the configuration information set in S201 (Base Configuration) and the differential configuration information received in S207 (Delta-Section), the O-RU10A updates the BF weights for port 0 and port 1, respectively, for UE2 with degraded link quality.

[0143] S209: O-RU10A performs communication with terminal 20 using beamforming based on the settings updated in S208.

[0144] (Effects) By using the method and examples described above, it is possible to avoid retransmissions by notifying only the changes, thereby reducing the bandwidth of the fronthaul. In addition, since partial corrections can be made in real time immediately in response to channel quality degradation, the response speed can be improved.

[0145] Therefore, the above-described method and embodiments enable efficient transmission of channel estimation and beamforming information in a wireless communication system. The above-described method, embodiments, and variations may be used in combination.

[0146] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the above-described embodiment. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0147] <Base Station 10> Figure 8 is a diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. As shown in Figure 8, 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 Figure 8 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

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

[0149] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20.

[0150] The control unit 140 performs control related to the processing described in the embodiment. The control unit 140 also performs scheduling. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0151] Furthermore, the base station 10 may include a distributed unit (O-DU) and a wireless unit (O-RU), and the distributed unit (O-DU) and the wireless unit (O-RU) may each have a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. Also, the distributed unit (O-DU) and the wireless unit (O-RU) may communicate with each other using the transmitting unit 110 and the receiving unit 120.

[0152] <Terminal 20> Figure 9 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 9, 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 Figure 9 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

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

[0154] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-configured setting information.

[0155] The control unit 240 performs control related to the processing described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

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

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

[0158] For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 10 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to 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 storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

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

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

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

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

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

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

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

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

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

[0169] O-CU may be interpreted as CU, control device, communication device, aggregation device, central device, management device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, O-CU may be interpreted as a central unit, aggregation node, etc.

[0170] O-DU may be interpreted as DU, control device, communication device, distributed device, high-PHY device, etc. Each of these devices may be rephrased as unit, node, etc. For example, O-DU may be interpreted as distributed unit, distributed node, etc.

[0171] O-RU may be interpreted as RU, radio equipment, RF (Radio Frequency) equipment, low PHY equipment, etc. Each piece of equipment may be rephrased as a unit, node, etc. For example, O-RU may be interpreted as a radio unit, radio node, etc.

[0172] SMO may be interpreted as a control device, communication device, or management device. Each of these devices may be rephrased as a unit, node, etc. For example, SMO may be interpreted as a management unit, management node, etc.

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

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

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

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

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

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

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

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

[0181] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

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

[0183] <Notes> (Note 1) A base station comprising a distributed unit and a radio unit, wherein the distributed unit and the radio unit have a communication unit that transmits and receives between the distributed unit and the radio unit a full message containing all parameters in configuration information relating to channel estimation and beamforming based on SRS (Sounding Reference Signal), and an update message containing some updated parameters in the configuration information, and a control unit that performs the update of the updated parameters using the full message and the update message. (Note 2) The base station according to Note 1, wherein the control unit performs the update of the updated parameters using information that identifies the updated parameters and the value of the updated parameters, or the difference between the updated parameters before and after the update, included in the update message. (Note 3) The base station according to Note 1, wherein the control unit of the distributed unit decides to update the beamforming algorithm when it detects a change in channel state, the communication unit of the distributed unit sends the update message containing information indicating the updated algorithm to the communication unit of the radio unit, and the communication unit of the radio unit performs communication with the terminal using beamforming according to the updated algorithm. (Note 4) The base station according to Note 1, wherein the control unit of the radio unit updates the beamforming weights corresponding to the terminal when it detects a decrease in link quality with the terminal, and the communication unit of the radio unit performs communication with the terminal using the updated beamforming weights.(Note 5) The base station according to Note 1, wherein the control unit of the wireless unit detects a decrease in link quality with a terminal, the communication unit of the wireless unit transmits a message to the communication unit of the distributed unit notifying it of the decrease in link quality, the control unit of the distributed unit calculates beamforming weights to improve the decrease in link quality and generates an update message including the calculated weights, the communication unit of the distributed unit transmits the update message to the communication unit of the wireless unit, and the communication unit of the wireless unit uses the beamforming weights included in the update message to communicate with the terminal. (Note 6) A communication method performed by a base station including a distributed unit and a wireless unit, comprising the steps of sending and receiving between the distributed unit and the wireless unit: a full message including all parameters in the configuration information relating to channel estimation and beamforming based on SRS (Sounding Reference Signal), and an update message including some updated parameters in the configuration information; and an update of the updated parameters using the full message and the update message.

[0184] Any of the provisions of Appendix 1 to Appendix 6 will enable efficient transmission of channel estimation and beamforming information in a wireless communication system.

[0185] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

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

[0187] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0207] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

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

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

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

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

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

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

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

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

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

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

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

[0219] This patent application claims priority based on Japanese Patent Application No. 2025-030976, filed on 28 February 2025, and the entire contents of Japanese Patent Application No. 2025-030976 are incorporated herein by reference.

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

Claims

1. A base station comprising a distributed unit and a radio unit, wherein the distributed unit and the radio unit have a communication unit that transmits and receives between the distributed unit and the radio unit a full message containing all parameters in configuration information relating to channel estimation and beamforming based on SRS (Sounding Reference Signal), and an update message containing some updated parameters in the configuration information, and a control unit that performs the update of the updated parameters using the full message and the update message.

2. The base station according to claim 1, wherein the control unit performs the update of the updated parameter using information that identifies the updated parameter, the value of the updated parameter, or the difference between the updated parameter before and after the update, which are included in the update message.

3. The base station according to claim 1, wherein the control unit of the distributed unit decides to update the beamforming algorithm when it detects a change in the channel state, the communication unit of the distributed unit sends the update message containing information indicating the updated algorithm to the communication unit of the wireless unit, and the communication unit of the wireless unit performs communication with a terminal using beamforming according to the updated algorithm.

4. The base station according to claim 1, wherein the control unit of the wireless unit updates the beamforming weights corresponding to the terminal when it detects a decrease in link quality with the terminal, and the communication unit of the wireless unit uses the updated beamforming weights to perform communication with the terminal.

5. The base station according to claim 1, wherein the control unit of the wireless unit detects a decrease in link quality with a terminal, the communication unit of the wireless unit transmits a message to the communication unit of the distributed unit notifying it of the decrease in link quality, the control unit of the distributed unit calculates beamforming weights to improve the decrease in link quality and generates an update message including the calculated weights, the communication unit of the distributed unit transmits the update message to the communication unit of the wireless unit, and the communication unit of the wireless unit uses the beamforming weights included in the update message to communicate with the terminal.

6. A communication method performed by a base station including a distributed unit and a radio unit, comprising the steps of sending and receiving between the distributed unit and the radio unit: a full message including all parameters in configuration information relating to channel estimation and beamforming based on SRS (Sounding Reference Signal); an update message including some updated parameters in the configuration information; and performing an update of the updated parameters using the full message and the update message.