CN116248629A - Registration optimization method for SCA equipment component - Google Patents
Registration optimization method for SCA equipment component Download PDFInfo
- Publication number
- CN116248629A CN116248629A CN202310245708.2A CN202310245708A CN116248629A CN 116248629 A CN116248629 A CN 116248629A CN 202310245708 A CN202310245708 A CN 202310245708A CN 116248629 A CN116248629 A CN 116248629A
- Authority
- CN
- China
- Prior art keywords
- component
- registration
- manager component
- domain manager
- sca
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
- H04L61/302—Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/005—Multiple registrations, e.g. multihoming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5018—Thread allocation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a registration optimization method of SCA equipment components, which belongs to the technical field of wireless communication and is mainly used for SCA software platform optimization, so that a unified registrar interface is used and maintained globally by a software platform, and the effects of simplifying registration connection relation, accelerating software platform starting speed and improving platform robustness are achieved. The equipment component optimization method comprises the following steps: and combining the register interfaces of the domain manager, the device manager and the application manager, only reserving the register interfaces of the domain manager, directly registering with the domain manager after the device component is started, and informing the domain manager of the registration information of the related device components of the device manager. The method and the device simplify the combination of the register interfaces of the SCA software platform, globally maintain and manage a unified register interface, and the device components directly register with the domain manager instead of registering step by step, so that the registration connection relationship can be simplified, the starting speed of the platform can be effectively improved, and the robustness of the software platform can be improved.
Description
Technical Field
The application relates to the technical field of wireless communication, in particular to a registration optimization method of a SCA device assembly.
Background
The Software Communications Architecture (SCA) is a design development standard for software radio equipment that plays an important role in the development of global software radio systems in terms of technological guidance and unification of development environment standards.
However, there are also problems in the related art: the registration of the components in the standard adopts a step-by-step registration mode, a plurality of registries exist globally, the domain manager component, the equipment manager component and the application factory component all need to maintain the respective registries, the resource waste is caused, and the complexity of the software codes is increased. After all the equipment components are required to be started and registered step by step, the platform waveform side can be used, and the starting waiting time is long. After the device manager component is started, all subordinate device components need to wait for starting and finishing registration, the device manager component can register with the domain manager component, and after all registration processes are finished, the platform waveform party can deploy and start. Registration parameter structures are complex. When the device component registers with the device manager component, the registration parameters only need to contain the information of the device component, and when the device manager component registers with the domain manager component, the device manager component and all subordinate device components thereof need to be carried, and the registration parameters are defined by considering two cases at the same time, so that the structure is complex. If a certain device component fails to start, the device manager component cannot register to the domain manager component, and other successfully started devices cannot be used, so that the use of the whole software platform is affected. When the software platform is used, the query relationship is complex and the efficiency is low when the specific resource condition of a certain equipment component needs to be queried. Because the software platform is provided with a plurality of registries, the registries respectively maintain the registration component information of the registries and are mutually related, when a user needs to inquire the information of a certain equipment component, the information of the equipment manager component to which the specified equipment component belongs needs to be inquired from the domain manager component, and then the information of the specified equipment component is inquired from the equipment manager component, so that the inquiry process is complex and the efficiency is lower.
Disclosure of Invention
The main purpose of the application is to provide a registration optimization method of SCA equipment components, so as to solve the problems of complex registration method and registration relationship of SCA equipment components, long time consumption and low efficiency in the prior art.
To achieve the above object, according to one aspect of the present application, there is provided a registration optimization method of a SCA device component.
The registration optimization method of the SCA equipment assembly comprises the following registration steps:
s1: the domain manager component starts up, publishes its registrar interface, and waits for the component to register;
s2: after the device manager component is started, acquiring a domain manager component register interface;
s3: the device manager component registers with the domain manager component;
s4: the device manager component starts each device component under the jurisdiction one by one;
s5: the equipment component is started successfully, and a domain manager component register interface is acquired;
s6: the device component registers with the domain manager component directly, and the registration parameters contain device component information;
s7: after the domain manager component receives the registration of a certain device component, a registration information notification function of the device manager component is called to notify the device manager component that the registration of a subordinate device component is successful;
s8: and if the equipment component is started to fail, ending the equipment component registration flow.
Further, the domain manager component and the device manager component are both disposed on the SCA software platform.
Further, the SCA software platform globally uses only one unified registrar interface maintained, which is implemented in the same process as the domain manager component.
Further, the device manager component and the domain manager component operate at the same address or at different addresses respectively, and each component communicates through CORBA.
Further, the registrar interface is implemented and maintained by a domain manager component with which all components in the platform register directly.
Further, the registrar interface manages the status and information of all registered components, and provides a registration function for registration of each component, where the registration parameters of the registration function are structures describing the information of each registered component.
Further, the device manager component adds a registration information notification function when implementing, after the subordinate device component registers successfully with the register interface of the domain manager component, the domain manager component notifies the device manager component that the subordinate device component is started and registers successfully by calling the registration information notification function, and meanwhile, the information of the device component is transmitted to the device manager component as the parameter of the registration information notification function.
Further, after the device manager component and the device components under the device manager component are started, the register interface object of the domain manager component is obtained through the Registry IOR.
Further, the device manager component manages two device components, namely, a GPP device component and an audio device component.
Further, the device manager component starts the device components GPP device components and the audio device components one by one in a thread mode.
The application has the advantages that: compared with a step-by-step registration mode in the standard, the method omits a register interface of the equipment manager component, only reserves the register interface of the domain manager component, globally only needs to maintain one component register interface, simplifies the registration relationship and flow, saves system resources and reduces the code complexity.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, are included to provide a further understanding of the application and to provide a further understanding of the application with regard to the other features, objects and advantages of the application. The drawings of the illustrative embodiments of the present application and their descriptions are for the purpose of illustrating the present application and are not to be construed as unduly limiting the present application. In the drawings:
FIG. 1 is a schematic illustration of a registration flow of a device component according to one embodiment of the present application;
FIG. 2 is a diagram of registered connections of equipment components in the SCA standard according to the related art;
FIG. 3 is a flowchart of registration of device components in the SCA standard according to the related art;
FIG. 4 is a schematic diagram of registered connectivity of a device component according to one embodiment of the present application;
fig. 5 is a specific registration flow diagram of a device component according to one embodiment of the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the present application described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Referring to fig. 1, the method for optimizing registration of an SCA device component according to an embodiment of the present application can optimize a process of registration of the device component in a use process of an SCA software platform, and includes the following steps:
s1: the domain manager component starts up, publishes its registrar interface, and waits for the component to register;
s2: after the device manager component is started, acquiring a domain manager component register interface;
s3: the device manager component registers with the domain manager component;
s4: the device manager component manages each device component one by starting the device;
s5: the equipment component is started successfully, and a domain manager component register interface is acquired;
s6: the device component registers with the domain manager component directly, and the registration parameters contain device component information;
s7: after the domain manager component receives the registration of a certain device component, a registration information notification function of the device manager component is called to notify the device manager component that the registration of a subordinate device component is successful;
s8: and if the equipment component is started to fail, ending the equipment component registration flow.
Wherein, the domain manager component and the device manager component are both arranged on the SCA software platform.
In the existing SCA4.1 standard, both the domain manager component and the device manager component provide a registrar interface, the registration connection of which is shown in fig. 2. As can be seen from fig. 2, in the existing standard, the device component registration adopts a step-by-step registration mode, each device manager component manages a plurality of device components, when the device manager starts to operate, the devices operate one by one, after the device starts successfully, the devices want to register, and after all the devices register, the device manager component carries all the device component information under jurisdiction to register to the domain manager component.
Fig. 3 shows a device component registration procedure defined by the existing SCA4.1 standard, which specifically includes the following steps:
(1) The device manager component starts;
(2) The device manager starts the subordinate device components one by one;
(3) The device manager component waits for registration of subordinate device components;
(4) The equipment component is successfully started, a registrar interface of the equipment manager component is obtained through the input starting parameters or configuration management files, registration is carried out on the equipment manager component, and relevant information of the equipment component is used as registration parameters to be transmitted to the equipment manager component;
(5) After the equipment manager component starts up and completes registration, the equipment manager component registers with the domain manager component, and the information of the equipment manager component and the subordinate equipment components thereof are used as registration parameters to be transmitted to the domain manager component;
(6) If the equipment component fails to be started, the equipment component registration flow is ended, and the equipment manager component fails to be started.
As can be seen from the above registration connection relationship and registration flow, the components in the SCA4.1 standard are registered step by step, and the domain manager component and the device manager component are respectively provided with a register interface, which also needs to be maintained at the same time, thus wasting resources very easily.
According to the method for optimizing registration of the SCA device component in the embodiment of the application, referring to the registration connection relation of FIG. 3, the device manager component no longer provides and maintains a registrar interface, only the domain manager component provides and maintains a registrar interface on the whole platform, the device component directly registers with the domain manager component, and after the registration is completed, the domain manager component informs the appointed device manager component that the subordinate device component is started and successfully registered.
In a specific embodiment, the SCA software platform comprises a Domain manager component, a device manager component. The device manager component manages two device components, namely a GPPDevic component and an audio device component AudioDeviceComponent, GPP, which are two device components implemented by a platform. The platform global maintains only one register interface ComponentRegistry, the register interface and the domain manager component are realized in the same process, the device manager component can operate at the same address with the domain manager component, can be distributed deployment, respectively operates at different addresses, and each component communicates through CORBA. The registrar interface object of the domain manager component can be obtained through a specified Registry IOR. Further, the registry interface ComponentRegistry is responsible for maintaining and managing the status and information of all the registered components, and providing registerComponent (ComponentType) functions for registration of each component, wherein the registration parameter ComponentType is a structure for describing information of each registered component, each registered component can fill out component identifier, component basic description information profile, component type, registered component object componentObject, provided port providsports, other attribute information specialzedbfo, and the like, when registering, wherein identifier, profile, type and componentObject are necessary contents. The device manager component adds a registration information notification function registryInfo (ComponentType) when implementing, and after receiving the registration information of the device component, the domain manager component notifies the device manager component that its subordinate device component has been successfully started and registered by calling the function, and obtains the information of the device component through the ComponentType parameter.
Referring to fig. 5 in combination with the above, the specific registration implementation steps are as follows:
(1) The domain manager component domainmannangercomponent starts, and the registrar interface waits for registration of each component;
(2) The device manager component is started, and a register interface object component Registry of the domain manager component is obtained through a Registry IOR;
(3) The device manager component calls a register component function of a register interface object to register with the domain manager component, and fills information of the device manager component into a ComponentType structure body, wherein the information comprises a device manager component identifier, basic information describing profile, component type and self object componentObject, and the basic information is used as registration parameters to be transmitted to the domain manager component;
(4) The device manager component starts the device components GPPDevicComponent and AudioDeviceComponent one by one in a thread mode;
(5) After the GPPDeviceCommonent component is started, acquiring a registrar interface object component Registry of the domain manager component through a Registry IOR;
(6) The GPPDevicComponent component calls a register component function of a register interface object to register with the domain manager component, and fills relevant information of the GPPDevicComponent into a ComponentType structure body, wherein the GPPDevicComponent component comprises a device component identifier, a device basic information profile, a component type and a self object componentObject, and the device basic information profile, the component type and the self object componentObject are used as registration parameters to be transmitted to the domain manager component;
(7) After receiving the registration information of the GPPDevicComponent, the domain manager component calls a registration information notification function registryInfo of a device manager component to notify the device manager component that the subordinate GPPDevicComponent has been successfully started and registered, and the information of the GPPDevicComponent is transmitted through parameters of a registryInfo function;
(8) After the AudioDeviceComponent is started, a registrar interface object ComponentRegistry of the domain manager component is obtained through a Registry IOR;
(9) The AudioDeviceComponent calls a register component function of a register interface object to register with the domain manager component, and relevant information of the AudioDeviceComponent is filled in a ComponentType structure body, wherein the register component function comprises a device component identifier, a device basic information profile, a component type and a component object of the device component, and the device basic information profile, the component type and the component object are used as registration parameters to be transmitted to the domain manager component;
(10) After receiving the registration information of the AudioDeviceComponent, the domain manager component calls the registration information notification function registryInfo of the devicemanager component to notify the device manager component that the subordinate AudioDeviceComponent has been successfully started and registered, and the information of the AudioDeviceComponent is transmitted through the parameters of the registryInfo function.
In a specific embodiment, by adopting the registration optimization method, the most important improvement is that the starting speed of the software platform is obviously improved from the aspect of user experience, and according to the original implementation manner, the starting time of the software platform can be represented by the following formula:
t＝MAX(t dm ，t dv )+MAX(t s1 ，t s2 )+MAX(t sd1 ，t sd2 )+t dd
wherein t is dm For the start-up time of the domain manager component, t dv T is the start-up time of the device manager component s1 For the startup time of GPP device components, t s2 For the start-up time of an audio device component, t sd1 Registration time, t, for GPP device component to device manager component sd2 Registration time, t, for an audio device component to a device manager component dd Registration time for the device manager component to the domain manager component. By adopting the registration optimization method, the starting time of the software platform is as follows:
t＝MAX(t dm ，t dv )+t dd
compared with the original platform starting time, the time MAX (t) for starting each equipment component is reduced s1 ，t s2 ) And a time MAX (t) sd1 ，t sd2 ) The starting speed of the software platform is improved, and the user experience is improved.
Compared with the prior art, the registration relationship is concise. Compared with a step-by-step registration mode in the standard, the method omits a registration manager interface of the equipment manager component, only reserves the registration manager interface of the domain manager component, globally only needs to maintain one component registration manager interface, simplifies registration relation and flow, saves system resources and reduces code complexity; the starting speed of the software platform is accelerated. The method has the advantages that the software platform realized according to the standard regulation mode needs to wait for all equipment components to be started successfully when the platform is started and is registered with the equipment manager component and the domain manager component step by step, the starting waveform can be deployed, the starting waiting time is long, the software platform can be started to be used only after the equipment manager component is started successfully and is registered with the domain manager component, the equipment components do not need to wait for all the equipment components, the equipment components can continue to finish the starting and registering work while the platform is used, and compared with the standard method, the starting speed of the platform is improved; the registration parameters are simple and consistent in structure. In the standard rule, only the information of the equipment component is needed to be contained in the registration parameters when the equipment component registers with the equipment manager component, and the registration parameters when the equipment manager component registers with the domain manager component are needed to contain the information of the equipment manager component and all the subordinate equipment components thereof, so that the parameter structure is complex; the registration parameters of all the components in the method only need to contain the information of the registration body, and the registration parameters have simple and consistent structures and are easy to manage and maintain; a single device component startup exception does not affect the operation and use of the device manager component to which it pertains and other device components thereunder. In a software platform realized according to a standard regulation mode, if a certain equipment component fails to start, the equipment manager component to which the equipment component belongs cannot register with the domain manager component, and other equipment components which are successfully started under the equipment manager component to which the equipment component belongs cannot be normally used; the starting registration process of each equipment component in the method is relatively independent, and whether the starting registration process is successful or not does not affect other equipment components, so that the availability and the robustness of the software platform are improved. In addition, when the software platform is used in operation, when the related resource information of a specified device component is required to be queried, the related information of the specified device component can be obtained by directly querying the maintained device component list through the register interface of the domain manager component, and the method is direct and simple and has higher query efficiency.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
It will be apparent to those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be centralized on a single computing device, or distributed across a network of computing devices, or they may alternatively be implemented in program code executable by computing devices, such that they may be stored in a memory device and executed by computing devices, or individually fabricated as individual integrated circuit modules, or multiple modules or steps within them may be fabricated as a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.
The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims (10)
1. A method for registration optimization of SCA equipment components, characterized by: the method comprises the following registration steps:
s1: the domain manager component starts up, publishes its registrar interface, and waits for the component to register;
s2: after the device manager component is started, acquiring a domain manager component register interface;
s3: the device manager component registers with the domain manager component;
s4: the device manager component starts each device component under the jurisdiction one by one;
s5: the equipment component is started successfully, and a domain manager component register interface is acquired;
s6: the device component registers with the domain manager component directly, and the registration parameters contain device component information;
s7: after the domain manager component receives the registration of a certain device component, a registration information notification function of the device manager component is called to notify the device manager component that the registration of a subordinate device component is successful;
s8: and if the equipment component is started to fail, ending the equipment component registration flow.
2. The method of registration optimization of SCA equipment assemblies as claimed in claim 1, wherein: the domain manager component and the device manager component are both arranged on the SCA software platform.
3. The method of registration optimization of SCA equipment assemblies as claimed in claim 2, wherein: the SCA software platform globally uses and maintains only one unified registrar interface, which is implemented in the same process as the domain manager component.
4. A method of optimizing registration of SCA equipment assemblies as claimed in claim 3, characterized by: the device manager component and the domain manager component operate at the same address or respectively at different addresses, and each component communicates through CORBA.
5. A method of optimizing registration of SCA equipment assemblies as claimed in claim 3, characterized by: the registrar interface is implemented and maintained by a domain manager component with which all components in the platform register directly.
6. The method of registration optimization of SCA equipment assemblies as claimed in claim 4, wherein: the register interface integrally manages the states and information of all registered components, and provides a registration function for registering each component, wherein the registration parameters of the registration function are structures for describing the information of each registered component.
7. The method of registration optimization of SCA equipment assemblies as claimed in claim 6, wherein: when the device manager component is realized, a registration information notification function is added, after the subordinate device component is successfully registered with a register interface of the domain manager component, the domain manager component notifies the device manager component that the subordinate device component is started and successfully registered by calling the registration information notification function, and meanwhile, the information of the device component is transmitted to the device manager component as a parameter of the registration information notification function.
8. The method of registration optimization of SCA equipment assemblies as claimed in claim 7, wherein: after the device manager component and the device components under the device manager component are started, the register interface objects of the domain manager component are obtained through the Registry IOR.
9. The method of registration optimization of SCA equipment assemblies as claimed in claim 8, wherein: the device manager component manages two device components, namely a GPP device component and an audio device component.
10. The method of registration optimization of SCA equipment assemblies as claimed in claim 9, wherein: the device manager component initiates the device components GPP device components and audio device components one by one in a thread manner.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310245708.2A CN116248629A (en) | 2023-03-13 | 2023-03-13 | Registration optimization method for SCA equipment component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310245708.2A CN116248629A (en) | 2023-03-13 | 2023-03-13 | Registration optimization method for SCA equipment component |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116248629A true CN116248629A (en) | 2023-06-09 |
Family
ID=86633072
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310245708.2A Pending CN116248629A (en) | 2023-03-13 | 2023-03-13 | Registration optimization method for SCA equipment component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116248629A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116614388A (en) * | 2023-07-14 | 2023-08-18 | 成都谐盈科技有限公司 | Method and terminal for realizing domain manager model based on software communication system structure |
-
2023
- 2023-03-13 CN CN202310245708.2A patent/CN116248629A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116614388A (en) * | 2023-07-14 | 2023-08-18 | 成都谐盈科技有限公司 | Method and terminal for realizing domain manager model based on software communication system structure |
| CN116614388B (en) * | 2023-07-14 | 2023-09-22 | 成都谐盈科技有限公司 | Method and terminal for realizing domain manager model based on software communication system structure |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11108653B2 (en) | Network service management method, related apparatus, and system | |
| CN106815066B (en) | Timed task scheduling method, device and system | |
| EP2285044A1 (en) | Computer readable medium, northbound interface uniform platform and starting method thereof | |
| CN106856438B (en) | Network service instantiation method, device and NFV system | |
| CN111245634B (en) | Virtualization management method and device | |
| CN116248629A (en) | Registration optimization method for SCA equipment component | |
| CN110391940A (en) | Response method, device, system, equipment and the storage medium of address of service | |
| CN106790084A (en) | A kind of heterogeneous resource integrated framework and its integrated approach based on ICE middlewares | |
| CN111078238A (en) | Centralized processing method and device for application configuration in container environment | |
| CN114710549A (en) | Dynamic management method, system and service node of network card in container platform | |
| CN111309474B (en) | Communication method, communication device and distributed service registration center | |
| CN105427149A (en) | Cross-border e-commerce BPO service method and device based on SOA expansion framework | |
| CN112217845B (en) | Data transmission method based on Netconf protocol and related equipment | |
| CN109660379B (en) | Network method, system and terminal | |
| US11683222B2 (en) | Virtual network function VNF deployment method and apparatus | |
| CN114157573A (en) | Method and device for deploying virtualized network function | |
| US20230041981A1 (en) | Identifying an Instance of a Virtual Network Function | |
| CN108196962B (en) | Method and device for realizing calling of interfaces of different versions | |
| CN109922482B (en) | OMC system deployment method, OMC system, electronic device and storage medium | |
| CN113364611B (en) | Resource ID management method, device, equipment and readable storage medium | |
| CN113010363A (en) | Container monitoring method under swarm cluster and shared service cloud platform | |
| WO2021052603A1 (en) | Method and apparatus for abstracting network resources in a mobile communications network | |
| CN115396305B (en) | Heterogeneous network equipment unified management and control method and system based on micro-service architecture | |
| CN109669793A (en) | Object calling method in middleware process | |
| CN113055211B (en) | Method for instantiating network service and network function virtualization orchestrator |
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 |