WO2009135375A1 - 实现单对话彩铃业务的呼叫建立方法 - Google Patents

实现单对话彩铃业务的呼叫建立方法 Download PDF

Info

Publication number
WO2009135375A1
WO2009135375A1 PCT/CN2008/073875 CN2008073875W WO2009135375A1 WO 2009135375 A1 WO2009135375 A1 WO 2009135375A1 CN 2008073875 W CN2008073875 W CN 2008073875W WO 2009135375 A1 WO2009135375 A1 WO 2009135375A1
Authority
WO
WIPO (PCT)
Prior art keywords
crbt
message
sdp
call
request
Prior art date
Application number
PCT/CN2008/073875
Other languages
English (en)
French (fr)
Inventor
谢振华
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN2008100946817A external-priority patent/CN101448046B/zh
Priority claimed from CN2008100993023A external-priority patent/CN101459874B/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2009135375A1 publication Critical patent/WO2009135375A1/zh

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/42017—Customized ring-back tones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • the present invention relates to the field of communications, and more particularly to a call setup method for implementing a single-talk CRBT service in an IP Multimedia Subsystem.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • 3GPP 3rd Generation Partnership Project
  • An IP-based network architecture that builds an open and flexible business environment to support multimedia applications, thereby providing users with rich multimedia services.
  • the control layer and the service layer are separated from each other. The control layer does not provide specific service functions, and only provides necessary triggering, routing, and accounting functions to the service layer.
  • the service triggering and control functions in the control layer are implemented by the Call Session Control Function (CSCF).
  • CSCF Call Session Control Function
  • the CSCF is divided into proxy session control function (Proxy CSCF, referred to as P-CSCF) and query session control function. (Interrogating CSCF, referred to as I-CSCF) and monthly session control function (Serving CSCF, S-CSCF for short), most of which use S-CSCF, the query type is optional.
  • the business layer is composed of a series of application servers (Application Servers, AS for short), which can provide specific business transactions.
  • the control layer controls the service trigger according to the subscription information of the user, invokes the service on the AS, and implements the service function.
  • the end-to-end device in the session is called User Equipment (UE) and is responsible for interaction with the user.
  • the above functional entities communicate using the Session Initiation Protocol (SIP) protocol.
  • SIP Session Initiation Protocol
  • MRF multimedia resource function
  • MRFC multimedia resource function controller
  • MRFP Multimedia Resource Function Processor
  • SE Softswitch and Policy Server
  • the signaling is translated and interpreted as an instruction corresponding to the MRFP, or vice versa, to translate and interpret the response of the MRFP as SIP signaling sent to the SE; the media processing portion MRFP is responsible for the transmission and reception of the media stream.
  • the SIP protocol can be used as the bearer layer of the Session Description Protocol (SDP).
  • SDP Session Description Protocol
  • the SDP is responsible for media resource information negotiation, including media type, media connection address, media connection port, and bandwidth requirements.
  • the content of the SDP protocol is divided into two types: request and response. Each request must correspond to one response.
  • the service for simultaneously playing multimedia information to the calling party during the call setup process is a service in the IMS, and the service may also be called a CRBT service, which allows the calling party to play in advance during the call by the called party. Multimedia information, and stop the multimedia information playback that has not stopped after the called party answers.
  • Single-talk CRBT is an implementation of the CRBT service, that is, the service implementation is completed in a SIP conversation without introducing a new conversation.
  • the ring tones AS and S-CSCF are drawn as an entity, and the interaction between them is a standard process.
  • 1 is a basic message flow diagram of a related single-talk CRBT service, in which a calling user is called to call a called user in the prior art, and the CRBT AS plays a ring back tone to the calling user during the call, and when the called user answers, the ring back tone
  • Step 101 The calling user UE-A initiates a call request, where the call request carries an SDP request, such as sending
  • the INVITE message carries an SDP request in the message body, and the message arrives at the CRBT AS through the forwarding of the P-CSCF and the S-CSCF.
  • Step 102 The CRBT AS forwards the call request to the called user UE-B, and the message passes through the S.
  • Step 103 the called user UE-B rings, and returns a ringing message to the calling party, for example, sends a "180 Ringing" message, and the ringing message arrives at the CRBT AS via the S-CSCF;
  • Step 104 CRBT AS call
  • the CRBT media server carries the SDP request in step 101, and the message passes through the S-CSCF;
  • Step 105 the CRBT media server answers the call, for example, sends a "200 OK" message to the CRBT.
  • Step 106 The CRBT AS sends an SDP response to the CRBT session to the calling party, such as by calling
  • the temporary response message of the message carries the response.
  • the temporary response message may be a message starting with "1" such as "183 Session Progress” message or "180 Ringing” message, and the message body carries the SDP response of the CRBT session, and the message passes through the S-CSCF.
  • the P-CSCF arrives at the UE-A;
  • Step 107 The CRBT AS sends an acknowledgement response message to the CRBT media server, for example, sends an ACK (Acknowledgement) message, and the message passes through the S-CSCF; wherein, steps 106 and 107 may not be in the same order. carried out.
  • Step 108 The CRBT media server receives the acknowledgement response message sent by the CRBT AS, and plays the CRBT to the UE-A.
  • the steps 104 to 108 may be performed at any time in steps 101 to 109.
  • the calling party may further negotiate the media resource information with the called party, and the subsequent negotiation is based on the foregoing negotiation result, because the calling party actually negotiates the media with the CRBT media server. Therefore, when the media type of the CRBT media is less than the media type in the SDP request in step 101, the caller thinks that the called party is only willing to make a call with less media type, and the called party also considers that the caller reduces the media type that is willing to use.
  • Step 109 The called user UE-B answers the call, and sends a response message to the calling party, for example, sends a "200 OK" message, which carries the SDP response of the called user, and passes through the S-CSCF to reach the CRBT AS;
  • Step 110 After the CRBT AS deletes the SDP response in the response message, it forwards the message to the calling party, and the message passes through the S-CSCF and the P-CSCF.
  • Step 111 The P-CSCF receives the response message, and instructs the charging function to start charging.
  • Step 112 The P-CSCF forwards the response message to the UE-A; wherein, steps 111 and 112 may be performed simultaneously without prioritization.
  • Step 113 The UE-A receives the response message, and sends an acknowledgement response message to the called party, for example, sends an ACK message, and the message arrives at the CRBT AS via the P-CSCF and the S-CSCF.
  • Step 114 The CRBT AS forwards the acknowledgement response message to the UE. -B, the message passes through the S-CSCF;
  • Step 115 At the same time, the CRBT AS queries the called party for the SDP information it is using, for example, sends a re-INVITE message without any SDP information, and the message arrives at the UE-B via the S-CSCF; The execution of steps 114 and 115 is not limited by the order.
  • the response to the re-call message may be The "200 OK" message
  • the SDP request is carried by the above-mentioned response re-calling message body, and the message arrives at the CRBT AS via the S-CSCF; from the foregoing analysis, the media type used by the SDP request at this time may be used by the SDP request in step 101. There are few media types.
  • Step 117 After receiving the SDP request of the called party, the CRBT AS sends a re-call message to the calling party, where the message body carries the received SDP request of the called party, and reaches the UE via the S-CSCF and the P-CSCF.
  • Step 120 UE-A and UE-B establish a media connection and start a call.
  • the shortcomings of the prior art are: The charging starts too early, and after the charging starts, there are still many signaling contacts to actually start the call, so that the charging information is compared with the actual situation. Larger access will result in a lower user experience; and after the called party answers, there are still many signaling calls to start the call. The above signaling will obviously take a considerable amount of time, increasing the waiting time of the user, and may even cause the user to think that a problem has occurred. Hang up the call.
  • the media type that can be used by the CRBT service solution in the prior art is limited to the media type specified when the calling party is called, and when the media type of the CRBT service includes only audio, the main and the called user have the video calling function. The terminal and the caller are willing to make a video call, and may only use an audio call after the answer, and thus have limitations.
  • the present invention has been made in view of the above-mentioned problem that the called response process is complicated, the user experience is low, and the charging start time is unreasonable. Therefore, the present invention aims to provide a call establishing method for implementing a single-talk CRBT service, which is used for Solve at least one of the above problems.
  • a call establishment method for implementing a single-talk CRBT service is provided.
  • the method for establishing a call for implementing a single-talk CRBT service according to the present invention mainly includes the following steps:
  • the calling party initiates a call, and the CRBT application server uses a single conversation mode to play media information to the calling party;
  • the called party answers the call, and the CRBT requests the called party to send an SDP request after receiving the response message of the called party and before forwarding the response message.
  • step A Calling party, ring back tone AS and called party establish call establishment according to standard procedures. Further, in step A, the calling party initiates the call, which specifically includes: the calling direction CRBT AS sends a call request message carrying the SDP request; in step A, the CRBT AS forwards the call request message to the called party, and is called The party returns a response message, where the message carries an SDP response. Further, in step A, after receiving the message of the calling party or the message of the called party, the CRBT AS interacts with the CRBT media server to the main The calling party forwards the SDP request or response of the CRBT session. Further, in step A: the SDP request of the CRBT session sent to the calling party is carried by the UPDATE message.
  • step A the SDP information of the CRBT session sent to the calling party includes all the media types in the SDP request of the calling party or the SDP response of the called party. Further, in step A: the CRBT AS will send the SDP letter of the CRBT session to the calling party.
  • step A the CRBT AS enhances the P-Early-Media header field in the session initial ten SIP message of the SDP information of the CRBT session, and sets the value of this header to sendonly. Further, in step A: after receiving the CRBT session SDP information, the CRBT AS receives the new SDP request from the calling party, and then changes the direction indication indicating that the direction of the media type that receives only recvonly is both sent and received. Sendrecv.
  • step A the CRBT AS sends the call request message that the calling party carries the SDP request to the called party, and adds a zero bandwidth identifier to the SDP information.
  • step C the CRBT AS carries the SDP request sent by the called party by using an update UPDATE message or a reply message to send it to the calling party.
  • step B the CRBT AS requests the called party to send an SDP request by using a re-INVITE message without any SDP information, and the called party sends an SDP request by using a response message starting with "2" of the re-INVITE.
  • FIG. 1 is a basic message flow diagram of a single-talk CRBT service in the prior art
  • FIG. 2 is a flowchart of a specific implementation of a call setup method for implementing a single-talk CRBT service according to an embodiment of the present invention
  • FIG. 4 is a basic message flow chart of application example 2 according to an embodiment of the present invention
  • FIG. 5 is a basic message flow chart of application example 3 according to an embodiment of the present invention.
  • a call setup method for implementing a single-talk CRBT service is provided.
  • the CRBT AS uses a single-talk mode to play to the calling party.
  • the caller is sent to the calling party; the subsequent calling party, the ring back tone AS and the called party implement call establishment according to a standard procedure.
  • FIG. 2 is a method for establishing a call for a single-talk CRBT service according to an embodiment of the present invention. As shown in FIG.
  • Step 201 The calling party initiates a call, and the CRBT The AS broadcasts the media information to the calling party in a single conversation manner;
  • Step 203 The called party answers the call, and the CRBT AS requests the called party to send an SDP request after receiving the response message of the called party and before forwarding the response message;
  • the CRBT AS may carry the SDP request sent by the called party by using an UPDATE message or a response message, and send the message to the calling party.
  • Step 205 The CRBT AS receives the SDP sent by the called party.
  • Step 207 the subsequent calling party, the CRBT AS and the called party implement call establishment according to a standard procedure. It can be seen from the above that if the response message carries the SDP request sent by the called party, the process between the response and the start of the call is greatly simplified. The details of the above steps are specifically described below.
  • Step 201 The calling party initiates the call, where the calling party sends a call request message carrying the SDP request;
  • Step 201 may further include: after receiving the call request message that the calling party carries the SDP request, the CRBT AS forwards the call request message to the called party, where the called party returns a response message, where the message carries an SDP response.
  • the CRBT AS interacts with the CRBT media server to forward the SDP request or response of the CRBT session to the calling party.
  • the start time of the CRBT can be any time after receiving the call until before receiving the response.
  • the SDP information of the CRBT session sent to the calling party includes all media types in the SDP request of the calling party or the SDP response of the called party.
  • the CRBT AS sets the direction indication of some or all of the media types in the SDP information of the CRBT session sent to the calling party to sendonly (send only).
  • the CRBT AS adds a P-Early-Media header field to the SIP message that sends the SDP information of the CRBT session, and the value of the ⁇ 1 jt header is set to sendonly.
  • the CRBT AS receives the new SDP request from the calling party, and changes the direction indication of the media type whose direction is indicated as recvonly to sendrecv (both sent and received). ).
  • the step 201 further includes: in order to prevent the data transmission error of the called party, the CRBT AS may forward the message to the called party after receiving the message of the SDP request, and add zero to the SDP information.
  • Step 203 In step 203, the SDP request of the CRBT session sent to the calling party is carried by the UPDATE message; the SDP response of the CRBT session sent to the calling party is a response message initiated by "1" of the INVITE message, or PRACK The response message starting with the "2" of the message is carried.
  • the SDP request is carried by the UPDATE message in order to enable the CRBT service to use a richer media type, and is not limited only by the type of media used in the SDP request sent by the calling party at the beginning of the call.
  • the CRBT AS requests the called party using a re-INVITE message without any SDP information.
  • the party sends an SDP request, and the called party sends an SDP request through a response message starting with "2" of re-INVITE.
  • Step 207 specifically includes: The calling party returns an SDP response, and after the CRBT AS forwards it to the called party, the calling party and the called party establish a call.
  • the invention will be further illustrated by three application examples below.
  • Example 1 FIG. 3 shows an application example 1 of the embodiment of the present invention. As shown in FIG. 3, the calling user is called to call the called user, and the CRBT server plays the ring back tone to the calling user during the call, when the called party is called.
  • Step 301 The calling user UE-A initiates a call request, and the request carries an SDP request, for example, sending an INVITE (invitation)
  • the message carries the SDP request in the message body, and the message is forwarded to the CRBT AS via the P-CSCF and the S-CSCF.
  • Step 302 The CRBT AS forwards the call message to the called user UE-B, in order to prevent the data transmission error of the UE-B.
  • the CRBT AS may add a zero bandwidth identifier to the SDP information, and the message passes through the S-CSCF.
  • Step 303 The called UE-B replies with a temporary response message to the calling party, for example, sending a "180 Ringing" or "183 Session Progress" message.
  • the message body may carry the SDP response of the UE-B, and the temporary response message passes through the S-CSCF to the CRBT AS;
  • Steps 304 to 305, and FIG. Steps 104 to 105 are equivalent;
  • Step 306 The CRBT AS sends an SDP response of the CRBT session to the calling party, for example, by using a temporary response message of the call message, and the temporary response message may be a "183 Session Progress" message or a "180 Ringing" message.
  • the message body carries the SDP response of the CRBT session, and the CRBT AS can modify the direction indication of some or all of the media types in the SDP response to sendonly (send only), or add force to the message.
  • P-Early-Media header or, and the value of this header field is set to sendonly, and the message arrives at UE-A via S-CSCF and P-CSCF;
  • Steps 307-309 are the same as steps 107-109 of FIG. 1.
  • Step 310 The CRBT AS sends an acknowledgement response message to the called party, for example, sending an ACK message, and the message arrives at the UE-B via the S-CSCF;
  • Step 311 at the same time, the CRBT The AS requests the called party to send an SDP request, such as sending a re-INVITE message without any SDP information, and the message arrives at the UE-B via the S-CSCF;
  • the following steps 313-314 are optional execution steps, and may not be performed.
  • Step 313 After receiving the SDP request of the called party, the CRBT AS sends an update message to the calling party, for example, sending an UPDATE message, where the message body carries the SDP request of the called party, and the message arrives through the S-CSCF and the P-CSCF.
  • UE-A Step 314: The UE-A receives the update message and sends a message agreeing to the update, for example, sending a response message starting with "2", such as a "200 OK" message, the message body carrying the SDP response, and the message passing through the P-
  • the CSCF and S-CSCF arrive at the CRBT AS; the following steps 315, 317 and 318 are described in the case where steps 313-314 are not performed.
  • Step 315 After receiving the SDP request of the called party, the CRBT AS sends a response message to the calling party, for example, sending a message starting with "2", such as a "200 OK" message, where the message body carries the SDP request of the called party.
  • the message passes the P-CSCF;
  • Step 316 The P-CSCF receives the response message, and instructs the charging function to start charging.
  • Step 317 At the same time, the P-CSCF forwards the response message to the UE-A.
  • Step 318 UE-A Receiving a response message, sending an acknowledgement response message to the called party, for example, sending an ACK message, the message body carrying the SDP response of the calling party, and the message passing through the P-CSCF and the S-CSCF to reach the CRBT AS; wherein, if the step is performed 313 ⁇ 314, then no SDP information is carried in the messages of steps 315, 317 and 318.
  • Step 319 The CRBT AS forwards the acknowledgement response message to the UE-B, where the SDP response of the calling party is carried, and the response message passes through the S-CSCF. Step 319 may occur after receiving the message carrying the SDP response of the calling party. At any time, if there are steps 313, 314, it occurs any time after step 314, otherwise it occurs after step 318.
  • Step 320 UE-A and UE-B establish a media connection and start a call.
  • FIG. 4 shows an application example 2 according to an embodiment of the present invention. As shown in FIG. 4, the calling user is called to call the called user, and the CRBT is playing the ring back tone to the calling user during the call.
  • Step 401 UE-A initiates a call request, carries an SDP request, for example, sends an INVITE message.
  • the SDP request is carried in the message body, and the P-CSCF and the S-CSCF are forwarded to the CRBT AS.
  • Step 402 The CRBT AS forwards the call message to the UE-B, and the message passes through the S-CSCF.
  • Step 403 Called The UE-B sends a temporary response message to the calling party, for example, sending a temporary response message starting with "1" such as "183 Session Progress" message, and the message body carries the called SDP response, and the temporary response message arrives through the S-CSCF.
  • Step 404 the CRBT AS calls the CRBT media server, carries the SDP request in step 401, or the SDP request generated based on the SDP response in step 403, and the message passes through the S-CSCF; wherein, step 404 can occur. Any time prior to step 405 after step 401.
  • Step 405 The CRBT media server answers the call, for example, sending a message starting with "2" such as "200 OK" message to the CRBT AS, carrying the SDP response of the CRBT session, and the message passing through the S-CSCF; Step 406, the CRBT AS to the calling party
  • the SDP response of the CRBT session is sent or the SDP response carried in step 403 is carried, for example, by a temporary response message of the call message.
  • the temporary response message may be a message such as "183 Session Progress" message or "180 Ringing" message starting with "1".
  • the message body carries the SDP response, and the carried SDP response may be a color ring tone session SDP response, and
  • Some or all of the media types in the SDP request of step 401, or some or all of the media types in the SDP response of step 403 may be added to the color ringback session SDP response according to the standard method, or may be the step 403.
  • the SDP responds to ensure that the media type used by the session is not reduced due to the reduction of the CRBT service.
  • the CRBT AS can also change the direction indication of some or all of the media types in the carried SDP response to send-only.
  • step 406 sends the SDP response carried in step 403 to the calling party. In 408, it is a call request, in step 409, it is a response message, and step 411 is not executed.
  • Step 407 The UE-A receives the temporary response message, and sends a pre-acknowledgment message to the called party, for example, sends a PRACK message, where the message body carries the new SDP request of the calling party, and the message passes through the P-CSCF and the S-CSCF.
  • Step 408 The CRBT AS sends a pre-confirmation message to the CRBT media server, for example, sending
  • the PRACK message carries the SDP request in step 407, and the message passes through the S-CSCF.
  • the CRBT media server receives the message of step 408, and sends a response pre-acknowledgment message, such as sending a "200 OK" message.
  • the message starting with "2" the message body carries the SDP response of the new CRBT session, and the message arrives at the CRBT AS via the S-CSCF;
  • Step 410 the CRBT AS sends a response pre-acknowledgment message to the calling party, for example, sending "200 OK”
  • the message, such as a message starting with "2” carries the SDP response in step 309, and the message arrives at the UE-A via the S-CSCF and the P-CSCF;
  • Step 411 the CRBT server answers the call, such as sending "
  • the 200 OK message such as the message "2" is given to the CRBT AS; wherein there is no limitation on the execution of the steps 411 and 410.
  • Step 412 After receiving the response message from the CRBT server, the CRBT AS sends an acknowledgement message to the CRBT server, for example, sends an ACK message, and the message passes through the S-CSCF.
  • Step 413 The CRBT AS forwards the pre-acknowledgment message of step 407 to the called party. And can add a zero bandwidth identifier in the SDP request in the pre-acknowledgment message to prevent data transmission error of UE-B.
  • Step 414 UE-B receives the pre-acknowledgment message, and sends a response pre-acknowledgment message, for example, sending "200"
  • the OK message is a message starting with "2", the message body carries the called new SDP response, and the message arrives at the CRBT AS via the S-CSCF;
  • Step 415 after receiving the confirmation response message, the CRBT media server sends the message to the main
  • the calling party plays the CRBT; wherein, step 415 can occur at any time after step 409 to before step 416.
  • Steps 416 to 419 are equivalent to steps 309 to 312 in FIG. 3; wherein, between steps 419 and 420, The steps equivalent to steps 313-314 of Figure 3 can be inserted, and if so, no SDP information is carried in the messages of steps 420, 422, and 423.
  • Steps 420-425 are equivalent to steps 315-320 of Figure 3.
  • FIG. 5 shows an application example 3 according to an embodiment of the present invention.
  • the calling user is called to call the called user, and the CRBT is playing the ring back tone to the calling user during the call.
  • the CRBT server initiates media renegotiation, which mainly includes the following steps (step 501-step 520): Steps 501-503, and step 401 ⁇ in FIG.
  • Step 504 The CRBT AS forwards the temporary response message to the calling party, and the message arrives at the UE-A through the S-CSCF and the P-CSCF. Step 505.
  • the CRBT AS calls the CRBT media server, for example, sends an INVITE message, without carrying any SDP information, the message passes through the S-CSCF; wherein, step 505 can occur any time after step 501 to before step 506.
  • Step 506 the CRBT media server answers the call, for example, sending a "200 OK" message to "2"
  • the message is sent to the CRBT AS, and the message carries the SDP request of the CRBT session and passes through the S-CSCF.
  • the SDP request carrying the CRBT session, the message arrives at the UE-A via the S-CSCF and the P-CSCF, and the SDP request in the above message may need to be adjusted on the basis of the SDP request in step 506 according to the requirements of the standard.
  • the CRBT AS can also modify the direction indication of some or all of the media types in the carried SDP request to send-only, or add force to the message.
  • Step 508 UE-A receives the update message, sends a consent update message to the called party, for example, sends a "200 OK" message. Waiting for the message starting with "2", the message body carries the SDP response of the calling party, and the message arrives at the CRBT AS via the P-CSCF and the S-CSCF; Step 509, after receiving the SDP response of the calling party, the CRBT AS receives Sending an acknowledgment response message to the CRBT media server, for example, sending an ACK message, where the message body carries the SDP response of the calling party, and the message passes through the S-CSCF.
  • Step S510 After receiving the confirmation response message, the CRBT media server plays the CRBT to the calling party.
  • Steps 511 to 520 are basically the same as steps 416 to 425 in FIG. 4, but only according to the standard.
  • the SDP request in step 515 may need to be adjusted on the basis of the SDP request in step 514.
  • the SDP response in step 519 may need to be adjusted based on the SDP response in step 518;
  • Excellent of the invention overcomes the limitations of the prior art, so that the CRBT service can implement playback of any media type and its combination; another optimization scheme can reduce the media type used by the finally established session without being reduced due to the media type of the CRBT service; There is also an optimization scheme to prevent data transmission errors from the called party.
  • the technical solution of the present invention improves the processing after the called response, reduces the interaction step after the response, and adjusts the time for starting the charging, so that the process from the response to the start of the call is greatly simplified, and the user experience is improved. , avoiding the wrong deduction.
  • steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network of multiple computing devices.
  • they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be fabricated into individual integrated circuit modules, or multiple of them Steps to make a single integrated circuit

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)

Description

实现单对话彩铃业务的呼叫建立方法
技术领域 本发明涉及通信领域， 更具体地， 涉及 IP多媒体子系统中一种实现单 对话彩铃业务的呼叫建立方法。 背景技术 网络互联十办议（ Internet Protocol，简称为 IP )多媒体子系统（ IP Multimedia Core Network Subsystem , 简称为 IMS ) 是由第三代合作伙伴计划 ( 3rd Generation Partnership Project,简称为 3GPP )提出的一种基于 IP的网络架构， 其构建了一个开放而灵活的业务环境， 用以支持多媒体应用， 从而可以为用 户提供丰富的多媒体业务。 在 IMS业务体系中， 控制层和业务层是相互分离的， 控制层不提供具 体业务功能， 只向业务层提供必要的触发、 路由、 计费等功能。 控制层中业 务触发和控制功能是通过呼叫会话控制功能 （ Call Session Control Function, 简称为 CSCF ) 来完成的， CSCF分为代理会话控制功能 （Proxy CSCF, 简 称为 P-CSCF )、 查询会话控制功能（ Interrogating CSCF , 简称为 I-CSCF )和 月 务会话控制功能（Serving CSCF , 简称为 S-CSCF )三种类型， 其中， 绝大 多数采用 S-CSCF , 查询类型是可选的。 业务层是由一系列应用服务器 ( Application Server, 简称为 AS )组成的， 能够提供具体业务月 务。 控制层 ( S-CSCF )才艮据用户的签约信息控制业务触发， 调用 AS上的业务， 实现业 务功能。 会话中的端到端设备称为用户设备 ( User Equipment , 简称为 UE ) , 负责与使用者的交互。 上述功能实体使用会话初始协议 （Session Initiation Protocol, 简称为 SIP )协议通讯。 在需要播放多媒体信息的业务中， 需要力口 入多媒体资源功能（ Media Resource Function, 简称为 MRF ), 也称为媒体月 务器， 其包括控制部分多媒体资源功能控制器（ Multimedia Resource Function Controller , 简称为 MRFC ) 和媒体处理部分多媒体资源功能处理器 ( Multimedia Resource Function Processor, 简称为 MRFP ), 其中， 控制 分 MRFC负责将软交换与策略月 务器（ Soft switch and Policy Server,简称为 SE ) 的 SIP信令翻译和解释为对应于 MRFP的指令，或者反之将 MRFP的回应翻 译和解释为向 SE发送的 SIP信令； 媒体处理部分 MRFP负责媒体流的发送 和接收。
1 P23857 SIP协议可以作为会话描述协议 ( Session Description Protocol, 简称为 SDP ) 的承载层， SDP负责进行媒体资源信息的协商， 包括媒体类型、 媒体 连接地址、 媒体连接端口、 带宽要求等信息。 SDP协议内容分为请求和响应 两种， 每个请求必须对应一个响应。 呼叫建立过程中同时向主叫播放多媒体信息的业务是 IMS 中的一种业 务， 该业务也可称为彩铃业务， 其允许在呼叫过程中， 向主叫方播放由被叫 方事先定制好的多媒体信息， 并在被叫方应答后停止尚未停止的多媒体信息 播放。 单对话彩铃是彩铃业务的一种实现方式， 即在一个 SIP对话中完成业 务实现， 而不需要引入新的对话。 为了简化描述， 图示中将彩铃 AS和 S-CSCF画成了一个实体， 他们两 者之间的交互是标准的流程。 图 1为相关的单对话彩铃业务的基本消息流程图，描述了现有技术中主 叫用户呼叫被叫用户， 彩铃 AS在呼叫过程中向主叫用户播放彩铃， 当被叫 用户应答后， 彩铃服务器发起媒体重协商的状况， 如图 1所示， 主要包括以 下步骤 (步骤 101-步骤 120 ): 步骤 101、 主叫用户 UE- A发起呼叫请求， 其中， 该呼叫请求携带 SDP 请求， 比如发送 INVITE (邀请） 消息， 在消息体中携带 SDP请求， 该消息 途经 P-CSCF和 S-CSCF的转发到达彩铃 AS; 步骤 102、 彩铃 AS 转发该呼叫请求给被叫用户 UE-B , 消息途经 S-CSCF; 步骤 103、被叫用户 UE-B振铃，回复振铃消息给主叫方，比如发送" 180 Ringing" 消息， 该振铃消息途经 S-CSCF到达彩铃 AS; 步骤 104、彩铃 AS呼叫彩铃媒体服务器，携带步骤 101中的 SDP请求， 消息途经 S-CSCF; 步骤 105、 彩铃媒体服务器应答呼叫， 比如发送 " 200 OK" 消息给彩铃
AS, 该消息携带彩铃会话的 SDP响应， 消息途经 S-CSCF。 按标准要求该响 应所使用的媒体类型都必须包含于 SDP请求中， 但可以比 SDP请求中的媒 体类型少； 步骤 106、 彩铃 AS向主叫方发送彩铃会话的 SDP响应， 比如通过呼叫
2 P23857 消息的临时回应消息携带该响应， 临时回应消息可以是 " 183 Session Progress" 消息或 "180 Ringing" 消息等以 "1 " 打头的消息， 消息体中携带 彩铃会话的 SDP响应， 消息途经 S-CSCF和 P-CSCF到达 UE-A; 步骤 107、彩铃 AS向彩铃媒体服务器发送确认应答消息，比如发送 ACK (确认） 消息， 该消息途经 S-CSCF; 其中， 步骤 106和 107可以不按先后顺序同时执行。 步骤 108、彩铃媒体服务器收到彩铃 AS发送的确认应答消息，向 UE-A 播放彩铃； 其中， 步骤 104至 108可以在步骤 101至 109中的任何时间执行。 按标准要求， 步骤 106至 108之间， 主叫可能还会与被叫进一步协商媒 体资源信息， 而后续的协商都是基于上述协商结果的， 由于主叫实际上是与 彩铃媒体服务器协商媒体， 所以当彩铃媒体的媒体类型较步骤 101中的 SDP 请求中的媒体类型少时， 主叫会认为被叫只愿意进行较少媒体类型的通话， 被叫也会认为主叫减少了愿意使用的媒体类型， 从而使得主被叫在通话前都 只准备了较少媒体类型的资源。 步骤 109、 被叫用户 UE-B应答呼叫， 发送应答消息给主叫方， 比如发 送 "200 OK" 消息， 该消息携带被叫用户的 SDP响应， 并途经 S-CSCF到达 彩铃 AS; 步骤 110、 彩铃 AS删除应答消息中的 SDP响应后， 转发给主叫方， 消 息途经 S-CSCF和 P-CSCF; 步骤 111、 P-CSCF收到应答消息， 并指示计费功能开始计费； 步骤 112、 P-CSCF转发应答消息给 UE-A; 其中， 步骤 111和 112可以不按先后顺序同时执行。 步骤 113、 UE-A收到应答消息， 发送确认应答消息给被叫方， 比如发 送 ACK消息， 该消息途经 P-CSCF和 S-CSCF到达彩铃 AS; 步骤 114、 彩铃 AS转发确认应答消息给 UE-B, 该消息途经 S-CSCF;
3 P23857 步骤 115、 同时， 彩铃 AS向被叫方询问其正在使用的 SDP信息， 比如 发送不带任何 SDP信息的 re-INVITE (重呼叫） 消息， 该消息途经 S-CSCF 到达 UE-B; 其中， 对于步骤 114和 115的执行， 没有先后顺序的限制。 步骤 116、 UE-B收到重呼叫消息， 返回 UE-B正在使用的 SDP信息， 并以 SDP请求的形式通过回应重呼叫消息携带该 SDP信息并发往主叫方， 回应重呼叫消息可以是 "200 OK" 消息， SDP请求通过上述回应重呼叫消息 体携带， 该消息途经 S-CSCF到达彩铃 AS; 由前述分析可知， 此时的 SDP请求使用的媒体类型可能比步骤 101 中 的 SDP请求使用的媒体类型少。 步骤 117、 彩铃 AS收到被叫方的 SDP请求后， 向主叫方发送重呼叫消 息， 该消息体中携带所收到的被叫方的 SDP请求， 途经 S-CSCF和 P-CSCF 到达 UE-A; 步骤 118、 UE-A ^：到重呼叫消息， 发送回应重呼叫消息给被叫方， 比 如发送 "200 OK"消息， 该消息体中携带 SDP响应，途经 P-CSCF和 S-CSCF 到达彩铃 AS; 步骤 119、 彩铃 AS向被叫方发送确认回应消息， 比如发送 ACK消息， 消息体中携带所收到的主叫方的 SDP响应， 消息途经 S-CSCF到达 UE-B; 步骤 120、 UE-A和 UE-B建立起媒体连接， 开始通话。 通过以上技术方案， 可以得出， 现有技术的不足之处在于： 计费开始得 太早， 计费开始后， 尚有许多信令往来才能真正开始通话， 使得计费信息与 实际情况有较大出入， 会导致用户体验降低； 而且被叫应答后， 尚有许多信 令往来才能开始通话， 上述信令往来会明显花费相当多时间， 增加了用户等 待时间， 甚至可能导致用户认为发生了问题而挂断通话。 另外， 现有技术中 的彩铃业务方案能使用的媒体类型受限于主叫呼叫时指定的媒体类型， 而且 当彩铃业务的媒体类型只包括音频时， 主、 被叫用户即使为具备视频通话功 能的终端并且主叫愿意进行视频通话时，在应答后也可能只能采用音频通话， 因此具有局限性。
4 P23857 发明内容 针对上述被叫应答过程复杂， 用户体验较低， 计费开始时间不合理等问 题而提出本发明， 为此， 本发明旨在提供一种实现单对话彩铃业务的呼叫建 立方法， 用于解决上述问题至少之一。 为了解决上述问题， 才艮据本发明， 提供了一种实现单对话彩铃业务的呼 叫建立方法。 根据本发明提供的实现单对话彩铃业务的呼叫建立方法，主要包括以下 步骤：
A、 主叫方发起呼叫， 彩铃应用服务器 AS采用单对话方式向主叫方播 放媒体信息；
B、 被叫方应答呼叫， 彩铃 AS在收到被叫方的应答消息后且在转发应 答消息前， 请求被叫方发送 SDP请求；
C、 彩铃 AS收到被叫方发送的 SDP请求后将其发给主叫方；
D、 主叫方、 彩铃 AS和被叫方按标准过程实现通话建立。 进一步地， 步骤 A 中， 主叫方发起呼叫具体包括： 主叫方向彩铃 AS 发送携带 SDP请求的呼叫请求消息； 步骤 A中， 彩铃 AS在收到呼叫请求消息后转发给被叫方， 被叫方返回 回应消息， 其中， 该消息携带 SDP响应； 进一步地， 步骤 A中， 彩铃 AS收到主叫方的消息或被叫方的消息后， 与彩铃媒体^^务器实现交互操作， 向主叫方转发彩铃会话的 SDP 请求或响 应。 进一步地， 步骤 A 中： 向主叫方发送的彩铃会话的 SDP 请求通过 UPDATE消息携带。 进一步地， 步骤 A中： 向主叫方发送的彩铃会话的 SDP信息包含主叫 方的 SDP请求或被叫方的 SDP响应中的所有媒体类型。 进一步地， 步骤 A中： 彩铃 AS将向主叫方发送的彩铃会话的 SDP信
5 P23857 息中的部分或全部媒体类型的方向指示设置为只发送 sendonly。 进一步地， 步骤 A中： 彩铃 AS在发送彩铃会话的 SDP信息的会话初 始十办议 SIP消息中增力口 P-Early-Media头域, 并将此头或的值设为 sendonly。 进一步地， 步骤 A中： 彩铃 AS在发送彩铃会话 SDP信息后， 如果收 到主叫方新的 SDP请求，则将其中方向指示为只接收 recvonly的媒体类型的 方向指示爹改为既发送也接收 sendrecv。 进一步地， 步骤 A中， 彩铃 AS收到主叫方携带 SDP请求的呼叫请求 消息后发给被叫方， 并在 SDP信息中增加零带宽标识。 进一步地， 步骤 C中， 彩铃 AS通过使用更新 UPDATE消息或应答消 息携带被叫方发送的 SDP请求， 以将其发送给主叫方。 进一步地， 步骤 B中： 彩铃 AS使用不带任何 SDP信息的 re-INVITE消息来请求被叫方发送 SDP请求， 被叫方通过 re-INVITE的 "2" 开头的回应消息发送 SDP请求。 借助于本发明的上述技术方案至少之一，由于通过本发明的技术方案对 被叫应答后的处理进行了改进， 减少了应答后的交互步骤， 并且调整了开始 计费的时间， 从而可以使应答到通话开始之间的过程大为简化， 改善了用户 的体验， 避免了错误的扣费。 附图说明 图 1为现有技术的单对话彩铃业务的基本消息流程图； 图 2 为根据本发明实施例提供的实现单对话彩铃业务的呼叫建立方法 的具体实施流程图； 图 3为根据本发明实施例的应用实例一的基本消息流程图； 图 4为根据本发明实施例的应用实例二的基本消息流程图； 图 5为根据本发明实施例的应用实例三的基本消息流程图。
6 P23857 具体实施方式 功能相克述 本发明实施例中， 提供了一种实现单对话彩铃业务的呼叫建立方法， 在 该方法中， 当主叫方发起呼叫时， 彩铃 AS采用单对话方式向主叫方播放媒 体信息； 被叫方应答呼叫， 彩铃 AS在收到被叫方的应答消息后且在转发该 应答消息前， 请求被叫方发送 SDP请求； 彩铃 AS收到被叫方发送的该 SDP 请求后将其发给主叫方； 后续主叫方、 彩铃 AS和被叫方按标准过程实现通 话建立。 下面将结合附图及实施例对本发明的技术方案进行更详细的说明。需要 说明的是， 如果不沖突， 本申请中的实施例以及实施例中的特征可以相互组 合。 图 2 为根据本发明实施例提供的一种实现单对话彩铃业务的呼叫建立 方法， 如图 2所示， 主要包括以下步骤（步骤 201-步骤 207 ): 步骤 201、 主叫方发起呼叫， 彩铃 AS采用单对话方式向主叫方播放媒 体信息； 步骤 203、 被叫方应答呼叫， 彩铃 AS在收到被叫方的应答消息后且在 转发该应答消息前， 请求被叫方发送 SDP请求； 优选地， 在该步骤中， 彩铃 AS可以通过使用 UPDATE消息或应答消息携带被叫方发送的 SDP请求， 并 将上述消息发送给主叫方； 步骤 205、 彩铃 AS收到被叫方发送的 SDP请求后将其发给主叫方； 步骤 207、 后续主叫方、 彩铃 AS和被叫方按标准过程实现通话建立。 由上可以看出， 如果使用应答消息携带被叫方发送的 SDP请求， 则应 答后和开始通话间的过程被大大简化了。 以下具体描述上述步骤的细节。 (一） 步骤 201 主叫方发起呼叫是指主叫方发送携带 SDP请求的呼叫请求消息；
P23857 步骤 201还可以包括: 彩铃 AS接收到主叫方携带 SDP请求的呼叫请求消息后， 将其转发给 被叫方， 被叫方返回回应消息， 其中， 该消息携带 SDP响应。 彩铃 AS在接收到主叫方的呼叫请求消息或被叫方的回应消息后， 与彩 铃媒体服务器实现交互操作， 向主叫方转发彩铃会话的 SDP请求或响应。 从 而使得彩铃的开始时刻可以是在接收到呼叫后至接收到应答前的任意时刻。 优选地， 向主叫方发送的彩铃会话的 SDP信息包含主叫方的 SDP请求 或被叫方的 SDP响应中的所有媒体类型。 优选地， 彩铃 AS将向主叫方发送的彩铃会话的 SDP信息中的部分或 全部媒体类型的方向指示设置为 sendonly (只发送）。 优选地， 彩铃 AS 在发送彩铃会话的 SDP 信息的 SIP 消息中增加 P-Early-Media头域， 并^1 jt匕头或的值设为 sendonly。 优选地， 彩铃 AS在发送彩铃会话 SDP信息后， 如果收到主叫方新的 SDP请求， 则将其中方向指示为 recvonly (只接收） 的媒体类型的方向指示 爹改为 sendrecv (既发送也接收）。 优选地， 步骤 201还包括： 为了防止被叫方发生数据传递错误的现象， 彩铃 AS接收到主叫方携带 SDP请求的消息后， 可以将其转发给被叫方， 并在 SDP信息中增加零带宽标 识——即将所有媒体的带宽要求设为 0。 (二） 步骤 203 步骤 203中， 向主叫方发送的彩铃会话的 SDP请求通过 UPDATE消息 携带； 向主叫方发送的彩铃会话的 SDP响应通过 INVITE消息的 " 1" 开头 的回应消息、 或 PRACK消息的 "2" 开头的回应消息携带。
SDP请求通过 UPDATE消息携带是为了使彩铃业务能够使用更丰富的 媒体类型，而不只受限于呼叫开始时主叫方发出的 SDP请求中使用的媒体类 型。 优选地，彩铃 AS使用不带任何 SDP信息的 re-INVITE消息来请求被叫
8 P23857 方发送 SDP请求， 被叫方通过 re-INVITE的 "2" 开头的回应消息发送 SDP 请求。
(三） 步骤 207 步骤 207具体包括： 主叫方返回 SDP响应， 彩铃 AS将其转发给被叫 方后， 主被叫双方建立通话。 下面用三个应用实例进一步说明本发明。 实例一 图 3示出了本发明实施例的应用实例一， 如图 3所示， 描述了主叫用户 呼叫被叫用户， 彩铃月 务器在呼叫过程中向主叫用户播放彩铃， 当被叫用户 应答后， 彩铃服务器发起媒体重协商的情况， 主要包括以下步骤（步骤 301- 步骤 320 ): 步骤 301、 主叫用户 UE-A发起呼叫请求， 该请求携带 SDP请求， 比如 发送 INVITE (邀请） 消息， 在消息体中携带 SDP请求， 消息途经 P-CSCF 和 S-CSCF转发至彩铃 AS; 步骤 302、 彩铃 AS转发该呼叫消息给被叫用户 UE-B, 为防止 UE-B发 生数据传递错误， 彩铃 AS 可在 SDP 信息中增加零带宽标识， 消息途经 S-CSCF; 步骤 303、 被叫 UE-B 回复临时回应消息给主叫方， 比如， 发送 " 180 Ringing" 或 " 183 Session Progress" 消息等以 " 1" 开头的消息， 消息体中可 携带 UE-B的 SDP响应， 该临时回应消息途经 S-CSCF至彩铃 AS; 步骤 304〜305、 与图 1的步骤 104〜105等同； 步骤 306、 彩铃 AS向主叫方发送彩铃会话的 SDP响应， 比如通过呼叫 消息的临时回应消息携带， 临时回应消息可以是 "183 Session Progress" 消 息或 " 180 Ringing" 消息等以 " 1 " 打头的消息， 消息体中携带彩铃会话的 SDP响应， 彩铃 AS可将此 SDP响应中的部分或全部媒体类型的方向指示修 改为 sendonly (只发送）， 或在消息中添力。 P-Early-Media头或， 并可将此头 域的值设为 sendonly, 消息途经 S-CSCF和 P-CSCF到达 UE-A;
9 P23857 步骤 307〜309、 与图 1的步骤 107〜109等同； 步骤 310、 彩铃 AS向被叫方发送确认应答消息， 比如发送 ACK消息， 消息途经 S-CSCF到达 UE-B; 步骤 311、 同时， 彩铃 AS请求被叫方发送 SDP请求， 比如发送不带任 何 SDP信息的 re-INVITE (重呼叫） 消息， 该消息途经 S-CSCF到达 UE-B; 步骤 312、 UE-B接收到步骤 311 的请求消息， 发送回应重呼叫消息， 比如发送 "200 OK" 消息， 该消息体中携带 SDP请求， 消息途经 S-CSCF 到达彩铃 AS; 以下的步骤 313〜314是可选的执行步骤， 一般可以不执行。 步骤 313、 彩铃 AS接收到被叫方的 SDP请求后， 向主叫方发送更新消 息， 比如发送 UPDATE消息， 该消息体中携带被叫方的 SDP请求， 消息途 经 S-CSCF和 P-CSCF到达 UE-A; 步骤 314、 UE-A接收到更新消息，发送同意更新的消息，比如发送 "200 OK" 消息等以 "2" 开头的回应消息， 该消息体中携带 SDP响应， 消息途经 P-CSCF和 S-CSCF到达彩铃 AS; 以下步骤 315、 317和 318以步骤 313〜314没有执行的情况来描述。 步骤 315、彩铃 AS收到被叫方的 SDP请求后，向主叫方发送应答消息， 比如发送 "200 OK" 消息等以 "2" 开头的消息， 该消息体中携带被叫方的 SDP请求， 该消息途经 P-CSCF; 步骤 316、 P-CSCF收到应答消息， 并指示计费功能开始计费； 步骤 317、 同时， P-CSCF转发应答消息给 UE-A; 步骤 318、 UE-A接收到应答消息， 发送确认应答消息给被叫方， 比如 发送 ACK消息， 该消息体中携带主叫方的 SDP响应， 消息途经 P-CSCF和 S-CSCF到达彩铃 AS; 其中， 如果执行了步骤 313〜314 , 则步骤 315、 317和 318的消息中都 不会携带任何 SDP信息。
10 P23857 步骤 319、彩铃 AS转发确认应答消息给 UE-B ,其中携带主叫方的 SDP 响应， 该响应消息途经 S-CSCF; 其中， 步骤 319可发生在收到携带主叫方的 SDP响应的消息后的任何 时候， 如果有步骤 313、 314, 则是发生在步骤 314后的任何时候， 否则， 则 是发生在步骤 318后。 步骤 320、 UE-A和 UE-B建立起媒体连接， 开始通话。 实例二 图 4示出了^ f艮据本发明实施例的应用实例二， 如图 4所示， 描述了主叫 用户呼叫被叫用户， 彩铃月 务器在呼叫过程中向主叫用户播放彩铃， 当被叫 用户应答后， 彩铃服务器发起媒体重协商的情况， 主要包括以下步骤 （步骤 401-步骤 425 ): 步骤 401、 UE-A发起呼叫请求， 携带 SDP请求， 比如发送 INVITE (邀 请） 消息， 在该消息体中携带 SDP请求， 途经 P-CSCF和 S-CSCF的转发到 达彩铃 AS; 步骤 402、 彩铃 AS转发该呼叫消息给 UE-B, 该消息途经 S-CSCF; 步骤 403、被叫 UE-B发送临时回应消息给主叫方，比如发送" 183 Session Progress" 消息等以 "1 " 开头的临时回应消息， 消息体中携带被叫的 SDP响 应， 该临时回应消息途经 S-CSCF到达彩铃 AS; 步骤 404、彩铃 AS呼叫彩铃媒体服务器，携带步骤 401中的 SDP请求， 或基于步骤 403中的 SDP响应生成的 SDP请求， 消息途经 S-CSCF; 其中， 步骤 404可发生在步骤 401之后至步骤 405之前的任何时刻。 步骤 405、彩铃媒体服务器应答呼叫， 比如发送" 200 OK"消息等以 "2" 开头的消息给彩铃 AS , 携带彩铃会话的 SDP响应， 消息途经 S-CSCF; 步骤 406、彩铃 AS向主叫方发送彩铃会话的 SDP响应或步骤 403中携 带的 SDP响应， 比如通过呼叫消息的临时回应消息携带， 临时回应消息可以 是 " 183 Session Progress" 消息或 " 180 Ringing" 消息等以 " 1" 开头的消息， 该消息体中携带 SDP响应， 携带的 SDP响应可以是彩铃会话 SDP响应， 也
11 P23857 可以按标准 ^故法， 在彩铃会话 SDP响应的基础上添加步骤 401的 SDP请求 中的部分或全部媒体类型，或步骤 403的 SDP响应中的部分或全部媒体类型， 还可以是步骤 403中的 SDP响应，以保证最终建立的会话使用的媒体类型不 会因彩铃业务的减少而减少， 彩铃 AS还可将携带的 SDP响应中的部分或全 部媒体类型的方向指示爹改为 send— only (只发送）， 或在消息中添加 P-Early-Media 头域, 并可将此头或的值设为 send— only, 消息途经 S-CSCF 和 P-CSCF到达 UE-A; 其中， 步骤 406可以发生在步骤 403之后至 407之前的任何时刻， 如果 步骤 404在步骤 406之前尚未发生， 则步骤 404-405可以不执行， 此时步骤 406向主叫方发送的是步骤 403中携带的 SDP响应，步骤 408中是呼叫请求， 步骤 409中是应答消息， 步骤 411不执行。 步骤 407、 UE-A收到临时回应消息， 发送预确认消息给被叫方， 比如 发送 PRACK 消息， 该消息体中携带主叫方的新的 SDP请求， 该消息途经 P-CSCF和 S-CSCF到达彩铃 AS; 步骤 408、 彩铃 AS 发送预确认消息给彩铃媒体服务器， 比如发送
PRACK消息，该消息体中携带步骤 407中的 SDP请求，该消息途经 S-CSCF; 步骤 409、彩铃媒体服务器收到步骤 408的消息，发送回应预确认消息， 比如发送 "200 OK" 消息等以 "2" 开头的消息， 该消息体携带新的彩铃会 话的 SDP响应， 该消息途经 S-CSCF到达彩铃 AS; 步骤 410、彩铃 AS发送回应预确认消息给主叫方， 比如发送 "200 OK" 消息等以 "2" 开头的消息， 该消息体中携带步骤 309中的 SDP响应， 该消 息途经 S-CSCF和 P-CSCF到达 UE-A; 步骤 411、 彩铃月 务器应答呼叫， 比如发送 "200 OK" 消息等以 "2" 开头的消息给彩铃 AS; 其中， 对于步骤 411和步骤 410的执行没有先后顺序的限制。 步骤 412、 彩铃 AS接收到彩铃服务器的应答消息后， 发送确认应答消 息给彩铃服务器， 比如发送 ACK消息， 该消息途经 S-CSCF; 步骤 413、 彩铃 AS转发步骤 407的预确认消息给被叫方， 并可在预确 认消息中的 SDP请求中增加零带宽标识， 以防止 UE-B发生数据传递错误，
12 P23857 同时， 如果步骤 406中彩铃 AS修改了媒体的方向指示， 则可将收到的 SDP 请求中的媒体类型的方向指示值为 recv— only (只接收） 的修 _改为 send— recv (即发送也接收）， 消息途经 S-CSCF到达 UE-B; 其中， 步骤 413可以发生在步骤 407之后至步骤 414之前的任何时刻。 步骤 414、 UE-B收到预确认消息，发送回应预确认消息，比如发送 "200
OK" 消息等以 "2" 开头的消息， 该消息体中携带被叫的新的 SDP响应， 该 消息途经 S-CSCF到达彩铃 AS; 步骤 415、 彩铃媒体服务器收到确认应答消息后， 向主叫方播放彩铃； 其中， 步骤 415可以发生在步骤 409之后至步骤 416之前的任何时刻。 步骤 416〜419、 与图 3中的步骤 309〜312等同； 其中， 在步骤 419和 420之间， 也可以插入与图 3中步骤 313〜314等同 的步骤， 如果这样， 则步骤 420、 422和 423的消息中都不会携带任何 SDP 信息。 步骤 420〜425与图 3中的步骤 315〜320等同。 实例三 图 5示出了^ f艮据本发明实施例的应用实例三， 如图 5所示， 描述了主叫 用户呼叫被叫用户， 彩铃月 务器在呼叫过程中向主叫用户播放彩铃， 当被叫 用户应答后， 彩铃服务器发起媒体重协商的情况， 主要包括以下步骤 （步骤 501-步骤 520 ): 步骤 501〜503、 与图 4中的步骤 401〜403等同； 步骤 504、 彩铃 AS转发临时回应消息给主叫方， 消息途经 S-CSCF和 P-CSCF到达 UE-A 步骤 505、 同时， 彩铃 AS呼叫彩铃媒体服务器， 比如发送 INVITE消 息， 不携带任何 SDP信息， 消息途经 S-CSCF; 其中， 步骤 505可发生在步骤 501之后至步骤 506之前的任何时候。 步骤 506、彩铃媒体服务器应答呼叫， 比如发送 "200 OK"消息等以 "2"
13 P23857 开头的消息给彩铃 AS , 该消息携带彩铃会话的 SDP请求， 并途经 S-CSCF; 步骤 507、 彩铃 AS向主叫方发送彩铃会话的 SDP请求， 比如通过发送 UPDATE更新消息携带， 该消息体中携带彩铃会话的 SDP请求， 该消息途经 S-CSCF和 P-CSCF到达 UE-A,才艮据标准的要求， 上述消息中的 SDP请求可 能需要在步骤 506的 SDP请求的基 上做些调整，彩铃 AS还可将携带的 SDP 请求中的部分或全部媒体类型的方向指示修改为 send— only (只发送）， 或在 消息中添力。 P-Early-Media头域, 并可 4夺 匕头或的值设为 send— only; 步骤 508、 UE-A收到更新消息， 发送同意更新消息给被叫方， 比如发 送 "200 OK" 消息等以 "2" 开头的消息， 该消息体中携带主叫方的 SDP响 应， 该消息途经 P-CSCF和 S-CSCF到达彩铃 AS; 步骤 509、 彩铃 AS收到主叫方的 SDP响应后， 向彩铃媒体服务器发送 确认应答消息， 比如发送 ACK消息， 该消息体中携带主叫方的 SDP响应， 该消息途经 S-CSCF , 根据标准的要求， 此消息中的 SDP响应可能需要在步 骤 508的 SDP响应的基 上 ^故些调整； 步骤 510、彩铃媒体服务器接收到确认应答消息后，向主叫方播放彩铃； 步骤 511〜520、 与图 4中的步骤 416〜425基本等同， 只是根据标准的要 求， 步骤 515中的 SDP请求可能需要在步骤 514的 SDP请求的基 上做些 调整， 步骤 519中的 SDP响应可能需要在步骤 518的 SDP响应的基础上丈 些调整； 综上所述， 本发明的优化方案克服了现有技术的局限性， 使彩铃业务可 以实现任意媒体类型及其组合的播放； 另一优化方案能使最终建立的会话使 用的媒体类型不会因彩铃业务的媒体类型少而减少； 还有一优化方案可以防 止被叫方发生数据传递错误。 本发明的技术方案对被叫应答后的处理进行了 改进， 减少了应答后的交互步骤， 并且调整了开始计费的时间， 使应答到通 话开始间的过程大为简化， 改善了用户的体验， 避免了错误的扣费。 显然， 本领域的技术人员应该明白， 上述的本发明的各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计 算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来 实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或者将它们 分别制作成各个集成电路模块， 或者将它们中的多个步骤制作成单个集成电
14 P23857 路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。 当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 情况下，熟悉本领域的技术人员当可根据本发明作出各种相应的改变和变形， 但这些相应的改变和变形都应属于本发明的权利要求的保护范围。
15 P23857

Claims

权 利 要 求 书
1. 一种实现单对话彩铃业务的呼叫建立方法， 其特征在于， 包括如下步 骤：
A、 主叫方发起呼叫， 彩铃应用月 务器 AS采用单对话方式向所述 主叫方播放媒体信息；
B、 被叫方应答呼叫， 所述彩铃 AS在收到所述被叫方的应答消息 后且在转发所述应答消息前， 请求所述被叫方发送 SDP请求；
C、所述彩铃 AS接收到所述被叫方发送的 SDP请求后，将所述 SDP 请求发送给所述主叫方；
D、 所述主叫方、 所述彩铃 AS和所述被叫方按预定过程实现通话 建立。
2. 根据权利要求 1所述的方法， 其特征在于，
步骤 A中， 所述主叫方发起呼叫包括： 所述主叫方向所述彩铃 AS 发送携带有 SDP请求的呼叫请求消息；
步骤 A中， 所述彩铃 AS在接收到所述呼叫请求消息后， 将所述呼 叫请求消息转发给所述被叫方， 所述被叫方返回回应消息， 其中， 所述 回应消息中携带有 SDP响应；
3. 根据权利要求 2所述的方法， 其特征在于，
步骤 A中，所述彩铃 AS接收到所述主叫方的消息或所述被叫方的 消息后，与彩铃媒体^ ^务器交互，向所述主叫方转发彩铃会话的所述 SDP 请求或响应。
4. 根据权利要求 3所述的方法， 其特征在于， 步骤 A中：
向所述主叫方发送的彩铃会话的所述 SDP请求通过 UPDATE消息 携带。
5. 根据权利要求 3所述的方法， 其特征在于， 步骤 A中：
向所述主叫方发送的彩铃会话的 SDP信息包含所述主叫方的 SDP 请求或所述被叫方的 SDP响应中的所有媒体类型。
16 P23857
6. 根据权利要求 5所述的方法， 其特征在于， 步骤 A中： 所述彩铃 AS将向所述主叫方发送的彩铃会话的 SDP信息中的部分 或全部媒体类型的方向指示设置为只发送 sendonly。
7. 根据权利要求 5所述的方法， 其特征在于， 步骤 A中：
所述彩铃 AS在发送彩铃会话的 SDP信息的会话初始协议 SIP消息 中增力。 P— Early-Media头或， 并^1 jt匕头或的值设为 sendonly。
8. 根据权利要求 5所述的方法， 其特征在于， 步骤 A中：
所述彩铃 AS在发送彩铃会话 SDP信息后，如果接收到所述主叫方 的新的 SDP 请求， 则将所述新的 SDP 请求中的方向指示为只接收 recvonly的媒体类型的方向指示爹改为既发送也接收 sendrecv。
9. 根据权利要求 2所述的方法， 其特征在于，
步骤 A中， 所述彩铃 AS接收到主叫方携带所述 SDP请求的呼叫 请求消息后，发送给所述被叫方，并在所述 SDP信息中增加零带宽标识。
10. 才艮据权利要求 1所述的方法， 其特征在于：
步骤 C中， 所述彩铃 AS通过使用更新 UPDATE消息或应答消息 携带所述被叫方发送的 SDP请求以将其发送给所述主叫方。
11. 根据权利要求 1所述的方法， 其特征在于， 步骤 B中：
所述彩铃 AS使用不带任何 SDP信息的 re-INVITE消息来请求所述 被叫方发送 SDP请求， 所述被叫方通过 re-INVITE的 "2" 开头的回应 消息发送 SDP请求。
17 P23857
PCT/CN2008/073875 2008-05-07 2008-12-30 实现单对话彩铃业务的呼叫建立方法 WO2009135375A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200810094681.7 2008-05-07
CN2008100946817A CN101448046B (zh) 2008-05-07 2008-05-07 一种实现单对话彩铃业务的呼叫建立方法
CN200810099302.3 2008-05-09
CN2008100993023A CN101459874B (zh) 2008-05-09 2008-05-09 单对话彩像业务的实现方法

Publications (1)

Publication Number Publication Date
WO2009135375A1 true WO2009135375A1 (zh) 2009-11-12

Family

ID=41264415

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073875 WO2009135375A1 (zh) 2008-05-07 2008-12-30 实现单对话彩铃业务的呼叫建立方法

Country Status (1)

Country Link
WO (1) WO2009135375A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404295A (zh) * 2010-09-15 2012-04-04 中兴通讯股份有限公司 会话中早媒体的播放方法及系统
CN111181740A (zh) * 2018-11-09 2020-05-19 中国电信股份有限公司 消息发送方法、装置、应用服务器及计算机可读存储介质
CN113784003A (zh) * 2021-08-11 2021-12-10 咪咕音乐有限公司 彩铃呼叫方法、系统及通信设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060055277A (ko) * 2004-11-18 2006-05-23 유엔젤주식회사 통신시스템에서의 대체 영상 서비스 방법
CN1859506A (zh) * 2006-03-27 2006-11-08 华为技术有限公司 一种实现语音交互的方法
CN1889604A (zh) * 2005-06-30 2007-01-03 华为技术有限公司 一种控制回铃音的方法及系统
CN101083844A (zh) * 2007-07-18 2007-12-05 中兴通讯股份有限公司 Ims网络中实现无话路迂回多媒体彩铃业务的方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060055277A (ko) * 2004-11-18 2006-05-23 유엔젤주식회사 통신시스템에서의 대체 영상 서비스 방법
CN1889604A (zh) * 2005-06-30 2007-01-03 华为技术有限公司 一种控制回铃音的方法及系统
CN1859506A (zh) * 2006-03-27 2006-11-08 华为技术有限公司 一种实现语音交互的方法
CN101083844A (zh) * 2007-07-18 2007-12-05 中兴通讯股份有限公司 Ims网络中实现无话路迂回多媒体彩铃业务的方法和系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404295A (zh) * 2010-09-15 2012-04-04 中兴通讯股份有限公司 会话中早媒体的播放方法及系统
CN111181740A (zh) * 2018-11-09 2020-05-19 中国电信股份有限公司 消息发送方法、装置、应用服务器及计算机可读存储介质
CN113784003A (zh) * 2021-08-11 2021-12-10 咪咕音乐有限公司 彩铃呼叫方法、系统及通信设备
CN113784003B (zh) * 2021-08-11 2024-04-09 咪咕音乐有限公司 彩铃呼叫方法、系统及通信设备

Similar Documents

Publication Publication Date Title
US9392028B2 (en) Apparatus and method for macro operation involving a plurality of session protocol transactions
US8718238B2 (en) Method and a system for implementing a multimedia ring back tone service
KR101548140B1 (ko) 원격통신 네트워크에서 매체 속성들에 기초한 선택적 호 포워딩을 위한 방법 및 시스템
WO2007064788A1 (en) Method and apparatus for providing customized ringback tones to calling party devices in an ims network
WO2009049531A1 (fr) Procédé, dispositif de commande de passerelle réseau multimédia et serveur d'application pour mettre en œuvre l'intercommunication des tonalités de retour d'appel personnalisées
KR20100042270A (ko) 호 전달 서비스 제공 방법, 호 전달 서비스 제공 장치 및 호 전달 서비스 제공 시스템
WO2014044224A1 (zh) 接入协商、释放中服务质量承载资源控制的方法及系统
EP2587777B1 (en) Method and system for implementing color ring back tone and multimedia ring alert tone service.
WO2010031230A1 (zh) 一种ip多媒体链路的媒体协商方法
WO2008064580A1 (fr) Procédé, système et serveur d'application pour éviter la diaphonie de signal de rappel couleur
CN101237614B (zh) 一种实现彩铃业务的方法
WO2009086758A1 (zh) 一种在线彩铃或彩像业务的实现方法
WO2009089797A1 (fr) Procédé de mise en oeuvre de service de tonalité de retour d'appel et/ou de tonalité de reour d'appel multimédia et de production de demande sdp multimédia anticipée
WO2011032402A1 (zh) 机顶盒基于sip实现呼叫转移的方法及系统
WO2007093116A1 (fr) Procédé et système de fourniture de service de simulation et entité adaptative de signalisation d'accès
WO2007062609A1 (fr) Procede, serveur d'application et systeme pour la mise en oeuvre de service de controle de tiers
WO2009124512A1 (zh) 控制早媒体播放的实现方法
WO2009135375A1 (zh) 实现单对话彩铃业务的呼叫建立方法
WO2011153752A1 (zh) 在ctd业务中实现呼叫转接的方法、系统及应用服务器
WO2010091567A1 (zh) 一种点击拨号业务到多媒体会议业务的切换系统及方法
CN101448046B (zh) 一种实现单对话彩铃业务的呼叫建立方法
WO2010000106A1 (zh) 用于在ims网络中实现定制化视频服务的方法和网络单元
WO2011023041A1 (zh) 一种指示终端媒体类型的呼叫方法及系统
WO2014000429A1 (zh) 一种ip多媒体子系统架构下终端移动业务的实现方法及装置
CN101330640B (zh) 一种ip多媒体子系统集中业务呼叫保持业务的实现方法

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: 08874169

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08874169

Country of ref document: EP

Kind code of ref document: A1