WO2021017906A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021017906A1
WO2021017906A1 PCT/CN2020/102841 CN2020102841W WO2021017906A1 WO 2021017906 A1 WO2021017906 A1 WO 2021017906A1 CN 2020102841 W CN2020102841 W CN 2020102841W WO 2021017906 A1 WO2021017906 A1 WO 2021017906A1
Authority
WO
WIPO (PCT)
Prior art keywords
adapter
information
protocol
client
interface
Prior art date
Application number
PCT/CN2020/102841
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to EP20847384.3A priority Critical patent/EP3975480A4/en
Publication of WO2021017906A1 publication Critical patent/WO2021017906A1/zh
Priority to US17/568,473 priority patent/US11785121B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • 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/02—Standardisation; Integration
    • H04L41/0226—Mapping or translating multiple network management protocols
    • 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/04—Network management architectures or arrangements
    • 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
    • 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
    • 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/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • 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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
    • 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/34—Signalling channels for network management communication
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • the basis of configuration management for the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) is the network resource management object (MO).
  • the 3GPP standard defines network resource model (NRM) modeling methods and MO types for different wireless network elements (such as base stations, etc.).
  • the configuration parameters of the network management system (network management system, NMS) sent to the element management system (EMS) or network element (network element, NE) are all encapsulated and sent based on the MO.
  • Configuration management is through a series of operations on NRM MO to realize the relevant network parameter setting of network elements (such as creating MO), and at the same time realize the maintenance and management of deployed network elements, such as configuration parameter modification (modify MO), query (query) MO and MO attributes) etc.
  • CM configuration management
  • CORBA common object request broker architecture
  • simple object access protocol simple object access protocol
  • SOAP REST representational state transfer
  • ONAP In order to build a unified network management infrastructure (open network automation platform (ONAP) + 3GPP services & systems aspects (SA) 5), ONAP needs to support the standard interfaces and NRM modeling mechanisms defined by 3GPP , It is possible to realize network configuration management. However, currently, the ONAP southbound interface does not support the CORBA, SOAP and RESTFul protocol processing supported by the Itf-N interface defined by the current 3GPP standard. If a unified network management infrastructure (ONAP+3GPP SA5) is to be built, ONAP cannot be implemented and 3GPP Business management docking.
  • ONAP open network automation platform
  • SA 3GPP services & systems aspects
  • This application provides a communication method and device for selecting a suitable adapter for realizing ONAP adaptation to 3GPP configuration management function, so as to realize ONAP and 3GPP business management docking.
  • this application provides a communication method, which may include: the adapter client obtains the southbound interface protocol type, and selects the first protocol adapter from two or more protocol adapters according to the southbound interface protocol type ; The adapter client is used to manage two or more protocol adapters; the first protocol adapter is used to implement the first protocol.
  • the adaptor client can be flexibly used Select the appropriate adapter to realize the connection between ONAP and 3GPP business management.
  • the adapter client obtains the protocol type of the southbound interface.
  • the specific method may be: the adapter client receives the first information from the service coordinator, and the first information is used to request network configuration for the first network element.
  • One information is a configuration parameter in the form of a name-value pair.
  • the first information includes the southbound interface protocol type; the adapter client obtains the southbound interface protocol type from the first information; or the adapter client obtains a preset southbound interface protocol Types of.
  • the adapter client can accurately obtain the southbound interface protocol type, so that a suitable protocol adapter can be selected subsequently.
  • the specific method for the adapter client to receive the first information from the service coordinator may be: the adapter client receives from the service coordinator the first information sent by the service coordinator calling the first interface; wherein, the first interface Provided for the adapter client.
  • the first interface may reuse an existing interface, or may be a newly defined interface.
  • the adapter client can accurately receive the first information from the service coordinator.
  • the adapter client may also perform the following operations: the adapter client sends the first information to the first protocol adapter; or the adapter client determines the first information according to the first information Second information, and send the second information to the first protocol adapter; the second information is the management object and its object attributes; the second information is obtained by mapping the first information based on the network resource management object template.
  • the first protocol adapter can subsequently be used to perform network resource management object template mapping through the first information, or the adapter client can directly send the converted second information to the first protocol adapter.
  • the specific method when the adapter client sends the first information to the first protocol adapter, the specific method may be: the adapter client calls the second interface provided by the first protocol adapter to send the first information to the first protocol adapter;
  • the specific method may be: the adapter client calls the second interface provided by the first protocol adapter to send the second information to the first protocol adapter.
  • the second interface can reuse an existing interface or a newly defined interface.
  • the adapter client can accurately send corresponding information to the first protocol adapter.
  • the adapter client sends a network resource model template query request to the first network element, and receives the network resource object model of the first network element from the first network element. In this way, the adapter client can subsequently map the network resource management object template.
  • the adapter client receives third information from the first protocol adapter.
  • the third information includes the name and identification of the first protocol adapter, and the supported protocol type; the adapter client sends the third information to the adapter client according to the third information. Create context information locally; the adapter client sends fourth information to the first protocol adapter, and the fourth information is used to notify the first protocol adapter of the registration result.
  • the adapter client can accurately manage the first protocol adapter, so that the first protocol adapter can be accurately selected as a suitable protocol adapter for the current business.
  • the first protocol adapter may be a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • this application provides a communication method, which may include: a first protocol adapter receives first information, determines second information according to the first information, and then sends the second information to the first network element; wherein, The first information is a configuration parameter in the form of a name-value pair; the first information is a configuration parameter for network configuration of the first network element; the first protocol adapter is used to implement the first protocol; the second information is the management object and its object attributes; The second information is obtained by mapping the first information based on the network resource management object template.
  • the specific method for the first protocol adapter to receive the first information may be: the first protocol adapter receives the first information from the adapter client, and the adapter client is used to manage two or more protocol adapters; or , The first protocol adapter receives the first information from the service coordinator.
  • the first protocol adapter can accurately obtain the first information.
  • the specific method when the first protocol adapter receives the first information from the adapter client, the specific method may be: the first protocol adapter receives the first information sent by the adapter client calling the second interface, and the second interface is the first Provided by a protocol adapter; when the first protocol adapter receives the first information from the service coordinator, the specific method may be: the first protocol adapter receives the first information sent by the service coordinator calling the second interface.
  • the second interface can reuse the existing interface, or it can be a newly defined interface.
  • the first protocol adapter can obtain the first information accurately.
  • the first protocol adapter sends a network resource model template query request to the first network element, and receives the network resource object model of the first network element from the first network element. In this way, the first protocol adapter can subsequently perform network resource management object template mapping.
  • the first protocol adapter sends third information to the adapter client.
  • the third information includes the name and identifier of the first protocol adapter, and the supported protocol type; the first protocol adapter receives the fourth information from the adapter client. Information, the fourth information is used to notify the registration result of the first protocol adapter.
  • the adapter client can accurately manage the first protocol adapter, so that the first protocol adapter can be accurately selected as a suitable protocol adapter for the current service.
  • the first protocol adapter may be a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • the present application also provides a communication device, which has the function of implementing the adapter client in the method example of the first aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes an acquisition module and a processing module, and optionally may also include a sending module. These modules can perform the corresponding functions in the above-mentioned method examples of the first aspect. The detailed description will not be repeated here.
  • the structure of the communication device includes a communication interface and a processor, and optionally may also include a memory.
  • the communication interface is used to send and receive data and communicate with other devices in the communication system.
  • the processor is configured to support the adapter client to perform the corresponding function in the above-mentioned first aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the present application also provides a communication device that has the function of implementing the first protocol adapter in the method example of the second aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes a receiving module, a processing module, and a sending module. These modules can perform the corresponding functions in the method examples of the second aspect. Refer to the detailed description in the method examples. Do repeat.
  • the structure of the communication device includes a communication interface and a processor, and optionally may also include a memory.
  • the communication interface is used to send and receive data and communicate with other devices in the communication system.
  • the processor is configured to support the first protocol adapter to perform the corresponding functions in the above-mentioned second aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • this application also provides a communication system, which may include the adapter client, the first protocol adapter, etc. mentioned in the above design.
  • the present application also provides a computer storage medium that stores computer-executable instructions, and the computer-executable instructions are used to make the computer execute any of the above when called by the computer. a way.
  • this application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute any of the above methods.
  • the present application also provides a chip system, which includes a processor, and is configured to support the communication device to implement the functions involved in the above aspect.
  • the chip system further includes a memory, and the memory is used to store necessary program instructions and data of the communication device.
  • the chip system can be composed of chips, or include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by this application.
  • FIG. 2 is a flowchart of a communication method provided by this application.
  • FIG. 3 is a flowchart of another communication method provided by this application.
  • FIG. 4 is a flowchart of a protocol adapter registration provided by this application.
  • FIG. 5 is a flowchart of a network element registration provided by this application.
  • FIG. 6 is a flowchart of an example of a communication method provided by this application.
  • FIG. 7 is a flowchart of an example of another communication method provided by this application.
  • FIG. 8 is a flowchart of an example of another communication method provided by this application.
  • FIG. 9 is a flowchart of an example of another communication method provided by this application.
  • FIG. 10 is a flowchart of an example of another communication method provided by this application.
  • FIG. 11 is a flowchart of an example of another communication method provided by this application.
  • FIG. 12 is a flowchart of an example of another communication method provided by this application.
  • FIG. 13 is a schematic structural diagram of a communication device provided by this application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by this application.
  • FIG. 15 is a structural diagram of a communication device provided by this application.
  • the embodiments of the present application provide a communication method and device for selecting a suitable adapter for implementing ONAP adaptation to 3GPP configuration management function.
  • the method and device described in the present application are based on the same inventive concept. Since the method and the device have similar principles for solving the problem, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • the adapter client is a newly proposed device in this application that has at least an adapter management function. For example, it can register and deregister the adapter; the adapter client manages two or two For the above protocol adapters, you can select a suitable protocol adapter according to your needs.
  • the protocol adapter can realize 3GPP interface protocol functions, for example, it can realize the processing of CORBA protocol, SOAP protocol and RESTFul protocol; correspondingly, the protocol adapter may include CORBA adapter, SOAP adapter, and RESTful adapter.
  • FIG. 1 shows the architecture of a possible communication system to which the communication method provided by the embodiment of the present application is applicable.
  • the communication system may be a network where ONAP and 3GPP service management are connected.
  • the architecture of the communication system may include a policy management function module (policy), a service coordinator (service orchestrator, SO), an available inventory management function entity (available and active inventory, AAI), and an ONAP optimization function module (ONAP optimization).
  • policy management function module policy management function module
  • SO service coordinator
  • AAI available inventory management function entity
  • ONAP optimization function module ONAP optimization
  • function, OOF data collection and analysis function module
  • DCAE adapter client
  • multiple protocol adapters network element management system (element management system, EMS)/network element (network element, NE). among them:
  • the SO can receive the business request of the NMS, trigger the corresponding workflow (workflow) processing process, and send the business processing request to the Adaptor client.
  • AAI mainly includes the functions of real-time view of inventory and topological relationships between them, and management functions such as event subscription, notification, data audit, and data version.
  • OOF is responsible for network function optimization, such as physical cell identifier (PCI) optimization.
  • PCI physical cell identifier
  • DCAE is used for data collection and analysis.
  • the adaptor client is used to manage the adaptor, for example, to register and deregister the adaptor.
  • the adaptor can be selected according to the needs; optionally, the adaptor client can also perform NRM network resource object template mapping.
  • Protocol adapters including multiple adapters supporting different protocols, such as Netconf adapter, Ansible adapter, Chef adapter, CORBA adapter, SOAP adapter, and RESTful adapter.
  • CORBA adaptor, SOAP adaptor and RESTFul adaptor are protocol adaptors supporting 3GPP protocol, which can implement 3GPP interface protocol functions.
  • EMS is used to manage the network elements in the communication system, that is, the EMS is used to manage the NE.
  • NE is a network element that needs to configure a network in the communication system to implement corresponding services.
  • EMS and NE can exist in the communication system at the same time, or only NE can exist.
  • EMS and NE can support one or more protocols among Netconf, Ansible, Chef, CORBA, SOAP, and RESTFul.
  • the communication system can also be extended to support other more protocols based on scenarios and needs.
  • Each of the above devices, functional modules, or functional entities, etc. can be either network elements implemented on dedicated hardware, software instances running on dedicated hardware, or virtualized functions on an appropriate platform. This application compares Not limited.
  • FIG. 1 is not limited to only include the devices shown in the figure, and may also include other devices not shown in the figure, which are not listed here in this application.
  • the communication method provided by the embodiment of the present application is applicable to the communication system shown in FIG. 1. As shown in Figure 2, the specific process of the method includes:
  • Step 201 The adapter client obtains the southbound interface protocol type; the adapter client is used to manage two or more protocol adapters.
  • Step 202 The adapter client selects the first protocol adapter from the two or more protocol adapters according to the southbound interface protocol type, and the first protocol adapter is used to implement the first protocol.
  • the protocol adapter managed by the adapter client may be two or more of the CORBA adapter, SOAP adapter, or RESTful adapter.
  • the first protocol adapter selected by the adapter client may be one of CORBA adapter, SOAP adapter, RESTful adapter, and so on.
  • the first protocol adapter is a CORBA adapter
  • the first protocol that can be implemented by the first protocol adapter is CORBA; of course, the situation is similar when the first protocol adapter is other adapters, and will not be listed here.
  • the adapter client obtains the southbound interface protocol type, and there may be two situations, for example:
  • the adapter client can receive first information from the service coordinator.
  • the first information is used to request network configuration for the first network element.
  • the first information is a configuration parameter in the form of a name-value pair.
  • the first information includes southbound Interface protocol type; the adapter client can obtain the southbound interface protocol type from the first information.
  • the key-value pair (key-value) format may be a parameter name-identification pair format, such as base station-identity (ID), cell-ID, CU-ID, DU-ID, and so on.
  • the first information further includes configured parameter data (parameter list), and may also include one or more of the following information: correlation ID, the corresponding management plane IP of the first network element Address and port (OM IP and port), network resource management object template (NRM MO template), operation type (action), operation object (action id), etc.
  • the correlation ID is the internal temporary identifier of the PNF allocated by the AAI when the physical network function (PNF) (here, the first network element) registers.
  • PNF physical network function
  • NRM MO template operation type
  • action operation object
  • the adapter client obtains the preset southbound interface protocol type, where the preset southbound interface protocol type can also be considered as the default southbound interface protocol type.
  • the specific method may be: the adapter client receives the first information sent by the service coordinator calling the first interface from the service coordinator; wherein the first interface is the adapter client which provided.
  • the first interface may be a reuse of an existing interface, such as an existing configuration application programming interface (configure (application programming interface, API)), or a newly defined interface.
  • the adapter client can perform one of the following two operations:
  • the adapter client sends the first information to the first protocol adapter.
  • the adapter client determines the second information according to the first information, and sends the second information to the first protocol adapter; the second information is the management object and its object attributes; the second information is that the first information is based on the network resource management object template Mapped.
  • the object attribute is a parameter or parameter set describing the nature of the management object, such as the geographic location of the base station, etc.;
  • the network resource management object template contains one or more management objects and the corresponding relationship of their object attributes, and the first information is based on
  • the management objects included in the corresponding network resource management object template and the corresponding object attributes are determined according to the name-value pair in the first information, and then the management included in the network resource management object template
  • the object and the corresponding object attribute are determined as the second information.
  • the network resource management object template will include one or more management objects related to the base station and the object attributes of the one or more management objects, and then combine the one or more management objects with The object attribute is determined as the second information.
  • the adapter client maps the first information to the second information according to the network resource management object template.
  • the first protocol adapter provides a second interface so that the adapter client can send information to the first protocol adapter by calling the second interface, for example:
  • the adapter client When the adapter client sends the first information to the first protocol adapter, the adapter client calls the second interface provided by the first protocol adapter to send the first information to the first protocol adapter;
  • the adapter client when the adapter client sends the second information to the first protocol adapter, the adapter client calls the second interface provided by the first protocol adapter to send the second information to the first protocol adapter.
  • the second interface may be an existing interface or a newly defined interface.
  • the adapter client may also perform the following operations: the adapter client sends a network resource model template query request to the first network element, and the first network element A network element receives the network resource object model of the first network element.
  • the network resource object model is the network resource management object template, and the two descriptions can be interchanged in this application.
  • the adapter client when there is a network element management system that manages the first network element in the communication system, when the adapter client sends a network resource model template query request to the first network element, it is sent to the first network element through the network element management system For example, the adapter client first sends a network resource model template query request to the network element management system, and then the network element management system sends a network resource model template query request to the first network element; accordingly, the first network element receives the first network For example, the first network element sends the network resource object model to the network element management system, and then the network element management system sends the network resource object model to the adapter client.
  • the adapter client When there is no network element management system in the communication system, the adapter client directly sends a network resource model template query request to the first network element, and directly receives the network resource object model of the first network element from the first network element.
  • the adapter client management protocol adapter needs the protocol adapter to register with the adapter client first.
  • the registration process of the first protocol adapter may be: the adapter client receives the third information from the first protocol adapter, and the third information is Including the name and identifier of the first protocol adapter, and the supported protocol type; the adapter client creates context information locally on the adapter client according to the third information; the adapter client sends fourth information to the first protocol adapter, and the fourth information is used for notification
  • the registration result of the first protocol adapter may be the actual name of the first protocol adapter, and the identification of the first protocol adapter may be the code or number of the first protocol adapter (for example, ID, etc.).
  • the name and the logo can also be the same concept, and one of the two can be used to represent the first protocol adapter. In this case, the name or the concept can include various examples of the name and logo in the above description.
  • the registration process of any protocol adapter is similar to the composition of the registration of the first protocol adapter.
  • the adapter client obtains the southbound interface protocol type; the adapter client selects the first protocol adapter from two or more protocol adapters according to the southbound interface protocol type, and the first protocol adapter uses To realize the first agreement.
  • the adaptor client can be used flexibly Select the appropriate adapter to realize the connection between ONAP and 3GPP business management.
  • the embodiment of the present application also provides a communication method. As shown in FIG. 3, the process of the method may include:
  • Step 301 The first protocol adapter receives first information, where the first information is a configuration parameter in the form of a name-value pair; the first information is a configuration parameter for network configuration of the first network element; the first protocol adapter is used to implement the first protocol .
  • Step 302 The first protocol adapter determines second information according to the first information.
  • the second information is the management object and its object attributes; the second information is obtained by mapping the first information based on the network resource management object template.
  • Step 303 The first protocol adapter sends second information to the first network element.
  • the first protocol adapter maps the first information to the second information according to the network resource management object template.
  • the first protocol adapter is a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • the first protocol adapter receiving the first information can be specifically divided into the following two situations:
  • the first protocol adapter receives the first information from the adapter client, and the adapter client is used to manage two or more protocol adapters.
  • the case c1 corresponds to the case where the adapter client performs the operation b1 in the embodiment shown in FIG. 2 above.
  • the first protocol adapter is managed by the adapter client.
  • the first protocol adapter receives the first information from the service coordinator.
  • the possible scenario may be that there is only the first protocol adapter in the communication system, but no other adapters.
  • the adapter client may not be set in the communication system; of course, the adapter client can also be set.
  • the adapter client When the adapter is set When the client is the client, the adapter client only manages the first protocol adapter.
  • the first protocol adapter provides a second interface so that other devices can call the second interface to send information to the first protocol adapter, for example:
  • the first protocol adapter When the first protocol adapter receives the first information from the adapter client, the first protocol adapter receives the first information sent by the adapter client calling the second interface, and the second interface is provided by the first protocol adapter;
  • the first protocol adapter When the first protocol adapter receives the first information from the service coordinator, the first protocol adapter receives the first information sent by the service coordinator calling the second interface.
  • the second interface can be an existing interface or a newly defined interface.
  • the first protocol adapter when the NRM MO template is not included in the first information, the first protocol adapter also performs the following operations: the first protocol adapter sends a network resource model template query request to the first network element, and The first network element receives the network resource object model of the first network element.
  • the first protocol adapter when there is a network element management system that manages the first network element in the communication system, when the first protocol adapter sends a network resource model template query request to the first network element, it is sent to the first network element through the network element management system.
  • the first protocol adapter first sends a network resource model template query request to the network element management system, and then the network element management system sends a network resource model template query request to the first network element; accordingly, the first network element receives the first network element
  • the first network element sends the network resource object model to the network element management system, and then the network element management system sends the network resource object model to the first protocol adapter.
  • the first protocol adapter When there is no network element management system in the communication system, the first protocol adapter directly sends a network resource model template query request to the first network element, and directly receives the network resource object model of the first network element from the first network element.
  • the first protocol adapter when the first protocol adapter is managed by the adapter client, the first protocol adapter needs to register with the adapter client first.
  • the specific process may include: the first protocol adapter sends third information to the adapter client. It includes the name and identifier of the first protocol adapter, and the supported protocol type; the first protocol adapter receives fourth information from the adapter client, and the fourth information is used to notify the first protocol adapter of the registration result.
  • the registration process of the first protocol adapter may refer to the process in FIG. 4.
  • the first protocol adapter receives first information, the first information is a configuration parameter in the form of a name-value pair; the first information is a configuration parameter for network configuration of the first network element; the first protocol The adapter is used to implement the first protocol; the first protocol adapter determines the second information according to the first information, the second information is the management object and its object attributes; the second information is obtained by mapping the first information based on the network resource management object template; A protocol adapter sends second information to the first network element.
  • the protocol adapter when the adapter client management protocol adapter is set in the communication system, the protocol adapter needs to be registered with the adapter client.
  • the Adaptor needs to send its attribute and capability information (such as the supported protocol types, etc.) to the Adaptor Client, and the Adaptor Client will uniformly manage the Adaptors corresponding to the interface, then the subsequent network configuration management process , Adaptor Client can select the appropriate adaptor based on the adaptor's capabilities.
  • the response information stored in the Adaptor Client is deleted through the relevant process.
  • Figure 4 shows the registration process after the protocol adapter goes online.
  • the process may include:
  • Step 401 The protocol adapter completes online deployment based on ONAP's current function module deployment mechanism, ONAP operations manager (OOM).
  • OOM ONAP operations manager
  • Step 402 The protocol adapter sends an adapter online notification message to the adapter client.
  • Adaptor Client the information of the adapter client (Adaptor Client) that manages this protocol adapter (such as the IP address of the adapter client (Adaptor client IP address), etc.) will be configured.
  • the adapter online notification message carries the name of the protocol adapter (Adaptor name), the identifier of the protocol adapter (Adaptor ID), and the supported protocol type ( Adaptor type), where the Adaptor ID can be its IP address, serial number, and other IDs that can uniquely identify and identify the protocol adapter.
  • Adaptor name the protocol adapter
  • Adaptor ID the identifier of the protocol adapter
  • Adaptor type the supported protocol type
  • the value of Adaptor type can be CORBA, SOAP, RESTful (the future expansion supports other protocol types, and the value of this parameter needs to be extended to support the corresponding protocol), etc.
  • the online notification message is the third information involved in the embodiment shown in FIG. 2 or FIG. 3 above.
  • Step 403 After receiving the online notification message of the protocol adapter, the adapter client creates a corresponding context record for the protocol adapter locally on the adapter client, and saves its corresponding attribute capability information (that is, the parameter information sent in step 402).
  • Step 404 After completing the information registration record of the protocol adapter, the adapter client returns an adapter online notification confirmation message to the protocol adapter to confirm the registration result.
  • the value of result (result) may be registration-accept, registration-reject, error, etc.
  • the online notification confirmation message is the fourth information involved in the embodiment shown in FIG. 2 or FIG. 3 above.
  • step 402 and step 403 is only an example, and can also be other messages with the same function.
  • the online notification message can be replaced by an adapter register request, etc.
  • online notification The confirmation message can be replaced with an adaptor register response (Adaptor register response), etc.
  • the Adaptor client manages the deployed and online protocol adapters in a unified manner.
  • the adapter client can select an adapted protocol adapter based on information such as the protocol type supported by the NE.
  • the Adaptor client can obtain the deployed and online protocol adapters and their attribute and capability information in a timely manner, so that appropriate protocol adapters can be selected in the follow-up, thereby realizing the connection between ONAP and 3GPP business management.
  • network equipment (network elements) of different equipment vendors may only support one interface protocol (such as the CORBA protocol), or may support multiple interface protocols (such as the CORBA protocol and the SAOP protocol).
  • the network equipment of different equipment vendors may support different NRM templates. For example, the products of equipment vendor A support the NRM model of R1 version, and the products of equipment vendor B support the NRM model of R2 version, then the network according to the different version of the NRM model The resource object is unreasonable.
  • the network device can be modeled as 5 MOs, and if according to the R2 version of the NRM model, the network device can be modeled as 10 MO. Therefore, in order to accurately obtain the attribute capability information of the network device, the network device, such as a physical network function network element (Physical Network Function, PNF), needs to notify the corresponding function module (such as AAI) of ONAP to save its attribute capability after deployment.
  • PNF Physical Network Function
  • FIG 5 shows a PNF registration process, which may specifically include the following steps:
  • Step 500 After the PNF is powered on, the initial configuration and IP address acquisition are completed.
  • step 500 the management plane IP address and port of ONAP are obtained.
  • Step 501 The PNF sends a PNF registration request message to the management plane function module (such as DCAE) of the management plane IP address and port identifier of the ONAP acquired in step 500.
  • the management plane function module such as DCAE
  • the protocol type parameters supported by the PNF (the values can be CORBA, SOAP, RESTful, etc.), the NRM MO template supported by the PNF and the management plane IP and port of the PNF are added.
  • the message may be reported to the DCAE in the form of a virtual network function event stream ((Virtual network function, VNF) event streaming, VES) event.
  • VNF Virtual network function
  • VES virtual network function event streaming
  • NRM MO template refers to the network resource object model corresponding to the corresponding version of the NRM modeling method supported by the PNF (for example, a tree structure model that includes multiple MOs and the relationship between MOs (such as inheritance, etc.)).
  • the value of the protocol type supported by PNF can be CORBA (CORBA-only), SOAP (SOAP-only), RESTful (RESTful-only), CORBA and SOAP (CORBA and SOAP supported), RESTful and SOAP-only SOAP (RESTful and SOAP supported), CORBA and RESTful (CORBA and RESTful supported), and fully supported (Full-supported). If PNF supports multiple protocols at the same time, the preferred protocol will be specified. For example, the value of the protocol type supported by PNF is CORBA and RESTful supported, and the preferred CORBA (CORBA preferred) or CORBA with high priority (CORBA with high- priority selected).
  • Step 502 DCAE parses the PNF registration request message, obtains the parameter information contained in the PNF registration request message, and sends a registration event message to the PRH, and sends the newly added parameter information in step 501 to the PRH together.
  • Step 503 The PRH notifies the AAI to create a corresponding AAI entity for the newly registered PNF, and sends the parameter information of the PNF to the AAI.
  • Step 504 AAI creates an AAI entity for PNF, assigns an internal identification Correlation ID to it, and saves its attribute parameter information.
  • the attribute parameter information may include the protocol type parameters supported by the PNF, the NRM MO template supported by the PNF, and the management plane IP and port parameters of the PNF.
  • Step 505 The ONAP function module executes PNF configuration.
  • the PNF does not need to include the NRM MO template it supports In the PNF registration request message, you only need to register the supported NRM version number (such as NRM Version) in DCAE (then in the subsequent business processing, the ONAP function module can query the corresponding NRM MO model based on the NRM version) ), so the new parameters that should be included in steps 501, 502, and 503 include the protocol type parameters supported by the PNF, the NRM version supported by the PNF, and the management plane IP and port of the PNF.
  • ONAP functional modules such as AAI
  • the foregoing process is the registration process of the first network element, and the relevant parameters are the parameters of the first network element.
  • the PNF needs to update the registered information.
  • the PNF sends the VES event to the DCAE and combines the updated information Sent to DCAE, DCAE sends an update request to PRH, and PRH updates the PNF information stored in AAI.
  • the detailed process is similar to the registration process described in FIG. 5, except that the names of steps 502, 503, and 504 are different.
  • the message only carries the necessary identification (such as PNF ID) and updated parameters.
  • the specific process can refer to the above registration process, which will not be described in detail here.
  • This application is used in the NMS to implement the configuration management process of NE network elements through ONAP functional modules (for example, the management process of management object creation, modification, and deletion)
  • ONAP functional modules for example, the management process of management object creation, modification, and deletion
  • the available inventory management function entity takes AAI as an example
  • the service coordinator takes SO as an example
  • the first network element takes NE as an example
  • the network element management system takes EMS as an example. Description etc.
  • the following examples can be applied to the initial configuration management of NE in the site-opening scenario, network operation and maintenance scenarios, or service features (such as mobility load balancing (MLB), carrier aggregation (CA) and other features) opening Scene management procedures such as modifying NE configuration parameters and deleting NE configuration parameters.
  • the site-opening scenario refers to the fact that the site-opening process actually performs basic parameter configuration on newly-built network equipment (that is, NE, such as base station) to enable service processing
  • the service-feature-opening scenario refers to: under normal circumstances, the service characteristics
  • the deployment data (such as the MO and its attributes corresponding to the business feature) will be imported into the EMS/NE system together with the site opening data when the site is built.
  • the main function of opening the business feature is to modify the attribute parameters of the management object related to the business feature to make it Service processing that supports this feature, such as the activation of the MLB feature, requires modification of the attribute parameter settings of the MLB-related MO, such as turning on the MLB algorithm switch, setting the cell identifier for enabling the MLB feature, etc., so that the base station supports MLB processing.
  • Figure 6 shows that when SO receives a business request from NMS, determines the business workflow (workflow) that needs to be executed based on the request parameters, and schedules the corresponding adapter client (Adaptor client) and protocol adapter to perform configuration processing.
  • An example of the communication method provided in the application embodiment, the process of this example may specifically include the following steps:
  • Step 600 The NMS sends a service request instruction message (service request) to the SO.
  • the service request instruction message may include a related parameter list (Parameter list).
  • Parameter list may also include one or more of the following: the requested operation type ( Action), operation object (Action id), southbound interface protocol type. among them:
  • Action Its value can be create-action, modify-action, and delete-action. If the service request instruction message does not carry this parameter, the default Action is to execute Create-action.
  • Action id It indicates the type of the operation object of the aforementioned Action, and the value can be NEfunction-type, cell-type, cell-relation-type, etc. If the service request instruction message does not carry this parameter, the aforementioned Action is for all operation objects by default.
  • Action id is defined according to the MO type abstracted by NMR modeling (that is, the MO type defined by NRM is the value range of Action id).
  • the NRM of 5G NR MO includes the distributed unit function of the base station ((gNodeB, GNB) (distributed unit) , DU) Function), GNB centralized unit (central unit, CU) Function, new air interface cell (NRCell), new air interface cell neighbor relationship (NRCellRelation), etc.
  • the value range of Action id includes GNBDUFunction-type, GNBCUFunction-type, NRCell-type, NRCellRelation-type, etc.
  • Parameter list the parameter data that the NMS needs to configure, in the form of a "name-value" pair format, which can specifically include the planning configuration data of the operator, such as network element identification (NE id), cell identification, and neighboring cell configuration relationships, Frequency setting, feature ID, cell identification for enabling features, etc.
  • NE id network element identification
  • cell identification cell identification
  • neighboring cell configuration relationships Frequency setting
  • feature ID cell identification for enabling features, etc.
  • Southbound interface protocol type its value can be CORBA-selected, SOAP-selected, RESTful-selected, and it identifies the protocol type of the southbound interface that the NMS hopes to select. This parameter is used as a reference when the Adaptor client selects the protocol adapter in the subsequent process. If the service request instruction message does not carry this parameter, the adaptor client selects the protocol adapter according to the default priority of the protocol type supported by the NE, that is, the adaptor client selects the protocol adapter according to the predefined southbound interface protocol type.
  • Action and Action id have a one-to-one correspondence. If the service request instruction message involves multiple operation objects, it involves the Action of each object.
  • Step 601 The SO determines a corresponding workflow based on the business request of the NMS, thereby triggering the execution of the corresponding business processing flow.
  • the SO obtains the identification (NE ID) of the network element targeted by the service request from the parameter list in step 600, and initiates a request to query AAI to confirm the registration status of the corresponding NE.
  • the network element may be the first network element involved in the embodiment shown in FIG. 2 or FIG. 3.
  • Workflow refers to a pre-defined business execution workflow, which can include all the functional modules that perform this business processing and the order in which the functional modules participate in the business processing.
  • the configuration management workflow is SO-AAI (execution information query confirmation)-Adaptor client( Perform MO template mapping, Adaptor selection)-protocol adapter (execute interface protocol conversion).
  • Step 602 The SO sends a network element registration status information query (NE onboarding status check) to the AAI to query whether the network element that needs to be operated has completed the online registration, and the network element registration status information query carries the network element identification (NE ID).
  • NE onboarding status check a network element registration status information query
  • this step can also be used to query whether a network element (such as a base station) supports a certain service feature (such as an MLB feature), that is, to query AAI to confirm whether the AAI entiy attribute of the corresponding network element includes MLB-related attributes Deployment parameter configuration. If so, the MLB feature is supported, otherwise it is not supported.
  • a network element such as a base station
  • a certain service feature such as an MLB feature
  • Step 603 If the network element identified by the queried NE ID does not save the corresponding registration information in the AAI, the AAI returns the network element status as Unavailable, and the SO receives the return message and informs the NMS that the corresponding network element has not completed registration , The process ends here. If the network element identified by the queried NE ID has stored corresponding registration information in the AAI, the AAI returns the relevant information of the network element, including NE ID, Correlation ID, OM IP and port, NRM MO template. Correlation ID is the internal temporary identification of the PNF allocated by AAI when the PNF is registered. OM IP and port and NRM MO template are sent to AAI when PNF is registered.
  • Step 604 SO calls the first configuration application programming interface (configure API) to initiate the configuration processing flow, and sends a configuration request to the Adaptor client, and sends the relevant parameters of step 600 and step 603 to the Adaptor client, where the relevant parameters include parameter list Optional also include one or more of the following: Correlation ID, OM IP and port, NRM MO template, Action, Action id, Southbound interface protocol type.
  • the first configure API is the first interface involved in the embodiment shown in FIG. 2, and in this step, the first interface is an existing configured interface.
  • the related parameters include the southbound interface protocol type
  • the above steps are equivalent to the situation in which the SO sends the first information to the adapter client in the situation a1 involved in the embodiment shown in FIG. 2.
  • Step 605 After the adaptor client receives the SO configuration request, it selects the corresponding protocol adapter based on the southbound interface protocol type.
  • the Adaptor client selects the protocol adapter according to the default priority of the protocol type supported by the NE (the preset Southbound interface protocol type). ) To select.
  • the protocol adapter selected by the adapter client here may be the first protocol adapter in the embodiment shown in FIG. 2 or FIG. 3.
  • Step 606 The adaptor client calls the second configure API to initiate interface adapter configuration processing, that is, forwards the configuration request to the selected protocol adapter.
  • step 606 is the operation b1 involved in the embodiment shown in FIG. 2 above.
  • the second configure API is the second interface involved in the embodiment shown in FIG. 2.
  • the second interface is a multiplexed existing existing second interface.
  • Step 607 The protocol adapter sends an NRM template query request to the EMS/NE, requesting to obtain the NRM MO template supported by the NE.
  • the request message carries the NE ID and the NRM version (version), and the NRM version has no actual value, only a parameter indication , Used to inform EMS/NE that they want to obtain NRM MO template.
  • step 608 the protocol adapter needs to perform this step and the following step 608.
  • the protocol adapter when there is an EMS in the communication system, the protocol adapter sends an NRM template query request to the EMS, and the EMS forwards the NRM template query request to the NE; when there is no EMS in the communication system, the protocol adapter directly sends the NRM template query request to NE.
  • Step 608 The EMS/NE returns the requested NE’s NRM MO template (NRM MO template) to the protocol adapter.
  • the returned NRM MO template is the network resource object model (for example, a tree) corresponding to the corresponding version of the NRM modeling method supported by the NE. Shape structure model, including multiple MOs and the relationship between MOs (such as inheritance, etc.)).
  • the NE when there is an EMS in the communication system, the NE sends the NRM MO template to the EMS, and then the EMS forwards the NRM MO template to the protocol adapter; when there is no EMS in the communication system, the NE directly sends the NRM MO template to the protocol adapter.
  • Step 609 The protocol adapter performs network resource management object template mapping.
  • the protocol adapter determines the type of network resource object MO that needs to be operated based on the Action id, and identifies the model attributes of the corresponding MO type based on the NRM MO template, and executes Parameter list(" Name-value") mapping to MO, that is, converting Parameter list into corresponding MO objects and attribute parameters.
  • the protocol adapter determines the operation processing for the corresponding MO based on the Action. If no Action and Action id are included in step 600, the protocol adapter performs default processing, that is, creating all MO objects of the NRM MO template.
  • Step 610 The protocol adapter performs the protocol format adaptation conversion according to the corresponding protocol, including operation conversion and parameter conversion.
  • the CORBA Adaptor will execute the Create_managed_object operation that converts the Create MO operation into CORBA.
  • the detailed conversion processing refers to the existing 3GPP standard Processing, this application will not describe the conversion process in detail.
  • Step 611 The protocol adapter calls the southbound interface API/SB API to send a corresponding configuration management instruction message to the address identified by the OMIP and the port identified by the port.
  • Step 612 The EMS receives the instruction to execute the configuration of the NE.
  • Step 613 After completing the NE configuration management processing, the EMS replies a response message to the protocol adapter, and includes the MO set by the EMS and its attribute parameters in the message.
  • Step 614 The protocol adapter receives the response message and sends parameter information to the SO, including converting the MO and its attribute parameters carried in step 613 into corresponding parameters in the form of "name-value" pairs, and carrying the Correlation ID and update parameters ( updated parameters).
  • Step 615 The SO updates the parameter information of the network element NE entity stored in the AAI, and carries the Correlation ID and updated parameters.
  • steps 602 and 603 in the above example can be performed by the Adaptor client, that is, the SO completes the processing of step 601 and directly initiates configuration management to the Adaptor client, that is, step 604 is performed.
  • step 604 is Including NE ID, southbound interface protocol type, Parameter list, Action, and Action id.
  • the Adaptor client receives step 604, it performs the operations in steps 602 and 603 above to obtain Correlation ID, OM IP and port, NRM MO template and other information, that is, the Adaptor client sends the network element registration status information query to AAI, and then receives Return the message, and then the Adaptor client will perform the next steps.
  • the corresponding operations involved in the subsequent examples shown in FIGS. 7 and 8 are similar. This application will not be described in detail here.
  • Fig. 7 shows another example of applying the communication method provided by the embodiment of the present application, and the scenario of this example is the same as the scenario of the example shown in Fig. 6.
  • the interface calls between SO, Adaptor client, and protocol adapters are unified reuse of the Configure API that has been supported in the prior art, and the function module identifies the function to be executed based on the action parameter
  • the analysis is only aware; and the example shown in Figure 7 defines a variety of different APIs in the interface between SO, Adaptor client and xx Adaptor.
  • the function module determines the business processing functions that need to be executed based on the API type, such as create , Modify, deploy site, etc. Then there is no need to pass Action parameters on the interface between functional modules.
  • the following Figure 7 takes the site opening scenario (the creation of MO needs to be executed) as an example for description.
  • the example process shown in Figure 7 may include the following steps:
  • Steps 700-703 similar to the above-mentioned step 600-step 603, the description refers to the description of the above-mentioned step 600-step 603, which will not be detailed here.
  • Step 704 SO is defined based on the workflow and calls the first API.
  • deploy site API initiates the configuration processing flow, and sends a configuration request to the Adaptor client, and sets the relevant parameters of step 700 and step 703, including the Parameter list, Optionally also include one or more of the following: Correlation ID, OM IP and port, NRM MO template, Action id, and Southbound interface protocol type sent to the Adaptor client.
  • the interface API called in this step is the first interface involved in the embodiment shown in FIG. 2, and the first interface in this step is a newly defined interface.
  • the related parameters include the southbound interface protocol type
  • the above steps are equivalent to the situation in which the SO sends the first information to the adapter client in the situation a1 involved in the embodiment shown in FIG. 2.
  • Step 705 The adaptor client receives the SO configuration request (for example, the site opening configuration request), and selects the corresponding protocol adapter based on the southbound interface protocol type.
  • SO configuration request for example, the site opening configuration request
  • the configuration request contains the protocol type of the southbound interface, it will be used directly. If this parameter is not carried, the adapter client will select the protocol adapter according to the default priority of the protocol type supported by the NE (the preset southbound interface protocol type) ) To select.
  • Step 706 The adaptor client determines that the object creation needs to be executed based on the API type of step 704 (deploy site is to open the site), and then calls the second API, such as create API to initiate interface adapter configuration processing, that is, forward the configuration request to the selected protocol adapter.
  • the second API such as create API to initiate interface adapter configuration processing
  • step 706 is the operation b1 involved in the embodiment shown in FIG. 2 above.
  • the second API is a second interface involved in the embodiment shown in FIG. 2.
  • the second interface is a newly defined second interface.
  • Steps 707 to 708 similar to the above step 607 to step 608, the description refers to the description of the above step 607 to step 608, which will not be detailed here.
  • Step 709 The protocol adapter performs network resource management object template mapping.
  • the protocol adapter determines the type of network resource object MO that needs to be operated based on the Action id, and identifies the model attributes of the corresponding MO type based on the NRM MO template, and executes Parameter list(" Name-value") mapping to MO, that is, converting Parameter list into corresponding MO objects and attribute parameters.
  • the Adaptor determines the operation processing for the corresponding MO based on the API type in step 706, such as Create. If Action and Action id are not included in step 700, the protocol adapter performs default processing, that is, creates all MO objects of the NRM MO template.
  • Steps 710-715 similar to the above-mentioned step 610-step 615, the description refers to the above-mentioned step 610-step 615 description, which will not be detailed here.
  • FIG. 8 shows another example of applying the communication method provided by the embodiment of the present application, and this example scenario is the same as the example shown in FIG. 6 and FIG. 7.
  • the NMS needs to display the type of operation object that needs to be operated through Action id in the service request.
  • the SO, Adaptor client and protocol adapter The interface call is still the same as the example shown in Figure 6, which is the unified reuse of the Configure API that has been supported in the prior art, and the NMS clearly indicates the management object MO that needs to be operated and its attribute settings in the service request, that is, the NMS pairs the network element
  • the configuration parameters of is not delivered as a parameter list in the form of "name-value" pairs, but are mapped into a series of corresponding MO and attribute parameters in the NMS, and at the same time specify the action for each MO, then
  • the protocol adapter also does not need to perform management object MO mapping processing based on the NRM MO template, and does not need to pass parameters such as Action id and NRM MO template on the interface between the functional modules.
  • the flow of the example shown in FIG. 8 may include the following steps:
  • Step 800 The NMS completes the network resource management object mapping process before the service request, determines the management object MO to be operated and its attribute parameters, and then the NMS sends a service request instruction message to the SO.
  • the service request instruction message may include the management object and its attribute parameters (MO and Attributes); it may also include one or more of Actions for MOs and southbound interface protocol types. among them:
  • MO and Attributes The specific network resource management objects that need to be operated for this service processing (such as 5G NR MO: GNBDUFunction, GNBCUFunction, NRCell, NRCellRelation, etc.). Attributes are the attribute parameters of each MO, such as GNBDUFunction.
  • the attribute parameters of MO include gNBDUId , GNBDUName, gNBId, gNBIdLength, NRCell MO attribute parameters include nCI, pLMNIdList, etc.
  • Actions for MOs For the Action list of all MOs, each MO corresponds to an Action, and its value can be Create-MOI, Modify-action and Delete-action. If the service request instruction message does not carry this parameter, the default is to execute Create-action.
  • Southbound interface protocol type its value can be CORBA-selected, SOAP-selected, RESTful-selected, and it identifies the protocol type of the southbound interface that the NMS hopes to select. This parameter is used as a reference when the Adaptor client selects the protocol adapter in the subsequent process. If the service request instruction message does not carry this parameter, the adaptor client selects the protocol adapter according to the default priority of the protocol type supported by the NE, that is, the adaptor client selects the protocol adapter according to the predefined southbound interface protocol type.
  • Action and MO have a one-to-one correspondence. If the service request instruction message involves multiple objects, the Action for each object needs to be specified.
  • Step 801 The SO determines the corresponding workflow based on the service request (configuration management) of the NMS, thereby triggering the execution of the corresponding service processing flow.
  • the SO obtains the identification (NE ID) of the network element targeted by the service request from the parameter list in step 800, and initiates a request to query AAI to confirm the registration status of the corresponding NE.
  • the network element may be the first network element involved in the embodiment shown in FIG. 2 or FIG. 3.
  • Workflow refers to a pre-defined business execution workflow, which can include all the functional modules that perform this business processing and the order in which the functional modules participate in the business processing.
  • the configuration management workflow is SO-AAI (execution information query confirmation)-Adaptor client( Perform MO template mapping, Adaptor selection)-protocol adapter (execute interface protocol conversion).
  • Step 802 The SO sends a network element registration status information query (NE onboarding status check) to the AAI to query and confirm whether the network element that needs to be operated has completed the online registration, and the network element registration status information query carries the network element identification (NE ID).
  • NE onboarding status check a network element registration status information query
  • Step 803 If the network element identified by the queried NE ID does not save the corresponding registration information in the AAI, the AAI returns the network element status as Unavailable, and the SO receives the return message and informs the NMS that the corresponding network element has not completed registration, and the process goes to This ends. If the network element identified by the queried NE ID has stored the corresponding registration information in the AAI, the AAI returns the relevant information of the network element, including NE ID, Correlation ID, OM IP and port. Correlation ID is the internal temporary identification of the PNF allocated by AAI when the PNF is registered. OM IP and port are sent to AAI when PNF is registered.
  • Step 804 SO calls the first configure API to initiate the configuration processing flow, and sends a configuration request to the Adaptor client, and sets the relevant parameters of step 800 and step 803, including MO and Attributes, Actions for MOs, and optionally also Correlation ID, OM There are multiple types of IP and port and southbound interface protocols.
  • the first configure API is the first interface involved in the embodiment shown in FIG. 2, and in this step, the first interface is an existing configured interface.
  • the related parameters include the southbound interface protocol type
  • the above steps are equivalent to the situation in which the SO sends the first information to the adapter client in the situation a1 involved in the embodiment shown in FIG. 2.
  • Step 805 The adaptor client receives the SO configuration request, and selects the corresponding protocol adapter based on the southbound interface protocol type.
  • the Adaptor client selects the protocol adapter according to the default priority of the protocol type supported by the NE (the preset Southbound interface protocol type). ) To select.
  • the protocol adapter selected by the adapter client here may be the first protocol adapter in the embodiment shown in FIG. 2 or FIG. 3.
  • Step 806 The adaptor client calls the second configure API to initiate interface adapter configuration processing, that is, forwards the configuration request to the selected protocol adapter.
  • step 806 is the operation b1 involved in the embodiment shown in FIG. 2 above.
  • the second configure API is the second interface involved in the embodiment shown in FIG. 2.
  • the second interface is the existing second interface that is multiplexed.
  • Step 807 The protocol adapter determines the operation processing for the corresponding MO based on the operation type (Action).
  • the protocol adapter performs default processing, that is, creating all MO objects.
  • Step 808 The protocol adapter performs the protocol format adaptation conversion according to the corresponding protocol, including operation conversion and parameter conversion.
  • the CORBA Adaptor will execute the Create_managed_object operation that converts the Create MO operation into CORBA.
  • Step 809 The protocol adapter calls the southbound interface API/SB API to send a corresponding configuration management instruction message to the address identified by the OMIP and the port identified by the port.
  • Step 810 The EMS receives an instruction to execute the configuration of the NE.
  • Step 811 After completing the NE configuration management processing, the EMS replies a response message to the protocol adapter, and includes the MO set by the EMS and its attribute parameters in the message.
  • Step 812 The protocol adapter receives the response message, converts the MO and its attribute parameters carried in step 811 into corresponding "name-value" pairs and sends it to the SO through the Adaptor client, and carries the Correlation ID and updated parameters.
  • Step 813 The SO updates the parameter information of the network element NE entity stored in the AAI, and carries the Correlation ID and updated parameters.
  • Fig. 9 shows another example of applying the communication method provided by the embodiment of the present application, and the scenario of this example is the same as the scenario of the example shown in Fig. 6.
  • the NRM MO template mapping process from parameter list to MO is implemented by the protocol adapter.
  • the NRM MO template mapping from parameter list to MO is performed by the Adaptor client.
  • the difference between the example shown in FIG. 9 and the example shown in FIG. 6 is that the functional modules that perform the NRM MO template mapping process are different, and other steps are similar.
  • the process of the example shown in FIG. 9 may specifically include the following steps:
  • Steps 900-905 similar to the above-mentioned step 600-step 605, the description refers to the above-mentioned step 600-step 605 description, which will not be detailed here.
  • Step 906 The Adaptor client sends an NRM template query request to the EMS/NE, requesting to obtain the NRM MO template supported by the NE.
  • the request message carries the NE ID and the NRM version.
  • the NRM version has no actual value and is only a parameter indication for Inform EMS/NE that they want to obtain NRM MO template.
  • the network equipment of the equipment vendor will not register the NRM MO template in the AAI when registering, then if the steps In 904, there is no NRM MO template parameter, so the Adaptor client needs to perform this step and the following step 907.
  • the Adaptor client when there is an EMS in the communication system, the Adaptor client sends an NRM template query request to the EMS, and the EMS forwards the NRM template query request to the NE; when there is no EMS in the communication system, the Adaptor client directly sends the NRM template query request to NE.
  • Step 907 The EMS/NE returns the NRM MO template (NRM MO template) of the requested NE to the Adaptor client, and the returned NRM MO template is the network resource object model corresponding to the corresponding version of the NRM modeling method supported by the NE (for example, a tree Shape structure model, including multiple MOs and the relationship between MOs (such as inheritance, etc.)).
  • NRM MO template NRM MO template
  • the network resource object model corresponding to the corresponding version of the NRM modeling method supported by the NE (for example, a tree Shape structure model, including multiple MOs and the relationship between MOs (such as inheritance, etc.)).
  • the NE when there is an EMS in the communication system, the NE sends the NRM MO template to the EMS, and then the EMS forwards the NRM MO template to the Adaptor client; when there is no EMS in the communication system, the NE directly sends the NRM MO template to the Adaptor client.
  • Step 908 The Adaptor client performs network resource management object template mapping.
  • the Adaptor client After the Adaptor client receives parameters such as NRM MO template, Parameter list, and Action id, it determines the MO type of network resource object that needs to be operated based on the Action id, and identifies the model attributes of the corresponding MO type based on the NRM MO template, and executes Parameter list(" Name-value") mapping to MO, that is, converting Parameter list into corresponding MO objects and attribute parameters.
  • the Adaptor determines the operation processing for the corresponding MO based on the Action. If no Action and Action id are included in step 900, the Adaptor client performs default processing, that is, all MO objects of the NRM MO template are created.
  • Step 909 The adaptor client determines the operation for each MO based on the Action parameter, and directly calls the interface API provided by the protocol coordinator to perform the operation on the MO, that is, sends the converted configuration request to the protocol adapter.
  • step 909 is the operation b2 involved in the embodiment shown in FIG. 2 above.
  • the interface API provided by the protocol coordinator is the second interface involved in the embodiment shown in FIG. 2, and in this step, the second interface is a multiplexed existing second interface.
  • Step 910 The protocol adapter performs the protocol format adaptation conversion according to the corresponding protocol, including operation conversion and parameter conversion.
  • the CORBA Adaptor will execute the Create_managed_object operation that converts the Create MO operation into CORBA.
  • Steps 911 to 912 similar to the above steps 611 to step 612, the description refers to the description of the above steps 611 to step 612, which will not be detailed here.
  • Step 913 After completing the configuration management processing of the NE, the EMS replies a response message to the protocol adapter, and includes the MO set by the EMS and its attribute parameters in the message.
  • Step 914 The protocol adapter receives the response message, performs the conversion of the corresponding protocol, and returns the MO and attribute parameters of the response message to the Adaptor Client. After receiving the response message, the Adaptor Client converts the MO and its attribute parameters carried in step 913 into The corresponding "name-value" pair is sent to the SO, carrying the Correlation ID and updated parameters.
  • Step 915 The SO updates the parameter information of the network element NE entity stored in the AAI, and carries the Correlation ID and updated parameters.
  • FIG. 10 shows another example of applying the communication method provided by the embodiment of the present application, and the scenario of this example is the same as that of the example shown in FIG. 9.
  • the interface calls between SO and Adaptor client are unified reuse of the Configure API that has been supported in the prior art, and the function module recognizes the function to be performed based on the analysis of the Action parameter. of.
  • the interface between SO and Adaptor client defines a variety of different APIs.
  • the function module determines the business processing functions that need to be executed based on the API type, such as create, modify, deploy site, etc., then in the function There is no need to pass Action parameters on the interface between modules.
  • the example process shown in Figure 10 may include the following steps:
  • Steps 1000-1003 similar to the above step 900 to step 903, the description refers to the description of the above step 900 to step 903, which will not be described in detail here.
  • Step 1004 SO based on the workflow definition, and calls the first API of the interface.
  • the deploy site API initiates the configuration processing process, and sends a configuration request to the Adaptor client, and sets the relevant parameters of step 1000 and step 1003, including Parameter list, optional It can also include one or more of the following: Correlation ID, OM IP and port, NRM MO template, Action id, and protocol type.
  • the interface API called in this step is the first interface involved in the embodiment shown in FIG. 2, and the first interface in this step is a newly defined interface.
  • Steps 1005-1008 similar to the above step 905 to step 908, the description refers to the description of the above step 905 to step 908, which will not be detailed here.
  • Step 1009 The adaptor client determines the operation for each MO based on the API type, and directly calls the second API provided by the protocol coordinator to perform the operation on the MO, that is, sends the converted configuration request to the protocol adapter.
  • step 1009 is the operation b2 involved in the embodiment shown in FIG. 2 above.
  • the interface API provided by the protocol coordinator is the second interface involved in the embodiment shown in FIG. 2.
  • the second interface is a newly defined second interface.
  • Steps 1010-1015 similar to the above steps 910 to 915, the description refers to the description of the above steps 910 to 915, which will not be detailed here.
  • Fig. 11 shows another example of applying the communication method provided by the embodiment of the present application, the scenario of this example and the scenario of the example shown in Figs. 9 and 10.
  • the NMS needs to display the type of operation object that needs to be operated through the Action id in the service request.
  • the SO, Adaptor client and the protocol coordinator The interface invocation is still the same as the example shown in Figure 9. It is to uniformly reuse the Configure API that has been supported in the prior art, and the NMS clearly indicates the management object MO that needs to be operated and its attribute settings in the service request, that is, the NMS is connected to the network.
  • the meta configuration parameters are not delivered as a parameter list/Parameter list in the form of "name-value" pairs, but are mapped into a series of corresponding MO and attribute parameters in the NMS, and at the same time specify the action for each MO, then Adaptor client does not need to perform management object MO mapping processing based on NRM MO template, and does not need to pass parameters such as Action id and NRM MO template on the interface between functional modules.
  • the flow of the example shown in FIG. 11 may include the following steps:
  • Steps 1100-1105 similar to the above-mentioned step 800-step 805, the description refers to the description of the above-mentioned step 800-step 805, which will not be detailed here.
  • Step 1106 The Adaptor client determines the operation processing for the corresponding MO based on Actions for MOs. If no Actions are included in step 1100, the Adaptor client performs default processing, that is, creates all MO objects.
  • Steps 1107-1113 similar to the above-mentioned steps 909-915, the description refers to the description of the above-mentioned steps 909-915, which will not be detailed here.
  • FIG. 12 shows an example of using the communication method provided by Hu Sili in this application.
  • the specific process of this example may include the following steps:
  • Step 1200 The NMS sends a service request instruction message (service request) to the SO.
  • the service request instruction message may include a related parameter list (Parameter list).
  • Parameter list a parameter list
  • it may also include one or more of the following: the requested operation type ( Action), operation object (Action id), southbound interface protocol type. among them:
  • Action Its value can be create-action, modify-action, and delete-action. If the service request instruction message does not carry this parameter, the default Action is to execute Create-action.
  • Action id It indicates the type of the operation object of the aforementioned Action, and the value can be NEfunction-type, cell-type, cell-relation-type, etc. If the service request instruction message does not carry this parameter, the aforementioned Action is for all operation objects by default.
  • Action id is defined according to the MO type abstracted by NMR modeling (that is, the MO type defined by NRM is the value range of Action id), such as 5G NR NRM MO includes GNBDUFunction, GNBCUFunction, new air interface cell (NRCell), and new air interface cell Neighbor Cell Relation (NRCellRelation), etc.
  • the value range of Action id includes GNBDUFunction-type, GNBCUFunction-type, NRCell-type, NRCellRelation-type, etc.
  • Parameter list the parameter data that the NMS needs to configure, in the form of a "name-value" pair format, which can specifically include the planning configuration data of the operator, such as network element identification (NE id), cell identification, and neighboring cell configuration relationships, Frequency setting, feature ID, cell identification for enabling features, etc.
  • NE id network element identification
  • cell identification cell identification
  • neighboring cell configuration relationships Frequency setting
  • feature ID cell identification for enabling features, etc.
  • Southbound interface protocol type its value can be CORBA-selected, SOAP-selected, RESTful-selected, and it identifies the protocol type of the southbound interface that the NMS hopes to select. This parameter is used as a reference when the Adaptor client selects the protocol adapter in the subsequent process. If the service request instruction message does not carry this parameter, the adaptor client selects the protocol adapter according to the default priority of the protocol type supported by the NE, that is, the adaptor client selects the protocol adapter according to the predefined southbound interface protocol type.
  • Action and Action id have a one-to-one correspondence. If the service request instruction message involves multiple operation objects, it involves the Action of each object.
  • Step 1201 The SO determines the corresponding workflow based on the business request of the NMS, thereby triggering the execution of the corresponding business processing flow.
  • the SO obtains the identification (NE ID) of the network element targeted by the service request from the parameter list in step 600, and initiates a request to query AAI to confirm the registration status of the corresponding NE.
  • the network element may be the first network element involved in the embodiment shown in FIG. 2 or FIG. 3.
  • Workflow refers to a pre-defined business execution workflow, which can include all the functional modules that perform this business processing and the execution sequence of the functional modules participating in the business processing.
  • the configuration management workflow is SO-AAI (execution information query confirmation)-protocol adapter ( Perform interface protocol conversion).
  • Step 1202 The SO sends a network element registration status information query (NE onboarding status check) to the AAI to query to confirm whether the network element that needs to be operated has completed the online registration, and the network element registration status information query carries the network element identification (NE ID).
  • NE onboarding status check a network element registration status information query
  • this step can also be used to query whether a network element (such as a base station) supports a certain service feature (such as an MLB feature), that is, to query AAI to confirm whether the AAI entiy attribute of the corresponding network element includes MLB-related attributes Deployment parameter configuration. If so, the MLB feature is supported, otherwise it is not supported.
  • a network element such as a base station
  • a certain service feature such as an MLB feature
  • Step 1203 If the network element identified by the queried NE ID does not save the corresponding registration information in the AAI, the AAI returns the network element status as Unavailable, and the SO receives the return message and informs the NMS that the corresponding network element has not completed registration , The process ends here. If the network element identified by the queried NE ID has stored corresponding registration information in the AAI, the AAI returns the relevant information of the network element, including NE ID, Correlation ID, OM IP and port, NRM MO template. Correlation ID is the internal temporary identification of the PNF allocated by AAI when the PNF is registered. OM IP and port and NRM MO template are sent to AAI when PNF is registered.
  • Step 1204 The SO calls the first configuration application programming interface (configure API) to initiate the configuration processing flow, and sends a configuration request to the protocol adapter, and sends the relevant parameters of step 1200 and step 1203 to the protocol adapter, where the relevant parameters include Parameter list Optional also include one or more of the following: Correlation ID, OM IP and port, NRM MO template, Action, Action id, Southbound interface protocol type.
  • Step 1205 The protocol adapter sends an NRM template query request to the EMS/NE, requesting to obtain the NRM MO template supported by the NE.
  • the request message carries the NE ID and the NRM version (version).
  • the NRM version has no actual value and is only a parameter indication , Used to inform EMS/NE that they want to obtain NRM MO template.
  • step 1206 the protocol adapter needs to perform this step and the following step 1206.
  • the protocol adapter when there is an EMS in the communication system, the protocol adapter sends an NRM template query request to the EMS, and the EMS forwards the NRM template query request to the NE; when there is no EMS in the communication system, the protocol adapter directly sends the NRM template query request to NE.
  • Step 1206 The EMS/NE returns the requested NE’s NRM MO template (NRM MO template) to the protocol adapter.
  • NRM MO template is the network resource object model corresponding to the corresponding version of the NRM modeling method supported by the NE (for example, a tree Shape structure model, including multiple MOs and the relationship between MOs (such as inheritance, etc.)).
  • the NE when there is an EMS in the communication system, the NE sends the NRM MO template to the EMS, and then the EMS forwards the NRM MO template to the protocol adapter; when there is no EMS in the communication system, the NE directly sends the NRM MO template to the protocol adapter.
  • Step 1207 The protocol adapter performs network resource management object template mapping.
  • the protocol adapter determines the type of network resource object MO that needs to be operated based on the Action id, and identifies the model attributes of the corresponding MO type based on the NRM MO template, and executes Parameter list(" Name-value") mapping to MO, that is, converting Parameter list into corresponding MO objects and attribute parameters.
  • the protocol adapter determines the operation processing for the corresponding MO based on the Action. If no Action and Action id are included in step 1200, the protocol adapter performs default processing, that is, creating all MO objects of the NRM MO template.
  • Step 1208 The protocol adapter performs the protocol format adaptation conversion according to the corresponding protocol, including operation conversion and parameter conversion.
  • CORBA Adaptor will execute the Create_managed_object operation that converts the Create MO operation into CORBA.
  • Step 1209 The protocol adapter calls the southbound interface API/SB API to send a corresponding configuration management instruction message to the address identified by the OMIP and the port identified by the port.
  • Step 1210 The EMS receives the instruction to execute the configuration of the NE.
  • Step 1211 After completing the NE configuration management processing, the EMS replies a response message to the protocol adapter, and includes the MO set by the EMS and its attribute parameters in the message.
  • Step 1212 The protocol adapter receives the response message, converts the MO and its attribute parameters carried in step 1211 into corresponding "name-value" pairs and sends it to the SO, and carries the Correlation ID and updated parameters.
  • Step 1213 The SO updates the parameter information of the network element NE entity stored in the AAI, and carries the Correlation ID and updated parameters.
  • FIG. 12 is only one of the specific examples when there is only one protocol adapter in the communication system, and there may be other examples, for example, the examples shown in FIGS. 6 to 11 above Deformation, here is not detailed description one by one.
  • each solution of the communication method provided by the embodiments of the present application is introduced from the perspective of each functional module or device itself and the interaction between each functional module or device.
  • each functional module or device such as the above-mentioned adapter client and the first protocol adapter, in order to realize the above-mentioned functions, includes hardware structures and/or software modules corresponding to each function.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the communication device may include an acquisition module 1301 and a processing module 1302, and optionally may also include a sending module 1303.
  • the acquisition module may also be a receiving module; when the acquisition module is used to acquire information or data stored locally in the communication device, the acquisition module is also It can be a processing module.
  • the communication device shown in FIG. 13 may be used to perform the operations of the adapter client in the embodiments shown in FIGS. 2 to 4 and 6 to 11 above.
  • the obtaining module 1301 is used to obtain the southbound interface protocol type; the adapter client is used to manage two or more protocol adapters;
  • the processing module 1302 is configured to select a first protocol adapter from two or more protocol adapters according to the southbound interface protocol type, and the first protocol adapter is used to implement the first protocol.
  • the obtaining module 1301 is specifically used to: when obtaining the southbound interface protocol type:
  • the first information is received from the service coordinator, the first information is used to request network configuration for the first network element, the first information is a configuration parameter in the form of a name-value pair, and the first information includes the southbound interface protocol type; Obtain the southbound interface protocol type from the information; or, obtain the preset southbound interface protocol type.
  • the acquiring module 1301 when the acquiring module 1301 receives the first information from the service coordinator, it is specifically configured to:
  • the first information sent by the service coordinator calling the first interface is received from the service coordinator; wherein, the first interface is provided by the adapter client.
  • the communication device further includes a sending module 1303;
  • the sending module 1303 is configured to send the first information to the first protocol adapter after the acquiring module receives the first information from the service coordinator; or, the processing module 1302 is also configured to determine the second information according to the first information; the sending module 1303 is configured to The second information is sent to the first protocol adapter; the second information is the management object and its object attributes; the second information is obtained by mapping the first information based on the network resource management object template.
  • the sending module 1303 when sending the first information to the first protocol adapter, is specifically configured to call the second interface provided by the first protocol adapter to send the first information to the first protocol adapter.
  • the sending module 1303 when sending the second information to the first protocol adapter, is specifically configured to call the second interface provided by the first protocol adapter to send the second information to the first protocol adapter.
  • the sending module 1303 is further configured to send a network resource model template query request to the first network element; the acquiring module 1301 is also configured to receive a network resource object model of the first network element from the first network element.
  • the acquiring module 1301 is further configured to receive third information from the first protocol adapter, and the third information includes the name and identification of the first protocol adapter, and the supported protocol type; the processing module 1302 is also configured to receive third information based on the third information The adapter client locally creates context information; the sending module 1303 is also used to send fourth information to the first protocol adapter, and the fourth information is used to notify the first protocol adapter of the registration result.
  • the first protocol adapter is a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • the communication device provided in the embodiment of the present application may further include a receiving module 1401, a processing module 1402, and a sending module 1403, as shown in FIG. 14 Schematic.
  • the communication device shown in FIG. 14 may be used to perform the operations of the first protocol adapter in the embodiments shown in FIG. 2 and FIG. 3, and may be used to perform the operations shown in FIGS. 4 and 6 to 12 The operation of the protocol adapter in the embodiment.
  • the receiving module 1401 is configured to receive first information, where the first information is a configuration parameter in the form of a name-value pair; the first information is a configuration parameter for network configuration of the first network element; the first protocol adapter is used to implement the first protocol;
  • the processing module 1402 is configured to determine second information according to the first information, the second information is the management object and its object attributes; the second information is obtained by mapping the first information based on the network resource management object template;
  • the sending module 1403 is configured to send the second information to the first network element.
  • the receiving module 1401 when receiving the first information, is specifically configured to receive the first information from an adapter client, which is used to manage two or more protocol adapters; or, to receive the first information from a service coordinator.
  • the receiving module 1401 when receiving the first information from the adapter client, is specifically configured to: receive the first information sent by the adapter client calling the second interface, the second interface being the first protocol adapter which provided.
  • the receiving module 1401 when receiving the first information from the service coordinator, is specifically configured to receive the first information sent by the service coordinator invoking the second interface.
  • the sending module 1403 is further configured to send a network resource model template query request to the first network element; the receiving module 1401 is also configured to receive a network resource object model of the first network element from the first network element.
  • the sending module 1403 is also used to send third information to the adapter client, and the third information includes the name and identification of the first protocol adapter, and the supported protocol type; the receiving module 1401 is also used to send third information from the adapter client The fourth information is received, and the fourth information is used to notify the registration result of the first protocol adapter.
  • the first protocol adapter may be a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • the division of units or modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • the communication device may include a communication interface 1501 and a processor 1502, and optionally may also include a memory 1503, as shown in FIG. 15 Structure diagram.
  • the processor 1502 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP, or the like.
  • the processor 1502 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL generic array logic
  • the communication interface 1501 and the processor 1502 are connected to each other.
  • the communication interface 1501 and the processor 1502 are connected to each other through a bus 1504;
  • the bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. .
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only a thick line is used in FIG. 15, but it does not mean that there is only one bus or one type of bus.
  • the memory 1503 is coupled with the processor 1502 and is used to store necessary programs for the communication device.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1503 may include RAM, or may also include non-volatile memory, such as at least one disk memory.
  • the processor 1502 executes the application program stored in the memory 1503 to realize the function of the communication device.
  • the communication device shown in FIG. 15 may be used to perform the operations of the adapter client in the embodiments shown in FIGS. 2 to 4 and 6 to 11 above.
  • the communication interface 1501 is used to obtain the protocol type of the southbound interface; the adapter client is used to manage two or more protocol adapters;
  • the processor 1502 is configured to select a first protocol adapter from two or more protocol adapters according to the southbound interface protocol type, and the first protocol adapter is used to implement the first protocol.
  • the communication interface 1501 acquires the protocol type of the southbound interface, it is specifically used to:
  • the first information is received from the service coordinator, the first information is used to request network configuration for the first network element, the first information is a configuration parameter in the form of a name-value pair, and the first information includes the southbound interface protocol type; Obtain the southbound interface protocol type from the information; or, obtain the preset southbound interface protocol type.
  • the communication interface 1501 when the communication interface 1501 receives the first information from the service coordinator, it is specifically used to:
  • the first information sent by the service coordinator calling the first interface is received from the service coordinator; wherein, the first interface is provided by the adapter client.
  • the communication interface 1501 is further configured to send the first information to the first protocol adapter after receiving the first information from the service coordinator; or the processor 1502 is further configured to determine the second information according to the first information Information; the communication interface 1501 is also used to send second information to the first protocol adapter; the second information is the management object and its object attributes; the second information is obtained by mapping the first information based on the network resource management object template.
  • the communication interface 1501 when the communication interface 1501 sends the first information to the first protocol adapter, it is specifically configured to call the second interface provided by the first protocol adapter to send the first information to the first protocol adapter.
  • the communication interface 1501 when the communication interface 1501 sends the second information to the first protocol adapter, it is specifically configured to call the second interface provided by the first protocol adapter to send the second information to the first protocol adapter.
  • the communication interface 1501 is further configured to send a network resource model template query request to the first network element, and receive the network resource object model of the first network element from the first network element.
  • the communication interface 1501 is further configured to receive third information from the first protocol adapter, and the third information includes the name and identifier of the first protocol adapter, and the supported protocol type; the processor 1502 is also configured to receive third information based on the third information
  • the adapter client locally creates context information; the communication interface 1501 is also used to send fourth information to the first protocol adapter, and the fourth information is used to notify the first protocol adapter of the registration result.
  • the first protocol adapter may be a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • the communication device shown in FIG. 15 may be used to perform the operations of the first protocol adapter in the embodiments shown in FIG. 2 and FIG. 3, and may be used to perform the operations shown in FIGS. 4 and 6 to 12 The operation of the protocol adapter in the embodiment.
  • the communication interface 1501 is used to receive first information, the first information is a configuration parameter in the form of a name-value pair; the first information is a configuration parameter for network configuration of the first network element; the first protocol adapter is used to implement the first protocol;
  • the processor 1502 is configured to determine second information according to the first information, the second information is a management object and its object attributes; the second information is obtained by mapping the first information based on a network resource management object template;
  • the communication interface 1501 is also used to send second information to the first network element.
  • the communication interface 1501 when the communication interface 1501 receives the first information, it is specifically used to receive the first information from the adapter client, which is used to manage two or more protocol adapters; or, to receive the first information from the service coordinator.
  • the adapter client which is used to manage two or more protocol adapters; or, to receive the first information from the service coordinator.
  • the communication interface 1501 when the communication interface 1501 receives the first information from the adapter client, it is specifically used to: receive the first information sent by the adapter client calling the second interface, the second interface being the first protocol adapter which provided.
  • the communication interface 1501 when the communication interface 1501 receives the first information from the service coordinator, it is specifically configured to receive the first information sent by the service coordinator invoking the second interface.
  • the communication interface 1501 is further configured to send a network resource model template query request to the first network element, and receive the network resource object model of the first network element from the first network element.
  • the communication interface 1501 is also used to send third information to the adapter client, and the third information includes the name and identifier of the first protocol adapter, and the supported protocol type; the communication interface 1501 is also used to send the adapter client The fourth information is received, and the fourth information is used to notify the registration result of the first protocol adapter.
  • the first protocol adapter may be a CORBA adapter, a SOAP adapter, or a RESTful adapter.
  • the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Abstract

一种通信方法及装置，用以为实现ONAP适配3GPP配置管理功能来选择合适的适配器。该方法为：适配器客户端获取南向接口协议类型，并根据所述南向接口协议类型在两个或者两个以上协议适配器中选择第一协议适配器，第一协议适配器用于实现第一协议；适配器客户端用于管理两个或者两个以上协议适配器，这样在ONAP的南向接口增加适配3GPP配置管理协议的接口适配器时，可以通过适配器客户端灵活选择合适的适配器，从而实现ONAP和3GPP业务管理对接。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2019年07月26日提交中国专利局、申请号为201910683991.0、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的配置管理基础是网络资源管理对象(managed object，MO)。目前，3GPP标准上针对不同的无线网元(如基站等)定义了网络资源模型(network resource model，NRM)建模方法和MO类型。网络管理系统(network management system，NMS)发送给网元管理系统(element management system，EMS)或网元(network element，NE)的配置参数都是以MO为基础进行封装并发送的。配置管理就是通过对NRM MO的一系列操作，实现网元的相关网络参数设置(如创建MO)，同时可实现对已部署网元的维护管理，如配置参数修改(修改MO)、查询(查询MO及MO属性)等。目前，3GPP标准定义了NMS和EMS之间的接口Itf-N的配置管理(configuration management，CM)支持公共对象请求代理结构(common object request Broker architecture，CORBA)、简单对象访问协议(simple object access protocol，SOAP)和REST表征状态转移(representational state transfer，RESTFul)协议处理。
为了构建统一的网络管理基础架构(开放网络自动化平台(open network automation platform，ONAP)+3GPP服务和系统工作组(services&systems aspects，SA)5)，ONAP需支持3GPP定义的标准接口和NRM建模机制，才可能实现网络的配置管理。但是，目前，ONAP南向接口不支持当前3GPP标准定义的Itf-N接口支持的CORBA、SOAP和RESTFul协议处理，若要构建统一的网络管理基础架构(ONAP+3GPP SA5)，ONAP不能实现和3GPP业务管理对接。
发明内容
本申请提供一种通信方法及装置，用以为实现ONAP适配3GPP配置管理功能来选择合适的适配器，从而实现ONAP和3GPP业务管理对接。
第一方面，本申请提供了一种通信方法，该方法可以包括：适配器客户端获取南向接口协议类型，并根据南向接口协议类型在两个或者两个以上协议适配器中选择第一协议适配器；适配器客户端用于管理两个或者两个以上协议适配器；第一协议适配器用于实现第一协议。
通过上述方法，为了实现ONAP适配3GPP配置管理功能，在ONAP的南向接口增加适配3GPP配置管理协议的接口适配器(如CORBA adaptor、SOAP adaptor和RESTFul  adaptor等)时，可以通过适配器客户端灵活选择合适的适配器，从而实现ONAP和3GPP业务管理对接。
在一个可能的设计中，适配器客户端获取南向接口协议类型，具体方法可以为：适配器客户端从服务协调器接收第一信息，第一信息用于请求为第一网元进行网络配置，第一信息为名值对形式的配置参数，第一信息中包括南向接口协议类型；适配器客户端从第一信息中获取南向接口协议类型；或者，适配器客户端获取预设的南向接口协议类型。
通过上述方法，适配器客户端可以准确地获取到南向接口协议类型，以使后续选择合适的协议适配器。
在一个可能的设计中，适配器客户端从服务协调器接收第一信息的具体方法可以为：适配器客户端从服务协调器接收服务协调器调用第一接口发送的第一信息；其中，第一接口为适配器客户端提供的。其中，第一接口可以复用现有的接口，也可以为新定义的接口。
通过上述方法，适配器客户端可以准确地从服务协调器接收到第一信息。
在一个可能的设计中，适配器客户端从服务协调器接收第一信息之后，还可能执行以下操作：适配器客户端向第一协议适配器发送第一信息；或者，适配器客户端根据第一信息确定第二信息，并向第一协议适配器发送第二信息；第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的。
通过上述方法，可以后续使第一协议适配器通过第一信息进行网络资源管理对象模板映射，或者适配器客户端直接将转换好的第二信息发给第一协议适配器。
在一个可能的设计中，当适配器客户端向第一协议适配器发送第一信息时，具体方法可以为：适配器客户端调用第一协议适配器提供的第二接口向第一协议适配器发送第一信息；当适配器客户端向第一协议适配器发送第二信息时，具体方法可以为：适配器客户端调用第一协议适配器提供的第二接口向第一协议适配器发送第二信息。其中，第二接口可以复用现有的接口或者是新定义的接口。
通过上述方法，适配器客户端可以准确地向第一协议适配器发送相应的信息。
在一个可能的设计中，适配器客户端向第一网元发送网络资源模型模板查询请求，并从第一网元接收第一网元的网络资源对象模型。这样可以使适配器客户端后续进行网络资源管理对象模板映射。
在一个可能的设计中，适配器客户端从第一协议适配器接收第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；适配器客户端根据第三信息在适配器客户端本地创建上下文信息；适配器客户端向第一协议适配器发送第四信息，第四信息用于通知第一协议适配器注册结果。
通过上述方法，适配器客户端可以准确地管理第一协议适配器，以使准确地选择出第一协议适配器为当前业务合适的协议适配器。
在一个可能的设计中，第一协议适配器可以为CORBA适配器、SOAP适配器或者RESTful适配器等。
第二方面，本申请提供了一种通信方法，该方法可以包括：第一协议适配器接收第一信息，并根据第一信息确定第二信息，然后向第一网元发送第二信息；其中，第一信息为名值对形式的配置参数；第一信息是为第一网元进行网络配置的配置参数；第一协议适配器用于实现第一协议；第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的。通过上述方法，可以实现ONAP和3GPP业务管理的对接。
在一个可能的设计中，第一协议适配器接收第一信息的具体方法可以为：第一协议适配器从适配器客户端接收第一信息，适配器客户端用于管理两个或者两个以上协议适配器；或者，第一协议适配器从服务协调器接收第一信息。
通过上述方法，第一协议适配器可以准确地获取到第一信息。
在一个可能的设计中，当第一协议适配器从适配器客户端接收第一信息时，具体方法可以为：第一协议适配器接收适配器客户端调用第二接口发送的第一信息，第二接口为第一协议适配器提供的；当第一协议适配器从服务协调器接收第一信息时，具体方法可以为：第一协议适配器接收服务协调器调用第二接口发送的第一信息。第二接口可以复用现有的接口，也可以是新定义的接口。
通过上述方法，第一协议适配器可以准取地获取到第一信息。
在一个可能的设计中，第一协议适配器向第一网元发送网络资源模型模板查询请求，并从第一网元接收第一网元的网络资源对象模型。这样可以使第一协议适配器后续进行网络资源管理对象模板映射。
在一个可能的设计中，第一协议适配器向适配器客户端发送第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；第一协议适配器从适配器客户端接收第四信息，第四信息用于通知第一协议适配器注册结果。
通过上述方法，可以使适配器客户端准确地管理第一协议适配器，以使后续准确地选择出第一协议适配器为当前业务合适的协议适配器。
在一种可能的设计中，第一协议适配器可以为CORBA适配器、SOAP适配器或者RESTful适配器等。
第三方面，本申请还提供了一种通信装置，该通信装置具有实现上述第一方面方法实例中适配器客户端的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述通信装置的结构中包括获取模块和处理模块，可选的还可以包括发送模块，这些模块可以执行上述第一方面方法示例中的相应功能，参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括通信接口和处理器，可选的还可以包括存储器，所述通信接口用于收发数据，以及与通信系统中的其他设备进行通信交互，所述处理器被配置为支持适配器客户端执行上述第一方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第四方面，本申请还提供了一种通信装置，该通信装置具有实现上述第二方面方法实例中第一协议适配器的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述通信装置的结构中包括接收模块、处理模块和发送模块，这些模块可以执行上述第二方面方法示例中的相应功能，参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括通信接口和处理器，可选的还可以包括存储器，所述通信接口用于收发数据，以及与通信系统中的其他设备进行通信交互，所述处理器被配置为支持第一协议适配器执行上述第二方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第五方面，本申请还提供了一种通信系统，所述通信系统可以包括上述设计中提及的适配器客户端、第一协议适配器等。
第六方面，本申请还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述任一种方法。
第七方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一种方法。
第八方面，本申请还提供了一种芯片系统，该芯片系统包括处理器，用于支持上述通信装置实现上述方面中所涉及的功能。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存通信装置必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
附图说明
图1为本申请提供的一种通信系统的架构示意图；
图2为本申请提供的一种通信方法的流程图；
图3为本申请提供的另一种通信方法的流程图；
图4为本申请提供的一种协议适配器注册的流程图；
图5为本申请提供的一种网元注册的流程图；
图6为本申请提供的一种通信方法的示例的流程图；
图7为本申请提供的另一种通信方法的示例的流程图；
图8为本申请提供的另一种通信方法的示例的流程图；
图9为本申请提供的另一种通信方法的示例的流程图；
图10为本申请提供的另一种通信方法的示例的流程图；
图11为本申请提供的另一种通信方法的示例的流程图；
图12为本申请提供的另一种通信方法的示例的流程图；
图13为本申请提供的一种通信装置的结构示意图；
图14为本申请提供的另一种通信装置的结构示意图；
图15为本申请提供的一种通信装置的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种通信方法及装置，用以为实现ONAP适配3GPP配置管理功能来选择合适的适配器。其中，本申请所述方法和装置基于同一发明构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
1)、适配器客户端(adaptor client)，是本申请新提出的一种至少具有适配器管理功能的设备，例如，可以进行适配器的注册和去注册等；所述适配器客户端管理两个或者两个以上的协议适配器，可以根据需要选择合适的协议适配器。
2)、协议适配器，可以实现3GPP接口协议功能，例如可以实现CORBA协议、SOAP 协议和RESTFul协议等的处理；相应的，所述协议适配器可以包括CORBA adaptor、SOAP adaptor和RESTFul adaptor等。
3)、在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的通信方法及装置进行详细说明。
图1示出了本申请实施例提供的通信方法适用的一种可能的通信系统的架构，通信系统可以是ONAP和3GPP业务管理对接的网络。示例性的，通信系统的架构中可以包括策略管理功能模块(policy)、服务协调器(service orchestrator，SO)、可用存量管理功能实体(available and active inventory，AAI)、ONAP优化功能模块(ONAP optimization function，OOF)、数据收集和分析功能模块(data collection,analytics,and events，DCAE)、适配器客户端(adaptor client)、多个协议适配器、网元管理系统(element management system，EMS)/网元(network element，NE)。其中：
policy，用于进行ONAP的策略管理。
SO可以接收NMS的业务请求，触发相应的工作流(workflow)处理流程，并向Adaptor client发送业务处理请求。
AAI，主要包含存量以及其之间拓扑关系的实时视图的功能，和事件订阅、通知、数据审计、数据版本等管理功能。
OOF，负责网络功能优化，如物理小区标识(physical cell identifier，PCI)优化等。
DCAE，用于数据收集和分析等。
adaptor client，用于管理适配器，例如，进行适配器的注册和去注册等，可以根据是需求选择合适的适配器；可选的，adaptor client还可以进行NRM网络资源对象模板映射。
多个协议适配器，包括多个支持不同协议的适配器，例如，Netconf adaptor、Ansible adaptor、Chef adaptor、CORBA adaptor、SOAP adaptor和RESTFul adaptor等。其中，CORBA adaptor、SOAP adaptor和RESTFul adaptor为支持3GPP协议的协议适配器，可以实现3GPP接口协议功能。
EMS，用于管理通信系统中的网元，也即EMS用于管理NE。
NE，为通信系统中需要进行配置网络等的网元，以实现相应的业务。
需要说明的是，通信系统中可以同时存在EMS和NE，也可以只存在NE，其中，EMS和NE可以支持Netconf、Ansible、Chef、CORBA、SOAP和RESTFul等中的一种或多种协议。
需要说明的是，除了上述列举的协议适配器，通信系统还可以基于场景和需要扩展支持其他更多的协议。
以上各个设备、功能模块或功能实体等，既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，本申请对比不作限定。
需要说明的是，图1所示的通信系统的架构中不限于仅包含图中所示的设备，还可以包含其它未在图中表示的设备，本申请在此处不再一一列举。
需要说明的是，本申请实施例并不限定各个设备的分布形式，图1所示的分布形式只是示例性的，本申请不作限定。
需要说明的是，本申请中设备的名称仅仅是一种示例，在未来的系统中可以叫其他名称，但是在功能上是一样的，本申请对涉及的设备的名称不做限定。
本申请实施例提供的一种通信方法，适用于如图1所示的通信系统。参阅图2所示，该方法的具体流程包括：
步骤201、适配器客户端获取南向接口协议类型；适配器客户端用于管理两个或者两个以上协议适配器。
步骤202、适配器客户端根据南向接口协议类型在两个或者两个以上协议适配器中选择第一协议适配器，第一协议适配器用于实现第一协议。
例如，适配器客户端管理的协议适配器可以是CORBA适配器、SOAP适配器或者RESTful适配器等等适配器中的两个或者两个以上。
相应的，适配器客户端选择的第一协议适配器可以为CORBA适配器、SOAP适配器、RESTful适配器等中的一个。例如，当第一协议适配器为CORBA适配器时，第一协议适配器可以实现的第一协议即为CORBA；当然第一协议适配器为其他适配器时情况类似，此处不再一一列举。
在一种可选的实施方式中，适配器客户端获取南向接口协议类型，可能有两种情况，例如：
情况a1、适配器客户端可以从服务协调器接收第一信息，第一信息用于请求为第一网元进行网络配置，第一信息为名值对形式的配置参数，第一信息中包括南向接口协议类型；适配器客户端可以从第一信息中获取南向接口协议类型。例如，名值对(key-value)形式可以为参数的名称-标识对的形式，例如基站-标识(identity，ID)、小区(cell)-ID、CU-ID、DU-ID等等。
示例性的，第一信息中还包括配置的参数数据(parameter list)，以及还可能包括以下信息中的一种或多种：关联标识(correlation ID)、第一网元的对应的管理面IP地址和端口(OM IP and port)、网络资源管理对象模板(NRM MO template)、操作类型(action)、操作对象(action id)等。其中correlation ID是物理网络功能网元(physical network function，PNF)(这里也即第一网元)注册时，AAI分配的PNF的内部临时标识。OM IP and port和NRM MO template是PNF注册时发送给AAI的，例如，网元注册流程后续结合图5进一步描述。
情况a2、适配器客户端获取预设的南向接口协议类型，其中预设的南向接口协议类型也可以认为是默认的南向接口协议类型。
例如，适配器客户端从服务协调器接收第一信息时，具体方法可以为：适配器客户端从服务协调器接收服务协调器调用第一接口发送的第一信息；其中，第一接口为适配器客户端提供的。其中，第一接口可以是复用现有的接口，例如现有的配置应用程序编程接口(configure(application programming interface，API))，还可以是新定义的接口。
在一种具体的实施方式中，适配器客户端从服务协调器接收第一信息之后，适配器客户端可以执行一下两种操作中的一种：
操作b1、适配器客户端向第一协议适配器发送第一信息。
操作b2、适配器客户端根据第一信息确定第二信息，并向第一协议适配器发送第二信息；第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的。其中，对象属性即为描述管理对象的性质的参数或参数集合，例如基站的地 理位置等；网络资源管理对象模板中包含了一个或者多个管理对象及其对象属性的对应关系，第一信息基于网络资源管理对象模板映射时，具体的是根据第一信息中的名值对确定相应的网络资源管理对象模板中包括的管理对象及对应的对象属性，然后将网络资源管理对象模板中包括的管理对象及相应的对象属性确定为第二信息。例如，第一信息为基站-ID时，网络资源管理对象模板中会包括基站相关的一个或者多个管理对象和这一个或多个管理对象的对象属性，然后将这一个或多个管理对象及其对象属性确定为第二信息。
例如，适配器客户端根据网络资源管理对象模板将第一信息映射成第二信息。
具体实现时，第一协议适配器提供第二接口，以使适配器客户端通过调用第二接口向第一协议适配器发送信息，例如：
适配器客户端向第一协议适配器发送第一信息时，适配器客户端调用第一协议适配器提供的第二接口向第一协议适配器发送第一信息；
或者，适配器客户端向第一协议适配器发送第二信息时，适配器客户端调用第一协议适配器提供的第二接口向第一协议适配器发送第二信息。
具体实现时，第二接口可以是现有已有的接口，也可以是新定义的接口。
在一种可选的实施方式中，当第一信息中不包括NRM MO template时，适配器客户端还可以执行如下操作：适配器客户端向第一网元发送网络资源模型模板查询请求，并从第一网元接收第一网元的网络资源对象模型。其中，网络资源对象模型即为网络资源管理对象模板，在本申请中这两个描述可以互换。
示例性的，当通信系统中有管理第一网元的网元管理系统时，适配器客户端向第一网元发送网络资源模型模板查询请求时，是通过网元管理系统向第一网元发送的，例如：适配器客户端先向网元管理系统发送网络资源模型模板查询请求，然后网元管理系统向第一网元发送网络资源模型模板查询请求；相应地，第一网元接收第一网元的网络资源对象模型时，例如：第一网元向网元管理系统发送网络资源对象模型，然后网元管理系统向适配器客户端发送网络资源对象模型。
当通信系统中没有网元管理系统时，适配器客户端直接向第一网元发送网络资源模型模板查询请求，并直接从第一网元接收第一网元的网络资源对象模型。
在具体实施时，适配器客户端管理协议适配器需协议适配器先注册到适配器客户端，例如，第一协议适配器的注册过程可以为：适配器客户端从第一协议适配器接收第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；适配器客户端根据第三信息在适配器客户端本地创建上下文信息；适配器客户端向第一协议适配器发送第四信息，第四信息用于通知第一协议适配器注册结果。其中，第一协议适配器的名称可以为第一协议适配器的实际命名，第一协议适配器的标识可以为第一协议适配器的编码或编号等(例如ID等)。需要说明的是，名称和标识也可以是同一个概念，两者可以用其中一个表示第一协议适配器，此时，名称或者概念可以包含上述描述中的名称和标识的各个举例。
例如，任一个协议适配器的注册过程均与第一协议适配器注册的构成相似，具体的可以参见图4所示的协议适配器的注册流程中的描述。
采用本申请实施例提供的通信方法，适配器客户端获取南向接口协议类型；适配器客户端根据南向接口协议类型在两个或者两个以上协议适配器中选择第一协议适配器，第一协议适配器用于实现第一协议。通过上述方法，为了实现ONAP适配3GPP配置管理功能，在ONAP的南向接口增加适配3GPP配置管理协议的接口适配器(如CORBA adaptor、SOAP  adaptor和RESTFul adaptor等)时，可以通过适配器客户端灵活选择合适的适配器，从而实现ONAP和3GPP业务管理对接。
本申请实施例还提供了一种通信方法，参阅图3所示，该方法的流程可以包括：
步骤301、第一协议适配器接收第一信息，第一信息为名值对形式的配置参数；第一信息是为第一网元进行网络配置的配置参数；第一协议适配器用于实现第一协议。
步骤302、第一协议适配器根据第一信息确定第二信息，第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的。
步骤303、第一协议适配器向第一网元发送第二信息。
例如，第一协议适配器根据网络资源管理对象模板将第一信息映射成第二信息。
示例性的，第一信息包括的内容可以参见图2所示的实施例中第一信息的描述，此处不再详细描述。
例如，第一协议适配器为CORBA适配器、SOAP适配器或者RESTful适配器等等。
在一种可选的实施方式中，第一协议适配器接收第一信息，具体可以分为以下两种情况：
情况c1、第一协议适配器从适配器客户端接收第一信息，适配器客户端用于管理两个或者两个以上协议适配器。
情况c1对应上述图2所示的实施例中适配器客户端执行操作b1的情况。在这种情况中，第一协议适配器是被适配器客户端所管理的。
情况c2、第一协议适配器从服务协调器接收第一信息。
在情况c2中，可能的场景可以是通信系统中只存在第一协议适配器，而没有其它适配器，此时，通信系统中可以不设置适配器客户端；当然也可以设置适配器客户端，当设置了适配器客户端时，适配器客户端只管理第一协议适配器。
在一种可选的实施方式中，第一协议适配器提供第二接口，以使其他设备调用第二接口向第一协议适配器发送信息，例如：
当第一协议适配器从适配器客户端接收第一信息时，第一协议适配器接收适配器客户端调用第二接口发送的第一信息，第二接口为第一协议适配器提供的；
当第一协议适配器从服务协调器接收第一信息时，第一协议适配器接收服务协调器调用第二接口发送的第一信息。
具体实现时，第二接口可以是现在已有的接口，也可以是新定义的接口。
在一种可选的实施方式中，当第一信息中不包括NRM MO template时，第一协议适配器还执行如下操作：第一协议适配器向第一网元发送网络资源模型模板查询请求，并从第一网元接收第一网元的网络资源对象模型。
示例性的，当通信系统中有管理第一网元的网元管理系统时，第一协议适配器向第一网元发送网络资源模型模板查询请求时，是通过网元管理系统向第一网元发送的，例如：第一协议适配器先向网元管理系统发送网络资源模型模板查询请求，然后网元管理系统向第一网元发送网络资源模型模板查询请求；相应地，第一网元接收第一网元的网络资源对象模型时，例如：第一网元向网元管理系统发送网络资源对象模型，然后网元管理系统向第一协议适配器发送网络资源对象模型。
当通信系统中没有网元管理系统时，第一协议适配器直接向第一网元发送网络资源模型模板查询请求，并直接从第一网元接收第一网元的网络资源对象模型。
具体实施时，当第一协议适配器被适配器客户端管理时，第一协议适配器需要先向适配器客户端注册，具体过程可以包括：第一协议适配器向适配器客户端发送第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；第一协议适配器从适配器客户端接收第四信息，第四信息用于通知第一协议适配器注册结果。示例性的，第一协议适配器的注册流程可以参见图4的过程。
采用本申请实施例提供的通信方法，第一协议适配器接收第一信息，第一信息为名值对形式的配置参数；第一信息是为第一网元进行网络配置的配置参数；第一协议适配器用于实现第一协议；第一协议适配器根据第一信息确定第二信息，第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的；第一协议适配器向第一网元发送第二信息。通过上述方法，可以实现ONAP和3GPP业务管理的对接。
基于以上实施例的描述，当通信系统中设置了适配器客户端管理协议适配器时，需要协议适配器注册到适配器客户端。实际中，适配器的类型有多种，且不同的Adaptor支持不同的协议功能，如CORBA adaptor、SOAP adaptor、RESTFul Adaptor等。因此，当每个Adaptor部署成功后，Adaptor需将其属性能力信息(如支持的协议类型等新)发送给Adaptor Client中，由Adaptor Client统一管理接口相应的Adaptors，那么后续在网络配置管理过程中，Adaptor Client可基于Adaptor的能力选择合适的适配器。反之，当Adaptor适配器下线，通过相关流程删除Adaptor Client中保存的响应Adaptor信息。例如，图4示出了协议适配器上线后的注册流程，例如，该流程可以包括：
步骤401、协议适配器基于ONAP当前的功能模块部署机制ONAP操作管理功能(ONAP operations manager，OOM)完成上线部署。
步骤402、协议适配器向适配器客户端发送适配器上线通知消息。
例如，任一个协议适配器(xx Adaptor)部署时，会配置管理这个协议适配器的适配器客户端(Adaptor Client)的信息(如适配器客户端的IP地址(Adaptor client IP address)等)，协议适配器上电后，即可向配置的Adaptor client IP address标示的Adaptor client发送适配器上线通知消息，该适配器上线通知消息携带该协议适配器的名称(Adaptor name)、协议适配器的标示(Adaptor ID)和支持的协议类型(Adaptor type)，其中，Adaptor ID可以是其IP address、编号等能够唯一标识和识别该协议适配器的ID。Adaptor type取值可以是CORBA、SOAP、RESTful(未来扩展支持了其他协议类型，该参数取值也需扩展支持相应的协议)等。
例如，当协议适配器为上述第一协议适配器时，上线通知消息即为上述图2或图3所示的实施例中涉及的第三信息。
步骤403、适配器客户端接收协议适配器的上线通知消息后，在适配器客户端本地为该协议适配器创建相应的上下文记录，并保存其对应的属性能力信息(即步骤402中发送的参数信息)。
步骤404、适配器客户端完成协议适配器的信息注册记录后，向协议适配器回复适配器上线通知确认消息，确认注册结果。
其中，结果(result)取值可以是注册接受(Registration-accept)、注册拒绝(Registration-reject)、错误(Error)等。
例如，当协议适配器为上述第一协议适配器时，上线通知确认消息即为上述图2或图3所示的实施例中涉及的第四信息。
需要说明的是，上述步骤402和步骤403中的消息仅仅是一种示例，还可以是其他功能相同的消息，例如，上线通知消息可以替换为适配器注册请求(Adaptor register request)等，以及上线通知确定消息可以替换为适配器注册回复(Adaptor register response)等。
通过上述注册流程，由Adaptor client统一管理部署上线的协议适配器，可以在后续业务处理流程(如配置管理)中，适配器客户端即可结合NE支持的协议类型等信息选择适配的协议适配器。通过上述流程，Adaptor client能够及时获得部署上线的协议适配器及其属性能力信息，便于后续能够选择到合适的协议适配器，从而实现ONAP和3GPP业务管理对接。
基于以上实施例，当为一个网元实现网络配置时，需要结合该网元支持的接口协议选择合适的协议适配器。但是在实际中，由于不同设备商的网络设备(网元)可能只支持一种接口协议(如CORBA协议)，也可能支持多种的接口协议(如即支持CORBA协议，也支持SAOP协议)。而且不同设备商的网络设备支持不同的NRM模板可能会不同，如A设备商的产品支持R1版本的NRM模型，B设备商的产品支持R2版的NRM模型，那么按照不同版本的NRM模型的网络资源对象是不通的，如按照R1版本的NRM模型，网络设备可建模成5个MO，而若按照R2版本的NRM模型，则网络设备可建模成10个MO。因此为了准确获取网络设备的这些属性能力信息，网络设备，如物理网络功能网元(Physical Network Function，PNF)部署后需将其属性能力通知给ONAP的相应功能模块(如AAI)保存。例如，图5示出了一种PNF的注册流程，该流程具体可以包括如下步骤：
步骤500：PNF上电后，完成初始配置和IP地址获取。
其中，步骤500中会获取ONAP的管理面IP地址和端口。
步骤501：PNF向步骤500中获取的ONAP的管理面IP地址和端口标识的管理面功能模块(如DCAE)发送PNF注册请求消息。
例如，在PNF注册请求消息中新增PNF支持的协议类型参数(取值可以是CORBA、SOAP、RESTful等)、PNF支持的NRM MO template和PNF的管理面IP及端口。
在现有技术中，该消息可以是以虚拟化网络功能事件流((Virtual network function，VNF)event streaming，VES)event形式上报给DCAE的。其中，NRM MO template即表示PNF支持的相应版本NRM建模方法对应的网络资源对象模型(例如，一种树形结构的模型，包括多个MO以及MO之间的关系(如继承等))。PNF支持的协议类型取值可以是仅支持CORBA(CORBA-only)、仅支持SOAP(SOAP-only)、仅支持RESTful(RESTful-only)、支持CORBA和SOAP(CORBA and SOAP supported)、支持RESTful和SOAP(RESTful and SOAP supported)、支持CORBA和RESTful(CORBA and RESTful supported)、全部支持(Full-supported)。如果PNF同时支持多种协议，则会指定优选的协议，如PNF支持的协议类型取值是CORBA and RESTful supported，并指定首选CORBA(CORBA preferred)或CORBA具有选择的高优先级(CORBA with high-priority selected)。
步骤502：DCAE解析PNF注册请求消息，获取PNF注册请求消息中包含的参数信息，并向PRH发送注册事件消息，将步骤501中新增的参数信息一起发送给PRH。
步骤503：PRH通知AAI为新注册的PNF创建相应的AAI实体(entity)，并将PNF的参数信息发送给AAI。
步骤504：AAI为PNF创建AAI实体，为其分配内部标识Correlation ID，并保存其属性参数信息。
其中，属性参数信息可以包括PNF支持的协议类型参数、PNF支持的NRM MO template和PNF的管理面IP及端口参数。
步骤505：ONAP功能模块执行PNF配置。
在一种可选的实施方式中，如果ONAP的功能模块(如AAI)中已经配置了不同版本对应的NRM网络资源模型，则在步骤501中，PNF即不需将其支持的NRM MO template包括在PNF注册请求消息中，只需将其支持的NRM版本号(如NRM Version)注册到DCAE中即可(那么后续业务处理过程中，ONAP功能模块基于NRM version就可查询到对应的NRM MO模型)，因此步骤501、502、503中应该包括的新增参数包括PNF支持的协议类型参数、PNF支持的NRM version和PNF的管理面IP及端口。
当PNF为上述实施例涉及的第一网元时，则上述流程是第一网元的注册流程，相关参数为第一网元的参数。
进一步地，当PNF的能力信息(如支持的NRM版本或NRM MO template升级)发生变化时，PNF需要更新注册的信息，在更新流程中，PNF向DCAE发送VES event，并将更新的信息一并发送给DCAE，DCAE向PRH发送更新请求，进而PRH更新AAI中保存的PNF信息，详细流程和图5描述的注册流程类似，只是步骤502、503、504的名称不同。消息中只携带必要的标识(如PNF ID)和更新的参数。具体的流程可以参见上述注册流程，此处不再详细描述。
下面图6-图11的实施例，分别是基于以上实施例，在NMS通过ONAP的功能模块实现NE网元的配置管理流程(例如，管理对象创建、修改和删除等管理流程)中采用本申请实施例提供的通信方法的示例。例如，在以下的示例中，可用存量管理功能实体以AAI为例进行说明，服务协调器以SO为例进行说明，第一网元以NE为例进行说明，网元管理系统以EMS为例进行说明等等。例如，以下示例可以适用于开站场景对NE的初始配置管理、网络运营维护场景或业务特性(如移动性负载均衡(mobility load balancing，MLB)、载波聚合(carrier aggregation，CA)等特性)开通场景对NE配置参数修改和删除NE的配置参数等管理流程。其中：开站场景是指开站过程实际就是对新建网络设备(也即NE，例如基站)执行基本参数配置，使其能够进行业务处理；业务特性开通场景是指：通常情况下，业务特性的部署数据(如该业务特性对应的MO及其属性)都会在建站是和开站数据一起导入EMS/NE系统，那么业务特性开通的主要功能是通过修改业务特性相关管理对象的属性参数，使其支持该特性的业务处理，如MLB特性开通需要修改MLB相关MO的属性参数设置，例如打开MLB算法开关、设置开通MLB特性的小区标识等，从而使基站支持MLB处理。
图6示出了在SO收到NMS的业务请求，基于请求参数确定需要执行的业务工作流(workflow)，并调度相应的适配器客户端(Adaptor client)和协议适配器执行配置处理过程中，应用本申请实施例提供的通信方法的一种示例，该示例的流程具体可以包括如下步骤：
步骤600：NMS向SO发送业务请求指令消息(service request)，业务请求指令消息中可以相关的参数列表(Parameter list)，可选的，还可以包括以下一种或多种：请求的操作类型(Action)、操作对象(Action id)、南向接口协议类型。其中：
Action：其取值可以是创建操作(create-action)、修改操作(modify-action)和删除操作(delete-action)。若该业务请求指令消息中没有携带该参数时，则默认Action是执行 Create-action。
Action id：其表示前述Action的操作对象类型，取值可以是NEfunction-type、小区类型(cell-type)、小区邻区关系类型(Cell Relation-type)等。若该业务请求指令消息中没有携带该参数，则默认前述Action是针对所有操作对象。Action id遵循NMR建模抽象的MO类型进行定义(即NRM定义的MO类型即为Action id的取值范围)，如5G NR的NRM MO包括基站分布式单元功能((gNodeB，GNB)(distributed unit，DU)Function)、GNB集中单元(central unit，CU)Function、新空口小区(NRCell)、新空口小区邻区关系(NRCellRelation)等，则Action id取值范围包括GNBDUFunction-type、GNBCUFunction-type、NRCell-type、NRCellRelation-type等。
Parameter list：是NMS需要配置的参数数据，其形式是“名-值”对的格式，具体可以包括运营商的规划配置数据，如网元标识(NE id)，小区标识，邻区配置关系，频点设置，特性ID，开通特性的小区标识等。
南向接口协议类型：其取值可以是CORBA-selected、SOAP-selected、RESTful-selected，其标识NMS希望选用的南向接口的协议类型。该参数用于后续流程中Adaptor client选择协议适配器时参考。若该业务请求指令消息中，没有携带该参数，则Adaptor client选择协议适配器时按照NE支持的协议类型的默认优先级进行选择，也即Adaptor client根据预先定义的南向接口协议类型选择协议适配器。
其中，Action和Action id是一一对应的，若业务请求指令消息涉及多个操作对象，则涉及每种对象的Action。
步骤601：SO基于NMS的业务请求确定相应的工作流(workflow)，从而触发执行相应的业务处理流程。
首先，SO从步骤600的parameter list参数中获取到该业务请求针对的网元的标识(NE ID)，并发起向AAI查询确认相应NE的注册状态的请求。其中，该网元可以为图2或图3所示的实施例中涉及的第一网元。
workflow是指预先定义的业务执行工作流，可以包括执行这种业务处理的所有功能模块和功能模块参与业务处理的执行顺序，如配置管理workflow是SO—AAI(执行信息查询确认)—Adaptor client(执行MO模板映射、Adaptor选择)—协议适配器(执行接口协议转换)。
步骤602：SO向AAI发送网元注册状态信息查询(NE onboarding status check)，查询确认需要操作的网元是否已完成上线注册，网元注册状态信息查询中携带网元标识(NE ID)。
在一种实施方式中，该步骤还可用于查询网元(例如基站)是否支持某个业务特性(如MLB特性)，即向AAI查询确认对应网元的AAI entiy的属性中是否包括MLB相关的部署参数配置。若有，则支持MLB特性，否则不支持该特性。
步骤603：若查询的NE ID标识的网元在AAI中没有保存相应注册信息，则AAI返回网元状态为不可用(Unavailable)，SO收到该返回消息，通知NMS相应的网元未完成注册，则流程到此结束。若查询的NE ID标识的网元在AAI中已保存相应注册信息，则AAI返回该网元的相关信息，包括NE ID、Correlation ID、OM IP and port、NRM MO template。其中Correlation ID是PNF注册时，AAI分配的PNF的内部临时标识。OM IP and port和NRM MO template是PNF注册时发送给AAI的。
步骤604：SO调用第一配置应用程序编程接口(configure API)发起配置处理流程，并向Adaptor client发送配置请求，将步骤600和步骤603的相关参数发送给Adaptor client，其中，相关参数包括Parameter list，可选的还包括以下一种或多种：Correlation ID、OM IP and port、NRM MO template、Action、Action id、南向接口协议类型。
例如，第一configure API即为图2所示的实施例中涉及的第一接口，在该步骤中第一接口为现有的配置的接口。
当相关参数中包含了南向接口协议类型时，上述步骤等同于图2所示的实施例中涉及的情况a1中SO向适配器客户端发送第一信息的情况。
步骤605：Adaptor client接收到SO的配置请求后，基于南向接口协议类型选择相应的协议适配器。
例如，当步骤604配置请求中包含南向接口协议类型，则直接使用，没有携带该参数，则Adaptor client选择协议适配器时按照NE支持的协议类型的默认优先级(预设的南向接口协议类型)进行选择。
此处适配器客户端选择的协议适配器可以为图2或图3所示的实施例中的第一协议适配器。
步骤606：Adaptor client调用第二configure API发起接口适配器配置处理，也即向选择的协议适配器转发配置请求。
例如，步骤606即为上述图2所示的实施例中涉及的操作b1。
其中，第二configure API即为图2所示的实施例中涉及的第二接口，在此步骤中，第二接口为复用的现有已有的第二接口。
步骤607：协议适配器向EMS/NE发送NRM模板查询请求，请求获取NE支持的NRM MO template，请求消息中携带NE ID和NRM版本(version)，其中NRM version无实际取值，仅是一个参数指示，用于告知EMS/NE希望获取NRM MO template。
需要说明的是，若设备商采用私有化NRM MO且不希望ONAP等感知其NRM建模方法，则该设备商的网络设备在注册时就不会将NRM MO template注册到AAI中，那么在步骤603和606中就没有NRM MO template参数，则协议适配器需执行该步骤以及后边的步骤608。
例如，当通信系统中有EMS时，则协议适配器向EMS发送NRM模板查询请求，EMS将NRM模板查询请求转发给NE；当通信系统中没有EMS时，则协议适配器直接将NRM模板查询请求发送给NE。
步骤608：EMS/NE向协议适配器返回请求的NE的NRM MO模板(NRM MO template)，返回的NRM MO template是NE支持的相应版本NRM建模方法对应的网络资源对象模型(例如，一种树形结构的模型，包括多个MO以及MO之间的关系(如继承等))。
相应地，当通信系统中有EMS时，则NE将NRM MO template发送给EMS，然后EMS向协议适配器转发NRM MO template；当通信系统中没有EMS时，则NE直接向协议适配器发送NRM MO template。
步骤609：协议适配器进行网络资源管理对象模板映射。
例如，协议适配器收到NRM MO template、Parameter list和Action id等参数后，基于Action id确定需要操作的网络资源对象MO类型，并基于NRM MO template识别相应MO类型的模型属性，执行Parameter list(“名-值”)向MO的映射，即将Parameter list转换为 对应的MO对象和属性参数。协议适配器基于Action确定针对相应MO的操作处理。若步骤600中没有包括Action和Action id，则协议适配器执行默认处理，即创建NRM MO template的所有MO对象。
步骤610：协议适配器按照对应协议执行协议格式适配转换，包括操作转换和参数转换，如CORBA Adaptor会执行将Create MO操作转化为CORBA的创建对象操作Create_managed_object，详细的转换处理参考3GPP现有标准的处理，本申请不再详细描述转换过程。
步骤611：协议适配器调用南向接口API/SB API向OM IP标识的地址和port标识的端口发送相应的配置管理指令消息。
步骤612：EMS收到指令执行NE的配置。
步骤613：EMS完成NE的配置管理处理后，向协议适配器回复响应消息，并将EMS设置的MO及其属性参数包含的在消息中。
步骤614：协议适配器接收到响应消息，向SO发送参数信息，包括将步骤613携带的MO及其属性参数转换成相应的“名-值”对的形式的参数，并携带Correlation ID和更新参数(updated parameters)。
步骤615：SO更新AAI中保存的网元NE实体的参数信息，携带Correlation ID和updated parameters。
在一种可选的实施方式中，上述示例的步骤602和603，可由Adaptor client执行，即SO完成步骤601的处理，直接向Adaptor client发起配置管理，即执行步骤604，此时步骤604中仅包括NE ID、南向接口协议类型、Parameter list、Action、Action id。那么Adaptor client收到步骤604后，执行上述步骤602和603中的操作，获取Correlation ID、OM IP and port、NRM MO template等信息，也即Adaptor client向AAI发送网元注册状态信息查询，然后接收返回消息，然后Adaptor client再执行后续步骤。相应地，后续图7和图8所示的示例中涉及到的相应的操作类似。本申请此处不再一一展开详细描述。
图7示出了另一种应用本申请实施例提供的通信方法的一种示例，该示例的场景与图6所示的示例的场景相同。其中，在图6所示的实施例中，SO、Adaptor client和协议适配器之间的接口调用都是统一重用现有技术中已支持的Configure API，功能模块识别需要执行的功能是基于对Action参数的解析才感知的；而图7所示的示例在SO、Adaptor client和xx Adaptor之间的接口定义多种不同的API，功能模块基于API类型判断需要执行的业务处理功能，如创建(create)、修改(modify)、开站(deploy site)等，那么在功能模块之间的接口上就不需要传递Action参数了。下面图7以开站场景(需执行创建MO)为例进行描述，图7所示的示例的流程可以包括以下步骤：
步骤700-703：与上述步骤600-步骤603类似，描述参考上述步骤600-步骤603的描述，此处不再详述。
步骤704：SO基于工作流(workflow)定义，并调用第一API，如deploy site API发起配置处理流程，并向Adaptor client发送配置请求，并将步骤700和步骤703的相关参数，包括Parameter list，可选的还包括以下一项或多项：Correlation ID、OM IP and port、NRM MO template、Action id、南向接口协议类型发送给Adaptor client。
其中，此步骤中调用的接口API即为图2所示的实施例中涉及的第一接口，在该步骤中第一接口为新定义的接口。
当相关参数中包含了南向接口协议类型时，上述步骤等同于图2所示的实施例中涉及的情况a1中SO向适配器客户端发送第一信息的情况。
步骤705：Adaptor client接收到SO的配置请求(例如开站配置请求)，并基于南向接口协议类型选择相应的协议适配器。
若步骤704中，配置请求中包含南向接口协议类型，则直接使用，没有携带该参数，则Adaptor client选择协议适配器时按照NE支持的协议类型的默认优先级(预设的南向接口协议类型)进行选择。
步骤706：Adaptor client基于步骤704的API类型(deploy site是开站)确定需要执行创建对象，则调用第二API，如create API发起接口适配器配置处理，也即向选择的协议适配器转发配置请求。
例如，步骤706即为上述图2所示的实施例中涉及的操作b1。
其中，第二API图2所示的实施例中涉及的第二接口，在此步骤中，第二接口为新定义的第二接口。
步骤707-708：与上述步骤607-步骤608类似，描述参考上述步骤607-步骤608的描述，此处不再详述。
步骤709：协议适配器进行网络资源管理对象模板映射。
例如，协议适配器收到NRM MO template、Parameter list和Action id等参数后，基于Action id确定需要操作的网络资源对象MO类型，并基于NRM MO template识别相应MO类型的模型属性，执行Parameter list(“名-值”)向MO的映射，即将Parameter list转换为对应的MO对象和属性参数。Adaptor基于步骤706的API类型确定针对相应MO的操作处理，如Create。若步骤700中没有包括Action和Action id，则协议适配器执行默认处理，即创建NRM MO template的所有MO对象。
步骤710-715：与上述步骤610-步骤615类似，描述参考上述步骤610-步骤615的描述，此处不再详述。
图8示出了另一种应用本申请实施例提供的通信方法的一种示例，该示例场景与图6和图7所示的示例相同。在图6和图7所示的示例中，NMS在业务请求中需通过Action id显示指示需要操作的操作对象的类型，而图8所示的示例中，SO、Adaptor client和协议适配器之间的接口调用还是和图6所示的示例一样，都是统一重用现有技术中已支持的Configure API，并且，NMS在业务请求明确指示需要操作的管理对象MO及其属性设置，即NMS对网元的配置参数不是以“名-值”对形式的参数列表(Parameter list)往下发，而是在NMS就映射成相应的一系列MO及属性参数，同时指明针对每个MO的操作Action，那么协议适配器也不需要基于NRM MO template执行管理对象MO映射处理，且在功能模块之间的接口上就不需要传递Action id、NRM MO template等参数。例如，图8所示的示例的流程可以包括以下步骤：
步骤800：NMS在业务请求前就完成网络资源管理对象映射处理，确定了需要操作的管理对象MO及其属性参数，然后NMS再向SO发送业务请求指令消息。
可选的，业务请求指令消息中可以包括管理对象及其属性参数(MO and Attributes)；还可以包括Actions for MOs、南向接口协议类型中一种或多种。其中：
MO and Attributes：本次业务处理需要操作的具体的网络资源管理对象(如5G NR MO：GNBDUFunction、GNBCUFunction、NRCell、NRCellRelation等)，Attributes是每个MO 的属性参数，如GNBDUFunction MO的属性参数包括gNBDUId、gNBDUName、gNBId、gNBIdLength，NRCell MO的属性参数包括nCI、pLMNIdList等。
Actions for MOs：针对所有MO的Action列表，每个MO对应一个Action，其取值可以是Create-MOI，Modify-action和Delete-action。若该业务请求指令消息中没有携带该参数，则默认是执行Create-action。
南向接口协议类型：其取值可以是CORBA-selected、SOAP-selected、RESTful-selected，其标识NMS希望选用的南向接口的协议类型。该参数用于后续流程中Adaptor client选择协议适配器时参考。若该业务请求指令消息中，没有携带该参数，则Adaptor client选择协议适配器时按照NE支持的协议类型的默认优先级进行选择，也即Adaptor client根据预先定义的南向接口协议类型选择协议适配器。
其中，Action和MO是一一对应的，若业务请求指令消息涉及多个对象，则需指明针对每种对象的Action。
步骤801：SO基于NMS的业务请求(配置管理)确定相应的workflow，从而触发执行相应的业务处理流程。
首先，SO从步骤800的parameter list参数中获取到该业务请求针对的网元的标识(NE ID)，并发起向AAI查询确认相应NE的注册状态的请求。其中，该网元可以为图2或图3所示的实施例中涉及的第一网元。
workflow是指预先定义的业务执行工作流，可以包括执行这种业务处理的所有功能模块和功能模块参与业务处理的执行顺序，如配置管理workflow是SO—AAI(执行信息查询确认)—Adaptor client(执行MO模板映射、Adaptor选择)—协议适配器(执行接口协议转换)。
步骤802：SO向AAI发送网元注册状态信息查询(NE onboarding status check)，查询确认需要操作的网元是否已完成上线注册，网元注册状态信息查询中携带网元标识(NE ID)。
步骤803：若查询的NE ID标识的网元在AAI中没有保存相应注册信息，则AAI返回网元状态为Unavailable，SO收到该返回消息，通知NMS相应的网元未完成注册，则流程到此结束。若查询的NE ID标识的网元在AAI中已保存相应注册信息，则AAI返回该网元的相关信息，包括NE ID、Correlation ID、OM IP and port。其中Correlation ID是PNF注册时，AAI分配的PNF的内部临时标识。OM IP and port是PNF注册时发送给AAI的。
步骤804：SO调用第一configure API发起配置处理流程，并向Adaptor client发送配置请求，将步骤800和步骤803的相关参数，包括MO and Attributes、Actions for MOs，可选的还包括Correlation ID、OM IP and port、南向接口协议类型中的一种多种。
例如，第一configure API即为图2所示的实施例中涉及的第一接口，在该步骤中第一接口为现有已配置的接口。
当相关参数中包含了南向接口协议类型时，上述步骤等同于图2所示的实施例中涉及的情况a1中SO向适配器客户端发送第一信息的情况。
步骤805：Adaptor client接收到SO的配置请求，基于南向接口协议类型选择相应的协议适配器。
例如，当步骤804配置请求中包含南向接口协议类型，则直接使用，没有携带该参数，则Adaptor client选择协议适配器时按照NE支持的协议类型的默认优先级(预设的南向接 口协议类型)进行选择。
此处适配器客户端选择的协议适配器可以为图2或图3所示的实施例中的第一协议适配器。
步骤806：Adaptor client调用第二configure API发起接口适配器配置处理，也即向选择的协议适配器转发配置请求。
例如，步骤806即为上述图2所示的实施例中涉及的操作b1。
其中，第二configure API图2所示的实施例中涉及的第二接口，在此步骤中，第二接口为复用的现在已有的第二接口。
步骤807：协议适配器基于操作类型(Action)确定针对相应MO的操作处理。
例如，若步骤800中没有包括Action，则协议适配器执行默认处理，即创建所有MO对象。
步骤808：协议适配器按照对应协议执行协议格式适配转换，包括操作转换和参数转换，如CORBA Adaptor会执行将Create MO操作转化为CORBA的创建对象操作Create_managed_object，详细的转换处理参考3GPP现有标准的处理，本申请不再详细描述转换过程。
步骤809：协议适配器调用南向接口API/SB API向OM IP标识的地址和port标识的端口发送相应的配置管理指令消息。
步骤810：EMS收到指令执行NE的配置。
步骤811：EMS完成NE的配置管理处理后，向协议适配器回复响应消息，并将EMS设置的MO及其属性参数包含的在消息中。
步骤812：协议适配器接收到响应消息，将步骤811携带的MO及其属性参数转换成相应的“名-值”对的形式通过Adaptor client发送给SO，并携带Correlation ID和updated parameters。
步骤813：SO更新AAI中保存的网元NE实体的参数信息，携带Correlation ID和updated parameters。
图9示出了另一种应用本申请实施例提供的通信方法的一种示例，该示例的场景和图6所示的示例的场景相同。在图6所示的示例，执行parameter list到MO的NRM MO模板映射处理是由协议适配器实现的，而在图9所示的示例中，由Adaptor client来执行parameter list到MO的NRM MO模板映射。图9所示的示例和图6所示的示例的区别在于执行NRM MO模板映射处理的功能模块不同，其他步骤类似，例如，图9所示的示例的流程具体可以包括以下步骤：
步骤900-905：与上述步骤600-步骤605类似，描述参考上述步骤600-步骤605的描述，此处不再详述。
步骤906：Adaptor client向EMS/NE发送NRM模板查询请求，请求获取NE支持的NRM MO template，请求消息中携带NE ID和NRM version，其中NRM version无实际取值，仅是一个参数指示，用于告知EMS/NE希望获取NRM MO template。
需要说明的是，若设备商采用私有化NRM MO且不希望ONAP等感知其NRM建模方法，则该设备商的网络设备在注册时就不会将NRM MO template注册到AAI中，那么若步骤904中就没有NRM MO template参数，则Adaptor client需执行该步骤以及后边的步骤907。
例如，当通信系统中有EMS时，则Adaptor client向EMS发送NRM模板查询请求，EMS将NRM模板查询请求转发给NE；当通信系统中没有EMS时，则Adaptor client直接将NRM模板查询请求发送给NE。
步骤907：EMS/NE向Adaptor client返回请求的NE的NRM MO模板(NRM MO template)，返回的NRM MO template是NE支持的相应版本NRM建模方法对应的网络资源对象模型(例如，一种树形结构的模型，包括多个MO以及MO之间的关系(如继承等))。
相应地，当通信系统中有EMS时，则NE将NRM MO template发送给EMS，然后EMS向Adaptor client转发NRM MO template；当通信系统中没有EMS时，则NE直接向Adaptor client发送NRM MO template。
步骤908：Adaptor client进行网络资源管理对象模板映射。
例如，Adaptor client收到NRM MO template、Parameter list和Action id等参数后，基于Action id确定需要操作的网络资源对象MO类型，并基于NRM MO template识别相应MO类型的模型属性，执行Parameter list(“名-值”)向MO的映射，即将Parameter list转换为对应的MO对象和属性参数。Adaptor基于Action确定针对相应MO的操作处理。若步骤900中没有包括Action和Action id，则Adaptor client执行默认处理，即创建NRM MO template的所有MO对象。
步骤909：Adaptor client基于Action参数确定了针对每个MO的操作，直接调用协议协调器提供的接口API执行对MO的操作，也即向协议适配器发送转换后的配置请求。
例如，创建MO(CreateMO)，若需要执行对多个MO的操作处理，则需调用多次/多种接口API，如需创建3个MO，则需调用3次CreateMO API，如要创建1个MO，修改两个MO，则需调用1次CreateMO API，2次ModifyMO API。
例如，步骤909即为上述图2所示的实施例中涉及的操作b2。
其中，协议协调器提供的接口API即为图2所示的实施例中涉及的第二接口，在此步骤中，第二接口为复用的现在已有的第二接口。
步骤910：协议适配器按照对应协议执行协议格式适配转换，包括操作转换和参数转换，如CORBA Adaptor会执行将Create MO操作转化为CORBA的创建对象操作Create_managed_object，详细的转换处理参考3GPP现有标准的处理，本申请不再详细描述转换过程。
步骤911-912：与上述步骤611-步骤612类似，描述参考上述步骤611-步骤612的描述，此处不再详述。
步骤913：EMS完成NE的配置管理处理后，向协议适配器回复响应消息，并将EMS设置的MO及其属性参数包含的在消息中。
步骤914：协议适配器接收到响应消息，执行相应协议的转换，并将响应消息的MO及属性参数返回给Adaptor Client，Adaptor Client接收到响应消息后，将步骤913携带的MO及其属性参数转换成相应的“名-值”对的形式发送给SO，携带Correlation ID和updated parameters。
步骤915：SO更新AAI中保存的网元NE实体的参数信息，携带Correlation ID和updated parameters。
图10示出了另一种应用本申请实施例提供的通信方法的一种示例，该示例的场景与图9所示的示例的场景相同。其中，在图9所示的示例中，SO和Adaptor client之间的接 口调用都是统一重用现有技术中已支持的Configure API，功能模块识别需要执行的功能是基于对Action参数的解析才感知的。而图10所示的示例中，在SO和Adaptor client之间的接口定义多种不同的API，功能模块基于API类型判断需要执行的业务处理功能，如create、modify、deploy site等，那么在功能模块之间的接口上就不需要传递Action参数了，例如，图10所示的示例的流程可以包括以下步骤：
步骤1000-1003：与上述步骤900-步骤903类似，描述参考上述步骤900-步骤903的描述，此处不再详述。
步骤1004：SO基于workflow定义，并调用接口第一API，如deploy site API发起配置处理流程，并向Adaptor client发送配置请求，并将步骤1000和步骤1003的相关参数，包括Parameter list，可选的还可以包括以下一项或多项：Correlation ID、OM IP and port、NRM MO template、Action id、协议类型。
其中，此步骤中调用的接口API即为图2所示的实施例中涉及的第一接口，在该步骤中第一接口为新定义的接口。
步骤1005-1008：与上述步骤905-步骤908类似，描述参考上述步骤905-步骤908的描述，此处不再详述。
步骤1009：Adaptor client基于API类型确定了针对每个MO的操作，直接调用协议协调器提供的第二API执行对MO的操作，也即向协议适配器发送转换后的配置请求。
例如，如创建MO/CreateMO，若需要执行对多个MO的操作处理，则需调用多次/多种接口API，如需创建3个MO，则需调用3次CreateMO API，如要创建1个MO，修改两个MO，则需调用1次CreateMO API，2次ModifyMO API。
例如，步骤1009即为上述图2所示的实施例中涉及的操作b2。
其中，协议协调器提供的接口API即为图2所示的实施例中涉及的第二接口，在此步骤中，第二接口为新定义的第二接口。
步骤1010-1015：与上述步骤910-步骤915类似，描述参考上述步骤910-步骤915的描述，此处不再详述。
图11示出了另一种应用本申请实施例提供的通信方法的一种示例，该示例的场景和图9和图10所示的示例的场景。在图9和图10所示的示例中，NMS在业务请求中需通过Action id显示指示需要操作的操作对象的类型，在图11所示的示例中，SO、Adaptor client和协议协调器之间的接口调用还是和图9所示的示例一样，都是统一重用现有技术中已支持的Configure API，并且，NMS在业务请求明确指示需要操作的管理对象MO及其属性设置，即NMS对网元的配置参数不是以“名-值”对形式的参数列表/Parameter list往下发，而是在NMS就映射成相应的一系列MO及属性参数，同时指明针对每个MO的操作Action，那么Adaptor client就不需要基于NRM MO template执行管理对象MO映射处理，且在功能模块之间的接口上就不需要传递Action id、NRM MO template等参数。例如，图11所示的示例的流程可以包括以下步骤：
步骤1100-1105：与上述步骤800-步骤805类似，描述参考上述步骤800-步骤805的描述，此处不再详述。
步骤1106：Adaptor client基于Actions for MOs确定针对相应MO的操作处理。若步骤1100中没有包括Actions，则Adaptor client执行默认处理，即创建所有MO对象。
步骤1107-1113：与上述步骤909-步骤915类似，描述参考上述步骤909-步骤915的 描述，此处不再详述。
在实际中，有一种情况下，通信系统中可以只有一个协议适配器，该协议适配器可以满足业务需求，在这种情况下，可以不需要适配器客户端的存在，也即不需要适配器客户端去选择合适的协议适配器。此时，在上述示例中涉及到协议客户端的操作可以忽略，或者可以由协议适配器直接执行。以一个具体的示例来详细描述，例如，图12示出了采用本申请是胡思里提供的通信方法的一中示例，该示例的具体的流程可以包括以下步骤：
步骤1200：NMS向SO发送业务请求指令消息(service request)，业务请求指令消息中可以相关的参数列表(Parameter list)，可选的，还可以包括以下一种或多种：请求的操作类型(Action)、操作对象(Action id)、南向接口协议类型。其中：
Action：其取值可以是创建操作(create-action)、修改操作(modify-action)和删除操作(delete-action)。若该业务请求指令消息中没有携带该参数时，则默认Action是执行Create-action。
Action id：其表示前述Action的操作对象类型，取值可以是NEfunction-type、小区类型(cell-type)、小区邻区关系类型(Cell Relation-type)等。若该业务请求指令消息中没有携带该参数，则默认前述Action是针对所有操作对象。Action id遵循NMR建模抽象的MO类型进行定义(即NRM定义的MO类型即为Action id的取值范围)，如5G NR的NRM MO包括GNBDUFunction、GNBCUFunction、新空口小区(NRCell)、新空口小区邻区关系(NRCellRelation)等，则Action id取值范围包括GNBDUFunction-type、GNBCUFunction-type、NRCell-type、NRCellRelation-type等。
Parameter list：是NMS需要配置的参数数据，其形式是“名-值”对的格式，具体可以包括运营商的规划配置数据，如网元标识(NE id)，小区标识，邻区配置关系，频点设置，特性ID，开通特性的小区标识等。
南向接口协议类型：其取值可以是CORBA-selected、SOAP-selected、RESTful-selected，其标识NMS希望选用的南向接口的协议类型。该参数用于后续流程中Adaptor client选择协议适配器时参考。若该业务请求指令消息中，没有携带该参数，则Adaptor client选择协议适配器时按照NE支持的协议类型的默认优先级进行选择，也即Adaptor client根据预先定义的南向接口协议类型选择协议适配器。
其中，Action和Action id是一一对应的，若业务请求指令消息涉及多个操作对象，则涉及每种对象的Action。
步骤1201：SO基于NMS的业务请求确定相应的workflow，从而触发执行相应的业务处理流程。
首先，SO从步骤600的parameter list参数中获取到该业务请求针对的网元的标识(NE ID)，并发起向AAI查询确认相应NE的注册状态的请求。其中，该网元可以为图2或图3所示的实施例中涉及的第一网元。
workflow是指预先定义的业务执行工作流，可以包括执行这种业务处理的所有功能模块和功能模块参与业务处理的执行顺序，如配置管理workflow是SO—AAI(执行信息查询确认)—协议适配器(执行接口协议转换)。
步骤1202：SO向AAI发送网元注册状态信息查询(NE onboarding status check)，查询确认需要操作的网元是否已完成上线注册，网元注册状态信息查询中携带网元标识(NE ID)。
在一种实施方式中，该步骤还可用于查询网元(例如基站)是否支持某个业务特性(如MLB特性)，即向AAI查询确认对应网元的AAI entiy的属性中是否包括MLB相关的部署参数配置。若有，则支持MLB特性，否则不支持该特性。
步骤1203：若查询的NE ID标识的网元在AAI中没有保存相应注册信息，则AAI返回网元状态为不可用(Unavailable)，SO收到该返回消息，通知NMS相应的网元未完成注册，则流程到此结束。若查询的NE ID标识的网元在AAI中已保存相应注册信息，则AAI返回该网元的相关信息，包括NE ID、Correlation ID、OM IP and port、NRM MO template。其中Correlation ID是PNF注册时，AAI分配的PNF的内部临时标识。OM IP and port和NRM MO template是PNF注册时发送给AAI的。
步骤1204：SO调用第一配置应用程序编程接口(configure API)发起配置处理流程，并向协议适配器发送配置请求，将步骤1200和步骤1203的相关参数发送给协议适配器，其中，相关参数包括Parameter list，可选的还包括以下一种或多种：Correlation ID、OM IP and port、NRM MO template、Action、Action id、南向接口协议类型。
步骤1205：协议适配器向EMS/NE发送NRM模板查询请求，请求获取NE支持的NRM MO template，请求消息中携带NE ID和NRM版本(version)，其中NRM version无实际取值，仅是一个参数指示，用于告知EMS/NE希望获取NRM MO template。
需要说明的是，若设备商采用私有化NRM MO且不希望ONAP等感知其NRM建模方法，则该设备商的网络设备在注册时就不会将NRM MO template注册到AAI中，那么在步骤1203中就没有NRM MO template参数，则协议适配器需执行该步骤以及后边的步骤1206。
例如，当通信系统中有EMS时，则协议适配器向EMS发送NRM模板查询请求，EMS将NRM模板查询请求转发给NE；当通信系统中没有EMS时，则协议适配器直接将NRM模板查询请求发送给NE。
步骤1206：EMS/NE向协议适配器返回请求的NE的NRM MO模板(NRM MO template)，返回的NRM MO template是NE支持的相应版本NRM建模方法对应的网络资源对象模型(例如，一种树形结构的模型，包括多个MO以及MO之间的关系(如继承等))。
相应地，当通信系统中有EMS时，则NE将NRM MO template发送给EMS，然后EMS向协议适配器转发NRM MO template；当通信系统中没有EMS时，则NE直接向协议适配器发送NRM MO template。
步骤1207：协议适配器进行网络资源管理对象模板映射。
例如，协议适配器收到NRM MO template、Parameter list和Action id等参数后，基于Action id确定需要操作的网络资源对象MO类型，并基于NRM MO template识别相应MO类型的模型属性，执行Parameter list(“名-值”)向MO的映射，即将Parameter list转换为对应的MO对象和属性参数。协议适配器基于Action确定针对相应MO的操作处理。若步骤1200中没有包括Action和Action id，则协议适配器执行默认处理，即创建NRM MO template的所有MO对象。
步骤1208：协议适配器按照对应协议执行协议格式适配转换，包括操作转换和参数转换，如CORBA Adaptor会执行将Create MO操作转化为CORBA的创建对象操作Create_managed_object，详细的转换处理参考3GPP现有标准的处理，本申请不再详细描述转换过程。
步骤1209：协议适配器调用南向接口API/SB API向OM IP标识的地址和port标识的端口发送相应的配置管理指令消息。
步骤1210：EMS收到指令执行NE的配置。
步骤1211：EMS完成NE的配置管理处理后，向协议适配器回复响应消息，并将EMS设置的MO及其属性参数包含的在消息中。
步骤1212：协议适配器接收到响应消息，将步骤1211携带的MO及其属性参数转换成相应的“名-值”对的形式发送给SO，并携带Correlation ID和更新参数(updated parameters)。
步骤1213：SO更新AAI中保存的网元NE实体的参数信息，携带Correlation ID和updated parameters。
需要说明的是，图12所示的示例仅仅是通信系统中仅有一个协议适配器时的其中一种具体的示例，还可以有其他的示例，例如，可以是上述图6-图11中示例的变形，此处不再一一详细描述。
上述本申请提供的实施例中，分别从各个功能模块或设备本身、以及从各个功能模块或设备之间交互的角度对本申请实施例提供的通信方法的各方案进行了介绍。可以理解的是，各个功能模块或设备，例如上述适配器客户端、第一协议适配器为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
例如，当上述功能模块或者设备通过软件模块来实现相应的功能时，本申请实施例提供的通信装置可以包括获取模块1301和处理模块1302，可选的还可以包括发送模块1303，可以参考如图13所示的结构示意图。需要说明的是，在本申请实施例中当获取模块仅用于接收信息或数据时，获取模块也可以是接收模块；当获取模块用于获取通信装置本地保存的信息或数据时，获取模块也可以是处理模块。
在一个实施例中，图13所示的通信装置可以用于执行上述图2-图4、图6-图11所示的实施例中的适配器客户端的操作。例如：
获取模块1301用于获取南向接口协议类型；适配器客户端用于管理两个或者两个以上协议适配器；
处理模块1302用于根据南向接口协议类型在两个或者两个以上协议适配器中选择第一协议适配器，第一协议适配器用于实现第一协议。
在一种可选的实施方式中，获取模块1301，在获取南向接口协议类型时，具体用于：
从服务协调器接收第一信息，第一信息用于请求为第一网元进行网络配置，第一信息为名值对形式的配置参数，第一信息中包括南向接口协议类型；从第一信息中获取南向接口协议类型；或者，获取预设的南向接口协议类型。
一种示例中，获取模块1301在从服务协调器接收第一信息时，具体用于：
从服务协调器接收服务协调器调用第一接口发送的第一信息；其中，第一接口为适配器客户端提供的。
一种可能的实现方式中，通信装置还包括发送模块1303；
发送模块1303用于在获取模块从服务协调器接收第一信息之后，向第一协议适配器发送第一信息；或者，处理模块1302还用于根据第一信息确定第二信息；发送模块1303用于向第一协议适配器发送第二信息；第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的。
一种示例性的实施方式中，发送模块1303在向第一协议适配器发送第一信息时，具体用于调用第一协议适配器提供的第二接口向第一协议适配器发送第一信息。
一种示例性的实施方式中，发送模块1303在向第一协议适配器发送第二信息时，具体用于调用第一协议适配器提供的第二接口向第一协议适配器发送第二信息。
例如，发送模块1303还用于向第一网元发送网络资源模型模板查询请求；获取模块1301还用于从第一网元接收第一网元的网络资源对象模型。
示例性的，获取模块1301还用于从第一协议适配器接收第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；处理模块1302还用于根据第三信息在适配器客户端本地创建上下文信息；发送模块1303还用于向第一协议适配器发送第四信息，第四信息用于通知第一协议适配器注册结果。
例如，第一协议适配器为CORBA适配器、SOAP适配器或者RESTful适配器等。
又例如，当上述功能模块或者设备通过软件模块来实现相应的功能时，本申请实施例提供的通信装置还可以包括接收模块1401、处理模块1402和发送模块1403，可以参考如图14所示的结构示意图。
在一个实施例中，图14所示的通信装置可用于执行上述图2、图3所示的实施例中第一协议适配器的操作，以及可用于执行图4、图6-图12所示的实施例中协议适配器的操作。例如：
接收模块1401用于接收第一信息，第一信息为名值对形式的配置参数；第一信息是为第一网元进行网络配置的配置参数；第一协议适配器用于实现第一协议；
处理模块1402用于根据第一信息确定第二信息，第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的；
发送模块1403用于向第一网元发送第二信息。
例如，接收模块1401在接收第一信息时，具体用于从适配器客户端接收第一信息，适配器客户端用于管理两个或者两个以上协议适配器；或者，从服务协调器接收第一信息。
在一种可选的实施方式中，接收模块1401在从适配器客户端接收第一信息时，具体用于：接收适配器客户端调用第二接口发送的第一信息，第二接口为第一协议适配器提供的。
在另一种可选的实施方式中，接收模块1401在从服务协调器接收第一信息时，具体用于接收服务协调器调用第二接口发送的第一信息。
示例性的，发送模块1403还用于向第一网元发送网络资源模型模板查询请求；接收模块1401还用于从第一网元接收第一网元的网络资源对象模型。
一种可能的示例，发送模块1403还用于向适配器客户端发送第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；接收模块1401还用于从适配器客户端接收第四信息，第四信息用于通知第一协议适配器注册结果。
示例性的，第一协议适配器可以为CORBA适配器、SOAP适配器或者RESTful适配器等。
需要说明的是，本申请实施例中对单元或模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
又例如，当上述功能模块或者设备通过硬件来实现相应的功能时，本申请提供的通信装置可以包括通信接口1501和处理器1502，可选的还可以包括存储器1503，可以参考如图15所示结构图。
例如，处理器1502可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合等等。处理器1502还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。处理器1502在实现上述功能时，可以通过硬件实现，当然也可以通过硬件执行相应的软件实现。
通信接口1501和处理器1502之间相互连接。可选的，通信接口1501和处理器1502通过总线1504相互连接；总线1504可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1503，与处理器1502耦合，用于存放通信装置必要的程序等。例如，程序可以包括程序代码，该程序代码包括计算机操作指令。存储器1503可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。处理器1502执行存储器1503所存放的应用程序，实现通信装置的功能。
在一个实施例中，图15所示的通信装置可用于执行上述图2-图4、图6-图11所示的实施例中的适配器客户端的操作。例如：
通信接口1501用于获取南向接口协议类型；适配器客户端用于管理两个或者两个以上协议适配器；
处理器1502用于根据南向接口协议类型在两个或者两个以上协议适配器中选择第一协议适配器，第一协议适配器用于实现第一协议。
在一种可选的实施方式中，通信接口1501在获取南向接口协议类型时，具体用于：
从服务协调器接收第一信息，第一信息用于请求为第一网元进行网络配置，第一信息为名值对形式的配置参数，第一信息中包括南向接口协议类型；从第一信息中获取南向接口协议类型；或者，获取预设的南向接口协议类型。
一种示例中，通信接口1501在从服务协调器接收第一信息时，具体用于：
从服务协调器接收服务协调器调用第一接口发送的第一信息；其中，第一接口为适配器客户端提供的。
一种可能的实现方式中，通信接口1501还用于在从服务协调器接收第一信息之后，向第一协议适配器发送第一信息；或者，处理器1502还用于根据第一信息确定第二信息；通信接口1501还用于向第一协议适配器发送第二信息；第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的。
一种示例性的实施方式中，通信接口1501在向第一协议适配器发送第一信息时，具体用于调用第一协议适配器提供的第二接口向第一协议适配器发送第一信息。
一种示例性的实施方式中，通信接口1501在向第一协议适配器发送第二信息时，具体用于调用第一协议适配器提供的第二接口向第一协议适配器发送第二信息。
例如，通信接口1501还用于向第一网元发送网络资源模型模板查询请求，并从第一网元接收第一网元的网络资源对象模型。
示例性的，通信接口1501还用于从第一协议适配器接收第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；处理器1502还用于根据第三信息在适配器客户端本地创建上下文信息；通信接口1501还用于向第一协议适配器发送第四信息，第四信息用于通知第一协议适配器注册结果。
例如，第一协议适配器可以为CORBA适配器、SOAP适配器或者RESTful适配器等。
在另一个实施例中，图15所示的通信装置可用于执行上述图2、图3所示的实施例中第一协议适配器的操作，以及可用于执行图4、图6-图12所示的实施例中协议适配器的操作。例如：
通信接口1501用于接收第一信息，第一信息为名值对形式的配置参数；第一信息是为第一网元进行网络配置的配置参数；第一协议适配器用于实现第一协议；
处理器1502用于根据第一信息确定第二信息，第二信息为管理对象及其对象属性；第二信息是第一信息基于网络资源管理对象模板映射得到的；
通信接口1501还用于向第一网元发送第二信息。
例如，通信接口1501在接收第一信息时，具体用于从适配器客户端接收第一信息，适配器客户端用于管理两个或者两个以上协议适配器；或者，从服务协调器接收第一信息。
在一种可选的实施方式中，通信接口1501在从适配器客户端接收第一信息时，具体用于：接收适配器客户端调用第二接口发送的第一信息，第二接口为第一协议适配器提供的。
在另一种可选的实施方式中，通信接口1501在从服务协调器接收第一信息时，具体用于接收服务协调器调用第二接口发送的第一信息。
示例性的，通信接口1501还用于向第一网元发送网络资源模型模板查询请求，并从第一网元接收第一网元的网络资源对象模型。
一种可能的示例，通信接口1501还用于向适配器客户端发送第三信息，第三信息中包括第一协议适配器的名称、标识，支持的协议类型；通信接口1501还用于从适配器客 户端接收第四信息，第四信息用于通知第一协议适配器注册结果。
示例性的，第一协议适配器可以为CORBA适配器、SOAP适配器或者RESTful适配器等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种通信方法，其特征在于，包括：
    适配器客户端获取南向接口协议类型；所述适配器客户端用于管理两个或者两个以上协议适配器；
    所述适配器客户端根据所述南向接口协议类型在所述两个或者两个以上协议适配器中选择第一协议适配器，所述第一协议适配器用于实现第一协议。
  2. 如权利要求1所述的方法，其特征在于，所述适配器客户端获取南向接口协议类型，包括：
    所述适配器客户端从服务协调器接收第一信息，所述第一信息用于请求为第一网元进行网络配置，所述第一信息为名值对形式的配置参数，所述第一信息中包括所述南向接口协议类型；所述适配器客户端从所述第一信息中获取所述南向接口协议类型；或者
    所述适配器客户端获取预设的所述南向接口协议类型。
  3. 如权利要求2所述的方法，其特征在于，所述适配器客户端从服务协调器接收所述第一信息，包括：
    所述适配器客户端从所述服务协调器接收所述服务协调器调用第一接口发送的所述第一信息；其中，所述第一接口为所述适配器客户端提供的。
  4. 如权利要求2或3所述的方法，其特征在于，所述适配器客户端从所述服务协调器接收所述第一信息之后，所述方法还包括：
    所述适配器客户端向所述第一协议适配器发送所述第一信息；或者
    所述适配器客户端根据所述第一信息确定第二信息，并向所述第一协议适配器发送所述第二信息；所述第二信息为管理对象及其对象属性；所述第二信息是所述第一信息基于网络资源管理对象模板映射得到的。
  5. 如权利要求4所述的方法，其特征在于，
    所述适配器客户端向所述第一协议适配器发送所述第一信息，包括：
    所述适配器客户端调用所述第一协议适配器提供的第二接口向所述第一协议适配器发送所述第一信息；
    或者，
    所述适配器客户端向所述第一协议适配器发送所述第二信息，包括：
    所述适配器客户端调用所述第一协议适配器提供的所述第二接口向所述第一协议适配器发送所述第二信息。
  6. 如权利要求4或5所述的方法，其特征在于，所述方法还包括：
    所述适配器客户端向所述第一网元发送网络资源模型模板查询请求，并从所述第一网元接收所述第一网元的网络资源对象模型。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述适配器客户端从所述第一协议适配器接收第三信息，所述第三信息中包括所述第一协议适配器的名称、标识，支持的协议类型；
    所述适配器客户端根据所述第三信息在所述适配器客户端本地创建上下文信息；
    所述适配器客户端向所述第一协议适配器发送第四信息，所述第四信息用于通知所述第一协议适配器注册结果。
  8. 如权利要求1-7任一项所述的方法，其特征在于，所述第一协议适配器为CORBA适配器、SOAP适配器或者RESTful适配器。
  9. 一种通信方法，其特征在于，包括：
    第一协议适配器接收第一信息，所述第一信息为名值对形式的配置参数；所述第一信息是为第一网元进行网络配置的配置参数；所述第一协议适配器用于实现第一协议；
    所述第一协议适配器根据所述第一信息确定第二信息，所述第二信息为管理对象及其对象属性；所述第二信息是所述第一信息基于网络资源管理对象模板映射得到的；
    所述第一协议适配器向所述第一网元发送所述第二信息。
  10. 如权利要求9所述的方法，其特征在于，第一协议适配器接收第一信息，包括：
    所述第一协议适配器从适配器客户端接收所述第一信息，所述适配器客户端用于管理两个或者两个以上协议适配器；或者
    所述第一协议适配器从服务协调器接收所述第一信息。
  11. 如权利要求10所述的方法，其特征在于，
    所述第一协议适配器从所述适配器客户端接收第一信息，包括：
    所述第一协议适配器接收所述适配器客户端调用第二接口发送的所述第一信息，所述第二接口为所述第一协议适配器提供的；
    或者，
    所述第一协议适配器从服务协调器接收所述第一信息，包括：
    所述第一协议适配器接收所述服务协调器调用所述第二接口发送的所述第一信息。
  12. 如权利要求9-11任一项所述的方法，其特征在于，所述方法还包括：
    所述第一协议适配器向所述第一网元发送网络资源模型模板查询请求，并从所述第一网元接收所述第一网元的网络资源对象模型。
  13. 如权利要求9-12任一项所述的方法，其特征在于，所述方法还包括：
    所述第一协议适配器向适配器客户端发送第三信息，所述第三信息中包括所述第一协议适配器的名称、标识，支持的协议类型；
    所述第一协议适配器从所述适配器客户端接收第四信息，所述第四信息用于通知所述第一协议适配器注册结果。
  14. 如权利要求9-13任一项所述的方法，其特征在于，所述第一协议适配器为CORBA适配器、SOAP适配器或者RESTful适配器。
  15. 一种通信装置，所述通信装置为适配器客户端，其特征在于，包括：
    获取模块，用于获取南向接口协议类型；所述适配器客户端用于管理两个或者两个以上协议适配器；
    处理模块，用于根据所述南向接口协议类型在所述两个或者两个以上协议适配器中选择第一协议适配器，所述第一协议适配器用于实现第一协议。
  16. 如权利要求15所述的通信装置，其特征在于，所述获取模块，在获取南向接口协议类型时，具体用于：
    从服务协调器接收第一信息，所述第一信息用于请求为第一网元进行网络配置，所述第一信息为名值对形式的配置参数，所述第一信息中包括所述南向接口协议类型；从所述第一信息中获取所述南向接口协议类型；或者
    获取预设的所述南向接口协议类型。
  17. 如权利要求16所述的通信装置，其特征在于，所述获取模块，在从服务协调器接收所述第一信息时，具体用于：
    从所述服务协调器接收所述服务协调器调用第一接口发送的所述第一信息；其中，所述第一接口为所述适配器客户端提供的。
  18. 如权利要求16或17所述的通信装置，其特征在于，所述通信装置还包括发送模块；
    所述发送模块，用于在所述获取模块从所述服务协调器接收所述第一信息之后，向所述第一协议适配器发送所述第一信息；或者
    所述处理模块还用于：根据所述第一信息确定第二信息；所述发送模块用于：向所述第一协议适配器发送所述第二信息；所述第二信息为管理对象及其对象属性；所述第二信息是所述第一信息基于网络资源管理对象模板映射得到的。
  19. 如权利要求18所述的通信装置，其特征在于，
    所述发送模块，在向所述第一协议适配器发送所述第一信息时，具体用于：
    调用所述第一协议适配器提供的第二接口向所述第一协议适配器发送所述第一信息；
    或者，
    所述发送模块，在向所述第一协议适配器发送所述第二信息时，具体用于：
    调用所述第一协议适配器提供的所述第二接口向所述第一协议适配器发送所述第二信息。
  20. 如权利要求18或19所述的通信装置，其特征在于，
    所述发送模块，还用于向所述第一网元发送网络资源模型模板查询请求；
    所述获取模块，还用于从所述第一网元接收所述第一网元的网络资源对象模型。
  21. 如权利要求15-20任一项所述的通信装置，其特征在于，
    所述获取模块，还用于从所述第一协议适配器接收第三信息，所述第三信息中包括所述第一协议适配器的名称、标识，支持的协议类型；
    所述处理模块，还用于根据所述第三信息在所述适配器客户端本地创建上下文信息；
    所述通信装置还包括发送模块，所述发送模块，用于向所述第一协议适配器发送第四信息，所述第四信息用于通知所述第一协议适配器注册结果。
  22. 如权利要求15-21任一项所述的通信装置，其特征在于，所述第一协议适配器为CORBA适配器、SOAP适配器或者RESTful适配器。
  23. 一种通信装置，所述通信装置为第一协议适配器，其特征在于，包括：
    接收模块，用于接收第一信息，所述第一信息为名值对形式的配置参数；所述第一信息是为第一网元进行网络配置的配置参数；所述第一协议适配器用于实现第一协议；
    处理模块，用于根据所述第一信息确定第二信息，所述第二信息为管理对象及其对象属性；所述第二信息是所述第一信息基于网络资源管理对象模板映射得到的；
    发送模块，用于向所述第一网元发送所述第二信息。
  24. 如权利要求23所述的通信装置，其特征在于，所述接收模块，在接收第一信息时，具体用于：
    从适配器客户端接收所述第一信息，所述适配器客户端用于管理两个或者两个以上协议适配器；或者
    从服务协调器接收所述第一信息。
  25. 如权利要求24所述的通信装置，其特征在于，
    所述接收模块，在从所述适配器客户端接收第一信息时，具体用于：
    接收所述适配器客户端调用第二接口发送的所述第一信息，所述第二接口为所述第一协议适配器提供的；
    或者，
    所述接收模块，在从服务协调器接收所述第一信息时，具体用于：
    接收所述服务协调器调用所述第二接口发送的所述第一信息。
  26. 如权利要求23-25任一项所述的通信装置，其特征在于，
    所述发送模块，还用于：向所述第一网元发送网络资源模型模板查询请求；
    所述接收模块，还用于：从所述第一网元接收所述第一网元的网络资源对象模型。
  27. 如权利要求23-26任一项所述的通信装置，其特征在于，
    所述发送模块，还用于向适配器客户端发送第三信息，所述第三信息中包括所述第一协议适配器的名称、标识，支持的协议类型；
    所述接收模块，还用于从所述适配器客户端接收第四信息，所述第四信息用于通知所述第一协议适配器注册结果。
  28. 如权利要求23-27任一项所述的通信装置，其特征在于，所述第一协议适配器为CORBA适配器、SOAP适配器或者RESTful适配器。
  29. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1至14任意一项所述的方法。
PCT/CN2020/102841 2019-07-26 2020-07-17 一种通信方法及装置 WO2021017906A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20847384.3A EP3975480A4 (en) 2019-07-26 2020-07-17 COMMUNICATION METHOD AND DEVICE
US17/568,473 US11785121B2 (en) 2019-07-26 2022-01-04 Selecting protocol adaptor in a communication network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910683991.0 2019-07-26
CN201910683991.0A CN112311567B (zh) 2019-07-26 2019-07-26 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/568,473 Continuation US11785121B2 (en) 2019-07-26 2022-01-04 Selecting protocol adaptor in a communication network

Publications (1)

Publication Number Publication Date
WO2021017906A1 true WO2021017906A1 (zh) 2021-02-04

Family

ID=74230188

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/102841 WO2021017906A1 (zh) 2019-07-26 2020-07-17 一种通信方法及装置

Country Status (4)

Country Link
US (1) US11785121B2 (zh)
EP (1) EP3975480A4 (zh)
CN (1) CN112311567B (zh)
WO (1) WO2021017906A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115733785A (zh) * 2021-08-27 2023-03-03 中兴通讯股份有限公司 网络设备管理方法、装置、系统及存储介质
CN114968891A (zh) * 2022-06-10 2022-08-30 芯来智融半导体科技(上海)有限公司 芯片交互方法、装置、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1744594A (zh) * 2004-08-30 2006-03-08 北京航空航天大学 Web服务传输协议适配器及其生成方法
US7127517B2 (en) * 2000-12-27 2006-10-24 International Business Machines Corporation Protocol adapter framework for integrating non-IIOP applications into an object server container
CN102790781A (zh) * 2011-05-17 2012-11-21 南京中兴新软件有限责任公司 一种中间件、带行业应用中间件的m2m系统及其应用方法
CN103181119A (zh) * 2010-10-29 2013-06-26 国际商业机器公司 管理不同通信协议网络之间的通信
WO2013169156A1 (en) * 2012-05-10 2013-11-14 Telefonaktiebolaget Lm Ericsson (Publ) System, method and computer program product for protocol adaptation

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4146983B2 (ja) * 1999-02-26 2008-09-10 インターナショナル・ビジネス・マシーンズ・コーポレーション サーバ・オブジェクトのメソッドを呼び出すプロセス方法及びデータ処理システム
US7376958B1 (en) * 2002-06-06 2008-05-20 Unisys Corporation Method and apparatus for honoring CORBA transaction requests by a legacy data base management system
DE60222544T2 (de) * 2002-07-18 2008-06-19 Telefonaktiebolaget Lm Ericsson (Publ) Verwaltungssystem umd Methode zur Erbringung von Abonnementdienstleistungen
EP1655974A1 (de) * 2004-11-08 2006-05-10 Siemens Aktiengesellschaft Verfahren und Vorrichtungen zum Informationsabgleich zwischen Manager und Agent in eiem Managementnetz
CN100411355C (zh) * 2005-08-20 2008-08-13 华为技术有限公司 网管接口中信息服务层次继承关系的实现方法及网管装置
US8019839B2 (en) * 2009-05-11 2011-09-13 Accenture Global Services Limited Enhanced network adapter framework
CN104885407A (zh) * 2013-12-31 2015-09-02 华为技术有限公司 一种网络功能虚拟化nfv故障管理装置、设备及方法
US9998566B2 (en) * 2014-11-03 2018-06-12 General Electric Company Intelligent gateway with a common data format
CN106302071B (zh) * 2015-05-29 2020-02-14 华为技术有限公司 一种适配器、网络设备以及端口配置的方法
CN106484611B (zh) * 2015-09-02 2021-01-15 腾讯科技（深圳）有限公司 基于自动化协议适配的模糊测试方法和装置
US10644942B2 (en) * 2018-02-07 2020-05-05 Mavenir Networks, Inc. Management of radio units in cloud radio access networks
CN108667547B (zh) * 2018-08-10 2019-10-11 电信科学技术第五研究所有限公司 一种网络时间协议转换方法及系统
CN109889521B (zh) * 2019-02-21 2021-11-19 北京航星永志科技有限公司 存储器、通信通道复用实现方法、装置和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7127517B2 (en) * 2000-12-27 2006-10-24 International Business Machines Corporation Protocol adapter framework for integrating non-IIOP applications into an object server container
CN1744594A (zh) * 2004-08-30 2006-03-08 北京航空航天大学 Web服务传输协议适配器及其生成方法
CN103181119A (zh) * 2010-10-29 2013-06-26 国际商业机器公司 管理不同通信协议网络之间的通信
CN102790781A (zh) * 2011-05-17 2012-11-21 南京中兴新软件有限责任公司 一种中间件、带行业应用中间件的m2m系统及其应用方法
WO2013169156A1 (en) * 2012-05-10 2013-11-14 Telefonaktiebolaget Lm Ericsson (Publ) System, method and computer program product for protocol adaptation

Also Published As

Publication number Publication date
EP3975480A1 (en) 2022-03-30
US20220131958A1 (en) 2022-04-28
CN112311567B (zh) 2022-04-05
US11785121B2 (en) 2023-10-10
EP3975480A4 (en) 2022-08-10
CN112311567A (zh) 2021-02-02

Similar Documents

Publication Publication Date Title
US11146462B2 (en) Network slice management method, device, and system
EP3609161B1 (en) Network slice creating method and apparatus, and communication system
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
EP3595244B1 (en) Network slice management method, unit and system
US10298439B2 (en) Network functions virtualization network system and data processing method, and apparatus
US10270648B2 (en) Configuration information management method, device, network element management system and storage medium
JP6007217B2 (ja) ネットワーク仮想化のための方法及び装置
WO2018171459A1 (zh) 网络切片的管理方法和装置
WO2019062836A1 (zh) 网络切片管理方法及其装置
WO2018058579A1 (zh) 网络切片的管理方法及管理单元
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
CN109391490B (zh) 网络切片的管理方法和装置
JP2018530214A (ja) ネットワークサービスをデプロイするための方法及び装置
US20190260636A1 (en) Method and apparatus for managing network slice instance
WO2021017906A1 (zh) 一种通信方法及装置
WO2019072033A1 (zh) 一种网络方法和系统、及终端
KR20150088462A (ko) 클라우드 환경에서 네트워크 장치의 연동 방법 및 장치
US20230041981A1 (en) Identifying an Instance of a Virtual Network Function
WO2021226975A1 (zh) 配置方法和装置
WO2022110944A1 (zh) 网络切片规划的方法以及相关设备
WO2023116638A1 (zh) 切片配置方法、系统、服务器和存储介质
CN117729103A (zh) 分布式网络的部署方法、系统和网络系统
TW202312779A (zh) 行固網整合ｉｐ位址資源管理系統、方法及電腦可讀媒介
JP2019193297A (ja) ネットワークサービスをデプロイするための方法及び装置
CN115733743A (zh) 网络业务部署方法、nfvo以及nfv系统

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: 20847384

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020847384

Country of ref document: EP

Effective date: 20211221

NENP Non-entry into the national phase

Ref country code: DE