WO2008043261A1 - Système de messagerie convergent - Google Patents

Système de messagerie convergent Download PDF

Info

Publication number
WO2008043261A1
WO2008043261A1 PCT/CN2007/002831 CN2007002831W WO2008043261A1 WO 2008043261 A1 WO2008043261 A1 WO 2008043261A1 CN 2007002831 W CN2007002831 W CN 2007002831W WO 2008043261 A1 WO2008043261 A1 WO 2008043261A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
message service
user
unit
service
Prior art date
Application number
PCT/CN2007/002831
Other languages
English (en)
Chinese (zh)
Inventor
Liming Zhang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008043261A1 publication Critical patent/WO2008043261A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the present invention relates to the field of communications, and in particular, to a converged message system. Background technique
  • SMS Short Message Service
  • IM instant messaging
  • POC cluster services
  • 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).
  • CPs content providers
  • service providers CPs and service providers.
  • SMS 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.
  • GPRS General Packet Radio Service
  • GSM Global System for Mobile Communications
  • 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.
  • SMC Short Message Center
  • PSTN public switched telephone network
  • ISDN Service Digital Network
  • PSPDN Public Packet Switched Data Network
  • 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).
  • MSC Mobile Switch Center
  • VLR Visitor Location Register
  • Home home location register
  • 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.
  • BSS Base Station Subsystem
  • the MSC 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.
  • SMS Short Message Service Center
  • 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;
  • 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.
  • Multimedia Messaging Service 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.
  • FIG. 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 Relay MMS Relay
  • MMS Server MMS Server
  • User Database User Database
  • MMS User Agent User Agent
  • 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.
  • CDR charging data
  • 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 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 Wireless Application Protocol
  • 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.
  • WSP Wireless Session Protocol
  • 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.
  • MIME Multipurpose Internet Mail Extensions
  • 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;
  • the system After confirming the processing method, the system passes the called user's mobile user international ISDN
  • MSISDN MMS-Relay
  • WAP gateway WAP gateway
  • 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.
  • IM comes with presence capability. Pres is the key enabling technology of IM.
  • the Presence attribute is personal, the user can control the permissions according to their own wishes.
  • 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.
  • 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.
  • 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).
  • IMS IP Multimedia Subsystem
  • PoC Server is the main call control device of the service, and is an Application Server of the IMS network;
  • 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.
  • 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.
  • TBCP Talk Burst Control Protocol
  • the Talk Burst can be forwarded by the PoC Server to other members of the group.
  • 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.
  • 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
  • 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.
  • these different messaging services have their own implementation systems and interface specifications, and the maintenance costs and interworking costs are high.
  • 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 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 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.
  • FIG. 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
  • FIG. 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.
  • FIG. 7 and FIG. 8 are schematic structural diagrams of a common message processing unit according to an embodiment of the present invention.
  • FIG. 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
  • 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.
  • FIG. 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the terminal devices 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 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).
  • 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.
  • 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:
  • 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.
  • 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.
  • the CMS implements interworking with the external message service system through the message service interworking unit 302.
  • the CMS supports internal IM services and wants to communicate with external IM services.
  • the interworking service unit 302 needs to communicate with the external IM message service.
  • Example 1 The entities in Example 1 are described as follows:
  • 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.
  • 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.
  • a message service providing system located outside the CMS 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.
  • UE1 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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 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).
  • CMS can provide message communication between the converged message user and the legacy message user.
  • the message communication between the converged message user and the short message user is
  • 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.
  • 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.
  • 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 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système de messagerie convergent comprenant : un premier équipement utilisateur sur lequel est installé un premier programme client et qui est utilisé pour lancer une demande de service de messagerie; une unité de traitement de messages commune (20) destinée à recevoir le service de messagerie lancé par le premier équipement utilisateur et transmettre la demande de service de messagerie à une unité de traitement de service de messagerie (30) correspondante d'après le contenu de la demande de service de messagerie; ainsi qu'une unité de traitement de service de messagerie (30) destinée à traiter le service de messagerie correspondant.
PCT/CN2007/002831 2006-09-29 2007-09-27 Système de messagerie convergent WO2008043261A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610140662.4 2006-09-29
CN2006101406624A CN101155329B (zh) 2006-09-29 2006-09-29 一种融合消息系统

Publications (1)

Publication Number Publication Date
WO2008043261A1 true WO2008043261A1 (fr) 2008-04-17

Family

ID=39256707

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002831 WO2008043261A1 (fr) 2006-09-29 2007-09-27 Système de messagerie convergent

Country Status (2)

Country Link
CN (1) CN101155329B (fr)
WO (1) WO2008043261A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291693A (zh) * 2011-08-24 2011-12-21 中兴通讯股份有限公司 一种基于终端的融合消息业务实现方法及装置
CN103763332A (zh) * 2014-02-19 2014-04-30 广东天波信息技术股份有限公司 一种媒体流转发方式动态切换的方法和系统

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101498731B1 (ko) * 2008-02-13 2015-03-05 삼성전자주식회사 비통합 메시징 서비스와 인터워킹하기 위해 통합 메시징 서비스를 제공하는 서버 및 방법 및 이를 위한 시스템
CN101572714B (zh) * 2009-05-23 2012-11-21 华为终端有限公司 一种内容审核的方法、设备及系统
CN101998302B (zh) * 2009-08-10 2014-07-16 中兴通讯股份有限公司 消息发送方法、装置、系统及用于融合业务系统的pf、cf和isf
CN102006564B (zh) * 2009-09-03 2014-08-13 中兴通讯股份有限公司 消息互通方法及融合业务系统
CN101964961A (zh) * 2010-05-20 2011-02-02 宇龙计算机通信科技(深圳)有限公司 一种移动终端的公告发布、接收方法、系统及移动终端
CN102571636A (zh) * 2011-11-24 2012-07-11 中兴通讯股份有限公司 一种基于开放业务发布平台的消息通信方法及系统
CN102546471A (zh) * 2011-12-31 2012-07-04 深圳中兴网信科技有限公司 一种服务商旅全过程的消息发送方法
CN103368821A (zh) * 2012-04-10 2013-10-23 中兴通讯股份有限公司 发送语音消息的方法及系统、融合消息服务器及客户端
CN103596135A (zh) * 2012-08-16 2014-02-19 中国电信股份有限公司 实现消息推送的方法和通用消息平台
EP3503469B1 (fr) * 2012-09-21 2021-03-03 Huawei Technologies Co., Ltd. Procédé de transmission de message commun et dispositif
CN102970208B (zh) * 2012-10-29 2016-08-03 华为终端有限公司 应用信息处理方法和终端设备
CN104104532B (zh) * 2013-04-07 2017-06-16 浙江大华技术股份有限公司 一种信息处理方法、装置及系统
CN104753877B (zh) * 2013-12-30 2017-12-22 中国移动通信集团公司 一种群组通信方法及装置
CN105743766B (zh) * 2014-12-10 2018-11-23 中国移动通信集团公司 一种群组通信方法及装置
CN105812229A (zh) * 2014-12-30 2016-07-27 中国移动通信集团公司 一种终端通信方法、系统及相关装置
CN104837124B (zh) * 2015-05-04 2018-10-12 南京邮电大学 一种sip网络与集群系统和电信网络短信互通的方法和系统
CN106506316A (zh) * 2015-09-06 2017-03-15 中兴通讯股份有限公司 信息传输方法和装置
WO2018086123A1 (fr) * 2016-11-14 2018-05-17 华为技术有限公司 Système, appareil et procédé de traitement de session
CN109120502B (zh) * 2017-06-26 2022-05-20 中兴通讯股份有限公司 用于多业务融合平台的通信方法、设备、系统及存储介质
CN113709081B (zh) * 2020-05-20 2023-06-30 南京南瑞信息通信科技有限公司 基于ims与移动互联技术的融合通讯方法和系统
CN111970650A (zh) * 2020-08-14 2020-11-20 上海三吉电子工程有限公司 一种基于移动互联网的多网融合通信平台及其应用

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1501328A2 (fr) * 2003-07-24 2005-01-26 Samsung Electronics Co., Ltd. Procédé et appareil pour la transmission et la réception d'informations de contrôle MBMS dans un système de communication mobile
CN1625276A (zh) * 2003-12-03 2005-06-08 三星电子株式会社 多区布置中的无线专网系统之间的短消息服务
CN1835450A (zh) * 2005-03-15 2006-09-20 北京航空航天大学 网格作业管理器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1501328A2 (fr) * 2003-07-24 2005-01-26 Samsung Electronics Co., Ltd. Procédé et appareil pour la transmission et la réception d'informations de contrôle MBMS dans un système de communication mobile
CN1625276A (zh) * 2003-12-03 2005-06-08 三星电子株式会社 多区布置中的无线专网系统之间的短消息服务
CN1835450A (zh) * 2005-03-15 2006-09-20 北京航空航天大学 网格作业管理器

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291693A (zh) * 2011-08-24 2011-12-21 中兴通讯股份有限公司 一种基于终端的融合消息业务实现方法及装置
CN103763332A (zh) * 2014-02-19 2014-04-30 广东天波信息技术股份有限公司 一种媒体流转发方式动态切换的方法和系统
CN103763332B (zh) * 2014-02-19 2017-07-28 广东天波信息技术股份有限公司 一种媒体流转发方式动态切换的方法和系统

Also Published As

Publication number Publication date
CN101155329A (zh) 2008-04-02
CN101155329B (zh) 2010-11-10

Similar Documents

Publication Publication Date Title
WO2008043261A1 (fr) Système de messagerie convergent
US7107017B2 (en) System and method for providing support services in push to talk communication platforms
EP2124399B1 (fr) Procédé, dispositif et système pour la mise en convergence d'une messagerie sur ip
EP1958467B1 (fr) Procede pour l'activation de service combinatoire et reseau de communication de mise en oeuvre du service
US8670760B2 (en) Converged mobile-web communications solution
US9906603B2 (en) System and method for transferring a session between multiple clients
US20130310089A1 (en) Voice texting over sms
US20080207233A1 (en) Method and System For Centralized Storage of Media and for Communication of Such Media Activated By Real-Time Messaging
US20080096592A1 (en) Systems and Methods for Providing Communications Services Using Assigned Codes
WO2008003255A1 (fr) Procédé de personnalisation de pseudonyme dans un message, et appareil, serveur de message et terminal associés
EP2058991A1 (fr) Procédé, système et appareil destinés à mettre en uvre l'interfonctionnement de messages
WO2007033549A1 (fr) Procede de transmission de message hors ligne
CN103023868B (zh) 用于发送寻呼模式消息的方法和设备
WO2007056928A1 (fr) Procede et systeme d'adaptation pour terminal de messagerie mobile
US9325851B2 (en) Method and apparatus for enabling communications between users
CN101083535B (zh) 群组业务中实现个性化服务的方法及其系统
EP2301225B1 (fr) Procédés, noeud de télécommunication et équipement utilisateur pour la transmission d'un identifiant d'utilisateur
WO2009043280A1 (fr) Procédé, équipement et système pour identifier un type de service et établir un service selon l'identifiant
KR100727762B1 (ko) 광대역 코드분할다중접속 네트워크를 통해 전송되는 단문메시지(ｓｍｓ)를 장식하는 방법 및 시스템
WO2008125058A1 (fr) Procédé, système et appareil destinés à déterminer une passerelle de routage
KR20030021771A (ko) 이동통신단말기를 이용한 채팅방법
WO2019037007A1 (fr) Procédé d'envoi de message et terminal
WO2007016873A1 (fr) Procede et systeme de transmission d'informations jointes dans un systeme de communication
WO2008051778A2 (fr) Systèmes et procédés pour fournir des services de communications au moyen de codes attribués
WO2007028316A1 (fr) Procede de realisation de service d'individualisation en service de groupe, systeme et serveur d'application de services

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07816445

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07816445

Country of ref document: EP

Kind code of ref document: A1