Business nesting rule configuration methods and devices, business triggering methods

By generating contract information through BOSS and sending it to the business nesting module via API, and combining network parameters to determine business nesting rules, the problem of high resource consumption in existing technologies is solved, and efficient configuration and triggering of business nesting rules are achieved.

CN114666780BActive Publication Date: 2026-11-17ZTE CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202011526573.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-22
Publication Date
2026-11-17
Estimated Expiration
2040-12-22

AI Technical Summary

Technical Problem

In existing technologies, when users add or remove value-added services, it is necessary to modify the subscription information and exchange signaling in the core network, which leads to high resource consumption and performance loss of the communication system.

Method used

Contract information is generated through the Business Operation Support System (BOSS) and sent directly to the business nesting module via the Application Programming Interface (API). The business nesting rules are determined in conjunction with network parameters, thereby reducing information interaction in the core network.

Benefits of technology

It effectively reduces resource consumption and performance loss in communication systems, and improves the efficiency of configuring nested business rules.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114666780B_ABST
    Figure CN114666780B_ABST
Patent Text Reader

Abstract

This invention discloses a service nesting rule configuration method and apparatus, and a service triggering method. The service nesting rule configuration method includes: obtaining subscription information, which is generated by a BOSS and sent to a service nesting module via API according to preset pointer information; completing a service subscription based on the subscription information and updating the subscription information table; obtaining network parameters, and determining service nesting rules based on the network parameters and the subscription information table, where the network parameters characterize the network attributes of the service. According to the solution provided by this invention, resource consumption during service triggering and performance loss in the communication system can be effectively reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to, but is not limited to, the field of communication technology, and particularly to a service nesting rule configuration method and apparatus, and a service triggering method. Background Technology

[0002] With the continuous innovation of value-added services in intelligent networks, users are offered a variety of intelligent network service functions to choose from. To meet the demand of users simultaneously enjoying multiple value-added services, service subscriptions are required for each user's chosen service. A service nesting module then nests and combines each value-added service to derive the service nesting rules used to trigger the service. The generation and updating of service nesting rules are typically triggered by service subscriptions. The Business Operation Support System (BOSS) sends the subscription information to the core network, completes the service subscription in the core network, and sends signaling to the service nesting module, enabling the module to parse the signaling and determine the service nesting rules. However, using the existing method, every time a user adds or removes a value-added service, the subscription information needs to be modified in the core network, and the service nesting rules need to be re-determined through signaling interaction. This increases resource consumption and causes a loss of communication system performance. Summary of the Invention

[0003] The following is an overview of the subject matter described in detail herein. This overview is not intended to limit the scope of the claims.

[0004] This invention provides a method and apparatus for configuring nested business rules, as well as a business triggering method, which can reduce resource consumption.

[0005] In a first aspect, embodiments of the present invention provide a method for configuring business nesting rules, applied to a business nesting module, the method comprising: Obtain contract information, which is generated by BOSS and sent to the business nesting module via API according to preset pointing information; Complete the business contract signing based on the aforementioned contract information and update the contract information table; Obtain network parameters, and determine service nesting rules based on the network parameters and the contract information table. The network parameters are used to characterize the network attributes of the service.

[0006] Secondly, embodiments of the present invention provide a business nesting rule configuration method, applied to BOSS, the business nesting rule configuration method including: Generate contract information; Obtain preset pointing information, and send the subscription information to the service nesting module via API according to the pointing information, so that the service nesting module completes the service subscription and determines the subscription information table according to the subscription information, thereby enabling the service nesting module to determine the service nesting rules according to the network parameters and the subscription information table, and the service nesting rules are used to characterize the network attributes of the service.

[0007] Thirdly, embodiments of the present invention provide a service triggering method applied to a service nesting module, wherein the service nesting module is communicatively connected to the core network, and the service triggering method includes: When a service interaction instruction sent by the core network is received, the service nesting rule is obtained. The service nesting rule is configured by the service nesting rule configuration method described in the first aspect above. The business to be triggered is determined according to the aforementioned business nesting rules; Send a service triggering instruction to the service network element corresponding to the service to be triggered.

[0008] Fourthly, embodiments of the present invention provide a service triggering method applied to a core network, wherein the core network is communicatively connected to a service nesting module, and the service triggering method includes: Upon receiving a call request, generate a business interaction instruction based on the call request; The business interaction instruction is sent to the business nesting module so that the business nesting module can obtain the business nesting rules and trigger the business according to the business nesting rules. The business nesting rules are configured by the business nesting rule configuration method described in the first aspect above.

[0009] Fifthly, embodiments of the present invention also provide an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements the business nesting rule configuration method as described in the first aspect above, or implements the business triggering method as described in the third aspect.

[0010] In a sixth aspect, embodiments of the present invention also provide a computer-readable storage medium storing computer-executable instructions, the computer-executable instructions being used to execute the business nesting rule configuration method as described in the first aspect above, or to execute the business nesting rule configuration method as described in the second aspect above, or to execute the business triggering method as described in the third aspect above, or to execute the business triggering method as described in the fourth aspect above.

[0011] This invention includes a service nesting rule configuration method and apparatus, and a service triggering method. The service nesting rule configuration method includes: obtaining subscription information, which is generated by a BOSS and sent to the service nesting module via API according to preset pointing information; completing a service subscription based on the subscription information and updating a subscription information table; obtaining network parameters, and determining service nesting rules based on the network parameters and the subscription information table, wherein the network parameters characterize the network attributes of the service. According to the solution provided by this invention, resource consumption during service triggering and performance loss in the communication system can be effectively reduced.

[0012] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the description, claims, and drawings. Attached Figure Description

[0013] The accompanying drawings are provided to further understand the technical solutions of the present invention and constitute a part of the specification. They are used together with the embodiments of the present invention to explain the technical solutions of the present invention, and do not constitute a limitation on the technical solutions of the present invention.

[0014] Figure 1 This is a schematic diagram of the process structure for completing a business contract according to an embodiment of the present invention; Figure 2 This is a flowchart of a business nesting rule configuration method applied to a business nesting module, provided by another embodiment of the present invention; Figure 3 This is a flowchart of updating the contract information table provided in another embodiment of the present invention; Figure 4 This is a flowchart for determining contract type information provided in another embodiment of the present invention; Figure 5 This is a flowchart of obtaining network parameters provided in another embodiment of the present invention; Figure 6 This is a flowchart of a business nesting rule configuration method applied to BOSS provided in another embodiment of the present invention; Figure 7 This is a flowchart of BOSS generating contract information provided in another embodiment of the present invention; Figure 8 This is a flowchart of a business triggering method applied to a business nesting module provided in another embodiment of the present invention; Figure 9 This is a flowchart of another embodiment of the present invention, showing how to send a service triggering instruction to the service network element corresponding to the service to be triggered; Figure 10 This is a flowchart of another embodiment of the present invention, showing how to send a service triggering instruction to the service network element corresponding to the service to be triggered; Figure 11 This is a flowchart of another embodiment of the present invention, showing how to send a service triggering instruction to the service network element corresponding to the service to be triggered; Figure 12 This is a flowchart of a business nesting trigger provided in another embodiment; Figure 13 This is a flowchart of a service triggering method applied to the core network provided in another embodiment; Figure 14 This is a flowchart of a business nesting rule configuration method provided in another embodiment of the present invention; Figure 15 This is a flowchart of a service triggering method provided in another embodiment of the present invention; Figure 16 This is an example diagram of a service triggering method provided in another embodiment of the present invention; Figure 17 This is an example diagram of CS service signaling interaction provided in another embodiment of the present invention; Figure 18 This is an example diagram of IMS service signaling interaction provided in another embodiment of the present invention; Figure 19 This is a schematic diagram of the structure of an electronic device provided in another embodiment of the present invention. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0016] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, or the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0017] This invention provides a service nesting rule configuration method and apparatus, and a service triggering method. The service nesting rule configuration method includes: acquiring subscription information, which is generated by a business operation support system (BOSS) and sent to a service nesting module via an application programming interface (API) according to preset pointer information; completing a service subscription based on the subscription information and updating the subscription information table; acquiring network parameters, and determining service nesting rules based on the network parameters and the subscription information table, where the network parameters characterize the network attributes of the service. The service triggering method includes: upon receiving a service interaction instruction from the core network, acquiring the service nesting rules, determining the service to be triggered based on the service nesting rules, and sending a service triggering instruction to the service network element corresponding to the service to be triggered. According to the solution provided by this embodiment, resource consumption during service triggering and performance loss in the communication system can be effectively reduced.

[0018] The embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0019] Reference Figure 1 , Figure 1 This is a schematic diagram of a system architecture for completing a service contract according to an embodiment of the present invention, including a BOSS, a core network, and a service nesting module. This structure is used for: After receiving the customer's "Subscribed Service A" for the first time, BOSS generates subscription information and sends it to the Home Location Register (HLR) and Home Subscriber Server (HSS) in the core network.

[0020] It should be noted that the BOSS can send subscription information to the HLR and HSS in the core network through the Cloud Service Bus (CSB), but this embodiment does not impose any limitations.

[0021] The core network determines the available service nesting modules based on the contract information and generates pointing information to send to the BOSS. The pointing information is used to point the service contract to the available service nesting module, so that the BOSS can send the contract information to the service nesting module through the API, thereby enabling the service nesting module to complete the service contract and activate service A.

[0022] When BOSS receives a subscription request again, it generates new subscription information "Subscription Service B". BOSS does not need to send subscription modification information to HLR and HSS. Based on the pointing information, it sends "Subscription Service B" to the service nesting module via API, so that the service nesting module adds service B to the user. At this time, the user completes the subscription task AB, thereby reducing the information interaction between BOSS and the core network and reducing resource consumption.

[0023] It should be noted that BOSS is a business operation support system used for unified planning and integration of intelligent network business functions; the service nesting module can be a network element, such as an intelligent network element service control point (SCP), but this embodiment does not impose any restrictions; the core network includes HLR and HSS for storing subscription information, and BOSS communicates with the core network and the service nesting module respectively.

[0024] Based on the above structure, the method of this application will be described below.

[0025] Reference Figure 2 , Figure 2 This is a flowchart of a business nesting rule configuration method for a business nesting module provided in another embodiment of the present invention. The business nesting rule configuration method includes, but is not limited to, steps S200, S210 and S220.

[0026] Step S200: Obtain contract information. The contract information is generated by BOSS and sent to the business nested module via API according to the preset pointing information.

[0027] In one embodiment, the contract information can include any information related to intelligent network services, such as service package type information, user attribute information, and contracted service status information. This embodiment does not impose any limitations and can be adjusted according to actual needs.

[0028] Step S210: Complete the business contract signing based on the contract information and update the contract information table.

[0029] In one embodiment, after obtaining the contract information, the contract information table is updated according to the different information types contained in the contract information to determine the contract status as completed. The parameters of the contract information table can be obtained from a parameter database and configured according to the actual needs of completing the contract. If the obtained contract information contains information types that do not belong to the original contract information table, and it is determined that the information type is available, the parameters are obtained from the parameter database and the corresponding information type is configured. Alternatively, it can be a pre-set contract information table, updating the parameter information of the corresponding parameter attributes in the original contract information table according to the obtained contract information. It should be noted that the process of signing a contract based on the contract information is not an improvement made in this embodiment and will not be elaborated upon here.

[0030] Step S220: Obtain network parameters and determine the business nesting rules based on the network parameters and the contract information table. The network parameters are used to characterize the network attributes of the business.

[0031] In one embodiment, network parameters are generated when the BOSS first receives a subscription request, generates subscription information, and sends it to the core network. The core network generates and saves the network parameters when it first triggers the service based on the subscription information. The network parameters are used to characterize the network attributes of the service. The network parameters include initial subscription information, such as user phone number, location information, and service key. This embodiment does not impose many limitations.

[0032] In one embodiment, the service nesting rules determined based on network parameters and the subscription information table include the user's initial subscription information and subscription service attribute information related to intelligent network services. The service nesting rules provide service triggering support for the service nesting module, and the service nesting module can trigger the corresponding service for the received subscription information according to the service nesting rules.

[0033] Additionally, refer to Figure 3 In one embodiment, Figure 2 Step S210 in the illustrated embodiment also includes, but is not limited to, the following steps: Step S300: Obtain the contract information table, which includes several contract parameters. The contract parameters in the contract information table are pre-obtained and configured from a preset parameter database. Step S310: Update the contract information table based on the contract parameters and contract information.

[0034] In one embodiment, a contract information table is initially obtained, and several contract parameters in the contract information table are used to characterize service contract attributes. It should be noted that these contract parameters are pre-obtained and configured from a preset parameter database. This embodiment provides a contract information table that can obtain and configure contract parameters from a preset parameter database. Compared to some existing fixed contract information tables, which require modifying the table structure to maintain user contract information for new services, thus increasing R&D and maintenance costs, the user information table provided in this embodiment can dynamically expand parameters as needed based on actual conditions. This adapts to the continuous updates of intelligent network services and the addition of new service attributes, reducing corresponding R&D and maintenance costs.

[0035] In one embodiment, the acquired contract information is matched with the contract parameters in the user's contract information, and the contract information table is updated.

[0036] Additionally, refer to Figure 4 In one embodiment, Figure 2 Step S220 in the illustrated embodiment also includes, but is not limited to, the following steps: Step S400: Determine the contract type information for the business contract based on the contract parameters and contract information.

[0037] It should be noted that this embodiment also includes determining the contract type information of the service contract based on the contract parameters and contract information. The contract type information is used to define the type of contracted service. For example, if user A and user B have the same contract information, then user A and user B have the same contract type. Determining the contract type information allows for the batch acquisition of contract information from multiple users belonging to the same contract type, and enables the unified management of services of the same contract type. For example, it allows for the unified management of the service usage of users who have activated package A, specifically the services included in package A, such as data usage monitoring and call charge management. This embodiment does not impose further limitations.

[0038] Additionally, refer to Figure 5 In one embodiment, Figure 2 Step S220 in the illustrated embodiment also includes, but is not limited to, the following steps: Step S500: If the contract information table is determined for the first time, trigger the business corresponding to the contract information table; Step S510: Obtain and save the network parameters fed back by the triggered service.

[0039] In some embodiments, the network parameters are initial contract information. When the contract information table is determined for the first time, the service corresponding to the contract information table is triggered, and the generated network parameters are returned. It is understandable that, in order to facilitate subsequent use and reduce the number of times network parameters are obtained, the network parameters can be saved after being obtained by the service nesting module, so that the saved network parameters can be directly used to determine the service nesting rules later.

[0040] Reference Figure 6 , Figure 6 This is a flowchart of a business nesting rule configuration method applied to BOSS provided by another embodiment of the present invention. The business nesting rule configuration method includes, but is not limited to, steps S610 and S620.

[0041] Step S610: Generate contract information.

[0042] In one embodiment, the service network element sends a subscription instruction to the BOSS via standard signaling. The BOSS generates subscription information based on the subscription instruction. The content format of the subscription information has been described in step S200 and will not be repeated here.

[0043] Step S620: Obtain preset pointing information, and send the subscription information to the service nesting module via API according to the pointing information, so that the service nesting module completes the service subscription and determines the subscription information table according to the subscription information, thereby enabling the service nesting module to determine the service nesting rules according to the network parameters and the subscription information table. The service nesting rules are used to characterize the network attributes of the service.

[0044] It should be noted that the pointing information is generated by the core network after receiving the initial contract information generated and sent by the BOSS, and after determining the available service nesting modules. The core network then feeds this information back to the BOSS and saves it. This pointing information is used to direct the permissions for obtaining and updating the contract information table, as well as the permissions for completing the corresponding service contract and triggering the service, to the service nesting module. This ensures that when the BOSS receives a contract instruction again and generates contract information, it sends the contract information to the service nesting module, enabling the module to complete the service contract and trigger the corresponding service.

[0045] It should be noted that after obtaining this pointing information, BOSS can save it and, upon receiving another operation involving a business nesting module, directly interact with the business nesting module via API based on this pointing information. This reduces signaling parsing and helps reduce resource consumption.

[0046] Additionally, refer to Figure 7 In one embodiment, Figure 6 Step S610 in the illustrated embodiment also includes, but is not limited to, the following steps: Step S700: Obtain the subscription instruction sent by the service network element through standard signaling; Step S710: Generate contract information according to the contract signing instruction.

[0047] In one embodiment, the service nesting module obtains the subscription instruction sent to the service nesting module by the service network element through standard signaling. The standard signaling may be CAMEL Application Part (CAP), or INAP Gateway (Intelligent Network Application Protocol, INAP), or Session Initiation Protocol (SIP). This embodiment does not impose any limitations and can be adjusted according to actual needs.

[0048] In one embodiment, the subscription instruction is a subscription request sent by a service network element. The subscription instruction includes subscription request information related to the intelligent network service, such as "user requests to subscribe to service A". The BOSS generates the corresponding "activate service A" subscription information based on the subscription instruction.

[0049] In another embodiment, the BOSS is connected to the core network. The pointing information is generated by the core network after determining the available service nesting modules upon receiving the subscription information generated and sent by the BOSS for the first time. The core network then feeds it back to the BOSS and saves it.

[0050] It should be noted that the principle of generating pointer information can be found by referring to... Figure 6The description of the illustrated embodiments will not be repeated here for the sake of simplicity.

[0051] Reference Figure 8 , Figure 8 This is a flowchart of a service triggering method applied to a service nesting module provided by another embodiment of the present invention. The service triggering method includes, but is not limited to, steps S800, S810 and S820.

[0052] Step S800: Upon receiving a service interaction instruction from the core network, obtain the service nesting rules; Step S810: Determine the business to be triggered according to the business nesting rules; Step S820: Send a service triggering instruction to the service network element corresponding to the service to be triggered.

[0053] In some embodiments, the service interaction command is used to trigger the service corresponding to the received subscription information. When a service interaction command sent by the core network is received, the service nesting rule is obtained from the service nesting module, and the service to be triggered is determined according to the service nesting rule. A service triggering command is then sent to the service network element corresponding to the service to be triggered, so that the service network element triggers the corresponding service according to the service triggering command. This achieves service triggering through an internal API, reducing resource consumption compared to the method of triggering services through signaling interaction. It should be noted that the configuration method of the service nesting rule is referenced... Figure 2 The principles of the illustrated embodiments will not be elaborated here.

[0054] Additionally, refer to Figure 9 In one embodiment, Figure 8 In the illustrated embodiment, the number of services to be triggered in step S820 is N, where N is an integer greater than 1. Step S820 also includes, but is not limited to, the following steps: Step S900: Send a service triggering instruction to the service network element corresponding to the (N-1)th service to be triggered; Step S910: When the service network element corresponding to the (N-1)th service to be triggered is received, a service trigger instruction is sent to the service network element corresponding to the Nth service to be triggered according to the response result fed back by the service trigger instruction.

[0055] In one embodiment, when a service network element has multiple services to be triggered, the services to be triggered corresponding to the triggering instructions are triggered according to the order in which the triggering instructions are received. For example, there are N services to be triggered, where N is an integer greater than 1. When the (N-1)th service to be triggered provides a response result according to the corresponding service triggering instruction, it indicates that the (N-1)th service to be triggered has received the service triggering instruction and sends the service triggering instruction to the service network element corresponding to the Nth service to be triggered.

[0056] Additionally, refer to Figure 10In one embodiment, during execution Figure 8 Following step S820 in the illustrated embodiment, the following steps may also be included, but are not limited to: Step S1000: Once the response results for all services to be triggered are obtained, send the trigger response information to the core network. Step S1010: Obtain the service execution information fed back by the core network based on the response information; Step S1020: Trigger the pending business based on the business execution information.

[0057] In one embodiment, when the response results corresponding to all services to be triggered are obtained, the service nesting module sends trigger response information to the core network to indicate that all services to be triggered have received the service triggering instruction and are in a ready-to-trigger state. When the service execution information fed back by the core network based on the response information is obtained, the services to be triggered are triggered based on the service execution information.

[0058] Additionally, refer to Figure 11 In one embodiment, Figure 8 In the illustrated embodiment, step S820 includes both internal and external network elements as service network elements. Step S820 also includes, but is not limited to, the following steps: Step S1100: When the service network element is an internal network element, the service trigger command is sent to the internal network element via API.

[0059] Step S1110: When the service network element is an external network element, the service triggering instruction is sent to the external network element through standard signaling.

[0060] In one embodiment, the service network element includes internal network elements and external network elements. Internal network elements are network elements within the communication system comprised of the core network and the service nesting module, while external network elements are external devices of a third-party platform connected to the communication system. It should be noted that internal network elements are used to nest new services and obtain service information requested by external network elements; external network elements are used to request subscribed services. Since the external network element is a third-party platform, such as an operator, it needs to interact with the service nesting module through standard signaling interaction methods. In this embodiment, the internal network element interacts with the service nesting module through an API. Using an API reduces the signaling encoding and decoding processing required in standard signaling interaction methods, thereby improving interaction efficiency. The service nesting module supports both API and standard signaling interaction methods, enabling various applicable scenarios.

[0061] Additionally, refer to Figure 12 In one embodiment, after execution Figure 8 Following step S820 in the illustrated embodiment, the following steps may also be included, but are not limited to: Step S1200: Obtain the response result from the network element corresponding to the service to be triggered, based on the service triggering instruction. Step S1210: Based on the response result and business nesting rules, determine the associated triggering business related to the business to be triggered.

[0062] It should be noted that, in addition to contract information, the business nesting rules can also include additional criteria for triggering business nesting, depending on actual needs. For example, the next business to be triggered can be determined based on the triggering or response result of each business. It should also be noted that in this embodiment, multiple triggered businesses and... Figure 9 The multiple services triggered in the illustrated embodiments are not the same. Figure 9 The illustrated embodiment triggers N independent services based on a nested business rule, with no correlation between the services. However, the associated triggering of services in this embodiment, based on response results and the nested business rule, depends on the response results of the services triggered earlier. For example, the nested business rule includes services A, B, C, and D. It could be that after service A is triggered, service B is automatically triggered based on its successful trigger signal, and then services C and D are triggered based on their successful trigger signals. Alternatively, after service A is triggered, if service A's response result is successful, service D is triggered according to the nested business rule; if service A's response result is unsuccessful, service B is triggered according to the nested business rule. It should be noted that the above examples are merely illustrative of principles and do not limit the business triggering method of this embodiment. Those skilled in the art are motivated to adjust the nested rules for associated triggering services according to actual needs, and no further limitations are made here.

[0063] refer to Figure 13 , Figure 13 This is a flowchart of a service triggering method applied to a core network provided by another embodiment of the present invention. The service triggering method includes, but is not limited to, steps S1300 and S1310.

[0064] Step S1300: When a call request is received, a business interaction instruction is generated based on the call request.

[0065] Step S1310: Send the business interaction instruction to the business nesting module so that the business nesting module can obtain the business nesting rules and trigger the business according to the business nesting rules.

[0066] It should be noted that the principles of steps S1300 to S1310 above can be referred to Figure 9 The principles of the embodiments shown will not be elaborated here for the sake of simplicity.

[0067] Additionally, refer to Figure 14 , Figure 14This is a flowchart of a business nesting rule configuration method provided in another embodiment of the present invention. The business nesting rule configuration method includes the following steps: Step S1400: BOSS obtains the subscription instruction sent by the service network element through standard signaling, and generates subscription information according to the subscription instruction; Step S1410: BOSS obtains the pointing information generated by the core network after determining the available service nesting module upon receiving the first contract information generated and sent by BOSS, and sends the contract information to the service nesting module via API according to the pointing information. Step S1420: The business nesting module obtains the contract information; obtains the contract information table, which includes several contract parameters. The contract parameters in the contract information table are pre-obtained and configured from a preset parameter database; completes the business contract signing based on the contract parameters and contract information and updates the contract information table. Step S1430: The business nesting module determines the contract type information of the business contract based on the contract parameters and contract information; In step S1440, when the service nesting module first determines the contract information table, it triggers the service corresponding to the contract information table, obtains and saves the network parameters fed back by the triggered service, and the network parameters are used to characterize the network attributes of the service. In step S1450, the service nesting module determines the service nesting rules based on network parameters and the contract information table.

[0068] Additionally, refer to Figure 15 , Figure 15 This is a flowchart of a service triggering method provided in another embodiment of the present invention, which includes the following steps: In step S1500, the core network obtains the call request, generates a service interaction instruction based on the call request, and sends the service interaction instruction to the service nesting module. Step S1510: When the service nesting module receives the service interaction instruction sent by the core network, it obtains the service nesting rules and determines the service to be triggered according to the service nesting rules. Step S1520: The service nesting module sends a service triggering instruction to the service network element corresponding to the service to be triggered. Step S1530: When the service network element is an internal network element, the service triggering command is sent to the internal network element via API; Step S1540: When the service network element is an external network element, the service triggering instruction is sent to the external network element through standard signaling; Step S1550: The number of services to be triggered is N, where N is an integer greater than 1. Send a service triggering instruction to the service network element corresponding to the (N-1)th service to be triggered. Step S1560: When the response result of the service network element corresponding to the (N-1)th service to be triggered is received according to the service trigger instruction, the service trigger instruction is sent to the service network element corresponding to the Nth service to be triggered. Step S1570: When the service nesting module obtains the response results corresponding to all services to be triggered, it sends the trigger response information to the core network; it obtains the service execution information fed back by the core network based on the response information, and triggers the services to be triggered based on the service execution information.

[0069] The following examples illustrate the principles behind the business triggering method of this application. (Reference) Figure 16 , Figure 16 This is an example diagram of a service triggering method provided in another embodiment of the present invention. In this example, the service is a user subscription, and the core network also includes HLR and HSS. The service triggering method includes the following steps: In step S1600, the core network receives a call request for the subscribed service A. Step S1610: The core network queries the HLR / HSS for contract information and obtains the contract information queried from the HLR / HSS. In step S1620, the core network triggers the service nesting module based on the contract information, so that the service nesting module matches service A from the stored contract information; Step S1630: The business nesting module triggers business A according to the business nesting rules; or, Step S1640: The core network receives a call request, which is for subscribed service A and service B. Step S1650: The core network queries the HLR / HSS for contract information and obtains the contract information queried from the HLR / HSS. In step S1660, the core network triggers the service nesting module based on the contract information, so that the service nesting module matches service A and service B from the stored contract information. Step S1670: The business nesting module triggers business A according to the business nesting rules; In step S1680, the business nesting module triggers business B according to the business nesting rules.

[0070] The following two specific examples illustrate the business signaling interaction process in the business triggering method.

[0071] Example 1: Reference Figure 17 , Figure 17 This is an example diagram of CS service signaling interaction provided in another embodiment of the present invention. The signaling interaction process includes the following steps: Step S1700: The core network triggers Internet Datagram Protocol (IDP) information to the service nesting module; Step S1710: After the business nesting module determines the business nesting rules, the first business to be triggered is matched. The first business to be triggered is business A corresponding to the internal network element. The business triggering instruction is sent to the internal network element through the Parlay internal interface. Step S1720: The internal network element sends a response result to the service nesting module based on the service trigger command. Step S1730: The service nesting module matches the second service to be triggered according to the service nesting rules. The second service to be triggered is service B corresponding to the internal network element. The service triggering instruction is sent to the internal network element through the Parlay internal interface. In step S1740, the internal network element sends a response result to the service nesting module through the Parlay internal interface according to the service trigger command. In step S1750, the service nesting module matches the third service to be triggered according to the service nesting rules. The third service to be triggered is service C corresponding to the external network element. The service nesting module sends an IDP message to the external network element through standard signaling. In step S1760, the external network element sends the response result back to the service nesting module via standard signaling; Step S1770: When the service nesting module obtains the response results corresponding to all services to be triggered, it sends the trigger response information to the core network. In step S1780, the core network obtains the service execution information based on the trigger response information and sends the service execution information to the corresponding service to be triggered, thereby triggering the service to be triggered.

[0072] Example 2: Reference Figure 18 , Figure 18 This is an example diagram of IMS service signaling interaction provided in another embodiment of the present invention. The signaling interaction process includes the following steps: In step S1800, the core network triggers an INVITE message to the service nesting module; Step S1810: After the business nesting module determines the business nesting rules, the first business to be triggered is matched. The first business to be triggered is business A corresponding to the internal network element. The business triggering instruction is sent to the internal network element through the Parlay internal interface. Step S1820: The internal network element sends a response result to the service nesting module based on the service trigger command. In step S1830, the service nesting module matches the second service to be triggered according to the service nesting rules. The second service to be triggered is service B corresponding to the internal network element. The service triggering instruction is sent to the internal network element through the Parlay internal interface. In step S1840, the internal network element sends a response result to the service nesting module through the Parlay internal interface according to the service trigger command. In step S1850, the service nesting module matches the third service to be triggered according to the service nesting rules. The third service to be triggered is service C corresponding to the external network element. The service nesting module sends an INVITE message to the external network element through standard signaling. In step S1860, the external network element sends the response result back to the service nesting module via standard signaling; Step S1870: When the service nesting module obtains the response results corresponding to all services to be triggered, it sends the trigger response information to the core network. In step S1880, the core network obtains the service execution information based on the trigger response information and sends the service execution information to the corresponding service to be triggered, thereby triggering the service to be triggered.

[0073] Additionally, refer to Figure 19 , Figure 19 This is a schematic diagram of the structure of an electronic device provided in another embodiment of the present invention. An electronic device 1900 of the present invention includes: a memory 1910, a processor 1920, and a computer program stored in the memory 1910 and executable on the processor 1920.

[0074] The processor 1920 and memory 1910 can be connected via a bus or other means.

[0075] The non-transient software program and instructions required to implement the service nesting rule configuration method or service triggering method of the above embodiments are stored in the memory 1910. When executed by the processor 1920, the service nesting rule configuration method or service triggering method of the electronic device 1900 in the above embodiments is executed, for example, the above-described... Figure 2 Method steps S200 to S220, Figure 3 Method steps S300 to S310, Figure 4 Method step S400, Figure 5 Method steps S500 to S510, Figure 6 Method steps S610 to S620, Figure 7 Method steps S700 to S710, Figure 8 Method steps S800 to S820, Figure 9 Method steps S900 to S910, Figure 10 Method steps S1000 to S1020, Figure 11 Method steps S1100 to S1110, Figure 12Method steps S1200 to S1210, Figure 13 The method steps S1300 to S1310.

[0076] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; 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.

[0077] Furthermore, one embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions that are executed by a processor or controller, for example, by a processor in the above-described client device embodiment. These instructions cause the processor to execute the business nesting rule configuration method applied to the business nesting module in the above-described embodiment, for example, executing the above-described... Figure 2 Method steps S200 to S220, Figure 3 Method steps S300 to S310, Figure 4 Method step S400, Figure 5 Method steps S500 to S510; or, execute the business nesting rule configuration method applied to BOSS in the above embodiments, for example, execute the above-described method. Figure 6 Method steps S610 to S620, Figure 5 Method steps S700 to S710; or, execute the business triggering method applied to the business nesting module in the above embodiments, for example, execute the above-described method. Figure 8 Method steps S800 to S820, Figure 9 Method steps S900 to S910, Figure 10 Method steps S1000 to S1020, Figure 11 Method steps S1100 to S1110, Figure 12 Method steps S1200 to S1210; or, execute the service triggering method applied to the core network in the above embodiments, for example, execute the above-described method. Figure 13The method steps S1300 to S1310 are described above. Those skilled in the art will understand that all or some of the steps in the methods and systems disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0078] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of the present invention.

Claims

1. A method for configuring business nesting rules, applied to a business nesting module, comprising: Obtain contract information, which is generated by the Business Operation Support System (BOSS) and sent to the business nesting module through the application programming interface (API) according to preset pointing information. The pointing information is generated by the core network after determining the available business nesting module upon receiving the contract information generated and sent by the BOSS for the first time, and is fed back to the BOSS by the core network and saved. Complete the business contract signing based on the aforementioned contract information and update the contract information table; Obtain network parameters, and determine service nesting rules based on the network parameters and the contract information table. The network parameters are used to characterize the network attributes of the service.

2. The method according to claim 1, characterized in that, The step of completing the business contract signing and determining the contract information table based on the contract information includes: Obtain a contract information table, which includes several contract parameters, wherein the several contract parameters in the contract information table are pre-obtained and configured from a preset parameter database; The contract information table is updated based on the contract parameters and the contract information.

3. The method according to claim 2, characterized in that, The step of completing the business contract signing and updating the contract information table based on the contract information also includes: The contract type information for the business contract is determined based on the contract parameters and the contract information.

4. The method according to claim 1, characterized in that, The acquisition of network parameters includes: Upon initial determination of the contract information table, the corresponding business function of the contract information table is triggered; Obtain and save the network parameters fed back by the triggered service.

5. A method for configuring nested business rules, applied to BOSS, including: Generate contract information; Obtain preset pointing information, and send the subscription information to the service nesting module via API according to the pointing information, so that the service nesting module completes the service subscription and determines the subscription information table according to the subscription information, thereby enabling the service nesting module to determine the service nesting rules according to the network parameters and the subscription information table, and the service nesting rules are used to characterize the network attributes of the service; The BOSS is connected to the core network. The pointing information is generated by the core network after it receives the contract information generated and sent by the BOSS for the first time, determines the available service nesting modules, and is fed back to the BOSS by the core network and saved.

6. The method according to claim 5, characterized in that, The BOSS communicates with the service network element, and the generation of contract information includes: Obtain the subscription instruction sent by the service network element via standard signaling; The signing information is generated according to the signing instruction.

7. A service triggering method, applied to a service nesting module, the service nesting module being communicatively connected to the core network, comprising: When a service interaction instruction sent by the core network is received, the service nesting rule is obtained, wherein the service nesting rule is configured by the method described in any one of claims 1 to 4; The business to be triggered is determined according to the aforementioned business nesting rules; Send a service triggering instruction to the service network element corresponding to the service to be triggered.

8. The method according to claim 7, characterized in that, The identified number of services to be triggered is N, where N is an integer greater than 1. Sending a service trigger instruction to the network element corresponding to each service to be triggered includes: Send a service triggering command to the service network element corresponding to the (N-1)th service to be triggered; When the response result of the service network element corresponding to the (N-1)th service to be triggered is received according to the service trigger instruction, the service trigger instruction is sent to the service network element corresponding to the Nth service to be triggered.

9. The method according to claim 8, characterized in that, After sending the service triggering instruction to the service network element corresponding to the service to be triggered, the method further includes: Once the response results corresponding to all the services to be triggered are obtained, trigger response information is sent to the core network; Obtain the service execution information fed back by the core network based on the response information; The pending service is triggered based on the service execution information.

10. The method according to claim 7, characterized in that, The service network element includes internal network elements and external network elements. Sending a service triggering instruction to the service network element corresponding to the service to be triggered includes: When the service network element is an internal network element, the service trigger command is sent to the internal network element via API; or, When the service network element is an external network element, the service triggering instruction is sent to the external network element through standard signaling.

11. The method according to claim 7, characterized in that, After sending the service triggering instruction to the service network element corresponding to the service to be triggered, the method further includes: Obtain the response result fed back by the service network element corresponding to the service to be triggered according to the service triggering instruction; Based on the response result and the business nesting rules, the associated triggering business is determined to be related to the business to be triggered.

12. A service triggering method, applied to a core network, wherein the core network is communicatively connected to a service nesting module, comprising: Upon receiving a call request, generate a business interaction instruction based on the call request; The business interaction instruction is sent to the business nesting module so that the business nesting module can obtain the business nesting rules and trigger the business according to the business nesting rules, wherein the business nesting rules are configured by the method described in any one of claims 1 to 4.

13. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements the method as claimed in any one of claims 1 to 4, or implements the method as claimed in claims 5 to 6, or implements the method as claimed in any one of claims 7 to 11, or implements the method as claimed in claim 12.

14. A computer-readable storage medium storing computer-executable instructions for performing the method as claimed in any one of claims 1 to 4, or the method as claimed in claims 5 to 6, or the method as claimed in any one of claims 7 to 11, or the method as claimed in claim 12.

Citation Information

Patent Citations

  • Method and system for processing multimedia message value added service

    CN101207849A

  • Intelligent network service nesting method, system and service broker

    CN102547484A