WO2009046645A1

WO2009046645A1 - A method for realizing interaction between conversation blind transfer service and session service

Info

Publication number: WO2009046645A1
Application number: PCT/CN2008/071507
Authority: WO
Inventors: Zhenhua Xie
Original assignee: Zte Corporation
Priority date: 2007-10-12
Filing date: 2008-07-01
Publication date: 2009-04-16
Also published as: CN101141273B; CN101141273A

Abstract

A method for realizing interaction between conversation blind transfer service and session service is provided, which is applied in IP multimedia subsystem to save signaling route. In the method, the UE A of the session service cuts in blind transfer service; when the said UE A transmits the request of transferring the said conversation to the said session service to the UE B which has a session connection with the UE A, if the creator of the said session service is judged to be the said UE A, and the said requested transfer object is judged to be the session contact address of the said session service, the said requested transfer object is maintained, and the said request is transferred to the said UE B, otherwise the blind transfer service logic is performed. The method of the present invention reduces the signaling route and the redundant operation, at the same time it also reduces the unwanted blind transfer service overhead of the transferring side.

Description

Method for realizing interaction between session blind transfer service and conference service

Technical field

The present invention relates to multimedia services in the field of communications, and more particularly to session blind transfer services and conference services in an IP multimedia subsystem.

Background technique

The IP (Internet Protocol) Multimedia Subsystem (IMS) is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP). An open and flexible business environment that supports multimedia applications and provides users with rich multimedia services.

In the IMS service system, the control layer and the service layer are separated. The control layer does not provide specific services, and only provides the necessary triggering, routing, and accounting functions to the service layer. The service triggering and control functions in the control layer are controlled by the Call Session Control Function (CSCF, Call Session Control Function; divided into Proxy Proxy, Interrogating and Serving Serving). The main responsibility is the Serving CSCF, ie S- CSCF; Interrogating type is optional) completed. The business layer is composed of a series of application servers (AS, Application Server) that can provide specific business services. The AS can be an independent entity or it can exist in the S-CSCF. The control layer (S-CSCF) controls the service trigger according to the subscription information of the user, invokes the service on the AS, and implements the service function. AS and S-CSCF can be collectively referred to as service equipment (SE, Server Equipment). The end-to-end device in the session is called User Equipment (UE) and is responsible for interacting with the user. These functional entities communicate using the SIP (Session Initiation Protocol) protocol.

The session blind transfer service is a service in the IMS, which allows the user equipment to transfer the session to the transfer target device after the session is established, so that the transferred party no longer talks with the transfer party, and then transfers the target. The device talks, where the transfer party and the transferred party are both parties to the original call.

The conference service is also a service in IMS, which allows multiple people to talk at the same time, that is, one person can speak, and others can hear it. The conference service SE manages all conference services on it, and each conference service is uniquely identified by the conference contact address. If the user equipment has opened the session blind transfer service, In the case of a conference service, there are interactions between the two services because they need to use the same message. Figure 1 is a basic message flow diagram of the existing blind-switching service and conference service interaction. It is described that user equipment A (UE-A) has opened the blind-switching service, and UE-A and user equipment B (UE-B) are established. In the session, UE-A creates a conference service, and then invites UE-B to join the conference. The steps are as follows: Step 101: UE-A and UE-B have established a multimedia session, because UE-A has opened the blind transfer service. Therefore, the blindly switched service SE is on the path of the session signaling;

Step 102: UE-A creates a conference. Similarly, UE-A activates the blind transfer service, and the blind transfer service SE is also on the signaling path of the session, and the blind transfer service SE records the conference contact address and UE-A is Meeting creator;

Step 103: The UE-A requests to transfer the session of the UE-B to the conference, so that the UE-B joins the conference service, for example, the UE-A sends a handover (REFER) message to the UE-B to be transferred, and transfers the message. The information in the Refer-To header field points to the transfer destination - the conference contact address;

Step 104: The blind-transfer service SE receives the transfer message sent by the UE-A to the UE-B, and considers that the blind transfer service is performed, and then changes the transfer destination to the address of the blind-transfer service SE, and forwards the modified transfer message to the UE. -B;

Step 105, UE-B receives the modified transfer message, indicating that the transfer is agreed, for example, responding to the "202 Accepted" message, and the response message passes through the blind transfer service SE;

Step 106, the blind transfer service SE forwards the response message to the UE-A;

Step 107, the UE-B first ends the session to be transferred, for example, sends a End Session (BYE) message to the UE-A, and ends the session message through the blind transfer service SE;

Step 108, the blind transfer service SE forwards the end session message of the UE-B to the UE-A;

Step 109: The UE-B sends a call request to the transfer destination, that is, the blind transfer service SE according to the transfer message, for example, sending an invitation (INVITE) message;

Step 110: The blind transfer service SE receives the call request sent by the UE-B, and modifies the call target to the conference contact address, and then forwards the call request of the UE-B according to the address;

Step 111: Because the conference contact address is on the conference service SE, the conference service SE receives the call request forwarded by the blind transfer service SE, associates it with the specified conference service, and sends a response response message to the blind transfer service SE to respond. Call, such as responding to a "200 OK"message; Step 112: The response response message passes through the blind transfer service SE, and the blind transfer service SE forwards the response response to the UE-B to indicate the answering call;

Step 113: From then on, UE-B ends the original session and establishes a session with the conference service SE, thereby joining the conference service created by UE-A.

The flow in FIG. 1 is abstracted to form a four-part flow chart shown in FIG. 2, and the steps are as follows: Step 201: UE-A sends a transfer message to UE-B, requesting UE-B to transfer its session to the conference contact address. , the transfer message passes through the blind transfer service SE;

Step 202: After the blind transfer service SE modifies the transfer destination to itself, the UE forwards the transfer message sent by the UE-A to the UE-B.

Step 203: The UE-B receives the transfer message forwarded by the blind transfer service SE, and sends a call request to the call transfer target, the blind transfer service SE.

Step 204: The blind transfer service SE receives the call request sent by the UE-B, and then modifies the transfer destination to the conference contact address, and then forwards the call request to the real transfer destination according to the address (stored on the conference service SE).

According to the basic message flow chart shown in Fig. 1 and the summary flow chart shown in Fig. 2, it is possible to clearly see the technical defects. Based on the existing implementation scheme, the blind transfer service SE treats the transfer message belonging to the conference service as a request for the blind transfer service, so that the subsequent UE-B call request unnecessarily passes through the blind transfer service SE, and the signaling is added. The path and unnecessary transfer target modification operations also increase the unnecessary blind transfer service overhead of UE-A.

Summary of the invention

The technical problem to be solved by the present invention is to provide a method for realizing the interaction between the session blind transfer service and the conference service, thereby saving the signaling path.

In order to solve the above technical problem, the present invention provides a method for implementing a session blind transfer service and a conference service interaction, which is applied to an IP multimedia subsystem, and the user equipment A in the conference service activates a blind transfer service, when the user equipment A Determining that the creator of the conference service is the user equipment A, and the requesting transfer destination is the conference service, when sending a request to the user equipment B that has a session connection to transfer the session to the conference service Meeting contact address, keep the request The requested transfer destination is unchanged, and the request is forwarded to the user equipment B, otherwise the blind transfer service logic is executed.

According to the above method, the conference contact address may be recorded by the blind transfer service device. Further, the creator of the conference service may be marked by the blind transfer service service device. Further, the user equipment A may access the blind connection service device, establish the session connection with the user equipment B, and send the request to the user equipment B.

Further, the request may include a transfer message.

Still further, the requested transfer destination may be indicated by information in a Refer-To header field of the transfer message.

In addition, the blind transfer service device may determine whether the creator of the conference service is the user equipment A, and if yes, further determine whether the requested transfer destination is a conference contact address of the conference service, and if yes, maintain The requested transfer destination is unchanged, and the request is forwarded to the user equipment B, otherwise the blind transfer service logic is executed.

Further, if the blind transfer service device determines that the creator of the conference service is not the user device A, the blind transfer service logic may be executed.

And, the blind transfer service service device keeps the transfer target unchanged, and after forwarding the request to the user device B, the method may further include the following steps:

The user equipment B sends a response message to the user equipment A to indicate that the transfer is agreed to;

The user equipment B passes the blind transfer service device, and sends a end session message to the user equipment A to end the session;

The user equipment B sends a call request to the conference service service device according to the transfer destination to join the conference;

Receiving, by the conference service service device, the call request, associating the call request with the conference service, and answering the call request;

The user equipment B establishes a session with the conference service service device to join the conference service. Further, the conference contact address may be saved on the conference service service device. According to the method provided by the present invention, since the blind transfer service device directly forwards the request to the transferred party by confirming that the transfer destination is the conference contact address provided by the conference creator that sends the request, the call request of the subsequent transferred party is made. It does not need to go through the blindly switched service service equipment, which not only reduces the signaling path and redundant operations, but also reduces the unnecessary blind transfer service overhead of the transfer party.

BRIEF abstract

FIG. 1 is a basic message flow chart of an existing blind transfer service and a conference service interaction;

Figure 2 is a schematic flow chart for abstracting Figure 1;

3 is a basic message flow chart of the blind transfer service and the conference service interaction according to the present invention;

Fig. 4 is a schematic flow chart for abstracting Fig. 3.

Preferred embodiment of the invention

The method for realizing the interaction between the session blind transfer service and the conference service provided by the present invention is as follows: User equipment A (UE-A) in the conference service is opened for the blind transfer service, and the blind transfer service SE records the conference for the conference service. Contact address, and mark the creator of the conference service (either UE-A, or other user equipment); when UE-A requests other user equipment B (UE-B) to transfer the session with its session connection, The blind-transfer service SE determines whether the UE-A is the conference service creator. If yes, it further determines whether the transfer destination is the conference contact address created by the UE-A, and the address of the transfer destination remains unchanged, and directly forwards to the UE-B. Request; otherwise perform blind turn business logic.

The technical solution of the present invention will be described in more detail below with reference to the accompanying drawings and embodiments.

FIG. 3 is a basic message flow diagram of the present invention for implementing the interaction between the blind transfer service and the conference service, and the UE-A establishes a blind transfer service, and establishes a session with the UE-B, and then the UE-A creates the conference service. The process of inviting UE-B to join the conference service is as follows:

Steps 301 to 303 are the same as steps 101 to 103 of the basic message flow shown in FIG. 1. Step 304: The blind-transfer service SE receives the transfer message sent by the UE-A to the UE-B, and first determines the UE-A that sends the transfer message. Whether it is the conference service creator, if not, it is performed according to the blind transfer service; if yes, it is further determined whether the transfer destination is the conference contact address determined by the UE-A, and if not, the blind transfer service is not performed and the address of the transfer destination remains unchanged. If not, perform a blind transfer business; Step 305: The blind-transfer service SE forwards the transfer message sent by the UE-A to the UE-B.

Step 306, which is the same as step 105 of the basic message flow shown in FIG. 1;

Step 307, which is the same as step 106 of the basic message flow shown in FIG. 1;

Step 308, which is the same as step 107 of the basic message flow shown in FIG. 1;

Step 309, which is the same as step 108 of the basic message flow shown in FIG. 1;

Step 310: UE-B according to the transfer destination of the transfer message - the conference contact address,

The SE initiates a call request to join the conference service;

Step 311: Because the conference contact address is on the conference service SE, the conference service SE receives the call request sent by the UE-B, associates the call request with the designated conference service, and answers the call request, for example, responding to "200 OK" Message

Step 312: From then on, UE-B ends the original session and establishes a session with the conference service SE, thereby joining the conference service created by UE-A.

Figure 4 is a schematic flow chart for the abstraction of the flow in Figure 3, the steps are as follows:

Step 401: UE-A requests UE-B to transfer its session to the conference contact address, and the request passes through the blind transfer service SE;

Step 402: The blind transfer service SE determines that the request is proposed by the conference service creator, and the transfer destination of the request is a conference contact address created by the conference service creator, and the blind transfer service logic is not executed, and the request is directly forwarded to the request. UE-B;

Step 403: The UE-B receives the request, and sends a call request to the call transfer destination, the conference contact address (stored on the conference service SE).

The advantages of the present invention over the prior art can be clearly seen from the basic message flow diagram of the method of the present invention shown in Figure 3 and the summary flow chart shown in Figure 4. The invention judges the transfer message of the user through the blind transfer service SE, and directly determines whether it is performing the conference service or the blind transfer service, thereby effectively implementing the interaction of the two services, reducing the unnecessary signaling path and Excess business operations, thus providing users with better services.

It is a matter of course that the invention can be embodied in various other forms and modifications without departing from the spirit and scope of the invention.

Claims

Claim

A method for implementing a session blind transfer service and a conference service interaction, which is applied to an IP multimedia subsystem, wherein the user equipment A in the conference service is opened with a blind transfer service, and when the user equipment A has a session with the session When the connected user equipment B sends a request to transfer the session to the conference service, it is determined that the creator of the conference service is the user equipment A, and the requested transfer destination is the conference contact address of the conference service. Then, the transfer destination of the request is kept unchanged, and the request is forwarded to the user equipment B, otherwise the blind transfer service logic is executed.

2. The method of claim 1 wherein said conference contact address is recorded by a blind transfer service device.

3. The method according to claim 2, wherein the creator of the conference service is marked by the blind transfer service service device.

The method according to claim 3, wherein the user equipment A accesses the blind transfer service device, establishes the session connection with the user equipment B, and sends the session to the user equipment B. request.

5. The method of claim 4 wherein the request comprises a transfer message.

6. The method of claim 5 wherein the requested transfer destination is indicated by information in a Refer-To header field of the transfer message.

The method according to claim 3, wherein the blind transfer service server determines whether the creator of the conference service is the user equipment A, and if yes, further determines whether the requested transfer destination is The conference contact address of the conference service, if yes, the destination of the request is kept unchanged, and the request is forwarded to the user equipment B, otherwise the blind turn service logic is executed.

The method according to claim 7, wherein the blind transfer service service device determines that the creator of the conference service is not the user equipment A, and performs blind turn service logic.

The method according to claim 3, wherein the blind transfer service service device keeps the transfer target unchanged, and after forwarding the request to the user device B, the method further includes the following steps: The user equipment B sends a response message to the user equipment A to indicate that the transfer is agreed to;

The user equipment B establishes a session with the conference service service device to join the conference service.

10. The method according to claim 9, wherein the conference contact address is saved on the conference service service device.