CN100355247C - Interrupt indication method of package area intelligent service - Google Patents

Abstract

The invention discloses a method for prompting interruption of packet domain intelligent services. In the packet domain service management process, when a service control node (SCP) determines that service access fails according to a service request triggered by a general packet radio service node (GSN), the The method includes: A. The SCP determines the cause of the service access failure, and determines different GSN cause values according to different access failure reasons; B. The SCP sends the determined GSN cause value to the GSN, and the GSN receives the different The GSN cause value is converted into a different mobile terminal MS cause value and sent to the MS; C. The MS determines and displays different interrupt prompt information indicating the cause of the service access failure according to the received different MS cause values. By adopting the method of the invention, clear interruption prompt information can be realized, which is convenient for users to use services and improves overall service quality.

Description

A method for prompting interruption of intelligent service in packet domain

technical field

The invention relates to an interruption prompting technology in an intelligent service, in particular to an interruption prompting method for an intelligent service in a packet domain.

Background technique

At present, intelligent services have been applied to the voice services of the public switched telephone network (PSTN) and the global system for mobile communications (GSM), and its perfect voice prompt function has brought great convenience to users. With the development of General Packet Radio Service (GPRS) and Universal Mobile Telecommunications System (UMTS), operators will consider using intelligent services in the packet domain services of GPRS/UMTS in order to facilitate the use of users and attract consumer groups of all levels. That is: GPRS/UMTS mobile intelligent network is established on the basis of GPRS/UMTS network to provide intelligent packet domain services.

The intelligent network that provides intelligent services is an additional network set up on the basis of the original communication network, mainly including: Service Switching Point (SSP) and Service Control Point (SCP). Among them, the SCP is the core part of the intelligent network, which has the functions of managing user data, network data, and service control; the SSP has the function of call control, and the user triggers a service request to the SCP through the SSP to start the intelligent service, and the prompt information of the SCP is passed through the SSP Send it to the user.

In the GPRS/UMTS mobile intelligent network, the function of the SSP is realized by a GPRS node (GSN). The GSN may be a GPRS Support Node (SGSN), and the SGSN is called SGSN/gprsSSP; the GSN may also be a GPRS Gateway Node (GGSN), and the GGSN is called GGSN/gprsSSP. The SCP interacts with the SGSN/gprsSSP or GGSN/gprsSSP on the application part protocol (CAP, CAMELApplication Part) signaling of the customized application protocol of the enhanced logic of the mobile network to realize the management process of the packet domain service and execute the intelligent service. The SGSN/gprsSSP or GGSN/gprsSSP provides the triggering of the intelligent service, accepts the control of the SCP, and sends the prompt information from the SCP to the mobile terminal (MS) and the like. To simplify the description, the SGSN mentioned below refers to SGSN/gprsSSP, and the GGSN refers to GGSN/gprsSSP.

Wherein, the management process of the PS domain service includes: a mobility management process and a session management process. When the SGSN implements the SSP function, the mobility management process and the session management process are jointly completed by the SGSN and the SCP. When the GGSN implements the SSP function, the session management process is completed by the GGSN. The mobility management process mainly includes: user attachment/detachment, periodic routing area update, and the like. The session management process mainly includes: MS-initiated Packet Data Protocol (PDP) context activation, MS-initiated PDP context deactivation, packet-domain MS-initiated call, packet-domain MS-initiated call release, and the like. When the user balance is insufficient, routing update is not allowed, external network access point name (APN) is not allowed, quality of service (QoS) is not allowed, network resources are insufficient, or the service fails, the SCP cannot access the current service request and the service is interrupted. , thereby causing processes such as user attachment failure or user detachment in mobility management, or processes such as PDP context activation failure or deactivation of user-side PDP context in session management.

However, the interruption prompt information provided by the GPRS/UMTS intelligent service is not clear enough at present. Taking the session management process as an example, the reasons for the current service access failure include: insufficient user balance, disallowed routing update, disallowed APN, disallowed QoS, insufficient network resources, and service failure. However, no matter what causes the service access failure, the SCP sends the same GSN cause value to the GSN that triggers the service request, so the interruption prompt information sent by the GSN to the MS is also the same. For example: no matter the reason for the current access failure is insufficient balance or the APN does not allow it, the interruption prompt message received by the MS is "Service Option Not Supported". Here, the GSN cause value may be an SGSN cause value or a GGSN cause value. When the GSN is a GGSN, the SCP usually sends the GGSN cause value to the GGSN through the Gn interface according to the Gn interface message format, and when the GSN is an SGSN , the SCP usually sends the SGSN cause value to the SGSN through the Ge interface according to the Ge interface message format.

Therefore, the user cannot know the real cause of the interruption according to the above interruption prompt information, and cannot take effective measures to solve the current service interruption problem, and may also waste a large amount of system resources. For example, if the original reason for interruption is that the APN is not allowed, the user can no longer use the same APN to access the network, but since the user can only see an ambiguous interruption message like "Service Option Not Supported", it is very likely Continue to use the same APN to retry sending invalid service requests. In this way, for the entire system, if a large number of users retry such wireless service requests, a lot of system resources will be wasted and the overall service quality will be reduced.

To sum up, the existing GPRS/UMTS smart services cannot provide users with humanized services in terms of interruption prompts, and do not give full play to the advantages of the intelligent service prompt function to provide users with effective interruption prompt information, which may cause a large number of network failures. Waste of resources.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a packet-domain smart service interruption prompt method, which can clearly indicate the reason for the current service access failure for the user, thereby effectively prompting the user to take measures to solve the service interruption problem.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for prompting interruption of a packet domain intelligent service. In the packet domain service management process, when the SCP determines that the service access fails according to the service request triggered by the GSN, the method includes:

A. The SCP determines the cause of the service access failure, and determines different GSN cause values according to different reasons for the access failure;

B. The SCP sends the GSN cause value determined in step A to the GSN, and the GSN converts the received different GSN cause values into different mobile terminal MS cause values and sends them to the MS;

C. The MS in step B determines and displays different interrupt prompt information indicating the cause of service access failure according to the received different MS cause values.

Wherein, the GSN is the SGSN; the GSN cause value is the SGSN cause value.

Wherein, the GSN includes GGSN and SGSN, the GGSN triggers the service request, and the SGSN sends the MS cause value to the MS; the GSN cause value is the SGSN cause value; the step B includes: The SGSN cause value determined in step A is sent to the GGSN that triggers the service request, and the GGSN transparently transmits the received SGSN cause value to the SGSN, and the SGSN converts the received different SGSN cause values into different MS The cause value is sent to the MS.

Wherein, in step A, the SCP determines the SGSN cause value according to the correspondence between the pre-configured access failure cause and the SGSN cause value; in step B, the SGSN determines the SGSN cause value according to the pre-configured correspondence between the SGSN cause value and the MS cause value Converting the MS cause value; in step C, the MS determines the interruption prompt information according to the correspondence between the pre-configured MS cause value and the interruption prompt information.

Wherein, the GSN includes general packet radio service gateway nodes GGSN and SGSN, the GGSN triggers the service request, and the SGSN sends the MS cause value to the MS; in step A, the determined GSN cause value is GGSN Cause value; in step B, the GSN cause value that is converted into the MS cause value is the SGSN cause value;

Described step B comprises:

B1.SCP sends the GGSN cause value determined in step A to the GGSN that triggers the service request, and the GGSN converts the received different GGSN cause values into different SGSN cause values and sends them to the SGSN;

B2. The SGSN converts the different SGSN cause values received in step B1 into different MS cause values and sends them to the MS.

In step A, the SCP determines the GGSN cause value according to the correspondence between the pre-configured access failure reason and the GGSN cause value; in step B1, the GGSN sends the received The received GGSN cause value is converted into an SGSN cause value; in step B2, the SGSN converts the received SGSN cause value into an MS cause value according to the corresponding relationship between the pre-configured SGSN cause value and the MS cause value; in step C, the MS The interruption prompt information is determined according to the correspondence between the pre-configured MS cause value and the interruption prompt information.

In step A, the SCP queries the user database connected to itself according to the service information in the current service request to determine the reason for the access failure.

In step A, the SCP determines the reason for the access failure according to the service information in the current service request.

Wherein, the packet domain service management process is a session management process; the reasons for the access failure include: insufficient balance, or disallowed routing update, or APN disallowed, or QoS disallowed, or insufficient network resources, or service failure , or any combination of these six.

Wherein, the packet domain service management process is a mobility management process; the reasons for the access failure include: insufficient balance, or disallowed routing update, or insufficient network resources, or service failure, or any combination of these four.

As can be seen from the above scheme, the key of the present invention is: the SCP determines different GSN cause values according to different service access failure reasons and sends them to the GSN, and the GSN converts the received different GSN cause values into different MS The cause value is sent to the MS, and finally the MS determines and displays the interruption prompt information indicating different reasons for the access failure according to the received different MS cause values.

Therefore, the interrupt notification method for packet domain intelligent services provided by the present invention can provide users with specific and clear interruption prompt information according to the reasons for the current service access failure, so that users can take effective measures to solve the interruption problem, and ensure that subsequent initiated Services can be successfully accessed, thereby effectively utilizing system resources and improving service quality as a whole.

Description of drawings

Fig. 1 is a schematic diagram of the processing flow of a preferred embodiment of the method of the present invention.

Detailed ways

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

The interruption prompting method of the packet domain intelligent service provided by the present invention is applied to the management process of the packet domain intelligent service, including: a session management process and a mobility management process. In each packet domain intelligent service management process, the main processing idea is: when the SCP judges that the service access fails according to the current service request, it determines different cause values for different reasons for the access failure; then, the SCP uses the determined cause The value is sent to the GSN, and the GSN converts the received different cause values into different MS cause values and sends them to the MS; finally, the MS displays different interruption prompt information according to the received different cause values. The information can indicate different reasons for service access failure.

According to the description of the background technology, in the GPRS/UMTS mobile intelligent network, when the SGSN serves as the SSP, the SGSN triggers the service request to the SCP, and when the GGSN serves as the SSP, the GGSN triggers the service request to the SCP. The method of the present invention will be described in detail below by taking the session management process when the SGSN acts as the SSP to trigger a service request to the SCP as an example.

Fig. 1 is a schematic diagram of the processing flow of a preferred embodiment of the method of the present invention. As shown in Figure 1, specific processing includes:

Step 101: The SCP receives a service request from the SGSN, which can be: GPRS monitoring point initialization (Initial DP GPRS), or GPRS event report (Event Report GPRS), or GPRS charging request report (Apply Charging Report GPRS), etc. information.

Step 102: The SCP judges whether the current service access fails according to the service request received in step 101, and if so, executes step 103; otherwise, ends the current processing and enters the normal business logic processing flow of the smart service.

Wherein, the SCP can query the user database connected to itself according to the service information in the service request to obtain the usage of the current service, so as to judge whether the access of the current service fails. When the service request is an Initial DP GPRS message, according to the user identification in the message such as International Mobile Station Subscriber Identity (IMSI)/Mobile Station Integrated Services Digital Network Identification (MSISDN), query the user database to obtain the user's current service Usage status, including: current balance, user level, location attribute, APN attribute, QoS attribute and other information, so as to know whether the user has insufficient balance, or whether the routing update is not allowed, or whether the APN is not allowed, or whether the QoS is not allowed, if the user If the balance is insufficient, or the routing update is not allowed, or the APN is not allowed, or the QoS is not allowed, it is judged that the current service access fails. When the service request is an Event Report GPRS message, according to the IMSI/MSISDN in the message, query the user database to obtain the current service usage of the user, including: location attributes, APN attributes, QoS attributes and other information, so as to know whether the user is If the route update is not allowed, or whether the APN is not allowed, or whether the QoS is not allowed, if the user's route update is not allowed, or the APN is not allowed, or the QoS is not allowed, it is judged that the current service access fails. When the service request is an Apply Charging Report GPRS message, query the user database according to the reference number (ReferenceNumber) in the message to obtain the current service usage of the user, including: current balance, rate and other information, and according to the information in the message The carried user’s service duration/traffic, etc. can be calculated to determine whether the user’s balance is insufficient. If the user’s balance is insufficient, it is judged that the current service access fails.

In addition, when the SCP receives a service request, if the current network resources are insufficient, or the SCP learns that the service corresponding to the service information fails according to the service information in the service request, the SCP will directly judge that the current service access fails without further judgment Whether the balance of the user is insufficient, or whether the routing update is not allowed, or whether the APN is not allowed, or whether the QoS is not allowed.

Step 103: The SCP analyzes the cause of the service access failure in step 102, and determines the SGSN cause value according to the cause of the access failure.

Wherein, each service request corresponds to an access failure reason, and for multiple service requests, their respective access failure reasons may be the same or different. Here, when determining the SGSN cause value according to the access failure cause, for the service requests with different access failure causes, different SGSN cause values will be determined according to different access failure causes. Here, the SCP can pre-configure the correspondence between the reasons for the access failure and the value of the SGSN cause, so that the corresponding different SGSN cause values can be determined according to different reasons for the access failure.

For example: if the reason for the access failure is insufficient balance, then determine that the SGSN cause value is 0; if the reason for the access failure is that the routing update is not allowed, then determine the SGSN cause value as 1; if the reason for the access failure is that the APN is not allowed, then determine The SGSN reason value is 2; if the reason for the access failure is that QoS is not allowed, then determine the SGSN cause value as 3; if the reason for the access failure is insufficient network resources, determine the SGSN cause value as 4; if the reason for the access failure is service failure , it is determined that the SGSN cause value is 5. The present invention does not limit the specific value of the determined SGSN cause value when determining the SGSN cause value according to the access failure cause.

Step 104: The SCP includes the SGSN cause value determined in step 103 in the response message to the SGSN and sends it to the SGSN.

Step 105: The SGSN parses the response message in step 104 to obtain the SGSN cause value indicating the cause of the access failure, and converts the SGSN cause value into an MS cause value.

Wherein, each service request response message corresponds to one SGSN cause value, and for multiple service request response messages, their respective SGSN cause values may be the same or different. Here, when converting the SGSN cause value into the MS cause value, for the response message of the service request with different SGSN cause values, each different SGSN cause value will be converted into a different MS cause value. Here, the SGSN can pre-configure the corresponding relationship between the SGSN cause value and the MS cause value, so that different corresponding MS cause values can be determined according to different SGSN cause values.

For example: if the SGSN cause value is 0 indicating that the balance is insufficient, then determine the MS cause value is 130; if the SGSN cause value is 1 indicating that the routing update is not allowed, then determine the MS cause value is 131; If 2 is allowed, the MS cause value is determined to be 132; if the SGSN cause value is 3 indicating that QoS is not allowed, then the MS cause value is determined to be 133; if the SGSN cause value is 4 indicating insufficient network resources, then the MS cause value is determined to be 134; if the SGSN cause value is 5 indicating a service failure, determine that the MS cause value is 135. The present invention does not limit the specific value of the converted MS cause value when the SGSN cause value is converted into the MS cause value.

Step 106: The SGSN includes the MS cause value converted in step 105 in the response message to the MS and sends it to the MS.

Step 107: The MS receives the response message in step 106, parses the response message to obtain a cause value indicating access failure, determines interruption prompt information according to the cause value, and displays it to the user.

Wherein, each response message received by the MS corresponds to an MS cause value, and for multiple response messages, their respective MS cause values may be the same or different. Here, when the interruption prompt information is determined according to the MS cause value, for the response messages with different MS cause values, the MS will determine different interruption prompt information according to different MS cause values, so the user can use different interruption prompt information Distinguish between different access failure reasons. Here, the MS can pre-configure the corresponding relationship between the MS cause value and the interruption prompt information, so that different corresponding interruption prompt information can be determined according to different MS cause values.

For example: if the MS cause value is 130 indicating that the balance is insufficient, then it is determined that the interruption prompt information is "insufficient balance"; if the MS cause value is 131 indicating that the routing update is not allowed, then it is determined that the interruption prompt information is "roaming is not allowed"; if If the MS cause value is 132 indicating that the APN is not allowed, then it is determined that the interrupt prompt information is "APN error"; if the MS cause value is 133 indicating that the QoS is not allowed, then it is determined that the interrupt prompt information is "QoS does not support"; if the MS cause value For 134 indicating insufficient network resources, determine the interruption prompt information as "network busy"; if the MS cause value is 135 indicating service failure, then determine the interruption prompt information as "service failure". The present invention does not limit the specific content of the interrupt prompt information determined when the interrupt prompt information is determined according to the MS cause value.

In the above embodiment, when the SCP and the SGSN respectively include the determined SGSN cause value and the MS cause value in their respective corresponding response messages for delivery, the values of the SGSN cause value and the MS cause value may be specified in the protocol. Any numerical value in the reason value reserved value field in the above-mentioned response message may also be other numerical values not specified in the protocol, which is not limited in the present invention.

The above is the process of the present invention applied to the session management process of SGSN as SSP, the reasons for the service access failure determined by the SCP may include: insufficient balance, or disallowed routing update, or disallowed APN, or disallowed QoS, Or insufficient network resources, or service failure, or any combination of these six. When the present invention is applied to the SGSN as the mobility management flow of the SSP, the processing process is basically the same as the above processing, the difference is that the reasons for the service access failure determined by the SCP may include: insufficient balance, or disallowed routing update, or Insufficient network resources, or service failure, or any combination of these four. And, because the access failure cause determined in the mobility management procedure is different from the access failure cause determined in the session management procedure, the subsequent SCP determines the SGSN cause value according to the access failure cause, and the SGSN assigns the SGSN There are also slight differences in the process of converting the cause value into the MS cause value and the MS determining the interrupt prompt information according to the MS cause value, but the difference is only in the specific value and quantity of the SGSN cause value, the MS cause value, and the interrupt prompt information. Therefore, it will not be described in detail here.

When the GGSN triggers a service request to the SCP as an SSP, the GGSN and the SCP will participate in the session management process. The processing of the method of the present invention applied to the session management flow of the GGSN as the SSP is basically the same as the above-mentioned processing of the session management flow of the SGSN as the SSP, and the reasons for the failure of the service access may also include: insufficient balance, or insufficient routing update Allowed, or not allowed by APN, or not allowed by QoS, or insufficient network resources, or service failure, or any combination of these six. The difference lies in the process from when the SCP determines the cause of the service access failure to when the SGSN receives the response message containing the SGSN cause value. The present invention proposes two processing mechanisms for the process from when the SCP determines the cause of the service access failure to when the SGSN receives the message containing the SGSN cause value: 1. The SCP determines the cause of the service access failure according to the different SGSN cause value, and send the SGSN cause value in the response message to GGSN to GGSN, GGSN does not do any processing on the received SGSN cause value, and sends the SGSN cause value in the response message to SGSN to SGSN; 2. The SCP includes the GGSN cause value in the response message to the GGSN and sends it to the GGSN according to the different GGSN cause values determined by different reasons for the service access failure, and the GGSN will receive the different GGSN cause values It is converted into a different SGSN cause value, and the SGSN cause value is included in the response message to the SGSN and sent to the SGSN.

Since the value of the SGSN cause value determined by the SCP may be the same as that of some GGSN cause values, if the above-mentioned first processing mechanism is adopted, when the GGSN receives the SGSN cause value determined by the SCP, the SGSN cause value may be regarded as Make the GGSN cause value, and convert the SGSN cause value into other SGSN cause values according to the rules for converting the GGSN cause value to the SGSN cause value, thus causing errors in the subsequent processing flow. Therefore, the second processing mechanism takes into account the possible problems of the first processing mechanism, the SCP determines the GGSN cause value, and then the GGSN converts the GGSN cause value into an SGSN cause value and sends it to the SGSN, thereby ensuring that the SGSN No error handling will be done on received cause values.

Wherein, the processing principle of the SCP determining different GGSN cause values according to different service access failure reasons is the same as the processing principle of the SCP determining different SGSN cause values according to different service access failure reasons, and will not be described here The processing principle that the GGSN converts different GGSN cause values into different SGSN cause values is the same as the processing principle that the SGSN described in Figure 1 converts different SGSN cause values into different MS cause values, so it is no longer describe.

To sum up, by applying the method of the present invention, when the access service request fails, the SCP sends the SGSN cause values indicating different reasons for the access failure to the SGSN directly, or indirectly through the GGSN to the SGSN, and the SGSN then sends the received Different cause values are converted into different MS cause values, so that the MS can display interruption prompt information indicating different access failure reasons according to different MS cause values. In this way, when the service access fails, the user can clearly understand the real reason for the access failure, such as: insufficient balance, APN does not allow, etc., and will not continue to repeatedly initiate service requests when the balance is insufficient, or continue to use the original The wrong APN resends the service request, which avoids the unnecessary waste of system resources caused by these repeated invalid service requests. In addition, after the user gets the clear interruption prompt information described in the present invention, he can recharge in time, or change the APN, or modify the QoS, etc., so that the subsequent services initiated by the user can basically be successfully accessed, and the user can also use GPRS/UMTS smart Business has brought great convenience.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention are included within the scope of the present invention.

Claims (10)

1. A method for prompting interruption of packet domain intelligent services, characterized in that, in the packet domain service management process, when the service control node SCP determines that the service access fails according to the service request triggered by the general packet radio service node GSN, the method includes : A. The SCP determines the cause of the service access failure, and determines different GSN cause values according to different reasons for the access failure; B. The SCP sends the GSN cause value determined in step A to the GSN, and the GSN converts the received different GSN cause values into different mobile terminal MS cause values and sends them to the MS; C. The MS in step B determines and displays different interrupt prompt information indicating the cause of service access failure according to the received different MS cause values. 2. The method according to claim 1, wherein the GSN is a General Packet Radio Service Support Node (SGSN); the GSN cause value is an SGSN cause value. 3. The method according to claim 1, wherein the GSN includes general packet radio service gateway nodes GGSN and SGSN, the GGSN among them triggers the service request, and the SGSN among them sends the MS cause value to the MS The GSN cause value is an SGSN cause value; the step B includes: the SCP sends the SGSN cause value determined in step A to the GGSN that triggers the service request, and the GGSN transparently transmits the received SGSN cause value to the The SGSN converts the received different SGSN cause values into different MS cause values and sends them to the MS. 4. A method according to claim 2 or 3, characterized in that In step A, the SCP determines the SGSN cause value according to the correspondence between the pre-configured access failure reason and the SGSN cause value; In step B, the SGSN converts the MS cause value according to the pre-configured correspondence between the SGSN cause value and the MS cause value; In step C, the MS determines the interruption prompt information according to the correspondence between the pre-configured MS cause value and the interruption prompt information. 5. The method according to claim 1, wherein the GSN includes general packet radio service gateway nodes GGSN and SGSN, the GGSN among them triggers the service request, and the SGSN among them sends the MS cause value to the MS ; In step A, the determined GSN cause value is a GGSN cause value; In step B, the GSN cause value converted into the MS cause value is an SGSN cause value; Described step B comprises: B1.SCP sends the GGSN cause value determined in step A to the GGSN that triggers the service request, and the GGSN converts the received different GGSN cause values into different SGSN cause values and sends them to the SGSN; B2. The SGSN converts the different SGSN cause values received in step B1 into different MS cause values and sends them to the MS. 6. The method of claim 5, wherein: In step A, the SCP determines the GGSN cause value according to the correspondence between the pre-configured access failure cause and the GGSN cause value; In step B1, the GGSN converts the received GGSN cause value into an SGSN cause value according to the pre-configured correspondence between the GGSN cause value and the SGSN cause value; In step B2, the SGSN converts the received SGSN cause value into an MS cause value according to the pre-configured correspondence between the SGSN cause value and the MS cause value; In step C, the MS determines the interruption prompt information according to the correspondence between the pre-configured MS cause value and the interruption prompt information. 7. The method according to claim 1, 2, 3, 5 or 6, characterized in that in step A, the SCP queries the user database connected to itself according to the service information in the current service request to determine that the access fails s reason. 8. The method according to claim 1, 2, 3, 5 or 6, wherein in step A, the SCP determines the reason for the access failure according to the service information in the current service request. 9. The method according to claim 1, 2, 3, 5 or 6, wherein the packet domain service management process is a session management process; The reasons for the access failure include: insufficient balance, or disallowed routing update, or disallowed external network access point name APN, or disallowed quality of service QoS, or insufficient network resources, or business failure, or any of these six combination. 10. The method according to claim 1, 2, 3, 5 or 6, wherein the packet domain service management process is a mobility management process; The reasons for the access failure include: insufficient balance, or disallowed routing update, or insufficient network resources, or service failure, or any combination of these four.

Images