Interface management methods, devices, electronic devices and storage media
By using the gSOAP tool to generate communication distribution and interface files, the problem of low interface management efficiency of UDM/HSS network elements is solved, and rapid business logic processing and simplified interface management process are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-30
- Publication Date
- 2026-04-03
AI Technical Summary
Currently, UDM/HSS network elements in the 5G core network communicate and encode/decode by implementing their own SOAP APIs, resulting in low interface management efficiency and long development cycles.
The gSOAP tool is used to generate communication distribution files and interface files based on the target WSDL and XSD files, and then compiled into the target network element to enable it to have a remote procedure call interface and realize the business processing of the Boss system.
By simplifying the underlying communication and message encoding/decoding process, the efficiency of interface management is improved, enabling rapid business logic processing and reducing the development cycle.
Smart Images
Figure CN116248467B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, specifically to an interface management method, apparatus, electronic device, and storage medium. Background Technology
[0002] In the current implementation of the Boss capability of UDM / HSS network elements in the 5G core network, manufacturers use their own SOAP APIs for communication and encoding / decoding. However, due to the relatively complex code implementation and the long development cycle for a large number of API interfaces, the current interface management efficiency is low. Summary of the Invention
[0003] This application provides an interface management method, apparatus, electronic device, and storage medium to solve the problem that current manufacturers use their own SOAP APIs for communication and encoding / decoding, which are relatively complex to implement and have long development cycles for a large number of API interfaces, resulting in low interface management efficiency.
[0004] In a first aspect, embodiments of this application provide an interface management method, including:
[0005] Identify the target WSDL file and the target XSD file;
[0006] Using gSOAP, a communication distribution file and an interface file are generated based on the target WSDL file and the target XSD file;
[0007] The communication distribution file and the interface file are compiled into the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0008] In one embodiment, the gSOAP includes the wsdl2h tool and the soapcpp2 tool. The step of generating a communication distribution file and an interface file using gSOAP based on the target WSDL file and the target XSD file includes:
[0009] Using the wsdl2h tool, a target header file is generated based on the target WSDL file and the target XSD file;
[0010] The soapcpp2 tool is used to generate communication distribution files and interface files based on the target header file.
[0011] In one embodiment, gSOAP further includes a service interface for providing the ability to write SOAP service code.
[0012] In one embodiment, after compiling the communication distribution file and the interface file into the target network element, enabling the target network element to have the remote procedure call interface corresponding to the interface file, the method further includes:
[0013] The SOAP service target code of the target network element is determined through the service interface, and the service management of the remote procedure call interface is performed based on the SOAP service target code.
[0014] In one embodiment, the step of generating a communication distribution file and an interface file using gSOAP based on the target WSDL file and the target XSD file further includes:
[0015] Compile the communication distribution file and interface file into a dynamic library file;
[0016] The dynamic library file is linked to the target network element, enabling the target network element to have the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0017] In one embodiment, the target WSDL file and the target XSD file include an interface update file and a version number, used to update the dynamic library file so that the target network element has the remote procedure call interface corresponding to the interface update file.
[0018] In one embodiment, the target network element includes a UDM network element and / or an HSS network element.
[0019] Secondly, embodiments of this application provide an interface management device, including:
[0020] The determination module is used to identify the target WSDL file and the target XSD file;
[0021] The generation module is used to generate a communication distribution file and an interface file based on the target WSDL file and the target XSD file using gSOAP.
[0022] The compilation module is used to compile the communication distribution file and the interface file into the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0023] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the interface management method described in the first aspect.
[0024] Fourthly, embodiments of this application provide a storage medium, which is a computer-readable storage medium including a computer program. When the computer program is executed by a processor, it implements the interface management method described in the first aspect.
[0025] The interface management method, apparatus, electronic device, and storage medium provided in this application generate communication distribution files and interface files based on the target WSDL file and target XSD file using gSOAP. After the communication distribution files and interface files are compiled into the target network element, the target network element has a remote procedure call interface corresponding to the interface file. This allows the business processing of the Boss system corresponding to the target network element to be completed based on the remote procedure call interface. This enables interface management to focus only on specific business operations without considering the underlying communication and SOAP / XML encoding / decoding of messages. Business logic processing can be quickly and directly performed through the interface generated by gSOAP, thereby improving interface management efficiency. Attached Figure Description
[0026] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0027] Figure 1 This is one of the flowcharts illustrating the interface management method provided in the embodiments of this application;
[0028] Figure 2 This is a schematic diagram of the specific process of step 200 in the interface management method provided in the embodiments of this application;
[0029] Figure 3 This is a second flowchart illustrating the interface management method provided in the embodiments of this application;
[0030] Figure 4 This is a schematic diagram of the functional modules of an embodiment of the interface management device of this application;
[0031] Figure 5 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0032] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0033] The interface management method, apparatus, electronic device, and storage medium provided by the present invention will be described in detail below with reference to embodiments.
[0034] Figure 1 This is one of the flowcharts illustrating the interface management method provided in an embodiment of this application. (Refer to...) Figure 1 This application provides an interface management method, which may include:
[0035] Step 100: Identify the target WSDL file and the target XSD file;
[0036] It should be noted that the execution subject of the interface management method provided in this application embodiment can be a computer device, such as a mobile phone, tablet computer, laptop computer, handheld computer, vehicle electronic device, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.
[0037] In this application, users can write WSDL and XSD files according to their needs, and the completed WSDL and XSD files can be identified as the target WSDL file and the target XSD file, respectively.
[0038] For WSDL files, Web Services Description Language (WSDL) is an XML application that defines a set of service access points. Clients can access services containing document-oriented information or procedure-oriented calls (similar to remote procedure calls) through these service access points.
[0039] The WSDL first abstracts and describes the access operations and the request / response messages used during access, and then binds them to specific transport protocols and message formats to ultimately define the service access points for specific deployment.
[0040] The specific service access points deployed in the relevant context can be combined to form an abstract web service.
[0041] WSDL files typically contain seven important elements: types, import, message, portType, operation, binding, and service. These elements are nested within the definitions element, which is the root element of the WSDL file.
[0042] Types is a container for data type definitions, which uses a type system (generally the type system in XML Schema).
[0043] Message is an abstract, typed definition of the data structure for a communication message. The entire message data structure is defined using the types defined by Types.
[0044] An Operation is an abstract description of the operations supported by a service. Generally, a single Operation describes a request / response message pair for an access point.
[0045] PortType is an abstract set of operations supported for a given access point type, which can be supported by one or more service access points.
[0046] Binding is the binding of a specific protocol and data format specification for a specific port type.
[0047] A port is defined as a single service access point that combines a protocol / data format binding with a specific web access address.
[0048] A Service is a collection of access points for related services.
[0049] For XSD files, XSD stands for XML Schema Definition, which is a schema definition file.
[0050] XML Schema is an XML-based syntax or schema specification used to define how XML documents are marked up.
[0051] XML Schema is a schema specification recommended by Microsoft that has significant advantages over Document Type Definitions (DTDs), which were originally used to define XML models.
[0052] The features of XSD include: 1) One of the most important capabilities of XML Schema is its support for data types. It makes it easier to define data constraints (data facets), easier to define data models (or data formats), and easier to convert data between different data types; 2) It uses XML syntax; 3) It can protect data communication; 4) It is scalable; 5) It can catch errors.
[0053] Currently, WSDL files are used to describe the corresponding services, providing an abstract description of request / response messages, as well as the specific transport protocol and message format.
[0054] Use XSD files to describe the definition of data types and their constraints.
[0055] Both the WSDL and XSD files describe the definition and implementation of the interface.
[0056] Step 200: Using gSOAP, generate the communication distribution file and interface file based on the target WSDL file and the target XSD file;
[0057] gSOAP is a type of compilation tool that provides a SOAP / XML implementation in C / C++, making it much easier to develop web services or client programs in C / C++.
[0058] Most C++ web service toolkits provide a set of API function libraries to handle specific SOAP data structures, forcing users to modify their program structure to adapt to these libraries. In contrast, gSOAP utilizes compiler technology to provide a transparent set of SOAP APIs, hiding development-independent SOAP implementation details from the user.
[0059] It should be noted that gSOAP provides the wsdl2h tool and the soapcpp2 tool.
[0060] The wsdl2h tool can be used to convert WSDL and XSD files into .h header files containing data binding interface declaration services and C / C++ data.
[0061] The wsdl2h tool can use commands such as: wsdl2h[options] -o file.h...WSDL and XSD files or URLs to WSDLs and XSDs....
[0062] The soapcpp2 tool can be used as a C / C++ preprocessor to generate source code from .h header files with data binding interfaces.
[0063] The command used by the soapcpp2 tool can be, for example, soapcpp2[options]file.h.
[0064] This application allows the target WSDL file and target XSD file to be input into gSOAP, and the communication distribution file and interface file to be generated using the tools provided by gSOAP.
[0065] Step 300: Compile the communication distribution file and interface file into the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0066] After obtaining the communication distribution file and interface file, this application can compile the interface file and communication distribution file into the target network element, specifically into the project of the target network element.
[0067] Enable the target network element to have the Remote Procedure Call (RPC) interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the RPC interface.
[0068] BOSS (Business & Operation Support System) refers to the business operations support system. Typically, a BOSS system consists of four parts: billing and settlement system, sales and accounting system, customer service system, and decision support system. From a business perspective, BOSS is a framework that houses the business system, CRM system, and billing system, enabling vertical and horizontal management within a unified framework.
[0069] The Boss system can handle tasks including but not limited to adding or deleting contract data, opening accounts, closing accounts, and suspending service.
[0070] It should be noted that the target network element in this application can be a UDM network element and / or an HSS network element.
[0071] In some scenarios, the target network element of this application can be a UDM network element; in some scenarios, the target network element of this application can be an HSS network element; in some scenarios, the target network element of this application can be both a UDM network element and an HSS network element.
[0072] The Unified Data Management (UDM) function can be used for 3GPPAKA authentication, user identification, access authorization, registration, mobility, subscription, SMS management, etc.
[0073] The Home Subscriber Server (HSS) is a server in EPS used to store user subscription information. It is an evolution and upgrade of the 2G / 3G network element HLR and is mainly responsible for managing user subscription data and mobile user location information.
[0074] Furthermore, after compiling the communication distribution file and interface file into the target network element, enabling the target network element to have the remote procedure call interface corresponding to the interface file, the process also includes:
[0075] By using the service interface, the SOAP service target code of the target network element is determined, so as to perform service management of the remote procedure call interface based on the SOAP service target code.
[0076] It should be noted that gSOAP in this application can also provide service interfaces, which can be used to provide the function of writing SOAP service code.
[0077] Therefore, users can use the service interfaces provided by gSOAP to write SOAP service-related code suitable for the UDM / HSS framework, which can then be used as the SOAP service target code for the target network element. The SOAP service can include, but is not limited to, service startup, service shutdown, and service message processing mechanisms.
[0078] After obtaining the SOAP service target code of the target network element, service management of the remote procedure call interface can be performed, such as service startup, service stop, and service message processing.
[0079] The interface management method provided in this application generates communication distribution files and interface files based on the target WSDL file and target XSD file using gSOAP. After the communication distribution files and interface files are compiled into the target network element, the target network element has a remote procedure call interface corresponding to the interface file. This allows the business processing of the Boss system corresponding to the target network element to be completed based on the remote procedure call interface. This enables the interface management to focus only on the specific business without considering the underlying communication and SOAP / XML encoding and decoding of messages. Business logic processing can be quickly and directly performed through the interface generated by gSOAP, thereby improving the efficiency of interface management.
[0080] Figure 2 A schematic diagram illustrating the specific flow of step 200 in the interface management method provided in this embodiment of the application. (Refer to...) Figure 2In one embodiment, a communication distribution file and an interface file are generated using gSOAP based on the target WSDL file and the target XSD file, including:
[0081] Step 201: Using the wsdl2h tool, generate the target header file based on the target WSDL file and the target XSD file;
[0082] After obtaining the target WSDL file and the target XSD file, this application can input the target WSDL file and the target XSD file into the wsdl2h tool provided by gSOAP. The wsdl2h tool will convert the format of the target WSDL file and the target XSD file into the .h file format, and the converted file will be identified as the target header file.
[0083] Step 202: Using the soapcpp2 tool, generate the communication distribution file and interface file based on the target header file.
[0084] After obtaining the target header file, this application can input the target header file into the soapcpp2 tool provided by gSOAP, and the soapcpp2 tool can generate communication distribution files and interface files based on the target header file.
[0085] It should be noted that the wsdl2h tool can generate interface files from a set of WSDL and XSD files, and then input the interface files, along with imported protocol declarations and custom serializers, into the soapcpp2 CLI. The soapcpp2 CLI can further generate data binding implementations and service code.
[0086] This embodiment can generate communication distribution files and interface files based on the target WSDL file and target XSD file using gSOAP. After compiling the communication distribution files and interface files into the target network element, the target network element will have the remote procedure call interface corresponding to the interface file. The business processing of the corresponding Boss system of the target network element can be completed based on the remote procedure call interface. This allows the interface management to focus only on the specific business without considering the underlying communication and SOAP / XML encoding and decoding of messages. Business logic processing can be quickly and directly performed through the interface generated by gSOAP, which can improve the efficiency of interface management.
[0087] Figure 3 This is a second flowchart illustrating the interface management method provided in an embodiment of this application. (Refer to...) Figure 3 In one embodiment, the method of generating a communication distribution file and an interface file based on the target WSDL file and the target XSD file using gSOAP further includes:
[0088] Step 400: Compile the communication distribution file and interface file into a dynamic library file;
[0089] Understandably, the interface between the current Boss system and the UDM / HSS network element requires negotiation between both sides. After the negotiation is completed, the interface is modified according to the file content, and then the software package upgrade is provided at the same time. This approach is inefficient.
[0090] Based on this, after obtaining the communication distribution file and interface file, this application can also compile the communication distribution file and interface file into a dynamic library file, specifically a dynamic library libboss.so file.
[0091] Step 500: Link the dynamic library file to the target network element so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0092] After obtaining the dynamic library file, this application can link the dynamic library file to the target network element, enabling the target network element to have the Remote Procedure Call (RPC) interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0093] Compiling the communication distribution files and interface files into a dynamic library file libboss.so facilitates modular upgrades of the communication interface.
[0094] In this application, WSDL and XSD files can be equipped with file transfer interfaces that carry the current version number information, and an interface for obtaining the version number can also be added.
[0095] Furthermore, the target WSDL file and the target XSD file include an interface update file and a version number, which are used to update the dynamic library file so that the target network element has the remote procedure call interface corresponding to the interface update file.
[0096] Specifically, the BOSS system can update the WSDL and XSD files through the file transfer interface and actively query the corresponding interface version of the connected UDM / HSS network elements.
[0097] When the BOSS system verifies and determines that an upgrade is needed, it sends an interface update file and version number to the UDM / HSS network element.
[0098] After receiving the interface update file and version number, the UDM / HSS network element verifies the file format and version number respectively. After the verification is successful, it calls the compilation module to compile the updated wsdl file and xsd file to achieve automatic compilation and generate libboss.so.
[0099] Meanwhile, the upgrade module parses the WSDL and XSD files, generates relevant business logic code based on interface changes, and calls the compile module to compile the liboper.so module.
[0100] After compilation is complete, the UDM / HSS network element restarts and actively reports the upgrade completion, along with its version number. At this point, the interface version used by the Boss system and the UDM / HSS network element is consistent.
[0101] Since UDM / HSS network elements are data storage network elements, and most of the Boss interfaces are related to adding, deleting, modifying, and querying, a logic module that can automatically generate business code can be implemented, which parses and generates the code for the query database based on the WSDL and XSD files.
[0102] This embodiment can reduce the negotiation process caused by Boss system interface updates by automatically updating the interface through real-time distribution of WSDL and XSD files.
[0103] This application utilizes the gSOAP open-source tool to develop the BOSS functionality for UDM / HSS network elements. It can quickly complete RPC communication and SOAP / XML message serialization and deserialization processing code through structure files. Since gSOAP encapsulates the relevant processing, users only need to focus on the specific business processing of the RPC interface and understand the basic service activation interface to complete the relevant development. Using an automated interface upgrade scheme, the interface upgrade capability of the attached UDM / HSS network elements can be achieved simply by updating the unified interface file through the Boss system. Through modular processing, it achieves automated compilation of interface files, optimizes the complexity of interface upgrades, and enables one-click interface updates.
[0104] The gSOAP compiler automatically generates SOAP / XML format RPC interfaces, providing the API interfaces required for the maintenance of UDM / HSS network elements. A file transfer interface is added between the UDM / HSS network elements and the Boss system, enabling real-time upgrades of network element interfaces after changes to the Boss system interface. The UDM / HSS network elements parse WSDL and XSD files to generate business code modules, completing one-click automated processing of interface upgrades.
[0105] Furthermore, this application also provides an interface management device.
[0106] Reference Figure 4 , Figure 4 This is a schematic diagram of the functional modules of an embodiment of the interface management device of this application.
[0107] The interface management device includes:
[0108] Module 410 is used to determine the target WSDL file and the target XSD file;
[0109] The generation module 420 is used to generate a communication distribution file and an interface file based on the target WSDL file and the target XSD file using gSOAP.
[0110] The compilation module 430 is used to compile the communication distribution file and the interface file into the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0111] The interface management device provided in this application generates a communication distribution file and an interface file based on the target WSDL file and the target XSD file using gSOAP. After the communication distribution file and the interface file are compiled into the target network element, the target network element has a remote procedure call interface corresponding to the interface file. The business processing of the Boss system corresponding to the target network element is completed based on the remote procedure call interface. This allows the user to focus only on the specific business when managing interfaces, without considering the underlying communication and SOAP / XML encoding and decoding of messages. Business logic processing can be performed quickly and directly through the interface generated by gSOAP, which can improve the efficiency of interface management.
[0112] In one embodiment, the generation module 420 is used for:
[0113] Using the wsdl2h tool, a target header file is generated based on the target WSDL file and the target XSD file;
[0114] The soapcpp2 tool is used to generate communication distribution files and interface files based on the target header file.
[0115] In one embodiment, the generation module 420 is further configured to:
[0116] Compile the communication distribution file and interface file into a dynamic library file;
[0117] The dynamic library file is linked to the target network element, enabling the target network element to have the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0118] In one embodiment, compiler module 430 is used for:
[0119] The SOAP service target code of the target network element is determined through the service interface in order to perform service management of the remote procedure call interface.
[0120] Figure 5 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5 As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other via the communication bus 540. The processor 510 can call a computer program in the memory 530 to execute the steps of the interface management method, such as including:
[0121] Identify the target WSDL file and the target XSD file;
[0122] Using gSOAP, a communication distribution file and an interface file are generated based on the target WSDL file and the target XSD file;
[0123] The communication distribution file and the interface file are compiled into the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0124] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0125] On the other hand, embodiments of this application also provide a storage medium, which is a computer-readable storage medium storing a computer program. The computer program is used to cause a processor to execute the steps of the methods provided in the above embodiments, including, for example:
[0126] Identify the target WSDL file and the target XSD file;
[0127] Using gSOAP, a communication distribution file and an interface file are generated based on the target WSDL file and the target XSD file;
[0128] The communication distribution file and the interface file are compiled into the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface.
[0129] The computer-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical storage (e.g., CD, DVD, BD, HVD), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).
[0130] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0131] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. An interface management method, characterized in that, include: Identify the target WSDL file and the target XSD file; Using gSOAP, a communication distribution file and an interface file are generated based on the target WSDL file and the target XSD file; Compile the communication distribution file and interface file into a dynamic library file; The dynamic library file is linked to the target network element, enabling the target network element to have the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface; the target network element includes UDM network element and / or HSS network element; The BOSS system updates the WSDL and XSD files through the file transfer interface and actively queries the interface version corresponding to the connected UDM / HSS network elements. When the BOSS system verifies and determines that an upgrade is needed, it sends an interface update file and version number to the UDM / HSS network element. After receiving the interface update file and version number, the UDM / HSS network element verifies the file format and version number respectively. After the verification is successful, it calls the compilation module to compile the updated wsdl file and xsd file and generate libboss.so. The upgrade module parses the WSDL and XSD files, generates relevant business logic code based on interface changes, and calls the compilation module to compile the liboper.so module. After compilation, the UDM / HSS network element restarts and actively reports the upgrade completion, along with the version number. At this point, the interface version used by the Boss system and the UDM / HSS network element is consistent.
2. The interface management method according to claim 1, characterized in that, The gSOAP includes the wsdl2h tool and the soapcpp2 tool. The process of generating a communication distribution file and an interface file using gSOAP, based on the target WSDL file and the target XSD file, includes: Using the wsdl2h tool, a target header file is generated based on the target WSDL file and the target XSD file; The soapcpp2 tool is used to generate communication distribution files and interface files based on the target header file.
3. The interface management method according to claim 1, characterized in that, The gSOAP also includes a service interface for providing the ability to write SOAP service code.
4. The interface management method according to claim 1, characterized in that, The target WSDL file and the target XSD file include an interface update file and a version number, which are used to update the dynamic library file so that the target network element has the remote procedure call interface corresponding to the interface update file.
5. An interface management device, characterized in that, include: The determination module is used to identify the target WSDL file and the target XSD file; The generation module is used to generate a communication distribution file and an interface file based on the target WSDL file and the target XSD file using gSOAP. The generation module is further configured to compile the communication distribution file and the interface file into a dynamic library file; connect the dynamic library file to the target network element, so that the target network element has the remote procedure call interface corresponding to the interface file, so as to complete the business processing of the Boss system corresponding to the target network element based on the remote procedure call interface; the target network element includes UDM network element and / or HSS network element; the target network element includes UDM network element and / or HSS network element; The BOSS system updates the WSDL and XSD files through the file transfer interface and actively queries the interface version corresponding to the connected UDM / HSS network elements. When the BOSS system verifies and determines that an upgrade is needed, it sends an interface update file and version number to the UDM / HSS network element. After receiving the interface update file and version number, the UDM / HSS network element verifies the file format and version number respectively. After the verification is successful, it calls the compilation module to compile the updated wsdl file and xsd file and generate libboss.so. The upgrade module parses the WSDL and XSD files, generates relevant business logic code based on interface changes, and calls the compilation module to compile the liboper.so module. After compilation, the UDM / HSS network element restarts and actively reports the upgrade completion, along with the version number. At this point, the interface version used by the Boss system and the UDM / HSS network element is consistent.
6. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the interface management method according to any one of claims 1 to 4.
7. A storage medium, said storage medium being a computer-readable storage medium, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the interface management method according to any one of claims 1 to 4.