WO2008043261A1

WO2008043261A1 - Convergent message system

Info

Publication number: WO2008043261A1
Application number: PCT/CN2007/002831
Authority: WO
Inventors: Liming Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-09-29
Filing date: 2007-09-27
Publication date: 2008-04-17
Also published as: CN101155329A; CN101155329B

Abstract

A convergent message system includes: a first user equipment installed a first client program and used for initiating a message service request; a common message processing unit (20) for receiving the message service initiated by the first user equipment, and sending the message service request to a corresponding message service processing unit (30) according to the content of the message service request; and a message service processing unit (30) for processing the corresponding message service.

Description

A fusion message system

The present invention relates to the field of communications, and in particular, to a converged message system. Background technique

With the development of telecommunication services, more and more messaging services have emerged. Short message service

(Short Message Service, SMS), multimedia messaging service, instant messaging (IM) service, typical IM in mobile applications, mobile IM, Internet-based IM, etc., in addition to simultaneous support for voice and multimedia messaging That is to say, cluster services (POC), and frequent use of emails. It can be seen that the message-based business has become one of the important services of the current telecommunications and Internet services. It is also foreseeable that the message service is also one of the key services in the next generation network/next generation mobile network (NGN/NGMN).

The commonly used message services are as follows:

(1) Short message service:

The short message service adopts the storage and forwarding mode, and the bearer channel is the control signaling channel, so the information capacity is not large, and a short message contains at most 140 bytes (160 characters or 70 Chinese characters). In addition to providing SMS/SMS service between SMS users, it also works with content providers (CPs) and service providers.

(SP) cooperated to carry out information (content) services such as information on demand and information subscription by using the bearer channel of SMS, and created a mobile data value-added service. SMS information has a small capacity and a single form of information. After the General Packet Radio Service (GPRS) packet bearer channel is introduced in the Global System for Mobile Communications (GSM) network (G network), SMS can be offloaded to the GPRS bearer channel, which increases the information capacity of the SMS and reduces the information capacity. The load of the signaling channel.

As shown in Figure 1, is the location of the short message system in the GSM network, where the short message center

(Short Message Center, SMC) is a business processing system independent of the GSM network. Its main functions are to submit, store, forward short messages, and complete the public switched telephone network (PSTN), comprehensive Interworking between networks such as the Service Digital Network (ISDN) and the Public Packet Switched Data Network (PSPDN) to implement the delivery of short messages from other SMCs.

The location of the short message system in the network is shown in Figure 1. The physical entities associated with the short message system are the Mobile Switch Center (MSC)/Visitor Location Register (VLR) and the home location register (Home). Location Register, HLR, ), their respective roles in the short message sending process are as follows:

MSC: The short message submitted by the mobile subscriber (Mobile Subscriber, MS) arrives at the MSC through the Base Station Subsystem (BSS), and the MSC is responsible for handing over to the corresponding short message system.

After receiving the short message sent by the short message system, the MSC system sends the relevant route and user information to the VLR and the HLR, and delivers the information to the user through the BSS base station subsystem.

VLR: Provides authentication management before the user sends a short message and when the short message is sent, the MSC looks up the user route.

HLR: Before the short message system sends a short message, it searches for the basic information of the user when the home MSC and the MSC send a short message.

Features of short message service:

(1) The transmission of SMS uses the store-and-forward method, that is, after the short message is sent, it is not sent directly to the receiver, but is stored in the Short Message Service Center (SMSC), and then forwarded by the SMSC. To the recipient. The MS can receive/send short messages regardless of whether it is at the home office or when roaming; the database of the short message center automatically stores the short message sent to the MS even if the MS is powered off, not in the wireless coverage, or the SMS overflows in the SIM card memory. (generally no more than three days), when the MS is valid, send it again;

(2) Support the transmission of two-way information, that is, the mobile station can receive/send short messages;

(3) In the process of sending a short message, the SMS sender can receive a confirmation notice after sending the short message, return the message of success or failure, and the reason why the other party cannot reach.

(2) Multimedia messaging services:

Multimedia Messaging Service (MMS M乍 is the evolution of SMS, It is a service processing system independent of the mobile communication network and can be applied to 2.5G/3G networks such as GRPS, Code Division Multiple Access (CDMA IX), Wideband CDMA (WCDMA), etc. Complete the functions of submitting, storing, and forwarding multimedia messages. Multimedia messages can include text, graphics, animation, video, audio, and more. MMS services can be used in a little bit, point to application, application to point, and so on.

As shown in Figure 2, it is a schematic diagram of the standard architecture of the MMS system. The network devices in the MMS system include MMS Relay (MMS Relay), MMS Server (MMS Server), User Database (User Database) and User Agent (MMS User Agent). )Wait.

MMS Server: Responsible for storing and processing multimedia short messages in both directions of arrival and departure. There can be multiple MMS servers in each MMSE. The MMS server can work with standard external interfaces such as E-Mail servers and SMS servers on the external network to provide users with a rich service type.

MMS Repeater: Responsible for passing messages between different messaging systems to consolidate various types of servers in different networks. The MMS repeater should be able to generate charging data (CDR) when receiving or delivering messages to other MMS User Agents or to another MMSE. The MMS repeater and MMS server also have the function of address translation and temporary storage of multimedia messages to ensure that multimedia messages are not lost until they are successfully transferred to another MMSE entity.

MMS User Database: Records business information related to the user. Such as the user's business characteristics, control of users accessing MMS services, and so on.

User agent: It can be located in the user device or in an external device directly connected to the user device. A user agent is a functional entity at the application layer that provides users with the ability to browse, synthesize, and process multimedia messages. The processing of multimedia messages includes operations such as sending, receiving, and deleting. The MMS user agent also provides negotiation of the capability of the user terminal to receive the multimedia message; sends the multimedia message notification to the user; encrypts and decrypts the multimedia message of the user; and signs the multimedia message between the users; and processes the case where the user's SIM card supports the MMS Information related to MMS in the SIM card; management of user characteristics and other functions.

The working principle and process of MMS: The multimedia information service is built on the data transmission network using the Wireless Application Protocol (WAP) as a carrier. It is available in GSM networks (R7/R8), GPRS networks, CDMA IX and future 3G networks. However, in order to obtain a user-satisfied bandwidth, it is preferably in a GPRS, CDMA IX or 3G network environment, and of course, in a GSM network that implements High Speed Circuit Switched Data (HSCSD) technology.

WAP technology plays an important role in multimedia information services. Push via WAP,

Notification and Poll functions, the end user can complete communication with the system.

Taking the system to send information to the mobile phone as an example, analyze the process of the multimedia information service. The process is as follows:

(1) When a multimedia message is sent to a user, the information is encoded by WAP's Wireless Session Protocol (WSP) and transmitted to the WAP gateway through the wireless network; (2) The WAP gateway uses HTTP protocol and MMS. -Relay communicates and transfers the contents of the file to MMS-Relay;

(3) MMS-Relay sends the file to the MMS-C server. The content of the multimedia information in the server is converted into a Multipurpose Internet Mail Extensions (MIME) format and stored in the SMS memory.

(MMS-Message Store);

(4) The server performs data analysis to obtain routing information, user terminal information, and the like. The information in the user database is called during the analysis. The system will determine whether the user's terminal can support MMS and perform different processing according to the user's terminal's carrying capacity (such as display resolution, terminal capacity, etc.). For example, when the user terminal does not support the MMS, the system will remove the multimedia information in the multimedia information, and only send the text portion of the information to the user by means of a short message;

(5) After confirming the processing method, the system passes the called user's mobile user international ISDN

(MSISDN) number is routed. MMS-Relay will communicate with the external network through the WAP gateway. This information is always stored in the SMS memory until it has been confirmed that the called user has accepted the message. The operator can set the length of time saved by software;

(6) The system server generates billing information and transmits it to the billing center. The concept of instant messaging is similar in fixed networks and mobile networks. Mobile IM, developed by the Open Mobile Alliance (ΟΜΑ), is integrated with other innovative features, with good interoperability and enhanced user experience. Users can use point-to-point messages and point-to-multipoint messages, send IM messages to terminals that are not online, send IM messages to non-IM terminals or unknown terminals, interwork with E-mail, and other IM systems (MSN, ICQ, etc.) Interoperability and other services. Generally, IM comes with presence capability. presence is the key enabling technology of IM. It includes client device validity (mobile phone on/off, making a call), user status (free, no time, meeting) , location, client device capabilities (voice, text, GPRS, multimedia) and user status for searching, such as mood (happy, angry) and hobbies (soccer, fishing, computer, dancing). Because the Presence attribute is personal, the user can control the permissions according to their own wishes. The IM system architecture of the SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE) protocol. The core of the IM services provided by the IM client is the IM client and the IM server.

The IM Client is located in the mobile terminal and is used to initiate/participate/terminate the IM session and send and receive instant messages from the peer IM Clients or IM Server;

The IM Server is located on the network side and is responsible for receiving IM session requests from users, creating and managing IM sessions, sending and receiving IM messages, maintaining chat room information, responsible for media copying and distribution, providing online transmission and storage of offline messages, and providing mobile IM and fixed network IM. Interactions, interoperability with remote IM systems, etc.

(iv) PoC:

The concept of the PoC service comes from the walkie-talkie, and its user experience is similar to that of the walkie-talkie. It is simple, fast, and half-duplex. By setting the call group in advance, the user does not need to dial when making a call, and press and hold a specific button to simultaneously transmit the voice to all other members in the group. The button is spoken, and the call and call connection process is completed in an instant. The receiver can answer without any response. The call process uses half-duplex mode. When one party is talking, other members can only answer and cannot speak.

The organization that formulates the PoC standard specification is OMA. The schematic diagram of the PoC network defined in the specification is shown in Figure 4. Shown. The PoC network is based on the IP Multimedia Subsystem (IMS) ("SIP/IP core" in the figure). The main entities are as follows:

PoC Server (PoC Server): is the main call control device of the service, and is an Application Server of the IMS network;

PoC Document Management Server (XDMS): Storage

a server for data such as group information required by the PoC service;

PoC Client: The user uses the client and the PoC Server to initiate, receive PoC calls, apply for a floor, speak, and so on.

After the PoC group call is established, the user can apply for the floor to the PoC server through the Talk Burst Control Protocol (TBCP) protocol. Only when the floor is obtained, the user is allowed to speak. The Talk Burst can be forwarded by the PoC Server to other members of the group. As shown in Figure 5, it is a flow chart of the application for the right to speak. The process is as follows:

Steps 501 - 502: The user can apply for a floor (Floor) to the PoC Server through the TBCP protocol "Talk Burst Request" message;

Steps 503 - 504: The PoC Server returns a "Talk Burst Granted" message to the applicant to inform him that he has been permitted to speak;

Steps 505 - 506: The PoC Server also sends a "Talk Burst Taken" message to other users to inform the current speaker information to other members participating in the group session;

Steps 507 - 510: The user who gets the speech speaks, and the media stream (Talk Burst) is forwarded by the PoC Server to other members in the group;

Steps 511 - 512: The user completes the speech and releases the floor;

Steps 513 - 516: The group floor is idle, and the PoC Server broadcasts a "Floor Control Idle" message to the group members.

Considering the importance of messaging services, how to continuously improve the experience of messaging services, simplify the implementation of messaging services, and protect existing investments of operators, is becoming a research hotspot in the industry. At present, various standards organizations have established corresponding working groups and topics for these news services and Their evolutionary development is standardized.

In addition, with the all-IP of the mobile fixed network and the development of the 3GPP IMS subsystem, the IP of various network services and applications is also the trend of the times. Under the condition of all IP, it is possible to implement the message service by adopting a unified mechanism and method. .

One of the characteristics of the current message service is that there are many types of message services, and users can choose according to their own needs. There are also many types, which cause the user to be confused at the time of selection. The service experience is relatively poor. For example, when sending a simple text message, using SMS, when sending pictures, using MMS, when you want to communicate in real time through session In addition, the IM service is used, and if half-duplex voice chat is to be switched to the PoC, the similar situation makes the user use the message service more complicated. In addition, these different messaging services have their own implementation systems and interface specifications, and the maintenance costs and interworking costs are high.

To summarize the shortcomings of existing messages, it can be described as:

The user needs to select and switch between various message services, and the use is complicated, and the user experience can be further improved;

The message service functions are similar, and the service characteristics overlap each other;

Each message service has its own implementation method, which is based on different platforms and architectures, and has high maintenance costs and difficulties in interoperability;

The subsequent addition of new message features is very complicated, and the introduction of new message services is prone to user confusion. Summary of the invention

The embodiments of the present invention provide a converged message system, which is used to solve the problem that the user uses the message in the prior art and the maintenance of the message is difficult.

The embodiment of the invention provides a fusion message system, including:

a first user equipment, configured with a first client program, configured to initiate a message service request, and a public message processing unit, configured to receive a message service initiated by the first user equipment, and The content service request content is sent to the corresponding message service processing unit; the message service processing unit performs corresponding message service processing.

The beneficial effects of the embodiments of the present invention are as follows:

The embodiment of the invention provides a converged message system, which processes the message service request initiated by the terminal in a centralized manner by the common message processing unit, simplifies the use of the message service by the user, improves the experience of the message service, and facilitates the realization of the message service, and It promotes the intercommunication between message services and enables the smooth evolution of traditional messaging to converged messaging platforms, which is beneficial to protect existing investments. DRAWINGS

1 is a schematic diagram of a location of a short message system in a GSM network platform in the prior art; FIG. 2 is a schematic diagram of a standard architecture of an MMS system in the prior art;

3 is a schematic diagram of an architecture of an IM system based on the SIPLE protocol defined by the OMA in the prior art; FIG. 4 is a network structure diagram of the OMA PoC specification in the prior art;

FIG. 5 is a schematic diagram of an application process of an OMA PoC floor in the prior art; FIG.

6 is a schematic structural diagram of a converged message system according to an embodiment of the present invention;

7 and FIG. 8 are schematic structural diagrams of a common message processing unit according to an embodiment of the present invention;

9 and FIG. 10 are schematic diagrams showing the structure of a message service processing unit according to an embodiment of the present invention; FIG. 11 and FIG. 12 are schematic diagrams showing the structure of a message service interworking unit according to an embodiment of the present invention; FIG. 13 is a message service interworking unit according to an embodiment of the present invention; A schematic diagram of a network structure for performing interworking between an IM service and an email service;

Figure 14 is a schematic structural view of Embodiment 1 of the present invention;

Figure 15 is a schematic structural view of Embodiment 2 of the present invention;

Figure 16 is a schematic structural view of Embodiment 3 of the present invention;

Figure 17 is a schematic structural view of Embodiment 4 of the present invention;

Figure 18 is a schematic structural view of Embodiment 5 of the present invention;

Figure 19 is a schematic flowchart of Embodiment 5 of the present invention;

Figure 20 is a schematic structural view of Embodiment 6 of the present invention; 21 is a schematic flowchart of Embodiment 6 of the present invention;

Figure 22 is a schematic flow chart of an embodiment of the present invention. detailed description

The specific embodiments of the present invention are described below in conjunction with the accompanying drawings.

As shown in FIG. 6, the fusion message system of the present invention mainly includes:

The user equipment 10 is installed with a client program for initiating a message service request.

The client program can be based on a mobile device, such as a mobile phone PDA (Personal Digital Assistant), etc.; it can also be based on a personal computer or a business application server. For the mobile device-based implementation, the implementation can be implemented in a soft and hardware customized manner: that is, the software and hardware programs of a certain function are solidified in the mobile terminal, and the function of the fusion message client is provided. It can also be implemented in pure software: it provides software based on a specific mobile operating system, and then provides the integrated messaging client function on the mobile terminal by installing or loading. This method is common based on Kjava, Brew platform, or software programs based on Symbians, WinCE operating system. These program installation/upgrades are easier to update and uninstall. Because it is a pure software implementation, the performance aspect will be slightly lower than the customization method.

From the function of the client software, mainly through related protocols (such as: real-time transport protocol / real-time transport control protocol / reliable multicast transport protocol I XML configuration access protocol (SIP / SDP / RTP RTCP / RMTP / XCAP)) The service signaling and media are sent and received to implement the corresponding business logic of the converged message service, such as: client state machine for converging message service, related protocol function, user interface, user operation function, and the like. '

The user equipment may also be an independent service server. The service server sends a message service request to the converged message platform through a specific interface protocol, and the application sends or receives a message to the converged message platform. This scenario is most common when SPs (service providers) perform business interactions with telecom operators, where the service servers are attributed to the server provider.

The purpose of the converged message service is to facilitate the user's business practicality and improve the business experience. Therefore, some interfaces of the original message service are integrated and integrated in the interface. Typically, the user can see a list of users and groups. After selecting a user or group object, you can choose the right one. The method initiates a service, for example, a short message mode, an instant message mode, a PoC service mode, and the like. It is also possible to input only the content that needs to be sent after selecting a user or group object, and the method of sending is determined by the client and the server. For example: When a user sends a picture and text, the client or server sends it by means of a multimedia multimedia message. When the user sends a video clip, it is sent by instant message. The basis for the client or server to determine the manner in which the message content is sent may be set by the user, or may be a policy set by the operator, or may be specified by the business logic.

To put it simply, the existing messaging system uses a certain message delivery method. The type of client program is enabled when the user wants to send the type, and the user is required to be familiar with the sending capabilities and characteristics of various services. The feature of the converged messaging service is the ability to combine various messaging services to deliver the message content to the recipient in the most appropriate manner for the sole purpose. Converged messages can not require users to have a deep understanding of various types of messaging services. The goal is that users only need to know: Who can send what content. Of course, the user is also allowed to specify to use the service in some way.

The public message processing unit 20 is configured to receive the message service initiated by the user equipment 10, and send the message service request to the corresponding message service processing unit 30 according to the content of the message service request;

The message service processing unit 30 performs corresponding message service processing.

In the above architecture, the public message processing unit 20 is configured to perform centralized processing on the message service request initiated by the user equipment. As shown in FIG. 7, the public message processing unit 20 may further include:

The message parsing unit 201: parsing the received message, removing the message header, and transferring the message body content to the message pre-processing unit 202 and the message scheduling management unit 203;

The message pre-processing unit 202: performs some common processing according to the content of the message body, where the processing includes the ability to invoke the common service component to manage the message, the session, and the user. For example, querying user information data, performing user authentication, assigning session identifiers and performing session association, and issuing updated Presence status;

Here, the processing according to the content of the message body is as follows: If the user's request requires the establishment of a session type message interaction, a new session is established, and the context information of the session is set, such as: The sender ID/recipient ID, the media type supported by the session, etc., prepare for the processing of subsequent messages. See the policy processing unit according to the processing of the policy processing unit.

The message scheduling management unit 203: forwards the message to the message service processing subsystem or the message service interworking subsystem according to the content of the message body, such as the message request type.

Further, as shown in FIG. 8, the common message processing unit 20 includes one or a combination of the following units:

The session management unit 204 is configured to provide a session management function to various types of message services. For example, if a CM user A initiates an IM chat to the CM user B, the session management unit 204 creates a corresponding session, and then, through the unit, the fused message system The context management of the A and B sessions is performed. When the chats of A and B are finished, the corresponding session is deleted.

The presentation management unit 205 is configured to provide a presentation state management of the user. Through the presentation function, the user can understand the online status of other users and enhance the service experience.

The database 206 is configured to provide unified database storage support, such as storing user subscription information, storing user personalized setting information, user message routing information, and the like;

The group management unit 207 is configured to manage a group that the user joins, and the user can create/modify a group, and perform group chat or group sending in the message service;

The contact management unit 208 is configured to maintain a contact list of the user, and the user can maintain a contact list of the user. The contact list on the network can be downloaded to the terminal regardless of the terminal, so that the contact is selected. Send a message or initiate a conversation;

The network storage unit 209 is configured to provide a function for saving various types of history messages to the user. In the solution of the present invention, the user may have multiple types of messages, and the unit provides the user with the function of saving various types of historical messages. Users can delete and download these historical messages;

The service providing and self-service management unit 210 is configured to provide a self-service management function to the user, and may provide a web-based service, such as performing personalized setting of the converged message service, modifying/deleting the history message, modifying the group information, and modifying the contact information. and many more.

The above self-management features include:

Users set their own business preferences through the functions provided by the system; and/or The user operates the messages or media in the network storage unit according to the functions provided by the system; and/or the user manages their contact list and/or group information according to the functions provided by the system.

These units provide functions independently, and these units can be integrated into the common message processing subsystem or can be independent functional entities outside the CMS.

In the above architecture, the message service processing unit 30 may be further refined. As shown in FIG. 9, the method may include:

The internal message service processing unit 301 processes the internal message service;

The message service interworking unit 302 is connected to the external message service processing unit and configured to process the external message service.

In the above architecture, as shown in FIG. 10, the internal message service processing unit 301 may further include the following contents:

The MMS implementation unit 3011 is configured to implement a multimedia message service.

The PoC implementation unit 3012 is configured to implement a PoC service.

The IM implementation unit 3013 is configured to implement an IM service.

The short message implementation unit 3014 is configured to implement a short message service.

The IP-based short message implementation unit 3015 is configured to implement an IP-based short message service.

The specific settings of the internal message service processing unit 301 can be selected according to system requirements, and each of the foregoing implementation units can be conveniently superimposed as a sub-module of the internal message service processing unit 301.

In the above framework, as shown in FIG. 11, the message service interworking unit 302 further includes: a format conversion unit 3021, configured to format and send the message service request to the external message system.

The message service interworking unit 302 can further perform the setting as shown in FIG. 12: The first message service interworking module 3022 is connected to the external message service system 1 to complete the interworking of the first message service;

The second message service interworking module 3023 is connected to the external message service system 2 to complete interworking of the second message service. Further, the message service interworking unit 302 and the external message system may adopt a unified interface. In this case, the interworking interface 1 and the interworking interface 2 adopt the same interface protocol. This solution simplifies the external interface of the message service interworking unit 302. When the externally interconnected message system is added, the interface protocol with the message service interworking unit 302 need not be modified.

As shown in FIG. 13, the message service interworking unit performs the setting of the IM service and the email service interworking. The IM service interworking module and the email service interworking module are set in the figure, and are respectively connected to the external IM message system and the email message system to complete the above two. Interoperability of business.

In the above solution, the main three parts are: a public message processing unit 20, an internal message service processing unit 301, and a message service interworking unit 302. The three can be flexibly set, and can be set in the same server or separately. Set in different servers, the specific settings can be determined according to needs.

In the foregoing solution, the communication between the user equipments 10 may be completed by the same message service system, or may be completed by different message service systems. When completed by different message service systems, the terminal devices may have the same Function, you can also only have the work required by the user.

The following description will be made in conjunction with several practical applications of the solution of the present invention.

example 1

As shown in FIG. 14, it is a schematic structural diagram of the first embodiment. In the first example, the public message processing unit 20, the internal message service processing unit 301, and the message service interworking unit 302 are disposed in a server, which may be referred to as a converged message server (CMS). In the first example, the CMS becomes the processing center of the fused message. It can process some message service requests independently, and can communicate with external messages through the message service interworking subsystem. For the message service that the CMS can process independently, it is called the internal message service of the CMS. The message service can be an existing message service, such as IM, PoC, MMS, SMS, etc., or it can be a newly generated message service in the future. .

The message service interworking unit 302 has two main functions:

1. Through the message service interworking unit 302, the CMS can send a message service request that is not supported by the CMS to an external corresponding message system for processing, and implement the message service indirectly. For example, CMS does not To support SMS, the CMS sends the SMS service request of UE1 to the external short message system and processes it to the short message system.

2. The CMS implements interworking with the external message service system through the message service interworking unit 302. For example, the CMS supports internal IM services and wants to communicate with external IM services. In this case, the interworking service unit 302 needs to communicate with the external IM message service.

The entities in Example 1 are described as follows:

(1) CMS: Supports converged messaging services. Converged messaging users can send and receive various types of messages through the CMS. Through CMS, not only can CM users exchange messages, but also CM users and non-CM users can exchange messages. In Example 1, the CMS mainly consists of three parts:

The public message processing unit 20 is responsible for uniformly processing the message request of the UE1, and directly transmitting and receiving the CM message with the UE1. Upon receiving the request from the CMC, the CMS determines that if the message service within the CMS is requested, the request is sent to the internal message service processing unit 301 for processing, and if the external message service is requested, it is sent to the message service interworking unit 302 for processing. . In this way, direct message service processing or intercommunication with external systems is realized. Internal message service processing unit 301.· Responsible for the implementation of specific message services, such as implementing IM service teasing.

The message service interworking unit 302: is responsible for implementing interworking with an external message system.

(2) External message system: A message service providing system located outside the CMS, for example, may be a conventional SMS short message center, an MMS message system, a PoC server, a server in a mobile/fixed network, an Email server, and the like.

(3) UE1 (CMC): A user terminal supporting a converged message, which may be a mobile terminal or a fixed terminal, and capable of interacting with a CMS to use a converged message service. For example, UE1 sends a message to the ordinary short message user UE2 by sending a message to the CMS. In addition to supporting converged messages, UE1 can also support normal messaging services.

(4) UE2 (supports traditional message service): A client that supports a certain type or a certain type of message service, which may be a mobile terminal or a fixed terminal. Such user terminals are connected to a specific external messaging system to perform corresponding message services. For example, UE2 is an ordinary mobile terminal that supports the short message industry. The external message system is the short message system; the UE2 interacts with the short message system to send and receive short messages.

In general, the CMS is equal to the internal messaging service system plus the messaging service interworking gateway. The external function embodied is that CMS can handle many types of messaging services. As a CMS user, it is not necessary to know which network entity the message service is processed by. He simply needs to tell the CMS the content of the message to be sent and the recipient of the message, and the rest of the work is handled by the CMS.

Example 2

In the solution of the first embodiment, the message service interworking unit 302 can be located inside the converged message platform, and can also be independent from the converged message platform in the actual application, and is located outside the converged message platform. As shown in Fig. 15, in the example 2, the message service interworking unit 302 is set outside the converged message server, and the rest is set in the same manner as in the example 1, so that the same effect can be achieved.

Example 3

In the solutions of the first and second embodiments, an internal message service processing unit 301 is provided, which is based on the solution that the internal message service processing unit performs internal message processing by the fusion message system, and may actually not set internal message service processing. Unit 301, both of which complete the message service through external messaging system resources. As shown in Fig. 16, it is a schematic diagram of such a scheme. In the fused message server accessed by the UE1 in the example 3, only the public message processing unit 20 and the message service interworking unit 302 are set, and the message service processing unit that implements the message service is not set, and the functional units of the message service are specifically implemented. Utilize the message service processing unit in the existing external system.

Example 4

In the previous three scenarios, the external messaging system is utilized to enrich and supplement the message service. If there is no external message system and only the internal resources of the fused message system are used, the scheme shown in Figure 17 is used. The solution only sets the public message processing unit 20 and the internal message service processing unit 301. Such a scheme is suitable for the development of the converged message system to a relatively mature stage. The converged message system can provide all the message services independently, and the message service interworking unit is unnecessary. . Of course, the interaction between the converged messaging systems still exists, and that is not an interaction between different converged messaging systems.

Example 5 As shown in FIG. 18, it is a networking diagram of the fusion message system of the present invention in practical applications, in which the converged message system appears in the form of a converged message server (CMS). According to the above-described converged message service system, the CMS can provide message communication between two converged message users. CMS-A and CMS-B are respectively two converged message servers, which respectively process the converged message services of the respective home users. CMC-1 and CMC-2 are two converged message client user devices, respectively belonging to CMS-A and CMS-B, which conduct converged message communication through the mobile network.

As shown in Figure 19, the two converged message user communication processes include the following steps:

Step 1901: The CMC-1 sends a message sending request to the CMS-AJ!, and carries the message content to be sent in the request. According to the capabilities of CMC-1 and CMS-A, the message content can be text, multimedia pictures, video clips, etc.

Step 1902: After receiving the request, the CMS-A performs judgment processing, and mainly includes: determining whether the CMC-1 has a message initiation permission, checking whether the message receiver is a local user, and if not, querying the address of the home server.

Step 1903: The CMS-A forwards the message to the CMS-B where the receiver is located.

Step 1904: After receiving the request, the CMS-B performs a judgment process, which mainly includes: determining whether the CMC-2 is in the service activation, and if not in the service activation state (for example, shutting down), saving the message in the CMS-B. For example, if the storage is saved in the SMC user, if it is not online, it is determined whether the CMC-2 masks the CMC-1 message, and whether the CMC-2 terminal has the ability to receive the media content.

Step 1905: The CMS-B sends a message to the CMC-2.

Step 1906: The CMC-2 sends an acknowledgement message to the CMS-B.

Step 1907: The CMS-B sends a confirmation message.

Step 1908: The CMS-A sends a confirmation message.

Example 6

In Example 6, the message communication between the user of the messaging system and the user of the traditional messaging system (CMC is sent to the traditional message user), in which the converged message system appears in the form of a converged message server (CMS). According to the above-described converged message service system, the CMS can provide message communication between the converged message user and the legacy message user. Here, the message communication between the converged message user and the short message user is For example, as shown in FIG. 20, the CMS-A is a converged message server, which is responsible for processing the converged message service of its home subscriber. The SMC is a short message center and is responsible for processing the short message service. The CMC-1 and the SMS UE are respectively a converged message client and a normal short message terminal, which are respectively belonged to the CMS-A and the SMC, and they communicate through the mobile network. As shown in Figure 21, it mainly includes the following steps:

Step 2101: The CMC-1 sends a message sending request to the CMS-A, where the content of the message to be sent is carried in the request. According to the capabilities of CMC-1 and CMS-A, the message content can be text, multimedia pictures, video clips, etc.

Step 2102: After receiving the request, the CMS-A performs a judgment process, and according to the instruction in the request message, the CMC-1 wants to send a short message to the called party.

Step 2103: The CMS-A forwards the short message to the traditional short message system through the SMS-IWMSC. Step 2104 - Step 2107: Process the existing short message processing, which is omitted here.

Step 2108 - Step 2109: Return a confirmation message.

Example 7

Example 7 is a message communication between a converged message user and a traditional message user (a traditional message user sends it to the CMC), and its network structure diagram can be set as in FIG. As shown in Figure 22, the main steps are as follows:

Step 2201: The traditional SMS user sends a short message to the converged message user CMC-1 through the short message center SMC.

Step 2202: The SMC forwards the message to the GMSC.

Step 2203: The GMSC queries the called information through the HSS, and the called party registers the fused message service, and sets the fused message as the preferred message receiving mode, and forwards the short message to the CMS-1 according to the routing information obtained by the query.

Step 2204: The CMS-1 converts the received short message format into a format of the fused message and sends it to the CMC-1.

Step 2205 - Step 2208: Return a confirmation message.

The invention provides an implementation method of a converged message system and a corresponding system architecture. It simplifies the use of message services by users, improves the experience of message services, and simplifies the implementation of message services. It simplifies the interworking between message services and enables the smooth evolution of traditional messaging to converged messaging platforms, which is beneficial to protect existing investments. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Rights request

A converged message system, comprising:

a first user equipment, configured with a first client program, configured to initiate a message service request; a public message processing unit, configured to receive a message service initiated by the first user equipment, and send a message service request to the message service request content according to the message service request content Corresponding message service processing unit;

The message service processing unit performs corresponding message service processing.

The system according to claim 1, wherein the message service processing unit comprises: an internal message service processing unit that processes the internal message service;

The message service interworking unit is connected to the external message service processing unit and is configured to process the external message service.

The system according to claim 1, wherein the public message processing unit comprises: a message parsing unit, configured to parse the received message, and obtain the body content of the message;

The message preprocessing unit performs public processing according to the content of the message body;

The message scheduling management unit routes the message service request to the corresponding message service processing unit according to the content of the message body.

4. The system of claim 3, wherein the common message processing unit further comprises one or a combination of the following:

a session management unit, configured to provide a session management function;

a presentation management unit, configured to provide presentation state management of the user;

Database, used to provide unified database storage support;

a group management unit, configured to manage a group to which the user joins;

a contact management unit for the user to maintain a contact list thereof;

A network storage unit, configured to provide a user with a function of storing various types of historical messages and media content; a service providing and self-service management unit for providing self-service management functions to the user.

The system according to claim 2, wherein the message service interworking unit comprises: a format conversion unit, configured to format and send a message service request to an external message system System.

The system according to claim 2, wherein when the message service interworking unit is connected to the external message service processing unit:

Use different interfaces with different external messaging service processing units, or

Use a uniform interface with all external messaging business processing units.

7. The system of claim 2, wherein the internal message service processing unit comprises one or a combination of the following:

An MMS implementation unit, configured to implement a multimedia message service;

a PoC implementation unit, configured to implement a PoC service;

An IM implementation unit for implementing an IM service;

a short message implementation unit, configured to implement a short message service;

An IP-based short message implementation unit for implementing IP-based short message service.

The system according to claim 2 or 3, wherein the public message processing unit, the internal message service processing subunit, and the message service interworking unit may be located in the same server or in different servers.

The system according to claim 1 or 2, wherein the public message processing unit and the message service processing unit are located on the same server or on different servers.

The system of claim 1, 2 or 3, further comprising a second user equipment, installed with a second client program, configured to initiate a message service request, the first user equipment and the The two user devices may be the same or different.

The system according to claim 2, wherein the internal message processing unit and/or the message service interworking unit can be set to be multiple.

12. The system of claim 1, 2 or 3, wherein the first user equipment is a mobile terminal, or a personal computer, or a business application server.