CN1917538A - Method of sending message in multimedia - Google Patents
Method of sending message in multimedia Download PDFInfo
- Publication number
- CN1917538A CN1917538A CN 200610104218 CN200610104218A CN1917538A CN 1917538 A CN1917538 A CN 1917538A CN 200610104218 CN200610104218 CN 200610104218 CN 200610104218 A CN200610104218 A CN 200610104218A CN 1917538 A CN1917538 A CN 1917538A
- Authority
- CN
- China
- Prior art keywords
- user
- multimedia
- message
- call transfer
- transfer service
- 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.)
- Granted
Links
Images
Abstract
The method comprises: the multimedia message service center receives the multimedia message; if the user to receive the multimedia message has already set a call transfer service, then the call transfer information will be carried in the multimedia message; sending the multimedia message; after receiving the multimedia message sent from other multimedia service centers, according to the call transfer service information, the multimedia service center makes a check to decide if there is a possibility of call transfer loop back; if yes, then stopping the sending of multimedia message.
Description
Technical field
The present invention relates to communication system, relate to a kind of method of sending message in multimedia especially.
Background technology
Multimedia messaging service, MMS (Multimedia Messaging Service, be called for short MMS) be to develop into for 2.5 generations the mobile network, a kind of service that portable terminal is tending towards is intelligent, grow up under the multimedization condition, the length of MMS message can reach 30～100 kilobytes.Except that text, can comprise the combination of one or more media formats in sound, picture and the video segment in the MMS message.The abundant of the information content can make the form of communication between the user various, also provides the space for content supplier's exploitation mobile value-added service.In 3G on the horizon (the Third Generation Partnership Project) epoch, MMS certainly will become the mandatory service of most of 3G portable terminals as the Wordn short message in 2G epoch.
The same with voice call transfer, calling transfer is the supplementary service of MMS.As long as the called subscriber is provided with call transfer service, activate call transfer service, the calling transfer behavior will take place automatically so.
Because with per family Call Transfer being set, therefore may there be the problem of call setting loopback in each, as shown in Figure 1, user 1 is provided with calling transfer to user 2, and user 2 is provided with calling transfer to user 3, and user 3 is provided with calling transfer to user 1.In this case, if user 1, user 2, user 3 belong to same MMS Relay/Server (Multimedia Messaging Service Center, be called for short MMSC), the MMSC calling transfer loopback that can detect MMS message causes the situation of endless loop so, thereby MMSC evades processing.
If but the same MMSC of user 1, user 2 ownership, if this MMSC is MMSC A and user 3 another MMSC of ownership, if this MMSC is MMSC B, because it is the ownership place service that MMS is provided with, user 1 and user's 2 calling transfer is arranged on MMSC A and finishes, user 3 calling transfer is arranged on MMSC B and finishes, MMSC A can't be known user 3 calling transfer situation, MMSC B can't be known user 1, user's 2 calling transfer situation, thereby can't detect the situation that the calling transfer loopback causes endless loop.
Cause the situation of endless loop for fear of this calling transfer loopback, setting limits prior art to calling transfer, only allow between with the user who belongs in the same MMSC, call transfer service to be set, and forbid the user that calling transfer covers to outside MMSC.Cause the situation of endless loop though use this restriction to avoid the calling transfer loopback, call transfer service can only carry out in this MMSC inside, has limited professional development.
Summary of the invention
The technical problem to be solved in the present invention provides a kind of commentaries on classics call method of multimedia messaging service, MMS, when between the MMSC call transfer service being set to be implemented in, avoiding the calling transfer loopback and causes the endless loop situation.
For solving the problems of the technologies described above, the objective of the invention is to be achieved through the following technical solutions:
A kind of method of sending message in multimedia may further comprise the steps:
MMS Relay/Server receives Multimedia Message, if the reception user of described Multimedia Message has been provided with the call transfer service of multimedia messaging service, MMS, then in described Multimedia Message, carry described call transfer service information, and send described Multimedia Message;
The multimedia service center receives the Multimedia Message that external multimedia service centre sends, and according to described call transfer service information, detects whether there is calling transfer loopback possibility, if then stop to send described Multimedia Message.
In the inventive method, preferably, described call transfer service information comprises the user ID of described reception user ID and described reception user's call transfer service associated user.
In the inventive method, preferably, describedly in described Multimedia Message, carry described call transfer service information, specifically realize by following steps:
If described Multimedia Message type is multipart.related, then increase is used to carry the note of described call transfer service information in the smil of described Multimedia Message body.
In the inventive method, preferably, describedly in described Multimedia Message, carry described call transfer service information, specifically realize by following steps:
If described Multimedia Message type is multipart.mixed, be multipart.related with described Multimedia Message type conversion then, increase is used to carry the note of described call transfer service information in the smil body of the Multimedia Message after conversion.
In the inventive method, preferably, whether described detection exists calling transfer loopback possibility, specifically realizes by following steps:
Judge described reception user ID and described reception user the call transfer service associated user user ID arbitrary whether with described call transfer service information in arbitrary user ID in the call transfer service information of carrying be complementary, if then be the calling transfer loopback; Otherwise be not the calling transfer loopback.
In the inventive method, preferably, whether the described multimedia messaging service, MMS of described call transfer service message identification is call transfer service.
In the inventive method, preferably, whether described detection exists calling transfer loopback possibility, specifically realizes by following steps:
If the described multimedia messaging service, MMS of described call transfer service message identification is a call transfer service, and the reception user of described Multimedia Message has been provided with call transfer service, and, then there is calling transfer loopback possibility in calling transfer to this multimedia service center.
In the inventive method, preferably, described step further may further comprise the steps:
If the described multimedia messaging service, MMS of described call transfer service message identification is a call transfer service, and, the reception user of described Multimedia Message has been provided with call transfer service, and, described call transfer service is intracardiac in this multimedia service, and then whether intracardiac detection exists the calling transfer loopback in this multimedia service.
Above technical scheme as can be seen, the present invention compared with prior art has following advantage:
Because MMSC of the present invention when transmitting MMS message owing to call transfer service, carries call transfer service information in MMS message; When MMSC receives the MMS message of outside MMSC transmission, the call transfer service information that can carry according to the MMS message that receives, detect whether there is the possibility of calling transfer,, then stop to continue to send the MMS message that is received if detect the possibility that has calling transfer.The present invention, stops the calling transfer loopback and causes the situation of endless loop under the situation of outside MMSC in call transfer service call forwarding that the user is provided with, has expanded call transfer service greatly.
Further, because MMSC of the present invention is when transmitting MMS message owing to call transfer service, calling transfer according to this MMS message sink user of this MMSC record is provided with record, carries in the MMSC message of transmitting whether this MMS message of sign is call transfer service; As the MMSC that receives outside MMS message, if also need to continue calling transfer to the MMSC outside, the information that then further whether belongs to call transfer service according to entrained this MMS message of sign of this received MMS message, if this message identification: this MMS message belongs to call transfer service, then as can be known, the possibility that has the calling transfer loopback, and stop to continue to transmit this MMS message to outside MMSC, make and arrive under the situation of outside MMSC in the call transfer service call forwarding that the user is provided with, stop the calling transfer loopback and cause the situation of endless loop, prior art has been expanded call transfer service greatly relatively.In addition, the inventive method only needs MMSC when sending MMS message to the outside, increase by one and be used to identify the information unit whether this MMS message belong to call transfer service and can realize in MMS message, thereby the inventive method implementation is strong.
Further, MMSC of the present invention is when transmitting MMS message owing to call transfer service, in the MMS message of transmitting, carry the user ID of associated user of reception user's the user ID of described Multimedia Message and described reception user's call transfer service, make call transfer service information be accurate to the call transfer service associated user, make the present invention can judge accurately whether calling transfer constitutes loopback, realized having guaranteed the correct transmission of MMS message avoiding the calling transfer loopback to cause under the prerequisite of endless loop.
Further, when the present invention carries the user ID related with the transfer of described Multimedia Message reception customer call in the MMS message of transmitting, by converting the multipart.mixed type of message to the multipart.related type of message, make all MMS message of transmitting to outside MMSC all comprise smil message, carry call transfer service information by the form of in smil message body, inserting note.Because the conversion of multipart.mixed type of message and multipart.related type of message, just that the media content display format of MMS message is automatic by manually changing into, and do not change the media content of MMS message, simultaneously annotated in smil message body do not constitute having any influence in the MMS message.
Description of drawings
Fig. 1 is a calling transfer loopback schematic diagram;
Fig. 2 is the user distribution schematic diagram;
Fig. 3 is the method flow schematic diagram of embodiment 3.
Embodiment
Core concept of the present invention is, by in Multimedia Message, carrying described call transfer service information record, make when the multimedia service center is received in the Multimedia Message of external multimedia service centre transmission, can be according to described call transfer service information record, detect and whether have calling transfer loopback possibility, if then stop to send described Multimedia Message.When the present invention has realized that the call transfer service that is provided with as the user is between MMSC, stop the calling transfer loopback and caused the situation of endless loop, made the call transfer service of multimedia messaging service, MMS be not limited in the MMSC, expanded call transfer service greatly.
In order to make those skilled in the art better understand technical solution of the present invention, below further in conjunction with the accompanying drawings and specific embodiment the present invention will be described:
At first there is user distribution schematic diagram as shown in Figure 2 in hypothesis, and as shown, user 1, user 2, user 3, user 7 and user 8 be with ownership MMSC A, and user 4, user 5 be with ownership MMSC B, user 6 ownership MMSC C.
Embodiment 1:
If user's distribution as shown in Figure 2, suppose that user 1 is the primary reception user of MMS message, and, user 1 is provided with calling transfer to 2, user 2 is provided with calling transfer to 3, after MMSC A receives the MMS message that sends to user 1, receive user (user 1) address in the definition multimedia message, and carry out the calling transfer setting of inquiring user 1.Because user 1, user 2 and user 3 are with ownership MMSC A, its calling transfer is provided with all to be finished in MMSC, so MMSC A knows that the final reception user of this MMS is user 3, and is provided with according to calling transfer this MMS message is sent to user 3.
Embodiment 2:
If user's distribution is as shown in Figure 2, suppose that user 1 is the primary reception user of MMS message, and user 1 is provided with calling transfer to 3, user 3 is provided with calling transfer to 4.After MMSC A receives the MMS message that sends to user 1, according to user 1, the user 2, user 3 calling transfer is provided with inquiry, the reception user of knowing this MMS message is not for the user 4 of this MMSC, obtain the system address of the MMSC B at user 4 places, according to third generation co-operative project (Third Generation Partnership Project, abbreviation 3GPP) MMS standard, with this MMS message by the interactive interface between the different multimedia information system (the MM4 interface of stipulating among the 3GPP), with the form of request, with the MMSC B of MMS forwards to user 4 places.
Different is with prior art, and whether the present invention in the MMS message of transmitting to be used to identify this MMS be the information unit of call transfer service if increasing by one, and this information unit is carried out value, and make this value indicate: this MMS message is call transfer service.
After MMSC B received this MMS message, whether be the information unit value of call transfer service according to carrying if being used to identify this MMS, know the MMS message that this MMS message forwards owing to calling transfer for outside MMSC.The calling transfer of MMSC B inquiring user 4 in this MMSC is provided with situation, if user 4 has been provided with calling transfer to user 5 in MMSC B, then MMSC B is known the possibility that does not exist the calling transfer loopback to cause endless loop, directly this MMS message is sent to user 5; If user 4 has been provided with calling transfer to user 2 in MMSC B, because user 2 is not in MMSC B, MMSC B can't know that user 2 calling transfer is provided with situation, if MMSC B with this MMS forwards to MMSCA, if user 2 has been provided with calling transfer to user 1 in MMSC A so, user 2 or user 3, calling transfer loopback and cause endless loop then, if thereby recall is transferred to outside MMSC, the possibility that has the calling transfer loopback, cause the situation of endless loop in order to stop the calling transfer loopback, MMSC B refusal to outside MMSC, and stops the transmission of this MMS message with this MMS forwards.
In like manner, if user 4 has been provided with calling transfer to user 6 in MMSC B, in like manner MMSC B refusal continues calling transfer to MMSC C with this MMS message, and stops the transmission of this MMS message.
As seen, because in the MMS message that the present invention sends between MMSC, whether increase by is used to identify this MMS message is the information unit of call transfer service, make the MMSC that receives this MMS message can judge whether this MMS message is call transfer service according to the value of this information unit, if, then when need in this MMSC, continuing calling transfer to outside MMSC, and have the calling transfer loopback and cause the possibility of endless loop, and take to evade, and stop the transmission of MMS message.
Embodiment 3:
Below be the primary reception user of MMS message with hypothesis user 1, and user 1 is provided with calling transfer to 3, it is example that user 3 is provided with calling transfer to user 4 situation, and the process of transmitting of this method to this MMS message is described.
Fig. 3 is the transmission flow schematic diagram of present embodiment method, as shown, may further comprise the steps:
Step S301:MMSC A receives the MMS message that is sent to user 1.
The call transfer service of step S302:MMSC A inquiring user 1.
After MMSC A received the MMS message that sends to user 1, according to the call transfer service inquiry to user 1, know that this calling transfer situation is: user's 1 calling transfer was to user 3, and user's 3 calling transfer are to user 4.
Step S303: judge whether call forwarding outside MMSC A, if, then execution in step S304 and step S305; Otherwise carrying out call transfer service according to the call transfer service handling process in the MMSC of prior art handles.
Obviously in the present embodiment, user 4 does not belong to MMSC A, and belongs to MMSC B, then while execution in step S304 and step S305.
Step S304: the system address that obtains the MMSC B at user 4 places.
For behind the user 4 not, then obtain the system address of the MMSC B at user 4 places the reception user of knowing this MMS message at this MMSC.
Step S305: whether the message body type of judging this MMS message is multipart.related, if execution in step S307 then; Otherwise, execution in step S306.
Step S306: this MMS type of message is converted to multipart.related, continues execution in step S307.
When type of message is multipart.mixed, inserts the endomorph of one section smil form at the head of MMS message body, and type of message is changed to multipart.related.
Step S307:MMSC A inserts note in the smil of this MMS message body, to indicate the calling transfer situation of this MMS message in this MMSC.
So far, the message body type of all MMS message has been the multipart.related type, the calling transfer that MMSCA obtains user 1 and user 1 is associated and belongs to the user's of this MMSC user ID, and in the smil of MMS message body, insert one section note that carries the user totem information that is obtained, to indicate the call transfer service of this MMS message in this MMSC.Assumed condition at present embodiment: suppose that user 1 is the primary reception user of MMS message, and, user 1 is provided with calling transfer to 3, and user 3 is provided with calling transfer to user 4 situation, and the call transfer service in MMSC A that is indicated is: user's 1 calling transfer is to user 3.
General, can adopt the station address of user in this MMSC as user ID.The note that inserts in the smil body, can adopt shown in the following form:
＜!--FW:To: user 1 address, Fw: user 3 addresses--＞, wherein FW represents call transfer service.
Above annotation callout form is only done effect for example, be not limited thereto in actual applications, as long as can in this notes content, carry MMS message the reception user ID, receive the user label of user's the associated user of call transfer service in this MMSC, and needn't indicate that the calling transfer of calling transfer concerns by note form as implied above.
Step S308:MMSC A with this MMS forwards to MMSC B.
After MMSC A finishes and insert note in MMS message, according to third generation co-operative project (ThirdGeneration Partnership Project, abbreviation 3GPP) MMS standard, with this MMS message by the interactive interface between the different multimedia information system (the MM4 interface of stipulating among the 3GPP), with the form of request, with the MMSC B of MMS forwards to user 4 places.
Step S309:MMSC B resolves the reception user of this MMS message, reception user's call transfer service associated user, and resolves the smil notes content in this MMS message.
After MMSC B receives this MMS message, the user ID of message sink user (being user 4 in this enforcement) is obtained in parsing, and according to user ID, the call transfer service of inquiring user 4 in this MMSC, if user 4 has been provided with call transfer service, then further obtain the user ID of this call transfer service associated user.
Suppose that user 4 has been provided with calling transfer and (has represented at this user X: the arbitrary user among the MMSC A) to the user X that belongs to MMSC A in MMSC B, under this supposed situation, because the user ID of user X only is recorded among its place MMSC (MMSC A), thereby the concrete calling transfer of call transfer service that MMSC B can only be known user 4 is to outside MMSC, and can't get access to the user ID of the purpose user X of calling transfer.Thereby under this supposed situation, the user ID that this step MMSC B obtains is: user's 4 signs.
Simultaneously, the notes content of the smil body of the MMS message that parsing is received obtains the call transfer service record that carries in the smil body.
Step S310:MMSC B judges whether this calling transfer is the calling transfer loopback, if not, and then execution in step S311 and step S312; Otherwise execution in step S316 evades processing, stops sending this MMS message.
The reception user ID of MMSC B by judging the MMS message in step S309, obtain, one of any user ID of whether carrying with the notes content of smil body one of any consistent of user ID that receives user's association, and judge whether this calling transfer is the calling transfer loopback, if, then be judged to be loopback, otherwise judge be not loopback.
Obviously, carry the call transfer service record in the smil body in MMS message, write down user 1 and user's 3 user ID, but because the setting of MMS is the ownership place service, and user 1, user 3 be in MMSC B, thereby MMSC B can't discern the user 1 in the note, user 3 user ID.
According to calling transfer loopback decision method, the user ID of being obtained among the step S309: user's 4 signs are all inconsistent with the arbitrary user ID in the comment entry, thereby are judged to be: be not the calling transfer loopback.
Step S311:MMSC B obtains the system address of MMSC A.
Hypothesis user 4 has been provided with calling transfer to the situation of user X in MMSC B in above step S309, and carry out this step: MMSC B obtains the system address of the MMSC A at user X place.
Step S312:MMSC B upgrades the note of mark customer call transfer service in the MMS message.
MMSC B carries the call transfer service of message sink user in this MMSC in this MMS message, specifically be that the business of exhaling is changeed in the calling that is increased in the message sink user in the MMSC B in the note in the smil of MMS message message body.Note after the increase is as follows:
＜!--FW:To: user 1 address, Fw: user 3 addresses, FW: user 4 addresses--＞, wherein FW represents call transfer service.
Step S313:MMSC B with this MMS forwards to MMSC A.
After MMSC B upgrades the note of mark customer call transfer service in the MMS message, MMSC B is according to the MMS standard of 3GPP, with this MMS message by the interactive interface between the different multimedia information system (the MM4 interface of stipulating among the 3GPP), with the request form, with the MMS forwards to MMSC A.
Step S314:MMSC A resolves the reception user of this MMS message, reception user's call transfer service associated user, and resolves the smil notes content in this MMS message.
After MMSC A receives this MMS message, resolve the interior MMS message call transfer service record of smil body of this message
Simultaneously, MMSC A resolves the reception user's (user X) of received MMS message user ID, and inquire about this user X and whether in this MMSC, be provided with call transfer service, if be provided with, then further obtain the user ID of this call transfer service associated user.
Such as:
First hypothesis: suppose that this user X is user 1, then obtain user 1 user ID, because user's 1 calling transfer to user 3, is then further obtained user 3 user ID;
Second hypothesis: suppose that this user X is user 2, and the user has been provided with calling transfer to user 7, and user's 7 calling transfer are to user 8, and user's 8 calling transfer are to user 3, then MMSC A obtains user 2 user ID, and further obtains user 7, user 8, user's 3 user ID;
The 3rd hypothesis: suppose that user X is user 2, and the user has been provided with calling transfer to user 7, and user's 7 calling transfer are to user 8, (wherein user Y belongs to MMSC A to user's 8 calling transfer to user Y, and this user Y is not user 1 or user 3), then MMSC A obtains user 2 user ID, and further obtains the user ID of user 7, user 8, user Y;
The 4th hypothesis: suppose that user X is user 2, and the user has been provided with calling transfer to user 7, and user's 7 calling transfer are to user 8, user's 8 calling transfer are not to user Y (wherein user Y belongs to MMSCA), then MMSC A obtains user 2 user ID, and further obtains user 7, user's 8 user ID.
Step S315:MMSC A judges whether this calling commentaries on classics is exhaled is the calling transfer loopback, if, execution in step S316; Otherwise, execution in step S317.
The MMS message sink user ID of MMSC A by obtaining among the determination step S314, receive the user the call transfer service associated user user ID arbitrary whether with MMS message smil body in the entrained call transfer service record of note in user ID arbitrary consistent, and judge whether this calling transfer constitutes loopback, if, then determine that it is loopback, otherwise, be judged to be and do not constitute loopback.
Under the situation of first hypothesis, then according to calling transfer loopback decision method, the user ID that obvious user 1, user 3 user ID and note carry is consistent, and MMSC A judges that this MMS message call shifts formation calling transfer loopback, jumps to step S316.
Under the situation of second hypothesis, though the entrained user ID of note is inconsistent in the smil body of user 2 user ID and the MMS message that is received, but it changes and to be the transfer service associated user: the entrained user ID of user 3 user ID and the interior note of the smil body of MMS message is consistent, so, MMSC A judges that this call transfer service constitutes loopback, jumps to step S316.
Under the situation of the 3rd hypothesis, the entrained user ID of note in the smil body of the arbitrary all different and MMS message of the user ID of user 2, user 7, user 8, user Y, so MMSC A judges this call transfer service and is not the calling transfer loopback, jumps to step S317.
Under the situation of the 4th hypothesis, in like manner, MMSC A judges that this call transfer service defies the calling transfer loopback, jumps to step S317.
Step S316: stop the transmission of this MMS message.
Under the situation of any discovery calling transfer loopback, carry out this step.
Step S317:MMSC A upgrades the note that changes the mark customer call transfer service in the MMS message according to the call transfer service situation of this message sink user in this MMSC, continues to send this MMS message.
If the user ID of the reception user of the MMS message that this MMSC receives or reception user's calling transfer associated user, all with in the MMS message that is received do not indicate the consistent arbitrarily of user ID that the note of customer call transfer service carries, then carry out this step.
As from the foregoing, present embodiment is with respect to embodiment 2, when present embodiment is provided with call transfer service as the reception user of MMS message, call transfer service information in the MMS message of transmitting is carried this reception user ID, and the user ID that should receive user's call transfer service associated user, the call transfer service record that makes MMS message carry arrives each user in detail, and be not only whether to be transfer service through transfer as the only mark among the embodiment 1, make every MMSC to judge accurately whether calling transfer constitutes the calling transfer loopback and will cause endless loop according to the call transfer service information in this MMS message.The present embodiment technical scheme had both been stopped the situation that the calling transfer loopback causes endless loop, had guaranteed the accurate transmission of MMS message again.
Further, at present embodiment by converting the multipart.mixed type of message to the multipart.related type of message, make all MMS message of transmitting to outside MMSC all comprise the smil body, carry call transfer service information by the form of in the smil body, inserting note.Because the conversion of multipart.mixed type of message and multipart.related type of message, just that the media content display format of MMS message is automatic by manually changing into, and do not change the media content of MMS message, in addition, annotated in smil message body, do not constitute having any influence in the MMS message.
As seen, present embodiment has been realized: when outside MMSC is arrived in the call transfer service call forwarding of user's setting, cause under the prerequisite of erroneous judgement avoiding the calling transfer loopback, realized the correct transmission of MMS message simultaneously.
More than a kind of method of sending message in multimedia provided by the present invention is described in detail, used specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (8)
1, a kind of method of sending message in multimedia is characterized in that, may further comprise the steps:
MMS Relay/Server receives Multimedia Message, if the reception user of described Multimedia Message has been provided with the call transfer service of multimedia messaging service, MMS, then in described Multimedia Message, carry described call transfer service information, and send described Multimedia Message;
The multimedia service center receives the Multimedia Message that external multimedia service centre sends, and according to described call transfer service information, detects whether there is calling transfer loopback possibility, if then stop to send described Multimedia Message.
2, method of sending message in multimedia according to claim 1 is characterized in that, described call transfer service information comprises the user ID of described reception user ID and described reception user's call transfer service associated user.
3, method of sending message in multimedia according to claim 2 is characterized in that, describedly carries described call transfer service information in described Multimedia Message, specifically realizes by following steps:
If described Multimedia Message type is multipart.related, then increase is used to carry the note of described call transfer service information in the smil of described Multimedia Message body.
4, method of sending message in multimedia according to claim 2 is characterized in that, describedly carries described call transfer service information in described Multimedia Message, specifically realizes by following steps:
If described Multimedia Message type is multipart.mixed, be multipart.related with described Multimedia Message type conversion then, increase is used to carry the note of described call transfer service information in the smil body of the Multimedia Message after conversion.
According to claim 3 or 4 described method of sending message in multimedia, it is characterized in that 5, whether described detection exists calling transfer loopback possibility, specifically realizes by following steps:
Judge described reception user ID and described reception user the call transfer service associated user user ID arbitrary whether with described call transfer service information in arbitrary user ID in the call transfer service information of carrying be complementary, if then be the calling transfer loopback; Otherwise be not the calling transfer loopback.
6, method of sending message in multimedia according to claim 1 is characterized in that, whether the described multimedia messaging service, MMS of described call transfer service message identification is call transfer service.
7, method of sending message in multimedia according to claim 6 is characterized in that, whether described detection exists calling transfer loopback possibility, specifically realizes by following steps:
If the described multimedia messaging service, MMS of described call transfer service message identification is a call transfer service, and the reception user of described Multimedia Message has been provided with call transfer service, and, then there is calling transfer loopback possibility in calling transfer to this multimedia service center.
8, method of sending message in multimedia according to claim 7 is characterized in that, described step further may further comprise the steps:
If the described multimedia messaging service, MMS of described call transfer service message identification is a call transfer service, and, the reception user of described Multimedia Message has been provided with call transfer service, and, described call transfer service is intracardiac in this multimedia service, and then whether intracardiac detection exists the calling transfer loopback in this multimedia service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101042187A CN100563289C (en) | 2006-08-01 | 2006-08-01 | A kind of method of sending message in multimedia |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101042187A CN100563289C (en) | 2006-08-01 | 2006-08-01 | A kind of method of sending message in multimedia |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1917538A true CN1917538A (en) | 2007-02-21 |
| CN100563289C CN100563289C (en) | 2009-11-25 |
Family
ID=37738429
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101042187A Expired - Fee Related CN100563289C (en) | 2006-08-01 | 2006-08-01 | A kind of method of sending message in multimedia |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100563289C (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009010015A1 (en) * | 2007-07-19 | 2009-01-22 | Huawei Technologies Co., Ltd. | Method and device for message passing |
| WO2009024055A1 (en) * | 2007-08-17 | 2009-02-26 | Huawei Technologies Co., Ltd. | Method, application server and user device for transferring the media flow of the multimedia session |
| CN101420680A (en) * | 2008-12-08 | 2009-04-29 | 中国移动通信集团浙江有限公司 | Multimedia message transferring system and method thereof |
| CN102857407A (en) * | 2012-08-24 | 2013-01-02 | 华为终端有限公司 | Multimedia Messaging Service MMS processing method and mobile terminal |
-
2006
- 2006-08-01 CN CNB2006101042187A patent/CN100563289C/en not_active Expired - Fee Related
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009010015A1 (en) * | 2007-07-19 | 2009-01-22 | Huawei Technologies Co., Ltd. | Method and device for message passing |
| WO2009024055A1 (en) * | 2007-08-17 | 2009-02-26 | Huawei Technologies Co., Ltd. | Method, application server and user device for transferring the media flow of the multimedia session |
| US8402154B2 (en) | 2007-08-17 | 2013-03-19 | Huawei Technologies Co., Ltd | Method, application server and user equipment for transferring media streams of multimedia session |
| CN101420680A (en) * | 2008-12-08 | 2009-04-29 | 中国移动通信集团浙江有限公司 | Multimedia message transferring system and method thereof |
| CN102857407A (en) * | 2012-08-24 | 2013-01-02 | 华为终端有限公司 | Multimedia Messaging Service MMS processing method and mobile terminal |
| CN102857407B (en) * | 2012-08-24 | 2015-09-30 | 华为终端有限公司 | Multimedia information service mms processing method and mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100563289C (en) | 2009-11-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1913661A (en) | Message transmitting equipment and method | |
| CN1186908C (en) | Location sensitive multimedia messaging (MMS) | |
| CN1960400A (en) | Communication terminal and reception blocking method thereof | |
| CN101043755A (en) | Method, system and apparatus for admittance determination in mobile communication system | |
| CN1934894A (en) | Mobile communication system | |
| CN1867102A (en) | Method for transmitting short message | |
| CN101075987A (en) | Apparatus and method for transmitting message | |
| CN1930895A (en) | System and method of interworking messages between mobile communication terminals | |
| CN1738446A (en) | Multimedia message system and method for transmitting multimedia message | |
| CN1665321A (en) | Multimedia messaging service system and method thereof | |
| CN1264232A (en) | Universal information receiving structure | |
| CN1917538A (en) | Method of sending message in multimedia | |
| CN1728689A (en) | Multimedia message conversion system and method using support language of terminal | |
| CN1968449A (en) | Message communication method and communication terminal | |
| CN1925486A (en) | Digital television multimedia message system framework and communication protocol thereof | |
| CN1859331A (en) | Method and system for realizing multiple way communication | |
| CN1711748A (en) | Multimedia message service center and telecommunication device for accessing deposited multimedia messages | |
| CN1859621A (en) | System and method for transmitting service short message | |
| CN1905601A (en) | Method and system for remote-controlling mobile apparatus | |
| CN101080044A (en) | SMS forward and processing method and device | |
| CN1829339A (en) | System and method for realizing other value added service by point-to-point short message mode | |
| CN1913655A (en) | Short message receiving system and method for preventing span text messages | |
| US20080070607A1 (en) | Apparatus and method for transmitting/receiving binary data in short message system | |
| CN1658698A (en) | Method for registrating roaming region position of mobile terminal | |
| CN1881953A (en) | Method and apparatus for transmitting message |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20091125 Termination date: 20130801 |