Software-defined radio device and method of using radio communication software programs

Abstract

Domain management functionality is implemented internally to a software-defined radio device. A software-defined radio device that includes plural hardware modules 220 to 222 and implements radio device functions by downloading radio communication software programs 203 for controlling the plural hardware modules from outside. The software-defined radio device includes domain management software 202 among environment software programs 215 that are activated when the device is activated. The domain management software generates an interface necessary to use each of the radio communication software programs according to a domain for each of the radio communication software programs and performs activation, setup, and connection with other programs for each of the radio communication software programs.

Claims

1. A method of using radio communication software programs in a software-defined radio device, the method comprising: receiving an instruction to activate a first radio communication software program from a user interface unit; determining whether a thread has been generated, the thread implementing a domain management function for a domain of the first radio communication software program; and generating a new thread for the domain of the first radio communication software program, if such thread has not been generated, wherein, upon being notified of completion of activation of the thread for the domain of the first radio communication software program, the user interface unit instructs the thread to activate the first radio communication software program; receiving an instruction to terminate a second radio communication software program from the user interface unit; and instructing a thread for a domain of the second radio communication software program to terminate the second radio communication software program, wherein, after completion of termination of the second radio communication software program, the user interface unit determines whether a radio communication software program is active and managed under the same domain that the second radio communication software program belongs to, and wherein, if there is no radio communication software that is active and managed under the same domain that the second radio communication software program belongs to, the thread for the domain of the second radio communication software program is deactivated.

2. The method of using radio communication software programs according to claim 1, wherein the domain management functions include functions of generating an interface necessary to use each of the radio communication software programs according to a domain for each of the radio communication software programs and performing activation, setup, and connection with other programs for each of the radio communication software programs.

3. The method of using radio communication software programs according to claim 1, wherein the domain management functions include functions of generating an interface necessary to use each of the radio communication software programs according to a domain for each of the radio communication software programs and performing activation, setup, and connection with other programs for each of the radio communication software programs.

Description

BRIEF DESCRIPTION OF DRAWINGS

(1) FIG. 1 is a diagram to explain a software-defined radio device.

(2) FIG. 2 is a diagram depicting a software configuration of the software-defined radio device.

(3) FIG. 3 is a diagram depicting a software structure of the software-defined radio device.

(4) FIG. 4 is a diagram depicting a data structure of records in a domain data unit.

(5) FIG. 5 is a sequence of generating a domain management software thread.

(6) FIG. 6 is a diagram depicting a data structure of a thread management table.

(7) FIG. 7 is a sequence of deleting a domain management software thread.

DESCRIPTION OF EMBODIMENTS

(8) An embodiment of the invention is now described in detail.

(9) Software radio technology is a radio communication technology that enables switching between radio communication protocols by changing control software without modifying hardware itself. FIG. 1 depicts an overview of a software-defined radio device 100. The software-defined radio device 100 includes, as hardware modules, an antenna 101, a radio frequency unit 102, an A/D and D/A unit 103, a digital signal processing unit 104, and a control unit 105. The antenna 101 performs radio frequency signal transmission and reception. The radio frequency unit 102 converts a received signal in a radio frequency band received by the antenna 101 to a received signal in a low frequency band or converts a transmission signal in a low frequency band to a transmission signal in a radio frequency band. The A/D and D/A unit 103 converts an analog signal received to a digital signal or converts a digital signal to transmit to an analog signal. The digital signal processing unit 104 performs processing such as, inter alia, encoding a transmission signal and decoding a received signal. The control unit 105 receives control from a control terminal 107 via a network 106 and performs control of the hardware modules of the software-defined radio device.

(10) FIG. 2 depicts a software configuration of the software-defined radio device 100. Hardware modules 220 to 222 correspond to the radio frequency unit 102, A/D and D/A unit 103, and digital signal processing unit 104 in FIG. 1, respectively. Hardware device drivers 210 to 212 drive these hardware modules 220 to 222, respectively. Although they operate on a predefined OS (Operating System) 209, applications and OS/hardware are made separable by CORBA middleware 208. When the software-defined radio device is powered on, the OS 209, hardware device drivers 210 to 212, and CORBA middleware 208 are first activated. Then, environment software programs 215 are activated. The environment software programs 215 are those that have to be active at all time for the software-defined radio device to operate, and a user interface program 201, domain management software 202, hardware management software 204, hardware control software pieces 205 to 207 are included therein. The hardware control software pieces 205 to 207 are also provided to correspond to the hardware device drivers 210 to 212 and they are host software for controlling these drivers.

(11) As a feature of the software-defined radio device, radio functions such as filtering, modulation and demodulation, equalization, and a synchronization function are made programmable and, by rewriting software, change can be made to system-specific radio functions such as a modulation scheme, a transmitting and receiving frequency, a bandwidth, and a transmission rate which are radio parameters. Programs that are rewritten to change these parameters are radio communication software programs 203. Therefore, most of them are activated according to an instruction from a user interface program 201, though the radio communication software programs 203 can be activated also when the device is powered on. In addition, radio communication software programs are heretofore pieces of software managed under one domain and, within the same domain, an interface necessary to use the radio communication software programs is common and, therefore, the software-defined radio device does not need to be aware of the domain. In contrast, in the present embodiment, the software-defined radio device is allowed to use radio communication software programs which are managed under different domains. For this reason, domain management software 202 is provided that, according to a domain under which a radio communication software program is managed, generates an interface necessary to use that program, performs activation, setup, and connection with other programs for the radio communication software program, and also receives, inter alia, a notification of abnormality and a request for an operation record from a software program. This enables the software-defined radio device to use radio communication software programs managed under predefined domains, with the radio communication software programs 203 being free from a fixed domain.

(12) The domain management software 202 is implemented as the environment software 215, as noted above, in the present embodiment. To make this configuration effective, it is necessary for the software-defined radio device to have a domain management software function for plural domains which are anticipated to be used and this function has to be active at all time. That is, since the environment software is not arbitrarily activated by a user, the domain management software regarding radio communication software programs that are likely to be activated has to be activated when the device is powered on. Therefore, even though a radio communication software program being actually used at a point of time is the radio communication software program belonging to one domain, considering that the domain management software covering all domains of such programs that are likely to be used must have been started up, memory consumption involved in this operation results in deterioration of performance of the software-defined radio device or battery drainage, and efficiency decreases significantly.

(13) FIG. 3 depicts a software structure that enables execution of radio communication software programs under plural domains, while maintaining the performance of the software-defined radio device. FIG. 4 depicts a data structure of records in a domain data unit 304. The domain data unit 304 is for recording the software name of a radio communication software program and a domain path in which the software is located. A domain path denotes a domain under which the radio communication software program is managed. Thereby, the user interface program 201 can become aware of a domain under which a radio software program is managed by searching through the domain data unit 304.

(14) An integrated domain management software 301 implements the function of the domain management software 202 described in FIG. 2 as threads. By the implementation with threads in this way, only a process (parent thread) of the integrated domain management software will be active at all time and domain management software threads which are implemented as its child threads will be generated as required and deleted when no longer necessary; thereby, performance deterioration or battery drainage can be avoided.

(15) A sequence of generating a domain management software thread 302i is described using FIG. 5. When a user interface unit 201 is instructed of a radio communication software program to be activated from a user (S51), it sends a search instruction to the domain data unit 304 (S52) to become aware of a domain under which the radio communication software program is managed. Upon receiving a search result from the domain data unit 304 (S53), the user interface unit 201 checks with the integrated domain management software 301 as to whether the corresponding domain management software thread has been generated (S54). This inquiry may be made through either a CORBA interface specified in IDL or a message interface using inter-process communication. The integrated domain management software 301 checks to see whether the thread has already been generated using a thread management table which is presented in FIG. 6 (S55). In the thread management table, a memory address is stored where a CORBA servant object that executes a domain management software thread for the corresponding domain is stored, for example, as presented in FIG. 6. If such address is registered, it can be determined that the thread has been generated; if not, the thread has not yet been generated. If the thread has been generated, a response telling that the domain management software thread has been generated is sent to the user interface unit 201 (S56). If the domain management software thread has not yet been generated, the integrated domain management software 301 generates the corresponding domain management software thread (S57), receives a report of generation (S58), and sends a response telling that the domain management software thread has been generated to the user interface unit 201 (S56). Upon completing activation, a newly generated CORBA servant notifies the integrated domain management software 301 of completion of the activation (S59). At this stage, the integrated domain management software 301 updates the thread management table (FIG. 6) and notifies the user interface unit that activation of the domain management software thread (CORBA servant) has been completed. After that, the user interface unit 201 calls a CORBA servant interface to send an instruction to activate the radio communication software program (S62).

(16) A sequence of deleting a domain management software thread 302i is described using FIG. 7. When the user interface unit 201 is instructed of a radio communication software program to be terminated from a user (S71), it sends a search instruction to the domain data unit 304 (S72) to become aware of a domain under which the radio communication software program is managed. Upon receiving a search result from the domain data unit 304 (S73), the user interface unit 201 calls the corresponding CORBA servant interface and sends an instruction to terminate the radio communication software program (S74). Upon completing termination of the radio communication software program, the domain management software thread 302i instructed of the termination notifies the user interface unit 201 of completion of the termination (S75). With respect to radio communication software programs that are active currently, the user interface unit 201 checks to see whether there is another radio communication software program that is active currently under the same domain that the terminated program belongs to (S76). If there is another radio communication software program that is active, the processing terminates here. Otherwise, if there is not another radio communication software program that is active under that domain, unnecessary battery use can be avoided and unnecessary memory can be released by deactivating the domain management software thread. Then, the user interface unit 201 issues a request to deactivate the domain management software thread for that domain to the integrated domain management software 301 (S79). Upon receiving this request, the integrated domain management software 301 deactivates the corresponding thread of domain management software (S80) and sends a confirmation response that the domain management software thread is being deactivated to the user interface unit 201 (S81). Upon completion of deactivating the domain management software thread (S82), the integrated domain management software 301 updates the thread management table (FIG. 6) (S83, deletes the address of the CORBA servant object) and notifies the user interface unit 201 that deactivation of the domain management software thread has been completed.

INDUSTRIAL APPLICABILITY

(17) The present invention is applicable to software-defined radio devices and suited for domain management internal to a software-defined radio device. Moreover, the present invention is suited for radio systems that can use radio communication software programs belonging to plural domains, minimizing deterioration of performance of software-defined radio devices and radio device battery drainage. This application claims the benefit of priority on the basis of Japanese Patent Application No. 2017-050730 filed on Mar. 16, 2017, the disclosure of which is incorporated by citation herein in its entirety.

REFERENCE SIGNS LIST

(18) 100: software-defined radio device,

(19) 101: antenna,

(20) 102: radio frequency unit,

(21) 103: A/D and D/A unit

(22) 104: digital signal processing unit,

(23) 105: control unit,

(24) 106: network,

(25) 107: control terminal