CN116614388B - Method and terminal for realizing domain manager model based on software communication system structure - Google Patents
Method and terminal for realizing domain manager model based on software communication system structure Download PDFInfo
- Publication number
- CN116614388B CN116614388B CN202310861042.3A CN202310861042A CN116614388B CN 116614388 B CN116614388 B CN 116614388B CN 202310861042 A CN202310861042 A CN 202310861042A CN 116614388 B CN116614388 B CN 116614388B
- Authority
- CN
- China
- Prior art keywords
- manager
- domain manager
- application program
- domain
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000003213 activating effect Effects 0.000 claims abstract description 11
- 230000006870 function Effects 0.000 claims description 141
- 230000004913 activation Effects 0.000 claims description 15
- 230000007717 exclusion Effects 0.000 claims description 14
- 238000009434 installation Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 239000004973 liquid crystal related substance Substances 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000005856 abnormality Effects 0.000 claims description 2
- 238000010276 construction Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/20—Network management software packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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
Technical Field
The invention relates to a method and a terminal for realizing a domain manager model, in particular to a method and a terminal for realizing a domain manager model based on a software communication system structure.
Background
Software Defined Radio (SDR) is a radio broadcast communication technology that is based on a software defined wireless communication protocol rather than being implemented by hard-wiring, including frequency bands, air interface protocols, and functions, may all be upgraded by software downloads and updates without completely replacing the hardware. It is an effective and safe solution to the problem of building multi-mode, multi-frequency and multi-function wireless communication devices. The software defined radio may replace several different radios (functions defined and limited by hardware) with a single general purpose radio (built by general purpose hardware) which may be reconfigured by software, i.e. by software to control performance parameters such as wavelength, modulation or encryption. In order to enable interoperability between radios, the Software Communications Architecture (SCA) standard is a key element, SCA is an open framework defining 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).
The software architecture is an important component of the SCA and comprises a Core Framework (CF) and an Operating Environment (OE), wherein the core framework comprises a domain manager, a device manager, services, devices and the like, and is mainly responsible for managing and connecting various components in the system to complete communication tasks among the components.
In SCA, the SCA domain contains event channels, nodes, devices, components, services, implementations, etc., and components in the SCA application can run on different nodes, so that one domain manager is required to manage and control the entire SCA domain.
At present, a small amount of prior art proposes functions of installing and deleting applications of a domain manager, for example, patent application with application number 201410366827.4 and name of "a core framework integration method based on a software communication architecture", but no literature and prior art propose a specific implementation method for the whole model architecture of the domain manager.
Disclosure of Invention
The invention provides a method and a terminal for realizing a domain manager model based on a software communication system structure, which are used for providing a complete domain manager interface and a construction mode of a domain manager which accord with SCA (software communication system structure) standards and SRTF (software radio communication equipment system structure) standards, facilitating the management of the whole domain and improving the running efficiency of the domain.
The invention relates to a method for realizing a domain manager model based on a software communication system structure, which comprises the realization of a domain manager interface and the realization of a domain manager, wherein the domain manager is accessed through the domain manager interface, the domain manager interface is used for configuring and managing devices, services and applications in a domain, and the domain manager is used for managing the resources of the whole 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 storing a unique identifier of the component instance, the attributes in the component interface comprising: domain manager configuration file attributes, device manager attributes, application factory attributes, and file manager attributes;
the component instance refers to a separate autonomous functional software module provided with one or more access interfaces. Wherein, the liquid crystal display device comprises a liquid crystal display device,
implementation of domain manager profile attributes: copying the domain manager configuration file attribute of the domain manager object into a newly allocated memory space, and returning the information of the newly allocated memory space to a client;
implementation of device manager properties: preventing concurrent access to the device manager list by a mutex lock, copying each device manager as a CORBA object (common object request broker architecture object), adding the CORBA object to the sequence buffer of the device manager list, and then calling the mutex variable of the function unlock mutex lock; controlling all device managers in the domain through the device manager attribute, and controlling all devices in the domain through the device manager;
Implementation of application attributes: acquiring the number of application programs in a domain manager through a function, extracting an application program object of a current node from each application program, copying the reference of the application program object into a cache, and returning all application program objects to a client after copying the reference of all application programs; the application program attribute comprises an application management component sequence in the domain, and an application program object of the application program in the domain is obtained through the application program attribute, so that the application program is controlled;
implementation of application factory properties: acquiring the number of application program factories in a domain manager, taking out the application program factory objects of the current node from each application program factory, copying the references of the application program factory objects into a cache, and returning each application program factory object to a client after copying the references of all the application program factory objects;
implementation of the file manager attribute: copying the reference of the file management object of the domain manager into an initialized parameter object, returning the copied parameter object, and controlling the file manager by using the file manager attribute;
after each attribute is realized, writing a log record into the log of the domain manager to indicate that the attribute is acquired;
The implementation of the domain manager includes:
creating a file manager in an object realized by the domain manager, initializing the domain manager, activating the domain manager through an activation function, acquiring parameters of the domain manager, starting event services of IDM (Input Domain Manager, domain manager input) and ODM (Output Domain Manager, domain manager output), setting naming services for the domain manager through creating a naming service function, starting a component registration program through a component registration function, acquiring a file of an application program through acquiring an installation file function, installing the application program, deleting an application program configuration file name from the installed application program file through a calling function when the application program needs to be uninstalled, preventing the application program from being automatically reinstalled when the domain manager is restarted, and uninstalling the application program from the domain.
The domain manager provided by the invention has a control function, can control all devices and services in the domain, and the specific implementation process of the functions of installing, uninstalling and registering the domain manager, and also provides a log recording function for tracking access to each attribute and recording event logs 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 SRTF (software radio communications equipment architecture) standards.
Specifically, the implementation of the domain manager profile attribute is to define a checking function and a profile path function for acquiring a profile path of the domain manager, then call the checking function to check whether the domain manager is being closed, if so, the checking function returns the information that the domain manager is being closed, and terminate the subsequent operation; if the domain manager is not closed, judging whether the configuration file path of the domain manager obtained through the configuration file path function is empty, then allocating a memory space matched with the configuration file attribute of the domain manager, judging whether the configuration file attribute of the domain manager is allocated with a non-empty pointer, if not, discarding the exception, if so, copying the configuration file attribute of the domain manager into the allocated memory space, returning the information of the allocated memory space to the client, finally writing a log record into a log of the domain manager to represent that the configuration file attribute of the domain manager is obtained, and then releasing the memory of the log record and returning the sequence of the configuration file attribute of the domain manager.
Specifically, the implementation of the device manager attribute is to acquire a device manager list in a domain manager, then use a mutual exclusion lock to protect the concurrent access device manager list, so as to prevent a plurality of threads from modifying the content in the device manager list at the same time, traverse the device manager list and calculate the total number of the device managers, then call an allocation function to allocate a memory space, use the memory space as a sequence object for packaging all the device managers, set the size of a buffer area of the sequence object according to the number of the device managers, use the memory space as a buffer area of all the device manager sequence objects, traverse the device manager list, copy each device manager as a CORBA object, add the CORBA object into the buffer area, call a function to unlock mutual exclusion variable of the mutual exclusion lock, finally write a log record into a log of the domain manager, record log information of the access device manager attribute into the log of the domain manager, then release the log record memory, return the sequence object, control all the device managers and service through the device manager attribute, and control all the device managers in the domain and all the device manager through the device manager and all the devices in the domain manager and all the nodes.
Specifically, the implementation of the application attribute is to define a function for acquiring all application objects under the domain manager, call the function to allocate memory for storing all application objects, lock the function by a thread to prevent other concurrent operation interference when processing an application list, assign the number of the application programs in the domain manager to a parameter, add the application programs to a buffer, take out the application objects of the current node from the application programs, copy the references of the application program objects to the buffer, unlock the application objects by the thread after copying the references of all application objects, return the application objects to the client, and finally write a log record to a log of the domain manager to indicate that the access application attribute is acquired, wherein the application attribute comprises an application management component sequence in the domain, and obtain the objects of the application programs in the domain by the application attribute, thereby controlling the application programs.
Specifically, the implementation of the application factory attribute is to define a function for acquiring all application factory objects under the domain manager, call the function to allocate and store the memory sizes of all application factory objects, lock the application factory objects by using threads to prevent interference of other concurrent operations when processing the application factory list, assign the number of application factories in the domain manager to a parameter, allocate the memory for the application factory objects and add the application factory objects to a buffer zone, take the application factory object of the current node from the application factory, copy the references of the application factory objects to the buffer zone, unlock the application factory objects by using threads after copying the references of all application factory objects, return the application factory objects to the client, and finally write a log record to the log of the domain manager to indicate that the access application factory attribute is acquired.
Specifically, the implementation of the file manager attribute is to define a function for acquiring the file manager object under the domain manager, call the function to copy the reference of the file manager object of the domain manager into an initialized parameter, if the copy is successful, write a log record into the log of the domain manager to indicate that the file manager attribute is acquired, if the copy fails, throw out the exception, and finally return the parameter obtained by the copy to control the file manager through the file manager attribute.
Specifically, in the implementation of the domain manager, the file manager is created in the object of the domain manager implementation by creating a function of the file manager: distributing an object realized by a file manager, initializing the object, setting a callback function, activating and converting the object into a CORBA object reference, and finally returning the CORBA object reference of the file manager;
initializing a function through a domain manager, including initializing codes and data generated from an interface description file, initializing each component and domain manager configuration description file, initializing each attribute, assigning an initial value to each attribute, and initializing each type of port;
The domain manager is activated by the activation function, a log is recorded firstly, the domain manager is indicated to start to be activated, then the realization object of the domain manager is activated by the activation function is called, the object identifier returned by the realization object is stored in the corresponding field of the domain manager realization structure, and finally the memory of the corresponding field is released and set as NULL;
when acquiring parameters of the domain manager, acquiring object references of the domain manager by using an acquisition domain manager reference function, then converting the input realization object parameters into the object references of the domain manager through the function, and finally returning the object references;
then respectively starting the event services of the IDM and the ODM by starting the event service function: initializing object references and event service channels of the event services of the IDM and the ODM through a function, adding the event services of the IDM and the ODM into a list of registered services of a domain manager through the function, and finally returning the object references of the event services of the IDM and the ODM;
setting naming service for the domain manager by creating naming service function, namely creating a new naming context by analyzing initial reference of the naming service, and binding domain manager object into the naming context;
The component registration program is started through the component registration function, whether the equipment object is empty and valid is judged, and the equipment object which is invalid is unloaded through the unloading function; under the condition that the device object is not empty and effective, loading a software configuration file from a file system according to device information, distributing a memory space for a software package description file variable, analyzing data in the software package description file and storing the result in a software package description file analysis variable, releasing the memory of the software package description file variable, acquiring a device manager where the device object is located, locking a mutual exclusion variable through a locking function, preventing the problem of concurrent access when processing a device manager list, acquiring a device object identifier and a device ID and storing the device identifier and the device ID in corresponding variables, checking whether an interface of the device object realizes a device object interface defined in a SCA (software communication architecture) specification and a SRTF (software radio communication equipment architecture) standard through a function, if so, transmitting the variables storing the device identifier and the device ID into a domain manager device adding function, adding the device object into the domain manager, registering the device manager, and unlocking the mutual exclusion variable through an unlocking function;
The method comprises the steps of firstly obtaining the file name of an application program of an installation domain manager, then analyzing the corresponding application program file and related files, circularly traversing an application program factory list, checking whether a designated application program is installed in a file system, if so, continuing to install the next application program, otherwise, installing the corresponding application program factory for the designated application program, setting related attribute values for the application program factory, and finally adding the application program factory into the application program factory list.
Specifically, in the implementation of the domain manager, an application program is uninstalled from a domain manager configuration file through an uninstalling application function, firstly an application program with a specified identifier is searched, then a calling function deletes an application program configuration file name corresponding to the specified identifier from an installed application program file, the application program is prevented from being automatically reinstalled when the domain manager is restarted, and finally the application program is uninstalled from the domain.
The invention also provides a realization terminal of the domain manager model based on the software communication system structure for the realization method, wherein the domain manager is provided with a domain manager interface, the domain manager interface comprises 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, and the component interface comprises a domain manager configuration file attribute realization module, a device manager attribute realization module, an application program factory attribute realization module, a file manager attribute realization module and a log module which are arranged in parallel. The domain manager is accessible through a domain manager interface;
The domain manager comprises the following steps of sequentially connecting:
the file manager creation module: creating a file manager in an object implemented by the domain manager, and returning a CORBA object reference of the file manager;
domain manager initialization module: initializing a domain manager, including initializing codes and data generated from an interface description file, initializing components and domain manager configuration description files, initializing attributes, assigning an initial value to the attributes, and initializing various ports;
domain manager activation module: activating a domain manager through an activation function, and storing an object identifier returned by the implementation object into a corresponding field of a domain manager implementation structure body;
domain manager parameter acquisition module: acquiring an object reference of the domain manager by using a function for acquiring the reference of the domain manager, converting the input realization object parameters into the object reference of the domain manager through the function, and finally returning the object reference;
event service module: starting event services of the IDM and the ODM, adding the event services of the IDM and the ODM into a list of registered services of a domain manager, and returning object references of the event services of the IDM and the ODM;
domain manager naming module: setting a naming service for a domain manager, and binding a domain manager object into a naming context;
Component registration module: starting a component registration program, adding the device object into a domain manager and registering;
an application program installation module: acquiring a file of an application program to install the application program, and adding an application program factory corresponding to the application program into an application program factory list;
an application program uninstallation module: the application configuration file name is deleted from the installed application file, and the application is uninstalled from the domain.
The invention also provides a terminal comprising a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the implementation method of the domain manager model based on the software communication architecture when executing the computer program.
The beneficial effects of the invention include:
1. the domain manager interface and the construction mode of the domain manager which are completely in accordance with the SCA (software communication architecture) specification and the SRTF (software radio communication equipment architecture) standard are provided, so that the management of the whole domain is greatly facilitated, and the running efficiency of the domain is obviously improved.
2. The access, operation and management of all components in the whole domain are realized, and interfaces for accessing the domain and the components in the domain are provided for a system based on a software communication architecture.
Drawings
FIG. 1 is a flow chart of a method of implementing a domain manager model based on a software communication architecture of the present application.
Fig. 2 is a flow chart of the initialization domain manager of fig. 1.
FIG. 3 is a flow chart of a startup component registration procedure of the domain manager of FIG. 1.
Description of the embodiments
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of 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, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
Example 1:
as shown in fig. 1, the implementation method of the domain manager model based on the software communication architecture of the present application includes the implementation of a domain manager interface and the implementation of a domain manager, and the domain manager is accessed through the domain manager interface, where the domain manager interface is used for configuring and managing devices, services and applications in a domain, and the domain manager is used for managing resources of the whole 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 storing a unique identifier of the component instance, the attributes in the component interface comprising: domain manager profile attributes (domainmanager profiles), device manager attributes (manager), application attributes (applications), application factory attributes (application industries), and file manager attributes (fileMgr); the component instance refers to a separate autonomous functional software module provided with one or more access interfaces. Wherein, the liquid crystal display device comprises a liquid crystal display device,
implementation of domain manager profile attributes: copying the domain manager configuration file attribute of the domain manager object into a newly allocated memory space, and returning the information of the newly allocated memory space to a client;
implementation of device manager properties: preventing concurrent access to the device manager list by a mutex lock, copying each device manager as a CORBA object (common object request broker architecture object), adding the CORBA object to the sequence buffer of the device manager list, and then calling the mutex variable of the function unlock mutex lock; controlling all device managers in the domain through the device manager attribute, and controlling all devices in the domain through the device manager;
Implementation of application attributes: acquiring the number of application programs in a domain manager through a function, extracting an application program object of a current node from each application program, copying the reference of the application program object into a cache, and returning all application program objects to a client after copying the reference of all application programs; the application program attribute comprises an application management component sequence in the domain, and an application program object of the application program in the domain is obtained through the application program attribute, so that the application program is controlled;
implementation of application factory properties: acquiring the number of application program factories in a domain manager, taking out the application program factory objects of the current node from each application program factory, copying the references of the application program factory objects into a cache, and returning each application program factory object to a client after copying the references of all the application program factory objects;
implementation of the file manager attribute: copying the reference of the file management object of the domain manager into an initialized parameter object, returning the copied parameter object, and controlling the file manager by using the file manager attribute;
after each attribute is realized, writing a log record into the log of the domain manager to indicate that the attribute is acquired;
The implementation of the domain manager includes:
creating a file manager in an object realized by the domain manager, initializing the domain manager, activating the domain manager through an activation function, acquiring parameters of the domain manager, starting event services of IDM (Input Domain Manager, domain manager input) and ODM (Output Domain Manager, domain manager output), setting naming services for the domain manager through creating a naming service function, starting a component registration program through a component registration function, acquiring a file of an application program through acquiring an installation file function, installing the application program, deleting an application program configuration file name from the installed application program file through a calling function when the application program needs to be uninstalled, preventing the application program from being automatically reinstalled when the domain manager is restarted, and uninstalling the application program from the domain.
The domain manager provided by the invention has a control function, can control all devices and services in the domain, and the specific implementation process of the functions of installing, uninstalling and registering the domain manager, and also provides a log recording function for tracking access to each attribute and recording event logs 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 SRTF (software radio communications equipment architecture) standards.
Example 2:
on the basis of embodiment 1, the implementation of the domain manager profile attribute is to define a checking function and a profile path function for acquiring a profile path of the domain manager, then call the checking function to check whether the domain manager is closing, if closing, the checking function returns the information that the domain manager is closing, and terminate the subsequent operation; if the domain manager is not closed, judging whether the configuration file path of the domain manager obtained through the configuration file path function is empty, then allocating a memory space matched with the configuration file attribute of the domain manager, judging whether the configuration file attribute of the domain manager is allocated with a non-empty pointer, if not, discarding the exception, if so, copying the configuration file attribute of the domain manager into the allocated memory space, returning the information of the allocated memory space to the client, finally writing a log record into a log of the domain manager to represent that the configuration file attribute of the domain manager is obtained, and then releasing the memory of the log record and returning the sequence of the configuration file attribute of the domain manager.
Example 3:
based on embodiment 1, the implementation of the device manager attribute is that firstly, a device manager list in a domain manager is obtained, then a mutual exclusion lock is used to protect the concurrent access device manager list, so as to prevent a plurality of threads from modifying the content in the device manager list at the same time, then the device manager list is traversed, the total number of the device managers is calculated, then an allocation function is called to allocate a memory space, the memory space is used as a sequence object for packaging all the device managers, the buffer area size of the sequence object is set according to the number of the device managers, the buffer area size is used as a buffer area of all the device manager sequence objects, then the device manager list is traversed, each device manager is copied into a CORBA object, the CORBA object is added into the buffer area, then a function is called to unlock the mutual exclusion variable of the mutual exclusion lock, finally a log record is written into the log of the domain manager, log information of the access device manager attribute is recorded into the log of the domain manager, then the log record memory is released, the sequence object is returned, all the device managers in the domain are controlled by the device manager attribute, and all the devices in the domain are controlled by the device manager and all the nodes in the domain and all the devices are controlled by the nodes.
Example 4:
on the basis of embodiment 1, the implementation of the application attribute is to define a function for acquiring all application objects under the domain manager, call the function to allocate memory for storing all application objects, lock the application objects by threads to prevent interference of other concurrent operations when processing the application list, assign the number of the application programs in the domain manager to a parameter, add the application programs to a buffer, take the application objects of the current node from the application programs, copy the references of the application objects to the buffer, unlock the application objects by threads after copying the references of all application objects, return the application objects to the client, and finally write a log record to the log of the domain manager to indicate that the application attribute is acquired, wherein the application attribute comprises an application management component sequence in the domain, and the application objects in the domain are obtained by the application attribute, thereby controlling the application programs.
Example 5:
on the basis of embodiment 1, the implementation of the application factory attribute is to define a function for acquiring all application factory objects under the domain manager, call the function to allocate and store the memory sizes of all application factory objects, lock the application factory objects by using threads to prevent interference of other concurrent operations when processing the application factory list, assign the number of application factories in the domain manager to a parameter, allocate memory for the application factory objects and add the application factory objects to a buffer, take the application factory object of the current node from the application factory, copy the reference of the application factory object to the buffer, unlock the application factory object by using the threads after copying the reference of all application factory objects, return the application factory object to the client, and finally write a log record into a log of the domain manager to indicate that the access to the application factory attribute is acquired.
Example 6:
on the basis of embodiment 1, the implementation of the file manager attribute is to define a function for acquiring the file manager object under the domain manager, call the function to copy the reference of the file manager object of the domain manager into an initialized parameter, if the copying is successful, write a log record into the log of the domain manager to indicate that the access file manager attribute is acquired, if the copying fails, throw out the exception, and finally return the parameter obtained by the copying to control the file manager through the file manager attribute.
Example 7:
on the basis of embodiment 1, in the implementation of the domain manager, creating a file manager in an object of the domain manager implementation by creating a function of the file manager: distributing an object realized by a file manager, initializing the object, setting a callback function, activating and converting the object into a CORBA object reference, and finally returning the CORBA object reference of the file manager;
the domain manager is then initialized by a domain manager initialization function, as shown in FIG. 2, including initializing code and data generated from interface description files, such as CosNamine. Idl and CF. Idl. Then initializing each component, such as the creation and the number of application factories, the creation and the number of application programs, the creation of a device manager, the creation and the number of device objects, the creation of services and the like; initializing a domain manager configuration description file (DMD), firstly creating a file system to read the domain manager configuration description file, then analyzing the domain manager configuration description file through a DMD analysis function, transmitting an analysis result to a parameter, judging whether the parameter is empty or not, releasing the parameter if the parameter is not empty, and simultaneously releasing file system resources; initializing each attribute, assigning an initial value to each attribute, and finally initializing various ports such as a device manager registration port, an installation port, a time channel port and the like in the domain;
Activating a domain manager through an activation function, firstly recording a log by using a CF_DEBUG0 macro to indicate that the domain manager starts to activate, then calling an implementation object of the activation function to activate the domain manager, storing an object identifier returned by the implementation object into a corresponding field of an implementation structure of the domain manager, and finally releasing the memory of the corresponding field and setting the memory as NULL;
when acquiring parameters of the domain manager, acquiring object references of the domain manager by using an acquisition domain manager reference function, then converting the input implementation object parameters into the object references of the domain manager through the function, checking whether the object references are empty or not, and returning the object references if the object references are not empty;
then respectively starting the event services of the IDM and the ODM by starting the event service function: initializing object references and event service channels of event services of the IDM and the ODM through a function, respectively adding IDM_channel services and ODM_channel services corresponding to the event services of the IDM and the ODM into a list of registered services of a domain manager through the function, and finally returning the object references of the IDM_channel services and the ODM_channel services;
setting naming service for the domain manager by creating naming service function, namely creating a new naming context by analyzing initial reference of the naming service, and binding domain manager object into the naming context;
The component registration program is started through the component registration function, as shown in fig. 3, whether the equipment object is empty or not is judged first, if the equipment object is empty, the abnormality is thrown out, and if the equipment object is invalid, the invalid equipment object is unloaded through the unloading function; under the condition that the device object is not empty and effective, acquiring information such as a label, a software configuration file path and a device ID of the device through a device management interface, loading the software configuration file from a file system, calculating a memory space required for analyzing a software package description file (SPD), distributing a memory space for a software package description file variable, analyzing data in the software package description file through an SPD analysis function and storing the result in a software package description file analysis variable, releasing a memory of the software package description file variable, acquiring a device manager where the device object is located, locking a mutual exclusion variable through a locking function to prevent the problem of concurrent access when processing a list of the device manager, acquiring a device object identifier and the device ID, storing the device object identifier in corresponding variables, checking whether the device object interface realizes a SCA (software communication architecture) specification and a SRTF (software radio communication equipment architecture) standard, if so, transferring the variable storing the device identifier and the device ID to a domain manager device adding function, adding the device object to the domain manager and registering the device object, and then unlocking the device object, calling the device object by the unlocking function, and releasing the error log when the current register fails, and recording the device is failed to release the corresponding error log according to the failure types when the current register is used, and the error log is not failed to be recorded;
The application program installation is carried out by acquiring the file of the installation file function acquisition application program, namely the file of the installation file function acquisition application program is acquired, and the name of the file (namely the SAD file) for storing the installation application program is searched; the application program is installed by installing the application function, namely, firstly, the application program file name of the installation domain manager is acquired, an allocation function is called to allocate storage space for the application program file name and store the SAD file in the storage space, then, whether the file exists or not is checked, a corresponding application program file and related files are analyzed, an application program factory list is circularly traversed, whether a designated application program is installed in a file system or not is checked, if the designated application program is installed, the next application program is continuously installed, otherwise, a corresponding application program factory is installed for the designated application program, related attribute values such as an application program factory name and identifier, a software configuration file and the like are set for the application program factory, and finally, the application program factory is added into the application program factory list.
Example 8:
on the basis of the above embodiment, in the implementation of the domain manager, the application program is uninstalled from the domain manager configuration file through the uninstalling application function, firstly, the application program with the specified identifier is searched, then the calling function deletes the application program configuration file name corresponding to the specified identifier from the installed application program file, the application program is prevented from being automatically reinstalled when the domain manager is restarted, and finally, the application program is uninstalled from the domain.
Example 9:
the invention also provides an implementation terminal of the domain manager model based on the software communication system structure for the implementation method embodiment, wherein a domain manager interface is arranged in the domain manager, the domain manager interface comprises a component identifier interface and a component interface corresponding to each component instance, a storage space for storing the unique identifier of the component instance is arranged in the component identifier interface, and the component interface comprises a domain manager configuration file attribute implementation module, a device manager attribute implementation module, an application program factory attribute implementation module, a file manager attribute implementation module and a log module which are arranged in parallel.
Example 10:
on the basis of embodiment 9, the domain manager includes sequentially connected:
the file manager creation module: creating a file manager in an object implemented by the domain manager, and returning a CORBA object reference of the file manager;
domain manager initialization module: initializing a domain manager, including initializing codes and data generated from an interface description file, initializing components and domain manager configuration description files, initializing attributes, assigning an initial value to the attributes, and initializing various ports;
Domain manager activation module: activating a domain manager through an activation function, and storing an object identifier returned by the implementation object into a corresponding field of a domain manager implementation structure body;
domain manager parameter acquisition module: acquiring an object reference of the domain manager by using a function for acquiring the reference of the domain manager, converting the input realization object parameters into the object reference of the domain manager through the function, and finally returning the object reference;
event service module: starting event services of the IDM and the ODM, adding the event services of the IDM and the ODM into a list of registered services of a domain manager, and returning object references of the event services of the IDM and the ODM;
domain manager naming module: setting a naming service for a domain manager, and binding a domain manager object into a naming context;
component registration module: starting a component registration program, adding the device object into a domain manager and registering;
an application program installation module: acquiring a file of an application program to install the application program, and adding an application program factory corresponding to the application program into an application program factory list;
an application program uninstallation module: the application configuration file name is deleted from the installed application file, and the application is uninstalled from the domain.
Example 11:
on the basis of the above embodiment, the present application further provides a terminal, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor executes the implementation method of the domain manager model based on the software communication architecture in the above embodiment when executing the computer program.
The above examples merely illustrate specific embodiments of the application, which are described in more detail and are not to be construed as limiting the scope of the application. It should be noted that, for those skilled in the art, it is possible to make related modifications and improvements without departing from the technical idea of the application, which fall within the protection scope of the application.
Claims (10)
1. The method for realizing the domain manager model based on the software communication system structure is characterized by comprising the following steps: the method comprises the implementation of a domain manager interface and the implementation of a domain manager, wherein the domain manager is accessed through the domain manager interface, the domain manager interface is used for configuring and managing devices, services and applications in a domain, and the domain manager is used for managing resources of the whole 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 storing a unique identifier of the component instance, the attributes in the component interface comprising: domain manager configuration file attributes, device manager attributes, application factory attributes, and file manager attributes; wherein, the liquid crystal display device comprises a liquid crystal display device,
implementation of domain manager profile attributes: copying the domain manager configuration file attribute of the domain manager object into a newly allocated memory space, and returning the information of the newly allocated memory space to a client;
implementation of device manager properties: preventing concurrent access to the device manager list by the mutex lock, copying each device manager as a CORBA object, adding the CORBA object to a sequence buffer of the device manager list, and then calling a function to unlock the mutex variable of the mutex lock; controlling all device managers in the domain through the device manager attribute, and controlling all devices in the domain through the device manager;
implementation of application attributes: acquiring the number of application programs in a domain manager through a function, extracting an application program object of a current node from each application program, copying the reference of the application program object into a cache, and returning all application program objects to a client after copying the reference of all application programs; the application program attribute comprises an application management component sequence in the domain, and an application program object of the application program in the domain is obtained through the application program attribute, so that the application program is controlled;
Implementation of application factory properties: acquiring the number of application program factories in a domain manager, taking out the application program factory objects of the current node from each application program factory, copying the references of the application program factory objects into a cache, and returning each application program factory object to a client after copying the references of all the application program factory objects;
implementation of the file manager attribute: copying the reference of the file management object of the domain manager into an initialized parameter object, returning the copied parameter object, and controlling the file manager by using the file manager attribute;
after each attribute is realized, writing a log record into the log of the domain manager to indicate that the attribute is acquired;
the implementation of the domain manager includes:
creating a file manager in an object realized by a domain manager, initializing the domain manager, activating the domain manager through an activation function, acquiring parameters of the domain manager, starting event services of the IDM and the ODM, setting naming services for the domain manager through creating a naming service function, starting a component registration program through a component registration function, acquiring a file of an application program through acquiring an installation file function, installing the application program, deleting an application program configuration file name from the installed application program file by a calling function when the application program needs to be uninstalled, preventing the application program from being automatically reinstalled when the domain manager is restarted, and uninstalling the application program from the domain.
2. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: the implementation of the domain manager profile attribute is to define a checking function and a profile path function for acquiring the profile path of the domain manager, then call the checking function to check whether the domain manager is closing, if so, the checking function returns the information that the domain manager is closing, and terminate the subsequent operation; if the domain manager is not closed, judging whether the configuration file path of the domain manager obtained through the configuration file path function is empty, then allocating a memory space matched with the configuration file attribute of the domain manager, judging whether the configuration file attribute of the domain manager is allocated with a non-empty pointer, if not, discarding the exception, if so, copying the configuration file attribute of the domain manager into the allocated memory space, returning the information of the allocated memory space to the client, finally writing a log record into a log of the domain manager to represent that the configuration file attribute of the domain manager is obtained, and then releasing the memory of the log record and returning the sequence of the configuration file attribute of the domain manager.
3. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: the implementation of the device manager attribute is to acquire a device manager list in a domain manager, then use a mutual exclusion lock to protect the concurrent access device manager list, so as to prevent a plurality of threads from modifying the content in the device manager list at the same time, traverse the device manager list and calculate the total number of the device managers, then call an allocation function to allocate a memory space, use the memory space as a sequence object for packaging all the device managers, set the size of a buffer area of the sequence object according to the number of the device managers, use the memory space as the buffer area of all the device manager sequence objects, traverse the device manager list, copy each device manager as a CORBA object, add the CORBA object into the buffer area, call a mutual exclusion variable of the mutual exclusion lock, finally write a log record into a log of the domain manager, record log information of the access device manager attribute into the domain manager, then release the log record memory and return the sequence object, control all the device managers in the domain through the device manager attribute, and service nodes in the domain through the device manager, and all the device manager are controlled through the device manager and all the device manager nodes in the domain.
4. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: the implementation of the application program attribute is to define a function for acquiring all application program objects under a domain manager, call the function to allocate memory for storing all application program objects, lock the function by a thread to prevent other concurrent operation interference when processing an application program list, assign the number of application programs in the domain manager to a parameter, add the application programs to a buffer, take out the application program object of a current node from the application programs, copy the reference of the application program object to the buffer, unlock the application program object by the thread after copying the reference of all application program objects, return the application program object to a client, write a log record into a log of the domain manager to indicate that the access application program attribute is acquired, the application program attribute comprises an application management component sequence in a domain, and obtain the object of the application program in the domain by the application program attribute, thereby controlling the application program.
5. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: the implementation of the application program factory attribute is to define a function for acquiring all application program factory objects under a domain manager, call the function to allocate and store the memory size of all application program factory objects, lock the application program factory objects by using threads to prevent other concurrent operation interference when processing an application program factory list, assign the number of application program factories in the domain manager to a parameter, allocate the memory for the application program factory objects, add the application program factory objects into a buffer zone, take out the application program factory objects of the current node from the application program factory, copy the references of the application program factory objects into the buffer zone, unlock the application program factory objects by using threads after copying the references of all application program factory objects, return the application program factory objects to a client, and finally write a log record into a log of the domain manager to indicate that the access application program factory attribute is acquired.
6. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: the realization of the file manager attribute is to define a function for acquiring the file manager object under the domain manager, call the function to copy the reference of the file manager object of the domain manager into an initialized parameter, if the copying is successful, write a log record into the log of the domain manager to indicate that the access file manager attribute is acquired, if the copying is failed, throw out the abnormality, and finally return the parameter obtained by the copying to control the file manager through the file manager attribute.
7. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: in an implementation of the domain manager, creating a file manager in an object of the domain manager implementation by creating a function of the file manager: distributing an object realized by a file manager, initializing the object, setting a callback function, activating and converting the object into a CORBA object reference, and finally returning the CORBA object reference of the file manager;
Initializing a function through a domain manager, including initializing codes and data generated from an interface description file, initializing each component and domain manager configuration description file, initializing each attribute, assigning an initial value to each attribute, and initializing each type of port;
the domain manager is activated by the activation function, a log is recorded firstly, the domain manager is indicated to start to be activated, then the realization object of the domain manager is activated by the activation function is called, the object identifier returned by the realization object is stored in the corresponding field of the domain manager realization structure, and finally the memory of the corresponding field is released and set as NULL;
when acquiring parameters of the domain manager, acquiring object references of the domain manager by using an acquisition domain manager reference function, then converting the input realization object parameters into the object references of the domain manager through the function, and finally returning the object references;
then respectively starting the event services of the IDM and the ODM by starting the event service function: initializing object references and event service channels of the event services of the IDM and the ODM through a function, adding the event services of the IDM and the ODM into a list of registered services of a domain manager through the function, and finally returning the object references of the event services of the IDM and the ODM;
Setting naming service for the domain manager by creating naming service function, namely creating a new naming context by analyzing initial reference of the naming service, and binding domain manager object into the naming context;
the component registration program is started through the component registration function, whether the equipment object is empty and valid is judged, and the equipment object which is invalid is unloaded through the unloading function; under the condition that the device object is not empty and effective, loading a software configuration file from a file system according to device information, distributing a memory space for a software package description file variable, analyzing data in the software package description file and storing the result in a software package description file analysis variable, releasing a memory of the software package description file variable, acquiring a device manager where the device object is located, locking a mutual exclusion variable through a locking function to prevent the problem of concurrent access when processing a device manager list, acquiring a device object identifier and a device ID and storing the device object identifier and the device ID in corresponding variables, checking whether an interface of the device object realizes a device object interface defined in an SCA specification and an SRTF standard through a function, if so, transmitting the variables storing the device identifier and the device ID to a domain manager device adding function, adding the device object to the domain manager and registering, and unlocking the mutual exclusion variable through an unlocking function;
The method comprises the steps of firstly obtaining the file name of an application program of an installation domain manager, then analyzing the corresponding application program file and related files, circularly traversing an application program factory list, checking whether a designated application program is installed in a file system, if so, continuing to install the next application program, otherwise, installing the corresponding application program factory for the designated application program, setting related attribute values for the application program factory, and finally adding the application program factory into the application program factory list.
8. The method for implementing a domain manager model based on a software communication architecture as recited in claim 1, wherein: in the implementation of the domain manager, an application program is uninstalled from a domain manager configuration file through an uninstalling application function, an application program with a specified identifier is firstly searched, then an application program configuration file name corresponding to the specified identifier is deleted from an installed application program file by a calling function, the application program is prevented from being automatically reinstalled when the domain manager is restarted, and finally the application program is uninstalled from the domain.
9. Implementation terminal of a domain manager model based on a software communication architecture for implementing the method according to one of claims 1 to 8, characterized in that: a domain manager interface is arranged in the domain manager, the domain manager interface comprises a component identifier interface and a component interface corresponding to each component instance, a storage space for storing the unique identifier of the component instance is arranged in the component identifier interface, and the component interface comprises a domain manager configuration file attribute realizing module, a device manager attribute realizing module, an application program factory attribute realizing module, a file manager attribute realizing module and a log module which are arranged in parallel;
the domain manager comprises the following steps of sequentially connecting:
the file manager creation module: creating a file manager in an object implemented by the domain manager, and returning a CORBA object reference of the file manager;
domain manager initialization module: initializing a domain manager, including initializing codes and data generated from an interface description file, initializing components and domain manager configuration description files, initializing attributes, assigning an initial value to the attributes, and initializing various ports;
Domain manager activation module: activating a domain manager through an activation function, and storing an object identifier returned by the implementation object into a corresponding field of a domain manager implementation structure body;
domain manager parameter acquisition module: acquiring an object reference of the domain manager by using a function for acquiring the reference of the domain manager, converting the input realization object parameters into the object reference of the domain manager through the function, and finally returning the object reference;
event service module: starting event services of the IDM and the ODM, adding the event services of the IDM and the ODM into a list of registered services of a domain manager, and returning object references of the event services of the IDM and the ODM;
domain manager naming module: setting a naming service for a domain manager, and binding a domain manager object into a naming context;
component registration module: starting a component registration program, adding the device object into a domain manager and registering;
an application program installation module: acquiring a file of an application program to install the application program, and adding an application program factory corresponding to the application program into an application program factory list;
an application program uninstallation module: the application configuration file name is deleted from the installed application file, and the application is uninstalled 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 by: which processor, when executing the computer program, carries out the implementation method of one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310861042.3A CN116614388B (en) | 2023-07-14 | 2023-07-14 | Method and terminal for realizing domain manager model based on software communication system structure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310861042.3A CN116614388B (en) | 2023-07-14 | 2023-07-14 | Method and terminal for realizing domain manager model based on software communication system structure |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116614388A CN116614388A (en) | 2023-08-18 |
| CN116614388B true CN116614388B (en) | 2023-09-22 |
Family
ID=87680338
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310861042.3A Active CN116614388B (en) | 2023-07-14 | 2023-07-14 | Method and terminal for realizing domain manager model based on software communication system structure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116614388B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117579458B (en) * | 2024-01-17 | 2024-04-23 | 成都谐盈科技有限公司 | Data transmission method based on software communication system structure |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104090810A (en) * | 2014-07-29 | 2014-10-08 | 中国航空无线电电子研究所 | Core framework integration method based on software communication system architecture |
| CN108847852A (en) * | 2018-06-08 | 2018-11-20 | 中国人民解放军国防科技大学 | SCA-based domain configuration file parser and use method thereof |
| CN109254757A (en) * | 2018-07-17 | 2019-01-22 | 中国航空无线电电子研究所 | The software communications architecture of double-core frame |
| CN109324912A (en) * | 2018-09-21 | 2019-02-12 | 中国航空无线电电子研究所 | The communication means of the application management class software of software-oriented communication architecture |
| CN111447079A (en) * | 2020-02-28 | 2020-07-24 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | High-availability extension system and method based on SCA framework |
| CN113312245A (en) * | 2021-05-28 | 2021-08-27 | 成都谐盈科技有限公司 | Integrated waveform management terminal and management method |
| CN116248629A (en) * | 2023-03-13 | 2023-06-09 | 中国人民解放军国防科技大学 | Registration optimization method for SCA equipment component |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100903999B1 (en) * | 2007-11-30 | 2009-06-22 | 한국전자통신연구원 | System and method for operating domain profile using database in a core framework for SDR mobile terminals |
-
2023
- 2023-07-14 CN CN202310861042.3A patent/CN116614388B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104090810A (en) * | 2014-07-29 | 2014-10-08 | 中国航空无线电电子研究所 | Core framework integration method based on software communication system architecture |
| CN108847852A (en) * | 2018-06-08 | 2018-11-20 | 中国人民解放军国防科技大学 | SCA-based domain configuration file parser and use method thereof |
| CN109254757A (en) * | 2018-07-17 | 2019-01-22 | 中国航空无线电电子研究所 | The software communications architecture of double-core frame |
| CN109324912A (en) * | 2018-09-21 | 2019-02-12 | 中国航空无线电电子研究所 | The communication means of the application management class software of software-oriented communication architecture |
| CN111447079A (en) * | 2020-02-28 | 2020-07-24 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | High-availability extension system and method based on SCA framework |
| CN113312245A (en) * | 2021-05-28 | 2021-08-27 | 成都谐盈科技有限公司 | Integrated waveform management terminal and management method |
| CN116248629A (en) * | 2023-03-13 | 2023-06-09 | 中国人民解放军国防科技大学 | Registration optimization method for SCA equipment component |
Non-Patent Citations (2)
| Title |
|---|
| 基于SCA架构的信息处理模块设计;吕浩;中国新通信(第11期);168-170 * |
| 基于SCA的多协议终端软件体系架构的研究与设计;裴文钰;《中国优秀硕士学位论文全文数据库》;I136-1210 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116614388A (en) | 2023-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4297790B2 (en) | Persistent key-value repository with pluggable architecture abstracting physical storage | |
| US7698390B1 (en) | Pluggable device specific components and interfaces supported by cluster devices and systems and methods for implementing the same | |
| EP0573190B1 (en) | Dynamically configurable kernel | |
| US7203774B1 (en) | Bus specific device enumeration system and method | |
| US6393474B1 (en) | Dynamic policy management apparatus and method using active network devices | |
| CN116614388B (en) | Method and terminal for realizing domain manager model based on software communication system structure | |
| US6269442B1 (en) | Apparatus and method for on-line replacement of a running program code and data using checkpoints | |
| CN110597531B (en) | Distributed module upgrading method and device and storage medium | |
| EP1437657A2 (en) | System and method for management of software applications | |
| KR100903999B1 (en) | System and method for operating domain profile using database in a core framework for SDR mobile terminals | |
| US7937713B2 (en) | System and method for providing services on a distributed network | |
| WO2001016730A2 (en) | FIXING INCOMPATIBLE APPLICATIONS BY PROVIDING STUBS FOR APIs | |
| CN107220074B (en) | Method and device for accessing and upgrading supporting layer software function | |
| CN112463303A (en) | JAVA virtual machine class loading method and system | |
| CN113703859A (en) | Dynamic link library injection method, device, equipment and storage medium | |
| CN116541184A (en) | Multi-protocol application framework system | |
| CN111752635A (en) | Application program running method and device, computer equipment and storage medium | |
| CN110083378B (en) | Automatic software upgrading method and device based on file system | |
| WO2019162829A1 (en) | Fast recovery from failures in a chronologically ordered log-structured key-value storage system | |
| US20190332370A1 (en) | Storage reserve in a file system | |
| US20210373905A1 (en) | Systems and methods for cloud-centric operating system deployment through service operating system | |
| CN115543224B (en) | ZNS SSD-based file system control method, device and equipment | |
| CN112130900B (en) | User information management method, system, equipment and medium for BMC | |
| KR100554521B1 (en) | storage medium for descriptor file architecture based on SCA system and file parsing method thereof | |
| CN116382713A (en) | Method, system, device and storage medium for constructing application mirror image |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |