WO2008077308A1

WO2008077308A1 - Processing method and entity of public identity shared by multi-terminals

Info

Publication number: WO2008077308A1
Application number: PCT/CN2007/003618
Authority: WO
Inventors: Dongming Zhu; Hengliang Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-12-22
Filing date: 2007-12-14
Publication date: 2008-07-03
Also published as: CN101207548A

Abstract

A processing method and entity of public identity shared by multi-terminals are disclosed, to resolve the succession session failed problem that may be resulted by non-adopting the particular operation when the CSI-Interworking(CSI-IW) receives the public identify shared by multi-terminals indicated by the session message from the calling side. The method includes the following steps: when the CSI-IW receives the public identify shared by multi-terminals indicated by the session message from the calling side, selecting the operation manner of the session message; in the processing of routing the session message, notifying the selected information to the following net element; the following net element processing the session message according to the notified information. The entity includes: a judging unit, a selecting unit and a notifying unit. Thus, when the CSI-IW receives the public identify shared by multi-terminals indicated by the session message from the calling side, adopting the particular operation can improve the success ratio of succession session.

Description

Method and entity for processing shared identifiers of multiple terminals

The present invention relates to the field of communications, and in particular, to a method and an entity for processing a shared identifier of a multi-terminal. Background technique

IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) is an IP Multimedia Subsystem in the WCDMA (Wide-Band Code Division Multiple Access) network defined by the 3GPP R5/R6 standard, which is implemented by 3G mobile network. Packet voice and packet data, providing a unified network of multimedia services and applications. The IMS uses the IP packet domain as the bearer channel for its control signaling and media transmission, and uses the SIP (Session Initiation Protocol) protocol as the call control signaling. In IMS, the IMS user subscription data is centrally managed in the HSS, and the service is uniformly provided by the application server AS. The session control is completed by the S-CSCF (Service Call Session Control Function), and the two are completely separated in the network structure, and the service passes through S. -CSCF triggers to AS processing, and multiple ASs can work together. The user accesses the IMS through the current local proxy node P-CSCF (Proxy Call Session Control Function), and the session and service control are completed by the home domain service node of the registered place, so the user can always get the same service at different access points. It realizes the separation of service management, session control and bearer access, and service provision independent of access and location.

CSI (Combined CS Bearers with IMS) is a research topic in the current 3GPP standard. This topic is concerned with the following related technologies for how to implement the interworking between the CSI terminal and the IMS terminal in the 3G CS domain service and the IMS domain service. The CSI interworking function entity CSI-IW (CSI-Interworking) is set on the CSI terminal side. After receiving the session request from the IMS terminal, the function entity splits the session message with multiple media components according to the related information, and the session is split. Split into sessions with real-time media components and sessions with non-real-time media components. Then judge according to the relevant information, choose to terminate the real-time session in the CS domain, and terminate the non-reality in the IMS domain. Time session.

The interworking process between the CSI terminal and the IMS terminal, as shown in Figure 1, includes the following steps:

1. The VoIP (voice over IP) terminal initiates an IMS session request to the CSI terminal, and the request includes real-time services and non-real-time services.

2. The IMS on the VoIP side forwards the request to the CSI-IW on the CSI terminal side.

3. The CSI-IW performs business logic processing according to the related information, and separates the session request.

4. The CSI-IW sends a session request to the CSI terminal. The request message includes non-real-time services and indication information that the CSI terminal is required to initiate the terminal-to-network CS bearer.

5. After receiving the session request message, the CSI terminal initiates a CS call to the CSI-IW.

6. The MGCF (Media Gateway Control Function) receives the CS call request from the CSI terminal and maps it to the INVITE and sends it to the CSI-IW.

7. The CSI-IW sends a 200 OK response message to the MGCF.

8. The MGCF maps the 200 OK response message to the CS connect message to the CSI terminal.

9. The CSI terminal sends a 200 OK response message. The response message contains only the media information of the MSRP (Message Session Relay Protocol).

10. The CSI-IW combines the CS call from the CSI terminal with the IMS session.

11. The CSI-IW sends the merged 200 OK response message to the called IMS.

12. The called IMS forwards the 200 OK message to the VoIP terminal.

During the process of the invention, the inventor has found that the CSI-IW does not know that the IP multimedia public identity (IMPU) of the called user is shared by multiple terminals. What action should CSI-IW take?

If the CSI-IW does not take special actions and the Forking mechanism is triggered by the S-CSCF, since different terminals may have different capabilities, the S-CSCF will not be based on the terminal after the session request has not been processed. The CSI capability performs the transfer of the IMS voice session to the CS domain, and does not perform the splitting of the multimedia session and the merge processing of the response. Therefore, there are many failures that can occur when the S-CSCF is processed. Summary of the invention

An embodiment of the present invention provides a method and an entity for processing a shared identifier of a multi-terminal, which is used to solve the problem that when a CSI interworking function entity receives a public message from a calling party to a public identity shared by multiple terminals, Taking special actions may cause problems with session connection failure.

The method of the embodiment of the present invention includes the following steps: A. When a CSI interworking function entity receives a session message from a calling party and points to a public identity shared by multiple terminals, selects an operation mode of the session message; In the process of describing the session message, the selected information is notified to the subsequent network element; C. The subsequent network element processes the session message according to the notified information.

The CSI interworking function entity of the embodiment of the present invention includes: a determining unit, configured to determine whether a session message received from a calling side points to a public identifier shared by multiple terminals; and a selecting unit, configured to output a judgment result in the determining unit If yes, the operation mode of the session message is selected; the notification unit is configured to notify the subsequent network element of the information selected by the selection unit in the process of routing the session message.

When the CSI interworking function entity in the embodiment of the present invention receives the session information from the calling side and points to the public identity shared by the multiple terminals, selects the operation mode of the session message, and in the process of routing the session message, The selected information is sent to the subsequent network element; the subsequent network element processes the session message according to the notified information, thereby avoiding the blind operation of the subsequent network element and improving the success rate of the session connection. DRAWINGS

FIG. 1 is a flow chart of interworking between an existing CSI terminal and an IMS terminal;

2 is a flow chart of steps of a method according to an embodiment of the present invention;

3 is a signaling flowchart of Embodiment 1 of a method according to the present invention;

4 is a signaling flowchart of Embodiment 2 of a method according to the present invention;

FIG. 5 is a flowchart of a signaling method according to Embodiment 3 of the present invention;

6 is a signaling flowchart of Embodiment 4 of a method according to the present invention;

Figure Ί is a schematic structural diagram of a CSI interworking function entity according to an embodiment of the present invention; 8 is a schematic structural diagram of Embodiment 1 of a CSI interworking function entity according to the present invention;

9 is a schematic structural diagram of Embodiment 2 of a CSI interworking function entity according to the present invention;

FIG. 10 is a schematic structural diagram of Embodiment 3 of a CSI interworking function entity according to the present invention. detailed description

In order to improve the success rate of the session connection, the embodiment of the present invention provides a method for processing a public identifier of a multi-terminal, which is shown in FIG. 2 and includes the following main steps:

51. The CSI interworking function entity receives a session message from the calling side, and perceives that the session message points to a public identity shared by multiple terminals.

52. The CSI interworking function entity selects an operation mode of the session message.

The method for selecting the operation of the session message includes: the CSI interworking function entity indicates whether the subsequent network element performs the fork processing Forking; and indicates that the Forking is based on one of the following two methods: mode 1: the CSI interworking function entity is locally The policy indicates whether the subsequent network element performs Forkmg. In the second mode, the CSI interworking function entity senses the Forking processing mode of the subsequent network element. If the subsequent network element uses the serial Forking mode, the subsequent network element is selected to indicate that the subsequent network element does not perform Forking; if the subsequent network element uses the parallel Forking mode, the indication is followed by the subsequent network. Yuan carries out Forking.

Under the above two methods, there are three cases:

In the first case, if the CSI interworking function entity indicates that the subsequent network element does not perform the Forking, the operation mode of the selection of the session message further includes: the CSI interworking function entity selects the destination terminal, and selects whether the session is selected for the selected destination terminal. After the split operation is performed, the subsequent network element is instructed to send to the destination terminal.

The CSI interworking function entity selects the destination terminal according to at least one of the following information: media component information and terminal capability information in the session message (including but not limited to whether the terminal supports CSI service capability, whether the terminal supports VoIP capability), The preference information, the access network information of the terminal (including but not limited to the DTM/MuktiRAB capability of the access network where the terminal is located), and the priority information of the terminal.

If the selected destination terminal has multiple access modes, the CSI interworking function entity further determines whether splitting is required, and selects the terminal access domain. If there are multiple media in the session message The selected destination terminal has multiple access modes, and the specific access mode of the selected destination terminal can only carry part of the media in the session message, and the CSI interworking function entity selects to split the session message; otherwise Choose not to split the session message.

In the second case, if the CSI interworking function entity indicates that the subsequent network element performs the forking, the operation mode of the selecting the session message further includes: the CSI interworking function entity copies the session message and the category to which the multiple terminals belong. Correspondingly, and determining whether to split the session message corresponding to the category terminal; and according to the characteristics of each category of the terminal, instructing the subsequent network element to send to each category terminal.

Wherein, if there are multiple media components in the session message, the terminal of the class has multiple access modes, and the specific access mode of the class terminal can only carry part of the media in the session message, then the CSI interworking function entity The session message corresponding to the category terminal is split; otherwise, the session message corresponding to the category terminal is not split.

In the third case, if the CSI interworking function entity indicates that the subsequent network element does not perform the forking, the operation mode of the selecting the session message further includes: the CSI interworking function entity copies the session message and corresponds to the multiple terminals. And determining whether to split the session message corresponding to the terminal; and according to the characteristics of each terminal, indicating that the subsequent network element is correspondingly sent to each terminal.

Wherein, if there are multiple media components in the session message, the terminal has multiple access modes, and the specific access mode of the terminal can only carry part of the media in the session message, the CSI interworking function entity will correspond to The session message of the terminal is split; otherwise, the session message corresponding to the terminal is not split.

S3. In the process of routing the session message, notify the subsequent network element of the selected information.

In the process of routing the session message, the CSI interworking function entity notifies the information of the subsequent network element at least: whether to perform the instruction of the Forking. Further, the information about the subsequent network element may further include: calling preference information, or a globally routable user agent identifier (GRUU information) of the destination terminal.

S4. The subsequent network element processes the session message according to the notified information.

The subsequent network element determines whether to perform the Forking process on the session message according to the notified information, and further directly routes the session message to the corresponding terminal according to the calling preference information or the GRUU information. Corresponding to the first situation in the step S2, the subsequent network element routes the session message to the destination terminal according to the notified information, and if the destination terminal returns a failure response message, the CSI interworking function entity is within the range of the multiple terminals. The destination terminal is reselected from other terminals than the destination terminal, and steps S3 and S4 are continued.

Corresponding to the third case in the step S2, after the network element correspondingly routes the session message to each terminal according to the notified information, if the CSI interworking function entity receives the response message of at least two terminals, the CSI interworking function entity selects the A successfully responding terminal is connected to the calling side and tears down the session with the terminal that successfully transmits the subsequent response.

The method of the embodiment of the present invention is specifically described below through four method embodiments.

Method Embodiment 1: The CSI IW does not require the S-CSCF to perform forkging processing, and selects the VoIP terminal termination session and the reselection after the VoIP failure. See Figure 3, including the following steps:

1. The calling party initiates a multimedia session containing real-time media components and non-real-time media components.

Note: Here the caller can initiate media changes to the original session.

2. After receiving the information, the S-CSCF on the called side forwards the request to the CSI IW to the session request.

3. The CSI IW judges according to the local policy, determines that the S-CSCF is not required for the forking process, and selects the IMS VoIP terminal to terminate the session according to the terminal capability, the media type information included in the session request, and the priority information of the terminal.

4. The CSI IW initiates a multimedia session to the IMS VoIP terminal.

In order to ensure that the session can be correctly routed to the designated IMS VoIP terminal, the CSI IW can add some information to the session request for the S-CSCF to perform subsequent routing. The information includes caller preference information indicating that the S-CSCF selects the IMS terminal for processing.

In the above steps, the S-CSCF may carry an indication message in the message that does not require the S-CSCF to perform the forking process.

The S-CSCF can also directly use the GRUU information of the IMS terminal as the Request URI of the session request to achieve the above purpose. At this time, the S-CSCF does not need to carry the instruction information in the message that does not require the S-CSCF to perform the forking process.

5a. The IMS VoIP terminal sends a 200 OK response message of the session. 6a. The CSI IW sends a 200 OK response message to the S-CSCF.

7a. The S-CSCF forwards the 200 OK response message to the calling side. At this time, the IMS VoIP terminal establishes real-time media and non-real-time media bearers with the calling side.

5b. The VoIP terminal sends a failure response message.

6b. The CSI IW deletes the VoIP from the list of candidate terminals and continues the terminal selection. This time select UE2.

7b. The CSI IW sends a session request to UE2.

Method Embodiment 2: CSI IW Selection The CSI terminal terminates the multimedia session and performs session splitting according to the media type. See Figure 4, including the following steps:

Note: Here the caller can initiate media changes to the original session.

3. The CSI IW according to the information configured by the S-CSCF, for example, the S-CSCF uses the configuration information of the serial forking to determine, does not trigger the forkgmg mechanism of the S-CSCF, and according to the terminal capability, the media type information included in the session request, The priority information of the terminal, and one of the access network capability information in which the terminal is located or any combination of the information selects the CSI terminal.

4. The CSI IW initiates a non-real-time media session to the CSI terminal, and the session carries a non forking indication.

In order to ensure that the session can be correctly routed to the IMS part of the specified CSI terminal, the CSI IW can add some information to the session request for the S-CSCF to perform subsequent routing. The information includes caller preference information indicating that the S-CSCF selects the IMS portion of the CSI terminal for processing.

The S-CSCF can also directly use the GRUU information of the IMS terminal as the request for the session request.

URL

5. The IMS part of the CSI terminal sends a 200 OK response message for the non-real-time session.

6. The CSI IW initiates a real-time media session to the CS domain of the CSI terminal. The non forking instruction is carried in the session.

The CSI IW fills in the TelURI information of the CSI terminal in the Request UI of the session. The session request Route to the MGCF.

7. The MGCF sends a CS call request to the CS domain of the CSI terminal.

8. The CS domain of the CSI terminal sends a CS call response.

9. The MGCF sends a 200 OK response message for the real-time session request.

10 SI IW sends a 200 OK response message containing real-time media and non-real-time media to the S-CSCF. 11. The S-CSCF sends a 200 OK response message to the calling side.

A real-time media bearer is established between the calling side and the CS domain of the CSI terminal, and a non-real-time media bearer is established with the IMS terminal.

Method Embodiment 3: CSI IW requires the S-CSCF to perform forking processing, and judges that session splitting is required. See Figure 5, which includes the following steps:

Note: If the CSI IW receives media changes to the original session initiated by the calling party, the CSI IW can process the new media components in the same way.

3. The CSI IW judges according to the local policy and decides that the S-CSCF needs to be used for Forking. At this time, the CSI IW determines the capability information of the terminal, such as the presence of the IMS VoIP terminal and the CSI terminal, determines the different session requests to the S-CSCF, and carries the corresponding calling preference information in the session request.

For example, at this point the CSI IW decides to initiate a multimedia session request to IMS VoIP (step 4) and initiates a split session request to the CSI terminal (steps 9 and 15).

4. The CSI IW initiates a multimedia session request to the S-CSCF, the request including caller preference information, the caller preference information excluding the use of the CSI terminal to terminate the session request.

Note: This step 4 and the following steps 9, step 15 are not strictly defined, that is, step 4 and step 9, step 15 and subsequent steps triggered thereby can occur in any order.

5. The S-CSCF performs terminal selection processing according to the calling preference information.

Here, if there are multiple terminals satisfying the calling preference condition, the S-CSCF can use the Forking mechanism to initiate a session request to each terminal. The S-CSCF's Forking can be serial forking or parallel forking.

6. The S-CSCF sends a multimedia session request to the IMS terminal.

If there is forking in step 5, then in this step, the S-CSCF may initiate a session request (parallel forking) to multiple terminals. Or, after receiving the failure response of the IMS terminal, the S-CSCF initiates a session request (parallel forking) to another terminal.

7. The IMS terminal sends a 200 OK response message of the multimedia session.

8. The S-CSCF sends a 200 OK response message to the CSI IW.

9. The CSI IW initiates a real-time session request to the S-CSCF, and the request URI information of the request fills in the tel URI information of the CS domain of the CSI terminal.

10. The S-CSCF routes the request to the MGCF.

11. The MGCF sends a CS call request to the CS domain of the CSI terminal.

12. The CSI terminal sends a CS call response message to the MGCF.

13. The MGCF sends a 200 OK response message to the S-CSCF.

14. The S-CSCF sends a real-time session response message to the CSI IW.

15. The CSI terminal sends a request message for the non-real-time session to the S-CSCF, where the session request carries the caller preference information, instructing the S-CSCF to route the request to the IMS part of the CSI terminal.

16. The S-CSCF sends the request to the IMS portion of the CSI terminal.

17. The IMS part of the CSI terminal sends a 200 OK response message.

18. The S-CSCF forwards the 200 OK response message to the CSI IW.

19. The CSI IW sends a 200 OK response message to the calling side.

20. After receiving the 200 OK response message, the S-CSCF forwards the message to the calling side.

Method Embodiment 4: The CSI IW does not require the S-CSCF to perform the forking process, and the session request is copied according to the terminal data, and is sent to the subsequent network element for routing. Referring to FIG. 6, the following steps are included: 1. The calling party initiates a multimedia session including real-time media components and non-real-time media components.

Note: Here the caller can initiate media changes to the original session.

2. After receiving the message, the called S-CSCF forwards the session request to the CSI IW.

3. The CSI IW decides to copy the session request message according to the number of terminals. 4. The CSI IW initiates a session to the IMS UE1 terminal, and the session carries a non forking indication.

5. The CSI IW initiates a session to the IMS UE3 terminal, and the session carries a non forking indication.

6. The CSI IW initiates a session to the IMS UE2 terminal, and the session carries a non forking indication.

In steps 4, 5, 6, in order to ensure that the session can be correctly routed to the designated terminal, the CSI IW can add some information to the session request for the S-CSCF to perform subsequent routing. The information includes caller preference information indicating that the S-CSCF selects a terminal for processing.

The S-CSCF can also directly use the terminal's GRUU information as the Request URL for the session request. Note: Steps 4, 5, and 6 do not have a strict order relationship. That is, steps 4, 5, and 6 can occur in any order.

7. The IMS UE1 terminal sends a 200 OK response message.

8. The IMS UE3 terminal sends a 200 OK response message.

9. The IMS UE2 terminal sends a 200 OK response message.

10. The CSI IW initiates a 200 OK response message to the calling side, and the message carries the media information of the IMS UE1.

11. The IMS UE1 establishes media with the calling side.

12. The CSI IW initiates a Bye message to the IMS UE2.

13. The CSI IW initiates a Bye message to the IMS UE3.

14. IMS UE2 sends a 200 response message of Bye.

15. The IMS UE3 sends a 200 response message of Bye.

A real-time media bearer is established between the calling party and the CS domain of the CSI terminal, and a non-real-time media bearer is established with the IMS terminal.

Corresponding to the foregoing method, an embodiment of the present invention further provides a CSI interworking function entity, which is shown in FIG. 7, and includes a judging unit, a selecting unit, and a notification unit that are sequentially connected.

Further, as shown in FIG. 8, in the first embodiment of the CSI interworking function entity of the present invention, the selecting unit includes a first selecting subunit, and further includes a second selecting subunit connected to the first selecting subunit, and Second, the third selection subunit and the exclusion unit connected to the subunit are selected.

Further, as shown in FIG. 9, in the second embodiment of the CSI interworking function entity of the present invention, the selection The first selection subunit is included in the selection unit, and further includes a fourth selection subunit connected to the first selection subunit.

The third embodiment of the present invention includes: unit.

The determining unit is configured to determine whether the session message received from the calling side points to a public identifier shared by multiple terminals;

The selecting unit is configured to select an operation mode of the session message when the determination result output by the determining unit is affirmative.

The first selection sub-unit is configured to indicate whether the subsequent network element performs the Forking according to the local policy selection, or the Forking processing mode of the subsequent network element, and if the subsequent network element uses the serial Forking mode, select the indication subsequent network. The element does not perform Forking; if the subsequent network element uses the parallel Forking method, it selects to instruct the subsequent network element to perform Forking.

The second selecting subunit is configured to further select the destination terminal when the first selecting subunit selection indicates that the subsequent network element does not perform Forking.

The third selection subunit is configured to select, for the destination terminal selected by the second selection subunit, whether to split the session message, and perform a split operation.

The exclusion unit is configured to: after obtaining the failure response message from the destination terminal, exclude the target terminal from the multiple terminals sharing the same public identity, and trigger the second selection sub-unit to re-select the destination terminal.

The fourth selecting subunit is configured to: when the first selecting subunit selection indicates that the subsequent network element performs Forking, copy the session message and correspond to a category to which the multiple terminals belong, and select whether Split the session message for the category terminal and perform the split operation. And informing the unit according to the feature indication of each category of terminals, to further instruct the subsequent unit to send the corresponding network element to each category terminal.

The fifth selection subunit is configured to: when the first selection subunit selection indicates that the subsequent network element does not perform Forking, copy the session message and correspond to the multiple terminals, and select whether Split the session message corresponding to the terminal and perform the split operation. And instructing, according to the feature indication of each terminal, to further indicate, by the notification unit, that the subsequent network element is correspondingly sent to each terminal.

The informing unit is configured to notify the subsequent network element of the information selected by the selecting unit in the process of routing the session message.

The executing unit is configured to: when receiving the response message of the at least two terminals, select the terminal that is the first successful response to be connected to the calling side, and tear down the session between the terminal that successfully responds with the subsequent transmission.

In summary, when the CSI interworking function entity in the embodiment of the present invention receives the session message from the calling side and points to the public identity shared by multiple terminals, selects the operation mode of the session message, and routes the session. In the process of the message, the selected information is notified to the subsequent network element; the subsequent network element processes the session message according to the notified information, thereby avoiding the blind operation of the subsequent network element and improving the success rate of the session connection.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A method for processing a public identifier of a multi-terminal, comprising the following steps: when a CSI interworking function entity receives a session message from a calling party and points to a public identifier shared by multiple terminals, selecting a session message Mode of operation;

During the routing of the session message, the CSI interworking function entity informs the subsequent network element to process the session message with the selected information.

The method of claim 1, wherein the CSI interworking function entity selects an operation mode of the session message, and the method includes: the CSI interworking function entity indicates whether the subsequent network element performs the fork processing.

The method according to claim 2, wherein the CSI interworking function entity indicates whether the subsequent network element performs Forking according to the local policy; or

The CSI interworking function entity senses the Forking processing mode of the subsequent network element. If the subsequent network element uses the serial Forking mode, the selection indicates that the subsequent network element does not perform Forking; if the subsequent network element uses the parallel Forking mode, the selection indicates that the subsequent network element performs the Forking .

The method of claim 3, wherein, if the CSI interworking function entity indicates that the subsequent network element does not perform the forking, the operation mode of the session message is further selected by: the CSI interworking function entity selects the destination terminal, and Determining whether to split the session message for the selected destination terminal; after performing the split operation, instructing the subsequent network element to send to the destination terminal.

The method according to claim 4, wherein the CSI interworking function entity selects the destination terminal according to at least one of the following information:

The media component information, the terminal capability information, the calling preference information, the access network information of the terminal, and the priority information of the terminal in the session message.

The method according to claim 5, wherein if the selected destination terminal has multiple access modes, the CSI interworking function entity further determines whether splitting and selecting the terminal access domain is required.

7. The method according to claim 6, wherein if there are multiple media components in the session message, the selected destination terminal has multiple access modes, and the specific access of the selected destination terminal The mode can only carry part of the media in the session message, and the CSI interworking function entity chooses to split the session message; otherwise, the session message is not split.

The method according to any one of claims 4 to 7, wherein the subsequent network element routes the session message to the destination terminal according to the notified information, and if the destination terminal returns a failure response message, the CSI The interworking function entity reselects the destination terminal from other terminals than the destination terminal within the range of the plurality of terminals.

The method according to claim 3, wherein, if the CSI interworking function entity indicates that the subsequent network element performs the forking, the operation mode of the selecting the session message further includes: the CSI interworking function entity is configured to: Copying and correspondingly corresponding to the categories to which the plurality of terminals belong, and determining whether to split the session message corresponding to the category terminal; and according to the characteristics of the terminals of each category, indicating that the subsequent network element is correspondingly transmitted to each category of the terminal.

The method according to claim 9, wherein if there are multiple media components in the session message, the terminal of the class has multiple access modes, and the specific access mode of the class terminal can only The part of the media in the session message is carried, and the CSI interworking function entity splits the session message corresponding to the category terminal; otherwise, the session message corresponding to the category terminal is not split.

The method according to claim 3, wherein, if the CSI interworking function entity indicates that the subsequent network element does not perform the forking, the operation mode of the selecting the session message further includes: the CSI interworking function entity is the session The message is copied and corresponding to the plurality of terminals, and the session message corresponding to the terminal is split. According to the characteristics of each terminal, the subsequent network element is instructed to be sent to each terminal.

The method according to claim 11, wherein if there are multiple media components in the session message, the terminal has multiple access modes, and the specific access mode of the terminal can only carry session messages. In some media, the CSI interworking function entity splits the session message corresponding to the terminal; otherwise, the session message corresponding to the terminal is not split.

The method according to claim 11 or 12, wherein, if the CSI interworking function entity receives the response message of the at least two terminals, the CSI interworking function entity selects the first successfully responding terminal and the calling side interface Pass, and tear down the session with the terminal that successfully sent the subsequent response.

The method according to any one of claims 1 to 7, wherein the CSI interworking function entity informs the information of the subsequent network element at least: whether the indication of the Forking is performed.

The method according to claim 14, wherein the CSI interworking function entity notifies the information of the subsequent network element further includes: calling preference information, or global routable user agent identifier GRUU information of the destination terminal.

16. A CSI interworking functional entity, comprising:

a determining unit, configured to determine whether the received session message from the calling side points to a public identifier shared by multiple terminals;

a selecting unit, configured to select an operation mode of the session message when the judgment result output by the determining unit is affirmative;

The informing unit is configured to notify the subsequent network element of the information selected by the selecting unit during the routing of the session message.

The entity of claim 16, wherein the selecting unit includes: a first selecting subunit, configured to: indicate, according to a local policy, whether a subsequent network element performs a Forking; or, a Forking that senses a subsequent network element If the subsequent NEs use the serial Forking mode, the subsequent NEs are not selected for Forking. If the subsequent NEs use the parallel Forking mode, the subsequent NEs are selected to perform Forking.

The entity according to claim 17, wherein, if the first selection sub-unit selection indicates that the subsequent network element does not perform Forking, the selecting unit further includes:

a second selection subunit, configured to select a destination terminal;

And a third selection subunit, configured to select, for the destination terminal selected by the second selection subunit, whether to split the session message, and perform a split operation.

The entity of claim 18, wherein the entity further comprises:

The excluding unit is configured to: after receiving the failure response message, the destination terminal excludes the destination terminal from the multiple terminals sharing the same public identity, and triggers the second selection subunit to reselect the destination terminal.

20. The entity of claim 17, wherein if the first selection subunit is selected Instructing the subsequent network element to perform the Forking, the selecting unit further includes:

And a fourth selecting subunit, configured to copy the session message and correspond one-to-one with the categories to which the plurality of terminals belong, and select whether to split the session message corresponding to the category terminal, and perform a split operation.

And a fifth selection subunit, configured to copy the session message and correspond to the plurality of terminals, and select whether to split the session message corresponding to the terminal, and perform a split operation.

The entity of claim 21, further comprising: an execution unit, configured to: when receiving the response message of the at least two terminals, select the first successfully responding terminal to be connected to the calling side, And tear down the session with the terminal that successfully sent the subsequent response.