CN100455050C - Disconnection cause notifying method - Google Patents
Disconnection cause notifying method Download PDFInfo
- Publication number
- CN100455050C CN100455050C CNB2006100012536A CN200610001253A CN100455050C CN 100455050 C CN100455050 C CN 100455050C CN B2006100012536 A CNB2006100012536 A CN B2006100012536A CN 200610001253 A CN200610001253 A CN 200610001253A CN 100455050 C CN100455050 C CN 100455050C
- Authority
- CN
- China
- Prior art keywords
- user terminal
- mobile subscriber
- disconnection cause
- subscriber terminal
- msc
- 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 a method of notifying causes of disconnection for users who want to change a communication state of user terminals into a disconnection state, and the user terminals are all user terminals being used for communication interaction and include mobile user terminals. The mobile exchange center gets a disconnection cause of a user terminal, and sends the disconnection cause acquired to other user terminals used for communication interaction; thus, the other user terminals can know the disconnection cause of the user terminal of the user who wants to turn into the disconnection state. Thus, user experiences are obviously optimized, and user satisfactions are also obviously increased.
Description
Technical field
The present invention relates to wireless communication field, be specifically related to a kind of disconnection cause notifying method.
Background technology
At present, no matter be mobile subscriber terminal or fixing user terminal, no matter be man-to-man voice communication or the trunking communication that participates in many ways also, in just communicating all mutual user terminals, in case user terminal is arranged, and reason will become disconnect state by communications status because of unexpected call drop or channel be unavailable etc., so after this user terminal is taken out stitches, other user terminal that carries out described communication interaction can become the disconnect state of unknown cause suddenly from the state with the user terminal proper communication of taking out stitches, both can't continue to communicate by letter, also have no way of learning the disconnection cause of this user terminal with the user terminal of taking out stitches.This can influence user experience, is unfavorable for the raising of user satisfaction; If above-mentioned situation occurs when comparing important communication interaction between each user terminal, then user experience especially can be affected, and more can obviously reduce user satisfaction.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of disconnection cause notifying method, guarantee just communicating in all mutual user terminals, when user terminal will become disconnect state by communications status, the disconnection cause of this user terminal can be sent to other user terminal that carries out described communication interaction, to optimize user experience, improve user satisfaction.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention discloses a kind of disconnection cause notifying method, this method may further comprise the steps:
A. in just communicating all mutual user terminals,, obtain the disconnection cause of this user terminal by moving exchanging center MSC at the user terminal that will become disconnect state by communications status; Described communicating in all mutual user terminals comprises mobile subscriber terminal; The described mobile subscriber terminal subscription data that communicate mutual each mobile subscriber terminal of MSC by storing among the inquiry Home Location Register HLR, judging whether to have at least to have comprised disconnection cause prompt service sign-on ID in the mobile subscriber terminal subscription data, is execution in step b then;
B.MSC sends to the disconnection cause that obtains other user terminal that carries out described communication interaction that will become the disconnect state user terminal except that described.
The user terminal that will become disconnect state by communications status is a mobile subscriber terminal, and this mobile subscriber terminal base station to its access before becoming disconnect state sends the release request that comprises release cause;
Then among the step a, the method that described MSC obtains disconnection cause comprises:
Become the base station that described mobile subscriber terminal inserted of disconnect state, the release cause that comprises in will the release request from this mobile subscriber terminal is carried on the user terminal request of taking out stitches or user terminal and takes out stitches to finish and send to MSC in the message.
The user terminal that will become disconnect state by communications status is a mobile subscriber terminal; And before this mobile subscriber terminal became disconnect state, the base station that it inserted obtained the communications status of this mobile subscriber terminal, was defined as this mobile subscriber terminal according to the communications status that obtains and took out stitches, and determine corresponding disconnection cause;
Then among the step a, the method that described MSC obtains disconnection cause comprises:
Become the base station that described mobile subscriber terminal inserted of disconnect state, send the user terminal request of taking out stitches that carries this mobile subscriber terminal disconnection cause to MSC.
Among the step b, described user terminal is fixing user terminal; Then among the step b, the method that described disconnection cause is sent to fixing user terminal comprises:
MSC sends to fixing user terminal with disconnection cause by the fixedly switching center that fixing user terminal connected.
Described disconnection cause is that the mode with voice messaging or Word message sends to described fixing user terminal.
The user terminal that will become disconnect state by communications status is a fixing user terminal, and before this fixing user terminal becomes disconnect state, the fixedly switching center that it connected obtains the communications status of this fixing user terminal, be defined as this fixing user terminal according to the communications status that obtains and take out stitches, and determine corresponding disconnection cause;
Then among the step a, the method that described MSC obtains disconnection cause comprises:
Become the fixedly switching center that described fixing user terminal connected of disconnect state, send the user terminal request of taking out stitches that carries this fixing user terminal disconnection cause to MSC.
Among the step b, described user terminal is mobile subscriber terminal; Then among the step b, the method that described disconnection cause is sent to mobile subscriber terminal comprises:
MSC sends to mobile subscriber terminal with disconnection cause by the base station that mobile subscriber terminal inserted; Or disconnection cause sent to mobile subscriber terminal by Short Message Service Platform.
When MSC sent disconnection cause by described base station, this disconnection cause was that the mode with voice messaging or Word message sends to described mobile subscriber terminal;
When MSC sent disconnection cause by described Short Message Service Platform, this disconnection cause was that the mode with short message sends to described mobile subscriber terminal.
Among the step b, described user terminal comprises mobile subscriber terminal and fixing user terminal; Then among the step b, the method that described disconnection cause is sent to user terminal comprises:
At mobile subscriber terminal, MSC sends to mobile subscriber terminal with disconnection cause by the base station that mobile subscriber terminal inserted; Or disconnection cause sent to mobile subscriber terminal by Short Message Service Platform;
At fixing user terminal, MSC sends to fixing user terminal with disconnection cause by the fixedly switching center that fixing user terminal connected.
At mobile subscriber terminal, when MSC sent disconnection cause by described base station, this disconnection cause was that the mode with voice messaging or Word message sends to described mobile subscriber terminal; When MSC sent disconnection cause by described Short Message Service Platform, this disconnection cause was that the mode with short message sends to described mobile subscriber terminal;
At fixing user terminal, when MSC sent disconnection cause by described fixedly switching center, this disconnection cause was that the mode with voice messaging or Word message sends to described fixing user terminal.
Among the step b, described user terminal is further according to the send mode of the disconnection cause received, plays accordingly or shows processing at this disconnection cause.
Further comprised before step a: described communicating has at least a mobile subscriber terminal to send disconnection cause prompt service register requirement to HLR in each mutual mobile subscriber terminal; After HLR receives disconnection cause prompt service register requirement, in the mobile subscriber terminal subscription data of mobile subscriber terminal of the described register requirement of transmission of self storage, add disconnection cause prompt service sign-on ID.
Compared with prior art, disconnection cause notifying method provided by the present invention, just communicating mutual and comprising in all user terminals of mobile subscriber terminal, at the user terminal that will become disconnect state by communications status, obtain the disconnection cause of this user terminal by mobile switching centre, and the disconnection cause that obtains is sent to other user terminal that carries out described communication interaction; Make other user terminal can know the disconnection cause of the user terminal that will become disconnect state.This has obviously optimized user experience, has also obviously improved user satisfaction.
Description of drawings
Fig. 1 is the disconnection cause notice flow chart of a preferred embodiment of the present invention;
Fig. 2 is the disconnection cause notice flow chart of another preferred embodiment of the present invention;
Fig. 3 is a disconnection cause notice general flow chart of the present invention.
Embodiment
Below in conjunction with drawings and the specific embodiments to the detailed description of the invention.
Disconnection cause notifying method provided by the invention, just communicating mutual and comprising in all user terminals of mobile subscriber terminal, at the user terminal that will become disconnect state by communications status, obtain the disconnection cause of this user terminal by mobile switching centre, and the disconnection cause that obtains is sent to other user terminal that carries out described communication interaction.
Referring to Fig. 1, Fig. 1 is the disconnection cause notice flow chart of a preferred embodiment of the present invention.Succinct in order to draw, a base station only is shown among Fig. 1, when the communication process relevant with user terminal A carried out in this base station, the base station that representative of consumer terminal A is inserted; And this base station is when carrying out the communication process relevant with user terminal B, then the base station inserted of representative of consumer terminal B.For convenience, in Fig. 1 the base station that user terminal A inserted is called base station A, the base station that user terminal B is inserted is called base station B.Certainly, base station A might be identical base station with base station B.
Flow process shown in Figure 1 may further comprise the steps:
Step 101: when user terminal A and user terminal B proper communication, if user terminal A is taken out stitches, user terminal A then becomes disconnect state by normal communication state.Particularly, user terminal A may be taken out stitches because of multiple different reason, as: normal on-hook of user terminal A or user terminal A call drop etc.
Step 102: user terminal A sends the release request that carries disconnection cause to base station A.Particularly, user terminal A can be used prior art and detect the reason of self taking out stitches, and uses prior art with the pairing cause parameter adding of detected disconnection cause release request, and the release request that will add cause parameter again sends to base station A.As: user terminal A with user terminal B normal talking process in shut down because of electric weight is not enough, user terminal A is not enough to send the release request that comprises electric weight deficiency (power down) to base station A to will shut down the time detecting self electric quantity so.
Step 103: after base station A receives release request from user terminal A, determine to discharge and user terminal A between transfer resource, and send the user terminal A request of taking out stitches that comprises the user terminal A sign at least to mobile switching centre (MSC).
Step 104:MSC receives from after the request of taking out stitches of the user terminal A of base station A, sends the user terminal A disconnect command to base station A.Certainly, MSC can further take out stitches according to described user terminal A and ask the application prior art that the user terminal A communications status of self preserving is upgraded.
Step 105: after base station A receives user terminal A disconnect command from MSC, send to user terminal A and to discharge response, discharge again and user terminal A between transfer resource.
Step 106: base station A discharge and user terminal A between transfer resource after, the disconnection cause that the release request in the step 102 is comprised is carried on user terminal A and takes out stitches and finish in the message, sends to MSC.
Step 107:MSC reads the disconnection cause that the user terminal A of receiving is taken out stitches and finished in the message to be comprised, with the reason of determining that user terminal A is taken out stitches, and with the user terminal A disconnection cause informing user terminal B that determines.Particularly, MSC reads the user terminal A of receiving and takes out stitches and finish the cause parameter of the expression disconnection cause that comprises in the message, and the value of cause parameter is sent to user terminal B in modes such as voice messaging, Word messages by base station B; Certainly, MSC also can send to Short Message Service Platform in the Word message mode with described cause parameter value, by Short Message Service Platform the cause parameter value of receiving is sent to user terminal B with short message way.
After user terminal B receives the cause parameter value that transmits with voice messaging or Word message mode, play accordingly or show processing, with disconnection cause to the user prompt user terminal A.
Certainly, MSC also can be according to the described disconnection cause that reads, and the application prior art is carried out the statistical operation at the telex network situation.
Step 108:MSC uses prior art and sends user terminal B disconnect command to base station B.
Step 109: after base station B receives user terminal B disconnect command from MSC, send release command to user terminal B.
Step 110: after user terminal B receives release command from base station B, send to base station B and to discharge response.
Step 111: base station B receives from after the release of the user terminal B response, discharge with user terminal B between transfer resource, and take out stitches to MSC transmission user terminal B and to finish message.
In fact, in the release request of step 102, carried the disconnection cause of user terminal A, therefore base station A can be carried on the user terminal A disconnection cause of receiving in the user terminal A request of taking out stitches in step 103, and with user terminal A take out stitches the request send to MSC, make MSC in step 103, know the request of taking out stitches of user terminal A.So, MSC just can be to the disconnection cause of user terminal B informing user terminal A after step 103, and this makes the user who uses user terminal B can more early know the disconnection cause of user terminal A.
Have again, in the step 107, if the cause parameter value of receiving is sent to user terminal B with short message way by Short Message Service Platform, because short message does not rely on step 108 related base station B and the transmission link between the user terminal B to the step 111, can carry out in step 108 to any time in the step 111 so sending SMS message in the step 107 operated yet.
In actual applications, user terminal B might be a fixing user terminal.In this case, in the step 107, MSC then must send to the fixedly switching center that user terminal B is connected in modes such as voice messaging, Word messages with described cause parameter value, by this fixedly switching center voice messaging or the Word message of receiving sent to user terminal B.Have, step 108 need become the fixedly communication interaction between the switching center that MSC is connected with user terminal B with step 111 again; And this no longer carries out the operation of step 109 and step 110 after fixedly described user terminal B disconnect command is received by switching center in step 108, but directly discharge and user terminal B between transfer resource, enter step 111 afterwards.
As shown in Figure 1, when user terminal A was communicated by letter with user terminal B, if user terminal A is initiatively taken out stitches, user terminal B can in time be known the disconnection cause of user terminal A.
In fact, when user terminal A is communicated by letter with user terminal B, the base station that user terminal A inserted may initiatively discharge and user terminal A between transmission link, make user terminal A be in disconnect state because of passive taking out stitches.In this case, equally need be with the timely informing user terminal B of the disconnection cause of user terminal A, concrete notice flow process is as shown in Figure 2.
A base station equally only is shown among Fig. 2, when the communication process relevant with user terminal A carried out in this base station, the base station that representative of consumer terminal A is inserted; And this base station is when carrying out the communication process relevant with user terminal B, then the base station inserted of representative of consumer terminal B.For convenience, in Fig. 2 the base station that user terminal A inserted is called base station A, the base station that user terminal B is inserted is called base station B.Certainly, base station A might be identical base station with base station B.
Flow process shown in Figure 2 may further comprise the steps:
Step 201: when user terminal A and user terminal B proper communication, base station A uses the communications status that prior art is obtained user terminal A.Concrete operations are generally: base station A detects the communication channel quality for the user terminal A distribution, or the user terminal A wireless signal strength received of base station A measurement etc.
Step 202: the base station is used prior art and is determined whether to take out stitches for user terminal A according to the user terminal A communications status that obtains.Concrete operations are generally: base station A will detect the communication channel quality for the user terminal A distribution of gained and compare with the channel available standards that sets in advance, if described communication channel quality does not reach the channel available standards of setting, base station A determines and will take out stitches for user terminal A, and definite disconnection cause is that channel is unavailable, otherwise base station A determines not take out stitches for user terminal A; Perhaps, base station A compares the user terminal A wireless signal strength that measures with the weak thresholding that sets in advance, if described user terminal A wireless signal strength is lower than the weak thresholding of setting, base station A determines and will take out stitches for user terminal A, and definite disconnection cause is that channel is unavailable, otherwise base station A determines not take out stitches for user terminal A.
If base station A determines and will take out stitches for user terminal A, then enters step 203; Certainly, if base station A determines not take out stitches for user terminal A, then no longer carry out the subsequent operation shown in Fig. 2.
Step 203: base station A sends the user terminal A request of taking out stitches that carries the user terminal A disconnection cause to MSC.
Step 204:MSC reads the user terminal A disconnection cause that is comprised in the user terminal A of the receiving request of taking out stitches, with the reason of determining that user terminal A is taken out stitches, and with the user terminal A disconnection cause informing user terminal B that determines.Particularly, MSC reads the cause parameter of the expression disconnection cause that comprises in the user terminal A of the receiving request of taking out stitches, and the value of cause parameter is sent to user terminal B in modes such as voice messaging, Word messages by base station B; Certainly, MSC also can send to Short Message Service Platform in the Word message mode with described cause parameter value, by Short Message Service Platform the cause parameter value of receiving is sent to user terminal B with short message way.
After user terminal B receives the cause parameter value that transmits with voice messaging or Word message mode, play accordingly or show processing, with disconnection cause to the user prompt user terminal A.
Certainly, MSC also can be according to the user terminal A disconnection cause that reads, and the application prior art is carried out the statistical operation at the telex network situation.
Step 205:MSC sends the user terminal A disconnect command to base station A.Certainly, MSC can further take out stitches according to described user terminal A and ask the application prior art that the user terminal A communications status of self preserving is upgraded.
Step 206: after base station A receives user terminal A disconnect command from MSC, discharge and user terminal A between transfer resource, and send user terminal A to MSC and take out stitches and finish message.
Step 207 discharges transfer resource between base station B and the user terminal B to step 210:MSC control base station B, and concrete operations are identical to step 111 with step 108 among Fig. 1.
In step 204, if the cause parameter value of receiving is sent to user terminal B with short message way by Short Message Service Platform, because short message does not rely on step 207 related base station B and the transmission link between the user terminal B to the step 210, can carry out in step 205 to any time in the step 210 so sending SMS message in the step 204 operated yet.
In actual applications, user terminal B might be a fixing user terminal.In this case, in the step 204, MSC then must send to the fixedly switching center that user terminal B is connected in modes such as voice messaging, Word messages with described cause parameter value, by this fixedly switching center voice messaging or the Word message of receiving sent to user terminal B.Have, step 207 need become the fixedly communication interaction between the switching center that MSC is connected with user terminal B with step 210 again; And this no longer carries out the operation of step 208 and step 209 after fixedly described user terminal B disconnect command is received by switching center in step 207, but directly discharge and user terminal B between transfer resource, enter step 210 afterwards.
Certainly, user terminal A might be a fixing user terminal, and user terminal B then is a mobile subscriber terminal.In this case, the operating main body of step 201 and step 202 no longer is the base station that user terminal A inserted then, but the fixedly switching center that user terminal A connected.Particularly, in the step 201, fixedly switching center that user terminal A connected uses the communications status that prior art is obtained user terminal A, as: this fixedly switching center detect the connection status of the physical interface that self links to each other with user terminal A.In the step 202, the fixedly switching center that user terminal A connected is according to the user terminal A communications status that obtains, using prior art determines whether to take out stitches for user terminal A, as: as described in fixedly switching center by detecting the physical interface connection status self link to each other with user terminal A, know that this physical interface is in malfunction, this fixedly switching center then determine and will take out stitches for user terminal A; And definite disconnection cause is the physical interface fault.
Have again, the user terminal A disconnection cause that is comprised in the request of taking out stitches of user terminal A in the step 203 then can not relate to the radio communication aspect, and only may be that circuit connects the disconnection causes relevant with fixed communication such as fault, physical interface fault, and need the request of taking out stitches of this user terminal A is sent to MSC by the fixedly switching center that user terminal A connected, and no longer be to send by the base station.
As shown in Figure 2, when user terminal A was communicated by letter with user terminal B, if user terminal A is in disconnect state because of passive taking out stitches, user terminal B can in time be known the disconnection cause of user terminal A.
By above-mentioned Fig. 1, Fig. 2 as can be known, when user terminal A was communicated by letter with user terminal B, no matter user terminal A was initiatively or passive taking out stitches, and user terminal B all can in time be known the disconnection cause of user terminal A.
In actual applications, the user can also carry out universal at present user registration course in advance, on network the mobile subscriber terminal that self uses is registered as disconnection cause prompt service registration terminal.
Concise and to the point register flow path is: the user uses mobile subscriber terminal to send disconnection cause prompt service register requirement to Home Location Register (HLR).After HLR receives disconnection cause prompt service register requirement from described mobile subscriber terminal, in this mobile subscriber terminal subscription data of self storing, add disconnection cause prompt service sign-on ID, registered the disconnection cause prompt service to show this mobile subscriber terminal.Particularly, described disconnection cause prompt service sign-on ID can be a field with special content, or value is 1 disconnection cause prompting enables parameter.
Like this, in Fig. 1, Fig. 2, know the disconnection cause of user terminal A as MSC after, just inquire about the mobile subscriber terminal subscription data among the user terminals stored A and user terminal B among the HLR alternately by communicating with HLR, and judge in the mobile subscriber terminal subscription data of finding whether comprise described disconnection cause prompt service sign-on ID, if comprise, MSC determines that this mobile subscriber terminal registered the disconnection cause prompt service, and carries out follow-up with operations such as user terminal A disconnection cause informing user terminal B; Otherwise MSC determines that this mobile subscriber terminal do not register the disconnection cause prompt service, thereby not with the disconnection cause informing user terminal B of user terminal A.
Particularly, among user terminal A and the user terminal B, may have only one to be mobile subscriber terminal, also two of possibilities are mobile subscriber terminal.At having only one to be the situation of mobile subscriber terminal among user terminal A and the user terminal B, above-mentioned inquiry subscription data and described decision operation are to carry out at the mobile subscriber terminal among user terminal A and the user terminal B naturally, that is: when only the mobile subscriber terminal in user terminal A and user terminal B has been registered the disconnection cause prompt service, just carry out follow-up with operations such as user terminal A disconnection cause informing user terminal B.
Be the situation of mobile subscriber terminal at user terminal A and user terminal B, above-mentioned inquiry subscription data and described decision operation can only be carried out at one of them mobile subscriber terminal, that is: as long as have a mobile subscriber terminal to register the disconnection cause prompt service among user terminal A and the user terminal B, just carry out follow-up with operations such as user terminal A disconnection cause informing user terminal B; Certainly, above-mentioned inquiry subscription data and described decision operation also can be carried out respectively at user terminal A and user terminal B, that is: only when user terminal A and user terminal B have registered the disconnection cause prompt service, just carry out follow-up with operations such as user terminal A disconnection cause informing user terminal B.
In above-mentioned Fig. 1, Fig. 2, the main body of communication interaction has only two user terminals; Yet in actual applications, communicating mutual main body may be a plurality of user terminals, as: user terminal A, user terminal B, user terminal C and user terminal D carry out trunking communication, user terminal A is as the communication initiator, and user terminal B, user terminal C and user terminal D are then as communicating by letter participant.In this case, in just communicating all mutual user terminals, if there is user terminal to become disconnect state, need obtains the disconnection cause of this user terminal equally by MSC, and the disconnection cause that obtains is sent to other user terminal that carries out described communication interaction by communications status.
Particularly, when the user terminal that will become disconnect state was mobile subscriber terminal, the method that MSC obtains this mobile subscriber terminal disconnection cause was identical with the method that aforementioned MSC obtains the mobile subscriber terminal disconnection cause; In like manner, when the user terminal that will become disconnect state was fixing user terminal, the method that MSC obtains this fixing user terminal disconnection cause was identical with the method that aforementioned MSC obtains the fixing user terminal disconnection cause.
Have again, when MSC sends disconnection cause to other user terminal that carries out described communication interaction, if include mobile subscriber terminal in these user terminals, MSC is identical to the method that mobile subscriber terminal sends disconnection cause with aforesaid MSC to the method for mobile subscriber terminal transmission disconnection cause so; In like manner, if include fixing user terminal in these user terminals, MSC is identical to the method that fixing user terminal sends disconnection cause with aforesaid MSC to the method for fixing user terminal transmission disconnection cause so.
Certainly, can also carry out aforesaid inquiry subscription data and decision operation at the mobile subscriber terminal that is comprised in all user terminals that carry out described communication interaction; And described inquiry subscription data and decision operation can be carried out at one in all user terminals or any a plurality of mobile subscriber terminal, also can carry out at all mobile subscriber terminals in all user terminals.
By the above as seen, disconnection cause notifying method provided by the invention can be briefly described and is flow process shown in Figure 3.Flow process shown in Figure 3 may further comprise the steps:
Step 301 is to step 302: just communicating mutual and comprise in all user terminals of mobile subscriber terminal, having user terminal to become disconnect state by communications status; MSC obtains the disconnection cause of this user terminal.
Step 303:MSC sends to the disconnection cause that obtains other user terminal that carries out described communication interaction.
By the above as can be seen, disconnection cause notifying method provided by the present invention, just communicating in all mutual user terminals, when user terminal will become disconnect state by communications status, the disconnection cause of this user terminal can be sent to other user terminal that carries out described communication interaction, make other user terminal can know the disconnection cause of the user terminal that will become disconnect state.This has obviously optimized user experience, has also obviously improved user satisfaction.
Claims (12)
1, a kind of disconnection cause notifying method is characterized in that, this method may further comprise the steps:
A. in just communicating all mutual user terminals,, obtain the disconnection cause of this user terminal by moving exchanging center MSC at the user terminal that will become disconnect state by communications status; Described communicating in all mutual user terminals comprises mobile subscriber terminal; The described mobile subscriber terminal subscription data that communicate mutual each mobile subscriber terminal of MSC by storing among the inquiry Home Location Register HLR, judging whether to have at least to have comprised disconnection cause prompt service sign-on ID in the mobile subscriber terminal subscription data, is execution in step b then;
B.MSC sends to the disconnection cause that obtains other user terminal that carries out described communication interaction that will become the disconnect state user terminal except that described.
2, the method for claim 1, it is characterized in that, the user terminal that will become disconnect state by communications status is a mobile subscriber terminal, and this mobile subscriber terminal base station to its access before becoming disconnect state sends the release request that comprises release cause;
Then among the step a, the method that described MSC obtains disconnection cause comprises:
Become the base station that described mobile subscriber terminal inserted of disconnect state, the release cause that comprises in will the release request from this mobile subscriber terminal is carried on the user terminal request of taking out stitches or user terminal and takes out stitches to finish and send to MSC in the message.
3, the method for claim 1 is characterized in that, the user terminal that become disconnect state by communications status is a mobile subscriber terminal; And before this mobile subscriber terminal became disconnect state, the base station that it inserted obtained the communications status of this mobile subscriber terminal, was defined as this mobile subscriber terminal according to the communications status that obtains and took out stitches, and determine corresponding disconnection cause;
Then among the step a, the method that described MSC obtains disconnection cause comprises:
Become the base station that described mobile subscriber terminal inserted of disconnect state, send the user terminal request of taking out stitches that carries this mobile subscriber terminal disconnection cause to MSC.
As claim 2 or 3 described methods, it is characterized in that 4, among the step b, described user terminal is fixing user terminal; Then among the step b, the method that described disconnection cause is sent to fixing user terminal comprises:
MSC sends to fixing user terminal with disconnection cause by the fixedly switching center that fixing user terminal connected.
5, method as claimed in claim 4 is characterized in that, described disconnection cause is that the mode with voice messaging or Word message sends to described fixing user terminal.
6, the method for claim 1, it is characterized in that, the user terminal that will become disconnect state by communications status is a fixing user terminal, and before this fixing user terminal becomes disconnect state, the fixedly switching center that it connected obtains the communications status of this fixing user terminal, be defined as this fixing user terminal according to the communications status that obtains and take out stitches, and determine corresponding disconnection cause;
Then among the step a, the method that described MSC obtains disconnection cause comprises:
Become the fixedly switching center that described fixing user terminal connected of disconnect state, send the user terminal request of taking out stitches that carries this fixing user terminal disconnection cause to MSC.
As claim 2,3 or 6 described methods, it is characterized in that 7, among the step b, described user terminal is mobile subscriber terminal; Then among the step b, the method that described disconnection cause is sent to mobile subscriber terminal comprises:
MSC sends to mobile subscriber terminal with disconnection cause by the base station that mobile subscriber terminal inserted; Or disconnection cause sent to mobile subscriber terminal by Short Message Service Platform.
8, method as claimed in claim 7 is characterized in that, when MSC sent disconnection cause by described base station, this disconnection cause was that the mode with voice messaging or Word message sends to described mobile subscriber terminal;
When MSC sent disconnection cause by described Short Message Service Platform, this disconnection cause was that the mode with short message sends to described mobile subscriber terminal.
As claim 2,3 or 6 described methods, it is characterized in that 9, among the step b, described user terminal comprises mobile subscriber terminal and fixing user terminal; Then among the step b, the method that described disconnection cause is sent to user terminal comprises:
At mobile subscriber terminal, MSC sends to mobile subscriber terminal with disconnection cause by the base station that mobile subscriber terminal inserted; Or disconnection cause sent to mobile subscriber terminal by Short Message Service Platform;
At fixing user terminal, MSC sends to fixing user terminal with disconnection cause by the fixedly switching center that fixing user terminal connected.
10, method as claimed in claim 9 is characterized in that, at mobile subscriber terminal, when MSC sent disconnection cause by described base station, this disconnection cause was that the mode with voice messaging or Word message sends to described mobile subscriber terminal; When MSC sent disconnection cause by described Short Message Service Platform, this disconnection cause was that the mode with short message sends to described mobile subscriber terminal;
At fixing user terminal, when MSC sent disconnection cause by described fixedly switching center, this disconnection cause was that the mode with voice messaging or Word message sends to described fixing user terminal.
11, the method for claim 1 is characterized in that, among the step b, described user terminal is further according to the send mode of the disconnection cause received, plays accordingly or shows processing at this disconnection cause.
12, the method for claim 1 is characterized in that, this method further comprised before step a:
Described communicating has at least a mobile subscriber terminal to send disconnection cause prompt service register requirement to HLR in each mutual mobile subscriber terminal;
After HLR receives disconnection cause prompt service register requirement, in the mobile subscriber terminal subscription data of mobile subscriber terminal of the described register requirement of transmission of self storage, add disconnection cause prompt service sign-on ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100012536A CN100455050C (en) | 2006-01-10 | 2006-01-10 | Disconnection cause notifying method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100012536A CN100455050C (en) | 2006-01-10 | 2006-01-10 | Disconnection cause notifying method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1870776A CN1870776A (en) | 2006-11-29 |
| CN100455050C true CN100455050C (en) | 2009-01-21 |
Family
ID=37444312
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100012536A Expired - Fee Related CN100455050C (en) | 2006-01-10 | 2006-01-10 | Disconnection cause notifying method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100455050C (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106028473B (en) * | 2016-05-19 | 2019-05-10 | 珠海市魅族科技有限公司 | A kind of call hang-ups method and device |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07336762A (en) * | 1994-06-03 | 1995-12-22 | Canon Inc | Radio telephone system |
| JPH08130501A (en) * | 1994-10-28 | 1996-05-21 | Nippon Ido Tsushin Kk | Mobile communication system |
| JPH09307959A (en) * | 1996-05-15 | 1997-11-28 | Nec Commun Syst Ltd | Mobile communication system |
| JPH10200957A (en) * | 1997-01-14 | 1998-07-31 | Saitama Nippon Denki Kk | Digital radio telephone set |
| JPH1175262A (en) * | 1997-08-28 | 1999-03-16 | Toyo Commun Equip Co Ltd | Line connection control system for mobile radio communication system |
| JPH11177713A (en) * | 1997-12-11 | 1999-07-02 | Casio Comput Co Ltd | Communication terminal equipment |
| JP2001028645A (en) * | 1999-07-13 | 2001-01-30 | Toshiba Corp | Information device with radio telephone set, telephone set control method and recording medium storing telephone set control program |
| JP2002064864A (en) * | 2000-08-16 | 2002-02-28 | Sony Corp | Method of communicating state of mobile terminal |
| JP2003125458A (en) * | 2001-10-16 | 2003-04-25 | Sanyo Electric Co Ltd | Communication system |
| WO2003055240A1 (en) * | 2001-12-21 | 2003-07-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Delivering messages in a telecommunications network |
| JP2004007808A (en) * | 2003-07-28 | 2004-01-08 | Mitsubishi Electric Corp | Communication system for moving object |
| JP2004080384A (en) * | 2002-08-19 | 2004-03-11 | Sony Ericsson Mobilecommunications Japan Inc | Portable terminal and message replying method |
| JP2004242259A (en) * | 2003-02-10 | 2004-08-26 | Nec Corp | System and method for analyzing cause of abnormal disconnection in mobile communication, and apparatus and program for investigating abnormally disconnected call |
| JP2004364224A (en) * | 2003-06-09 | 2004-12-24 | Nec Corp | Cellular phone terminal, notification method of communication disconnection, and program for controlling notification of communication disconnection |
| JP2004363953A (en) * | 2003-06-04 | 2004-12-24 | Nec Saitama Ltd | Mobile terminal |
| JP2005020311A (en) * | 2003-06-25 | 2005-01-20 | Ntt Docomo Inc | Mobile station |
| JP2005026838A (en) * | 2003-06-30 | 2005-01-27 | Ntt Docomo Inc | Packet switching server apparatus, additional service server apparatus, packet communication system, and packet communication method |
| JP2005086650A (en) * | 2003-09-10 | 2005-03-31 | Nec Corp | System and method for notifying cause of transmission disabled portable terminal, server for notifying cause and cause notification program |
| US20050245250A1 (en) * | 2003-02-21 | 2005-11-03 | Gidon Ebenshpanger | Device, system and method for detection of communication disconnection |
-
2006
- 2006-01-10 CN CNB2006100012536A patent/CN100455050C/en not_active Expired - Fee Related
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07336762A (en) * | 1994-06-03 | 1995-12-22 | Canon Inc | Radio telephone system |
| JPH08130501A (en) * | 1994-10-28 | 1996-05-21 | Nippon Ido Tsushin Kk | Mobile communication system |
| JPH09307959A (en) * | 1996-05-15 | 1997-11-28 | Nec Commun Syst Ltd | Mobile communication system |
| JPH10200957A (en) * | 1997-01-14 | 1998-07-31 | Saitama Nippon Denki Kk | Digital radio telephone set |
| JPH1175262A (en) * | 1997-08-28 | 1999-03-16 | Toyo Commun Equip Co Ltd | Line connection control system for mobile radio communication system |
| JPH11177713A (en) * | 1997-12-11 | 1999-07-02 | Casio Comput Co Ltd | Communication terminal equipment |
| JP2001028645A (en) * | 1999-07-13 | 2001-01-30 | Toshiba Corp | Information device with radio telephone set, telephone set control method and recording medium storing telephone set control program |
| JP2002064864A (en) * | 2000-08-16 | 2002-02-28 | Sony Corp | Method of communicating state of mobile terminal |
| JP2003125458A (en) * | 2001-10-16 | 2003-04-25 | Sanyo Electric Co Ltd | Communication system |
| WO2003055240A1 (en) * | 2001-12-21 | 2003-07-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Delivering messages in a telecommunications network |
| JP2004080384A (en) * | 2002-08-19 | 2004-03-11 | Sony Ericsson Mobilecommunications Japan Inc | Portable terminal and message replying method |
| JP2004242259A (en) * | 2003-02-10 | 2004-08-26 | Nec Corp | System and method for analyzing cause of abnormal disconnection in mobile communication, and apparatus and program for investigating abnormally disconnected call |
| US20050245250A1 (en) * | 2003-02-21 | 2005-11-03 | Gidon Ebenshpanger | Device, system and method for detection of communication disconnection |
| JP2004363953A (en) * | 2003-06-04 | 2004-12-24 | Nec Saitama Ltd | Mobile terminal |
| JP2004364224A (en) * | 2003-06-09 | 2004-12-24 | Nec Corp | Cellular phone terminal, notification method of communication disconnection, and program for controlling notification of communication disconnection |
| JP2005020311A (en) * | 2003-06-25 | 2005-01-20 | Ntt Docomo Inc | Mobile station |
| JP2005026838A (en) * | 2003-06-30 | 2005-01-27 | Ntt Docomo Inc | Packet switching server apparatus, additional service server apparatus, packet communication system, and packet communication method |
| JP2004007808A (en) * | 2003-07-28 | 2004-01-08 | Mitsubishi Electric Corp | Communication system for moving object |
| JP2005086650A (en) * | 2003-09-10 | 2005-03-31 | Nec Corp | System and method for notifying cause of transmission disabled portable terminal, server for notifying cause and cause notification program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1870776A (en) | 2006-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103262625B (en) | For the IP-based paging of DSDS | |
| EP2478669B1 (en) | Method for performing offline indication of machine type communication device in mobile communication system | |
| CN102238701A (en) | Apparatus and method for automatic SIM card selection according to network environment in dual mode terminal | |
| US7386312B2 (en) | Mobile terminal, communication system, and method for changing location registration | |
| CN104168387B (en) | Mobile phone users identification card changing method and system | |
| CN101651973A (en) | Network switching method for mobile communication equipment terminals and system thereof | |
| CN106161497A (en) | From WIFI module and the most adaptive method of attachment of WIFI module of adaptive connection protocol | |
| KR101543286B1 (en) | Method for state transition and network equipment | |
| CN100455050C (en) | Disconnection cause notifying method | |
| CN101472299A (en) | Method, system and device for dynamically determining Off-Channel | |
| CN110278215B (en) | Call establishment method and system, and session management function entity | |
| CN100536612C (en) | A method and device to perfect the terminal authentication | |
| CN102883470A (en) | A communication device and user identification card priority and wireless activity arrangement method | |
| CN103118416A (en) | Method and device of controlling network congestion | |
| CN105101329A (en) | Mobile communication device and mobile communication method thereof | |
| US20120243401A1 (en) | Terminal device and communication method | |
| KR100960274B1 (en) | Method and Apparatus for Measuring Traffic Congestion via RNC Control based on Signaling Network Equipment Status in Mobile Communication System | |
| JP6348920B2 (en) | Mobile communication system and mobile communication terminal | |
| KR20070054541A (en) | Method for exchanging condition information in mobile to mobile and the mobile | |
| KR100664119B1 (en) | Status informing service providing method of mobile communication terminal | |
| KR100828546B1 (en) | System and method for providing information on entering and exiting zone-service area | |
| KR100738921B1 (en) | Method and system for providing safety call service preventing from voice busy truncation | |
| KR20100009069A (en) | Method and telecommunication system for providing state information of receiving mobile commnication terminal | |
| KR20030021563A (en) | Call transfer method for mobile telecommunication system | |
| WO2012144353A1 (en) | Wireless communication system, wireless base station, wireless terminal and communication control method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090121 Termination date: 20130110 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |