CN100355247C - Interrupt indication method of package area intelligent service - Google Patents
Interrupt indication method of package area intelligent service Download PDFInfo
- Publication number
- CN100355247C CN100355247C CNB2005100555839A CN200510055583A CN100355247C CN 100355247 C CN100355247 C CN 100355247C CN B2005100555839 A CNB2005100555839 A CN B2005100555839A CN 200510055583 A CN200510055583 A CN 200510055583A CN 100355247 C CN100355247 C CN 100355247C
- Authority
- CN
- China
- Prior art keywords
- cause value
- sgsn
- ggsn
- gsn
- different
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
The present invention discloses an interrupt indication method of intelligent services of a packet switched domain. In the process of the packet domain service management, when the service control point (SCP) confirms the failure of service access according to a service request triggered by a general packet wireless service node (GSN), the method comprises: A. the SCP determines the reason of the failure of service access, and determines different GSN reason values according to different reason of the failure of service access; B. the SCP sends the determined GSN reason values to a GSN, the GSN converts the received different GSN reason values into different mobile terminal MS reason values and sends the mobile terminal MS reason values to MSs; C. the MSs determine and display different interruption indication information indicating the reason of the failure of service access according to the received different MS reason values. When the method of the present invention is used, specific interruption indication information can be realized, users can use the service conveniently, and the whole service quality can be improved.
Description
Technical field
The present invention relates to the interruption prompting technology in the IN service, particularly the interruption reminding method of package area intelligent service.
Background technology
At present, used IN service in the voice service of Public Switched Telephone Network and global system for mobile communications (GSM), its perfect sound prompt function brings great convenience to the user.Development along with GPRS (GPRS) and universal mobile telecommunications system (UMTS), use, attract the various levels of consumer group for the convenience of the user, operator will consider to use IN service in the packet switch domain service of GPRS/UMTS, that is: set up the GPRS/UMTS mobile intelligent net on the basis of GPRS/UMTS network intelligentized packet switch domain service is provided.
The intelligent network that IN service is provided is a kind of complementary network that is provided with on the basis of original communication network, mainly comprises: Service Switching Point and Service Control Point.Wherein, SCP is the core of intelligent network, and it has leading subscriber data, network data and service control function; SSP has CCF, and the user triggers service request by SSP and starts IN service to SCP, and the information of SCP then is handed down to the user by SSP.
In the GPRS/UMTS mobile intelligent net, the function of described SSP is realized by GPRS node (GSN).Described GSN can be GPRS Support Node (SGSN), and this SGSN is called as SGSN/gprsSSP; Described GSN also can be GPRS gateway node (GGSN), and this GGSN is called as GGSN/gprsSSP.The mutual mobile network of described SCP and SGSN/gprsSSP or GGSN/gprsSSP strengthens applying portion agreement (CAP, the CAMELApplication Part) signaling of the customization application protocol of logic, realizes the management process of packet switch domain service, and carries out IN service.Described SGSN/gprsSSP or GGSN/gprsSSP provide the triggering of IN service, accept the control of SCP, will be handed down to portable terminal (MS) etc. from the information of SCP.Be simplified illustration, the following stated SGSN all refers to SGSN/gprsSSP, and described GGSN all refers to GGSN/gprsSSP.
Wherein, the management process of described packet switch domain service comprises: mobile management flow process and session management flow process.When SGSN realized the SSP function, described mobile management flow process and session management flow process were finished jointly by SGSN and SCP.When GGSN realized the SSP function, described session management flow process was finished by GGSN.Described mobile management flow process mainly comprises: the user adheres to/separates, Routing Area Update etc. periodically.Described session management flow process mainly comprises: PDP Context deactivation, the packet domain MS that packet data protocol (PDP) context activation that MS initiates, MS initiate makes a call, packet domain MS makes a call release etc.When user balance deficiency, routing update do not allow, external network Access Point Name (APN) does not allow, service quality (QoS) does not allow, when Internet resources deficiency or business break down, SCP can't insert the current business request, service disconnection takes place, thereby the user in the initiation mobile management adheres to failure or flow process such as separate users, perhaps causes flow processs such as PDP context activation failure in the session management or deactivation user side PDP Context.
But the interruption information that present GPRS/UMTS IN service is provided is clear and definite inadequately.With the session management flow process is example, and the reason that causes the current business access failure comprises: user balance deficiency, routing update do not allow, APN does not allow, QoS does not allow, Internet resources deficiency and business break down etc.But the reason that no matter causes the service access failure is any, and SCP is same GSN cause value to the GSN transmission that triggers service request, thereby the interruption information that this GSN issues to MS also is identical.Such as: Sorry, your ticket has not enough value no matter current access failure is former or APN does not allow, and the interruption information that MS receives is " business is not supported (Service Option NotSupported) ".Here, described GSN cause value can be SGSN cause value or GGSN cause value, when described GSN is GGSN, SCP presses the gn interface message format usually and sends the GGSN cause value to described GGSN by gn interface, and described GSN is when being SGSN, and SCP presses Ge interface message form usually and sends the SGSN cause value to described SGSN by the Ge interface.
Therefore, the user can't be known the true cause that causes interruption according to above-mentioned interruption information, also just can not adopt an effective measure to solve the problem of service interruption of current appearance, and may waste a large amount of system resources.Such as: the original reason that causes interruption is that APN does not allow, then the user can not re-use same APN access network, but because the user only can see similar " Service Option Not Supported " indefinite like this interruption information, then might continue very much to use same APN retry to send invalid service request, like this, for whole system, if this type of wireless service request of a large number of users retry is arranged, will waste a large amount of system resources, whole quality of service is descended.
In sum, existing GPRS/UMTS IN service is aspect the interruption prompting, the service of hommization can't be provided for the user, and the advantage of not giving full play to the IN service prompt facility provides effective interruption information for the user, thereby may cause a large amount of network resources waste.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of interruption reminding method of package area intelligent service, can clearly indicate the reason of current business access failure for the user, thereby effectively point out the user to take measures to solve problem of service interruption.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of interruption reminding method of package area intelligent service, in the packet switch domain service management process, SCP according to the GSN business of triggering request determine service access when failure, this method comprises:
A.SCP determines the reason of service access failure, determines different GSN cause values according to different access failure reasons;
B.SCP sends to GSN with the determined GSN cause value of steps A, and the different GSN cause value that described GSN will receive is converted into different mobile terminal MS cause values and is handed down to MS;
C. the described MS of step B determines and shows the interruption information of different indicating services access failure reasons according to the different MS cause value that receives.
Wherein, described GSN is SGSN; Described GSN cause value is the SGSN cause value.
Wherein, described GSN comprises GGSN and SGSN, triggers described service request by wherein GGSN, issues the MS cause value by wherein SGSN to MS; Described GSN cause value is the SGSN cause value; Described step B comprises: SCP sends to the determined SGSN cause value of steps A the GGSN of described triggering service request, to described SGSN, the different SGSN cause value that this SGSN will receive is converted into different MS cause values and is handed down to MS this GGSN with the SGSN cause value transparent transmission that receives.
Wherein, in the steps A, SCP determines the SGSN cause value according to pre-configured access failure reason and the corresponding relation between the SGSN cause value; Among the step B, SGSN is according to pre-configured SGSN cause value and the conversion of the corresponding relation between MS cause value MS cause value; Among the step C, MS determines to interrupt information according to the corresponding relation between pre-configured MS cause value and the interruption information.
Wherein, described GSN comprises GPRS gateway node GGSN and SGSN, triggers described service request by wherein GGSN, issues the MS cause value by wherein SGSN to MS; In the steps A, determined GSN cause value is the GGSN cause value; Among the step B, the GSN cause value of the described MS of being converted into cause value is the SGSN cause value;
Described step B comprises:
B1.SCP sends to the GGSN of described triggering service request with the determined GGSN cause value of steps A, and the different GGSN cause value that this GGSN will receive is converted into different SGSN cause values and is handed down to described SGSN;
B2. described SGSN is converted to the different SGSN cause values that receive among the step B1 different MS cause values and is handed down to MS.
In the steps A, SCP determines the GGSN cause value according to pre-configured access failure reason and the corresponding relation between the GGSN cause value; Among the step B1, GGSN is converted to the SGSN cause value according to pre-configured GGSN cause value and the corresponding relation between the SGSN cause value with the GGSN cause value that receives; Among the step B2, SGSN is converted to the MS cause value according to pre-configured SGSN cause value and the corresponding relation between the MS cause value with the SGSN cause value that receives; Among the step C, MS determines to interrupt information according to the corresponding relation between pre-configured MS cause value and the interruption information.
In the steps A, the described SCP customer data base that inquiry connects self according to the business information in the current business request is determined the reason of described access failure.
In the steps A, described SCP determines the reason of described access failure according to the business information in the current business request.
Wherein, described packet switch domain service management process is the session management flow process; The reason of described access failure comprises: Sorry, your ticket has not enough value or routing update does not allow or APN does not allow or QoS does not allow or Internet resources deficiency or traffic failure or this combination in any.
Wherein, described packet switch domain service management process is the mobile management flow process; The reason of described access failure comprises: Sorry, your ticket has not enough value or routing update does not allow or Internet resources deficiency or traffic failure or this combination in any.
By such scheme as can be seen, key of the present invention is: SCP determines different GSN cause values and is handed down to GSN according to different service access failure causes, the different GSN cause value that GSN will receive again is converted to different MS cause values and is handed down to MS, and last MS determines that according to the different MS cause value that receives the interruption information of the different access failure reasons of indication shows.
Therefore, the interruption reminding method of package area intelligent service provided by the present invention, can be according to the reason of current business access failure, for the user provides concrete, clear and definite interruption information, be convenient to user's solution disruption of adopting an effective measure, the business that guarantees follow-up initiation can successfully insert, thereby has effectively utilized system resource, improves quality of service on the whole.
Description of drawings
Fig. 1 is the inventive method one preferred embodiment handling process schematic diagram.
Embodiment
The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
The interruption reminding method of package area intelligent service provided by the present invention is applied to the package area intelligent service management process, comprising: session management flow process and mobile management flow process.In each package area intelligent service management process, it is mainly handled thought and is: when SCP judges the service access failure according to the current business request, determine different cause values at different access failure reasons; Then, SCP sends to GSN with determined cause value, and the cause value that the different cause values that GSN will receive again are converted into different MS is handed down to MS; At last, MS shows different interruption informations according to the different cause values that receive, and this different interruption information can be indicated different service access failure causes.
As can be known according to background technology, in the GPRS/UMTS mobile intelligent net, SGSN is toggled to SCP by SGSN with service request during as SSP, and GGSN then is toggled to SCP by GGSN with service request during as SSP.Session management flow process when triggering service request to SCP with SGSN as SSP below is an example, and the inventive method is described in detail.
Fig. 1 is the inventive method one preferred embodiment handling process schematic diagram.As shown in Figure 1, the concrete processing comprises:
Step 101:SCP receives the service request from SGSN, and this service request can be GPRS control point initialization (Initial DP GPRS) or GPRS event report (Event Report GPRS) or the GPRS request report message such as (Apply Charging Report GPRS) of chargeing.
Step 102:SCP judges whether the current business access failure according to the service request that receives in the step 101, if, execution in step 103; Otherwise finish to work as pre-treatment, enter the regular traffic logical process flow process of IN service.
Wherein, SCP can obtain the operating position of current business according to the customer data base that the inquiry of the business information in the described service request connects self, thereby judges whether the current business access failure.When service request is Initial DP GPRS message, according to the user ID in this message such as international user of mobile station identification code (IMSI)/travelling carriage integrated services digital network sign (MSISDN), inquire about described customer data base and obtain the current professional operating position of this user, comprise: current remaining sum, user class, position attribution, the APN attribute, information such as QoS attribute, thereby as can be known the user whether Sorry, your ticket has not enough value, or routing update does not allow, or APN does not allow, or QoS does not allow, if user balance deficiency, or routing update does not allow, or APN does not allow, or QoS do not allow, and then judges the current business access failure.When service request is Event Report GPRS message, according to the IMSI/MSISDN in this message, inquire about described customer data base and obtain the current professional operating position of this user, comprise: information such as position attribution, APN attribute, QoS attribute, thereby as can be known the user whether routing update do not allow or APN does not allow or QoS does not allow, if user's routing update does not allow or APN does not allow or QoS does not allow, then judge the current business access failure.When service request is Apply Charging Report GPRS message, obtain the current professional operating position of this user according to the described customer data base of the reference number in this message (ReferenceNumber) inquiry, comprise: information such as current remaining sum, rate, and use professional duration/flow etc. according to the user who carries in this message, whether Sorry, your ticket has not enough value can to determine the user by calculating, if the user balance deficiency is then judged the current business access failure.
In addition, when SCP receives service request, if current network resources deficiency or SCP learn that according to the business information in the service request this business information corresponding service breaks down, then SCP will directly judge the current business access failure, and needn't judge the user more whether Sorry, your ticket has not enough value or routing update does not allow or APN does not allow or QoS does not allow.
The reason of service access failure is determined the SGSN cause value according to this access failure reason in the step 103:SCP analytical procedure 102.
Wherein, the corresponding access failure reason of each service request, and for a plurality of service request, its access failure reason separately may be identical or different.Here, when determining the SGSN cause value,, will determine different SGSN cause values according to each different access failure reason for the different service request of described access failure reason according to the access failure reason.Here, the corresponding relation that connects people's failure cause and SGSN cause value that SCP can be pre-configured, thus can determine its each self-corresponding different SGSN cause value according to each different access failure reason.
Such as: Sorry, your ticket has not enough value if access failure is former, determines that then the SGSN cause value is 0; Routing update does not allow if access failure is former, determines that then the SGSN cause value is 1; APN does not allow if access failure is former, determines that then the SGSN cause value is 2; QoS does not allow if access failure is former, determines that then the SGSN cause value is 3; The Internet resources deficiency if access failure is former determines that then the SGSN cause value is 4; The traffic failure if access failure is former determines that then the SGSN cause value is 5.When the present invention does not limit and determines the SGSN cause value according to the access failure reason, the concrete numerical value of determined SGSN cause value.
Step 104:SCP is included in the determined SGSN cause value of step 103 in the response message to SGSN and sends to SGSN.
Step 105:SGSN resolves the SGSN cause value that obtains indicating the access failure reason from the described response message of step 104, and this SGSN cause value is converted to the MS cause value.
Wherein, the corresponding described SGSN cause value of the response message of each service request, and for the response message of a plurality of service request, its SGSN cause value separately may be identical or different.Here, when the SGSN cause value is converted to the MS cause value, for the response message of the different service request of described SGSN cause value, each different SGSN cause value will be converted into different MS cause values.Here, the SGSN cause value that SGSN can be pre-configured and the corresponding relation of MS cause value, thus can determine its each self-corresponding different MS cause value according to each different SGSN cause value.
Such as: Sorry, your ticket has not enough value 0 if the SGSN cause value is for indication, determines that then the MS cause value is 130; If the SGSN cause value is unallowed 1 for the indication routing update, determine that then the MS cause value is 131; If the SGSN cause value is unallowed 2 for indication APN, determine that then the MS cause value is 132; If the SGSN cause value is unallowed 3 for indication QoS, determine that then the MS cause value is 133; If the SGSN cause value is 4 of an indication network inadequate resource, determine that then the MS cause value is 134; If the SGSN cause value is 5 of an indicating services fault, determine that then the MS cause value is 135.When the present invention does not limit the SGSN cause value is converted to the MS cause value, the concrete numerical value of the MS cause value that is converted to.
The MS cause value that step 106:SGSN is converted to step 105 is included in the response message to MS and is handed down to MS.
Step 107:MS receiving step 106 described response messages are resolved the cause value that obtains indicating access failure from this response message, and determine to interrupt information and be shown to the user according to this cause value.
Wherein, the corresponding MS cause value of each response message that MS receives, and for a plurality of response messages, its MS cause value separately may be identical or different.Here, when determining to interrupt information according to the MS cause value, for the different response message of described MS cause value, MS will determine different interruption informations according to different MS cause values, so the user can distinguish different access failure reasons by each different interruption information.Here, MS cause value that MS can be pre-configured and the corresponding relation that interrupts information, thus can determine its each self-corresponding different interruption information according to each different MS cause value.
Such as: Sorry, your ticket has not enough value 130 if the MS cause value is for indication, determines that then interrupting information is " Sorry, your ticket has not enough value "; If the MS cause value is unallowed 131 for the indication routing update, then determines to interrupt information and be " roaming does not allow "; If the MS cause value is unallowed 132 for indication APN, determine that then interrupting information is " APN mistake "; If the MS cause value is unallowed 133 for indication QoS, determine that then interrupting information is " QoS does not support "; If the MS cause value is 134 of an indication network inadequate resource, determine that then interrupting information is " network busy "; If the MS cause value is 135 of an indicating services fault, determine that then interrupting information is " traffic failure ".When the present invention does not limit according to the definite interruption of MS cause value information, the particular content of determined interruption information.
In the foregoing description, SGSN cause value that SCP and SGSN will determine respectively separately and MS cause value are included in when issuing in each self-corresponding response message, the value of described SGSN cause value and MS cause value can be any number in the cause value reserved value section in the described response message of agreement regulation, can be other numerical value of non-agreement defined, the present invention does not limit this yet.
The above is applied to the processing of SGSN as the session management flow process of SSP for the present invention, and the service access failure cause that described SCP determines can comprise: Sorry, your ticket has not enough value or routing update does not allow or APN does not allow or QoS does not allow or Internet resources deficiency or traffic failure or this combination in any.When the present invention is applied to SGSN as the mobile management flow process of SSP, processing procedure and above-mentioned processing are basic identical, difference is that the determined service access failure cause of SCP can comprise: Sorry, your ticket has not enough value or routing update does not allow or Internet resources deficiency or traffic failure or this combination in any.And, owing to determined access failure reason in described mobile management flow process is different with the access failure reason of determining in described session management flow process, therefore to determine that according to the access failure reason SGSN cause value, SGSN are converted into the processing that MS cause value and MS determine to interrupt information according to the MS cause value with the SGSN cause value also slightly variant for follow-up SCP, but described difference only is SGSN cause value, MS cause value and the concrete value and the quantity of interrupting information, therefore no longer describes in detail here.
When GGSN triggers service request to SCP as SSP, GGSN and SCP will participate in the session management flow process.It is basic identical as the processing of the session management flow process of SSP as the processing and the above-mentioned SGSN of being applied to of the session management flow process of SSP that the inventive method is applied to this GGSN, and described service access failure cause equally also can comprise: Sorry, your ticket has not enough value or routing update does not allow or APN does not allow or QoS does not allow or Internet resources deficiency or traffic failure or this combination in any.Difference is, receives processing the response message that comprises the SGSN cause value to SGSN after SCP determines the service access failure cause.The present invention is directed to and describedly after SCP determines the service access failure cause, receive processing the message that comprises the SGSN cause value to SGSN, two kinds of treatment mechanisms have been proposed: one, the SCP different SGSN cause value definite according to different service access failure causes, and this SGSN cause value is included in the response message to GGSN is sent to GGSN, GGSN does not do any processing to the SGSN cause value that receives and this SGSN cause value is included in the response message to SGSN is issued to SGSN; Two, the SCP different GGSN cause value definite according to different service access failure causes, this GGSN cause value is included in the response message to GGSN is sent to GGSN, the different GGSN cause value that described GGSN will receive is converted to different SGSN cause values, and this SGSN cause value is included in the response message to SGSN is issued to SGSN.
Because, the numerical value of the determined SGSN cause value of SCP may be identical with the numerical value of some GGSN cause value, if therefore adopt above-mentioned first kind of treatment mechanism, GGSN may be used as the GGSN cause value with this SGSN cause value when receiving the determined SGSN cause value of SCP, and to the rule that the SGSN cause value transforms this SGSN cause value is converted into other SGSN cause value, thereby cause follow-up processing flow mistake to occur by the GGSN cause value.Therefore, described second kind of treatment mechanism considered described first kind of problem that treatment mechanism may occur, determine the GGSN cause value by SCP, GGSN is converted into the SGSN cause value with this GGSN cause value and is handed down to SGSN then, thereby guarantees that SGSN can not carry out fault processing to the cause value that receives.
Wherein, described SCP determines that according to different service access failure causes the handling principle of different GGSN cause values determines that according to different service access failure causes the handling principle of different SGSN cause values is identical with the described SCP of Fig. 1, does not describe here; The handling principle that described GGSN is converted into different GGSN cause values different SGSN cause values is also identical with the handling principle that different SGSN cause values is converted into different MS cause values with the described SGSN of Fig. 1, therefore also no longer describes here.
In sum, use the inventive method, SCP will indicate the SGSN cause value of different access failure reasons directly to be sent to SGSN or to be sent to SGSN by GGSN indirectly when the access service request is failed, the different cause values that described SGSN will receive again are converted to different MS cause values, thereby MS can show the interruption information of the different access failure reasons of indication according to different MS cause values.Like this, when the user fails in service access, can clearly recognize the true cause of access failure, as: Sorry, your ticket has not enough value, APN does not allow etc., just can not continue under the situation that Sorry, your ticket has not enough value, to repeat to initiate service request, or continue to use original wrong APN to retransmit service request, the unnecessary system resource waste that invalid service request caused of also just having avoided these to repeat to initiate.In addition, the user is after obtaining clear and definite interruption information of the present invention, can in time supplement or change APN with money or revise QoS etc., the professional of the follow-up initiation of user can be inserted successfully substantially, also use the GPRS/UMTS IN service to bring great convenience to the user.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all be included in of the present invention comprising in the scope.
Claims (10)
1, a kind of interruption reminding method of package area intelligent service is characterized in that, in the packet switch domain service management process, service control node SCP according to GPRS node GSN business of triggering request determine service access when failure, this method comprises:
A.SCP determines the reason of service access failure, determines different GSN cause values according to different access failure reasons;
B.SCP sends to GSN with the determined GSN cause value of steps A, and the different GSN cause value that described GSN will receive is converted into different mobile terminal MS cause values and is handed down to MS;
C. the described MS of step B determines and shows the interruption information of different indicating services access failure reasons according to the different MS cause value that receives.
2, method according to claim 1 is characterized in that, described GSN is universal grouping wireless business supporting node SGSN; Described GSN cause value is the SGSN cause value.
3, method according to claim 1 is characterized in that, described GSN comprises GPRS gateway node GGSN and SGSN, triggers described service request by wherein GGSN, issues the MS cause value by wherein SGSN to MS; Described GSN cause value is the SGSN cause value; Described step B comprises: SCP sends to the determined SGSN cause value of steps A the GGSN of described triggering service request, to described SGSN, the different SGSN cause value that this SGSN will receive is converted into different MS cause values and is handed down to MS this GGSN with the SGSN cause value transparent transmission that receives.
4, according to claim 2 or 3 described methods, it is characterized in that,
In the steps A, SCP determines the SGSN cause value according to pre-configured access failure reason and the corresponding relation between the SGSN cause value;
Among the step B, SGSN is according to pre-configured SGSN cause value and the conversion of the corresponding relation between MS cause value MS cause value;
Among the step C, MS determines to interrupt information according to the corresponding relation between pre-configured MS cause value and the interruption information.
5, method according to claim 1 is characterized in that, described GSN comprises GPRS gateway node GGSN and SGSN, triggers described service request by wherein GGSN, issues the MS cause value by wherein SGSN to MS;
In the steps A, determined GSN cause value is the GGSN cause value;
Among the step B, the GSN cause value of the described MS of being converted into cause value is the SGSN cause value;
Described step B comprises:
B1.SCP sends to the GGSN of described triggering service request with the determined GGSN cause value of steps A, and the different GGSN cause value that this GGSN will receive is converted into different SGSN cause values and is handed down to described SGSN;
B2. described SGSN is converted to the different SGSN cause values that receive among the step B1 different MS cause values and is handed down to MS.
6, method according to claim 5 is characterized in that,
In the steps A, SCP determines the GGSN cause value according to pre-configured access failure reason and the corresponding relation between the GGSN cause value;
Among the step B1, GGSN is converted to the SGSN cause value according to pre-configured GGSN cause value and the corresponding relation between the SGSN cause value with the GGSN cause value that receives;
Among the step B2, SGSN is converted to the MS cause value according to pre-configured SGSN cause value and the corresponding relation between the MS cause value with the SGSN cause value that receives;
Among the step C, MS determines to interrupt information according to the corresponding relation between pre-configured MS cause value and the interruption information.
According to claim 1,2,3,5 or 6 described methods, it is characterized in that 7, in the steps A, the described SCP customer data base that inquiry connects self according to the business information in the current business request is determined the reason of described access failure.
According to claim 1,2,3,5 or 6 described methods, it is characterized in that 8, in the steps A, described SCP determines the reason of described access failure according to the business information in the current business request.
According to claim 1,2,3,5 or 6 described methods, it is characterized in that 9, described packet switch domain service management process is the session management flow process;
The reason of described access failure comprises: Sorry, your ticket has not enough value or routing update does not allow or external network Access Point Name APN does not allow or service quality QoS does not allow or Internet resources deficiency or traffic failure or this combination in any.
According to claim 1,2,3,5 or 6 described methods, it is characterized in that 10, described packet switch domain service management process is the mobile management flow process;
The reason of described access failure comprises: Sorry, your ticket has not enough value or routing update does not allow or Internet resources deficiency or traffic failure or this combination in any.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100555839A CN100355247C (en) | 2005-03-16 | 2005-03-16 | Interrupt indication method of package area intelligent service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100555839A CN100355247C (en) | 2005-03-16 | 2005-03-16 | Interrupt indication method of package area intelligent service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1835461A CN1835461A (en) | 2006-09-20 |
| CN100355247C true CN100355247C (en) | 2007-12-12 |
Family
ID=37003074
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100555839A Expired - Fee Related CN100355247C (en) | 2005-03-16 | 2005-03-16 | Interrupt indication method of package area intelligent service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100355247C (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102355686B (en) | 2008-07-16 | 2015-08-05 | 华为技术有限公司 | Tunnel management method, device and communication system |
| CN105163289A (en) * | 2015-07-28 | 2015-12-16 | 小米科技有限责任公司 | Method and apparatus for prompting connection failure during access to wireless local area network (WLAN) |
| CN106502709B (en) * | 2016-11-15 | 2019-08-13 | 腾讯科技（深圳）有限公司 | Applied business reminding method and applied business suggestion device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1376371A (en) * | 1999-09-28 | 2002-10-23 | 诺基亚公司 | A security procedure in universal mobile telephone service |
| WO2004107710A1 (en) * | 2003-05-30 | 2004-12-09 | Lg Electronics, Inc. | Home network system |
| WO2004110040A1 (en) * | 2003-06-10 | 2004-12-16 | Symbian Software Limited | A method of enabling a wireless information device to automatically modify its behaviour |
-
2005
- 2005-03-16 CN CNB2005100555839A patent/CN100355247C/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1376371A (en) * | 1999-09-28 | 2002-10-23 | 诺基亚公司 | A security procedure in universal mobile telephone service |
| WO2004107710A1 (en) * | 2003-05-30 | 2004-12-09 | Lg Electronics, Inc. | Home network system |
| WO2004110040A1 (en) * | 2003-06-10 | 2004-12-16 | Symbian Software Limited | A method of enabling a wireless information device to automatically modify its behaviour |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1835461A (en) | 2006-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2341908C2 (en) | Protocol for controlling calls when there is insufficient credit | |
| US7039388B2 (en) | Method for providing a collect call service in a mobile communication system | |
| CN100433845C (en) | Establishing emergency sessions in packet data networks for wireless devices having invalid subscriber identities | |
| CN100428708C (en) | A technique for setting up calls in internet protocol mobile network | |
| EP1142379B1 (en) | Voice mail notification service between mobile communication systems | |
| US6600928B1 (en) | Method for establishing a temporary simplex call group in a wireless communication system | |
| JP2002305763A (en) | Mobile data network | |
| US8862094B2 (en) | System and method for modifying calling behavior | |
| JPH10501109A (en) | Telecommunications system | |
| EP2658236B1 (en) | Communication system, communication control device, communication method, and mobile device | |
| CN100355247C (en) | Interrupt indication method of package area intelligent service | |
| CN100438703C (en) | Method for network side-recognizing mobile terminal style | |
| CN100442930C (en) | Mobile exchanging center and called parner processing method | |
| WO2011017936A1 (en) | Method and device for implementing unstructured supplementary service data | |
| CN100372428C (en) | Method for registrating roaming region position of mobile terminal | |
| CN100542342C (en) | Carry out the method for separating non-excited users | |
| KR100292705B1 (en) | Temporary Reference Number Structure for Wireless Registration of Mobile Phones | |
| CN101141695B (en) | Method, device and mobile communication system for prepaid user to implement characteristic service | |
| CN100428760C (en) | A method for implementing temporary number change notification service | |
| US9247414B2 (en) | Dynamic configuration of unlimited service for roaming subscriber | |
| CN100512501C (en) | Information notification method, system and device for mobile intelligent subscriber during international roaming | |
| KR100312416B1 (en) | Method for providing dynamic user data using short message service in wireless network | |
| KR100519665B1 (en) | Method for Restriction of Anonymity Call in Asynchronous IMT-2000 Network | |
| CN100442806C (en) | Method of realizing using service new telephone number | |
| KR20070045004A (en) | Method for inputting incoming restriction number |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20071212 Termination date: 20130316 |