WO2009043280A1

WO2009043280A1 - A method, equipment and system for identifying service type and establishing service according to the identifier

Info

Publication number: WO2009043280A1
Application number: PCT/CN2008/072492
Authority: WO
Inventors: Lei Xie
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-26
Filing date: 2008-09-24
Publication date: 2009-04-09
Also published as: CN101400022B; CN101400022A

Abstract

A method, equipment and system are disclosed for identifying service type and establishing service according to the identifier to improve user experience. The method for identifying service type includes: step 1, selecting the sub-service in the converged messaging service; step 2, identifying the selected sub-service in the message. The session type information is obtained by the two session users prior to the session by means of identifying the different service types, which thereby enables the user experience. At the same time, the resource distribution, recording of charge messages and other necessary tasks which are needed by the service are completed according to the pre-configuration of the system by using the means in the converged service system. This reduces the processing service complexity of the converged service system, and increases the ability of said system to process different service types.

Description

Method, device and system for identifying a service type and establishing a service according to the identification

The present invention relates to the field of wireless communications, and in particular, to a method, device and system for identifying a service type and establishing a service according to the identification. Background technique

Mobile communication networks (such as 2G (2nd Generation, 2nd Generation Digital Communication), 3G (3rd Generation, 3rd Generation Digital Communication) and multimedia sub-domains) and the Internet (Internet) carry out message services including short messages, multimedia messages Instant messaging and converged messaging services, etc., wherein instant messaging and converged messaging are messaging services based on SIP (Session Initiation Protocol) technology, belonging to personal-to-person, personal-to-application and personal-to-group based on presence information. The message class of mobile data services.

The existing messaging service engine defined by OMA (Open Mobile Alliance) is designed and standardized separately, and its messaging service provides a single user experience and is limited to a specific medium and application. E.g:

1. SMS (Short Message Service) provides a basic text message service;

2. MMS (Multimedia Message Service) provides basic multimedia messaging services;

3, IM (Instant Message, Instant Messaging) provides quasi-real-time text services;

4. PoC (Push-To-Talk over Cellular) provides a half-duplex voice service.

With the development of networks and technologies, many messaging services have begun to alternate, with the following characteristics:

1. Many services support multimedia;

2. Many services are based on presence information;

3. Many services have a single address book;

4, have some common functions and capabilities shared, such as XML (extensible Markup Language, Extensible Markup Language) Document Management.

The convergence of these features requires a single converged messaging platform to absorb different technologies and support different messaging experiences for users. IP-based converged messaging, CPM (Converged IP Messaging), is a new messaging service framework defined by OMA to provide users with a converged business experience, such as: instant messaging, offline messaging, multimedia sessions, half-duplex / Full-duplex audio, video conferencing, etc. Converged Messages CPM services allow users to use communication services with different technical characteristics in a unified manner, overcoming the "slots" (silos) between non-CPM message services due to technical differences, thus providing a unified service experience for user services.

While consolidating the basic capabilities of existing messaging services, the CPM service also incorporates many of the business features that emerged during the evolution of mobile data services, such as:

1. CPM can manage multiple simultaneous sessions with different media types, allowing users to set services according to different devices, contact addresses, and media types.

2. The CPM service does not depend on the carrier network and user terminals, so it can provide services in a multi-terminal environment;

3. CPM provides the ability of users, such as messages and multimedia content, to store personal networks;

4. CPM supports seamless interconnection with non-CPM messaging systems, enabling maximum interoperability between different types of message users;

5. CPM not only supports one-to-one, one-to-many data communication services, but also provides the ability to interact with third-party applications. In the process of implementing business capabilities, CPM interacts with other functional entities in OMA, such as rendering servers and XML. Document management entity.

The convergence of services provides users with a more convenient, fast and practical user experience. For example, the introduction of a converged IP messaging project can free users from the trouble of using different client software for a large number of messaging services. Although the convergence of services transforms various services into a converged service through a unified platform and architecture, the specificity of the original services still exists, taking full-duplex and half-duplex sessions as examples. Among them, OMAIM provides SIP-based technology. Instant messaging, which can support message conversations based on text and discrete media types, as well as message chat room functions that involve multiple users, and can also provide temporary storage and notification of offline messages. OMA PoC mainly provides half-duplex voice based on SIP technology, supports controllable real-time voice conversation, and can realize group communication and network storage. However, its application scenario does not include message exchange, mail sending or receiving, or non-CPM messaging system (such as SMS). Interconnection of systems, MMS systems, etc.).

In the process of implementing the present invention, the inventor has found that the prior art has at least the following problems: The service scope of the existing CPM includes the above two types of sessions, and the user experience of the two sessions is greatly different, so before the session is performed, The inviting party and the receiving party of the session need to know the type of the current session to be performed. In addition, the system also needs to perform functions such as charging and allocating resources according to different session types. However, the prior art does not provide a mechanism to identify different service types. Therefore, not only the two parties of the session cannot obtain the type information of the session to be performed before the session, and thus the corresponding service experience of the user cannot be realized, and the service system is integrated. It is also impossible to complete the resource allocation and billing information recording required for the service type according to the pre-system configuration.

Summary of the invention

The embodiments of the present invention provide a method, a device, and a system for identifying a service type and establishing a service according to the identifier, so as to improve the service experience of the user.

To achieve the above, the embodiment of the present invention provides a method for identifying a service type, including:

Select a sub-service in the converged message service;

The selected sub-service is identified in the message.

In addition, an embodiment of the present invention provides an apparatus for identifying a service type, including: a selecting unit, configured to select a sub-service in a converged message service;

An identification unit, configured to identify the selected sub-service in the message.

An embodiment of the present invention further provides a method for establishing a service according to a service type identifier, including:

After receiving the message sent by the first user, the first server selects the sub-service in the fused message service, and determines whether the selected sub-service is identified in the message, and if yes, sends the message Sending the message, if not, identifying the selected sub-service in the message, and then transmitting the message;

And establishing the sub-service between the first user end and the second user end according to the identifier. In the meantime, the embodiment of the present invention provides a system for establishing a service according to a service type identifier, including:

a first user terminal, configured to send a message;

a first server, configured to receive a message sent by the first user, where the first server is further configured to select a sub-service in the fused message service, and determine whether the selected sub-service is identified in the message, if Sending the message, if not, identifying the selected sub-service in the message, and then transmitting the message;

The second user end is configured to receive the message, and establish the sub-service with the first user end according to the identifier.

After receiving the message sent by the first user, the identifier conversion device first determines the type of the sub-service in the message, selects the corresponding service type supported by the second user, and converts the service type identifier in the message into the second user service. Type the identifier, and then send the message carrying the service type identifier;

a first user terminal, configured to send a message;

The identifier conversion device is configured to receive the message sent by the first user end, determine the type of the sub-service in the message, select a corresponding service type supported by the second user end, and convert the service type identifier in the message into the second user service. Type identifier

And the second user end is configured to receive the message forwarded by the identifier conversion device, and establish the service with the first user end according to the second user service type identifier.

Compared with the prior art, the embodiment of the present invention identifies different service types by selecting a sub-service in the fused message service and setting a service identifier for the selected sub-service. In this way, the two parties of the session can obtain the type information of the session before the session, thereby implementing the corresponding service experience of the user. At the same time, the method is adopted in the converged service system, so that the system can complete the service according to the pre-system configuration. The resource allocation and billing information records required by the type enhance the ability of the converged service system to handle different service types. DRAWINGS

1 is a flowchart of identifying different service types in an embodiment of the present invention;

2 is a schematic diagram of an apparatus for identifying different service types in the embodiment of the present invention; FIG. 3 is a flowchart of establishing a service according to a service type identifier in the embodiment of the present invention; FIG. 4 is a schematic diagram of establishing an IM according to two converged message service users in the embodiment of the present invention; Business flow chart;

FIG. 5 is a flowchart of establishing a service according to a PoC service system and a converged message service system according to an embodiment of the present invention. detailed description

In order to make the objects, technical solutions and advantages of the present invention more comprehensible, the embodiments of the present invention will be further described in detail with reference to the accompanying drawings.

Referring to FIG. 1, a method for identifying a service type in a converged service system according to Embodiment 1 of the present invention includes the following steps:

Step 10: Select a sub-service in the converged message service.

Step 11: Identify the selected sub-service in the message.

The foregoing sub-services may be full-duplex session services or half-duplex session services, but the present invention is not limited to the two types of session services, and other sub-services included in the converged service system are within the scope of the present invention. After the calling party selects the sub-service, different service type identifiers are used to distinguish different sub-services, and the specific sub-service identifiers are described in detail below.

The sub-services in the converged message service may be selected by the user end, that is, the sub-services in the converged service are selected at the user end under the direction of the user. The subjective will of the user, that is, the user can choose to use one of the sub-services in the converged service system according to his or her own wishes.

The sub-services in the converged service service may also be selected by the network, and the network may determine which sub-services in the converged service system are used according to the settings of the user or the policy of the operator or the information obtained from other entities. And identify the corresponding sub-service in the message. Regardless of the form in which the sub-service is identified in the message, once the identity is determined, it cannot be changed. Until the use of the sub-service is completed, the session is the end of the session. The selection of the sub-service type can be based on the time the user uses the type of service, the bearers allowed by the network, and other conditions.

According to the setting of the client, the user selects the corresponding sub-service in different situations, and the network uses the selected sub-service as its sub-service according to different situations.

According to the operator's policy, when the calling party and the called party's settings conflict, for example, the calling party selects the full-duplex session service, and the called party sets the half-duplex session service, and the calling party and the calling party both occur. Conflicts require operators to make decisions. In a specific case, for a specific time, for example, the sub-service selected by the calling party may be very busy. In this case, the decision of the operator is also required according to the strategy of the operator. In short, there may be multiple situations according to the operator's policy. Not described in detail.

According to the information obtained from other entities, the information obtained from other entities is used as the basis for selecting the sub-service. For example, the converged service system can obtain the communication mode desired by the receiver user from the converged address book to select the service type. The network side selects the sub-services in the converged message service is not limited to the above embodiments, and any implementation manner that can implement the network side to determine a sub-service is in the present invention.

The message may be a SIP message.

The identifying the selected sub-service in the message is performed by carrying the feature identifier in the message, where the feature identifier may be a feature identifier added in the Accept-Contact header field, or added in the custom header field. The feature identifier, or the service feature of the message body, will be described in detail below.

The first method is to add a feature identifier in the Accept-Contact header field to identify the selected sub-service. According to the IETF (The Internet Engineering Task Force, RFC3841, defined by the Internet Engineering Task Force, can add feature identifiers in the Accept-Contact header field to indicate different types of services. For example, a +g.oma.sip-CPM-IM or a +g.oma.sip-CPM-PoC identifier is added to the CPM, where the two identifier suffixes are respectively IM and PoC to distinguish two different session services. The present invention is not limited to the above two identification methods, and any identification method capable of distinguishing the two different session services is applicable to the present invention, and in addition to the above two CPM sub-services, other types of CPM sub-services may also be marked with corresponding identifiers. distinguish. The same reason. The CPM client or the CPM server can add a corresponding identifier in the session invitation Accept-Contact header field to indicate the type of session to be initiated. Table 1 below shows that the CPM client initiates a PoC type half-duplex session in the session. The message after the PoC type service identifier is added to the Accept-Contact header field.

Table 1

Request-URI sip: CPM. networkA. net

SIP HEADERS

P-Preferred-Identity: "CPM User A" <sip: CPM-User A@networkA. net>

Accept-Contact: *;+g.oma.sip-CPM-PoC;+g.poc.talkburst;require;explicit

User-Agent: CPM-client/OMA2.0 Acme-Talk5000/vl.01

Contact: <sip:CPM-ClientA.networkA.net>;+g.poc.talkburst

Supported: Timer

Session-Expires: 1800; refresher=uac

Allow: INVITE, ACK, CA CEL, BYE, REFER, SUBSCRIBE,

NOTIFY, OPTIONS

SDP ARAMETERS

c= IN IP6 5555::aaa:bbb:ccc:ddd

m= audio 3456 RTP/AVP 97

a= rtpmap:97 AMR

a= rtcp:5560 m= application 2000 udp TBCP

a= fmtp:TBCP queuing=l; tb_priority=2; timestamp=l

The second method is to add a feature identifier in the custom header field to identify the selected sub-service, that is, to implement the feature identifier by using a specific identifier service header field. For example, by adding a specific header field in the SIP message header field to carry the service identifier, H does not add a Service header field in the SIP message header field to indicate different types of services, and the CPM user or the CPM server can be in the Service header field. Add content to identify these businesses. Table 2 below shows the message after the CPM client initiates a PoC-type half-duplex session and adds a predefined PoC type service identifier (such as +g.oma.sip-CPM-PoC) in the session invitation service header field.

Table 2

a= rtcp:5560

m= application 2000 udp TBCP

a= fmtp: TBCP queuing=l; tb_priority=2; timestamp=l wherein the third method of the present invention identifies the selected sub-service according to the service characteristics of the message body. Since the Media Burst Control Protocol is a protocol unique to the PoC type service, once the media stream transmission control protocol is added to the session invitation, it indicates that a PoC type half-duplex session is to be established, so the client or The server can know the type of service for which the session is to be established by parsing the content in the message body. Table 3 below shows that the CPM user initiates a PoC-type half-duplex session with no other identifiers, but the message body contains the media stream transmission control protocol mapped to the Session Description Protocol, which is reflected in Table 3. In the Contact, force +g.poc.talkburst.

table 3

Request-URI sip: CPM. networkA. net

SIP HEADERS

P-Preferred-Identity: "CPM User A" <sip: CPM-User A@networkA. net>

Accept-Contact: *;+g.poc.talkburst; require;explicit

User-Agent: CPM-client/OMA2.0 Acme-Talk5000/vl.01

Contact: <sip:CPM-ClientA.networkA.net>;+g.poc.talkburst

Supported: Timer

Session-Expires: 1800; refresher=uac

Allow: INVITE, ACK, CA CEL, BYE, REFER,

SUBSCRIBE, NOTIFY, OPTIONS

SDP PARAMETERS

c= IN IP6 5555::aaa:bbb:ccc:ddd

m= audio 3456 RTP/AVP 97 a= rtpmap:97 AMR

a= rtcp:5560

m= application 2000 udp TBCP

a= fmtp:TBCP queuing=l; tb_priority=2; timestamp=l In the CPM, not all PoC-type half-duplex session control messages carry the media stream transmission control protocol, but once this session is established, the system The session type and the session identifier can be automatically matched, even if the message in the session does not have a media stream transmission control protocol, it can be judged that this is a PoC type half-duplex session.

In addition, the feature identifier of the present invention is not limited to the foregoing three methods, and may be used to identify that the selected sub-service is identified according to the setting of the called party. In summary, any implementation feature identifier is in the scope of protection of the present invention. within.

As shown in FIG. 2, it is a device for identifying a service type corresponding to the first embodiment of the present invention, where the device 10 includes:

The selecting unit 11 is configured to select a sub-service in the fused message service;

The identifying unit 12 is configured to identify the selected sub-service in the message.

The sub-service is a half-duplex session service or a full-duplex session service.

The device 10 is a user end or a network end, where the selected sub-service is identified in the message as the user side actively selects, or the network end obtains according to the setting of the user end, or the policy of the operator or from other entities. The information is selected and the sub-services in the message service are integrated. The specific implementation is described in detail in the first embodiment, and details are not described herein again.

The message is a SIP message.

The identifier unit 12 carries the feature identifier in the message according to the selected sub-service to identify the sub-service. The feature identifier may be a feature identifier added in the Accept-Contact header field, or a feature identifier added in the custom header field, or a service feature of the message body. The detailed description has been described in detail in Embodiment 1, and details are not described herein again.

It can be seen that the first embodiment of the present invention provides a method and an apparatus for identifying different service types. By identifying an IM session service or a PoC session service, or other session service type, both parties of the session can understand the type of the session, thereby improving the user. Business experience. The first embodiment of the method for establishing a service according to the service type identifier is shown in FIG. 3, and the specific steps are as follows:

Step 101: The first UE sends a message to the first serving call control function entity. Step 102: After receiving the message, the first serving call control function entity forwards the message to the first server.

Step 103: After receiving the message, the first server selects a sub-service in the converged message service.

Step 104: The first server determines whether the selected sub-service is identified in the message, and if yes, sends the message, and if no, step 105 is performed.

Step 105: Identify the selected sub-service in the message, and then send the message with the identifier to the first service call control function entity.

Step 106: After receiving the message forwarded by the first server, the first serving call control function entity forwards the message to the second serving call control function entity.

Step 107: The second serving call control function entity receives the message forwarded by the first serving call control function entity, and forwards the message to the second server.

Step 108: After receiving the message, the second server forwards the message to the second user.

Step 109: Establish the sub-service between the first user end and the second user end according to the identifier.

The sub-service is a half-duplex session service or a full-duplex session service. The selected sub-service may be identified by using a feature identifier carried in the message, where the feature identifier may be a feature identifier added in an Accept-Contact header field, or a feature identifier added in a custom header field, or The service feature of the message body; or the first server identifies the selected child service according to the setting of the called party.

The first user end and the second user end may be CPM users.

As shown in FIG. 4, the second embodiment of the present invention is a flowchart for establishing a service according to a service type identifier of two CPM users. In addition, the first user terminal may also be a full-duplex user or a half-duplex user, and the second user terminal is The process of establishing a service according to the service type identifier of the CPM user is shown in Figure 4. As shown in Figure 4, the CPM acts as a converged IP message, including at least the full-duplex session of the IM and the half-duplex session of the PoC. Since the two sessions have different system settings and user experience, it is necessary to identify this in the session control. Two kinds of sessions, Figure 4 is a scenario where one CPM user initiates a session invitation to another CPM user.

Step 1 : The CPM user 1 wants to communicate with another CPM user 2, and sends a session invitation to the S-CSCF (Serving-Call Session Control Function). 1 The session invitation does not specify the type of the session.

Step 2: The S-CSCF1 sends the session invitation to the CPM CS (Converged IP Messaging Conversation Server, hereinafter referred to as the CPM conference server).

Step 3: The CPM session server 1 finds that the calling user wants to use the IM session exchange according to the user setting, and adds the IM type identifier to the invitation.

Step 4: The CPM session server 1 forwards the session invitation carrying the identifier to the S-CSCF1.

Step 5: The S-CSCF1 forwards the session invitation carrying the identifier to the receiver S-CSCF2.

Step 6. The S-CSCF2 forwards the session invitation to the CPM session server 2 of the recipient user's home location.

Step 7: The CPM session server 2 forwards the session invitation to the receiver CPM user 2. The CPM user 2 knows by the identifier that the CPM user 1 wishes to establish an IM type CPM session.

Steps 8 ~ 12, the called user returns a response message.

Among them, Figure 4 only shows the services that two CPM users want to establish IM communication. Similarly, the two CPM users want to establish PoC communication services, or establish other CPM sub-services.

The second embodiment of the second embodiment of the present invention is a scenario in which the user 1 initiates a session invitation and the user 2 does not perform setting. The second embodiment of the present invention is a scenario in which the user 1 initiates a session invitation and the user 2 performs setting, which is different from the second embodiment: In step 3, the CPM session server 1 finds that the user 2 wishes to use according to the user 2 setting. IM Session communication, adding the IM service type identifier to the invitation, and notifying the user 1 that the session initiated is an IM session.

In addition, in the fourth embodiment of the present invention, the user 1 specifies a session type in the session invitation, such as an IM session, and the user 2 also sets the user type as a PoC session, which is different from the second embodiment: In the session invitation of 1, the IM session is specified. In step 3, the CPM session server 1 finds that the called user wants to use the PoC session to communicate, the CPM session server 1 selects according to the policy, and if the IM session is selected, the IM session service type identifier is selected. If the PoC session type is selected, the PoC session service type identifier is added to the invitation and the session initiated by the user 1 is notified to be a PoC session service.

The fifth embodiment of the present invention is as shown in FIG. 5. The CPM system involves interworking with an IM or a PoC system. When interworking with these systems, the corresponding identifier needs to be converted. FIG. 5 identifies the PoC user. Send a scene to invite CPM users.

Step 1 : The PoC user 1 wants to communicate with another CPM user 2, and sends a PoC session invitation to the S-CSCF1.

Step 2: The S-CSCF1 sends the PoC session invitation to the PoC AS (PoC Application Server) of the sender's home location.

Step 3: After the PoC session server processes the session invitation, it forwards it to S-CSCF1. Step 4: The S-CSCF1 forwards the session invitation to the S-CSCF2.

Step 5: The S-CSCF2 forwards the session invitation to the CPM session server 2 of the recipient user's home location.

Step 6: After receiving the session invitation, the CPM session server 2 first determines the type of the inviting neutron service, and finds the PoC session service, and converts the service identifier of the PoC system into the PoC service type identifier in the CPM. This work can also be performed in other The identity conversion entity is completed, as in the IWF (Interworking Function), and the difference from the above process is that the interworking function entity routes the session invitation to the CPM session server 2 after completing the conversion, by the CPM session server. 2 is sent to the recipient CPM user.

Step 7, the CPM session server 2 forwards the session invitation to the receiver CPM user. 2. The CPM user 2 knows by the identifier that the PoC user 1 wishes to establish a PoC session. Steps 8 ~ 12, the called user returns a response message.

In Figure 5, only the process of establishing a PoC communication between the PoC user and the CPM user is given. Similarly, the IM process is also applicable to the IM user and the CPM user. In addition, if the CPM user sends a session invitation to the PoC user or the IM user as the calling party, the CPM server converts the PoC service type identifier or the IM service type identifier in the CPM into the service identifier of the corresponding PoC system or the service identifier of the IM system. The user type of the user initiated by the CPM user is notified to establish a service with the PoC user or the IM user. The specific process is not described here.

It can be seen that the server and the client of the converged service system can identify the corresponding service type according to the service identifier, and according to different service types, the server can perform functions such as corresponding charging and resource allocation, and the user can learn the service. Type, which improves the user experience.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware or by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for identifying a service type, comprising:

Select a sub-service in the converged message service;

The selected sub-service is identified in the message.

The method for identifying a service type according to claim 1, wherein the sub-service is a half-duplex session service or a full-duplex session service.

The method for identifying a service type according to claim 1, wherein the selecting a sub-service in the converged message service is performed by a user, or the network is configured according to a user end, or an operator's policy or a slave The information obtained in other entities is selected.

4. The method for identifying a service type according to claim 1, wherein the message is a Session Initiation Protocol SIP message.

The method for identifying a service type according to any one of claims 1 to 4, characterized in that the selected sub-service is identified in the message by carrying the feature identifier of the sub-service in the message.

The method for identifying a service type according to claim 5, wherein the feature identifier is a feature identifier added in an Accept-Contact header field, or a feature identifier added in a custom header field, or The business characteristics of the message body.

7. A device for identifying a service type, comprising:

a selection unit, configured to select a sub-service in the converged message service;

The device for identifying a service type according to claim 7, wherein the sub-service is a half-duplex session service or a full-duplex session service.

The device for identifying a service type according to claim 7, wherein the device is a client, and the selecting unit of the client selects a sub-service in the fused message service; or

The device is a network, and the selecting unit of the network selects the information in the fused message service according to the setting of the user end, or the policy of the operator or the information obtained from other entities. Sub-business.

The apparatus for identifying a service type according to any one of claims 7 to 9, characterized in that the identification unit identifies the selected sub-service according to the feature identification of the sub-service selected by the selection unit.

The device for identifying a service type according to claim 10, wherein the feature identifier is a feature identifier added in an Accept-Contact header field, or a feature identifier added in a custom header field, or The business characteristics of the message body.

12. A method for establishing a service according to a service type identifier, the method comprising: after receiving a message sent by the first user end, the first server selects a sub-service in the converged message service, and determines whether the identifier is selected in the message. The sub-service, if yes, send the message, if not, identify the selected sub-service in the message, and then send the message;

And establishing the sub-service between the first user end and the second user end according to the identifier.

The method for establishing a service according to a service type identifier according to claim 12, wherein the sub-service is a half-duplex session service or a full-duplex session service.

The method for establishing a service according to the service type identifier according to claim 12, wherein before the first server receives the message sent by the first user, the method further includes the following steps:

Receiving, by the first serving call control function entity, the message sent by the first user end;

The first serving call control function entity forwards the message to the first server.

The method for establishing a service according to the service type identifier according to claim 12, wherein the step of establishing the sub-service between the first user end and the second user end further comprises the steps of:

The second service call control function entity receives a message sent by the first service call control function entity;

The second serving call control function entity performs the first service call control function The message sent by the entity is sent to the second server;

The second server sends a message sent by the second serving call control function entity to the second user end.

The method for establishing a service according to a service type identifier according to any one of claims 12 to 15, wherein the selected sub-service is identified by carrying the feature identifier of the sub-service in the message.

The method for establishing a service according to a service type identifier according to claim 16, wherein the feature identifier is a feature identifier added in an Accept-Contact header field, or a feature identifier added in a custom header field. , or the business characteristics of the message body.

A system for establishing a service according to a service type identifier, comprising: a first user end, configured to send a message;

And the second user end is configured to receive the message carrying the identifier, and establish the sub-service with the first user end according to the identifier.

The system for establishing a service according to the service type identifier according to claim 18, wherein the sub-service is a half-duplex session service or a full-duplex session service.

The system for establishing a service according to the service type identifier according to claim 18, further comprising:

And a first service call control function entity, configured to receive the message sent by the first user, and forward the message to the first server.

The system for establishing a service according to the service type identifier according to claim 20, further comprising: a second service call control function entity and a second server, wherein the second service call control function entity is configured to receive Transmitting, by the first service call control function, a message carrying the identifier, and forwarding the message carrying the identifier to the second server;

The second server is configured to send the second service call control function entity A message is sent to the second client.

The system for establishing a service according to the service type identifier according to any one of claims 18 to 21, wherein the first server identifies the selected child by carrying a feature identifier of the sub-service in the message. business.

The system for establishing a service according to the service type identifier according to claim 22, wherein the feature identifier is a feature identifier added in an Accept-Contact header field, or a feature identifier is added in a custom header field. Or the business characteristics of the message body.

A method for establishing a service according to a service type identifier, comprising: after receiving the message sent by the first user end, the identifier conversion device first determines the type of the sub-service in the message, and selects the type supported by the second user end. Corresponding service type, and converting the service type identifier in the message into a second user service type identifier, and then sending a message carrying the service type identifier;

25. A method of establishing a service based on a service type identifier according to claim 24, wherein:

If the first user end is a full-duplex session service user or a half-duplex session service user, the second user end is a converged message service user;

If the first user end is a converged message service user, the second user end is a full-duplex session service user or a half-duplex session service user.

The method for establishing a service according to the service type identifier according to claim 24, wherein the identity conversion device is a converged message service server or an interworking function entity.

27. A system for establishing a service according to a service type identifier, comprising: a first user end, an identity conversion device, and a second user terminal,

The first user end is configured to send a message;

The identifier conversion device is configured to receive the message sent by the first user end, determine the service type identifier of the sub-service in the message, select a corresponding service type supported by the second user end, and select the message Converting the service type identifier into a service type identifier supported by the second client; The second user end is configured to receive the message forwarded by the identifier conversion device, and establish the service with the first user end according to the second user service type identifier.