WO2024062806A1 - Dispositif ru, dispositif de commande, procédé et programme - Google Patents

Dispositif ru, dispositif de commande, procédé et programme Download PDF

Info

Publication number
WO2024062806A1
WO2024062806A1 PCT/JP2023/029552 JP2023029552W WO2024062806A1 WO 2024062806 A1 WO2024062806 A1 WO 2024062806A1 JP 2023029552 W JP2023029552 W JP 2023029552W WO 2024062806 A1 WO2024062806 A1 WO 2024062806A1
Authority
WO
WIPO (PCT)
Prior art keywords
mode
rpc
message
control device
indicating
Prior art date
Application number
PCT/JP2023/029552
Other languages
English (en)
Japanese (ja)
Inventor
昌志 中田
右京 菱
鵬 邵
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Publication of WO2024062806A1 publication Critical patent/WO2024062806A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the present disclosure relates to an RU device, a control device, a method, and a program.
  • O-RAN Open-Radio Access Network
  • O-RU O-RAN Radio Unit
  • O-DU O-DU
  • RAN Distributed Units One of the purposes of the O-RAN fronthaul specification is to facilitate the connection between O-DU vendors and O-RUs from different vendors, and to realize multi-vendor radio access networks.
  • O-DU may also be simply called DU.
  • O-RU can also be simply called RU.
  • Non-Patent Document 1 defines specifications regarding M (Management)-Plane, which is defined for transmitting management data between O-RU and O-DU.
  • M-Plane provides management functionality for O-RU.
  • O-DU or SMO Service Management and Orchestration
  • SMO Service Management and Orchestration
  • Ethernet/IP/TCP Transmission Control Protocol
  • SSH Secure SHell
  • Ethernet/IP/TCP Transmission Control Protocol
  • TLS Transmission Control Protocol
  • Non-Patent Document 1 describes changing the O-RU Power State.
  • the O-RU performs normal operation (operation that is not in ES mode (Energy saving mode)), and when the Power State is SLEEPING, the O-RU operates in Energy saving mode.
  • the Power State of the O-RU is changed by the RU control device sending an RPC (Remote Procedure Call) message indicating configuration editing (edit-config) to the O-RU. That is, a change in the O-RU Power State is typically triggered by the RU controller.
  • RPC Remote Procedure Call
  • O-RAN-WG4.MP.0-v09.00 O-RAN Working Group 4 (Open Fronthaul Interfaces WG) Management Plane Specification”
  • Non-Patent Document 1 it is assumed that the DU device or the SMO is the main control entity and sets the state of the RU device.
  • Non-Patent Document 1 does not sufficiently consider this point.
  • One of the objectives that the embodiments disclosed in this specification aim to achieve is to provide a control device and an RU device that contribute to solving at least one of the problems, including the problems described above. It should be noted that this objective is only one of the objectives that the embodiments disclosed in this specification aim to achieve. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings.
  • the RU (Radio Unit) device includes: at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor autonomously causes the RU device to transition from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • ES Electronicgy Saving
  • a radio unit (RU) device includes: At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor requests an RU control device to transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is satisfied.
  • ES Electronicgy Saving
  • the controller includes: at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor transmits an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating a configuration edit (edit-config) to an RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • the controller includes: at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor transmits an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating a configuration edit (edit-config) to an RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to request the RU control device to transition the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. .
  • a method performed by a Radio Unit (RU) device includes: The method includes autonomously shifting the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • ES Electronicgy Saving
  • a method performed by a Radio Unit (RU) device includes: The method includes requesting the RU control device to shift the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • ES Electronicgy Saving
  • a method performed by a controller includes: including sending an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config) to the RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • a method performed by a controller includes: including sending an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config) to the RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to request the RU control device to transition the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. .
  • the program In the RU (Radio Unit) device, When a predetermined condition is met, the RU device is caused to perform processing including autonomously shifting from a normal mode to an ES (Energy Saving) mode.
  • ES Electronicgy Saving
  • the program In the RU (Radio Unit) device, If a predetermined condition is met, a process is executed that includes requesting the RU control device to shift the RU device from a normal mode to an ES (Energy Saving) mode.
  • a process is executed that includes requesting the RU control device to shift the RU device from a normal mode to an ES (Energy Saving) mode.
  • the program to the control device, Execute processing including sending an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config) to the RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • the program to the control device, Execute processing including sending an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config) to the RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to request the RU control device to transition the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. .
  • an RU device a control device, a method, and a program that contribute to solving at least one of a plurality of problems including the problems described above.
  • FIG. 11 is a diagram illustrating an example of a procedure for acquiring the state of an RU.
  • FIG. 3 is a diagram illustrating an example of a procedure for changing the state of an RU.
  • FIG. 3 is a diagram for explaining the Power State of RU.
  • FIG. 6 is a diagram showing possible transitions and combinations of “active” and “state” parameters.
  • , is a block diagram showing an example of a system.
  • FIG. 3 is a diagram illustrating an example of processing operations of the RU device and the control device of the present disclosure.
  • FIG. 7 is a diagram illustrating another example of the processing operation of the RU device and the control device of the present disclosure.
  • FIG. 7 is a diagram illustrating another example of the processing operation of the RU device and the control device of the present disclosure.
  • FIG. 11 is a diagram illustrating an example of a procedure for acquiring the state of an RU.
  • FIG. 3 is a diagram illustrating an example of a procedure for changing the state of an
  • FIG. 7 is a diagram illustrating another example of the processing operation of the RU device and the control device of the present disclosure. It is a figure showing an example of composition of a control device.
  • FIG. 2 is a diagram showing an example of the configuration of a DU device. A diagram showing an example of the configuration of an RU device.
  • FIG. 2 is a diagram showing a configuration example of an SMO device.
  • if means “when,” “at or around the time,” and “after,” depending on the context. "after”, “upon”, “in response to determining", “in accordance with a determination", or “detecting” may be interpreted to mean “in response to detecting”. These expressions may be interpreted to have the same meaning, depending on the context.
  • C (Control)-Plane is a protocol for transferring control signals.
  • U (User)-Plane is a protocol for transferring user data.
  • C/U-Plane supports a protocol stack that directly transmits signals used in eCPRI or RoE (Radio over Ethernet) via Ethernet, and an optional protocol stack that transmits signals via UDP (User Datagram Protocol)/IP.
  • S (Synchronization)-Plane is a protocol for achieving synchronization between devices.
  • S-Plane supports a protocol stack that transmits signals used in PTP (Precision Time Protocol) and SyncE (Synchronous Ethernet) over Ethernet.
  • M (Management)-Plane is a protocol that handles maintenance monitoring signals.
  • Ethernet/IP/TCP Transmission Control Protocol
  • SSH Secure SHell
  • Ethernet/IP/TCP Transmission Control Protocol
  • TLS Transmission Protocol stacks that transmit data using Layer Security
  • the O-RAN (Open-Radio Access Network) Alliance has adopted a configuration in which the RAN communication processing function can be separated into three components: RU (Radio Unit), DU (Distributed Unit), and CU (Central Unit). .
  • RIC RAN Intelligent Controller
  • SMO Service Management and Orchestration
  • RU and DU are connected by an open fronthaul.
  • CUS/M-Plane signals are transmitted through this open front hole between the RU and DU. Note that an open front hole may be used to connect the RU and the SMO, and the M-Plane signal may be transmitted through this open front hole.
  • the CUS-Plane signal is transmitted by the open fronthaul between the RU and DU.
  • the DU and SMO are connected by an O1 interface.
  • the CU and SMO are also connected through the O1 interface.
  • the managed RU corresponds to the NETCONF server
  • the device that manages (controls) the RU corresponds to the NETCONF client.
  • the NETCONF client may be located in the DU or in the SMO.
  • FIG. 1 is a diagram illustrating an example of an RU State acquisition procedure.
  • the RU controller uses the NETCONF ⁇ get> procedure to obtain the state of the RU.
  • the RU control device sends an RPC (Remote Procedure Call) message indicating acquisition (get) to the RU.
  • the RU sends an RPC reply (rpc-reply) message to the RU controller in response to the RPC message.
  • This RPC response message includes information indicating the state of the RU. That is, the RU control device can obtain the RU State by a ⁇ get> request.
  • the RU controller can change the RU's configurable state for RUs that support optional hardware-state features defined in the RU's hardware.
  • the RU controller can change the RU's configurable state using the NETCONF ⁇ edit-config> procedure without a reset.
  • FIG. 2 is a diagram illustrating an example of a procedure for changing the state of an RU.
  • the RU controller changes the RU's configurable state using the NETCONF ⁇ edit-config> procedure without reset.
  • the RU control device sends an RPC message indicating configuration editing (edit-config) to the RU.
  • the RU changes its state based on this RPC message. Then, if the change is successful, the RU sends an RPC response message indicating ⁇ OK> to the RU controller.
  • FIG. 3 An example of a configurable state of an RU is the power-state.
  • the power states of an RU include "AWAKE” and "SLEEPING".
  • Fig. 3 is a diagram used to explain the power states of an RU.
  • the RU control device can change the power state of an RU by using the NETCONF ⁇ edit-config> procedure. Specifically, the RU control device controls the power state of the RU by sending an RPC message indicating configuration editing (edit-config) to the RU and editing the "energy-saving-enabled" parameter of the RU.
  • - AWAKE This power state indicates that the RU is operating normally, i.e., it is not in ES (Energy Saving) mode.
  • - SLEEPING This power state indicates that the RU is in ES mode.
  • the RU control device can configure (update) parameters of the RU using the NETCONF ⁇ edit-config> procedure. For example, the RU control device performs activation by setting the value of the “active” parameter for the tx-array-carrier(s) element (and/or the rx-array-carrier(s) element) to “ACTIVE”. The RU control device performs deactivation by setting the value of the “active” parameter for the tx-array-carrier(s) element (and/or the rx-array-carrier(s) element) to “INACTIVE”.
  • the RU control device also puts the tx-array-carrier(s) element (and/or the rx-array-carrier(s) element) to sleep by setting the value of the “active” parameter for the tx-array-carrier(s) element (and/or the rx-array-carrier(s) element) to “SLEEP”.
  • the tx-array-carrier(s) element (and/or the rx-array-carrier(s) element) is in sleep mode when the value of the "active" parameter is "SLEEP" and the value of the "State” parameter is "READY".
  • Figure 4 shows possible transitions and combinations of the "active" and "state” parameters.
  • tx-array-carrier(s) is a data node that is generated by the RU control device and includes carrier configuration parameters, and is associated with the transmission array (tx-array) information of the RU.
  • rx-array-carrier(s) is a data node that is generated by the RU control device and includes carrier configuration parameters, and is associated with RU reception array (rx-array) information.
  • tx-array-carrier(s) and rx-array-carrier(s) are generated for each carrier and for each transmitting/receiving array, and the center frequency, bandwidth, transmission power, etc. of the carrier for the RU are set.
  • Fig. 5 is a block diagram showing an example of a system.
  • a system 1 has a DU device 10, an RU device 20, and an SMO device 30.
  • the DU device 10 may be a logical node that executes functions in the PDCP (Packet Data Convergence Protocol) layer, RLC (Radio Link Control) layer, and MAC (Media Access Control) layer, as well as upper functions of the physical layer.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • the upper functions of the physical layer may include, for example, encoding and modulation processing, furthermore, decoding and demodulation processing.
  • Functions in the PDCP layer may be executed in a logical node called a CU (Central Unit) (not shown).
  • CU Central Unit
  • the RU device 20 may be a logical node that executes physical layer lower function (PHY-Low) and RF (Radio Frequency) processing, or may be a physical device equipped with this logical node. good.
  • the lower function of the physical layer may be, for example, FFT (Fast Fourier Transform)/IFFT (Inverse FFT) processing, BF (Beam Forming) processing, etc.
  • the SMO device 30 maintains and orchestrates the RIC (RAN Intelligent Controller) and RAN (Radio Access Network), which are platforms that optimize radio resource management and automate operations.
  • RIC RAN Intelligent Controller
  • RAN Radio Access Network
  • the DU device 10 has a control section (control device) 11.
  • This control unit (control device) 11 corresponds to a NETCONF client.
  • the RU device 20 has a control section 21.
  • the RU device 20 itself or the control unit 21 corresponds to the NETCONF server.
  • the DU device 10 and the SMO device 30 are connected via an O1 interface. Furthermore, the DU device 10 and the RU device 20 are connected via an open front hole. This open front hole can transmit CUS-Plane signals and M-Plane signals.
  • control unit (control device) 11 may be provided in the SMO device 30 instead of the DU device 10.
  • the RU device 20 and the SMO device 30 may also be connected through an open front hole.
  • the open fronthaul connecting the DU device 10 and the RU device 20 transmits the CUS-Plane signal
  • the open fronthaul connecting the RU device 20 and the SMO device 30 transmits the M-Plane signal. to transmit.
  • FIG. 6 is a diagram illustrating an example of processing operations of the RU device and control device of the present disclosure.
  • the control device 11 transmits a message indicating acquisition (hereinafter sometimes referred to as "first request message") to the RU device 20 (step S11).
  • the message indicating the acquisition may be an RPC (Remote Procedure Call) message.
  • the RU device 20 transmits a response message (hereinafter sometimes referred to as a "first response message") to the control device 11 in response to the first message (step S12).
  • the response message may be an RPC response (rpc-reply) message. That is, the processing operations of the RU device and the control device in the first embodiment shown in FIG. 6 may be the processing operations of the RU device 20 and the control device 11 according to the NETCONF ⁇ get> procedure.
  • the "first request message” may be an RPC (Remote Procedure Call) message indicating acquisition (get-config).
  • the first request message may include, for example, "request information” indicating a request to the RU device 20 to transmit a first response message including "requested information.”
  • the request information may indicate a request for an entire information set including multiple information elements, or may indicate a request for each information element.
  • the requested information is "information related to the RU device 20," and may be, for example, capability information of the RU device 20.
  • the RU device 20 receives the first request message, and generates a first response message containing the requested information based on the request information of the first request message. For example, if the requested information is Capability information of the RU device 20, the first response message includes the Capability information.
  • the "information regarding the RU device 20" can be used, for example, for connection establishment between the RU device 20 and the control device 11. In the meantime (as part of the establishment procedure), the control device 11 may obtain it from the RU device 20.
  • the first message may include request information regarding any one or any combination (including all) of a plurality of information elements described below.
  • the first response message may include any one or any combination (including all) of a plurality of information elements described below, based on the request information.
  • the first response message may include part or all of the content related to any combination (including all) of a plurality of information elements described below, based on the request information.
  • Example 1 of information element The information element in Example 1 indicates that the RU device 20 has the ability to autonomously transition the RU device 20 from the normal mode to the ES (Energy Saving) mode (or indicates whether the RU device 20 has the ability or not. ) Capability information. If the Capability of the RU device 20 is valid, the RU device 20 autonomously shifts to the ES mode when a "predetermined condition" for shifting to the ES mode is met.
  • the mode in which the RU device 20 can autonomously shift to the ES mode may be called “autonomous saving mode (Self Saving mode).” That is, the autonomous saving mode (Self Saving mode) can be said to be an ES mode triggered by the RU device 20.
  • the RU device 20 triggers a transition from the normal mode to the ES (Energy Saving) mode.
  • ES Electronicgy Saving
  • Self Saving mode may be referred to as "RU triggered Saving mode”.
  • Example 2 of information element The information element in Example 2 provides the RU device with the ability to send a message (for example, a Notification message) to the control device 11 to notify the control device 11 that the RU device 20 has autonomously transitioned from the normal mode to the ES mode. Capability information indicating that the RU device 20 has the capability (or indicating whether the RU device 20 has the capability). If the information element in Example 2 indicates that this Capability is valid, the RU device 20 transmits the message (for example, a Notification message) to the control device 11 when autonomously transitioning from the normal mode to the ES mode. When the control device 11 receives this message, the control device 11 can understand that the RU device 20 has autonomously shifted to the ES mode.
  • a message for example, a Notification message
  • the RU device 20 may stop the operation of at least some of the antennas included in the RU device 20. Specifically, for example, the RU device 20 may stop the operation of at least one antenna array among the plurality of antenna arrays (tx-arrays and rx-arrays) included in the RU device 20. good.
  • the RU device 20 may set the corresponding parameters when transitioning the RU device 20 from the normal mode to the ES mode. Specifically, for example, the RU device 20 sets parameters similar to "Parameter Example 1", “Parameter Example 2", or "Parameter Example 3" described in the third embodiment. There may be.
  • RU equipment 20 may shut down at least one of the C/U (Control/User)-plane, S (Synchronization)-plane, M (Management)-plane, and components of RU equipment 20.
  • the components of the RU device 20 described above may include one or both of a digital device section and an analog device section.
  • This digital device section may be at least one of the FPGA (Field Programmable Gate Array), CPLD (Complex Programmable Logic Device), ASIC (Application Specific Integrated Circuit), processor, and network interface of the RU device 20. good.
  • this analog device section may be a PA (Power Amplifier).
  • the RU device 20 may stop some of the plurality of antenna arrays in the ES mode.
  • the RU device 20 may lower the voltage of the RU device 20.
  • Lowering the voltage of the RU device 20 mentioned above includes, for example, “lowering the antenna transmission power of the RU device 20,” “stopping parts of the RU device 20,” and “reducing the connection to the RU device 20.” ⁇ stopping the power supply from the RU device 20 to the external device that has been installed.''
  • lowering the antenna transmission power of the RU device 20 may mean autonomously lowering the antenna output to the minimum value of the antenna transmission power of the RU device 20.
  • the minimum value of the antenna transmission power of the RU device 20 may be indicated from the RU device 20 to the control device 11 by the “min-power-per-antenna” parameter of module-capability.yang module.
  • stopping the components of the RU device 20 may mean turning off the switches of the components of the RU device 20.
  • the above “stopping power supply from the RU device 20 to an external device connected to the RU device 20” may be an external device connected to the ALD (Antenna Line Device) port of the RU device 20.
  • This external device may be an antenna tilt control device that controls the tilt of the antenna of the RU device 20.
  • the "predetermined conditions” include (condition 1) that the "overheat determination parameter" of the RU device 20 satisfies the overheat condition, (condition 2) that the number of user equipment (UE) communicating with the RU device 20 is smaller than a threshold, Alternatively, it may include any one or any combination of (condition 3) that a predetermined transition time to the ES mode has come.
  • (Condition 1) may be that the temperature (for example, internal temperature) of the RU device 20 is higher than the overheat determination threshold.
  • this (Condition 1) is satisfied, the RU device 20 shifts to the ES mode, thereby reducing the power consumption of the RU device 20, thereby reducing heat generation in the RU device 20. This avoids or eliminates overheating in the RU device 20.
  • the RU device 20 can grasp the number of UEs that communicate with the RU device 20. Note that the RU device 20 may autonomously transition from the ES mode to the normal mode when the number of user equipments (UE) communicating with the RU device 20 increases from a state smaller than a threshold value to a threshold value or more.
  • UE user equipments
  • the RU device 20 transmits an RPC reply (rpc-reply) message to the control device 11 in response to an RPC (Remote Procedure Call) message indicating acquisition (get or get-config).
  • RPC reply message includes information about the RU device 20.
  • This information about the RU device 20 includes capability information indicating that the RU device 20 has the capability to autonomously transition the RU device 20 from normal mode to ES mode (or indicating whether the RU device 20 has this capability).
  • This configuration of the RU device 20 allows the control device 11 (NETCONF client) to flexibly control the "self-saving mode" of the RU device 20.
  • the RU device 20 also sends an RPC reply (rpc-reply) message to the control device 11 in response to an RPC (Remote Procedure Call) message indicating acquisition (get or get-config).
  • RPC reply message includes information about the RU device 20.
  • This information about the RU device 20 includes capability information indicating that the RU device 20 has the capability to send a message (e.g., a Notification message) to the control device 11 to notify the control device 11 that the RU device 20 has autonomously transitioned from normal mode to ES mode (or indicating whether the RU device 20 has this capability).
  • This configuration of the RU device 20 allows the control device 11 to understand that the RU device 20 has autonomously shifted to the ES mode.
  • the first message may include request information regarding any one or any combination (including all) of a plurality of information elements described below.
  • the first response message may include any one or any combination (including all) of a plurality of information elements described below, based on the request information.
  • the first response message may include part or all of the content related to any combination (including all) of a plurality of information elements described below, based on the request information.
  • Example 3 of information element The information element in Example 3 indicates the ability of the RU to request the control device 11 to shift the RU device 20 from the normal mode to the ES mode when the "predetermined conditions" for the RU device 20 to shift to the ES mode are met.
  • This is Capability information indicating that the device 20 has the capability (or indicating whether the RU device 20 has the capability). If this Capability is valid, the RU device 20 requests the control device 11 to shift the RU device 20 from the normal mode to the ES mode when the above-mentioned "predetermined condition" is satisfied. In response to the request, the control device 11 executes control to shift the RU device 20 from the normal mode to the ES mode.
  • This control uses, for example, edit-config.
  • the transition from the normal mode to the ES mode is triggered by the RU device 20 (RU triggered saving mode) in that the starting point is a request from the RU device 20.
  • the control device 11 can grasp that there is a possibility of receiving the above request from the RU device 20 in the future.
  • the information element in Example 4 is a message for requesting the control device 11 to shift the RU device 20 from the normal mode to the ES mode when the "predetermined conditions" for the RU device 20 to shift to the ES mode are met.
  • This is Capability information indicating that the RU device 20 has the ability to send (for example, a Notification message) to the control device 11 (or indicating whether the RU device 20 has the capability). If this Capability is valid, the RU device 20 transmits the message (for example, a Notification message) to the control device 11 when the above-mentioned "predetermined condition" is satisfied.
  • the control device 11 executes control to shift the RU device 20 from the normal mode to the ES mode in response to the message.
  • This control uses, for example, edit-config. Even in this case, it can be said that the transition from the normal mode to the ES mode is triggered by the RU device 20 (RU triggered saving mode) in that the message from the RU device 20 is the starting point. Note that by the control device 11 receiving this Capability information, the control device 11 can grasp that there is a possibility of receiving the above message from the RU device 20 in the future.
  • Example 4 the aspect of "sending a message to the control device 11 to request the control device 11 to shift the RU device 20 from normal mode to ES mode" according to the information element of Example 4 is similar to the information element of Example 3. This can be said to be a specific example of the mode of "requesting the control device 11 to shift the RU device 20 from the normal mode to the ES mode".
  • FIG. 7 is a diagram illustrating another example of the processing operation of the RU device and the control device of the present disclosure.
  • the control device 11 transmits a message indicating configuration editing (edit-config) (hereinafter sometimes referred to as a "second request message") to the RU device 20 (step S21).
  • the second request message may be an RPC message.
  • the second request message includes at least one of the following configuration information elements.
  • the second request message includes, for example, a configuration information element indicating that the RU device 20 is allowed to autonomously transition the RU device 20 from the normal mode to the ES mode when a predetermined condition is met.
  • This setting information element is used, for example, in pair with the Capability information of the "information element of example 1" described in the first embodiment. That is, by receiving the first response message including the information element of Example 1, the control device 11 determines that the RU device 20 has the ability to autonomously transition the RU device 20 from the normal mode to the ES (Energy Saving) mode. ”, the second request message including this configuration information element may be sent.
  • the RU device 20 validates a parameter indicating that the RU device 20 is allowed to autonomously transition to the ES mode (step S22). ).
  • the parameter may be a new parameter (for example, a "self-saving-enabled” parameter) that is not described in Non-Patent Document 1.
  • the RU device 20 is set to the above-mentioned "autonomous saving mode (Self Saving mode)". That is, the RU device 20 autonomously transitions the RU device 20 from the normal mode to the ES mode when a predetermined condition is met. (Example 2 of configuration information element)
  • the second request message requests the control device 11 to shift the RU device 20 from the normal mode to the ES mode when a predetermined condition is met (more specifically, the second request message includes a setting information element indicating that the RU device 20 is permitted to send the RU device 20 to the control device 11.
  • This setting information element is used in pair with, for example, the "information element of example 3" or the "information element of example 4" described in the first embodiment.
  • the control device 11 instructs the control device 11 to “transfer the RU device 20 from the normal mode to the ES mode.”
  • the RU device 20 has the ability to make a request (more specifically, the ability to send a request message to the control device 11)
  • it sends a second request message that includes this configuration information element. It may be.
  • the RU device 20 When the RU device 20 receives the second request message including the configuration information element described above, the RU device 20 transmits a parameter indicating that the request is allowed to be made to the control device 11 or the message to the control device 11. Alternatively, a parameter indicating that is permitted may be validated (step S22). As a result, the RU device 20 enters a state where it makes the above request (more specifically, a state where it sends a message for the above request) when the predetermined conditions are met.
  • the RU device 20 transmits an RPC response (rpc-reply) message (hereinafter sometimes referred to as a "second response message") to the control device 11 in response to the second message (step S23). That is, FIG. 7 shows an example of the processing operations of the RU device 20 and the control device 11 according to the NETCONF ⁇ edit-config> procedure.
  • Fig. 8 is a diagram showing another example of the processing operation of the RU device and the control device of the present disclosure. Note that the third embodiment is based on the premise that the RU device 20 is set to the autonomous saving mode described in the second embodiment.
  • the RU device 20 waits until the above "predetermined condition" is satisfied (step S31 NO). If the above "predetermined condition" is satisfied (step S31 YES), the RU device 20 autonomously shifts the mode of the RU device 20 from the normal mode to the ES mode (step S32). Thereby, the RU device 20 can flexibly control transition to the ES mode.
  • the RU device 20 may change the settings of any of the following parameters.
  • the RU device 20 may set the value of the active parameter of the tx/rx-array-carriers of the RU device 20 to SLEEP or INACTIVE.
  • the RU device 20 may set the value of the active parameter of the tx/rx-array-carriers of the RU device 20 to a value indicating that the RU device 20 has autonomously transitioned to the ES mode.
  • the value indicating that the RU device 20 has autonomously transitioned to the ES mode may be a new value not described in Non-Patent Document 1 (for example, "SELF-SLEEP").
  • the RU device 20 may set the value of a parameter indicating autonomous transition of the RU device 20 to the ES mode to SLEEP.
  • the parameter indicating autonomous transition to the ES mode may be, for example, a new parameter not described in Non-Patent Document 1 (for example, a "self-active" parameter).
  • Self-active is, for example, a parameter that selectively takes a value of "ACTIVE" or "SLEEP".
  • the RU device 20 transmits a notification indicating that the RU device 20 has autonomously transitioned to the ES mode to the control device 11 (NETCONF client) (step S33). Thereby, the control device 11 can understand that the RU device 20 has autonomously shifted to the ES mode.
  • the order of steps S32 and S33 is not limited to this, and step S32 may be performed after step S33.
  • FIG. 9 is a diagram illustrating another example of the processing operation of the RU device and control device of the present disclosure. Note that the fourth embodiment assumes that the RU device 20 is in a state in which the request described in the second embodiment is permitted (more specifically, in a state in which transmission of a message for the request is permitted). There is.
  • the RU device 20 waits until the above-mentioned "predetermined condition" is satisfied (step S41 NO). If the above "predetermined conditions" are met (step S41 YES), the RU device 20 sends a message (for example, a Notification message) to request the control device 11 to change the mode of the RU device 20 (change to ES mode). is transmitted to the control device 11 (step S42). Thereby, the RU device 20 can flexibly control transition to the ES mode.
  • a message for example, a Notification message
  • control device 11 When the control device 11 receives the above message, that is, in response to the reception of the above message, the control device 11 sends an RPC message (hereinafter referred to as "third request message") indicating configuration editing (edit-config). ) is transmitted to the RU device 20 (step S43).
  • RPC message hereinafter referred to as "third request message”
  • edit-config configuration editing
  • the third request message may include any of the following configuration information elements.
  • Example 1 of configuration information element The configuration information element in Example 1 is configuration information for setting the value of the active parameter of tx/rx-array-carriers of the RU device 20 to SLEEP or INACTIVE.
  • the configuration information element in Example 2 is configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device 20 to a value indicating that the RU device 20 has autonomously transitioned to the ES mode. .
  • the configuration information element of Example 3 is configuration information that sets the value of the parameter indicating autonomous transition of the RU device 20 to the ES mode to SLEEP.
  • the RU device 20 Upon receiving the third request message, the RU device 20 shifts the mode of the RU device 20 from the normal mode to the ES mode (step S44).
  • the RU device 20 changes the parameter settings based on the setting information included in the third request message. For example, if the third request message includes the configuration information element of Example 1 above, the RU device 20 sets the value of the active parameter of the tx/rx-array-carriers of the RU device 20 to SLEEP or INACTIVE. . Furthermore, if the third request message includes the configuration information element of Example 2 above, the RU device 20 sets the value of the active parameter of the tx/rx-array-carriers of the RU device 20 to Set to a value that indicates that the mode has been switched to ES mode. Furthermore, if the third request message includes the configuration information element of Example 3 above, the RU device 20 sets the value of the parameter indicating autonomous transition of the RU device 20 to the ES mode to SLEEP.
  • the RU device 20 transmits an RPC response (rpc-reply) message (“third response message”) to the control device 11 in response to the third request message (step S45). That is, FIG. 9 shows an example of the processing operations of the RU device 20 and the control device 11 according to the NETCONF ⁇ edit-config> procedure. Note that the order of steps S44 and S45 is not limited to this, and step S44 may be performed after step S45.
  • FIG. 10 is a diagram showing a configuration example of a control device.
  • a control device 100 includes a processor 101 and a memory 102.
  • the control device 11 may have the configuration shown in FIG.
  • the processor 101 may be, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit).
  • Processor 101 may include multiple processors.
  • Memory 102 is configured by a combination of volatile memory and nonvolatile memory. Memory 102 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
  • SRAM Static Random Access Memory
  • DRAM Dynamic RAM
  • Non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof.
  • Memory 102 may include storage located remotely from processor 101. In this case, the processor 101 may access the memory 102 via an I (Input)/O (Output) interface, which is not shown.
  • the memory 102 may store one or more software modules (computer programs) including a group of instructions and data for performing processing by the control device 11 described in the multiple embodiments described above.
  • the processor 101 may be configured to read and execute the software modules from the memory 102 to perform the processing of the controller 11 described in the embodiments above.
  • FIG. 11 is a diagram showing a configuration example of a DU device.
  • device 200 includes a network interface 201, a processor 202, and a memory 203.
  • the DU device 10 may have the configuration shown in FIG. 11.
  • the network interface 201 is used, for example, to communicate with network elements (e.g., SMO device 30, other RAN nodes).
  • the network interface 1201 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.
  • NIC network interface card
  • the processor 202 may be, for example, a microprocessor, MPU, or CPU. Processor 202 may include multiple processors.
  • the memory 203 is composed of volatile memory and nonvolatile memory.
  • Memory 203 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. Non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof.
  • Memory 203 may include storage located remotely from processor 202. In this case, processor 202 may access memory 203 via network interface 201 or I/O interface.
  • the memory 203 may store one or more software modules (computer programs) including a set of instructions and data for performing processing by the DU device 10 described in the multiple embodiments described above.
  • processor 202 may be configured to read and execute the software modules from memory 203 to perform the operations of DU device 10 described in the embodiments above.
  • FIG. 12 is a diagram showing an example of the configuration of the RU device.
  • device 300 includes an antenna array 301, a Radio Frequency transceiver 302, a network interface 303, a processor 304, and a memory 305.
  • the RU device 20 may have the configuration shown in FIG. 12.
  • RF transceiver 302 performs analog RF signal processing to communicate with UEs.
  • RF transceiver 302 may include multiple transceivers.
  • RF transceiver 302 is coupled to antenna array 301 and processor 304.
  • RF transceiver 302 receives modulation symbol data from processor 304, generates a transmit RF signal, and provides the transmit RF signal to antenna array 301.
  • RF transceiver 302 generates a baseband reception signal based on the reception RF signal received by antenna array 301 and supplies this to processor 304 .
  • RF transceiver 302 may include analog beamformer circuitry for beamforming.
  • the analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
  • the network interface 303 is used to communicate with network nodes (e.g. DU10, SMO30).
  • the network interface 303 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.
  • NIC network interface card
  • the processor 304 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
  • Processor 304 may include multiple processors.
  • the processor 304 includes a modem processor (e.g. Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g. Central Processing Unit (CPU) or Micro Processing Unit (MPU) that performs control plane processing). ) may also be included.
  • DSP Digital Signal Processor
  • MPU Micro Processing Unit
  • Processor 304 may include a digital beamformer module for beamforming.
  • the digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and precoder.
  • MIMO Multiple Input Multiple Output
  • the memory 305 is configured by a combination of volatile memory and nonvolatile memory.
  • Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
  • Non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof.
  • Memory 305 may include storage located remotely from processor 304. In this case, processor 304 may access memory 305 via network interface 303 or an I/O interface, not shown.
  • the memory 305 may store one or more software modules (computer programs) containing instructions and data for performing processing by the RU device 20 described in the multiple embodiments above.
  • processor 304 may be configured to retrieve and execute the software modules from memory 305 to perform the operations of RU device 20 described in the embodiments above.
  • the antenna array 301 may correspond to the above-mentioned tx-array and rx-array.
  • FIG. 13 is a diagram showing an example of the configuration of the SMO device.
  • SMO device 400 is implemented as a computer system.
  • Computer system 400 includes one or more processors 401 , memory 402 , and mass storage 403 that communicate with each other via bus 407 .
  • processors 401 may include, for example, a Central Processing Unit (CPU) or a Graphics Processing Unit (GPU) or both.
  • Computer system 400 may include other devices, such as one or more output devices 404, one or more input devices 405, and one or more peripherals 406.
  • One or more peripherals 406 may include a modem or a network adapter, or any combination thereof.
  • One or both of memory 402 and mass storage 403 includes a computer-readable medium that stores one or more sets of instructions. These instructions may be partially or completely located in memory within one or more processors 401. These instructions, when executed in one or more processors 401, cause the one or more processors 401 to provide the functionality of the SMO device 30 described in the embodiments above.
  • An RU (Radio Unit) device at least one memory; at least one processor coupled to the at least one memory; Equipped with the at least one processor autonomously transitions the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met; RU equipment.
  • An RU (Radio Unit) device at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor requests an RU control device to transition the RU device from a normal mode to an ES (Energy Saving) mode if a predetermined condition is met.
  • RU equipment At least one processor requests an RU control device to transition the RU device from a normal mode to an ES (Energy Saving) mode if a predetermined condition is met.
  • the at least one processor includes: Receives an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating acquisition (get or get-config) from the RU control device; sending an RPC reply (rpc-reply) message to the RU controller in response to the RPC message;
  • the RPC response message includes Capability information indicating that the RU device has the ability to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode.
  • the at least one processor includes: Receives an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating acquisition (get or get-config) from the RU control device; sending an RPC reply (rpc-reply) message to the RU controller in response to the RPC message;
  • the RPC response message includes Capability information indicating that the RU device has the ability to request the RU control device to transition the RU device from a normal mode to an ES (Energy Saving) mode.
  • the at least one processor transmits a Notification message to the RU control device to notify the RU control device that the RU device has autonomously transitioned from a normal mode to an ES (Energy Saving) mode.
  • the at least one processor transmits a Notification message to the RU control device to request the RU control device to transition the RU device from a normal mode to an ES (Energy Saving) mode.
  • the predetermined conditions are: an overheating determination parameter of the RU device satisfies an overheating condition; the number of user equipment (UE) communicating with the RU device is less than a threshold; or At the predetermined time to transition to ES mode, including any one or any combination of RU device described in Appendix 1 or 2.
  • the at least one processor transmits a message sent from the RU control device in response to a request from the RU device to transition the RU device from normal mode to ES (Energy Saving) mode, receiving an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config);
  • the RPC message is configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to SLEEP or INACTIVE; Configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to a value (SELF-SLEEP) indicating that the RU device has autonomously transitioned from normal mode to ES mode, or , configuration information that sets the value of a parameter (self-active) indicating autonomous transition of the RU device to ES mode to SLEEP; including, RU device described in Appendix 2.
  • the at least one processor stops at least one of a C/U (Control/User)-plane, an S (Synchronization)-plane, an M (Management)-plane, and a component of the RU device.
  • the component includes at least one of a digital device section and an analog device section.
  • the digital device section includes at least one of an FPGA (Field Programmable Gate Array), a CPLD (Complex Programmable Logic Device), an ASIC (Application Specific Integrated Circuit), a processor, and a network interface.
  • the analog device section is an antenna array or a PA (Power Amplifier), RU device described in Appendix 11.
  • the at least one processor lowers the voltage of the RU device in the ES mode; RU device described in Appendix 1 or 2.
  • Lowering the voltage of the RU device means: lowering the antenna transmission power of the RU device; stopping a PA (Power Amplifier) of the RU device, and stopping power supply from the RU device to an external device connected to the RU device; including at least one of RU device described in Appendix 14.
  • (Appendix 16) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor transmits an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating a configuration edit (edit-config) to an RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met. Control device.
  • (Appendix 17) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor transmits an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating a configuration edit (edit-config) to an RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to request the RU control device to transition the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. , Control device.
  • the at least one processor When the at least one processor is requested by the RU device to transition the RU device from a normal mode to an ES (Energy Saving) mode, the at least one processor performs configuration editing based on a NETCONF (Network Configuration Protocol) protocol.
  • NETCONF Network Configuration Protocol
  • the RPC message is configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to SLEEP or INACTIVE; Configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to a value (SELF-SLEEP) indicating that the RU device has autonomously transitioned from normal mode to ES mode, or , configuration information that sets the value of a parameter (self-active) indicating autonomous transition of the RU device to ES mode to SLEEP; including, The control device according to supplementary note 17.
  • a method carried out by an RU (Radio Unit) device comprising: including autonomously transitioning the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met; Method.
  • a method carried out by an RU (Radio Unit) device comprising: If a predetermined condition is met, requesting the RU control device to shift the RU device from a normal mode to an ES (Energy Saving) mode; Method.
  • RPC Remote Procedure Call
  • NETCONF Network Configuration Protocol
  • RPC reply rpc-reply
  • the RPC response message includes Capability information indicating that the RU device has the ability to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode.
  • RPC Remote Procedure Call
  • NETCONF Network Configuration Protocol
  • RPC reply rpc-reply
  • the RPC response message includes Capability information indicating that the RU device has the ability to request the RU control device to transition the RU device from a normal mode to an ES (Energy Saving) mode.
  • the predetermined conditions are: an overheating determination parameter of the RU device satisfies an overheating condition; the number of user equipment (UE) communicating with the RU device is less than a threshold; or At the predetermined time to transition to ES mode, including any one or any combination of The method described in Appendix 19 or 20.
  • the RPC message is configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to SLEEP or INACTIVE;
  • Configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to a value (SELF-SLEEP) indicating that the RU device has autonomously transitioned from normal mode to ES mode, or , configuration information that sets the value of a parameter (self-active) indicating autonomous transition of the RU device to ES mode to SLEEP; including, The method described in Appendix 20.
  • a C/U (Control/User)-plane In the ES mode, at least one of a C/U (Control/User)-plane, an S (Synchronization)-plane, an M (Management)-plane, and a component of the RU device is stopped.
  • the method described in Appendix 19 or 20. The component includes at least one of a digital device section and an analog device section.
  • the digital device section includes at least one of an FPGA (Field Programmable Gate Array), a CPLD (Complex Programmable Logic Device), an ASIC (Application Specific Integrated Circuit), a processor, and a network interface. The method described in Appendix 29.
  • the analog device section is an antenna array or a PA (Power Amplifier), The method described in Appendix 29.
  • Appendix 32 In the ES mode, the voltage of the RU device is lowered, The method described in Appendix 19 or 20.
  • Appendix 33 The fact that the voltage of the RU device is lowered means that the antenna transmission power of the RU device is lowered; A PA (Power Amplifier) of the RU device is stopped, and power supply from the RU device to an external device connected to the RU device is stopped; including at least one of The method described in Appendix 32.
  • a method carried out by a control device comprising: including sending an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config) to the RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met.
  • a method carried out by a control device comprising: including sending an RPC (Remote Procedure Call) message based on the NETCONF (Network Configuration Protocol) protocol and indicating configuration editing (edit-config) to the RU (Radio Unit) device;
  • the RPC message includes configuration information that allows the RU device to request the RU control device to transition the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. , Method.
  • RPC Remote Procedure
  • NETCONF Network Configuration Protocol
  • indicating configuration editing (edit-config) Call message
  • the RPC message is configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to SLEEP or INACTIVE;
  • Configuration information that sets the value of the active parameter of tx/rx-array-carriers of the RU device to a value (SELF-SLEEP) indicating that the RU device has autonomously transitioned from normal mode to ES mode, or , configuration information that sets the value of a parameter (self-active) indicating autonomous transition of the RU device to ES mode to SLEEP; including, The method described in Appendix 35.
  • Execute processing including sending an RPC (Remote Procedure Call) message indicating configuration editing (edit-config) to an RU (Radio Unit) device based on the NETCONF (Network Configuration Protocol) protocol,
  • the RPC message includes configuration information that allows the RU device to autonomously transition the RU device from a normal mode to an ES (Energy Saving) mode when a predetermined condition is met. program.
  • Execute processing including sending an RPC (Remote Procedure Call) message indicating configuration editing (edit-config) to an RU (Radio Unit) device based on the NETCONF (Network Configuration Protocol) protocol,
  • the RPC message includes configuration information that allows the RU device to request the RU control device to transition the RU device from normal mode to ES (Energy Saving) mode when predetermined conditions are met. , program.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention exécute une commande flexible d'un mode d'économie d'énergie (ES) d'une unité radio (RU). Lorsque certaines conditions sont satisfaites, le dispositif RU effectue une transition autonome du mode normal au mode ES, ou demande à un dispositif de commande de faire passer le dispositif RU du mode normal au mode ES.
PCT/JP2023/029552 2022-09-22 2023-08-16 Dispositif ru, dispositif de commande, procédé et programme WO2024062806A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022151204 2022-09-22
JP2022-151204 2022-09-22

Publications (1)

Publication Number Publication Date
WO2024062806A1 true WO2024062806A1 (fr) 2024-03-28

Family

ID=90454210

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/029552 WO2024062806A1 (fr) 2022-09-22 2023-08-16 Dispositif ru, dispositif de commande, procédé et programme

Country Status (1)

Country Link
WO (1) WO2024062806A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016149601A (ja) * 2015-02-10 2016-08-18 富士通株式会社 無線通信装置、基地局システム及び無線通信装置制御方法
WO2019063072A1 (fr) * 2017-09-27 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Régulation de puissance de nœud de réseau

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016149601A (ja) * 2015-02-10 2016-08-18 富士通株式会社 無線通信装置、基地局システム及び無線通信装置制御方法
WO2019063072A1 (fr) * 2017-09-27 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Régulation de puissance de nœud de réseau

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
O-RAN WORKING GROUP 4 (OPEN FRONTHAUL INTERFACSE WG): "Management Plane Specification [online]", O-RAN.WG4.MP.0-V10.00, 15 August 2022 (2022-08-15) *

Similar Documents

Publication Publication Date Title
EP3732928B1 (fr) Procédés fournissant une connectivité double pour des trajets de plan utilisateur redondants et entité de contrôle d'un réseau central et réseau de communication sans fil
US8543116B2 (en) Method and base station for energy saving compensation
WO2020030051A1 (fr) Dispositif et procédé de configuration de ressources
US8767588B2 (en) Method and apparatus for implementing a blanket wireless local area network control plane
JP6839273B2 (ja) ベアラ状態不整合回避のためのシステムおよび方法
CA2591763A1 (fr) Procede et systeme pour recuperer des defaillances de liaison d'infrastructure a point d'acces
BRPI0714310A2 (pt) suporte sem fios para dispositivo tocador de mÍdia portÁtil
JP6024437B2 (ja) 基地局装置
WO2008030171A2 (fr) Stations de base de télécommunications non-homogènes
US20060264214A1 (en) Mode-switching wireless communications equipment
US11595831B2 (en) Controller redundancy in a centralized radio access network
JP7130755B2 (ja) ワイヤレス通信デバイスについてサービングセルの動作状態を判定し又は示すための方法及び装置
WO2024062806A1 (fr) Dispositif ru, dispositif de commande, procédé et programme
US11197197B2 (en) Dynamic load balancing of gateway access points
WO2024024493A1 (fr) Dispositif ru, dispositif de commande, procédé de dispositif ru et procédé de dispositif de commande
WO2024062785A1 (fr) Dispositif de commande, dispositif ru, système, et procédé
WO2024024423A1 (fr) Dispositif de communication, système de communication, procédé de communication, et support non transitoire lisible par ordinateur
WO2024062828A1 (fr) Dispositif ru, dispositif du, système de communication et procédé de communication
KR20200049545A (ko) 무선 통신 시스템에서 측정 동작을 제어하기 위한 장치 및 방법
US20240073783A1 (en) Ble link cluster control and management
US20240073782A1 (en) Ble link cluster discovery, establishing, and termination
US20230291638A1 (en) Zero-Touch Provisioning of an Access Point by a Switch
WO2024034524A1 (fr) Station de base, dispositif de commande, système de communication, procédé, et programme
US20230018858A1 (en) Multiple coexisting personal area networks having different handshaking
JP5915755B2 (ja) 情報処理装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23867931

Country of ref document: EP

Kind code of ref document: A1