WO2016065773A1 - Procédé et appareil pour une gestion distribuée par une interface vers les couches supérieures - Google Patents

Procédé et appareil pour une gestion distribuée par une interface vers les couches supérieures Download PDF

Info

Publication number
WO2016065773A1
WO2016065773A1 PCT/CN2015/072804 CN2015072804W WO2016065773A1 WO 2016065773 A1 WO2016065773 A1 WO 2016065773A1 CN 2015072804 W CN2015072804 W CN 2015072804W WO 2016065773 A1 WO2016065773 A1 WO 2016065773A1
Authority
WO
WIPO (PCT)
Prior art keywords
service processing
passive
service
northbound interface
processing process
Prior art date
Application number
PCT/CN2015/072804
Other languages
English (en)
Chinese (zh)
Inventor
吴高科
肖志彬
曾蔚翔
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016065773A1 publication Critical patent/WO2016065773A1/fr

Links

Images

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

Definitions

  • the present invention relates to the field of communications, and in particular to a northbound interface distributed management method and apparatus.
  • the Optical Transport Network (OTN) and the Packet Transport Network (PTN) are carried on the market.
  • the IP equipment is increasing rapidly, and the demand from customers for unified supervision and centralized supervision through the northbound interface is increasing.
  • the first phase of centralized supervision of the northbound interface cascading adaptation.
  • the initial state of the northbound interface is the northbound interface of multiple vendors, multiple types of northbound interfaces, and regional supervision of multiple northbound interfaces of multiple network areas.
  • the northbound interface has developed a variety of devices, based on the existing northbound interface device, to achieve centralized supervision, such as: Simple Network Management Protocol (SNMP) multi-level
  • SNMP Simple Network Management Protocol
  • the cascading implementation is centralized and managed.
  • the Common Object Request Broker Architecture (CORBA) is implemented in a multi-level cascading manner. The basic idea is to layer-level cascading adaptation to achieve centralized management.
  • EMS network management platform with full device type, such as Huawei's U2000, and a batch of EMS network management platform represented by ZTE's U31. The number of equivalent network elements managed by these network management platforms gradually begins to count in tens of thousands.
  • the client manufacturers are currently requesting centralized supervision of the province, which means that the number of regulatory equivalent network elements will increase from 20,000 to 50,000, and 100,000, and the requirements for EMS network management platforms of various vendors are becoming more and more demanding. High, and the requirements for large-scale network management capabilities for northbound interfaces are also increasing.
  • the client vendor manages the device manufacturer's device.
  • the device In the new technology, such as the Software Defined Network (SDN), the device is managed by the northbound interface of the device manufacturer. This management method is very long. For a period of time, there is no essential change.
  • the SNMP interface is only suitable for managing alarm notifications.
  • the FTP interface is only suitable for managing configuration data. It needs to be fully managed, configured, alarmed, performance, and service delivered.
  • CORBA, MTOSI and other connection-oriented interfaces For the customer manufacturer, a connection (that is, a set of northbound interfaces on a vendor EMS network management) is a basic requirement, and the other is to require the stability of the northbound interface.
  • the new network management system replaces the original northbound interface, which unifies the northbound interface, reduces the number and number of northbound interface technologies, and improves the northbound interface management capability.
  • Most of the northbound interfaces in this phase are basically Single process processing.
  • the third phase of centralization supervision of the northbound interface large-scale network.
  • the northbound interface may have insufficient management capabilities due to excessive management data and complex services (such as insufficient memory).
  • the CPU capability is insufficient, which in turn causes the northbound interface to be unstable.
  • the invention provides a northbound interface distributed management method and device to solve at least the above problems.
  • a northbound interface distributed management apparatus including: a main process, at least one passive service processing process, and at least one active service processing process, where the main process is set to provide An interface that interacts with the user; the passive service processing process is configured to process a passive service corresponding to the user command; and the active service processing process is configured to process an active service that operates spontaneously.
  • the main process includes: a main process initialization module, configured to initialize parameters of the main process, and/or a context related to the main process; and a registration module configured to register the passive service process The process information and/or the service capability information; the command distribution module is configured to process the user command and deliver the user command to the passive service process.
  • a main process initialization module configured to initialize parameters of the main process, and/or a context related to the main process
  • a registration module configured to register the passive service process
  • the command distribution module is configured to process the user command and deliver the user command to the passive service process.
  • the passive service processing process includes: a passive service processing process initialization module, configured to initialize the passive service processing process, and/or register process information and/or service capability information of the passive service processing process to the location a main process; a passive service command receiving module, configured to receive and forward through the main process Transmitting, by the user, the user command to the passive service processing module, and returning a result of the processing by the passive service processing module; the passive service processing module, configured to process the forwarded by the passive service command receiving module User command.
  • a passive service processing process initialization module configured to initialize the passive service processing process, and/or register process information and/or service capability information of the passive service processing process to the location a main process
  • a passive service command receiving module configured to receive and forward through the main process Transmitting, by the user, the user command to the passive service processing module, and returning a result of the processing by the passive service processing module
  • the passive service processing module configured to process the forwarded by the passive service command receiving module User command.
  • the active service processing process includes: an active service processing process initialization module, configured to initialize the active service processing process, and/or register process information of the active service processing process to the main process;
  • the processing module is set to handle the active business running spontaneously.
  • the northbound interface comprises one of the following: a CORBA northbound interface, and an MTOSI northbound interface.
  • a method for distributed management of a northbound interface including: interacting with a user by using an interface provided by a main process to interact with a user; and passing at least one passive service Processing the process, processing the passive service corresponding to the user command; and processing the active service running spontaneously through the at least one active service processing process.
  • the interaction with the user by the interface provided by the main process and interacting with the user includes: initializing parameters of the main process, and/or a context related to the main process; and registering the passive Process information and/or service capability information of the service processing process; processing the user command, and delivering the user command to the passive service processing process.
  • processing, by the at least one passive service processing process, the passive service corresponding to the user command comprises: initializing the passive service process, and/or registering process information and/or service capability of the passive service process. Receiving information to the main process; receiving the user command forwarded by the main process, and forwarding the user command to a passive service processing module, and returning a result processed by the passive service processing module; processing the passive service command Receiving the user command forwarded by the module.
  • processing the spontaneously running active service by at least one active service processing process includes: initializing the active service processing process, and/or registering process information of the active service processing process to the main process; processing the spontaneous operation Active business.
  • the northbound interface comprises one of the following: a CORBA northbound interface, and an MTOSI northbound interface.
  • an interaction with a user is performed through an interface provided by a main process to interact with a user; a passive service corresponding to a user command is processed through at least one passive service processing process; and a process is processed through at least one active service
  • FIG. 1 is a schematic structural diagram of a northbound interface distributed management apparatus according to an embodiment of the present invention
  • FIG. 2 is a first schematic structural diagram 1 of a northbound interface distributed management apparatus according to an embodiment of the present invention
  • FIG. 3 is a second schematic structural diagram of a northbound interface distributed management apparatus according to an embodiment of the present invention.
  • FIG. 4 is a third schematic structural diagram of a northbound interface distributed management apparatus according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart diagram of a northbound interface distributed management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a northbound interface large-scale network management apparatus according to a preferred embodiment of the present invention.
  • FIG. 7 is a flow chart of a northbound interface large-scale network management apparatus according to a preferred embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a large-scale network management apparatus performed by a CORBA interface according to a preferred embodiment of the present invention.
  • FIG. 9 is a flowchart showing the operation of a CORBA interface for performing a large-scale network management apparatus according to a preferred embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a large-scale network management apparatus for an MTOSI interface according to a preferred embodiment of the present invention.
  • FIG. 11 is a flow chart showing the operation of a large-scale network management apparatus for an MTOSI interface according to a preferred embodiment of the present invention.
  • the embodiment of the present invention designs a scalable device for large-scale network management of the northbound interface from the distributed capability.
  • the device can distribute services to different service processes, and the service process can be extended as needed, thereby improving the large-scale network management capability of the northbound interface and adapting to the development of large-scale networks.
  • FIG. 1 is a schematic structural diagram of a northbound interface distributed management apparatus according to an embodiment of the present invention.
  • the northbound interface distributed management apparatus includes: a main process. 12. At least one passive service processing process 14, at least one active service processing process 16, wherein the main process 12 is configured to provide an interface for interacting with the user; the passive service processing process 14 is coupled to the main process 12, configured to process and user The passive service corresponding to the command; the active service processing process 16 is coupled to the main process 12 and configured to handle the active service running autonomously.
  • modules and units involved in the embodiments of the present invention may be implemented by software or by hardware.
  • the described modules and units in this embodiment may also be disposed in a processor.
  • a processor may include a main process 12, at least one passive service processing process 14, and at least one active service processing process 16.
  • the names of these modules do not constitute a limitation on the module itself under certain circumstances.
  • the main process 12 can also be described as "a module that is set to provide an interface for interacting with the user.”
  • the main process 12 may include: a main process initialization module 122, configured to initialize parameters of the main process, And/or a context associated with the main process; the registration module 124 is coupled to the main process initialization module 122, the passive service process 14 and the active service process 16, and is configured to register process information and/or service capabilities of the passive service process.
  • the information distribution module 126 is coupled to the registration module 124 and the passive service processing process 14 and is configured to process user commands and issue user commands to the passive service processing process.
  • FIG. 3 is a schematic diagram of a preferred structure of a northbound interface distributed management apparatus according to an embodiment of the present invention.
  • the passive service processing process 14 may include: a passive service processing process initialization module 142, configured to initialize passive The service processing process, and/or registration of process information and/or service capability information of the passive service processing process to the main process; the passive service command receiving module 144 is coupled to the passive service processing module 146, configured to receive user commands forwarded by the main process And forwarding the user command to the passive service processing module, and returning the result of the passive service processing module processing; the passive service processing module 146 is coupled to the passive service processing process initialization module 142, configured to process the user command forwarded by the passive service command receiving module.
  • FIG. 4 is a schematic diagram 3 of a preferred structure of a northbound interface distributed management apparatus according to an embodiment of the present invention.
  • the active service processing process 16 includes: an active service processing process initialization module 162, configured to initialize an active service. Processing the process, and/or registering process information of the active business process to the main process;
  • the active service processing module 164 is coupled to the active service processing process initialization module 162, configured to handle the active services that are running autonomously.
  • the northbound interface described above includes, but is not limited to, a northbound interface of one of: a CORBA northbound interface, and an MTOSI northbound interface.
  • a northbound interface of one of: a CORBA northbound interface, and an MTOSI northbound interface is preferred.
  • Their common feature is that the technology of the above-mentioned northbound interface application has its own distributed capabilities.
  • FIG. 5 is a schematic flowchart of a method for distributed management of a northbound interface according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • Step S502 Perform an interaction with the user by using an interface that is provided by the main process and interacts with the user;
  • Step S504 processing passive services corresponding to user commands by using at least one passive service processing process
  • Step S506 processing the active service running spontaneously through at least one active service processing process.
  • the foregoing step S502 may include: initializing parameters of the main process, and/or a context related to the main process; registering process information and/or service capability information of the passive service process; processing user commands, and delivering the user Command to passive business process.
  • the foregoing step S504 may include: processing, by the at least one passive service processing process, the passive service corresponding to the user command, including: initializing the passive service process, and/or registering the process information and/or service capability of the passive service process.
  • the information is sent to the main process; the user command forwarded by the main process is received, and the user command is forwarded to the passive service processing module, and the result processed by the passive service processing module is returned; and the user command forwarded by the passive service command receiving module is processed.
  • the foregoing step S506 may include: initializing an active service processing process, and/or registering process information of the active service processing process to the main process; and processing the active service running spontaneously.
  • the northbound interface described above comprises one of the following: a CORBA northbound interface, and an MTOSI northbound interface.
  • the preferred embodiment of the present invention relates to an adaptation apparatus and method, and more particularly to a northbound interface large-scale network management apparatus and method.
  • the device is applicable to the interface with the distributed capability of the northbound interface technology itself, for example, the CORBA northbound interface and the MTOSI northbound interface.
  • the technical solution adopted by the preferred embodiment of the present invention is: adopting a northbound interface
  • the device of the scale network management utilizes the idea of distributed management to deploy the service to different processes, thereby achieving the purpose of improving the northbound interface management capability and the scalable management capability.
  • the device includes the following processes:
  • the main process as the user's only connection entry, the user only interacts with the process.
  • the main process includes an initialization module, a registration module, and a command distribution module.
  • the initialization module initializes the main process parameters and initializes the context related to the main process.
  • the registration module is set to register the relevant information and business capability information to the main process for the passive service processing process.
  • the command distribution module processes user commands and addresses corresponding passive service processing processes, and forwards the commands to the passive service processing process.
  • the command distribution module has remote access capability and is the key to distributed processing.
  • the passive service processing process is relatively more active than the active service, which means that the related service needs to be triggered by the user command.
  • the passive service processing process includes a passive service processing process initialization module, a passive service command receiving module, and a passive service processing module.
  • the passive service processing process initialization module is responsible for the passive process initialization, and registers the corresponding process information and service capability information to the main process registration module;
  • the passive service command receiving module receives the user command forwarded by the main process, and forwards it to the passive service processing module for processing and processing.
  • the command receiving module is the receiver of the corresponding command distribution module, which is the key to distributed processing.
  • the active service processing process includes an active service processing process initialization module and an active service processing module.
  • the active service processing process initialization module is responsible for active service initialization and registers corresponding process information to the main process. After the initialization is completed, the active service processing module starts processing the corresponding active service.
  • the distributed management device adopts the distributed processing mode and the registration mechanism, one main process, N passive service processing processes, and N active service processing processes can be deployed. Balanced deployment based on service types and service invocations can be deployed in different passive services and active service processing processes to achieve scalability of large-scale management, reduce the complexity of each process, and improve stability.
  • the device is applied to a connected northbound interface, including northbound interfaces such as CORBA, MTOSI, and the like.
  • northbound interfaces such as CORBA, MTOSI, and the like.
  • the device is applicable to a vendor-based network management northbound interface management of an equivalent network element in units of 10,000, or a large-scale network management northbound interface management.
  • FIG. 6 is a schematic structural diagram of a northbound interface large-scale network management apparatus according to a preferred embodiment of the present invention. Referring to the flowchart of the northbound interface large-scale network management apparatus shown in FIG. 7, the northbound interface management process of the preferred embodiment of the present invention is described:
  • Step S702 the main process initializes, reads relevant parameters, and initializes the context environment.
  • Step S704 initializing the passive service processing process context.
  • Step S706 the passive service processing process registers the process context information and the service capability information with the main process.
  • Service capability information refers to which services can be processed by the passive service process.
  • Step S708 the main process registration module initializes the passive process registration information.
  • Step S710 the main process registration module passes the parameter information to the passive service processing process.
  • step S712 the passive service processing process is initialized until initialization is completed.
  • Step S714 initializing the active service processing process context.
  • Step S716 the active service processing process registers the process context information with the main process.
  • Step S720 the main process registration module passes the parameter information to the active service processing process.
  • step S722 the active service processing process is initialized until the initialization is completed.
  • Step S724 After the active service processing process is initialized, the corresponding service processing is started, for example, a series of service operations that do not need to be triggered, such as notification sending and FTP file generation.
  • active service processing it is suitable for services that require high-efficiency processing. For example, for notifications on a large-scale network, it is generally necessary to process hundreds of notifications per second, which is a service that consumes memory and CPU resources.
  • step S726 the user initiates a service call and sends a command to the main process.
  • step S728 the main process invokes the service information according to the command, and queries the registration module to query the address information of the corresponding passive service processing process.
  • step S730 the main process forwards the command to the corresponding passive service processing process.
  • Step S732 the passive service processing process service processing module processes the command.
  • step S734 if it is required to return data, the passive service processing process returns data to the caller.
  • a large-scale network management device diagram is performed with reference to the CORBA interface shown in FIG.
  • the CORBA interface has the distributed management capability itself.
  • the service distribution processing is generally not considered.
  • the apparatus of the preferred embodiment of the present invention can be implemented using CORBA distributed features.
  • the naming service process and the notification service process are also required.
  • the naming service process implements a naming tree, and the naming tree can access remote objects registered to the naming service, thereby implementing distributed management.
  • the device naming service naming tree needs to register two login nodes: the login manager and the registration module object.
  • the login manager is the EmsSessionFactory manager object defined by TMF814, and the registration module object belongs to the internal object of the device, which is a device implemented by the device. key point.
  • the service process is notified to implement the message proxy.
  • the main process, the active service processing process, and the passive service processing process of the device belong to the server, and the notification service can set up the notification agent on the server and the user end, thereby implementing the notification of the server and the client. Uncoupling.
  • the notification processing process sends a notification to the notification service, and the notification service is responsible for exchanging with the client.
  • Northbound interface CORBA main process including initialization module, registration module and command distribution module.
  • the initialization module initializes the main process parameters and initializes the main process ORB environment.
  • the registration module registers the CORBA object information related to the passive process, and the registration process needs to register itself with the naming service.
  • the command distribution module processes the user command, and addresses the corresponding passive service processing process according to the CORBA object corresponding to the command, and forwards the command to the passive service processing process.
  • the northbound interface configures the processing process, which processes the northbound interface configuration data, that is, the resource configuration data. It belongs to the passive business process, and the device only uses the passive service processing process to process the configuration data. Multiple passive service processing processes can handle various services such as alarm, performance, and end-to-end services according to the type of service.
  • the passive service processing process includes an initialization module, a passive service command receiving module, and a passive service processing module.
  • the configuration processing process initialization module acquires the main process registration module object from the naming service, registers the corresponding process information and service capability information to the main process registration module, acquires initialization parameter information, and completes the configuration processing process ORB initialization according to the parameter information.
  • the configuration processing process command receiving module receives the user command forwarded by the northbound interface CORBA main process, and forwards it to the configuration processing process processing module. After the processing is completed, if the data needs to be returned, the data is returned to the caller.
  • the northbound interface notifies the processing process and belongs to the active service processing process.
  • the northbound interface notification processing process includes an initialization module that notifies the processing module.
  • the northbound interface notification processing process initialization module acquires the main process registration module object from the naming service, registers the corresponding process information to the main process registration module, acquires initialization parameter information, and completes the configuration processing process ORB initialization according to the parameter information.
  • the northbound interface notification processing process is initialized, the corresponding notification information is processed and a notification is sent to the notification service process.
  • Step S902 notifying the service process to initialize.
  • step S904 the naming service process is initialized.
  • step S906 the Corba northbound interface main process initializes the context and initializes the ORB.
  • Step S908 the Corba northbound interface main process registers the login manager and the registration module object to the naming service.
  • Step S910 the Corba northbound interface configures the service processing process to initialize context information.
  • Step S912 the Corba northbound interface configuration service processing process acquires the main process registration module object from the naming service.
  • Step S914 the Corba northbound interface configuration service processing process registers the process context information and the CORBA service object with the Corba northbound interface main process.
  • step S916 the Corba northbound interface main process registration module passes the parameter information to the Corba northbound interface to configure the service processing process.
  • Step S918 the Corba northbound interface configures the service processing process to initialize the ORB.
  • step S920 the Corba northbound interface notifies the process to initialize the context information.
  • step S922 the Corba northbound interface notifies the process to acquire the main process registration module object from the naming service.
  • Step S924 the Corba northbound interface notifies the process to register the process context information with the Corba northbound interface main process.
  • Step S926 the Corba northbound interface main process registration module passes the parameter information to the Corba northbound interface notification process.
  • step S928 the Corba North notification process initializes the ORB.
  • step S930 the Corba North notification process notification processing module processes the notification.
  • step S932 Corba North sends a notification to the notification service process to the notification process.
  • Step S934 the user initializes, establishes a notification agent with the server, and receives the notification.
  • step S936 the user obtains the login manager object from the naming service.
  • step S938 the user performs a login operation to acquire a manager.
  • step S940 the user sends a configuration data acquisition command to the Corba northbound interface main process.
  • Step S942 the Corba northbound interface main process command distribution module performs addressing according to the manager object corresponding to the command, and finds the Corba northbound interface configuration service processing process.
  • Step S944 the Corba northbound interface main process forwards the command to the Corba northbound interface to configure the service processing process.
  • Step S946 the Corba northbound interface configures the service processing process service processing module to process the command.
  • step S948 if the data needs to be returned, the Corba northbound interface configures the service to return data to the user.
  • a large-scale network management device diagram is performed; as shown in FIG. 10, since the MTOSI sends a SOAP message based on the webservice, it has strong distributed management capability and supports registration and the like.
  • the apparatus of the preferred embodiment of the invention can thus be conveniently implemented.
  • the main module in FIG. 11 is identical to the device diagram shown in FIG. 6, except that the command receiving device is specialized as a service receiving addressing module in MTOSI, and an internal service is registered in the web service registration module 0 for other
  • the process obtains the startup parameters, and the passive process is specialized to process the processing process and the service delivery process.
  • the other parts are the same as those of FIG. 6, and will not be described again.
  • step S1102 the MTOSI main process is initialized.
  • step S1104 the MTOSI main process registers the internal service, and mainly provides services such as internal parameters.
  • Step S1106 The notification process acquires the startup parameter through the MTOSI internal service.
  • Step S1108 the process is notified to initialize.
  • step S1110 the configuration processing process registers the service with the MTOSI main process, and obtains the startup parameter through the MTOSI internal service.
  • step S1112 the configuration processing process is initialized.
  • step S1114 the service delivery processing process registers the service with the MTOSI main process, and obtains the startup parameter through the MTOSI internal service.
  • step S1116 the service delivery process is initialized.
  • step S1118 the notification process acquires the user notification service and sends a notification to the user.
  • step S1120 the user sends a service creation command to the MTOSI main process.
  • step S1122 the MTOSI main process performs service addressing as requested.
  • step S1124 the MTOSI main process distributes the request to the service delivery processing process.
  • Step S1126 The service delivery processing process processes the request message.
  • step S1128 the service delivery processing process returns processing data to the user.
  • the above embodiments and preferred embodiments of the present invention provide a scalable device that can achieve a northbound interface management capability of a 10,000-equivalent network element network and provide a scale management capability for network scale expansion. Scalability.
  • services can be distributed to different processes or different machines, the computing power and processing capability of the service are improved, and the complexity of each distributed process is reduced, thereby bringing about double improvement in performance and stability.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in a storage device by a computing device, or they may be fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the above-mentioned technical solution provided by the embodiment of the present invention uses an interface that interacts with the user provided by the main process to perform user command interaction with the user; and processes the passive service corresponding to the user command through at least one passive service processing process;
  • the problem of the northbound interface being unstable due to the large amount of management data and complicated services is solved by the at least one active service processing process, and the stability of the northbound interface is improved.

Abstract

La présente invention concerne un procédé et un appareil pour une gestion distribuée par une interface vers les couches supérieures. Le procédé consiste à : réaliser une interaction d'une commande d'un utilisateur avec un utilisateur par le biais d'une interface fournie par un processus principal et utilisée pour l'interaction avec l'utilisateur ; traiter un service passif correspondant à la commande de l'utilisateur par le biais d'au moins un processus de traitement de service passif ; et traiter un service actif s'exécutant spontanément par le biais d'au moins un processus de traitement de service actif. La présente invention permet de résoudre le problème dans l'état de la technique selon lequel une interface vers les couches supérieures est instable en raison d'une grande quantité de données gérées et d'un service complexe, et permet d'améliorer la stabilité de l'interface vers les couches supérieures.
PCT/CN2015/072804 2014-10-29 2015-02-11 Procédé et appareil pour une gestion distribuée par une interface vers les couches supérieures WO2016065773A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410594191.9A CN105634767A (zh) 2014-10-29 2014-10-29 北向接口分布式管理方法及装置
CN201410594191.9 2014-10-29

Publications (1)

Publication Number Publication Date
WO2016065773A1 true WO2016065773A1 (fr) 2016-05-06

Family

ID=55856490

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072804 WO2016065773A1 (fr) 2014-10-29 2015-02-11 Procédé et appareil pour une gestion distribuée par une interface vers les couches supérieures

Country Status (2)

Country Link
CN (1) CN105634767A (fr)
WO (1) WO2016065773A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116501713B (zh) * 2023-06-26 2023-09-22 成都谐盈科技有限公司 一种分布式文件系统的实现方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621814A (zh) * 2009-05-11 2010-01-06 中兴通讯股份有限公司 一种ip多媒体子系统业务及网络管理方法与系统
CN102680886A (zh) * 2011-03-11 2012-09-19 清华大学 远程逻辑分析系统
US20120253728A1 (en) * 2011-04-01 2012-10-04 Verizon Patent And Licensing Inc. Method and system for intelligent automated testing in a multi-vendor, multi-protocol heterogeneous environment
CN104079436A (zh) * 2014-07-14 2014-10-01 武汉大学 一种跨设备跨协议的epon网络中的网元管理系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100596122C (zh) * 2007-01-29 2010-03-24 中国联合网络通信集团有限公司 一种基于即时通信装置的自助服务系统及方法
CN101938579A (zh) * 2009-06-30 2011-01-05 中兴通讯股份有限公司 基于多进程的座席系统及座席业务的实现方法
CN102135929B (zh) * 2010-01-21 2013-11-06 腾讯科技（深圳）有限公司 一种分布式容错服务系统
CN103678008B (zh) * 2012-09-24 2017-12-22 腾讯科技（深圳）有限公司 数据读取方法及相应的数据读取装置
CN103064711B (zh) * 2012-12-27 2016-03-16 北京思特奇信息技术股份有限公司 一种基于Spread分布式应用系统的热加载方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621814A (zh) * 2009-05-11 2010-01-06 中兴通讯股份有限公司 一种ip多媒体子系统业务及网络管理方法与系统
CN102680886A (zh) * 2011-03-11 2012-09-19 清华大学 远程逻辑分析系统
US20120253728A1 (en) * 2011-04-01 2012-10-04 Verizon Patent And Licensing Inc. Method and system for intelligent automated testing in a multi-vendor, multi-protocol heterogeneous environment
CN104079436A (zh) * 2014-07-14 2014-10-01 武汉大学 一种跨设备跨协议的epon网络中的网元管理系统

Also Published As

Publication number Publication date
CN105634767A (zh) 2016-06-01

Similar Documents

Publication Publication Date Title
US11323316B2 (en) Device configuration method and apparatus that are based on network configuration protocol
US10575153B2 (en) Enhanced operations between service layer and management layer in an M2M system by allowing the execution of a plurality of commands on a plurality of devices
Datta et al. A lightweight framework for efficient M2M device management in oneM2M architecture
CA3103305C (fr) Procede de configuration de reseau et dispositif de communication
KR101740449B1 (ko) M2m(machine-to-machine)시스템에서 게이트웨이 변경 방법 및 이를 위한 장치
CN106789606B (zh) 一种网络通信系统、其管理方法及通信方法
CN107273228B (zh) 基于星型拓扑架构的消息传输方法
US20220405153A1 (en) Report application programming interface (api) capability change based on api filter
WO2013097719A1 (fr) Procédé et appareil pour la synchronisation de ressources
WO2018024121A1 (fr) Procédé de gestion de fonction de réseau (nf) et dispositif de gestion nf
WO2020238411A1 (fr) Procédé et appareil de découverte et de sélection de fonction d'exposition de réseau
WO2010127602A1 (fr) Procédé d'approvisionnement de paramètres de terminal, système afférent et dispositif de gestion de terminal
CN106487538B (zh) 业务提速方法、策略控制平台以及系统
CN109412877B (zh) 一种基于utn网络的网络能力开放系统
CN107645394B (zh) 一种sdn网络中的交换机配置方法
CN113852939A (zh) 面向云原生的用户面功能微服务系统
US20210274020A1 (en) Communication method, client device, and server device
WO2016065773A1 (fr) Procédé et appareil pour une gestion distribuée par une interface vers les couches supérieures
JP2017503422A (ja) ネットワーク要素データアクセス方法および装置、およびネットワーク管理システム
CN105049255B (zh) 一种网元数据同步的方法及其装置
CN101729530B (zh) 一种数据同步方法及系统
WO2016184227A1 (fr) Dispositif et procédé de production de modèle d'onu
US20220109607A1 (en) Customer premises equipment configuration management method and apparatus
CN106341353B (zh) 资源处理方法及装置
CN105320517A (zh) 基于web服务的适配器中间件系统及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15854405

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15854405

Country of ref document: EP

Kind code of ref document: A1