CN107645413B - Intelligent telephone switching network core side access side fully automatic configuration platform and method - Google Patents

Abstract

The invention discloses a fully automatic configuration platform and method for the access side of the core side of an intelligent telephone switching network. The B/S architecture is adopted, and the front end performs parameter configuration through a Web page; the back end includes HTTP servers A and B, and business application servers C and D. , database servers E and F. Two HTTP servers, A and B, are respectively connected to service application servers C and D, and service application servers C and D are respectively connected to database servers E and F, and are connected to the IMS core side and the IMS access side through CE core switches 7706, The provincial network PE-NE20 and the national network PE-Cisco7609 mainly communicate with the backbone communication network, and complete the data exchange with the SPG northbound interface of the IMS. Beneficial effects of the present invention: the present invention realizes integrated delivery of IMS core network configuration and IMS access network configuration information, standardizes data information, and simplifies IP equipment maintenance steps.

Description

Intelligent telephone switching network core side access side fully automatic configuration platform and method

technical field

The invention relates to the field of intelligent and automatic configuration of network authentication information and terminal parameter information in the field of IMS communication network, in particular to a platform and method for automatic configuration of the access side of the core side of an intelligent telephone switching network.

Background technique

At present, the IMS administrative switching network of State Grid Shandong Electric Power Company is centrally deployed in the provincial company, with three-level access in the province, city and county. The parameter configuration of the SIP terminal and the IAD device connected to the IMS needs to be completed on the core network side and the access network side respectively. The parameter configuration on the core network side is completed by the operation and maintenance personnel of the provincial company by executing more than 20 instructions on the HSS, ATS, and ENS network elements respectively. The web pages of the SIP terminal and the IAD device are completed. With the gradual transition of program-controlled switching users to the IMS switching network, the network structure of the IMS administrative switching network of the power grid has become increasingly complex. It is isolated from the access-side network, the configuration process is cumbersome, there is a lack of intelligent and fully automatic configuration methods, and there is a lack of a one-click synchronization configuration mechanism for the access-side terminal equipment on the core network element and the access-side integrated operation and maintenance support platform.

The specific problem is described as follows:

The IMS core network element needs to execute more than 20 instructions in five steps to store the account opening information of the SIP terminal and IAD device. The HSS network element stores the SUBID, IMPI ID, IMPI authentication type, user name and password, capability level of the access terminal. Template ID, billing information template ID, ServiceProfile template ID, implicit registration-level template ID and other information; ATS network element stores smart service information, group information, extended data, etc. of terminal equipment; ENS network element stores NAPTR resources of terminal equipment Records, including E164 numbers, area names, regular expressions, etc. The IMS access-side integrated operation and maintenance support platform equipment needs to be configured with information such as the MAC address, SN identifier, and user of the access-side terminal equipment; SBC address and other fields. The separate configuration process of the core side and the access side of the IMS administrative switching network is cumbersome, the manual configuration error rate is high, and the error checking is time-consuming and labor-intensive.

With the transition of 100,000 users across the province to IMS, the number of users carried by the IMS administrative switching network is increasing, and the types of terminal equipment on the access side are different. The synchronization and simultaneity of the parameter configuration of the inbound side are becoming more and more demanding.

SUMMARY OF THE INVENTION

In order to solve the problem of isolating and configuring authentication information and parameter information on the core side and the access side of the existing IMS administrative switching network, the present invention discloses a platform and a method for the automatic configuration of the access side on the core side of the intelligent telephone switching network. The fully automatic one-click synchronous configuration platform realizes the intelligent, automatic and synchronous configuration of the integrated operation and maintenance support system of the core network element and the access side, and the terminal Web page, so as to achieve the goal of one-click installation.

In order to achieve the above object, the present invention adopts the following technical solutions:

The invention discloses a fully automatic configuration platform on the access side of the core side of an intelligent telephone switching network, based on a B/S architecture, comprising:

Equipment layer, including IMS core network elements, IMS access network IAD and IMS access network IP phones;

The adaptation layer is used to implement service configuration, protocol configuration, interface configuration and connection management with the device layer;

Persistence layer, including database server E and database server F, is used to realize the storage and reading of configuration information, authentication information, and subscription information, real-time synchronization, and master-standby disaster recovery;

The application layer, including the business application server C and the business application server D, is used to realize dual-machine mutual backup and prevent single point failure. IP phone for communication;

HTTP forwarding layer, including HTTP server A and HTTP server B, is used to realize the mutual backup mechanism of http service using Nginx's HTTP service and keepalived technology, realize load balancing of application server C and application server D, and provide WEB to lower-level access points. system access entry;

The presentation layer is used for parameter configuration through the Web page;

The HTTP server A and the HTTP server B of the HTTP forwarding layer are respectively connected with the application layer business application server C and the business application server D; the application layer business application server C and the business application server D are respectively connected with the persistence layer database server E, database The server F is connected to the adaptation layer, the adaptation layer, the persistence layer and the device layer respectively communicate.

Further, when the service configuration is automatically issued, the user accesses the front-end web page of the platform, and the operation and maintenance personnel at all levels access the back-end main HTTP server through the information intranet or access network, and the HTTP server is routed to the main service application through the load. The server, the business application server performs verification according to the business type and request data, and generates a business record; and parses out the business interface of the core network or the access network according to the business record;

The IMS core network performs data analysis according to the service interface number to form one or more network element operation requests, encapsulates message instructions according to the network element operation requests, and sends operation instructions to the IMS core network elements in sequence.

Further, after the IMS core network completes all network element operation requests, the application layer parses the returned results, and forms one or more configuration requests according to the service interface number to send instructions to the specified access-side device, parses the returned responses, and finally forms The unified response results are recorded to the persistent layer database server according to the corresponding results and business keywords, and the final result description of the business configuration is displayed to the user, and is returned to the Web page of the presentation layer through the HTTP forwarding layer response.

Further, the business application server includes a front-end controller IMSAdmin, and the front-end controller IMSAdmin is divided into four layers, specifically: a Controller layer, a Service layer, a DAO layer and a Call layer;

The front-end controller IMSAdmin performs data format verification through the Controller layer; encapsulates business logic application requests through the Service layer; performs data interaction with the database server through the DAO layer; and completes remote calls through the Call layer.

Further, the business application server includes an interface adaptation service InterfaceAdapter;

The interface service adapter InterfaceAdapter communicates with the IMS core network element and the IMS access network terminal equipment through the northbound interface in the HTTP+SOAP manner.

Further, the interface service adapter InterfaceAdapter and the IMS access network equipment conduct information exchange through the State Grid PE backbone network, core CE, and access CE, and the information exchange type includes: HTTP, TELNET or STELNET; complete user name, password request authentication , packet encapsulation, packet analysis, decryption and decryption, authentication and authentication, and provide unified data standards for the IMS core network side and the access network side through the northbound SPG interface.

Further, the business application server includes a message queue Kafka service; the Kafka service is used to solve the problem of parameter configuration and instruction delivery when the IMS core network or the access network terminal is not registered or disconnected;

After the core network completes all network element operation requests, it parses the returned results, and forms one or more configuration requests according to the service interface number to send commands to the specified access-side device. After a command, it requests the target terminal through HttpUrlConnection. If the target terminal is offline or unregistered, the command will be re-queued; if the target terminal is registered, the command will be dequeued to complete the delivery to the terminal device.

The invention also discloses a fully automatic configuration method for the access side of the core side of the intelligent telephone network switching, including:

The specific process of the interface service adapter InterfaceAdapter interacting with the IMS core network is as follows:

Step 1: Start the interface business adapter InterfaceAdapter;

Step 2: The interface business adapter InterfaceAdapter performs cache processing, and caches the data information of the business definition data table NT_BUSI_DEFINE, the interface definition data table INT_INTERFACE_DEFINE, the interface SCHEMA definition table INT_SCHEMA_DEFINE, and the interface element definition table INT_ELEMENT_DEFINE to Redis;

Step 3: The interface business adapter InterfaceAdapter receives the business operation request, and indexes the detailed business information from Redis according to the business ID in the request;

Step 4: Parse the business information, including the interface ID for executing the business and the interface ID for rolling back the business;

Step 5: Index the interface definition data table INT_INTERFACE_DEFINE in Redis according to the interface ID in Step 4, and obtain the IP address, port, request method and timeout time of the interface;

Step 6: Obtain the request message element and the response message element of the interface protocol in the interface element definition table INT_ELEMENT_DEFINE, and assemble the SOAP message object according to the parent-child relationship;

Step 7: Obtain the SCHEMA information of the interface protocol in the interface SCHEMA definition table INT_SCHEMA_DEFINE, and form a SOAP object by assembling the HEADER element, the BODY element and the SCHEMA information;

Step 8: According to the definition of the wildcard rule, replace the key data elements of the business operation request into the message structure in the form of key-value pairs, and convert the SOAP message object into a text type String through the toString() method;

Step 9: Operation request information of the IMS core network element After completing the message encapsulation according to the above steps 5-8, initiate a request to the target network element through HttpUrlConnection in JAVA and obtain the response of the IMS core network, connection timeout and request timeout The time is set according to the configuration, and the read response information parses the data of the returned message from the core network according to the response message body structure of the data table.

The invention also discloses a fully automatic configuration method for the access side of the core side of the intelligent power IMS switching network, including: the specific process of the interface service adapter InterfaceAdapter interacting with the access network is as follows:

Step 1: Start the Redis database server, and store the verification information table INT_COMMON_ENCRYPT, terminal device information table INT_BUSI_DEVICEINTREL, and business interface table INT_COMMON_Bizdefineorigin in the database server;

Step 2: The interface service adapter InterfaceAdapter parses the response information returned by the IMS core network, determines whether the operation request of the Web page is successfully delivered to the core network, and if so, executes step 3; otherwise, returns to step 1;

Step 3: The interface service adapter InterfaceAdapter judges the service request sent to the access network terminal equipment, and verifies whether the request is legal, and stores the verification information in the INT_COMMON_ENCRYPT table. If it is a legal request, it is searched according to the service number in the verification information table. Corresponding business interface;

Step 4: query the terminal device information table INT_BUSI_DEVICEINTREL according to the destination terminal MAC address in the service request, obtain information such as terminal type, brand, etc., and obtain the interface information of the terminal at the same time, and perform interface protocol adaptation;

Step 5: According to the terminal type in Step 4, perform configuration and delivery operations.

Further, the data distribution operation performed in the step 5 is specifically:

If it is an IAD device, select TELNET or STELNET protocol to connect the terminal device, and store all configuration instructions in the Kafka message queue;

The Kafka message queue defines two object roles, Producer and Customer. The Producer completes the configuration command entry operation; the Customer judges whether the IAD device is registered or online, and if so, selects the port to issue the configuration command; if not, defines a temporary queue , cache the configuration instructions, and judge the connectivity status of the IAD device every set time, if it is connected, the configuration instructions are taken out from the cache queue, and the configuration is automatically issued;

If the IP phone device generates the corresponding configuration file according to the brand and model, put the configuration file in the directory specified by the configuration file server for configuration delivery.

Beneficial effects of the present invention:

The invention realizes the integrated delivery of the IMS core network configuration and the IMS access network configuration information, regulates the data information, and simplifies the maintenance steps of the IP equipment.

The platform of the invention can reduce the work pressure of operation and maintenance personnel, and replace manual configuration with automatic means; avoid frequent operation of the core side and the access side separately, resulting in asynchronous data on the core side and the access side, resulting in dirty data; The synchronous configuration platform realizes the intelligent, automatic and synchronous configuration of the integrated operation and maintenance support system of the core network element and the access side, and the terminal Web page, so as to achieve the goal of one-click installation.

Description of drawings

Figure 1 is a network architecture diagram of a platform for fully automatic configuration on the access side of the core side of the intelligent power IMS switching network;

Fig. 2 is the logical function architecture diagram of the platform;

FIG. 3 is a flow chart of the service configuration of the present invention.

Detailed ways

The present invention will be further described below with reference to the accompanying drawings and specific embodiments.

The invention discloses a platform for fully automatic configuration of the access side of the core side of an intelligent power IMS switching network, which adopts a B/S architecture, as shown in Figure 1, the front end configures parameters through a Web page; HTTP server B, business application server C and business application server D, database server E and database server F. Two HTTP servers, HTTP server A and HTTP server B, are connected to business application server C and business application server D respectively. Request packet forwarding and load balancing of back-end cluster applications are realized through Nginx HTTP service, which is implemented based on Linux server through Keepalived technology. Active and standby 1:1 disaster recovery; the business application server C and business application server D are connected to database server E and database server F respectively, and are deployed in a 1:1 mode for active and standby disaster recovery, and are connected to the IMS core side and the IMS The side communicates through the backbone communication network dominated by CE core switch 7706, provincial network PE-NE20, and national network PE-Cisco7609, and completes data exchange with the SPG northbound interface of IMS; the database server E and database server F are used for configuration Storage and reading of information, authentication information and contract information, real-time synchronization, active and standby disaster recovery.

The logical function architecture of the fully automatic configuration platform on the access side at the core side of the intelligent telephone switched network is shown in Figure 2, including:

Equipment layer, including IMS core network elements, IMS access network IAD and IMS access network IP phones;

The adaptation layer is used to implement service configuration, protocol configuration, interface configuration and connection management with the device layer;

Persistence layer, including database server E and database server F, is used to realize the storage and reading of configuration information, authentication information, and subscription information, real-time synchronization, and master-standby disaster recovery;

The application layer, including the business application server C and the business application server D, is used to realize dual-machine mutual backup and prevent single point failure. IP phone for communication;

HTTP forwarding layer, including HTTP server A and HTTP server B, is used to realize the mutual backup mechanism of http service using Nginx's HTTP service and keepalived technology, realize load balancing of application server C and application server D, and provide WEB to lower-level access points. system access entry;

The presentation layer is used for parameter configuration through the Web page;

HTTP forwarding layer HTTP server A and HTTP server B are respectively connected with application layer business application server C and business application server D; application layer business application server C and business application server D are respectively connected with persistence layer database server E, database server F and adaptation Layer connection, adaptation layer persistence layer and device layer communicate separately.

HTTP server A and HTTP server (forwarding and load) B are respectively connected to application server C and application server D, and application server C and application server D are connected to database server E and database server F.

Active-active synchronization of database services on database server E and database server F.

Application server C and application server D (implementing services and big data analysis), IMS core network elements, and IMS access network equipment CE communicate through the internal backbone network, and application server C and application server D respectively complete data with the SPG northbound interface of IMS. communication.

HTTP server A and HTTP server B use Nginx's HTTP service and keepalived technology to realize the mutual backup mechanism of HTTP service, realize the load balancing of application server C and application server D, and provide WEB system access points to lower-level intervention points such as provinces, cities, and counties. .

The Nignx HTTP service provides HTTP request packet forwarding and load balancing functions for back-end cluster applications, and the Keepalived technology implements 1:1 disaster recovery of active and standby HTTP servers based on Linux servers.

The application server C and the application server D are used for dual-machine mutual backup and single-point failure prevention, and communicate with each network element of the IMS core network and each access device of the IMS access network through the network.

It should be noted that the HTTP server A and the HTTP server B, the business application server C and the business application server D, and the database server E and the database server F are in a master-slave relationship with each other.

The business application server includes the front-end controller IMSAdmin, the interface adaptation service InterfaceAdapter, and the message queue Kafka service.

The front-end controller IMSAdmin is divided into four layers. Data format verification is performed through the Controller layer; business logic application requests are encapsulated through the Service layer; data interaction with the database server through the DAO layer; Complete the core-side and access-side service configuration and automatic parameter distribution.

The interface service adapter InterfaceAdapter communicates with the IMS core network elements (HSS, ATS, ENS) and the IMS access side terminal equipment through the northbound interface in the HTTP+SOAP mode.

The interface service adapter InterfaceAdapter and the access network equipment exchange information through the State Grid PE backbone network, core CE, and access CE. The information exchange types include HTTP, TELNET, STELNET, etc. It provides unified data standards for the IMS core side and the access side through the northbound SPG interface.

The Kafka service mainly solves the problem of parameter configuration and command delivery when the access terminal on the IMS core side is not registered or disconnected. After the core network completes all network element operation requests, the interface service adapter InterfaceAdapter parses the returned results, and forms one or more configuration requests according to the service interface number to send commands to the specified access-side device. All commands are entered into the message queue in turn, and messages are retrieved After the first command in the queue, request to the target terminal through HttpUrlConnection. If the target terminal is offline or unregistered, the command will be re-queued; if the target terminal is registered, the command will be dequeued to complete the delivery to the terminal device.

It should be noted that the B/S architecture involves http requests, and HttpUrlConnection is a way of requesting through the HTTP protocol.

URLConnection is an abstract class that has two direct subclasses, HttpURLConnection and JarURLConnection. Another important class is URL, usually URL can generate a URL instance pointing to a specific address by passing a String type parameter to the constructor.

Each HttpURLConnection instance can be used to generate a single request, but other instances can transparently share the underlying network connected to the HTTP server. Calling the close() method on the HttpURLConnection's InputStream or OutputStream after a request releases the network resources associated with this instance, but has no effect on the shared persistent connection. If the persistent connection is idle when disconnect() is called, the underlying socket may be closed.

As shown in Figure 3, when the service configuration is automatically issued, the user accesses the front-end Web page of the platform, and the provincial, city and county operation and maintenance personnel access the back-end main HTTP server through the information intranet or access network, and the HTTP server is routed to the main server through the load. Using the business application server, the application server checks the business type and request data through the IMSAdmin controller, enters the Service service layer to generate business records, and the HTTP JSON interface transmits the business request to the interface business adapter InterfaceAdapter. The interface service adapter, InterfaceAdapter, parses out the service interface of the core network or the access network according to the service record. The core network parses the data according to the service interface number to form one or more network element operation requests, and encapsulates the packet instructions according to the network element operation request. Send operation instructions to the IMS core network HSS, ATS, and ENS network elements in sequence, and perform analysis to return the analysis result. After the core network completes all network element operation requests, the interface service adapter InterfaceAdapter parses the returned results, and forms one or more configuration requests according to the service interface number to send commands to the specified access-side device, parses the returned responses, and finally forms a unified The response result is returned to the front controller (IMSAdmin). The front-end controller (IMSAdmin) application records to the database server according to the returned results and business keywords, and displays the final result description of the business configuration to the user. The response to the user's browser is displayed to the end user via an HTTP Response. The configuration of each network element of the IMS core network and each access device (IAD device, IP phone) of the IMS access network is automatically delivered through the page operation.

In view of the installation timeliness of the access network equipment, the Kafka message queue mechanism is provided to dequeue and complete the execution of the command when the connected device can be connected to the network, and the execution of the command for the access device that is not powered on or not connected to the network will fail to execute. Re-enter the queue after the execution of the dequeue fails, and wait for the network to connect to the queue to issue the command FIFO.

(All instructions are queued, and after taking out the instructions in the queue, request to the target address through HttpUrlConnection. If the target is unreachable, the instructions will be re-queued; otherwise, the queue will be dequeued, and the configuration will be issued.)

The Nginx soft load in the HTTP server communicates with the application server through HTTP forwarding. The HTTP server A and B nodes use keepalived to complete mutual backup and disaster recovery through sockets.

The interface business adapter InterfaceAdapter interacts with the core network using HTTP+SOAP. The specific process is as follows:

Step 1: Start the interface business adapter InterfaceAdapter.

Step 2: The interface service adapter performs cache processing, and caches data information such as the service definition data table NT_BUSI_DEFINE, the interface definition data table INT_INTERFACE_DEFINE, and the interface SCHEMA definition table INT_SCHEMA_DEFINE to Redis.

Step 3: The interface service adapter receives the service operation request from IMSAdmin, and indexes detailed service information from Redis according to the service ID in the request.

Step 4: Parse the business information, including the interface ID for executing the business and the interface ID for rolling back the business;

Step 5: Index the interface definition data table INT_INTERFACE_DEFINE in Redis according to the interface ID in Step 4, and obtain the IP address, port, request method, and timeout time of the interface.

Step 6: Obtain the request message element and the response message element of the interface protocol in the interface element definition table INT_ELEMENT_DEFINE, and assemble the SOAP message object according to the parent-child relationship.

Step 7: Obtain the SCHEMA requirements of the interface protocol in the interface SCHEMA definition table INT_SCHEMA_DEFINE, and form a SOAP object by assembling the HEADER element, the BODY element and the SCHEMA information.

Among them, the HEADER element and the BODY element are the message header and the message body respectively. This is the request method of HTTP+SOAP, which is the composition of the SOAP request.

Step 8: According to the definition of the wildcard rule, replace the key data elements of the business operation request into the message structure in the form of key-value pairs, and convert the SOAP message object into a text type String through the toString() method.

Step 9: After the operation request information of the IMS core network elements HSS, ATS, and ENS completes the message encapsulation according to the above steps 5, 6, 7, and 8, initiates a request to the target network element through HttpUrlConnection in JAVA and obtains the information of the IMS core network. Response, connection timeout and request timeout are set according to the configuration, and the read response information parses the data returned by the core network according to the response message body structure of the data table.

The interface service adapter InterfaceAdapter interacts with the access network using the TR069 protocol, TELNET, and STENET methods. The specific process is as follows:

Step 1: Start the Redis database server, and store the verification information table INT_COMMON_ENCRYPT, the terminal device information table INT_BUSI_DEVICEINTREL, and the business interface table INT_COMMON_Bizdefineorigin in the database server.

Step 2: The interface service adapter InterfaceAdapter parses the response information returned by the IMS core network, judges that the request is successful, and executes Step 3.

Among them, "successful request" means that the configuration of the core network has been issued. The intuitive steps are: after operating from the Web page, the platform of the invention first issues the configuration to the core network, and the core network completes the operation and the operation is successful. Afterwards, the platform of the invention delivers the configuration to the access side.

For the operation and maintenance personnel, they just click the mouse on the Web page of the invention platform to fill in the information, and the information is automatically sent to the core network and the access network through the background.

Step 3: The interface service adapter InterfaceAdapter judges the service request sent to the access network terminal equipment, and verifies whether the request is legal, and stores the verification information in the INT_COMMON_ENCRYPT table. If it is a legal request, it is searched according to the service number in the verification information table. Corresponding business interface.

Step 4: Query the terminal device information table INT_BUSI_DEVICEINTREL according to the destination terminal MAC address in the service request, obtain information such as terminal type, brand, etc., and at the same time obtain terminal interface information, and perform interface protocol adaptation.

Step 5: According to the terminal type in Step 4, perform configuration and delivery operations. If it is an IAD device, select TELNET or STELNET protocol to connect the terminal device. And store all configuration instructions in the Kafka message queue. The Kafka message queue defines two object roles, Producer and Customer. The Producer completes the configuration command entry operation; the Customer judges whether the IAD device is registered or online, and if so, selects the port to issue the configuration command; if not, defines a temporary queue , cache the configuration instruction, and judge the connectivity status of the IAD device every 10s. If it is connected, the configuration instruction is taken out from the cache queue to automatically issue the configuration. If the IP phone device generates the corresponding configuration file according to the brand and model, put the configuration file in the directory specified by the configuration file server for configuration delivery.

Although the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, they do not limit the scope of protection of the present invention. Those skilled in the art should understand that on the basis of the technical solutions of the present invention, those skilled in the art do not need to pay creative work. Various modifications or variations that can be made are still within the protection scope of the present invention.

Claims (9)

1. an intelligent telephone switched network core side access side fully automatic configuration platform, based on B/S architecture, is characterized in that, comprises: Equipment layer, including IMS core network elements, IMS access network IAD and IMS access network IP phones; The adaptation layer is used to implement service configuration, protocol configuration, interface configuration and connection management with the device layer; Persistence layer, including database server E and database server F, is used to realize the storage and reading of configuration information, authentication information, and subscription information, real-time synchronization, and master-standby disaster recovery; The application layer, including the business application server C and the business application server D, is used to realize dual-machine mutual backup and prevent single point failure. IP phone for communication; HTTP forwarding layer, including HTTP server A and HTTP server B, is used to realize the mutual backup mechanism of http service using Nginx's HTTP service and keepalived technology, realize load balancing of application server C and application server D, and provide WEB to lower-level access points. system access entry; The presentation layer is used for parameter configuration through the Web page; The HTTP server A and the HTTP server B of the HTTP forwarding layer are respectively connected with the application layer business application server C and the business application server D; the application layer business application server C and the business application server D are respectively connected with the persistence layer database server E, database The server F is connected to the adaptation layer, and the adaptation layer, the persistence layer and the device layer communicate respectively; When the service configuration is automatically issued, users access the front-end web page of the platform, and operation and maintenance personnel at all levels access the main back-end HTTP server through the information intranet or access network. The HTTP server is routed to the service application server through load balancing. The server performs verification according to the service type and request data, and generates a service record; and parses out the service interface of the core network or the access network according to the service record; The interface service adapter of the service application server performs data analysis according to the service interface number to form one or more network element operation requests, encapsulates message instructions according to the network element operation request, and sends operation instructions to the IMS core network elements in sequence. 2. The fully automatic configuration platform on the access side of the core side of an intelligent switched telephone network as claimed in claim 1, characterized in that after the IMS core network completes all network element operation requests, the application layer parses the returned results, and according to the The service interface number forms one or more configuration requests to send instructions to the specified access-side device, parses the returned responses, and finally forms a unified response result, which is recorded to the persistent layer database server according to the corresponding results and business keywords, and displayed to the user. The final result description of the business configuration is returned to the Web page of the presentation layer through the HTTP forwarding layer response. 3. The fully automatic configuration platform on the access side of the core side of an intelligent switched telephone network according to claim 1, wherein the service application server comprises a front-end controller IMSAdmin, and the front-end controller IMSAdmin is divided into four parts. Layer, specifically: Controller layer, Service layer, DAO layer and Call layer; The front-end controller IMSAdmin performs data format verification through the Controller layer; encapsulates business logic application requests through the Service layer; performs data interaction with the database server through the DAO layer; and completes remote calls through the Call layer. 4. The fully automatic configuration platform on the access side of the core side of an intelligent telephone switched network according to claim 1, wherein the business application server comprises an interface adaptation service InterfaceAdapter; The interface service adapter InterfaceAdapter communicates with the IMS core network element and the IMS access network terminal equipment through the northbound interface in the HTTP+SOAP manner. 5. The fully automatic configuration platform on the access side of the core side of an intelligent telephone switched network as claimed in claim 4, wherein the interface service adapter InterfaceAdapter and the IMS access network equipment pass through the national network PE backbone network, the core CE, access CE for information exchange, information exchange types include: HTTP, TELNET or STELNET; complete user name, password request authentication, packet encapsulation, packet parsing, encryption and decryption, and authentication and authentication, and pass the northbound SPG interface to the IMS The core network side and the access network side provide unified data standards. 6. The fully automatic configuration platform on the access side of the core side of an intelligent telephone switching network as claimed in claim 1, wherein the business application server comprises a message queue Kafka service; the Kafka service is used to resolve the IMS core Problems in parameter configuration and command delivery when the network or access network terminal is not registered or disconnected; After the core network completes all network element operation requests, it parses the returned results, and forms one or more configuration requests according to the service interface number to send commands to the specified access-side device. After a command, it requests the target terminal through HttpUrlConnection. If the target terminal is offline or unregistered, the command will be re-queued; if the target terminal is registered, the command will be dequeued to complete the delivery to the terminal device. 7. A fully automatic configuration method for the access side of the core side of an intelligent telephone switched network, characterized in that it comprises: The specific process of the interface service adapter InterfaceAdapter interacting with the IMS core network is as follows: Step 1: Start the interface business adapter InterfaceAdapter; Step 2: The interface business adapter InterfaceAdapter performs cache processing, and caches the data information of the business definition data table NT_BUSI_DEFINE, the interface definition data table INT_INTERFACE_DEFINE, the interface SCHEMA definition table INT_SCHEMA_DEFINE, and the interface element definition table INT_ELEMENT_DEFINE to Redis; Step 3: The interface business adapter InterfaceAdapter receives the business operation request, and indexes the detailed business information from Redis according to the business ID in the request; Step 4: Parse the business information, including the interface ID for executing the business and the interface ID for rolling back the business; Step 5: Index the interface definition data table INT_INTERFACE_DEFINE in Redis according to the interface ID in Step 4, and obtain the IP address, port, request method and timeout time of the interface; Step 6: Obtain the request message element and the response message element of the interface protocol in the interface element definition table INT_ELEMENT_DEFINE, and assemble the SOAP message object according to the parent-child relationship; Step 7: Obtain the SCHEMA information of the interface protocol in the interface SCHEMA definition table INT_SCHEMA_DEFINE, and form a SOAP object by assembling the HEADER element, the BODY element and the SCHEMA information; Step 8: According to the definition of the wildcard rule, replace the key data elements of the business operation request into the message structure in the form of key-value pairs, and convert the SOAP message object into a text type String through the toString() method; Step 9: The operation request information of the IMS core network element is completed according to the above steps 5 to 8. After the message encapsulation is completed, a request is initiated to the target network element through HttpUrlConnection in JAVA and the response of the IMS core network is obtained, connection timeout and request timeout time According to the configuration settings, the read response information parses the data of the returned message from the core network according to the response message body structure of the data table. 8. A fully automatic configuration method for the access side of the core side of an intelligent telephone switched network, characterized in that it comprises: the specific process of the interaction between the interface service adapter InterfaceAdapter and the access network is: Step 1: Start the Redis database server, and store the verification information table INT_COMMON_ENCRYPT, terminal device information table INT_BUSI_DEVICEINTREL, and business interface table INT_COMMON_Bizdefineorigin in the database server; Step 2: The interface service adapter InterfaceAdapter parses the response information returned by the IMS core network, determines whether the operation request of the Web page is successfully delivered to the core network, and if so, executes step 3; otherwise, returns to step 1; Step 3: The interface service adapter InterfaceAdapter judges the service request sent to the access network terminal equipment, and verifies whether the request is legal, and stores the verification information in the INT_COMMON_ENCRYPT table. If it is a legal request, it is searched according to the service number in the verification information table. Corresponding business interface; Step 4: query the terminal device information table INT_BUSI_DEVICEINTREL according to the destination terminal MAC address in the service request, obtain terminal type and brand information, and at the same time obtain terminal interface information, and perform interface protocol adaptation; Step 5: According to the terminal type in Step 4, perform configuration and delivery operations. 9. The fully automatic configuration method for the access side of the core side of an intelligent switched telephone network as claimed in claim 8, wherein the data delivery operation in the step 5 is specifically: If it is an IAD device, select TELNET or STELNET protocol to connect the terminal device, and store all configuration instructions in the Kafka message queue; The Kafka message queue defines two object roles, Producer and Customer. The Producer completes the configuration command entry operation; the Customer judges whether the IAD device is registered or online, and if so, selects the port to issue the configuration command; if not, defines a temporary queue , cache the configuration instructions, and judge the connectivity status of the IAD device every set time, if it is connected, the configuration instructions are taken out from the cache queue, and the configuration is automatically issued; If the IP phone device generates the corresponding configuration file according to the brand and model, put the configuration file in the directory specified by the configuration file server for configuration delivery.

Images