WO2008052476A1 - Procédé de gestion de conversation, client de message universel et serveur de message universel associés - Google Patents

Procédé de gestion de conversation, client de message universel et serveur de message universel associés Download PDF

Info

Publication number
WO2008052476A1
WO2008052476A1 PCT/CN2007/070981 CN2007070981W WO2008052476A1 WO 2008052476 A1 WO2008052476 A1 WO 2008052476A1 CN 2007070981 W CN2007070981 W CN 2007070981W WO 2008052476 A1 WO2008052476 A1 WO 2008052476A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
message
identifier
primary
universal
Prior art date
Application number
PCT/CN2007/070981
Other languages
English (en)
Chinese (zh)
Inventor
Rui Wang
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 WO2008052476A1 publication Critical patent/WO2008052476A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]

Definitions

  • the present invention relates to the field of wireless communications, and more particularly to a technique for managing sessions in a general messaging system.
  • the general message system consists of two parts: the client and the server.
  • the client exists in the terminal, and the server is set in the network.
  • the terminal may be a wireless mobile terminal (such as a mobile phone) or a fixed terminal (such as a PC), which is a device that can access the IP network.
  • the network is an IP-based network.
  • the terminal and the network can be separated by a variety of intermediate networks, such as wireless mobile networks, or intranets, or home LANs.
  • Dedicated messaging clients and dedicated messaging system servers are existing or future dedicated messaging service entities, such as SMS (SMS) clients and SMS servers, or instant messaging (IM) clients and IM servers.
  • the universal message client transmits the content of the message and the address of the recipient and the sender to the dedicated message client, and a dedicated message is generated by the dedicated message client, and then the message is sent by the general message client. After the general message encapsulation, the general message generation is completed.
  • the universal message client When the universal message client receives a general message, it removes the general message from the general message encapsulation, and then sends the dedicated message inside the package to the dedicated message client for parsing, and the dedicated message client returns the message content and the sender address. To the general message client, displayed to the user by the generic message client.
  • the universal message terminal completes communication with each other through a general message server.
  • a generic message server receives a generic message, it has two ways to process the message before forwarding it. One After receiving the message, the processing is completed and directly forwarded to the receiving end. Second, after receiving the message, the message delivery unit sends the message to the dedicated message system server, and the dedicated message system server completes the processing of the dedicated message and then returns to the general message server, and the general message server sends the message to the receiving end.
  • the universal message system supports the universal message terminal to replace the terminal or the new terminal to join the session during the session, and the universal message user sends the communication mode of the replaced terminal to the communication partner through the server before or after the terminal is replaced, so as to implement the communication.
  • the user after the terminal is replaced, the user cannot selectively continue the existing communication, and there is no historical record of the past communication.
  • the existing communication cannot be obtained. History records choose to talk to existing parties.
  • the present invention provides a general message server, a general message client, and a method for managing a session, so that a new terminal joins a session or a user can select an inherited session and an aborted session during the process of replacing the terminal, and Provide session records for newly added terminals or replaced terminals.
  • the present invention provides a management session method, including: a method for managing a session, including:
  • Generating a primary session identifier for the current session storing a session record containing the primary session identifier; receiving a session request message, finding a primary session identifier in the session record, and establishing a session of the correspondent party corresponding to the primary session identifier.
  • a general-purpose messaging client including:
  • a session identifier management module configured to generate a primary session identifier of the communication parties, and store the session identifier record
  • a message identifier management module configured to generate a message identifier corresponding to the master session identifier during a session of the communication partner, and store the message identifier;
  • the external communication module is configured to perform transmission of session identification records with the general message server.
  • a general-purpose message server which mainly includes:
  • a session identifier management module configured to generate a primary session identifier of the communication parties, and store the session identifier record
  • a message identifier management module configured to generate a correspondence corresponding to the primary session identifier during a session of the communication partner The message is identified and stored;
  • the external communication module is configured to perform transmission of session identification records with the general message client.
  • the implementation of the present invention has the following beneficial effects:
  • a communication party initiates a session, by establishing a primary session identifier for the communication parties, a message identifier is generated along with each message during the session of the communication parties, and the primary session identifier is simultaneously stored on the client and the server of the universal message system.
  • the session identifier record and the message identifier of each message enable a session of the communication parties to be established by acquiring and selecting the master session identifier when a new terminal joins the session or replaces the terminal.
  • 1 is a schematic structural diagram of an existing general message system
  • FIG. 2 is a schematic structural diagram of an embodiment of a general message client of the present invention.
  • FIG. 3 is a schematic structural diagram of an embodiment of a general message server of the present invention.
  • FIG. 4 is a flow chart of a method of generating a primary session identifier of the present invention.
  • FIG. 5 is a flow chart of a method for generating a second embodiment of a primary session identifier of the present invention
  • FIG. 6 is a schematic flowchart of a first embodiment of a method for transmitting a message identifier by a client and a server according to the present invention
  • FIG. 7 is a schematic flowchart of a second embodiment of a method for transmitting a message identifier by a client and a server according to the present invention
  • FIG. 8 is a schematic flowchart of a method for the first and second embodiments of the management session of the present invention
  • FIG. 9 is a schematic flowchart of a method for the third embodiment of the management session of the present invention.
  • An embodiment of the present invention resides in marking a message in a session of a communication party by using a message identifier, storing the message identifier in a server and a client of the universal message system, and simultaneously storing the session identifier record by the server and the client, so that a new terminal joins
  • a session or a user changing a terminal during a session a continuous session and an aborted session can be selected, and a session record is provided.
  • FIG. 2 it is a schematic structural diagram of a general message client embodiment of the present invention.
  • the universal message client 1 specifically includes: a message processing unit 10, an external communication unit 11, a message display unit 12, a message content acquisition unit 13, a message delivery unit 14, and a communication.
  • the message processing unit 10 of the present invention further includes:
  • the session identifier management module 100 is configured to generate a primary session identifier of the communication parties, and store the session identification record.
  • the message identifier management module 101 is configured to generate a message identifier corresponding to the primary session identifier during a session of the communication partner, and store the message identifier;
  • the session identifier management module 100 includes:
  • a primary session identifier generating submodule 1000 configured to generate a primary session identifier between the client of the universal messaging system when the client initiates a session to the communication partner;
  • the session identifier record 1001 is used to record the content of the main session identifier of the communication party generated by the master session identifier generation submodule 1000, and the content thereof is as shown in Table 1:
  • the message identifier management module 101 includes:
  • the message identifier generation submodule 1010 is configured to: when the client of the universal message system sends each message to the server, generate a message identifier;
  • the message identifier storage sub-module 1011 is configured to store a message identifier of each message in the session of the communication party, and the content thereof is as shown in Table 2:
  • the primary session identifier is used to distinguish the session, such as: Bob and Alice have one session, and Mary has another session, and the two sessions must use different primary session identifiers;
  • the current serial number is used to distinguish the sequence of the current session, which is incremented as the number of times the message is sent during the session. This value can have an upper limit, and when the serial number counts to the maximum value, it is incremented again to the minimum value. If the primary session serial number is 8 bits, when the count reaches 255, the next message sequence number is set to 0; the session message type is used to indicate the message type used by the session; The message identifier may also contain time information indicating when the message identifier was generated or sent.
  • the external communication unit 11 of the present invention is used for communication with a general message server, and specifically includes:
  • the external communication unit 11 sends the primary session identifier to the general message server through the message identifier;
  • the external communication unit 11 When the primary session identifiers of the two communication parties are established by the general message server, the external communication unit 11 first initiates a primary session identification establishment request message to the general message server, and receives the returned session identification record from the general message server;
  • the external communication unit 11 as the universal message client before the replacement is used to send the communication address information of the replaced dedicated message terminal to the universal message server;
  • its external communication unit 11 is configured to send a login request message to the universal message server to acquire a session identification record, receive a login response message from the universal message server, and send a session to the universal message server. Update the message and receive the returned session ID.
  • session identifier management module 100 and the message identifier management module 101 of the universal message client of the present invention may also be directly connected to the message processing unit 10, and the functions thereof are the same as those described above.
  • FIG. 3 is a schematic structural diagram of an embodiment of a general message server according to the present invention.
  • the universal message server 2 provided by the present invention comprises: a message processing unit 20, an external communication unit
  • the message processing unit 20 of the present invention specifically includes:
  • the session identifier management module 200 is configured to generate a primary session identifier of the communication parties, and store the session identification record.
  • the message identifier management module 201 is configured to generate a message identifier corresponding to the primary session identifier during a session of the communication partner, and store the message identifier.
  • the session identifier management module 200 includes:
  • the primary session identifier generating submodule 2000 is configured to generate a primary conference between the client of the dedicated messaging system and the user identity of the universal messaging system user of the communication partner when the client initiates the session to the communication partner.
  • the identifier of the voice or used to uniformly assign the primary session identifier to both parties;
  • the session identifier record 2001 is used to record the content of the main session identifier of the communication parties generated by the master session identifier generation submodule 2000, and the contents thereof are as shown in Table 3:
  • the message identifier management module 201 includes:
  • a message identifier generation submodule 2010, configured to generate a message identifier when each message is sent to the client;
  • the message identifier storage sub-module 2011 is configured to store a message identifier of each message of the communication party during the session, and the content thereof is as shown in Table 4:
  • the primary session identifier is used to distinguish the session, for example: Bob and Alice perform one session, and Mary performs another session, and the two sessions must use different primary session identifiers;
  • the current serial number is used to distinguish the sequence of the current session, which is incremented as the number of times the message is sent during the session. This value can have an upper limit and is incremented again to the minimum value when the serial number is counted to the maximum value. If the primary session serial number is 8 bits, when the count reaches 255, the next message sequence number is set to 0; the session message type is used to indicate the message type used by the session;
  • the message identifier may also contain time information indicating when the message identifier was generated or sent.
  • the communication between the external communication unit 21, 22 and the universal message client of the present invention specifically includes: when the primary session identifier of the communication parties is established by the general message client, the external communication unit of the universal message server is configured to receive the message from the general message.
  • the external communication unit When the primary session identifier of the two communication parties is established by the universal message server, the external communication unit first receives the primary session identifier establishment request message initiated by the universal message client, and returns a session identification record to the communication terminal;
  • the universal message client is replaced with a dedicated message client during the session, the external communication unit is configured to receive the communication address information of the dedicated message client sent by the universal message client, and receive the session message sent by the dedicated message client, and The session identifier record is encapsulated by a message format supported by the dedicated message client and sent to the dedicated message client that initiates the session request;
  • session identifier management module 200 and the message identifier management module 201 of the universal message server of the present invention may also be directly connected to the message processing unit 20, and the functions thereof are the same as those described above.
  • the primary session identifier is generated based on the user identity:
  • step S100 when the universal message client is ready to initiate a communication, the session identifier management module of the client generates a master session identifier based on the universal message system user identifier, and the universal message system user identifier can ensure the uniqueness of the master session identifier. .
  • step S101 the universal message client sends the primary session identifier and the message identifier together with the message content to the universal message server by using the session message as a carrier;
  • step S102 the server records the primary session identifier in its own general message session identification record table
  • step S103 if the communication partner is a general message client, the general message server notifies the communication partner of the master session identifier and the message identifier by using the session message.
  • the master session identifier may be established by the session identifier management module of the universal message server according to the user identifier of the universal message system user, and then the master session identifier is established. Pass through session messages to the general messaging system user.
  • FIG. 5 it is a flowchart of a method for generating a second embodiment of a primary session identifier of the present invention.
  • the primary session identity is uniformly assigned by the session identity management module of the server of the universal messaging system, i.e., when the generic messaging client initiates a communication, it requests the generic message server to generate a primary session identity.
  • the universal message client sends a session identification setup request message to the universal message server, where the message includes the sender username, the recipient username, or the recipient address.
  • the meaning of the above program code is: If the source user is the sender user name, and the target user is the recipient user name or the recipient address, or the target user is the sender user name, and the source user is the recipient user name or recipient. Address, then find the corresponding item, otherwise the corresponding item can not be found.
  • step S203 is performed, otherwise step S204 is performed.
  • step S203 if the server finds the corresponding item, the general message server takes out the main session identifier of the corresponding item, and then proceeds to step S205;
  • step S204 if the corresponding item is not found, the universal message server generates a primary session identifier, ensuring that the identifier is different from the other primary session identifiers. Then proceeds to step S205;
  • step S205 the universal message server returns a session identification record, including a sender user name, a recipient user name or a recipient address, and a primary session identifier;
  • the returned response message also includes the current serial number of each source user and target user pair.
  • step S206 is further performed to notify the communication partner of the master session identifier and the message identifier by using the session message as a carrier.
  • step S200 the dedicated message client sends a session message to the general message server, where the session message includes a main session for acquiring The identified address information;
  • step S205 is omitted
  • step S206 the universal message server sends the master session identifier directly to the communication partner's general message client using the session message as a carrier, and the other
  • FIG. 6 is a schematic flowchart of a first embodiment of a method for transmitting a message identifier by a client and a server according to the present invention.
  • the universal message system transmits the message identifier by using the session message as a carrier.
  • a message identifier indicating the general message system is embedded in the message header. It should be noted that the identifier includes not only the The content also contains: Subsession ID and message type.
  • the sub-session identifier is generated when the message is generated, and the number of sub-sessions is determined according to the number of times the message is decomposed, that is, a group of message content provided by the user may be carried by multiple sub-sessions.
  • step S301 the universal message client sends a session message to the universal message server.
  • step S302 the universal message server receives the session message, and the message identifier of the session message is obtained.
  • message identifier can also be sent by the general message server to the general message client.
  • FIG. 7 a schematic flowchart of a second embodiment of a method for transmitting a message identifier by a client and a server according to the present invention is shown.
  • the universal message server is not responsible for the direct reception and transmission of the user message, that is, only the signaling interaction of the general message system is completed with the client, and the message content is still sent through the dedicated message system, the client and the server. Notification of the general message system message identification by the message notification message.
  • the universal message client sends a message notification message to the universal message server;
  • the message notification message includes session information of a message, mainly: a primary session identifier, a current serial number, a sender username or a sender address, and a reception.
  • step S401 extracting a message identifier of the general message from the notification message
  • step S402 after obtaining the message identifier, the server considers that the next received message from the same user goes to the same destination, and the session message of the same message type corresponds to the message identifier.
  • message notification message may be sent by the universal message client to the universal message server, or may be sent by the universal message server to the universal message client.
  • the generic messaging client, server When the user exits the universal messaging system, the generic messaging client, server will delete the primary session identity associated with the user. If the general message system user needs to replace the terminal during the session, or a new terminal requests to join the session, there must be a terminal supporting the general message system before and after the terminal is replaced or before the new terminal joins. If there is a dedicated message terminal before and after the replacement of the terminal or before the new terminal joins, the other communication terminal must be a general message terminal, so there are four cases:
  • the terminal before the replacement or the terminal with the existing session is a universal message terminal, and the replaced terminal or the terminal newly joining the session is a universal message terminal, and the communication partner is a general message terminal;
  • the terminal before the replacement or the terminal used by the existing session is a universal message terminal, and the terminal after the replacement or the terminal newly joining the session is a universal message terminal, and the communication partner is a dedicated message terminal;
  • the terminal before the replacement or the terminal with the existing session is a dedicated message terminal, and the replaced terminal or the terminal newly joining the session is a universal message terminal, and the communication partner is a general message terminal;
  • the terminal before the replacement or the terminal with the existing session is a universal message terminal, and the replaced terminal or the terminal newly joining the session is a dedicated message terminal, and the communication partner is a general message terminal.
  • the general message terminal needs to send a login request message, complete the function of the session request message, and obtain the session record through the login response message returned by the network.
  • the user is allowed to selectively continue the previous session, and the universal message server needs the client to provide a session update message, and sends a response call record to the client. Message.
  • the technical solution of the management session provided by the present invention is different: when the terminal is replaced, the universal message server replaces the session record with The communication address of the previous terminal is updated to the communication address of the replaced terminal; and when a new terminal joins the session, the universal message server adds or modifies the session identification record and session message related to the terminal newly joining the session in its session record. And its corresponding message identifier.
  • FIG. 8 is a schematic flowchart of a method for a first embodiment of a management session when a user replaces a terminal according to the present invention.
  • the general message terminal Before and after the user replaces the terminal, the general message terminal is used, and the message content of the selected session is the same regardless of the terminal of the communication partner.
  • the general messaging system user Bob the universal messaging system user ID is 12345, and the support is short.
  • the general messaging system user Alice the universal messaging system user ID is 45678, supports SMS and Email.
  • the session ID record table saved on the server and Bob client is:
  • the session ID record table saved on the Alice client is:
  • the replaced terminal is a universal message terminal that supports SMS and MMS.
  • the method steps for managing the session when the user replaces the terminal are as follows:
  • step S500 Bob opens the terminal, logs into the general message system, and sends a login request message to the general message server.
  • the program code is as follows:
  • ⁇ !-- : 2 means SMS, refers to the supported message types —> ⁇ TargetMode>2 ⁇ /TargetMode>
  • step S501 after receiving the login request, the server verifies the identity of Bob, and the Bob login is accepted. After completing the login process to Bob, the session corresponding to Bob is searched.
  • step S502 the universal message server returns a login response message to the general message client, and the program code is as follows:
  • step S503 Bob's client displays to Bob that a call is being made with Alice and Mike.
  • the client establishes a session identification record table and records the session identifier: Primary session ID source user target user current serial number
  • step S504 after receiving the message, the server retains the 456780001 session. Aborting the session of 123450001, and releasing the corresponding message of 123450001 to identify the corresponding storage information;
  • step S505 the universal message server sends the message identifier in the message identifier storage module corresponding to the selected primary session identifier or a message to the general message client.
  • Alice receives the message identifier from Bob.
  • the source user Bob in the message identifier is different from the previous 13601119999, and the session identification record table saved in itself is updated to the content of the table in step S503. .
  • FIG. 8 it is a schematic flowchart of a method for managing a second embodiment of a user when a user replaces a terminal according to the present invention
  • the dedicated message terminal When the user replaces the terminal, the dedicated message terminal is used, and after the replacement, the universal message terminal is used, and the other party is a general message terminal, for example:
  • the general messaging system user Alice the universal messaging system user ID is 45678, supports SMS and Email.
  • the replaced terminal is a universal message terminal, supporting SMS and MMS.
  • step S500 Bob opens the terminal, logs into the general message system, sends a login request message to the general message server, and provides the communication address used by the previous terminal.
  • the program code is as follows:
  • step S501 after receiving the login request, the server verifies the identity of the Bob, and the Bob login is accepted. After completing the login process for Bob, look for the original terminal contact method: 13601119999 The corresponding session, update 13601119999 to Bob.
  • the server's session ID record table is: Primary Session ID Source User Target User Current Serial Number
  • step S502 the universal message server returns a login response message to the replaced universal message client:
  • Bob's client displays to Bob that a call is being made with Alice, and Bob chooses to continue.
  • the general message client establishes a session identification record table, records the session identifier, as in the form in step S501, and returns a session update message to the server.
  • step S504 after receiving the session update message, the server reserves the 456780001 session.
  • step S505 the universal message server sends a call record delivery message to the replaced client. It should be noted that when Bob and Alice continue to communicate, Alice receives the message identifier from Bob. The source user Bob in the message identifier is different from the previous 13601119999, and the session identification record table saved in itself is updated to the content of the table in step S501. .
  • FIG. 9 is a schematic flowchart of a method for a third embodiment of a management session when a user replaces a terminal according to the present invention.
  • the replacement is a general message terminal
  • the replacement is a dedicated message terminal
  • the communication partner is a general message terminal.
  • the general message system user Bob the universal message system user ID is 12345, and supports short messages;
  • General messaging system user Alice the universal messaging system user ID is 45678, supports SMS and
  • the session ID record table saved on the server and Bob client is:
  • the session representation record saved on the Alice client is:
  • the replaced terminal is a traditional message terminal that supports short messages.
  • the method steps for managing the session when replacing the terminal are as follows:
  • step S600 Bob sends a replacement terminal notification message to the server before replacing the terminal.
  • the program code is as follows: ⁇ CPM-CSP-Message
  • step S601 after receiving the replacement terminal notification message, the universal message server retains the 456780001 session.
  • the session of 123450001 is aborted, and the corresponding storage information of the message corresponding to 123450001 is released.
  • Its session ID record table is as follows: Primary session ID source user target user current serial number
  • step S602 the universal message server encapsulates the message identifier stored in the message identifier storage module corresponding to 456780001 in a short message and sends it to the traditional message terminal of Bob.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé de gestion de conversation consistant à : générer une marque de conversation principale destinée à la présente conversation; stocker l'enregistrement de conversation comprenant la marque de conversation principale; recevoir le message de demande de conversation; rechercher la marque de conversation principale dans l'enregistrement de conversation, et établir la conversation du côté communication correspondant à la marque de conversation principale. L'invention concerne également un client de message universel et un serveur de message universel.
PCT/CN2007/070981 2006-11-01 2007-10-30 Procédé de gestion de conversation, client de message universel et serveur de message universel associés WO2008052476A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 200610123196 CN1953386B (zh) 2006-11-01 2006-11-01 管理会话的方法、通用消息客户端及服务器
CN200610123196.9 2006-11-01

Publications (1)

Publication Number Publication Date
WO2008052476A1 true WO2008052476A1 (fr) 2008-05-08

Family

ID=38059528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070981 WO2008052476A1 (fr) 2006-11-01 2007-10-30 Procédé de gestion de conversation, client de message universel et serveur de message universel associés

Country Status (2)

Country Link
CN (1) CN1953386B (fr)
WO (1) WO2008052476A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105635249A (zh) * 2015-12-18 2016-06-01 小米科技有限责任公司 会话管理方法及装置
CN114024998A (zh) * 2021-11-11 2022-02-08 瑞斯康达科技发展股份有限公司 一种基于netconf协议的支持多会话的方法和装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1953386B (zh) * 2006-11-01 2010-09-29 华为技术有限公司 管理会话的方法、通用消息客户端及服务器
CN101453483B (zh) * 2007-11-29 2012-05-02 华为技术有限公司 会话历史记录的存储处理和查询方法、系统和装置
CN101997964A (zh) * 2009-08-13 2011-03-30 中国电信股份有限公司 一种移动通信终端及其联系记录的处理方法
CN102208988B (zh) * 2010-03-29 2013-09-11 华为技术有限公司 消息处理方法、系统及设备
CN103618747B (zh) * 2013-12-11 2016-09-21 中国联合网络通信集团有限公司 一种实现sip信息服务的方法及系统
CN110430124B (zh) * 2019-08-05 2022-08-19 腾讯科技（深圳）有限公司 未读标记处理方法、装置、系统、存储介质和计算机设备
CN111641690B (zh) * 2020-05-20 2022-09-02 北京字节跳动网络技术有限公司 会话消息处理方法、装置及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002032072A2 (fr) * 2000-10-10 2002-04-18 Intel Corporation Gestion de la clientele a distance
CN1492656A (zh) * 2002-10-25 2004-04-28 �Ҵ���˾ 在多通道上共享应用程序会话信息的方法、装置和系统
CN1953386A (zh) * 2006-11-01 2007-04-25 华为技术有限公司 管理会话的方法、通用消息客户端及服务器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002032072A2 (fr) * 2000-10-10 2002-04-18 Intel Corporation Gestion de la clientele a distance
CN1492656A (zh) * 2002-10-25 2004-04-28 �Ҵ���˾ 在多通道上共享应用程序会话信息的方法、装置和系统
CN1953386A (zh) * 2006-11-01 2007-04-25 华为技术有限公司 管理会话的方法、通用消息客户端及服务器

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105635249A (zh) * 2015-12-18 2016-06-01 小米科技有限责任公司 会话管理方法及装置
CN105635249B (zh) * 2015-12-18 2020-01-07 小米科技有限责任公司 会话管理方法及装置
CN114024998A (zh) * 2021-11-11 2022-02-08 瑞斯康达科技发展股份有限公司 一种基于netconf协议的支持多会话的方法和装置
CN114024998B (zh) * 2021-11-11 2023-05-23 瑞斯康达科技发展股份有限公司 一种基于netconf协议的支持多会话的方法和装置

Also Published As

Publication number Publication date
CN1953386A (zh) 2007-04-25
CN1953386B (zh) 2010-09-29

Similar Documents

Publication Publication Date Title
JP5622802B2 (ja) 統合ｉｐメッセージングサービスにおけるメッセージスレッドを管理する方法及びシステム
WO2008052476A1 (fr) Procédé de gestion de conversation, client de message universel et serveur de message universel associés
US8078153B2 (en) System and method for dynamic provisioning of contextual-based identities
WO2008003255A1 (fr) Procédé de personnalisation de pseudonyme dans un message, et appareil, serveur de message et terminal associés
KR20110081935A (ko) 컴퓨터 디바이스를 위한 ｓｍｓ 기술
US8825772B2 (en) System and method for operating a server for real-time communication of time-based media
WO2009026822A1 (fr) Procédé, système et appareil d'interfonctionnement de messages
JP2005318503A (ja) プレゼンスサーバ、セッション制御サーバ、パケット中継システム、サーバ、及びシステム
WO2007000091A1 (fr) Procédé et système destinés à limiter les temps de transfert d’un message multimédia pour le centre de service de messagerie multimédia mmsc
JP2013507678A (ja) コンバージドｉｐメッセージング（ｃｐｍ）とショートメッセージサービス（ｓｍｓ）との間のインターワーキングサービスを提供するための方法及びインターネットプロトコルショートメッセージゲートウェイ（ｉｐ−ｓｍ−ｇｗ）
EP2456144B1 (fr) Procédé, dispositif et système pour identifier un service
KR100779012B1 (ko) 타 메신저간 통신 시스템 및 방법
US20070160085A1 (en) Method and system for transmitting supplementary data, and communication terminal
US9900353B2 (en) Method and apparatus for enabling communications between users
CA2834838C (fr) Transport a base de sms pour la discussion en ligne sur des plateformes multiples
EP2453681A1 (fr) Système et procédé pour le routage d'une conversation d'un protocole d'ouverture de session
CN103368821A (zh) 发送语音消息的方法及系统、融合消息服务器及客户端
CN103379017B (zh) 语音留言方法及系统、融合消息服务器及客户端
US20100112985A1 (en) Method and system for identifier mapping to service capability
JP2011259277A (ja) セッション制御プロトコル対応型ネットワークシステム、発着信制御方法および発着信制御プログラム
KR100549684B1 (ko) Ｓｉｐ 프로토콜을 이용한 발신자 이미지 표시 서비스시스템 및 방법과 이를 위한 통신 단말
US20090227246A1 (en) Mobile communication in a network-device environment
WO2011153772A1 (fr) Procédé et système d'obtention de multiples informations instantanées
WO2012151811A1 (fr) Procédé et dispositif de traitement d'un message multimédia
KR100784635B1 (ko) 이동 통신망에서의 엠엠에스 제공 시스템 및 방법

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: 07817172

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: 07817172

Country of ref document: EP

Kind code of ref document: A1