CN114531517A

CN114531517A - Service management method and related device

Info

Publication number: CN114531517A
Application number: CN202011323950.XA
Authority: CN
Inventors: 刘永春; 罗向荣; 汪洋
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-11-23
Filing date: 2020-11-23
Publication date: 2022-05-24

Abstract

The embodiment of the invention discloses a service management method and a related device, which are applied to an online gateway OM, and the method can comprise the following steps: receiving an active release service message, and sending a user list request to a charging function module CHF; receiving a list of users for the CHF feedback; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released; sending a service release request to a mobile service switching center (MSC); the service release request comprises the one or more service identifications; the service release request is used for indicating the MSC to release services corresponding to the one or more service identifiers respectively. The embodiment of the invention can improve the service management capability of the charging system.

Description

Service management method and related device

Technical Field

The present invention relates to the field of service management technologies, and in particular, to a service management method and a related apparatus.

Background

With the continuous development of mobile communication technology, mobile terminals such as smart phones gradually blend into the aspects of people's lives. The number of mobile terminals is increasing, making mobile communication the most widely used communication method. The smart phone can be used as a tool for sharing information in various scenes such as life entertainment, work and office and the like through a mobile communication technology, so that management of telecommunication services (such as voice services, video phones, electronic data exchange and the like) depending on mobile communication is correspondingly developed.

Currently, an operator can charge and deduct a fee for a voice call service used by a user through a charging system based on a Credit Control protocol (DCC). For example, the mobile terminal initiates a voice call, the mobile switching center monitors the voice call event and sends charging information (such as call duration, call user information, etc.) to the charging system, and then the charging system can deduct the charge from the user account according to the call duration in the charging information.

However, it was found during actual use that the charging system has some drawbacks for voice or video call services. For example, when the billing system is going to perform system maintenance, the billing system needs to be stopped or restarted, during which the billing system will stop service and the billing session will be cleaned up. For a voice call which is connected but not hung up before the charging system performs system maintenance, the charging system cannot acquire charging information related to the voice call event through a mobile switching center, so that charging and fee deduction cannot be performed, and income of an operator is damaged. For another example, when the charging system is overloaded, the charging system cannot access the sessions of the user of Value (VIP) in time, resulting in call failure of these VIP users or call success by dialing many times, which may cause dissatisfaction of the VIP users on the service quality, thereby causing a significant complaint.

Therefore, how to improve the service management capability of the charging system is an urgent problem to be solved.

Disclosure of Invention

The technical problem to be solved by the embodiments of the present invention is to provide a service management method and a related device, which solve the problem of service management of a charging system in a specific scene and effectively improve service management capability.

In a first aspect, an embodiment of the present invention provides a service management method applied to an online gateway OM, including: receiving an active release service message, and sending a user list request to a charging function module CHF; receiving a list of users for the CHF feedback; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released; sending a service release request to a mobile service switching center (MSC); the service release request comprises the one or more service identifications; the service release request is used for indicating the MSC to release services corresponding to the one or more service identifiers respectively.

In the prior art, when a charging system (including an online gateway, a charging function module, and a Portal) cannot constantly and normally operate under some special conditions (such as restart update or overload), problems may occur such as inability to immediately receive corresponding service charging information or inability to access new user services. The method includes that due to uncertainty of time for a user to actively end a service, when a charging system is in an abnormal working state and the user is still in service, at this time, since an operator is already in the abnormal working state, related information of the ongoing service may not be received and accurate charging may not be performed. Therefore, when the operator maintenance department detects that the charging system is about to enter an abnormal working state, the embodiment of the invention actively releases the current service and carries out corresponding charging according to the requirement, thereby being capable of managing the user service more conveniently and actively. Specifically, in some special cases, the charging system (including the online gateway, the charging function module, and the Portal) receives a message for actively releasing services, then the online gateway OM requests the charging function module CHF to record a user list corresponding to services currently being released, where the list may include one or more service identifiers of the services currently being performed, after receiving the user list, the OM sends a request for releasing the services to be released corresponding to the service identifiers on the list to the mobile service switching center MSC, and then the MSC may disconnect the services to be released according to the request to end the services currently being performed by the user, and then the charging system may further obtain usage information of the services that have been actively released, and then perform corresponding charging according to the usage information. By implementing the method of the embodiment of the invention, the operator can actively release the ongoing service of the user and correspondingly deduct the fee of the used service of the user (including the service that the user is not actively hung up), thereby improving the service management capability. For example, the charging system may deduct the fee for all the services used by the user before suspending the operation, or receive the service use request of the VIP user after releasing the services used by the common user under the condition of system overload, so as to implement the corresponding service management for the user who does not actively finish the service, thereby avoiding the income loss of the operator and improving the user experience of the VIP user.

In a possible implementation manner, after receiving the active release service message, the method further includes: receiving a service request access sent by the MSC; the service request access is an application for requesting a service to be used by a user; sending a preset error code to the MSC; the preset error code is used for indicating the MSC to refuse to respond to the service request access. In the embodiment of the invention, after the online gateway OM receives the message of actively releasing the service, if a new user requests to use the service again, the OM can send a preset error code to the mobile service switching center MSC for indicating the MSC to reject the request of the user and not providing corresponding service for the user, thereby realizing that the new user service is not accessed before the charging system (comprising the online gateway, the charging function module and the Portal) is maintained or updated.

In one possible implementation, the method further includes: receiving an application charging report ACR sent by the MSC; the ACR comprises service use duration corresponding to the one or more service identifications in the user list respectively; generating charging information according to the ACR; sending the charging information to the CHF; the charging information is used for the CHF to deduct the fees of the services corresponding to the one or more service identifications respectively. In the embodiment of the present invention, after the mobile services switching center MSC releases the service to be released corresponding to the service identifier in the user list, the online gateway OM receives the ACR message (for example, including the service usage time information of the current user service) of the service that has been actively released and sent by the MSC, and then the OM generates charging information according to the information, and sends the charging information to the charging function module CHF, so as to perform specific charging on the CHF.

In one possible implementation, the method further includes: receiving deduction information sent by the CHF; and the fee deduction information is used for informing the OM that fee deduction operation is completed. In the embodiment of the present invention, after the charging function module CHF completes the fee deduction of the service to be released corresponding to the service identifier recorded on the user list according to the charging information, the online gateway OM receives the fee deduction information sent by the CHF, the content of the fee deduction information includes the notification OM that the fee deduction is completed, and then OM ends the management of the service that has been actively released.

In a possible implementation manner, the active release service message includes a web service webservice instruction sent by a Portal of the charging system; or, the active release service message includes a message of overload of the service system sent by the OM, the CHF or the Portal in the charging system. In the embodiment of the invention, when the charging system needs to be maintained or updated and other special scenes, the Portal of the charging system sends a network service webservice instruction to the OM to inform the OM of actively releasing the current service, or after the charging system exceeds the borne service processing capacity, the OM or CHF in the charging system sends a message of actively releasing the service to the OM.

In a possible implementation manner, the sending a service release request to a mobile services switching center MSC includes: and sending a service release request to the MSC by continuing the dialogue service processing TC-continue primitive. In the embodiment of the present invention, the OM sends the release service request to the MSC through a TC-continue primitive (for example, the MSC may be triggered to enter or be in a hold state) instead of the TC-end primitive (for example, the MSC may be triggered to enter an end stage), where the TC-continue primitive carries a release cause value for releasing the service (for example, the cause value for actively releasing the voice service may be 8). It should be noted that the release reason value for releasing the service may be obtained by querying a service release and release reason value correspondence table, which is defined by a standard protocol. After the service release request is sent through the TC-continuity primitive, the OM can continue to receive the information sent by the MSC (for example, receive the application charging report ACR) after the corresponding service is successfully released.

In a second aspect, the present application provides a service management method, which is applied to a charging function module CHF, and includes: receiving a user list request sent by an online gateway OM; the user list request is sent by the OM after receiving the active release service message; generating a user list according to a preset rule; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released; and sending the user list to the OM. In the embodiment of the invention, after an online gateway OM receives a message of actively releasing a service, a charging function module CHF receives a request of the OM for recording a user list corresponding to a service which can be released currently, and then the CHF generates a user list according to preset rules configured in advance (such as non-VIP users with overlong online time and the like), wherein the user list can comprise one or more service identifiers of the service to be released, and then the user list is sent to the OM, so that the OM can conveniently manage the service of the current user, and thus, a charging system can also manage the corresponding service of users which do not actively finish the service in a system maintenance or system overload scene, thereby improving the service management capability of the user, reducing the income loss of an operator and avoiding major complaints of VIP users.

In one possible implementation, the method further includes: receiving charging information sent by the OM; the charging information comprises an ACR (application charging report); the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list. In the embodiment of the invention, CHF can obtain charging information from OM, thereby facilitating the subsequent charging of services corresponding to the service identification recorded in the user list.

In one possible implementation, the method further includes: and according to the charging information, deducting the services corresponding to the one or more service identifications in the user list respectively. In the embodiment of the invention, after the CHF receives the charging information, the charging information is used for correspondingly deducting the service used by the user, so that the charging system actively releases the service of the user and correspondingly charges the used service which is not actively hung up by the user in special scenes such as system maintenance or system overload, the service management capability of the user is improved, the income loss of an operator is reduced, and meanwhile, the major complaint of a VIP user can be avoided.

In one possible implementation, the method further includes: sending fee deduction information to the OM; and the fee deduction information is used for informing the OM that fee deduction operation is completed. In the embodiment of the present invention, when the CHF completes the operation of deducting the fee of the service to be released corresponding to the service identifier recorded on the user list according to the charging information, the CHF sends the fee deduction information to OM, and then OM ends the management of the service that has been actively released.

In one possible implementation, the preset rule includes a service identifier for recording services which are not currently VIP users and have long online time. In the embodiment of the invention, after receiving a request of OM for recording a user list corresponding to a record which can release the current ongoing service, CHF can record the service identifier of the current non-VIP service with overlong online time according to a preset rule and generate the user list, thereby facilitating the subsequent management of the user service. It should be noted that the recorded service identifier is an identifier of a service that needs to be actively released.

In a third aspect, the present application provides a service management method, applied to a mobile services switching center MSC, including: receiving a service release request sent by an online gateway OM; the service release request comprises one or more service identifications recorded in a user list, and each service identification corresponds to a service to be released; the service release request is sent by the OM after receiving the active release service message; and releasing the services corresponding to the one or more service identifications according to the service release request. In the embodiment of the invention, after receiving the service release request sent by the OM, the mobile service switching center MSC disconnects the services to be released corresponding to the service identifiers according to the service identifiers in the service release request to finish the service currently performed by the user, so that the operator can actively release the user service and correspondingly charge the used service which is not actively hung up by the user, thereby improving the service management capability of the user, reducing the income loss of the operator and avoiding major complaints of the VIP user.

In a possible implementation manner, an application charging report ACR is sent to the OM; the ACR includes service usage durations respectively corresponding to the one or more service identifiers in the user list. In the embodiment of the invention, after the MSC completes the active release task of the service to be released, the MSC sends the ACR information of the application charging report of the actively released service to the OM, and the service use duration information of the user service is recorded in the information, so that a charging system (comprising an online gateway, a charging function module and a Portal) can conveniently carry out corresponding charging.

In a fourth aspect, the present application provides a service management apparatus, which is applied to an online gateway OM, and includes: a first receiving unit, configured to receive an active release service message and send a user list request to a charging function module CHF; a second receiving unit, configured to receive a user list of the CHF feedback; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released; a first sending unit, configured to send a service release request to a mobile services switching center MSC; the service release request comprises the one or more service identifications; the service release request is used for indicating the MSC to release services corresponding to the one or more service identifiers respectively.

In one possible implementation, the apparatus further includes: the device further comprises: a third receiving unit, configured to receive a service request access sent by the MSC; the service request access is an application for requesting a service to be used by a user; a second sending unit, configured to send a preset error code to the MSC; the preset error code is used for indicating the MSC to refuse to respond to the service request access.

In one possible implementation, the apparatus further includes: a fourth receiving unit, configured to receive an application charging report ACR sent by the MSC; the ACR comprises service use duration corresponding to the one or more service identifications in the user list respectively; the first processing unit is used for generating charging information according to the ACR; a third transmitting unit, configured to transmit the charging information to the CHF; the charging information is used for the CHF to deduct the fees of the services corresponding to the one or more service identifications respectively.

In a possible implementation manner, the apparatus further includes a fifth receiving unit, configured to receive deduction information sent by the CHF; and the fee deduction information is used for informing the OM that fee deduction operation is completed.

In a possible implementation manner, the first sending unit is specifically configured to: and sending a service release request to the MSC by continuing the dialogue service processing TC-continue primitive.

In a fifth aspect, the present application provides a service management apparatus, which is applied to a charging function module CHF, and includes: the first receiving unit is used for receiving a user list request sent by an online gateway OM; the user list request is sent by the OM after receiving the active release service message; the first processing unit is used for generating a user list according to a preset rule; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released; and the first sending unit is used for sending the user list to the OM. In one possible implementation, the apparatus further includes: the second receiving unit is used for receiving the charging information sent by the OM; the charging information comprises an ACR (application charging report); the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list.

In one possible implementation, the apparatus further includes: and the second processing unit is used for deducting the service corresponding to the one or more service identifiers in the user list according to the charging information.

In one possible implementation, the apparatus further includes: the second sending unit is used for sending fee deduction information to the OM; and the fee deduction information is used for informing the OM that fee deduction operation is completed.

In a sixth aspect, the present application provides a service management apparatus, which is applied to a mobile services switching center MSC, and includes: the first receiving unit is used for receiving a service release request sent by an online gateway OM; the service release request comprises one or more service identifications recorded in a user list, and each service identification corresponds to a service to be released; the service release request is sent by the OM after receiving the active release service message; and the first processing unit is used for releasing the services corresponding to the one or more service identifications according to the service release request.

In one possible implementation, the apparatus further includes: a first sending unit, configured to send an application charging report ACR to the OM; the ACR includes service usage durations respectively corresponding to the one or more service identifiers in the user list.

In a seventh aspect, the present invention provides a mechanism for actively releasing services, where the mechanism is also effective in data services, and in the data services, the session is ended by actively issuing an ASR message, and the GGSN charges the last segment to the charging system through CCR-T carrying used traffic after the user finishes surfing the internet.

In an eighth aspect, an embodiment of the present invention provides an electronic device, where the electronic device includes a processor, and the processor is configured to support the electronic device to implement corresponding functions in the service management method provided in the first aspect, the second aspect, or the third aspect. The electronic device may also include a memory, coupled to the processor, that stores program instructions and data necessary for the electronic device. The electronic device may also include a communication interface for the electronic device to communicate with other devices or a communication network.

In a ninth aspect, the present application provides a chip system, where the chip system includes a processor, configured to support an electronic device to implement the functions recited in the first aspect, the second aspect, or the third aspect, for example, to generate or process information recited in the service management method. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the electronic device. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

In a tenth aspect, the present application provides a computer program, which may comprise: the computer program includes instructions that, when executed by a computer, enable the computer to execute the procedures executed by the processing module in the service management apparatus in the first aspect, the second aspect, or the second aspect.

Drawings

Fig. 1 is a schematic diagram of a current operator voice charging process according to an embodiment of the present invention.

Fig. 2 is a schematic diagram of a system architecture for service management according to an embodiment of the present invention.

Fig. 3 is a flowchart illustrating a service management method according to an embodiment of the present invention.

Fig. 4 is a schematic view of an application of a service management method in a voice service according to an embodiment of the present invention.

Fig. 5 is a flowchart of a voice charging system in the case of system maintenance according to an embodiment of the present invention.

Fig. 6A is a schematic view of a voice service charging management flow of a voice charging system in an overload scenario according to an embodiment of the present invention.

Fig. 6B is a flowchart of a work flow in an overload scenario of a voice charging system according to an embodiment of the present invention.

Fig. 7 is a schematic diagram of a first structure of a service management apparatus according to an embodiment of the present invention.

Fig. 8 is a schematic diagram of a second structure of a service management apparatus according to an embodiment of the present invention.

Fig. 9 is a schematic diagram of a third structure of a service management apparatus according to an embodiment of the present invention.

Detailed Description

The embodiments of the present invention will be described below with reference to the drawings.

The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different elements and not for describing a particular sequential order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

Hereinafter, some terms in the present application are explained to facilitate understanding by those skilled in the art.

(1) Active Release Call (Auto Release Call) refers to a charging system actively requesting the core network to end a Call because of service requirements.

(2) Overload (Over Load) traffic exceeds the processing power that the system is experiencing resulting in calls being rejected.

(3) Revenue loss (Revenue Lost) the operator incurs cost loss because the user uses the service but does not have a scenario such as a fee deduction.

(4) System maintenance (System Maintain) is temporarily unable to provide service maintenance due to operations such as upgrading and modifying.

First, the technical problems to be specifically solved by the present application are analyzed and presented. In the prior art, a service charging management technology includes the following schemes:

for facilitating understanding of the current service charging management technology, please refer to fig. 1, where fig. 1 is a schematic diagram of a current operator voice charging flow. The process of charging the voice service by the current operator charging system specifically comprises the following steps 1 to 17:

step 1, the Mobile terminal (MS) sends an Initial Call message request Call to the Mobile services switching center MSC. For example, after the user dials the number on the mobile phone, the mobile phone first sends a message carrying a call request to the MSC, and requests the MSC for the call.

And 2, the MS sends an Initial DP (IDP) message to an Online gateway (OM) to start the call. For example, after receiving the mobile phone request call, the MSC sends a message for starting the call to the OM, and notifies the online gateway that there is a mobile phone that needs to perform a voice call.

Step 3, OM sends Request monitoring and reports BCSM Event message (RRBE) to Mobile services Switching center (MSC) to Request MSC to monitor BCSM Event. For example, after receiving a call initiation message that a mobile phone needs to perform a voice call, the OM sends a request to the MSC to perform basic call state event monitoring.

And step 4, OM sends Credit-Control-Request (CCR-I) to a charging Function module (CHF) to Request the CHF to perform authentication and budget. For example, after the online gateway sends the RRBE message to the mobile services switching center, it sends a CCR-I message carrying the charging requirement to the charging function module, and then requests the charging function module to perform authentication and budget according to the CCR-I message.

And step 5, performing authentication and budget by using the CHF. For example, the CHF determines whether the user has the right to make a voice call and calculates whether the user has a balance to make a call according to the mobile phone user account in the CCR-I message.

And step 6, the CHF sends a Credit-Control-Answer message (CCA-I) to the OM. For example, after CHF has authenticated, if the user of the mobile phone has the right to make a voice call and has a balance to make a call, a CCA-I message carrying that mobile phone can make a voice call is sent to OM.

Step 7, the OM sends an application Charging message (AC) to the MSC to request the MSC to monitor the call duration. For example, the online gateway may issue a call duration to the MSC, and then request the MSC to monitor the voice call duration and record the voice call duration information, so as to facilitate subsequent charging and deduction.

And step 8, the OM sends a Continue message to the MSC to request to Continue calling. For example, after the OM sends the message requesting the MSC to monitor the call duration, the OM may also send a message of continuing the call to the MSC to allow the mobile phone to continue the call.

Step 9, MSC sends Connect Call message to MS to continue calling. For example, when the mobile services switching center starts to monitor the call duration of the mobile phone and receives a message of continuing the call, it will send a message of continuing the call to the mobile phone, allowing the mobile phone to make a voice call.

Step 10, the MS rings to continue calling. For example, after receiving the call continuation message, the mobile phone starts ringing and makes a voice call after being connected.

And step 11, the MS finishes the call hang-up.

Step 12, MSC reports application accounting report ACR to OM to request accounting. For example, in the process of a voice call of a mobile phone, the MSC monitors and records the call duration of the mobile phone in real time, and reports the recorded call duration information to the OM when receiving a message of ending a session of the mobile phone.

Step 13, MSC reports BCSM Event (Event Report BCSM, ERB) to OM. For example, after the mobile phone finishes the voice call, the MSC reports the on-hook event of the mobile phone to the OM.

And step 14, OM sends a CCR-T message to CHF to request CHF deduction. For example, after the mobile phone finishes the voice call, the OM sends the relevant information for charging, such as the length of the call, to the charging function module, and the charging function module can perform charging based on the information.

And 15, deducting fee by using CHF. For example, after receiving a CCR-T message sent by an online gateway, the charging function module may perform corresponding fee deduction on a mobile phone user account according to the voice call duration in the message.

Step 16, the CHF sends a CCA-T message to OM.

And step 17, the OM sends a release call message to the MSC to inform the release of the call. For example, when the on-line gateway receives the CCA-T message, it will notify the mobile services switching center to release the call, and end the monitoring of the basic call status event of the handset.

The scheme can charge the voice service used by the user under the normal working condition of the charging system, but when the charging system has problems, the following defects exist:

disadvantage 1: and when the charging system starts system maintenance, the user account number is failed to deduct the fee, so that the income of an operator is reduced. For example, if the charging system (including OM and CHF) starts to maintain during the voice call of the user, when the user actively hangs up or reaches the monitoring duration issued by the AC, the OM cannot receive the ACR message sent by the MSC, and the CHF cannot obtain the call duration of the mobile phone, thereby causing the loss of income of the operator due to the failure of charging.

And (2) disadvantage: in case of overload of the charging system, the VIP user cannot normally talk. For example, when the voice traffic exceeds the processing capacity that the billing system can handle, no new call can be accessed, but each operator has its own VIP subscriber. If the VIP user requests to use the voice service, in this case, the charging system cannot access the session of the VIP user in time, which may cause call failure of these VIP users or call success after multiple dialing waits for the active hang-up of the user who is talking, which may cause dissatisfaction of the VIP user with the service quality, thereby causing a serious complaint.

In summary, in the conventional service charging management method, under special conditions such as system maintenance and system overload of the charging system, the income loss of an operator and the user experience of the VIP user are poor. Therefore, the service management method provided in the present application is used to solve the above technical problem.

In order to facilitate understanding of the embodiments of the present invention, the following exemplarily lists a scenario to which the service management method is applied in the present application. Two scenarios may be included:

scene one: the charging system carries out a system maintenance scenario. Under the normal use scene, the charging system receives the user service use information report reported by the mobile service switching center in the core network, and then carries out corresponding charging on the user account according to the report. However, when the charging system performs upgrading, modifying, etc., the charging system may be shut down or restarted, resulting in the failure of the charging system to provide services. In this scenario, the charging system cannot receive the user service usage information report reported by the mobile service switching center, and the charging system will remove the charging session, so that the user uses the service provided by the operator but the operator cannot make a corresponding fee deduction on for the user. By using the service management method in the application, the system maintenance mode can be entered in advance before the charging system stops service, an operator can actively release the user session using the service currently and no longer provide new service access service, then corresponding charging is carried out based on the user service use information report, and the service of the charging system is suspended after the charging is finished, so that the income loss of the operator is reduced.

Scene two: charging system overload scenarios. In a normal usage scenario of the charging system, for example, after a user initiates a voice call request, the mobile services switching center sends a message of call service access to an online gateway in the charging system, and then the online gateway and the charging function module perform authentication. However, under the overload condition of the charging system, the charging system can directly reject the call request of the user and send a call request rejection message to the mobile service switching center for rejecting the call request of the user. In this scenario, if the VIP users of the operator request to use the voice call service, the VIP users cannot make normal calls, thereby causing the VIP users to be dissatisfied with the service quality. By using the service management method in the application, under the overload condition of the charging system, if an operator identifies that a VIP user needs to carry out voice call, the operator can actively release the ordinary user session with overlong online time, and access the call request of the VIP user after charging the corresponding ordinary user, thereby improving the user experience of the VIP user.

It is understood that the above two application scenarios are only a few exemplary implementations in the embodiments of the present invention, and the application scenarios in the embodiments of the present invention include, but are not limited to, the above application scenarios.

Embodiments of the present application are described below with reference to the drawings.

Based on the technical problems and the corresponding application scenarios in the present application, in order to facilitate understanding of the embodiments of the present invention, a system architecture based on the embodiments of the present invention is described below. Referring to fig. 2, fig. 2 is a schematic diagram of a system architecture for service management according to an embodiment of the present invention, where the system is used to solve the problems that an error exists in operator billing and a user experience of a VIP user is poor in a case of maintenance or overload of a charging system. The system architecture may include a terminal device 201, a core network 202 and a charging system 203. Wherein the content of the first and second substances,

terminal equipment 201, terminal equipment 201 can be devices such as wisdom screen, personal computer, panel computer, smart mobile phone. For example, when the terminal device 201 is a smart phone, the smart phone may implement data exchange services such as voice call and video call with other terminal devices. If the smart phone needs to perform a voice call service, a service request message is sent to a Mobile Switching Center (MSC) in the core network 202, and then the smart phone can continue the voice call after receiving a message that the smart phone can continue to call and is sent by the core network 202.

The core network 202, the core network 202 is a network that provides convergence services and switches services. Its main role is overall service signaling control and bearer establishment. The core network 202 includes a mobile services switching center MSC, a Visitor Location Register (VLR), and a soft switching center (SSP). The mobile service switching center provides switching function and other functional entities facing the system to connect the mobile user and the mobile user, the mobile user and the fixed network user, and can provide telecommunication service (such as telephone, emergency call, etc.), bearing service (such as synchronous data, etc.) and supplementary service (such as call forwarding, call restriction, etc.) for the mobile user; the visitor location register serves mobile subscribers within its control area, stores information about registered mobile subscribers entering its control area, and provides the registered mobile subscribers with the necessary conditions for establishing call continuation. The softswitch center provides call control and connection control functions for services with real-time requirements. For example, after receiving a service request message sent by the terminal device 201, the mobile services switching center may continue the request or data of the user to different networks and may monitor the service duration used by the user; meanwhile, the monitoring information is uploaded to the charging system 203, which facilitates the service management of the subsequent charging system 203.

The charging system 203, the charging system 203 will charge based on the service usage record generated according to the used duration and the used flow, and provide service monitoring and service management for the user. The charging system 203 comprises an online gateway OM, a charging function module CHF and Portal. The online gateway is mainly used for interacting with a mobile service switching center, generating charging information according to service use related information sent by the mobile service switching center, and sending the charging information to a charging function module. The charging function module can deduct the charge of the corresponding service according to the charging information provided by the online gateway. Portal is an interface capable of configuring various parameters of a charging system, and is mainly used for sending an active service release request to an online gateway in the embodiment of the invention. For example, after receiving the service duration of the user service reported by the mobile services switching center, the charging system 203 may correspondingly deduct the fee from the user account based on the service duration of the user service.

It is understood that a service management system architecture in fig. 2 is only an exemplary implementation manner in the embodiment of the present application, and the service management system architecture in the embodiment of the present application includes, but is not limited to, the above system architecture.

The following describes a specific method architecture on which the embodiments of the present invention are based. Referring to fig. 3, fig. 3 is a schematic flow chart of a service management method in this embodiment, and the service management method in this embodiment will be described from the interactive side of the terminal device, the core network, and the charging system based on the service management system architecture in fig. 2 in conjunction with fig. 3. It should be noted that, in order to describe the service management method in the embodiment of the present application in more detail, in each flow step, the corresponding execution main bodies are described as modules in the terminal device, the core network, and the charging system, but it does not mean that the embodiment of the present application can only perform the corresponding method flow through the described execution main bodies.

Step S301: and the online gateway OM receives the active release service message.

Specifically, in case that the operator maintenance department detects that there is a need to actively release the user service, this active release service message is issued and OM receives the message. Optionally, when the charging system (including the online gateway, the charging function module and the Portal) is under maintenance or system overload state, the online gateway (OM) receives a message for actively releasing the current user service.

In a possible implementation manner, the active release service message includes a web service webservice instruction sent by a Portal of the charging system; or, the active release service message includes a message of overload of the service system sent by the OM and the CHF in the charging system. Specifically, when the charging system needs to be maintained or updated in a special scene, the Portal of the charging system sends a web service instruction to the OM to notify the OM that the OM needs to actively release the currently ongoing service, or after the charging system exceeds the borne service processing capacity, the OM or CHF in the charging system sends a message of actively releasing the service to the OM. For example, corresponding descriptions are performed with reference to fig. 4 and the first scenario, as shown in fig. 4, fig. 4 is an application schematic diagram of a service management method provided in an embodiment of the present invention in a voice service, and S401 in fig. 4 can send a webservice instruction to an online gateway through a Portal in a scenario where a voice charging system (including the online gateway, a charging function module, and the Portal) needs to be maintained, so that the voice charging system enters a maintenance mode. For another example, as shown in fig. 5, fig. 5 is a flowchart illustrating a working process of a voice charging system in a system maintenance situation according to an embodiment of the present invention, and step 1 in fig. 5 may send an active release service message to an online gateway through a Portal. It should be noted that in the maintenance mode, the operator may actively hang up the user currently engaged in the voice call.

In a possible implementation manner, after the OM receives the active release service message, the method further includes: OM receives the service request access sent by the mobile service switching center MSC; the service request access is an application for requesting a service to be used by a user; OM sends the default error code to the said MSC; the preset error code is used for indicating the MSC to refuse to respond to the service request access. Specifically, after the online gateway OM receives the message of actively releasing the service, if a new user requests to use the service again, the OM may send a preset error code to the mobile services switching center MSC for instructing the MSC to reject the request of the user and not provide the corresponding service for the user, so that it may be realized that the new user service is not accessed before the charging system (including the online gateway, the charging function module, and the Portal) is maintained or updated. For example, referring to fig. 4 and the first scenario for corresponding description, fig. 4 is a schematic view of an application of the service management method in the voice service according to the embodiment of the present invention, after S401 in fig. 4, when a user requests a new voice call, an OM may send a preset error code to an MSC to perform call-through recognition for the MSC, so that the voice charging system directly rejects the newly accessed voice call request, and no new voice call service is provided for the user.

Step S302: OM sends a user list request to the charging function module CHF.

In particular, OM, after receiving the message of releasing the service actively, requests from CHF a list of users who record that the service currently in progress can be released, and the list may include one or more service identifiers of the services to be released. For example, at S402 in fig. 4, OM requests a user list from CHF, where the service identifier of the user who has successfully accessed the voice call service currently, i.e., the service identifier of the user who is currently using voice for conversation, is recorded.

In one possible implementation, the CHF receives a user list request sent by OM; the user list request is sent by the OM after receiving the active release service message. Specifically, when OM receives the message of actively releasing the service, CHF receives a request from OM for recording a user list corresponding to the service that can be currently performed.

Step S303: and the charging function module CHF generates a user list according to a preset rule strategy.

Specifically, after the CHF receives an OM request for a user list recording that the current ongoing service can be released, the CHF may generate a user list according to a preset rule policy configured in advance (for example, a common user with an excessively long current service online time, etc.), where the user list may include one or more service identifiers of the current user service. For example, as shown in S403 in fig. 4, the CHF selects the service identifier of the non-VIP user currently using the voice call service and the service is online for too long according to the preset rule policy. It should be noted that there may be one or more users currently using the voice call service, and therefore, there may be one or more service identifiers on the user list.

In one possible implementation, the preset rule includes a service identifier for recording services which are not currently VIP users and have long online time. Specifically, after receiving an OM request for recording a user list corresponding to a service which can be released currently in progress, the CHF can record a service identifier of the service which is not VIP currently and has too long online time according to a preset rule and generate the user list, thereby facilitating subsequent management of the user service. It should be noted that the recorded service identifier is an identifier of a service that needs to be actively released.

Step S304: the CHF sends the user list to OM.

Specifically, the CHF sends the user list to the OM, which is convenient for the OM to perform service management on the service to be released, so that the charging system can perform corresponding service management on the user who does not actively finish the service in special scenes such as system maintenance or system overload scenes, thereby improving the service management capability of the user, reducing the income loss of operators and avoiding major complaints of VIP users.

In one possible implementation, OM receives a list of users of the CHF feedback; the user list comprises one or more service identifications of services to be released. Specifically, after receiving the user list, OM may perform corresponding service management on the user who does not actively end the service, thereby improving the service management capability of the user. For example, as S404 in fig. 4, after receiving the user list, OM may know which voice call services need to be actively released for calling, so that the user voice call services may be better managed.

Step S305: OM sends service release request to mobile services switching center MSC.

Specifically, the service release request includes the one or more service identifiers; the service release request is used for indicating the MSC to release the services corresponding to the one or more service identifications. It should be noted that, after receiving the user list, OM sends a request for releasing the service to be released corresponding to the service identifier on the list to the MSC, so as to further end the service currently performed by the user. For example, as S405 in fig. 4, OM sends a Release Call active Release Call request to MSC, and the cause value of Release Call may be filled in as 8 (representing that the Call is released actively by the operator). For another example, as shown in fig. 5, in step 2 in fig. 5, the OM sends a Release Call active Release Call request to the MSC.

In a possible implementation manner, the OM sending the service release request to the MSC includes: sending a release service request to the MSC by continuing a Session-Continue (TC-Continue) primitive. Specifically, the OM sends a service release request to the MSC through a TC-continue primitive (which may trigger the MSC to enter or be in a hold state) instead of the TC-end primitive (which may trigger the MSC to enter an end stage), where the TC-continue primitive carries a release cause value for releasing the service (for example, the cause value for actively releasing the voice service may be 8), it should be noted that the release cause value for releasing the service may be obtained by querying a service release and release cause value correspondence table, and the correspondence table is defined by a standard protocol. Because the service releasing request is sent through the TC-continue primitive, the OM can continuously receive the information sent by the MSC (such as receiving an application charging report ACR) after the corresponding service is released. For example, as S405 in fig. 4, the OM sends a Release Call active Release Call request to the MSC through the TC-continuity primitive, so that after the MSC releases the voice service, the application charging report ACR of the non-charging service can be continuously reported. For another example, as shown in fig. 5, in step 2 of fig. 5, the OM sends a Release Call active Release Call request to the MSC through the TC-continue primitive.

In one possible implementation, the method applied to the mobile services switching center MSC may include: MSC receives the service release request sent by the on-line gateway OM; the service release request comprises the one or more service identifications; the service release request is sent by the OM after receiving the active release service message. Specifically, after receiving the service release request sent by the OM, the MSC releases the service to the user currently using the voice call service.

Step S306: and the MSC releases the services corresponding to one or more service identifications according to the service release request sent by the OM.

Specifically, after receiving a service release request sent by the OM, the MSC disconnects the services to be released corresponding to the service identifiers according to the service identifiers in the service release request to end the service currently performed by the user, so that the operator can actively release the user service and correspondingly deduct the fee of the used service which is not actively hung up by the user, thereby improving the service management capability of the user, reducing the income loss of the operator, and avoiding major complaints of the VIP user. For example, as S406 in fig. 4, the MSC may actively disconnect the service that is currently performing a voice call according to the release request sent by the OM, so that the operator can actively hang up the user service that is currently performing a voice call. For another example, as shown in fig. 5, in step 3 of fig. 5, the MSC may send a release request according to OM.

Step S307: MSC sends application accounting report ACR to OM.

Specifically, the MSC sends an application charging report ACR to the OM; the ACR includes service usage durations of actively released services corresponding to the one or more service identifiers in the user list, respectively. It should be noted that the ACR is only information used for recording the service usage duration of the voice service, the usage traffic of the data service, and other user service usage services in the embodiment of the present invention, and is not limited to recording only the service usage duration information of one specific service. Specifically, after the MSC completes the task of releasing the service to be released, the MSC sends an application charging report ACR information of the service that has been actively released to the OM, where the service usage duration of the user service is recorded in the information, so that the charging system (including the online gateway, the charging function module, and the Portal) can perform corresponding charging. Optionally, the MSC sends ERB information to the OM, and the information records an end service event (e.g., the operator actively releases the voice call service, etc.), so as to facilitate subsequent charging. For example, as S407 in fig. 4, and as another example, step 4 in fig. 5, the MSC may send the unreported user call duration (including the service usage duration of the current user actively hanging up to end the voice call or the service usage duration of the operator actively releasing the voice call) to the OM through the ACR. Optionally, as shown in fig. 5, fig. 5 is a working flow chart of the voice charging system in the case of system maintenance according to the embodiment of the present invention, and step 5 in fig. 5 reports the ERB to the OM after the MSC completes the disconnection, where the disconnection event is a caller abandonment (Origin-Abandon, O _ Abandon), so that the subsequent voice charging system can perform corresponding charging on the voice service.

In one possible implementation, the method further includes: OM receives the ACR sent by MSC; the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list. Specifically, after the MSC releases the service to be released corresponding to the service identifier in the user list, the OM receives the ACR message of the service that has been actively released and sent by the MSC, and it should be noted that the ACR message includes the service use time of the service that has been actively released or the service that has been actively released by the user, so that the charging system can perform specific charging. Optionally, as shown in fig. 5, fig. 5 is a working flow chart of the voice charging system provided in the embodiment of the present invention under the condition of system maintenance, and in step 5 in fig. 5, the OM may receive an ERB event sent by the MSC, so that the subsequent voice charging system can charge a corresponding service conveniently.

Step S308: OM generates charging information according to the charging application report ACR sent by MSC.

Specifically, the charging information is used for charging the services corresponding to the one or more service identifiers by the CHF. It should be noted that, the OM receives ACR messages of the services that have been actively released and sent by the MSC after the MSC has released the service to be released corresponding to the service identifier in the user list, where the messages include information related to charging, such as service usage duration of the services that have been actively released, and then the OM generates charging information according to the information, so as to facilitate the charging system (including the online gateway, the charging function module, and the Portal) to perform corresponding charging. Optionally, the charging information may include an ERB event sent by the MSC to the OM. For example, in S408 in fig. 4, the OM generates a CCR-T message according to the ACR message, where the CCR-T message includes all relevant messages (such as the call duration of the user) required for performing voice charging. It should be noted that the CCR-T message corresponds to the charging information in the embodiment of the present invention.

Step S309: OM sends charging information to CHF.

Specifically, the charging information is used for charging the services corresponding to the one or more service identifiers by the CHF. It should be noted that OM sends charging information to CHF, so as to facilitate specific charging of CHF. For example, OM sends a CCR-T message to CHF, as in S409 in fig. 4, and for example, step 6 in fig. 5, in order for CHF to charge for the corresponding service. It should be noted that the CCR-T message corresponds to the charging information in the embodiment of the present invention.

Step S310: and the CHF deducts the fee after receiving the charging information sent by the OM.

Specifically, the method further comprises: the CHF receives the charging information sent by the OM; the charging information comprises an ACR (application charging report); the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list. Specifically, the CHF can obtain the charging information from OM, which facilitates the subsequent charging of the service corresponding to the service identifier recorded in the user list. For example, as shown in S410 in fig. 4, after the CHF receives the CCR-T message sent by the OM, corresponding charging may be respectively performed on the user who finishes the call according to the call duration of the user in the CCR-T message.

In a possible implementation manner, according to the charging information, the CHF deducts the services corresponding to the one or more service identifiers in the user list respectively. Specifically, after the charging information is received by the CHF, the service to be released is charged correspondingly according to the charging information, so that the charging system actively releases the user service and charges the used service which is not actively hung up by the user in special scenes such as system maintenance or system overload, thereby improving the service management capability of the user, reducing the income loss of an operator and avoiding major complaints of a VIP user.

Step S311: the CHF sends deduction information to the OM.

Specifically, the fee deduction information is used to notify the online gateway OM that the fee deduction operation is completed. It should be noted that, after the CHF completes the fee deduction operation of the current user service corresponding to the service identifier recorded on the user list according to the charging information, the CHF sends the fee deduction information to the OM, and then the OM ends the management of the current user service. For example, as S411 in fig. 4, as well as step 7 in fig. 5, when the CHF deduction is successful, a CCA-T message is returned to OM, where Result value is 2001 (the successful deduction return value specified by the Diameter credit control protocol is 2001), and in order to notify OM that the fee deduction is successful, OM ends the service management on the corresponding service. It should be noted that, in a scenario where the charging system needs to be maintained, after the charging system completes charging the services corresponding to all the service identifiers in the user list, the operator may stop the charging system and start maintenance.

In one possible implementation, OM receives deduction information sent by the CHF; and the fee deduction information is used for informing the OM that fee deduction operation is completed. Specifically, the OM may end the service management of the corresponding service after receiving the fee deduction information.

By using the method of the embodiment of the invention, the operator can realize the active release of the user service and the corresponding charging of the used service which is not actively hung up by the user, so that the charging system can deduct the fee of the service used by all users before the work is suspended, or receive the service use request of the VIP user after the service which is used by a common user is released under the condition of overload of the system, and realize the corresponding service management of the user which does not actively finish the service, thereby avoiding the income loss of the operator, improving the user experience of the VIP user and improving the service management capability.

In order to describe the service management method in this embodiment in more detail, this embodiment will be described in detail with reference to the second application scenario and a schematic voice service management flow diagram of the voice charging system provided in fig. 6A in an overload scenario.

As shown in steps S601-S610 in fig. 6A, a voice call service is requested for the mobile terminal of the a subscriber, and if the load of the voice charging system is loaded after the mobile terminal of the a subscriber successfully accesses the voice call, the charging system cannot access a new voice service in the prior art. However, the service management method according to the embodiment of the present invention may perform the following steps:

step S611: the mobile terminal of the VIP user sends an Initial Call message to the mobile services switching center MSC requesting a Call. For example, after the VIP user dials the number on the mobile phone, the mobile phone first sends a message carrying a call request to the MSC, and requests the MSC for the call.

Step S612: the MSC sends an IDP message to the online gateway OM to initiate the call. For example, as shown in fig. 6B, fig. 6B is a work flow diagram in a scenario where the voice charging system is overloaded according to the embodiment of the present invention, and in step 2 in fig. 6B, after the MSC receives a mobile phone call request of a VIP user, although the charging system is overloaded at this time, the charging system does not directly reject the call request application of the VIP user, but the MSC sends a message for starting a call to the OM, and notifies the OM that the VIP user needs to perform a voice call.

Step S613: OM sends RRBE message to MSC to request MSC to monitor BCSM event. For example, in step 3 in fig. 6B, after receiving the message that the VIP user needs to perform the voice call, the OM sends a request to the MSC to perform the basic call state event monitoring.

Step S614: OM sends a user list request to the charging function module CHF. For example, in the case of overload of the charging system, if the charging system recognizes that there is a VIP user who needs to use the voice call service, one or more services (such as services with an excessively long call duration) may be selected from the general users who are currently using the voice call service to be actively released. OM will request a subscriber list from CHF at this time, where the service identifier of the operator that can release the service actively is recorded, and the subscriber list may include one or more service identifiers.

Step S615: and the CHF generates a user list according to a preset rule strategy. For example, the CHF may select one or more common users with too long passing time and record the service identifier thereof in the user list, so that the voice call service identifier of the common user a is recorded in the user list, thereby facilitating the subsequent active release of the services corresponding to the service identifiers.

Step S616: the CHF sends the user list to OM.

Step S617: OM sends Release Call request to MSC through TC-continue primitive to Release Call service message. For example, in step 4 in fig. 6B, at this time, the OM may send a request to release the voice call service of the general subscriber a to the MSC through the TC-continue primitive.

Step S618: the mobile services switching centre performs a Release Call. For example, in step 5 in fig. 6B, the MSC disconnects the corresponding service according to the service identifier of the user a, thereby implementing that the operator actively hangs up the voice call service of the user a.

Step S619: MSC sends application accounting report ACR to OM. For example, in step 6 in fig. 6B, after actively hanging up the voice call service of the a subscriber, the MSC may send the related information for charging, such as the call duration of the a subscriber, to the OM. Optionally, as shown in fig. 6B, in step 7 in fig. 6B, the MSC may send the monitored ERB event to the OM, which may facilitate the subsequent charging system to perform corresponding charging.

Step S620: OM generates CCR-T (A) according to the application charging report ACR. For example, OM generates a CCR-T (A) message that facilitates CHF deduction based on the ACR received. Optionally, the CCR-t (a) message may include an ERB event (e.g., an operator active hang event) sent by the MSC to the OM, which may facilitate the charging system to perform corresponding charging subsequently.

Step S621: OM sends CCA-T (A) to CHF. For example, in step 8 in fig. 6B, OM sends a CCA-t (a) message to the CFH.

Step S622: the charging function module (CHF) deducts the fee. For example, CHF deducts the call duration of the ordinary user a according to the record in CCR-t (a).

Step S623: the charging function (CHF) sends CCA-T (A) to the online gateway (OM). For example, in step 9 in fig. 6B, after the CHF finishes deducting, a CCA-t (a) message is sent to OM to notify OM that the deduction is finished, OM does not need to manage the voice call service of the user a, at this time, the active release of the voice call service of the user a is completed, and the charging system is not overloaded any more, and then the charging system can access the service of the VIP user.

Step S624: OM sends CCR-I (VIP) message to CHF requesting CHF to authenticate and budget. For example, in step 10 of fig. 6B, after releasing the a subscriber's service, OM sends a CCR-i (VIP) message to CHF carrying a cost for calculating the VIP subscriber, and then requests the CHF to authenticate and budget based on the CCR-i (VIP) message.

Step S625: CHF performs authentication and budgeting. For example, the charging function module may determine whether the VIP user has permission to make a voice call or calculate whether the VIP user has a balance to make a call according to a VIP mobile phone user account in a CCR-i (VIP) message.

Step S626: CHF sends CCA-I (VIP) to OM. For example, in step 9 of fig. 6B, after the CHF completes authentication, if the user of the mobile phone of the VIP user has the right to dial, a CCA-I message carrying that mobile phone can make a voice call is sent to OM.

Step S627: the OM sends an AC message to the MSC to request the MSC to monitor the call duration. For example, in step 12 in fig. 6B, the OM may issue a message to the MSC about a call duration and then request to monitor the voice call duration of the VIP user, so as to facilitate the subsequent charging and deduction.

Step S628: the OM sends down TC-continue request to MSC to continue calling. For example, in step 13 in fig. 6B, after sending the message requesting the MSC to monitor the duration of the voice call, the OM further sends a message of continuing the call to the MSC, so as to allow the VIP user's handset to continue the call.

Step S629: the MSC places a Connect Call to the mobile terminal of the VIP user to continue the Call. For example, in step 13 of fig. 6B, when the MSC starts to monitor the duration of the voice call of the VIP user and receives a continue call message, the MSC sends a continue call message to the mobile phone to allow the mobile phone to make the voice call. Therefore, under the condition that the charging system is overloaded, the VIP user is provided with service.

By using the method of the embodiment of the invention, the operator can realize the active release of the user service and can correspondingly charge and deduct the used service which is not actively hung up by the user, thereby receiving the service use request of the VIP user after releasing the service which is used by the common user under the condition of overload of the system, realizing the corresponding service management of the user which does not actively finish the service, and improving the user experience of the VIP user and the service management capability.

The method of the embodiments of the present invention is explained in detail above, and the related apparatus of the embodiments of the present invention is provided below.

Referring to fig. 7, fig. 7 is a schematic diagram of a first structure of a service management apparatus according to an embodiment of the present invention, where the service management apparatus 70 is applied to an online gateway OM, and may include a first receiving unit 701, a second receiving unit 702, a first sending unit 703, a third receiving unit 704, a second sending unit 705, a fourth receiving unit 706, a first processing unit 707, a third sending unit 708, and a fifth receiving unit 709, where details of each module are as follows.

A first receiving unit 701, configured to receive an active release service message, and send a user list request to a charging function module CHF;

a second receiving unit 702, configured to receive a user list of the CHF feedback; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released;

a first sending unit 703, configured to send a service release request to a mobile services switching center MSC; the service release request comprises the one or more service identifications; the service release request is used for indicating the MSC to release services corresponding to the one or more service identifiers respectively.

In one possible implementation, the apparatus further includes: the device further comprises: a third receiving unit 704, configured to receive a service request access sent by the MSC; the service request access is an application for requesting a service to be used by a user; a second sending unit 705, configured to send a preset error code to the MSC; the preset error code is used for indicating the MSC to refuse to respond to the service request access.

In one possible implementation, the apparatus further includes: a fourth receiving unit 706, configured to receive an application charging report ACR sent by the MSC; the ACR comprises service use duration corresponding to the one or more service identifications in the user list respectively; a first processing unit 707 configured to generate charging information according to the ACR; a third transmitting unit, configured to transmit the charging information to the CHF; the charging information is used for the CHF to deduct the fees of the services corresponding to the one or more service identifications respectively.

In one possible implementation, the apparatus further includes: a fifth receiving unit 709, configured to receive deduction information sent by the CHF; and the fee deduction information is used for informing the OM that fee deduction operation is completed.

In a possible implementation manner, the first sending unit 703 is specifically configured to: and sending a service release request to the MSC by continuing the dialogue service processing TC-continue primitive.

It should be noted that, for the functions of each functional unit in the service management device 70 described in the embodiment of the present invention, reference may be made to the related descriptions of step S301 to step S302, step S305, and step S308 to step S309 in the embodiment of the method described in fig. 3, and details are not repeated here.

Referring to fig. 8, fig. 8 is a schematic diagram of a second structure of a service management apparatus, where the service management apparatus 80 is applied to a charging function module CHF, and may include a first receiving unit 801, a first processing unit 802, a first sending unit 803, a second receiving unit 804, a second processing unit 805, and a second sending unit 806, where details of each module are described below.

A first receiving unit 801, configured to receive a user list request sent by an online gateway OM; the user list request is sent by the OM after receiving the active release service message;

a first processing unit 802, configured to generate a user list according to a preset rule; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released;

a first sending unit 803, configured to send the user list to the OM.

In one possible implementation, the apparatus further includes: a second receiving unit 804, configured to receive the charging information sent by the OM; the charging information comprises an ACR (application charging report); the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list.

In one possible implementation, the apparatus further includes: a second processing unit 805, configured to deduct a fee from a service corresponding to the one or more service identifiers in the user list according to the charging information.

In one possible implementation, the apparatus further includes: a second sending unit 806, configured to send fee deduction information to the OM; and the fee deduction information is used for informing the OM that fee deduction operation is completed.

It should be noted that, for the functions of each functional unit in the service management device 70 described in the embodiment of the present invention, reference may be made to the related descriptions of step S303 to step S304 and step S310 to step S311 in the embodiment of the method described in fig. 3, and details are not described here again.

Referring to fig. 9, fig. 9 is a schematic diagram of a third structure of a service management apparatus according to an embodiment of the present invention, where the service management apparatus 90 is applied to a mobile services switching center MSC, and may include a first receiving unit 901, a first processing unit 902, and a first sending unit 903, where details of each module are described below.

A first receiving unit 901, configured to receive a service release request sent by an online gateway OM; the service release request comprises one or more service identifications recorded in a user list, and each service identification corresponds to a service to be released; the service release request is sent by the OM after receiving the active release service message;

a first processing unit 902, configured to release, according to the service release request, a service corresponding to the one or more service identifiers.

In one possible implementation, the apparatus further includes: a first sending unit 903, configured to send an application charging report ACR to the OM; the ACR includes service usage durations respectively corresponding to the one or more service identifiers in the user list.

It should be noted that, for the functions of each functional unit in the service management device 70 described in the embodiment of the present invention, reference may be made to the related description of step S306 to step S307 in the embodiment of the method described in fig. 3, which is not described herein again.

An embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a program, and when the program is executed, the program includes some or all of the steps of any one of the service management methods described in the foregoing method embodiments.

Embodiments of the present invention further provide a computer program, where the computer program includes instructions, and when the computer program is executed by a computer, the computer may perform part or all of the steps of any one of the service management methods.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like, and may specifically be a processor in the computer device) to execute all or part of the steps of the above-described method of the embodiments of the present application. The storage medium may include: a U-disk, a removable hard disk, a magnetic disk, an optical disk, a Read-Only Memory (ROM) or a Random Access Memory (RAM), and the like.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A service management method is applied to an online gateway OM, and comprises the following steps:

receiving an active release service message, and sending a user list request to a charging function module CHF;

receiving a list of users for the CHF feedback; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released;

sending a service release request to a mobile service switching center (MSC); the service release request comprises the one or more service identifications; the service release request is used for instructing the MSC to release services corresponding to the one or more service identifiers respectively.

2. The method of claim 1, wherein after receiving the unsolicited release traffic message, the method further comprises:

receiving a service request access sent by the MSC; the service request access is an application for requesting a service to be used by a user;

sending a preset error code to the MSC; the preset error code is used for indicating the MSC to refuse to respond to the service request access.

3. The method according to any one of claims 1-2, further comprising:

receiving an application charging report ACR sent by the MSC; the ACR comprises service use duration corresponding to the one or more service identifications in the user list respectively;

generating charging information according to the ACR;

sending the charging information to the CHF; the charging information is used for the CHF to deduct the fees of the services corresponding to the one or more service identifications respectively.

4. The method according to any one of claims 1-3, further comprising:

receiving deduction information sent by the CHF; and the fee deduction information is used for informing the OM that fee deduction operation is completed.

5. The method of claim 1, wherein the unsolicited release service message comprises a web service webservice command sent by a Portal of a billing system; or, the active release service message includes a message of overload of the service system sent by the OM, the CHF or the Portal in the charging system.

6. The method according to claim 1, wherein said sending a service release request to a mobile services switching center, MSC, comprises: and sending a service release request to the MSC by continuing the dialogue service processing TC-continue primitive.

7. A service management method is applied to a charging function module CHF, and comprises the following steps:

receiving a user list request sent by an online gateway OM; the user list request is sent by the OM after receiving the active release service message;

generating a user list according to a preset rule; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released;

and sending the user list to the OM.

8. The method of claim 7, further comprising:

receiving charging information sent by the OM; the charging information comprises an ACR (application charging report); the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list.

9. The method according to any one of claims 7-8, further comprising:

and according to the charging information, deducting the services corresponding to the one or more service identifications in the user list respectively.

10. The method according to any one of claims 7-9, further comprising:

sending fee deduction information to the OM; the fee deduction information is used for informing the OM that fee deduction operation is completed.

11. The method according to any of claims 7-10, wherein the preset rules comprise a service identifier for recording traffic of current non-VIP users that is online for too long.

12. A service management method, applied to a mobile services switching center MSC, comprising:

receiving a service release request sent by an online gateway OM; the service release request comprises one or more service identifications recorded in a user list, and each service identification corresponds to a service to be released; the service release request is sent by the OM after receiving the active release service message;

and releasing the services corresponding to the one or more service identifications according to the service release request.

13. The method of any one of claims 12, further comprising:

sending an application charging report ACR to the OM; the ACR includes service usage durations respectively corresponding to the one or more service identifiers in the user list.

14. A service management device applied to an online gateway OM includes:

a first receiving unit, configured to receive an active release service message and send a user list request to a charging function module CHF;

a second receiving unit, configured to receive a user list of the CHF feedback; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released;

a first sending unit, configured to send a service release request to a mobile services switching center MSC; the service release request comprises the one or more service identifications; the service release request is used for instructing the MSC to release services corresponding to the one or more service identifiers respectively.

15. The apparatus of claim 14, further comprising:

a third receiving unit, configured to receive a service request access sent by the MSC; the service request access is an application for requesting a service to be used by a user;

a second sending unit, configured to send a preset error code to the MSC; the preset error code is used for indicating the MSC to refuse to respond to the service request access.

16. The apparatus of any one of claims 14-15, further comprising:

a fourth receiving unit, configured to receive an application charging report ACR sent by the MSC; the ACR comprises service use duration corresponding to the one or more service identifications in the user list respectively;

the first processing unit is used for generating charging information according to the ACR;

a third transmitting unit, configured to transmit the charging information to the CHF; the charging information is used for the CHF to deduct the fees of the services corresponding to the one or more service identifications respectively.

17. The apparatus of any one of claims 14-16, further comprising:

a fifth receiving unit, configured to receive deduction information sent by the CHF; and the fee deduction information is used for informing the OM that fee deduction operation is completed.

18. The apparatus of claim 14, further comprising:

19. The apparatus according to claim 14, wherein the first sending unit is specifically configured to:

and sending a service release request to the MSC by continuing the dialogue service processing TC-continue primitive.

20. A service management device, applied to a charging function module CHF, comprising:

the first receiving unit is used for receiving a user list request sent by an online gateway OM; the user list request is sent by the OM after receiving the active release service message;

the first processing unit is used for generating a user list according to a preset rule; the user list comprises one or more service identifications, and each service identification corresponds to a service to be released;

and the first sending unit is used for sending the user list to the OM.

21. The apparatus of claim 20, further comprising:

the second receiving unit is used for receiving the charging information sent by the OM; the charging information comprises an ACR (application charging report); the ACR includes service usage durations of services respectively corresponding to the one or more service identifiers in the user list.

22. The apparatus of any one of claims 20-21, further comprising:

and the second processing unit is used for deducting the service corresponding to the one or more service identifiers in the user list according to the charging information.

23. The apparatus of any one of claims 20-22, further comprising:

the second sending unit is used for sending fee deduction information to the OM; the fee deduction information is used for informing the OM that fee deduction operation is completed.

24. A service management apparatus, applied to a mobile services switching center MSC, comprising:

the first receiving unit is used for receiving a service release request sent by an online gateway OM; the service release request comprises one or more service identifications recorded in a user list, and each service identification corresponds to a service to be released; the service release request is sent by the OM after receiving the active release service message;

and the first processing unit is used for releasing the services corresponding to the one or more service identifications according to the service release request.

25. The apparatus of claim 24, further comprising:

a first sending unit, configured to send an application charging report ACR to the OM; the ACR includes service usage durations respectively corresponding to the one or more service identifiers in the user list.

26. An electronic device comprising a processor, a memory, and a communication interface, wherein the memory is configured to store information transmission program code, and the processor is configured to invoke the service management program code to perform the method of any of claims 1-6 or 7-11 or 12-13.

27. A system on chip, the system on chip comprising at least one processor, memory and interface circuitry, the memory, the interface circuitry and the at least one processor interconnected by wires, the at least one memory having instructions stored therein; the method of any of claims 1-6 or 7-11 or 12-13 when the instructions are executed by the processor.

28. A computer storage medium, characterized in that it stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 1-6 or 7-11 or 12-13.

29. A computer program, characterized in that the computer program comprises instructions which, when executed by a computer, cause the computer to carry out the method according to any one of claims 1-6 or 7-11 or 12-13.