CN1092886C - Method for realizing intelligent network service management point to be unconcerned with concrete service - Google Patents

Abstract

The invention discloses a method for realizing that the service management point of an intelligent network has nothing to do with specific services, including: designing a set of general operation interfaces, including service management operations and user service management operations; In the database, the business-independent data required by the system and the user interface are also placed in the database; through the operation of such general operation interfaces, the system can fill in the required data according to the description data of the specific business, including business logic and business data. The corresponding database described above, create a database related to the specific business, and perform corresponding business management and user business management operations. Because of this implementation method that has nothing to do with specific services, the launch of new services does not require changing the intelligent network service management point system, shortening the time from service design to putting into use, improving the scalability of the intelligent network system and introducing new services online.

Description

A method for realizing that intelligent network service management points are not related to specific services

The invention relates to a method for realizing an intelligent network service management point, in particular to a method for realizing an intelligent network service management point which has nothing to do with specific services.

As an additional "value-added" communication network that provides new services quickly and effectively on the original communication network, Intelligent Network (IN) has become more and more important in our country and has achieved great development. Among them, the service management point (SMP) is the service management node of the intelligent network, and completes functions such as service management, user management, and network management. The design of the traditional intelligent network service management point (SMP) is related to the service, that is, the SMP is limited to a specific service. When the service is modified or a new service is added, the SMP must be changed accordingly to adapt to the new service. management requirements. Referring to FIG. 1 and FIG. 2 , they are respectively a structural schematic diagram and a working flow chart of a traditional SMP. As shown in Figure 1, we can see that when the traditional SMP is put into operation, specific business components are integrated in the system, such as charge card calling service (ACC), toll-free or pay-to-party service (FPH), general personal Communication service (UPT), virtual private network service (VPN), telephone voting service (VOT), wide area centralized user exchange service (WAC), mass call service (MAS), etc. In this way, when accepting users, the system will be limited to existing services. As shown in Figure 2, when a general SMP accepts a user's request, it first selects the service requested by the user, and then enters the processing flow of the corresponding service. However, each service has its own processing flow, and the system cannot support newly created services. That is, the traditional SMP integrates the managed services inside the system, and the system's functions are limited to the existing services. If it is necessary to add new services or change the existing services, major changes must be made to the system software.

In today's world, which is changing rapidly, business opportunities are fleeting. How to put the newly opened business into the market as soon as possible and actually run it has become an important requirement for intelligent network operators and service providers. In order to meet the needs of network operators and service providers, intelligent network developers should shorten the development cycle of intelligent network products as much as possible.

The purpose of the present invention is to propose a method for implementing intelligent network service management points that has nothing to do with specific services, so that the introduction of new services does not require changing the intelligent network service management point system, shortening the time from service design to putting into use, and improving the intelligent network system. Scalability and online introduction of new services.

The object of the present invention is achieved by the following method: a method for realizing that the service management point of the intelligent network has nothing to do with specific services, the method comprising: taking basic operations irrelevant to specific services in service management operations and user service management operations as a A set of general operation interface; put the data irrelevant to the business into the pre-designed database, and the data irrelevant to the business required by the system and user interface are also placed in the database; through the operation of the general operation interface, the system can The description data of a specific business, including business logic and business data, is used to fill in the corresponding database, create a database related to the specific business, and perform corresponding business management and user business management operations.

According to the above method steps, the operation structure of the general operation interface has a fixed part and a variable part, and the fixed part includes: operation number, operation type, source functional entity, destination functional entity, source serial number, destination serial number, operator Number, the variable part is the data related to the operation, it can be empty.

According to the above method steps, the business management operations include business acquisition, loading, activation, deactivation, closure, and deletion; for each business, the description data of the business is first obtained, then loaded to the corresponding node, and finally activated The business; when a business loses its use meaning, first perform the deactivation operation, then close the business, and finally delete the business.

According to the above method steps, the user service management operations include user service application, creation, loading, activation, deactivation, uninstallation, decreation, and termination; Business-related databases, and then create, load, and activate user services in sequence; when users need to cancel the services they use, they will go through deactivation, uninstallation, creation, and termination of user services.

According to the above method steps, the database includes: a user business database index library, a database structure library, a user business arrangement structure library, a user business reference table, a basic user database, a basic user business table, a business operation library, and a business version library.

Due to the above-mentioned technical solution design irrelevant to specific services, that is, with the help of database and general operation interface design, the service management point (SMP) of the intelligent network can be independent from specific services.

Because of this irrelevance, when the SMP system is delivered for use, it may not include any specific services, and the specific services can be established after the system is running. Realize that after the system is put into use, services can be added, deleted, and modified without changing the system software.

Because of this irrelevance, the introduction of new services does not need to change the SMP system, and other devices in the intelligent network such as service control point (SCP) and service switching point (SSP) are originally independent of specific services, so as long as the service generation environment ( SCE) can quickly put the business into operation after defining and generating the business. It shortens the cycle of a new business from design, generation to putting into use from the usual one and a half years to six months or even three months.

In addition, by using the database and the general operation interface, the system can act as a database management server, which can provide end users (End Users) with the function of maintaining their own data, and also provides convenience for the customization of business users. End users can use general operations The interface is very convenient to access the database of SMP. And because the system provides a unified operation interface and interface, it is convenient for system users to operate and use the system.

Furthermore, because the system is designed to make business components and applications independent, adding new services does not affect the existing system, which enhances the scalability of the system and introduces new services without interrupting the operation of the system. Introduce new business online.

The present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

FIG. 1 is a schematic structural diagram of an existing SMP.

Fig. 2 is a schematic diagram of the workflow of the existing SMP.

Fig. 3 is a structural schematic diagram of the present invention.

FIG. 4 is a schematic diagram of a workflow of an embodiment of the present invention.

Fig. 5 is a schematic diagram of business component allocation.

FIG. 6 is a schematic diagram of an operation flow of a general operation interface according to an embodiment of the present invention.

First, please refer to FIG. 3 , which is a schematic structural diagram of the present invention. In the service management point (SMS) of the present invention, a set of general operation interface is designed, including service management operation and user service management operation, and data irrelevant to the service is put into a pre-designed database, and the system and user interface The required data that has nothing to do with the business is also placed in the database. Through the operation of the general operation interface, the system can fill in the corresponding database according to the description data of the specific business, including business logic and business data, and create a database related to the specific business. database, and perform corresponding business management and user business management operations. Various management functions of SMS are completed through the general operation interface and database interface (DBMS) interface. The system is not limited to one or several businesses. The system can realize the management of existing businesses and support the management of new businesses. The management process is the same. See Figure 4 for the business management process of the present invention and Schematic diagram of the user business management process. For each service, first obtain the service components from the service generation environment (SCE) of the intelligent network, including service logic and service data, then load the service components to the corresponding network unit, and finally activate the operation of the service, and the service can be completed Put into use. When the service loses its meaning of use, first suspend the operation of the service, then close the service, and finally delete the service. In this way, it is realized to dynamically introduce new services or remove old services online. When the telecommunications business administration needs to add new services, there is no need to make changes to the SMS system, as long as the business logic and business data of the corresponding business are provided.

In the present invention, the basic general operation interface includes service management operations and user service management operations. Service management operations include service acquisition, loading, activation, deactivation, closure, and deletion; user service management operations include user service application, creation, loading, activation, deactivation, uninstallation, creation, and termination. The database includes: user business database index library, database structure library, user business arrangement structure library, user business reference table, user basic database, user business basic table, business operation library, and business version library.

The management process of the user service shown in Figure 4 is firstly the application of the user service. According to the user's request, the service applied by the user is selected from the loaded services, and a user service number is assigned to it. Then enter the user business data. At this time, the database template of the corresponding business must be obtained from the database structure library to fill in the user data. After the user service data is successfully entered, the user service is created, loaded, and activated in sequence, and the user service is ready to use. When a user needs to cancel the service he uses, he needs to go through steps such as suspension, uninstallation, de-creation, data deletion, and termination of the user service.

Figure 5 shows a schematic diagram of service component allocation. SCE provides all components of a business: business execution logic, business management logic, business data templates, business trigger information, and business resource information. After the SMP executes the business acquisition operation, it will obtain these business components, in which the business management logic is reserved by the SMP for its own use, and the business data template must be loaded to the business data point (SDP) in addition to being reserved for its own use, and the business execution logic must be Loaded to the SCP, service trigger information is loaded to the SSP, and service resource information is loaded to the intelligent peripheral (IP).

The operation structure of the above-mentioned basic general operation interface has a fixed part and a variable part. The fixed part includes: operation number, operation type, source functional entity, destination functional entity, source serial number, destination serial number, operator number, variable part Can be empty for the data associated with the operation.

The following is an implementation example of the general operation interface design and database design of Huawei's intelligent network service management point (TELLIN® SMP) based on the above-mentioned technical solution design that has nothing to do with specific services.

The fixed part of the operation structure of the general operation interface is shown in Table 1:

Table 1 Operation parameter name Description of operating parameters Parameter Type parameter bytes msgID operation ID integer 4 msgType operation type integer 4 sourceFE source functional entity integer 4 destFE purpose functional entity integer 4 sourceFSM From the serial number of the engine integer 4 destFSM Destination automaton serial number integer 4 logname operator group name character type 16 There are three types of operations: issued command (Argument), returned result (Result), and returned error (Error). The operation ID in Table 1 identifies each operation, and the specific operation assignment is shown in Table 2:

Table 2 serial number operation name ID direction describe module 1 ServiceGet 1001 SMAP→SMP business acquisition business management 2 SerConfig 1005 SMAP→SMP business loading 3 SerActive 1006 SMAP→SMP business activation 4 SerDeactive 1008 SMAP→SMP business deactivation 5 SerClose 1009 SMAP→SMP business closed 6 SerDelete 1010 SMAP→SMP Business deletion 7 ApplySubServ 3000 SMAP→SMP User business application User business management 8 CreateSubServ 3001 SMAP→SMP User service creation 9 AddSubServ 3003 SMAP→SMP User service loading 10 ActivateSubServ 3005 SMAP→SMP User service activation 11 DeactivateSubServ 3007 SMAP→SMP User service deactivation 12 DeleteSubServ 3009 SMAP→SMP User service offloading 13 ClearSubServ 3029 SMAP→SMP User business clearance 14 TerminateSubServ 3030 SMAP→SMP User service termination 15 QuerySubServ 3040 SMAP→SMP User business inquiry 16 ModifySubServ 3028 SMAP→SMP User business modification

The source functional entity and the destination functional entity represent the sender and receiver of the operation respectively. The number definitions of functional entities are shown in Table 3:

table 3 entity name number range illustrate SMPs: 10 business management point SCP: 100~199 business control point SCE: 300 business generation environment SDPs: 500~599 business data point SAUs: 700~799 signaling access unit SMAP: 1000~1999 Service Management Access Point SSPs: 2000~2999 business exchange point IP: 3000~3999 smart peripherals VMServer: 4000~4999 voicemail server

Numbers less than 10 are reserved for SMP internal modules. The automaton serial number is used to distinguish each instance of the operation.

The variable part of the operation is data related to the operation. Business management operations include service acquisition, loading, activation, replacement, deactivation, shutdown, and deletion. User service management operations include user service application, creation, loading, activation, and deactivation. Activate, uninstall, create, terminate, query, modify, etc. Please see Table 4-Table 20: 1. Business management operations:

Table 4 Business Acquisition parameter name Parameter Description Parameter Type parameter bytes manageFile Business Management Logic File char MAX_FILE_LEN dataFile Business data template file char MAX_FILE_LEN logicFile business logic file char MAX_FILE_LEN MAX_FILE_LEN is the maximum allowed file name length defined by the system.

Table 5 Service loading parameter name Parameter Description Parameter Type parameter bytes serviceKey business key int 4 dbVersion database version number int 4 logicVersion Business logic version number int 4 scpno SCP number int 4

Table 6 Service activation parameter name Parameter Description Parameter Type parameter bytes serviceKey business key int 4 scpno SCP number int 4

Table 7 Service Replacement parameter name Parameter Description Parameter Type parameter bytes serviceKey business key int 4 dbVersion database version number int 4 logicVersion Business logic version number int 4 scpno SCP number int 4

Table 8 Service deactivation parameter name Parameter Description Parameter Type parameter bytes serviceKey business key int 4 scpno SCP number int 4

Table 9 Business closure parameter name Parameter Description Parameter Type parameter bytes serviceKey business key int 4 scpno SCP number int 4

Table 10 Business deletion parameter name Parameter Description Parameter Type parameter bytes serviceKey business key int 4 dbVersion database version number int 4 logicVersion Business logic version number int 4 2. User business management operations:

Table 11 User service application parameter name Parameter Description Parameter Type parameter bytes idSubscriber User ID UInt 4 ServiceKey business key UInt 4 DBVersion database version number UInt 4 flagPublicUserID user group logo UInt 4 currPublicUserID current user group number UInt 4

Table 12 User service creation parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4 dtAdd loading time char 15 idGroup user group number int 4 userIdentify User ID char 28

Table 13 User service loading parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4

Table 14 User service activation parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4

Table 15 Deactivation of user services parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4

Table 16 User service offloading parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4

Table 17 User business to create parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4

Table 18 User service termination parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4

Table 19 User business query parameter name Parameter Description Parameter Type parameter bytes SubServ User business number UINT4 4 SQLNum SQL number TINTEGER 4 idSCP SCP number INT4 4 QLCounter Query Items TINTEGER 4 tmtArr query term definition SQLStmt_def [32] Among them, the SQLStmt_def structure definition: parameter name Parameter Description Parameter Type parameter bytes type query type int 4 table Table Name char 18 fields field list char 2048 where Query conditions char 2048

Table 20 User Service Modification parameter name Parameter Description Parameter Type parameter bytes idSubServ User business number UInt 4 idSCP SCP number UInt 4 nrofSQL Number of SQL entries INT 4 sqlcontent Array of SQL statements char ^* [64]

The above general operations are issued by the service access point (SMAP) and processed by the SMP. During the process of processing, SMP sends an operation to SCP if necessary, continues to process after receiving the response from SCP, and finally returns the result to SMAP. The operation flow is shown in Figure 6. ①SMAP sends an operation 1 to SMP; ②SMP sends a new operation 2 to SCP during the processing of the operation: ③SCP sends a response to SMP after processing operation 2; ④SMP finishes processing After operation 1, send a response to SMAP.

Table 21-Table 28 introduce the database design of Huawei Intelligent Network Service Management Point (TELLIN® SMP), where type N represents numeric type, and C represents character type.

Table 21 User business database index library Database name User business database index library ss_index Functional description Index the user database of a business keywords dbname field description field name type length Valid Values/Constraints describe business key ServiceKey N 4 database version dbversion N 4 Database name dbName C 30 database status dbState C 1 1: Created, 2: To be created Description of the library dbMemo C 30 parent library name fathername N 4 library type dbtype N 4 public sign ispublic C 2

Table 22 Database structure library Database name Database structure library dbstructure Functional description Describe the structure of the database keywords dataItemId field description field name type length Valid Values/Constraints describe data item ID dataItemId N 4 Database name dbName C 18 field name fieldName C 18 field description fieldMemo C 32 Field Type fieldType C 1 field length fieldLen N 4 default length defaultLen N 4 Effective reception length effectLen N 4 keyword flag keyFlag C 1 T: keyword query field queryFlag C 1 T: Queryable

Table 23 User business arrangement database Database name User business arrangement database service_arrange Functional description Connect business and users keywords SubServiceID field description field name type length Valid Values/Constraints describe User business ID SubServiceID N 4 User ID userid N 4 business key service key N 4 database version dbversion N 4 User business database version status useState C 1 1: not created, 3: not submitted, 4: loaded (valid), 5: activated Enabled date startDate DT 14 end date endDate DT 14 user group number publicuserid N 4 assigned to SCP scpno N 4

Table 24 User business reference table Database name User business reference table ss_refer Functional description Connect user services on SMP with user service data on SCP keywords subserviceid field description field name type length Valid Values/Constraints describe User business ID SubServiceID N 4 User ID UserIdentifier C 28 business key ServiceKey N 4 user group number PublicUserID N 4

Table 25 User basic database Name database User Basic Database Functional description Record user data not related to business keywords User ID number field description field name type length Valid Values/Constraints describe user name username C 20 User nature userproperty C 20 ID number residentid C 15 company name unitname C 20 contact number telephone N 10 contact person linkman C 10 Payment methods payfeemethod C 10 User ID number userid N 10

Each business must have a basic table, and there must be at least three fields in the basic table, and other fields in the table can be set as required.

Table 26 Basic table of user services Name database Basic business table Functional description Record the basic information of users who apply for the service keywords User ID field description field name type length Valid Values/Constraints describe User ID user identifier C 28 user group number publicuserid N 4 User business status substate C 1 1: active, 0: inactive

Table 27 Business runtime library Database name Business runtime Functional description Describes the state of the business loaded into the SCP keywords serviceId field description field name type length Valid Values/Constraints describe business number serviceId N 4 SCP number SCPNo N 4 start date startDate C 8 end date endDate C 8 Registered users numOfUser N 4 positive users numOfUsing N 4 business status serviceState C 1 1: to be loaded, 2: loaded, 3: running

Table 28 Business version library Database name Business version library Functional description Businesses recorded in SMP keywords serviceId field description field name type length Valid Values/Constraints describe business number serviceId N 4 business name serviceName C 32 business key serviceKey N 4 DB version number dbVersion N 4 logical version number logicVersion N 4 manage files manageFile C 32 data file dataFile C 32 logical file logicFile C 32

The implementation process of the above general operations is described as follows:

1. Service acquisition - obtain a new service (or new version of service) from SCEP, fill in the corresponding database in SMP according to the information provided by SCEP, and create a library with the same structure as the library to be created in SDF. After processing, Echoes processing results, including success/failure flags. Processing flow:

a) Fill in the business version library.

b) Fill in the user business database index library and database structure library.

c) Create a user business database in the SMP according to the "business user database index library" and "database structure library".

d) Issue the corresponding Result (successful response) or Error (error response) operation.

2. Service loading——to load the service, first check the validity of the data, and then configure the service to each network unit. Processing flow:

a) Check the validity of the data (business), if it passes the check, add this business to the business operation library, set the business status to be loaded, otherwise send an error response to SMAP.

b) Send the configuration SCP operation to the SCP, and wait for the response of the SCP. Resend if there is no response within the given time. If there is still no response after resending twice, an error will be returned to SMAP. If an error response from the SCP is received, the processing is terminated and an error response is returned to the SMAP.

c) After normal processing, set the service status as loaded, and send a success response to SMAP.

3. Service activation - only when the service status is loaded, the service can be activated. Processing flow:

a) Check the business and business status (in the business operation library).

b) Send an activation operation to the SCP, wait for a response, and resend if there is no response.

c) If a successful response from the SCP is received, set the service status in the service operation library to active, and send a successful response to the SMAP. If it receives an error response from the SCP or does not receive a response from the SCP within a limited time, it returns an error response to the SMAP.

4. Service deactivation - only when the service status is activated, the service can be "deactivated". Processing flow:

a) Check whether the business and business status (in the business operation library) are active, if not, return an error response to SMAP.

b) Send a deactivation operation to the SCP, wait for a response, and resend if there is no response.

c) If a successful response from the SCP is received, the service status in the service runtime library is set as loaded, and a successful response is sent to the SMAP. If it receives an error response from the SCP or does not receive a response from the SCP within a limited time, it returns an error response to the SMAP.

5. Business closure - the business can only be closed after the business is deactivated. Processing flow:

a) Check the business status, if it is not loaded, send an error response to SMAP.

b) Sending an operation of deleting user services to the user service management module.

c) After receiving a successful response from the user service management module, send a service close operation to the SCP.

d) If an error response from the SCP is received or a timeout occurs, an error response is returned to the SMAP.

e) After receiving a successful response from the SCP, delete the corresponding record of the closed service in the SMP service operation library.

Return a successful response to SMAP.

6. Business deletion - the business can only be deleted after the business is closed. Deleting a service refers to deleting records and libraries related to this service on the SMP. Processing flow:

a) Check whether there is this service in the service version library, if not, return an error response to SMAP.

b) Check whether the service operation library has this service and the status of the service. If the service status is not closed, return an error response to SMAP.

c) Query the user business database index library, delete the data related to this business, and then delete the corresponding records in the database structure library, user business database index library, and business version library. If it succeeds, it will send a successful response to SMAP, and if it fails, it will return an error response to SMAP.

7. User service application - apply for a user service number for a user. Processing flow:

a) Receive the operation ApplySubServ/Argu sent by SMAP to obtain the user number, service key, database version number, public user logo, and public user number.

b) Determine whether the specified user and service exist, and return the error operation ApplySubServ/E if they do not exist.

c) Find out the current maximum user service number, add 1 and use it as the user service number applied for by the user.

d) Set the public user number.

e) Set the user business data version status to "not created".

f) Inserting the user service number and the public user number into the user service arrangement structure database.

g) Return the user service number to the MMI (Man-Machine-Interface) as a parameter of the ApplySubServ/R operation.

8. User service creation—creating the service applied for by a user. Processing flow:

a) Receive the CreateSubServ/A operation sent by the MMI to obtain the user service number, SCP number, public user number, and user ID.

b) If the user service does not exist or the user service data version status is not "not created", return to the operation CreateSubServ/E.

c) Check whether the user service has valid data, and if there is no data, return to CreateSubServ/E.

d) Find out the service key and database version number according to the user service number.

e) Insert the business key, database version number, user business number, and user ID into the user business reference table.

f) Set the user business data version status as "unsubmitted".

g) return successful operation CreateSubServ/R.

9. User service loading—load user service to SCP. Processing flow:

a) Receive the operation AddSubServ/A sent by the MMI to obtain the user service number.

b) If the user service does not exist or the user service data version status is not "unsubmitted", return to the operation AddSubServ/E.

c) Query whether this user service already exists on the SCP, if it already exists, go to step f.

d) Set the user service status as "inactive", take out the user service data from the SMP, use it as a parameter for operating SCPMultiChange/A, and send the operation SCPMultiChange/A to the SCP corresponding to the user service.

e) If the error response SCPMultiChange/E from the SCP is received or the operation times out, return to the operation AddSubServ/E.

f) Set the user business data version status to "Valid".

g) return successful operation AddSubServ/R.

10. User service activation - activate a service that a user has applied for but not yet put into use. Processing flow:

a) If the data version status is not "valid", return the error operation ActivateSubServ/E.

b) Query the user service on the SCP, and send the operation SCPSelect/A to the SCP.

c) If the user service does not exist on the SCP, set the data version status as "not submitted", and then return the error operation ActivateSubServ/E.

d) If the user service on the SCP is already activated, go to step g.

e) Set the service status of the user on the SCP to "Active", and send the operation SCPChange/A.

f) If the error response SCPChange/E from the SCP is received or the operation times out, return to the operation ActivateSubServ/E.

g) Set the user service status on the SMP as "activated", and the data version status as "activated".

h) Return successful operation ActivateSubServ/R.

11. Deactivation of user services - suspend the running user services. Processing flow:

a) If the data version status is not "activated", return the error operation DeactivateSubServ/E.

b) Query the user service on the SCP, and send the operation SCPSelect/A to the SCP.

c) If the user service does not exist on the SCP, set the data version status as "not submitted", and then return the error operation DeactivateSubServ/E.

d) If the user service on the SCP has been deactivated, go to step g.

e) Set the service status of the user on the SCP to "deactivated", and send the operation SCPChange/A.

f) If the error response SCPChange/E from the SCP is received or the operation times out, the operation DeactivateSubServ/E is returned.

g) Set the user service status on the SMP to "deactivated", and the data version status to "valid".

h) Return successful operation DeactivateSubServ/R.

12. User service unloading - delete the user service on the SCP. Processing flow:

a) If the data version status is not "valid", return the error operation DeleteSubServ/E.

b) Query the user service on the SCP, and send the operation SCPSelect/A to the SCP.

c) If the error response SCPChange/E from the SCP is received or the operation times out, the operation DeleteSubServ/E is returned.

d) If the user service does not exist on the SCP, go to step h.

e) If the user service status on the SCP is "activated", then set the user service status and data version status on the SMP to "activate", and then return to the operation DeleteSubServ/E.

f) Assemble the SQL statement for deleting the user service according to the user service number, and send the operation SCPMultiChange/A to the SCP.

g) If the error response SCPChange/E from the SCP is received or the operation times out, the operation DeleteSubServ/E is returned.

h) Set the data version status to "unsubmitted".

i) Return successful operation DeleteSubServ/R.

13. De-creation of user services - change the status of user services on the SMP to uncreated. Processing flow:

a) If the data version status is not "uncommitted", return the error operation ClearSubServ/E.

b) Query whether there is user service data on the SCP.

c) If there is still user service data on the SCP, then set the data version status on the SMP to "valid", and return the error operation ClearSubServ/E.

d) Set the data version status to "not created".

e) Return a successful response to ClearSubServ/R.

14. User service termination - terminate user service and clear all data related to this user service. Processing flow:

a) If the data version status is not uncreated, return the error operation TerminateSubServ/E.

b) Delete the data in the user service data table, delete the data related to the user service in the user service reference table and the user service arrangement table, and return the error operation TerminateSubServ/E if the deletion is wrong.

c) Return a successful response to TerminateSubServ/R.

15. Deleting all user services of a service—corresponding to when the service is closed and the service is deleted, the corresponding user services are processed. Processing flow:

a) If it is an operation issued when the business is deleted, go to step e.

b) Query the number of user business records of the business, if the number of records is 0, return a successful response. If an error occurs, an error response is returned.

c) Set all user services of the service to the "inactive" state, and set the data version state to the "unsubmitted" state.

d) If an error occurs, an error response is returned, otherwise a success response is returned.

e) Delete the data of all user services related to this service in the user service reference table, and delete the data of all user services related to this service in the user service arrangement table.

f) If an error occurs, an error response is returned, otherwise a success response is returned.

16. User service query - query the user service data on the SCP to the SMP. Processing flow:

a) According to the query table name, field name, and conditions given by MMI, combine SQL statements, and send query operation SCPSelect/A to SCP.

b) If the query fails or times out, return the error operation QuerySubServ/E.

c) Insert or update the queried data into the user service database of the SMP.

d) Return a successful response to QuerySubServ/R.

17. User business modification——The modification of user business can only be carried out in the "valid" state of the data version, and the modification is only for the modified data item. Modify the user service data on the SCP first, and then modify the user service data on the SMP after success. Processing flow:

a) If the data version status is not "valid", return ModifySubServ/E.

b) Send the SQL to modify the database to the SCP by operating SCPMultiChange/A.

c) If the error response SCPMultiChange/E from the SCP is received or the operation times out, the operation ModifySubServ/E is returned.

d) After receiving a successful response from the SCP, modify the user service data of the SMP.

e) If the modification fails, return the error operation ModifySubServ/E.

f) Return successful operation ModifySubServ/R.

Claims (5)

1. A method for realizing that an intelligent network service management point has nothing to do with specific services, which is characterized in that the method includes: using basic operations that have nothing to do with specific services in service management operations and user service management operations as a set of general operation interfaces; The data irrelevant to the business is placed in the pre-designed database, and the data irrelevant to the business required by the system and the user interface is also placed in the database; through the operation of the general operation interface, the system can describe the data according to the specific business, including Business logic and business data are used to fill in the corresponding database, create a database related to the specific business, and perform corresponding business management and user business management operations. 2. The method according to claim 1 for realizing that the intelligent network service management point has nothing to do with specific services, characterized in that: the operation structure of the general operation interface has a fixed part and a variable part, and the fixed part includes: operation number, Operation type, source functional entity, destination functional entity, source serial number, destination serial number, operator number, the variable part is the data related to the operation, which can be empty. 3. The method according to claim 1 or 2 for realizing that the intelligent network service management point has nothing to do with specific services, characterized in that: said service management operations include service acquisition, loading, activation, deactivation, shutdown, and deletion; For each service, first obtain the description data of the service, then load it to the corresponding node, and finally activate the service; when a service loses its meaning, first perform the deactivation operation, then close the service, and finally delete the service. 4. The method according to claim 1 or 2 for realizing that the intelligent network service management point has nothing to do with specific services, characterized in that: said user service management operations include user service application, creation, loading, activation, deactivation, Uninstall, create, and terminate; first, apply for the user service according to the user's requirements, then fill in the database related to the application service, and then create, load, and activate the user service in sequence: when the user needs to cancel the service it uses, Then go through the deactivation, uninstallation, creation, and termination of user services. 5. The method for realizing that intelligent network service management points have nothing to do with specific services according to claim 1, characterized in that said database includes: user service database index library, database structure library, user service arrangement structure library, user service reference table, user basic database, user business basic table, business operation library, and business version library.

Images