WO2008119283A1 - Procédé et système d'appel pour visiophone - Google Patents
Procédé et système d'appel pour visiophone Download PDFInfo
- Publication number
- WO2008119283A1 WO2008119283A1 PCT/CN2008/070478 CN2008070478W WO2008119283A1 WO 2008119283 A1 WO2008119283 A1 WO 2008119283A1 CN 2008070478 W CN2008070478 W CN 2008070478W WO 2008119283 A1 WO2008119283 A1 WO 2008119283A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bearer
- videophone
- message
- terminal
- calling
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42085—Called party identification service
- H04M3/42102—Making use of the called party identifier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/83—Notification aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/83—Notification aspects
- H04M15/835—Time or frequency of notifications, e.g. Advice of Charge [AoC]
- H04M15/8351—Time or frequency of notifications, e.g. Advice of Charge [AoC] before establishing a communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/83—Notification aspects
- H04M15/84—Types of notifications
- H04M15/844—Message, e.g. SMS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42017—Customized ring-back tones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/14—Systems for two-way working
- H04N7/141—Systems for two-way working between two video terminals, e.g. videophone
- H04N7/147—Communication arrangements, e.g. identifying the communication as a video-communication, intermediate storage of the signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1096—Supplementary features, e.g. call forwarding or call holding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/81—Notifying aspects, e.g. notifications or displays to the user
- H04M2215/8104—Time or frequency of notification
- H04M2215/8108—Time or frequency of notification before establishing a communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/81—Notifying aspects, e.g. notifications or displays to the user
- H04M2215/8129—Type of notification
- H04M2215/8137—Message, e.g. alphanumeric text, SMS, MMS, EMS or www-based messaging service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/82—Advice-of-Charge [AOC], i.e. notify subscriber of charges/cumulative charge; meter at the substation
Definitions
- the present invention relates to the field of communication and multimedia technologies, and more particularly to videophone calling technology. Background technique
- the ring back tone also known as the personalized ring back tone service, is a service that is customized by the called user to provide the user with a piece of music song or other recording instead of the ordinary ring back tone.
- the user can set the personalized ring back tone.
- the personalized ring back tone can be any piece of music, song, recording, video, etc.; if it is a video, the calling user terminal needs to have a corresponding video media playing capability to correctly experience, which is also called a multimedia ring back tone. Or color vision business.
- the multimedia ring back tone service of the videophone is a videophone service, which is customized by the called user.
- the system provides a section for the calling party while the called party rings.
- the videophone service is a point-to-point communication service that can simultaneously utilize audio and video as defined in the Universal Mobile Telecommunication System (UMTS), which can be visualized between two visible mobile terminals. Two-way real-time communication of audio and video between the mobile terminal and the visual fixed terminal or between the visible mobile terminal and the PC.
- UMTS Universal Mobile Telecommunication System
- H.245 The multimedia communication control signaling protocol H.245 involved in the videophone service is introduced below.
- the multimedia ring back tone service of the videophone is implemented by implementing a function module of the multimedia ring back tone on the terminal, that is, after the user downloads the multimedia ring back tone and performs setting, when the user dials the video call to the user's terminal, the user's terminal Play the multimedia ring back tone to the calling terminal.
- the operator realizes the profit by charging the information fee of the user to download the multimedia ring back tone, without the need for the operator's network.
- the side of the network is modified.
- the user's terminal is a modified videophone terminal, and a functional module of the multimedia ring back tone is superimposed on the basis of the videophone terminal.
- the called terminal After receiving a call request from another terminal, the called terminal sends an Alerting message to the calling party, and then sends a Connecting message to initiate the bearer setup procedure.
- the multimedia ring back tone application of the terminal is started, and the content of the color ring back tone is ready to be played.
- the called terminal and the calling terminal establish a multimedia ring back tone through H.245.
- the multimedia ring back tone module of the called terminal plays the multimedia ring back tone through the built bearer, and the calling terminal listens to and receives the content of the multimedia ring back tone through the bearer of the videophone.
- the CRBT module of the called terminal stops playing the content, and the control is transferred to the terminal user. At this point, the process of the entire multimedia CRBT service is completed.
- the inventors of the present invention have found that since the prior art solution requires modification of the terminal, a function module for implementing the multimedia ring back tone is added to play the content of the multimedia ring back tone during the call. Moreover, it is also necessary to integrate the function module for realizing the multimedia ring back tone with the function module for the videophone call, and cooperate with the work, and therefore, the requirements for the terminal are high. If the terminal needs to select a large amount of multimedia ring tones content, it also needs to complete the content storage function locally. Moreover, for the operator, the profit can only be realized by charging the information fee of the user to download the multimedia ring back tone, which fundamentally changes the income mode of the existing operator and runs counter to the needs of the operator.
- the embodiment of the invention provides a videophone calling method and system, so that the multimedia ring back tone service of the videophone can be realized at a small cost.
- a fourth bearer of the videophone is established between the calling terminal and the called terminal, and videophone communication is performed between the calling terminal and the called terminal through the fourth bearer.
- a bearer establishing unit configured to establish a first bearer of the videophone between the calling terminal and the multimedia ring back tone server
- a multimedia ring back tone playing unit configured to play a multimedia ring back tone to the calling terminal by using the first bearer established by the bearer establishing unit;
- a detecting unit configured to detect whether the called terminal is off-hook, and after detecting that the called terminal is off-hook, indicating to the bearer establishing unit that the called terminal is off-hook; the bearer establishing unit is further configured to receive After the indication to the detecting unit, establishing a second bearer of the videophone between the called terminal and the multimedia ringback tone server;
- a communication unit configured to perform videophone communication between the calling terminal and the called terminal by using the first bearer and the second bearer established by the bearer establishing unit.
- a bearer establishing unit configured to establish a third bearer of the videophone between the calling terminal and the multimedia ringback tone server, and establish a fourth bearer of the videophone between the calling terminal and the called terminal;
- a sound playing unit configured to play a multimedia ring back tone to the calling terminal by using the third bearer established by the bearer establishing unit;
- a communication unit configured to perform videophone communication between the calling terminal and the called terminal by using the fourth bearer established by the bearer establishing unit.
- the multimedia CRBT service provided by the embodiment of the present invention can be implemented on a network framework based on an existing videophone. Moreover, the multimedia ring back tone is played by the multimedia ring back tone server to the calling terminal, thereby avoiding the protocol level modification of the terminal, so that the implementation of the multimedia ring back tone service of the videophone can minimize the impact on the terminal. .
- DRAWINGS 1 is a schematic diagram of a network structure of a videophone calling method according to a first embodiment of the present invention
- FIG. 2 is a flowchart of a videophone calling method according to a first embodiment of the present invention.
- FIG. 3 is a flow chart of a method of videophone calling according to a second embodiment of the present invention.
- FIG. 4 is a flow chart of a videophone calling method according to a third embodiment of the present invention.
- FIG. 5 is a flowchart of a videophone calling method according to a fourth embodiment of the present invention.
- FIG. 6 is a flow chart of a videophone calling method according to a fifth embodiment of the present invention.
- FIG. 7 is a flow chart of a videophone calling method according to a sixth embodiment of the present invention.
- FIG. 8 is a schematic diagram of a network structure of a videophone calling method according to a seventh embodiment of the present invention
- FIG. 9 is a flowchart of a videophone calling method according to a seventh embodiment of the present invention.
- FIG. 10 is a flowchart of a videophone calling method according to an eighth embodiment of the present invention.
- FIG. 11 is a flowchart of a videophone calling method according to a ninth embodiment of the present invention.
- Figure 12 is a block diagram showing the structure of a videophone calling system in accordance with an eleventh embodiment of the present invention
- Figure 13 is a block diagram showing the structure of a videophone calling system in accordance with a twelfth embodiment of the present invention.
- a first embodiment of the present invention relates to a videophone calling method.
- a multimedia ringback tone server passes a first bearer of a videophone established between a calling terminal and a multimedia ringback tone server.
- a multimedia ring back tone is played to the calling terminal.
- After detecting that the called terminal is off-hook establishing a second bearer of the videophone between the called terminal and the multimedia ringback tone server, by using the established first bearer and the second bearer, at the calling terminal Videophone communication is performed with the called terminal.
- the network structure of this embodiment is as shown in FIG. 1 and includes a mobile switching center (Mobile Switching).
- Mobile Switching Mobile Switching
- MSC Media Gateway
- MGW Media Gateway
- RNC Radio Network Controller
- Node Node Station Node B
- HLR Home Location Register
- A Authentication Center
- the MSC server can be associated with the VLR.
- the integrated network element, the MSC server and the MGW establish a connection through the H.248 process, and the HLR can be integrated with the AuC, which is a unified network element. (AuC may not exist in the case of actual deployment).
- the specific process is shown in Figure 2, including the following steps:
- Step 201 The calling terminal, User Equipment (“UE") A, sends a SETUP message to the attached MSC server A.
- the ITC in the BC-IE cell carried in the message is 'UDI, (ORA) , Other Rate Adaptation) for ⁇ .223& ⁇ .245,.
- Step 202 The MSC server A initiates a Send Routing Info (SRI) request to the called terminal, that is, the HLR B of the UE B, to query the routing information.
- SRI Send Routing Info
- Step 203 The HLR B sends a message requesting a Roaming Number ("PRN") to the MSC server B to which the UE B is attached, and requests the mobile station roaming number (MSRN) of the UE B. ).
- PRN Roaming Number
- MSRN mobile station roaming number
- Step 204 The MSC server B returns the MSRN of the UE B to the HLR B. If the MSC server B supports the pre-paging, the IMS server B first initiates the pre-paging process and then returns to the MSRN of the UE.
- Step 205 The HLR B returns the routing information of the UE B (ie, the MSRN of the UE B) to the MSC server A, and carries the information of whether the called user (ie, the user using UE B) customizes the multimedia CRBT service.
- Step 206 After obtaining the MSRN of the UE B, the MSC server A initiates a Call-Proceeding process to the UE A.
- Step 207 The MSC server A initiates an ISUP IAM message to the multimedia ringback tone server (integrated service digital network user part start address message). If the called user subscribes to the calling number display service, the ISUP IAM message needs to carry the calling number and the service prefix information.
- the multimedia ring back tone server is a system for providing multimedia ring tones for videophone users, has multimedia ring tones storage, playback and management capabilities, and supports Bearer Independent Call Control (BICC) / Integrated Services Digital Network User Part (ISDN User Part, referred to as "ISUP") protocol.
- BICC Bearer Independent Call Control
- ISDN User Part Integrated Services Digital Network User Part
- Step 208 The multimedia ring back tone server initiates an ISUP IAM message to the MSC server B. If the called user subscribes to the calling number display service, the ISUP IAM message needs to carry the main Call the number.
- Step 209 If the MSC server B does not initiate the pre-paging process before returning the MSRN of the UE B to the HLR B, in this step, the MSC server B initiates a paging request message to the UE B.
- Step 210 UE B returns a paging response message to the MSC server B.
- Step 211 The MSC server B sends a SETUP message to the UE B, where the ITC of the BC_IE cell carried in the message is UDI, and the ORA is ⁇ .223 & ⁇ .245.
- Step 212 The UE returns a CALL CONFIRMED message to the MSC server, and does not carry a new BC_IE, indicating that the called party can support the videophone. At this time, the UE B starts ringing.
- Step 213 After UE B rings, UE B returns an Alerting message to MSC server B.
- ACM address complete message
- Step 215 After receiving the ACM sent by the MSC server B, the multimedia ringback tone server sends the ACM that carries the CRBT information to the MSC server A.
- Step 216 The MSC server A identifies the CRBT information and sends an Alerting to UE A.
- Step 217 The multimedia ringback tone server sends a response message ("ATM" message) to the MSC server A, and triggers the MSC server A to send a Connect message to the UE A.
- the ANM message is an ANM signal sent from the multimedia ring back tone server to the MSC server A, indicating that a call between the multimedia ring back tone server and the UE A can be established and used to trigger the Connect message.
- this step is an optional step, and the specific selection depends on actual needs.
- the MSC server A may also send a Connect message to the UE A after receiving the ACM carrying the CRBT information from the multimedia ringback tone server. That is to say, the sending of the Connect message can also be triggered without the ANM message.
- Step 218 After receiving the Connect message, UE A sends a Connect to MSC Server A.
- Step 219 The first bearer of the videophone is established between the UE A and the multimedia ringback tone server by using a videophone signaling protocol procedure.
- the video telephony signaling protocol may be video telephony signaling of H.324, H.323 or Session Initiation Protocol ("SIP"). Agreement.
- SIP Session Initiation Protocol
- This embodiment uses the H.245 process in H.323 to establish the first bearer of the videophone as an example for description.
- Step 220 UE A views the video ring back tone through the multimedia ring back tone server.
- Step 221 After completing the off-hook action, the UE B sends a Connect message to the MSC server B. The called response process begins.
- Step 222 The MSC server B sends an ANM message to the multimedia ringback tone server.
- Connect_ACK Connection Response
- Step 224 The multimedia ring back tone server sends an ANM message to the MSC server A, at which time the MSC server A attached to the UE A starts charging for the videophone communication. Since the videophone communication is charged after detecting that the UE B is off-hook, the call duration can be accurately calculated and controlled during the implementation of the multimedia CRBT service.
- MSC Server A can send Connect signaling to UE A. It should be noted that, in an actual application, the MSC server A may not send the Connect signaling to the UE A or even if the Connect message is sent, the UE A does not process the Connect message, that is, the Connect message is sent or not at this time. Optional steps. If UE A receives the Connect message and chooses to process the Connect message, UE A may reply to MSC Server A with a Connect-ACK response message, and of course may not reply any message.
- Step 225 The multimedia ringback tone server and the UE B establish a second bearer of the videophone by using a multimedia communication control signaling protocol H.245 process.
- Step 226 The first bearer of the videophone established between the UE A and the multimedia ring back tone server, and the second bearer of the videophone established between the UE B and the multimedia ring back tone server, in the UE A and The video communication of the third generation mobile communication (The Third Generation, referred to as "3G") circuit domain is performed between UE Bs.
- 3G Third Generation
- the multimedia ring back tone service can be implemented based on the network frame of the existing videophone.
- the multimedia ring back tone is played by the multimedia ring back tone server to the calling terminal, thereby avoiding the protocol level modification of the terminal, so that the implementation of the multimedia ring back tone service of the videophone can minimize the impact on the terminal.
- UE A and UE B only need to establish a videophone bearer with the multimedia ring back tone server, respectively.
- UE A and UE B complete the videophone through the multimedia ring back tone server.
- the modification of the MSC server and the terminal in this embodiment is small and easy to implement.
- the Connect ACK message in step 218 and step 223 in this embodiment is used to confirm the Connect message, and may or may not exist. The specific selection depends on the actual needs.
- the second embodiment of the present invention relates to a videophone calling method, which is substantially the same as the first embodiment, except that in the first embodiment, the MSC server A sends a Connect message to the UE A (e.g., Step 217), informing UE A to establish a first bearer of the videophone.
- the MSC server A after transmitting the Alerting message to the UE A, the MSC server A does not send the Connect message as shown in step 217 to the UE A (as shown in FIG. 3), but sends an Alerting message to the UE A. Carry the business logo.
- the information element "User - User" in the Alerting message carries a special text identifying the multimedia CRBT service, so that the UE A can identify whether the multimedia ring back tone is to be received. If the service identifier is not carried in the Alerting message, the normal procedure is followed. The communication of the videophone is started; if the service identifier is carried in the Alerting message, the first bearer of the videophone is established.
- the MSC server A sends a Connect message to the UE A when the called terminal UE B picks up the phone and receives the ANM message from the multimedia ringback tone server (ie, step 224 in the first embodiment). , As shown in Figure 3.
- the terminal that does not support the multimedia CRBT service does not affect the normal connection after receiving the alerting message, and is flexibly compatible with the terminal that does not support the multimedia CRBT service.
- UE A needs to initiate 3G-324M protocol interaction after receiving the Alerting message, and requires the network to establish Circuit Switch Data (CSD) 64 circuit link at this time, so that the subsequent process can be quickly performed.
- CSD Circuit Switch Data
- the third embodiment of the present invention relates to a videophone calling method, which is substantially the same as the first embodiment, except that in the first embodiment, the network side does not need to notify the calling terminal (ie, UE A).
- the network side before detecting that the called terminal (ie, UE B) is off-hook, the network side sends a notification to the called terminal that the network side has not started charging.
- the "Facility" message notifies the calling terminal to ignore the charging or timing; after detecting that the called terminal is off-hook, sending a packet indicating that the network side starts charging to the called terminal
- the "Facility" message informs the calling terminal to start billing or timing.
- the first "Facility" message is hereinafter referred to as "Facility” message FA
- the second "Facility” message is referred to as "Facility” message FB.
- step 421 the MSC server A or the multimedia ringback tone server sends a "Facility" message FA to the UE A, notifying the UE A that this is not a normal call, and the network side has not started charging.
- Steps 422 to 425 are completely the same as steps 221 to 224, and are not described herein again.
- step 426 the MSC server A or the multimedia ring back tone server sends to the UE A.
- the "Facility" message FB notifies the UE A that the normal call starts, and the network side starts charging.
- UE A Since during the normal videophone process, UE A will establish the bearer of the videophone after receiving the Connect message in step 417. At this time, UE A will display to the user: "In the videophone call, , in general, the call time of the videophone is also added, such as "00:19,, etc.
- the multimedia ring back tone service belongs to the overlay service based on the videophone technology. Therefore, if no modification is made to the UE, the videophone application considers that the process of the multimedia ring back tone service is also a process of videophone conversation, therefore, During the process of playing the multimedia ring back tone, "video call" and related timing information are displayed.
- the UE may still receive the Connect message in step 417, The time is counted according to the normal situation, but after receiving the message indicating that the network side has not started charging, that is, the " Facility" message FA, the user may be displayed with information indicating that the network side has not started charging. For example, the displayed timing information is zeroed, and the screen displays "the ringback tone is being played, the billing has not been started, and the like, and the user is notified that the network side has not started charging. The UE receives the indication on the network side. After the start of the billing message, the "Facilities" message FB, the videophone application begins to time/pay for the videophone and displays the videophone for a medium similar word.
- the "Facilities" message FB the videophone application begins to time/pay for the videophone and displays the videophone for a medium similar word.
- the Connect message in the step 417 is optional, when the Connect message sent by the system side is not received by the UE, and the function of the Connect message is replaced by another signaling message, the UE will display according to the multimedia ring back tone, that is, display the similar words such as the ring back tone being played, the timing information is not displayed, or is displayed as "00:00". After receiving the Connect message, all content is displayed in accordance with the normal videophone display process.
- Step 427 and step 428 are identical to steps 225 and 226, respectively, and are not described herein again.
- the Connect ACK message in step 418 and step 424 in this embodiment may or may not exist, and the specific selection depends on actual needs.
- the "Facilities" message FA in step 421 may be located at any position before step 425 after step 416, in addition to the position shown in FIG.
- the MSC server A may send a Connect message to the UE A, or may not send the message. If the MSC server A sends the Connect message, it will receive the ANM sent from the multimedia ringback tone server. Then, the Connect message is sent to the UE A, and the UE A may process the message, or may not perform any processing on the message.
- step 421 and step 426 in this embodiment is to prompt the calling terminal whether the real videophone has started.
- the calling terminal can accurately learn the length of the call calculated by the network side, so as to prevent the user of the calling terminal from misunderstanding the charging information, and solve the problem that the terminal starts timing during the process of playing the multimedia ring back tone.
- the MSC server A can also trigger the playback of the multimedia ring back tone by using the Alerting message or the Connect message sent to the UE A in step 416 or step 417.
- the information is sent to UE A so that UE A can accurately count accordingly. For example, if there is no such information in the message, UE A starts timing according to the original normal mode. If there is this information in the message, UE A will not start the timing when the first Connect message is received, but wait for the subsequent network to send a message indicating the start timing, and then start the timing after receiving the message indicating the start timing. .
- Whether the ringing will trigger the playback of the multimedia ring back tone can be extended by the facility field in the message, or by the extension of the User-User field in the Connect message. For example, if the value of the User-User field in the Connect message is 1, then It indicates that UE A does not count when receiving the first Connect message; in the Connect message, the value of the User-User field is 0, indicating that UE A starts timing according to the original normal mode.
- the fourth embodiment of the present invention relates to a videophone calling method, which is substantially the same as the first embodiment, except that in the first embodiment, the network side does not need to notify the calling terminal (ie, UE A).
- the network side before detecting that the called terminal (ie, UE B) is off-hook, the network side sends a notification to the called terminal that the network side has not started charging.
- SMS Short Message Service
- SMS message SA notifying the calling terminal to ignore the charging or timing
- sending to the called terminal indicates that the network side starts counting
- the SMS message of the fee informs the calling terminal to start billing or timing.
- SMS message SA the first SMS message
- SB the second SMS message
- the MSC server A sends an SMS message SA to the UE A, notifying the UE A that this is not a normal call, and the network side has not started charging.
- UE A may display information indicating that the network side has not started charging. For example, on the screen, the message "The ringback tone is being played, the billing has not been started" is displayed, and the user is notified that the network side has not started billing.
- Steps 522 to 525 are completely the same as steps 221 to 224, and are not described herein again.
- step 526 the MSC server A sends an SMS message SB to the UE A, notifying the UE A that the normal call starts, and the network side starts charging.
- the sending of the SMS message in step 521 and step 526 is actually a logical process.
- the MSC server A may send the SMS, or may be sent in cooperation with an auxiliary device such as a short message gateway.
- the meaning of the MSC server A sending the SMS is that the SMS message is triggered by a certain device and then sent via the MSC server A.
- Step 527 and step 528 are completely the same as steps 225 and 226, respectively, and are not described herein again.
- the Connect ACK message in step 518 and step 524 in this embodiment may or may not exist, and the specific selection depends on actual needs.
- the SMS message A in step 521 may be located at any position before step 525 after step 516, in addition to the position shown in FIG.
- the MSC server A may send a Connect message to the UE A, or may not send the message. If the MSC server A sends the Connect message, it will receive the ANM sent from the multimedia ringback tone server. Then, the Connect message is sent to the UE A, and the UE A may process the message, or may not perform any processing on the message.
- step 521 and step 526 in this embodiment is to prompt the calling terminal whether the real videophone has started.
- the calling terminal can accurately learn the length of the call calculated by the network side, so as to prevent the user of the calling terminal from misunderstanding the charging information, and solve the problem that the terminal starts timing during the process of playing the multimedia ring back tone.
- SMS is a common communication method of the terminal
- the content carried by the SMS indicates that the network side has not started charging or starts charging information. What kind of content is carried in the SMS to indicate the corresponding information may be according to a prior agreement. For example, "MRBT Begin" carried in the SMS message may indicate that the videophone has not started yet, and is currently a multimedia ring back tone service, and the calling terminal receives the information.
- SMS messages can carry different content and information, so the information represented by SMS messages may vary, depending on prior agreement.
- SMS Multimedia Message Services
- E-mail e-mail
- the MSC server A may further trigger the playback of the multimedia ring back tone by using the Alerting message or the Connect message sent to the UE A in step 516 or step 517.
- the information is sent to UE A so that UE A can accurately count accordingly. For example, if there is no such information in the message, UE A starts timing according to the original normal mode. If there is this information in the message, UE A will not start the timing when the first Connect message is received, but wait for the subsequent network to send a message indicating the start timing, and then start the timing after receiving the message indicating the start timing. .
- Whether the ringing will trigger the playback of the multimedia ring back tone can be extended by the facility field in the message, or by extending the User-User field in the Connect message. For example, if the value of the User-User field in the Connect message is 1, it indicates that UE A does not count when receiving the first Connect message; in the Connect message, the value of the User-User field is 0, indicating UE A. Start timing in the normal way.
- SMS message A Omitted, but still need to send an SMS message SB, which is the message that starts the timing as the above indication.
- a fifth embodiment of the present invention relates to a videophone call method, which is substantially the same as the first embodiment, except that in the first embodiment, the network side does not need to notify the calling terminal (ie, UE A).
- the network side before detecting that the called terminal (ie, UE B) is off-hook, the network side sends a notification to the called terminal that the network side has not started charging.
- the H.245 Command or Indication message notifies the calling terminal to ignore the charging or timing; after detecting that the called terminal is off-hook, sending to the called terminal indicates that the network side starts counting
- the H.245 command or indication message of the fee informs the calling terminal to start charging or timing.
- the command or indication message of the first H.245 is hereinafter referred to as the command or indication message A of H.245, and the command or indication message of the second item H.245 is referred to as the command of H.245 or Indicates the message HB.
- steps 601 to 620 are respectively performed with steps 201 to 220. It is exactly the same and will not be described here.
- the multimedia ringback tone server sends a command or indication message H of H.245 to UE A, notifying UE A that this is not a normal call, and the network side has not started charging.
- UE A may display information indicating that the network side has not started charging. For example, the message "The ringback tone is being played, the billing has not been started" is displayed on the screen, and the user is notified that the network side has not started billing.
- Steps 622 to 625 are identical to steps 221 to 224, respectively, and are not described herein again.
- the multimedia ringback tone server sends an H.245 command or indication message HB to UE A, notifying UE A that the normal call starts, and the network side starts charging.
- Step 627 and step 628 are completely the same as steps 225 and 226, respectively, and are not described herein again.
- the Connect ACK message in step 618 and step 624 in this embodiment may or may not exist, and the specific selection depends on actual needs.
- the command or indication message HA of H.245 in step 621 may be located at any position before step 625 after step 619, in addition to the position shown in FIG.
- the MSC server A may send a Connect message to the UE A, or may not send the message. If the MSC server A sends the Connect message, it will receive the ANM sent from the multimedia ringback tone server. Then, the Connect message is sent to the UE A, and the UE A may process the message, or may not perform any processing on the message.
- step 621 and step 626 in this embodiment is to prompt the calling terminal whether the real videophone has started.
- the calling terminal can accurately learn the length of the call calculated by the network side, so as to prevent the user of the calling terminal from misunderstanding the charging information, and solve the problem that the terminal starts timing during the process of playing the multimedia ring back tone. Since the whole multimedia ring back tone is required to support H.245, the H.245 command or indication message can be used to indicate that the network side has not started charging or starts charging. ⁇ Which H.245 command or indication message is used to indicate the corresponding information can be based on prior agreement. For example, the Indication indicator of USER INPUT in H.245 uses the following format: Indication Message: user input
- the "GeneralString" field in the Indication message of the USER INPUT carries 10000 to indicate that the videophone has not started yet.
- the multimedia ring back tone service is received.
- the calling terminal considers that the current session is a multimedia ring back tone session, The current session is processed as a call of the videophone; the "GeneralString" field in the Indication message of the USER INPUT may carry 10001 to indicate the end of the multimedia ring back tone service, and the videophone starts.
- the calling terminal receives the message, it will consider The current session is a videophone call and the current session will be handled as a normal videophone call. Since the USER INPUT Indication message can carry a variety of data, the above scheme is only one possible way and value.
- the H.245 Command message A can also transmit a dual tone multi-frequency ("DTMF") a signal through a user push indication ("UII").
- DTMF dual tone multi-frequency
- UAI user push indication
- the UE is instructed to stop the terminal timing. After receiving the message, UE A stops timing, clears the timer, and prompts the user to play the multimedia ring back tone.
- the H.245 Command message b can transmit the DTMF B signal to indicate that UE A starts timing. After receiving the message, UE A starts timing and prompts the user to start normal communication.
- H.245 commands, instructions, or other messages may be used in the implementation process.
- the specific implementation is similar to the embodiment, and details are not described herein again.
- the MSC server A may also use the Alerting message or the Connect message sent to the UE A to trigger the playback of the multimedia ring back tone in step 616 or step 617.
- the information is sent to UE A so that UE A can accurately count accordingly. For example, if there is no such information in the message, UE A starts timing according to the original normal mode. If there is this message in the message, UE A will not receive the first Connect message. The timing is started, but waiting for the subsequent network to send a message indicating the start timing, and after receiving the message indicating the start timing, the timing is started.
- Whether the ringing will trigger the playback of the multimedia ring back tone can be extended by the facility field in the message, or by extending the User-User field in the Connect message. For example, if the value of the User-User field in the Connect message is 1, it indicates that UE A does not count when receiving the first Connect message; in the Connect message, the value of the User-User field is 0, indicating UE A. Start timing in the normal way.
- a sixth embodiment of the present invention relates to a videophone call method, which is substantially the same as the first embodiment, except that in the first embodiment, the network side does not need to notify the calling terminal (ie, UE A).
- the network side before detecting that the called terminal (ie, UE B) is off-hook, the network side sends a notification to the called terminal that the network side has not started charging.
- the Unstructured Supplementary Service Data (“USSD”) signal notifies the calling terminal to ignore the accounting or timing; after detecting that the called terminal is off-hook, by sending a representation to the called terminal
- the USSD signal that starts to be charged on the network side notifies the calling terminal to start charging or timing.
- the first USSD signal is referred to as USSD signal A
- the second USSD signal is referred to as USSD signal B.
- Steps 701 to 720 are completely the same as steps 201 to 220, and are not described here.
- the MSC server A sends the USSD signal A to the UE A, notifying the UE A that this is not a normal call, and the network side has not started charging.
- UE A may display information indicating that the network side has not started charging. For example, on the screen, the message "The ringback tone is being played, the billing has not been started" is displayed, and the user is notified that the network side has not started billing.
- Steps 722 to 725 are completely the same as steps 221 to 224, and details are not described herein again.
- the MSC server A sends a USSD signal B to the UE A, notifying the UE A that the normal call starts, and the network side starts charging.
- Step 727 and step 728 are completely the same as steps 225 and 226, respectively, and are not described herein again.
- the Connect ACK message in step 718 and step 724 in this embodiment may or may not exist, and the specific selection depends on actual needs.
- the USSD signal A in step 721 may be located at any position before step 725 after step 716, in addition to the position shown in FIG.
- the MSC server A may send a Connect message to the UE A, or may not send the message. If the MSC server A sends the Connect message, it will receive the ANM sent from the multimedia ringback tone server. Then, the Connect message is sent to the UE A, and the UE A may process the message, or may not perform any processing on the message.
- step 721 and step 726 in this embodiment is to prompt the calling terminal whether the real videophone has started.
- the calling terminal can accurately learn the length of the call calculated by the network side, so as to prevent the user of the calling terminal from misunderstanding the charging information, and solve the problem that the terminal starts timing during the process of playing the multimedia ring back tone.
- the USSD is a common communication mode of the terminal, the USSD signal can carry information indicating that the network side has not started charging or starts charging.
- the USSD signal used to indicate the corresponding information may be based on a prior agreement.
- a flag indicating the start of the color ring tone carried by the USSD signal may be used to indicate that the calling terminal is currently a multimedia ring back tone service, and the calling terminal receives the information.
- the current session is considered to be a multimedia ring back tone session, and the current session is not treated as a videophone call;
- a flag indicating the start of the videophone carried by the USSD signal may be used to indicate that the calling terminal starts the videophone.
- the terminal After receiving the USSD signal, the terminal considers that the current session is a videophone call, and the current session is processed as a normal videophone call.
- the information represented by the different USSD signals will vary, depending on the prior agreement.
- the USSD signal is used to notify the calling terminal that the network side has started charging.
- the calling terminal may be a session initiation protocol (Session) Initation Protocol (abbreviated as "SIP"), Hypertext Transfer Protocol ("Hyper Text Transfer Protocol", "Real Time Streaming Protocol”(RTSP”), etc.
- SIP Session Initation Protocol
- RTSP Hypertext Transfer Protocol
- the specific implementation is similar to the implementation of the present embodiment. The difference is only the difference between the underlying links, and details are not described herein again.
- the MSC server A may also use the Alerting message or the Connect message sent to the UE A in step 716 or step 717 to determine whether the current ringing will trigger the playback of the multimedia ring back tone.
- the information is sent to UE A so that UE A can accurately count accordingly. For example, if there is no such information in the message, UE A starts timing according to the original normal mode. If there is this information in the message, UE A will not start the timing when the first Connect message is received, but wait for the subsequent network to send a message indicating the start timing, and then start the timing after receiving the message indicating the start timing. .
- Whether the ringing will trigger the playback of the multimedia ring back tone can be extended by the facility field in the message, or by extending the User-User field in the Connect message. For example, if the value of the User-User field in the Connect message is 1, it indicates that UE A does not count when receiving the first Connect message; in the Connect message, the value of the User-User field is 0, indicating UE A. Start timing in the normal way.
- a seventh embodiment of the present invention relates to a videophone calling method.
- a multimedia ringback tone server passes a third bearer of a videophone established between a calling terminal and a multimedia ringback tone server.
- a multimedia ring back tone is played to the calling terminal.
- a fourth bearer for establishing a videophone is established between the calling terminal and the called terminal, and the fourth bearer performs videophone communication between the calling terminal and the called terminal.
- the third bearer and the fourth bearer are videophone communication links established by a video telephony protocol of H.324, H.323, or SIP.
- the H.245 process in H.323 is used to establish the The third bearer and the fourth bearer are described as an example.
- the network structure of this embodiment is shown in FIG. 8. Different multimedia ringback tone servers are established in different areas, and the MSC server is still integrated with the VLR, which is a unified network element, MSC server. The connection is still established with the MGW through the H.248 process, and the HLR is still integrated with the AuC, which is a unified network element. The specific process is shown in Figure 9.
- Step 901 The calling terminal, UE A, sends a SETUP message to the attached MSC server A.
- the ITC in the BC_IE cell carried in the message is UDI, and the ORA is 'H.223&H.245'.
- step 902 the MSC server A initiates an SRI request to the called terminal, that is, the HLR B of the UE B.
- the HLR B takes the mobile station roaming number MSRN of the UE B to the MSC server B to which the UE B is attached.
- the MSC server B returns the MSRN of the UE B to the HLR B. If the MSC server B supports the pre-paging, the IMS server B first initiates the pre-paging process and then returns to the MSRN of the UE B.
- the HLR B returns the routing information of the UE B (ie, the MSRN of the UE B) to the MSC server A, and carries the information of whether the called user (ie, the user using UE B) customizes the multimedia CRBT service.
- step 906 after the MSC server A obtains the MSRN of the UE B, it initiates to the UE A.
- step 907 the MSC server A initiates an ISUP IAM message to the MSC server B. If the called user subscribes to the calling number display service, the calling number needs to be carried in the ISUP IAM message.
- step 908 if the MSC server B does not initiate the pre-paging process before returning the MSRN of the UE B to the HLR B, in this step, the MSC server B initiates a paging request message to the UE B.
- step 909 UE B returns a paging response message to the MSC server B.
- step 910 the MSC server B sends a SETUP message to the UE B, where the ITC of the BC_IE cell carried in the message is UDI, and the ORA is ⁇ .223 & ⁇ .245.
- step 911 the UE returns a CALL CONFIRMED message to the MSC server, and does not carry a new BC_IE, indicating that the called party can support the videophone.
- step 912 after UE B rings, UE B returns an Alerting message to MSC Server B.
- step 913 the MSC server B returns a BICC ACM message to the MSC server A.
- step 914 MSC Server A returns an Alerting message to UE A.
- step 915 the MSC server A initiates a BICC IAM message to the multimedia ringback tone server, and carries information about whether the UE B customizes the multimedia ring back tone service.
- the multimedia ringback tone server returns a BICC ACM message to the MSC server A.
- the MSC server A identifies the ACM message sent by the multimedia ringback tone server, and does not send an Alerting message to the calling terminal.
- the multimedia ring back tone server sends a BICC ANM message to the MSC server A.
- the MSC server A After receiving the BICC ANM message, the MSC server A sends a connection signaling CONNECT to the calling terminal UE A, and simultaneously monitors whether the MSC server B has a return message.
- the ANM message indicates that a call between the multimedia ring back tone server and UE A can be established and used to trigger a Connect message.
- this step is an optional step, and the specific selection depends on actual needs.
- step 918 after receiving the Connect message, UE A sends a Connect ACK message to MSC Server A.
- step 919 UE A and the multimedia ringback tone server establish a third bearer of the videophone through a multimedia communication control signaling protocol H.245 procedure. And after the third bearer of the videophone is established, the multimedia ring back tone information played by the multimedia ring back tone server is viewed.
- step 920 the called terminal UE B sends a response message CONNECT to the MSC server.
- MSC Server B returns a BICC ANM message to MSC Server A.
- MSC Server B returns a Connection Confirmation CONNECT ACK message to UE B.
- step 923 the MSC server A sends a BICC Release message to the multimedia ringback tone server, indicating that the third bearer established between the multimedia ringback tone server and the UE A is removed.
- step 924 the third bearer of the established videophone is removed between the multimedia ringback tone server and UE A.
- step 925 the multimedia ringback tone server returns a BICC Release Complete message to the MSC server A.
- step 926 UE A and UE B establish a fourth bearer of the videophone through a multimedia communication control signaling protocol H.245 procedure.
- step 927 the videophone communication of the 3G circuit domain is performed between the UE A and the UE B through the fourth bearer of the videophone established between the UE A and the UE B.
- step 928 after the videophone call is completed, the established fourth bearer and the bottom circuit are removed between UE A and UE B.
- the multimedia ring back tone service can be implemented based on the network framework of the existing videophone. Moreover, the multimedia ring back tone is played by the multimedia ring back tone server to the calling terminal, thereby avoiding the protocol level modification of the terminal, so that the implementation of the multimedia ring back tone service of the videophone can minimize the impact on the terminal. .
- the third bearer established between the calling terminal and the multimedia ringback tone server needs to be removed.
- the circuit occupied by the multimedia ringback tone server can be immediately released, which saves limited circuit resources.
- the network side also needs to charge the videophone communication.
- the call duration can be accurately calculated and controlled.
- the MSC server A may also perform the ringing of the multimedia ring back tone by using the Alerting message or the Connect message sent to the UE A in step 914 or step 917.
- the information is sent to UE A so that UE A can accurately count accordingly. For example, if there is no such information in the message, UE A starts timing according to the original normal mode. If there is this information in the message, UE A will not start the timing when the first Connect message is received, but wait for the subsequent network to send a message indicating the start timing, and then start the timing after receiving the message indicating the start timing. .
- Whether the ringing will trigger the playback of the multimedia ringback tone can be extended by the facility field in the message, or by the extension of the User-User field in the Connect message. For example, if the value of the User-User field in the Connect message is 1, it indicates that UE A does not count when receiving the first Connect message; in the Connect message, the value of the User-User field is 0, indicating UE A. Start timing in the normal way.
- the eighth embodiment of the present invention relates to a videophone calling method, which is substantially the same as the seventh embodiment, except that in the seventh embodiment, the third bearer and the fourth bearer pass H.324.
- the H.323 or SIP videophone communication protocol is established over the CSD link.
- the third bearer may be decomposed into: a fifth bearer between the calling terminal and the MSC server of the calling terminal, and a sixth bearer between the MSC server of the calling terminal and the multimedia ring back tone server;
- the four bearers can be decomposed into: a fifth bearer between the calling terminal and the MSC server of the calling terminal, and a seventh bearer between the MSC server of the calling terminal and the called terminal.
- a fifth bearer is established between the UE A and the MSC server A
- a sixth bearer is established between the MSC server A and the multimedia ring back tone server.
- the fifth bearer and the sixth bearer are both CSD links.
- an H.245 process is established on the basis of the fifth bearer and the sixth bearer.
- the calling terminal user can watch the multimedia ring back tone played by the multimedia ring back tone server.
- Steps 1020 to 1024 are completely the same as steps 920 to 924, respectively, and are not described here.
- the multimedia ringback tone server returns a BICC Release Complete message to MSC Server A.
- the MSC server A sends a Facility message to UE A, indicating that the bearer (i.e., six bearers) of the MSC server A and the multimedia ring back tone server has been removed, and the CS64 kbps bearer link between the MSC server A and the MSC server B has been established.
- the main purpose of this step is to prompt the calling terminal, UE A.
- the call process of the entire videophone involves two establishments of the H.245 bearer process, indicating that the UE A receives the facility message for the second time.
- the H.245 bearer process ie, the fourth bearer of the videophone between UE A and UE B) is prepared to prepare for the bearer with UE B on the existing CS64kbp link.
- This step can appear not only in the position shown in Figure 10, but also in step 1023. To any position between step 1026, its role is mainly to prompt the establishment of two H.245 bearer processes.
- step 1026 on the basis of the fifth bearer between the existing UE A and the MSC server A, and the seventh bearer between the MSC server A and the UE B, the H.245 process is established, that is, the calling terminal is established.
- Steps 1027 and 1028 are identical to steps 927 and 928, respectively, and are not described here.
- the present embodiment can provide a faster two-time H.245 bearer setup process than the seventh embodiment, and the change workload is small, and there is no implementation obstacle.
- a ninth embodiment of the present invention relates to a videophone calling method.
- the UE A and the multimedia ringback tone server respectively initiate a H.245 self-hanging process to remove the UE.
- the purpose of the third bearer of the videophone between the A and the multimedia ringback tone server is shown in Figure 11.
- Steps 1101 to 1120 are completely the same as steps 901 to 920, respectively, and are not described herein again.
- MSC Server B returns a BICC ANM message to MSC Server A. And, MSC Server A sends a facility message to UE A. After receiving the facility message, UE A initiates the H.245 self-hanging process (that is, does not send the hang up signaling "End Session") to the communicating party, and directly releases the local resource.
- Step 1122 is identical to step 923.
- step 1123 the MSC server A sends a BICC Release message to the multimedia ringback tone server, and after receiving the message, the multimedia ringback tone server initiates a H.245 self-hanging process (ie, does not communicate with each other) Send the hang up signaling "End Session").
- step 1124 UE A initiates a second H.245 bearer setup after completing the H.245 self-hanging process, that is, initiates a video call between UE A and UE B described in the seventh embodiment.
- the establishment process of the fourth bearer is not limited to, a second H.245 bearer setup after completing the H.245 self-hanging process, that is, initiates a video call between UE A and UE B described in the seventh embodiment.
- step 1125 the multimedia ringback tone server returns a BICC Release Complete message to MSC Server A.
- Step 1126 and step 1127 are the same as step 927 and step 928, respectively, and are not described herein again. It is not difficult to find that the difference between this embodiment and the seventh embodiment is that the network side sends a prompt message (that is, the above-mentioned facility message) to the calling terminal, indicating that the playback process of the multimedia ring back tone service of the calling terminal ends, and the request is required.
- the calling terminal establishes a second H.245 bearer. After receiving the prompt message, the calling terminal initiates a self-hanging process.
- the H.245 bearer between the first established multimedia ringback tone server will end up by the calling terminal hanging up the communication link.
- Such a process conforms to the normal call flow, and further reduces the time of the entire network connection, reduces the time for service switching, and improves the user experience.
- the entire multimedia CRBT service can be regarded as two calls, the first call is used as the multimedia ring back tone service, and the second call is used as the normal videophone call.
- the calling terminal terminates the session of the entire multimedia CRBT in a self-hanging manner according to the prompt message sent by the network side, and initiates a new H.245 bearer for the call of the videophone after suspending the session. The establishment process, thus smoothly achieving normal videophone calls.
- step 1123 when the multimedia ringback tone server receives the BICC Release message from the MSC server A, a self-hanging process is initiated.
- the multimedia ring back tone server can appear as a logical terminal in the entire multimedia ring back tone service, providing multimedia ring tones content.
- the multimedia ring back tone server can participate in the dismantling process of the entire multimedia ring back tone bearer as a participating party of the session.
- the self-hanging process initiated by the UE A and the self-hanging process initiated by the multimedia ringback tone server are basically similar (ie, the bearer between the UE A multimedia ringback tone servers is removed), so that the UE A can actually only be in the UE.
- the self-hanging process initiated in A, or the self-hanging process initiated only in the multimedia ringback tone server can also be initiated in the UE A and the multimedia ring back tone server respectively, and, in practical applications, the two There is no strict sequence of self-hanging processes.
- step 1123 of the embodiment the BICC Release message sent by the MSC server A to the multimedia ring back tone server is actually used to instruct the multimedia ring back tone server to perform the self-hanging process. Therefore, if the multimedia ringback tone server does not perform the self-hanging process, step 1123 can be omitted.
- the multimedia ring back tone server also needs to reside in the subsequent videophone call process. Among them, bear the role of a back-to-back server, which is called a bridging scheme for convenience of description.
- a back-to-back server which is called a bridging scheme for convenience of description.
- the communication link between the multimedia ringback tone server and the calling terminal needs to be removed, and the calling terminal and the called terminal need to be established.
- the communication link for the videophone service is characterized in that the calling terminal needs to establish a H.245 bearer with the multimedia ringback tone server and the called terminal respectively.
- the scheme is called non- Bridging scheme.
- a tenth embodiment of the present invention relates to a videophone calling method, which is a crossover scheme in the first to sixth embodiments, and a non-crossover scheme in the seventh to ninth embodiments. .
- the calling terminal carries the type of the CRBT scheme supported by the terminal (that is, supports the bridging scheme or the non-crossover scheme) in the SETUP message sent to the MSC server A.
- the value of the User-User field in the SETUP message can be used to indicate whether the terminal supports a non-crossover scheme or a crossover scheme. It can be agreed in advance that when the value of the User-User field is 0, it means that the terminal supports the spanning scheme. When the value of the User-User field is 1, it means that the terminal supports the non-crossover scheme.
- the subsequent procedure may be the same as any one of the foregoing first to sixth embodiments; if the network side finds that the calling terminal supports the non-crossover scheme, The subsequent process may be the same as any one of the foregoing seventh to ninth embodiments, and details are not described herein again.
- An eleventh embodiment of the present invention relates to a videophone call system, as shown in FIG. 12, including: a bearer establishing unit, configured to establish a first videophone between a calling terminal and a multimedia ringback tone server a multicast ringback tone playing unit, configured to play a multimedia ringback tone to the calling terminal by using the first bearer established by the bearer establishing unit, and a detecting unit, configured to detect whether the called terminal picks up the phone, and detects After the called terminal picks up the phone, the bearer establishing unit indicates that the called terminal is off-hook, and the bearer establishing unit is further configured to: after receiving the indication of the detecting unit, ringing the multimedia with the called terminal Establishing a second bearer of the videophone between the audio servers; a communication unit, configured to perform videophone communication between the calling terminal and the called terminal by using the first bearer and the second bearer established by the bearer establishing unit .
- the multimedia ring back tone service can be implemented based on the network framework of the existing videophone. Moreover, the multimedia ring back tone playing unit plays the multimedia ring back tone to the calling terminal, thereby avoiding the protocol level modification of the terminal, so that The realization of the multimedia ring back tone service of the videophone can minimize the impact on the terminal.
- the multimedia ring back tone playing unit is located in the multimedia ring back tone server, and the bearer establishing unit establishes the first bearer and the second bearer by using a videophone signaling protocol procedure.
- the video telephony signaling protocol can be a video telephony signaling protocol for H.324, H.323 or SIP.
- the videophone system of the embodiment may further include a charging unit for charging the videophone communication; the detecting unit is further configured to: after detecting that the called terminal is off-hook And indicating to the charging unit that the called terminal has gone off-hook, and after receiving the indication, the charging unit starts charging for videophone communication. This enables accurate calculation and control of the duration of the call during the implementation of the multimedia ring back tone service.
- a notification unit may be further included for notifying the calling terminal to ignore the charging or timing, and notifying the calling terminal to start charging or timing.
- the detecting unit is further configured to indicate to the notification unit that the called terminal has been off-hook after detecting that the called terminal is off-hook.
- the notification unit notifies the calling terminal to ignore the charging or timing before receiving the indication of the detecting unit, and after receiving the indication of the detecting unit, notifying the calling terminal to start charging or timing.
- the calling terminal can accurately learn the length of the call calculated by the network side, so as to prevent the user of the calling terminal from misunderstanding the charging information.
- a twelfth embodiment of the present invention relates to a videophone call system, as shown in FIG. 13, comprising: a bearer establishing unit, configured to establish a third form of a videophone between the calling terminal and the multimedia ringback tone server Bearer, establishing a fourth bearer of the videophone between the calling terminal and the called terminal.
- the multimedia ring back tone playing unit is configured to play a multimedia ring back tone to the calling terminal by using the third bearer established by the bearer establishing unit.
- the communication unit is configured to perform videophone communication between the calling terminal and the called terminal by using the fourth bearer established by the bearer establishing unit.
- the multimedia ring back tone service can be implemented based on the existing video frame of the videophone.
- the videophone call system of this embodiment may further include: a detecting unit, configured to detect whether the called terminal is off-hook, and a bearer removal unit, configured to remove the bearer.
- the third bearer and the fourth bearer are circuit switched data CSD links, and the third bearer is logically decomposed into: a fifth bearer between the calling terminal and the MSC server of the calling terminal, and the calling party a sixth bearer between the MSC server of the terminal and the multimedia ringback tone server; the fourth bearer is logically decomposed into: the fifth bearer, and the MSC server of the calling terminal to the called party The seventh bearer between the terminals. Then, after detecting that the called terminal is off-hook, the detecting unit indicates to the bearer removal unit that the called terminal has been off-hook, and after receiving the indication, the bearer removing unit removes the MSC server at the calling terminal to The sixth bearer between the multimedia ringback tone servers.
- the detecting unit detects that the called terminal picks up the phone, The bearer removal unit indicates that the called terminal has been off-hook, and after receiving the indication, the bearer removal unit removes the third bearer established by the bearer establishing unit, and instructs the bearer establishing unit to establish the fourth bearer.
- the multimedia ringback tone server plays a multimedia ringback to the calling terminal by using the first bearer of the videophone established between the calling terminal and the multimedia ringback tone server. sound.
- establishing a second bearer of the videophone between the called terminal and the multimedia ringback tone server by using the established first bearer and the second bearer, at the calling terminal
- Videophone communication is performed with the called terminal.
- the multimedia ring back tone server plays the multimedia ring back tone to the calling terminal through the third bearer of the visible telephone established between the calling terminal and the multimedia ring back tone server.
- a fourth bearer of the videophone is established between the calling terminal and the called terminal, and the fourth bearer performs videophone communication between the calling terminal and the called terminal.
- the multimedia ring back tone service can be implemented on a network framework based on existing videophones. Moreover, the multimedia ring back tone is played by the multimedia ring back tone server to the calling terminal, thereby avoiding the protocol level modification of the terminal, so that the implementation of the multimedia ring back tone service of the videophone can minimize the impact on the terminal. .
- the network side After detecting that the called terminal picks up the phone (or completes the establishment of the fourth bearer), the network side performs charging for the videophone communication, so that during the implementation of the multimedia ring back tone service, the call duration can be accurately calculated and controlled. .
- the calling terminal Before detecting that the called terminal is off-hook, the calling terminal is notified to ignore the charging. After detecting that the called terminal is off-hook, the calling terminal is notified to start charging.
- the calling terminal can accurately learn the length of the call calculated by the network side, so as to prevent the user of the calling terminal from misunderstanding the charging information.
- the calling terminal and the multimedia ringback tone server are removed. The third bearer established between. When the user's call is connected, the circuit occupied by the multimedia ring back tone server can be immediately released, which saves limited circuit resources.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Mobile Radio Communication Systems (AREA)
Description
可视电话呼叫方法及*** 本申请要求分别于 2007年 03月 31 日、 2007年 09月 04日提交中国专 利局、 申请号分别为 200710073941.8、 200710149813.7 ,发明名称分别为"多 媒体彩铃信息控制和传递方法及***"、 "可视电话呼叫方法及***"的中国 专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信及多媒体技术领域, 特别涉及可视电话呼叫技术。 背景技术
彩铃也称为个性化回铃音业务, 是一项由被叫用户定制, 为主叫用户 提供一段音乐歌曲或其他录音来替代普通回铃音的业务。 客户申请开通彩 铃业务之后, 可以自行设定个性化回铃音, 在其做被叫时, 为主叫用户播 放个性化定制的音乐歌曲或其他录音, 来代替普通的回铃音。 具体的说, 个性化回铃音可以是任意一段音乐、 歌曲、 录音、 视频等; 如果是视频, 则需要主叫用户终端具有相应的视频媒体播放能力才能正确体验, 此时又 称为多媒体彩铃或彩视业务。
可视电话的多媒体彩铃业务是一项在可视电话业务中, 由被叫用户定 制, 当主叫以可视电话方式拨打被叫时, ***在被叫振铃的同时为主叫用 户提供一段绚丽、 悦耳的多媒体视频来替代普通回铃音的业务。
可视电话业务是在通用 移动通信系 统 ( Universal mobile telecommunication system, 简称" UMTS" ) 中定义的一种可以同时利用音频 和视频的点对点通信业务, 可以在两个可视移动终端之间, 可视移动终端 和可视固定终端之间或者可视移动终端与 PC机之间实现音频和视频的双 向实时交流。 下面对可视电话业务中涉及到的多媒体通信控制信令协议 H.245进行介绍。
目前, 通过在终端上内置实现多媒体彩铃的功能模块, 实现可视电话 的多媒体彩铃业务, 即用户下载多媒体彩铃并进行设置后, 当他人给该用 户的终端拨打可视电话时, 该用户的终端向主叫终端播放多媒体彩铃。 运 营商通过收取用户下载多媒体彩铃的信息费实现盈利, 无需对运营商的网
络侧进行改造。 具体地说, 用户的终端是经过改造的可视电话终端, 在可 视电话终端的基础之上叠加了多媒体彩铃的功能模块。 当接收到其它终端 的呼叫请求之后, 被叫终端发送 Alerting (通告) 消息给主叫方, 并随后发 送 Connecting (连接)消息启动承载建立流程。 并同时启动终端的多媒体彩 铃应用程序, 准备开始播放彩铃内容; 与此同时, 被叫终端同主叫终端之 间通过 H.245 , 建立多媒体彩铃的承载。 当完成承载的建立过程之后, 被叫 终端的多媒体彩铃模块通过建好的承载播放多媒体回铃音, 主叫终端通过 可视电话的承载收听、 收看到多媒体彩铃的内容。 当被叫用户摘机后, 被 叫终端的彩铃模块停止播放内容, 控制权转移到终端用户手中, 至此, 整 个多媒体彩铃业务的过程完成。
然而, 本发明的发明人发现, 由于现有技术的方案需要对终端进行改 造, 增加实现多媒体彩铃的功能模块, 以便在呼叫过程中播放多媒体彩铃 的内容。 而且, 还需要将实现多媒体彩铃的功能模块同用于可视电话呼叫 的功能模块进行整合, 配合工作, 因此, 对终端的要求较高。 如果终端需 要选择大量的多媒体彩铃内容, 还需要在本地完成内容的存储功能。 而且, 对运营商而言, 仅能够通过收取用户下载多媒体彩铃的信息费实现盈利, 这从根本上改变了现有运营商的收入模式, 与运营商的需求背道而驰。
另一方面, 由于信令的模式问题, 在播放多媒体彩铃阶段, 终端就会 错误地认为可视电话的通话过程已经开始, 因此对终端而言, 无法实现对 通话时长的精确计费, 从而容易造成用户的投诉。 发明内容
本发明实施例提供一种可视电话呼叫方法及***, 使得可视电话的多 媒体彩铃业务可通过较小的代价得以实现。
本发明实施例提供的一种可视电话呼叫方法, 包括:
在主叫终端与多媒体回铃音服务器之间建立可视电话的第一承载; 通过所述第一承载向所述主叫终端播放多媒体回铃音;
检测到被叫终端摘机后, 在该被叫终端与所述多媒体回铃音服务器之 间建立可视电话的第二承载;
通过所述第一承载和第二承载, 在所述主叫终端和被叫终端之间进行
可视电话通信。
本发明实施例提供的另一种可视电话呼叫方法, 包括:
在主叫终端与多媒体回铃音服务器之间建立可视电话的第三承载; 通过所述第三承载向所述主叫终端播放多媒体回铃音;
在所述主叫终端和被叫终端之间建立可视电话的第四承载, 通过该第 四承载在所述主叫终端和被叫终端之间进行可视电话通信。
本发明实施例提供的一种可视电话呼叫***, 包括:
承载建立单元, 用于在主叫终端与多媒体回铃音服务器之间建立可视 电话的第一承载;
多媒体回铃音播放单元, 用于通过所述承载建立单元建立的所述第一 承载向所述主叫终端播放多媒体回铃音;
检测单元 , 用于检测被叫终端是否摘机 , 并在检测到该被叫终端摘机 后, 向所述承载建立单元指示该被叫终端已摘机; 所述承载建立单元还用 于在收到所述检测单元的所述指示后, 在所述被叫终端与所述多媒体回铃 音服务器之间建立可视电话的第二承载;
通信单元, 用于通过所述承载建立单元建立的所述第一承载和第二承 载, 在所述主叫终端和所述被叫终端之间进行可视电话通信。
本发明实施例提供的另一种可视电话呼叫***, 包括:
承载建立单元, 用于在主叫终端与多媒体回铃音服务器之间建立可视 电话的第三承载, 在该主叫终端和被叫终端之间建立可视电话的第四承载; 多媒体回铃音播放单元, 用于通过所述承载建立单元建立的所述第三 承载向所述主叫终端播放多媒体回铃音;
通信单元, 用于通过所述承载建立单元建立的所述第四承载, 在所述 主叫终端和所述被叫终端之间进行可视电话通信。
与现有技术相比, 本发明实施例提供的多媒体彩铃业务可以在基于现 有的可视电话的网络框架上得以实现。 而且, 由多媒体回铃音服务器向该 主叫终端播放多媒体回铃音, 避免了对终端进行协议层面的改造, 使得可 视电话的多媒体彩铃业务的实现, 对终端的影响能够减小到最小程度。 附图说明
图 1是根据本发明第一实施例的可视电话呼叫方法的网络结构示意图; 图 2是根据本发明第一实施例的可视电话呼叫方法流程图;
图 3是根据本发明第二实施例的可视电话呼叫方法流程图;
图 4是根据本发明第三实施例的可视电话呼叫方法流程图;
图 5是根据本发明第四实施例的可视电话呼叫方法流程图;
图 6是根据本发明第五实施例的可视电话呼叫方法流程图;
图 7是根据本发明第六实施例的可视电话呼叫方法流程图;
图 8是根据本发明第七实施例的可视电话呼叫方法的网络结构示意图; 图 9是根据本发明第七实施例的可视电话呼叫方法流程图;
图 10是根据本发明第八实施例的可视电话呼叫方法流程图;
图 11是根据本发明第九实施例的可视电话呼叫方法流程图;
图 12是根据本发明第十一实施例的可视电话呼叫***结构示意图; 图 13是根据本发明第十二实施例的可视电话呼叫***结构示意图。 具体实施方式
为使本发明的目的、 技术方案和优点更加清楚, 下面将结合附图对本 发明的实施方式作进一步地详细描述。
本发明的第一实施例涉及一种可视电话呼叫方法, 在本实施例中, 多 媒体回铃音服务器通过在主叫终端与多媒体回铃音服务器之间建立的可视 电话的第一承载, 向该主叫终端播放多媒体回铃音。 当检测到被叫终端摘 机后, 在该被叫终端与该多媒体回铃音服务器之间建立可视电话的第二承 载, 通过所建立的第一承载和第二承载, 在该主叫终端和该被叫终端之间 进行可视电话通信。
本实施例的网络结构如图 1所示,包含移动交换中心(Mobile Switching
Center, 简称" MSC" )服务器、 媒体网关 (Media Gateway, 简称" MGW" )、 拜访位置寄存器(Visitor Location Register, 简称" VLR" )、 无线网络控制器 ( Radio Network Controller, 简称" RNC" )、 基站节点 ( Node Base Station, 简称" Node B,,)、 归属位置寄存器(Home Location Register, 简称 "HLR,,)、 鉴权中心 (Authentication Center, 简称" AuC,,)、 提供多媒体回铃音的多媒 体回铃音服务器等网元,以及主、被叫终端。其中, MSC服务器可以与 VLR
集成在一起, 为合一网元, MSC服务器与 MGW之间通过 H.248过程建立 连接, HLR可以与 AuC集成在一起, 为合一网元。 (AuC在实际的布网的 情况下可能不存在)。 具体流程如图 2所示, 包括如下步骤:
步骤 201 , 主叫终端即用户设备(User Equipment, 简称" UE" ) A向附 着的 MSC服务器 A发 SETUP (建立 )消息, 消息中携带的 BC— IE信元中 ITC为' UDI,, (ORA, Other Rate Adaptation) 为 Ή.223&Η.245,。
步骤 202, MSC服务器 A向被叫终端即 UE B的 HLR B发起发送路由 信息 (Send Routing Info, 简称" SRI" )请求, 查询路由信息。
步骤 203 , HLR B向 UE B附着的 MSC服务器 B发送请求提供漫游号 码( Provide Roaming Number, 简称" PRN" ) 的消息, 请求该 UE B的移动 台漫游号码( Mobile Station Roaming Number, 简称" MSRN" )。
步骤 204, MSC服务器 B向 HLR B返回该 UE B的 MSRN,如果 MSC 服务器 B支持预寻呼,这时会先发起预寻呼过程后再返回该 UE Β的 MSRN。
步骤 205, HLR B向 MSC服务器 A返回 UE B的路由信息(即该 UE B 的 MSRN ), 并携带被叫用户 (即使用 UE B的用户 )是否定制多媒体彩铃 业务的信息。
步骤 206, MSC服务器 A获得 UE B 的 MSRN后, 向 UE A发起 Call— Proceeding (呼叫过程)。
步骤 207, MSC服务器 A向多媒体回铃音服务器发起 ISUP IAM消息 (综合业务数字网用户部分起始地址消息)。 如果被叫用户签约了主叫号码 显示业务,则该 ISUP IAM消息中需要携带主叫号码和业务前缀信息。其中, 多媒体回铃音服务器是为可视电话用户提供多媒体彩铃的***, 具备多媒 体彩铃存储、播放和管理能力, 并且支持无关呼叫控制( Bearer Independent Call Control, 简称" BICC" ) /综合业务数字网用户部分( ISDN User Part, 简 称 "ISUP" )协议。 在被叫用户申请多媒体彩铃业务后, 该服务器应可以为 主叫终端提供多媒体彩铃的播放, 并在被叫用户接听时可以自动中断该多 媒体彩铃的播放。
步骤 208,多媒体回铃音服务器向 MSC服务器 B发起 ISUP IAM消息。 如果被叫用户签约了主叫号码显示业务,则该 ISUP IAM消息中需要携带主
叫号码。
步骤 209, 如果 MSC服务器 B在向 HLR B返回 UE B的 MSRN前没 有发起预寻呼过程, 则在本步骤中, 该 MSC服务器 B向 UE B发起寻呼请 求消息。
步骤 210, UE B向该 MSC服务器 B返回寻呼响应消息。
步骤 211 , MSC服务器 B向 UE B发送 SETUP消息, 消息中携带的 BC— IE信元中 ITC为, UDI,, ORA为 Ή.223&Η.245,。
步骤 212, UE Β向该 MSC服务器 Β返回 CALL CONFIRMED (呼叫 确认) 消息, 没有携带新的 BC— IE, 表示能够支持可视电话的被叫。 此时, 该 UE B开始振铃。
步骤 213 , UE B振铃后, UE B向 MSC服务器 B返回 Alerting消息。 步骤 214, MSC 服务器 B 向多媒体回铃音服务器发送地址完成消息 ( Address Complete Message , 简称" ACM" )。
步骤 215 , 多媒体回铃音服务器在接收到 MSC服务器 B发来的 ACM 后, 向 MSC服务器 A发送携带彩铃信息的 ACM。
步骤 216, MSC服务器 A识别该彩铃信息, 发送 Alerting给 UE A。 步骤 217 ,多媒体回铃音服务器向 MSC服务器 A发送应答消息( Answer Message, 简称" ANM" )消息, 触发 MSC服务器 A发送 Connect消息给 UE A。 该 ANM消息是从多媒体回铃音服务器向 MSC服务器 A发送的 ANM 信号, 表示可以进行建立多媒体回铃音服务器和 UE A之间的通话, 并用来 触发 Connect消息。 在本实施例当中本步骤为可选步骤, 具体的选择, 取决 于实际的需要。 需要说明的是, MSC服务器 A也可以在收到来自多媒体回 铃音服务器的携带彩铃信息的 ACM后, 向 UE A发送 Connect消息。 也就 是说, Connect消息的发送, 也可以不通过 ANM消息来触发。
步骤 218 , UE A在接收到 Connect消息后,向 MSC服务器 A发送 Connect
ACK (连接响应 ) 消息。
步骤 219, UE A和多媒体回铃音服务器之间通过可视电话信令协议过 程, 建立可视电话的第一承载。 该可视电话信令协议可以是 H.324、 H.323 或会话发起协议(Session Initiation Protocol, 简称" SIP" ) 的可视电话信令
协议。 本实施例以 H.323 中的 H.245过程建立可视电话的第一承载为例进 行说明。
步骤 220, UE A通过多媒体回铃音服务器收看视频彩铃。
步骤 221 , UE B完成摘机动作之后, 向 MSC服务器 B发送 Connect 消息。 被叫应答过程开始。
步骤 222, MSC服务器 B向多媒体回铃音服务器发送 ANM消息。 步骤 223 , MSC服务器 B向 UE B发送 Connect— ACK (连接响应 ) 消 息。
步骤 224, 多媒体回铃音服务器向 MSC服务器 A发送 ANM消息, 此 时 UE A附着的 MSC服务器 A对可视电话通信开始计费。 由于是在检测到 UE B摘机后再对可视电话通信进行计费的, 因此可使得在多媒体彩铃业务 的实现过程中, 能够对通话时长进行精确计算和控制。 此时, MSC服务器 A可以向 UE A发送 Connect信令。需要说明的是,在实际应用中, MSC服 务器 A也可以不向 UE A发送 Connect信令或即使发送 Connect消息, UE A 也不处理 Connect消息, 也就是说, 此时 Connect消息的发送与否为可选步 骤。 如果 UE A收到了该 Connect消息并且选择处理该 Connect消息, 则该 UE A可以向 MSC服务器 A回复一个 Connect— ACK响应消息,当然也可以 不回复任何的消息。
步骤 225, 多媒体回铃音服务器和 UE B之间通过多媒体通信控制信令 协议 H.245过程, 建立可视电话的第二承载。
步骤 226 , 通过 UE A和多媒体回铃音服务器之间建立的可视电话的第 一承载, 与 UE B和多媒体回铃音服务器之间建立的可视电话的第二承载, 在该 UE A与 UE B之间进行第三代移动通信 ( The Third Generation, 简称 "3G" ) 电路域的可视电话通信。
不难发现, 在本实施例中, 多媒体彩铃业务可以基于现有的可视电话 的网络框架上得以实现。 而且, 由多媒体回铃音服务器向该主叫终端播放 多媒体回铃音, 避免了对终端进行协议层面的改造, 使得可视电话的多媒 体彩铃业务的实现, 对终端的影响能够减小到最小程度。 另外, UE A和 UE B分别只需与多媒体回铃音服务器建立一次可视电话承载,呼叫接通后,
UE A和 UE B通过多媒体回铃音服务器完成可视电话。 而且, 本实施例对 MSC服务器与终端的改造都较小, 易于实现。
需要说明的是, 本实施例中步骤 218和步骤 223中的 Connect ACK消 息是用来对 Connect消息进行确认的, 可以存在, 也可以不存在, 具体的选 择, 取决于实际的需要。
本发明的第二实施例涉及一种可视电话呼叫方法, 本实施例与第一实 施例大致相同,其区别在于,在第一实施例中, MSC服务器 A通过向 UE A 发送 Connect消息(如步骤 217 ), 通知 UE A建立可视电话的第一承载。 而 在本实施例中, MSC服务器 A在向 UE A发送 Alerting消息后, 不向 UE A 发送如步骤 217所示的 Connect消息 (如图 3所示 ), 而是在发送给 UE A 的 Alerting消息中携带业务标识。 比如说, 通过 Alerting消息中的信息元素 "User - User"携带标识多媒体彩铃业务的特殊文本, 以便 UE A能够识别是 否将要开始接收多媒体彩铃,如果 Alerting消息中没有携带该业务标识, 则 按正常流程开始可视电话的通信; 如果 Alerting消息中携带有该业务标识, 则建立可视电话的第一承载。
另外, MSC服务器 A在被叫终端 UE B摘机后, 并且收到了来自多媒 体回铃音服务器的 ANM消息 (即第一实施例中的步骤 224 ) 时, 该 MSC 服务器 A向 UE A发送 Connect消息, 如图 3所示。
通过在 Alerting消息中携带业务标识,可使得不支持多媒体彩铃业务的 终端收到该 Alerting消息后,也不会对正常接续造成影响, 灵活地兼容了不 支持多媒体彩铃业务的终端。 另外, UE A收到 Alerting消息之后还需要启 动 3G-324M协议交互,同时要求网络在此时能够建立电路交换数据( Circuit Switch Data, 简称" CSD" ) 64电路链路, 以便后续流程的迅速进行。
本发明的第三实施例涉及一种可视电话呼叫方法, 本实施例与第一实 施例大致相同, 其区别在于, 在第一实施例中, 网络侧无需通知主叫终端 (即 UE A )相关的可视电话通话时长的计费信息, 而在本实施例中, 网络 侧在检测到被叫终端 (即 UE B )摘机之前, 通过向该被叫终端发送表示网 络侧尚未开始计费的 "Facility"消息, 通知该主叫终端忽略计费或计时; 在 检测到该被叫终端摘机后, 通过向该被叫终端发送表示网络侧开始计费的
"Facility"消息, 通知该主叫终端开始计费或计时。 为描述方便, 下文中将 第一条" Facility"消息称为 "Facility"消息 FA, 将第二条" Facility"消息称为 "Facility"消息 FB。
具体流程如图 4所示,步骤 401至步骤 420分别与步骤 201至步骤 220 完全相同, 在此不再赘述。
在步骤 421 中, MSC服务器 A或多媒体回铃音服务器向 UE A发送 "Facility"消息 FA, 通知 UE A这不是一次正常通话, 网络侧尚未开始计费。
步骤 422至步骤 425分别与步骤 221至步骤 224完全相同, 在此不再 赘述。
在步骤 426中, MSC服务器 A或多媒体回铃音服务器向 UE A发送
"Facility"消息 FB , 通知 UE A正常通话开始, 网络侧开始计费。
由于在正常的可视电话的过程当中, UE A在收到步骤 417中的 Connect 消息之后, 将会建立可视电话的承载, 这个时候, UE A会向用户显示: "可 视电话通话中,,,一般情况下,还会附加可视电话的通话时间,如" 00:19,,等。 而多媒体彩铃业务属于在可视电话技术基础之上的叠加业务, 因此, 如果 不对 UE进行任何的改造的话,可视电话应用会认为多媒体彩铃业务的过程 也是可视电话通话的过程, 因此, 会在播放多媒体回铃音的过程当中显示 "可视电话通话中 "以及相关的计时信息。
为了避免用户对计费信息产生误解, 同时尽可能的减小业务对可视电 话应用的修改, 让正常的可视电话通信不受影响, UE可以在收到步骤 417 中的 Connect消息之后, 仍按照正常的情况进行计时,但在收到表示网络侧 尚未开始计费的消息, 即" Facility"消息 FA后, 可向用户显示表示网络侧尚 未开始计费的信息。 比如说, 将显示的计时信息进行归零处理, 并且在屏 幕上显示"正在播放回铃音, 尚未开始计费,,等信息,通知用户网络侧尚未开 始计费。在 UE收到表示网络侧开始计费的消息, 即" Facility"消息 FB之后, 让可视电话应用开始对可视电话进行计时 /计费, 并且显示可视电话进行中 等类似的字样。
由于步骤 417中的 Connect消息是可选的, 因此在 UE未收到***侧下 发的 Connect消息, 该 Connect消息的功能被其他的信令消息所替代时, 该
UE在收到替代 Connect消息功能的信令的时候, 将会按照多媒体彩铃的方 式进行显示, 即显示正在播放回铃音等类似的字样, 计时信息不显示, 或 者显示为" 00:00"。 在收到 Connect 消息之后, 按照正常的可视电话显示过 程显示所有内容。
步骤 427和步骤 428分别与步骤 225和步骤 226完全相同, 在此不再 赘述。
需要说明的是, 本实施例中步骤 418和步骤 424中的 Connect ACK消 息可以存在, 也可以不存在, 具体的选择, 取决于实际的需要。 另外, 步 骤 421中的" Facility"消息 FA除了可以在如图 4所示的位置外,也可以位于 步骤 416之后的步骤 425之前的任意一个位置。
在本实施例的步骤 425中, MSC服务器 A可以向 UE A发送 Connect 消息, 也可以不发送该消息, 如果 MSC服务器 A发送该 Connect消息, 则 将在收到来自多媒体回铃音服务器发送的 ANM之后, 再向 UE A发送该 Connect消息, UE A可以处理这个消息, 也可以不对这个消息进行任何的 处理。
不难发现, 本实施例中步骤 421和步骤 426的主要作用在于, 提示主 叫终端是否真正的可视电话已经开始。 使得该主叫终端能够准确地获知网 络侧计算的通话时长, 以免该主叫终端的用户对计费信息产生误解, 解决 在播放多媒体彩铃过程中终端开始计时的问题。
值得一提的是, 在本实施例中, MSC服务器 A还可以在步骤 416或步 骤 417中, 通过下发给 UE A的 Alerting消息或 Connect消息, 将本次振铃 是否会触发多媒体彩铃的播放的信息发送给 UE A, 以便 UE A能够据此准 确计时。 比如说, 如果消息中没有此信息, 则 UE A按照原有正常方式启动 计时。 如果消息中有此信息, 则 UE A将不会在收到第一个 Connect消息时 启动计时, 而是等待后续网络发送指示启动计时的消息, 在收到指示启动 计时的消息后, 再启动计时。
本次振铃是否会触发多媒体彩铃的播放的信息可以通过消息中的 facility字段来扩展实现, 也可以通过 Connect消息当中的 User-User字段的 扩展来实现。 比如说, 如果在 Connect消息中 User-User字段的值为 1 , 则
指示 UE A在收到第一个 Connect消息时不计时;在 Connect消息中 User-User 字段的值为 0 , 则指示 UE A按照原有正常方式启动计时。
不难发现, 如果下发给 UE A的 Alerting消息或 Connect消息中, 携带 本次振铃是否会触发多媒体彩铃的播放的信息, 则等同于已经执行了步骤 421 , 因此" Facility"消息 FA的发送就可以省略, 但是仍需发送 "Facility"消 息 FB , 该" Facility"消息 FB即作为上述指示启动计时的消息。
本发明的第四实施例涉及一种可视电话呼叫方法, 本实施例与第一实 施例大致相同, 其区别在于, 在第一实施例中, 网络侧无需通知主叫终端 (即 UE A )相关的可视电话通话时长的计费信息, 而在本实施例中, 网络 侧在检测到被叫终端 (即 UE B )摘机之前 , 通过向该被叫终端发送表示网 络侧尚未开始计费的短消息业务(Short Message Service, 简称" SMS" ) 消 息, 通知该主叫终端忽略计费或计时; 在检测到该被叫终端摘机后, 通过 向该被叫终端发送表示网络侧开始计费的 SMS消息, 通知该主叫终端开始 计费或计时。 为描述方便, 下文中将第一条 SMS消息称为 SMS消息 SA, 将第二条 SMS消息称为 SMS消息 SB。
具体流程如图 5所示,步骤 501至步骤 520分别与步骤 201至步骤 220 完全相同, 在此不再赘述。
在步骤 521中, MSC服务器 A向 UE A发送 SMS消息 SA,通知 UE A 这不是一次正常通话, 网络侧尚未开始计费。 UE A在收到该 SMS消息 A 后, 可向用户显示表示网络侧尚未开始计费的信息。 比如说, 在屏幕上显 示"正在播放回铃音,尚未开始计费 "等信息,通知用户网络侧尚未开始计费。
步骤 522至步骤 525分别与步骤 221至步骤 224完全相同, 在此不再 赘述。
在步骤 526中, MSC服务器 A向 UE A发送 SMS消息 SB,通知 UE A 正常通话开始, 网络侧开始计费。
步骤 521与步骤 526中 SMS消息的发送实际上是一个逻辑的过程, 在 实际实现当中可以是 MSC服务器 A发送 SMS , 也可以是和短信网关之类 的辅助设备相配合发送。 在本实施例中, MSC服务器 A发送 SMS的含义 在于, SMS消息通过某个设备触发, 然后经由 MSC服务器 A发送。
步骤 527和步骤 528分别与步骤 225和步骤 226完全相同, 在此不再 赘述。
需要说明的是, 本实施例中步骤 518和步骤 524中的 Connect ACK消 息可以存在, 也可以不存在, 具体的选择, 取决于实际的需要。 另外, 步 骤 521中的 SMS消息 A除了可以在如图 5所示的位置外,也可以位于步骤 516之后的步骤 525之前的任意一个位置。
在本实施例的步骤 525中, MSC服务器 A可以向 UE A发送 Connect 消息, 也可以不发送该消息, 如果 MSC服务器 A发送该 Connect消息, 则 将在收到来自多媒体回铃音服务器发送的 ANM之后, 再向 UE A发送该 Connect消息, UE A可以处理这个消息, 也可以不对这个消息进行任何的 处理。
不难发现, 本实施例中步骤 521和步骤 526的主要作用在于, 提示主 叫终端是否真正的可视电话已经开始。 使得该主叫终端能够准确地获知网 络侧计算的通话时长, 以免该主叫终端的用户对计费信息产生误解, 解决 在播放多媒体彩铃过程中终端开始计时的问题。 由于 SMS是一种终端常见 的通信方式, 因此可以通过 SMS携带的内容表示网络侧尚未开始计费或开 始计费的信息。 在 SMS中携带何种内容来表示相应的信息可以根据事先的 约定, 比如说,可以利用 SMS消息携带的" MRBT Begin"表示可视电话尚未 开始, 目前是多媒体彩铃业务, 主叫终端接收到该 SMS消息之后, 会认为 目前的会话为多媒体彩铃会话, 不将当前会话作为可视电话的通话进行处 理; 可以利用 SMS消息携带的" VP Begin"作为可视电话开始的标志, 主叫 终端接收到该 SMS消息之后, 会认为目前的会话为可视电话的通话, 当前 会话将作为正常可视电话的通话进行处理。 SMS 消息可以携带不同的内容 和信息, 因此 SMS消息所表示的信息可能会有所不同, 这个取决于事先的 约定。
另外, 值得一提的是, 本实施例中, 是以通过 SMS消息通知主叫终端 网络侧是否已经开始计费为例进行说明的, 在实际应用中, 也可以通过其 它的方式来通知该主叫终端, 如多媒体消息业务 ( Multimedia Message Services , 简称" MMS" )、 电子函件 ( Electronic mail , 简称 "E-mail" )、 即时
送信业务( Instant Messenger, 简称" IM" ), 推消息( Push Message )等, 具 体实现方式与本实施例类似, 在此不再赘述。
需要说明的是, 在本实施例中, MSC服务器 A还可以在步骤 516或步 骤 517中, 通过下发给 UE A的 Alerting消息或 Connect消息, 将本次振铃 是否会触发多媒体彩铃的播放的信息发送给 UE A, 以便 UE A能够据此准 确计时。 比如说, 如果消息中没有此信息, 则 UE A按照原有正常方式启动 计时。 如果消息中有此信息, 则 UE A将不会在收到第一个 Connect消息时 启动计时, 而是等待后续网络发送指示启动计时的消息, 在收到指示启动 计时的消息后, 再启动计时。
本次振铃是否会触发多媒体彩铃的播放的信息可以通过消息中的 facility字段来扩展实现, 也可以通过 Connect消息当中的 User-User字段的 扩展来实现。 比如说, 如果在 Connect消息中 User-User字段的值为 1 , 则 指示 UE A在收到第一个 Connect消息时不计时;在 Connect消息中 User-User 字段的值为 0 , 则指示 UE A按照原有正常方式启动计时。
不难发现, 如果下发给 UE A的 Alerting消息或 Connect消息中, 携带 本次振铃是否会触发多媒体彩铃的播放的信息, 则等同于已经执行了步骤 521 , 因此 SMS消息 A的发送就可以省略, 但是仍需发送 SMS消息 SB, 该 SMS消息 SB即作为上述指示启动计时的消息。
本发明的第五实施例涉及一种可视电话呼叫方法, 本实施例与第一实 施例大致相同, 其区别在于, 在第一实施例中, 网络侧无需通知主叫终端 (即 UE A )相关的可视电话通话时长的计费信息, 而在本实施例中, 网络 侧在检测到被叫终端 (即 UE B )摘机之前, 通过向该被叫终端发送表示网 络侧尚未开始计费的 H.245的命令 ( Command )或指示(Indication )消息, 通知该主叫终端忽略计费或计时; 在检测到该被叫终端摘机后, 通过向该 被叫终端发送表示网络侧开始计费的 H.245 的命令或指示消息, 通知该主 叫终端开始计费或计时。 为描述方便, 下文中将第一条 H.245 的命令或指 示消息称为 H.245的命令或指示消息 A,将第二条 H.245的命令或指示消息 称为 H.245的命令或指示消息 HB。
具体流程如图 6所示,步骤 601至步骤 620分别与步骤 201至步骤 220
完全相同, 在此不再赘述。
在步骤 621中,多媒体回铃音服务器向 UE A发送 H.245的命令或指示 消息 A, 通知 UE A这不是一次正常通话, 网络侧尚未开始计费。 UE A在 收到该 H.245的命令或指示消息 HA后,可向用户显示表示网络侧尚未开始 计费的信息。 比如说, 在屏幕上显示"正在播放回铃音, 尚未开始计费 "等信 息, 通知用户网络侧尚未开始计费。
步骤 622至步骤 625分别与步骤 221至步骤 224完全相同, 在此不再 赘述。
在步骤 626中,多媒体回铃音服务器向 UE A发 H.245的命令或指示消 息 HB, 通知 UE A正常通话开始, 网络侧开始计费。
步骤 627和步骤 628分别与步骤 225和步骤 226完全相同, 在此不再 赘述。
需要说明的是, 本实施例中步骤 618和步骤 624中的 Connect ACK消 息可以存在, 也可以不存在, 具体的选择, 取决于实际的需要。 另外, 步 骤 621中的 H.245的命令或指示消息 HA,除了可以在如图 6所示的位置外, 也可以位于步骤 619之后的步骤 625之前的任意一个位置。
在本实施例的步骤 625中, MSC服务器 A可以向 UE A发送 Connect 消息, 也可以不发送该消息, 如果 MSC服务器 A发送该 Connect消息, 则 将在收到来自多媒体回铃音服务器发送的 ANM之后, 再向 UE A发送该 Connect消息, UE A可以处理这个消息, 也可以不对这个消息进行任何的 处理。
不难发现, 本实施例中步骤 621和步骤 626的主要作用在于, 提示主 叫终端是否真正的可视电话已经开始。 使得该主叫终端能够准确地获知网 络侧计算的通话时长, 以免该主叫终端的用户对计费信息产生误解, 解决 在播放多媒体彩铃过程中终端开始计时的问题。 由于整个多媒体彩铃的开 展过程都是需要 H.245的支持, 因此可以通过 H.245的命令或指示消息来 表示网络侧尚未开始计费或开始计费的信息。 釆用何种 H.245 的命令或指 示消息来表示相应的信息可以根据事先的约定, 比如说, H.245 中 USER INPUT的 Indication (指示) 消息釆用如下的格式:
Indication Message: user input
Userlnputlndication ::=CHOICE nonstandard NonStandardParameter,
alphanumeric General String,
则可以在 USER INPUT的 Indication消息当中的 "GeneralString"字段携 带 10000 来表示可视电话尚未开始, 目前是多媒体彩铃业务, 主叫终端接 收到该消息之后, 会认为目前的会话为多媒体彩铃会话, 不将当前会话作 为可视电话的通话进行处理;可以在 USER INPUT的 Indication消息当中的 "GeneralString"字段携带 10001来表示多媒体彩铃业务结束,可视电话开始, 主叫终端接收到该消息之后, 会认为目前的会话为可视电话的通话, 当前 会话将作为正常可视电话的通话进行处理。 由于 USER INPUT的 Indication 消息可以携带各种各样的数据, 上述方案仅是一种可能的方式和取值。
如果以 H.245 Command 消息为例, 则 H.245 Command 消息 A还可以 通过用户推指示(USER INPUT Indication , 简称 "UII")传送双音多频 ( Dualtone multifrequency, 简称" DTMF" ) a信号, 指示 UE Α停止终端计 时, UE A收到此消息后, 停止计时, 将计时器清零, 并提示用户将进行多 媒体彩铃播放。 H.245 Command 消息 b可以通过传送 DTMF B信号, 指示 UE A开始计时, UE A收到此消息后, 开始计时, 并提示用户开始正常通 信。
具体的实现过程当中还可能釆用其他的 H.245 的命令、 指示、 或者其 他的消息。 具体实现方式与本实施例类似, 在此不再赘述。
需要说明的是, 在本实施例中, MSC服务器 A还可以在步骤 616或步 骤 617中, 通过下发给 UE A的 Alerting消息或 Connect消息, 将本次振铃 是否会触发多媒体彩铃的播放的信息发送给 UE A, 以便 UE A能够据此准 确计时。 比如说, 如果消息中没有此信息, 则 UE A按照原有正常方式启动 计时。 如果消息中有此信息, 则 UE A将不会在收到第一个 Connect消息时
启动计时, 而是等待后续网络发送指示启动计时的消息, 在收到指示启动 计时的消息后, 再启动计时。
本次振铃是否会触发多媒体彩铃的播放的信息可以通过消息中的 facility字段来扩展实现, 也可以通过 Connect消息当中的 User-User字段的 扩展来实现。 比如说, 如果在 Connect消息中 User-User字段的值为 1 , 则 指示 UE A在收到第一个 Connect消息时不计时;在 Connect消息中 User-User 字段的值为 0, 则指示 UE A按照原有正常方式启动计时。
不难发现, 如果下发给 UE A的 Alerting消息或 Connect消息中, 携带 本次振铃是否会触发多媒体彩铃的播放的信息, 则等同于已经执行了步骤 621 , 因此 H.245 命令或指示消息 HA 的发送就可以省略, 但是仍需发送 H.245 命令或指示消息 HB,该 H.245 命令或指示消息 HB即作为上述指示 启动计时的消息。
本发明的第六实施例涉及一种可视电话呼叫方法, 本实施例与第一实 施例大致相同, 其区别在于, 在第一实施例中, 网络侧无需通知主叫终端 (即 UE A )相关的可视电话通话时长的计费信息, 而在本实施例中, 网络 侧在检测到被叫终端 (即 UE B )摘机之前, 通过向该被叫终端发送表示网 络侧尚未开始计费的非结构的补充业务数据 ( Unstructured Supplementary Service Data, 简称" USSD" )信号, 通知该主叫终端忽略计费或计时; 在检 测到该被叫终端摘机后, 通过向该被叫终端发送表示网络侧开始计费的 USSD信号, 通知该主叫终端开始计费或计时。 为描述方便, 下文中将第一 条 USSD信号称为 USSD信号 A, 将第二条 USSD信号称为 USSD信号 B。
具体流程如图 7所示,步骤 701至步骤 720分别与步骤 201至步骤 220 完全相同, 在此不再赘述。
在步骤 721中, MSC服务器 A向 UE A发送 USSD信号 A,通知 UE A 这不是一次正常通话, 网络侧尚未开始计费。 UE A在收到该 USSD信号 A 后, 可向用户显示表示网络侧尚未开始计费的信息。 比如说, 在屏幕上显 示"正在播放回铃音,尚未开始计费 "等信息,通知用户网络侧尚未开始计费。
步骤 722至步骤 725分别与步骤 221至步骤 224完全相同, 在此不再 赘述。
在步骤 726中, MSC服务器 A向 UE A发 USSD信号 B, 通知 UE A 正常通话开始, 网络侧开始计费。
步骤 727和步骤 728分别与步骤 225和步骤 226完全相同, 在此不再 赘述。
需要说明的是, 本实施例中步骤 718和步骤 724中的 Connect ACK消 息可以存在, 也可以不存在, 具体的选择, 取决于实际的需要。 另外, 步 骤 721中的 USSD信号 A, 除了可以在如图 7所示的位置外, 也可以位于 步骤 716之后的步骤 725之前的任意一个位置。
在本实施例的步骤 725中, MSC服务器 A可以向 UE A发送 Connect 消息, 也可以不发送该消息, 如果 MSC服务器 A发送该 Connect消息, 则 将在收到来自多媒体回铃音服务器发送的 ANM之后, 再向 UE A发送该 Connect消息, UE A可以处理这个消息, 也可以不对这个消息进行任何的 处理。
不难发现, 本实施例中步骤 721和步骤 726的主要作用在于, 提示主 叫终端是否真正的可视电话已经开始。 使得该主叫终端能够准确地获知网 络侧计算的通话时长, 以免该主叫终端的用户对计费信息产生误解, 解决 在播放多媒体彩铃过程中终端开始计时的问题。 由于 USSD是一种终端常 见的通信方式, 因此可以通过 USSD信号携带表示网络侧尚未开始计费或 开始计费的信息。 釆用何种 USSD信号来表示相应的信息可以根据事先的 约定, 比如说, 可以利用 USSD信号携带的一个表示彩铃开始的标志, 指 示主叫终端目前是多媒体彩铃业务, 该主叫终端接收到该 USSD信号之后, 会认为目前的会话为多媒体彩铃会话, 不将当前会话作为可视电话的通话 进行处理; 可以利用 USSD信号携带的一个表示可视电话开始的标志, 指 示主叫终端可视电话开始, 终端接收到该 USSD信号之后, 会认为目前的 会话为可视电话的通话, 当前会话将作为正常可视电话的通话进行处理。 不同的 USSD信号表示的信息会有所不同, 这个取决于事先的约定。
另外, 值得一提的是, 本实施例中, 是以通过 USSD信号通知主叫终 端网络侧是否已经开始计费为例进行说明的, 在实际应用中, 也可以通过 其它的信令方式来通知该主叫终端, 比如说,可以是会话发起协议(Session
Initation Protocol , 简称" SIP" )、 超文本传输协议 (Hyper Text Transfer Protocol, 简称' ΉΤΤΡ,,)、 实时流协议( Realtime Streaming Protocol, 简称 "RTSP" )信令等等。 具体实现方式与本实施方式类似, 不同的仅仅是底层 的链路存在区别, 在此不再赘述。
需要说明的是, 在本实施例中, MSC服务器 A还可以在步骤 716或步 骤 717中, 通过下发给 UE A的 Alerting消息或 Connect消息, 将本次振铃 是否会触发多媒体彩铃的播放的信息发送给 UE A, 以便 UE A能够据此准 确计时。 比如说, 如果消息中没有此信息, 则 UE A按照原有正常方式启动 计时。 如果消息中有此信息, 则 UE A将不会在收到第一个 Connect消息时 启动计时, 而是等待后续网络发送指示启动计时的消息, 在收到指示启动 计时的消息后, 再启动计时。
本次振铃是否会触发多媒体彩铃的播放的信息可以通过消息中的 facility字段来扩展实现, 也可以通过 Connect消息当中的 User-User字段的 扩展来实现。 比如说, 如果在 Connect消息中 User-User字段的值为 1 , 则 指示 UE A在收到第一个 Connect消息时不计时;在 Connect消息中 User-User 字段的值为 0 , 则指示 UE A按照原有正常方式启动计时。
不难发现, 如果下发给 UE A的 Alerting消息或 Connect消息中, 携带 本次振铃是否会触发多媒体彩铃的播放的信息, 则等同于已经执行了步骤 721 , 因此 USSD信号 A的发送就可以省略, 但是仍需发送 USSD信号 B , 该 USSD信号 B即作为上述指示启动计时的消息。
本发明的第七实施例涉及一种可视电话呼叫方法, 在本实施例中, 多 媒体回铃音服务器通过在主叫终端与多媒体回铃音服务器之间建立的可视 电话的第三承载, 向该主叫终端播放多媒体回铃音。 该主叫终端和被叫终 端之间建立可视电话的第四承载, 通过该第四承载在该主叫终端和被叫终 端之间进行可视电话通信。 该第三承载和第四承载为通过 H.324、 H.323、 或 SIP的可视电话协议建立的可视电话通信链路,本实施例中以 H.323中的 H.245过程建立该第三承载和第四承载为例进行说明。
本实施例的网络结构如图 8 所示, 不同的区域建立不同的多媒体回铃 音服务器, MSC服务器仍与 VLR集成在一起, 为合一网元, MSC服务器
仍与 MGW之间通过 H.248过程建立连接, HLR仍与 AuC集成在一起, 为 合一网元。 具体流程如图 9所示。
步骤 901 ,主叫终端即 UE A向附着的 MSC服务器 A发 SETUP(建立 ) 消息, 消息中携带的 BC— IE信元中 ITC为,UDI,, ORA为 'H.223&H.245'。
步骤 902中, MSC服务器 A向被叫终端即 UE B的 HLR B发起发 SRI 请求。
步骤 903中, HLR B向 UE B附着的 MSC服务器 B取该 UE B的移动 台漫游号码 MSRN。
步骤 904中, MSC服务器 B向 HLR B返回该 UE B的 MSRN, 如果 MSC服务器 B支持预寻呼, 这时会先发起预寻呼过程后再返回该 UE B的 MSRN。
步骤 905中, HLR B向 MSC服务器 A返回 UE B的路由信息 (即该 UE B的 MSRN ), 并携带被叫用户 (即使用 UE B的用户)是否定制多媒体 彩铃业务的信息。
步骤 906中, MSC服务器 A获得 UE B的 MSRN后, 向 UE A发起
Call— Proceeding (呼叫过程)。
步骤 907中, MSC服务器 A向 MSC服务器 B发起 ISUP IAM消息。 如果被叫用户签约了主叫号码显示业务,则该 ISUP IAM消息中需要携带主 叫号码。
步骤 908中, 如果 MSC服务器 B在向 HLR B返回 UE B的 MSRN前 没有发起预寻呼过程, 则在本步骤中, 该 MSC服务器 B向 UE B发起寻呼 请求消息。
步骤 909中, UE B向该 MSC服务器 B返回寻呼响应消息。
步骤 910中, MSC服务器 B向 UE B发送 SETUP消息, 消息中携带 的 BC— IE信元中 ITC为, UDI,, ORA为 Ή.223&Η.245,。
步骤 911中, UE Β向该 MSC服务器 Β返回 CALL CONFIRMED (呼 叫确认) 消息, 没有携带新的 BC— IE, 表示能够支持可视电话的被叫。
步骤 912中, UE B振铃后, UE B向 MSC服务器 B返回 Alerting消息。 步骤 913中, MSC服务器 B向 MSC服务器 A返回 BICC ACM消息。
步骤 914中, MSC服务器 A向 UE A返回 Alerting消息。
接步骤 915中, MSC服务器 A向多媒体回铃音服务器发起 BICC IAM 消息, 携带 UE B是否定制多媒体彩铃业务的信息。
步骤 916中, 多媒体回铃音服务器向 MSC服务器 A返回 BICC ACM 消息。 MSC服务器 A识别该多媒体回铃音服务器发来的 ACM消息, 并且, 不向主叫终端发送 Alerting消息。
步骤 917中, 多媒体回铃音服务器向 MSC服务器 A发送 BICC ANM 消息。 MSC服务器 A在收到该 BICC ANM消息后, 向主叫终端 UE A发送 连接信令 CONNECT, 同时监听 MSC服务器 B是否有返回消息。 该 ANM 消息表示可以进行建立多媒体回铃音服务器和 UE A之间的通话,并用来触 发 Connect消息。 在本实施例当中本步骤为可选步骤, 具体的选择, 取决于 实际的需要。
步骤 918中, UE A在接收到 Connect消息后, 向 MSC服务器 A发送 Connect ACK (连接响应) 消息。
步骤 919中, UE A和多媒体回铃音服务器之间通过多媒体通信控制信 令协议 H.245 过程, 建立可视电话的第三承载。 并在该可视电话的第三承 载建立完成后, 收看多媒体回铃音服务器播放的多媒体彩铃信息。
步骤 920中, 被叫终端 UE B发送应答消息 CONNECT给 MSC服务器
B。
步骤 921中, MSC服务器 B向 MSC服务器 A返回 BICC ANM消息。 步骤 922中, MSC服务器 B向 UE B返回连接确认 CONNECT ACK消 息。
步骤 923中, MSC服务器 A向多媒体回铃音服务器发送 BICC Release ( BICC释放)消息, 指示拆除该多媒体回铃音服务器和 UE A之间建立的 第三承载。
步骤 924中,该多媒体回铃音服务器和 UE A之间拆除所建立的可视电 话的第三承载。
步骤 925中,该多媒体回铃音服务器向 MSC服务器 A返回 BICC Release Complete ( BICC释放完成) 消息。
步骤 926中, UE A和 UE B之间通过多媒体通信控制信令协议 H.245 过程, 建立可视电话的第四承载。
步骤 927中, 通过 UE A和 UE B之间建立的可视电话的第四承载, 在 该 UE A与 UE B之间进行 3G电路域的可视电话通信。
步骤 928中, 可视电话通话完毕后, UE A和 UE B之间拆除所建立的 第四承载和底层电路。
不难发现, 在本实施例中, 多媒体彩铃业务可以基于现有的可视电话 的网络框架上得以实现。 而且, 由多媒体回铃音服务器向该主叫终端播放 多媒体回铃音, 避免了对终端进行协议层面的改造, 使得可视电话的多媒 体彩铃业务的实现, 对终端的影响能够减小到最小程度。
另外, 在建立可视电话的第四承载之前, 需要在检测到被叫终端摘机 后, 拆除在该主叫终端与多媒体回铃音服务器之间建立的第三承载。 使得 在用户通话接通时, 可以立即释放掉多媒体回铃音服务器所占用的电路, 节约了有限的电路资源。
值得一提的是, 在本实施例中, 当主叫终端与被叫终端之间的可视电 话的第四承载建立完成后, 网络侧还需要对该可视电话通信进行计费。 使 得在多媒体彩铃业务的实现过程中, 能够对通话时长进行精确计算和控制。
需要说明的是, 在本实施例中, MSC服务器 A还可以在步骤 914或步 骤 917中, 通过下发给 UE A的 Alerting消息或 Connect消息, 将本次振铃 是否会触发多媒体彩铃的播放的信息发送给 UE A, 以便 UE A能够据此准 确计时。 比如说, 如果消息中没有此信息, 则 UE A按照原有正常方式启动 计时。 如果消息中有此信息, 则 UE A将不会在收到第一个 Connect消息时 启动计时, 而是等待后续网络发送指示启动计时的消息, 在收到指示启动 计时的消息后, 再启动计时。
本次振铃是否会触发多媒体回铃音的播放的信息可以通过消息中的 facility字段来扩展实现, 也可以通过 Connect消息当中的 User-User字段的 扩展来实现。 比如说, 如果在 Connect消息中 User-User字段的值为 1 , 则 指示 UE A在收到第一个 Connect消息时不计时;在 Connect消息中 User-User 字段的值为 0, 则指示 UE A按照原有正常方式启动计时。
本发明的第八实施例涉及一种可视电话呼叫方法, 本实施例与第七实 施例大致相同, 其区别在于, 在第七实施例中, 第三承载和第四承载为通 过 H.324、 H.323、 或 SIP的可视电话协议建立的可视电话通信链路; 而在 本实施例中, 第三承载和第四承载为 CSD链路, 可视电话的逻辑通道通过 H.324、 H.323或 SIP可视电话通信协议在 CSD链路之上建立。 其中, 第三 承载可分解为: 由主叫终端到该主叫终端的 MSC服务器之间的第五承载, 和该主叫终端的 MSC服务器到多媒体回铃音服务器之间的第六承载; 第四 承载可分解为: 主叫终端到该主叫终端的 MSC服务器之间的第五承载, 和 主叫终端的 MSC服务器到被叫终端之间的第七承载。
具体流程如图 10所示, 步骤 1001至步骤 1018分别与步骤 901至步骤
918完全相同, 在此不再赘述。
在步骤 1019中, 先在 UE A和 MSC服务器 A之间建立第五承载, 在 MSC服务器 A和多媒体回铃音服务器之间建立第六承载。 该第五承载和第 六承载均为 CSD链路。然后,在该第五承载和第六承载的基础上建立 H.245 过程。 建立后, 主叫终端用户可以收看多媒体回铃音服务器播放的多媒体 回铃音。
步骤 1020至步骤 1024分别与步骤 920至步骤 924完全相同, 在此不 再赘述。
在步骤 1025 中, 多媒体回铃音服务器向 MSC服务器 A返回 BICC Release Complete ( BICC释放完成) 消息。 MSC服务器 A向 UE A发送 Facility消息,此消息表示 MSC服务器 A与多媒体回铃音服务器的承载 (即 六承载) 已拆除, MSC服务器 A与 MSC服务器 B之间的 CS64kbps承载 链路已建立。 当然, 通过 facility消息来携带该信息只是一种具体的实现方 式, 实际上也可以用其他的消息进行替代。 本步骤的主要目的在于提示主 叫终端即 UE A, 在整个可视电话的呼叫过程会涉及两次 H.245承载过程的 建立,指示该 UE A在收到 facility消息后, 为第二次的 H.245承载过程 (即 UE A与 UE B之间的可视电话的第四承载)做准备,准备在现有的 CS64kbp 的链路上进行与 UE B之间的承载的建立。
本步骤不仅可以出现在如图 10 所示的位置, 还可能出现在步骤 1023
至步骤 1026之间的任何位置, 其作用主要是用于提示进行两次 H.245承载 过程的建立。
在步骤 1026中, 在现有的 UE A和 MSC服务器 A之间的第五承载, 和 MSC服务器 A和 UE B之间的第七承载的基础上, 建立 H.245过程, 即 建立主叫终端 UE A和被叫终端 UE B之间的第四承载。
步骤 1027和步骤 1028分别与步骤 927和步骤 928完全相同, 在此不 再赘述。
不难发现, 本实施例与第七实施例相比, 可以提供更快速的 2次 H.245 承载过程的建立过程, 并且改动工作量小, 无实现障碍。
本发明的第九实施例涉及一种可视电话呼叫方法, 本实施例在第七实 施例的基础上,通过 UE A和多媒体回铃音服务器分别发起 H.245 自行挂断 过程,达到拆除 UE A和多媒体回铃音服务器之间可视电话的第三承载的目 的。 具体流程如图 11所示。
步骤 1101至步骤 1120分别与步骤 901至步骤 920完全相同,在此不再 赘述。
在步骤 1121中, MSC服务器 B向 MSC服务器 A返回 BICC ANM消 息。 并且, MSC服务器 A向 UE A发送 facility消息。 UE A收到该 facility 消息后, 发起 H.245 自行挂断流程(即不向通信的对方发送挂断信令 "End Session" ), 并直接释放本地资源。
步骤 1122与步骤 923完全相同。
在步骤 1123 中, MSC服务器 A 向多媒体回铃音服务器发送 BICC Release ( BICC 释放) 消息, 该多媒体回铃音服务器收到该消息后, 发起 H.245 自行挂断流程(即不向通信的对方发送挂断信令 "End Session" )。
在步骤 1124中, UE A在完成 H.245的自行挂断流程后, 发起第二次 H.245的承载建立, 即发起第七实施例中所述的 UE A与 UE B之间可视电 话的第四承载的建立过程。
在步骤 1125 中, 多媒体回铃音服务器向 MSC服务器 A返回 BICC Release Complete ( BICC释放完成) 消息。
步骤 1126与步骤 1127分别与步骤 927和步骤 928相同,在此不再赘述。
不难发现, 本实施例与第七实施例的区别在于, 由网络侧向主叫终端 下发一个提示消息(即上述 facility消息 ),指示主叫终端该多媒体彩铃业务 的播放过程结束, 要求该主叫终端建立第二个 H.245 的承载。 主叫终端在 收到该提示消息后, 会发起一个自挂断的流程。 这样, 第一次建立的与多 媒体回铃音服务器之间的 H.245 承载将通过主叫终端挂断通信链路的方式 结束。 这样的一个过程符合正常的通话流程, 而且, 进一步减少了整个网 络接续的时间, 减小了业务切换的时间, 提高了用户的体验。
可以将整个多媒体彩铃业务将看作两次通话, 第一次通话作为多媒体 彩铃业务, 第二次通话作为正常的可视电话的通话。 主叫终端根据网络侧 下发的提示消息, 以自挂断的方式来结束整个多媒体彩铃的会话, 并且在 自挂断会话之后, 发起一个新的用于可视电话的通话的 H.245承载的建立 过程, 从而顺利实现正常的可视电话的通话。
在步骤 1123 中, 当多媒体回铃音服务器收到来自 MSC服务器 A的 BICC Release 消息后, 会发起一个自挂断的流程。 多媒体回铃音服务器在 整个多媒体彩铃业务当中可作为一个逻辑上的终端出现, 提供多媒体的彩 铃内容。 在提供多媒体彩铃内容的过程结束之后, 该多媒体回铃音服务器 可以作为会话的参与一方参与到整个的多媒体彩铃承载的拆除过程。
UE A发起的自挂断流程与多媒体回铃音服务器发起的自挂断流程, 完 成的功能基本相似 (即拆除 UE A多媒体回铃音服务器之间的承载 ), 因此, 实际上可以只在 UE A中发起的自挂断流程,或只在多媒体回铃音服务器中 发起的自挂断流程。 但是, 出于整个***的协同工作的考虑, 为了尽量的 减少***出错的可能,也可以在 UE A和多媒体回铃音服务器中分别发起自 挂断流程, 而且, 在实际应用中, 这两个自挂断流程并无严格的先后顺序。 另外, 本实施例的步骤 1123中, MSC服务器 A向多媒体回铃音服务器发 送的 BICC Release消息, 实际上是用于指示该多媒体回铃音服务器进行自 挂断过程的。 因此, 如果该多媒体回铃音服务器不执行自挂断的过程, 则 步骤 1123可以省略。
不难发现, 在本发明的第一至第六实施例中, 在整个多媒体彩铃业务 完成之后, 多媒体回铃音服务器还需要驻留在后续的可视电话的通话过程
当中, 承担一个背靠背服务器的作用, 为描述方便, 将该方案称为跨接方 案。 在本发明的第七至第九实施例中, 在整个多媒体彩铃业务完成之后, 需要拆除多媒体回铃音服务器与主叫终端之间的通信链路, 主叫终端和被 叫终端之间需要建立起用于可视电话业务的通信链路, 该方案最大的特征 在于, 主叫终端需要分别与多媒体回铃音服务器、 被叫终端建立 H.245 的 承载, 为描述方便, 将该方案称为非跨接方案。
本发明的第十实施例涉及一种可视电话呼叫方法, 本实施例为第一至 第六实施例中的跨接方案, 与第七至第九实施例中的为非跨接方案的融合。
具体地说, 主叫终端在发送给 MSC服务器 A的 SETUP消息中, 携带 上本终端所支持的彩铃方案的类型 (即是支持跨接方案还是支持非跨接方 案)。 比如说, 可以通过 SETUP消息中 User-User 字段的取值, 来指示终端 支持的是非跨接方案, 还是跨接方案。 可以事先约定, User-User 字段取值 为 0时, 表示本终端支持跨接方案, User-User 字段取值为 1时, 表示本终 端支持非跨接方案。
如果网络侧发现主叫终端支持的是跨接方案, 则后续流程可以与上述 第一至第六实施例中的任一实施例相同; 如果网络侧发现主叫终端支持的 是非跨接方案, 则后续流程可以与上述第七至第九实施例中的任一实施方 式相同, 在此不再赘述。
本发明的第十一实施例涉及一种可视电话呼叫***, 如图 12所示, 包 括: 承载建立单元, 用于在主叫终端与多媒体回铃音服务器之间建立可视 电话的第一承载; 多媒体回铃音播放单元, 用于通过该承载建立单元建立 的第一承载, 向该主叫终端播放多媒体回铃音; 检测单元, 用于检测被叫 终端是否摘机, 并在检测到该被叫终端摘机后, 向该承载建立单元指示该 被叫终端已摘机, 该承载建立单元还用于在收到该检测单元的该指示后, 在该被叫终端与该多媒体回铃音服务器之间建立可视电话的第二承载; 通 信单元, 用于通过该承载建立单元建立的第一承载和第二承载, 在该主叫 终端和该被叫终端之间进行可视电话通信。 使得多媒体彩铃业务可以基于 现有的可视电话的网络框架上得以实现。 而且, 由多媒体回铃音播放单元 向该主叫终端播放多媒体回铃音, 避免了对终端进行协议层面的改造, 使
得可视电话的多媒体彩铃业务的实现, 对终端的影响能够减小到最小程度。 其中, 多媒体回铃音播放单元位于多媒体回铃音服务器内, 承载建立 单元通过可视电话信令协议过程建立该第一承载和该第二承载。 该可视电 话信令协议可以为 H.324、 H.323或 SIP的可视电话信令协议。
值得一提的是, 本实施例的可视电话呼叫***中, 还可以包括计费单 元, 用于对可视电话通信进行计费; 该检测单元还用于在检测到被叫终端 摘机后, 向该计费单元指示该被叫终端已摘机, 该计费单元在收到该指示 后, 对可视电话通信开始计费。 使得在多媒体彩铃业务的实现过程中, 能 够对通话时长进行精确计算和控制。
在本实施例的可视电话呼叫***中, 还可以包括通知单元, 用于通知 主叫终端忽略计费或计时, 以及通知主叫终端开始计费或计时。 该检测单 元还用于在检测到被叫终端摘机后, 向该通知单元指示该被叫终端已摘机。 该通知单元在收到该检测单元的该指示之前, 通知该主叫终端忽略计费或 计时, 在收到该检测单元的该指示之后, 通知该主叫终端开始计费或计时。 使得该主叫终端能够准确地获知网络侧计算的通话时长, 以免该主叫终端 的用户对计费信息产生误解。
本发明的第十二实施例涉及一种可视电话呼叫***, 如图 13所示, 包 括: 承载建立单元, 用于在主叫终端与多媒体回铃音服务器之间建立可视 电话的第三承载, 在该主叫终端和被叫终端之间建立可视电话的第四承载。 多媒体回铃音播放单元, 用于通过该承载建立单元建立的第三承载向该主 叫终端播放多媒体回铃音。 通信单元, 用于通过该承载建立单元建立的第 四承载, 在该主叫终端和该被叫终端之间进行可视电话通信。 使得多媒体 彩铃业务可以基于现有的可视电话的网络框架上得以实现。
本实施例的可视电话呼叫***还可以包括: 检测单元, 用于检测被叫 终端是否摘机, 和承载拆除单元, 用于拆除承载。
如果第三承载和第四承载为电路交换数据 CSD链路, 且该第三承载在 逻辑上可分解为: 主叫终端到该主叫终端的 MSC服务器之间的第五承载、 和该主叫终端的 MSC服务器到多媒体回铃音服务器之间的第六承载; 该第 四承载在逻辑上可分解为: 该第五承载、 和主叫终端的 MSC服务器到被叫
终端之间的第七承载。 那么, 该检测单元在检测到该被叫终端摘机后, 向 该承载拆除单元指示该被叫终端已摘机, 该承载拆除单元在收到该指示后, 拆除在主叫终端的 MSC服务器到多媒体回铃音服务器之间的第六承载。
如果第三承载和第四承载为通过 H.324、 H.323、 或 SIP的可视电话协 议建立的可视电话通信链路, 则该检测单元在检测到该被叫终端摘机后, 向该承载拆除单元指示该被叫终端已摘机, 该承载拆除单元在收到该指示 后, 拆除该承载建立单元建立的该第三承载, 并指示该承载建立单元建立 该第四承载。
由此可见, 在用户通话接通时 (即检测单元检测到该被叫终端摘机), 可以立即释放掉多媒体回铃音服务器所占用的电路, 因此能够有效节约有 限的电路资源。
综上所述, 在本发明的实施例中, 多媒体回铃音服务器通过在主叫终 端与多媒体回铃音服务器之间建立的可视电话的第一承载, 向该主叫终端 播放多媒体回铃音。 当检测到被叫终端摘机后, 在该被叫终端与该多媒体 回铃音服务器之间建立可视电话的第二承载, 通过所建立的第一承载和第 二承载, 在该主叫终端和该被叫终端之间进行可视电话通信。 或者, 多媒 体回铃音服务器通过在主叫终端与多媒体回铃音服务器之间建立的可视电 话的第三承载, 向该主叫终端播放多媒体回铃音。 该主叫终端和被叫终端 之间建立可视电话的第四承载, 通过该第四承载在该主叫终端和被叫终端 之间进行可视电话通信。 使得多媒体彩铃业务可以基于现有的可视电话的 网络框架上得以实现。 而且, 由多媒体回铃音服务器向该主叫终端播放多 媒体回铃音, 避免了对终端进行协议层面的改造, 使得可视电话的多媒体 彩铃业务的实现, 对终端的影响能够减小到最小程度。
网络侧在检测到被叫终端摘机(或完成第四承载的建立)后, 再对可 视电话通信进行计费, 使得在多媒体彩铃业务的实现过程中, 能够对通话 时长进行精确计算和控制。
在检测到被叫终端摘机之前 , 通知该主叫终端忽略计费 , 在检测到该 被叫终端摘机后, 通知该主叫终端开始计费。 使得该主叫终端能够准确地 获知网络侧计算的通话时长, 以免该主叫终端的用户对计费信息产生误解。
在通过第四承载进行可视电话通信的方案中, 在建立可视电话的第四 承载的步骤之前, 需要在检测到被叫终端摘机后, 拆除在该主叫终端与多 媒体回铃音服务器之间建立的第三承载。 使得在用户通话接通时, 可以立 即释放掉多媒体回铃音服务器所占用的电路, 节约了有限的电路资源。
虽然通过参照本发明的某些优选实施例, 已经对本发明进行了图示和 描述, 但本领域的普通技术人员应该明白, 可以在形式上和细节上对其作 各种改变, 而不偏离本发明的精神和范围。
Claims
1. 一种可视电话呼叫方法, 其特征在于, 包括:
在主叫终端与多媒体回铃音服务器之间建立可视电话的第一承载; 通过所述第一承载向所述主叫终端播放多媒体回铃音;
检测到被叫终端摘机后, 在该被叫终端与所述多媒体回铃音服务器之 间建立可视电话的第二承载;
通过所述第一承载和第二承载, 在所述主叫终端和被叫终端之间进行 可视电话通信。
2. 根据权利要求 1所述的可视电话呼叫方法, 其特征在于, 所述第一 承载和所述第二承载通过可视电话信令协议过程建立。
3. 根据权利要求 2所述的可视电话呼叫方法, 其特征在于, 所述可视 电话信令协议为 H.324、 H.323或会话发起协议 SIP。
4. 根据权利要求 1所述的可视电话呼叫方法, 其特征在于, 还包括: 在检测到所述被叫终端摘机后, 对所述可视电话通信进行计费。
5. 根据权利要求 1所述的可视电话呼叫方法, 其特征在于, 在所述建 立可视电话的第一承载之前, 还包括:
所述多媒体回铃音服务器在向所述主叫终端发送的 Alerting 消息中携 带标识多媒体彩铃业务的特殊文本,或者,向该主叫终端发送 Connect消息, 通知该主叫终端建立所述第一承载。
6. 根据权利要求 1至 5中任一项所述的可视电话呼叫方法, 其特征在 于, 还包括:
在检测到所述被叫终端摘机之前, 通知所述主叫终端忽略计费或计时, 在检测到该被叫终端摘机后 , 通知该主叫终端开始计费或计时。
7. 根据权利要求 6所述的可视电话呼叫方法, 其特征在于, 所述通知 所述主叫终端忽略计费或计时的方式包括:
向所述主叫终端发送表示尚未开始计费的信息, 该信息通过发送给该 主叫终端的消息、 信令、 信号、 或电子函件携带。
8. 根据权利要求 7所述的可视电话呼叫方法, 其特征在于,
所述消息为 H.245命令、 H.245 指示、 短消息、 多媒体消息、 Facility
消息、 Alterting消息、 Conncet消息、 即时消息、 或推 ( Push ) 消息; 所述信号为双音多频 DTMF信号或非结构的补充业务数据 USSD信号; 所述信令为 SIP信令、超文本传输协议 HTTP信令、或实时流协议 RTSP 信令。
9. 根据权利要求 6所述的可视电话呼叫方法, 其特征在于, 所述通知 所述主叫终端开始计费或计时的方式包括:
向所述主叫终端发送表示开始计费的信息, 该信息通过发送给该主叫 终端的消息、 信令、 信号、 或电子函件携带。
10. 根据权利要求 9所述的可视电话呼叫方法, 其特征在于, 所述消息为 H.245命令、 H.245 指示、 短消息、 多媒体消息、 Facility 消息、 即时消息、 或推(Push ) 消息; 和 /或
所述信号为双音多频 DTMF信号或 USSD信号; 和 /或
所述信令为 SIP信令、 HTTP信令、 或 RTSP信令。
11. 一种可视电话呼叫方法, 其特征在于, 包括:
在主叫终端与多媒体回铃音服务器之间建立可视电话的第三承载; 通过所述第三承载向所述主叫终端播放多媒体回铃音;
在所述主叫终端和被叫终端之间建立可视电话的第四承载, 通过该第 四承载在所述主叫终端和被叫终端之间进行可视电话通信。
12. 根据权利要求 11所述的可视电话呼叫方法, 其特征在于, 所述第三承载和第四承载为电路交换数据 CSD链路, 或者为通过可视 电话协议建立的可视电话通信链路。
13. 根据权利要求 12所述的可视电话呼叫方法, 其特征在于, 所述第 三承载和第四承载为 CSD链路;
所述第三承载由所述主叫终端到该主叫终端的移动交换中心 MSC服务 器之间的第五承载、和该主叫终端的 MSC服务器到所述多媒体回铃音服务 器之间的第六承载组成;
所述第四承载由所述第五承载、和所述主叫终端的 MSC服务器到所述 被叫终端之间的第七承载组成。
14. 根据权利要求 13所述的可视电话呼叫方法, 其特征在于, 在所述
建立可视电话的第四承载之前, 还包括:
当检测到所述被叫终端摘机后, 拆除在所述主叫终端的 MSC服务器到 所述多媒体回铃音服务器之间的所述第六承载。
15. 根据权利要求 12所述的可视电话呼叫方法, 其特征在于, 所述第 三承载和第四承载为通过可视电话协议建立的可视电话通信链路;
在所述建立可视电话的第四承载之前, 还包括:
当检测到所述被叫终端摘机后, 拆除在所述主叫终端与多媒体回铃音 服务器之间建立的所述第三承载。
16. 根据权利要求 15所述的可视电话呼叫方法, 其特征在于, 所述拆 除第三承载的方式如下:
向所述主叫终端发送用于指示该主叫终端发起自挂断流程的消息, 和 / 或, 向所述多媒体回铃音服务器发送用于指示该多媒体回铃音服务器发起 自挂断流程的消息。
17. 根据权利要求 11所述的可视电话呼叫方法, 其特征在于, 所述建 立可视电话的第四承载, 包括:
在原有可视电话通信链路的基础之上发起 H.245重新建立的过程; 或者由所述主叫终端发起 H.324可视电话通信的重新建立过程。
18. 根据权利要求 11至 18中任一项所述的可视电话呼叫方法, 其特 征在于, 在所述建立可视电话的第四承载之后, 还包括:
对所述可视电话通信进行计费。
19. 一种可视电话呼叫***, 其特征在于, 包括:
承载建立单元, 用于在主叫终端与多媒体回铃音服务器之间建立可视 电话的第一承载;
多媒体回铃音播放单元, 用于通过所述承载建立单元建立的所述第一 承载向所述主叫终端播放多媒体回铃音;
检测单元 , 用于检测被叫终端是否摘机 , 并在检测到该被叫终端摘机 后, 向所述承载建立单元指示该被叫终端已摘机; 所述承载建立单元还用 于在收到所述检测单元的所述指示后, 在所述被叫终端与所述多媒体回铃 音服务器之间建立可视电话的第二承载;
通信单元, 用于通过所述承载建立单元建立的所述第一承载和第二承 载, 在所述主叫终端和所述被叫终端之间进行可视电话通信。
20. 根据权利要求 19所述的可视电话呼叫***, 其特征在于, 所述多 媒体回铃音播放单元位于所述多媒体回铃音服务器内。
21. 根据权利要求 19所述的可视电话呼叫***, 其特征在于, 所述承 载建立单元通过可视电话信令协议过程建立所述第一承载和所述第二承 载;
所述可视电话信令协议包括 H.324、 H.323或 SIP。
22. 根据权利要求 19所述的可视电话呼叫***, 其特征在于,还包括: 计费单元, 用于对所述可视电话通信进行计费;
所述检测单元还用于在检测到所述被叫终端摘机后, 向所述计费单元 指示该被叫终端已摘机, 该计费单元在收到该指示后, 对所述可视电话通 信开始计费。
23. 根据权利要求 19至 22中任一项所述的可视电话呼叫***, 其特 征在于, 还包括:
通知单元, 用于通知所述主叫终端忽略计费或计时, 以及通知所述主 叫终端开始计费或计时;
所述检测单元还用于在检测到所述被叫终端摘机后, 向所述通知单元 指示该被叫终端已摘机;
所述通知单元在收到所述检测单元的所述指示之前, 通知所述主叫终 端忽略计费或计时, 在收到所述检测单元的所述指示之后, 通知该主叫终 端开始计费或计时。
24. 一种可视电话呼叫***, 其特征在于, 包括:
承载建立单元, 用于在主叫终端与多媒体回铃音服务器之间建立可视 电话的第三承载, 在该主叫终端和被叫终端之间建立可视电话的第四承载; 多媒体回铃音播放单元, 用于通过所述承载建立单元建立的所述第三 承载向所述主叫终端播放多媒体回铃音;
通信单元, 用于通过所述承载建立单元建立的所述第四承载, 在所述 主叫终端和所述被叫终端之间进行可视电话通信。
25. 根据权利要求 24所述的可视电话呼叫***, 其特征在于, 所述第三承载和第四承载为电路交换数据 CSD链路; 或者, 所述第三承载和第四承载为通过可视电话协议建立的可视电话通信链 路。
26. 根据权利要求 25所述的可视电话呼叫***, 其特征在于, 所述第三承载和第四承载为 CSD链路;
所述第三承载由所述主叫终端到该主叫终端的 MSC服务器之间的第五 承载、和该主叫终端的 MSC服务器到所述多媒体回铃音服务器之间的第六 载组成;
所述第四承载包括所述第五承载、和所述主叫终端的 MSC服务器到所 述被叫终端之间的第七承载;
所述***还包括:
检测单元, 用于检测被叫终端是否摘机;
承载拆除单元, 用于拆除承载;
所述检测单元在检测到所述被叫终端摘机后, 向所述承载拆除单元指 示该被叫终端已摘机, 该承载拆除单元在收到该指示后, 拆除在所述主叫 终端的 MSC服务器到所述多媒体回铃音服务器之间的所述第六承载。
27. 根据权利要求 25所述的可视电话呼叫***, 其特征在于, 所述第三承载和第四承载为通过可视电话协议建立的可视电话通信链 路;
所述***还包括:
检测单元, 用于检测被叫终端是否摘机;
承载拆除单元, 用于拆除承载;
所述检测单元在检测到所述被叫终端摘机后, 向所述承载拆除单元指 示该被叫终端已摘机, 该承载拆除单元在收到该指示后, 拆除所述承载建 立单元建立的所述第三承载, 并指示该承载建立单元建立所述第四承载。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP08715214.6A EP2106111B1 (en) | 2007-03-31 | 2008-03-12 | Calling method and system for a video telephone |
JP2009549763A JP5117511B2 (ja) | 2007-03-31 | 2008-03-12 | テレビ電話のための呼出方法およびシステム |
US12/495,227 US8351906B2 (en) | 2007-03-31 | 2009-06-30 | Calling methods and systems for video phone |
US13/329,061 US8630628B2 (en) | 2007-03-31 | 2011-12-16 | Multimedia calling methods and systems for video phones |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200710073941 | 2007-03-31 | ||
CN200710073941.8 | 2007-03-31 | ||
CN200710149813.7 | 2007-09-04 | ||
CNB2007101498137A CN100531271C (zh) | 2007-03-31 | 2007-09-04 | 可视电话呼叫方法及*** |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/495,227 Continuation US8351906B2 (en) | 2007-03-31 | 2009-06-30 | Calling methods and systems for video phone |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008119283A1 true WO2008119283A1 (fr) | 2008-10-09 |
Family
ID=39807813
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2008/070478 WO2008119283A1 (fr) | 2007-03-31 | 2008-03-12 | Procédé et système d'appel pour visiophone |
Country Status (5)
Country | Link |
---|---|
US (2) | US8351906B2 (zh) |
EP (1) | EP2106111B1 (zh) |
JP (3) | JP5117511B2 (zh) |
CN (1) | CN100531271C (zh) |
WO (1) | WO2008119283A1 (zh) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7668538B2 (en) * | 2005-06-15 | 2010-02-23 | Music Choice | Systems and methods for facilitating the acquisition of content |
CN100531271C (zh) | 2007-03-31 | 2009-08-19 | 华为技术有限公司 | 可视电话呼叫方法及*** |
CN101282579B (zh) * | 2008-05-08 | 2011-06-08 | 华为技术有限公司 | 记录通话的方法、***、通话记录平台及彩铃平台 |
US8204200B2 (en) * | 2008-09-03 | 2012-06-19 | Core Wireless Licensing S.à.r.l. | Method, system, and apparatus for overriding a ring back signal |
KR101685442B1 (ko) * | 2010-04-07 | 2016-12-13 | 삼성전자주식회사 | 전계 정보 기반의 메타데이터를 이용한 영상 통화 품질 향상을 위한 장치 및 방법 |
JP5743708B2 (ja) * | 2011-05-18 | 2015-07-01 | 日本電気通信システム株式会社 | 通信システム、サーバおよび通信方法 |
CN103139398B (zh) * | 2011-11-29 | 2015-08-12 | 中兴通讯股份有限公司 | 一种呼叫业务实现方法及*** |
CN107257317B (zh) * | 2012-05-04 | 2022-06-03 | 江虹 | 在通信终端设备之间已建立通信信道的即时通信***和方法 |
CN107708103B (zh) * | 2017-11-05 | 2020-08-14 | 浙江东信昆辰科技股份有限公司 | 基于map信令实现号码保密的方法 |
CN111865883A (zh) * | 2019-04-30 | 2020-10-30 | 华为技术有限公司 | 呼叫处理的方法和设备 |
CN113993093B (zh) * | 2021-12-24 | 2022-03-18 | 嘉兴域途科技有限公司 | 4g/5g条件下双向呼叫多端远程视频通信方法和*** |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001119676A (ja) * | 1999-10-19 | 2001-04-27 | Soichi Ueno | インターネットテレビ電話中継装置 |
CN1556643A (zh) * | 2003-12-30 | 2004-12-22 | ***通信集团公司 | 在移动智能网***中提供个性化回铃音的方法 |
CN1671160A (zh) * | 2005-03-11 | 2005-09-21 | 上海华为技术有限公司 | 可视电话业务中的回铃音和回铃图像实现方法 |
CN1874373A (zh) * | 2005-12-20 | 2006-12-06 | 华为技术有限公司 | 慢速呼叫终端播放个性化回铃音的方法 |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6195543B1 (en) * | 1997-06-20 | 2001-02-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for providing advice of charge parameters for mobile radio telephone calls |
JP2003275016A (ja) | 2002-01-18 | 2003-09-30 | Matsushita Electric Works Ltd | ヘアーセット機器 |
JP2003274016A (ja) | 2002-03-19 | 2003-09-26 | Hideo Matsuo | 回線交換装置、リングバックトーン管理システム、及び該リングバックトーン管理システムの制御方法 |
JP2003348239A (ja) | 2002-05-30 | 2003-12-05 | Show Engineering:Kk | 電話交換接続システムおよび電話交換接続方法 |
US7340049B2 (en) * | 2003-10-10 | 2008-03-04 | Lucent Technologies Inc. | Feedback to calling communication device on call connected with intelligent network signaling |
JP2005229547A (ja) * | 2004-02-16 | 2005-08-25 | Hiroyasu Mikabe | 録画方法、録画システム、再生方法及び再生システム |
KR100646376B1 (ko) * | 2004-06-28 | 2006-11-23 | 에스케이 텔레콤주식회사 | 발신측 교환기를 이용하여 멀티미디어 링백톤 서비스를제공하는 방법 및 시스템 |
US8068593B2 (en) | 2004-12-30 | 2011-11-29 | Alcatel Lucent | Method and apparatus for providing multimedia ringback services to mobile user devices in pre-IMS networks |
US7693134B2 (en) | 2004-12-30 | 2010-04-06 | Alcatel-Lucent Usa Inc. | Method and apparatus for providing multimedia ringback services to user devices in IMS networks |
EP1855475A4 (en) * | 2005-05-16 | 2008-10-01 | Huawei Tech Co Ltd | SYSTEM FOR REALIZING MULTIMEDIA RECALL CELLS AND METHOD THEREFOR |
WO2006137781A1 (en) * | 2005-06-20 | 2006-12-28 | Telefonaktiebolaget Lm Ericsson (Publ) | A method and arrangement for making a call-setup. |
CN1859475B (zh) * | 2005-07-22 | 2010-05-12 | 华为技术有限公司 | 一种实现多媒体回铃音的方法及*** |
US20070291106A1 (en) * | 2005-07-28 | 2007-12-20 | Dilithium Networks, Inc. | Method and apparatus for providing interactive media during communication in channel-based media telecommunication protocols |
US9883028B2 (en) * | 2005-07-28 | 2018-01-30 | Onmobile Global Limited | Method and apparatus for providing interactive media during communication in channel-based media telecommunication protocols |
US8873539B2 (en) * | 2005-09-06 | 2014-10-28 | Nokia Corporation | Multimedia call control mechanism and communication equipment using the same |
CN1859496B (zh) | 2006-03-10 | 2010-07-28 | 华为技术有限公司 | 一种实现多媒体视频彩铃业务的***及方法 |
CN100463471C (zh) | 2006-05-17 | 2009-02-18 | ***通信集团公司 | 实现视频彩铃播放的方法 |
US20080037740A1 (en) * | 2006-08-08 | 2008-02-14 | Nortel Networks Limited | Intelligent ring-back indicator |
CN1917532B (zh) | 2006-09-01 | 2010-08-11 | 北京邮电大学 | 基于移动通信网的多媒体彩铃业务的实现方法 |
CN1917531A (zh) | 2006-09-01 | 2007-02-21 | 北京邮电大学 | 基于移动通信网络的播送多媒体彩铃的***和方法 |
CN100531271C (zh) | 2007-03-31 | 2009-08-19 | 华为技术有限公司 | 可视电话呼叫方法及*** |
CN101635819B (zh) | 2007-09-04 | 2012-01-11 | 华为技术有限公司 | 可视电话呼叫方法及*** |
-
2007
- 2007-09-04 CN CNB2007101498137A patent/CN100531271C/zh active Active
-
2008
- 2008-03-12 EP EP08715214.6A patent/EP2106111B1/en active Active
- 2008-03-12 JP JP2009549763A patent/JP5117511B2/ja active Active
- 2008-03-12 WO PCT/CN2008/070478 patent/WO2008119283A1/zh active Application Filing
-
2009
- 2009-06-30 US US12/495,227 patent/US8351906B2/en active Active
-
2011
- 2011-12-16 US US13/329,061 patent/US8630628B2/en active Active
-
2012
- 2012-08-22 JP JP2012183019A patent/JP5486055B2/ja active Active
- 2012-08-22 JP JP2012183018A patent/JP5675730B2/ja active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001119676A (ja) * | 1999-10-19 | 2001-04-27 | Soichi Ueno | インターネットテレビ電話中継装置 |
CN1556643A (zh) * | 2003-12-30 | 2004-12-22 | ***通信集团公司 | 在移动智能网***中提供个性化回铃音的方法 |
CN1671160A (zh) * | 2005-03-11 | 2005-09-21 | 上海华为技术有限公司 | 可视电话业务中的回铃音和回铃图像实现方法 |
CN1874373A (zh) * | 2005-12-20 | 2006-12-06 | 华为技术有限公司 | 慢速呼叫终端播放个性化回铃音的方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2106111A4 * |
Also Published As
Publication number | Publication date |
---|---|
US20100022226A1 (en) | 2010-01-28 |
JP2012227975A (ja) | 2012-11-15 |
EP2106111A1 (en) | 2009-09-30 |
EP2106111A4 (en) | 2011-10-26 |
JP5675730B2 (ja) | 2015-02-25 |
JP5486055B2 (ja) | 2014-05-07 |
CN100531271C (zh) | 2009-08-19 |
US8630628B2 (en) | 2014-01-14 |
US20120086766A1 (en) | 2012-04-12 |
JP2012249329A (ja) | 2012-12-13 |
US8351906B2 (en) | 2013-01-08 |
JP5117511B2 (ja) | 2013-01-16 |
EP2106111B1 (en) | 2017-12-20 |
JP2010518791A (ja) | 2010-05-27 |
CN101277474A (zh) | 2008-10-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2008119283A1 (fr) | Procédé et système d'appel pour visiophone | |
EP1677485B1 (en) | Method and apparatus for providing multimedia ringback services to user devices in IMS networks. | |
US7912198B2 (en) | System and method for implementing multimedia ring back tone service | |
US8131265B2 (en) | System and method for implementing multimedia ring back tone service | |
CN101317431B (zh) | 多媒体回铃音平台、实现多媒体彩铃业务的***及方法 | |
JP2005124183A (ja) | 通信セッション上で起動中の複数個の通信機器の識別情報を情報受信コンポーネントに送信する装置および方法 | |
WO2009062403A1 (fr) | Procédé pour réaliser un service de présentation du nom de l'appelant et dispositif de service d'informations relatives à l'appelant | |
US8059800B1 (en) | Method for viral distribution of ringback media | |
CN102868689B (zh) | 一号通业务中实现彩铃业务的方法和*** | |
WO2007009386A1 (fr) | Méthode et système pour fournir un service supplémentaire sur signal crochet commutateur | |
CN102664863B (zh) | 终端实现呼叫等待的方法、装置和*** | |
CN102075496B (zh) | 一种多媒体子***彩铃自服务转人工台的方法和*** | |
CN101489201B (zh) | 实现彩铃业务过程中指示通话计时的方法及相应设备 | |
WO2012151858A1 (zh) | 一种呼叫续接方法和应用服务器 | |
EP2723053B1 (en) | Transfer inquiry method, application server, service terminal, and system | |
WO2010037302A1 (zh) | 一种实现彩振业务的方法、装置及通信*** | |
CN101621588B (zh) | 可视电话呼叫方法 | |
CN101969615B (zh) | 可视电话呼叫方法 | |
WO2007056936A1 (fr) | Procede et equipement de reseau pour l'espacement arriere de multimedias dans un reseau de communication et reseau de communication correspondant | |
CN101635819B (zh) | 可视电话呼叫方法及*** | |
CN101489001B (zh) | 基于非跨接技术实现彩铃业务的方法及相应设备 | |
KR100712681B1 (ko) | 멀티미디어 데이터 서비스 방법 및 이를 수행하기 위한시스템 | |
WO2010066174A1 (zh) | 非跨接彩振通信的方法、终端及*** | |
KR100335994B1 (ko) | 차세대 지능망에서 유선 전화를 이용하여 개인용 컴퓨터를호출하는 폰투피시 지능망 서비스 제공 방법 | |
WO2009045754A2 (en) | Method for transmitting color ring back tones |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08715214 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008715214 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2009549763 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |