Network element management method, system and device under service-oriented architecture

Abstract

The present disclosure relates to the technical field of communication, in particular to a method, system and device for network element management under service-oriented architecture, a computer readable storage medium and an electronic device. The method comprises: receiving registration information of a service-oriented network element, obtaining management domain information of the service-oriented network element; transmitting the management domain information of the service-oriented network element to a management platform, so that the management platform establishes a communication link with the service-oriented network element according to the management domain information. The technical scheme of the embodiment of the present disclosure overcomes the problem that the efficiency of docking of the newly added network element is not clear.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, in particular to a network element management method, system and device under a service-oriented architecture, a computer readable storage medium and an electronic device. BACKGROUND

[0002] With the rapid development of 5G network and 5G application, 5G network is still under rapid construction and deployment, and automatic discovery and rapid management of newly added / expanded network elements become an urgent need.

[0003] In the prior art, the newly added / expanded network elements are put into use, and only business domain interconnection is not enough, and management domain needs to be managed and connected to realize automatic configuration operation and monitoring and maintenance of alarms, performance and logs of the network elements. The management domain needs to be managed and connected through offline manual mode to obtain connection information, which affects the management and connection efficiency and the business online progress.

[0004] It should be noted that the information disclosed in the above background section is only used to strengthen the understanding of the background of the present disclosure, and therefore can include information that does not constitute prior art known to those of ordinary skill in the art. SUMMARY

[0005] The purpose of the present disclosure is to provide a network element management method, system and device under a service-oriented architecture, a computer readable medium and an electronic device, so as to at least partially overcome the problem of low efficiency of newly added network element management and connection.

[0006] According to a first aspect of the present disclosure, a network element management method under a service-oriented architecture is provided, comprising: receiving registration information of a service-oriented network element, obtaining management domain information of the service-oriented network element; transmitting the management domain information of the service-oriented network element to a management platform, so that the management platform establishes a communication link with the service-oriented network element according to the management domain information.

[0007] According to a second aspect of the present disclosure, a network element management system under a service-oriented architecture is provided, comprising: a network storage function comprising a business registration interface and a management registration interface, wherein the business registration interface is used to obtain business domain information of a service-oriented network element, and the management registration interface is used to obtain management domain information of the service-oriented network element; a management platform used to obtain the management domain information of the service-oriented network element from the network storage function, so as to establish a communication link with the service-oriented network element according to the management domain information.

[0008] According to a second aspect of this disclosure, a network element management device under a service-oriented architecture is provided, comprising: an information receiving module for receiving registration information of a service-oriented network element and obtaining management domain information of the service-oriented network element; and an information uploading module for transmitting the management domain information of the service-oriented network element to a management platform, so that the management platform establishes a communication link with the service-oriented network element based on the management domain information.

[0009] According to a fourth aspect of this disclosure, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described above.

[0010] According to a fifth aspect of this disclosure, an electronic device is provided, characterized in that it includes: one or more processors; and a memory for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the method described above.

[0011] One embodiment of this disclosure provides a network element management method under a service-oriented architecture. During the registration of a service-oriented network element, the management domain information of the service-oriented network element is directly obtained and uploaded to the management platform. This enables the management platform to establish a communication link with the service-oriented network element based on the management domain information. This eliminates the need for manual uploading of the management domain information of newly added service-oriented network elements, achieving automated management and integration of newly added / expanded network elements, improving the efficiency of network equipment deployment and reducing operation and maintenance costs.

[0012] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0013] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0014] Figure 1 The system architecture diagram of network element management under the service-oriented architecture in related technologies is shown.

[0015] Figure 2 The flowchart illustrates a network element management method under a service-oriented architecture in an exemplary embodiment of this disclosure.

[0016] Figure 3 The diagram illustrates an architecture diagram of a network element management method under a service-oriented architecture in an exemplary embodiment of this disclosure.

[0017] Figure 4This illustration schematically depicts a network element management system under a service-oriented architecture, as shown in an exemplary embodiment of this disclosure.

[0018] Figure 5 This schematic diagram illustrates the composition of a network element management device under a service-oriented architecture in an exemplary embodiment of the present disclosure.

[0019] Figure 6 A schematic diagram of an electronic device to which embodiments of the present disclosure may be applied is shown. Detailed Implementation

[0020] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0021] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0022] In related technologies, 5G SA (Service-Based Architecture) implements each logical network function (NF) as an independent service, with loosely coupled interfaces enabling interoperability. NRF (Network Repository Function) supports service registration / deregistration and discovery. NRF receives NF discovery requests from NF instances and provides information about the discovered NF instances. The deployment of 5G SA and NRF lays the foundation for automatic registration and discovery of 5G network element service domains.

[0023] With the rapid development of 5G networks and applications, 5G networks are still under rapid construction and deployment. For newly added / expanded network elements, in addition to the automatic registration and discovery of service domains, the management domain also needs to achieve automatic discovery and rapid management. NRF supports the automatic registration capability of service-oriented network elements, which can include AMF (Access and Mobility Management Function), SMF (Service Management Function), NSSF (Network Slice Selection Function), NEF (Network Element Function), PCF (Policy Control Function), UDM (Unified Data Management), BSF (Binding Support Function), AUSF (Authentication Server Function), SMSF (Short Message Service Function), CHF (Charging Function), AF (Application Function), etc., enabling automatic registration and discovery of the service domains of newly added network elements. The Nnrf_NFManagement_NFRegister service defined in 3GPP 23.502 includes information such as: NF type, NF instance ID, FQDN or NF service domain IP address, supported NF service names, and PLMN ID. However, for newly added / expanded network elements, service domain interoperability alone is insufficient; management domain integration is also required for automated configuration and monitoring / maintenance of network elements, including alarms, performance, and logs. Management domain integration, however, necessitates manual offline acquisition of integration information, impacting integration efficiency and service rollout progress.

[0024] Reference Figure 1As shown, when adding a new service-oriented network element AMF2, during the deployment process, AMF2 automatically registers with the NRF via the Nnrf_NFManagement_NFRegister service. AMF2 now communicates with other service-oriented network elements' service domains. Then, the management domain information for AMF2 is obtained offline. The cloud network acquisition and control platform / network management system interfaces with AMF2's OAM, enabling data collection and service configuration distribution for the new network element. However, the management domain integration requires manual intervention, making automated integration impossible. This process is time-consuming, impacting the efficiency of deploying new and expanded network elements and increasing operating costs.

[0025] Based on the above shortcomings, this disclosure provides a network element management method under a service-oriented architecture, which is described below in conjunction with... Figure 2 The service-oriented architecture network element management method in this exemplary embodiment will be described. Figure 2 An exemplary flow of the network element management method under the service-oriented architecture is shown, which may include steps S210 to S220.

[0026] The following is about Figure 2 Each step in the process will be explained in detail.

[0027] In step S210, the registration information of the service-oriented network element is received, and the management domain information of the service-oriented network element is obtained.

[0028] In one example implementation of this disclosure, when adding or expanding service-oriented network elements, the Network Repository Function (NRF) can accept the registration information of the newly added service-oriented network element, obtain the management domain information of the service-oriented network element, and also obtain the service domain information of the service-oriented network element.

[0029] Specifically, the aforementioned network storage function may include a service domain interface and a management domain interface. When adding or expanding service-oriented network elements, the newly added service-oriented network elements will access the service domain interface and management domain interface of the aforementioned network storage function to upload the service domain information and management domain information of the service-oriented network elements to the aforementioned network storage function.

[0030] The aforementioned service-oriented network elements may include AMF (Access and Mobility Management Function), SMF (Service Management Function), NSSF (Network Slice Selection Function), NEF (Network Element Function), PCF (Policy Control Function), UDM (Unified Data Management), BSF (Binding Support Function), AUSF (Authentication Server Function), SMSF (Short Message Service Function), CHF (Charging Function), AF (Application Function), etc., which can realize the automatic registration and discovery of the service domain of newly added network elements.

[0031] The newly added service-oriented network element can be one or more of the above-mentioned elements, and the existing service-oriented network element can also be one or more of the above-mentioned elements. No specific limitation is made in this example implementation.

[0032] Specifically, refer to Figure 3 As shown, the original service-oriented network elements include all the service-oriented network elements mentioned above. A new service-oriented network element, AMF2, has been added. At this time, the Nnrf_NFManagement_NFRegister service registration information can be extended. In addition to registering the service domain information to the NRF, the management domain information of AMF2 is also registered to the NRF.

[0033] For example, if the newly added service-oriented network element is SMF2, the Nnrf_NFManagement_NFRegister service registration information can be extended. In addition to registering the service domain information to the NRF, the management domain information of SMF2 can also be registered to the NRF.

[0034] In one exemplary embodiment of this disclosure, when adding the aforementioned service-oriented network element, the service-oriented network element invokes the interface information of the Network Repository Function (NRF) to extend the interface of the NRF, enabling it to possess both a management domain interface and a service domain interface. The service-oriented network element invokes the management domain interface to receive the registration information of the service-oriented network element and obtain its management domain information. Similarly, the service-oriented network element invokes the service domain interface to receive the registration information of the service-oriented network element and obtain its service domain information.

[0035] In step S220, the management domain information of the service-oriented network element is transmitted to the management platform so that the management platform can establish a communication link with the service-oriented network element based on the management domain information.

[0036] In this example implementation, after the Network Repository Function (NRF) receives the management domain information of the service-oriented network element, it can output the management domain information to the management platform so that the management platform can establish a communication link with the service-oriented network element based on the management domain information.

[0037] In one example implementation, after the Network Repository Function (NRF) receives the management domain information of the service-oriented network element, it can transmit an information update instruction to the management platform, so that the management platform can scan the Network Repository Function to obtain the management domain information of the service-oriented network element according to the information update instruction.

[0038] For example, suppose a new service-oriented network element AMF2 is added. After the Network Repository Function (NRF) receives the management domain information corresponding to AMF2, it can transmit an information update command to the management platform, informing the management platform that the data in the Network Repository Function (NRF) has been updated. This allows the management platform to scan the Network Repository Function (NRF), and after detecting the new management domain information, retrieve the new management domain information, namely the management domain information corresponding to AMF2, to establish a communication link between AMF2 and the management platform.

[0039] In another example implementation, the management platform can automatically scan the Network Repository Function (NRF) at a preset frequency. Upon detecting new management domain information within the NRF, it can obtain this information and establish a communication link with the corresponding service-oriented network element. Specifically, it automatically obtains the management domain information (management domain IP, port, account encryption information, etc.) of the newly added network element AMF2 through the query interface of the already connected NRF management domain (OAM (Operation Administration and Maintenance)).

[0040] The preset frequency can be once every 10 minutes, once every 20 minutes, or it can be customized according to user needs. In this example implementation, no specific limitation is made.

[0041] For example, suppose a new service-oriented network element AMF2 is added. When the Network Repository Function (NRF) receives the management domain information corresponding to AMF2, the management platform can automatically scan the NRF at a preset frequency. Once new management domain information is detected within the NRF—specifically, the management domain information corresponding to AMF2—the platform can acquire this new management domain information, i.e., the management domain information corresponding to AMF2. Then, a communication link is established between the management platform and AMF2 based on this management domain information.

[0042] The aforementioned management platform may be a cloud network acquisition and control platform, a network management system, etc., and is not limited to it in detail in this example implementation.

[0043] As mentioned above, the management domain information may include the management domain IP, port, account encryption information, etc., and may also be customized according to user needs. In this example implementation, no specific limitation is made.

[0044] In one example implementation, the aforementioned management domain account can be a general default account, and the password is transmitted in an encrypted manner, such as encrypting the original plaintext password with an AES key. After the management domain accepts the account, it can modify the initial password through the management domain interface of the management platform to ensure the security of account information.

[0045] In summary, this exemplary embodiment, during the registration of service-oriented network elements, firstly, directly obtains the management domain information of the service-oriented network element and uploads it to the management platform. This allows the management platform to establish a communication link with the service-oriented network element based on the management domain information, eliminating the need for manual uploading of the management domain information of newly added / expanded network elements. This achieves automated management and integration of new / expanded network elements, improving the efficiency of network equipment deployment and reducing operation and maintenance costs. Secondly, it accelerates the deployment of network elements, better meeting business development and customer needs. The automated management and integration process reduces manual management and integration steps, lowering operation and maintenance costs. Furthermore, it can promote the optimization and improvement of 5G SA service-oriented architecture-related standards, driving industry development.

[0046] Furthermore, this disclosure also provides a new network element management system under a service-oriented architecture, referring to... Figure 4 As shown, the network element management system under the service-oriented architecture can include network storage functions and a management platform. The network storage functions include a service registration interface and a management registration interface. The service registration interface is used to obtain the service domain information of the service-oriented network element, and the management registration interface is used to obtain the management domain information of the service-oriented network element. The management platform is used to obtain the management domain information of the service-oriented network element from the network storage function, so as to establish a communication link with the service-oriented network element based on the management domain information.

[0047] When adding or expanding service-oriented network elements, the aforementioned Network Repository Function (NRF) can accept the registration information of the new service-oriented network element, obtain the management domain information of the service-oriented network element, and also obtain the service domain information of the service-oriented network element.

[0048] Specifically, the aforementioned network storage function may include a service domain interface and a management domain interface. When adding or expanding service-oriented network elements, the newly added service-oriented network elements will access the service domain interface and management domain interface of the aforementioned network storage function to upload the service domain information and management domain information of the service-oriented network elements to the aforementioned network storage function.

[0049] In one exemplary embodiment of this disclosure, when adding the aforementioned service-oriented network element, the service-oriented network element invokes the interface information of the Network Repository Function (NRF) to extend the interface of the NRF, enabling it to possess both a management domain interface and a service domain interface. The service-oriented network element invokes the management domain interface to receive the registration information of the service-oriented network element and obtain its management domain information. Similarly, the service-oriented network element invokes the service domain interface to receive the registration information of the service-oriented network element and obtain its service domain information.

[0050] After receiving the management domain information of the service-oriented network element, the Network Repository Function (NRF) can transmit an information update command to the management platform, so that the management platform can scan the Network Repository Function to obtain the management domain information of the service-oriented network element according to the information update command.

[0051] The aforementioned management platform can automatically scan the Network Repository Function (NRF) at a preset frequency. Upon detecting new management domain information within the NRF, it can obtain this information and establish a communication link with the corresponding service-oriented network element. Specifically, it automatically retrieves the management domain information (management domain IP, port, account encryption information, etc.) of the newly added network element AMF2 through the query interface of the connected NRF management domain (OAM (Operation Administration and Maintenance)).

[0052] The aforementioned management platform may be a cloud network acquisition and control platform, a network management system, etc., and is not limited to it in detail in this example implementation.

[0053] The specific functions of network storage and management platform have been described in detail in the above-mentioned service-oriented architecture network element management method, and will not be repeated here.

[0054] It should be noted that the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0055] Further reference Figure 5 As shown, this example implementation also provides a network element management device 500 under a service-oriented architecture, including an information receiving module 510 and an information uploading module 520. Wherein:

[0056] The information receiving module 510 can be used to receive the registration information of the service-oriented network element and obtain the management domain information of the service-oriented network element; the information uploading module 520 can be used to transmit the management domain information of the service-oriented network element to the management platform, so that the management platform can establish a communication link with the service-oriented network element based on the management domain information.

[0057] In one example implementation, the information receiving module 510 can be configured to respond to a call instruction from a service-oriented network element to its management domain interface, receive the registration information of the service-oriented network element through the management domain interface, and obtain the management domain information of the service-oriented network element. The information receiving module 510 can also receive the registration information of the service-oriented network element and obtain its service domain information.

[0058] In one example implementation, the information upload module 520 can be configured to transmit an information update instruction to the management platform, so that the management platform can scan the network storage function according to the information update instruction to obtain the management domain information of the service-oriented network element.

[0059] In another example implementation, the information upload module 520 can be configured to respond to the scanning operation of the management platform and transmit the management domain information of the service-oriented network element to the management platform.

[0060] The management domain information includes the management domain address, management domain account, and account management information. Transmitting the management domain information of the service-oriented network element to the management platform includes transmitting the management domain address, management domain account, and account management information to the management platform.

[0061] The specific details of each module in the above-mentioned device have been described in detail in the method section of the implementation. For any undisclosed details, please refer to the implementation content of the method section, and therefore will not be repeated here.

[0062] Exemplary embodiments of this disclosure also provide an electronic device for performing the above-described network element management method under a service-oriented architecture.

[0063] The following is based on Figure 6Taking a mobile terminal 600 as an example, the construction of this electronic device will be described by way of example. Those skilled in the art will understand that, apart from components specifically designed for mobile purposes, Figure 6 The structure can also be applied to fixed types of equipment.

[0064] like Figure 6 As shown, the mobile terminal 600 may specifically include: a processor 601, a memory 602, a bus 603, a mobile communication module 604, an antenna 1, a wireless communication module 605, an antenna 2, a display screen 606, a camera module 607, an audio module 608, a power module 609, and a sensor module 610.

[0065] Processor 601 may include one or more processing units, such as: AP (Application Processor), modem processor, GPU (Graphics Processing Unit), ISP (Image Signal Processor), controller, encoder, decoder, DSP (Digital Signal Processor), baseband processor and / or NPU (Neural-Network Processing Unit), etc.

[0066] The processor 601 can be connected to the memory 602 or other components via the bus 603.

[0067] The memory 602 can be used to store computer executable program code, which includes instructions. The processor 601 executes various functional applications and data processing of the mobile terminal 600 by running the instructions stored in the memory 602. The memory 602 can also store application data, such as images, videos, and other files.

[0068] The communication function of the mobile terminal 600 can be implemented through a mobile communication module 604, antenna 1, a wireless communication module 605, antenna 2, a modem processor, and a baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. The mobile communication module 604 can provide 2G, 3G, 4G, and 5G mobile communication solutions for use on the mobile terminal 600. The wireless communication module 605 can provide wireless communication solutions such as wireless local area network, Bluetooth, and near-field communication for use on the mobile terminal 600.

[0069] The display screen 606 is used to implement display functions, such as displaying the user interface, images, and videos. The camera module 607 is used to implement shooting functions, such as capturing images and videos. The audio module 208 is used to implement audio functions, such as playing audio and capturing voice. The power module 209 is used to implement power management functions, such as charging the battery, powering the device, and monitoring the battery status. The sensor module 610 may include a depth sensor 6101, a pressure sensor 6102, a gyroscope sensor 6103, a barometric pressure sensor 6104, etc., to implement corresponding sensing and detection functions.

[0070] The aforementioned electronic device may include the network element management system under the aforementioned service-oriented architecture. The network element management system under the service-oriented architecture may include network storage functions and a management platform. The network storage function includes a service registration interface and a management registration interface. The service registration interface is used to obtain the service domain information of the service-oriented network element, and the management registration interface is used to obtain the management domain information of the service-oriented network element. The management platform is used to obtain the management domain information of the service-oriented network element from the network storage function, so as to establish a communication link with the service-oriented network element based on the management domain information.

[0071] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0072] Exemplary embodiments of this disclosure also provide a computer-readable storage medium having a program product stored thereon capable of implementing the methods described above in this specification. In some possible embodiments, various aspects of this disclosure may also be implemented as a program product including program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure.

[0073] It should be noted that the computer-readable medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0074] In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can transmit, propagate, or transfer a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wireline, optical fiber, RF, etc., or any suitable combination thereof.

[0075] Furthermore, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0076] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0077] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A network element management method under a service-oriented architecture, applied to network storage functions, wherein the network storage functions include a management domain interface, characterized in that, include: Receiving registration information of a service-oriented network element and obtaining management domain information of the service-oriented network element includes: responding to a call instruction from the service-oriented network element to the management domain interface, receiving the registration information of the service-oriented network element through the management domain interface, and obtaining the management domain information of the service-oriented network element; The management domain information of the service-oriented network element is transmitted to the management platform so that the management platform can establish a communication link with the service-oriented network element based on the management domain information.

2. The method according to claim 1, characterized in that, The step of transmitting the management domain information of the service-oriented network element to the management platform includes: The information update instruction is transmitted to the management platform so that the management platform can scan the network storage function to obtain the management domain information of the service-oriented network element according to the information update instruction.

3. The method according to claim 1, characterized in that, In response to the scanning operation of the management platform, the management domain information of the service-oriented network element is transmitted to the management platform.

4. The method according to claim 1, characterized in that, The management domain information includes the management domain address, management domain account, and account management information; the transmission of the management domain information of the service-oriented network element to the management platform includes: The management domain address, the management domain account, and the account management information are transmitted to the management platform.

5. The method according to claim 1, characterized in that, The method further includes: Receive the registration information of the service-oriented network element and obtain the service domain information of the service-oriented network element.

6. A network element management system under a service-oriented architecture, characterized in that, include: The network storage function includes a service registration interface and a management domain interface. The service registration interface is used to obtain the service domain information of the service-oriented network element, and the management domain interface is used to obtain the management domain information of the service-oriented network element. The management domain information of the service-oriented network element is obtained by responding to the service-oriented network element's call instruction to the management domain interface, receiving the registration information of the service-oriented network element through the management domain interface, and obtaining the management domain information of the service-oriented network element. The management platform is used to obtain the management domain information of the service-oriented network element from the network storage function, so as to establish a communication link with the service-oriented network element based on the management domain information.

7. A network element management device under a service-oriented architecture, characterized in that, This is applied to network storage functions, which include a management domain interface, including: The information receiving module is used to receive registration information of the service-oriented network element and obtain the management domain information of the service-oriented network element, including: responding to the service-oriented network element's call instruction to the management domain interface, receiving the registration information of the service-oriented network element through the management domain interface, and obtaining the management domain information of the service-oriented network element; The information upload module transmits the management domain information of the service-oriented network element to the management platform, so that the management platform can establish a communication link with the service-oriented network element based on the management domain information.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the network element management method under the service-oriented architecture as described in any one of claims 1 to 5.

9. An electronic device, characterized in that, include: The network element management system under the service-oriented architecture as described in claim 6.

Images