Communication device, radio device, control device, radio communication system, and control method

Abstract

This radio communication system is constructed on the basis of an open interface specification and includes a control device, radio devices each accommodating a radio terminal, and communication devices that process signals of the radio devices, one or more of the radio devices being provided under the control of each communication device, wherein: each communication device includes a communication device reception unit for receiving, from the control device, a service inquiry including service information relating to the type of a service, and a communication device transmission unit that transmits a radio device service inquiry including the type of the service to all the radio devices under the control thereof, if the communication device itself supports the service; the communication device reception unit receives information indicating whether or not the service is supported, from the radio device; and the communication device transmission unit transmits, to the control device, a service inquiry notification including identification information of a compatible radio device that supports the service, from among the radio devices under the control of the communication device.

Description

Communication device, wireless device, control device, wireless communication system, and control method

[0001] The present invention relates to a communication device, a wireless device, a control device, a wireless communication system, and a control method.

[0002] In recent years, O-RAN (Open Radio Access Network), a 5G radio access network built based on open interface specifications and with separated functions, has been attracting attention. The interface (fronthaul interface) between the DU and RU was previously designed by each communications equipment vendor, but the O-RAN (Open RAN) Alliance defines the radio access network interface and communications equipment specifications. By providing communications equipment that conforms to the O-RAN specifications, 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.

[0003] In O-RAN, for example, the functions of a base station device are separated into a DU (Distributed Unit) and an RU (Radio Unit). The RU is a unit that transmits and receives radio signals, and the DU is a unit that controls the RU. In addition, the O-RAN has, for example, an OPS (Operation System) that monitors and controls the DU.

[0004] In O-RAN, the O-RAN specification version (hereinafter referred to as ORAN version) that a device supports may differ depending on the development period of each device. Therefore, the O-RAN specification guarantees backward compatibility to realize an interface with devices with lower ORAN version numbers.

[0005] In wireless access networks, for example, the NETCONF (NETwork CONFiguration) protocol is used to acquire and update network device settings. NETCONF is one of the standard transport protocols for communicating with network devices. NETCONF uses the YANG (Yet Another Next Generation) modeling language as a description language for configuration items, etc. In other words, in NETCONF, network devices are configured based on data described in YANG. YANG is a modeling language developed for the purpose of describing the structure of network device configuration items, states, procedure calls, etc. in a format that is easy for humans to interpret. Note that data abstracted from the configuration values ​​and structure of network devices using YANG is sometimes called a "YANG data model" or "YANG module." In the O-RAN specification, backward compatibility is guaranteed in YANG modules to realize an interface with lower ORAN version devices.

[0006] The technology related to O-RAN is described in the following prior art documents.

[0007] WO2021 / 181910 Publication Special Publication No. 2022-554262

[0008] As described above, the O-RAN devices may correspond to different ORAN versions 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 must investigate 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 investigate the ORAN version numbers and the services supported by all devices used in operations, which may require a huge amount of work.

[0009] Therefore, one disclosure provides a control device and a control method that reduce the number of steps required by an operator.

[0010] The communication device is in a wireless communication system constructed based on an open interface specification and includes a control device, a wireless device that accommodates a wireless terminal, and a communication device that processes signals from the wireless device, each of which has one or more wireless devices subordinate thereto. The communication device includes a communication device receiving unit that receives a service inquiry including service information regarding a type of service from the control device, and a communication device transmitting unit that, if the device itself supports the service, transmits a wireless device service inquiry including the service information to all of the wireless devices subordinate thereto. The communication device receiving unit receives from the wireless devices whether or not the service is supported, and the communication device transmitting unit transmits a service inquiry notification to the control device that includes identification information of the wireless devices that support the service among the wireless devices subordinate to the communication device.

[0011] One aspect of the present invention is to reduce the amount of work required by an operator.

[0012] FIG. 1 is a diagram showing an example of the configuration of a wireless communication system 10. FIG. 2 is a diagram showing an example of the configuration of an OPS 300. FIG. 3 is a diagram showing an example of the configuration of a DU 200. FIG. 4 is a diagram showing an example of the configuration of an RU 100. FIG. 5 is a diagram showing an example of a sequence of initial processing in service inquiry processing. FIG. 6 is a diagram showing an example of a DU function table. FIG. 7 is a diagram showing an example of an RU function table. FIG. 8 is a diagram showing an example of a sequence in service inquiry processing where a service inquiry is successful. FIG. 9 is a diagram showing an example of a sequence in service inquiry processing where a service inquiry fails because the DU 200 is not compatible with the service. FIG. 10 is a diagram showing an example of a sequence in service inquiry processing where a service inquiry fails because the RU 100 is not compatible with the service. 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. FIG. 13 is a diagram showing an example of a sequence in service inquiry processing where a service inquiry is successful. 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.

[0013] [First embodiment] A first embodiment will be described. 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 200-2, and RUs 100-1 to 100-3, and is, for example, an O-RAN. Note that a network 400 and a network 500 in Fig. 1 may be the same network, or may be different networks.

[0014] The OPS 300 is a control device operated by an operator, such as a server machine. The OPS 300 is connected to the DUs 200-1 and 2 via a network 400, for example, and controls the DUs 200-1 and 2. The OPS 300 also monitors the DUs 200-1 and 2.

[0015] The DUs 200-1 and 200-2 (hereinafter sometimes referred to as DU 200) are control devices that control the RUs 100-1 to 100-3. The DU 200 is connected to the RUs 100-1 to 100-3 via a network 500 and controls the RUs 100-1 to 100-3. The DU 200 processes, for example, tasks related to the upper part of the physical layer (High-PHY), media access control (MAC), and radio link control (RLC). The DU 200 may also have the functionality of a CU (Central Unit). In addition, in the wireless communication system 10, a CU may be connected above the DU 200 (between the OPS 300 and the DU 200).

[0016] RUs 100-1 to 100-3 (hereinafter sometimes referred to as RUs 100) are wireless stations that perform wireless communication in accordance with instructions from DU 200. RUs 100 provide, for example, processing of RF (Radio Frequency) and the lower part of the physical layer (Low-PHY), and can accommodate wireless terminals. Therefore, RUs 100 are an example of a wireless device that accommodates wireless terminals.

[0017] In the wireless communication system 10, the OPS 300 performs a service inquiry process when starting a certain service. The service inquiry process is a process of searching for a combination of the DU 200 and the RU 100 that can execute the service. By performing the service inquiry process, the OPS 300 can recognize the combination of the DU 200 and the RU 100 that supports the service to be executed under the control of the OPS 300.

[0018] In the wireless communication system 10, the RU 100 is controlled by one DU 200. In FIG. 1, for example, RUs 100-1 and 100-2 are controlled by DU 200-1, and RU 100-3 is controlled by DU 200-2. The controlling / controlled relationship (master-slave relationship) between the RU 100 and the DU 200 may be dynamically switched. The master-slave relationship may be switched, for example, due to a change in the system reorganization caused by a device failure or a system reorganization caused by a change in the wireless state (such as a concentration of terminals or an environmental change). In the wireless communication system 10, the RU 100 may be controlled by multiple DUs 200.

[0019] 2 is a diagram showing 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.

[0020] The storage 320 is an auxiliary storage device, such as a flash memory, a hard disk drive (HDD), or a solid state drive (SSD), that stores programs and data. The storage 320 stores a communication control program 321 and a service inquiry program 322.

[0021] The memory 330 is an area into which the programs stored in the storage 320 are loaded. The memory 330 may also be used as an area in which the programs store data.

[0022] 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.

[0023] The CPU 310 is a processor that loads programs stored in the storage 320 into the memory 330, executes the loaded programs, configures each unit, and realizes each process.

[0024] The CPU 310 performs communication control processing by executing the communication control program 321. The communication control processing is processing for controlling the DU 200 and controlling wireless communication executed via the RU 100.

[0025] The CPU 310 executes the service inquiry program 322 to configure a control unit and a communication unit and perform service inquiry processing. The service inquiry processing is processing for 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.

[0026] The CPU 310 executes a service inquiry start module 3221 included in the service inquiry program 322 to establish a control unit and a communication unit and perform service inquiry start processing. The service inquiry start processing is a process for starting the service inquiry processing. In the service inquiry start processing, the OPS 300 transmits a DU service inquiry request including a certain service (for example, a service desired by an operator) to a subordinate DU 200 and waits for a DU service inquiry response from the DU 200.

[0027] The CPU 310 executes a DU service query notification reception module 3222 included in the service query program 322 to construct a control unit and a communication unit and perform DU service query notification reception processing. The DU service query notification reception processing is processing for receiving a DU service query notification from the DU 200. In the DU service query notification reception processing, the OPS 300 waits for reception of a DU service query notification from the subordinate DU 200.

[0028] 3 is a diagram showing 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.

[0029] The storage 220 is an auxiliary storage device such as a flash memory, HDD, or SSD that stores programs and data. The storage 220 stores an RU control program 221, a DU service inquiry program 223, and a DU function table 222. The DU function table 222 is a table that indicates the correspondence between the functions (services) supported by the DU 200 and the corresponding ORAN versions. Details of the DU function table 222 will be described later.

[0030] The memory 230 is an area into which the programs stored in the storage 220 are loaded. The memory 230 may also be used as an area in which the programs store data.

[0031] 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 may be a communication circuit that supports wireless connection.

[0032] The CPU 210 is a processor that loads programs stored in the storage 220 into the memory 230, executes the loaded programs, configures each unit, and realizes each process.

[0033] The CPU 210 performs RU control processing by executing the RU control program 221. The RU control processing is processing for controlling wireless communication performed in the RU 100.

[0034] The CPU 210 executes the DU service inquiry program 223 to configure a DU control unit and a DU communication unit and perform DU service inquiry processing. The DU service inquiry processing is processing for inquiring of the RU 100 about whether a certain service is supported, the ORAN version number supported by the RU 100, and the like.

[0035] The CPU 210 executes a DU service query request receiving module 2231 included in the DU service query program 223 to construct a DU control unit and a DU communication unit and perform 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. In the DU service query request receiving processing, the DU 200 transmits an RU service query request to a subordinate RU 100 and waits for an RU service query response from the RU 100.

[0036] The CPU 210 executes the RU service inquiry notification receiving module 2232 included in the DU service inquiry program 223 to construct a DU control unit and a DU communication unit and perform 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. In the RU service inquiry notification receiving processing, the DU 200 transmits a DU service inquiry notification to the OPS 300.

[0037] 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.

[0038] The storage 120 is an auxiliary storage device such as a flash memory, HDD, or SSD that stores programs and data. The 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.

[0039] The memory 130 is an area into which the programs stored in the storage 120 are loaded. The memory 130 may also be used as an area in which the programs store data.

[0040] 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 may be a communication circuit that supports wireless connection.

[0041] The wireless communication circuit 150 is a device that performs wireless communication with a wireless communication terminal, and includes an antenna 151. The antenna 151 includes, for example, a directional antenna that can control the direction of transmission and reception of radio waves.

[0042] The CPU 110 is a processor that loads programs stored in the storage 120 into the memory 130, executes the loaded programs, configures each unit, and realizes each process.

[0043] The CPU 110 performs wireless communication processing by executing the wireless communication program 121. The wireless communication processing is processing for wirelessly connecting to a wireless communication terminal, transmitting and receiving signals, and performing wireless communication.

[0044] The CPU 110 executes the RU service inquiry program 123 to configure an RU control unit and an RU communication unit, and to perform RU service inquiry processing. The RU service inquiry processing is processing for receiving an RU service inquiry request from the DU 200, and transmitting to the DU 200 information such as whether the own device supports a certain service and the corresponding ORAN version number.

[0045] The CPU 110 executes the RU service inquiry request receiving module 1231 included in the RU service inquiry program 123 to configure an RU control unit and an RU communication unit, and to perform RU service inquiry request receiving processing. The RU service inquiry processing is processing for receiving an RU service inquiry request from the DU 100.

[0046] <Service Inquiry Processing> In the wireless communication system 10, when an operator starts a certain service, he or she operates the OPS 300 to perform a service inquiry processing. The service inquiry processing is described below. Note that in the following sequence, an example in which there is one DU 200 and one RU 100 is described, but there may be two or more of each.

[0047] 5 is a diagram showing an example of the sequence of the initial processing in the service inquiry processing. When the DU 200 is started (S101), it creates the DU function table 222 (S102). Creating the DU function table includes, for example, the process of expanding a table stored in a program into the memory of the DU 200.

[0048] 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 for including corresponding functions in the DU function table is that a DU 200 corresponding to a certain ORAN version may not support services (functions) defined in a certain ORAN version, for example, non-essential services, due to constraints such as hardware configuration, and therefore may not be able to support all of them. For example, as shown in FIG. 6, a DU 200 is compatible with ORAN version V11 and is compatible with function A, which is a function of ORAN version V10. However, another DU 200, even if it is compatible with ORAN version V11, may not be compatible with function A, which is a function of ORAN version V10.

[0049] 6, the DU200 corresponds to ORAN version V11. That is, the DU200 can communicate with other devices (RU100 and OPS300) using structures (YANG modules) defined in ORAN version V11.

[0050] 5, the RU 100 creates an RU function table (S104) upon startup (S103). Creating an RU function table includes, for example, expanding a table stored in a program into the memory of the RU 100.

[0051] FIG. 7 is a diagram showing an example of an RU function table. The RU function table shows the relationship between ORAN versions and corresponding functions. The reason for including corresponding functions in the RU function table is that an RU 100 corresponding to a certain ORAN version may not support services (functions) defined in that ORAN version, for example, non-essential services, due to constraints such as hardware configuration, and therefore may not be able to support all of them. For example, as shown in FIG. 7, an RU 100 supports up to ORAN version V12 and is capable of function A, which is a function of ORAN version V10. However, another RU 100, even if it supports up to ORAN version V12, may not support function A, which is a function of ORAN version V10.

[0052] 7, the RU 100 corresponds to ORAN version V12. This indicates that the RU 100 can communicate with other devices (DU 200 and OPS 300) using structures (YANG modules) defined in ORAN version V12.

[0053] Returning to the sequence of Fig. 5, the DU 200 and the RU 100 transmit and receive information to each other (SSH or TLS & Hello) (S105). At this time, the RU 100 notifies the DU 200 of whether or not the DU 200 supports the service inquiry function as capability information to be transmitted and received. In other words, the DU 200 acquires from the RU 100 whether or not the DU 200 supports the service inquiry function as capability information to be transmitted and received. If the RU 100 does not support the service inquiry function, the DU 200 does not transmit an RU service inquiry request, which will be described below.

[0054] Furthermore, if a DU 200 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.

[0055] 8 is a diagram showing an example of a sequence in which a service query is successful in the service query process. A successful service query indicates that a combination of DU 200 and RU 100 corresponding to the service exists. In the following sequence, it is assumed that the service being queried is function A.

[0056] The OPS 300 transmits a DU service inquiry request to the DU 200 (S201). The DU service inquiry request includes function A, which is the service to be inquired about.

[0057] If the OPS 300 has a plurality of DUs 200 under its control, it transmits a DU service inquiry request to all of the DUs 200 under its control, for example.

[0058] When the DU 200 accepts the DU service inquiry request, it transmits a DU service inquiry response including acceptance OK to the OPS 300 (S202).

[0059] The DU 200 may not accept the DU service inquiry request if, for example, there is a syntax error in the DU service inquiry request, or if the DU 200 is in a state where it cannot accept the DU service inquiry request (for example, if communication with the RU 100 is disconnected). In such cases, the DU 200 transmits a DU service inquiry response including acceptance NG to the OPS 300.

[0060] DU200 checks whether its own device supports function A (S203). DU200 refers to DU function table 222 to check whether it can support function A. If the DU function table has the contents shown in Figure 6, DU200 recognizes that it supports function A as a function of ORAN version V10.

[0061] If the DU 200 supports function A, it transmits an RU service inquiry request to the RU 200 (S204). The RU service inquiry request includes function A, which is the service to be inquired about.

[0062] If the DU 200 has a plurality of RUs 100 under its control, it sends an RU service inquiry request to all the RUs 100 under its control, for example.

[0063] When the RU 100 accepts the RU service inquiry request, it transmits an RU service inquiry response including acceptance OK to the DU 200 (S205).

[0064] The RU 100 may not accept the RU service inquiry request if, for example, there is a syntax error in the RU service inquiry request, or if the RU 100 is in a state where it cannot accept the RU service inquiry request (for example, during maintenance or when wireless communication is not possible), etc. In such cases, the RU 100 transmits an RU service inquiry response including an acceptance NG to the DU 200.

[0065] The RU 100 checks whether its own device supports function A (S206). The RU 100 refers to the RU function table 122 to check whether it can support function A. If the RU function table has the contents shown in Fig. 7, the RU 100 recognizes that it supports function A as a function of ORAN version V10.

[0066] If the RU 100 supports function A, it transmits an RU service inquiry notification to the DU 200 (S207). The RU service inquiry notification includes support for the inquired function (supported).

[0067] When the DU 200 receives the RU service inquiry notification from the RU 100, it transmits the DU service inquiry notification to the OPS 300 (S208). The DU service inquiry notification includes support for the queried function (supported). The DU service inquiry notification also includes the names (identifiers) of the RU 100 and DU 200 that support function A. The DU service inquiry notification also includes ORAN version V10, which is the ORAN version corresponding to function A.

[0068] If the DU 200 has multiple subordinate RUs 100, it may wait for DU service inquiry notifications from all of the subordinate RUs 100. In this case, 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. Furthermore, while waiting for DU service inquiry notifications from all of the subordinate RUs 100, the DU 200 may start a timer for waiting for reception of a DU service inquiry notification, and if the DU 200 is unable to receive the notification within a predetermined time, it may determine that the RU 100 does not support the function.

[0069] When OPS 300 receives the DU service inquiry notification, it stores the names (identifiers) of DU 200 and RU 100 that support function A, the ORAN version number that function A supports, and the like.

[0070] As described above, the OPS 300 can recognize the combination of the DU 200 and the RU 100 that corresponds to the desired service by executing the service inquiry process.

[0071] 9 is a diagram showing an example of a sequence in which a service inquiry fails in service inquiry processing due to the DU 200 not being compatible with the service. A service inquiry failure indicates that there is no combination of DU 200 and RU 100 that is compatible with the service (the DU 200 is not compatible, or all of the RUs 100 subordinate to the DU 200 are not compatible).

[0072] The OPS 300 transmits a DU service inquiry request to the DU 200 (S301). The DU service inquiry request includes function A, which is the service to be inquired about.

[0073] The DU 200 sends a DU service inquiry response including acceptance OK to the OPS 300 (S302).

[0074] If DU200 does not support function A, it transmits 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 not supporting it).

[0075] When OPS 300 receives a DU service inquiry notification, it stores the name (identifier) ​​of DU 200 that does not support function A and the reason.

[0076] 4. Service Inquiry Failure (RU 100 is Service Incompatible) FIG. 10 is a diagram showing an example of a sequence in the service inquiry process in which a service inquiry fails because the RU 100 is service incompatible.

[0077] The OPS 300 transmits a DU service inquiry request to the DU 200 (S401). The DU service inquiry request includes function A, which is the service to be inquired about.

[0078] When the DU 200 accepts the DU service inquiry request, it transmits a DU service inquiry response including acceptance OK to the OPS 300 (S402).

[0079] The DU 200 checks whether its own device supports function A (S403). The DU 200 refers to the DU function table 222 to check whether it can support function A. If the DU function table has the contents shown in Figure 6, the DU 200 recognizes that it supports function A as a function of ORAN version V10.

[0080] If the DU 200 supports function A, it transmits an RU service inquiry request to the RU 200 (S404). The RU service inquiry request includes function A, which is the service to be inquired about.

[0081] When the RU 100 accepts the RU service inquiry request, it transmits an RU service inquiry response including acceptance OK to the DU 200 (S405).

[0082] The RU 100 checks whether its own device supports function A (S406). The RU 100 refers to the RU function table 122 to check whether it can support function A. The RU 100 recognizes from the RU function table 122 that it does not support function A.

[0083] If the RU 100 does not support function A, it transmits an RU service inquiry notification to the DU 200 (S407). The RU service inquiry notification includes information indicating that the queried function is not supported (not supported).

[0084] When the DU 200 receives the RU service inquiry notification from the RU 100, the DU 200 transmits the DU service inquiry notification to the OPS 300 (S408). 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 the RU does not support function A as a reason for not supporting function A.

[0085] If the DU 200 has multiple subordinate RUs 100, it may wait for DU service inquiry notifications from all of the subordinate RUs 100. In this case, if all of the subordinate RUs 100 are unsupported, the DU 200 transmits a DU service inquiry notification including unsupported to the OPS 300. On the other hand, if there is even one supported RU 100, the DU 200 transmits a DU service inquiry notification including supported to the OPS 300.

[0086] When OPS 300 receives the DU service inquiry notification, it stores the name (identifier) ​​of DU 200 that does not support function A and the reason. In this sequence, since DU 200 supports the function, the DU 200 may be stored as supported.

[0087] <Message Format> The message format will be described. 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.

[0088] The DU service inquiry request is a message sent when a service inquiry process starts, and includes a service (function). The service is a service desired by the operator, and may be, for example, a numeric value (identification number) corresponding to the service.

[0089] 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 is accepted, and NG indicates that the request is not accepted.

[0090] The DU service inquiry notification is a message indicating the support status of a service for the DU 200 and the RU 100. If the service is supported (if a combination of the DU 200 and the RU 100 having the function exists), the DU service inquiry notification includes the service name (identification number), the ORAN version required for the service, and the names (identifiers) of the DU 200 and the RU 100 corresponding to the service. The ORAN version required for the service is the ORAN version required to execute the service, and indicates, for example, the ORAN version in which the service is implemented or defined. The ORAN version required for the service is extracted by the DU 200 from the DU function table. The DU service inquiry notification may also include the names (identifiers) of RUs 100 that do not support the function.

[0091] On the other hand, if there is no support, the DU service inquiry notification includes the reason for the lack of support. The reason for the lack of support includes that the DU 200 is not supported or that the RU 100 is not supported. The reason for the lack of support may also include, for example, that there is no RU 100 to connect to. Furthermore, the DU service inquiry notification may include the name (identifier) ​​of the DU 200 or RU 100 that does not support the function.

[0092] The RU service inquiry request is a message that checks whether the RU 100 supports a service, and includes a service (function). The service is a service desired by the operator, and is, for example, a numeric value (identification number) corresponding to the service.

[0093] 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 is accepted, and NG indicates that the request is not accepted.

[0094] The RU service inquiry notification is a message indicating the support status of the service of the RU 100. If the function is supported (if the RU 100 supports the function), the RU service inquiry notification includes "supported." On the other hand, if the function is not supported, the RU service inquiry notification includes "not supported."

[0095] [Second Embodiment] A second embodiment will be described. In the second embodiment, the OPS 300 acquires a usable ORAN version number. The usable ORAN version number refers to an ORAN version number that allows use of a defined interface, such as communication using a defined structure (YANG module). For example, a device that supports up to ORAN version V11 cannot use an interface defined in ORAN version V12 because there is a functional difference in the structure (YANG module). Therefore, even if a device supports ORAN version V12, when communicating with a device that supports up to ORAN version V11, the device that supports ORAN version V12 applies backward compatibility and communicates using an interface of the lower supported version, ORAN version V11 (or an even lower version). For example, if DU200 is ORAN version V11 and RU100 is ORAN version V12, RU100 applies backward compatibility, and DU200 and RU100 interface with each other using ORAN version V11. On the other hand, if DU200 is ORAN version V11 and RU100 is ORAN version V10, DU200 applies backward compatibility, and 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 the service inquiry notification and notified to OPS300.

[0096] <Service Inquiry Processing> The service inquiry processing in the second embodiment will be described below, taking the case where the service inquiry is successful.

[0097] 1. Successful Service Inquiry FIG. 13 is a diagram showing an example of a sequence in which a service inquiry is successful in the service inquiry process.

[0098] The processes S501 to S505 in FIG. 13 are the same as the processes S201 to S205 in FIG.

[0099] The RU 100 checks whether its own device supports function A (S506). The RU 100 refers to the RU function table 122 to check whether it can support function A. If the RU function table has the contents shown in Fig. 7, the RU 100 recognizes that it supports function A as a function of ORAN version V10.

[0100] If the RU 100 supports function A, it sends an RU service inquiry notification to the DU 200 (S507). The RU service inquiry notification includes information indicating that the queried function is supported (supported) and the ORAN version number supported by the RU 100 itself. The supported ORAN version number is the ORAN version number that the RU 100 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 FIG. 7, the supported ORAN version number is ORAN version V12.

[0101] When DU200 receives the RU service inquiry notification from RU100, it transmits the DU service inquiry notification to OPS300 (S509). The DU service inquiry notification includes support for the queried 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.

[0102] For example, if DU200 has ORAN version V11 and RU100 has ORAN version V12, backward compatibility can be applied to RU100, so ORAN version V11 on the DU200 side with the lower ORAN version is selected (S508). Also, if DU200 has ORAN version V11 and RU has ORAN version V10, backward compatibility can be applied to DU200, so ORAN version V10 on the RU100 side with the lower ORAN version is selected (S508).

[0103] When 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). When the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, it may be, for example, the lowest compatible ORAN version number that is the compatible ORAN version number.

[0104] When OPS 300 receives the DU service inquiry notification, it stores the names (identifiers) of DU 200 and RU 100 that support function A, the ORAN version number that function A supports, and the usable ORAN version number.

[0105] This allows the OPS 300 to recognize not only the combination of the DU 200 and the RU 100 that corresponds to the service, but also the ORAN version number that can be used in that combination.

[0106] <Message Format> The message format will be described. 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.

[0107] The DU service inquiry request is the same as in the first embodiment.

[0108] The DU service inquiry response is the same as in the first embodiment.

[0109] If supported, the DU service inquiry notification includes a usable ORAN version number in addition to the DU service inquiry notification in the first embodiment. The usable ORAN version number is an ORAN version number that can be used for the interface. For example, the usable ORAN version number is an ORAN version number that is compatible with both the RU 100 and the DU 200, and is the lower version number of the versions supported by the DU 200 and the RU 100.

[0110] Note that, when the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, the usable ORAN version number is included in the message, for example, for the DU 200 and each of the RUs 100. Also, when the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, the usable ORAN version number may be an ORAN version number usable by all of the RUs 100 and the DU 200. Also, when the DU service inquiry notification includes the names (identifiers) of multiple RUs 100, the ORAN version numbers 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 the OPS 300.

[0111] On the other hand, if the DU service inquiry notification is not supported, it is the same as in the first embodiment.

[0112] The RU service inquiry request is the same as in the first embodiment.

[0113] The RU service inquiry response is the same as in the first embodiment.

[0114] If supported, 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 supported by the RU 100 (the highest ORAN version number).

[0115] On the other hand, if the RU service inquiry notification is not supported, it is the same as in the first embodiment.

[0116] [Other embodiments] The requirements described in the first, second, and other embodiments may be combined. Furthermore, if the support for each service (function) necessarily corresponds to the ORAN version (if a device compatible with ORAN version N necessarily supports function M supported by ORAN version N), the service name may be replaced with the ORAN version. In this case, the ORAN version required for the service (the ORAN version corresponding to function A) may be omitted.

[0117] 10: 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

Claims

1. A communication device in a wireless communication system constructed based on an open interface specification, the communication device including a control device, a wireless device accommodating a wireless terminal, and a communication device processing a signal of the wireless device, the communication device each having one or more wireless devices under its control, a communication device receiving unit that receives a service inquiry including service information related to a type of service from the control device; a communication device transmitter that transmits a wireless device service inquiry including a type of the service to all subordinate wireless devices when the wireless device itself supports the service; the communication device receiving unit receives from the wireless device whether the service is supported or not; The communication device transmitter transmits, to the control device, a service inquiry notification including identification information of a wireless device corresponding to the service among wireless devices subordinate to the communication device. Communication equipment.

2. The service inquiry notification further includes service version information capable of executing the service. The communication device according to claim 1 .

3. the communication device receiving unit receives, from the compatible wireless device, wireless device version information compatible with the compatible wireless device; The service inquiry notification further includes information on compatible versions that are compatible with both the communication device and the compatible wireless device selected based on backward compatibility. The communication device according to claim 1 .

4. If the communication device does not support the service, the service inquiry notification includes communication device non-support information indicating that the communication device does not support the service. The communication device according to claim 1 .

5. When the communication device supports the service and all wireless devices subordinate to the communication device do not support the service, the service inquiry notice includes wireless device non-support information indicating that all wireless devices subordinate to the communication device do not support the service. The communication device according to claim 1 .

6. A wireless device in a wireless communication system constructed based on an open interface specification, the wireless device including a control device, a wireless device accommodating a wireless terminal, and a communication device processing a signal of the wireless device, the communication device each having one or more wireless devices under its control, a wireless device receiving unit that receives a wireless device service inquiry including service information regarding a type of service transmitted from the control device and transmitted by the communication device; a wireless device transmitter that transmits to the communication device whether or not the service is supported; The communication device transmits a service inquiry notification including identification information of a compatible wireless device that supports the service to the control device in response to receiving information on whether the service is supported from the wireless device. Radio equipment.

7. A control method for a control device of a wireless communication system constructed based on an open interface specification, the control device including a control device, a wireless device accommodating a wireless terminal, and a communication device processing a signal of the wireless device, the communication device each having one or more wireless devices under its control, the method comprising: sending a service inquiry to the communication device, the service inquiry including service information relating to a type of service; receiving a service inquiry notification including support information for the service from the communication device; If the communication device supports the service, the support information includes identification information of a wireless device that supports the service and is subordinate to the communication device. Control method.