CN116614388B - Method and terminal for realizing domain manager model based on software communication system structure - Google Patents

Abstract

The invention relates to a method and a terminal for realizing a domain manager model based on a software communication system structure, wherein the method comprises the following steps: a domain manager interface and an implementation of a domain manager; implementation of the domain manager interface: each component instance corresponds to a component identifier interface and a component interface, and the attributes in the component interface include: domain manager configuration file attributes, device manager attributes, application factory attributes, and file manager attributes; implementation of the domain manager: creating a file manager, initializing a domain manager, activating the domain manager, acquiring parameters of the domain manager, starting event services of the IDM and the ODM, setting naming services for the domain manager, starting a component registration program, and installing and uninstalling an application program. The invention provides a complete domain manager interface conforming to SCA specification and SRTF standard and a construction mode of a domain manager, thereby greatly facilitating the management of the whole domain and obviously improving the operation efficiency of the domain.

Description

Implementation method and terminal of domain manager model based on software communication architecture

Technical field

The present invention relates to an implementation method and terminal of a domain manager model, specifically to an implementation method and terminal of a domain manager model based on software communication architecture.

Background technique

Software-defined radio (SDR) is a radio broadcast communication technology that is based on a software-defined wireless communication protocol rather than through hard wiring. The frequency band, air interface protocol and functions can be upgraded through software downloads and updates. No need to completely replace the hardware. It is an effective and secure solution to the problem of building multi-mode, multi-frequency and multi-function wireless communication devices. Software-defined radio can replace several different radios (functions defined and limited by hardware) with a single universal radio (built from common hardware) that can be reconfigured through software, i.e., software controls performance parameters such as wavelength, Modulation or encryption. To make interoperability between radios possible, the Software Communications Architecture (SCA) standard is a key element. SCA is an open framework that defines how software and hardware components interoperate in software-defined radios, and SCA integrates interoperability features and standards defined in the Common Object Request Broker Architecture (CORBA) specification originally developed by the Object Management Group (OMG).

Software architecture is an important part of SCA. It includes core framework (CF) and operating environment (OE). The core framework includes domain manager, device manager, services and devices, etc., and is mainly responsible for managing and connecting various components in the system. Components complete communication tasks between components.

In SCA, the SCA domain includes event channels, nodes, devices, components, services, implementations, etc. The components in the SCA application can run on different nodes, so a domain manager is required to manage and control the entire SCA domain.

There are currently a small number of existing technologies that propose the function of installing and deleting applications by domain managers, such as the patent application with application number 201410366827.4, titled "A core framework integration method based on software communication architecture", but there are no documents and The existing technology proposes a specific implementation method for the entire model architecture of the domain manager.

Contents of the invention

The present invention provides an implementation method and terminal of a domain manager model based on software communication architecture to provide a complete domain manager that complies with SCA (Software Communication Architecture) specifications and SRTF (Software Radio Communication Equipment Architecture) standards. The interface and domain manager are constructed in a way that facilitates the management of the entire domain and improves the operational efficiency of the domain.

The implementation method of the domain manager model based on the software communication architecture of the present invention includes the implementation of the domain manager interface and the implementation of the domain manager. The domain manager is accessed through the domain manager interface, and the domain manager interface is used for configuring and Manage devices, services and applications within the domain, and the domain manager is used to manage resources of the entire system;

The implementation of the domain manager interface includes:

Each component instance corresponds to a component identifier interface and a component interface. The component identifier interface stores the unique identifier of the component instance. The properties in the component interface include: domain manager configuration file properties, device manager properties, application programs properties, application factory properties, and file manager properties;

The component instance refers to an independent software module that has autonomous functions and provides one or more access interfaces. in,

Implementation of domain manager configuration file attributes: Copy the domain manager configuration file attributes of the domain manager object to the newly allocated memory space, and return the newly allocated memory space information to the client;

Implementation of device manager properties: Prevent concurrent access to the device manager list through a mutex, copy each device manager as a CORBA object (Common Object Request Broker Architecture Object), and add this CORBA object to the device manager in the sequence buffer of the device list, and then call the function to unlock the mutex variable of the mutex; control all device managers in the domain through the device manager properties, and then control all devices in the domain through the device manager;

Implementation of application attributes: Get the number of applications in the domain manager through a function, take out the application object of the current node from each application, and copy the reference of the application object to the cache, and copy the application objects of all applications. After reference, all application objects are returned to the client; the application attributes contain the sequence of application management components in the domain, and the application objects of the applications in the domain are obtained through the application attributes, thereby controlling the application;

Implementation of the application factory attribute: Get the number of application factories in the domain manager, take out the application factory object of the current node from each application factory, and copy the reference of the application factory object to the cache, and copy all applications After obtaining the reference of the program factory object, return each application factory object to the client;

Implementation of file manager attributes: Copy the reference of the domain manager's file management object to an initialized parameter object, and return the copied parameter object. The file manager attributes are used to control the file manager;

After each attribute is implemented, a log record is written to the domain manager's log indicating that the attribute has been obtained;

The domain manager implementation includes:

Create a file manager in the object implemented by the domain manager, then initialize the domain manager, and then activate the domain manager through the activation function. After obtaining the parameters of the domain manager, start IDM (Input Domain Manager, domain manager input) and ODM (Output Domain Manager, domain manager output) event service, then set the naming service for the domain manager by creating a naming service function, and start the component registration program through the component registration function, and then obtain the application file through the get installation file function. Application installation, when the application needs to be uninstalled, call the function to delete the application configuration file name from the installed application file to prevent the application from being automatically reinstalled when the domain manager restarts, and then uninstall the application from the domain.

The domain manager provided by the invention has a control function and can control all devices and services in the domain, as well as the specific implementation process of the domain manager's installation, uninstallation and registration functions. At the same time, it also proposes a logging function for tracking Access to each attribute is recorded in the event log of the domain manager. The implementation of the domain manager and domain manager interface is fully compliant with the SCA (Software Communications Architecture) specification and the SRTF (Software Radio Communications Equipment Architecture) standard.

Specifically, the implementation of the domain manager configuration file attribute is to first define a check function and a configuration file path function for obtaining the configuration file path of the domain manager, and then call the check function to check whether the domain manager is Shut down. If it is shutting down, the check function will return information that the domain manager is shutting down and terminate subsequent operations; if the domain manager is not shut down, it will determine whether the configuration file path of the domain manager obtained through the configuration file path function is empty. Then allocate memory space that matches the domain manager configuration file attributes, determine whether the domain manager configuration file attributes have been allocated a non-null pointer, if not, throw an exception, and if so, copy the domain manager configuration file attributes to in the allocated memory space, and returns the allocated memory space information to the client. Finally, a log record is written to the domain manager's log, indicating that the domain manager configuration file attributes have been obtained, and then the log record memory is released and returned to domain management. A sequence of server configuration file properties.

Specifically, the device manager attribute is implemented by first obtaining the device manager list in the domain manager, and then using a mutex to protect concurrent access to the device manager list to prevent multiple threads from modifying device management at the same time. content in the device manager list, then traverse the device manager list and calculate the total number of device managers, then call the allocation function to allocate memory space, use the memory space as a sequence object that encapsulates all device managers, and set it according to the number of device managers. Determine the buffer size of the sequence object and use it as the buffer for all device manager sequence objects, then iterate through the device manager list, copy each device manager as a CORBA object, and add the CORBA object to the buffer, then call a function to unlock the mutex variable of the mutex lock, and finally write a log record to the domain manager's log, record the log message of accessing the device manager properties to the domain manager's log, and then release the log Record the memory and return the sequence object, control all device managers and services in the domain through the device manager properties, control all devices in the domain through the device manager, and manage the node through the device manager in a node All equipment and services within.

Specifically, the implementation of the application attributes is to first define a function for obtaining all application objects under the domain manager, call this function to allocate memory for storing all application objects, and then lock it through threads to prevent When other concurrent operations interfere with processing the application list, then assign the number of applications in the domain manager to a parameter, add the application to the buffer, take the application object of the current node from the application, and copy the The reference of the application object is stored in the cache. After copying the references of all application objects, a thread is used to unlock the application object and the application object is returned to the client. Finally, a log record is written to the domain manager's log indicating that access has been obtained. Application attributes include a sequence of application management components in the domain. Through the application attributes, the object of the application in the domain is obtained, thereby controlling the application.

Specifically, the implementation of the application factory attribute is to first define a function for obtaining all application factory objects under the domain manager, call this function to allocate the memory size for storing all application factory objects, and then use thread locking. , to prevent other concurrent operations from interfering when processing the application factory list, and then assign the number of application factories in the domain manager to a parameter, then allocate memory for the application factory object and add the application factory object to the buffer, Get the application factory object of the current node from the application factory, and copy the reference of the application factory object to the cache. After copying the references of all application factory objects, use thread unlocking and return the application factory object to The client, finally writes a log record to the domain manager's log indicating that access to the application factory property has been obtained.

Specifically, the implementation of the file manager attribute is to first define a function for obtaining the file manager object under the domain manager, and call this function to copy the reference of the file management object of the domain manager to an initialized Among the parameters, if the copy is successful, a log record is written to the domain manager's log, indicating that access to the file manager attribute has been obtained. If the copy fails, an exception is thrown. Finally, the copied parameters are returned and passed through the file. Manager properties control the file manager.

Specifically, in the implementation of the domain manager, the file manager is created in the object implemented by the domain manager through the function of creating the file manager: allocate an object implemented by the file manager, and then initialize the object and set the callback function, then activate and convert the object into a CORBA object reference, and finally return the CORBA object reference of the file manager;

Then initialize the domain manager through the domain manager initialization function, including initializing the code and data generated from the interface description file, then initializing each component and domain manager configuration description file, then initializing each attribute, assigning an initial value to each attribute, and finally initializing Various ports;

The domain manager is activated through the activation function. First, a log is recorded indicating that the domain manager has started to activate. Then the activation function is called to activate the implementation object of the domain manager, and the object identifier returned by the implementation object is stored in the domain manager implementation structure. In the corresponding field, finally, release the memory of the corresponding field and set it to NULL;

When obtaining the parameters of the domain manager, use the Get Domain Manager Reference function to obtain the object reference of the domain manager, then convert the incoming implementation object parameters into the object reference of the domain manager through the function, and finally return the object reference;

Then start the event services of IDM and ODM respectively by starting the event service function: initialize the object reference and event service channel of the event service of IDM and ODM through the function, and then add the event service of IDM and ODM to the registered service of the domain manager through the function In the list, the object reference of the event service of IDM and ODM is finally returned;

The step of setting the naming service for the domain manager by creating the naming service function is to parse the initial reference of the naming service, create a new naming context, and bind the domain manager object to the naming context;

To start the component registration program through the component registration function, it is first determined whether the device object is empty and valid, and the expired device object is uninstalled through the uninstall function; when the device object is not empty and valid, it is retrieved from the file according to the device information. Load the software configuration file in the system, allocate memory space for the software package description file variables, then parse the data in the software package description file and store the results in the software package description file parsing variables, release the memory of the software package description file variables, and then obtain The device manager where the device object is located locks the mutex variable through the lock function to prevent concurrent access problems when processing the device manager list, and then obtains the device object identifier and device ID and stores them in the corresponding variables, through the function Check whether the interface of the device object implements the device object interface defined in the SCA (Software Communications Architecture) specification and the SRTF (Software Radio Communications Equipment Architecture) standard. If it is implemented, pass the variables storing the device identifier and device ID to In the domain manager device addition function, add the device object to the domain manager and register it, and then unlock the mutex variable through the unlock function;

The method of obtaining application files for application installation through the Get Installation File function is to first obtain the application file name of the installation domain manager, then parse the corresponding application files and related files, loop through the application factory list, and check whether The specified application has been installed in the file system. If it has been installed, continue to install the next application. Otherwise, install the corresponding application factory for the specified application and set the relevant attribute values for the application factory. Finally, add the application factory to the list of application factories.

Specifically, in the implementation of the domain manager, the application is uninstalled from the domain manager configuration file through the uninstall application function. First, the application with the specified identifier is found, and then the function is called to delete the application from the installed application file. The name of the application configuration file corresponding to the specified identifier prevents the application from being automatically reinstalled when the domain manager is restarted, and finally uninstalling the application from the domain.

The present invention also provides an implementation terminal of the domain manager model based on the software communication architecture for the above implementation method. The domain manager is provided with a domain manager interface, and the domain manager interface includes a link to each domain manager. The component identifier interface and the component interface corresponding to the component instance. The component identifier interface is provided with a storage space for storing the unique identifier of the component instance. The component interface includes a domain manager configuration file attribute implementation module set in parallel. , device manager property implementation module, application property implementation module, application factory property implementation module, file manager property implementation module, and log module. The domain manager can be accessed through the domain manager interface;

The domain manager includes sequential connections:

File manager creation module: creates a file manager in the object implemented by the domain manager and returns the CORBA object reference of the file manager;

Domain manager initialization module: Initialize the domain manager, including initializing the code and data generated from the interface description file, initializing each component and domain manager configuration description file, initializing each attribute, assigning initial values to each attribute, and initializing various ports. ;

Domain manager activation module: Activate the domain manager through the activation function, and store the object identifier returned by the implementation object into the corresponding field of the domain manager implementation structure;

Domain manager parameter acquisition module: Use the Get Domain Manager Reference function to obtain the object reference of the domain manager, then convert the incoming implementation object parameters into the object reference of the domain manager through the function, and finally return the object reference;

Event service module: Start the event service of IDM and ODM, add the event service of IDM and ODM to the list of registered services of the domain manager, and return the object reference of the event service of IDM and ODM;

Domain manager naming module: Sets the naming service for the domain manager and binds the domain manager object to the naming context;

Component registration module: Start the component registration program, add the device object to the domain manager and register it;

Application installation module: obtain the application files for application installation, and add the application factory corresponding to the application to the application factory list;

Application Uninstall Module: Removes the application profile name from installed application files before uninstalling the application from the domain.

The present invention also provides a terminal, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor. The processor executes the above software-based communication system when executing the computer program. Implementation method of the domain manager model of the structure.

The beneficial effects of the present invention include:

1. Provides a complete domain manager interface and domain manager construction method that conforms to SCA (Software Communications Architecture) specifications and SRTF (Software Radio Communications Equipment Architecture) standards, which greatly facilitates the management of the entire domain, and The operational efficiency of the domain is significantly improved.

2. It realizes access, operation and management of all components in the entire domain, and provides an interface for accessing the domain and components within the domain for systems based on software communication architecture.

Description of the drawings

Figure 1 is a flow chart of the implementation method of the domain manager model based on the software communication architecture of the present invention.

Figure 2 is a flow chart of initializing the domain manager in Figure 1.

Figure 3 is a flow chart of the startup component registration procedure of the domain manager in Figure 1.

Implementation

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only These are part of the embodiments of this application, but not all of them. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Accordingly, the following detailed description of the embodiments of the application provided in the appended drawings is not intended to limit the scope of the claimed application, but rather to represent selected embodiments of the application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without any creative work shall fall within the scope of protection of this application.

Example 1:

As shown in Figure 1, the implementation method of the domain manager model based on the software communication architecture of the present invention includes the implementation of the domain manager interface and the implementation of the domain manager. The domain manager is accessed through the domain manager interface. The domain management The domain manager interface is used to configure and manage devices, services and applications within the domain, and the domain manager is used to manage the resources of the entire system;

The implementation of the domain manager interface includes:

Each component instance corresponds to a component identifier interface and a component interface. The component identifier interface stores the unique identifier of the component instance. The attributes in the component interface include: domain manager profile attributes (domainManagerProfile), device manager attributes (managers), application properties (applications), application factory properties (applicationFactories), and file manager properties (fileMgr); the component instances refer to independent autonomous functions and provide one or more access Interface software module. in,

Implementation of domain manager configuration file attributes: Copy the domain manager configuration file attributes of the domain manager object to the newly allocated memory space, and return the newly allocated memory space information to the client;

Implementation of device manager properties: Prevent concurrent access to the device manager list through a mutex, copy each device manager as a CORBA object (Common Object Request Broker Architecture Object), and add this CORBA object to the device manager in the sequence buffer of the device list, and then call the function to unlock the mutex variable of the mutex; control all device managers in the domain through the device manager properties, and then control all devices in the domain through the device manager;

Implementation of application attributes: Get the number of applications in the domain manager through a function, take out the application object of the current node from each application, and copy the reference of the application object to the cache, and copy the application objects of all applications. After reference, all application objects are returned to the client; the application attributes contain the sequence of application management components in the domain, and the application objects of the applications in the domain are obtained through the application attributes, thereby controlling the application;

Implementation of the application factory attribute: Get the number of application factories in the domain manager, take out the application factory object of the current node from each application factory, and copy the reference of the application factory object to the cache, and copy all applications After obtaining the reference of the program factory object, return each application factory object to the client;

Implementation of file manager attributes: Copy the reference of the domain manager's file management object to an initialized parameter object, and return the copied parameter object. The file manager attributes are used to control the file manager;

After each attribute is implemented, a log record is written to the domain manager's log indicating that the attribute has been obtained;

The domain manager implementation includes:

Create a file manager in the object implemented by the domain manager, then initialize the domain manager, and then activate the domain manager through the activation function. After obtaining the parameters of the domain manager, start IDM (Input Domain Manager, domain manager input) and ODM (Output Domain Manager, domain manager output) event service, then set the naming service for the domain manager by creating a naming service function, and start the component registration program through the component registration function, and then obtain the application file through the get installation file function. Application installation, when the application needs to be uninstalled, call the function to delete the application configuration file name from the installed application file to prevent the application from being automatically reinstalled when the domain manager restarts, and then uninstall the application from the domain.

The domain manager provided by the invention has a control function and can control all devices and services in the domain, as well as the specific implementation process of the domain manager's installation, uninstallation and registration functions. At the same time, it also proposes a logging function for tracking Access to each attribute is recorded in the event log of the domain manager. The implementation of the domain manager and domain manager interface is fully compliant with the SCA (Software Communications Architecture) specification and the SRTF (Software Radio Communications Equipment Architecture) standard.

Example 2:

On the basis of Embodiment 1, the implementation of the domain manager configuration file attribute is to first define a check function and a configuration file path function for obtaining the configuration file path of the domain manager, and then call the check function to check Whether the domain manager is shutting down. If it is shutting down, the check function will return the information that the domain manager is shutting down and terminate subsequent operations; if the domain manager is not shutting down, it will determine the configuration file of the domain manager obtained through the configuration file path function. Whether the path is empty, then allocate memory space that matches the domain manager configuration file attributes, determine whether the domain manager configuration file attributes have been allocated a non-null pointer, if not, throw an exception, if so, add the domain manager The configuration file attributes are copied to the allocated memory space, and the allocated memory space information is returned to the client. Finally, a log record is written to the domain manager's log, indicating that the domain manager configuration file attributes have been obtained, and then the log record is released. Memory and returns a sequence of domain manager profile properties.

Example 3:

On the basis of Embodiment 1, the device manager attribute is implemented by first obtaining the device manager list in the domain manager, and then using a mutex lock to protect concurrent access to the device manager list to prevent multiple The thread simultaneously modifies the content in the device manager list, then traverses the device manager list and calculates the total number of device managers, then calls the allocation function to allocate memory space, and uses the memory space as a sequence object that encapsulates all device managers. According to the device The number of managers sets the buffer size of the sequence object and uses it as the buffer for all device manager sequence objects. Then iterates through the device manager list, copies each device manager into a CORBA object, and copies the CORBA The object is added to said buffer, then a function is called to unlock the mutex's mutex variable, and finally a log record is written to the domain manager's log, and a log message for accessing the device manager's properties is logged to the domain manager's log. , then releases the logging memory and returns the sequence object, controls all device managers and services in the domain through the device manager attributes, controls all devices in the domain through the device manager, and controls the device management in a node The server manages all devices and services within the node.

Example 4:

On the basis of Embodiment 1, the implementation of the application attributes is to first define a function for obtaining all application objects under the domain manager, call the function to allocate memory for storing all application objects, and then use The thread locks to prevent interference from other concurrent operations when processing the application list, then assigns the number of applications in the domain manager to a parameter, adds the application to the buffer, and removes the application of the current node from the application. object and copy the reference of the application object to the cache. After copying the references of all application objects, use the thread to unlock and return the application object to the client. Finally, write a log record to the domain manager's log. , indicating that the application attribute has been accessed. The application attribute contains the sequence of application management components in the domain. The object of the application in the domain is obtained through the application attribute, thereby controlling the application.

Example 5:

On the basis of Embodiment 1, the implementation of the application factory attribute is to first define a function for obtaining all application factory objects under the domain manager, and call this function to allocate the memory size for storing all application factory objects. Then use thread locking to prevent interference from other concurrent operations when processing the application factory list, then assign the number of application factories in the domain manager to a parameter, then allocate memory for the application factory object and add the application factory object to the buffer, take out the application factory object of the current node from the application factory, and copy the reference of the application factory object to the cache. After copying the references of all application factory objects, use thread unlocking and apply The application factory object is returned to the client, and finally a log record is written to the domain manager's log indicating that access to the application factory properties has been obtained.

Example 6:

On the basis of Embodiment 1, the implementation of the file manager attribute is to first define a function for obtaining the file manager object under the domain manager, and call the function to copy the reference of the file management object of the domain manager. into an initialized parameter. If the copy is successful, a log record is written to the domain manager's log, indicating that access to the file manager attribute has been obtained. If the copy fails, an exception is thrown. Finally, all copied values are returned. The above parameters are used to control the file manager through the file manager properties.

Example 7:

On the basis of Embodiment 1, in the implementation of the domain manager, the file manager is created in the object implemented by the domain manager through the function of creating the file manager: allocate an object implemented by the file manager, and then assign the object Initialize the object and set the callback function, then activate the object and convert it into a CORBA object reference, and finally return the CORBA object reference of the file manager;

The domain manager is then initialized through the domain manager initialization function, as shown in Figure 2, including initializing the code and data generated from the interface description file, such as the code and data generated by CosNaming.idl and CF.idl. Then initialize each component, such as the creation and number of application factories, the creation and number of applications, the creation of device managers, the creation and number of device objects, and the creation of services; initialize the domain manager configuration description file (DMD), first Create a file system to read the domain manager configuration description file, then parse the domain manager configuration description file through the DMD parsing function, and pass the parsing result to a parameter to determine whether the parameter is empty. If it is not empty, release the parameters, and release file system resources at the same time; then initialize each attribute, assign an initial value to each attribute, and finally initialize various ports, such as the device manager registration port, installation port, time channel port, etc. in the domain;

Activate the domain manager through the activation function. First, use the CF_DEBUG0 macro to record a log indicating that the domain manager has started to activate. Then call the activation function to activate the implementation object of the domain manager, and store the object identifier returned by the implementation object to the domain manager implementation. In the corresponding field of the structure, finally, release the memory of the corresponding field and set it to NULL;

When obtaining the parameters of the domain manager, use the Get Domain Manager Reference function to obtain the object reference of the domain manager, and then use the function to convert the incoming implementation object parameters into the object reference of the domain manager. Check whether the object reference is empty. If not, If it is empty, the object reference is returned;

Then start the event services of IDM and ODM respectively by starting the event service function: initialize the object reference and event service channel of the event service of IDM and ODM through the function, and then use the function to set the IDM_Channel service and ODM_Channel service corresponding to the event service of IDM and ODM respectively. Add to the list of registered services of the domain manager, and finally return the object references of the IDM_Channel service and ODM_Channel service;

The step of setting the naming service for the domain manager by creating the naming service function is to parse the initial reference of the naming service, create a new naming context, and bind the domain manager object to the naming context;

The component registration program is started through the component registration function, as shown in Figure 3. It is first judged whether the device object is empty and valid. If the device object is empty, an exception will be thrown. If the device object is invalid, the uninstall function will be used to remove the device object. Uninstall the invalid device object; when the device object is not empty and valid, obtain the device label, software configuration file path, device ID and other information through the device management interface, load the software configuration file from the file system, and then calculate and parse the software package The memory space required by the description file (SPD), allocates memory space for the software package description file variables, then parses the data in the software package description file through the SPD parsing function and stores the results in the software package description file parsing variables, and releases the software package Describe the memory of the file variable, then obtain the device manager where the device object is located, lock the mutex variable through the locking function to prevent concurrent access problems when processing the device manager list, and then obtain the device object identifier and device ID and store them In the corresponding variable, the function checks whether the device object interface implements the device object interface defined in the SCA (Software Communications Architecture) specification and the SRTF standard (Software Radio Communications Equipment Architecture). If it is implemented, the device identifier will be stored and device ID variables are passed to the domain manager device addition function, the device object is added to the domain manager and registered, then the mutex variable is unlocked through the unlock function, and the current registered device list is printed. If the device registration fails, according to Different failure reasons use different exception types to handle the error situation, and output corresponding log records, and finally call the clear function to release the used memory space;

Obtaining the file of the application through the Get Installation File function to install the application is to obtain the file of the application through the Get Installation File function and retrieve the name of the file (i.e., SAD file) used to store the installation application; through the Install Application function To install an application, first obtain the application file name for installing the domain manager, and call the allocation function to allocate storage space for it and store the SAD file in the storage space. Then check whether the file exists. If it exists, parse the corresponding application. Program files and related files, loop through the application factory list, check whether the specified application has been installed in the file system, if it has been installed, continue to install the next application, otherwise, install the corresponding application for the specified application program factory, and set relevant attribute values for the application factory, such as application factory name and identifier, software configuration file, etc., and finally add the application factory to the application factory list.

Example 8:

Based on the above embodiment, in the implementation of the domain manager, the application is uninstalled from the domain manager configuration file through the uninstall application function. First, the application with the specified identifier is searched, and then the function is called to remove the installed application from the application. Remove the application profile name corresponding to the specified identifier from the program file, prevent the application from being automatically reinstalled when the domain manager restarts, and finally uninstall the application from the domain.

Example 9:

The present invention also provides an implementation terminal for the domain manager model based on the software communication architecture of the above implementation method embodiment. The domain manager is provided with a domain manager interface, and the domain manager interface includes: The component identifier interface and the component interface corresponding to each component instance. The component identifier interface is provided with a storage space for storing the unique identifier of the component instance. The component interface includes domain manager configuration file attributes set in parallel. Implementation module, device manager property implementation module, application property implementation module, application factory property implementation module, file manager property implementation module, and logging module.

Example 10:

Based on Embodiment 9, the domain manager includes sequential connections:

File manager creation module: creates a file manager in the object implemented by the domain manager and returns the CORBA object reference of the file manager;

Domain manager initialization module: Initialize the domain manager, including initializing the code and data generated from the interface description file, initializing each component and domain manager configuration description file, initializing each attribute, assigning initial values to each attribute, and initializing various ports. ;

Domain manager activation module: Activate the domain manager through the activation function, and store the object identifier returned by the implementation object into the corresponding field of the domain manager implementation structure;

Domain manager parameter acquisition module: Use the Get Domain Manager Reference function to obtain the object reference of the domain manager, then convert the incoming implementation object parameters into the object reference of the domain manager through the function, and finally return the object reference;

Event service module: Start the event service of IDM and ODM, add the event service of IDM and ODM to the list of registered services of the domain manager, and return the object reference of the event service of IDM and ODM;

Domain manager naming module: Sets the naming service for the domain manager and binds the domain manager object to the naming context;

Component registration module: Start the component registration program, add the device object to the domain manager and register it;

Application installation module: obtain the application files for application installation, and add the application factory corresponding to the application to the application factory list;

Application Uninstall Module: Removes the application profile name from installed application files before uninstalling the application from the domain.

Example 11:

Based on the above embodiments, the present invention also provides a terminal, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. The processor executes the computer program. The program executes the implementation method of the domain manager model based on the software communication architecture in the above embodiment.

The above-described embodiments only express specific implementation modes of the present application, and their descriptions are relatively specific and detailed, but should not be construed as limiting the scope of protection of the present application. It should be noted that, for those of ordinary skill in the art, relevant modifications and improvements can be made without departing from the concept of the technical solution of the present application, and these all belong to the protection scope of the present application.

Claims (10)

1. An implementation method of a domain manager model based on software communication architecture, which is characterized by: including the implementation of a domain manager interface and the implementation of a domain manager, accessing the domain manager through the domain manager interface, and the domain manager interface Used to configure and manage devices, services and applications within the domain, and the domain manager is used to manage resources of the entire system; The implementation of the domain manager interface includes: Each component instance corresponds to a component identifier interface and a component interface. The component identifier interface stores the unique identifier of the component instance. The properties in the component interface include: domain manager configuration file properties, device manager properties, application programs properties, application factory properties, and file manager properties; where, Implementation of domain manager configuration file attributes: Copy the domain manager configuration file attributes of the domain manager object to the newly allocated memory space, and return the newly allocated memory space information to the client; Implementation of device manager properties: prevent concurrent access to the device manager list through a mutex, copy each device manager as a CORBA object, and add the CORBA object to the sequence buffer of the device manager list, and then Call the function to unlock the mutex variable of the mutex lock; control all device managers in the domain through the device manager properties, and then control all devices in the domain through the device manager; Implementation of application attributes: Get the number of applications in the domain manager through a function, take out the application object of the current node from each application, and copy the reference of the application object to the cache, and copy the application objects of all applications. After reference, all application objects are returned to the client; the application attributes contain the sequence of application management components in the domain, and the application objects of the applications in the domain are obtained through the application attributes, thereby controlling the application; Implementation of the application factory attribute: Get the number of application factories in the domain manager, take out the application factory object of the current node from each application factory, and copy the reference of the application factory object to the cache, and copy all applications After obtaining the reference of the program factory object, return each application factory object to the client; Implementation of file manager attributes: Copy the reference of the file management object of the domain manager to an initialized parameter object, and return the copied parameter object. The file manager attributes are used to control the file manager; After each attribute is implemented, a log record is written to the domain manager's log indicating that the attribute has been obtained; The domain manager implementation includes: Create a file manager in the object implemented by the domain manager, then initialize the domain manager, and then activate the domain manager through the activation function. After obtaining the parameters of the domain manager, start the event services of IDM and ODM, and then create a naming service function Set up a naming service for the domain manager, and start the component registration program through the component registration function. Then obtain the application file through the Get Installation File function for application installation. When the application needs to be uninstalled, call the function from the installed application file. Remove the application profile name from the domain manager to prevent automatic reinstallation of the application when the domain manager restarts, and then uninstall the application from the domain. 2. The implementation method of the domain manager model based on the software communication architecture as claimed in claim 1, characterized in that: the implementation of the domain manager configuration file attributes is to first define a check function and a function for obtaining the domain management The configuration file path function of the configuration file path of the server, and then call the check function to check whether the domain manager is shutting down. If it is shutting down, the check function will return the information that the domain manager is shutting down, and terminate subsequent operations; if the domain manager is not closed, then determine whether the configuration file path of the domain manager obtained through the configuration file path function is empty, then allocate memory space that matches the domain manager configuration file attributes, and determine whether the domain manager configuration file attributes have been assigned non- Null pointer, if no, throw an exception, if yes, copy the domain manager configuration file attributes to the allocated memory space, return the allocated memory space information to the client, and finally write to the log of the domain manager A log record indicating that a domain manager profile attribute has been obtained, followed by a sequence of freeing logging memory and returning domain manager profile attributes. 3. The implementation method of the domain manager model based on the software communication architecture as claimed in claim 1, characterized in that: the implementation of the device manager attributes is to first obtain the device manager list in the domain manager, and then use A mutex lock protects concurrent access to the device manager list to prevent multiple threads from modifying the contents of the device manager list at the same time. Then it traverses the device manager list and calculates the total number of device managers, and then calls the allocation function to allocate memory. space, use this memory space as a sequence object that encapsulates all device managers, set the buffer size of the sequence object according to the number of device managers, and use it as a buffer for all device manager sequence objects, and then traverse the device managers list, copy each device manager as a CORBA object, add that CORBA object to said buffer, then call a function to unlock the mutex variable of the mutex, and finally write a log to the domain manager's log Record, record the log message of accessing the device manager properties to the log of the domain manager, then release the logging memory and return the sequence object, control all device managers and services in the domain through the device manager properties, and then use the device The manager controls all devices in the domain and manages all devices and services in the node through the device manager in the node. 4. The implementation method of the domain manager model based on the software communication architecture as claimed in claim 1, characterized in that: the implementation of the application attributes is to first define a method for obtaining all application objects under the domain manager. function, call this function to allocate memory for storing all application objects, and then lock it through threads to prevent interference from other concurrent operations when processing the application list, and then assign the number of applications in the domain manager to a parameter, Add the application to the buffer, take out the application object of the current node from the application, and copy the reference of the application object to the cache. After copying the references of all application objects, use the thread to unlock and transfer the application The object is returned to the client, and finally a log record is written to the domain manager's log, indicating that the access application attribute has been obtained. The application attribute contains the sequence of application management components in the domain. The object of the application in the domain is obtained through the application attribute, thus Take control over applications. 5. The implementation method of the domain manager model based on the software communication architecture according to claim 1, characterized in that: the implementation of the application factory attribute is to first define an application factory for obtaining all application factories under the domain manager. Object's function, call this function to allocate the memory size for storing all application factory objects, then use thread locking to prevent interference from other concurrent operations when processing the application factory list, and then assign the number of application factories in the domain manager to a parameter, then allocate memory for the application factory object and add the application factory object to the buffer, take the application factory object of the current node from the application factory, and copy the reference of the application factory object to the cache, After copying the references to all application factory objects, use a thread to unlock and return the application factory object to the client, and finally write a log record to the domain manager's log indicating that access to the application factory properties has been obtained. 6. The implementation method of the domain manager model based on the software communication architecture as claimed in claim 1, characterized in that: the implementation of the file manager attribute is to first define a file manager for obtaining the domain manager. Object's function, call this function to copy the reference of the domain manager's file management object to an initialized parameter. If the copy is successful, a log record will be written to the domain manager's log, indicating that access to the file manager has been obtained. Properties, if the copy fails, an exception is thrown. Finally, the copied parameters are returned, and the file manager is controlled through the file manager properties. 7. The implementation method of the domain manager model based on the software communication architecture as claimed in claim 1, characterized in that: in the implementation of the domain manager, the object implemented in the domain manager is created by the function of the file manager. Create a file manager in: allocate an object implemented by the file manager, then initialize the object and set the callback function, activate and convert the object into a CORBA object reference, and finally return the CORBA object reference of the file manager; Then initialize the domain manager through the domain manager initialization function, including initializing the code and data generated from the interface description file, then initializing each component and domain manager configuration description file, then initializing each attribute, assigning an initial value to each attribute, and finally initializing Various ports; The domain manager is activated through the activation function. First, a log is recorded indicating that the domain manager has started to activate. Then the activation function is called to activate the implementation object of the domain manager, and the object identifier returned by the implementation object is stored in the domain manager implementation structure. In the corresponding field, finally, release the memory of the corresponding field and set it to NULL; When obtaining the parameters of the domain manager, use the Get Domain Manager Reference function to obtain the object reference of the domain manager, then convert the incoming implementation object parameters into the object reference of the domain manager through the function, and finally return the object reference; Then start the event services of IDM and ODM respectively by starting the event service function: initialize the object reference and event service channel of the event service of IDM and ODM through the function, and then add the event service of IDM and ODM to the registered service of the domain manager through the function In the list, the object reference of the event service of IDM and ODM is finally returned; The step of setting the naming service for the domain manager by creating the naming service function is to parse the initial reference of the naming service, create a new naming context, and bind the domain manager object to the naming context; To start the component registration program through the component registration function, it is first determined whether the device object is empty and valid, and the expired device object is uninstalled through the uninstall function; when the device object is not empty and valid, it is retrieved from the file according to the device information. Load the software configuration file in the system, allocate memory space for the software package description file variables, then parse the data in the software package description file and store the results in the software package description file parsing variables, release the memory of the software package description file variables, and then obtain The device manager where the device object is located locks the mutex variable through the lock function to prevent concurrent access problems when processing the device manager list, and then obtains the device object identifier and device ID and stores them in the corresponding variables, through the function Check whether the interface of the device object implements the device object interface defined in the SCA specification and SRTF standard. If it does, pass the variables storing the device identifier and device ID to the domain manager device addition function to add the device object to the domain. Manager and register, then unlock the mutex variable through the unlock function; The method of obtaining application files for application installation through the Get Installation File function is to first obtain the application file name of the installation domain manager, then parse the corresponding application files and related files, loop through the application factory list, and check whether The specified application has been installed in the file system. If it has been installed, continue to install the next application. Otherwise, install the corresponding application factory for the specified application and set the relevant attribute values for the application factory. Finally, add the application factory to the list of application factories. 8. The implementation method of the domain manager model based on the software communication architecture as claimed in claim 1, characterized in that: in the implementation of the domain manager, the application is uninstalled from the domain manager configuration file through the uninstall application function. , first find the application with the specified identifier, and then call the function to delete the application profile name corresponding to the specified identifier from the installed application files to prevent the application from being automatically reinstalled when the domain manager restarts. Finally uninstall the application from the domain. 9. The implementation terminal of the domain manager model based on the software communication architecture for the implementation method of one of claims 1 to 8, characterized in that: a domain manager interface is provided in the domain manager, and the domain management The device interface includes a component identifier interface and a component interface corresponding to each component instance. The component identifier interface is provided with a storage space for storing the unique identifier of the component instance. The component interface includes a parallel setting domain. Manager profile attribute implementation module, device manager attribute implementation module, application attribute implementation module, application factory attribute implementation module, file manager attribute implementation module, and logging module; The domain manager includes sequential connections: File manager creation module: creates a file manager in the object implemented by the domain manager and returns the CORBA object reference of the file manager; Domain manager initialization module: Initialize the domain manager, including initializing the code and data generated from the interface description file, initializing each component and domain manager configuration description file, initializing each attribute, assigning initial values to each attribute, and initializing various ports. ; Domain manager activation module: Activate the domain manager through the activation function, and store the object identifier returned by the implementation object into the corresponding field of the domain manager implementation structure; Domain manager parameter acquisition module: Use the Get Domain Manager Reference function to obtain the object reference of the domain manager, then convert the incoming implementation object parameters into the object reference of the domain manager through the function, and finally return the object reference; Event service module: Start the event service of IDM and ODM, add the event service of IDM and ODM to the list of registered services of the domain manager, and return the object reference of the event service of IDM and ODM; Domain manager naming module: Sets the naming service for the domain manager and binds the domain manager object to the naming context; Component registration module: Start the component registration program, add the device object to the domain manager and register it; Application installation module: obtain the application files for application installation, and add the application factory corresponding to the application to the application factory list; Application Uninstall Module: Removes the application profile name from installed application files before uninstalling the application from the domain. 10. A terminal, comprising a memory, a processor and a computer program stored on the memory and capable of running on the processor, characterized in that: the processor executes claims 1 to 1 when executing the computer program. The implementation method described in one of 8.