WO2024247197A1 - 通信装置、無線装置、制御装置、無線通信システム、及び制御方法 - Google Patents

通信装置、無線装置、制御装置、無線通信システム、及び制御方法 Download PDF

Info

Publication number
WO2024247197A1
WO2024247197A1 PCT/JP2023/020366 JP2023020366W WO2024247197A1 WO 2024247197 A1 WO2024247197 A1 WO 2024247197A1 JP 2023020366 W JP2023020366 W JP 2023020366W WO 2024247197 A1 WO2024247197 A1 WO 2024247197A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
communication device
wireless
control
communication
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2023/020366
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
伊藤勇三
小川浩二
大塚泰哲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to PCT/JP2023/020366 priority Critical patent/WO2024247197A1/ja
Priority to EP23939672.4A priority patent/EP4723803A1/en
Priority to JP2025523147A priority patent/JPWO2024247197A1/ja
Publication of WO2024247197A1 publication Critical patent/WO2024247197A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices

Definitions

  • the present invention relates to a communication device, a wireless device, a control device, a wireless communication system, and a control method.
  • O-RAN Open Radio Access Network
  • 5G radio access network a 5G radio access network built based on open interface specifications and with separated functions
  • the interface (fronthaul interface) between the DU and RU was previously designed for each communications equipment vendor, but the O-RAN (Open RAN) Alliance will stipulate the radio access network interface and communications equipment specifications.
  • O-RAN Open Radio Access Network
  • equipment vendors will be able to interconnect with communications equipment from other companies.
  • O-RAN can use subcomponents provided by various service providers and vendors.
  • O-RAN for example, the functions of a base station device are separated into a DU (Distributed Unit) and a RU (Radio Unit).
  • the RU is a unit that transmits and receives radio signals
  • the DU is a unit that controls the RU.
  • O-RAN has, for example, an OPS (Operation System) that monitors and controls the DU.
  • OPS Operaation System
  • O-RAN the O-RAN specification version (hereafter sometimes referred to as ORAN version) that a connected device supports may differ depending on the development date of each device. For this reason, the O-RAN specification guarantees backward compatibility to realize an interface with devices with lower ORAN version numbers.
  • NETCONF NETwork CONFiguration
  • NETCONF is one of the standard transport protocols for communicating with network devices.
  • YANG Yet Another Next Generation
  • YANG Yet Another Next Generation
  • network devices are configured based on data described in YANG.
  • YANG is one of the modeling languages developed with the aim of describing the structure of network device configuration items, states, procedure calls, etc. in a format that is easy for people to interpret.
  • the O-RAN version numbers of the devices that make up the O-RAN may differ depending on the time of development, etc. Operators combine these devices to provide services to users, but in order to start the desired service, they need to research the ORAN version numbers of the devices to be combined and the services that the devices can support. This is because even devices that comply with the O-RAN specifications may not support non-essential services due to constraints such as hardware configuration. Therefore, operators may have to research the ORAN version numbers and services that the devices support for all devices used in operations, which can require a huge amount of work.
  • one disclosure provides a control device and control method that reduces operator labor costs.
  • a communication device in a wireless communication system having a control device, a wireless device that accommodates wireless terminals, and a communication device that processes signals from the wireless device, each of which has one or more wireless devices under its control, and which is constructed based on an open interface specification, has a communication device receiving unit that receives a service inquiry including service information regarding a service type from the control device, and a communication device transmitting unit that transmits a wireless device service inquiry including the service information to all subordinate wireless devices if the control device supports the service, and the communication device receiving unit receives from the wireless device whether the service is supported, and the communication device transmitting unit transmits a service inquiry notification including identification information of a wireless device that supports the service among the wireless devices under the control of the communication device to the control device.
  • One disclosure can reduce operator man-hours.
  • FIG. 1 is a diagram showing an example of the configuration of a wireless communication system 10.
  • FIG. 2 is a diagram illustrating an example of the configuration of the OPS 300.
  • FIG. 3 is a diagram showing an example of the configuration of DU 200.
  • FIG. 4 illustrates an example of the configuration of the RU 100.
  • FIG. 5 is a diagram showing an example of a sequence of an initial process in a service inquiry process.
  • FIG. 6 is a diagram showing an example of a DU function table.
  • FIG. 7 is a diagram showing an example of the RU function table.
  • FIG. 8 is a diagram showing an example of a sequence in which a service inquiry is successful in the service inquiry process.
  • FIG. 1 is a diagram showing an example of the configuration of a wireless communication system 10.
  • FIG. 2 is a diagram illustrating an example of the configuration of the OPS 300.
  • FIG. 3 is a diagram showing an example of the configuration of DU 200.
  • FIG. 4 illustrates an example of the configuration of the
  • FIG. 9 is a diagram showing an example of a sequence in which a service inquiry fails due to DU 200 not being compatible with the service during service inquiry processing.
  • FIG. 10 is a diagram showing an example of a sequence in which a service inquiry fails due to the RU 100 not being compatible with the service during service inquiry processing.
  • FIG. 11 is a diagram showing an example of a message format between OPS 300 and DU 200.
  • FIG. 12 is a diagram showing an example of a message format between DU 200 and RU 100.
  • FIG. 13 is a diagram showing an example of a sequence in which a service inquiry is successful in the service inquiry process.
  • FIG. 14 is a diagram showing an example of a message format between OPS 300 and DU 200.
  • FIG. 15 is a diagram showing an example of a message format between DU 200 and RU 100.
  • Fig. 1 is a diagram showing an example of the configuration of a wireless communication system 10.
  • the wireless communication system 10 is a system having an OPS 300, DUs 200-1 and 2, and RUs 100-1 to 3, and is, for example, an O-RAN.
  • a network 400 and a network 500 in Fig. 1 may be the same network, or may be different networks.
  • OPS300 is a control device operated by an operator, for example a server machine.
  • OPS300 is connected to DU200-1, 2 via network 400, for example, and controls DU200-1, 2.
  • OPS300 also monitors DU200-1, 2.
  • DU200-1, 2 (hereinafter sometimes referred to as DU200) is a control device that controls RU100-1 to 3.
  • DU200 is connected to RU100-1 to 3 via network 500 and controls RU100-1 to 3.
  • DU200 processes, for example, tasks of the upper part of the physical layer (High-PHY), media access control (MAC), and radio link control (RLC).
  • DU200 may also have the functionality of a CU (Central Unit). Also, in the wireless communication system 10, a CU may be connected above DU200 (between OPS300 and DU200).
  • RU100-1 to RU100-3 are radio stations that perform wireless communication according to instructions from DU200.
  • RU100 provides, for example, processing of RF (Radio Frequency) and the lower part of the physical layer (Low-PHY), and can accommodate wireless terminals.
  • RU100 is an example of a wireless device that accommodates wireless terminals.
  • the OPS 300 performs a service inquiry process when starting a certain service.
  • the service inquiry process is a process for searching for a combination of a DU 200 and a RU 100 that can execute the service.
  • the OPS 300 can recognize the combination of a DU 200 and a RU 100 that supports the service to be executed under the control of the OPS 300.
  • the RUs 100 are controlled by one DU 200.
  • RUs 100-1 and 100-2 are controlled by DU 200-1
  • RU 100-3 is controlled by DU 200-2.
  • the controlling/controlled relationship (master-slave relationship) between the RUs 100 and DU 200 may be dynamically switched.
  • the master-slave relationship may be switched, for example, by a change in the system reconfiguration due to a device failure, or by a system reconfiguration due to a change in the wireless state (such as a concentration of terminals or a change in the environment).
  • the RUs 100 may be controlled by multiple DUs 200.
  • ⁇ Configuration example of OPS 300> 2 is a diagram illustrating an example of the configuration of the OPS 300.
  • the OPS 300 includes a CPU (Central Processing Unit) 310, a storage 320, a memory 330, and a communication circuit 340.
  • CPU Central Processing Unit
  • Storage 320 is an auxiliary storage device such as a flash memory, HDD (Hard Disk Drive), or SSD (Solid State Drive) that stores programs and data.
  • Storage 320 stores a communication control program 321 and a service inquiry program 322.
  • Memory 330 is an area into which programs stored in storage 320 are loaded. Memory 330 may also be used as an area in which programs store data.
  • the communication circuit 340 is a device that communicates with the DU 200 and the RU 100.
  • the communication circuit 340 may be, for example, a wired communication circuit such as an NI (Network Interface), or a communication circuit that supports wireless connection.
  • NI Network Interface
  • CPU 310 is a processor that loads programs stored in storage 320 into memory 330, executes the loaded programs, configures each component, and realizes each process.
  • the CPU 310 performs communication control processing by executing the communication control program 321.
  • the communication control processing is processing that controls the DU 200 and controls wireless communication performed via the RU 100.
  • the CPU 310 executes the service inquiry program 322 to construct a control unit and a communication unit, and to perform service inquiry processing.
  • the service inquiry processing is a process of requesting the DU 200 whether or not a certain service is supported, and the names (including identifiers, etc.) of the DU 200 and RU 100 that support the service.
  • the CPU 310 executes the service inquiry start module 3221 of the service inquiry program 322 to construct a control unit and a communication unit, and performs the service inquiry start process.
  • the service inquiry start process is the start process of the service inquiry process.
  • the OPS 300 transmits a DU service inquiry request including a certain service (for example, a service desired by the operator) to the subordinate DU 200, and waits for a DU service inquiry response from the DU 200.
  • the CPU 310 executes the DU service inquiry notification receiving module 3222 contained in the service inquiry program 322 to construct a control unit and a communication unit, and performs DU service inquiry notification receiving processing.
  • the DU service inquiry notification receiving processing is processing for receiving a DU service inquiry notification from the DU 200.
  • the OPS 300 waits to receive a DU service inquiry notification from the subordinate DU 200.
  • ⁇ Configuration example of DU200> 3 is a diagram illustrating an example of the configuration of the DU 200.
  • the DU 200 includes a CPU 210, a storage 220, a memory 230, and a communication circuit 240.
  • Storage 220 is an auxiliary storage device such as a flash memory, HDD, or SSD that stores programs and data.
  • Storage 220 stores RU control program 221, DU service inquiry program 223, and DU function table 222.
  • DU function table 222 is a table that indicates the functions (services) supported by the DU 200 and the correspondence with the corresponding ORAN version. Details of DU function table 222 will be described later.
  • Memory 230 is an area into which programs stored in storage 220 are loaded. Memory 230 may also be used as an area in which programs store data.
  • the communication circuit 240 is a device that communicates with the OPS 300 and the RU 100.
  • the communication circuit 240 may be, for example, a wired communication circuit such as an NI, or a communication circuit that supports wireless connection.
  • the CPU 210 is a processor that loads the programs stored in the storage 220 into the memory 230, executes the loaded programs, configures each component, and realizes each process.
  • the CPU 210 performs RU control processing by executing the RU control program 221.
  • the RU control processing is processing that controls wireless communication performed by the RU 100.
  • the CPU 210 executes the DU service inquiry program 223 to construct a DU control unit and a DU communication unit, and to perform DU service inquiry processing.
  • the DU service inquiry processing is a process for inquiring of the RU 100 as to whether a certain service is supported, the ORAN version number that the RU 100 supports, etc.
  • the CPU 210 executes the DU service query request receiving module 2231 contained in the DU service query program 223 to construct a DU control unit and a DU communication unit, and performs DU service query request receiving processing.
  • the DU service query request receiving processing is processing for receiving a DU service query request from the OPS 300.
  • the DU 200 transmits an RU service query request to the subordinate RU 100, and waits for an RU service query response from the RU 100.
  • the CPU 210 executes the RU service inquiry notification receiving module 2232 of the DU service inquiry program 223 to construct a DU control unit and a DU communication unit, and performs RU service inquiry notification receiving processing.
  • the RU service inquiry notification receiving processing is processing for receiving an RU service inquiry notification from a subordinate RU 100.
  • the DU 200 transmits a DU service inquiry notification to the OPS 300.
  • ⁇ Configuration example of RU 100> 4 is a diagram showing an example of the configuration of the RU 100.
  • the RU 100 includes a CPU 110, a storage 120, a memory 130, a communication circuit 140, a wireless communication circuit 150, and an antenna 151.
  • Storage 120 is an auxiliary storage device such as a flash memory, HDD, or SSD that stores programs and data.
  • Storage 120 stores a wireless communication program 121, an RU service inquiry program 123, and an RU function table 122.
  • the RU function table 122 is a table that shows the correspondence between the functions (services) supported by the RU 100 and the corresponding ORAN versions.
  • Memory 130 is an area into which programs stored in storage 120 are loaded. Memory 130 may also be used as an area in which programs store data.
  • the communication circuit 140 is a device that communicates with the OPS 300 and the DU 200.
  • the communication circuit 140 may be, for example, a wired communication circuit such as an NI, or a communication circuit that supports wireless connections.
  • the wireless communication circuit 150 is a device that performs wireless communication with a wireless communication terminal.
  • the wireless communication circuit 150 has an antenna 151.
  • the antenna 151 includes, for example, a directional antenna that can control the direction of transmission and reception of radio waves.
  • the CPU 110 is a processor that loads the programs stored in the storage 120 into the memory 130, executes the loaded programs, configures each component, and realizes each process.
  • the CPU 110 executes the wireless communication program 121 to perform wireless communication processing.
  • the wireless communication processing is processing for wirelessly connecting to a wireless communication terminal, transmitting and receiving signals, and performing wireless communication.
  • the CPU 110 executes the RU service inquiry program 123 to construct an RU control unit and an RU communication unit, and to perform RU service inquiry processing.
  • the RU service inquiry processing is a process in which an RU service inquiry request is received from the DU 200, and information is sent to the DU 200, such as whether the device itself supports a certain service, the corresponding ORAN version number, etc.
  • the CPU 110 executes the RU service query request receiving module 1231 contained in the RU service query program 123 to construct an RU control unit and an RU communication unit, and to perform RU service query request receiving processing.
  • the RU service query processing is processing for receiving an RU service query request from the DU 100.
  • ⁇ Service inquiry processing> In the wireless communication system 10, when an operator starts a certain service, the operator operates the OPS 300 to perform a service inquiry process.
  • the service inquiry process will be described below. Note that in the following sequence, an example in which there is one DU 200 and one RU 100 will be described, but there may be two or more of each.
  • Initial Processing> 5 is a diagram showing an example of a sequence of initial processing in a service inquiry process.
  • the DU 200 When the DU 200 is started (S101), the DU 200 creates a DU function table 222 (S102).
  • Creating the DU function table includes, for example, a process of expanding a table stored in a program on the memory of the DU 200.
  • FIG. 6 is a diagram showing an example of a DU function table.
  • the DU function table is a table showing the relationship between ORAN versions and corresponding functions.
  • the reason why the DU function table includes corresponding functions is that a DU 200 corresponding to a certain ORAN version may not support services (functions) defined in a certain ORAN version, for example, services that are not required, due to constraints such as hardware configuration, and therefore may not be able to support all.
  • DU 200 supports up to ORAN version V11 and is compatible with function A, which is a function of ORAN version V10.
  • function A which is a function of ORAN version V10
  • other DUs 200 may not support function A, which is a function of ORAN version V10, even if they support up to ORAN version V11.
  • DU200 corresponds to ORAN version V11.
  • DU200 is capable of communicating with other devices (RU100 and OPS300) using structures (YANG modules) defined in ORAN version V11.
  • Creating an RU function table includes, for example, a process of expanding a table stored in a program into the memory of the RU 100.
  • Figure 7 is a diagram showing an example of an RU function table.
  • the RU function table is a table showing the relationship between ORAN versions and corresponding functions.
  • the reason why the RU function table includes corresponding functions is that an RU 100 corresponding to a certain ORAN version may not support services (functions) defined in a certain ORAN version, for example, services that are not required, due to constraints such as hardware configuration, and therefore may not be able to support all.
  • RU 100 supports up to ORAN version V12 and is able to support function A, which is a function of ORAN version V10.
  • other RUs 100 may not support function A, which is a function of ORAN version V10, even if they support up to ORAN version V12.
  • RU100 supports ORAN version V12.
  • RU100 is capable of communicating with other devices (DU200 and OPS300) using structures (YANG modules) defined in ORAN version V12.
  • DU200 and RU100 send and receive information to each other (SSH or TLS & Hello) (S105).
  • RU100 notifies DU200 of whether or not it supports the service query function as part of the capability information to be sent and received.
  • DU200 obtains from RU100 whether or not it supports the service query function as part of the capability information to be sent and received. If RU100 does not support the service query function, DU200 does not send an RU service query request, which will be described below.
  • a DU200 that does not support the service inquiry function receives a service inquiry request as described below, it will discard the message or treat it as an error message.
  • Service inquiry success> 8 is a diagram showing an example of a sequence of a successful service inquiry in the service inquiry process.
  • a successful service inquiry indicates that a combination of a DU 200 and a RU 100 corresponding to the service exists. In the following sequence, it is assumed that the service to be inquired about is function A.
  • OPS300 sends a DU service query request to DU200 (S201).
  • the DU service query request includes function A, which is the service to be queried.
  • OPS300 If OPS300 has multiple DU200 under its control, it will send a DU service inquiry request to all of the subordinate DU200, for example.
  • DU200 When DU200 accepts the DU service inquiry request, it sends a DU service inquiry response including an acceptance OK to OPS300 (S202).
  • DU200 may not accept a DU service query request if, for example, there is a syntax error in the DU service query request, or if DU200 is in a state where it cannot accept the DU service query request (for example, communication with RU100 is disconnected). In such cases, DU200 sends a DU service query response including acceptance NG to OPS300.
  • DU200 checks whether its own device supports function A (S203). DU200 refers to DU function table 222 to check whether function A is supported. If the DU function table contains the contents shown in FIG. 6, DU200 recognizes that function A is supported as a function of ORAN version V10.
  • DU200 If DU200 supports function A, it sends an RU service query request to RU200 (S204).
  • the RU service query request includes function A, which is the service to be queried.
  • the DU200 If the DU200 has multiple RUs100 under its control, it will send an RU service inquiry request to all of the RUs100 under its control, for example.
  • RU100 accepts the RU service inquiry request, it sends an RU service inquiry response including an acceptance OK to DU200 (S205).
  • RU100 may not accept an RU service inquiry request if there is a syntax error in the RU service inquiry request, or if RU100 is in a state where it cannot accept the RU service inquiry request (for example, during maintenance or when wireless communication is not possible). In such cases, RU100 sends an RU service inquiry response including an NG acceptance to DU200.
  • RU100 checks whether its own device supports function A (S206). RU100 refers to RU function table 122 to check whether it can support function A. If the RU function table contains the contents shown in FIG. 7, RU100 recognizes that it supports function A as a function of ORAN version V10.
  • RU100 If RU100 supports function A, it sends an RU service inquiry notification to DU200 (S207).
  • the RU service inquiry notification includes support for the inquiry function (supported).
  • the DU service inquiry notification includes support for the inquiry function (supported).
  • the DU service inquiry notification also includes the names (identifiers) of RU100 and DU200 that support function A.
  • the DU service inquiry notification also includes ORAN version V10, which is the ORAN version that corresponds to function A.
  • the DU 200 may wait for DU service inquiry notifications from all of the subordinate RUs 100.
  • the names (identifiers) of the RUs 100 included in the DU service inquiry notification will be the names (identifiers) of all of the RUs 100 that support function A.
  • the DU 200 may start a timer to wait for the DU service inquiry notification to be received, and if the notification is not received within a specified time, it may determine that the RU 100 does not support the function.
  • OPS300 When OPS300 receives a DU service inquiry notification, it stores the names (identifiers) of DU200 and RU100 that support function A, the ORAN version number that function A supports, etc.
  • OPS300 can recognize the combination of DU200 and RU100 that corresponds to the desired service.
  • Service inquiry failure (DU200 does not support the service)> 9 is a diagram showing an example of a sequence of a service inquiry failure due to the service not being supported by the DU 200 in the service inquiry process.
  • a service inquiry failure indicates that there is no combination of the DU 200 and the RU 100 that supports the service (the DU 200 is not supported, or all the RUs 100 under the DU 200 are not supported).
  • OPS300 sends a DU service query request to DU200 (S301).
  • the DU service query request includes function A, which is the service to be queried.
  • DU200 sends a DU service inquiry response including acceptance OK to OPS300 (S302).
  • DU200 If DU200 does not support function A, it sends a DU service inquiry notification to OPS300 (S304).
  • the DU service inquiry notification includes information that function A is not supported (not supported) and the reason for this (DU200 does not support it).
  • OPS300 When OPS300 receives a DU service inquiry notification, it stores the name (identifier) of the DU200 that does not support function A and the reason.
  • FIG. 10 is a diagram showing an example of a sequence in which a service inquiry fails due to the RU 100 not being compatible with the service during service inquiry processing.
  • OPS300 sends a DU service query request to DU200 (S401).
  • the DU service query request includes function A, which is the service to be queried.
  • DU200 When DU200 accepts the DU service inquiry request, it sends a DU service inquiry response including an acceptance OK to OPS300 (S402).
  • DU200 checks whether its own device supports function A (S403). DU200 refers to DU function table 222 to check whether function A is supported. If the DU function table has the contents shown in FIG. 6, DU200 recognizes that function A is supported as a function of ORAN version V10.
  • DU200 If DU200 supports function A, it sends an RU service query request to RU200 (S404).
  • the RU service query request includes function A, which is the service to be queried.
  • RU100 accepts the RU service inquiry request, it sends an RU service inquiry response including an acceptance OK to DU200 (S405).
  • RU100 checks whether its own device supports function A (S406). RU100 refers to RU function table 122 to check whether function A is supported. RU100 recognizes from RU function table 122 that function A is not supported.
  • RU100 If RU100 does not support function A, it sends an RU service inquiry notification to DU200 (S407).
  • the RU service inquiry notification includes a notification that the queried function is not supported (not supported).
  • the DU service inquiry notification includes information indicating that the queried function is not supported (not supported).
  • the DU service inquiry notification also includes information indicating that RU does not support function A as a reason for not supporting function A.
  • the DU 200 may wait for DU service inquiry notifications from all of the subordinate RUs 100. In this case, when all of the subordinate RUs 100 are unsupported, the DU 200 sends a DU service inquiry notification including "unsupported" to the OPS 300. On the other hand, when there is even one supported RU 100, the DU 200 sends a DU service inquiry notification including "supported" to the OPS 300.
  • OPS300 When OPS300 receives a DU service inquiry notification, it stores the name (identifier) of DU200 that does not support function A and the reason. Note that in this sequence, since DU200 supports the function, the DU200 may be stored as supported.
  • Fig. 11 is a diagram showing an example of a message format between the OPS 300 and the DU 200.
  • Fig. 12 is a diagram showing an example of a message format between the DU 200 and the RU 100.
  • the DU service inquiry request is a message sent when the service inquiry process starts, and includes a service (function).
  • the service is the service desired by the operator, and is, for example, a number (identification number) corresponding to the service.
  • the DU service inquiry response is a message indicating whether or not the DU service inquiry request is accepted, and includes OK or NG.
  • OK indicates that the request was accepted
  • NG indicates that the request was not accepted.
  • the DU service inquiry notification is a message indicating the support status of a service of the DU200 and RU100. If there is support (if there is a combination of DU200 and RU100 that has the function in question), the DU service inquiry notification includes the service name (identification number), the ORAN version required for the service, and the names (identifiers) of the DU200 and RU100 that correspond to the service.
  • the ORAN version required for a service is the ORAN version required to execute the service in question, and indicates, for example, the ORAN version in which the service is implemented or defined.
  • the ORAN version required for a service is extracted by the DU200 from the DU function table.
  • the DU service inquiry notification may also include the names (identifiers) of RU100 that do not support the function in question.
  • the DU service inquiry notification includes the reason for the lack of support.
  • Reasons for the lack of support include that the DU 200 is not supported, or that the RU 100 is not supported.
  • Reasons for the lack of support may also include, for example, that there is no RU 100 to connect to.
  • the DU service inquiry notification may include the name (identifier) of the DU 200 or RU 100 that does not support the function.
  • the RU service inquiry request is a message that asks the RU 100 whether or not a service is supported, and includes a service (function).
  • the service is the service desired by the operator, and is, for example, a number (identification number) that corresponds to the service.
  • the RU service inquiry response is a message indicating whether or not the RU service inquiry request is accepted, and includes OK or NG.
  • OK indicates that the request was accepted
  • NG indicates that the request was not accepted.
  • the RU service inquiry notification is a message indicating the support status of the service of RU100. If there is support (if RU100 supports the function), the RU service inquiry notification will include “supported.” On the other hand, if there is no support, the RU service inquiry notification will include "not supported.”
  • the OPS 300 acquires a usable ORAN version number.
  • the usable ORAN version number indicates an ORAN version number that can use a defined interface, such as communication using a defined structure (YANG module).
  • YANG module a defined structure
  • a device that supports up to ORAN version number V11 cannot use an interface defined in ORAN version number V12 because there is a functional difference in the structure (YANG module). Therefore, even if the device supports ORAN version number V12, when communicating with a device that supports up to ORAN version number V11, the device that supports ORAN version number V12 applies backward compatibility and communicates using an interface of ORAN version number V11 (or a lower version number) that supports a lower version number.
  • DU200 is ORAN version V11 and RU100 is ORAN version V12
  • RU100 applies backward compatibility
  • DU200 and RU100 interface with each other using ORAN version V11.
  • DU200 is ORAN version V11 and RU100 is ORAN version V10
  • DU200 applies backward compatibility
  • DU200 and RU100 interface with each other using ORAN version V10.
  • the ORAN version that can be used for the interface is determined by DU200, and is included in a service inquiry notification and notified to OPS300.
  • FIG. 13 is a diagram showing an example of a sequence in which a service inquiry is successful in the service inquiry process.
  • Processing S501 to S505 in FIG. 13 is the same as processing S201 to S205 in FIG. 8.
  • RU100 checks whether its own device supports function A (S506). RU100 refers to RU function table 122 to check whether it can support function A. If the RU function table contains the contents shown in FIG. 7, RU100 recognizes that it supports function A as a function of ORAN version V10.
  • RU100 If RU100 supports function A, it sends an RU service inquiry notification to DU200 (S507).
  • the RU service inquiry notification includes information indicating that the inquiry function is supported (supported) and the ORAN version number supported by the device itself.
  • the supported ORAN version number is the ORAN version number that RU100 can support, and indicates, for example, the highest ORAN version number in the RU function table. If the RU function table has the contents shown in Figure 7, the supported ORAN version number is ORAN version V12.
  • the DU service inquiry notification includes support for the inquiry function (supported).
  • the DU service inquiry notification also includes the names (identifiers) of RU100 and DU200 that support function A.
  • the DU service inquiry notification also includes ORAN version V10, which is the ORAN version corresponding to function A.
  • the DU service inquiry notification also includes the available ORAN version.
  • DU200 is ORAN version V11 and RU100 is ORAN version V12
  • backward compatibility can be applied to the RU100 side, so ORAN version V11 on the DU200 side with the lower ORAN version is selected (S508).
  • DU200 is ORAN version V11 and the RU is ORAN version V10
  • backward compatibility can be applied to the DU200 side, so ORAN version V10 on the RU100 side with the lower ORAN version is selected (S508).
  • the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, it may include, for example, the compatible ORAN version number for each RU 100 (for each combination of RU 100 and DU 200).
  • the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, it may include, for example, the lowest compatible ORAN version number as the compatible ORAN version number.
  • OPS300 When OPS300 receives a DU service inquiry notification, it stores the names (identifiers) of DU200 and RU100 that support function A, the ORAN version number that function A supports, and the available ORAN version number.
  • Fig. 14 is a diagram showing an example of a message format between the OPS 300 and the DU 200.
  • Fig. 15 is a diagram showing an example of a message format between the DU 200 and the RU 100.
  • the DU service inquiry request is the same as in the first embodiment.
  • the DU service inquiry response is the same as in the first embodiment.
  • the DU service inquiry notification includes the usable ORAN version number in addition to the DU service inquiry notification in the first embodiment.
  • the usable ORAN version number is the ORAN version number that can be used for the interface.
  • the usable ORAN version number is, for example, the ORAN version number that is compatible with both RU100 and DU200, and is the lower version number that is compatible with DU200 and RU100.
  • the usable ORAN version number is included in the message, for example, for the DU 200 and each of the RUs 100. Also, if the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, the usable ORAN version number may be the ORAN version number usable by all RUs 100 and DU 200 included in the message. Also, if the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, the ORAN version number that the DU 200 and each of the RUs 100 can support may be included instead of the usable ORAN version number. In this case, the usable ORAN version number is determined, for example, by OPS 300.
  • the RU service inquiry request is the same as in the first embodiment.
  • the RU service inquiry response is the same as in the first embodiment.
  • the RU service inquiry notification includes the corresponding ORAN version number in addition to the RU service inquiry notification in the first embodiment.
  • the corresponding ORAN version number is the ORAN version number (the highest ORAN version number) that RU100 supports.
  • Wireless communication system 100 RU 110: CPU 120: Storage 121: Wireless communication program 122: RU function table 123: RU service inquiry program 1231: RU service inquiry request receiving module 130: Memory 140: Communication circuit 150: Wireless communication circuit 151: Antenna 200: DU 210: CPU 220: Storage 221: RU control program 222: DU function table 223: DU service inquiry program 2231: DU service inquiry request receiving module 2232: RU service inquiry notification receiving module 230: Memory 240: Communication circuit 300: OPS 310: CPU 320: Storage 321: Communication control program 322: Service inquiry program 3221: Service inquiry initiation module 3222: DU service inquiry notification reception module 330: Memory 340: Communication circuit 400: Network 500: Network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2023/020366 2023-05-31 2023-05-31 通信装置、無線装置、制御装置、無線通信システム、及び制御方法 Ceased WO2024247197A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/JP2023/020366 WO2024247197A1 (ja) 2023-05-31 2023-05-31 通信装置、無線装置、制御装置、無線通信システム、及び制御方法
EP23939672.4A EP4723803A1 (en) 2023-05-31 2023-05-31 Communication device, radio device, control device, radio communication system, and control method
JP2025523147A JPWO2024247197A1 (https=) 2023-05-31 2023-05-31

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/020366 WO2024247197A1 (ja) 2023-05-31 2023-05-31 通信装置、無線装置、制御装置、無線通信システム、及び制御方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/396,561 Continuation US20260128967A1 (en) 2025-11-21 Communication device, wireless device, control device, wireless communication system, and control method

Publications (1)

Publication Number Publication Date
WO2024247197A1 true WO2024247197A1 (ja) 2024-12-05

Family

ID=93657277

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/020366 Ceased WO2024247197A1 (ja) 2023-05-31 2023-05-31 通信装置、無線装置、制御装置、無線通信システム、及び制御方法

Country Status (3)

Country Link
EP (1) EP4723803A1 (https=)
JP (1) JPWO2024247197A1 (https=)
WO (1) WO2024247197A1 (https=)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021181910A1 (ja) 2020-03-11 2021-09-16 日本電気株式会社 通信装置、データ記録方法、及び非一時的なコンピュータ可読媒体
US20220345896A1 (en) * 2021-04-22 2022-10-27 Mavenir Systems, Inc. Systems and methods for enabling communications over shared spectrum using o-ran fronthaul interface in radio access networks
JP2022552996A (ja) * 2019-10-16 2022-12-21 コムスコープ テクノロジーズ リミティド ライアビリティ カンパニー 互換性のない無線と仮想ベースバンドユニットとの間の通信のためのシステムおよび方法
JP2022554262A (ja) 2019-10-31 2022-12-28 華為技術有限公司 デバイス管理方法、装置、システム、及びデバイス、並びに記憶媒体

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022552996A (ja) * 2019-10-16 2022-12-21 コムスコープ テクノロジーズ リミティド ライアビリティ カンパニー 互換性のない無線と仮想ベースバンドユニットとの間の通信のためのシステムおよび方法
JP2022554262A (ja) 2019-10-31 2022-12-28 華為技術有限公司 デバイス管理方法、装置、システム、及びデバイス、並びに記憶媒体
WO2021181910A1 (ja) 2020-03-11 2021-09-16 日本電気株式会社 通信装置、データ記録方法、及び非一時的なコンピュータ可読媒体
US20220345896A1 (en) * 2021-04-22 2022-10-27 Mavenir Systems, Inc. Systems and methods for enabling communications over shared spectrum using o-ran fronthaul interface in radio access networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"O-Ran Technical Specification", 10 April 2023, O-RAN ALLIANCE, DE, article O-RAN: "O-RAN Operations and Maintenance Interface Specification ", pages: 1 - 89, XP093243945 *

Also Published As

Publication number Publication date
EP4723803A1 (en) 2026-04-08
JPWO2024247197A1 (https=) 2024-12-05

Similar Documents

Publication Publication Date Title
EP2978144B1 (en) Unified device management method and system
CN111278031B (zh) Pdu类型的设置方法、ue策略的设置方法、实体及存储介质
CN109644522B (zh) 用于通过无线网络安全加载设备的方法和系统
CN107196964A (zh) 用于实现多频段服务发现的系统和方法
CN103517300B (zh) 分布式基站的自发现方法、装置及系统
CN113746651B (zh) 接入网络切片的方法、电子设备及存储介质
WO2011156998A1 (zh) 一种实现设备自动配置的系统及方法
CN112217845B (zh) 一种基于Netconf协议的数据传输方法及相关设备
CN111937461A (zh) 分割基站中的rrc版本处理
EP2171917B1 (en) System and method for providing device management service to electronic device having no broadband communication module
WO2012174799A1 (zh) 升级包下载及安装的方法、服务器及系统
CN115514667B (zh) 接入服务处理方法、系统、装置、电子设备以及存储介质
CN117997807A (zh) 一种物联网设备心跳检测的方法、系统以及通信装置
WO2023025180A1 (zh) 管理节点的方法、节点和系统
CN111130865A (zh) 一种基于二层交换的网络设备固件批量升级方法及系统
CN114982199A (zh) 一种安全信息发现方法、安全信息配置方法及设备
EP4371293B1 (en) Wireless communication service over an edge data network between a user equipment and an application server
WO2010075738A1 (zh) 一种管理多模网元的方法、系统及多模网元
WO2024247197A1 (ja) 通信装置、無線装置、制御装置、無線通信システム、及び制御方法
CN115842769A (zh) 信息更新方法及装置、存储介质、电子装置
US20260128967A1 (en) Communication device, wireless device, control device, wireless communication system, and control method
JP4445302B2 (ja) 無線端末装置、サービス検索方法
US20240291714A1 (en) Automated power on notification system and method thereof
EP2426859B1 (en) Method and server for transferring large object
CN116419287A (zh) 业务通信方法、装置、电子设备及存储介质

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: 23939672

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025523147

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2023939672

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023939672

Country of ref document: EP

Effective date: 20260102

ENP Entry into the national phase

Ref document number: 2023939672

Country of ref document: EP

Effective date: 20260102

ENP Entry into the national phase

Ref document number: 2023939672

Country of ref document: EP

Effective date: 20260102

ENP Entry into the national phase

Ref document number: 2023939672

Country of ref document: EP

Effective date: 20260102

ENP Entry into the national phase

Ref document number: 2023939672

Country of ref document: EP

Effective date: 20260102

ENP Entry into the national phase

Ref document number: 2023939672

Country of ref document: EP

Effective date: 20260102

WWP Wipo information: published in national office

Ref document number: 2023939672

Country of ref document: EP